WO2014112581A1 - Device management apparatus, device management system, device management method, and program - Google Patents

Abstract

The present invention contributes to the easy determination and management of a device to be managed. A device management apparatus is provided with: a management apparatus communication unit which communicates with one or more devices; a presence/absence information generation unit which generates presence/absence information corresponding to each of the devices on the basis of whether communication with each of the devices is enabled or not; a device-specific information acquisition unit which acquires device-specific information from the devices; and a device management table generation unit which generates a device management table in which the presence/absence information, the device-specific information, and device-related information are associated.

Description

Device management apparatus, device management system, device management method and program

(Description of related applications)
The present invention is based on the priority claim of Japanese patent application: Japanese Patent Application No. 2013-007354 (filed on Jan. 18, 2013), and the entire contents of the application are incorporated and described herein by reference. And
The present invention relates to a device management apparatus, a device management system, a device management method, and a program.

When an administrator or maintenance worker checks a managed server machine, PC (Personal Computer), printer, network device, etc., it is difficult to determine a managed device (hereinafter referred to as a managed device). There are cases. For example, in an environment where there are a plurality of devices of the same model, it is difficult for an administrator or the like to determine a device to be managed.

Patent Document 1 discloses a technique for acquiring installation location information based on the output of a GPS (Global Positioning System) unit mounted on a managed device. In the technique disclosed in Patent Document 1, it is determined whether or not the current location of the maintenance worker matches the installation location of the managed device.

Patent Document 2 discloses a technique for creating a network design drawing. In the technique disclosed in Patent Document 2, a network configuration diagram relating to a management target device is created based on the network design drawing.

JP 2009-187499 A JP 2003-101586 A

It should be noted that the disclosures of the above prior art documents are incorporated herein by reference. The following analysis has been made from the viewpoint of the present invention.

As described above, it may be difficult for an administrator or the like to identify a managed device when checking the managed device.

For example, the administrator or the like may determine the management target device based on the label attached to the management target device. However, when the label is not properly applied, it is often difficult to determine the management target device. In addition, when a managed device is removed, it is often difficult to confirm whether or not there is a managed device.

In the technique disclosed in Patent Document 1, it is necessary to attach a GPS unit to a device to be managed. For this reason, the technology disclosed in Patent Document 1 may limit the manageable devices.

Furthermore, in the technique disclosed in Patent Document 1, the administrator or the like needs to move to the installation location of the managed device. Therefore, with the technique disclosed in Patent Document 1, an administrator or the like cannot manage a management target device from a remote location.

In the technique disclosed in Patent Document 2, it is necessary to create a network design drawing in advance. Therefore, the technology disclosed in Patent Document 2 cannot be used in an environment where the network configuration of the device is unknown. For example, the network configuration of a customer is often unknown. Therefore, the technique disclosed in Patent Document 2 cannot be used for the customer's environment.

Therefore, a device management apparatus, a device management system, a device management method, and a program that contribute to easily discriminating and managing managed devices are desired.

According to the first aspect of the present invention, whether or not to generate presence / absence information corresponding to each device based on the management device communication unit that communicates with one or more devices and whether or not communication with each device is possible A device management table that generates a device management table in which an information generation unit, a device specific information acquisition unit that acquires device specific information from the device, the presence / absence information, the device specific information, and device related information are associated with each other A device management apparatus comprising a generation unit is provided.

According to a second aspect of the present invention, device management including one or more devices, a device-related information server that manages device-related information of the devices, and a device management apparatus that manages information related to the devices. The device management apparatus includes: a management device communication unit that communicates with one or more of the devices and the device-related information server; and whether or not communication with the devices is possible. Device that associates presence / absence information generation unit that generates corresponding presence / absence information, device-specific information acquisition unit that acquires device-specific information from the device, presence / absence information, device-specific information, and device-related information A device management system is provided that includes a device management table generation unit that generates a management table.

According to the third aspect of the present invention, the management device communication process for communicating with one or more devices and whether to generate presence / absence information corresponding to each device based on whether communication with each device is possible An information generation step, a device specific information acquisition step of acquiring device specific information from the device, a step of generating a device management table in which the presence information, the device specific information, and device related information are associated with each other; A device management method is provided.
Note that this method is linked to a specific machine called a device management apparatus that manages information related to devices.

According to a fourth aspect of the present invention, there is provided a program that is executed by a computer that controls a device management apparatus, the management device communication processing for communicating with one or more devices, and whether communication with each device is possible. Presence / absence information generation processing for generating presence / absence information corresponding to each device, device-specific information acquisition processing for acquiring device-specific information from the device, the presence / absence information, the device-specific information, and device-related information And a process for generating a device management table in which are associated with each other.
This program can be recorded on a computer-readable storage medium. The storage medium may be non-transient such as a semiconductor memory, a hard disk, a magnetic recording medium, an optical recording medium, or the like. The present invention can also be embodied as a computer program product.

According to each aspect of the present invention, there are provided a device management apparatus, a device management system, a device management method, and a program that contribute to easily discriminating and managing managed devices.

It is a figure for demonstrating the outline | summary of one Embodiment. 1 is a diagram illustrating an example of an overall configuration of a device management system 10 according to a first embodiment. It is a block diagram which shows an example of an internal structure of the apparatus relevant information server 30 which concerns on 1st Embodiment. It is a block diagram which shows an example of an internal structure of the apparatus management apparatus 40 which concerns on 1st Embodiment. It is a figure which shows an example of the presence information management table. It is a figure which shows an example of a structure information management table. It is a figure which shows an example of an apparatus related information management table. It is a figure which shows an example of the information memorize | stored in each database. 5 is a flowchart showing an example of the operation of the device management apparatus 40. It is a flowchart which shows an example of the process which adds presence information. It is a flowchart which shows an example of the process which acquires structure information. It is a flowchart which shows an example of the process which adds structure information. It is a flowchart which shows an example of the process which acquires maintenance contract information. It is a flowchart which shows an example of the process which adds maintenance contract information. It is a flowchart which shows an example of the process which produces | generates and displays an apparatus management table. It is a figure which shows an example of an apparatus management table. It is a block diagram which shows an example of an internal structure of the apparatus management apparatus 40a which concerns on 2nd Embodiment. It is a flowchart which shows an example of the process which analyzes a network structure. It is a figure which shows an example of the display of network configuration information. It is a figure which shows an example of the whole structure of the apparatus management system 10a which concerns on 3rd Embodiment.

