JP2007316863A - Facility monitoring system and apparatus - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a facility monitoring system for automatically adapting to an increase and decrease in the number of monitoring apparatuses without collecting facility situations of a building etc., at a place and also referring to all the facility situations via the Internet. <P>SOLUTION: In the system including monitoring apparatuses, each of the constituting apparatuses has a Web server function, and is mutually connected to form a network. The monitoring apparatus having a communication means to communicate with the outside of the system automatically acquires local IP addresses of other monitoring apparatuses, stores identification information of the monitoring apparatuses and file information based on the IP addresses by associating them, and generates and replies data for a reply by using a prescribed file shown by the file information stored by associating with the identification information when receiving a request for information by specifying the identification information from the outside of the system. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a function for monitoring equipment such as a building, and more particularly to a technique for referring to a monitoring result.

Conventionally, in order to check whether facilities such as buildings, such as lighting equipment and air conditioning equipment, are operating normally, it is possible to connect each equipment to a network so that the status of the equipment can be grasped in one place. I have to. This is because in a building of a certain size, the number of lighting facilities alone is considerable, so manual inspection is not efficient.
In addition, in order to collectively monitor the facilities of large-scale buildings and a plurality of buildings, a system has been developed in which the entire facilities are classified and managed by a plurality of monitoring devices. This system can be linked to each monitoring device so that the equipment status of each monitoring device can be referred from one place without collecting it in one place, and the system can be reconfigured automatically by increasing or decreasing the number of monitoring devices. Therefore, the trouble of resetting the link is eliminated (see Patent Document 1).

Although this technique has an advantage that the equipment status of each monitoring device can be referred to without being aggregated and a link is automatically established, the equipment status can be referred to only from within the same network.
This is because the link established to each monitoring device uses a local IP (Internet Protocol) address that is valid only inside a LAN (Local Area Network) or the like.

That is, it is not possible to refer to the equipment status of each monitoring apparatus from the outside such as a LAN via the Internet or the like using the information related to the link.
In view of the recent spread of the Internet, it is desirable from the viewpoint of convenience for users and managers that it is possible to refer to the equipment status not only from within the LAN or the like, but also from the WAN side, that is, via the Internet.

Here, as a technology that can refer to the equipment status of multiple buildings via the Internet etc., collect the equipment status of each building collected by the management device of each building in the server device and access all the server devices There is a technology that can refer to the equipment status (see Patent Document 2).
JP 2006-039965 A JP 2000-308152 A

However, in this technology, each monitoring device must transmit the equipment status to the server device, and each time the monitoring device increases or decreases, it is necessary to make settings for it, and the entire equipment status is collected in the server device. There is a disadvantage that a large capacity memory is required.
Therefore, the present invention is capable of automatically responding to increase / decrease of the monitoring device without collecting the facility status of the building etc. in one place, and can monitor all the facility status via the Internet. The purpose is to provide a system.

  In order to solve the above-described problems, an equipment monitoring system according to the present invention is an equipment monitoring system that includes a plurality of monitoring devices each having a Web server function and connected to each other via a network. The monitoring device having communication means for communicating with the outside of the equipment monitoring system includes an acquisition means for acquiring a local IP address of another monitoring device connected to the network, and the other monitoring device connected to the network. Storage means for associating and storing identification information for identification and information based on the local IP address obtained by the obtaining means and indicating file information indicating a predetermined file in the other monitoring device; When the identification information is designated from outside the equipment monitoring system and an information request is received, the file information stored in association with the identification information is stored. In using a predetermined file indicated to create the response data, characterized by comprising a returning means for returning.

  The facility monitoring system according to the present invention has the above-described configuration, so that the monitoring device connected to the outside of the system detects another monitoring device connected to the system at a certain point in time, and the identification information of the monitoring device Since a predetermined file is stored in association with each other, even if the monitoring device increases or decreases, the change is automatically detected, and by specifying identification information of the monitoring device from outside the system, for example, the Internet, the monitoring device's It is possible to refer to a predetermined file.

Since the detection of the monitoring device and the association between the identification information of the monitoring device and the predetermined file are automatically performed, it is possible to save the trouble of setting even when the number of the monitoring devices increases or decreases. .
In addition, since any file in the LAN can be accessed from the Internet, not only can the file for each monitoring device be referenced, but detailed settings for each monitoring device can be performed via the Internet, and management can be performed from a distance. There is an advantage that work can be performed.

Moreover, when developing this system, it is only necessary to develop the Web service function of the monitoring device to be added, and it is not necessary to newly create or modify the contents for integration thereof. Since there is no need to replace the monitoring device with a new monitoring device, there is an advantage that the cost at the time of system development can be suppressed.
Here, creating a reply file is not only processing a file or creating a new file by referring to a file, but also creating a file once in the memory of the device itself. Is also included.

  The monitoring device having a communication unit that communicates with the outside of the facility monitoring system further includes a transmission unit that transmits the identification information of the other monitoring device to the outside of the facility monitoring system, and the reply unit includes the transmission unit. When a request for specifying one or more pieces of identification information among the identification information transmitted by the means is received, reply data is created using a predetermined file indicated by the file information stored in association with the identification information. It is also possible to reply.

As a result, the identification information of each monitoring device can be transmitted to the outside of the system and the identification information can be designated from the outside of the system, so that a predetermined file of an arbitrary monitoring device can be designated and referred to.
In addition, the identification information transmitted by the transmission unit may be information indicating the name of the other monitoring device.

Thereby, since the identification information of each monitoring apparatus can be created with characters, the name of the monitoring apparatus can be displayed on the browser outside the system.
By making this name a name that can recognize the location, role, etc. of the monitoring device, there is an advantage that it is possible to easily recognize which monitoring device the user is.
The transmission means may further transmit information for identifying a specific file in the other monitoring device.

Thereby, since the identification information of the predetermined file of a certain monitoring apparatus can be further described in the file to be returned, any file can be displayed sequentially in a hierarchical manner. For example, an HTML frame or the like.
The predetermined file in the other monitoring device includes information on equipment connected to the other monitoring device, and the reply data created by the reply unit is created using the predetermined file. It may be information described in a Web page description language.

As a result, the reply file can be created in the Web page description language, so that the browser displaying the monitoring information can easily display the status of the monitored equipment in each monitoring device.
The local IP address acquired by the acquisition unit may be a local IP address when an IP packet is transmitted to a certain local IP address and the IP packet is normally received.

As a result, it is possible to confirm whether or not an IP packet can be received, so that a monitoring device connected to the network can be easily acquired.
The monitoring device having a communication unit that communicates with the outside of the facility monitoring system further includes a granting unit that gives a local IP address to another monitoring device connected to the network, and the obtaining unit obtains the monitoring device. The local IP address may be a local IP address assigned to another monitoring device by the assigning unit.

