JP4647584B2 - Object mapping method, object mapping program, gateway device, device management system - Google Patents

Description

  The present invention relates to a method for mapping objects connected to different networks, a program thereof, a gateway device for executing the method in an equipment management network, and a device management system using the device.

Conventionally, “to obtain a gateway device that can improve response, reduce program development man-hours, and save labor in setting mapping data. As the technology for the purpose, “the first communication processing unit 30a, the second communication processing unit 30e, the first database 30d that holds information of the managed device 11, and the first database management unit” 30c, the second database 30g in which the first database 30d is converted into information required by the device management apparatus 21, the second database management means 30f, the first database 30d, and the second database 30g A database mapping unit 30h for matching corresponding items and a command distribution unit 30b for delivering a command to each unit and transferring the command while converting the command through the database mapping unit 30h are provided. (Patent Document 1).
JP 2000-244551 A (summary)

In the mapping between different types of networks as in the above-described conventional technology, mapping of object instances, which are models of devices connected to each network, or attributes (properties) of instances is normally performed. Data exchange takes place.
Thereby, even when the attribute of the instance is changed due to a change in the network configuration or the like, it can be easily handled by changing only the mapping information.
On the other hand, functions such as various conversion processes and various processes executed in association with data exchange cannot be changed by the above mapping, and are fixed for each type of device represented by the instance. When there is a need to change functions during property handling or maintenance, there is a problem that it is necessary to rewrite the software itself, which requires maintenance costs.
The present invention solves the above-described problems, can easily cope with a change in the network configuration, and can reduce the maintenance cost required for mapping, the object mapping method, the program thereof, and the equipment management network It is an object of the present invention to obtain a gateway device to be executed and a device management system using the device.

The mapping method between objects according to the present invention includes:
A method of defining the correspondence between objects connected to different networks (hereinafter referred to as mapping),
An attribute mapping table that defines the correspondence between attributes of each object instance;
A function mapping table for associating a function to be executed for an attribute included in one instance of the object for each attribute and a function for executing an attribute included in the other instance of the object for each attribute; ,
Provided with rewritable storage means storing
When mapping each object,
While referring to the attribute mapping table, associating attributes included in the instance of the mapping target object,
The function to be executed is associated with each attribute by referring to the function mapping table.

  According to the mapping method between objects according to the present invention, it is possible to easily change the mapping of functions provided in each object in addition to mapping between instances of objects and attributes, so it can easily cope with a change in network configuration. An object-to-object mapping method that can reduce the maintenance cost required for mapping is obtained.

Embodiment 1 FIG.
FIG. 1 is a schematic diagram conceptually showing functions of the gateway device according to Embodiment 1 of the present invention.
The gateway device according to the first embodiment includes a BACnet instance DB 100 that manages instances of managed objects in a management-side network (hereinafter, “BACnet” will be taken as an example. Details will be described later), and a facility device that is a managed device. And a facility net instance DB 101 that manages the current status of each facility device in a network (hereinafter “equipment network”) connected as an instance of an object representing the facility device.
The BACnet instance DB 100 and the equipment net instance DB 101 hold attributes (property) and attribute values of each object.
Further, the gateway device according to the first embodiment includes a BACnet function DB 102 and an equipment network function DB 103.
The BACnet function DB 102 holds a group of functions describing various functions provided on the BACnet, that is, various conversion processes performed at the time of data manipulation / monitoring and data exchange and various processes executed in association with the data exchange.・ We manage.
Similarly, the equipment network function DB 103 holds and manages a function group describing various functions provided on the equipment network.
The mapping DB 104 holds and manages mapping data that associates instance information and various functions on the BACnet with instance information and various functions on the equipment net.
The mapping execution unit 105 refers to the mapping DB 104 and performs a process of mapping an instance on the BACnet and an instance on the equipment net. The purpose and contents of the mapping process will be described later.
Note that “instance information” refers to attributes and attribute values of an instance.

The mapping execution means 105 can be implemented by software executed on an arithmetic device such as a CPU or a microcomputer.
Each DB can be mounted on a writable storage device such as a RAM, an HDD, or a flash memory. The mounting method may be matrix data in a matrix or may be stored in a relation table format. Further, middleware such as RDBMS may be mediated in the middle. In the following description, it is assumed that the data is stored in a table format.
In FIG. 1, a network interface for the gateway device to connect to each network is omitted, but it is assumed that a necessary interface is appropriately provided according to the communication protocol.

FIG. 2 shows an example of the configuration and data of the BACnet instance DB 100.
The BACnet instance DB 100 can be configured in a table format, for example (the same applies to the following DBs). The configuration example of FIG. 2 includes an “instance ID” column, an “attribute ID” column, and an “attribute value” column.
(1) “Instance ID” column This column stores IDs for specifying individual instances of managed objects configured on the BACnet side. A specific example of the management object on the BACnet will be described later with reference to FIG.
(2) “Attribute ID” column This column stores an ID for specifying an attribute (property) included in the instance specified by the value of the “Instance ID” column. The value in this column may be an ID for specifying an attribute, or may be specified directly by an attribute name if the name does not overlap.
Since different attributes are provided for different types of managed objects, the value in this column may differ for each managed object specified in the “Instance ID” column. In addition, since one managed object may have a plurality of attributes, there may be a plurality of rows having the same “instance ID” column value.
In the data example of FIG. 2, “attribute ID = 85” indicates an attribute “current value”.
(3) “Attribute Value” Column This column stores the actual value of the attribute specified by the values of the “Instance ID” column and the “Attribute ID” column.

