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

Description

The present invention relates to a device management system, a device management apparatus, a relay management apparatus, a device management method, a device management program, and a relay management program.

In a system in which a management PC and a managed PC are connected via a network, and a printer is locally connected to the managed PC, the managed PC obtains printer information from the printer, and the management PC obtains printer information from the managed PC. A configuration for acquiring is disclosed (see Patent Document 1). Also, a network printer is connected to the network of Document 1 without going through the managed PC.

JP-A-2005-128890

However, conventionally, management of network printers connected to the network without going through the managed PC and management of printers locally connected to the managed PC are controlled separately (different communication protocols, commands, etc.). It was executed under communication control using Therefore, under the network management protocol, it is possible to manage devices, such as obtaining information from locally connected devices and configuring settings for locally connected devices, from a management device connected to the network. I didn't. The present invention provides a device management system, a device management apparatus, a relay management apparatus, a device management method, a device management program, and a relay management program useful for solving the above problems.

One aspect of the present invention is a device management system in which a device management apparatus that manages devices and a relay management apparatus that connects a plurality of the devices via local communication paths are connected via a network, The device management apparatus is a first processing request according to a predetermined network management protocol for managing a management target connected to the network, and includes device identification information for identifying the device connected to the relay management apparatus. a first network communication unit configured to transmit the first processing request containing the first processing request to the relay management device via the network, wherein the relay management device receives the first processing request via the network; 2. A network communication unit, acquiring object identification information for identifying management information to be processed among the management information held by the device from the first process request, and generating a second process request including the object identification information. and a local communication unit that transmits the second processing request via the local communication path to the device indicated by the device identification information included in the first processing request.

The figure which shows the structure of a system simply. 6 is a flowchart showing device pre-search processing; 4 is a flowchart showing device management processing (device management method); 4A and 4B are diagrams showing structures of SNMP packets and USB commands in the first embodiment; FIG. FIG. 10 is a diagram showing structures of SNMP packets and USB commands in the second embodiment; FIG. 11 is a diagram showing structures of SNMP packets and USB commands in the third embodiment; 4 is a flow chart showing a modification of steps S300 to S320;

Hereinafter, embodiments of the present invention will be described with reference to each drawing. Note that each drawing is merely an example for describing the present embodiment.

1. Brief description of the system:
FIG. 1 simply shows the configuration of a system 1 according to this embodiment. At least part of the system 1 corresponds to a device management system. System 1 includes device management apparatus 10 and relay management apparatus 20 . The device management apparatus 10 and the relay management apparatus 20 are each realized by, for example, a personal computer (PC) or an information processing apparatus having a processing capability equivalent to that of the PC. Further, hardware capable of realizing the control unit 11 of this embodiment may be called a device management device, and hardware capable of realizing the control unit 21 of this embodiment may be called a relay management device.

The device management apparatus 10 and relay management apparatus 20 are each connected to a network 60 and can communicate with the outside via the network 60 . Network 60 may include, for example, a local area network (LAN) or the Internet.
Devices 30 , 40 and 50 are a plurality of devices to be managed by the device management apparatus 10 . The devices 30, 40, and 50 are, for example, printers, scanners, and multi-function machines having multiple functions such as printers and scanners.

In the example of FIG. 1, device 30 is connected to network 60 . Therefore, the device 30 corresponds to a network device managed by the device management apparatus 10. FIG. On the other hand, devices 40 and 50 are locally connected to relay management apparatus 20 via local communication paths 70, respectively. The local communication path 70 is, for example, a USB cable conforming to the USB (Universal Serial Bus) communication standard. Such devices 40 and 50 are also called locally connected devices. However, the devices 40 and 50 are called locally connected devices because they are connected to the relay management apparatus 20 via the local communication path 70, and even if they are connected to the network 60 like the device 30, For example, like the device 30, it functions as a network device. Needless to say, the number of network devices and locally connected devices need not be as shown in FIG. Also, the number of relay management apparatuses 20 recognized by the device management apparatus 10 is not limited to one. To distinguish between locally attached devices and network devices, the locally attached device may be referred to as the first device and the network device may be referred to as the second device.

The device management apparatus 10 includes, for example, a control unit 11, a display unit 17, an operation reception unit 18, a network (NW) communication interface (IF) 19, and the like. The control unit 11 includes one or a plurality of ICs having a CPU 11a, a ROM 11b, a RAM 11c, etc., and other storage media such as memories and hard disk drives (HDD) as appropriate. In the control unit 11, the CPU 11a controls behavior of the device management apparatus 10 by executing arithmetic processing according to programs stored in the ROM 11b or the like using the RAM 11c or the like as a work area. The control unit 11 is loaded with a program P1, and implements functions such as a search unit 12, a device selection unit 13, a first processing request generation unit 14, a NW communication control unit 15, etc. according to the program P1. The program P1 can be called a device management program that causes a computer (for example, the CPU 11a) to execute processing for managing devices via the network 60. FIG.

The NW communication IF 19 is used by the control unit 11 to communicate with the outside via the network 60 in compliance with predetermined communication standards (TCP/IP (Transmission Control Protocol/Internet Protocol), UDP (User Datagram Protocol), etc.). is a generic term for IF. The display unit 17 is means for displaying visual information, and is configured by, for example, a liquid crystal display (LCD), an organic EL display, or the like. The display unit 17 may be configured to include a display and a drive circuit for driving the display. The operation accepting unit 18 is means for accepting user operations, and is implemented by, for example, physical buttons, a touch panel, a mouse, a keyboard, and the like. Of course, the touch panel may be implemented as one function of the display unit 17 . Also, the display unit 17 and the operation reception unit 18 can be collectively referred to as an operation panel or the like.