As a result, a monitoring device connected to the outside can assign a local IP address to another monitoring device, so that the monitoring device to which the address is assigned can be quickly acquired. In this case, there is an advantage that traffic on the network for detecting the connected monitoring device can be suppressed.
The monitoring device according to the present invention is a monitoring device used in an equipment monitoring system that includes a plurality of monitoring devices each having a Web server function and connected to each other over the network. Identification means for identifying communication means for communicating with the outside of the equipment monitoring system, acquisition means for obtaining a local IP address of another monitoring apparatus connected to the network, and the other monitoring apparatus connected to the network And storage means for storing information associated with the local IP address acquired by the acquisition means and indicating file information indicating a predetermined file in the other monitoring device, and external to the equipment monitoring system When a request for information is received by designating the identification information from a predetermined file indicated by the file information stored in association with the identification information Used to create the response data, characterized by comprising a returning means for returning.

  Further, the computer program according to the present invention is a computer program for causing a monitoring device used in an equipment monitoring system having a plurality of monitoring devices each having a Web server function and connected to each other to perform monitoring processing. The monitoring device communicates with the outside of the facility monitoring system, acquires a local IP address of another monitoring device connected to the network, and other connected The identification information for identifying the monitoring device and the information based on the local IP address acquired in the acquisition step and file information indicating a predetermined file in the other monitoring device are associated with each other in the memory. A storage step for storing, and requesting information by designating the identification information from outside the equipment monitoring system. If digits, create a response data using a predetermined file indicated by the file information stored in association with the identification information, characterized in that it comprises a return step for returning.

  As a result, the facility monitoring system can be easily constructed.

<Embodiment 1>
<Overview>
The facility monitoring system according to the present invention is configured so that, when a monitoring device connected to the Internet among the monitoring devices constituting the system receives access via the Internet, the facility monitoring system is installed from another monitoring device whenever necessary. The situation is received and sent back via the Internet.

For this purpose, a monitoring device connected to the Internet (hereinafter referred to as “monitoring server device”) is a facility desired by a device accessed via the Internet (hereinafter referred to as “monitoring information display device”). It is necessary to know which monitoring device is collecting the situation, and when the number of monitoring devices increases or decreases, it is necessary to know effective monitoring devices in a timely manner.
The information that such a monitoring server device should know is that the network administrator etc. resets whenever there is a change. In this system, the information can be reset automatically, and the equipment provider And the convenience of users.

Hereinafter, a system for monitoring an emergency light of a building will be described as an example of an equipment monitoring system according to the present invention.
<Configuration>
First, the structural example of the equipment monitoring system which concerns on embodiment of this invention is demonstrated using FIG.

FIG. 1 is a diagram illustrating a configuration example of an equipment monitoring system according to an embodiment of the present invention.
The facility monitoring system 100 includes a monitoring server device 1000, a monitoring device (2000, 3000, 4000), and a router 5000, which are connected via a LAN 110. In this figure, for convenience of explanation, it is assumed that three of the plurality of monitoring devices and one monitoring server device are described.

The router 5000 is connected to the monitoring information display device 9000 via the Internet 200.
In this embodiment, it is assumed that the monitoring server device 1000, the monitoring device 2000, the monitoring device 3000, and the monitoring device 4000 are monitoring the status of emergency lights on each floor, and whether each emergency light is normal or not. Are regularly recorded.

For example, the monitoring server device 1000 monitors an emergency light on the third floor underground, and the monitoring device 2000 monitors an emergency light on the third floor. Each device is given a name. For example, the monitoring device 2000 is “3F lighting control device”.
Each device connected to the LAN 110 has a local IP address. In this figure, the local IP address of each device is described in the upper left of the rectangle indicating each device. For example, the monitoring device 2000 is like “192.168.0.7”.

The router 5000 has a function similar to that of a normal router, and has a local IP address “192.168.0.254” and a global IP address “133.254.7.211” for connecting to the Internet 200.
The monitoring information display device 9000 is connected to the Internet and has a browser function for normal Web content. The user of this system checks the status of the emergency light of the building from the monitoring information display device 9000.

Next, the monitoring server device 1000 and the monitoring devices (2000, 3000, 4000) will be described with reference to FIG.
FIG. 2 is a functional block diagram of the monitoring server device 1000 and the monitoring device 2000 according to the present invention.
The monitoring device 2000, the monitoring device 3000, and the monitoring device 4000 have the same configuration. Here, the monitoring device 2000 will be described.

The monitoring server device 1000, the monitoring device 2000, and the like of this embodiment have a function of a normal facility monitoring device, but the monitoring server device 1000 further has a server function. Note that “monitoring device 2000 or the like” refers to all monitoring devices other than the monitoring server device such as the monitoring device 3000 and the monitoring device 4000, and the same applies to the following.
First, the monitoring server device 1000 includes a network communication unit 1100, a Web service processing unit 1200, a monitoring information file acquisition unit 1300, a monitoring device detection unit 1400, a correspondence information storage unit 1500, and a monitoring information storage unit 1600.

First, the network communication unit 1100 has a function of exchanging data with other monitoring devices 2000 and the like and the router 5000 through the LAN 110.
Next, the Web service processing unit 1200 has a function of creating and returning a content file for browsing with a browser in response to a request from the Web browser.
Specifically, a request from the monitoring information display device 9000 is received via the router 5000, and an HTML (Hyper Text Markup Language) file to be displayed on the browser of the monitoring information display device 9000 is created and sent back.

In response to the request, the file to be returned is a file stored in the own device, is created using data stored in the own device, or is stored in the monitoring device 2000 or the like. There are cases where data that has been used is used.
When a file stored in another monitoring device 2000 or the like is required, the monitoring information file acquisition unit 1300 is requested to acquire the file.

When this Web service processing unit 1200 requests the monitoring information file acquisition unit 1300 to acquire a file, the Web service processing unit 1200 needs to instruct which monitoring device to acquire the file from, but is stored in the correspondence information storage unit 1500. Determine by referring to the table. The table will be described later in <Data>.
The monitoring information file acquisition unit 1300 operates as a Web client in response to a request from the Web service processing unit 1200 and has a function of acquiring a file stored in another monitoring device 2000 or the like. Further, the acquired file has a function of processing it as necessary and returning it to the monitoring information display device 9000 via the network communication unit 1100. Furthermore, it has a function of passing the acquired file to the Web service processing unit 1200 depending on a request from the Web service processing unit 1200.