First, an outline of an embodiment will be described with reference to FIG. Note that the reference numerals of the drawings attached to the outline are attached to the respective elements for convenience as an example for facilitating understanding, and the description of the outline is not intended to be any limitation.

As described above, it may be difficult for an administrator or the like to identify a managed device when checking the managed device. Therefore, a device management apparatus that contributes to easily discriminating and managing managed devices is desired.

As an example, the device management apparatus 100 shown in FIG. 1 is provided. The device management apparatus 100 includes a management device communication unit 101 that communicates with one or more devices, a presence / absence information generation unit 102 that generates presence / absence information corresponding to each device based on whether communication with each device is possible, A device management table generating unit 104 that generates a device management table that associates device-specific information with a device-specific information acquisition unit 103 that acquires device-specific information from a device, presence / absence information, device-specific information, and device-related information; .

The device management apparatus 100 tries to communicate with one or more devices. Here, it is assumed that the communication target device includes a management target device.

Then, the device management apparatus 100 generates presence / absence information corresponding to each device based on the availability of communication with each device. The presence / absence information means information indicating the presence / absence of a device. For example, the device management apparatus 100 transmits a predetermined signal to one or more devices. The device management apparatus 100 may set presence / absence information to “present” for the device that has responded. On the other hand, the device management apparatus 100 may set the presence / absence information to “none” for a device that has not responded.

Furthermore, the device management apparatus 100 acquires information for identifying the device (hereinafter referred to as device-specific information) from the device. The device unique information is preferably information unique to the device even if the connection state of the device is changed. Furthermore, the device-specific information is preferably information that is difficult for a user, an administrator, or the like to change.

The device management apparatus 100 generates a device management table in which presence / absence information, device-specific information, and information related to the device (hereinafter referred to as device-related information) are associated with each other. The device related information may include information for managing the device. In this case, the device management apparatus 100 can manage the presence / absence of a management target device and information for managing the management target device even when an administrator or the like is in a remote place. Furthermore, the device management apparatus 100 can easily determine the management target device even in an environment in which a management target device and devices other than the management target device coexist.

Therefore, the device management apparatus 100 contributes to easily discriminating and managing managed devices.

Hereinafter, specific embodiments will be described in more detail with reference to the drawings. In the following description, the device-related information will be described by exemplifying information related to a maintenance contract (hereinafter referred to as maintenance contract information). However, this is not intended to limit the present invention to the management of devices that have signed a maintenance contract.

[First Embodiment]
The first embodiment will be described in more detail with reference to the drawings.

FIG. 2 is a diagram illustrating an example of the overall configuration of the device management system 10. The device management system 10 includes a device 20, a device related information server 30, and a device management apparatus 40. 2 is not intended to limit the configuration of the device management system 10 to the configuration shown in FIG.

The device 20 means a device connected to the device management apparatus 40 via the network 51. The device 20 may be a server machine, a PC, a printer, a router, a switch, or the like. For example, when the device management apparatus 40 exists in the LAN, the device 20 is a device in the same LAN as the device management apparatus 40.

Here, the device 20 includes a management target device 21 and a device 22 other than the management target device. Note that a plurality of managed devices 21 may be provided. Also, there may be a plurality of devices 22 other than the devices to be managed.

The device related information server 30 is connected to the device management apparatus 40 via the network 52.

The network 51 and the network 52 include networks such as a telephone line, the Internet, and a LAN (Local Area Network). There are various types of networks, but the details are not limited.

The device related information server 30 manages the maintenance contract information of the device 20. Specifically, the device related information server 30 manages maintenance contract information of the management target device 21. The maintenance contract information preferably includes the maintenance contract number, maintenance contract deadline, user name (contractor name), and the like of the managed device 21. Furthermore, the maintenance contract information includes a number for identifying the management target device 21 (hereinafter referred to as a device identification number), information for identifying the type of the management target device 21 (hereinafter referred to as a device code), and the like. May be included.

For example, the administrator or the like may input a device identification number, a device code, a maintenance contract number, and the like via an operation unit (not shown) of the device related information server 30. Further, when the contract contents are changed, the administrator or the like may change the maintenance contract number, the maintenance contract deadline, the user name (contractor name), and the like via the operation unit of the device related information server 30.

The device management apparatus 40 manages information related to the device 20. Specifically, the device management apparatus 40 manages the presence / absence information of the device 20, device unique information, and maintenance contract information in association with each other.

The device specific information preferably includes a MAC (Media Access Control) address. This is because the MAC address is information unique to each device 20 and is difficult for a user, administrator, or the like to change.

FIG. 3 is a block diagram illustrating an example of the internal configuration of the device-related information server 30. The device-related information server 30 includes a device-related information server communication unit 301 and a device-related information database 302. For simplicity, FIG. 3 mainly describes modules related to the device-related information server 30 according to the present embodiment.

The device related information server communication unit 301 communicates with the device management apparatus 40. Specifically, the device-related information server communication unit 301 sends information requested by the device management device 40 out of information stored in the device-related information database 302 in response to a request from the device management device 40. 40.

The device related information database 302 stores a device identification number, a device code, and device related information. For example, the device related information database 302 may store the device unique information in association with the maintenance contract information. Furthermore, the device related information database 302 may store the date and time when the stored information was accessed, the last update date and time, and the like.

FIG. 4 is a block diagram illustrating an example of the internal configuration of the device management apparatus 40. The device management apparatus 40 includes a management device communication unit 401, a network information acquisition unit 402, a device specific information acquisition unit 403, a presence / absence information generation unit 404, a presence / absence information management database 405, a configuration information acquisition unit 406, and a configuration. An information management database 407, a device related information acquisition unit 408, a device related information management database 409, a state estimation unit 410, and a device management table generation unit 411 are configured. For simplicity, FIG. 4 mainly describes modules related to the device management apparatus 40 according to the present embodiment.

The management device communication unit 401 communicates with one or more devices 20. Further, the management device communication unit 401 communicates with the device related information server 30.

The network information acquisition unit 402 acquires network information of one or more devices 20. The network information preferably includes an IP (Internet Protocol) address. Furthermore, the network information may include a subnet mask, a default gateway, a DNS (Domain Name System) server name, and the like.