The relay management device 20 includes, for example, a control unit 21, a NW communication IF 24, a local communication IF 25, and the like. The control unit 21 includes one or a plurality of ICs having a CPU 21a, a ROM 21b, a RAM 21c, etc., and other storage media such as memories and HDDs as appropriate. In the control unit 21, the CPU 21a controls the behavior of the relay management device 20 by executing arithmetic processing according to programs stored in the ROM 21b or the like using the RAM 21c or the like as a work area. The control unit 21 is loaded with the program P2, and realizes each function such as the second processing request generation unit 22, the communication control unit 23, etc. according to the program P2. The program P2 can be called a relay management program that causes a computer (for example, the CPU 21a) connected to a plurality of devices via the local communication path 70 to execute a process of relaying communication for managing the devices.

The NW communication IF 24 is a general term for IFs for the control unit 21 to communicate with the outside via the network 60 in compliance with a predetermined communication standard, like the NW communication IF 19 . The local communication IF 25 is an IF for locally connecting one or more devices to the relay management device 20. If the local communication path 70 is a USB cable as described above, the local communication IF 25 can be used with such a cable. Includes a USB port for connectivity. Needless to say, the relay management device 20 can also have an operation panel and the like, like the device management device 10 . Further, the communication control unit 23 is configured to identify and manage a plurality of local communication paths 70 that connect the locally connected devices by the connection number N. As shown in FIG. The connection number N is information assigned in order from a predetermined number (for example, N=0) to the plurality of local communication paths 70 to which the local connection device connects, and is a specific example of connection identification information.

The device management apparatus 10 manages managed objects connected to the network 60 according to a predetermined network management protocol for managing those managed objects. The predetermined network management protocol is Simple Network Management Protocol (SNMP). Therefore, this embodiment will be described on the premise that the devices 30, 40, and 50 are devices that support SNMP. The management of managed objects by SNMP includes the process of the SNMP manager requesting and acquiring information (management information) about the managed objects from the SNMP agent, and the SNMP manager requesting the SNMP agent to change the settings of the management information. Refers to the processing, etc., that causes the change to be executed. A device to be managed has a management information database called MIB (Management Information Base) relating to itself. Here, regarding the relationship between the device management apparatus 10 and the device 30 (network device) connected by the network 60, the device management apparatus 10 (program P1) is the SNMP manager, and the application resident in the device 30 (network device) is the SNMP agent. correspond to Then, in response to a processing request according to SNMP from the device management apparatus 10, the SNMP agent acquires information in the MIB of the device 30 (network device) and returns it to the device management apparatus 10, or writes information to the MIB. to run. That is, the first network communication unit of the device management apparatus 10 transmits a processing request according to SNMP to the network device via the network 60, and receives a response from the network device to the processing request via the network 60. .

Such management and monitoring of network devices such as the device 30 by the SNMP manager is general processing using SNMP. In addition to this, in this embodiment, the device management apparatus 10 treats the relay management apparatus 20 (program P2), to which the devices 40 and 50 are locally connected and also connected to the network 60, as a kind of SNMP agent. In other words, management of locally connected devices (devices 40 and 50) is also executed through communication with the relay management device 20 according to SNMP.

2. Device pre-discovery processing:
FIG. 2 is a flow chart showing device pre-search processing executed by the device management apparatus 10 prior to device management. In FIG. 2, processing on the side of the device management apparatus 10 and processing on the side of the relay management apparatus 20 are shown together.
First, on the side of the device management apparatus 10, the control unit 11 (search unit 12) designates the relay management apparatus 20 as a communication destination and transmits PING (step S100). In other words, the searching unit 12 causes the NW communication IF 19 to transmit a specific echo command (PING) to the destination (the IP address of the relay management device 20 or the like) acquired in advance.

On the relay management apparatus 20 side, when the control unit 21 receives the PING transmitted from the device management apparatus 10 via the NW communication IF 24 (step S200), it responds to the received PING (step S210). That is, the control unit 21 transmits the received PING to the device management apparatus 10 that is the source of the PING via the NW communication IF 24 .

On the side of the device management apparatus 10, the search unit 12 receives the response from the relay management apparatus 20 to the PING transmitted in step S100 (step S110). When the response to PING is received in this way, the search unit 12 confirms that communication with the relay management device 20 is possible via the network 60, and proceeds to step S120. If the response to the PING transmitted in step S100 cannot be received from the relay management device 20 (for example, due to timeout), the searching unit 12 performs the processing in FIG. End the process. Hereinafter, in the description of FIG. 2, the relay management device 20 that has been confirmed to be able to communicate via the network 60 by the processing of steps S100 and S110 is also called the target relay management device 20. FIG.

In step S<b>120 , the search unit 12 initializes the number (connection number N) used when searching for devices locally connected to the target relay management device 20 . That is, the connection number N=0.
In step S<b>130 , search unit 12 transmits a predetermined search packet for searching for a device with connection number N from NW communication IF 19 to target relay management device 20 . A search packet is a command that requests basic device information (manufacturing number (serial number), model name, corresponding SNMP version, other identification information such as MAC address and IP address, etc.). be. In each figure, the serial number of the device is abbreviated as "SN".

On the relay management apparatus 20 side, when the control unit 21 receives the search packet transmitted from the device management apparatus 10 via the NW communication IF 24 (step S220), it sends a response (search response) to the received search packet. (step S230). Specifically, when the control unit 21 receives the search packet, among the devices (for example, the devices 40 and 50) recognized via the local communication IF 25, the device basic information at the present time is sent as a response to the search packet. Device basic information about one device that has not yet been transmitted is transmitted to the device management apparatus 10 via the NW communication IF 24 as a response to the search packet received in step S220. That is, in step S230, the control unit 21 connects to the local communication path 70 identified by the connection number N specified by the search packet received in step S220, among the local communication paths 70 connected to the local communication IF 25. device basic information for the device to be sent as a response to the probe packet.

As can be seen from FIG. 2, each time step S130 is repeated, steps S220 and S230 are executed on the target relay management device 20 side. Note that when the control unit 21 receives the search packet in step S220, if there is no locally connected device that has not yet transmitted device basic information as a response to the search packet at this time, the control unit 21 sends a search response (step S230). Either it is not executed, or a predetermined error notification is sent as a search response (step S230).