The monitoring device detection unit 1400 has a function of detecting a device functioning as an HTTP (HyperText Transfer Protocol) server among devices connected to the LAN 110 and a function of creating a table for managing these detected devices. . The table to be created will be described in the following <Data> section using FIG.
This monitoring device detection unit 1400 operates when the system is started up, and operates periodically in case the number of monitoring devices constituting the system increases or decreases. In addition, a user interface function (not shown) for detecting a button press or the like is provided, and it is possible to operate according to an instruction from the administrator.

The correspondence information storage unit 1500 stores a table for managing devices created by the monitoring device detection unit 1400, and has a function of reading, writing, and the like.
In addition, the monitoring information storage unit 1600 has a function of storing, reading, updating, and the like of the state of the emergency light monitored by the monitoring server apparatus 1000.
Next, the monitoring device 2000 will be described.

The monitoring device 2000 includes a network communication unit 2100, a web service processing unit 2200, and a monitoring information storage unit 2600.
The network communication unit 2100 has a function similar to that of the network communication unit 1100 of the monitoring server apparatus 1000, and has a function of exchanging data with the monitoring server apparatus 1000, other monitoring apparatuses (such as 3000) and the router 5000 through the LAN 110. Have.

The Web service processing unit 2200 has a function of returning a stored file or a file processed as necessary to the monitoring server apparatus 1000 in response to a request from the monitoring server apparatus 1000.
The monitoring information storage unit 2600 has a function of storing the state of the emergency light monitored by the monitoring device 2000, reading, updating, and the like.

Here, all or a part of each processing by each unit such as the Web service processing unit 1200 is realized by a CPU (not shown) executing various programs.
<Data>
Hereinafter, main data used by the equipment monitoring system according to the present invention will be described with reference to FIG. Refer to FIGS. 4 and 5 for the description.

FIG. 3 is a diagram showing a table for managing the monitoring device, FIG. 3A is a diagram showing a configuration and example contents of the IP table 1510, and FIG. 3B is a diagram showing a configuration of the link table 1520. It is a figure which shows the example of a content.
These tables are created by the monitoring device detection unit 1400 of the monitoring server device 1000 and stored in the correspondence information storage unit 1500. Also. Referenced by the Web service processing unit 1200.

4A is a diagram illustrating a configuration example of a directory included in the monitoring server apparatus 1000, and FIG. 4B is a diagram illustrating a configuration example of a directory included in the monitoring apparatus 2000 or the like. It is assumed that an ellipse is a directory and a rectangle indicates a file (the same applies to FIG. 11).
FIG. 5 is a diagram showing an example of the contents of the file 2621 “/AutoLink/Index.html” shown in FIG.

First, the IP table 1510 in FIG.
The IP table 1510 includes a local IP address 1511 and a reference directory 1512.
A local IP address 1511 represents a local IP address of a device connected to the LAN 110.

In this table, only the address of a device that functions as an HTTP server is registered. Therefore, basically, only the address of the monitoring device is registered, and the address of the router 5000 is not registered. In addition, a non-functional monitoring device is not registered, and a monitoring device removed from the LAN 110 is not registered in this table.
That is, in this table, only monitoring devices that are functioning effectively as HTTP servers at the present time are registered. In this embodiment, it is assumed that the local IP address “192.168.0.100” of the monitoring server device that is the device itself is not registered.

The reference directory 1512 represents a directory when accessing the monitoring device represented by these local IP addresses 1511 from outside the LAN 110. Accordingly, it is only necessary to be able to identify each monitoring device. In this embodiment, the local IP address “. (Period)” is changed to “_ (underscore)” (see FIG. 4A). ).
For example, when the monitoring information display device 9000 accesses the directory “/ 192_168_0_7 /” of the monitoring server device 1000 via the Internet 200, the monitoring server device 1000 corresponds to the reference directory 1512 “/ 192_168_0_7 /”. It is determined that the monitoring device indicated by the local IP address 1511 “192.168.0.7” has been accessed.

Next, the link table 1520 in FIG.
The link table 1520 includes a reference directory 1512, an acquisition URL 1521, and a link name 1522.
The reference directory 1512 is the same as the reference directory 1512 of the IP table 1510.

The acquisition URL 1521 represents a URL that the monitoring server apparatus 1000 requests to acquire a file when the reference directory 1512 is accessed.
For example, when the reference directory 1512 “/ 192 — 168 — 0 — 7 /” is accessed, the monitoring server device 1000 transmits the acquisition URL 1521 “http://192.168.0.7/” and, as a result, the file in the corresponding monitoring device. That is, the file 2610 “Index.html” shown in FIG.

The link name 1522 represents a name for the user to recognize the monitoring device represented by the reference directory 1512 and use it for access.
For example, the monitoring device indicated by the reference directory 1512 “/ 192 — 168 — 0 — 5 /” is named “1F lighting control device”.
The link name 1522 can be obtained by accessing the directory in each monitoring apparatus, the directory 2620 “/ AutoLink /” in FIG. That is, “http://192.168.0.5/AutoLink/Index.html” is transmitted, and as a result, the file 2621 “Index.html” shown in FIG. 4B is received. The contents of the file are the contents shown in FIG.

The monitoring server apparatus 1000 extracts the portion ““ 1F lighting control apparatus ”” representing the link name from the data of this file and sets it to the corresponding link name 1522.
<Operation>
Hereinafter, operations of the monitoring server device 1000 and the monitoring device 2000 of the facility monitoring system described above will be described with reference to FIGS.

Here, the operation of the equipment monitoring system will be described in two parts.
One is a process in which the monitoring server apparatus 1000 searches for a monitoring apparatus in the LAN 110 and creates an IP table 1510 and a link table 1520. The other is a display of the equipment status from the monitoring information display apparatus 9000. This is about the processing of the monitoring server apparatus 1000 and the monitoring apparatus 2000 when there is a request to be made.

<Monitoring device search processing>
First, a process in which the monitoring server apparatus 1000 searches for a monitoring apparatus in the LAN 110 and creates the IP table 1510 and the link table 1520 will be described with reference to FIG.
FIG. 6 is a flowchart showing processing for searching for a monitoring device in the LAN 110.
This processing is processing performed by the monitoring device detection unit 1400 of the monitoring server device 1000. Further, when to perform depends on the operation of this system, and is performed periodically, for example, when the monitoring server apparatus 1000 is turned on or at 24:00 on Sunday. In the case of 24 o'clock on Sunday, if a monitoring device is added / deleted by then, the setting is automatically made, and operation on the latest system is possible from Monday.