FIG. 3 shows an example of the configuration and data of the equipment net instance DB 101.
The column configuration of the equipment net instance DB 101 is the same as that of the BACnet instance DB 100. However, the stored value is information representing individual equipment connected to the equipment net.
(1) “Instance ID” column This column stores IDs for specifying individual facility devices connected to the facility net. Specifically, an instance ID of an object representing the equipment is stored.
(2) “Attribute ID” column This column stores an ID for specifying an attribute included in the equipment specified by the “Instance ID” column. The value in this column may be an ID for specifying an attribute, or may be specified directly by an attribute name if the name does not overlap.
Since the attribute names provided differ depending on the type of equipment, the value in this column may differ for each equipment specified in the “Instance ID” column. In addition, since one facility device may have a plurality of attributes, there may be a plurality of rows having the same “instance ID” column value.
In the data example of FIG. 3, the equipment specified by “instance ID = 5001” has an attribute (operation state) of “attribute ID = 0”, an attribute (operation mode) of “attribute ID = 1”, and “attribute ID”. = 2 ”attribute (set temperature).
Similarly, the equipment specified by “instance ID = 7001” has an attribute (lighting state) of “attribute ID = 10” and an attribute (dimming state) of “attribute ID = 11”.
(3) “Attribute Value” Column This column stores the actual value of the attribute of the equipment specified by the values of the “Instance ID” column and the “Attribute ID” column.
In the data example of FIG. 3, the value of the attribute (set temperature) of “attribute ID = 2” of the equipment specified by “instance ID = 5001” is “29”.

FIG. 4 shows an example of the configuration and data of the BACnet function DB 102. In the configuration example of FIG. 4, the BACnet function DB 102 has a “function ID” column, a “function name” column, and a “function description” column.
The “Function ID” column is a function describing various functions provided on the BACnet, that is, various conversion processes performed at the time of data manipulation / monitoring and data exchange and various processes executed in association with the data exchange. Stores an ID for identification.
The “function name” column stores the name of the function specified by the value of the “function ID” column. The value in this column may be the function name itself or may indirectly specify the function using a function pointer or the like.
The “function description” column stores a simple function description of the function specified in the “function ID” column. Since this column is provided for convenience, it may be omitted.

FIG. 5 shows an example of the configuration and data of the equipment network function DB 103.
The column configuration of the facility network function DB 103 is the same as that of the BACnet function DB 102. However, the stored value is the ID, name, and function description of a function describing various functions provided on the equipment network.

  The specific mounting method of each DB may be, for example, a flat file that constitutes a table, or a virtual table realized on software.

  Here, before explaining the remaining configuration of FIG. 1, the purpose, contents, and problems of the mapping processing in the prior art will be described.

FIG. 16 illustrates the configuration of a facility equipment network management system in a building.
On each floor of the building 1601, equipment such as an air conditioner and lighting are laid. For each floor, facility equipment networks 1605a to 1605c (hereinafter, may be abbreviated as “equipment net”) connecting these equipments are configured. In each equipment net, a controller that collects the same kind of equipment is connected, and the same kind of equipment is connected under the controller.
In addition, an equipment management device 1602 for integrated management of equipment installed on each floor in the building 1601 is installed in a control room or the like.
The above-mentioned management target equipment is referred to as “managed equipment”.
Note that the gateway device on each floor in FIG. 16 is assumed to be compatible with a plurality of communication protocols used in the equipment network, so it is added that there is only one gateway device on each floor. .

In general, the device management apparatus 1602 often uses the BACnet protocol, which is a standard, as a protocol for communicating with each facility device for monitoring and control. On the other hand, equipment and control panels laid on each floor are not necessarily from the same manufacturer, and are not always directly monitorable / controllable by the BACnet protocol.
Therefore, a configuration is provided in which one gateway device 1604a to 1604c is provided between the two networks for each floor, the gateway device and each controller are connected, and even if the communication protocol is different, instructions are mutually converted to enable information communication. Is taken. Hereinafter, steps will be described.

(1) Communication using the BACnet protocol The device management apparatus 1602 in FIG. 16 performs communication using the BACnet protocol and transmits a command command when controlling each facility device. The command reaches the gateway devices 1604a to 1604c on each floor.
(2) Configuration of Instance Corresponding to Each Protocol The gateway devices 1604a to 1604c on each floor configure an instance of a management object corresponding to the BACnet protocol inside, and receive an instruction command or the like transmitted by the device management device 1602.
Also, an equipment device instance corresponding to the protocol on the equipment net is configured inside, and is associated with the managed object instance on the BACnet protocol (mapping).
(3) Command Command Conversion and Execution The gateway devices 1604a to 1604c execute a command between an instance of a management object corresponding to the BACnet protocol and an equipment device instance corresponding to the protocol on the equipment net mapped to this. Convert commands.
Next, it communicates with the equipment to be executed by the protocol on the equipment network, and executes the instruction command issued by the equipment management apparatus 1602.

  As described above, the gateway devices 1604a to 1604c have a function of converting command commands between networks connected to both sides and enabling mutual communication. Objects are mapped to each other when command commands are converted.

On the other hand, the gateway devices 1604a to 1604c also have a role that can flexibly cope with a network configuration change.
As described above, command command conversion is performed by mapping objects, but even if the configuration of equipment connected to the network is changed, it is possible to deal with it simply by resetting the contents of this mapping. Thus, there is no need to replace the gateway devices 1604a to 1604c themselves or rewrite the program.

  However, there are cases where it is not possible to cope with the problem by simply resetting the mapping between the objects. Hereinafter, a specific example will be described.

