JP2010141826A - Equipment integrated management apparatus, equipment integrated management program, equipment connection apparatus, equipment connection program, equipment integrated management system, and equipment integrated management method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To effectively manage a plurality of pieces of equipment of different models in an integrated manner while mitigating an operating load. <P>SOLUTION: An equipment integrated management apparatus 200 transmits data as a URL-type instruction 202 to a gateway 300 which communicatively connects with a plurality of monitoring object equipments 400, wherein the data includes an equipment ID for identifying a specific monitoring object equipment 400 and a processing ID for identifying the processing to be executed by the specific monitoring object equipment 400 as execution processing, in addition to a URL in which the host name of the gateway 300 is set. The gateway 300 receives the URL-type instruction 202 transmitted by the equipment integrated management apparatus 200, and transmits API data 301 for making the specific monitoring object equipment 400 execute the execution processing based on the received URL-type instruction 202 to the specific monitoring object equipment 400 to make the specific monitoring object equipment 400 execute the execution processing. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to, for example, a device integration management device, a device integration management program, a device connection device, a device connection program, a device integration management system, and a device integration management method that collectively manage a plurality of devices of different models.

Conventionally, security equipment for office buildings (entrance / exit management devices, video monitoring devices, etc.) and building equipment (air conditioning management devices, lighting equipment, elevators, crime prevention / disaster prevention systems, etc.) have been constructed in separate LANs in the building. Have been independently operated and managed by device type.
In recent years, security devices (for example, entrance / exit management devices and video monitoring devices), security devices and building equipment devices, security devices and information systems have been linked, and buildings have been linked via an IP network such as the Internet, Increasing cases of integrating and managing devices. In such a cooperation / integration system, the system configuration becomes large-scale, and there are many device types as constituent elements. For this reason, device configuration management (connection relationship between devices), device profile (ID, network communication information, model, model number, firmware version, etc.) management, and monitoring / control of each device are improved. Is required. For example, there is a demand for device configuration, automatic acquisition of information on each device, remote monitoring / control using a network, etc. at the time of new installation / relocation of devices.

  The following Patent Documents 1 and 2 are known as conventional examples for notifying / acquiring change of configuration information of a communication device connected to a network.

Japanese Patent Application Laid-Open No. 2004-228561 discloses a method for managing the hierarchies of device types and the like by dividing the interface ID portion of the IPv6 address into categories such as device type, product type, and product serial number.
However, the method of Patent Document 1 is a method of giving a special meaning to the bit part of the address for communication. If there is no tool for interpreting this meaning, the address displayed in hexadecimal display is compared with the above definition. The general operation manager has a problem that the operation load is high.

Japanese Patent Application Laid-Open No. 2004-228561 performs configuration management on the private network side in a configuration in which a private network is connected to the Internet through a gateway. In other words, when the configuration of the private network connected to the Internet is changed by the gateway, the gateway detects this, and notifies the change information by notifying the server on the Internet of the change information.
However, the detection in Patent Document 2 is only change detection limited to network information such as addition of a new address due to addition of a connection device to the private network or change of the address of a device connected to the private network. In other words, management of detailed information (model name, etc.) of devices connected to the private network, configuration management of devices not directly connected to the private network, and active monitoring / control of devices from the server side are not possible. There was a problem.
In addition, functions executed on the device side (API: Application Program Interface) vary from model to model, and functions that monitor and control security devices and building devices are provided as APIs on certain devices, but are not supported on other models. There was a problem that it was difficult to integrate device management by a unified operation (action) that the integrated operation management device wanted to perform.
In addition, when you want to know the operating status of peripheral devices attached to devices that can communicate with IP, there are many peripheral devices connected by a method other than IP network connection. It is necessary to monitor and control the peripheral device by managing the ID of the peripheral device, the ID of the parent device, and the address information of the parent device, and communicating with the parent device. In such device configuration management, there is a problem that it is difficult to uniformly manage a plurality of devices of different models because the management method is different for each model.
JP 2007-288234 A JP 2006-203731 A

  For example, an object of the present invention is to efficiently integrate and manage a plurality of devices of different models while reducing the operation load.

  The device integrated management apparatus according to the present invention includes a device ID for identifying a specific monitoring target device and a specific monitoring target device in a URL (Uniform Resource Locator) in which addresses of device connection devices that communicate with and connect to a plurality of monitoring target devices are set. A URL type command generation unit that generates data with a process ID that identifies a process to be executed as an execution process as a URL type command using a CPU (Central Processing Unit), and the URL type command generation unit By transmitting a URL type command to the device connection device using a communication device, an execution command for causing the specific monitoring target device to execute the execution process is transmitted from the device connection device to the specific monitoring target device. URL type that causes the specific monitored device to execute the execution process And a decree transmitting unit.

  According to the present invention, for example, a plurality of devices of different models can be controlled using URL-type commands and efficiently integrated and managed.

Embodiment 1 FIG.
A system that integrates and manages a plurality of devices of different models using URL-type commands will be described.

FIG. 1 is a device configuration diagram of a device integrated management system 100 according to the first embodiment.
A device configuration of the device integrated management system 100 according to the first embodiment will be described below with reference to FIG.

The device integrated management system 100 includes a device integrated management device 200, a gateway 300 (an example of a device connection device), a plurality of devices to be monitored 400 (an electric lock control panel 410, a network monitoring camera 420, a card reader 491, etc.), and a device integrated management. A display device 110 is provided.
The device integrated management apparatus 200 performs IP (Internet Protocol) communication with the gateway 300 installed in the building 103 via the Internet 101 (an example of a wide area network), and connects a plurality of monitoring target devices 400 installed in the building 103. Integrated management. As a wide area network that replaces the Internet 101, for example, a VPN (Virtual Private Network) can be cited.
The monitoring target device 400 is classified into an IP device 401 and a peripheral device 402, and the IP device 401 (electric lock control panel 410, network monitoring camera 420, etc.) is a local area network (hereinafter, “LAN102”) provided in the building 103. The peripheral device 402 (card reader 491, electric lock door 492, etc.) is connected to the IP device 401 by contact connection, serial connection, or the like, and is connected to the gateway 300 to perform IP communication. To communicate with the IP device 401.
The gateway 300 is installed in the building 103, and performs IP communication with the device integrated management apparatus 200 via the Internet 101 and IP communication with each IP device 401 via the LAN.

  Each data (request data 201, response data 302 and the like described later) via the Internet 101 and the LAN 102 is set in an IP packet and transmitted / received.

In general, as shown in FIG. 1, a large number of devices (monitored devices 400) are installed in the building 103. Each of these devices provides specific functions (profile setting function, profile output function, time setting function, internal time output function, etc.) to other devices via the network. The device integrated management apparatus 200 can manage each device by using a function provided by each device.
However, an input / output interface (hereinafter referred to as “API (Application Program Interface)”) for using the function of each device is different for each model. For example, even if the profile output function is the same, the API is different between the electric lock control panel 410 and the network monitoring camera 420.
Further, the monitoring target device 400 includes many IP devices 401 that are not connected to the network.