The local IP address of the monitoring server device 1000 is “192.168.0.100” and the subnet mask of the LAN 110 is “255.255.255.0”. These pieces of information are set in advance by the administrator of the system, and are monitored. The server apparatus 1000 is assumed to be stored in its own memory.
When the monitoring server device 1000 is turned on, it performs initial processing necessary for startup, and requests the monitoring device detection unit 1400 to detect the monitoring device.

The monitoring device detection unit 1400 that has received the request, except for the local IP address “192.168.0.100” of its own device, “192.168.0.1”, “192.168.0.2”, “192.168.0.3” to “192.168.0.254” The following two processes are performed for all 253 local IP addresses (step S100).
One is a search process for searching whether there is an assigned monitoring apparatus, and if there is, a search process for registering the monitoring apparatus in the table, and a name acquisition process for acquiring the name of the registered monitoring apparatus. .

<Search process>
First, it is determined whether or not the local IP address to be searched is the local IP address “192.168.0.100” of the own device. If the local IP address is that of the own device (step S110: Y), the next local IP address is searched. .
If it is not the device itself (step S110: N), it is determined whether or not it has been registered (step S120). Specifically, it is searched whether or not the current search target is registered in the local IP address 1511 of the IP table 1510 (see FIG. 3A).

If registered (step S120: Y), a <name acquisition process> described later is performed in order to obtain the latest name in consideration of a change in the name.
If it is not registered (step S120: N), it is determined whether there is a device connected to the LAN 110 (step S130). This determination is made by issuing a ping command and determining that some device is connected if the ping command is completed normally, and determining that the device is not connected if the ping command is not completed normally.

  Here, the ping command is a network inspection command using Internet Control Message Protocol (ICMP), and confirms network communication. If this command is executed normally, network communication has been confirmed. Specifically, for the device to be confirmed, here, an IP packet is issued to the local IP address to be searched, and if there is a reply that it has arrived, the ping command is normally terminated.

If the ping command does not end normally (step S130: N), it is determined that the device is not connected, and the next local IP address is searched (step S100).
If it is determined that the ping command is normally completed and some device is connected (step S130: Y), it is determined whether or not the device functions as an HTTP server, that is, whether or not it has a Web service function. (Step S140). This determination is made by issuing a command for connecting to the server, for example, a connect command, and if it can be connected normally, it is determined that it has an HTTP server function, and if it cannot be connected, it does not have an HTTP server function. to decide.

This connect command is used to connect to the server by designating the server IP address, port number, etc., and designates the HTTP service port 80 or the HTTPS (HyperText Transfer Protocol Security) service port 443 as the port number.
When it is determined that the device does not function as an HTTP server (step S130: N), the next local IP address is searched (step S100).

If it is determined that the device functions as an HTTP server (step S130: Y), it is registered in the IP table 1510 and the link table 1520.
Specifically, the local IP address to be searched is set in the local IP address 1511 of the IP table 1510, and “. (Period)” of the local IP address is set in the reference directory 1512 by “_ (underscore). ) "Is set, and the corresponding directory is created.

In addition, the same directory as the reference directory 1512 of the IP table 1510 is set in the reference directory 1512 of the link table 1520, and “http: //” is set in the acquisition URL 1521 before the local IP address that is the search target. A URL is created and set by adding “/” later.
For example, when the local IP address to be searched is “192.168.0.1”, the local IP address 1511 of the IP table 1510 is “192.168.0.1”, the reference directory 1512 is “/ 192_168_0_1 /”, and the acquisition URL 1521 is “http: //192.168.0.1/ ”is set.

<Name acquisition process>
Next, a name acquisition process for acquiring the name of the monitoring apparatus having the local IP address 1511 of the IP table 1510 will be described.
It is assumed that the name is recorded in advance in a predetermined file in the monitoring device, and the file is “/AutoLink/Index.html” (see FIG. 4B and FIG. 5).

The monitoring device detection unit 1400 uses the acquisition URL 1521 of the link table 1520 to request a file containing a name (step S160). If the file is successfully acquired (step S160: Y), the received name is linked. The link name 1522 of the table 1520 is set (step S170).
For example, when the name of the monitoring device whose local IP address 1511 is “192.168.0.7” is acquired, “AutoLink /” is added after the acquisition URL 1521 “http://192.168.0.7/” and “http: // Request as “192.168.0.7/AutoLink/”.

The “1F lighting control device” is extracted from the contents of the returned file “CONTROLNAME =“ 1F lighting control device ””, and the reference directory 1512 of the link table 1520 is set to the link name 1522 corresponding to “/ 192_168_0_7 /”. (See FIG. 3B and FIG. 5).
On the other hand, if the file acquisition fails (step S160: N), a name for identifying the monitoring device is created and set to the link name 1522 (step S180).

The name created here only needs to be able to identify the monitoring device.
In this embodiment, it is created using a host address. In the case of this embodiment, it is the last digit of the local IP address. For example, the link name 1522 of the monitoring device whose local IP address 1511 is “192.168.0.1” is “monitoring device 1” (see FIGS. 3A and 3B).
When searching for all 253 local IP addresses “192.168.0.1” to “192.168.0.254” other than its own device is finished, it is assumed that termination processing or the like is performed as necessary.

<Equipment status display processing>
Next, processing of the monitoring server device 1000 and the monitoring device 2000 when there is a request for displaying the equipment status from the monitoring information display device 9000 will be described with reference to FIGS.
FIG. 7 is a flowchart showing processing of the monitoring information display device 9000, the monitoring server device 1000, and the monitoring device 2000.

In this example, a case where the equipment status of the monitoring device 2000 is displayed will be described.
First, a user makes a display request from the monitoring information display device 9000 in order to confirm the facility status of a building (step S200).
Specifically, the monitoring information display device 9000 issues a request for the URL “http://133.254.7.211/” (step S201).

  This request reaches the router 5000 whose global IP address is “133.254.7.211”, and the router 5000 receiving the request transmits the received request to the monitoring server apparatus 1000. In the present embodiment, it is assumed that the router 5000 is set in advance to transmit a request to the monitoring server apparatus 1000. Note that the monitoring server device 1000 may have a router function.

The monitoring server apparatus 1000 that has received the request via the network communication unit 1100 passes the request to the Web service processing unit 1200.
Receiving the request, the Web service processing unit 1200 creates an HTML file for displaying a list of monitoring devices in the LAN 110 (step S300), and returns it to the monitoring information display device 9000 (step S301).

  When creating the HTML file to be returned, the Web service processing unit 1200 refers to the link table 1520 stored in the correspondence information storage unit 1500 (see FIG. 3B). Specifically, an HTML file that can display the name of the device that stores the facility status in the LAN 110, that is, the name of the monitoring device 2000 or the like that is the link name 1522, and the name of the own monitoring server device 1000 is created. . The displayed device name is linked to a directory in the own device.