On the device management apparatus 10 side, after transmitting the search packet with the connection number N to the target relay management apparatus 20 in step S130, the search unit 12 responds to the search packet with the connection number N (a normal response that is not an error notification). ) has been received via the NW communication IF 19 (step S140). Then, for example, if a normal response to the search packet of the connection number N can be received within a predetermined time after step S130 (that is, without timeout) ("Yes" in step S140), step Proceed to S150. On the other hand, after transmitting the search packet with the connection number N to the target relay management device 20 in step S130, the search unit 12 receives an error notification from the target relay management device 20 or responds to the search packet with the connection number N. If a (normal response that is not an error notification) has not been received by the timeout ("No" in step S140), the process of FIG. 2 ends.

In step S150, the search unit 12 stores the content of the response to the search packet of the connection number N determined to have been received in step S140. That is, the device basic information of one device locally connected to the target relay management device 20 is associated with the target relay management device 20, and stored in a predetermined storage unit (such as the RAM 11c of the control unit 11, or other storage unit). memory or HDD). In step S160 after step S150, the search unit 12 adds "1" to the current connection number N, and then repeats the processes after step S130.

According to the description of such pre-search processing, the relay management device 20 identifies the plurality of local communication paths 70 by the connection identification information. The device management apparatus 10 transmits a request, that is, a search packet including the designation of the connection identification information to the relay management apparatus 20 via the network 60, and the device of the device connected to the local communication path 70 corresponding to the designated connection identification information. Basic information is received from relay management device 20 via network 60 . As a result, the device management apparatus 10 acquires device basic information such as the serial number of each device (for example, the devices 40 and 50) locally connected to the relay management apparatus 20 that can communicate via the network 60. , can be stored. Of course, if a plurality of relay management apparatuses 20 are connected to the network 60, the device management apparatus 10 executes such pre-search processing for each relay management apparatus 20 and is locally connected to each relay management apparatus 20. Get basic device information for each device. In addition to the preliminary search processing shown in FIG. 2, the device management apparatus 10 broadcasts a search packet according to SNMP on the network 60, and receives a response from the network device that received the broadcast search packet. By doing so, the basic device information of each network device (for example, the device 30) connected to the network 60 can also be acquired and stored.

3. Device management processing:
FIG. 3 shows the device management processing by means of a flowchart. FIG. 3 also shows the processing on the side of the device management apparatus 10, the side of the relay management apparatus 20, and the side of devices locally connected to the relay management apparatus 20 (locally connected devices).
On the side of the device management apparatus 10, the control unit 11 (device selection unit 13) selects a device to be a target of management processing from among the devices whose basic device information has already been stored (step S300). Various device selection methods are conceivable. For example, the device selection unit 13 may automatically select each device whose basic device information is stored one by one at predetermined time intervals as a target of management processing. .

Alternatively, the device selection unit 13 may select a device according to user's operation. In this case, the device selection unit 13 causes the display unit 17 to display the device list based on the device basic information for each device stored in the device management apparatus 10 . The device list presents the user with a list of devices that can be managed, for example, by listing information such as the model name and identification information (serial number, MAC address, IP address, etc.) of each device. The user can arbitrarily select a device from the device list displayed on the display section 17 by operating the operation reception section 18 . The device selection unit 13 selects a device (accepts selection of a device by the user) according to such user's operation.

In step S310, the control unit 11 (first processing request generation unit 14) generates a communication packet (SNMP packet) containing the serial number of the device selected in step S300 (hereinafter, selected device). A serial number is an example of device identification information that identifies a device. The SNMP packet generated in step S310 is a first processing request conforming to a predetermined network management protocol (SNMP) and containing device identification information for identifying a device connected to relay management device 20. Applicable.

In step S320, the control unit 11 (NW communication control unit 15) causes the SNMP packet generated in step S310 to be transmitted from the NW communication IF 19 to the relay management device 20 to which the selected device is locally connected (first process request transmission step). The NW communication IF 19 corresponds to the first network communication section.

On the relay management device 20 side, the control unit 21 (communication control unit 23) receives the SNMP packet transmitted from the device management device 10 as described above via the NW communication IF 24 (step S400, first processing request receiving process). The NW communication IF 24 corresponds to the second network communication section.

In step S410, control unit 21 determines that the device (selected device) corresponding to the serial number included in the SNMP packet received in step S400 is currently communicating with itself (relay management device 20) via local communication IF 25. After confirming that the connection is possible, the process proceeds to step S420. If the device (selected device) corresponding to the serial number included in the SNMP command received in step S400 is not currently communicably connected via the local communication IF 25, the control unit 21 performs step The process of FIG. 3 is ended without executing the process after S420. In this case, step S460 (transmitting an SNMP packet from the relay management apparatus 20 to the device management apparatus 10), which will be described later, is not executed.

In step S420, the control unit 21 (second processing request generation unit 22) generates a USB command as a processing request (second processing request) to the selected device based on the SNMP packet received in step S400 ( second process request generating step).

FIG. 4 shows structural examples of SNMP packets and USB commands, respectively.
The content shown in FIG. 4 is also called a first example in this embodiment.
The SNMP packet 80 is an SNMP packet transmitted from the device management apparatus 10 to the relay management apparatus 20 via the network 60 in step S320, and is a packet in a format corresponding to SNMP versions SNMPv1 and SNMPv2. The SNMP packet 80 includes a version area 81 describing the version of SNMP to which the SNMP packet 80 corresponds, a community area 82 describing a community name used for limiting access to the MIB, and data (SNMP PDU (Protocol Data Unit) ) region 83 .

