JP6232998B2 - Management information generating apparatus and device management system - Google Patents

Description

  The present invention relates to a management information generation device and a device management system.

  For example, as a system for efficiently managing equipment in an office, a system that collects various management information from equipment in an office connected to a network and stores the collected information in a server is known. Yes. For example, an industry standard MIB (Management Information Base) is defined for a multifunction peripheral (hereinafter also referred to as “MFP”), and an industry standard such as PJLink is defined for a projector. Various management standards are provided based on these standards. A technique for efficiently collecting and managing such information is known.

  In such a system, information on each device may be managed using identification information on each device. However, when a device managed by the above system includes a mobile device, another company's device, or an OEM (Original Equipment Manufacturer) product, the ID for identifying each device is not unique to each device. Can occur. For example, when an IP address is used as an ID for identifying each device, the IP address assigned to the device is changed by changing the network to which the device is connected due to movement of the device. In this case, the system manages the device identified by the IP address before the change and the device identified by the IP address after the change as different devices although they are the same device. Conversely, when an IP address assigned to one device at a certain time is assigned to another device at a different time, the system manages different devices with the same IP address. Thus, when the ID for identifying each device is not an ID unique to each device, it is difficult for the system to manage each device in an integrated manner.

  An object of one embodiment of the present invention is to generate identification information unique to a device to be managed.

  According to one embodiment, the management information generating apparatus is connected to a management control device that manages a device via a first network, and is connected to the device to be managed via a second network, In the information acquisition request packet transmitted from the device, setting information holding means for holding address information of the management control device, at least one of information unique to the management information generation device and information unique to the device The address information of the destination device of the response packet is extracted from the response packet that responds, and the identification information of the device is obtained based on the extracted address information and the address information held by the setting information holding unit. Packet analysis means for determining whether to generate, and when it is determined by the packet analysis means to generate identification information of the device, Management information generation means for generating identification information of the device based on at least one of the information unique to the management information generation device held in the fixed information holding means and the information unique to the device. A featured management information generation device is provided.

  According to an embodiment of the present invention, a device can be managed based on the generated identification information unique to the device to be managed.

It is a figure which shows the structural example of the system in 1st embodiment of this invention. It is a figure which shows the structural example of the functional block of the management ID provision apparatus in 1st embodiment of this invention. It is a figure for demonstrating an example of the basic procedure in 1st embodiment of this invention. It is a figure which shows an example of the judgment algorithm of whether the management ID in the packet analysis part in 1st embodiment of this invention is provided. It is a figure which shows the 1st example of the production | generation method of management ID in 1st embodiment of this invention. It is a figure which shows the 2nd example of the production | generation method of management ID in 1st embodiment of this invention. It is a figure which shows the 1st example of the management ID provision method in 1st embodiment of this invention. It is a figure which shows the 2nd example of the management ID provision method in 1st embodiment of this invention. It is a figure which shows an example of the reference of the setting value of the management ID provision apparatus in 1st embodiment of this invention, and a change method. It is a figure which shows an example of the procedure of the reference of the setting value in 1st embodiment of this invention, and a change method. It is a figure shown about the example of a screen at the time of referring and changing the setting value in 1st embodiment of this invention. It is a figure shown about the structural example at the time of adding the management protocol in 1st embodiment of this invention. It is a figure which shows the example of a screen of a setting value change when the management protocol in 1st embodiment of this invention is added. It is a figure which shows an example of the procedure of the addition method of the management protocol in 1st embodiment of this invention. It is a figure which shows an example of the connection procedures other than LAN by the device connection part in 1st embodiment of this invention. It is a figure explaining an example in the case of managing a device via a network.

Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In addition, in this specification and drawing, about the component which has the substantially same function structure, the duplicate description is abbreviate | omitted by attaching | subjecting the same code | symbol.
(Introduction)
First, an example of managing devices via a network will be described with reference to FIG.
When a management control device manages a device via a network, if there is no individual identification ID defined by the protocol among the protocols for acquiring management information, the management control device will respond to all IP addresses in the specified range. Generally, an information acquisition request is transmitted. However, in such a method, if the IP address of the management target device changes due to reasons such as the physical movement of the management target device, it is originally the same management target device but is different on the device management system. There may be a problem that the device is managed as a management target device. This problem will be described with reference to FIGS. 16A and 16B showing the state of management information before and after the management target device moves.

  The device management system includes a management control device 300 and managed devices 201, 202, and 203. The management control device 300 and the management target devices 201, 202, 203 are connected via the network 1. Here, LAN (Local Area Network) will be described as an example of the network 1. The management control device 300 manages the management target devices 201, 202, and 203 via the network 1.

  Before the management target device 201 moves, the management control device 300 manages the management information collected from the management target devices 201, 202, and 203 as shown in the upper right table of FIG.

  Before the managed device 201 moves, the management control device 300 collects managed device information A and information B from the managed devices 201, 202, and 203.

  Here, the management control device 300 manages the information collected using the IP address used when connecting to the network 1 in order to identify each management target device 201, 202, 203. The management range of the IP address managed by the management control device 300 is a range from (192.168.1.1) to (192.168.1.10). The management control device 300 transmits an information acquisition request packet to a device having an IP address in the management range of the management control device 300. Each managed device 201, 202, 203 receives the information acquisition request packet transmitted from the management control device 300. After receiving the information acquisition request packet, each of the management target devices 201, 202, 203 includes the information A and the information B held by itself in the response packet of the information acquisition request and transmits it to the management control device 300. The information A of the management target device 201 is “xxx”, and the information B is “ppp”. The information A of the management target device 202 is “yyy”, and the information B is “qqq”. The information A of the management target device 203 is “zzz”, and the information B is “rrr”.

  The management control device 300 receives the response packet of the information acquisition request from each of the management target devices 201, 202, and 203, thereby managing the management information (“IP address”, “information A”) of each of the management target devices 201, 202, and 203. And “Information B”).

  The IP address is extracted from the address of the transmission source of the response packet for the information acquisition request. The collected information is managed as management information for each IP address of the management target device. The management control device 300 manages the management information of the management target device 201 based on the IP address by associating “Information A: xxx” and “Information B: ppp” with “IP address: 192.168.1.2”. . Similarly, the management control device 300 manages the management information of the management target device 202 by associating “information A: yyy” and “information B: qqq” with “IP address: 192.168.1.5”. . Similarly, the management control device 300 manages the management information of the management target device 203 by associating “Information A: zzz” and “Information B: rrr” with “IP address: 192.168.1.10”. .

  After the managed device 201 moves, the status of management information managed by the management control device 300 is as shown in the upper right table of FIG.

  Since the managed device 201 has moved to another location, the IP address used by the managed device 201 has been changed from (192.168.1.2) to (192.168.1.4). The situation of the other devices to be managed 202 and 203 is the same as that shown in the table of FIG.

  With the IP address of the management target device 201 changed, the management control device 300 transmits an information acquisition request packet to a device having an IP address in the management range of the management control device 300 at a specific timing. .

  When the management target device 201 receives the information acquisition request packet from the management control device 300, the management target device 201 includes the information A “xxx” and the information B “ppp” in a response packet of the information acquisition request and transmits them to the management control device 300. The management control device 300 acquires the management information of each managed device 201, 202, 203 from the response packet of the received information acquisition request. Since there are no particular changes with respect to the management target devices 202 and 203, the collected management information is the same as that shown in the table of FIG. The management information of the management target device 201 is “IP address: 192.168.1.4”, “information A: xxx”, and “information B: ppp”. The collected management information is as shown in FIG.

  The management control device 300 cannot recognize the device of “IP address: 192.168.1.2” and the device of “IP address: 192.168.1.4” as the management information of the same managed device 201. As a result, information A and information B associated with “IP address: 192.168.1.2” and information A and information B associated with “IP address: 192.168.1.4” Are managed as management information of different managed devices.

