JP5810864B2 - DEVICE IDENTIFICATION DEVICE, DEVICE IDENTIFICATION SYSTEM, DEVICE IDENTIFICATION METHOD, DEVICE IDENTIFICATION PROGRAM, AND STORAGE MEDIUM - Google Patents

Description

  The present invention relates to a device identification device, a device identification system, a device identification method, a device identification program, and a storage medium.

  A technique for identifying a device connected to a network using a serial number registered in the device is known (for example, see Patent Document 1).

  However, the uniqueness of the serial number is usually not guaranteed unless the model and manufacturer are the same. There are also devices that cannot obtain serial numbers due to specifications. Therefore, in the conventional technology as described above, when various devices are connected to the network, such as when multiple models are connected to the network, or devices of multiple manufacturers are connected to the network. Identification may fail.

  The present invention has been made in view of the above circumstances, and even when various devices are connected to a network, a device identification device, a device identification system, and the like that can reduce device identification failures, An object is to provide a device identification method, a device identification program, and a storage medium.

  In order to solve the above-described problems and achieve the object, a device identification device according to one aspect of the present invention is a device identification device connected to a device via a network, and has at least one piece of identification information unique. Requesting the device for first identification information that is a plurality of pieces of identification information whose performance is not guaranteed, and obtaining non-acquisition information indicating that any one of the first pieces of identification information cannot be obtained is returned from the device. A request unit that requests the device for second identification information; and when the first identification information is returned to the request unit, the device is identified using the first identification information, and the request unit includes the first identification information. An identification unit that identifies the device using the second identification information when two identification information is returned.

  In addition, a device identification system according to another aspect of the present invention is a device identification system including a device identification device and a device connected to the device identification device via a network. The first identification information, which is a plurality of identification information whose uniqueness of the identification information is not guaranteed, is requested to the device, and the non-acquisition information indicating that any one of the first identification information cannot be acquired When a response is received from the device, a request unit that requests the device for second identification information, and when the first identification information is returned to the request unit, the device is identified using the first identification information, An identification unit that identifies the device using the second identification information when the second identification information is returned to the request unit, and the device receives the first identification information from the device identification device. Is requested, if the first identification information can be acquired, the first identification information is returned to the device identification device, and if any of the first identification information cannot be acquired, the acquisition is not possible. A response unit that responds information to the device identification device and responds to the device identification device with the second identification information when the second identification information is requested from the device identification device. .

  A device identification method according to another aspect of the present invention is a device identification method executed by a device identification device connected to a device via a network, wherein the request unit includes at least one piece of identification information unique. Requesting the device for first identification information that is a plurality of pieces of identification information whose performance is not guaranteed, and obtaining non-acquisition information indicating that any one of the first pieces of identification information cannot be obtained is returned from the device. Requesting the device for second identification information; and when the identification unit responds to the requesting unit with the first identification information, the identification unit identifies the device using the first identification information, and the request An identification step of identifying the device using the second identification information when the second identification information is returned to the unit.

  A device identification program according to another aspect of the present invention is for causing a computer to execute the device identification method.

  A storage medium according to another aspect of the present invention is a computer-readable medium storing the device identification program.

  According to the present invention, even when various devices are connected to the network, it is possible to reduce device identification failures.