More specifically, the area 83 includes a PDU type (SNMP command type) area 84 , a request ID area 85 , an error status area 86 , an error index area 87 and a variable binding area 88 . The variable binding area 88 has a plurality of fields for describing combinations of OIDs (Object Identifiers) for identifying management information (objects) stored in the MIB of the device and values of the objects corresponding to the OIDs. are divided into regions 88-1, 88-2, . . . The OID stored in the variable binding area 88 corresponds to object identification information for identifying management information to be processed among the management information held by the device.

In the SNMP packet 80 having such a structure, the serial number of the selected device is written in the community area 82 in this embodiment. That is, in step S310, the first processing request generator 14 generates the SNMP packet 80 in which the serial number of the selected device selected in step S300 is described in the community area 82. FIG.

In step S420, the second processing request generator 22 generates a USB command by adding a predetermined USB header 101 to the SNMP PDU (area 83) of the SNMP packet 80. FIG. At this time, the second processing request generation unit 22 generates USB commands that are separated for each combination of the OID and the value in the variable binding area 88 of the area 83 . In the example of FIG. 4, for the variable binding area 88, only the area 88-1 is cut out, and the USB command 100 added with the USB header 101 is added to the area 83. For the variable binding area 88, only the area 88-2 is cut out. 83, a USB command 110 to which the USB header 101 is added is generated.

The USB header 101 is a header that can be interpreted by a device (USB device) that is locally connected to the relay management device 20. By adding the USB header 101, a type of command conforming to the USB communication standard can be used. will be handled by the USB device as In executing step S420 as described above, the second processing request generation unit 22 extracts from the first processing request (SNMP packet) object identification information (OID) that identifies the management information to be processed among the management information possessed by the selected device. ) and generates a second processing request (USB command) including the OID.

In step S430, the controller 21 (communication controller 23) controls the device (selected device) indicated by the serial number (described in the community area 82 of the SNMP packet 80) included in the SNMP packet received in step S400. ) via the local communication IF 25, the USB command generated in step S420 is transmitted (second processing request transmission step). According to the example of FIG. 4, at step S430, USB commands 100 and 110 are transmitted to the device (selected device) indicated by the serial number via the local communication IF 25. FIG. The local communication IF 25 corresponds to the local communication section.

A locally connected device (for example, device 40 ) locally connected to relay management device 20 as a selected device receives USB commands (USB commands 100 and 110 ) from relay management device 20 via local communication path 70 . (Step S500). The selected device then responds to the USB command received in step S500 (step S510).

For example, if the PDU type (area 84) of the USB commands 100 and 110 indicates a Get request, the selected device reads the management information corresponding to the OID specified in the USB command 100 from its own MIB. Management information is written in the area 88-1 of the USB command 100 as a value corresponding to the OID. Similarly, the selected device reads the management information corresponding to the OID specified in the USB command 110 from its own MIB, and uses the read management information as a value corresponding to the OID in the area 88- of the USB command 110. Write to 2.

Also, for example, if the PDU type (area 84) of the USB commands 100 and 110 indicates a Set request, the selected device stores the management information in its own MIB corresponding to the OID specified in the USB command 100, It is rewritten with the corresponding value (Value), and the effect of rewriting is written in the area 83 of the USB command 100 . Similarly, the selected device rewrites the management information in its own MIB corresponding to the OID specified in the USB command 110 with the corresponding value (Value), and writes the rewritten information in the area 83 of the USB command 110. .

Examples of management information include the remaining amount of consumables such as printer (device) ink and toner, status such as device errors and startup status, and network settings such as the IP address set in the device. . The selected device responds by replying or rewriting the management information specified by the OID. For convenience, the USB commands 100 and 110 that have undergone such processing on the selected device side are referred to as USB commands 100' and 110' (see FIG. 4). The selected device then transmits the USB commands 100' and 110' after such processing to the relay management device 20 via the local communication path 70 as a response to step S510 (step S510).

On the relay management device 20 side, after transmitting the USB command to the selected device in step S430, the control unit 21 continuously determines whether or not the response to the USB command has been received via the local communication IF 25. (Step S440). Then, for example, if a response to the USB command can be received within a predetermined time after step S430 (that is, without timeout) ("Yes" in step S440), the process proceeds to step S450. On the other hand, after transmitting the USB command to the selected device in step S430, if the control unit 21 fails to receive a response to the USB command before the timeout expires ("No" in step S440), End the process. For example, if the selected device is busy, such as during firmware update processing, the selected device may not be able to respond to the USB command from the relay management device 20 .

When it is determined that the selected device is not communicably connected via the local communication IF 25 in connection confirmation in step S410 described above, and when it is determined "No" in step S440, step S460 (from the relay management device 20 From the point of view of the device management apparatus 10, the same result is obtained in that the transmission of the SNMP packet to the device management apparatus 10) is not executed.

If an error occurs during each process corresponding to the USB commands 100 and 110 received in step S500, the selected device relays the USB commands 100' and 110' in which information about the error is written as a response in step S510. Send to the management device 20 . Specifically, the selected device writes the error number of the error that has occurred in the error status area 86, and writes the position in the variable binding area 88 where the error has occurred in the error index area 87. is sent to relay management device 20 as a response to step S510.

In step S450, the control unit 21 (second processing request generation unit 22) generates an SNMP packet based on the response from the selected device (USB command after processing by the selected device). For example, referring to FIG. 4, the second processing request generation unit 22 synthesizes portions of SNMP PDUs (region 83) from which the USB header 101 has been removed from the USB commands 100' and 110' processed by the selected device. Then, by adding a version area 81 and a community area 82, one SNMP packet 80' corresponding to the format of the original SNMP packet is generated. Of course, the values (Value) for each of the areas 88-1, 88-2, . In comparison with the SNMP packet 80 received from 10, the content has been appropriately rewritten according to the processing by the selected device.