FIG. 17 shows the equipment connection status of the equipment network in the building. The upper diagram of FIG. 17 shows the connection status of the floor with the building 1601, and the lower diagram shows the connection status of the floor with another building 1602.
In any building, equipment such as an air conditioner and lighting is connected to the first equipment network 1605a under the first gateway device 1604a. Here, for simplicity of explanation, the controller is omitted.
In general, the type and number of equipment connected to the first gateway device 1604a and the arrangement on the network are different for each building or for each floor in the same building. Therefore, it is desirable that the first gateway device 1604a can flexibly change the attribute of the object in accordance with the attribute included in these equipment devices. The technique shown in Patent Document 1 enables such a flexible attribute change.

However, there are cases where it is not possible to cope with a change in the configuration of the equipment only by changing the attribute of the object.
For example, in the equipment configuration shown in the upper diagram of FIG. 17, when the air conditioner operating state changes from “movable” to “stopped”, the first equipment network 1605a is notified of a state change notification. Assume that one gateway device 1604a has been set.
On the other hand, if the same setting is applied to the equipment configuration shown in the lower part of FIG. 17, there are cases where the response speed of the operation is slowed by issuing a state change notification because the number of air conditioners is large. In this case, it is necessary to reduce the frequency of state change notifications.
As described above, the details of the functions required for the gateway device may differ depending on the individual situation of the equipment device network to which the gateway device is connected.

In this case, when the conventional technique as shown in Patent Document 1 is used, the inconvenience described below occurs.
In a conventional gateway device, each equipment device object is mapped in an instance unit or an attribute unit.
However, as described above, when it is necessary to change not only the “attribute” change of each equipment device but also the “function” to be executed for the attribute of each equipment device, It is not possible to change the correspondence between the command commands of the objects simply by changing the mapping.
After all, there was a problem that there was no corresponding means other than rewriting the program of the gateway device, and maintenance cost was required.
Furthermore, in the management network of equipment, the frequency required to change the mapping in fine units as described above is high, which is a problem of the prior art.

In order to solve such a problem, the present invention proposes a gateway device in which functions provided on each network can be changed by mapping in addition to mapping in instance units and attribute units.
The following will return to the description of the remaining configuration in FIG.

FIG. 6 shows a configuration and data example of an attribute mapping table 104a (not shown) provided in the mapping DB 104.
The attribute mapping table 104a includes an “instance ID_A” column, an “attribute ID_A” column, an “attribute value_A” column, an “instance ID_B” column, an “attribute ID_B” column, and an “attribute value_B” column.
The contents of the “instance ID_A” column to the “attribute value_A” column are the same as the content of the BACnet instance DB 100. The contents of the “instance ID_B” column to the “attribute value_B” column are the same as the content of the equipment net instance DB 101.
That is, with this table, the attribute value provided in the equipment device instance on the BACnet and the attribute value provided in the equipment device instance on the equipment net are associated with each other.
In the data example of FIG. 6, “current value = 0” of the equipment instance on the BACnet identified by “Instance ID_A = 0x0100000A” is the same as the equipment instance on the equipment net identified by “Instance ID_B = 5001”. It will be associated with “driving state = 0”.

FIG. 7 shows a configuration and data example of a function mapping table 104b (not shown) provided in the mapping DB 104. This table defines the relationship between each attribute included in the equipment device instance on the BACnet and the function executed for that attribute.
The function mapping table 104b has an “instance ID” column, an “attribute ID” column, and a “function ID” column.
The contents of the “instance ID” column and the “attribute ID” column are the same as those in the BACnet instance DB 100.
The “function ID” column stores an ID for specifying a function to be executed for the attribute specified by the values of the “instance ID” column and the “attribute ID” column. As this ID value, one of the values stored in the “function ID” column of the BACnet function DB 102 is stored.
In the data example of FIG. 7, the “current value” attribute of the equipment device instance on the BACnet specified by “Instance ID = 0x0100000A” is changed by the function (“WriteProperty” function) specified by “Function ID = 0001”. And so on.

FIG. 8 shows a configuration and data example of a function mapping table 104c (not shown) provided in the mapping DB 104. This table defines the relationship between each attribute of the equipment instance on the equipment network and the function to be executed for that attribute.
The configuration of the function mapping table 104c is the same as that of the function mapping table 104b, except that the stored data is related to the facility device instance on the facility network.
In the data example of FIG. 8, the “operation state” attribute of the equipment device instance on the equipment net identified by “Instance ID = 5001” is determined by the function (“setInfProperty” function) identified by “Function ID = 1002”. It can be seen that changes are made.

  FIG. 9 conceptually shows the mapping relationship by each DB described in FIGS. This will be specifically described below.