For example, the network information acquisition unit 402 may transmit a so-called PING signal to the network 51 using the broadcast address as a transmission destination. In this case, the network information acquisition unit 402 can acquire the IP address of the device 20 that has responded.

The device specific information acquisition unit 403 acquires device specific information from the device 20. Specifically, the device specific information acquisition unit 403 acquires device specific information based on the network information.

For example, the device specific information acquisition unit 403 may refer to an ARP (Address Resolution Protocol) table stored in each device 20. Then, the device specific information acquisition unit 403 may acquire a MAC address corresponding to the IP address of the device 20 as device specific information. The ARP table is a table that stores an IP address and a MAC address in association with each other.

And a memory | storage part (not shown) memorize | stores the network information which the network information acquisition part 402 acquired. That is, the storage unit stores the network information of the device 20 that has responded. Further, the storage unit stores the device specific information acquired by the device specific information acquisition unit 403.

The presence / absence information generation unit 404 generates presence / absence information of the device 20 based on whether communication with the device 20 is possible. Specifically, when the network information acquisition unit 402 can acquire network information from the device 20, the presence / absence information generation unit 404 determines that the device 20 exists. On the other hand, if the network information acquisition unit 402 cannot acquire network information from the device 20, the presence / absence information generation unit 404 determines that the device 20 does not exist.

Then, when the device 20 exists, the presence / absence information generation unit 404 sets the presence / absence information regarding the device 20 to “present”. On the other hand, when the device 20 does not exist, the presence / absence information generation unit 404 sets the presence / absence information regarding the device 20 to “none”.

The presence / absence information management database 405 stores the device-specific information in association with the presence / absence information. Specifically, the presence / absence information management database 405 stores a presence / absence information management table in which device-specific information is associated with presence / absence information. Further, the presence / absence information management table may include the date and time when the presence / absence information management database 405 is updated, and the last update date / time of the presence / absence information management database 405.

FIG. 5 is a diagram showing an example of the presence / absence information management table. In the case of FIG. 5, the devices 20 are “server machine A”, “client PC”, “printer”, “switch”, “router”, and “server machine B”. In the case of FIG. 5, the presence / absence information management table indicates the correspondence between “IP address”, “presence / absence information”, “confirmation date / time”, “last update date / time”, and “MAC address”. However, FIG. 5 is not intended to limit the presence / absence information management table to the information shown in FIG.

For example, it is assumed that the network information acquisition unit 402 has acquired the IP addresses of “server machine A”, “client PC”, “printer”, “switch”, “router”, and “server machine B” at least once. In that case, the device specific information acquisition unit 403 acquires the MAC addresses of the devices 20 based on the IP address.

Then, the presence / absence information generation unit 404 generates a presence / absence information management table of the devices 20. In the case of FIG. 5, the presence / absence information generation unit 404 sets the presence / absence information of “server machine A”, “client PC”, “printer”, “switch”, “router”, and “server machine B” as “present”. Generate an information management table.

However, after that, when the network information acquisition unit 402 tries to acquire the network address of the device 20, it is assumed that the IP addresses of “printer” and “server machine B” cannot be acquired. In that case, as shown in FIG. 5, the presence / absence information generation unit 404 updates the presence / absence information management table with the presence / absence information set to “none” for “printer” and “server machine B”.

The configuration information acquisition unit 406 acquires configuration information based on the network information. The configuration information means information including the host name of the device 20 and the like. For example, the configuration information acquisition unit 406 transmits a configuration information request signal to the IP address of the device 20 via the management device communication unit 401. Here, it is assumed that the presence / absence information of the device 20 is previously confirmed as “present”. When the device 20 receives the configuration information request signal, the device 20 transmits the configuration information to the device management apparatus 40.

The configuration information management database 407 stores device specific information in association with network information. Specifically, the configuration information management database 407 stores a configuration information management table in which device specific information is associated with network information. Furthermore, the configuration information management table may include the date and time when the configuration information management database is updated, and the last update date and time of the configuration information management database 407.

FIG. 6 is a diagram illustrating an example of the configuration information management table. In the case of FIG. 6, the devices 20 are “server machine A”, “client PC”, “printer”, “switch”, “router”, and “server machine B”. In the case of FIG. 6, the configuration information management table indicates a correspondence relationship between “IP address”, “host name”, “confirmation date / time”, “last update date / time”, and “MAC address”. However, FIG. 6 is not intended to limit the configuration information management table to the information shown in FIG.

For example, it is assumed that the network information acquisition unit 402 acquires the IP addresses of “server machine A”, “client PC”, “printer”, “switch”, “router”, and “server machine B”. In that case, the device specific information acquisition unit 403 acquires the MAC addresses of the devices 20 based on the IP address. Furthermore, it is assumed that the configuration information acquisition unit 406 acquires the host names of those devices 20 as configuration information. In that case, as illustrated in FIG. 6, the configuration information acquisition unit 406 generates a configuration information management table.

The device related information acquisition unit 408 acquires device related information from the device related information server 30 based on the device specific information. For example, the device related information acquisition unit 408 may acquire maintenance contract information from the device related information server 30 based on the device specific information.

The device-related information management database 409 stores device-specific information in association with device-related information. For example, the device-related information management database 409 may store device-specific information in association with maintenance contract information. Specifically, the device related information management database 409 may store a device related information management table in which device specific information is associated with maintenance contract information. Further, the device-related information management table may include a confirmation date and time of update of the device-related information management database 409 and a last update date and time of the device-related information management database 409.

FIG. 7 is a diagram illustrating an example of a device-related information management table. In the case of FIG. 7, the devices 20 are “server machine A”, “client PC”, “printer”, “switch”, “router”, and “server machine B”. In the case of FIG. 7, the device-related information management table includes “user name”, “device code”, “device identification number”, “maintenance contract information”, “confirmation date”, “last update date”, “MAC address”. "Is shown. However, FIG. 7 is not intended to limit the device-related information management table to the information shown in FIG.

For example, it is assumed that the network information acquisition unit 402 acquires the IP addresses of “server machine A”, “client PC”, “printer”, “switch”, “router”, and “server machine B”. In that case, the device specific information acquisition unit 403 acquires the MAC addresses of the devices 20 based on the IP address. Then, the device related information acquisition unit 408 extracts maintenance contract information from the device related information database 302 using the MAC address as a key.

However, it is assumed that the maintenance contract information corresponding to the MAC address “00-22-22-22-22-22” of the client PC is not stored in the device related information database 302. In this case, the device-related information acquisition unit 408 acquires information “no maintenance contract” for the client PC.