FIG. 1 is a schematic diagram illustrating an example of a configuration of a device management system according to the present embodiment. FIG. 2 is a block diagram illustrating an example of the configuration of the device management apparatus according to the present embodiment. FIG. 3 is a diagram illustrating an example of a priority file according to the present embodiment. FIG. 4 is a diagram illustrating an example of information stored in the identification information storage unit of the device management apparatus according to the present embodiment. FIG. 5 is a block diagram illustrating an example of the configuration of the management target device according to the present embodiment. FIG. 6 is a diagram illustrating an example of information stored in the identification information storage unit of the management target device according to the present embodiment. FIG. 7 is a diagram illustrating an example of information stored in the identification information storage unit of the management target device according to the present embodiment. FIG. 8 is a diagram illustrating an example of information stored in the identification information storage unit of the management target device according to the present embodiment. FIG. 9 is a diagram illustrating an example of information stored in the identification information storage unit of the management target device according to the present embodiment. FIG. 10 is a flowchart illustrating an example of identification information registration processing executed in the device management system of the present embodiment. FIG. 11 is a flowchart illustrating an example of identification processing executed by the device management system of the present embodiment. FIG. 12 is a sequence diagram showing a specific example of identification processing executed in the device management system of the present embodiment. FIG. 13 is a sequence diagram illustrating a specific example of identification processing executed in the device management system of the present embodiment.

  Hereinafter, embodiments of a device identification device, a device identification system, a device identification method, a device identification program, and a storage medium according to the present invention will be described in detail with reference to the accompanying drawings. In the present embodiment, a case where the device identification system is applied to a device management system will be described as an example, but the present invention is not limited to this.

  First, the configuration of the device management system of this embodiment will be described.

  FIG. 1 is a schematic diagram illustrating an example of the configuration of the device management system 100 of the present embodiment. As illustrated in FIG. 1, the device management system 100 includes a device management device 200 (an example of a device identification device) and managed devices 300-1 to 300-4 (an example of a device).

  The device management apparatus 200 and the management target devices 300-1 to 300-4 are connected via the network 101. The network 101 only needs to connect the device management apparatus 200 and the management target devices 300-1 to 300-4 so that they can communicate with each other. For example, the network 101 can be realized by the Internet, a LAN (Local Area Network), or the like.

  The device management apparatus 200 is provided in a service center of a service providing company that provides device management services, and manages the management target devices 300-1 to 300-4 provided in the service base. However, the installation location of the device management apparatus 200 is not limited to the service center, and may be a service base or the like. The service base is an area in which managed devices are installed, and corresponds to, for example, a business office of a company that receives a device management service.

  The device management apparatus 200 can be realized by a PC (Personal Computer) in which a device management program and a device identification program are installed. The managed devices 300-1 to 300-4 may be electronic devices that can be connected to the network 101. For example, a printing device, a copier, a multifunction device, a scanner device, a facsimile device, a projector, a conference system, a PC, and the like. Is mentioned. The multifunction peripheral has at least two functions among a copying function, a printing function, a scanner function, and a facsimile function.

  In FIG. 1, the management target devices 300-1 to 300-3 that are printing apparatuses and the management target device 300-4 that is a PC are illustrated as the management target devices. However, the management target devices are not limited to these. is not. In addition, it is assumed that the devices to be managed 300-1 to 300-3 are different from each other. In addition, all the devices to be managed 300-1 to 300-4 may be provided at the same service base, or any of the devices may be provided at different service bases. In the following description, the management target devices 300-1 to 300-4 may be simply referred to as the management target device 300 when it is not necessary to distinguish them.

  FIG. 2 is a block diagram illustrating an example of the configuration of the device management apparatus 200 according to the present embodiment. As illustrated in FIG. 2, the device management apparatus 200 includes a communication unit 210, an operation unit 220, a display unit 230, a storage unit 240, and a control unit 250.

  The communication unit 210 communicates with the management target device 300 via the network 101 and can be realized by a communication device such as a communication interface.

  The operation unit 220 inputs various operations and can be realized by at least one of input devices such as a keyboard, a mouse, a touch pad, and a touch panel.

  The display unit 230 displays various screens and can be realized by a display device such as a liquid crystal display or a touch panel display.

  The storage unit 240 stores various programs such as a device management program and a device identification program executed by the device management apparatus 200, data used for various processes performed by the device management apparatus 200, and the like. The storage unit 240 is magnetic, optical, or electrical such as a hard disk drive (HDD), a solid state drive (SSD), a memory card, an optical disk, a read only memory (ROM), and a random access memory (RAM). This can be realized by at least one of the storage devices that can store the data.

  The storage unit 240 includes a priority file storage unit 241 and an identification information storage unit 243. Details of the priority file storage unit 241 and the identification information storage unit 243 will be described later.

  The control unit 250 controls each unit of the device management apparatus 200 and can be realized by a control device such as a CPU (Central Processing Unit). The control unit 250 includes a device management unit 251 and a device identification unit 253. Here, the control unit 250 activates (executes) the device management program and the device identification program stored in the storage unit 240, thereby realizing the device management unit 251 and the device identification unit 253 as software, respectively.

  The device management unit 251 requests the device identification unit 253 to identify whether the management target device 300 is a target device. Specifically, the device management unit 251 notifies the device identification unit 253 of the IP address and device name of the management target device 300 to be identified, and the management target of the device name notified by the management target device 300 of the notified IP address. A request is made to identify whether the device 300 (target device) or not.

  In addition, the device management unit 251 receives the identification result of the device identification unit 253, and manages the management target device 300 identified as the target device. Specifically, the device management unit 251 indicates that the identification result of the device identification unit 253 indicates that the management target device 300 having the notified IP address is the management target device 300 (target device) notified by the device name. Management information such as device information and failure information is acquired from the managed device 300 and managed on the storage unit 240.

  The device identification unit 253 identifies whether or not the management target device 300 is a target device, and includes a reception unit 254, a request unit 255, and an identification unit 256.

  The reception unit 254 receives an identification request from the device management unit 251 as to whether or not the management target device 300 is a target device. Specifically, the reception unit 254 receives the IP address and device name of the management target device 300 to be identified from the device management unit 251, and manages the device name notified of the management target device 300 of the notified IP address. An identification request as to whether or not the target device 300 (target device) is received is accepted.

  The requesting unit 255 requests the identification target management target device 300 for first identification information that is a plurality of pieces of identification information whose uniqueness is not guaranteed. Specifically, the request unit 255 requests the first identification information from the management target device 300 having the IP address received by the receiving unit 254.

  For example, a serial number corresponds to the identification information whose uniqueness is not guaranteed. The serial number is usually an identifier for identifying a device within the same model. Therefore, there is a possibility that the serial number will be duplicated if the model or manufacturer is different. As in this embodiment, when it is necessary to identify various managed devices of different models and manufacturers, the serial number cannot guarantee uniqueness.

  For this reason, in the present embodiment, the management target device 300 is requested for first identification information in which identification information whose uniqueness is not guaranteed and other identification information is combined, and the requested first identification information is sent to the management target device 300. Used for identification. This is because even if the identification information is not guaranteed to be unique, uniqueness can be expected by combining it with other identification information.

  The other identification information may be any information that can be identified, and may be identification information for which uniqueness is guaranteed, or identification information for which uniqueness is not guaranteed. In the present embodiment, the serial number is used for identification information whose uniqueness is not guaranteed, and the model name of the device is used for other identification information. However, the present invention is not limited to this. Since the device model name is an identifier for identifying the device model, uniqueness is not guaranteed.

  Further, when the non-acquisition information indicating that any one of the first identification information cannot be acquired is returned from the management target device 300, the request unit 255 requests the management target device 300 for the second identification information. To do. Specifically, when the non-acquisition information is returned from the management target device 300 having the IP address received by the reception unit 254, the request unit 255 requests the second identification information from the management target device 300.

  This is because some managed devices with different models and manufacturers cannot acquire identification information such as serial numbers depending on the specifications, so the managed device is identified because the identification information cannot be acquired. This is to prevent a situation where it is impossible to do so.

  The non-acquisition information may be any information as long as it is information indicating that any one of the first identification information cannot be acquired, for example, an error code.

  The second identification information only needs to be identification information different from the first identification information. For example, identification information that guarantees uniqueness or user setting information that is set in advance by the user is applicable. The identification information whose uniqueness is guaranteed corresponds to, for example, a MAC (Media Access Control) address. Since the MAC address is determined by the specification to be assigned to a NIC (Network Interface Card) without duplication, uniqueness is guaranteed. The user setting information corresponds to a comment character string set in advance by the user.

  The request unit 255 requests identification information from the management target device 300 in descending order of priority defined in a priority file described later. Therefore, if the priority of the first identification information is set higher than the priority of the second identification information in the priority file, the request unit 255 first sets the first identification information as the management target device as described above. If the first identification information is not responded to the management target device 300, the second identification information is requested to the management target device 300. On the other hand, if the priority of the second identification information is set higher than the priority of the first identification information in the priority file, the request unit 255 first sets the second identification information to the management target device 300, unlike the above. If the second identification information is not responded to, the management target device 300 is requested for the first identification information.

  Here, the priority file storage unit 241 will be described. The priority file storage unit 241 stores a priority file that defines the priority of the first identification information and the priority of the second identification information. In the priority file, it is preferable to set the priority of identification information having high reliability in identification to a high priority. In this embodiment, the priority of the first identification information is set higher than the priority of the second identification information. doing.

  FIG. 3 is a diagram illustrating an example of a priority file according to the present embodiment. In the example shown in FIG. 3, the priority file is an XML (Extensible Markup Language) format file, and the priority is defined in XML. In the example shown in FIG. 3, the priority of the serial number / model name pair (an example of the first identification information) is “1”, and the priority of the MAC address (an example of the second identification information) is “2”. The priority of the serial number / model name pair is higher than the priority of the MAC address.

  The NIC to which the MAC address is assigned can be easily replaced especially in the case of a PC. Therefore, if the MAC address is used for the identification information, there is a possibility that misidentification will occur due to the NIC being replaced. For this reason, in this embodiment, the priority of the serial number / model name pair is set higher than the priority of the MAC address.

  Here, the identification information storage unit 243 will be described. The identification information storage unit 243 stores at least one of first identification information and second identification information for each managed device. The identification information stored in the identification information storage unit 243 is acquired in advance from the management target device 300 and registered. Registration of identification information in the identification information storage unit 243 will be described later. The identification information storage unit 243 may be a database external to the device management apparatus 200.

  FIG. 4 is a diagram illustrating an example of information stored in the identification information storage unit 243 of the present embodiment. In the example illustrated in FIG. 4, the identification information storage unit 243 stores a table in which the device name of the management target device 300 is associated with the identification information in a file format. Here, the device name of the management target device 300-1 is “D”, the device name of the management target device 300-2 is “E”, the device name of the management target device 300-3 is “F”, and the management target device 300- It is assumed that the device name 4 is “G”, but the present invention is not limited to this.

  The device name “D” is associated with the serial number “S12345” and the model name “AAA model D” as identification information (first identification information). The device name “E” is associated with the serial number “S12345” and the model name “BBB model E” as identification information (first identification information). The device name “F” is associated with the model name “CCC model F” as identification information (part of the first identification information), and the MAC address “CC” as identification information (second identification information). : CC: CC: 00: 00: 01 ". The device name “G” is associated with MAC address “DD: DD: DD: 00: 00: 02” as identification information (second identification information).

  In the example shown in FIG. 4, the serial numbers of the management target device 300-1 (device name “D”) and the management target device 300-2 (device name “E”) are the same, but the model names are different from each other. Therefore, the management target device 300-1 and the management target device 300-2 can be identified as different devices by combining the serial number with the model name and using it for identification.

  When the first identification information is responded to the request unit 255, the identification unit 256 identifies the management target device 300 using the first identification information. When the second identification information is returned to the request unit 255, the identification unit 256 The managed device 300 is identified using the second identification information.

  Specifically, when the first identification information is returned to the request unit 255, the identification unit 256 receives the first identification information of the management target device 300 with the device name received by the reception unit 254 from the identification information storage unit 243. It is determined whether or not the first identification information acquired and responded to the request unit 255 matches the first identification information acquired from the identification information storage unit 243. In the present embodiment, the identification unit 256 determines whether the serial number and model name responded to the request unit 255 match the serial number and model name acquired from the identification information storage unit 243, respectively. When the first identification information matches, the identification unit 256 uses the management target device 300 having the IP name received by the reception unit 254 as the management target device 300 (target device) having the device name received by the reception unit 254. The device management unit 251 is notified of the identification result indicating that it is present.

  Similarly, when the second identification information is returned to the request unit 255, the identification unit 256 acquires the second identification information of the management target device 300 having the device name received by the receiving unit 254 from the identification information storage unit 243. Then, it is determined whether or not the second identification information responded to the request unit 255 matches the second identification information acquired from the identification information storage unit 243. In the present embodiment, the identification unit 256 determines whether or not the MAC address responded to the request unit 255 matches the MAC address acquired from the identification information storage unit 243. When the second identification information matches, the identification unit 256 uses the management target device 300 (target device) having the device name received by the reception unit 254 as the management target device 300 having the IP address received by the reception unit 254. The device management unit 251 is notified of the identification result indicating that it is present.

  Note that the device management apparatus 200 does not have to have all the above-described units as essential configurations, and may be configured such that some of them are omitted.

  FIG. 5 is a block diagram illustrating an example of the configuration of the management target device 300 according to the present embodiment. As illustrated in FIG. 5, the management target device 300 includes a communication unit 310, an operation unit 320, a display unit 330, a storage unit 340, and a control unit 350.

  The communication unit 310 communicates with the device management apparatus 200 via the network 101 and can be realized by a communication apparatus such as a communication interface.

  The operation unit 320 inputs various operations, and can be realized by at least one of input devices such as a keyboard, a mouse, a touch pad, and a touch panel.

  The display unit 330 displays various screens and can be realized by a display device such as a liquid crystal display or a touch panel display.

  The storage unit 340 stores various programs executed by the management target device 300, data used for various processes performed by the management target device 300, and the like. The storage unit 340 is, for example, magnetic, optical, or electrical such as an HDD (Hard Disk Drive), an SSD (Solid State Drive), a memory card, an optical disk, a ROM (Read Only Memory), and a RAM (Random Access Memory). This can be realized by at least one of the storage devices that can store the data.

  The storage unit 340 includes an identification information storage unit 341. Details of the identification information storage unit 341 will be described later.

  The control unit 350 controls each unit of the management target device 300 and can be realized by a control device such as a CPU (Central Processing Unit). Control unit 350 includes a response unit 351.

  Here, the identification information storage unit 341 will be described. The identification information storage unit 341 stores at least one of its own first identification information and second identification information.

  FIG. 6 is a diagram illustrating an example of information stored in the identification information storage unit 341 of the management target device 300-1 according to the present embodiment. In the example illustrated in FIG. 6, the identification information storage unit 341 stores a serial number “S12345” and a model name “AAA model D” as identification information (first identification information).

  FIG. 7 is a diagram illustrating an example of information stored in the identification information storage unit 341 of the management target device 300-2 according to the present embodiment. In the example illustrated in FIG. 7, the identification information storage unit 341 stores a serial number “S12345” and a model name “BBB model E” as identification information (first identification information).

  FIG. 8 is a diagram illustrating an example of information stored in the identification information storage unit 341 of the management target device 300-3 according to the present embodiment. In the example illustrated in FIG. 8, the identification information storage unit 341 stores the model name “CCC model F” as the identification information (part of the first identification information) and also as the identification information (second identification information). MAC address “CC: CC: CC: 00: 00: 01” is stored. Here, the management target device 300-3 does not store the serial number in the identification information storage unit 341. This is because the management target device 300-3 does not support acquisition of the serial number according to the specification. . However, the management target device 300-3 may store the serial number in a storage area of the storage unit 340 that cannot be accessed by a vendor or the like (an area that cannot be accessed by a response unit 351 described later).

  FIG. 9 is a diagram illustrating an example of information stored in the identification information storage unit 341 of the management target device 300-4 according to the present embodiment. In the example illustrated in FIG. 9, the identification information storage unit 341 stores a MAC address “DD: DD: DD: 00: 00: 02” as identification information (second identification information). The reason why the management target device 300-4 does not store the serial number in the identification information storage unit 341 is the same as that of the management target device 300-3.

  When the first identification information is requested from the device management apparatus 200, the response unit 351 responds to the device management apparatus 200 with the first identification information and can obtain the first identification information. If any of the identification information cannot be acquired, the non-acquisition information is returned to the device management apparatus 200.

  Specifically, when the first identification information is requested from the device management apparatus 200, the response unit 351 confirms whether or not the first identification information is stored in the identification information storage unit 341, and the first identification information is stored. If the identification information is stored, the first identification information is acquired and transmitted to the device management apparatus 200. On the other hand, if any identification information of the first identification information is not stored in the identification information storage unit 341, the response unit 351 transmits the unacceptable information to the device management apparatus 200.

  Further, when the device management apparatus 200 requests the second identification information, the response unit 351 responds to the device management apparatus 200 with the second identification information. Specifically, when the second identification information is requested from the device management apparatus 200, the response unit 351 acquires the second identification information from the identification information storage unit 341 and transmits the second identification information to the device management apparatus 200.

  Note that the management target device 300 does not have to have all the above-described components as essential configurations, and may be configured such that some of them are omitted.

  Next, the operation of the device management system of this embodiment will be described.

  FIG. 10 is a flowchart illustrating an example of identification information registration processing executed by the device management system 100 according to the present embodiment. The process illustrated in FIG. 10 is a process of registering identification information in the identification information storage unit 243, and is performed in advance before executing the identification process of the management target device 300.

  The reception unit 254 receives the IP address and device name of the management target device 300 to be registered from the device management unit 251, and receives the identification information of the management target device 300 of the notified IP address as the management target of the notified device name. A registration request for registration as identification information of the device 300 is accepted.

  Upon receiving this registration request, the request unit 255 requests the first identification information from the management target device 300 having the IP address received by the receiving unit 254 (step S100).

  When the first identification information is returned to the request unit 255 (Yes in step S102), the identification unit 256 associates the device name received by the reception unit 254 with the returned first identification information, and manages the device management apparatus. It is stored in the identification information storage unit 243 of 200 (step S104).

  On the other hand, when the first identification information is not responded to the request unit 255 (No in step S102), that is, when the non-acquisition information is responded to the request unit 255, the request unit 255 is received by the receiving unit 254. The second identification information is requested to the management target device 300 of the IP address (step S106).

  When the second identification information is returned to the request unit 255 (Yes in step S108), the identification unit 256 associates the device name received by the reception unit 254 with the returned second identification information and stores the identification information. The data is stored in the unit 243 (step S110).

  On the other hand, if the second identification information is not responded to the request unit 255 (No in step S108), the process ends.

  FIG. 11 is a flowchart illustrating an example of identification processing executed by the device management system 100 according to the present embodiment.

  The reception unit 254 receives the IP address and device name of the management target device 300 to be identified from the device management unit 251, and the management target device 300 of the device name to which the management target device 300 of the notified IP address is notified (purpose) The device receives a request for identifying whether the device is a device.

  Upon receiving this identification request, the request unit 255 requests the first identification information from the management target device 300 having the IP address received by the receiving unit 254 (step S200).

  When the first identification information is returned to the request unit 255 (Yes in step S202), the identification unit 256 is received by the reception unit 254 from the identification information stored (stored) in the identification information storage unit 243. The first identification information of the management target device 300 having the device name is acquired, and it is determined whether or not the first identification information responded to the request unit 255 matches the first identification information acquired from the identification information storage unit 243. (Step S204).

  When both the first identification information matches (Yes in step S204), the identification unit 256 determines that the management target device 300 of the IP address received by the reception unit 254 is the management target device 300 of the device name received by the reception unit 254. It identifies that it is a (target device) (step S206), and notifies the device management unit 251 of an identification result indicating that.

  On the other hand, when the first identification information does not match (No in step S204), the identification unit 256 manages the device name managed by the receiving unit 254 of the management target device 300 having the IP address received by the receiving unit 254. It identifies that it is not the apparatus 300 (target apparatus) (step S208), and notifies the apparatus management part 251 of the identification result which shows that.

  In addition, when the first identification information is not responded to the request unit 255 (No in step S202), that is, when the non-acquisition information is responded to the request unit 255, the request unit 255 is received by the receiving unit 254. The second identification information is requested to the management target device 300 of the IP address (step S210).

  When the second identification information is not responded to the request unit 255 (No in step S212), the identification unit 256 receives the device name from which the management target device 300 having the IP address received by the reception unit 254 is received by the reception unit 254. The device management unit 251 is notified of an identification result indicating that it is not possible to identify whether or not the device is a management target device 300 (target device) (step S214).

  On the other hand, when the second identification information is responded to the request unit 255 (Yes in step S212), the identification unit 256 is received from the identification information stored (stored) in the identification information storage unit 243 by the receiving unit 254. Whether or not the second identification information of the management target device 300 having the accepted device name is acquired, and the second identification information returned from the request unit 255 matches the second identification information acquired from the identification information storage unit 243. Is determined (step S216).

  When the two pieces of second identification information match (Yes in step S216), the identification unit 256 determines that the management target device 300 having the IP address received by the reception unit 254 is the management target device 300 having the device name received by the reception unit 254. It identifies that it is a (target device) (step S206), and notifies the device management unit 251 of an identification result indicating that.

  On the other hand, when the two pieces of second identification information do not match (No in step S216), the identification unit 256 manages the device name management target device 300 having the IP address received by the reception unit 254 received by the reception unit 254. It identifies that it is not the apparatus 300 (target apparatus) (step S208), and notifies the apparatus management part 251 of the identification result which shows that.

  FIG. 12 is a sequence diagram illustrating a specific example of identification processing executed by the device management system 100 according to the present embodiment, and illustrates an identification example of the management target device 300-3.

  First, the device management unit 251 notifies the device identification unit 253 of the IP address “192.168.1.2” and the device name “F” of the management target device 300-3 to be identified, and manages the notified IP address. A request is made to identify whether or not the device name of the target device 300-3 is “F” (step S300).

  When the device identification unit 253 (reception unit 254) accepts this identification request, the device identification unit 253 (request unit 255) reads the priority file (see FIG. 3) from the priority file storage unit 241, and stores the identification information. It is ascertained that the requested order is the order of serial number / model name pair and MAC address (step S302).

  Subsequently, the device identification unit 253 (request unit 255) requests a serial number from the management target device 300-3 having the IP address “192.168.1.2” (step S304).

  Subsequently, the management target device 300-3 (the response unit 351) checks whether or not the serial number is stored in the identification information storage unit 341 (see FIG. 8), and the serial number is not stored. Inappropriate information is returned to the device management apparatus 200 (step S306).

  Subsequently, the device identification unit 253 (request unit 255) requests the MAC address from the management target device 300-3 having the IP address “192.168.1.2” because the non-acquisition information has been returned (step S308). ).

  Subsequently, the management target device 300-3 (the response unit 351) checks whether or not the MAC address is stored in the identification information storage unit 341 (see FIG. 8), and the MAC address is stored. The MAC address “CC: CC: CC: 00: 00: 01” is acquired from the information storage unit 341 and responds to the device management apparatus 200 (step S310).

  Subsequently, when the MAC address is returned to the device identification unit 253 (requesting unit 255), the device identification unit 253 (identification unit 256) receives the device name “F” from the identification information storage unit 243 (see FIG. 4). The MAC address “CC: CC: CC: 00: 00: 01” of the managed device is read (step S312). Then, the device identification unit 253 (identification unit 256) compares both the MAC address of the returned MAC address and the read MAC address (step S314), both of which are “CC: CC: CC: 00: 00: 01”. ", It is determined that they match (step S316).

  Subsequently, the device identification unit 253 (identification unit 256) determines that the device name of the management target device 300-3 with the IP address “192.168.1.2” is “F” because both MAC addresses match. As an identification result, the device management unit 251 is notified that the device name of the management target device 300-3 with the IP address “192.168.1.2” is “F” (step S318).

  FIG. 13 is a sequence diagram illustrating a specific example of identification processing executed by the device management system 100 of the present embodiment, and illustrates an identification example of the management target device 300-1.

  First, the device management unit 251 notifies the device identification unit 253 of the IP address “192.168.1.1” and the device name “D” of the management target device 300-1 to be identified, and manages the notified IP address. A request is made to identify whether or not the device name of the target device 300-1 is “D” (step S400).

  When the device identification unit 253 (reception unit 254) accepts this identification request, the device identification unit 253 (request unit 255) reads the priority file (see FIG. 3) from the priority file storage unit 241, and stores the identification information. It is ascertained that the requested order is the order of serial number / model name pair and MAC address (step S402).

  Subsequently, the device identification unit 253 (request unit 255) requests a serial number from the management target device 300-1 having the IP address “192.168.1.1” (step S404).

  Subsequently, the management target device 300-1 (response unit 351) confirms whether or not the serial number is stored in the identification information storage unit 341 (see FIG. 6), and the serial number is stored. The serial number “S12345” is acquired from the information storage unit 341 and responds to the device management apparatus 200 (step S406).

  Subsequently, when the serial number is returned to the device identification unit 253 (request unit 255), the device identification unit 253 (identification unit 256) receives the device name “D” from the identification information storage unit 243 (see FIG. 4). The serial number “S12345” of the management target device is read (step S408). Then, the device identification unit 253 (identification unit 256) compares the serial numbers of the response serial number and the read serial number (step S410), and since both are “S12345”, it is determined that they match (step S410). Step S412).

  Subsequently, since the serial numbers match, the device identification unit 253 (request unit 255) requests a model name from the management target device 300-1 having the IP address “192.168.1.1” (step S414).

  Subsequently, the management target device 300-1 (the response unit 351) checks whether or not the model name is stored in the identification information storage unit 341 (see FIG. 6), and the model name is stored. The model name “AAA model D” is acquired from the information storage unit 341 and responds to the device management apparatus 200 (step S416).

  Subsequently, when the model name is returned to the device identification unit 253 (request unit 255), the device identification unit 253 (identification unit 256) receives the device name “D” from the identification information storage unit 243 (see FIG. 4). The model name “AAA model D” of the management target device is read (step S418). Then, the device identification unit 253 (identification unit 256) compares both the model name of the response model name and the read model name (step S420), and determines that they match because both are “AAA model D”. (Step S422).

  Subsequently, the device identification unit 253 (identification unit 256) determines that the device name of the management target device 300-1 having the IP address “192.168.1.1” is “D” because both model names match. As a result of the identification, the device management unit 251 is notified that the device name of the management target device 300-1 having the IP address “192.168.1.1” is “D” (step S424).

  As described above, in the present embodiment, the management target device is identified using the first identification information obtained by combining identification information whose uniqueness is not guaranteed and other identification information. Therefore, according to the present embodiment, even when various devices are connected to the network, such as when multiple models are connected to the network, or devices of multiple manufacturers are connected to the network. Therefore, it can be expected to uniquely identify a device, and failure of device identification can be reduced.

  In the present embodiment, if any of the first identification information cannot be acquired in the management target device, the second identification information is acquired to identify the management target device. For this reason, according to the present embodiment, even when there is identification information that cannot be acquired due to the specification, it is possible to prevent a situation in which the managed device cannot be identified because the identification information cannot be acquired. .

  In the present embodiment, the identification information with higher reliability in identification has a higher priority, and the identification information is requested from the management target device in the order of the identification information with the higher priority. For this reason, according to the present embodiment, identification information with high reliability in identification can be preferentially used for identifying managed devices.

  In this embodiment, a general-purpose device management technique such as using MIB (Management Information Base) information published by SNMP (Simple Network Management Protocol) or using WS-Management can be applied. There is no need to use a unique method such as a vendor-specific protocol or private MIB in order to support the device. However, the use of such a specific method is not limited.