The device integrated management apparatus 200 according to the first embodiment performs integrated management of these various types of monitoring target devices 400 via the gateway 300 using a URL-type command 202 (URL: Uniform Resource Locator) described later.
Details of the device integration management method using the URL type command 202 will be described later.

The electric lock control panel 410 controls the card reader 491 and the electric lock door 492, and the electric lock control panel 410, the card reader 491 and the electric lock door 492 constitute an entrance / exit management system.
The network monitoring camera 420 is installed in various places of the building 103, and transmits the captured video to a specific device (for example, the video monitoring display device 440) via the LAN.
The monitoring recorder 430 is connected to analog monitoring cameras 493 installed in various places of the building 103 by a coaxial (NTSC) cable or the like, and records images captured by the analog monitoring camera 493 on a storage medium.
The video monitoring display device 440 displays the video captured by the network monitoring camera 420 and the video recorded on the monitoring recorder 430.
The air conditioning control device 450 adjusts the air conditioning by controlling the air conditioning unit 494 based on the control command received via the LAN 102.
The lighting control device 460 controls the lighting unit 495 based on a control command received via the LAN 102 to switch lighting on / off, adjust illuminance, and the like.

The electric lock control panel 410, the network monitoring camera 420, the monitoring recorder 430, the video monitoring display device 440, the air conditioning control device 450, and the lighting control device 460 are examples of the IP device 401 (monitoring target device 400). The lock door 492, the analog monitoring camera 493, the air conditioning unit 494, and the lighting unit 495 are examples of the peripheral device 402 (monitored device 400).
In addition, the elevator system, the crime prevention system, and the devices constituting the crime prevention system may be cited as the monitoring target device 400.

  The device integrated management display device 110 is a terminal device that acquires management information of each monitoring target device 400 from the device integrated management device 200 and displays it.

A flow of processing when an administrator operates the device integrated management display device 110 to manage profile information of a specific monitoring target device 400 (may be plural or all) will be described.
The administrator designates a specific monitoring target device 400 and inputs a request for profile information to the device integrated management display device 110. The device integrated management display device 110 transmits the display content request data 111 via the Internet 101 to the device integrated management device. 200.
The device integrated management apparatus 200 transmits request data 201 (including the URL type command 202) for requesting profile information of the monitoring target device 400 to the gateway 300 via the Internet 101.
The gateway 300 generates API data 301 corresponding to the API of the monitoring target device 400 based on the URL type command 202 and transmits the generated API data 301 to the monitoring target device 400 via the LAN 102.
The monitoring target device 400 processes the API data 301 to acquire profile information from the storage unit, and transmits the acquired profile information as execution result data 409 to the gateway 300 via the LAN 102.
The gateway 300 generates response data 302 representing profile information in a predetermined format based on the execution result data 409, and transmits the generated response data 302 to the device integrated management apparatus 200 via the Internet 101.
The device integrated management apparatus 200 generates display content 203 indicating the profile information of the monitoring target device 400 based on the response data 302, and transmits the generated display content 203 to the device integrated management display device 110 via the Internet 101. .
The device integrated management display device 110 displays the display content 203, and the administrator confirms the display content 203 displayed on the device integrated management display device 110 and manages the monitored device 400.

  The communication connection from the device integration management display device 110 to the device integration management device 200 may be security-managed by known means such as user authentication and connection restriction by a source address.

  Hereinafter, the processing of the device integration management apparatus 200 and the gateway 300 will be mainly described.

FIG. 2 is a sequence diagram illustrating a processing flow of the device integrated management system 100 according to the first embodiment.
An outline of processing when the device integrated management apparatus 200 acquires device information (for example, a profile) from each monitored device 400 will be described below with reference to FIG.

The device integrated management apparatus 200 requests the device configuration information indicating the device configuration of each monitoring target device 400 from the gateway 300. The device configuration information includes a device ID that individually identifies the monitoring target device 400 (S110).
The gateway 300 manages the device configuration information as will be described later, and responds to the device configuration management device 200 when receiving the request (S120).
The device integrated management apparatus 200 that has acquired the device configuration information specifies the device ID of the monitoring target device 400 for which device information is to be acquired based on the device configuration information, and the device information of the monitoring target device 400 that is identified by the specified device ID. Is requested to the gateway 300 (S130).
The gateway 300 specifies the model of the monitoring target device 400 identified by the device ID, and requests device information from the monitoring target device 400 according to the API of the specified model (S140).
The monitoring target device 400 returns device information to the gateway 300 (S150).
The gateway 300 responds to the device integrated management apparatus 200 by representing the device information returned from the monitoring target device 400 in a specific format (S160).

In S110, information (host name or IP address) for communicating with the gateway 300 is set, tool, or installation notification from the gateway 300 (for example, notification from the newly installed gateway 300). 200 is stored. This notification means can be easily performed by those skilled in the art using known techniques.
In S160, the gateway 300 converts the response of the monitoring target device 400 into a data format that can be interpreted by the device integrated management device 200 (for example, XML (XML: extensible Markup Language)), and the converted data is converted into the device integrated management device 200. Respond to.

Hereinafter, processing (S110 to S120) in which the device integrated management apparatus 200 acquires device configuration information is referred to as “initial processing”, and processing in which the device integrated management apparatus 200 controls the monitoring target device 400 via the gateway 300 (S130 to S120). S160) is referred to as “management processing”.
Details of the initial process and the management process will be described later.

FIG. 3 is a diagram illustrating an example of hardware resources of the device integrated management system 100 according to the first embodiment.
In FIG. 3, a device integrated management device 200, a gateway 300, a monitored device 400, and a device integrated management display device 110 include a CPU 911 (Central Processing Unit, a central processing unit, a processing unit, a computing unit, a microprocessor that executes a program. , Also referred to as a microcomputer or a processor). The CPU 911 is connected to the ROM 913, the RAM 914, the communication board 915, and the magnetic disk device 920 via the bus 912, and controls these hardware devices. Furthermore, the device integration management device 200 and the device integration management display device 110 include input / output devices such as a display device 901, a keyboard 902, and a mouse 903, and the CPU 911 also controls these input / output devices. Instead of the magnetic disk device 920, another storage device (for example, a semiconductor memory such as a RAM or a flash memory) may be used.
The RAM 914 is an example of a volatile memory. The storage medium of the ROM 913 and the magnetic disk device 920 is an example of a nonvolatile memory. These are examples of a storage device, a storage device, or a storage unit. A storage device in which input data is stored is an example of an input device, an input device, or an input unit, and a storage device in which output data is stored is an example of an output device, an output device, or an output unit.
The communication board 915 is an example of an input / output device, an input / output device, or an input / output unit.

  The communication board 915 is wired or wirelessly connected to a communication network such as a LAN 102, the Internet 101, a WAN (wide area network) such as ISDN, and a telephone line.

  The magnetic disk device 920 stores an OS 921 (operating system), a program group 923, and a file group 924. The programs in the program group 923 are executed by the CPU 911 and the OS 921.

  The program group 923 stores a program for executing a function described as “˜unit” in the embodiment. The program is read and executed by the CPU 911.

