Coordination system and coordination 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 linkage system for linking a plurality of systems and a linkage control method. [Background technology]

[0002] JP 2021-152860 A (Patent Document 1) discloses a collaboration system in a building environment that includes a building management system used by building managers to manage buildings and a general IoT (Internet of Things) environment provided to general users.

[0003] This coordination system includes a coordination control device that executes coordination control so as to realize coordination of predetermined functions between a device group including an equipment-compatible device included in the building management system and a device in the general IoT environment. As one aspect of application coordination between the device in the building management system and the device in the general IoT environment, application coordination is possible between the device in the building management system and one or more predetermined devices in the general IoT environment as coordination destinations, triggered by a coordination command sent from the device in the building management system. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2021-152860 A Summary of the Invention [Problem to be solved by the invention]

[0005] When two systems need to work together, one system sends a command to the other requesting that they work together, and the other system that receives the command executes the process according to the command. This is how the two systems work together.

[0006] However, when the vendors responsible for the development, construction, and operation of the two systems are different, the device expressions (e.g., ID (identifier), device name, network address, function name, etc.) used in commands requesting cooperation may differ from each other. Therefore, when one system sends a command specifying a target device to the other system, the other system that receives the command cannot interpret the expression used in the command, resulting in a problem in which the process according to the command cannot be executed.

[0007] The present disclosure has been made in consideration of the above problems, and its purpose is to provide an integration system and an integration control method that can easily achieve integration between two systems that use different device representations in commands that require integration. [Means for solving the problem]

[0008] According to an aspect of the present disclosure, a linkage system includes a first system and a second system that manages a management target in cooperation with the first system. The management target includes a plurality of first devices and a plurality of second devices. The first system includes at least one first computer that is communicatively connected to the plurality of first devices and manages the plurality of first devices, and a first model that defines a relationship between the at least one first computer and the plurality of first devices. The second system includes at least one second computer that is communicatively connected to the plurality of second devices and manages the plurality of second devices, and a second model that defines a relationship 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.

[0009] According to another aspect of the present disclosure, there is provided a cooperative control method for managing managed objects by coordinating a first system and a second system. The managed objects include a plurality of first devices and a plurality of second devices. The first system includes at least one first computer communicatively connected to the plurality of first devices and managing the plurality of first devices, and a first model defining a relationship between the at least one first computer and the plurality of first devices. The second system includes at least one second computer communicatively connected to the plurality of second devices and managing the plurality of second devices, and a second model defining a relationship between the at least one second computer and the plurality of second devices. The cooperative control method includes a step of updating the first model by the at least one first computer acquiring the second model from the second system and integrating the acquired second model with the first model, and a step of writing a command according to a definition in the updated first model and transmitting the command to the at least one second computer when the first system cooperates with the second system. Effect of the Invention

[0010] According to the present disclosure, it is possible to easily realize cooperation between a plurality of systems in which different device representations are used in commands that request cooperation. [Brief description of the drawings]

[0011] [Figure 1] 1 is a diagram illustrating an example of a building management system to which a linkage system according to a first embodiment is applied. [Diagram 2] FIG. 2 is a block diagram showing an example of a functional configuration of a central monitoring system and a lighting system. [Diagram 3] FIG. 13 is a diagram showing an example of a vocabulary list in the central monitoring system. [Figure 4] FIG. 13 is a diagram showing an example of a vocabulary list in a lighting system. [Diagram 5] FIG. 1 is a diagram illustrating an example of a common model that defines a central monitoring system. [Figure 6]FIG. 1 is a diagram showing an example of a common model that defines a lighting system. [Figure 7] 13 is a diagram illustrating a process flow in a common model exchange unit. FIG. [Figure 8] FIG. 13 is a diagram showing an example of a common model after combination in a central monitoring system. [Figure 9] 11A and 11B are diagrams illustrating an example of processing in a collaboration request unit and a collaboration response unit. [Figure 10] 13A and 13B are diagrams illustrating another example of the processing in the collaboration request unit and the collaboration response unit. [Figure 11] FIG. 1 is a diagram illustrating an example of a common model that defines a central monitoring system. [Figure 12] FIG. 1 is a diagram showing an example of a common model that defines a lighting system. [Figure 13] FIG. 13 is a diagram showing an example of a common model after combination in a central monitoring system. [Figure 14] 11A and 11B are diagrams illustrating an example of processing in a collaboration request unit and a collaboration response unit. [Figure 15] 13A and 13B are diagrams illustrating another example of the processing in the collaboration request unit and the collaboration response unit. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present disclosure will now be described in detail with reference to the accompanying drawings, in which the same or corresponding parts in the drawings are designated by the same reference characters and will not be described repeatedly.