FIG. 8A shows an example of an HTML file created by the monitoring server device, and FIG. 8B shows an example of a screen displaying the HTML file.
In the HTML file 1210, the link name 1522 of the monitoring device and the reference directory 1512 are associated with each other.
The monitoring information display device 9000 that has received the HTML file displays the received HTML file (see FIG. 8B: screen 9010).

The user clicks on the equipment status to be viewed from the screen 9010 displayed on the monitoring information display device 9000 (step S210). In this embodiment, it is assumed that “1F lighting control device” is selected.
The monitoring information display device 9000 that has detected that “1F lighting control device” has been selected from the screen 9010 refers to the global IP address “133.254.7.211” of the router 5000 associated with “1F lighting control device”. The directory “/ 192_168_0_5 /” is connected to create a URL “http://133.254.7.211/192_168_0_5/” and request it (step S211).

The router 5000 that has received the request transmits the request to the monitoring server apparatus 1000, and the received monitoring server apparatus 1000 passes the request to the Web service processing unit 1200.
Upon receiving the request, the Web service processing unit 1200 searches whether the directory part “/ 192_168_0_5 /” in the request “http://133.254.7.211/192_168_0_5/” is registered in the reference directory 1512 of the link table 1520.

If registered, the directory part is passed to the monitoring information file acquisition unit 1300 to request acquisition of the file. The presence in the reference directory 1512 indicates that a necessary file does not exist in the own device but exists in any of the monitoring devices 2000 and the like.
Upon receiving the request, the monitoring information file acquisition unit 1300 performs proxy processing as a request to the acquisition URL 1521 corresponding to the received directory. That is, the monitoring server apparatus 1000 makes a request (step S310, step S311). That is, a request for the acquisition URL “http://192.168.0.5” corresponding to the reference directory 1512 “/ 192 — 168 — 0 — 5 /” of the link table 1520 is issued.

The Web service processing unit 2200 of the monitoring device 2000 that has received the request via the network communication unit 2100 creates an HTML file to be returned based on the information stored in the monitoring information storage unit 2600 and returns the request (step) S400, step S401).
FIG. 9A shows an example of an HTML file created by the monitoring apparatus, and FIG. 9B shows an example of a screen displaying the HTML file.

The monitoring information file acquisition unit 1300 that has received the HTML file 1220 from the monitoring device 2000 performs processing or the like if necessary, and sends it back to the monitoring information display device 9000 (steps S320 and S321).
The monitoring information display device 9000 that has received the HTML file displays the received HTML file (see step S220, FIG. 9B: screen 9020).

In this example, it is assumed that processing is not performed and the monitoring information display device 9000 is returned.
As described above, in step S310, the Web service processing unit 1200 that has received the request searches whether the directory portion in the request is registered in the reference directory 1512 of the link table 1520. The directory part is passed to the monitoring information file acquisition unit 1300 to request acquisition of the file. If the file is not registered, the file is acquired from the directory in the own apparatus.

  For example, when the request is “http://133.254.7.211/192_168_0_100/”, the directory part “/ 192_168_0_100 /” in the request is not registered in the reference directory 1512 of the link table 1520. This is because the monitoring server device, that is, its own device. In this case, a reply file is created on the basis of a file at a predetermined location in the own apparatus and returned.

For example, a file 1610 “/192_168_0_100/Index.html” in the own apparatus as shown in FIG.
<Embodiment 2>
<Overview>
In the first embodiment, as described with reference to FIG. 7, the user makes a display request from the monitoring information display device 9000 to confirm the facility status of the building (step S200), and the monitoring information display device 9000. Issue a request for the URL “http://133.254.7.211/” (step S201), the monitoring server device 1000 creates an HTML file for displaying a list of monitoring devices in the LAN 110, and monitors them. It returns to the information display device 9000 (step S301).

In the present embodiment, instead of an HTML file for displaying a list of monitoring devices in the LAN 110, a reply file that displays a plurality of information in a plurality of independent windows using an HTML frame is created. Is.
Here, only the difference between this embodiment and Embodiment 1 is demonstrated.
<Configuration>
The configuration of each device is basically the same as the configuration in the first embodiment, except for the following points.

The Web service processing unit 1200 creates an HTML file using a frame, and the monitoring device detection unit 1400 acquires information indicating the presence or absence of frame content in the same manner as the link name 1522 is acquired, and sets the information in the IP table 1510. The point to do is different.
<Data>
Hereinafter, data used in the present embodiment will be described with reference to FIG.

The only difference from the data used in the first embodiment is the IP table 1510 (see FIG. 3A) stored in the correspondence information storage unit 1500, and the others are the same.
FIG. 10 is a diagram illustrating a configuration example and contents example of an IP table according to the second embodiment.
The IP table 6000 includes a local IP address 1511, a reference directory, and frame content 6001.

The local IP address 1511 and the reference directory are the same as the IP table 1510 of the first embodiment.
The frame content 6001 indicates whether or not the monitoring device represented by the corresponding local IP address 1511 stores the content for the frame. “Present” indicates that it is stored, and “None” indicates that it is not stored.

In the present embodiment, the Web service processing unit 1200 determines whether to create an HTML file using a frame or an HTML file with only a link as in the first embodiment based on the frame content 6001.
In the present embodiment, if at least one of the monitoring devices stores content for a frame, an HTML file using the frame is created. However, for a monitoring device that does not store frame content, It is good also as not displaying.

In addition, the directory structure and the like of the monitoring server apparatus 1000 and each monitoring apparatus 2000 are different due to having the frame file.
FIG. 11A illustrates a configuration example of a directory included in the monitoring server apparatus 1000 according to the second embodiment, and FIG. 11B illustrates a configuration example of a directory included in the monitoring apparatus 2000 according to the second embodiment. It is.

FIG. 12 is a diagram showing an example of the contents of the file 6621 “/AutoLink/Index.html” shown in FIG.
In the monitoring server apparatus 1000, when the contents for frames are stored in each monitoring apparatus, a directory for frames is created under the directory representing each apparatus. For example, if the monitoring device with the IP address “192.168.0.5” has frame content, the directory is “/ 192_168_0_5 / ForFrame /”.

On the other hand, the monitoring apparatus 2000 has a frame file 6631 “Index.html” under the directory 2630 “ForFrame”.
Further, the file 6621 “/AutoLink/Index.html” describes information indicating the presence / absence of frame content. In the first embodiment, the file is a file in which the name of the device is described. In the present embodiment, the presence / absence of frame content is additionally described. For example, “CONTROLFRAME =“ present ”” (see FIG. 5).

