WO2015107613A1 - Wide area management system, wide area management device, building management device, wide area management method, identifier information transmission method, identifier issuing method, and program - Google Patents

Abstract

In order to reduce a state whereby a message identifier cannot be issued when a request has been issued for high-priority data acquisition, a wide area management device (21) associates and stores: an identifier allocated to a message exchanged between building management devices (31, 41) provided in buildings (B1, B2) and facility devices (32, 42); and acquisition priority information indicating the acquisition priority for the data obtained from the facility devices (32, 42). The wide area management device (21) sends the stored identifier and acquisition priority information to the building management devices (31, 41). The building management devices (31, 41 ) receive the identifier and the acquisition priority information that are sent from the wide area management device (21), store same in an identifier information storage unit, browse the identifier information storage unit, and issue an identifier corresponding to the acquisition priority for the message data.

Description

Wide area management system, wide area management apparatus, building management apparatus, wide area management method, identifier information transmission method, identifier issuance method, and program

The present invention relates to a wide area management system, a wide area management apparatus, a building management apparatus, a wide area management method, an identifier information transmission method, an identifier issuance method, and a program.

Conventionally, buildings, hospitals, schools, factories, and other buildings have management devices that manage equipment. Information on equipment in multiple buildings is monitored from a remote location via a communication network. The system exists. In such a system, messages exchanged between a building management apparatus installed in a building and a plurality of equipment installed in the building need to be appropriately exchanged.

For example, the building management apparatus transmits a request message to the equipment in order to acquire data such as temperature from the equipment. When the building management apparatus transmits a request message to the facility device, the building management apparatus includes the message identifier in the request message and transmits the message to the facility device.

When the equipment receives the request message from the building management apparatus, the equipment transmits data such as the measured temperature to the building management apparatus together with a response message. At that time, the equipment includes the message identifier included in the request message received from the building management apparatus in the response message and transmits the response message to the building management apparatus.

As a result, the building management device can recognize which request message corresponds to the response message returned from the equipment even when there are multiple equipment, and exchange the messages appropriately. can do.

Conventionally, in a remote monitoring and control system using electronic mail, a monitoring control system has been proposed that enables reception of a response message to a request message between the control device and the electronic mail remote monitoring and control device (for example, Patent Document 1).

JP 2003-157223 A

However, since the message identifiers are finite, they may be exhausted. Therefore, there is a problem that even if a request for data acquisition with high priority occurs, a request message cannot be issued.

For example, in the BACnet (Building Automation and Control Networking protocol) standard, 256 message identifiers represented by 8 bits are prepared. However, for example, due to the influence of slow response equipment, all 256 identifiers are assigned to the request message, and when the identifiers are exhausted, the building management device may generate a request to acquire data with high priority. A request message may not be issued.

Therefore, an object of the present invention is to provide a technique for reducing a state in which a message identifier cannot be issued when a request for data acquisition with high priority occurs.

The present application includes a plurality of means for solving at least a part of the above-described problems, and examples thereof are as follows. In order to solve the above problems, a wide area management system according to the present invention is provided corresponding to a wide area management apparatus and a building in which equipment is installed, exchanges messages with the equipment and transmits data from the equipment. First identifier information that stores an association of an identifier assigned to the message and acquisition priority information indicating an acquisition priority of the data in association with each other A storage unit; and a transmission unit that transmits the identifier stored in the first identifier information storage unit and the acquisition priority information to the building management device, wherein the building management device is configured to transmit the transmission unit. A receiving unit that receives the identifier and the acquisition priority information transmitted from a second identifier information storage unit that stores the identifier and the acquisition priority information received by the receiving unit; Referring to the second identifier information storage unit, and having a an issuing unit for issuing said identifier the corresponding to the obtained priority of the data of the message.

The building management apparatus further includes a data request unit that requests the data of the equipment and outputs a data request including the acquisition priority information, and the issuing unit includes the second identifier. The identifier corresponding to the acquisition priority information included in the data request of the data request unit may be issued with reference to an information storage unit.

Further, the acquisition priority information includes first acquisition priority information and second acquisition priority information having a higher acquisition priority of the data than the first acquisition priority information. It may be.

In addition, when the identifier of the second acquisition priority information is depleted and the data request including the second acquisition priority information is present, the issuing unit may include the first acquisition priority information. The identifier of the acquisition priority information may be issued.

In addition, the issuing unit may issue the identifier of the first acquisition priority information that has not been issued.

In addition, when the identifier of the first acquisition priority information is exhausted, the issuing unit uses the second acquisition of the identifier of the first acquisition priority information issued most recently. It may be characterized in that it is issued for the data request including priority information.

The second identifier information storage unit stores data amount information of the data acquired from the equipment corresponding to the identifier, and the data request output from the data request unit is stored in the data request. Includes the data amount information of the data, and the issuing unit refers to the second identifier information storage unit, and the acquisition priority information and the data included in the data request of the data request unit The identifier corresponding to the quantity information may be issued.

The data request output from the data request unit includes an estimated value of the time required for collecting the data, and the estimated value is the identifier assigned to the data request. Corresponding to the above, it may be stored in the second identifier information storage unit.

In addition, the issuing unit stores issuance state information indicating an issuance state of the identifier in the second identifier information storage unit, and when the issued identifier has passed the estimated value time, the identifier The issue status information may be unissued.

In addition, the issuing unit may monitor the issuing state of the identifier, and the acquisition priority information may be changed according to the issuing state.

Further, the wide area management apparatus according to the present invention shows an identifier assigned to a message exchanged between a building management apparatus provided in a building and equipment and an acquisition priority of data acquired from the equipment. An identifier information storage unit that stores the acquisition priority information in association with each other, and a transmission unit that transmits the identifier stored in the identifier information storage unit and the acquisition priority information to the building management device. It is characterized by that.

Further, the building management apparatus according to the present invention includes an identifier assigned to a message exchanged between the building management apparatus provided in the building and the equipment from a wide area management apparatus that manages power consumed in the building. A receiving unit that receives acquisition priority information indicating an acquisition priority of data acquired from the facility device associated with the identifier, and the identifier and the acquisition priority information received by the receiving unit. An identifier information storage unit that stores the identifier information, and an issue unit that refers to the identifier information storage unit and issues the identifier according to the acquisition priority of the data of the message.

Further, wide area management comprising the wide area management apparatus according to the present invention and a building management apparatus provided corresponding to a building in which the equipment is installed, exchanging messages with the equipment and acquiring data from the equipment. In the wide area management method of the system, the wide area management device stores a first identifier information storing the identifier assigned to the message and the acquisition priority information indicating the acquisition priority of the data in association with each other; A transmission step of transmitting the identifier stored in the first identifier information storage step and the acquisition priority information to the building management device, wherein the building management device is transmitted by the transmission step. A reception step of receiving the identifier and the acquisition priority information; and the identifier and the acquisition priority information received by the reception step; The identifier according to the acquisition priority of the data of the message with reference to the second identifier information storage step to be stored, the identifier stored in the second identifier information storage step, and the acquisition priority information And issuing step for issuing.

In addition, the identifier information transmission method of the wide area management apparatus according to the present invention includes an identifier assigned to a message exchanged between a building management apparatus provided in a building and the equipment, and data acquired from the equipment. An identifier information storage step for storing the acquisition priority information indicating the acquisition priority in association with each other, and a transmission for transmitting the identifier and the acquisition priority information stored in the identifier information storage step to the building management apparatus And a step.

Moreover, the identifier issuing method of the building management apparatus according to the present invention is:
An identifier assigned to a message exchanged between the building management device provided in the building and equipment from a wide area management device that manages power consumed in the building, and the equipment associated with the identifier A reception step of receiving acquisition priority information indicating acquisition priority of data acquired from the device; an identifier information storage step of storing the identifier received by the reception step; and the acquisition priority information; An issuing step of referring to the identifier stored in the identifier information storing step and the acquisition priority information, and issuing the identifier according to the acquisition priority of the data of the message. .

Further, the program of the wide area management apparatus according to the present invention includes an identifier assigned to a message exchanged between a building management apparatus provided in a building and equipment, and an acquisition priority of data acquired from the equipment. An identifier information storage unit that stores the acquisition priority information indicating the association, and a transmission unit that transmits the identifier stored in the identifier information storage unit and the acquisition priority information to the building management device, It is characterized by including.