(1) “Operating state” attribute of the equipment “air conditioner” The equipment “air conditioner” connected to the equipment network has the attribute “operating state”.
On the communication protocol used in the equipment network, if the “operating state” attribute value is “0”, “stop” is indicated, and if “4” is indicated, “operating” is indicated.
Such a binary attribute is represented by an object “Binary Output” on the BACnet protocol. The “current value” attribute of the “Binary Output” object takes one of the values “0” and “1”.
In the BACnet instance DB 100, the “current value” attribute of the instance represented by “instance ID = 0x0100000A” of the “Binary Output” object is registered, and “instance ID = 5001” of the “air conditioner” object is registered in the equipment net instance DB 101. Register the “Operation status” attribute of the instance represented by.
Further, in the attribute mapping table 104a of the mapping DB 104, a correspondence relationship between the two is defined.
In FIG. 9, 911 represents an instance of the “Binary Output” object, 910 represents an instance of an “air conditioner” object, and each “instance ID” is as shown in the “instance ID” of each instance. Reference numeral 914 represents a correspondence between attributes.
The “current value” attribute of the “Binary Output” instance 911 is represented by the data on the first line in FIG.
The “operating state” attribute of the “air conditioner” instance 910 is represented by the data in the first row of FIG.
The correspondence 914 between them is represented by the data in the first and second lines in FIG.
With the above mapping settings, the “current value” attribute (0 | 1) of the “Binary Output” instance 911 is associated with the “operating state” attribute (0 | 4) of the “air conditioner” instance 910.

(2) “Operation mode” attribute of the equipment “air conditioner” The equipment “air conditioner” connected to the equipment network has the attribute “operation mode”.
On the communication protocol used in the equipment network, if the “operation mode” attribute value is “0”, “cooling”, “1” means “heating”, and “2” means “dry”. To do.
Such attributes that take a plurality of state values are represented by an object “Multi-state Output” on the BACnet protocol. Here, the “current value” attribute of the “Multi-state Output” object is assumed to take one of the values “0”, “1”, and “2”.
In the BACnet instance DB 100, the “current value” attribute of the instance represented by “instance ID = 0x03800001” of the “Multi-state Output” object is registered, and “instance ID =” of the “air conditioner” object is registered in the equipment net instance DB 101. The “operation mode” attribute of the instance represented by “5001” is registered.
Further, in the attribute mapping table 104a of the mapping DB 104, a correspondence relationship between the two is defined.
In FIG. 9, 912 represents an instance of the “Multi-state Output” object, and “Instance ID” is as shown in “Instance ID” of 912. Reference numeral 915 denotes a correspondence relationship between attributes.
The “current value” attribute of the “Multi-state Output” instance 912 is represented by the data on the second line in FIG.
The “operation mode” attribute of the “air conditioner” instance 910 is represented by the data in the second row of FIG.
The correspondence 915 between them is represented by the data in the third row in FIG. For convenience of description, only the correspondence relationship between “attribute value_A = 1” and “attribute value_B = 1” is shown in the figure, but all values that “attribute value_A” and “attribute value_B” can take are supported. Relationships may be defined.
With the above mapping settings, the “current value” attribute (0 | 1 | 2) of the “Multi-state Output” instance 911 is associated with the “operation mode” attribute (0 | 1 | 2) of the “air conditioner” instance 910. It is done.

(3) “Set temperature” attribute of the equipment “air conditioner” The equipment “air conditioner” connected to the equipment network has the attribute “set temperature”.
On the communication protocol used in the equipment network, the “set temperature” attribute represents the set temperature value of the air conditioner, and assumes an integer value of “16” to “32”.
On the BACnet protocol, this is expressed by an object “Multi-state Output” as with the “operation mode” attribute. Here, it is assumed that the “current value” attribute of the “Multi-state Output” object takes one of values “0” to “16”.
In the BACnet instance DB 100, the “current value” attribute of the instance represented by “instance ID = 0x03800002” of the “Multi-state Output” object is registered, and “instance ID =” of the “air conditioner” object is registered in the equipment net instance DB 101. The “set temperature” attribute of the instance represented by “5001” is registered.
Further, in the attribute mapping table 104a of the mapping DB 104, a correspondence relationship between the two is defined.
In FIG. 9, 913 represents an instance of the “Multi-state Output” object, and “Instance ID” is as shown in “Instance ID” of 913. Reference numeral 916 represents the correspondence between attributes.
Note that different values are stored in the “instance ID” column in order to distinguish from instances of the “Multi-state Output” object corresponding to the “operation mode” attribute.
The “current value” attribute of the “Multi-state Output” instance 913 is represented by the data in the third row in FIG.
The “set temperature” attribute of the “air conditioner” instance 910 is represented by the data in the third row of FIG.
The correspondence 916 between the two is represented by the data in the fourth row in FIG. For convenience of description, only the correspondence relationship between “attribute value_A = 13” and “attribute value_B = 29” is illustrated, but all values that “attribute value_A” and “attribute value_B” can take are supported. Relationships may be defined.
With the above mapping setting, the “current value” attribute (0 to 16) of the “Multi-state Output” instance 911 is associated with the “set temperature” attribute (16 to 32) of the “air conditioner” instance 910.

(4) Function Mapping on BACnet In FIG. 9, the “current value” attribute included in each instance 911 to 913 on the BACnet is rewritten with a “WriteProperty” function.
Therefore, a correspondence relationship between the “current value” attribute included in each instance 911 to 913 on the BACnet and the “WriteProperty” function 950 registered in the BACnet function DB 102 is defined.
In FIG. 9, 951 to 953 represent these correspondences. Moreover, the data of each line of FIG. 7 represents the same relationship.

(5) Function Mapping on Equipment Net In FIG. 9, the “operating state” attribute and the “set temperature” attribute included in the instance 910 of the “air conditioner” object on the equipment net are rewritten with the “setInfProperty” function.
Therefore, a correspondence relationship between the “operating state” and “set temperature” attributes included in the instance 910 of the “air conditioner” object on the equipment net and the “setInfProperty” function 940 registered in the equipment net function DB 103 is defined.
In FIG. 9, 941 to 942 represent these correspondences. Further, the data in the first and third lines in FIG. 8 represent the same relationship.