<Operation>
Here, a method for acquiring the frame content 6001 of the IP table 6000 and the display operation of the HTML file using the frame will be described. Other operations are the same as those in the first embodiment.
First, in the present embodiment, the presence / absence of frame content is acquired together with the name in the <name acquisition process> of the first embodiment (see FIG. 6).

Specifically, in the monitoring device file “/AutoLink/Index.html”, in addition to the device name “CONTROLNAME =“ 1F lighting control device ””, presence / absence of frame content “CONTROLFRAME =“ present ”” or “ CONTROLFRAME = “None” ”is described (see FIG. 11B and FIG. 12).
The monitoring device detection unit 1400 uses the acquisition URL 1521 of the link table 1520 to request an AutoLink file (step S160). Frame content 6001 (see step S170).

  Specifically, when the content of the returned file is “CONTROLFRAME =“ Yes ””, “Yes” is set in the corresponding frame content 6001 of the IP table 6000, and the content of the returned file is “CONTROLFRAME =”. If “No” is set, “No” is set. Also, “None” is set when the file acquisition has failed (step S160: N) (see step S180).

Next, an HTML file display operation using a frame will be described.
Processing of the monitoring server device 1000 and the monitoring device 2000 when there is a request for displaying the equipment status from the monitoring information display device 9000 will be described with reference to FIGS. 13 and 14.
FIG. 13 is a flowchart showing processing of the monitoring information display device 9000, the monitoring server device 1000, and the monitoring device 2000.

FIG. 14A is an example of an HTML file created by the monitoring server device in the second embodiment, and FIG. 14B is an example of a screen displaying the HTML file.
In the case of the HTML shown in FIG. 14A, the screen shown in FIG. 14B can be displayed by requesting three files. Specifically, “/TopMenu.html”, “/ 192_168_0_5 / ForFrame /”, and “/ 192_168_0_5 / ForFrame /”.

Here, for convenience of explanation, a case where only the frame file of the monitoring device 2000 is displayed will be described.
First, the user issues a request “http://133.254.7.211/” from the monitoring information display device 9000 to confirm the facility status of the building (step S201) and makes a display request (step S200). .

The monitoring server apparatus 1000 that has received the request via the network communication unit 1100 passes the request to the Web service processing unit 1200, and the Web service processing unit 1200 that has received the request creates and returns an HTML file to be returned.
At the time of creation, the Web service processing unit 1200 refers to the frame content 6001 of the IP table 6000, and creates an HTML using the frame if there is even one “Yes” (see step S350, FIG. 14A). . It is assumed that the frame configuration is determined in advance.

In this example, the display screen is composed of three frames, and the menu screen “detailed screen of each monitoring device” and the equipment status of “1F lighting control device” and “2F lighting control device” are displayed (see FIG. 14 (b): see screen 9100).
An HTML file using the created frame is returned to the monitoring information display device 9000 (step S351).

For example, when the frame content 6001 of the monitoring device with the IP address “192.168.0.5” is “present”, the associated reference directories “/ 192_168_0_5 /” and “ForFrame /” are connected and displayed in the frame. The file “/ 192 — 168 — 0 — 5 / ForFrame /” is designated (see FIG. 14A).
The monitoring information display device 9000 that has received the HTML file interprets the received HTML file and requests the monitoring server device 1000 for a file to be displayed in the frame (step S250). Specifically, the global IP address “133.254.7.211” of the router 5000 and the frame content file “/ 192_168_0_5 / ForFrame /” are connected to create “http // 133.254.7.211 / 192_168_0_5 / ForFrame /” and request it. (Step S251).

  Upon receiving the request, the Web service processing unit 1200 of the monitoring server apparatus 1000 receives the acquisition URL “http: 133 //192.168.0.5 "and the next directory part" / ForFrame / "are connected and a request is issued (step S360, step S361).

The web service processing unit 2200 of the monitoring device 2000 that has received the request via the network communication unit 2100 returns “/ForFrame/Index.html” stored in the monitoring information storage unit 2600 (steps S450 and S451). ).
The monitoring information file acquisition unit 1300 that has received the HTML file 1220 from the monitoring device 2000 performs processing or the like if necessary, and sends it back to the monitoring information display device 9000 (steps S370 and S371).

The monitoring information display device 9000 that has received the HTML file displays the received frame HTML file (step S260).
In this way, request "http // 133.254.7.211 / 192_168_0_5 / ForFrame /", "http // 133.254.7.211 / TopMenu.html" and "http // 133.254.7.211 / 192_168_0_5 / ForFrame /" When three frames are displayed, a display screen 9100 of FIG.
<Embodiment 3>
<Overview>
In the first embodiment, as described in <Monitoring device search processing>, the monitoring device detection unit 1400 of the monitoring server device 1000 uses the subnet mask to ping all available local IP addresses. A command was issued to confirm the connection.

In the present embodiment, a connected device can be detected without searching with a ping command or the like.
This is because the monitoring server device 1000 of this embodiment has a function as a DHCP (Dynamic Host Configuration Protocol) server and assigns a local IP address to the accessed device.

Therefore, it is possible to know the device to which the IP address is assigned without searching with the ping command or the like. However, since the local IP address of the device is not always the same, the device is identified using a MAC (Media Access Control address) address that is a unique number for the Ethernet (registered trademark) card. To do.
Here, only the difference between this embodiment and Embodiment 1 is demonstrated.

<Configuration>
The configuration of each device is basically the same as the configuration in the first embodiment, except for the following points.
The detection method of the monitoring device detection unit 1400 of the monitoring server device 1000 is different. Further, as the detection method of the monitoring device detection unit 1400 is different, a difference is that a reference directory such as an IP table to be created is created based on the MAC address.

<Data>
The table used in this embodiment will be described below.
FIG. 15A is a diagram illustrating a configuration example and content example of the IP table of the third embodiment, and FIG. 15B is a diagram illustrating a configuration example and content example of the link table of the third embodiment.
The IP table 7000 in FIG. 15A includes a MAC address 7001, a local IP address 1511, a reference directory 7002, a use flag 7003, and a Web service 7004.

First, the MAC address 7001 is a number unique to the device. A device requesting an IP address requests the IP address by designating this number of the own device.
The local IP address 1511 is the same as that of the first embodiment.
Next, the reference directory 7002 is set by deleting “-(hyphen)” from the MAC address. For example, when the MAC address 7001 is “00-12-AB-57-87-23”, the reference directory 7002 is “/ 0012AB578723 /”.