Further, the program of the building management apparatus according to the present invention is assigned to a message exchanged between the building management apparatus and the equipment provided in the building from a wide area management apparatus that manages power consumed in the building. And a receiving unit that receives an acquisition priority information indicating an acquisition priority of data acquired from the facility device associated with the identifier, the identifier received by the receiving unit, and the acquisition An identifier information storage unit that stores priority information; and an issuing unit that refers to the identifier information storage unit and issues the identifier according to the acquisition priority of the data of the message. .

According to the present invention, it is possible to reduce a state in which a message identifier cannot be issued when a request for data acquisition with high priority occurs.

Problems, configurations, and effects other than those described above will be clarified by the following description of the embodiments.

It is the figure which showed the structural example of the wide area management system 1 which concerns on the 1st Embodiment of this invention. 3 is a block diagram illustrating an example of a functional configuration of a wide area management device 21. FIG. It is the figure which showed the data structural example of the identifier information storage part 62. FIG. 3 is a block diagram illustrating an example of a functional configuration of a building management device 31. FIG. It is the block diagram which showed an example of the function structure of BACnetI / F. 3 is a block diagram illustrating an example of a functional configuration of a TSM manager 83. FIG. 6 is a diagram illustrating a data configuration example of an identifier information storage unit 91. FIG. 5 is a sequence diagram illustrating an operation example of the building management apparatus 31. FIG. 5 is a flowchart showing an operation example of a TSM manager 83. 5 is a sequence diagram illustrating an operation example of the building management apparatus 31. FIG. 5 is a sequence diagram illustrating an operation example of the building management apparatus 31. FIG. It is a figure explaining assignment of Invoke_ID. It is the figure which showed an example of the hardware constitutions which implement | achieve the function of a building management apparatus. It is the figure which showed the example of a data structure of the identifier information storage part 91 which concerns on 2nd Embodiment. It is the figure which showed the example of a data structure of the identifier information storage part 91 which concerns on 3rd Embodiment.

[First Embodiment]
FIG. 1 is a diagram showing a configuration example of a wide area management system 1 according to the first embodiment of the present invention. As shown in FIG. 1, the wide area management system 1 includes a wide area management device 21 and building management devices 31 and 41 provided in buildings B1 and B2, respectively. Each of the wide area management device 21 and the building management devices 31 and 41 can transmit and receive communication data via a network 51 such as the Internet. In FIG. 1, only two buildings B1 and B2 are shown, but three or more buildings may exist. Again, each building is equipped with a building management device. Further, there may be three or more building management devices. Moreover, you may make it the structure which monitors a some building with one building management apparatus. That is, the configurations of the building management device and the equipment may have various forms.

The wide area management device 21 receives a control command for controlling the power consumption of each of the buildings B1 and B2 from the administrator 12 via the terminal device 11. The wide area management device 21 transmits the received control command to the building management devices 31 and 41 provided in the buildings B1 and B2 to be managed via the network 51.

The building management device 31 is connected to a network 33 such as a LAN provided in the building B1. The building management apparatus 31 can transmit and receive communication data with each of the plurality of facility devices 32 provided in the building B1 via the network 33.

The building management device 41 is also connected to a network 43 such as a LAN provided in the building B2 in the same manner as the building management device 31. The building management apparatus 41 can transmit and receive communication data with each of the plurality of facility devices 42 provided in the building B2 via the network 43.

The plurality of facility devices 32 provided in the building B1 are, for example, air conditioning devices, lighting devices, boiler devices, security devices, or monitoring devices that monitor IT (Information Technology) devices such as servers and routers.

Each of the facility equipment 32 has, for example, a sensor. The sensor is, for example, a temperature sensor that measures the temperature in the building B1, a current sensor that measures a current flowing in the building, or an infrared sensor that detects a person in the building B1. In response to a request from the building management apparatus 31, each of the facility devices 32 transmits sensor data to the building management apparatus 31, for example. Similarly to the building B1, the building B2 is provided with a plurality of facility devices 42 including sensors.

In FIG. 1, only four equipment devices 32 and 42 are shown in each of the buildings B1 and B2, but there may be one to three or five or more.

The building management device 31 receives and stores an event program from the wide area management device 21 via the network 51. The building management apparatus 31 may be configured with, for example, equipment used for BEMS.

The event program is a program for controlling the operation of the facility devices 32 and 42 provided in the buildings B1 and B2 and controlling the power consumption of each facility device. When the building management devices 31 and 41 receive a control command from the wide area management device 21 via the network 51, the building management device 31 and 41 executes an event program corresponding to the received control command, and thereby the building B1 , B2 overall power consumption is controlled.

FIG. 2 is a block diagram showing an example of the functional configuration of the wide area management device 21. As shown in FIG. As illustrated in FIG. 2, the wide area management device 21 includes a communication unit 61, an identifier information storage unit 62, a data storage unit 63, and a communication unit 64.

The communication unit 61 includes a transmission unit 61a and a reception unit 61b, and communicates with the terminal device 11. For example, the receiving unit 61b receives the identifier information received from the administrator 12 by the terminal device 11 from the terminal device 11. The identifier information includes an identifier and acquisition priority information. The identifier and acquisition priority information will be described below.

The transmission unit 61 a transmits the identifier information stored in the identifier information storage unit 62 and the data stored in the data storage unit 63 to the terminal device 11 in response to a request from the terminal device 11. For example, the terminal device 11 can display the data transmitted from the transmission unit 61a on the display.

Here, the identifier included in the identifier information and the acquisition priority information will be described. The building management apparatus 31 exchanges messages with a plurality of facility devices 32 and acquires, for example, sensor data included in the facility devices 32 from the plurality of facility devices 32. The identifier is an identifier assigned to a message in order to identify a message exchanged between the building management apparatus 31 and the plurality of facility devices 32. In the BACnet standard, 256 Invoke_IDs represented by 8 bits are prepared. In the following, description will be made using Invoke_ID of BACnet, which is an example of an identifier.

For example, it is assumed that the building management apparatus 31 transmits a request message for data such as temperature to the equipment device 32. When the building management apparatus 31 transmits a request message to the facility device 32, the building management device 31 includes the Invoke_ID in the request message and transmits the request message to the facility device 32.

When the facility device 32 receives the request message from the building management device 31, the facility device 32 transmits data such as temperature to the building management device together with a response message. At that time, the facility device 32 includes the Invoke_ID included in the request message received from the building management device 31 in the response message and transmits the response message to the building management device 31. Thereby, the building management apparatus 31 can recognize which request message the response message returned from the facility device 32 corresponds to even when there are a plurality of facility devices 32.

The acquisition priority information included in the identifier information is information indicating the acquisition priority of the data of the facility device 32. The acquisition priority information is stored in the identifier information storage unit 62 in association with the Invoke_ID, as will be described below.

For example, it is assumed that the building management apparatus 31 wants to acquire data of a certain facility device 32 with high priority. In this case, for example, an Invoke_ID associated with the acquisition priority information “high” is assigned to a request message transmitted to a certain equipment device 32. Further, it is assumed that the building management apparatus 31 wants to acquire data of a certain equipment 32 instead of high priority. In this case, for example, an Invoke_ID associated with the acquisition priority information “low” is assigned to a request message transmitted to a certain equipment device 32.

More specifically, the server temperature has a higher priority than the temperature of the room where people work. This is because a failure or failure of the server occurs when the temperature rises. Therefore, an Invoke_ID associated with the acquisition priority information “high” is assigned to the request message transmitted to the facility device 32 that manages the temperature of the server and the like. Further, an Invoke_ID associated with the acquisition priority information “low” is assigned to the request message transmitted to the facility device 32 that manages the room temperature.

The same applies to the building management apparatus 41. That is, 256 Invoke_IDs are also prepared in the building management apparatus 41, and the building management apparatus 41 and the equipment 42 exchange messages using 256 Invoke_IDs. In addition, acquisition priority information is associated with the Invoke_ID.

The identifier information storage unit 62 stores identifier information used in the building management apparatus 31. The identifier information storage unit 62 stores identifier information used by the building management apparatus 41. That is, the identifier information storage unit 62 stores identifier information for each building management device 41 and 42.