Further, it is assumed that the “operation mode” attribute included in the instance 910 of the “air conditioner” object on the equipment net is rewritten by the “setProperty” function.
Therefore, a correspondence relationship between the “operation mode” attribute included in the instance 910 of the “air conditioner” object on the equipment net and the “setProperty” function 930 registered in the equipment net function DB 103 is defined.
In FIG. 9, reference numeral 931 represents these correspondences. Further, the data in the second row in FIG. 8 represents the same relationship.

In the above, the concept / procedure of mapping the function to each attribute after mapping the instance information (object, attribute, attribute value) was explained. However, each attribute is assigned to each attribute in both the BACnet and the equipment net. A concept / procedure of associating a function with each other and associating a pair of the instance information including these attributes with the function between the BACnet and the equipment net may be used.
In the above description, the correspondence is performed at 1: 1, but the correspondence may be generally defined as N: M.

  Next, an example of a specific operation performed using the above mapping information will be described.

FIG. 10 is an operation flow of the first gateway device 1604a when issuing a command command from the BACnet side and operating the equipment on the equipment network side. The first gateway device 1604a is assumed to have the configuration described with reference to FIGS.
Here, the operation when the device management apparatus 1602 operates the “Binary Output” instance 911 of FIG. 9 to operate the “operating state” attribute of the “air conditioner” instance 910 in the building as shown in FIG. Take an example.

(S1010)
In the initial state, it is assumed that the databases shown in FIGS. 2 to 8 are configured in advance, and the data shown in the figures are already stored. In addition, the “current value” attribute value of the “Binary Output” instance 911 is “0”, and the “operating state” attribute value of the “air conditioner” instance 910 is “0”.
(S1020)
The device management apparatus 1602 transmits a command to start operation to the air conditioner connected to the first facility management network 1605a. This command is transmitted using the BACnet protocol. That is, a “WriteProperty” command command indicating that the “current value” attribute value of the “Binary Output” instance 911 should be changed from “0” to “1” is transmitted.
The transmitted “WriteProperty” command reaches the first gateway device 1604a.
(S1030)
The first gateway device 1604a executes the “WriteProperty” function, and updates the data in the first row of the BACnet instance DB 100 from “attribute value = 0” to “attribute value = 1”. At this time, “instance ID = 0x0100000A” and “attribute ID = 85 (current value)” are used as keys.
(S1040)
The mapping execution unit 105 searches the attribute mapping table 104a and searches for the attribute value of the instance on the equipment net associated with the “current value” attribute of the “Binary Output” instance 911.
Here, the instance ID “0x0100000A”, the attribute ID “85 (current value)”, and the attribute value “1” of the “Binary Output” instance 911 are used as search keys.
As a result of the search, data of “instance ID_B = 5001”, “attribute ID_B = 0 (operation state)”, and “attribute value_B = 4” is found. This corresponds to the “operating state” attribute of the “air conditioner” instance 910 in FIG.
(S1050)
The mapping execution unit 105 searches the function mapping table 104 c and acquires a function corresponding to the “operating state” attribute of the “air conditioner” instance 910.
Here, the instance ID “5001” of the “air conditioner” instance 910 and the attribute ID “0 (operating state)” are used as search keys.
As a result of the search, data of “function ID = 1002” is found.
(S1060)
The mapping execution unit 105 searches the equipment network function DB 103 using “function ID = 1002” as a key. As a result of the search, it is understood that the “setInfProperty” function should be executed.
(S1070)
The first gateway device 1604a executes the “setInfProperty” function to update the data in the first line of the equipment net instance DB 101 from “operating state = 0” to “operating state = 4”, and also the first equipment management network 1605a. An instruction command is issued to start the operation of the air conditioner connected to. In addition, according to the content of the “setInfProperty” function, the air conditioner operating state change notification is issued in the first facility management network 1605a.

  In addition, in each step of FIG. 10, when applicable data is not found in each DB, you may make it complete | finish by performing an error process suitably. As the contents of the error processing, for example, a predetermined error code may be returned according to the protocol on each network, or the request may be discarded as it is when no special measures are required.

Next, rewriting of data stored in the mapping DB 104 will be described.
The data rewriting of the mapping DB 104 is necessary when the network configuration is changed or when the gateway device is installed in another building / commercial facility as described with reference to FIG.
For example, in FIG. 9, the “operating state” attribute of “air conditioner” is mapped with the “setInfProperty” function, but there may be a case where notification of a state change is not necessary when installing in another building.
In the conventional gateway apparatus, mapping in the instance unit or the attribute unit was possible, but when the function mapping was changed, the software had to be rewritten.
In the gateway device according to the present invention, taking the above case as an example, it is only necessary to rewrite the data in the first row of the function mapping table 104c shown in FIG. 8 to “function ID = 1001”. The labor of additional development and maintenance work itself can be reduced significantly.

When actually rewriting the data in the mapping DB 104, for example, a maintenance terminal having a dedicated connector terminal is directly connected to the gateway device so that data for rewriting is sent to the gateway device. Good. In addition, it may be set via a physical medium (FD, CD, memory device such as a memory card). Moreover, you may make it set combining these.
For example, the default value can be mounted as part of the prescribed data, and subsequent changes can be set via the network.

In the first embodiment, each instance DB and the mapping table are individually constructed. However, since the data contents are duplicated, the instance DB may be omitted from the viewpoint of saving storage capacity.
Further, the mapping table may be configured to store only the correspondence between the rows of the instance DB.

  Also, the function mapping table 104b and the function mapping table 104c may be configured as a single table while considering duplication of instance IDs without being configured as separate tables. This will be described in detail in the second embodiment.