In step S460, the control unit 21 (communication control unit 23) causes the NW communication IF 24 to transmit the SNMP packet generated in step S450 to the device management apparatus 10, which is the transmission source of the SNMP packet received in step S400.
As a result, on the device management apparatus 10 side, the control unit 11 (NW communication control unit 15) receives the SNMP packet transmitted from the relay management apparatus 20 via the NW communication IF 19 (step S330). By reading information from the SNMP packet received in step S330, the control unit 11 acquires management information (for example, remaining amount of ink in the device as a printer) related to the selected device selected in step S300, or obtains information about the selected device. The selected device can be monitored by recognizing that the setting of the management information has been changed in the device. As a response to the SNMP packet transmission in step S320, if no SNMP packet is transmitted from the relay management apparatus 20 within a predetermined time, the control unit 11 determines that the selected device selected in step S300 is the relay management apparatus 20. is determined to be unconnected.

Thus, according to the present embodiment, the device management apparatus 10 that manages the devices 30, 40, 50, . A system 1 connecting via 60 is disclosed. The device management apparatus 10 (control unit 11) receives a first processing request according to a predetermined network management protocol (SNMP) for managing a management target connected to the network 60, and a device connected to the relay management apparatus 20. A first processing request (SNMP packet 80) containing device identification information (for example, a serial number) for identifying a is transmitted to the relay management device 20 via the network 60 (step S320). On the other hand, the relay management device 20 receives the first processing request via the network 60 (step S400), and from the first processing request, the target identification information ( OID), generates a second processing request (USB commands 100 and 110 including SNMP PDU (area 83)) including the target identification information (step S420), and A second processing request is transmitted via the local communication path 70 to the device indicated by the device identification information (step S430).

According to this configuration, the device management apparatus 10 issues a processing request (first processing request) according to SNMP when managing a locally connected device as well as when managing a network device (for example, the device 30). , to the relay management device 20 . However, at this time, the device identification information of the device locally connected to the relay management device 20 is included in the first processing request. Therefore, upon receiving the first processing request via the network 60, the relay management device 20 generates a processing request (second processing request) to be transmitted to the device locally connected to itself based on the first processing request, This second processing request (USB command) can be sent via the local communication path 70 to the device indicated by the device identification information included in the first processing request.

Also, the relay management apparatus 20 converts the response to the second processing request received from the device locally connected to itself into the SNMP packet format when transmitting it to the device management apparatus 10 via the network 60. (Steps S450, S460). For example, the relay management device 20 receives, via the local communication path 70, management information corresponding to the target identification information as part of the response to the second processing request from the destination device of the second processing request, The received management information is included in an SNMP packet and transmitted to the device management apparatus 10 via the network 60 . In the management of locally connected devices by the device management apparatus 10 via the relay management apparatus 20, as described above, in addition to the process of transmitting a processing request and acquiring management information from the locally connected device, a processing request is transmitted. It also includes a process of causing the locally connected device to change the setting of the management information, that is, to rewrite the management information.

That is, the device management apparatus 10 can manage locally connected devices using SNMP. As a result, the burden on the device management apparatus 10 can be significantly reduced compared to the conventional system in which the management of locally connected devices and network devices is performed under completely different communication controls. In addition, in the past, management of locally connected devices and network devices was performed under different communication controls, so there were differences in the types of management information that could be obtained from locally connected devices and network devices. In this embodiment, such an adverse effect can also be eliminated. Further, according to the first embodiment (FIG. 4), the device management apparatus 10 can easily specify the device to which the processing request is to be sent to the relay management apparatus 20 by using the community name in the SNMP packet. .

Several examples and modifications included in this embodiment will be described below. Descriptions of matters overlapping with the matters described so far will be omitted.

4. Second embodiment:
FIG. 5 shows the structures of SNMP packets and USB commands according to the second embodiment.
As described above, in step S310 (FIG. 3), the control unit 11 (first processing request generation unit 14) generates an SNMP packet containing the serial number of the selected device selected in step S300. At this time, in the second embodiment, the first processing request generation unit 14 generates an SNMP packet 80 as shown in FIG. 5 (step S310), and the NW communication control unit 15 relays the generated SNMP packet 80. It is transmitted to the management device 20 (step S320). The SNMP packet 80 according to the second embodiment does not have the serial number of the selected device in the community area 82, but adds the serial number to the value description area of the management information.

Specifically, as shown in FIG. 5, in the variable binding area 88 of the SNMP packet 80, in each of a plurality of areas (for example, area 88-1) for describing the combination of OID and value , a specific OID is described as the OID, and the serial number (area 88-1a) and SNMP PDU (area 88-1b) of the selected device are described in a value description area corresponding to the specific OID.

That is, in the area 88-1b, SNMP PDUs are inserted in a nested structure as entities of processing requests to be sent to the selected device. The SNMP PDU inserted in the area 88-1b is the object identification information (OID) to be transmitted from the relay management device 20 to the selected device in the form of the second processing request and the management information corresponding to the object identification information. It is an SNMP compliant command that includes a value description area and a value binding area in the form of a variable binding area. On the other hand, other than such specific OID, serial number (field 88-1a) and SNMP PDU (field 88-1b), the portion of the SNMP packet 80 (FIG. 5) is formatted according to SNMP. serves only as a container to contain a specific OID, serial number (field 88-1a) and SNMP PDU (field 88-1b).

The specific OID is not an OID for identifying management information in the MIB owned by the device, but a data structure in which the serial number and SNMP PDU of the selected device are inserted in the value description area in the variable binding area 88. It is specific identification information indicating that

In the second embodiment as described above, in step S410 (FIG. 3), the control unit 21 responds to the fact that the variable binding area 88 of the SNMP packet 80 received in step S400 contains the specific OID. The serial number can be read from the area 88-1a of the value description area corresponding to the OID. As a result, the connection confirmation for the device (selected device) corresponding to the serial number is performed. Further, in step S420, the control unit 21 (the second processing request generation unit 22) generates an SNMP PDU (area 88-1b) is extracted, and the USB header 101 described above is added to the extracted area 88-1b to generate a USB command (USB command 100 in the example of FIG. 5) as the second processing request.