(Hardware configuration)
An example of the hardware configuration of the device identification apparatus 200 and the management target device 300 according to the above embodiment will be described. The device identification device 200 and the management target device 300 according to the above embodiment include a control device such as a CPU, a storage device such as a ROM and a RAM, an external storage device such as an HDD, a display device such as a display, a keyboard, a mouse, and the like. And a communication device such as a communication interface, and has a hardware configuration using a normal computer.

  The device identification program executed by the device identification apparatus 200 of the above embodiment is a file in an installable or executable format, and is a CD-ROM, CD-R, memory card, DVD (Digital Versatile Disk), flexible disk ( (FD) and the like are provided by being stored in a computer-readable storage medium.

  The device identification program executed by the device identification device 200 of the above embodiment may be provided by storing it on a computer connected to a network such as the Internet and downloading it via the network. Further, the device identification program executed by the device identification apparatus 200 of the above embodiment may be provided or distributed via a network such as the Internet. Further, a device identification program executed by the device identification device 200 of the above embodiment may be provided by being incorporated in advance in a ROM or the like.

  The device identification program executed by the device identification device 200 of the above embodiment has a module configuration for realizing the above-described units on a computer. As actual hardware, the CPU reads the device identification program from the HDD onto the RAM and executes it, so that the above-described units are realized on the computer.

(Modification)
In addition, this invention is not limited to the said embodiment, A various deformation | transformation is possible.

  For example, in the above embodiment, the MAC address is used as the second identification information. However, the user setting information described above may be used instead of the MAC address, or the user setting information described above may be used in addition to the MAC address. You may do it. In this way, even when appropriate identification information is not prepared for the management target device, it can be dealt with.

  When the user setting information is used in addition to the MAC address, since the second identification information is plural (two), the priority is set not only for the MAC address but also for the user setting information. When the priority of the MAC address is higher than the priority of the user setting information, the request unit 255 requests the MAC address if the first identification information is not responded, and the user setting information if the MAC address is not responded. Will be required.

  When the user setting information is used as the second identification information, the user inputs a comment character string (user setting information) such as “ASET-0001” using the operation unit 320 of the management target device 300, and the control unit 350 may store the input comment character string in the identification information storage unit 341. As a result, identification using the user setting information as identification information becomes possible.

  Further, for example, in the above embodiment, the priority of the identification information is defined by the priority file. However, the priority of the identification information is described in the device identification program, and the request unit 255 requests the identification information according to this priority. It may be.

DESCRIPTION OF SYMBOLS 100 Device management system 101 Network 200 Device management apparatus 210 Communication part 220 Operation part 230 Display part 240 Storage part 241 Priority file storage part 243 Identification information storage part 250 Control part 251 Equipment management part 253 Equipment identification part 254 Reception part 255 Request part 256 Identification Units 300-1 to 300-4 (300) Managed Device 310 Communication Unit 320 Operation Unit 330 Display Unit 340 Storage Unit 341 Identification Information Storage Unit 350 Control Unit 351 Response Unit

JP 2007-249718 A

Claims (8)

A device identification device connected to a device via a network,
Non-acquisition information indicating that the first identification information, which is a plurality of identification information for which the uniqueness of at least any one of the identification information is not guaranteed, is requested from the device and any of the first identification information cannot be acquired. When a response is made from the device, a request unit that requests the device for second identification information;
When the first identification information is responded to the request unit, the device is identified using the first identification information. When the second identification information is responded to the request unit, the second identification information is An identification unit for identifying the device using,
A device identification apparatus comprising: A reception unit that receives an identification request as to whether or not the device is a target device;
An identification information storage unit for storing the first identification information;
When the first identification information is returned to the request unit, the identification unit matches the first identification information stored in the identification information storage unit with the first identification information responded to the request unit. The device identification apparatus according to claim 1, wherein if it matches, the device is identified as the target device. A reception unit that receives an identification request as to whether or not the device is a target device;
An identification information storage unit for storing the second identification information;
When the second identification information is responded to the request unit, the identification unit matches the second identification information stored in the identification information storage unit with the second identification information responded to the request unit. The device identification apparatus according to claim 1, wherein the device identification device identifies whether or not the device is the target device if they match. The priority of the first identification information is higher than the priority of the second identification information,
The said request | requirement part requests | requires identification information from the said apparatus in order with the said high priority, The apparatus identification device as described in any one of Claims 1-3 characterized by the above-mentioned. A device identification system comprising a device identification device and a device connected to the device identification device via a network,
The device identification device is
Non-acquisition information indicating that the first identification information, which is a plurality of identification information for which the uniqueness of at least any one of the identification information is not guaranteed, is requested from the device and any of the first identification information cannot be acquired. When a response is made from the device, a request unit that requests the device for second identification information;
When the first identification information is responded to the request unit, the device is identified using the first identification information. When the second identification information is responded to the request unit, the second identification information is An identification unit for identifying the device using,
With
The equipment is
When the first identification information is requested from the device identification device, if the first identification information can be acquired, the first identification information is returned to the device identification device, and any one of the first identification information When the identification information cannot be acquired, the non-acquisition information is returned to the device identification device, and when the second identification information is requested from the device identification device, the second identification information is returned to the device identification device. And
A device identification system comprising: A device identification method executed by a device identification device connected to a device via a network,
The request unit requests the first identification information, which is a plurality of identification information for which the uniqueness of at least any one of the identification information is not guaranteed, and cannot obtain any identification information among the first identification information. A request step for requesting the device for second identification information when the non-acquisition information to be shown is responded from the device;
When the identification unit responds to the request unit with the first identification information, the identification unit identifies the device using the first identification information, and when the request unit receives the second identification information, the identification unit 2 an identification step of identifying the device using identification information;
A device identification method comprising: A device identification program for causing a computer to execute the device identification method according to claim 6 . A computer-readable storage medium storing the device identification program according to claim 7 .

Images