Further, the attribute mapping table 104a is configured to define a correspondence relationship for each attribute value. For example, the attribute values in both networks are the same as the data in the first and third rows, and the “instance ID” When only “attribute ID” is different, only the relationship between “instance ID_A”, “attribute ID_A”, “instance ID_B”, and “attribute ID_B” may be defined.
In addition, the same can be done when the attribute values in both networks are related by a predetermined conversion formula.

As described above, the gateway device according to the first embodiment includes the attribute mapping table 104a, the function mapping table 104b, and the function mapping table 104c on the mapping DB 104, and each of these tables is used when mapping objects. Refer to, and map the attribute value / function of the instance.
Therefore, as described with reference to FIG. 17, even when the attribute value is not changed and only the required function is changed, it is not necessary to rewrite the software itself, and only rewrite the data stored in the mapping DB 104. Can be easily accommodated. Thereby, the additional development for individual correspondence and the maintenance work for it which were performed conventionally can be reduced significantly.

In addition, the attribute mapping table 104a, the function mapping table 104b, and the function mapping table 104c have a column configuration that allows the above-described function mapping to be performed in units of attribute values included in each facility device instance.
For this reason, function mapping can be performed in units of attribute values instead of in units of instances as in the conventional gateway device, and the following effects are obtained.
That is, in the conventional gateway device, if only the function of the equipment device object is changed, it means that the definition of the object itself has been changed, and therefore the software that implements the function of the object is changed. Although there was a need, in the first embodiment, since the attributes and functions of the object are separated from the object definition and can be combined individually, even if the attributes and functions of the object are changed to ad hoc, It is possible to easily cope with this by simply rewriting the mapping data that is the combination information.

Embodiment 2. FIG.
In the first embodiment, one configuration example of the mapping DB 104 is shown, and the configuration of the gateway device that can map the attributes and attribute values of the instance and also map the functions of the instance has been described.
In the second embodiment of the present invention, another configuration example of the function mapping table stored in the mapping DB 104 will be described.

FIG. 11 shows a configuration and data example of the function mapping table 104d stored in the mapping DB 104.
A function mapping table 104d shown in FIG. 11 is configured by integrating the function mapping table 104b (FIG. 7) and the function mapping table 104c (FIG. 8) described in the first embodiment. The contents of each column are the same as those described with reference to FIGS.
In the second embodiment, a function mapping table 104d shown in FIG. 11 is configured instead of the function mapping table 104b and the function mapping table 104c. By referring to this table, the function executed on the BACnet side and the function executed on the equipment net side can be immediately associated in units of “instance / attribute / function”.

FIG. 12 conceptually shows the mapping relationship by each DB provided in the gateway device according to the second embodiment.
The difference from FIG. 9 described in the first embodiment is that a correspondence 971 between the BACnet function DB 102 and the facility network function DB 103 is newly provided. The correspondence relationships represented by 951, 914, and 941 in FIG.
For the sake of brevity, the correspondence relationships 931, 942, 952, and 953 are omitted.

The function mapping table 104d newly provided in the second embodiment represents the correspondence 971 described above. For example, the data on the first line can be interpreted as follows.
(1) 3 columns in the left half Indicates that the “current value” attribute of the “Binary Output” instance 911 is associated with the function (WriteProperty) represented by “function ID = 0001”. It corresponds to.
(2) Three columns in the right half The “operating state” attribute of the “air conditioner” instance 910 is associated with the function (setInfProperty) represented by “function ID = 1002”. Equivalent to.
(3) Whole data in the first row The above (1) and (2) are stored in the first row, which means that the left end and the right end of 971 are connected. That is, when the “current value” attribute of the “Binary Output” instance 911 is updated with the “WriteProperty” function, the “operating state” attribute of the “air conditioner” instance 910 should be updated with “setInfProperty”.

  FIG. 13 is an operation flow of the first gateway device 1604a when a command command is issued from the BACnet side and the equipment device on the equipment network side is operated in the second embodiment. An operation similar to that in FIG. 10 described in the first embodiment will be described as an example.

(S1310) to (S1340)
Since it is the same as steps S1010 to 1040 in FIG.
(S1350)
The mapping execution unit 105 searches the function mapping table 104d using the instance ID “0x0100000A”, the attribute ID “85 (current value)”, and the function ID “0001” of the “Binary Output” instance 911 as keys.
As a result of the search, data of “instance ID_B = 5001”, “attribute ID_B = 0 (operation state)”, and “function ID_B = 1002” is found.
(S1360)
The mapping execution unit 105 searches the equipment network function DB 103 using “function ID_B = 1002” as a key. As a result of the search, it is understood that the “setInfProperty” function should be executed.
(S1370)
The first gateway device 1604a executes the “setInfProperty” function to update the data in the first row of the equipment net instance DB 101 from “operating state = 0” to “operating state = 4”, and also the first equipment management network 1605a. An instruction command is issued to start the operation of the air conditioner connected to. In addition, according to the content of the “setInfProperty” function, an operation state change notification of the air conditioner is issued in the first facility management network 1605a.

  In the second embodiment, the correspondence relationships represented by 931 to 953 in FIG. 9 are integrated into 971. However, the correspondence relationships represented by 951, 914, and 941 and 971 may coexist. In this case, the function of the counterpart network can be executed by following an appropriate correspondence according to each situation, so that the configuration flexibility is further increased.