FIG. 3 is a diagram showing a data configuration example of the identifier information storage unit 62. As illustrated in FIG. 3, the identifier information storage unit 62 stores Invoke_ID 62 a, acquisition priority information 62 b, and status information (issue state information) 62 c as identifier information.

The Invoke_ID 62a is an identifier assigned to a message exchanged between the building management apparatus 31 and the equipment 32 as described above.

The acquisition priority information 62b is information indicating the acquisition priority of the data of the equipment device 32. The acquisition priority information 62b is stored in the identifier information storage unit 62 in association with the Invoke_ID 62a. The acquisition priority information 62b includes, for example, “high” indicating that the data acquisition priority is high and “low” indicating that the data acquisition priority is high.

For example, in the example of FIG. 3, the acquisition priority information “high” is stored in the identifier information storage unit 62 in association with the Invoke_IDs “1” to “100”. Accordingly, Invoke_IDs “1” to “100” are assigned to messages having a high data acquisition priority. Also, the acquisition priority information “low” is stored in the identifier information storage unit 62 in association with the Invoke_IDs “101” to “256”. Accordingly, the Invoke_IDs “101” to “256” are assigned to messages with low data acquisition priority. In FIG. 3, only two types of acquisition priority information 62 b are shown, but three or more types of acquisition priority information 62 b may be stored in the identifier information storage unit 62.

The status information 62c is information indicating the issue status of the corresponding Invoke_ID 62a. As will be described later, the identifier information stored in the identifier information storage unit 62 is transmitted to the building management devices 31 and 41 and used by the building management devices 31 and 41. Accordingly, the status information 62c of the identifier information storage unit 62 stores an initial value such as “unissued”, for example.

The identifier information in the identifier information storage unit 62 shown in FIG. 3 can be displayed on the display of the terminal device 11. For example, the transmission unit 61 a acquires the identifier information stored in the identifier information storage unit 62 in response to an instruction from the terminal device 11 and transmits the identifier information to the terminal device 11. And the terminal device 11 displays the identifier information transmitted from the transmission part 61a on a display.

The administrator 12 can “change” the identifier information in the identifier information storage unit 62 on the display of the terminal device 11. Further, the administrator 12 can “create new” the identifier information stored in the identifier information storage unit 62 on the display of the terminal device 11. The identifier information “newly created” or “changed” is transmitted from the terminal device 11 to the receiving unit 61 b of the wide area management device 21 and stored in the identifier information storage unit 62. That is, the identifier information stored in the identifier information storage unit 62 is input by the administrator 12.

Note that the administrator 12 may or may not input the status information 62 c when the identifier information is “newly created” or “changed” using the terminal device 11. The administrator 12 inputs “unissued” when inputting the status information 62 c using the terminal device 11. Further, when the administrator 12 does not input the status information 62 c using the terminal device 11, for example, when the receiving unit 61 b receives the identifier information from the terminal device 11 and stores it in the identifier information storage unit 62, “ The “unissued” status information 62 c is stored in the identifier information storage unit 62. As a result, the status information 62c of the identifier information storage unit 62 stores an initial value such as “unissued”, for example.

In the above, an example of the data configuration of the identifier information of the building management device 31 of the building B1 is shown, but the identifier information of the building management device 41 of the building B2 also has the same data configuration as FIG. The identifier information of the building management device 41 is also stored in the identifier information storage unit 62 of the wide area management device 21.

Returning to the explanation of FIG. The data storage unit 63 stores data acquired by the sensors included in the equipment devices 32 and 42. The data storage unit 63 stores, for example, temperature data, current value data, or human detection data.

Note that, as described above, the transmission unit 61 a transmits the sensor data stored in the data storage unit 63 to the terminal device 11 in response to a request from the terminal device 11. The terminal device 11 displays the sensor data transmitted from the communication unit 61 on the display. Thereby, the administrator 12 can monitor the data acquired by the sensor of the equipment device 32.

The communication unit 64 includes a transmission unit 64a and a reception unit 64b, and communicates with the building management apparatuses 31 and 41. The transmission unit 64 a transmits the identifier information of the building management devices 31 and 41 stored in the identifier information storage unit 62 to each of the building management devices 31 and 41.

For example, when the identifier information stored in the identifier information storage unit 62 is “newly created” or “changed”, the transmission unit 64 a displays the identifier information of the building management apparatus 31 stored in the identifier information storage unit 62. To the building management device 31 of the building B1. In addition, when the identifier information of the building B2 stored in the identifier information storage unit 62 is “newly created” or “changed”, the transmission unit 64a stores the identifier information of the building B2 stored in the identifier information storage unit 62. Is transmitted to the building management apparatus 41 of the building B2.

The receiving unit 64b receives the sensor data of the facility devices 32 and 42 transmitted from the building management devices 31 and 41. The receiving unit 64 b stores the received sensor data of the facility equipment in the data storage unit 63.

In the above description, the communication unit 64 communicates with the two building management devices 31 and 41. However, the communication unit 64 can also communicate with a plurality of (three or more) building management devices.

FIG. 4 is a block diagram showing an example of the functional configuration of the building management apparatus 31. As shown in FIG. As illustrated in FIG. 4, the building management apparatus 31 includes a communication unit 71, a data request unit 72, a data storage unit 73, and a communication unit 74.

The communication unit 71 includes a transmission unit 71a and a reception unit 71b, and communicates with the wide area management device 21. For example, the receiving unit 71 b receives the identifier information transmitted from the wide area management device 21 and stored in the identifier information storage unit 62. The received identifier information is output to the communication unit 74.

The transmission unit 71 a transmits, for example, data acquired from the equipment 32 stored in the data storage unit 73 to the wide area management device 21.

The data request unit 72 outputs a data request for requesting data of the equipment 32 in accordance with an instruction from the event program. For example, the data request unit 72 outputs a data request at a certain cycle to a certain facility device 32 and outputs a data request at another cycle to another facility device 32. Further, for example, the data request unit 72 outputs a data request to the other equipment device 32 based on the data received from the equipment device 32.

The data request output from the data request unit 72 includes acquisition priority information indicating the acquisition priority of data acquired from the facility device 32. For example, a data request for a certain equipment device 32 output from the data request unit 72 includes acquisition priority information “high” indicating that data is acquired with high priority. In addition, the data request for another facility device 32 output from the data request unit 72 includes acquisition priority information “low” indicating that data need not be acquired with high priority. Note that the acquisition priority information included in the data request is described in advance in the event program. The data request output from the data request unit 72 is output to the communication unit 74.

In the data storage unit 73, the data of the equipment device 32 received by the communication unit 74 is stored. For example, the data storage unit 73 stores temperature data, current value data, or human detection data received by the communication unit 74. As described above, the data stored in the data storage unit 73 is transmitted to the wide area management device 21. The data is stored in the data storage unit 63 of the wide area management device 21.

The communication unit 74 communicates with the equipment device 32. For example, the communication unit 74 transmits the request message output from the data request unit 72 to the equipment device 32. Further, the communication unit 74 receives the response message and the data of the equipment device 32 from the equipment device 32.

The communication unit 74 is realized by, for example, BACnet I / F (I / F: Interface). Hereinafter, the communication unit 74 will be described using BACnet I / F as an example.

FIG. 5 is a block diagram showing an example of the functional configuration of the BACnet I / F. As shown in FIG. 5, the BACnet I / F (communication unit 74) includes a BACnet API layer 81 (API: Application Programming Interface), an application layer 82, a TSM (Transaction State Machine) manager 83, a service handler 84, and a network. A layer 85, a BACnet virtual link layer 86, and a physical layer 87 are included.

The BACnet API layer 81 performs data communication with the receiving unit 71b, the data requesting unit 72, and the data storage unit 73. For example, the BACnet API layer 81 receives the identifier information received from the wide area management device 21 by the receiving unit 71b. The BACnet API layer 81 outputs the received identifier information to the TSM manager 83 via the application layer 82.

In addition, the BACnet API layer 81 receives a data request output from the data request unit 72. The BACnet API layer 81 outputs the received data request to the TSM manager 83 via the application layer 82.

Also, the BACnetAPI layer 81 outputs the data of the equipment 32 received by the physical layer 87 to the data storage unit 73.