The use flag 7003 indicates whether the address indicated by the local IP address 1511 is currently being used. When the use flag 7003 is “in use”, it indicates that the address indicated by the corresponding local IP address 1511 is used. When the use flag 7003 is “in use”, it indicates that the address is not used. ing.
This use flag is set to “unused” when it is recognized that the corresponding device is disconnected from the network. For example, there is a case where a monitoring device that is a DHCP client notifies that an IP address is to be released, or a case where there is no renewal request and the lease term has expired.

Web service 7004 indicates whether or not the device indicated by the corresponding MAC address 7001 has a Web service function. “Yes” indicates a device having a Web service function, and “No” indicates a device having no Web service function.
Next, the link table 7100 in FIG. 15B includes a reference directory 7002, an acquisition URL 1521, and a link name 1522.

The reference directory 7002 is the same as that of the IP table 7000, and the acquisition URL 1521 and the link name 1522 are the same as those of the link table of the first embodiment.
<Operation>
Here, the process of the present embodiment corresponding to the <monitoring device search process> of the first embodiment will be described with reference to FIG.

FIG. 16 is a flowchart illustrating processing for searching for a monitoring device in the LAN 110 according to the third embodiment.
This processing is processing performed by the monitoring device detection unit 1400 of the monitoring server device 1000. In the first embodiment, this processing is executed when the monitoring server device is turned on or periodically. In this embodiment, this processing is performed every time a local IP address is requested.

As in the first embodiment, the local IP address of the monitoring server device 1000 is “192.168.0.100”, and the subnet mask of the LAN 110 is “255.255.255.0”. It is set by the administrator, and the monitoring server apparatus 1000 is assumed to be stored in the memory of the own apparatus.
When the local IP address is requested from the device in the LAN 110 to the monitoring server device 1000 by requesting the local IP address, the monitoring server device 1000 sends the designated MAC to the monitoring device detection unit 1400. Pass the address and ask for it.

The monitoring device detection unit 1400 that has received the request refers to the MAC address 7001 of the IP table 7000 and searches whether it has already been registered (step S700).
If not registered (step S700: N), a local IP address is allocated and registered in the IP table 7000 (step S710). It is assumed that the local IP address assigned here is assigned with a use flag 7003 that is not “in use”.

Specifically, the received MAC address, the assigned local IP address, and the received MAC address obtained by deleting “-(hyphen)” are the MAC address 7001 and local IP address 1511 of the IP table 7000, respectively. To the reference directory 7002. The use flag 7003 is “in use”.
Thereafter, the assigned IP address is returned to the requesting device.

  Next, it is determined whether or not the apparatus functions as an HTTP server, that is, whether or not the apparatus has a Web service function (step S720). This determination is made in the same way as in the first embodiment by issuing a command for connecting to the server, for example, a connect command, and if it can be normally connected, it is determined that it has an HTTP server function. Judge that it has no function.

If it is determined that the device does not have an HTTP server function (step S720: N), “None” is set in the Web service 7004 of the IP table 7000 (step S750).
If it is determined that the device has the HTTP server function (step S720: Y), “Yes” is set in the Web service 7004 of the IP table 7000 (step S730), and the device is stored in the link table 7100. sign up.

Specifically, the same reference directory 7002 of the IP table 7000 is set in the reference directory 7002 of the link table 7100, and “http: //” is placed in front of the assigned local IP address in the acquisition URL 1521. Then, a URL is created and set by adding “/” later.
Next, the name of the monitoring device having the local IP address 1511 of the IP table 7000 is acquired and set to the link name 1522 (step S800).

This process is the same as the <name acquisition process> in the first embodiment.
When a new MAC address is registered, restart processing or the like is performed as necessary.
On the other hand, referring to the MAC address 7001 of the IP table 7000, the monitoring device detection unit 1400 that has already been registered (step S700: Y) refers to the use flag 7003 corresponding to the corresponding MAC address, and “ If it is “in use” (step S760: in use), the process ends.

If it is “unused” (step S760: unused), the local IP address is reassigned and reset to the local IP address 1511 of the IP table 7000 (step S770). The use flag 7003 is “in use”. Thereafter, the reassigned IP address is returned to the requesting device.
Next, it is determined whether or not the apparatus functions as an HTTP server, that is, whether or not the apparatus has a Web service function (step S780). This determination is made with reference to the corresponding Web service 7004 in the IP table 7000.

If the apparatus is “No” for the Web service 7004 (step S780: No), the process ends.
When the Web service 7004 is “present” (step S780: present), the apparatus resets the URL created based on the new local IP address in the acquisition URL 1521 of the link table 7100 (step S780).

Next, the name of the monitoring device having the local IP address 1511 in the IP table 7000 is acquired again and set to the link name 1522 (step S800).
When the acquisition URL 1521 and the like are registered, restart processing or the like is performed as necessary.
<Supplement>
As mentioned above, although the equipment monitoring system concerning the present invention was explained based on the embodiment, this system can also be partially changed, and of course the present invention is not limited to the above-mentioned embodiment. That is,
(1) In the first embodiment, the ping command is used when detecting the IP address of the device connected to the network, but it may be confirmed by another protocol such as SNMP (Simple Network Management Protocol).

In the first embodiment, after detecting the connected device, it is further confirmed whether or not it has a WEB service function by returning to the HTTP protocol. However, it is connected to the network only by returning to the HTTP protocol. It is good also as detecting the apparatus which is.
(2) In the embodiment, the number of monitoring server devices is one, but a plurality of devices may be disclosed on the Internet.
In this case, there is an advantage that backup can be performed in the case where one unit breaks down by automatically searching for monitoring devices and creating tables.
(3) The frame content in the second embodiment can be reduced and enlarged in accordance with the display screen, or an internal object such as a JAVA (registered trademark) applet may be prepared.

In addition, when displaying the equipment status of a monitoring device that does not have content for a frame, only a link may be prepared.
(4) The function performed by the monitoring information file acquisition unit 1300 of the embodiment may be performed using the function of the provided Web service server.
For example, a reference directory and an acquisition URL are linked using a so-called reverse proxy function. In this case, after creating the IP table and the link table, it is necessary to perform linking with a ProxyPassReverse command or the like. This setting is automatically performed with reference to each table.
(5) In the embodiment, the link name or the like is returned in response to the URL “/ AutoLink /”, but is acquired by XML (Extensible Markup Language) or SOAP (Simple Object Access Protocol). It is good to do.