In FIG. 12, it has been described that the correspondence 971 is configured by the function mapping table 104d. However, depending on the configuration of the function mapping table, other correspondences may be configured.
For example, a new function mapping table 104e is provided, and a “function ID_A” column and a “function ID_B” column are provided. In each column, the value of the “function ID” column of the BACnet function DB 102 and the value of the “function ID” column of the equipment network function DB 103 are stored. Thereby, the functions on both networks can be directly associated with each other. For example, in the example of FIG. 12, this corresponds to connecting the “WriteProperty” function 950 and the “setProperty” function 930. The same applies to other functions.

Embodiment 3 FIG.
In the first and second embodiments, the configuration of the mapping DB 104 is mainly described, and a general method is used as a specific method of data rewriting.
In the third embodiment of the present invention, another implementation example of the mapping data receiving method for rewriting the mapping DB 104 will be described.

FIG. 14 illustrates an operation of rewriting the mapping DB 104 of the first gateway device 1604a in the same building equipment network as FIG. The network configuration is shown in a simplified manner.
The mapping DB 104 can be rewritten by connecting the maintenance terminal directly to the first gateway device 1604a as described in the first embodiment, but connecting the maintenance terminal 1401 to the BACnet network 1603 as shown in FIG. However, the mapping data may be sent via the network by the operation of the operator 1402.
Hereinafter, a configuration provided for the first gateway device 1604a to receive mapping data will be described.

FIG. 15 is a functional block diagram showing the configuration of the first gateway device 1604a.
The first gateway device 1604a includes a receiving unit 110 and a mapping setting unit 120. Since other configurations are the same as those in FIG. 1, the same reference numerals are given and description thereof is omitted.
The receiving means 110 receives the mapping data transmitted by the maintenance terminal 1401 in FIG. As the communication protocol, an appropriate method such as an arbitrary protocol on TCP / IP (Transfer Control Protocol / Internet Protocol) is appropriately used.

The receiving unit 110 includes a network interface capable of receiving a network packet including mapping data transmitted from the maintenance terminal 1401, and a circuit or software for processing the network interface.
The network interface may be shared with that provided for connection to the BACnet network 1603, or a separate network interface for maintenance may be provided.
A circuit or software for processing a network packet can be configured to open a specific port on TCP and wait for an IP packet, for example.

  The mapping setting unit 120 can be implemented by software executed on an arithmetic device such as a CPU or a microcomputer. The mapping execution unit 105 may be integrated.

When receiving the network packet including the mapping data transmitted from the maintenance terminal 1401, the receiving unit 110 delivers the data to the mapping setting unit 120.
The mapping setting unit 120 extracts mapping data from the received data, and updates the corresponding data in each DB based on the extracted mapping data. After updating each DB, mapping between objects is performed again based on the updated data, and information communication between networks is performed using the latest mapping information.

In addition, although the form which connects the maintenance apparatus 1401 to the BACnet network 1603 and transmitted mapping data was demonstrated in FIG. 14, it is not restricted to this, Even if mapping data is transmitted from the 1st installation apparatus network 1605a side. Good.
In this case, if the receiving unit 110 is configured to be compatible with the communication protocols of both the BACnet network 1603 and the first equipment network 1605a, it takes time for implementation. If it is not determined, it is preferable to use a general TCP / IP protocol for receiving the mapping data.

  In addition, a push distribution method in which mapping data is arranged on a server via the Internet and the latest mapping data is periodically distributed from the server to the first gateway device 1604a can be realized. A pull distribution method in which the first gateway device 1604a periodically accesses the server to obtain the latest mapping data is also possible.

  Although the mapping setting unit 120 for rewriting the data of the mapping DB has been described here, a unit for rewriting the instance DB and the function DB may be provided in the same manner.

As described above, the gateway device according to the third embodiment includes the receiving unit 110 and the mapping setting unit 120, and the data in the mapping DB 104 can be updated by the network packet including the mapping data.
Therefore, it is possible to update the data in the mapping DB 104 by remote maintenance, which contributes to further reduction in maintenance costs.

Embodiment 4 FIG.
In the first to third embodiments described above, the gateway device in the equipment management network has been described. However, the essence of the present invention can be applied to other things. In the fourth embodiment of the present invention, an example will be described.

There is ORB (Object Request Broker) as software for mapping objects that cannot be directly communicated to enable mutual information communication. This is a term that generically represents a common interface or software for use when an object communicates with another object.
If the processing of the mapping execution unit 105 described in the first to third embodiments is implemented as software and executed by a computer, software (mapping) that defines the correspondence between objects connected to different networks is configured.
If this is mounted on a server and installed at a relay point on the network, a server providing the ORB function can be configured. The gateway devices according to the first to third embodiments can also be realized as one implementation form of the ORB server.

As described above, according to the fourth embodiment, since the processing of the mapping execution unit 105 described in the first to third embodiments is implemented as software, the same operation as that of the gateway device of the first to third embodiments is performed. To obtain object-to-object mapping software.
By implementing this inter-object mapping software on, for example, an ORB server, mapping between objects can be performed flexibly even in a heterogeneous network other than the equipment management network, which contributes to a reduction in maintenance costs required for mapping.