Thus, when the ID for identifying each device is not unique to each device, it is difficult to manage each device in an integrated manner. Therefore, in the device management system according to an embodiment of the present invention described below, identification information unique to a device to be managed is generated, and the device is managed using this identification information.
[Overall configuration of device management system]
FIG. 1 shows an example of the overall configuration of a device management system according to an embodiment of the present invention. The device management system includes a management control device 300, management target devices 201, 202, and 203, management ID assigning devices 100a, 100b, and 100c (hereinafter collectively referred to as “management ID assigning device 100”). Have The management control device 300 is connected to the management ID assigning devices 100a, 100b, and 100c via the network 1. An example of the network 1 is a LAN, but is not limited thereto. The network 1 (LAN) is an example of a first network, and the first network may use another communication method.
(Management control equipment)
The management control device 300 functions as a server that manages the management target devices 201, 202, and 203 (hereinafter collectively referred to as “management target device 200”). For example, the management control device 300 according to the present embodiment includes an example of managing the management information of the management target devices 201, 202, and 203 such as a plurality of printers arranged in the office.
(Management ID assignment device)
The management ID assigning apparatuses 100a, 100b, and 100c are connected to the management target devices 201, 202, and 203 via the networks 2a, 2b, and 2c. An example of the network 2 is a LAN, but is not limited thereto. The network 2 (LAN) is an example of a second network, and the second network may use another communication method.

The management ID assigning apparatuses 100a, 100b, and 100c are used by being attached to LAN ports incorporated in the management target devices 201, 202, and 203. Accordingly, a LAN cable is used as shown in FIG. 1 to connect the second networks 2a, 2b, and 2c between the management ID assigning apparatuses 100a, 100b, and 100c and the LAN ports of the managed devices 201, 202, and 203. May be. Further, for the connection of the second networks 2a, 2b, and 2c, the management ID assigning devices 100a, 100b, and 100c may be directly attached to the management target devices 201, 202, and 203 without using a LAN cable.
(Managed device)
The managed devices 201, 202, and 203 are managed devices that are managed by the management control device 300. The device to be managed has a communication function that can be connected to a network such as an MFP (Multi Function Printer), a projector, a PC, a tablet terminal, a mobile terminal, a mobile phone, a mobile game device, a mobile music player, etc. Any device may be used.
For example, in the present embodiment, an example in which a LAN having the same communication method is adopted as the communication method of the first and second networks will be described. On the other hand, in the second embodiment to be described later, in the case where the first network and the second network are different communication methods, that is, an example in which a communication method other than LAN is adopted as the communication method of the second network. explain. As a communication method other than LAN, for example, any of USB (Universal Serial Bus), Wi-Fi (registered trademark) (Wireless Fidelity), optical communication, and the like may be used.
[Overview of device functions]
Next, an overview of the functions of the management control device 300, the management ID assigning devices 100a, 100b, and 100c and the management target devices 201, 202, and 203 will be described. The management control device 300 transmits a packet requesting management information for managing each managed device to the managed devices 201, 202, and 203 (hereinafter referred to as “information acquisition request packet”).

  Upon receiving the information acquisition request packet, the management ID assigning apparatuses 100a, 100b, and 100c transfer the information acquisition request packet to the management target devices 201, 202, and 203 via the networks 2a, 2b, and 2c. The managed devices 201, 202, and 203 return a response packet for the information acquisition request packet including information A and information B that are management information of each managed device. Response packets from the respective management target devices 201, 202, and 203 are transferred to the respective management ID assigning apparatuses 100a, 100b, and 100c.

  Each management ID assigning device 100a, 100b, 100c confirms that the transferred packet is a response packet to the management control device 300. The management ID assigning devices 100a, 100b, and 100c analyze the response packet and determine whether the response packet is a target packet to which the management ID is to be assigned. The management ID used in the description of the present embodiment is an example of information unique to each managed device 201, 202, 203 that can identify each managed device 201, 202, 203. When it is determined that the management ID should be assigned, the management ID assigning apparatuses 100 a, 100 b, and 100 c assign the management ID to the response packet and transmit the management ID to the management control device 300 via the network 1.

  For example, the management target device 201 transmits a response packet to which the information A “xxx” and the information B “ppp” are attached to the management ID assigning apparatus 100a via the network 2a. In the response packet, the IP address (192.168.1.2) of the management target device 201 is set as the transmission source of the response packet. In the management ID assigning device 100a, the management ID “aaa” generated by the management ID assigning device 100a is assigned to the response packet from the management target device 201 and transmitted to the management control device 300. A method for assigning the management ID will be described later with reference to FIG. 7 or FIG.

  The management control device 300 receives a response packet from each managed device 201, 202, 203 in response to the information acquisition request packet. The management control device 300 acquires the management information (for example, “management ID”, “IP address”, “information A”, “information B”, etc.) of each management target device 201, 202, 203 included in the response packet. Manage.