When the application layer 82 receives the data request output from the data request unit 72 via the BACnet API layer 81, the application layer 82 issues an Invoke_ID issuance request to the TSM manager 83. Further, the application layer 82 receives the Invoke_ID corresponding to the request for issuing the Invoke_ID from the TSM manager 83. When the application layer 82 receives the Invoke_ID from the TSM manager 83, the application layer 82 calls the service handler 84 to acquire data from the equipment device 32 using the received Invoke_ID.

Note that the data request output from the data request unit 72 includes acquisition priority information indicating the data acquisition priority as described above. The application layer 82 outputs the information including the acquisition priority information included in the data request to the TSM manager 83 when the Invoke_ID issuance request is issued.

The TSM manager 83 issues an Invoke_ID in response to an Invoke_ID issuance request from the application layer 82.

FIG. 6 is a block diagram showing an example of the functional configuration of the TSM manager 83. As illustrated in FIG. 6, the TSM manager 83 includes an identifier information storage unit 91, a determination unit 92, and an issue unit 93.

As described above, the receiving unit 71b of FIG. 4 receives the identifier information of the building management device 31 stored in the identifier information storage unit 62 of the wide area management device 21. The identifier information received by the receiving unit 71b is output to the TSM manager 83 via the BACnet API layer 81 and the application layer 82 in FIG. 5, and stored in the identifier information storage unit 91 in FIG.

FIG. 7 is a diagram showing a data configuration example of the identifier information storage unit 91. In the identifier information storage unit 91, Invoke_ID 91a, acquisition priority information 91b, and status information 91c are stored as identifier information. The Invoke_ID 91a and the acquisition priority information 91b are the same as the Invoke_ID 62a and the acquisition priority information 62b described in FIG.

The status information 91c is information indicating the issue status of the corresponding Invoke_ID 91a. That is, the status information 91c indicates whether or not the corresponding Invoke_ID 91a is currently assigned to the message.

For example, “Issuing” status information 91c in FIG. 7 indicates that the corresponding Invoke_ID is currently assigned to the message. The “unissued” status information 91c indicates that the corresponding Invoke_ID is not currently assigned to the message. Note that the “Issuing” Invoke_ID 62a is changed to “Not issued” when a response message is returned from the facility device 32, for example.

Returning to the explanation of FIG. The determination unit 92 receives a request for issuing the Invoke_ID output from the application layer 82. As described above, the issue request for Invoke_ID includes data acquisition priority information, and the determination unit 92 determines the acquisition priority of data acquired from the facility device 32.

The issuing unit 93 refers to the identifier information storage unit 91 based on the determination result of the determination unit 92, acquires the Invoke_ID, and outputs it to the application layer 82. That is, the issuing unit 93 issues an Invoke_ID in response to an Invoke_ID issuance request from the application layer 82.

For example, it is assumed that the determination result of the acquisition priority by the determination unit 92 is “high”. In this case, the issuing unit 93 acquires an Invoke_ID whose status information 91c is “unissued” and whose acquisition priority information 91b is “high”. Further, it is assumed that the determination result of the acquisition priority by the determination unit 92 is “low”. In this case, the issuing unit 93 acquires an Invoke_ID in which the status information 91c is “unissued” and the acquisition priority information 91b is “low”.

When there are a plurality of “unissued” status information 91c, the issuing unit 93 randomly acquires one Invoke_ID that matches the determination result of the determination unit 92 from the plurality of “unissued” Invoke_IDs. Also good. Alternatively, the issuing unit 93 may acquire an Invoke_ID having the smallest number that matches the determination result of the determining unit 92 among a plurality of “unissued” Invoke_IDs.

In addition, when the Invoke_ID of the acquisition priority information “high” is exhausted (when all are “issuing”), the issuing unit 93 determines the Invoke_ID for which the acquisition priority “high” is determined by the determination unit 92. Is issued, the status information is “unissued” and the acquisition priority information “low” Invoke_ID is issued.

For example, in FIG. 7, it is assumed that the acquisition priority information 91b for Invokes_ID “1” to “100” is “high” and the acquisition priority information 91b for Invokes_ID “101” to “256” is “low”. Further, it is assumed that the status information 91c of the Invoke_ID “1” to “255” is all “Issuing”, and the status information 91c of the Invoke_ID “256” is “Not issued”. In this case, the issuing unit 93 issues the Invoke_ID “256” when there is a request for issuing the Invoke_ID for which the acquisition priority “high” is determined by the determining unit 92.

In addition, the issuing unit 93 has a request for issuing an Invoke_ID for which the acquisition priority “high” is determined by the determination unit 92 when the Invoke_ID of the acquisition priority information “high” is exhausted. When the Invoke_ID is “Issuing”, the most recently issued Invoke_ID with the acquisition priority information “Low” is issued.

For example, in FIG. 7, it is assumed that all the Invoke_IDs “1” to “256” are “issuing”. Invoke_ID “101” among Invoke_IDs “101” to “256” of the acquisition priority information “low” is the most recently issued Invoke_ID. In this case, when there is an issue request for the Invoke_ID for which the acquisition priority “high” is determined by the determination unit 92, the issuing unit 93 is the most recently issued Invoke_ID “101” for the acquisition priority information “low”. Issue.

If there is a request for issuing an Invoke_ID with an acquisition priority “low”, the issuing unit 93 obtains the acquisition priority information “high” even if there is a vacant (unissued) Invoke_ID with the acquisition priority information “high”. Invoke_ID is not issued. That is, the Invoke_ID with the acquisition priority information “high” is prepared for an issuance request for Invoke_ID with a high acquisition priority. As a result, the TSM manager 83 can reduce the situation where the Invoke_ID cannot be issued when a request for data acquisition with high priority occurs.

In the above description, there are two cases where the acquisition priority information is “high” and “low”, but there may be three or more acquisition priority information. In this case, when the acquisition priority information of the acquisition priority included in the request for issuing the Invoke_ID is exhausted, the issuing unit 93 sets the Invoke_ID having a lower priority than the acquisition priority included in the request for issuing the Invoke_ID. Issue.

Returning to the explanation of FIG. The service handler 84 defines services used in the BACnet protocol stack and controls data transmission and reception. For example, the service handler 84 generates a request message for requesting data from the equipment device 32 when the service is called from the application layer 82 so as to obtain data from the equipment device 32 using Invoke_ID. The service handler 84 includes the Invoke_ID issued by the TSM manager 83 in the generated request message, and transmits it to the equipment 32 via the network layer 85, the BACnet virtual link layer 86, and the physical layer 87.

The network layer 85 responds to the service request of the application layer 82. The network layer 85 makes a service request to the BACnet virtual link layer 86. The BACnet virtual link layer 86 is an interface that connects the network layer 85 and the physical layer 87. The physical layer 87 controls the physical connection and transmission method of the network. The network layer 85, the BACnet virtual link layer 86, and the physical layer 87 are defined by the BACnet protocol stack standard.

FIG. 8 is a sequence diagram showing an operation example of the building management apparatus 31. The sequence in FIG. 8 is executed, for example, when the event program acquires the data of the equipment device 32.

First, the data request unit 72 outputs a data request for acquiring data from the equipment 32 in accordance with the event program (step S1). The data request output from the data request unit 72 includes acquisition priority information indicating an acquisition priority for acquiring data from the facility device 32.

Next, the BACnet API layer 81 receives the data request output from the data request unit 72 and outputs it to the application layer 82 (step S2).

Next, the application layer 82 receives a data request from the BACnet API layer 81 (step S3).

Next, when the application layer 82 receives a data request from the BACnet API layer 81, the application layer 82 issues an Invoke_ID issue request to the TSM manager 83 (step S4). The Invoke_ID issuance request includes the acquisition priority information included in the data request output by the data request unit 72.

Next, when the TSM manager 83 receives an Invoke_ID issue request from the application layer 82, the TSM manager 83 performs an Invoke_ID issue process (step S5). Here, the Invoke_ID issuance process of the TSM manager 83 will be described using a flowchart.

FIG. 9 is a flowchart showing an operation example of the TSM manager 83. The flowchart of FIG. 9 is executed when the TSM manager 83 receives an Invoke_ID issue request from the application layer 82.