FIG. 3 is a schematic diagram conceptually showing functions of the gateway device according to the first embodiment. The structure of BACnet instance DB100 and the example of data are shown. The structure of equipment net instance DB101 and the example of data are shown. An example of the configuration and data of the BACnet function DB 102 is shown. The structure of equipment network function DB103 and the example of data are shown. The structure of the attribute mapping table 104a with which mapping DB104 is provided, and a data example are shown. The structure of the function mapping table 104b with which mapping DB104 is provided, and a data example are shown. The structure of the function mapping table 104c with which mapping DB104 is provided, and a data example are shown. FIG. 9 conceptually shows the mapping relationship by each DB described in FIGS. It is an operation | movement flow of the 1st gateway apparatus 1604a when issuing a command command from the BACnet side and operating the equipment apparatus on the equipment network side. The configuration of the function mapping table 104d stored in the mapping DB 104 and an example of data are shown. 7 conceptually shows a mapping relationship by each DB provided in the gateway device according to the second embodiment. In Embodiment 2, it is an operation | movement flow of the 1st gateway apparatus 1604a when issuing a command command from the BACnet side and operating the equipment apparatus on the equipment net side. The operation of rewriting the mapping DB 104 of the first gateway device 1604a in the building equipment network similar to FIG. 16 will be described. It is a functional block diagram which shows the structure of the 1st gateway apparatus 1604a. The structure of the equipment network management system in a building is demonstrated. FIG. 17 is a floor plan of the top floor of the building 1601 in FIG. 16.

Explanation of symbols

  100 BACnet instance DB, 101 equipment net instance DB, 102 BACnet function DB, 103 equipment net function DB, 104 mapping DB, 104a attribute mapping table, 104b to 104d function mapping table, 105 mapping execution means, 110 receiving means, 120 mapping setting Means, 910 “air conditioner” object instance, 911 “Binary Output” object instance, 912 “Multi-state Output” object instance, 913 “Multi-state Output” object instance, 920 “lighting” object instance, 1401 Maintenance terminal, 1402 operator, 1601 , 1602 device management apparatus, 1603 BACnet network, 1604A～1604c gateway device, 1605A～1605c equipment network.

Claims (9)

A method of defining the correspondence between objects connected to different networks (hereinafter referred to as mapping),
An attribute mapping table that defines the correspondence between attributes of each object instance;
A function mapping table for associating a function to be executed for an attribute included in one instance of the object for each attribute and a function for executing an attribute included in the other instance of the object for each attribute; ,
Provided with rewritable storage means storing
When mapping each object,
While referring to the attribute mapping table, associating attributes included in the instance of the mapping target object,
An inter-object mapping method characterized by associating a function to be executed for each attribute with reference to the function mapping table. The inter-object mapping method according to claim 1, wherein the attribute mapping table includes the following columns.
(1) Column for storing an ID for specifying an instance of the first object (2) Column (3) for storing an ID for specifying an attribute included in the instance specified by the value of the column (1) (2) ) A column for storing an attribute value specified by the column value (4) A column for storing an ID for specifying an instance of the second object (5) (4) An attribute included in the instance specified by the column value Column for storing the ID for specifying (6) Column for storing the value of the attribute specified by the value of column (5) The inter-object mapping method according to claim 1, wherein the function mapping table includes the following columns.
(1) Column for storing an ID for specifying an instance of an object (2) Column (3) for storing an ID for specifying an attribute of an instance specified by the value of the column (1) (3) (2) A column that stores an ID for specifying the function to be executed for the attribute specified by the value of   An object mapping program for causing a computer to execute the object mapping method according to any one of claims 1 to 3. Provided between a first network for connecting a managed device and a second network for connecting a device management device;
A first object representing the managed device is associated with a second object that executes an operation, monitoring, or maintenance operation of the managed device (hereinafter referred to as mapping),
A gateway device that performs operation, monitoring, or maintenance of the managed device mapped to the second object by performing an operation, monitoring, or maintenance operation on the second object,
An attribute mapping table that defines a correspondence relationship between attributes of each instance of the first object and the second object;
A function mapping table that associates, for each attribute , a function to be executed with respect to an attribute included in the instance of the first object, and associates a function to be executed with respect to the attribute included in the instance of the second object for each attribute. ,
A rewritable storage means storing
Mapping execution means for executing mapping between the first object and the second object;
The mapping execution means
When mapping the first object and the second object,
While referring to the attribute mapping table, associating attributes included in the instance of the mapping target object,
A gateway device that refers to the function mapping table and associates a function to be executed with respect to each attribute. The gateway device according to claim 5, wherein the attribute mapping table includes the following columns.
(1) Column for storing an ID for specifying an instance of the first object (2) Column (3) for storing an ID for specifying an attribute included in the instance specified by the value of the column (1) (2) ) A column for storing an attribute value specified by the column value (4) A column for storing an ID for specifying an instance of the second object (5) (4) An attribute included in the instance specified by the column value Column for storing the ID for specifying (6) Column for storing the value of the attribute specified by the value of column (5) The gateway device according to claim 5 or 6, wherein the function mapping table includes the following columns.
(1) Column for storing an ID for specifying an instance of an object (2) Column (3) for storing an ID for specifying an attribute of an instance specified by the value of the column (1) (3) (2) A column that stores an ID for specifying the function to be executed for the attribute specified by the value of Receiving means for receiving data stored in the storage means from the first network or the second network;
Mapping setting means for storing the data received by the receiving means in the storage means and updating the attribute mapping table or the function mapping table based on the content of the data;
With
The mapping execution means
8. The gateway device according to claim 5, wherein mapping of the first object and the second object is performed again based on the updated content. 9. One or more managed devices connected to the first network;
A device management apparatus connected to the second network;
The gateway device according to any one of claims 5 to 8, provided between the first network and the second network;
A device management system comprising:

Images