In FIG. 1A, the management control device 300 acquires the management information of the management target devices 201, 202, and 203 to which the management ID assigning devices 100a, 100b, and 100c are attached via the network 1 (LAN). An example is shown.
The management control device 300 associates “IP address: 192.168.1.2”, “Information A: xxx”, and “Information B: ppp” with “Management ID: aaa” by the management ID “aaa”. Management information of the management target device 201 is managed. Similarly, the management control device 300 associates “IP address: 192.168.1.5”, “Information A: yyy”, and “Information B: qqq” with “Management ID: bbb”, thereby managing ID “bbb”. To manage the management information of the management target device 202. Also, the management control device 300 associates “IP address: 192.168.1.10”, “Information A: zzz”, and “Information B: rrr” with “Management ID: ccc”, thereby managing ID “ccc”. To manage the management information of the management target device 203.

  FIG. 1B shows an example where the IP address used by the managed device 201 is changed because the managed device 201 has moved to another location. The situation of other managed devices 202 and 203 is the same as that shown in FIG.

  The managed device 201 has moved and the IP address has been changed from (192.168.1.2) to (192.168.1.4). However, a management ID (aaa) is assigned to the management ID assigning device 100a. For this reason, as shown in the table of FIG. 16B, the management control device 300 includes “IP address: 192.168.1.4”, “Information A: xxx”, and “Management ID: aaa”. Management information of the management target device 201 is managed by the management ID “aaa” by associating information B: ppp ”.

In this way, even if the IP address of the management target device changes, the management target device 200 can be centrally managed without recognizing the same management target device 200 as a different one.
[Functional configuration of management ID assigning device]
Next, functions of each unit in the management ID assigning apparatus 100 will be described. FIG. 2 is a diagram illustrating a configuration example of functional blocks of the management ID assigning apparatus according to the first embodiment of the present invention.

  The management ID assigning apparatus 100 includes a communication unit 101, a device connection unit 102, a packet analysis unit 103, a setting information holding unit 104, a management ID adding unit 105, a setting screen generation unit 106, and a management protocol holding unit 107. And a packet conversion unit 108.

  The communication unit 101 communicates with the management control device 300 and other devices via the network 1. The communication unit 101 is a part that becomes an interface of the network 1 of the management ID assigning apparatus 100. The communication unit 101 receives an information acquisition request packet and transmits a response packet to the information acquisition request in communication with the management control device 300. The communication unit 101 may use 3G (3rd Generation) communication, BlueTooth (registered trademark), or the like as a communication means in addition to a LAN.

  The device connection unit 102 is connected to the management target device 200 via the network 2, and exchanges management information with the management target device 200. The communication method of the network 2 includes LAN, USB, serial, and the like. When the network 2 is a LAN communication method, all the functions of the device connection unit 102 can be replaced by the communication unit 101. When the network 2 is a communication method other than LAN, all of the functions of the device connection unit 102 cannot be replaced by the communication unit 101. The device connection unit 102 transfers a response packet (including management information) to the information acquisition request packet to the packet conversion unit 108 and causes the packet conversion unit 108 to convert the packet into a data format corresponding to the LAN of the network 1.

  The packet analysis unit 103 analyzes a packet transmitted from the management target device 200 and determines whether or not a management ID should be given to the analyzed packet. There are the following two determination conditions as conditions for determining whether or not the management ID should be given to the analyzed packet.

  As a first determination condition, the address information of the transmission destination of the response packet received from the management target device 200 is the same as the address information held in the setting information holding unit 104.

  As a second determination condition, the protocol of the response packet received from the management target device 200 is the same as the protocol held in the setting information holding unit 104.

  The address information held in the setting information holding unit 104 may hold address information of the management control device 300, for example. The protocol held in the setting information holding unit 104 may hold, for example, a protocol used by the management control device 300 to manage the management target device 200.

  In the present embodiment, the packet analysis unit 103 determines that a management ID should be given to the analyzed packet when the above two determination conditions are satisfied. However, when the first determination condition is satisfied, it may be determined that a management ID should be given to the analyzed packet without determining whether the second determination condition is satisfied.

  The setting information holding unit 104 holds information for determining whether the packet analysis unit 103 should give a management ID. For example, the setting information holding unit 104 stores address information of the management control device 300 and a protocol used by the management control device 300. The setting information holding unit 104 may hold setting values (such as user-specified parameters) such as an ID generation method used when assigning a management ID. The setting information holding unit 104 may store at least one of information unique to the management ID assignment device 100 and information unique to the management target device 200 as information used when assigning the management ID. As information unique to the management ID assigning apparatus 100 and information unique to the management target device 200, for example, the equipment number of the management ID assignment apparatus 100, the equipment number of the management target device 200, and the like are conceivable. Further, user-specified parameters (setting information set according to user operations), which is an example of information that can be used when assigning a management ID, will be described later in the description of FIG.

  The management ID assigning unit 105 generates a management ID and assigns a management ID to a predetermined packet. When the packet analysis unit 103 determines that the management ID needs to be assigned, the management ID assignment unit 105 receives an instruction from the packet analysis unit 103 and generates and assigns the management ID. A specific method for creating the management ID will be described later with reference to FIGS.

  The management ID assigning unit 105 described in an embodiment of the present invention is a management ID assigning device held in the setting information holding unit 104 when it is determined by the packet analyzing unit 103 that the identification information of the management target device is generated. 10 is an example of a management information generation unit that generates identification information of a management target device based on at least one of information specific to 100 and information specific to a management target device.

  The setting screen generation unit 106 generates a setting screen to be displayed on the WEB browser so that the setting value (setting information) held in the setting information holding unit 104 can be referred to and changed from an external computer. Further, when the management target device 200 is a device having a display function and an input function, a setting screen may be displayed on the management target device so that setting values can be referred to and changed from the setting screen.

  The management protocol holding unit 107 holds information regarding the type of protocol and the specification of each protocol for collation with the second determination condition of the packet analysis unit 103. Note that the protocol that the packet analysis unit 103 directly collates with the second determination condition is held by the setting information holding unit 104 and uses information. That is, the management protocol holding unit 107 holds information on a plurality of protocols used by the management control device 300. The setting information holding unit 104 holds information on a specific protocol selected from a plurality of protocols stored in the management protocol holding unit 107. The packet analysis unit 103 determines the second determination condition based on information on the selected specific protocol.

  When the network 1 and the network 2 use different communication methods, the packet conversion unit 108 has a function of converting into a data format suitable for each communication method. For example, when the network 1 is a LAN and the network 2 is a communication method other than the LAN, an information acquisition request packet is transmitted from the management control device 300 to each managed device 200 via the LAN of the network 1. In this case, the management ID assigning apparatus 100 receives an information acquisition request packet transmitted via the LAN. When the communication method between the management ID assigning apparatus 100 and the management target device 200 of the network 2 is, for example, USB, the management ID assignment apparatus 100 directly sends the information acquisition request packet received from the LAN of the network 1 to the management target device 200. It cannot be sent. For this reason, the packet conversion unit 108 converts the information acquisition request packet received from the LAN into the USB data format used in the network 2 and transmits it to the management target device 200. The packet converter 108 converts the response packet data received via the second network into a data format corresponding to the communication method of the first network, and transmits the data to the management control device 300.

  If the network 1 and the network 2 are the same communication method, for example, a LAN, it is not necessary to convert the data format, so that the received data can be transferred as it is.