First, the determination unit 92 of the TSM manager 83 determines whether the acquisition priority information included in the Invoke_ID issue request received from the application layer 82 is “high” or “low” (step S31). . When the acquisition priority information included in the Invoke_ID issuance request is “high” (in the case of “high” in step S31), the determination unit 92 shifts the processing to step S32. When the acquisition priority information included in the Invoke_ID issuance request is “low” (in the case of “low” in step S31), the determination unit 92 shifts the processing to step S37.

In step S31, when the determination unit 92 determines that the acquisition priority information included in the Invoke_ID issuance request is “high”, the issuance unit 93 refers to the identifier information storage unit 91 and the status information 91c. It is determined whether or not there is an Invoke_ID whose acquisition priority information 91b is “high”. If there is an Invoke_ID in which the status information 91c is “not issued” and the acquisition priority information 91b is “high” (in the case of “yes” in step S32), the issuing unit 93 shifts the process to step S33. If there is no Invoke_ID in which the status information 91c is “unissued” and the acquisition priority information 91b is “high” (“No” in step S32), the issuing unit 93 proceeds to step S34.

In step S32, when the issuing unit 93 determines that there is an Invoke_ID in which the status information 91c is “unissued” and the acquisition priority information 91b is “high”, the acquisition priority in which the status information 91c is “unissued”. The Invoke_ID whose information 91b is “high” is acquired. Further, the issuing unit 93 changes the status information 91c of the acquired Invoke_ID from “not issued” to “issued”. The issuing unit 93 issues (outputs) the acquired Invoke_ID to the application layer 82 that has issued the Invoke_ID issue request (Step S33).

In step S32, if the issuing unit 93 determines that there is no Invoke_ID in which the status information 91c is “unissued” and the acquisition priority information 91b is “high”, the acquisition priority is in which the status information 91c is “unissued”. It is determined whether there is an Invoke_ID whose degree information 91b is “low” (step S34). If there is an Invoke_ID in which the status information 91c is “unissued” and the acquisition priority information 91b is “low” (if “Yes” in step S34), the issuing unit 93 proceeds to step S35. If there is no Invoke_ID in which the status information 91c is “not issued” and the acquisition priority information 91b is “low” (if “No” in step S34), the issuing unit 93 proceeds to step S36.

In step S34, if the issuing unit 93 determines that there is an Invoke_ID in which the status information 91c is “unissued” and the acquisition priority information 91b is “low”, the acquisition priority is that the status information 91c is “unissued”. The Invoke_ID whose information 91b is “low” is acquired. Further, the issuing unit 93 changes the status information 91c of the acquired Invoke_ID from “not issued” to “issued”. The issuing unit 93 issues the acquired Invoke_ID to the application layer 82 that has issued the Invoke_ID issue request (Step S35).

In step S34, when the issuing unit 93 determines that there is no Invoke_ID in which the status information 91c is “unissued” and the acquisition priority information 91b is “low”, the status information 91c issued most recently is “ An Invoke_ID whose acquisition priority information 91b is “low” is acquired. The issuing unit 93 issues the acquired Invoke_ID to the application layer 82 that has issued the Invoke_ID issue request (Step S36).

In step S31, when the determination unit 92 determines that the acquisition priority information included in the Invoke_ID issuance request is “low”, the issuance unit 93 refers to the identifier information storage unit 91 and the status information 91c. It is determined whether or not there is an Invoke_ID whose acquisition priority information 91b is “low” with “not yet issued” (step S37). If there is an Invoke_ID in which the status information 91c is “unissued” and the acquisition priority information 91b is “low” (in the case of “Yes” in step S37), the issuing unit 93 shifts the process to step S38. If there is no Invoke_ID in which the status information 91c is “not issued” and the acquisition priority information 91b is “low” (if “No” in step S37), the issuing unit 93 proceeds to step S39.

In step S <b> 37, when the issuing unit 93 determines that there is an Invoke_ID whose status information 91 c is “unissued” and whose acquisition priority information 91 b is “low”, the acquisition priority whose status information 91 c is “unissued”. The Invoke_ID whose information 91b is “low” is acquired. Further, the issuing unit 93 changes the status information 91c of the acquired Invoke_ID from “not issued” to “issued”. The issuing unit 93 issues the acquired Invoke_ID to the application layer 82 that has issued the Invoke_ID issue request (Step S38).

In step S <b> 37, when the issuing unit 93 determines that there is no Invoke_ID whose status information 91 c is “unissued” and whose acquisition priority information 91 b is “low”, the issuing unit 93 indicates that the Invoke_ID is exhausted. (Invoke_ID cannot be issued) is output to the application layer 82 that has issued the Invoke_ID issue request (step S39).

Returning to the explanation of FIG. The issuing unit 93 outputs the issued Invoke_ID to the application layer 82 that has issued the Invoke_ID issuance request (step S6).

In addition, when the process of step S36 of FIG. 9 is performed, the issuing unit 93 outputs to the application layer 82 that the Invoke_ID has been discarded, as will be described below. When the application layer 82 receives from the issuing unit 93 that the Invoke_ID has been discarded, the application layer 82 outputs to the data request unit 72 that the Invoke_ID has been discarded. As a result, the event program that is the data request source can determine that the Invoke_ID has been discarded, and can determine that the data cannot be acquired from the facility device 32. Then, the event program can make a data acquisition request to the equipment device 32 again.

Further, when the processing of step S39 in FIG. 9 is performed, the issuing unit 93 notifies the application layer 82 that has issued the request for issuing the Invoke_ID that the Invoke_ID has been depleted (step S39). The application layer 82 outputs the notification received from the issuing unit 93 that the Invoke_ID is exhausted to the data request unit 72. As a result, the event program that is the data request source can determine that the Invoke_ID has not been issued, and can determine that the data cannot be acquired from the facility device 32. Then, the event program can make a data acquisition request to the equipment device 32 again.

Next, when receiving the Invoke_ID from the TSM manager 83, the application layer 82 makes a service call to the service handler 84 (step S7). When the application layer 82 makes a service call to the service handler 84, it outputs the Invoke_ID issued from the TSM manager 83 to the service handler 84.

Next, upon receiving a service call from the application layer 82, the service handler 84 performs service processing (step S8).

Next, the service handler 84 transmits a request message to the equipment 32 via the network layer 85, the BACnet virtual link layer 86, and the physical layer 87 (steps S9 and S10). The request message includes the Invoke_ID issued by the TSM manager 83.

Next, when the equipment device 32 receives the request message from the service handler 84, it performs response processing (step S11). For example, the facility device 32 acquires sensor data of the device itself.

Next, the facility device 32 includes the acquired data in the response message and transmits it to the building management device 31 (step S12). The facility device 32 includes the Invoke_ID included in the request message received in step S <b> 10 in the response message and transmits the response message to the building management apparatus 31.

Next, the service handler 84 receives the response message transmitted by the facility device 32 via the physical layer 87, the BACnet virtual link layer 86, and the network layer 85 (step S13).

Next, the service handler 84 outputs the response message received from the equipment 32 to the application layer 82 (step S14).

Next, the application layer 82 receives the response message output from the service handler 84 (step S15). The application layer 82 can determine which request message is the response message based on the Invoke_ID included in the received response message.

Next, the application layer 82 returns a response to the data request via the BACnet API layer 81 to the data request unit 72 that has requested the data (steps S16 and S17). The response includes the data of the equipment device 32.

Next, the data request unit 72 performs response processing of the received response (step S17). For example, the data request unit 72 outputs data to the event program that has requested the data.

The application layer 82 makes a release request for Invoke_ID to the TSM manager 83 (step S19). When making a request for releasing Invoke_ID, the application layer 82 outputs the Invoke_ID included in the response message received in Step S14 to the TSM manager 83.

The TSM manager 83 releases the Invoke_ID in response to the Invoke_ID release request from the application layer 82 (Step S20). For example, the issuing unit 93 of the TSM manager 83 changes the status information 62c corresponding to the Invoke_ID included in the Invoke_ID release request from “Issuing” to “Not issued”.

10 and 11 are sequence diagrams showing an example of the operation of the building management apparatus 31. FIG. The sequence of FIG. 10 shows an operation example when the Invoke_ID is discarded while the Invoke_ID is issued. For example, the sequences of FIGS. 10 and 11 show an operation example when the Invoke_ID is discarded in step S36 of FIG. 10, the same processes as those in FIG. 8 are denoted by the same reference numerals, and the description thereof is omitted.