Also, assume that the device-related information database 302 stores the maintenance contract information corresponding to the printer MAC address “00-33-33-33-33-33” at least once. Specifically, it is assumed that the device-related information acquisition unit 408 has acquired “user name”, “device identification number”, and “maintenance contract information” for the printer. However, after that, it is assumed that the printer maintenance contract is terminated. In this case, as illustrated in FIG. 7, the device-related information acquisition unit 408 updates the device-related information management table as “no maintenance contract” for the printer.

FIG. 8 is a diagram illustrating an example of information stored in the presence / absence information management database 405, the configuration information management database 407, and the device related information management database 409. As shown in FIG. 8, each database stores a common MAC address 501 for each device 20. Therefore, the device management apparatus 40 can associate information stored in each database with the MAC address 501 as a key.

Here, it is assumed that the presence / absence information management database 405 stores the presence / absence information management table shown in FIG. The configuration information management database 407 stores the configuration information management table shown in FIG. The device-related information management database 409 stores the device-related information management table shown in FIG. In this case, for example, the device management apparatus 40 can associate “presence / absence information”, “host name”, and “maintenance contract information” with the MAC address as a key.

For example, referring to FIG. 5 and FIG. 6, the device 20 (server machine A) with the host name “server1” exists. Further, referring to FIG. 7, the maintenance contract information of the device 20 (server machine A) is “A12345678”.

6 and 7, the maintenance contract information of the device 20 (server machine B) with the host name “server2” is “A23459876”. That is, the device 20 (server machine B) with the host name “server2” is the management target device 21. Further, referring to FIGS. 5 and 7, there is no managed device 20 (server machine B) whose maintenance contract information is “A23459876”.

Alternatively, referring to FIGS. 5 to 7, there is a device 20 (client PC) with the host name “pc1”, but there is no maintenance contract information. That is, referring to FIGS. 5 to 7, there is a device 20 (client PC) with the host name “pc1”, but the device 20 is a device 22 other than the management target device.

Based on whether or not the first device specific information acquired by the device specific information acquisition unit 403 matches the second device specific information stored in the device related information management database 409, the state estimation unit 410 The state of the device 20 is estimated. In the following description, the above-described first device specific information is referred to as reception specific information. In the following description, the above-described second device specific information is referred to as storage specific information.

Specifically, when the state estimation unit 410 cannot acquire the reception specific information that matches the storage specific information and acquires information indicating that there is no maintenance contract from the device related information server 30, the state estimation unit 410 corresponds to the storage specific information. It is estimated that the device 20 has been removed. That is, the state estimation unit 410 estimates that the device 20 has been removed when the presence of the device 20 that has been confirmed to be present cannot be confirmed and there is no maintenance contract.

In addition, the state estimation unit 410 cannot acquire the reception unique information that matches the storage unique information, but if the maintenance contract information is stored, the state estimation unit 410 estimates that the device 20 corresponding to the storage unique information may be defective. .

The device management table generation unit 411 generates a device management table in which presence / absence information, device specific information, and device related information are associated with each other. For example, the device management table generation unit 411 may generate a device management table in which presence / absence information, device specific information, and maintenance contract information are associated with each other. Furthermore, the device management table may include configuration information and the last update date and time of the management table.

Next, the operation of the device management system 10 according to the present embodiment will be described. In the following description, device specific information is described as a MAC address. However, this is not intended to limit the device-specific information to the MAC address.

FIG. 9 is a flowchart showing an example of the operation of the device management apparatus 40.

In step S1, the device management apparatus 40 starts a management program. Then, the network information acquisition unit 402 transmits a PING signal to the broadcast address via the management device communication unit 401.

In step S2, the presence / absence information generation unit 404 determines the presence / absence of the device 20.

In step S3, the presence / absence information generation unit 404 determines whether one or more devices 20 are present. If one or more devices 20 are present (Yes branch in step S3), the process proceeds to step S4. If the device 20 does not exist (No branch in step S3), the process proceeds to step S2 and the process is continued. In addition, you may transfer to step 2 after predetermined time (for example, 1 day) progress. That is, after a predetermined time has elapsed, the presence / absence information generation unit 404 may determine the presence / absence of the device 20 again.

In step S4, the device specific information acquisition unit 403 acquires the MAC address of the device 20. Specifically, the device specific information acquisition unit 403 accesses the device 20 and acquires the MAC address based on the network information.

In step S5, the presence / absence information generation unit 404 adds the presence / absence information to the presence / absence information management database 405. Details will be described later with reference to FIG.

In step S6, the configuration information acquisition unit 406 acquires the configuration information of the device 20. Specifically, the configuration information acquisition unit 406 accesses the device 20 and acquires the host name and the like of the device 20 as configuration information. Details will be described later with reference to FIG.

In step S7, the configuration information acquisition unit 406 adds the configuration information to the configuration information management database 407. Specifically, the configuration information acquisition unit 406 updates the configuration information management database 407 based on the acquired configuration information. Details will be described later with reference to FIG.

In step S8, the device related information acquisition unit 408 acquires maintenance contract information from the device related information server 30. Specifically, the device related information acquisition unit 408 acquires maintenance contract information regarding the device 20 whose existence has been confirmed from the device related information server 30. Details will be described later with reference to FIG.

In step S9, when there is updated maintenance contract information, the device related information acquisition unit 408 updates the device related information management database 409 based on the updated maintenance contract information. Details will be described later with reference to FIG. And it changes to step S601 shown in FIG.

FIG. 10 is a flowchart showing an example of processing for adding presence / absence information to the presence / absence information management database 405. That is, FIG. 10 is a flowchart showing details of the process in step S5 shown in FIG.

In step S101, the storage unit stores the IP address, MAC address, and response date and time of the device 20 that has responded in the storage unit.

In step S102, the presence / absence information generation unit 404 determines whether or not the MAC address stored in the storage unit in step S101 exists in the presence / absence information management database 405. When the MAC address saved in the storage unit in step S101 exists in the presence / absence information management database 405 (Yes branch in step S102), the process proceeds to step S103. On the other hand, when the MAC address stored in the storage unit in step S101 does not exist in the presence / absence information management database 405 (No branch in step S102), the process proceeds to step S104.