In the embodiment, the communication method of the network 2 will be described focusing on the LAN, but other communication means such as 3G communication or Bluetooth (registered trademark) may be used.
[Basic operation of management ID assigning device]
Next, the basic operation of the management ID assigning apparatus 100 will be described. FIG. 3 is a diagram for explaining an example of a basic procedure in the first embodiment of the present invention.
(Procedure when an information acquisition request packet is received)
First, a basic procedure of the management ID assigning apparatus 100 when an information acquisition request packet is received from the management control device 300 will be described with reference to FIG.

  In step S401, the management control device 300 transmits an information acquisition request packet to each management target device in order to acquire management information. The communication unit 101 of the management ID assigning apparatus 100 attached to the management target device 200 receives the information acquisition request packet transmitted from the management control device 300.

  In step S <b> 402, the information acquisition request packet received by the communication unit 101 is delivered to the device connection unit 102.

  In step S <b> 403, the device connection unit 102 delivers the received information acquisition request packet to the management target device 200. At this time, it is assumed that the network 2 between the device connection unit 102 and the management target device 200 is the same LAN, and the information acquisition request packet received by the communication unit 101 is transferred to the management target device as it is. The Therefore, in this embodiment, the information acquisition request packet is transferred to the management target device 200 via the device connection unit 102, but may be transferred by the communication unit 101 without passing through the device connection unit 102. .

Note that a communication method other than the LAN as the communication method of the network 2 will be described with reference to FIG.
(Procedure for responding to an information acquisition request packet)
Next, a procedure when the management target device 200 that has received the information acquisition request packet from the management control device 300 responds to the information acquisition request packet will be described with reference to FIG.

  In step S410, the management target device 200 transmits a response packet to the management control device 300 in response to the information acquisition request packet. A response packet from the management target device 200 is transmitted to the device connection unit 102 via the network 2.

  In step S411, the device connection unit 102 transmits a response packet in response to the received information acquisition request packet to the packet analysis unit 103. The communication method of the network 2 is LAN, and the device connection unit 102 transfers the data as it is to the packet analysis unit 103 without converting the data format. A communication system other than the LAN for the network 2 will be described with reference to FIG.

  The packet analysis unit 103 analyzes the response packet that responds to the received information acquisition request packet.

  In step S412, the packet analysis unit 103 requests the setting information holding unit 104 to provide a setting value in order to compare the information of the packet to be transmitted with the setting value stored in the setting information holding unit 104. For example, the setting values held in the setting information holding unit 104 are address information, protocol information, and the like of the management control device 300.

  In step S 413, the setting information holding unit 104 receives a setting value provision request from the packet analysis unit 103. The setting information holding unit 104 provides a setting value to the packet analysis unit 103.

  The packet analysis unit 103 checks whether the address information included in the received packet is the same as the destination (address information) recorded in the setting information holding unit 104. In addition, the packet analysis unit 103 checks whether the protocol included in the received packet is the same protocol as the protocol stored in the setting information storage unit 104. The packet analysis unit 103 confirms whether the management ID satisfies both the first condition and the second condition, and determines whether or not the management ID should be given. Details of the determination will be described with reference to FIG.

  When it is determined that the management ID should be given, the packet analysis unit 103 requests the management ID giving unit 105 to add the management ID to the received packet.

  In step S414, the packet analysis unit 103 requests the management ID assigning unit 105 to assign a management ID to the response packet in response to the information acquisition request packet.

  In step S415, the management ID assigning unit 105 generates a management ID in response to the management ID assignment request from the packet analysis unit 103, and assigns the generated management ID to the response packet. Details of generation of the management ID will be described with reference to FIGS.

  In step S416, the packet analysis unit 103 transmits a response packet to which the management ID is assigned to the communication unit 101.

In step S417, the communication unit 101 transmits a response packet to which the management ID is added to the management control device 300.
(Judgment procedure of whether to give management ID)
Next, a determination algorithm used when the packet analysis unit 103 determines whether to assign a management ID will be described. FIG. 4 is a diagram illustrating an example of a determination algorithm for determining whether or not to assign a management ID in the present embodiment.

  The packet analysis unit 103 analyzes the response packet received from the management target device 200 via the communication unit 101.

  In step S501, first, the packet analysis unit 103 extracts a destination IP address in the received response packet. Next, the packet analysis unit 103 acquires the IP address of the management control device 300 recorded in the setting information holding unit 104.

  Next, the packet analysis unit 103 compares the destination IP address in the received response packet with the IP address of the management control device 300 to confirm whether they match.

  If they match, the process proceeds to step S502. If they do not match, the packet analysis unit 103 determines that the management ID is not given, and ends this processing.

  In step S502, first, the packet analysis unit 103 extracts the protocol of the received packet. Next, the packet analysis unit 103 acquires the management protocol of the management control device 300 recorded in the setting information holding unit 104.

  Next, the packet analysis unit 103 compares the protocol in the received response packet with the management protocol of the management control device 300 recorded in the setting information holding unit 104 to confirm whether they match.

  If they match, the packet analysis unit 103 determines to assign a management ID, and proceeds to step S503. If they do not match, the packet analysis unit 103 determines not to assign a management ID.

  In step S503, the management ID assigning unit 105 generates a management ID and assigns the generated management ID to the response packet analyzed by the packet analysis unit 103. A detailed method for generating and assigning the management ID will be described with reference to FIGS.