In the file group 924, in the embodiment, result data such as “determination result”, “calculation result of”, “processing result of” when executing the function of “to part”, “to part” The data to be passed between programs that execute the function “,” other information, data, signal values, variable values, and parameters are stored as items “˜file” and “˜database”.
The “˜file” and “˜database” are stored in a recording medium such as a disk or a memory. Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit, and extracted, searched, referenced, compared, and calculated. Used for CPU operations such as calculation, processing, output, printing, and display. Information, data, signal values, variable values, and parameters are temporarily stored in the main memory, cache memory, and buffer memory during the CPU operations of extraction, search, reference, comparison, operation, calculation, processing, output, printing, and display. Is remembered.
In addition, arrows in the flowcharts described in the embodiments mainly indicate input / output of data and signals, and the data and signal values are recorded in the memory of the RAM 914, the magnetic disk of the magnetic disk device 920, and other recording media. . Data and signal values are transmitted online via a bus 912, signal lines, cables, or other transmission media.

  In addition, what is described as “˜unit” in the embodiment may be “˜circuit”, “˜device”, “˜device”, and “˜step”, “˜procedure”, “˜”. Processing ". That is, what is described as “˜unit” may be realized by firmware stored in the ROM 913. Alternatively, it may be implemented only by software, or only by hardware such as elements, devices, substrates, and wirings, by a combination of software and hardware, or by a combination of firmware. Firmware and software are stored as programs on a magnetic disk or other recording medium. The program is read by the CPU 911 and executed by the CPU 911. That is, the program causes the computer to function as “to part”. Alternatively, the procedure or method of “to part” is executed by a computer.

FIG. 4 is a functional configuration diagram of the device integration management apparatus 200 according to the first embodiment.
The functional configuration of the device integration management apparatus 200 according to Embodiment 1 will be described below with reference to FIG.

  The device integrated management apparatus 200 includes a display content generation unit 210 (an example of an execution result output unit), an MG control unit 220, an equipment data management unit 230 (an example of a URL type command generation unit), and an MG communication processing unit 240 (a URL type command). An example of a transmission unit) (an example of an execution result reception unit) and an integrated operation management DB 291 are provided.

  The MG control unit 220 uses the CPU 911 to analyze transmission / reception data (for example, request data 201 and response data 302 described later), display content generation unit 210, device data management unit 230, MG communication processing unit 240, and integrated operation The management DB 291 is controlled.

The device data management unit 230 uses the integrated operation management DB 291 to manage various types of information about the monitoring target device 400 such as device configuration information, profile information, and monitoring status information.
Furthermore, the device data management unit 230 (an example of a URL-type command generation unit) sets the address (which may be a corresponding host name) of the gateway 300 that is communicatively connected to the plurality of monitoring target devices 400 based on the device configuration information. Data in which a device ID for identifying a specific monitoring target device 400 and a processing ID for identifying a processing to be executed by the specific monitoring target device 400 are added to a URL as a URL instruction 202 is generated using the CPU. The device data management unit 230 generates request data 201 including the URL type command 202.

The MG communication processing unit 240 communicates with the gateway 300 and the device integration management display device 110 via the Internet 101 using a communication device. The MG communication processing unit 240 uses HTTP (HyperText Transfer Protocol) for communication with the gateway 300 and the device integrated management display device 110. However, HTTP is an example of a communication method.
For example, the MG communication processing unit 240 (an example of the URL type command transmission unit) transmits the request data 201 (including the URL type command 202) generated by the device data management unit 230 to the gateway 300 using the communication device. As a result, an execution command for causing the specific monitoring target device 400 to execute the execution process is transmitted from the gateway 300 to the specific monitoring target device 400, and the specific monitoring target device 400 executes the execution process.
Further, for example, the MG communication processing unit 240 (an example of the execution result receiving unit) receives the execution result of the execution process by the specific monitoring target device 400 as the response data 302 from the gateway 300 using the communication device.

The display content generation unit 210 uses content (for example, HTML content (HTML: HyperText Markup Language)) indicating the content of the response data 302 received by the MG communication processing unit 240 (execution result of the monitoring target device 400) using the CPU. To generate.
Furthermore, the display content generation unit 210 (an example of the execution result output unit) transmits the generated content as the display content 203 to the device integration management display device 110 via the MG communication processing unit 240. As a result, the display content 203 is displayed on the device integrated management display device 110. For example, the display content 203 indicates profile information output by the monitoring target device 400 and is displayed on the Web browser of the device integrated management display device 110. An administrator who uses the device integration management display device 110 manages the monitoring target device 400 by confirming the display content 203 displayed on the device integration management display device 110.

  The integrated operation management DB 291 stores various types of information about the monitoring target device 400 such as device configuration information, profile information, and monitoring status information using a storage medium.

FIG. 5 is a functional configuration diagram of the gateway 300 according to the first embodiment.
A functional configuration of the gateway 300 according to the first embodiment will be described below with reference to FIG.

  The gateway 300 includes a GW communication processing unit 310 (an example of a URL-type command reception unit) (an example of an execution command transmission unit) (an example of an execution result connection reception unit) (an example of an execution result connection transmission unit), a GW control unit 320, Device configuration management unit 330, device monitoring unit 340, response data generation unit 350 (an example of an execution format result generation unit), model-specific monitoring control unit 360 (an example of an execution command generation unit), control setting storage unit 391, device configuration / A monitoring DB 392 and a response data template DB 393 are provided.

The GW communication processing unit 310 communicates with the device integration management apparatus 200 and each IP device 401 using a communication device.
For example, the GW communication processing unit 310 performs the following communication.
The GW communication processing unit 310 (an example of a URL type command receiving unit) receives the request data 201 (including the URL type command 202) from the device integrated management apparatus 200 using the communication device.
The GW communication processing unit 310 (an example of an execution command transmission unit) transmits API data 301 (an example of an execution command) generated by the model-specific monitoring control unit 360 to a specific IP device 401 using a communication device. As a result, the API data 301 is processed by the specific IP device 401.
The GW communication processing unit 310 (an example of an execution result connection receiving unit) receives the processing result of the API data 301 from the specific IP device 401 as the execution result data 409 using the communication device.
The GW communication processing unit 310 (an example of the execution result connection transmission unit) uses the communication device to transmit the response data 302 in a predetermined format generated based on the execution result data 409 by the response data generation unit 350 to the device integrated management apparatus 200. Send.

  The GW control unit 320 controls the GW communication processing unit 310, the device configuration management unit 330, the device monitoring unit 340, the response data generation unit 350, and the model-specific monitoring control unit 360 using the CPU 911. Further, the GW control unit 320 converts the protocol between the device integrated management apparatus 200 and the gateway 300 and the protocol between the gateway 300 and the IP device 401.

  The device configuration management unit 330 updates and references the device configuration / monitoring DB 392 to manage the configuration of each monitoring target device 400 using the CPU 911.

  The device monitoring unit 340 periodically monitors each device to be monitored 400 and manages the configuration / state change using the CPU 911.