In step S103, the presence / absence information generation unit 404 updates the presence / absence information management database 405 based on the information stored in the storage unit. And it changes to step S105.

For example, assume that the network information acquisition unit 402 has acquired “192.168.1.20” as the IP address corresponding to the MAC address “00-11-11-11-11-11”. However, it is assumed that the presence / absence information management database 405 stores “10.0.0.0” as the IP address corresponding to the MAC address “00-11-11-11-11-11”. In this case, the presence / absence information generation unit 404 sets the IP address corresponding to the MAC address “00-11-11-11-11-11” stored in the presence / absence information management database 405 to “192.168.1.20”. Update. Regardless of whether or not the update is made, the presence / absence information generation unit 404 updates the confirmation date / time of the presence / absence information management database 405.

On the other hand, in step S104, the presence / absence information generation unit 404 newly registers the device 20 in the presence / absence information management database 405. And it changes to step S105.

In step S105, the presence / absence information generation unit 404 determines whether or not the information of all devices 20 whose presence / absence information is “Yes” has been updated. When the information of all the devices 20 whose presence / absence information is “present” is updated (Yes branch in step S105), the process proceeds to “A” (step S107) illustrated in FIG. On the other hand, when the information on all the devices 20 whose presence / absence information is “present” has not been updated (No branch in step S105), the process proceeds to step S106.

In step S106, the presence / absence information generation unit 404 updates the presence / absence information to “none” for the device 20 whose presence / absence information is “present” and whose existence could not be confirmed. And it changes to "A" (step S107) shown in FIG.

When the process proceeds to step S107, the process proceeds to step S201 shown in FIG.

FIG. 11 is a flowchart illustrating an example of processing for acquiring configuration information of the device 20. That is, FIG. 11 is a flowchart showing details of step S6 shown in FIG.

In step S201, the configuration information acquisition unit 406 determines whether there is a device 20 with presence / absence information “present”. If there is a device 20 whose presence / absence information is “present” (Yes branch in step S201), the process proceeds to step S202. On the other hand, when there is no device 20 with presence / absence information “Yes” (No branch in step S201), the process proceeds to “B” (step S205) shown in FIG.

In step S202, the management apparatus communication unit 401 transmits a signal requesting configuration information to the device 20 whose presence / absence information is “present”.

In step S203, the device 20 that has received the signal requesting the configuration information acquires the configuration information. Specifically, the device 20 acquires information such as the host name of the device itself.

In step S204, the device 20 transmits configuration information to the device management apparatus 40. And it changes to "B" (step 205) shown in FIG.

When the process proceeds to step S205, the process proceeds to step S301 shown in FIG.

FIG. 12 is a flowchart showing an example of processing for adding configuration information to the configuration information management database 407. That is, FIG. 12 is a flowchart showing details of step S7 shown in FIG. In the following description, the configuration information acquired by the configuration information acquisition unit 406 is referred to as reception configuration information. In the following description, the configuration information stored in the configuration information management database 407 is referred to as storage configuration information.

In step S301, the configuration information acquisition unit 406 determines whether a MAC address that matches the MAC address corresponding to the received configuration information exists in the configuration information management database 407. If a matching MAC address exists in the configuration information management database 407 (Yes branch in step S301), the process proceeds to step S304. On the other hand, when the matching MAC address does not exist in the configuration information management database 407 (No branch in step S301), the process proceeds to step S302.

In step S302, the configuration information acquisition unit 406 newly registers the device 20 in the configuration information management database 407.

In step S303, the date and time when the device 20 is registered is set as the confirmation date and time and the last update date and time. And it changes to "C" (step S308) shown in FIG.

On the other hand, in step S304, the configuration information acquisition unit 406 determines whether or not the received configuration information matches the storage configuration information.

If the received configuration information matches the storage configuration information (Yes branch in step S304), the configuration information acquisition unit 406 updates the confirmation date of the storage configuration information (step S305).

If the received configuration information does not match the stored configuration information (No branch in step S304), the configuration information acquisition unit 406 updates the stored configuration information to the received configuration information (step S306). Then, the configuration information acquisition unit 406 updates the confirmation date / time and the last update date / time of the configuration information management database 407 (step S307).

For example, assume that the configuration information acquisition unit 406 acquires “server1” as the host name corresponding to the MAC address “00-11-11-11-11-11”. However, it is assumed that the configuration information management database 407 stores “server10” as the host name corresponding to the MAC address “00-11-11-11-11-11”. In this case, the configuration information acquisition unit 406 updates the host name corresponding to the MAC address “00-11-11-11-11-11” to “server1”.

When the process proceeds to step S308, the process proceeds to step S401 shown in FIG.

FIG. 13 is a flowchart illustrating an example of processing for acquiring maintenance contract information from the device-related information server 30. That is, FIG. 13 is a flowchart showing details of step S8 shown in FIG.

In step S401, the management apparatus communication unit 401 transmits a request signal for maintenance contract information and a MAC address as a key to the device related information server 30.

In step S402, the device-related information server 30 determines whether or not maintenance contract information corresponding to the received MAC address exists in the device-related information database 302. That is, the device related information server 30 determines whether or not the device 20 corresponding to the received MAC address is a management target.

If the maintenance contract information exists (Yes branch in step S402), the device-related information server communication unit 301 transmits the maintenance contract information corresponding to the received MAC address to the device management apparatus 40 (step S403). On the other hand, when the maintenance contract information does not exist (No branch in step S402), the device related information server communication unit 301 responds to the device management apparatus 40 with “no maintenance contract” (step S404). And it changes to "D" (step S405) shown in FIG.

When the process proceeds to step S405, the process proceeds to step S501 shown in FIG.

FIG. 14 is a flowchart showing an example of processing for adding maintenance contract information to the device-related information management database 409. That is, FIG. 14 is a flowchart showing details of step S9 shown in FIG. In the following description, the maintenance contract information acquired by the device related information acquisition unit 408 is referred to as reception contract information. On the other hand, the maintenance contract information stored in the device related information management database 409 is referred to as storage contract information.

In step S501, the device related information acquisition unit 408 determines whether or not a MAC address that matches the MAC address corresponding to the reception contract information exists in the device related information management database 409.

If the MAC address corresponding to the MAC address corresponding to the reception contract information is present in the device related information management database 409 (Yes branch in step S501), the process proceeds to step S504. On the other hand, if the MAC address that matches the MAC address corresponding to the reception contract information does not exist in the device-related information management database 409 (No branch in step S501), the process proceeds to step S502.