In FIG. 4, the case where the packet analysis unit 103 confirms both the first determination condition (S501) and the second determination condition (S502) has been described, but only the first determination condition (S501) is satisfied. In this case, it may be determined that a management ID is generated. At this time, the packet analysis unit 103 does not ask whether the second determination condition (S502) is satisfied.
(First example of management ID generation method)
Next, a first example of a management ID generation method will be described with reference to FIG. FIG. 5 is a diagram illustrating a first example of a management ID generation method according to the present embodiment.

  Here, the ID generation method when the management ID is assigned in step S503 in FIG. 4 will be described in detail.

  The management ID to be assigned is generated based on parameters registered in advance by the user in the management ID assignment device 100 in consideration of ease of management. The parameter input method will be described later with reference to FIG.

  For example, in the case where the management target device 200p is a projector installed in a conference room A100, the user can easily identify which management target device 200p is information by specifying a management ID A100PJ. Easy to manage.

  However, if only the parameters (setting values) entered by the user are used as they are as management IDs, inconvenience may occur. For example, when a plurality of management ID assigning devices 100p specify the same management ID, the plurality of management target devices 200p cannot be distinguished from each other. For this reason, the management control device 300 has a problem that information on different devices is handled as information on the same device. Therefore, in the present embodiment, information unique to each management ID assigning device 100 (for example, Prifix) and parameters set by the user may be assigned as management IDs. According to this, even if the parameters specified by the user are the same, the management target device 200 equipped with a different management ID assigning device 100 is surely attached to the management target device 200 based on information unique to each management ID assigning device 100. Different management IDs can be assigned. Furthermore, security can be improved by generating a management ID in which parameters set by the user are added to information unique to the management ID assigning apparatus 100.

  For example, the management ID assigning device 100p attached to the management target device 200p is assigned (abc) as unique information (for example, Prifix) of the management ID assigning device 100p. The user-specified parameter of the management target device 200p is (A100PJ). The management ID assigning device 100p may use a management ID (abc-A100PJ) as a management ID, which is a combination of Prifix and user-specified parameters. Further, the management ID may be generated only by the unique information of the management ID assigning device 100p.

The management ID assigning apparatus 100p adds the management ID generated by the above method to the response packet received from the management target device 200p via the network 2. The management ID assigning device 100p transmits a response packet to which the management ID is added (a management ID is added to the response packet for the information acquisition request) to the management control device 300 via the network 1.
(Second example of management ID generation method)
Next, a second example of the management ID generation method will be described with reference to FIG.

  FIG. 6 is a diagram showing a second example of the management ID generation method in the first embodiment of the present invention.

Consider a case where the management target device 200 to which the management ID assigning apparatus 100 is attached is changed.
For example, there is a case where the management ID assigning device 100p is mounted on a certain projector A and operated, but the projector A is out of order and the management ID assigning device 100p is remounted on another projector B and used again. In the case of a management ID assigning device that uses the first method as a method for generating a management ID, the generated management ID (device-specific information (prefix) -user-specified parameter) changes the device on which the management ID assigning device 100p is mounted. It is necessary to change the user-specified parameter every time. Note that when setting the user-specified parameter, it is necessary to set the user-specified parameter so that the management ID is not the same as other devices.

  When changing the management target device 200 to which the management ID provision device 100 is attached, it is desired that the user can use the management ID provision device 100 only by attaching it to the management target device 200. For this purpose, the management ID assigning apparatus 100 may use information unique to the management target device 200 as information for generating a management ID.

  Therefore, as a second example of the management ID generation method, a MAC (Media Access Control) address that is unique information of the management target device 200 may be used.

  By generating a management ID from the MAC address of the management target device 200 to which the management ID assignment device 100 is attached, even when the management ID assignment device 100 is attached to a different management target device 200, the management target device 200 is correctly recognized. be able to. For example, as shown in the upper diagram of FIG. 6, a management ID assigning device 100m is attached to the management target device 200m via the network 2. As shown in the lower diagram of FIG. 6, a management ID assigning device 100n is attached to the management target device 200n via the network 2.

The MAC address of the management target device 200m is (11: 22: 33: 44: 55: 66). The MAC address of the management target device 200m is (aa: bb: cc: dd: ee: ff). Here, as an example of a method for generating a management ID using a MAC address, the management ID is generated according to a rule that the MAC address is divided into 3 bytes and the lower 3 bytes + the upper 3 bytes are combined. In this case, the management ID generated for the management target device 200m is (management ID: 4455661112233). Similarly, the management ID generated for the management target device 200n is (management ID: ddeffabbcc). According to this method, the management ID of each managed device 200 is generated using information unique to each managed device 200. Therefore, it is guaranteed that the management ID generated for the management target device 200m and the management ID generated for the management target device 200n are different management IDs. For this reason, the management control device 300 can manage the management information of the management target device 200 without manually changing the parameter even if the management target device 200 to which the management ID assigning apparatus 100 is mounted is changed. The important point is that the management ID is generated from the MAC address, and the generation rule is not limited. However, the condition of the generation rule that can be used by the management ID assigning apparatus 100 is a necessary condition that the MAC address used for generation and the management ID generated by the generation rule are a generation rule that can take a 1: 1 correspondence. .
(First example of method of assigning management ID to response packet)
Next, a first example of a method for assigning a management ID to a response packet will be described with reference to FIG. FIG. 7 is a diagram showing a first example of the management ID assigning method in the first embodiment of the present invention.

  For example, consider a case in which the management device 200 uses a management protocol that operates on the TCP (Transmission Control Protocol) as the protocol used in the network 2. In this case, the structure of the response packet transmitted through the network 2 before giving the management ID of the response packet for the information acquisition request is an ether header + IP header + TCP header + management information response part. When a management ID is given, a management ID header (including management ID information is included in this portion) is inserted after the TCP header. The management ID assigning apparatus 100 recalculates the checksum of the response packet in which the management ID header is inserted, reconstructs the response packet, and transmits the response packet to the management control device 300 via the network 1.