The response data generation unit 350 dynamically generates response data 302 that responds to the device integration management apparatus 200.
The URL type command 202 includes a process ID for identifying a process to be executed by a specific monitoring target device and a model ID for identifying the model of the specific monitoring target device. The response data template DB 393 includes a model ID and a processing ID. And a response data template 393a (an example of an execution result format definition file) is stored in advance. A response format representing the execution result is set in the response data template 393a.
The response data generation unit 350 (an example of the execution format result generation unit) generates response data 302 indicating the execution result data 409 received by the GW communication processing unit 310 using the CPU based on the response data template 393a. . The response data 302 indicates the execution result data 409 in a response format corresponding to the model ID included in the URL type command 202 and the process ID included in the URL type command 202.

The model-specific monitoring control unit 360 includes a model A controller [gw] 361, a model B controller [acs-pv] 362, a model C controller [c-100] 363, ... corresponding to the model of each monitored device 400. And monitoring each device 400 to be monitored according to the API of each model.
For example, the model-specific monitoring control unit 360 (an example of an execution command generation unit) specifies a specific monitoring target device 400 based on the request data 201 (including the URL type command 202) received by the GW communication processing unit 310. An execution instruction for executing processing is generated as API data 301 using the CPU.
The URL-type command 202 includes a process ID for identifying a process to be executed by a specific monitoring target device and a model ID for identifying the model of the specific monitoring target device.
The model-specific monitoring control unit 360 generates the API data 301 in a format corresponding to the model of a specific monitoring target device based on the model ID included in the URL type command 202.

The control setting storage unit 391 stores the routing definition file 391a using a storage medium.
In the routing definition file 391a (an example of a process name definition file), a process name for generating the API data 301 is set in advance in association with the model ID and the process ID.

The device configuration / monitoring DB 392 stores a device configuration monitoring table 392a using a storage medium.
In the device configuration monitoring table 392a, the device configuration of each monitoring target device 400 including the device ID and the model ID is set in advance.
The device configuration monitoring table 392a is updated by the device monitoring unit 340 in accordance with the addition / deletion of the monitoring target device 400.

The response data template DB 393 stores the response data template 393a using a storage medium.
In the response data template 393a (an example of an execution result format definition file), a response format representing an execution result is set in advance in association with the model ID and the process ID.

  Each IP device 401 (such as the electric lock control panel 410 and the network monitoring camera 420) processes the API data 301 in a predetermined format using the CPU 911 and outputs the execution result data 409 (interface B processing unit 411, Interface C processing unit 421).

FIG. 6 is a flowchart illustrating an initial process performed by the device integrated management apparatus 200 according to the first embodiment.
An initial process in which the device integrated management apparatus 200 acquires device configuration information indicating the device ID and model ID of each monitored device 400 from the gateway 300 will be described below with reference to FIG.
Each “˜unit” of the device integrated management apparatus 200 executes processing described below using a CPU.

<S210>
The device data management unit 230 generates a URL in which the host name of the gateway 300 is set.
The host name of the gateway 300 is a name corresponding to the IP address of the gateway 300 and is input by an administrator who operates the device integrated management apparatus 200 or notified from the gateway 300 and stored in advance in the integrated operation management DB 291 as a seed setting. Is done. Instead of the host name of the gateway 300, the IP address of the gateway 300 may be used.
Hereinafter, the host name of the gateway 300 will be described as “bda-gw1”.
In S210, the device data management unit 230 generates a URL “http: // bda-gw1”.
After S210, the process proceeds to S220.

<S220>
The device data management unit 230 generates a URL type command 202 by adding a request parameter for requesting device configuration information to the URL generated in S210.
The request parameter for requesting the device configuration information is stored in advance in the integrated operation management DB 291 as with the gateway 300 host name.
Hereinafter, the request parameter for requesting the device configuration information will be described as “/ devices / list”.
In S <b> 220, the device data management unit 230 generates “http: // bda-gw1 / devices / list” as the URL type instruction 202.
After S220, the process proceeds to S230.

<S230>
The device data management unit 230 generates the request data 201 including the URL type command 202 generated in S220.

FIG. 7 is a diagram illustrating an example of the request data 201 and the response data 302 according to the first embodiment.
For example, in S230 (see FIG. 6), the device data management unit 230 generates an HTTP-GET message “HTTP-GET http: // bda-gw1 / devices / list” as the request data 201 as shown in FIG. .

  After S230 (see FIG. 6), the process proceeds to S240.

<S240>
The MG communication processing unit 240 transmits the request data 201 generated in S230 to the gateway 300 via the Internet 101.
The request data 201 may be transmitted by HTTP communication with respect to a URL, or may be transmitted by a communication method such as XML-RPC or SOAP-RPC.
After S240, response data 302 indicating device configuration information is transmitted from the gateway 300 based on the request data 201. The process proceeds to S250.

<S250>
The MG communication processing unit 240 receives response data 302 indicating device configuration information from the gateway 300 via the Internet 101.
For example, the MG communication processing unit 240 receives response data 302 representing the device configuration information of each monitored device 400 in the XML format from the gateway 300 as shown in FIG.

  In FIG. 7, “id =” indicates the model ID of the monitoring target device 400 and the URL type ID 202a including the device ID, “type =” indicates the model name of the monitoring target device 400, and “ip =” indicates the monitoring target. The IP address of the device 400 is indicated, “model =” indicates the model name of the monitoring target device 400, and “firmware =” indicates the firmware name of the monitoring target device 400.