In step S502, the device-related information acquisition unit 408 newly registers the device 20 in the device-related information management database 409.

In step S503, the device related information acquisition unit 408 sets the date and time when the device 20 is registered as the confirmation date and time and the last update date and time. And it changes to "E" (step S508) shown in FIG.

On the other hand, in step S504, the device related information acquisition unit 408 determines whether or not the reception contract information matches the storage contract information. When the reception contract information matches the storage contract information (Yes branch in step S504), the device related information acquisition unit 408 updates the confirmation date of the storage contract information (step S505). And it changes to "E" (step S508) shown in FIG.

If the received contract information does not match the stored contract information (No branch of step S504), the device related information acquisition unit 408 updates the stored contract information to the received contract information (step S506). Then, the device-related information acquisition unit 408 updates the confirmation date and time and the last update date and time of the device-related information management database 409 (Step S507). And it changes to "E" (step S508) shown in FIG.

For example, it is assumed that the device-related information acquisition unit 408 acquires “A12345678” as the maintenance contract information corresponding to the MAC address “00-11-11-11-11-11”. However, it is assumed that the maintenance contract information management data database 409 stores “A11111111” as maintenance contract information corresponding to the MAC address “00-11-11-11-11-11”. In that case, the device-related information acquisition unit 408 updates the maintenance contract information corresponding to the MAC address “00-11-11-11-11-11” to “A12345678”.

When the process proceeds to step S508, the process proceeds to step S601 shown in FIG.

FIG. 15 is a flowchart showing an example of processing for generating and displaying a device management table.

In step S601, the state estimation unit 410 estimates the state of the device 20.

In step S602, the device management table generation unit 411 generates a device management table.

In step S603, the device management table generating unit 411 determines whether or not a predetermined time (for example, one day) has elapsed. When the predetermined time has elapsed (Yes branch in step S603), the process proceeds to “F” (step S607) illustrated in FIG. On the other hand, if the predetermined time has not elapsed (No branch in step S603), the process proceeds to step S604.

In step S604, the device management table generation unit 411 determines whether or not to display the device management table.

If it is determined that the device management table is to be displayed (Yes branch of step S604), the device management table generation unit 411 displays the device management table (step S605). For example, the device management table generation unit 411 may display the device management table on a display unit (not shown) of the device management apparatus 40. And it changes to "F" (step S607) shown in FIG.

On the other hand, if it is determined that the device management table is not displayed (No branch in step S604), it waits for a predetermined time (for example, one day) (step S606). And it changes to step S603 and continues a process.

When the process proceeds to step S607, the process proceeds to step S2 shown in FIG.

FIG. 16 is a diagram illustrating an example of a device management table. In the case of FIG. 16, the devices 20 are “server machine A”, “client PC”, “printer”, “switch”, “router”, and “server machine B”. In the case of FIG. 16, the device management table includes “presence / absence information”, “last update information”, “IP address”, “MAC address”, “user name”, “device code”, “device identification number”, “maintenance contract”. It shows the correspondence between “information” and “status of managed device”.

For example, in FIG. 16, the device identification number corresponding to the printer is “10002”. This indicates that the device-related information acquisition unit 408 has acquired the device identification number of the printer from the device-related information server 30 at least once. However, it is assumed that the presence / absence information generation unit 404 cannot confirm the presence of the printer thereafter. In addition, it is assumed that the device-related information acquisition unit 408 acquires information “no maintenance contract” for the printer. In that case, the state estimation unit 410 determines that the printer has been removed.

Also, for example, in FIG. 16, the device identification number corresponding to the server machine B is “10005”. This indicates that when the server machine B is registered in the device management table, the device-related information acquisition unit 408 can acquire the device identification number of the server machine B from the device-related information server 30. Further, the maintenance contract information corresponding to the server machine B is “A23459876”. However, it is assumed that the presence / absence information generation unit 404 cannot confirm the existence of the server machine B thereafter. In that case, the state estimation unit 410 determines that the server machine B may be out of order.

As described above, the first effect of the device management apparatus 40 according to the present embodiment is that the presence / absence of a device to be managed and device-related information such as maintenance contract information can be managed in association with each other. Therefore, in the device management apparatus 40 according to the present embodiment, an administrator or the like can easily acquire device-related information such as presence / absence of a management target device and maintenance contract information. Therefore, the device management apparatus 40 according to the present embodiment contributes to easily discriminating and managing managed devices.

The second effect of the device management apparatus 40 according to the present embodiment is that when the presence of a managed device cannot be confirmed, the state of the managed device can be estimated. Therefore, the device management apparatus 40 according to the present embodiment contributes to reducing time and labor for confirming the state of the management target device.

[Second Embodiment]
Next, the second embodiment will be described in more detail with reference to the drawings.

This embodiment is a form for generating and displaying a network configuration diagram of a management target device. In the description of the present embodiment, the description of the same parts as those in the first embodiment is omitted. Further, in the description of the present embodiment, the same components as those in the first embodiment are denoted by the same reference numerals, and the description thereof is omitted.

FIG. 17 is a block diagram illustrating an example of an internal configuration of the device management apparatus 40a according to the present embodiment. The difference between the device management apparatus 40 shown in FIG. 4 and the device management apparatus 40a shown in FIG. 17 is that a network configuration analysis unit 412 is provided.

The network configuration analysis unit 412 analyzes the network configuration of the device 20 based on the network information. Specifically, the network configuration analysis unit 412 analyzes the network configuration based on the IP address, subnet mask, default gateway, and the like.

Then, the network configuration analysis unit 412 generates network configuration information. The network configuration information is information indicating the connection relationship of the devices 20. For example, the network configuration information may be information expressing the connection relationship of the devices 20 in a hierarchical structure (for example, a tree structure).