Since the management control device 300 can grasp the management ID of the management target device 200 that is the source of the response packet by referring to the management ID header of the received response packet, the management control device 300 is associated with each management ID using the management ID. Management information of the managed device 200 can be managed.
(Second example of method of assigning management ID to response packet)
Next, a second example of a method for assigning a management ID to a response packet will be described with reference to FIG. FIG. 8 is a diagram showing a second example of the management ID assigning method in the first embodiment of the present invention.

  Note that FIG. 8 also shows the case where a management protocol operating on TCP is used, as in FIG.

  FIG. 8 describes a method in which a management ID assigning device different from that in FIG. 7 assigns a management ID to a response packet. The method of FIG. 7 is a method for reconstructing the content by rewriting the content of the original response packet. Here, as a method of assigning the management ID without rewriting the contents of the original response packet, a packet different from the response packet (hereinafter also referred to as “attached packet”) is generated, and the management ID information is attached to the attached packet. It is conceivable to include. The management ID assigning apparatus 100 receives a response packet from the management target device 200 via the network 2. When receiving the response packet, the management ID assigning device 100 generates an attached packet including the management ID. The management ID assigning apparatus 100 first transmits (1) the response packet received from the management target device to the management control device 300 via the network 1 without changing the contents of the original response packet. (1) After transmitting the response packet, the management ID assigning apparatus 100 then transmits the attached packet including the management ID (2) generated from the response packet to the management control device 300 via the network 1.

Note that (2) the transmission source and transmission destination of the attached packet including the management ID are set with reference to the content of (1) response packet.
(How to view and change setting values)
Next, an example of a method for referring to and changing setting values of the management ID assigning apparatus 100 according to the present embodiment will be described with reference to FIG. FIG. 9 is a diagram illustrating an example of a method for referring to and changing the setting value of the management ID assigning apparatus 100 according to the first embodiment of the present invention.

  Here, a method for referring to and changing the setting value held in the management ID assigning apparatus 100 will be described.

  Since the management ID assigning apparatus 100 is an apparatus that is externally attached to the network interface portion of the management target device 200, it is basically small and has no special user interface (display device, keyboard, mouse, etc.). It is preferable that

  Therefore, as shown in FIG. 9, the management ID assigning apparatus 100 is accessed from the setting value changing PC 400 connected to the network 1, and the user performs a predetermined operation using the setting value changing PC 400. The setting value is referenced and changed via By referring to or changing the setting value of the management ID assigning device 100 in this way, the management ID assigning device 100 does not have a special user interface and can be miniaturized.

Further, when the network 1 to which the management ID assigning device 100 is connected is a LAN, the setting value of the management ID assigning device 100 is set by directly connecting the PC to the interface of the network 1 of the management ID assigning device 100 with a LAN cable (cross). You may make it refer and change. When the management target device 200 to which the management ID assigning apparatus 100 is attached via the network 2 is a device having a display function and an input function, a setting screen is displayed on the management target device 200 and the setting is performed. The setting value may be referred to and changed from the screen.
(Refer to the setting value, change procedure)
Next, referring to and changing the setting value held by the setting information holding unit 104 will be described with reference to FIG. FIG. 10 is a diagram illustrating an example of a procedure for a method for referring to and changing a set value according to the first embodiment of the present invention.

  In either case of referring to or changing the set value, access from the device manager (an example of a user) is accepted via the communication unit 101.

  In step S1101, the device administrator uses the setting value changing PC 400 to request the communication unit 101 to refer to the setting value.

  In step S1102, the communication unit 101 instructs the setting screen generation unit 106 to generate a setting value list screen in response to a setting value reference request from the setting value changing PC 400.

  In step S <b> 1103, the setting screen generation unit 106 receives an instruction from the communication unit 101 and instructs the setting information holding unit 104 to acquire the current setting value.

  In step S1104, the setting information holding unit 104 provides respective setting values in response to an instruction from the setting screen generation unit 106.

  In step S <b> 1105, the setting screen generation unit 106 generates a setting value list screen in response to an instruction from the communication unit 101, and provides the list screen data to the communication unit 101.

  In step S <b> 1106, the communication unit 101 transmits the setting value list screen data provided from the setting screen generation unit 106 to the setting value changing PC 400.

  In step S1107, the device administrator displays a list screen acquired by the setting value changing PC 400 and confirms whether to change the setting value. When changing the setting value, the device administrator operates the screen of the setting value changing PC 400 to transmit an instruction to change the setting value to the communication unit 101.

In step S <b> 1108, the communication unit 101 determines whether to accept a setting change. When the setting change is accepted, the setting information holding unit 104 updates the setting value based on the information passed from the communication unit 101. .
(List of setting values)
FIG. 11 is a diagram showing an example of a screen when referring to and changing set values in the first embodiment of the present invention.

In step S1107, the device administrator is an example of a screen for confirming the setting items currently set, and is displayed on the screen of the setting value changing PC 400. Examples of information that can be changed include the IP address of the management control device 300, the type of management protocol, and a method for generating a management ID. When the management ID setting is manual setting, the management ID setting parameter can be changed. The device administrator changes the target item by directly inputting into the input column of the item to be changed, selecting from the pull-down menu, or checking the check column. After the setting value is changed, the device administrator presses the Enter key, for example, so that the setting value changing PC 400 used by the device administrator transmits an instruction to change the setting value to the communication unit 101. good.
(Configuration example when adding a management protocol)
FIG. 12 is a diagram showing a configuration example when adding a management protocol in the first embodiment of the present invention.

  Here, a procedure will be described when a management protocol is added to the management ID assigning apparatus 100 attached to the management target device 200. It is conceivable that new standards will be developed in the future for the device management protocol used in the device management system. Therefore, a procedure for adding a management protocol is necessary so that the management ID assigning apparatus 100 can cope with a new protocol.

  In FIG. 12, the network 1 includes a management control device 300, a management ID assigning device 100 connected to the management target device 200 via the network 2, a setting value changing PC 400, a plug-in disclosure server 500, Is connected. When a new protocol is published, a program that identifies the protocol name and which part of the packet can be identified is published on the plug-in publishing server 500 in the form of a plug-in. The device administrator uses the setting value changing PC 400 to (1) download the plug-in from the plug-in disclosure server 500 and save it in a specific directory of the setting value changing PC 400.

  In order to change the setting value of the management ID assigning device 100, the device administrator opens the WEB browser from the setting value changing PC 400 via the network 1 to the management ID assigning device 100 with (2 ) A request for reference / change of the set value is sent. When the device administrator saves the plug-in in a specific directory, the current setting item is displayed on the setting screen, and a newly added management protocol option is added to the management protocol item.