The processing shown in steps S1 to S14 shown in FIG. 10 indicates processing of a data request for which the data acquisition priority is “low”, in which the Invoke_ID has been issued most recently. For example, if it takes time for the response message to be returned in step S14 after the data request is started in step S1, the processing in steps S1 to S14 is the data request for which the Invoke_ID has been issued most recently. It becomes processing of.

In the sequence of FIGS. 10 and 11, as shown in steps S51 to S57, etc., another data request is made while the processing of steps S1 to S14 is being performed. In this case, when all the Invoke_IDs have been issued, the most recently issued Invoke_ID with the acquisition priority “low” is discarded and assigned to the data request with the acquisition priority “high” (step of FIG. 9). Process of S36).

First, the data request unit 72 outputs a data request for acquiring data from the facility device 32 in accordance with the event program (step S51). The data request in step S51 is different from the data request in step S1. It is assumed that the data request output from the data request unit 72 includes acquisition priority information with an acquisition priority “high”.

Since the processing of steps S52 to S54 is the same as that of steps S2 to S4, description thereof is omitted.

Next, the TSM manager 83 issues an Invoke_ID (step S55). Here, as described above, all Invoke_IDs are being issued. In this case, the issuing unit 93 discards the most recently issued Invoke_ID whose acquisition priority information 91b is “low”, and issues the discarded Invoke_ID in response to an issuance request for an Invoke_ID having an acquisition priority “high”. .

Next, the TSM manager 83 notifies the application layer 82 of discarding the Invoke_ID issued in response to the data request in step S1 (step S56).

Next, the application layer 82 receives the discard of the Invoke_ID output from the TSM manager 83 (step S57).

Next, when receiving the destruction of the Invoke_ID from the TSM manager 83, the application layer 82 notifies the data request unit 72 of a service error (step S58). For example, the application layer 82 notifies a service error to the data request unit 72 that has made a data request (data request in step S1) corresponding to the discarded Invoke_ID. Note that the event program that has not been able to acquire the data of the equipment device 32 can execute the process of acquiring data from the equipment device 32 again by receiving a service error from the data request unit 72, for example.

The application layer 82 discards the response message when the response message to the data request in step S1 (response message in step S14) is returned.

Next, the TSM manager 83 outputs the Invoke_ID issued in step S55 to the application layer 82 (step S59).

Next, when receiving the Invoke_ID from the TSM manager 83, the application layer 82 makes a service call to the service handler 84 (step S60). This service call is a service call for the data request in step S51. Note that the processing in steps S61 to S73 is the same as that in steps S8 to S20 in FIG.

Each processing unit in the above-described sequence and flowchart is divided according to the main processing contents in order to make the processing of the building management apparatus 31 easy to understand. The present invention is not limited by the way of dividing the processing unit or the name. The processing of the building management apparatus 31 can be divided into more processing units according to the processing contents. Moreover, it can also divide | segment so that one process unit may contain many processes.

Also, the building management apparatus 41 performs the same operation as the sequence and flowchart shown in FIGS.

FIG. 12 is a diagram for explaining the allocation of the Invoke_ID. An arrow A11 shown in FIG. 12 indicates a conventional method for assigning Invoke_ID. In the conventional method, the Invoke_ID is not grouped based on the data acquisition request level. In the conventional method, a vacant Invoke_ID is issued regardless of the acquisition priority of the data acquisition of the equipment device 32. Therefore, there is a possibility that a time during which data that should originally be acquired with high priority cannot be acquired may occur.

An arrow A12 illustrated in FIG. 12 indicates the method of assigning the Invoke_ID according to the first embodiment. In the first embodiment, the Invoke_ID assigned to the message is grouped based on the data acquisition request level. For example, in the first embodiment, Invoke_ID is grouped into Invoke_ID assigned to a message having a high acquisition priority and Invoke_ID assigned to a message having a low acquisition priority.

Specifically, as indicated by an arrow A12, the Invoke_ID “001” to “100” assigned to a message to be acquired with high priority and the Invoke_ID “101” to “256” to be assigned to a message to acquire data with low priority. Group. The first embodiment issues an Invoke_ID from among the high priority Invoke_IDs “001” to “100” for messages that acquire data with high priority, and for messages that acquire data with low priority Invoke_ID is issued from among low priority Invoke_IDs “101” to “256”.

As described above, in the first embodiment, since a predetermined number of Invoke_IDs to be allocated to messages to be acquired with high priority is secured, it is possible to suppress the situation where the allocation of Invoke_ID is occupied by data with low acquisition priority. it can. That is, it is possible to reduce a situation in which a message identifier cannot be issued when a request for data acquisition with high priority occurs.

FIG. 13 is a diagram illustrating an example of a hardware configuration that realizes the function of the building management apparatus. As shown in FIG. 13, the building management apparatus 31 includes an arithmetic unit 101 such as a CPU (Central Processing Unit), a main storage device 102 such as a RAM (Random Access Memory), an HDD (Hard Disk Drive), and the like. An auxiliary storage device 103, a communication interface (I / F) 104 for connecting to a communication network by wire or wireless, an input device 105 such as a mouse, keyboard, touch sensor, and touch panel, and a display device 106 such as a liquid crystal display And a read / write device 107 that reads / writes information from / to a portable storage medium such as a DVD (Digital Versatile Disk).

For example, in the functions of the communication unit 71, the data request unit 72, and the BACnet I / F (communication unit 74) in FIG. 4, the arithmetic device 101 executes a predetermined program loaded from the auxiliary storage device 103 or the like to the main storage device 102. This is realized. The data storage unit 73 and the identifier information storage unit 91 are realized by the arithmetic device 101 using the main storage device 102 or the auxiliary storage device 103, for example. Communication between the building management device 31 and the wide area management device 21 is realized by the arithmetic device 101 using the communication I / F 104, for example. Further, the communication between the building management apparatus 31 and the equipment 32 is realized by the arithmetic device 101 using the communication I / F 104, for example.

Note that the predetermined program may be installed from, for example, a storage medium read by the read / write device 107 or may be installed from a network via the communication I / F 104.

Further, some or all of the functions of the building management apparatus 31 may be realized by a controller board including an ASIC (Application Specific Integrated Circuit) including an arithmetic device, a storage device, a drive circuit, and the like.

The functional configuration of the building management apparatus 31 described above is classified according to main processing contents in order to facilitate understanding of the configuration of the building management apparatus 31. The present invention is not limited by the way of classification and names of the constituent elements. The configuration of the building management device 31 can be classified into more components depending on the processing content. Moreover, it can also classify | categorize so that one component may perform more processes. Further, the processing of each component may be executed by one hardware or may be executed by a plurality of hardware.

In addition, although the BACnet I / F is realized by a program, it may be realized by a hardware communication I / F 104, for example. Further, when the building management apparatus 31 communicates with the equipment device 32 compliant with IEEE1888, the IEEE1888 I / F can be applied to the BACnet I / F. In addition, when the building management apparatus 31 communicates with the facility devices 32 and 42 with sensors, the sensor I / F can be applied to the BACnet I / F. Further, the data request unit 72 may be realized by an event program stored in the main storage device 102, for example. The wide area management device 21 and the terminal device 11 also have the same hardware configuration as that in FIG.

Further, the data request unit 72 may be realized by an event program. Further, the communication units 71 and 74 and the data request unit 72 may be realized by an event program.

As described above, the building management apparatuses 31 and 41 have identifier information storage units that store the Invoke_ID assigned to the message and the acquisition priority information indicating the acquisition priority of the data of the facility devices 32 and 42 in association with each other. . As a result, for example, a predetermined number of Invoke_IDs assigned to messages that are desired to be acquired with high priority will be secured, so that an Invoke_ID cannot be issued when a request to acquire data with high priority occurs. Can be reduced.

In addition, the building management devices 31 and 41 allocate, for example, an unissued low priority when there is a high priority data request when the Invoke_ID assigned to the high priority data request is exhausted. Issued Invoke_ID. As a result, it is possible to reduce the situation where the Invoke_ID cannot be issued when a request for data acquisition with high priority occurs.