Further, the network configuration analysis unit 412 may analyze the network configuration of the device 20 based on the device code and the network information. In this case, as shown in FIG. 19, the network configuration analysis unit 412 displays network information, device specific information, maintenance contract information, and the like of a predetermined device 20 based on a user operation on the display unit ( (Not shown) may be displayed.

Further, when the device 20 includes an ID lamp, the network configuration analysis unit 412 may display a button for selecting ON / OFF of the ID lamp on the display unit. Then, the management device communication unit 401 may transmit a signal for controlling on / off of the ID lamp of the device 20 to the device 20. When the device management apparatus 40 controls the on / off of the ID lamp, it becomes easy to notify the management target device 21 to the administrator or the like.

Next, the operation of the device management apparatus 40a according to this embodiment will be described.

FIG. 18 is a flowchart showing an example of processing for analyzing the network configuration.

In step S701, the network configuration analysis unit 412 extracts a network device based on the device code. Specifically, the network configuration analysis unit 412 identifies a network device such as a router or a switch among the devices 20 based on the device code. In step S702, the network configuration analysis unit 412 extracts the device 20 connected to the network device based on the IP address or the like. In step S703, the network configuration analysis unit 412 generates network configuration information. Thereafter, the network configuration analysis unit 412 may display the network configuration information on the display unit of the device management apparatus 40a.

FIG. 19 is a diagram showing an example of display of network configuration information. FIG. 19 is a diagram in which the network configuration analysis unit 412 displays the devices 20 in a tree structure based on the network configuration. Specifically, FIG. 19 illustrates the connection relationship of the devices 20 whose host names are “rooter1”, “switch1”, “server1”, “pc1”, “printer1”, and “server2” in a tree structure.

Further, FIG. 19 shows network information, device specific information, and maintenance contract information for the device 20 with the host name “server1”. As shown in FIG. 19, the network configuration analysis unit 412 displays the network configuration, so that an administrator or the like can easily grasp the device 20 that is the management target device 21 and its state.

As described above, the device management apparatus 40a according to the present embodiment analyzes the network configuration and displays the analysis result. Therefore, the device management apparatus 40a according to the present embodiment contributes to determining and managing managed devices more easily.

Furthermore, the device management apparatus 40a according to the present embodiment further contributes to reducing time and labor for confirming the state of the device to be managed by controlling the ID lamp.

[Third Embodiment]
Next, the third embodiment will be described in more detail with reference to the drawings.

This embodiment is a form in which a device management table, a network configuration analysis result, and the like are transmitted to a terminal owned by an administrator or the like. In the description of this embodiment, the description of the same parts as those in the above embodiment is omitted. Further, in the description of the present embodiment, the same components as those of the above-described embodiment are denoted by the same reference numerals, and the description thereof is omitted.

FIG. 20 is a diagram illustrating an example of the overall configuration of the device management system 10a according to the present embodiment. The difference between the device management system 10 shown in FIG. 2 and the device management system 10a shown in FIG. 20 is that a terminal 70 owned by the administrator 60 is included. 20 is not intended to limit the configuration of the device management system 10a to the configuration shown in FIG.

The terminal 70 owned by the administrator 60 is connected to the device management apparatus 40a via the network 52. That is, the management device communication unit 401 communicates with the terminal 70 owned by the administrator 60.

Then, the management apparatus communication unit 401 transmits at least one of the device management table and the network configuration information to the terminal 70. Therefore, the manager 60 can manage the device 20 from a remote place away from the device management apparatus 40a.

Further, the device management apparatus 40a may control the network configuration information displayed on the terminal 70 based on the operation of the administrator 60 on the terminal 70. Further, the management device communication unit 401 may receive an operation of the administrator 60 on the terminal 70. Then, the management device communication unit 401 may control the ID lamp of the device 20 based on the operation of the administrator 60 on the terminal 70.

Therefore, the device management apparatus 40a according to the present embodiment contributes to the management and the like of determining and managing the device to be managed more easily.

In the above-described embodiment, the device management apparatus has been described as an example in which information such as a device management table is transmitted to a terminal owned by one administrator. However, it goes without saying that the device management apparatus may transmit information to a plurality of terminals owned by a plurality of managers.

In the above-described embodiment, the presence / absence information management database, the network information management database, and the device related information management database are arranged in the device management apparatus. However, each database may be arranged in a device different from the device management device. In that case, the device management apparatus may access each database via a network.

Some or all of the above embodiments can be described as in the following forms, but are not limited to the following.

(Mode 1) As in the device management apparatus according to the first aspect.

(Mode 2) A mode 1 comprising: a presence / absence information management database for storing the device-specific information in association with the presence / absence information; and a device-related information management database for storing the device-specific information in association with the device-related information. The device management apparatus described in 1.

(Mode 3) Based on whether or not the first device specific information acquired by the device specific information acquisition unit and the second device specific information stored in the device related information management database match. The device management apparatus according to aspect 2, further comprising a state estimation unit that estimates the state of the device.

(Mode 4) A network information acquisition unit that acquires network information of one or more of the devices, and the presence information generation unit, when the network information acquisition unit can acquire the network information from the device, The device management apparatus according to any one of Embodiments 1 to 3, wherein it is determined that a device is present, and the network information acquisition unit determines that the device does not exist when the network information acquisition unit cannot acquire the network information from the device.

(Mode 5) The device management apparatus according to mode 4, further comprising a network configuration analysis unit that analyzes a network configuration of the device based on the network information.

(Mode 6) The device management apparatus according to mode 5, wherein the network configuration analysis unit analyzes a network configuration of the device based on a device code and the network information.

(Mode 7) The network configuration analysis unit generates network configuration information, the management device communication unit communicates with a terminal owned by an administrator, and the terminal has at least one of the device management table and network configuration information. The apparatus management apparatus of the form 5 or 6 which transmits the information.

(Mode 8) The device management apparatus according to any one of modes 4 to 7, wherein the network information includes an IP (Internet Protocol) address.

(Mode 9) The device management apparatus according to any one of modes 1 to 8, wherein the device specific information includes a MAC (Media Access Control) address.

(Mode 10) The device according to any one of modes 1 to 9, wherein, when the device includes an ID lamp, the management device communication unit transmits a signal for controlling on / off of the ID lamp to the device. Management device.

(Mode 11) As in the device management system according to the second aspect.

(Mode 12) The device management system according to mode 11, wherein the device management apparatus includes a device-related information acquisition unit that acquires the device-related information from the device-related information server based on the device-specific information.

(Mode 13) As in the device management method according to the third aspect.

(Mode 14) The mode according to mode 13, comprising: a step of storing the device specific information in association with the presence / absence information; and a device related information management step of storing the device specific information in association with the device related information. Device management method.

(Mode 15) Based on whether or not the first device specific information acquired in the device specific information acquisition step matches the second device specific information stored in the device related information management step And the apparatus management method of the form 14 including the state estimation process which estimates the state of the said apparatus.

(Mode 16) including a network information acquisition step of acquiring network information of one or more of the devices, and determining that the device exists when the network information is acquired from the device in the presence / absence information generation step. The device management method according to any one of forms 13 to 15, wherein when the network information is not acquired from the device, it is determined that the device does not exist.

(Mode 17) The device management method according to mode 16, further including a network configuration analysis step of analyzing a network configuration of the device based on the network information.

(Mode 18) The device management method according to mode 17, wherein in the network configuration analysis step, the network configuration of the device is analyzed based on a device code and the network information.

(Mode 19) In the network configuration analysis step, network configuration information is generated, in the management device communication step, communicates with a terminal owned by an administrator, and the terminal has at least one of the device management table and the network configuration information. The device management method according to claim 17 or 18, wherein the information is transmitted.

(Mode 20) The device management method according to any one of modes 13 to 19, wherein in the management device communication step, a signal for controlling on / off of the ID lamp of the device is transmitted to the device.

(Form 21) As in the program according to the fourth viewpoint.

(Mode 22) The mode according to mode 21, including: a process for storing the device-specific information in association with the presence information; and a device-related information management process for storing the device-specific information in association with the device-related information. program.

(Mode 23) Based on whether or not the first device unique information acquired in the device unique information acquisition process matches the second device unique information stored in the device related information management process The program according to mode 22, which executes state estimation processing for estimating the state of the device.

(Mode 24) When network information acquisition processing for acquiring network information of one or more of the devices is executed, and the network information is acquired from the device in the presence / absence information generation processing, it is determined that the device exists And when the said network information is not acquired from the said apparatus, the program as described in any one of the forms 21 thru | or 23 which determines with the said apparatus not existing.

(Mode 25) The program according to mode 24, which executes network configuration analysis processing for analyzing the network configuration of the device based on the network information.

(Mode 26) The program according to mode 25, wherein in the network configuration analysis process, the network configuration of the device is analyzed based on the device code and the network information.

(Mode 27) Generate network configuration information in the network configuration analysis processing, communicate with a terminal owned by an administrator in the management device communication processing, and send at least one of the device management table and network configuration information to the terminal The program according to 25 or 26, wherein the information is transmitted.

(Mode 28) The program according to any one of modes 21 to 27, wherein in the management device communication process, a signal for controlling on / off of the ID lamp of the device is transmitted to the device.

In addition, each disclosure of the above cited patent documents shall be incorporated herein by reference. Within the scope of the entire disclosure (including claims) of the present invention, the embodiments and examples can be changed and adjusted based on the basic technical concept. In addition, various combinations of various indication elements (including each element of each claim, each element of each embodiment or example, each element of each drawing, etc.) within the scope of the claims of the present invention, Selection is possible. That is, the present invention of course includes various variations and modifications that could be made by those skilled in the art according to the entire disclosure including the claims and the technical idea. In particular, with respect to the numerical ranges described in this document, any numerical value or small range included in the range should be construed as being specifically described even if there is no specific description.

10, 10a Device management system 20 Device 21 Device to be managed 22 Device 30 other than device to be managed 30 Device related information server 40, 40a, 100 Device management device 51, 52 Network 60 Administrator 70 Terminal 101, 401 Management device communication unit 102, 404 presence / absence information generation unit 103, 403 device specific information acquisition unit 104, 411 device management table generation unit 301 device-related information server communication unit 302 device-related information database 402 network information acquisition unit 405 presence / absence information management database 406 configuration information acquisition unit 407 Information management database 408 Device related information acquisition unit 409 Device related information management database 410 State estimation unit 412 Network configuration analysis unit 501 MAC address

Claims (10)

1. A management device communication unit that communicates with one or more devices;
   A presence / absence information generating unit that generates presence / absence information corresponding to each device based on whether communication with each device is possible;
   A device specific information acquisition unit for acquiring device specific information from the device;
   A device management table generating unit that generates a device management table in which the presence / absence information, the device-specific information, and the device-related information are associated with each other;
   A device management apparatus comprising:
2. A presence / absence information management database that stores the device-specific information in association with the presence / absence information;
   A device related information management database for storing the device specific information in association with the device related information;
   The device management apparatus according to claim 1.
3. Based on whether the first device specific information acquired by the device specific information acquisition unit matches the second device specific information stored in the device related information management database, the state of the device The apparatus management apparatus according to claim 2, further comprising a state estimation unit that estimates
4. A network information acquisition unit that acquires network information of one or more of the devices;
   The presence / absence information generation unit determines that the device exists when the network information acquisition unit can acquire the network information from the device, and the network information acquisition unit cannot acquire the network information from the device, The device management apparatus according to claim 1, wherein it is determined that the device does not exist.
5. The device management apparatus according to claim 4, further comprising a network configuration analysis unit that analyzes a network configuration of the device based on the network information.
6. The device management apparatus according to any one of claims 1 to 5, wherein the device specific information includes a MAC (Media Access Control) address.
7. One or more devices,
   A device related information server for managing device related information of the device;
   A device management apparatus for managing information on the device;
   A device management system including
   The device management apparatus
   One or more devices, and a management device communication unit that communicates with the device-related information server;
   A presence / absence information generating unit that generates presence / absence information corresponding to each device based on whether communication with each device is possible;
   A device specific information acquisition unit for acquiring device specific information from the device;
   A device management table generating unit that generates a device management table in which the presence / absence information, the device-specific information, and the device-related information are associated with each other;
   A device management system comprising:
8. The device management system according to claim 7, wherein the device management apparatus includes a device-related information acquisition unit that acquires the device-related information from the device-related information server based on the device-specific information.
9. A management device communication step for communicating with one or more devices;
   Presence / absence information generation step for generating presence / absence information corresponding to each device based on the availability of communication with each device;
   A device specific information acquisition step of acquiring device specific information from the device;
   Generating a device management table in which the presence / absence information, the device-specific information, and the device-related information are associated with each other;
   Device management method including
10. A program to be executed by a computer that controls the device management apparatus,
    Management device communication processing for communicating with one or more devices;
    Presence / absence information generation processing for generating presence / absence information corresponding to each device based on whether communication with each device is possible;
    Device specific information acquisition processing for acquiring device specific information from the device;
    Processing for generating a device management table in which the presence / absence information, the device-specific information, and device-related information are associated with each other;
    A program that executes.

Images