When the device manager selects the added management protocol option, (3) plug-in installation is executed from the setting value changing PC 400 to the management ID assigning device 100 via the network 1.
(Screen example of setting value change)
FIG. 13 is a diagram showing an example of a setting value change screen when a management protocol is added in the first embodiment of the present invention. As a management protocol, “Crestron <new>” is newly added and displayed in addition to “PJLink”.
(Management protocol addition procedure)
Next, a procedure for additionally registering the management protocol downloaded by the device administrator in the management ID assigning apparatus 100 will be described with reference to FIG. FIG. 14 is a diagram illustrating an example of a procedure of a management protocol addition method according to the first embodiment of this invention.

  The device administrator uses the setting value changing PC 400 to download a new management protocol plug-in from the plug-in disclosure server 500. The downloaded new management protocol plug-in is stored in a specific directory of the setting value changing PC 400. When the device manager opens a web browser for referring to and changing the setting value, the management protocol options stored in the specific directory are added to the management protocol.

  In step S1501, the device administrator selects a management protocol option that has been added, so that a new management protocol plug-in is transmitted from the device administrator setting value change PC 400 to the management ID assigning apparatus 100. . That is, a management protocol is added. The communication unit 101 receives the new management protocol plug-in transmitted from the setting value changing PC 400 via the network 1.

  In step S1502, the communication unit 101 transmits the received new management protocol plug-in to the management protocol holding unit 107, and the management protocol holding unit 107 saves (installs) the received new management protocol plug-in.