In addition, the building management apparatuses 31 and 41, for example, when the Invoke_ID assigned to the high priority data request is exhausted and the Invoke_ID assigned to the low priority is the case when there is a high priority data request. If it is depleted, the lowest priority Invoke_ID issued in the past is discarded and issued for a high priority data request. As a result, it is possible to avoid a situation where the Invoke_ID cannot be issued when a request to acquire data with high priority occurs.

Note that the building management apparatuses 31 and 41 use up the Invoke_ID assigned to the low priority when the Invoke_ID assigned to the high priority data request is exhausted and the Invoke_ID assigned to the low priority is exhausted when there is a high priority data request. In this case, the Invoke_ID may not be issued for a high priority data request. Even in this case, it is possible to reduce the situation where the Invoke_ID cannot be issued when a request for data acquisition with high priority occurs.

[Second Embodiment]
In the first embodiment, the acquisition priority information is associated with the Invoke_ID and stored in the identifier information storage unit. In the second embodiment, the amount of data acquired from the equipment is further associated with Invoke_ID and stored in the identifier information storage unit.

FIG. 14 is a diagram illustrating a data configuration example of the identifier information storage unit 91 according to the second embodiment. 14, the same components as those in FIG. 7 are denoted by the same reference numerals, and the description thereof is omitted.

As shown in FIG. 14, the identifier information storage unit 91 further stores data amount information 111 as identifier information. The data amount information 111 indicates the data amount of data acquired from the facility device 32. For example, “S” in the data amount information 111 in FIG. 14 indicates that the amount of data acquired from the facility device 32 is small. Further, “L” in the data amount information 111 indicates that the amount of data acquired from the facility device 32 is large.

In the second embodiment, the data request output from the data request unit 72 includes data amount information of data acquired from the equipment 32 in addition to the acquisition priority information. The Invoke_ID issuance request output from the application layer 82 to the TSM manager 83 includes acquisition priority information and data amount information. The issuing unit 93 of the TSM manager 83 acquires the Invoke_ID 91a to be issued based on the acquisition priority information and the data amount information included in the Invoke_ID issue request. For example, the issuing unit 93 refers to the identifier information storage unit 91 in FIG. 14, and determines the Invoke_ID 91a in which the acquisition priority information included in the Invoke_ID issuance request whose status information 92c is “unissued” and the data amount information match. get.

More specifically, it is assumed that the issuing unit 93 receives a request for issuing an Invoke_ID including the acquisition priority information “high” and the data amount information “S” from the application layer 82. In this case, the issuing unit 93 acquires an unissued Invoke_ID from the Invoke_IDs “1” to “98” in which the acquisition priority information 91b is “high” and the data amount information 111 is “S”. And issue.

In addition, it is assumed that the issuing unit 93 receives a request for issuing an Invoke_ID including the acquisition priority information “high” and the data amount information “L” from the application layer 82. In this case, the issuing unit 93 acquires the unissued Invoke_ID from the Invoke_IDs “99” and “100” in which the acquisition priority information 91b is “high” and the data amount information 111 is “L”. And issue.

In the above description, only two types of data amount information “S” and “L” are shown, but there may be three or more types.

In the above description, the building management apparatus 31 has been described. Similarly, the building management apparatus 41 issues an Invoke_ID based on the acquisition priority information and the data amount information.

As described above, the building management devices 31 and 41 obtain the Invoke_ID assigned to the message, the acquisition priority information indicating the acquisition priority of the data of the facility devices 32 and 42, and the data amount acquired from the facility devices 32 and 42, respectively. It has an identifier information storage unit that stores data amount information to be shown in association with each other. As a result, for example, allocation of Invoke_ID is restricted for a data request with a large amount of data, so that a situation in which Invoke_ID cannot be issued when a request to acquire data with higher priority occurs even in high priority is reduced. can do.

Specifically, a data request whose data amount information is “L” is generated when requesting a trend graph or the like from the equipment devices 32 and 33, and the data amount information is such that only current data is acquired in real time. It is considered that the priority is lower than the data request “S”. Therefore, even if the acquisition priority information is “high”, the number of Invoke_IDs assigned to data requests with the data amount information “L” is set to be smaller than the number of Invoke_IDs assigned to data requests with the data amount information “S”. . As a result, it is possible to reduce the situation where the Invoke_ID cannot be issued when a request to acquire data with a higher priority (a data request with the data amount information “S”) occurs even in the higher priority.

[Third Embodiment]
In the third embodiment, the data request output from the data request unit 72 further includes an estimated time (collected time estimated value) required to collect the data of the equipment device 32. The estimated collection time value included in the data request output from the data request unit 72 is stored in the identifier information storage unit.

FIG. 15 is a diagram illustrating a data configuration example of the identifier information storage unit 91 according to the third embodiment. 15, the same components as those in FIG. 7 are denoted by the same reference numerals, and the description thereof is omitted.

As shown in FIG. 15, the identifier information storage unit 91 further stores a collection time estimated value 112 as identifier information. The collection time estimated value indicates an estimated value of the time required to acquire data from the facility device 32.

The data request output from the data request unit 72 includes an estimated collection time value in addition to the acquisition priority information. The Invoke_ID issuance request output from the application layer 82 to the TSM manager 83 includes acquisition priority information and an estimated collection time. When the issuing unit 93 of the TSM manager 83 issues the Invoke_ID in response to the Invoke_ID issuance request received from the application layer 82, the collection time estimation value included in the Invoke_ID issuance request corresponding to the issued Invoke_ID, Store in the identifier information storage unit 91.

For example, it is assumed that the issuing unit 93 receives a request for issuing an Invoke_ID including the acquisition priority information “high” and the collection time estimated value “1 second”. For example, the issuing unit 93 refers to the identifier information storage unit 91 and issues an Invoke_ID “100” whose acquisition priority information “not issued” is “high”. In this case, the issuing unit 93 stores “1 second” in the estimated collection time 112 corresponding to the Invoke_ID “100”.

When the issuing unit 93 issues an Invoke_ID and stores the estimated collection time value, for example, a timer corresponding to the issued Invoke_ID is provided. Then, the issuing unit 93 monitors the timer and determines whether or not the estimated collection time has elapsed after issuing the Invoke_ID. For example, in the case of the above example, the issuing unit 93 determines whether or not “1 second” has elapsed after issuing the Invoke_ID “100”.

The issuing unit 93 discards the issued Invoke_ID when it does not receive an Invoke_ID release request from the application layer 82 before the estimated collection time is exceeded after issuing the Invoke_ID. For example, the issuing unit 93 notifies the application layer 82 of the Invoke_ID to be discarded and information indicating that the Invoke_ID has timed out. That is, the issuing unit 93 times out the Invoke_ID when the estimated data collection time elapses due to a failure of the equipment device 32 or the like, and avoids a situation where the Invoke_ID cannot be assigned to a new request message.

Note that when the application layer 82 receives information indicating that the Invoke_ID has timed out from the issuing unit 93, the application layer 82 discards the time-out Invoke_ID response message received thereafter. In addition, the application layer 82 notifies the data request unit 72 of a service error.

In the above description, the building management apparatus 31 has been described. However, as with the building management apparatus 41, the estimated collection time value is stored in the identifier information storage unit, and the issue time of the Invoke_ID is monitored.

In this way, the building management devices 31 and 41 store the collection time estimated value in the identifier information storage unit in correspondence with the issued Invoke_ID, and issue it after the collection time estimated value has passed since issuing the Invoke_ID. Discard Invoke_ID. Thereby, the building management apparatuses 31 and 41 can avoid the situation where Invoke_ID cannot be assigned to a new request message.

As mentioned above, although this invention was demonstrated using embodiment, the technical scope of this invention is not limited to the range as described in the said embodiment. It will be apparent to those skilled in the art that various modifications or improvements can be made to the above embodiment. For example, the first embodiment to the third embodiment can be combined. Specifically, based on the acquisition priority information and the data amount information, the Invoke_ID is assigned to the message (second embodiment), and the collection time estimation value is stored in the identifier information storage unit, and the collection time estimation is performed. Invoke_ID exceeding the value may be timed out (third embodiment).