The URL type ID 202a indicated as “id =” is “URL set with the host name of the gateway 300 (http: // bda-gw1)” “model ID of the monitoring target device 400” “the monitoring target device 400”. Device ID ".
For example, “id =“ http: // bda-gw1 / acs-pv / 10 ”” in FIG. 7A indicates that the model ID of the electric lock control panel 410 is “acs-pv” and the electric lock control panel 410 This indicates that the device ID (relative identifier) is “10”.
Further, FIG. 7A shows that the IP address of the electric lock control panel 410 is “192.168.0.10/24”, the model name of the electric lock control panel 410 is “ACS-PV”, and the electric lock control panel 410. The firmware name is “YYY”.

  After S250 (see FIG. 6), the process proceeds to S260.

<S260>
The device data management unit 230 stores the device configuration information of each monitoring target device 400 received in S250 in the integrated operation management DB 291.
After S260, the process ends.

FIG. 8 is a flowchart showing an initial process by the gateway 300 in the first embodiment.
An initial process in which the gateway 300 provides device configuration information indicating the device ID and model ID of each monitored device 400 to the device integrated management apparatus 200 will be described with reference to FIG.
Each “˜unit” of the gateway 300 executes processing described below using the CPU.

<S310>
The GW communication processing unit 310 receives request data 201 including the URL type command 202 from the device integrated management apparatus 200 via the Internet 101. It is assumed that a request parameter of device configuration information is set in the URL type command 202.
For example, the GW communication processing unit 310 receives the request data 201 “HTTP-GET http: // bda-gw1 / devices / list” illustrated in FIG. 7.
After S310, the process proceeds to S320.

<S320>
The GW control unit 320 analyzes the request data 201 received in S310 based on the routing definition file 391a, and instructs the model A controller [gw] 361 to acquire device configuration information based on the URL type command 202.

FIG. 9 is a diagram illustrating an example of the routing definition file 391a according to the first embodiment.
The administrator generates a routing definition file 391 a “routing.def” as shown in FIG. 9 and stores it in the control setting storage unit 391 of the gateway 300 in advance.
In FIG. 9 (1), when the request data 201 is an HTTP-GET message and the host name of the URL type command 202 indicates “/ devices / list”, the model A controller identified by “gw” [gw 361 defines that the process (module, function, action, program, etc.) identified by “get_devices_list” is executed.

When the request data 201 is “GET http: // bda-gw1 / devices / list” in S320 (see FIG. 8), the GW control unit 320 follows the routing definition file 391a (see FIG. 9 (1)). The model A controller [gw] 361 is instructed to perform “get_devices_list” processing.
“Get_devices_list” indicates device configuration information acquisition processing.
After S320, the process proceeds to S330.

<S330>
The model A controller [gw] 361 acquires the device configuration information 392b from the device configuration monitoring table 392a.

FIG. 10 is a diagram illustrating an example of the device configuration monitoring table 392a according to the first embodiment.
The device configuration monitoring table 392a in the first embodiment will be described below with reference to FIG.
The device configuration monitoring table 392a indicates device configuration information 392b and device monitoring information 392c for each monitoring target device 400, and is stored in the device configuration / monitoring DB 392.
The device configuration information 392b includes the model ID of the IP device 401, the device ID of the IP device 401 and the device ID “device_path” of the peripheral device 402, the device ID “device_id” of the device, the model name “device_type” of the device, and the device IP address “device_ip” and the like.
The device monitoring information 392c includes polling (periodic communication) presence / absence “is_polling” from each monitoring target device 400, the status “status” of each monitoring target device 400 notified by polling, and the latest polling execution date “last polling_at”. Etc.

The device configuration information 392b is input by the administrator or notified from the IP device 401 and set in the device configuration monitoring table 392a.
The device monitoring information 392c is detected by communication periodically performed between the device monitoring unit 340 and each IP device 401, and is set in the device configuration monitoring table 392a by the device monitoring unit 340.

  For example, the IP address is found by standard protocols such as PING, DHCP, and SNMP. Each information may be managed by a known means such as setting with a tool or the like.

In S330 (see FIG. 8), the model A controller [gw] 361 acquires device configuration information 392b as shown in FIG.
After S330, the process proceeds to S340.

<S340>
The response data generation unit 350 generates response data 302 representing the device configuration information 392b acquired in S330 based on the response data template 393a.
One of the response data templates 393a shows a template of response data 302 representing the device configuration information 392b. A response data template 393a indicating a template of the response data 302 representing the device configuration information 392b is defined by the administrator and stored in advance in the response data template DB 393.
For example, an XML format template that indicates the URL type ID 202 a (id), model name (type), IP address (ip), model name (model), and firmware name (firmware) of the monitoring target device 400 for each monitoring target device 400 is provided. , Defined as one of the response data templates 393a. The response data generation unit 350 sets each value of the device configuration information 392b in the response data template 393a, and generates response data 302 as shown in FIG.
After S340, the process proceeds to S350.

<S350>
The GW communication processing unit 310 transmits the response data 302 generated in S340 to the device integration management apparatus 200 via the Internet 101.
After S350, the process ends.

FIG. 11 is a flowchart illustrating management processing performed by the device integrated management apparatus 200 according to the first embodiment.
A management process in which the device integrated management apparatus 200 causes each monitoring target device 400 to execute a specific process via the gateway 300 using the URL type command 202 will be described below with reference to FIG.
Each “˜unit” of the device integrated management apparatus 200 executes processing described below using a CPU.

<S400>
The device data management unit 230 acquires the device configuration information acquired from the gateway 300 by the above-described initial processing from the integrated operation management DB 291.
After S400, the process proceeds to S410.

<S410>
The device data management unit 230 selects one device to be monitored 400 (hereinafter referred to as “unprocessed device”) that has not requested a specific process from the device configuration information.
For example, the device data management unit 230 converts the electric lock control panel 410 (id = “http: // bda-gw1 / acs-pv / 10”) from the device configuration information shown as the response data 302 in FIG. Choose as.
After S410, the process proceeds to S411.

<S411>
The device data management unit 230 acquires the URL type ID 202a of the unprocessed device selected in S410 from the device configuration information.
For example, when the unprocessed device is the electric lock control panel 410, the device data management unit 230 URL of the electric lock control panel 410 set as “id =” in the device configuration information (see FIG. 7A). The type ID 202a “http: // bda-gw1 / acs-pv / 10” is acquired.
After S411, the process proceeds to S412.

<S412>
The device data management unit 230 generates a URL type command 202 by adding a process ID 202b for identifying a specific process to be executed by an unprocessed device to the URL type ID 202a acquired in S411.
The process ID 202b is defined by the administrator and stored in the integrated operation management DB 291 in advance. For example, “getprofile” is defined as the process ID 202b for identifying the profile information acquisition process, and “gettime” is defined as the process ID 202b for identifying the internal time acquisition process.

FIG. 12 is a diagram showing the format of the URL type command 202 in the first embodiment.
The format of URL type command 202 in the first embodiment will be described below with reference to FIG.
The URL type command 202 includes a URL type ID 202a and a process ID 202b.
The URL type ID 202a includes “HTTP: //”, “hostname”, “/”, “: device_controller_name”, “/”, “: device_id”, “/”, and “: subdevice_id”.
“Hostname” is the host name of the gateway 300, “: device_controller_name” is the model ID of the IP device 401, “: device_id” is the device ID of the IP device 401, and “: subdevice_id” is the device ID of the peripheral device 402. Is set.
As described later, the model ID of the IP device 401 corresponds to the controller name of the model-specific monitoring control unit 360 of the gateway 300.
The process ID 202b is set to “: action”.

For example, if the URL type ID 202a is “http: // bda-gw1 / acs-pv / 10” and the process ID 202b is “gettime” in S412 (see FIG. 11), the device data management unit 230 sets the URL type ID 202a. "Http: // bda-gw1 / acs-pv / 10 / gettime" with the process ID 202b added to the URL type command 202 is generated.
After S412, the process proceeds to S413.

<S413>
The device data management unit 230 generates the request data 201 including the URL type command 202 generated in S412.

FIG. 13 is a diagram illustrating an example of request data 201 and response data 302 according to the first embodiment.
For example, in S413 (see FIG. 11), the device data management unit 230 sends the HTTP-GET message “HTTP-GET http: // bda-gw1 / acs-pv / 10 / gettime” as the request data as shown in FIG. It generates as 201.

  After S413 (see FIG. 11), the process proceeds to S420.

<S420>
The MG communication processing unit 240 transmits the request data 201 generated in S413 to the gateway 300 via the Internet 101.
After S420, specific processing is executed by the unprocessed device via the gateway 300 based on the request data 201, and response data 302 indicating the processing result is transmitted from the gateway 300. The process proceeds to S430.

<S430>
The MG communication processing unit 240 receives response data 302 indicating the processing result of the specific processing by the unprocessed device from the gateway 300 via the Internet 101.
For example, the MG communication processing unit 240 receives response data 302 indicating the internal time acquired by the unprocessed device in the XML format as illustrated in FIG. 13 from the gateway 300.

<S440>
The device data management unit 230 stores the response data 302 (the processing result of the specific processing by the unprocessed device) received in S430 in the integrated operation management DB 291.
After S440, the process proceeds to S450.

<S450>
The device data management unit 230 refers to the device configuration information and determines whether there are any unprocessed devices remaining.
If there is an unprocessed device (YES), the process returns to S410. If there is no unprocessed device (NO), the process proceeds to S460.

<S460>
The display content generation unit 210 generates the display content 203 based on the processing result of each monitoring target device 400 stored in the integrated operation management DB 291 in S440.

FIG. 14 is a diagram illustrating an example of the display content 203 according to the first embodiment.
The display content 203 in the first embodiment will be described below based on FIG.
The display content 203 is HTML content and indicates “device display name”, “device ID”, “model name”, “state”, and “device time”.
The “device display name” includes the model name (type) indicated in the device configuration information, the installation location (for example, “A building”) indicated in the profile information acquired by the profile information acquisition process (processing ID “getprofile”). Is set based on
In the “device ID”, the URL type ID 202a (id) indicated in the device configuration information is set.
In the “model name”, a value (model) of the device configuration information is set.
In the “status”, status information acquired by the status information acquisition process (process ID “getstatus”) is set.
In “device time”, the internal time acquired by the internal time acquisition process (process ID “gettime”) is set.

For example, in S410 to S440 (see FIG. 11), for each monitoring target device 400, the request data 201 with the process ID “getprofile”, the request data 201 with the process ID “getstatus”, and the process ID “gettime”. Request data 201 is transmitted to the gateway 300, and profile information, status information, and internal time of each monitored device 400 are stored in the integrated operation management DB 291.
In this case, the display content generation unit 210 generates the display content 203 as shown in FIG. 14 in S460 (see FIG. 11).

  Further, the display content generation unit 210 may perform file system mapping (hierarchical display) on the URL path indicated by the “device ID”. For example, like a file browser, a directory path can be displayed in the left pane, and various device information can be displayed in the right pane. Furthermore, by simplifying the display of unnecessary information portions of the display content 203, management of a large-scale system becomes easy.

  After S460 (see FIG. 11), the process proceeds to S470.

<S470>
The MG communication processing unit 240 transmits the display content 203 generated in S460 to the device integration management display device 110 via the Internet 101.
The device integration management display device 110 displays the Web browser 112 showing the display content 203 transmitted by the MG communication processing unit 240 as shown in FIG.
After S470, the process ends.

  The management process (FIG. 11) by the device integrated management apparatus 200 is executed periodically or when the display content request data 111 is transmitted from the device integrated management display device 110. For example, the device data management unit 230 is started and executed by a monitoring data acquisition daemon program that is periodically started in the device integrated management apparatus 200.

FIG. 15 is a flowchart showing management processing by the gateway 300 in the first embodiment.
A management process in which the gateway 300 executes a specific process on the monitoring target device 400 based on the URL type command 202 will be described below with reference to FIG.
Each “˜unit” of the gateway 300 executes processing described below using the CPU.

<S510>
The GW communication processing unit 310 receives request data 201 including the URL type command 202 from the device integrated management apparatus 200 via the Internet 101. The URL type instruction 202 indicates a URL type ID 202a and a process ID 202b.
For example, the GW communication processing unit 310 receives the request data 201 “HTTP-GET HTTP: /// bda-gw1 / acs-pv / 10 / gettime” illustrated in FIG. 13.
After S510, the process proceeds to S520.

<S520>
The GW control unit 320 analyzes the request data 201 received in S510 based on the routing definition file 391a, and based on the URL type command 202, the controller and controller module (“action” “function” And the IP device 401 are determined.
Hereinafter, the controller of the model-specific monitoring control unit 360 determined in S520 is referred to as “specific controller”, the controller module as “specific module”, and the IP device 401 as “specific device”.
When the request data 201 is “HTTP-GET HTTP: /// bda-gw1 / acs-pv / 10 / gettime”, the GW control unit 320 specifies the specific controller according to the routing definition file 391a (see FIG. 9 (3)). Is the model B controller [acs-pv] 362, the electric lock control panel 410 having the specific device “10” as the device ID, and the specific module “GetAcsTime”.
When the request data 201 is “HTTP-GET HTTP: /// bda-gw1 / acs-pv / 10 / cr1 / gettime”, the GW control unit 320 uses the card reader 491 with “cr1” as the device ID. Decide on the target device.

  In addition, when analyzing the request data 201, the GW control unit 320 sets whether the device ID is set in the device configuration monitoring table 392a, whether the format of the URL-type command 202 is invalid, or whether the model ID or processing ID is the routing definition file 391a. Check whether it is defined in the above. When an error is detected, the GW control unit 320 transmits response data 302 indicating an error number, an error cause, and the like to the device integrated management apparatus 200 via the GW communication processing unit 310, and ends the management process. The response data 302 is generated by inserting an error number and error cause into the response data template 393a by the response data generation unit 350.

  After S520, the process proceeds to S530.

<S530>
The GW control unit 320 instructs the specific controller to execute the specific module based on the determination items in S520.
For example, when the specific controller is determined to be the model B controller [acs-pv] 362 and the specific module is “GetAcsTime” in S520, the GW control unit 320 causes the model B controller [acs-pv] 362 to execute the GetAcsTime module. Command.
After S530, the process proceeds to S540.

<S540>
By executing the specific module, the specific controller transmits the API data 301 and instructs the specific device to execute the specific process.
A program (instruction code) for causing a predetermined model to execute a predetermined process is defined in each module of the controller.
For example, by executing the GetAcsTime module, the model B controller [acs-pv] 362 generates command data for executing the internal time acquisition function (API) provided by the model “acs-pv” as the API data 301. The generated API data 301 is transmitted to a specific device (for example, the electric lock control panel 410) via the GW communication processing unit 310.
When the target device (for example, the card reader 491) is determined, the model B controller [acs-pv] 362 specifies API data 301 for operating the internal time acquisition function for the target device as a specific device (for example, To the electric lock control panel 410).
Since the API differs depending on the model and function of the monitoring target device 400, the API data 301 generated by each module of each controller is different.
For example, even if the API data 301 causes the same internal time acquisition function to be executed, the API data 301 generated by the GetAcsTime module of the model B controller [acs-pv] 362 (see FIG. 9 (3)) and the model C controller [ c-100] 363 is different from the API data 301 generated by the GetC100Time module (FIG. 9 (4)).

  The GW communication processing unit 310 acquires the IP address of the specific device from the device configuration monitoring table 392a based on the device ID, and transmits the API data 301 to the specific device using the acquired IP address.

  After S540, the processing result of the specific processing executed by the processing unit of the specific device (for example, the interface B processing unit 411 of the electric lock control panel 410) is transmitted to the gateway 300 as execution result data 409. The process proceeds to S550.

<S550>
The specific controller receives the execution result data 409 transmitted from the specific device via the GW communication processing unit 310.
After S550, the process proceeds to S560.

<S560>
The response data generation unit 350 generates response data 302 indicating the execution result data 409 received in S550, based on the response data template 393a.
In the response data template DB 393, a response data template 393a indicating a template of the response data 302 is stored for each model ID and process ID. Each response data template 393a is defined by the administrator and stored in advance in the response data template DB 393.

FIG. 16 is a diagram illustrating an example of the response data template 393a according to the first embodiment.
For example, as shown in FIG. 16, an XML-format response data template 393a corresponding to the model ID “acs-pv” and the process ID “gettime” is named “acs-pv_gettime.xml.template”. Stored in the DB 393.
“<% = H id%>” is the model ID and device ID of the URL type instruction 202, “<% = h action%>” is the process ID of the URL type instruction 202, and “<% = h action_response%>”. Is set with the value of the execution result data 409.
When the model B controller [acs-pv] 362 executes the GetAcsTime module corresponding to the process ID “gettime”, and the execution result data 409 of the electric lock control panel 410 indicates “2008-08-01 12:00:00” , S560 (see FIG. 15), the response data generation unit 350 generates response data 302 as shown in FIG. 13 based on “acs-pv_gettime.xml.template” (see FIG. 16).

  After S560 (see FIG. 15), the process proceeds to S570.

<S570>
The GW communication processing unit 310 transmits the response data 302 generated in S560 to the device integration management apparatus 200 via the Internet 101.
After S570, the process ends.

  The management process may be executed by any one of the monitoring target devices 400 instead of the gateway 300. In this case, the monitoring target device 400 that executes the management process has the configuration of the gateway 300 described above.

In the first embodiment, the following device integrated management system 100 and device integrated management method have been described.
The device integrated management system 100 manages IDs for specifying devices in the URL format in device monitoring / control and the like, and monitors and controls each device by transmitting this URL from the device integrated management apparatus 200 to the gateway 300.
The device integrated management system 100 designates a device or its peripheral device by a URL type ID, adds a monitoring / control command character string (processing ID) to the device or its peripheral device to the URL type ID, and adds the URL (URL Each device is monitored and controlled by HTTP communication according to the type command 202).
The device integrated management system 100 executes a monitoring / control command for the device or its peripheral device using the URL type ID, and manages a plurality of models in an integrated manner.
The gateway 300 (or the monitoring target device 400) receives a monitoring / control command for the device using the URL-type ID or its peripheral device from the device integrated management apparatus 200, and analyzes the URL to analyze the monitoring target device / peripheral device. , Specify the execution processing module / function to monitor / control the specified device by the URL and protocol, execute the monitoring / control command for the monitoring target by the specified execution processing module, and integrate the execution result into the device Responds to the management device 200.
The gateway 300 (or the device to be monitored 400) includes modules and functions for controlling and monitoring each device and peripheral device, model type information in the URL, device ID, execution command, routing map definition (routing definition file 391a), and so on. To execute the monitoring / control processing for each model.
The gateway 300 (or the monitoring target device 400) dynamically outputs an execution result corresponding to each parameter portion specified in the response data template file (response data template 393a) specified from the type of monitoring target and the execution command. The execution result is returned to the device integration management apparatus 200.

The device integrated management system 100 can manage the bases over a wide area in an integrated manner with good visibility by managing the device IDs in the URL format.
The device integrated management system 100 uses an API routing table (routing definition file 391a) for accessing a monitoring / control function provided for each device control with a uniform operation name (action name) (processing ID). Makes it easy to integrate different monitoring and control interfaces (APIs) individually.
The device integrated management system 100 absorbs the difference of the response data (execution result data 409) of the monitoring / control function call provided for each device control for each model, and the device integrated management device 200 has a unified response data format. Responding in (for example, XML format) facilitates integrated management.

FIG. 2 is a device configuration diagram of the device integrated management system 100 according to the first embodiment. FIG. 3 is a sequence diagram illustrating a processing flow of the device integrated management system 100 according to the first embodiment. FIG. 3 is a diagram illustrating an example of hardware resources of the device integrated management system 100 according to the first embodiment. FIG. 3 is a functional configuration diagram of the device integration management apparatus 200 according to the first embodiment. 2 is a functional configuration diagram of a gateway 300 according to Embodiment 1. FIG. 5 is a flowchart showing an initial process by the device integration management apparatus 200 according to the first embodiment. FIG. 6 shows an example of request data 201 and response data 302 in the first embodiment. 5 is a flowchart showing an initial process by the gateway 300 in the first embodiment. FIG. 6 is a diagram showing an example of a routing definition file 391a in the first embodiment. FIG. 6 is a diagram illustrating an example of a device configuration monitoring table 392a according to the first embodiment. 5 is a flowchart showing management processing by the device integrated management apparatus 200 according to Embodiment 1. FIG. 5 shows a format of a URL type instruction 202 in the first embodiment. FIG. 6 shows an example of request data 201 and response data 302 in the first embodiment. FIG. 6 shows an example of display content 203 in Embodiment 1; 5 is a flowchart showing management processing by a gateway 300 in the first embodiment. FIG. 6 shows an example of a response data template 393a in the first embodiment.

Explanation of symbols

  100 device integrated management system, 101 Internet, 102 LAN, 103 building, 110 device integrated management display device, 111 display content request data, 112 Web browser, 200 device integrated management device, 201 request data, 202 URL type command, 202a URL type ID, 202b Process ID, 203 Display content, 210 Display content generation unit, 220 MG control unit, 230 Device data management unit, 240 MG communication processing unit, 291 Integrated operation management DB, 300 Gateway, 301 API data, 302 Response data, 310 GW communication processing unit, 320 GW control unit, 330 device configuration management unit, 340 device monitoring unit, 350 response data generation unit, 360 model-specific monitoring control unit, 361 model A controller [gw], 362 model B controller [acs-pv], 363 Model C controller [c-100], 391 Control setting storage unit, 391a Routing definition file, 392 Device configuration / monitor DB, 392a Device configuration monitoring table, 392b Device configuration information, 392c Device monitoring Information, 393 Response data template DB, 393a Response data template, 400 Monitoring target device, 401 IP device, 402 Peripheral device, 409 Execution result data, 410 Electric lock control panel, 411 Interface B processing unit, 420 Network monitoring camera, 421 Interface C processing unit, 430 surveillance recorder, 440 video surveillance display device, 450 air conditioning control device, 460 illumination control device, 491 card reader, 492 door with electric lock, 493 analog surveillance camera, 49 Air conditioning unit, 495 lighting units, 901 display unit, 902 a keyboard, 903 mouse, 911 CPU, 912 Bus, 913 ROM, 914 RAM, 915 communication board, 920 a magnetic disk device, 921 OS, 923 programs, 924 files.

Claims (11)

A device ID for identifying a specific monitoring target device and a process to be executed by the specific monitoring target device are identified as execution processing in a URL (Uniform Resource Locator) in which addresses of device connection devices that are connected to a plurality of monitoring target devices are set. A URL type command generation unit that generates data with a processing ID to be generated as a URL type command using a CPU (Central Processing Unit);
An execution command for causing the specific monitoring target device to execute the execution process is transmitted from the device connection device by transmitting the URL type command generated by the URL type command generation unit to the device connection device using a communication device. A device integrated management apparatus comprising: a URL-type command transmission unit that transmits to the specific monitoring target device and causes the specific monitoring target device to execute the execution process. The device integrated management apparatus according to claim 1, wherein the URL-type command transmission unit transmits the URL-type command using HTTP (HyperText Transfer Protocol). An execution result receiving unit that receives an execution result of the execution process by the specific monitoring target device from the device connection device using a communication device;
The apparatus integrated management apparatus according to claim 1, further comprising: an execution result output unit that outputs an execution result received by the execution result receiving unit to an output device. A device ID for identifying a specific monitoring target device and a process to be executed by the specific monitoring target device are identified as execution processing in a URL (Uniform Resource Locator) in which addresses of device connection devices that are connected to a plurality of monitoring target devices are set. URL type command generation processing for generating data with a processing ID to be generated using a CPU (Central Processing Unit) as a URL type command;
An execution command for causing the specific monitoring target device to execute the execution process is transmitted from the device connection apparatus by transmitting the URL type command generated by the URL type command generation process to the device connection apparatus using a communication device. A device integration management program for causing a device integrated management apparatus to execute URL-type command transmission processing that is transmitted to the specific monitoring target device and causes the specific monitoring target device to execute the execution processing. A device connection device that communicates and connects with multiple monitored devices.
A device ID for identifying a specific monitoring target device and a processing ID for identifying a process to be executed by the specific monitoring target device as an execution process are added to a URL (Uniform Resource Locator) in which the host name of the device connection apparatus is set. A URL type command receiving unit that receives the URL type command using a communication device from a device integrated management device that transmits the received data as a URL type command;
An execution command generation unit that generates, using a CPU (Central Processing Unit), an execution command that causes the specific monitoring target device to execute the execution process based on the URL type command received by the URL type command reception unit;
An execution command transmission unit that transmits the execution command generated by the execution command generation unit to the specific monitoring target device using a communication device and causes the specific monitoring target device to execute the execution process. A device connection device. The URL type command includes a model ID for identifying the model of the specific monitoring target device,
6. The device connection according to claim 5, wherein the execution command generation unit generates the execution command in a format corresponding to a model of the specific monitored device based on a model ID included in the URL type command. apparatus. An execution result connection receiving unit that receives the execution result of the execution process from the specific monitoring target device using a communication device;
The execution result connection transmission part which transmits the execution result received by the said execution result connection receiving part to the said apparatus integrated management apparatus using a communication apparatus is provided. The apparatus connection apparatus of description. The URL type command includes a model ID for identifying the model of the specific monitoring target device,
The device connection apparatus uses the execution result received by the execution result connection receiving unit based on an execution result format definition file in which a format representing an execution result is set in advance in association with a model ID and a process ID. An execution format result generating unit that generates, using a CPU, an execution format result represented in a format corresponding to a model ID included in the URL type command and a processing ID included in the URL type command;
8. The device connection apparatus according to claim 7, wherein the execution result connection transmission unit transmits the execution format result generated by the execution format result generation unit to the device integrated management apparatus. As an execution process, a device ID for identifying a specific monitoring target device in a URL (Uniform Resource Locator) in which an address of a device connection apparatus that communicates with a plurality of monitoring target devices is set, and a process to be executed by the specific monitoring target device URL-type command reception processing for receiving the URL-type command using a communication device from a device integrated management device that transmits data to which a process ID for identification is added as a URL-type command;
An execution command generation process for generating, using a CPU (Central Processing Unit), an execution command for causing the specific monitoring target device to execute the execution process based on the URL type command received by the URL type command reception process;
An execution command transmission process for transmitting the execution command generated by the execution command generation process to the specific monitoring target device using a communication device and causing the specific monitoring target device to execute the execution processing. A device connection program to be executed. The device integrated management apparatus according to any one of claims 1 to 3,
A device integrated management system comprising the device connection apparatus according to claim 5. The device integrated management device causes the specific monitoring target device to execute the device ID for identifying the specific monitoring target device in a URL (Uniform Resource Locator) in which the addresses of the device connection devices that are connected to the plurality of monitoring target devices are set. Sending the data to which the process ID for identifying the process as an execution process is added as a URL-type command to the device connection apparatus,
The device connection apparatus receives the URL type command transmitted from the device integrated management apparatus, and executes an execution command for causing the specific monitoring target device to execute the execution process based on the received URL type command. A device integrated management method comprising: transmitting to a target device and causing the specific monitoring target device to execute the execution process.

Images