[0013] Embodiment 1 <Examples of application of linked systems> Fig. 1 is a diagram illustrating an example of a building management system to which a linkage system according to a first embodiment is applied. As illustrated in Fig. 1, the building management system is a system for managing a plurality of devices (facility devices and measuring 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 linkage system according to this embodiment realizes linkage between the central monitoring system 100 and the lighting system 200.

[0014] The central monitoring system 100 is a system that monitors and controls the operating states of facility devices installed in a 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 one embodiment of the "first system."

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

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

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

[0018] The power measurement controller 130 is connected to the management server 110 via a network 300. The power meter 160 is installed in a building. The power measurement controller 130 is connected to the power meter 160 so as to be able to communicate with the power meter 160, and manages the measurement value of the power meter 160.

[0019] The management server 110 receives measurement value data of the temperature sensors 140_1-140_4 from the air conditioning controller 120. The management server 110 also receives measurement value data of the watt-hour meter 160 from the power measurement controller 130. The management server 110 generates a control command for controlling the operation of the indoor unit 150 based on these received data, 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-140_4, the indoor unit 150, and the watt-hour meter 160 correspond to an embodiment of the "multiple first devices."

[0020] Lighting system 200 is a system that monitors and controls the operating states 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. Lighting system 200 corresponds to one embodiment of a "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 an example of "at least one second controller".

[0023] The illuminance sensor 230 and the lighting fixture 240 are installed in the building. The lighting controller 220 is communicatively connected to the illuminance sensor 230 and the lighting fixture 240, and manages the measurement value of the illuminance sensor 230 and controls the operation of the lighting fixture 240.

[0024] Management server 210 receives data of measurements by illuminance sensor 230 from lighting controller 220. Management server 210 generates control commands for controlling operation of lighting device 240 based on the received data, and transmits the generated control commands to lighting controller 220. Lighting controller 220 controls operation of lighting device 240 in accordance with the control commands from management server 210. Illuminance sensor 230 and lighting device 240 correspond to an example of the “plurality of second devices”.

[0025] In the building management system shown in FIG. 1, the indoor unit 150 and the lighting fixture 240 correspond to an example of "facility equipment" installed in the building, and the temperature sensors 140_1 to 140_4, the watt-hour meter 160, and the illuminance sensor 230 correspond to an example of "measurement equipment" installed in the building. The facility equipment installed in the building is not limited to this, and may include air conditioners, elevators, water supply and drainage equipment, sanitary equipment, disaster prevention equipment, and crime prevention equipment other than the indoor units. Furthermore, the measurement equipment is not limited to this, and may include surveillance cameras, surveillance monitors, and the like. A controller for managing these facility equipment and measurement equipment may be connected to the management server 110 or the management server 210 via the network 300.

[0026] <Hardware configuration of management server and controller> In the building management system shown in FIG. 1, the management server 110, the air conditioning controller 120, the power measurement controller 130, and the lighting controller 220 are mainly configured using computers.

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

[0028] The CPU 101 loads a program stored in the ROM 103 into the RAM 102 and executes the program to implement various functions of the management server 110. The ROM 103 stores a program in which the processing procedures of the management server 110 are written.

[0029] The RAM 102 serves as a working area when the CPU 101 executes a program, and temporarily stores the program, data required for executing the program, and the like.

[0030] The storage device 105 is a storage for storing various information, and stores information on the facility devices and measuring devices installed in the building. The storage device 105 also stores a common model in the central monitoring system 100. The common model will be explained in detail later. The storage device is, for example, a hard disk drive (HDD) or a solid state drive (SDD).

[0031] The management server 110 exchanges signals and data with the air conditioning controller 120 and the power measurement controller 130 via the communication IF 104. When the central monitoring system 100 and the lighting system 200 are linked, the management server 110 exchanges signals and data with the management server 210 of the lighting system 200 via the communication IF 101.

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

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

[0034] The CPU 121 loads a program stored in the ROM 123 into the RAM 122 and executes it to realize various functions of the air conditioning controller 120. The ROM 123 stores a program in which the processing procedures of the air conditioning controller 120 are written.

[0035] The RAM 122 serves as a working area when the CPU 121 executes a program, and temporarily stores the program and data required for executing the program. The air conditioning controller 120 may also include a non-volatile storage device. The storage device is, for example, an HDD or SSD.

[0036] The air conditioning controller 120 communicates with the management server 110 via the communication IF 124. Measurement value data of the temperature sensors 140_1 to 140_4 is input to the air conditioning controller 120 via the I / O interface 125. The air conditioning controller 120 outputs a control signal for controlling the operation of the indoor unit 150 to the indoor unit 150 via the I / O interface 125.

[0037] Although not shown in the figures, the power measurement controller 130 and the lighting controller 220 also have the same configuration as the air conditioning controller 120.

[0038] <Functional configuration of the linked system> The linkage system according to the present embodiment is a system for realizing linkage between the central monitoring system 100 and the lighting system 200 in the building management system shown in Fig. 1. The central monitoring system 100 and the lighting system 200 work together to comprehensively manage a plurality of facility devices (such as indoor units 150 and lighting fixtures 240) in a building, thereby enabling the efficient operation of the plurality of facility devices and realizing a comfortable living environment.

[0039] When these two systems are to be linked, one system sends a command to the other system requesting the linkage. This command is, for example, a command requesting data of measurements from a measuring device included in the other system, or a command instructing the setting values ​​of facility devices included in the other system.

[0040] The other system that receives the command executes the process according to the command. For example, the other system sends the measurement data of the measuring device specified in the command to the first system. Or, the other system operates the facility equipment according to the setting value specified in the command. In this way, the two systems are linked together.

[0041] However, when the vendors in charge of developing, building and operating the central monitoring system 100 and the lighting system 200 are different, the expressions (e.g., ID (identifier), device name, network address, function name, etc.) of facility equipment and measuring equipment used in commands may differ from each other. Therefore, when one system transmits a command specifying a target facility equipment or measuring equipment to the other system, the other system that receives the command cannot interpret the expression used in the command, resulting in a problem that the system cannot execute processing according to the command.

[0042] In order to solve such problems, the collaboration system of this embodiment is configured so that each system defines a common model that represents the devices that are to be managed by its own system, and exchanges this common model in advance with the system with which it is to collaborate.

[0043] In the above configuration, when each system receives a common model from a system with which it is to cooperate, it updates the common model of its own system by integrating the common model of its own system with the common model of the system with which it is to cooperate. Then, when cooperating with the system with which it is to cooperate, it writes a command according to the definition in the updated common model and transmits the command to the system with which it is to cooperate. The system with which it is to cooperate that receives the command can interpret the command by referring to the updated common model of its own system. As a result, it becomes possible to execute processing according to the interpreted command.

[0044] Fig. 2 is a block diagram showing an example of the functional configuration of the central monitoring system 100 and the lighting system 200. Fig. 2 shows the functional configuration of a portion related to a cooperative process in each of the central monitoring system 100 and the lighting system 200. The functional configuration is the same in the central monitoring system 100 and the lighting system 200. The functional configuration is realized by each of the management server 110 of the central monitoring system 100 and the management server 210 of the lighting system 200 executing a program.

[0045] 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. The configuration of each unit will be described below assuming a case where the central monitoring system 100 transmits a command requesting cooperation to the lighting system 200.

[0046] (Common Model Storage Unit 10) The common model storage unit 10 stores a common model for its own system. In this specification, a "common model" defines the relationship between at least one computer and multiple devices. The common model is generated, for example, by a vendor in charge of developing, building, and operating the system.

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

[0048] Another aspect is that the common model can utilize ontology definitions such as the Brick Schema, a unified building metadata schema and an open specification for the semantic representation of physical, logical and virtual assets in a building and their relationships. An ontology is a description of how the target world is perceived (conceptualized).

[0049] In yet another aspect, the common model can utilize the drawing definition of the building, such as BIM (Building Information Modelling). BIM is a modelling method for information about buildings, and is a comprehensive database of buildings, including their shapes.

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

[0051] 3 is a diagram showing an example of a vocabulary list in the central monitoring system 100. For example, when commands and data are written in Japanese in the central monitoring system 100, the meaning of each term is written in Japanese in the vocabulary list. For example, the first line of the vocabulary list shows that "B-OWS" means "management server." Furthermore, the second line of the vocabulary list shows that "B-BC" means "controller."

[0052] 4 is a diagram showing an example of a vocabulary list in the lighting system 200. For example, when commands and data are described in English in the lighting system 200, the meaning of each term is described in English in the vocabulary list. For example, the first line of the vocabulary list indicates that "B-OWS" means "management server." Furthermore, the second line of the vocabulary list indicates that "B-BC" means "controller."

[0053] Once the vocabulary list is defined, a common model is then generated that expresses 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 express each computer and each device. In the common model, the relationships between the at least one computer and multiple devices are expressed in a hierarchical structure. The common model has, for example, a tree structure, but is not limited to this. The common model is generated for each system and stored in the storage device 105 (FIG. 1) of the management server.

[0054] Fig. 5 is a diagram showing an example of a common model that defines the central monitoring system 100. As shown in Fig. 5(A), in the common model, the relationships among the management server 110, the air conditioning controller 120, 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 (Fig. 3). The common model shown in Fig. 5(A) corresponds to one embodiment of the "first model".

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

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

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

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

[0059] Fig. 6(B) is a table representation of the common model shown in Fig. 6(A). In the table, the relationship between each element of the common model and other elements is described. The common model shown in Fig. 6(A) is stored in the common model storage unit 10 of the lighting system 200.

[0060] (Common Model Exchange 20) 2, the common model exchange unit 20 exchanges common models with the systems that will be linked. When the common model exchange unit 20 receives a common model from the system that will be linked, the common model exchange unit 20 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 system that will be linked.

[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 combination unit 25, and an update unit 26.

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

[0063] The transmission unit 22 transmits the common model of the system of interest acquired by the acquisition unit 21 via the communication IF unit 50 to the system to be coordinated.

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

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

[0066] The combining unit 25 combines the elements extracted by the extracting unit 24 with the common model of its own system, thereby integrating the common model of its own system with the common model of the system with which it is linked.

[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 the combination.

[0068] Fig. 7 is a diagram for explaining the flow of processing in the common model exchange unit 20. Fig. 7 shows the flow of processing 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 Fig. 7 corresponds to the "common model of its own system". Also, the common model of the lighting system 200 shown in the upper right of Fig. 7 corresponds to the "common model of the system to be linked". Both of these two common models are expressed in 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 do not exist in the common model of the central monitoring system 100 .

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

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

[0072] Although not shown in the figure, the common model exchange unit 20 of the lighting system 200 also executes the same processing as in Fig. 7. That is, the common model of the lighting system 200 and the common model of the central monitoring system 100 are integrated, whereby the common model of the lighting system 200 is updated.

[0073] (Cooperation request unit 30) 2, the cooperation request unit 30 transmits a command requesting cooperation to a system that is to be a cooperation destination. When transmitting a command requesting cooperation from the central monitoring system 100 to the lighting system 200, the cooperation request unit 30 of the central monitoring system 100 describes the command according to the definition in the common model stored in the common model storage unit 10, and transmits the generated command to the lighting system 200.

[0074] Specifically, the collaboration request unit 30 includes a collaboration process determination unit 31, a transmission time common model acquisition unit 32, a common model association processing unit 33, a request command transmission unit , and a request command response reception unit .

[0075] The cooperation process determining unit 31 determines a process to cooperate with the lighting system 200, and generates a command to request the lighting system 200 to perform the determined process. Specifically, when the central monitoring system 100 cooperates with the lighting system 200 to control the lighting device 240, the cooperation process determining unit 31 generates a command to the lighting system 200 to request a measurement value of the illuminance sensor 230. Alternatively, the cooperation process determining unit 31 generates a command to the lighting system 200 to set the illuminance of the lighting device 240.

[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 correspondence processing unit 33 converts the command generated by the collaboration processing determination unit 31 into a command that can be interpreted by the lighting system 200 by corresponding the terms used in the command to definitions in the common model (FIG. 8).

[0078] As an example, it is assumed that the cooperation process determining unit 31 generates a command "acquire measurement value of illuminance sensor" requesting the measurement value of the illuminance sensor 230 as shown in FIG.

[0079] In this case, the common model correspondence processing unit 33 uses the relationship "I-Sensor is the AI ​​of B-BC" and the relationship "B-OWS manages B-BC" defined in the common model to convert the command into "GET http: / / <ip-address> / b-ows / b-bc / i-sensor HTTP / 1.1" command. <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 relationship between B-OWS, B-BC, and I-Sensor defined in the common model.

[0080] As another example, assume that, as shown in FIG. 10, collaboration process determination unit 31 generates a command “set illuminance of lighting device 240 to 80 lx” to set the illuminance of lighting device 240 to a predetermined value (e.g., 80 lx).

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

[0082] The request command transmitting unit 34 transmits the command generated by the common model association processing unit 33 to the management server 210 of the lighting system 200 via the communication IF 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] (Linkage response unit 40) Returning to Fig. 2, the collaboration response unit 40 receives a command requesting collaboration from the collaboration source system. When a command requesting collaboration is transmitted from the collaboration request unit 30 of the central monitoring system 100 to the lighting system 200, the collaboration response unit 40 of the lighting system 200 receives the command. The collaboration 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 the lighting device 240 in accordance with the interpreted command.

[0085] Specifically, the collaboration response unit 40 includes a collaboration process receiving unit 41 , a receiving time common model acquiring unit 42 , a conversion processing unit 43 , a request command executing unit 44 , and a request command response transmitting unit 45 .

[0086] The linkage processing receiving unit 41 receives a command from the central monitoring system 100 via the communication IF 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 the common model and converts the terminology used in the command into the terminology used in the own system. <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 "obtain analog input from the illumination sensor" based on the relationship "I-Sensor is the AI ​​of B-BC" and the relationship "B-OWS manages B-BC" defined in the common model. Therefore, the conversion processing unit 43 converts the command into a command "get the measured value of the illuminance sensor."

[0089] As another example, as shown in Figure 9, <ip-address>When the command ". / b-ows / b-bc / lighting HTTP / 1.1 {"value":80}" is received, the conversion processing unit 43 interprets that "lighting" is "the lighting equipment" and that the command means "set the analog output for the lighting equipment to 80" based on the relationship "Lighting is the AO of B-BC" defined in the common model and the relationship "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 Fig. 2, the request command execution unit 44 manages the illuminance sensor 230 and the lighting device 240 in accordance with the command converted by the conversion processing unit 43. Specifically, the request command execution unit 44 acquires the measured value of the illuminance sensor 230 in accordance with a command "get the measured value of the illuminance sensor". Alternatively, the request command execution unit 44 sets the illuminance of the lighting device 240 to 80lx in accordance with a command "set the illumination of the lighting equipment to 80", and controls the operation of the lighting device 240 so that the illuminance becomes the set illuminance.

[0091] The request command response transmitting unit 45 transmits a response to the received command to the system that is the source of the cooperation via the communication IF unit 50. Specifically, the request command response transmitting unit 45 transmits the measurement value of the illuminance sensor 230 acquired in accordance with the command "get the measured value of the illuminance sensor" to the central monitoring system 100.

[0092] Alternatively, the request command response transmitter 45 transmits to the central monitoring system 100 information that the illuminance of the lighting equipment 240 has been set in accordance with 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 the 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 drawings, when the lighting system 200 requests the central monitoring system 100 to cooperate, the cooperation request unit 30 of the lighting system 200 transmits a command requesting cooperation to the central monitoring system 100. At this time, the cooperation request unit 30 converts the command into a command that can be interpreted by the central monitoring system 100 by associating terms used in the command with definitions in the common model.

[0095] Then, when the cooperation response unit 40 of the central monitoring system 100 receives a command from the lighting system 200, it interprets the command by referring to the common model, and manages the indoor unit 150, the temperature sensors 140_1 to 140_4, and the watt-hour meter 160 in accordance with the command. Then, the cooperation response unit 40 transmits a response to the received command to the lighting system 200.

[0096] As described above, according to the linkage system of the first embodiment, each system defines a common model that expresses the relationship between at least one computer and a plurality of devices in its own system, and exchanges this common model in advance with the system to be linked. In a situation where the first system and the second system link together, the first system can generate a command requesting linkage with the second system in association with the common model, and transmit the generated command to the second system. Then, the second system can 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 expressions of commands are different between the first and second systems, each system can understand the device indicated by the command from the other system, the connection relationship between the device and other devices, and the requested processing content. As a result, the linkage between the first system and the second system can be easily realized.

[0097] Embodiment 2 In the first embodiment, a configuration has been described in which a common model is generated in which the relationships between a plurality of devices included in each system are defined by an ontology, and the common model is exchanged in advance between a plurality of systems.

[0098] In the second embodiment, a configuration is described in which a common model is generated by adding network information (instance) specific to the system to the ontology, and the common model is exchanged in advance between multiple systems. Note that the configuration of the federation system according to the second embodiment is the same as that of the federation system according to the first embodiment (FIGS. 1 and 2) except for the configuration of the common model, and therefore a description thereof is omitted.

[0099] (Common model) Fig. 11 is a diagram showing an example of a common model that defines the central monitoring system 100. As shown in Fig. 11(A), in the common model, the relationships among the management server 110, the air conditioning controller 120, 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 (Fig. 3).

[0100] The common model shown in Fig. 11(A) differs from the common model shown in Fig. 5(A) in that it includes information indicating the configuration of each element on the network. As shown in Fig. 1, the central monitoring system 100 includes one management server 110, two controllers 120, 130, four temperature sensors 140_1 to 140_4, one indoor unit 150, and one watt-hour meter 160. In the common model, the connections between these devices are described using ontology.

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

[0102] And by connecting "B-BC1" and "B-BC2" to "B-OWS1" with "Management", the relationship "B-OWS1 manages B-BC1 and B-BC2" is expressed. Also, by connecting "T-Sensor1", "T-Sensor2", and "T-Sensor3" to "B-BC1" with "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" with "DO", the relationship "PAC-IC1 is the DO of B-BC1" is expressed. By connecting "P-Meter1" to "B-BC2" with "PI", the relationship "P-Meter1 is the PI of B-BC2" is expressed.

[0103] Fig. 11(B) is a table representation of the common model shown in Fig. 11(A). In the table, the relationship between each element of the common model and other elements is described. The common model is stored in the common model storage unit 10 of the central monitoring system 100.

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

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

[0106] Fig. 12(B) is a table representation of the common model shown in Fig. 12(A). In the table, the relationship between each element of the common model and other elements is described. The common model is stored in the common model storage unit 10 of the lighting system 200.

[0107] In this way, the common model corresponds to a knowledge network (knowledge graph) that systematically connects multiple devices that make up a single system and represents them in a graph structure. Because it uses ontology, the representation of each device can be made common regardless of the system.

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

[0109] Fig. 13 is a diagram showing an example of a common model after the combination in the central monitoring system 100. As shown in Fig. 13, the common model after the combination is obtained by linking the common model shown in Fig. 12(A) to the common model shown in Fig. 11(A). According to the common model after the combination, it is possible to know the network of the linked system. The common model after the combination is stored in the common model accumulation unit 10 by the update unit 26. In this manner, the common model of the central monitoring system 100 is updated.

[0110] Although not shown in the figure, the common model exchange unit 20 of the lighting system 200 also executes the same processing as in Fig. 7. That is, the common model of the lighting system 200 and the common model of the central monitoring system 100 are integrated, whereby the common model of the lighting system 200 is updated.

[0111] In the second embodiment, as in the first embodiment, the collaboration request unit 30 generates a command requesting collaboration using the common model stored in the common model storage unit 10, and transmits the generated command to the collaboration destination system. When the collaboration response unit 40 receives a command requesting collaboration from the collaboration source system, it interprets the command by referring to the common model stored in the common model storage unit 10, and manages the facility devices and measuring devices in accordance with the interpreted command. Therefore, in the second embodiment, the same effects as in the first embodiment can be obtained.

[0112] As an example, assume that the cooperation process determination unit 31 of the central monitoring system 100 generates a command to “acquire the measurement value of the illuminance sensor” requesting the measurement value of the illuminance sensor 230, as shown in FIG.

[0113] In this case, the common model correspondence processing unit 33 uses the relationship "I-Sensor1 is the AI ​​of B-BC3" and the relationship "B-OWS2 manages B-BC3" defined in the common model (FIG. 13) to convert the command into "GET http: / / <ip-address> / v1 / b-ows2 / b-bc3 / i-sensor1 HTTP / 1.1" command. <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 defined in the common model.

[0114] As another example, assume that the coordination processing decision unit 31 of the central monitoring system 100 generates a command “Set the illuminance of the lighting device 240 to a predetermined value (e.g., 80 lx)” as shown in FIG. 15 .

[0115] In this case, the common model correspondence processing unit 33 uses the relationship "Lighting1 is an AO of B-BC3" and the relationship "B-OWS2 manages B-BC3" defined in the common model (FIG. 13) to convert the command into "POST http: / / <ip-address> / 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 lighting fixture 240 in lighting system 200. The command is described according to the relationship between B-OWS2, B-BC3, and Lighting1 defined in the common model.

[0116] As described above, in the second embodiment, the cooperation request unit 30 of the central monitoring system 100 can transmit a command by specifying an equipment device or a measuring device of the lighting system 200 as a cooperation destination. The cooperation response unit 40 of the lighting system 200 can immediately know the equipment device or the measuring device specified by the received command by referring to the common model.

[0117] [Note] The above-described embodiment is a specific example of the following supplementary notes.

[0118] (Appendix 1) A first system; a second system for managing a management target in cooperation with the first system, The management target includes a plurality of first devices and a plurality of second devices, The first system comprises: at least one first computer communicatively connected to the plurality of first devices and managing the plurality of first devices; a first model that defines a relationship between the at least one first computer and the plurality of first devices; The second system comprises: at least one second computer communicatively connected to the plurality of second devices and managing the plurality of second devices; a second model that defines a relationship between the at least one second computer and the plurality of second devices; 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; The cooperating system, when cooperating with the second system, writes a command according to a definition in the updated first model and transmits the command to the at least one second computer.

[0119] (Appendix 2) 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 collaborative system described in Appendix 1, when receiving the command from the first system, interprets the command by referring to the updated second model, and manages the multiple second devices in accordance with the interpreted command.

[0120] (Appendix 3) The at least one first computer: Extracting elements from the second model that are not present in the first model; 3. The collaborative system of claim 1, further comprising: updating the first model by combining the extracted elements with the first model.

[0121] (Appendix 4) the first model defines a relationship between the at least one first computer and the plurality of first devices using an ontology; The collaboration system according to any one of claims 1 to 3, wherein the second model defines the relationship between the at least one second computer and the plurality of second devices using an ontology.

[0122] (Appendix 5) the first model includes first network information that defines a configuration of the at least one first computer and the plurality of first devices on a network using an ontology; the second model includes second network information that defines a configuration of the at least one second computer and the plurality of second devices on a network using an ontology; The at least one first computer: The collaboration system described in Appendix 4, which updates the first model by integrating the second network information in the second model obtained from the second system and the first network information in the first model.

[0123] (Appendix 6) The at least one first computer: The coordination system of claim 5, wherein when coordinating with the second system, the command is written based on the second network information in the updated first model.

[0124] (Appendix 7) the first system and the second system are configured to cooperate with each other to manage a plurality of devices installed in a building; The collaborative system according to any one of appendices 1 to 6, wherein the first model and the second model utilize an object definition in BACnet, an ontology definition in Brick Schema, or a drawing definition in BIM.

[0125] (Appendix 8) A cooperative control method for managing a managed object by coordinating a first system and a second system, comprising: The management target includes a plurality of first devices and a plurality of second devices, The first system comprises: at least one first computer communicatively connected to the plurality of first devices and managing the plurality of first devices; a first model that defines a relationship between the at least one first computer and the plurality of first devices; The second system comprises: at least one second computer communicatively connected to the plurality of second devices and managing the plurality of second devices; a second model defining a relationship between the at least one second computer and the plurality of second devices; The cooperative control method includes: said at least one first computer acquiring said second model from said second system and updating said first model by integrating said acquired second model with said first model; and when the first system cooperates with the second system, the at least one first computer writes a command according to a definition in the updated first model and sends the command to the at least one second computer.

[0126] (Appendix 9) said at least one second computer acquiring said first model from said first system and updating said second model by integrating said acquired second model with said first model; The collaborative control method described in Appendix 8, further comprising a step of: when the command is received 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.

[0127] Although the embodiments of the present disclosure have been described, the embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The scope of the present disclosure is defined by the claims, and it is intended to include all modifications within the scope and meaning equivalent to the claims. [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 decision unit, 32 transmission time common model acquisition unit, 33 common model correspondence processing unit, 34 request command transmission unit, 35 request command response reception unit, 40 cooperation response unit, 41 cooperation processing reception unit, 42 reception time common model acquisition unit, 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 to 140_4 temperature sensors, 150 indoor unit, 160 power meter, 200 lighting system, 220 lighting controller, 230 illuminance sensor, 240 lighting fixture, 300 network.

Claims

1. A first system; and a second system for managing a management target in cooperation with the first system, The management target includes a plurality of first devices and a plurality of second devices, The first system comprises: at least one first computer communicatively connected to the plurality of first devices and managing the plurality of first devices; a first model that defines a relationship between the at least one first computer and the plurality of first devices; The second system is at least one second computer communicatively connected to the plurality of second devices and managing the plurality of second devices; a second model that defines a relationship between the at least one second computer and the plurality of second devices; 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; When cooperating with the second system, the cooperating system writes a command according to a definition in the updated first model and transmits the command to the at least one second computer.

2. 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 collaboration system of claim 1, wherein when the command is received from the first system, the collaboration 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 Extracting elements from the second model that are not present in the first model; The collaboration system according to claim 1 , further comprising: updating the first model by combining the extracted elements with the first model.

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

5. the first model includes first network information that defines a configuration of the at least one first computer and the plurality of first devices on a network using an ontology; the second model includes second network information that defines a configuration of the at least one second computer and the plurality of second devices on a network using an ontology; The at least one first computer The collaboration system according to claim 4 , wherein the first model is updated by integrating the second network information in the second model acquired from the second system and the first network information in the first model.

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

7. the first system and the second system are configured to cooperate with each other to manage a plurality of devices installed in a building; The collaboration system according to claim 1 , wherein the first model and the second model utilize an object definition in BACnet, an ontology definition in Brick Schema, or a drawing definition in BIM.

8. A cooperative control method for managing a management target by coordinating a first system and a second system, comprising: The management target includes a plurality of first devices and a plurality of second devices, The first system comprises: at least one first computer communicatively connected to the plurality of first devices and managing the plurality of first devices; a first model that defines a relationship between the at least one first computer and the plurality of first devices; The second system is at least one second computer communicatively connected to the plurality of second devices and managing the plurality of second devices; a second model defining a relationship between the at least one second computer and the plurality of second devices; The cooperative control method includes: said at least one first computer acquiring said second model from said second system and updating said first model by integrating said acquired second model with said first model; A method of controlling collaboration, comprising the steps of: when the first system collaborates with the second system, the at least one first computer writing a command according to a definition in the updated first model and sending the command to the at least one second computer.

9. said at least one second computer acquiring said first model from said first system and updating said second model by integrating said acquired second model with said first model; The cooperative control method according to claim 8, further comprising a step of: when the command is received 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 according to the interpreted command.

Images