Also, the TSM manager 83 may monitor the issue status of the Invoke_ID and change the acquisition priority information. For example, the TSM manager 83 includes a monitoring unit that monitors information stored in the identifier information storage unit 91. For example, the monitoring unit monitors the issuance status of the acquisition priority information “low”, and if the number of issued acquisition priority information “low” is over a certain threshold and a predetermined time has elapsed, the acquisition priority Increase the number of information “low” by a predetermined number. Specifically, in the example of FIG. 3, 156 Invokes_IDs of the acquisition priority information “low” are allocated, but when a predetermined time has passed in a state where the number of issues exceeds a certain threshold, the monitoring unit The number of Invoke_IDs with the acquisition priority information “high” is decreased by a predetermined number, and the number of Invoke_IDs with the acquisition priority information “low” is increased by a predetermined number. That is, the monitoring unit changes the allocation numbers of the acquisition priority information “high” and “low”. As a result, it is possible to avoid a state in which data with an acquisition priority of “low” cannot be acquired. Note that the monitoring unit restores the number of acquisition priority information “low” to the original when the number of issued acquisition priority information “low” being issued does not exceed a certain threshold and a predetermined time has elapsed.

The monitoring unit may also have a building management device 41. The monitoring unit may be provided in the wide area management device 21. In this case, the monitoring unit receives and monitors the identifier information in the identifier information storage unit from the building management devices 31 and 41.

Further, it is apparent from the description of the scope of the claims that the embodiments added with such changes or improvements can be included in the technical scope of the present invention. The present invention can also be provided as a method for controlling the wide area management system 1, the wide area management device 21, the building management devices 31, 31, a program for controlling, and a storage medium storing the program.

11 terminal device, 12 administrator, 21 wide area management device, 31, 41 building management device, 33, 43, 51 network, 32, 42 equipment, 61, 64, 71, 74 communication unit, 62, 91 identification information storage unit 63, 73 Data storage unit, 72 Data request unit, 81 BACnet API layer, 82 Application layer, 83 TSM manager, 84 Service handler, 85 Network layer, 86 BACnet virtual link layer, 87 Physical layer, 92 Judgment unit, 93 Issuing unit .

Claims (17)

1. A wide area management device;
   A building management device provided corresponding to a building in which equipment is installed, and exchanging messages with the equipment and obtaining data from the equipment;
   Have
   The wide area management device includes:
   A first identifier information storage unit that stores an identifier assigned to the message and acquisition priority information indicating an acquisition priority of the data in association with each other;
   A transmission unit for transmitting the identifier stored in the first identifier information storage unit and the acquisition priority information to the building management device;
   Have
   The building management device
   A receiving unit for receiving the identifier and the acquisition priority information transmitted from the transmitting unit;
   A second identifier information storage unit for storing the identifier received by the receiving unit and the acquisition priority information;
   An issuing unit that refers to the second identifier information storage unit and issues the identifier according to the acquisition priority of the data of the message;
   A wide area management system characterized by comprising:
2. The wide area management system according to claim 1,
   The building management device
   Further requesting the data of the equipment, further comprising a data request unit for outputting a data request including the acquisition priority information,
   The issuing unit refers to the second identifier information storage unit, and issues the identifier corresponding to the acquisition priority information included in the data request of the data request unit. .
3. The wide area management system according to claim 2,
   The acquisition priority information includes first acquisition priority information and second acquisition priority information having a higher acquisition priority of the data than the first acquisition priority information. system.
4. The wide area management system according to claim 3,
   The issuing unit, when the identifier of the second acquisition priority information is exhausted, and there is the data request including the second acquisition priority information, the first acquisition priority information A wide area management system that issues the identifier.
5. The wide area management system according to claim 4,
   The issuance unit issues the identifier of the first acquisition priority information that has not been issued.
6. The wide area management system according to claim 4,
   When the identifier of the first acquisition priority information is exhausted, the issuing unit uses the identifier of the first acquisition priority information issued most recently as the second acquisition priority information. A wide area management system for issuing the data request including the data request.
7. The wide area management system according to claim 2,
   In the second identifier information storage unit, corresponding to the identifier, data amount information of the data acquired from the equipment is stored,
   The data request output from the data request unit includes the data amount information of the data,
   The issuing unit refers to the second identifier information storage unit and issues the identifier corresponding to the acquisition priority information and the data amount information included in the data request of the data request unit. A featured wide area management system.
8. The wide area management system according to claim 2,
   The data request output from the data request unit includes an estimated value of the time required for collecting the data,
   The estimated value is stored in the second identifier information storage unit corresponding to the identifier assigned to the data request.
9. The wide area management system according to claim 8,
   The issuance unit stores issuance state information indicating an issuance state of the identifier in the second identifier information storage unit, and when the issued identifier has passed the estimated value time, the issuance state information of the identifier Wide-area management system characterized by unpublished.
10. A wide area management system according to any one of claims 1 to 9,
    The issuing unit monitors an issuing state of the identifier;
    The acquisition priority information is changed according to the issuance state.
11. An identifier assigned to a message exchanged between the building management apparatus provided in the building and the equipment is associated with acquisition priority information indicating the acquisition priority of data acquired from the equipment. An identifier information storage unit,
    A transmission unit that transmits the identifier stored in the identifier information storage unit and the acquisition priority information to the building management device;
    A wide area management apparatus characterized by comprising:
12. An identifier assigned to a message exchanged between the building management device provided in the building and the facility device from a wide area management device that manages power consumed in the building, and the facility device associated with the identifier A receiving unit for receiving acquisition priority information indicating an acquisition priority of data acquired from:
    An identifier information storage unit for storing the identifier received by the receiving unit and the acquisition priority information;
    An issuing unit that references the identifier information storage unit and issues the identifier according to the acquisition priority of the data of the message;
    The building management apparatus characterized by having.
    Building management device.
13. A wide area management method for a wide area management system, comprising: a wide area management apparatus; and a building management apparatus that is provided corresponding to a building in which the equipment is installed and exchanges messages with the equipment and acquires data from the equipment. There,
    The wide area management device includes:
    A first identifier information storing step for storing an identifier assigned to the message and acquisition priority information indicating an acquisition priority of the data in association with each other;
    A transmitting step of transmitting the identifier stored in the first identifier information storing step and the acquisition priority information to the building management device;
    Have
    The building management device
    A receiving step of receiving the identifier and the acquisition priority information transmitted by the transmitting step;
    A second identifier information storing step for storing the identifier received by the receiving step and the acquisition priority information;
    An issuing step of referring to the identifier stored in the second identifier information storing step and the acquisition priority information, and issuing the identifier according to the acquisition priority of the data of the message;
    A wide area management method characterized by comprising:
14. An identifier information transmission method for a wide area management device, comprising:
    An identifier assigned to a message exchanged between the building management apparatus provided in the building and the equipment is associated with acquisition priority information indicating the acquisition priority of data acquired from the equipment. An identifier information storing step,
    A transmitting step of transmitting the identifier stored in the identifier information storing step and the acquisition priority information to the building management device;
    An identifier information transmission method characterized by comprising:
15. An identifier issuing method for a building management device,
    An identifier assigned to a message exchanged between the building management device provided in the building and equipment from a wide area management device that manages power consumed in the building, and the equipment associated with the identifier A receiving step for receiving acquisition priority information indicating an acquisition priority of data acquired from the device;
    An identifier information storing step for storing the identifier received by the receiving step and the acquisition priority information;
    Issuing step of referring to the identifier stored in the identifier information storing step and the acquisition priority information, and issuing the identifier according to the acquisition priority of the data of the message;
    An identifier issuing method characterized by comprising:
16. A program for a wide area management device,
    An identifier assigned to a message exchanged between the building management apparatus provided in the building and the equipment is associated with acquisition priority information indicating the acquisition priority of data acquired from the equipment. An identifier information storage unit,
    A transmission unit that transmits the identifier stored in the identifier information storage unit and the acquisition priority information to the building management device;
    And a program for causing the wide area management apparatus to function.
17. A building management device program,
    An identifier assigned to a message exchanged between the building management device and equipment provided in the building from a wide area management device that manages power consumed in the building, and the equipment associated with the identifier A receiving unit that receives acquisition priority information indicating acquisition priority of data acquired from a device;
    An identifier information storage unit for storing the identifier received by the receiving unit and the acquisition priority information;
    An issuing unit that references the identifier information storage unit and issues the identifier according to the acquisition priority of the data of the message;
    And the building management apparatus is made to function.

Images