For example, data is transmitted and received between computers using XML, and a name is acquired, or data and a service of a monitoring device are called using SOAP, and a name is acquired.
(6) In the embodiment, each of the monitoring server device and the monitoring device has a Web server function, but the monitoring device does not have a Web server function, and at least receives data in response to a request from the monitoring server device. It may have a function of transmitting. In this case, the monitoring server device and the monitoring device exchange data using FTP (File Transfer Protocol) or the like.
(7) A program for causing the CPU to execute each control process (see FIG. 6 and the like) for realizing each function of the facility monitoring system described in the embodiment is recorded on a recording medium or via various communication paths. Can be distributed and distributed. Such a recording medium includes an IC card, an optical disk, a flexible disk, a ROM, a flash memory, and the like. The distributed and distributed program is used by being stored in a memory or the like that can be read by the CPU in the device, and each function described in the embodiment is realized by the CPU executing the program.

It is a figure which shows the structural example of the equipment monitoring system which concerns on embodiment of this invention. It is a functional block diagram of the monitoring server apparatus 1000 and the monitoring apparatus 2000 concerning this invention. FIG. 3A is a diagram illustrating a configuration and content example of the IP table 1510, and FIG. 3B is a diagram illustrating a configuration and content example of the link table 1520. 4A is a diagram illustrating a configuration example of a directory included in the monitoring server device 1000, and FIG. 4B is a diagram illustrating a configuration example of a directory included in the monitoring device 2000 or the like. It is a figure which shows the example of the content of file 2621 "/ AutoLink / Index / html" shown in FIG.4 (b). 4 is a flowchart showing processing for searching for a monitoring device in a LAN 110; 5 is a flowchart showing processing of a monitoring information display device 9000, a monitoring server device 1000, and a monitoring device 2000. FIG. 8A is a diagram illustrating an example of an HTML file created by the monitoring server device, and FIG. 8B is a diagram illustrating an example of a screen displaying the HTML file. FIG. 9A is a diagram illustrating an example of an HTML file created by the monitoring apparatus, and FIG. 9B is a diagram illustrating an example of a screen displaying the HTML file. It is a figure which shows the structural example and content example of an IP table of Embodiment 2. FIG. 11A illustrates a configuration example of a directory included in the monitoring server apparatus 1000 according to the second embodiment, and FIG. 11B illustrates a configuration example of a directory included in the monitoring apparatus 2000 according to the second embodiment. It is. It is a figure which shows the example of the content of file 6621 "/AutoLink/Index.html" shown in FIG.11 (b). 5 is a flowchart showing processing of a monitoring information display device 9000, a monitoring server device 1000, and a monitoring device 2000. FIG. 14A is an example of an HTML file created by the monitoring server device in the second embodiment, and FIG. 14B is an example of a screen displaying the HTML file. FIG. 15A is a diagram illustrating a configuration example and content example of the IP table of the third embodiment, and FIG. 15B is a diagram illustrating a configuration example and content example of the link table of the third embodiment. 10 is a flowchart illustrating processing for searching for a monitoring device in a LAN 110 according to the third embodiment.

Explanation of symbols

1000 Monitoring server device 1100 Network communication unit 1200 Service processing unit 1210 1220 HTML file 1300 Monitoring information file acquisition unit 1400 Monitoring device detection unit 1500 Corresponding information storage unit 1510 6000 7000 IP table 1511 Local IP address 1512 7002 Reference directory 1520 7100 Link table 1521 Acquisition URL
1522 Link name 1600 Monitoring information storage unit 2000 Monitoring device 2100 Network communication unit 2200 Service processing unit 2600 Monitoring information storage unit 2610 2621 File 2620 Directory 3000 4000 Monitoring device 5000 Router 6001 Frame content 6621 File 6631 Frame file 7001 MAC address 7003 Usage flag 7004 Web service 9000 Monitoring information display device 9010 9020 9100 Display screen

Claims (9)

A facility monitoring system comprising a plurality of monitoring devices each having a web server function and connected to each other via a network,
Among the monitoring devices, the monitoring device having communication means for communicating with the outside of the facility monitoring system,
Obtaining means for obtaining a local IP address of another monitoring device connected to the network;
Identification information for identifying the other connected monitoring device, information based on the local IP address acquired by the acquisition means, and file information indicating a predetermined file in the other monitoring device; Storage means for associating and storing
When a request for information is received from the outside of the equipment monitoring system by specifying the identification information, reply data is created using a predetermined file indicated by the file information stored in association with the identification information. A facility monitoring system comprising a replying means for replying. The monitoring device having a communication unit that communicates with the outside of the facility monitoring system further includes a transmission unit that transmits identification information of the other monitoring device to the outside of the facility monitoring system,
When the reply unit receives a request for designating one or more pieces of identification information among the identification information transmitted by the transmission unit, the reply unit displays a predetermined file indicated by the file information stored in association with the identification information. The equipment monitoring system according to claim 1, wherein reply data is created and sent back. The equipment monitoring system according to claim 2, wherein the identification information transmitted by the transmission unit is information representing a name of the other monitoring device. The facility monitoring system according to claim 2, wherein the transmission unit further transmits information for identifying a specific file in the other monitoring device. The predetermined file in the other monitoring device includes information on equipment connected to the other monitoring device,
The equipment monitoring system according to claim 1, wherein the reply data created by the reply unit is information described in a Web page description language created using the predetermined file. The local IP address acquired by the acquiring unit is a local IP address when an IP packet is transmitted to a certain local IP address and the IP packet is normally received. Equipment monitoring system. The monitoring device having a communication unit that communicates with the outside of the facility monitoring system further includes a granting unit that gives a local IP address to another monitoring device connected to the network,
The equipment monitoring system according to claim 1, wherein the local IP address acquired by the acquiring unit is a local IP address assigned to another monitoring device by the assigning unit. A monitoring device that is used in an equipment monitoring system that includes a plurality of monitoring devices each having a Web server function and connected to each other via a network,
The monitoring device includes communication means for communicating with the outside of the facility monitoring system;
Obtaining means for obtaining a local IP address of another monitoring device connected to the network;
Identification information for identifying the other connected monitoring device, information based on the local IP address acquired by the acquisition means, and file information indicating a predetermined file in the other monitoring device; Storage means for associating and storing
When a request for information is received from the outside of the equipment monitoring system by specifying the identification information, reply data is created using a predetermined file indicated by the file information stored in association with the identification information. And a reply means for replying. A computer program for causing a monitoring device used in an equipment monitoring system having a plurality of monitoring devices each having a Web server function and connected to each other to perform monitoring processing,
The monitoring device communicates with the outside of the facility monitoring system;
Obtaining a local IP address of another monitoring device connected to the network;
Identification information for identifying the other connected monitoring device, information based on the local IP address acquired in the acquiring step, and file information indicating a predetermined file in the other monitoring device; Storing in the memory in association with each other,
When a request for information is received from the outside of the equipment monitoring system by specifying the identification information, reply data is created using a predetermined file indicated by the file information stored in association with the identification information. A computer program comprising a reply step for replying.

Images