Further, in step S430, the control unit 21 (communication control unit 23) selects the device (selected device) indicated by the serial number read from the area 88-1a of the value description area corresponding to the specific OID as described above. to, via the local communication IF 25, the USB command generated in step S420. Also, in step S450, the control unit 21 (second processing request generating unit 22) generates an SNMP packet based on the response from the selected device (USB command after processing by the selected device). In other words, referring to FIG. 5, the second processing request generating unit 22 places the portion of the SNMP PDU (area 88-1b) obtained by removing the USB header 101 from the USB command 100′ processed by the selected device into the variable binding area 88. One SNMP packet 80' corresponding to the format of the original SNMP packet is generated by backfilling the description area of the value (Value) corresponding to the specific OID. Of course, the value (Value) corresponding to the OID, the error status area and the The error index area and the like are compared with the SNMP packet 80 received from the device management apparatus 10 in step S400, and the contents are appropriately rewritten according to the above-described processing by the selected device.

According to the second embodiment (FIG. 5), the device management apparatus 10 transmits, as the first processing request, an SNMP packet including device identification information in the management information description area of the SNMP packet. According to this configuration, it is possible to easily specify the device to which the processing request is to be sent to the relay management device 20 by using the management information value description area in the SNMP packet (first processing request). .
In the second embodiment, the area 88-1b of the value description area corresponding to the specific OID contained in the variable binding area 88 of the SNMP packet 80 contains an SNMP PDU (a form of the second processing request). command to be transmitted from the relay management apparatus 20 to the selected device) may be inserted, but the entire SNMP packet including this SNMP PDU may be inserted in a nested structure.

5. Third embodiment:
FIG. 6 shows the structures of SNMP packets and USB commands according to the third embodiment. The SNMP packet according to the third embodiment, when compared with the second embodiment (FIG. 5), has The data to be inserted is different. The insertion position of the serial number in the SNMP packet is common between the second embodiment and the third embodiment.

In the third embodiment, a packet (SNMPv3 packet) having a format corresponding to SNMP version SNMPv3 is inserted in the area 88-1b. As is known, the SNMPv3 packet does not use a community name unlike the SNMPv1 and SNMPv2 formats, but it has security-related settings (security model, security parameters, etc.). Also, the SNMPv3 packet includes the same SNMP PDU (area 88-1b1 shown in FIG. 6) as described above, and the SNMP PDU in this SNMPv3 packet is the SNMP packet 80 sent by the device management apparatus 10. At the time of generation (step S310 in FIG. 3), it is encrypted with a predetermined password. That is, the encrypted SNMP PDU among the SNMPv3 packets inserted in the area 88-1b is the target identification information (OID) to be transmitted from the relay management device 20 to the selected device in the form of the second processing request. The main part of the command according to SNMP, which includes a description area for the value of management information corresponding to the target identification information and a variable binding area in the form of a variable binding area.

The SNMP packets according to the third embodiment are apparently packets of formats corresponding to versions SNMPv1 and SNMPv2, but it can be said that some of them contain SNMPv3 packets of a format corresponding to version SNMPv3. In step S420 according to the third embodiment, the control unit 21 (the second processing request generation unit 22) fills the description area of the value (Value) corresponding to the specific OID included in the variable binding area 88 of the SNMP packet 80. The SNMPv3 packet (area 88-1b) is extracted, the USB header 101 described above is added to the extracted SNMPv3 packet (area 88-1b), and the USB command (in the example of FIG. 6, the USB command 100).