In this way, in this system, even if a new protocol is disclosed, device management can be performed by adding a plug-in later. Here, as an example, an example in which a device administrator user is used as a trigger to install a plug-in is shown, but any method can be used as long as a plug-in of a new management protocol can be added.
(Management protocol addition procedure)
Next, a sequence when the communication method of the second network is other than LAN will be described with reference to FIG. FIG. 15 is a diagram illustrating an example of a connection procedure other than the LAN by the device connection unit 102 according to the first embodiment of this invention. In the following, information transmitted to the networks 1 and 2 is described as a packet, but it may not necessarily be packetized information. For example, the information acquisition request or the response may be a command that transmits an information group as a signal.

  15A is divided into two examples when an information acquisition request packet is received, and FIG. 15B is divided into two examples when a response is made to the information acquisition request packet.

  FIG. 15A is an example of a procedure when an information acquisition request packet is received.

  The management control device 300 transmits an information acquisition request packet to each management target device 200 in order to acquire management information.

  In step S <b> 1601, the communication unit 101 of the management ID assigning apparatus 100 attached to the management target device 200 receives an information acquisition request packet from the management control device 300.

  In step S1602, the communication unit 101 passes the received information acquisition request packet to the packet conversion unit 108, and the packet conversion unit 108 converts the information acquisition request packet into a data format suitable for the communication method of the device connection unit 102. To do. For example, if it is connected by USB, it is converted into an information acquisition USB command.

  In step S <b> 1603, the packet conversion unit 108 delivers the information acquisition request packet converted to match the communication method of the device connection unit 102 to the communication unit 101.

  In step S <b> 1604, the communication unit 101 delivers the information acquisition request packet that has been converted from the packet conversion unit 108 so as to match the communication method of the device connection unit 102 to the device connection unit 102.

  In step S <b> 1605, the device connection unit 102 delivers the received information acquisition request packet to the management target device 200. Note that the communication method between the managed device 200 and the device connection unit 102 (second network) is assumed to be other than LAN. Therefore, in step S1605, communication is performed using a communication method different from the LAN, for example, USB.

  The managed device 200 that has received the information acquisition request packet from the management control device 300 according to the sequence of FIG. 15A shows the procedure for responding to the information acquisition request packet with reference to FIG. The description will be given with reference.

  FIG. 15B is an example of a procedure in the case of responding to the information acquisition request packet.

  In step S <b> 1611, the management target device 200 responds to the information acquisition request packet and transmits a response packet to the management control device 300. A response packet responding to the information acquisition request packet is first transmitted to the device connection unit 102 of the management ID assigning apparatus 100. Note that the communication method between the managed device 200 and the device connection unit 102 (second network) is assumed to be other than LAN. Therefore, in step S1611, communication is performed using a communication method different from the LAN, for example, USB.

  In step S <b> 1612, the device connection unit 102 delivers the received data to the packet conversion unit 108. The packet conversion unit 108 refers to the destination from the data of the response packet responding to the information acquisition request packet, and regenerates the packet for LAN.

  In step S <b> 1613, the packet conversion unit 108 regenerates the response packet into a LAN packet and transmits it to the device connection unit 102.

  In step S <b> 1614, the response packet regenerated to the LAN packet received by the device connection unit 102 is transmitted to the packet analysis unit 103. The packet analysis unit 103 analyzes the received response packet.

  Note that the processing after step S1614 is the same as the processing of steps S412 to S417 in FIG.

  By performing the processing as described above, device management can be performed even for a management target device that does not have a network function without limiting the communication method of the device connection unit 102 to a LAN.

  Heretofore, the device management system according to the present embodiment has been described. According to the device management system according to the present embodiment, the management target device can be centrally managed by generating the management ID as identification information unique to the management target device.

  Further, when the management ID assigning device 100 generates the management ID, it assigns the unique information (Prefix) that the management ID assigning device 100 has individually and the parameter concatenated ID specified by the user. Therefore, since the management ID assigning apparatus 100 can specify an arbitrary ID of the user, it is easy to manage the device.

  In addition, since the management ID assigning device 100 generates the management ID using the MAC address of the connected device, the ID assigned varies depending on the connected device. The apparatus 100 can be shared by a plurality of devices.

  Further, since the management ID assigning device 100 assigns the management ID only to the response packet for the information acquisition request packet, the total number of packets flowing in the network does not change, and the load on the network can be reduced.

  Further, since the management ID assigning device 100 transmits a packet including the management ID separately from the response packet for the information acquisition request, the management ID assigning device 100 assigns the management ID information without changing the data of the original response packet. be able to.

  Also, in the management ID assigning device 100, the management protocol holding unit 107 holds the protocol type and each protocol specification, and the setting information holding unit 104 holds information on the management protocol used by the device management system. . Therefore, the management ID assigning apparatus 100 can manage the device by changing to an arbitrary protocol.

  In addition, the management ID assigning apparatus 100 can additionally register a management protocol in the management protocol holding unit 107 via the network. Therefore, the management ID assigning device 100 can manage the device without replacing the management ID assigning device 100 even if a protocol used in the device management system is newly disclosed.

  In addition, the management ID assigning apparatus 100 holds the setting value of the ID generation method in the setting information holding unit 104, and generates the ID in the management ID giving unit 105 according to the set ID generation method. You can select a method that suits your purpose and make the device management system easier to use.

  Further, since the management ID assigning apparatus 100 can manage and change the address information of the management control device of the device management system by the setting information holding unit 104, the device can be managed by an arbitrary device management system. .

  Further, since the management ID assigning apparatus 100 can refer to, change, or add a setting value with a WEB browser, no special user interface is required on the communication device side.

  Further, even the management target device 200 connected via a LAN other than a USB can be transferred after being converted into a communication packet converted into each data format via the packet converter 108. As a result, even such a management target device 200 can be managed.

  According to an embodiment of the present invention, in a device management system, when a packet transmitted from a device to be managed is analyzed and a response packet is sent to a management control device that manages and controls the device management system, the device The management identification information unique to each is generated. Since management identification information unique to the device is added and a response packet is transmitted to the management control device, the management target can be centrally managed even when the management target is a third-party machine or an OEM mobile device.

  Further, by recording a program for realizing the control processing described in the first embodiment on a recording medium, the computer can execute the processing in each embodiment.

  It is also possible to record the program on a recording medium and cause the computer or portable terminal device to read the recording medium on which the program is recorded, thereby realizing the control processing described above. As the recording medium, various types of recording media such as a semiconductor memory for electrically recording information such as a CD-ROM, a flexible disk, and a magneto-optical disk can be used.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

  For example, the management ID is an example of identification information for identifying a device to be managed according to the present invention, and the generation method thereof is not limited to the method described above. For example, device identification information may be generated based on at least one of information unique to the management information generation apparatus of the present invention and information unique to the device to be managed. In addition, a device based on a combination of at least one of information unique to the management information generation device of the invention and information unique to the device to be managed and parameters specified by the user (setting information set according to the user's operation) The identification information may be generated. In addition, device identification information may be generated based on a combination of information unique to the management information generation apparatus of the invention and information unique to the device to be managed.

DESCRIPTION OF SYMBOLS 1 Network 100 Management ID provision apparatus 100a Management ID provision apparatus 100b Management ID provision apparatus 100c Management ID provision apparatus 100m Management ID provision apparatus 100n Management ID provision apparatus 100p Management ID provision apparatus 101 Communication part 102 Device connection part 103 Packet analysis part 104 Setting Information holding unit 105 Management ID giving unit 106 Setting screen generating unit 107 Management protocol holding unit 108 Packet conversion unit 200 Managed device 200m Managed device 200n Managed device 200p Managed device 201 Managed device 202 Managed device 203 Managed device 300 Management control device 400 PC for setting value change
500 Plug-in release server

JP 2005-303414 A

Claims (9)

A management information generating device connected to a management control device that manages a device via a first network and connected to the device to be managed via a second network,
Setting information holding means for holding address information of the management control device, at least one of information unique to the management information generation device and information unique to the device;
The address information of the destination device of the response packet is extracted from the response packet responding to the information acquisition request packet transmitted from the device, and the extracted address information and the address information held by the setting information holding unit And packet analysis means for determining whether to generate identification information of the device based on
If it is determined by the packet analysis unit that the identification information of the device is generated, based on at least one of the information unique to the management information generation device held in the setting information holding unit and the information specific to the device Management information generating means for generating identification information of the device;
A management information generating apparatus characterized by comprising: The setting information holding unit holds information on a protocol used by the management control device,
When the packet analysis unit determines to generate the device identification information, the packet analysis unit further extracts protocol information from the response packet, and extracts the protocol information and the protocol information stored in the setting information storage unit. Determining whether or not to generate identification information of the device based on the information;
The management information generating apparatus according to claim 1. The management information generating means obtains the identification information of the device based on at least one of setting information set according to a user operation, information unique to the management information generation device, and information unique to the device. Generate,
The management information generating apparatus according to claim 1 or 2, characterized by the above. The management information generating means includes identification information of the device in the response packet,
Communication means for transmitting a response packet including identification information of the device;
The management information generation device according to any one of claims 1 to 3. The management information generating means generates an attached packet including identification information of the device;
Communication means for transmitting the attached packet after transmitting the response packet;
The management information generation device according to any one of claims 1 to 3. Management protocol holding means for holding information of a plurality of protocols used by the management control device;
The setting information holding unit holds information of a specific protocol selected from a plurality of protocols stored in the management protocol holding unit;
The management information generation apparatus according to claim 1, wherein the management information generation apparatus is a management information generation apparatus. At least one of the address information of the management control device, the information unique to the device, the information of the protocol, and the setting information set according to the user's operation stored in the setting information holding unit One is set using the device or other device connected via the first network or the second network.
6. The management information generating apparatus according to claim 4, wherein the management information generating apparatus is a management information generating apparatus. The second network and the first network have different communication methods,
The data of the information acquisition request received via the first network is converted into a data format corresponding to the communication method of the second network, and the response data received via the second network is converted to the first data. Packet conversion means for converting to a data format according to the network communication method,
The management information generating apparatus according to claim 1, further comprising: A device management system in which a management control device that manages devices via a first network and a management information generation device are connected, and the device to be managed and the management information generation device are connected via a second network Because
Setting information holding means for holding address information of the management control device, at least one of information unique to the management information generation device and information unique to the device;
Extracting the address information of the destination device of the response packet from the response packet in response to the information acquisition request transmitted from the device, the extracted address information, the address information held by the setting information holding means, Packet analysis means for determining whether to generate identification information of the device based on
If it is determined by the packet analysis unit that the identification information of the device is generated, based on at least one of the information unique to the management information generation device held in the setting information holding unit and the information specific to the device Management information generating means for generating identification information of the device;
A device management system comprising:

Images