In addition, in the third embodiment, the selected device that has received the USB command as the second processing request in step S500 uses the security model and security set in the SNMPv3 packet (area 88-1b) included in the USB command. The SNMP PDU (area 88-1b1) in the SNMPv3 packet (area 88-1b) is decrypted based on the parameters and the password held in advance (by user's operation or the like). The SNMP PDU decrypted in this way is the entity of the processing request from the device management apparatus 10 to the selected device. Therefore, the selected device responds to the USB command as described above based on the decrypted SNMP PDU (step S510). In this case, after writing the value specified by the OID in the decrypted SNMP PDU, the selected device encrypts the SNMP PDU again using the password, and then encrypts the encrypted SNMP PDU. A USB command 100' (FIG. 6) containing an SNMPv3 packet (data area 88-1b) containing the SNMP PDU is transmitted to the relay management device 20 as a response to the USB command 100 (step S510).

In step S450, the control unit 21 (second processing request generating unit 22) generates an SNMP packet based on the response from the selected device (USB command after processing by the selected device). In other words, referring to FIG. 6, the second processing request generating unit 22 places the portion of the SNMPv3 packet (area 88-1b) in which the USB header 101 is removed from the USB command 100′ processed by the selected device in the variable binding area 88. One SNMP packet 80' corresponding to the format of the original SNMP packet is generated by backfilling the description area of the value (Value) corresponding to the specific OID. Of course, it corresponds to the OID included in the SNMP PDU (area 88-1b1) in the SNMPv3 packet (area 88-1b) in the variable binding area 88 of the SNMP packet 80' (FIG. 6) according to the third embodiment. The value (Value), the error status area, the error index area, etc. are compared with the SNMP packet 80 received from the device management apparatus 10 in step S400, and the contents are appropriately rewritten according to the processing by the selected device. . In addition, in the third embodiment, the device management apparatus 10, which received the SNMP packet 80' from the relay management apparatus 20 in step S330, naturally uses the password to transmit the SNMP PDU (area 88-1b1) of the SNMP packet 80'. You can decrypt it to get the information you need.

By the way, a device capable of receiving and processing a processing request (USB command 100 shown in FIG. 6) including an SNMPv3 packet as described above is a device capable of supporting version SNMPv3. Therefore, assuming the third embodiment, in step S320 (FIG. 3), the device management apparatus 10 performs the first SNMP authentication according to the version of SNMP to which the device (selected device) indicated by the device identification information (serial number) corresponds. A processing request (SNMP command) is transmitted.

FIG. 7 is a flow chart showing a modification of part of the processing (steps S300 to S320) of the device management apparatus 10 shown in FIG.
After selecting a device in step S300, the control unit 11 of the device management apparatus 10 determines in step S305 the version of SNMP supported by the selected device selected in step S300. The control unit 11 obtains device basic information for each device through the above-described preliminary search process (FIG. 2), and the device basic information includes the version of SNMP that the device supports. Therefore, based on the device basic information for each device, the control unit 11 determines whether the selected device is compatible with version SNMPv3 or not (compatible with either version SNMPv1 or SNMPv2). .

If the selected device does not support version SNMPv3 but supports either version SNMPv1 or SNMPv2, the control unit 11 proceeds to step S312. Proceed to S314. Both steps S312 and S314 correspond to step S310 (FIG. 3) of generating an SNMP packet containing the serial number of the selected device.

However, in step S312, the control unit 11 generates SNMP packets corresponding to versions SNMPv1 and SNMPv2. Specifically, in step S312, an SNMP packet according to the first embodiment (FIG. 4) or the second embodiment (FIG. 5) is generated. On the other hand, in step S314, the control unit 11 generates an SNMP packet corresponding to version SNMPv3. Specifically, in step S314, an SNMP packet according to the third embodiment (FIG. 6) is generated. The SNMP packet according to the third embodiment contains a processing request (SNMPv3 packet) conforming to version SNMPv3 in the SNMP PDU (area 83) (FIG. 6), and is considered to be a kind of SNMP packet corresponding to version SNMPv3. I can say Of course, in step S320 after step S312, control unit 11 transmits the SNMP packet generated in step S312 to relay management device 20, and in step S320 after step S314, control unit 11 performs step S314. to the relay management device 20.

According to the second embodiment and the third embodiment, the device management apparatus 10 stores the target identification information and the corresponding target identification information in the management information description area in the first processing request in the format according to SNMP. A command conforming to SNMP including a management information description area is inserted and transmitted as a first processing request. In other words, the device management apparatus 10 sends a command in a format conforming to SNMP including, in a part of the SNMP packet 80, the target identification information (OID) and the description area of the management information value (Value) corresponding to the target identification information. (SNMP PDU (area 88-1b in FIG. 5 or area 88-1b1 in FIG. 6)) is inserted into the nested first processing request. Relay management device 20 then generates a second processing request including the command. As a result, by encrypting the insertion portion, the security of the USB command transmitted as the second processing request to the device locally connected to the relay management device 20 can be easily enhanced. In particular, according to the third embodiment, the first processing request is transmitted by inserting an SNMPv3 packet according to version SNMPv3 into part of the SNMP packet 80 . As a result, the processing request can be transmitted from the device management apparatus 10 to the selected device while maintaining the security of the substance of the processing request to be transmitted to the selected device.

Further, according to this embodiment, the control unit 11 of the device management apparatus 10 includes the search unit 12 that obtains the version of SNMP supported by the device connected to the relay management apparatus 20 by searching via the network 60 . Then, the control unit 11 of the device management apparatus 10 sends a first processing request (SNMP packet) that includes the device identification information (serial number) of the selected device and conforms to the SNMP version corresponding to the selected device indicated by the device identification information. to the relay management device 20 (FIG. 7). As a result, the device management apparatus 10 can transmit an appropriate first processing request according to the processing capability of the device that is the transmission destination of the processing request locally connected to the relay management apparatus 20 .

Other examples:
In this embodiment, the predetermined network management protocol for managing managed objects connected to the network 60 is not limited to SNMP, and various protocols used for network monitoring can be adopted. Also, the communication standard for locally connecting the relay management apparatus 20 and the device is not limited to USB, and various communication standards that allow the device and a PC or the like to be connected without a network can be adopted.

As is clear from the description so far, the present embodiment includes a relay management apparatus connected to a plurality of devices via local communication paths, and a device management apparatus connected via a network. The first processing request, which is a first processing request according to a predetermined network management protocol for managing an object to be managed and which includes device identification information for identifying the device connected to the relay management device, is sent to the network. to the relay management device via.

Further, in this embodiment, a relay management apparatus is connected to a plurality of devices via a local communication path and connected via a network to a device management apparatus that manages the devices. sending a first processing request according to a predetermined network management protocol for managing an object, the first processing request including device identification information for identifying the device, from the device management apparatus via the network; receiving, acquiring from the first processing request, target identification information for identifying management information to be processed from among the management information held by the device, generating a second processing request including the target identification information, A configuration is provided for transmitting the second processing request via the local communication path to the device indicated by the device identification information included in the processing request.

Further, the present embodiment includes a program that causes a device management apparatus to execute the above-described process (a device management program that causes a computer to execute a process for managing devices via a network) and a program that causes a relay management apparatus to execute the above-described process. (a relay management program that causes a computer connected to a plurality of devices via a local communication path to execute a process of relaying communication for device management). Of course, this embodiment also provides a computer-readable storage medium storing these programs.

In addition, the present embodiment includes methods corresponding to the device management apparatus and the relay management apparatus, and methods including these methods (a device management apparatus that manages devices and a plurality of devices that are connected via local communication paths). It also provides a device management method for a system in which a relay management device connected via a network.

DESCRIPTION OF SYMBOLS 1... System, 10... Device management apparatus, 11... Control part, 12... Search part, 13... Device selection part, 14... First processing request generation part, 15... NW communication control part, 17... Display part, 18... Operation Reception unit 19 NW communication IF 20 relay management device 21 control unit 22 second processing request generation unit 23 communication control unit 24 NW communication IF 25 local communication IF 30, 40 , 50... device, 60... network, 70... local communication path, P1, P2... program

Claims (13)

A device management system in which a device management apparatus that manages devices and a relay management apparatus that connects the plurality of devices via local communication paths are connected via a network,
The device management device
A first processing request according to a predetermined network management protocol for managing a managed object connected to the network, the first processing including device identification information for identifying the device connected to the relay management device. a first network communication unit that transmits a request to the relay management device via the network;
The relay management device
a second network communication unit that receives the first processing request via the network;
a generating unit that acquires, from the first processing request, target identification information that identifies management information to be processed from among the management information held by the device, and generates a second processing request that includes the target identification information;
a local communication unit that transmits the second processing request via the local communication path to the device indicated by the device identification information included in the first processing request ;
The relay management device identifies the plurality of local communication paths by connection identification information,
The device management apparatus transmits a request including the designation of the connection identification information to the relay management apparatus via the network, and the device connected to the local communication path corresponding to the designated connection identification information. A device management system , wherein device identification information is received from the relay management apparatus via the network . the local communication unit receives, via the local communication path, the management information corresponding to the target identification information from the device to which the second processing request is sent;
2. The device management system according to claim 1, wherein said second network communication unit transmits said management information received by said local communication unit to said device management apparatus via said network. 3. The device management system according to claim 1, wherein said network management protocol is a simple network management protocol. The first network communication unit transmits, as the first processing request, the communication packet in which the device identification information is described in a community name description area in the communication packet according to the network management protocol. The device management system according to any one of claims 1 to 3. The first network communication unit transmits, as the first processing request, the communication packet including the device identification information in the management information description area in the communication packet according to the network management protocol. The device management system according to any one of claims 1 to 3. The first network communication unit inserts a command according to the network management protocol including the target identification information and a management information description area corresponding to the target identification information into the management information description area. transmitting a communication packet as the first processing request;
6. The device management system according to claim 5, wherein said generation unit generates said second processing request including said command. The device management device comprises a search unit that acquires the version of the network management protocol supported by the device connected to the relay management device by searching through the network,
The first network communication unit includes the device identification information, and transmits the first processing request according to the version of the network management protocol supported by the device indicated by the device identification information. The device management system according to any one of claims 1 to 6. The first network communication unit transmits a processing request according to the network management protocol to a second device connected to the network via the network, and receives a response from the second device to the processing request. , through said network. A relay management device connected to a plurality of devices via a local communication path, and a device management device connected via a network,
transmitting, via the network, a request including the designation of the connection identification information to the relay management device that identifies the plurality of local communication paths by the connection identification information;
receiving device identification information for identifying the device connected to the local communication path corresponding to the specified connection identification information from the relay management device via the network;
A first processing request in accordance with a predetermined network management protocol for managing a managed object connected to the network, the first processing request including the device identification information of the device connected to the relay management device. to the relay management apparatus via the network. A relay management device connected to a plurality of devices via a local communication path and connected via a network to a device management device that manages the devices,
identifying the plurality of local communication paths by connection identification information;
receiving a request including the specification of the connection identification information from the device management apparatus via the network;
transmitting device identification information identifying the device connected to the local communication path corresponding to the designated connection identification information to the device management apparatus via the network;
a first processing request according to a predetermined network management protocol for managing a managed object connected to the network, the first processing request including the device identification information of the device being transmitted via the network; received from the device management apparatus;
obtaining, from the first processing request, target identification information identifying management information to be processed among the management information held by the device, and generating a second processing request including the target identification information;
A relay management apparatus that transmits the second processing request to the device indicated by the device identification information included in the first processing request via the local communication path. A device management method for a system in which a device management apparatus that manages devices and a relay management apparatus that connects the plurality of devices via local communication paths are connected via a network,
a step of transmitting, via the network, a request including the designation of the connection identification information from the device management apparatus to the relay management apparatus that identifies the plurality of local communication paths by connection identification information;
a step in which the device management apparatus receives device identification information identifying the device connected to the local communication path corresponding to the designated connection identification information from the relay management apparatus via the network;
A first processing request in accordance with a predetermined network management protocol for managing a managed object connected to the network, the first processing request including the device identification information of the device connected to the relay management device. from the device management apparatus to the relay management apparatus via the network;
a first processing request receiving step in which the relay management device receives the first processing request via the network;
The relay management device acquires, from the first processing request, target identification information for identifying management information to be processed from among the management information held by the device, and generates a second processing request including the target identification information. 2 a process request generation step;
a second processing request transmission step of transmitting the second processing request by the relay management device to the device indicated by the device identification information included in the first processing request via the local communication path; A device management method characterized by: A device management program that causes a computer to execute processing for managing a device via a network,
A relay management apparatus that connects to a plurality of the devices via local communication paths and connects to the computer via the network, wherein the relay management apparatus identifies the plurality of local communication paths by connection identification information. to, a function of transmitting a request including the specification of the connection identification information via the network;
a function of receiving device identification information for identifying the device connected to the local communication path corresponding to the designated connection identification information from the relay management apparatus via the network;
A first processing request according to a predetermined network management protocol for managing a managed object connected to the network, the first processing request including the device identification information of the device connected to the relay management device. and a function of transmitting a processing request to the relay management apparatus via the network. A relay management program that causes a computer connected to a plurality of devices via a local communication path to execute a process of relaying communication for managing the devices,
a function of identifying the plurality of local communication paths by connection identification information;
a function of receiving a request including the specification of the connection identification information from a device management apparatus via a network;
a function of transmitting device identification information identifying the device connected to the local communication path corresponding to the specified connection identification information to the device management apparatus via the network;
a first processing request according to a predetermined network management protocol for managing a managed object connected to the network, the first processing request including the device identification information of the device being transmitted via the network; a function of receiving from the device management apparatus;
a function of acquiring, from the first processing request, target identification information identifying management information to be processed from among the management information held by the device, and generating a second processing request including the target identification information;
and a function of transmitting the second processing request to the device indicated by the device identification information included in the first processing request via the local communication path.

Images