JP2001282657A - Management system managing device over network - Google Patents

Abstract

PROBLEM TO BE SOLVED: To facilitate and speed up acquiring of information for management as to a device over a network. SOLUTION: For a management system provided on the network, a management block which generates management information and an MIB gateway which obtains device information representing the operation state of a printer as an object to be managed are constituted as functional blocks. The MIB gateway uses protocols discriminatingly by printers as the request of the management block to obtain the device information. The obtained information is stored as a virtual MIB by groups which are defined by departmentalizing MIBs of the respective printers. The management block accesses the virtual MIB to obtain information. Consequently, the management block is able to obtain the device information by a standardized protocol. Information that the virtual MIB has generated can be obtained rapidly, without the need to access a printer.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a management system for managing devices connected to a network, and more particularly, to flexibly and quickly transfer management information between a device having a wide variety of management protocols and the management system. About technology.

[0002]

2. Description of the Related Art In recent years, with the spread of a LAN (Local Area Network), a mode in which a printer is connected to a network and shared by a plurality of computers connected to the same network is spreading. A printer user selects a printer as an output destination from a computer connected to a network, submits a print job, and performs printing via the network.

When sharing a printer, a network administrator is usually provided. The administrator exchanges information between the management computer and each printer via a network to manage the status of each printer.

There are two methods for exchanging information regarding the status of the printer (hereinafter referred to as device information). One is SNMP (Simple Network Management Pr
otocol) and MIB (Management Information B)
ase) A method of exchanging information. On the printer side, a MIB database in which predetermined device information is stored at a predetermined address is facilitated. In SNMP, information in this database is exchanged by designating an address. When an agent that responds to the inquiry from the management system with appropriate MIB information is provided in the printer, there is an advantage that device information can be exchanged uniformly by SNMP.

Another method for exchanging device information is as follows:
This is a method that uses a command set specifically for the printer. According to this method, although the burden on the printer side is low, the management system needs to use a command corresponding to the printer, and the management process becomes complicated.

[0006]

When a printer is shared, various types of printers having different device information transfer methods are often managed. Conventionally, the management system acquires device information by using SNMP and printer-specific commands for each printer to be managed. Therefore, the processing of the management system has been complicated. In addition, in order to add a printer with a different available command to the management target, it is necessary to modify the entire management system.

If the number of printers to be managed increases,
It takes a long time to acquire device information of each printer. Therefore, conventionally, as the number of printers increases, the responsiveness of the management system decreases. If all the device information of the printer is stored in the management system, the response time can be reduced. However, this method causes another problem that the management information becomes enormous with the increase in the number of printers to be managed, and a large capacity memory is required in the management system.

Here, the printer has been described as an example, but the above-mentioned problem is a problem common to various devices connected to a network. The present invention has been made to solve such a problem, and an object of the present invention is to provide a technique for flexibly and quickly exchanging management information between various devices and a management system via a network. And

[0009]

In order to solve the above-mentioned problems, according to the present invention, in a management system for managing operation states of a plurality of devices connected to a network, Device information storage means for storing device information representing the state of the device; andmanagement means for generating management information in a predetermined format for managing the operation of the device based on the stored device information, The device information is information obtained only in a partial range including a specified item for a device specified by the management unit as a management information generation target among all device information of the plurality of devices. It was taken. Here, the devices to be managed include printers, output devices such as displays, scanners, CD drives, and other input devices.
There are various devices for exchanging digital information over a network. The network is not limited to the one connected by wire, but may be connected wirelessly. The network includes various modes that can mediate the exchange of information between a plurality of individually prepared devices. Devices connected by a so-called wireless LAN can also be managed in the present invention.

According to the present invention, not all the device information is acquired and stored for a plurality of devices connected to the network, but only part of the device information in response to a request from the management means is acquired and stored. Since the device information once generated does not need to be confirmed with each device, the response speed when generating the management information is improved. Further, since only a part of the requested device information is stored, it is possible to avoid an extremely large memory required for the management system.

It is preferable that the management system of the present invention further comprises an erasing means for erasing the device information stored in the device information storing means based on a predetermined erasing condition set in advance.

With this configuration, unnecessary device information can be erased at any time, so that the memory capacity required for the management system can be suppressed. By erasing unnecessary device information, memory resources can be effectively used. Various settings can be made for the predetermined erasing condition. For example, the frequency of access to the generated device information can be used as the erasing condition. Further, the contents of the device information can be used as the erasing condition. As an example of the latter condition, when dynamic device information is included, it can be deleted. The device information includes static device information that does not change over time, such as the name and model of the device, and dynamic device information that changes over time, such as the remaining amount of paper and toner. In many cases, dynamic device information cannot effectively utilize past information. As an example, when dynamic device information is included in the acquired device information, by erasing the device information, it is possible to effectively use memory resources.

In the management system of the present invention, various types of device information can be handled. The device information is information in which items are set in a plurality of layers, and the device information storage means is located at a lower level. It is preferable that the device information is stored in a unit of a predetermined layer. Here, a mode in which all the device information included in the predetermined hierarchy is acquired and stored, and a storage area capable of collectively storing the device information included in the predetermined hierarchy is secured. Acquiring and storing information.

When items are set in a hierarchical manner,
Normally, relevant device information is classified for each layer. Therefore, if the device information is obtained in units of a predetermined layer, highly relevant information can be handled collectively, so that the convenience in using the device information can be improved. Which layer is used as a unit can be arbitrarily set. By using lower layers as units, less device information is stored at once,
Although the convenience of handling device information at once is reduced,
There is an advantage that memory resources can be saved. If the higher hierarchy is used as a unit, there is an opposite advantage.

[0015] The manner of handling device information in units of layers as described above is particularly useful when the management means and the device information storage means exchange information by SNMP. In SNMP, there is a command for directly acquiring an MIB information by directly specifying an address, and a command for sequentially acquiring MIB information starting from a certain address. In the MIB, device information is hierarchically configured by addresses.
Therefore, if the MIB information is handled in units of layers, it is convenient to acquire the device information in the latter mode.

In the management system according to the present invention, when the device information corresponding to the specified item is not stored in the device information storage means for the device specified by the management means, the device is accessed. Then, it is desirable to include an acquisition unit for acquiring the device information. According to such a configuration, it is possible to acquire the device information without excess or deficiency.

Further, in the management system according to the present invention, when the device information includes dynamic information that fluctuates with time and static information that does not fluctuate, the dynamic information is Irrespective of whether or not dynamic information is generated in the device information storage means, a dynamic information acquisition means for accessing a device in response to a request from the management system and acquiring the device information; It is desirable to do. This makes it possible to appropriately acquire and manage the dynamic device information.

In the present invention, the device information is an MI
B information. MIB information is
There is an advantage that device information can be transferred uniformly for various devices.

According to the second aspect of the present invention, as a second configuration, in a management system that manages the operation status of a plurality of devices connected to a network, information transfer means for transferring device information to and from the plurality of devices; Management means for generating management information relating to the operation status of the device based on the device information exchanged by the exchange means, wherein the information exchange means follows a predetermined protocol set in advance with the management means. And a lower layer interface for transmitting and receiving device information to and from the device by a method corresponding to the device.

The information transfer means has a function of mediating the exchange of device information between each device and the management means. When various devices are included in the management target, a method for exchanging device information with these devices, that is, a protocol is not always unified. Some devices exchange device information with SNMP, and some devices exchange device information using device-specific commands. When a device-specific command is used, available commands may differ depending on the manufacturer and model of the device.

According to the above configuration, the management means can acquire the device information by a predetermined protocol by the mediation function of the device information performed by the information transfer means. Therefore, the processing content of the management means can be simplified, and the processing load can be reduced.

When a device to be managed is newly added, if only the configuration of the information transmitting / receiving means is changed to a state in which information can be transmitted / received to / from the device, the managing means becomes compatible with the newly added device. , Device information can be obtained. Therefore, the types of devices to be managed can be flexibly increased.

According to a third aspect of the present invention, there is provided an M which manages MIB information of a plurality of devices connected to a network.
An IB information management system having a hierarchical MIB
For each item in a predetermined hierarchy lower than the information, storage means for grouping and storing items belonging to a hierarchy lower than the hierarchy, and the management according to a protocol corresponding to a device to be managed of the MIB information. MIB information generating means for obtaining device information corresponding to a target item, storing the device information in the storage area and generating MIB information, and referring to the storage area to store the stored MIB information in SNMP.
MIB information output means for outputting in accordance with the protocol.

The MIB information management system obtains device information from devices having various protocols for exchanging device information with a protocol corresponding to each device, and converts the device information into MIB information which can be exchanged by SNMP. Plays the role of converting to a format. In other words, on the MIB information management system, a virtual MI
Construct B. The device information stored in the virtual MIB is output according to SNMP. Various systems that can use the MIB information, such as a management system for managing devices and devices connected to the same network, can be considered as an output destination. By making a wide variety of protocols unified and exchangeable by SNMP in this manner, various systems that receive information from the MIB information management system have advantages such as simplification of processing and reduction of processing load. Another advantage is that devices to be managed can be added flexibly.

In the third configuration, MIB information is generated and stored in groups of lower layers. Since it is not necessary to store all the MIB information of each device, it is possible to avoid an extremely large memory capacity required for storage even if the number of devices to be managed increases. In the third configuration,
It is also desirable to provide means for erasing MIB information that is no longer required under predetermined conditions.

The MIB information management system may be configured as a single system connected to a network, or may be configured in another system, for example, in the same housing as a management system using MIB information. Is also good.

The present invention relates to the above-described management system, MIB
It can be configured in various modes other than the information management system.
For example, the configuration may be such as a device management method, a mediation method for mediating management information between a device management system and a device, and an MIB information management method.
Further, the management system described above, M
It may be configured in a form of a program for realizing the function of the IB information management system, a signal form compatible with the program, a recording medium storing the program, and the like. Here, as a recording medium, a flexible disk or a CD-RO
M, a magneto-optical disk, an IC card, a ROM cartridge, a punched card, a printed matter on which a code such as a barcode is printed, a computer internal storage device (RAM or ROM)
A variety of computer-readable media can be used, such as a memory (e.g., memory) and external storage.

[0028]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of the present invention will be described below in the following order. A. System configuration: B. Management system: B1. Management block: B2. MIB Gateway: MIB template: Management information generation processing: Example of management information generation: Modification: F1. First Modification of MIB Erasure Condition: F2. Second Modification of MIB Erasure Condition: Other variations:

A. System Configuration: FIG. 1 is an explanatory diagram showing a schematic configuration of a system in an embodiment. In the present embodiment, the management server 100, the management computer PC,
A management device is connected via a network LAN. Printers PRT1 to PRT are used as management devices.
T5 is exemplified. Further, a plurality of management devices may be provided. The management computer PC is composed of a general-purpose computer. The administrator accesses the management server 100 using the management computer PC to acquire Web display data, and displays the Web display data using a predetermined browser.
The operating status of the PRT 5 can be managed.

B. Management system: FIG. 2 shows management server 1
It is an explanatory view showing a functional block of 00. In the present embodiment, each functional block is configured in the management server 100 as software. The function block is constructed by acquiring software for realizing each function via a recording medium or a network and installing the software. Of course, each of them can be configured by hardware. In the present embodiment, the management server 100 having these functional blocks corresponds to the management system and the MIB information management system of the present invention.

The management server 100 is provided with a control unit 102 for controlling the overall functions. This control unit 10
The management block 110, the MIB gateway 120, and the network interface 130 are provided as blocks functioning under the control of the second control.

The management server 100 exchanges various information with a printer and a management computer PC via a network. At this time, the network interface 130 has a function of realizing communication via the network. The exchange of information via the network is performed according to a predetermined communication protocol such as TCP / IP. The network interface 130 processes information to be transmitted from the management server 100 to the outside into packet data according to the communication protocol, and outputs the packet data to the network LAN. In addition, network LA
It has a function of analyzing packet data received via N according to a communication protocol and extracting its entity.

B1. Management block: Management block 110
Generates display data for causing the browser of the management computer PC to display information for managing the operation states of the printers PRT1 to PRT5. Management block 110
Is provided with a management database 112, a Web data generation module 114, and an SNMP module 116.

The management database 112 stores management information of the printers PRT1 to PRT5 in order to generate display data. Web data generation module 114
Generates data to be displayed on the browser of the management computer PC based on information stored in the management database 112 using a language such as HTML (Hyper Text Markup Language).

The SNMP module 116 has a function of acquiring management information stored in the management database 112. Device operation status management is performed by MIB (Manageme
(nt Information Base). The MIB is a database that stores device information indicating the operation status of the printer and the like in association with a predetermined address and a predetermined item. By accessing this database, the management block 11
0 indicates that the operation status of each printer can be confirmed.
By changing the contents of this database, the management block 110 can also change the operation settings of each printer. Information is exchanged with the MIB using SNMP (Simple N
This is performed according to a protocol called "Etwork Management Protocol". The function of the SNMP module 116 is to send and receive MIB information according to this protocol.
The management information acquired by the SNMP module 116 is stored in the management database 112.

However, in this embodiment, the management block 110
Does not directly access the MIB of the printer.
The management block 110 acquires management information by accessing an MIB virtually constructed in the management server 100. It is the function of the MIB gateway 120 to generate and store this virtual MIB. In the present embodiment, various advantages described later are realized by indirectly acquiring management information using the MIB gateway 120. Of course, this does not prohibit the management block 110 from directly accessing the MIB of the printer. For example, the management block 110 may use acquisition of management information via the MIB gateway 120 and acquisition of management information by directly accessing the printer.

Here, the terms "management information", "device information", and "MIB information" used in this embodiment are defined. Each of these terms means various information related to the management of the printer to be managed. Such information includes static information that does not change over time and dynamic information that changes. The former includes a model name of the printer, an identification number assigned by the administrator for management convenience, a type of a printing mechanism of the printer, an address on a network, and the like. The latter includes the remaining amount of toner, the remaining amount of paper, and the like.

The three terms are used depending on the entity that handles information. The term “management information” refers to information acquired and stored by the operation state management block 110 of the device. “Device information” means information exchanged between a printer to be managed and the MIB gateway 120. “MIB information” means information stored in a virtual MIB configured in the MIB gateway 120.

B2. MIB gateway: The MIB gateway 120 is a virtual MIB as described above.
(Hereinafter simply referred to as “virtual MIB”). The MIB gateway 120 includes an MIB information generation unit 122, an MIB template 124, an SNMP module 126, and a command module 128.

The MIB information generator 122 generates a virtual MIB by using the SNMP module 126 and the command module 128 selectively. The management block 110 accesses the MIB gateway 120 by specifying a printer from which information is to be obtained and an item to be obtained. Items to be acquired are M according to the SNMP protocol.
It is specified in a format using the address of the IB. The MIB information generation unit 122 configures a virtual MIB on a storage area within a certain range including the specified information. Items to be configured in the storage area are stored in the MIB template 124.
In the present embodiment, a virtual MIB is not generated for all items of all printers to be managed, but is generated only for a part including information requested from the management block 110. By generating the virtual MIB only for the required part, the memory capacity required for the management server 100 is suppressed, and the memory resources are effectively used.

An MIB template 124 specifies a range in which MIB information is to be generated for the requested information. The details will be described later. MIB information generation unit 1
Reference numeral 22 expands the MIB template 124 including the item requested from the management block 110 in a storage area, and secures an area for configuring a virtual MIB. At this point, only the storage area is reserved, and the MIB information is not stored. The MIB information generation unit 122 acquires device information from the printer by properly using the SNMP module 126 and the command module 128 as necessary, as described below. MIB information generation unit 122
Stores the device information thus obtained as MIB information. The MIB information generation unit 122 also has a function of deleting unnecessary virtual MIBs from the virtual MIB once generated.

The function of the MIB information generation unit 122 for acquiring device information from a printer will be described. SNM
In order to acquire device information based on the P, it is necessary that an MIB be prepared on the printer side and that software be installed that enables transmission and reception of device information by SNMP. The printers PRT1 to PRT5 to be managed do not always have these software. When a printer that cannot support SNMP is included in the management target, it is necessary to acquire the requested information from the printer by using a command individually prepared for each printer. The command module 128 is a block having this function. Command module 1
28 shows M about printers that cannot support SNMP.
Commands necessary for acquiring IB information are stored for each printer. When acquiring information from a printer that should use the command, the MIB information generation unit 122 instructs the command module 128 on the target printer and the information to be acquired. In response to this instruction, the command module 128 obtains device information using a command stored in advance, and transfers the device information to the MIB information generation unit 122.

The SNMP module 126 has a function of exchanging MIB information according to the SNMP protocol. First, the SNMP module 126 transmits and receives MIB information to and from a printer capable of supporting MIB. M
When acquiring information from a printer that supports SNMP, the IB information generation unit 122 instructs the SNMP module 126 about a target printer and information to be acquired. In this case, the instruction of the information to be obtained is performed using the address of the MIB. The SNMP module 126 transmits this address to the printer to acquire MIB information, and
The information is passed to the information generation unit 122.

Second, in addition to the above-mentioned exchange, the SNMP module 126 exchanges MIB information with the management block 110. As described above, the management block 110
Accesses the virtual MIB of the MIB gateway 120 and acquires management information. The transmission and reception of this information is realized by the management block 110 and the SNMP modules 116 and 126 of the MIB gateway 120. The SNMP module 126 of the MIB gateway 120
The virtual MIB stored in the information generation unit 122 is accessed, MIB information corresponding to the specified address is acquired from the management block 110, and the MIB information is transferred to the management block 110.

C. MIB template: The configuration of the MIB template 124 will be described. FIG. 3 is an explanatory diagram showing the configuration of the MIB. The MIB is configured as a database in which addresses and management items uniquely correspond. FIG. 3 specifically shows the configuration of a part of the MIB. "The address of the MIB is a prefix part,
Divided into suffix parts. An address specified by combining the two is an address used for exchanging MIB information. As shown, the prefix “1.
3.6.2.1.43.10 "and the suffix" 2.
Address “1.3.6.2.1.1.4” combining “1”
The item corresponding to “3.10.2.1” is “Entr.
y], that is, the entry name of the printer. The next address “1.3.6.2.1.43.10.2.1.1” is “Index”, that is, an identification number for printer management. The next address corresponds to the type of the printing mechanism, that is, the type of the inkjet printer, the laser printer, or the like. Also, the prefix “1.3.3.6.1.4”
In 3.18 ", the alert level of the printer and its status are given corresponding to the suffix. The alert level means a printer abnormality such as "the printer cover is open". As described above, in the MIB, MIB information can be exchanged by designating addresses. Note that the prefix and the suffix are expedient divisions. For example, for an address corresponding to “Entry”, “1.3.6.1.4.
Up to 3 "may be treated as a prefix, and subsequent ones may be treated as a suffix.

FIG. 4 is an explanatory diagram showing the contents of the MIB template 124. In the present embodiment, the MIB template 124 is configured by a combination of two types of tables. Pref corresponding to the prefix described above
ix table and Suffix corresponding to suffix
There are two types of tables.

The Prefix table stores the location of the Suffix table in association with the prefix of the address. As shown in FIG. 4, for example, if the prefix of the address is “1.3.6.2.1.33.1.
If it is “0”, the Prefix table indicates that the location of the corresponding Suffix table is Add1.
Is specified. “Add1” can be variously defined according to the configuration of the management server 100. Management server 1
00 may be specified by a path name based on the directory or folder structure in the management server 10.
An address within 0 may be specified. Note that S
The uffix table may be stored in a server different from the management server 100 connected to the network.

The Suffix table is a table for storing a suffix structure corresponding to a prefix. For example, the Suffix table A in the figure gives the configuration of all suffixes belonging to the prefix “1.3.6.2.1.43.10”. Here, “Entry”, “Index”, and the like are illustrated as contents, but actually, a memory area necessary for storing such information, that is, a template is stored. Suffix
Similarly, for the table B, the prefix “1.3.6.
2.1.43.18 "are stored. The Suffix table serves to secure a storage area in which a virtual MIB can be generated for all suffixes belonging to a prefix, and does not provide device information of a printer corresponding to each suffix.

When the MIB template 124 is referenced, the Prefix table is referenced based on the prefix of the address of the requested MIB, and the corresponding Su
The ffix table is read into the memory. Even if there is only one requested item, the Suff corresponding to that item
The entire ix table is expanded on the memory. That is, these Suffix tables are treated as one group.
In SNMP, there are a case where information is exchanged by directly specifying an address of the MIB and a case where information is exchanged by specifying an address relatively. As an example of the latter,
There is a method of designating a "next address" for an address with which information has been exchanged once. In the MIB, by specifying a predetermined address and acquiring information on the “alert level” shown in FIGS. 3 and 4, by specifying information on the “next address”, information on the “state” is immediately acquired. can do. In the present embodiment, by generating a virtual MIB with the Suffix table as one group, it is possible to cope with relative addressing in SNMP.

D. Management information generation processing: management information and management computer PC based on the above functional blocks
A description will now be given of a process for generating Web data used for managing the operation of the printer. When the administrator designates the contents to be displayed for managing the operation status of the printer from the management computer PC, the management block 110 accesses the MIB gateway 120 according to the contents to acquire the MIB information. Display Web data is generated based on the MIB information. Management information generation processing refers to a series of these processing.

FIG. 5 is a flowchart of the management information generation process. In terms of hardware, this processing is executed by the CPU of the management server 100. In terms of software, the functions mainly executed by the management block 110 and the MIB information generation unit 122 under the control of the control unit 102 Equivalent to.

In this process, first, setting of a target printer and setting of a target item are performed (steps S10 and S1).
2). These items are set based on the display contents specified by the management computer PC.

Next, the CPU determines whether or not the designated item is a static item, and whether information corresponding to the item has already been acquired (step S14). Static items refer to device information that does not change over time. For example, the printer model name, management identification number, type of printing mechanism, and the like correspond to the static items. On the other hand, the remaining amount of toner and the remaining amount of printing paper of the printer are information that constantly changes during operation of the printer. These items are hereinafter referred to as dynamic items.

If the requested item is a static item and has already been acquired, a virtual MIB has already been generated in the MIB information generating unit 122, so it is necessary to access the printer again. There is no. CPU is MI
The virtual MIB stored in the B information generation unit 122 is accessed to acquire management information (step S18). In this case, the management information can be obtained without accessing the printer, so that high-speed processing is possible.

On the other hand, if the requested item is a dynamic item, or if the requested item is a static item whose information has not yet been acquired, the CPU accesses the target printer and obtains the information. Obtain (step S16). In the present embodiment, information is acquired in the following two stages in terms of software. The first stage is generation of a virtual MIB.
That is, when the target printer supports SNMP, the CPU directly outputs an address corresponding to the target item to the printer to acquire device information. If the target printer does not support SNMP, CP
U transmits a command corresponding to the target item to the printer to acquire device information. By storing the obtained information in a storage area prepared in the MIB information generation unit 122, a virtual MIB is generated. The process up to this point is MIB
This corresponds to the function of the information generation unit 122.

The second stage is information acquisition from the virtual MIB. The CPU acquires management information from the virtual MIB by designating an address corresponding to the target item, as in step S18. This processing corresponds to the function of the management block 110. In this embodiment, the information is obtained in two stages as described above. However, along with the generation of the virtual MIB,
The information may be transferred to the management block 110.

The CPU generates Web data for displaying a screen on the management computer PC based on the management information thus obtained (step S20). Web data is described in a language that can be displayed by a browser such as HTML. By transmitting this data to the management computer PC using a predetermined protocol, the management computer PC can check the management information of the printer on the screen.

After the Web data is generated in this way, the CP
U determines whether to delete the virtual MIB (step S22). As described above, each time MIB information is requested, the management server 100 generates a virtual MIB corresponding to the requested item. If the virtual MIB is stored as it is, the memory of the management server 100 is used for storing the virtual MIB, and the memory capacity may be insufficient. In this embodiment, in order to avoid such a situation, the virtual MIB is deleted as needed under a predetermined condition. Here, for the virtual MIB including the dynamic item, Suf
Erasing is performed on a fix table basis. The CPU
Based on these conditions, it is determined whether each of the virtual MIBs created in the management server 100 can be deleted (step S22), and the contents of the erasable virtual MIB are deleted (step S24).

By executing the above processing in response to an instruction from the management computer PC, the management system according to the present embodiment can manage the operation status of the printer.

E. Example of management information generation: An example of managing the operation status of a printer by the management system of the present embodiment will be described. FIG. 6 is an explanatory diagram showing a display example of the printer management information. This is a screen displayed by the browser on the display of the management computer PC. As shown in FIG.
In the system of this embodiment, printers PRT1 to PRT5 are connected as management devices. FIG. 6 shows a display example in the case where the remaining amounts of toner and printing paper are managed for these printers. For convenience of illustration, the case where the target printers are PRT1 to PRT3 is shown. The management information can also be displayed for the printers PRT4 and PRT5.

The management information is not limited to these. Information on asset management, for example, information on the asset management number of each printer, the person in charge of management, etc. may be displayed. Information on settings on the network, for example, IP
Information such as an address and a MAC address may be displayed. In addition, it is possible to specify and display various information necessary for managing the printer.

FIG. 7 is an explanatory diagram showing a display example of the individual management information of the printer. In FIG. 6, the information is displayed by selecting the printer PRT1. Here, only items equivalent to those in FIG. 6, that is, the remaining amount of toner and the remaining amount of printing paper are shown, but the display contents are not limited to these.
The generation of management information for realizing the display shown in FIGS. 6 and 7 will be described below.

FIG. 8 is an explanatory diagram showing the contents of the virtual MIB when the management information is generated. Here, of the necessary information for convenience of illustration, “model name”, “index”, and “printing mechanism” belong to the prefix Prf1,
It is assumed that they are given by suffixes Suf11 to Suf13, respectively. The “toner remaining amount” and “paper remaining amount” belong to the prefix Prf2 and are given by the suffixes Suf21 and Suf22, respectively. Steps ST1 to ST8 in FIG. 8 correspond to processing steps at the time of management information generation, that is, elapse of time. A blank portion indicates an item for which a virtual MIB has not been generated. Hatched portions indicate items for which a storage area has been secured, but MIB information has not been acquired. The shaded portions indicate items for which MIB information has been generated.

When generating the management information corresponding to FIG. 6, first, the model name of the printer PRT1 is obtained (step ST1). At this point, in the management server 100, the template corresponding to the prefix Prf1 is expanded on the memory. Of the items corresponding to the prefix Prf1, information on the model name is obtained and stored at the address corresponding to the suffix Suf11. At the same time, this information is used to generate management information. For other information, only a storage area is reserved.

Next, an index is obtained for the printer PRT1 (step ST2). Since the storage area has already been secured in step ST1 described above, the acquired index information, here, “PRT1” is stored at the address corresponding to the suffix Suf12. At the same time, this information is used to generate management information.

Next, information on the remaining amount of toner corresponding to the dynamic item is acquired for the printer PRT1 (step ST3). At this point, the management server 100
The template corresponding to the prefix Prf2 is expanded on the memory. Information on the remaining amount of toner among the items corresponding to Prf2 is acquired, and the suffix Suf
21. At the same time, this information is used to generate management information. Thereafter, information on the remaining amount of paper corresponding to the dynamic item is obtained (Step S).
T4) The information is stored in the address corresponding to the suffix Suf22. At the same time, this information is used to generate management information.

As described above, the printer PRT1 is stored in the management server 100 by the processing of steps ST1 to ST4.
A virtual MIB is generated. As explained earlier,
In this embodiment, the virtual MIB including the dynamic item is deleted when it becomes unnecessary. Therefore, step S
At the end of T4, the MIB containing dynamic items, ie,
The MIB corresponding to the prefix Prf2 is Suff
ix table is erased as a unit. Since only static items are included for the prefix Prf1, the virtual MIB is held as it is.

Next, for the printer PRT2, similarly, information belonging to the prefix Prf1 and information belonging to the prefix Prf2 are obtained (step ST).
5). Here, for convenience of illustration, steps ST1 to ST1 are shown.
The process corresponding to 4 is shown as a single step. Of these pieces of information, information belonging to the prefix Prf2 includes dynamic items and is deleted when it becomes unnecessary. Further, thereafter, similarly, for the printer PRT3, information belonging to the prefix Prf1 and information belonging to the prefix Prf2 are obtained (step ST6). Of these information, prefix P
Since information belonging to rf2 includes dynamic items, it is deleted when it becomes unnecessary.

With the above processing, the printers PRT1-PRT
For RT3, management information necessary for the display of FIG. 6 is generated. In this generation process, as shown in FIG. 8, the generation and disappearance of the virtual MIB are performed, and the capacity occupied by the virtual MIB on the memory dynamically changes.

Next, the generation of the management information when the administrator selects the printer PRT1 and performs the display of FIG. 7 after the display of FIG. 6 is completed will be described. Since the management information necessary for the display in FIG. 7 is sufficient as the management information acquired in FIG. 6, it is possible to generate the display Web data in FIG. 7 by diverting the management information in FIG. Here, the virtual MI
In order to explain the fluctuation of B, a case where the management information is newly generated for the display of FIG. 7 is exemplified.

A virtual MIB has already been generated and held for the static items of the printer PRT1 among the management information necessary for performing the display of FIG. Therefore, by accessing the virtual MIB belonging to the prefix Prf1, it is possible to acquire management information without having to access the printer PRT1.

On the other hand, regarding the remaining amount of toner and the remaining amount of paper,
Since it is a dynamic item, the virtual MIB is not held.
Therefore, when acquiring such information, the virtual server belonging to the prefix Prf2 is renewed to the management server 100.
IB is generated (step ST7). By these processes, the display shown in FIG. 7 is realized. Prefix P
The virtual MIB belonging to rf2 is deleted again when it becomes unnecessary (step ST8).

The management system according to the present embodiment described above has the following various advantages. First, the management system according to the present embodiment includes the MIB gateway 120, so that management information can be easily acquired even if a printer that cannot support SNMP and a printer that can support SNMP are mixed in the management target. Can be. In the management system, the management block 110 that mainly generates management information is a
The device information of each printer can be uniformly obtained by the NMP. Since it is not necessary to determine whether the printer to be managed is compatible with SNMP and change the command to be used based on the determination, it is possible to avoid complication of the processing. In addition, when a printer that cannot support SNMP is added to the management target, information exchange with the printer can be easily realized by changing the command module 128 of the MIB gateway. Therefore, the printers to be managed can be flexibly expanded.

Second, the management system of the present embodiment
By configuring a virtual MIB on the B gateway 120, it is possible to realize high-speed acquisition of MIB information. Device information can be acquired for the information acquired in the virtual MIB without accessing the printer again, so that the response at the time of acquiring the management information can be speeded up.

Third, the management system according to the present embodiment uses the MI
The virtual MIB configured in the B gateway 120 is generated limited to a part required for generating the management information.
As a result, the memory capacity required for the management server 100 can be suppressed, and the memory resources can be effectively used. In addition, the necessity of the MIB is determined based on a predetermined condition, and the MIB determined to be unnecessary is deleted. By doing so, an extreme increase in the memory capacity required for the MIB can be suppressed. Since the MIB determined to be necessary is retained, the high responsiveness described above can be realized.

Fourth, in the management system of this embodiment, the virtual MIB is generated and deleted in units of the Suffix table corresponding to the prefix. By doing this,
It is possible to easily respond to the relative address specification by SNMP, and to speed up the acquisition of MIB information.

F. Modified Example: In the above-described embodiment, the case where the MIB including the dynamic item is deleted is illustrated (see steps S22 and S24 in FIG. 5). Various conditions can be set for erasing the MIB.

F1. First Modification of MIB Erasure Condition: For example, the erasure may be determined according to the frequency of access to information stored in the virtual MIB. FIG. 9 is an explanatory diagram showing a change in the virtual MIB based on an erasing condition as a first modification. Here, M which has low access frequency
As an example of erasing IB, a case where MIB information is erased when access has not been performed over five steps has been described.

As shown, the prefixes Prf1 to Prf1
It is assumed that a virtual MIB has been generated for Prf6. In FIG. 9, a hatched area in the figure indicates an area in which not only a storage area is secured but also MIB information is generated. The filled area indicates an item for which the management information has been accessed from the management block 110 in Suffix table units.

As shown, the access status to the MIB information in steps ST1 to ST5 is as follows. Step ST1 → Prefix Prf4; Step ST2 → Prefix Prf1; Step ST3 → Prefix Prf3; Step ST4 → Prefix Prf5; Step ST5 → Prefix Prf1;

At this point, the prefixes Prf2, Prf
Since the rf6 MIB has not been accessed for five steps, these MIBs are erased in step ST6.

Next, in step ST6, the prefix P
It is assumed that the MIB of rf3 has been accessed. At this point, the MIB belonging to the prefix Prf4 is erased because no access has been made for five steps from step ST2 to step ST6.

At step ST7, the prefix Prf6
Is accessed. Since this MIB has been deleted in step ST6, it is generated again in step ST7. In step ST8, the prefix Pr
It is assumed that the MIB of f2 is accessed. This MIB
Has also been erased in step ST6,
8 again.

As described above, the erasure condition of the virtual MIB is Su
It can also be set based on the access frequency for each ffix table. This way, even for static items,
An infrequently used MIB can be erased, and memory resources can be effectively used.

In the first modified example, the case of erasing an MIB that has not been accessed for five steps has been exemplified. However, various conditions can be set for the access frequency. Not only the number of steps but also time may be set.

F2. Second Modification of MIB Erasure Condition: Erasure may be determined according to the ratio of the virtual MIB to the memory resources. FIG. 10 is an explanatory diagram showing a change in the virtual MIB based on an erasing condition as a second modification. Here, when the occupation ratio of the memory required for the virtual MIB exceeds 60%, the old virtual MIB starts the S
The case of erasing in units of uffix table has been exemplified.

As shown, the prefixes Prf1 to Prf1
Consider a case in which a virtual MIB belonging to Prf6 is generated. Here, it is assumed that the generation of all these MIBs corresponds to the amount of using 100% of the memory of the management server 100.

The hatched portions in the figure indicate items for which the virtual MIB is reserved in the storage area. Management block 110
It is assumed that the number of generated MIBs gradually increases in accordance with the items requested from. In step ST1, an MIB belonging to the prefix Prf1 is generated. In step ST2, an MIB belonging to the prefix Prf2 is generated while holding the MIB of the prefix Prf1. In steps ST3 and ST4, MIBs belonging to the prefixes Prf3 and Prf4 are generated. At this point, the ratio of the memory occupied by the MIB (hereinafter referred to as the occupation ratio) is 67%, which exceeds 60%.

In step ST5, the MIB belonging to the prefix Prf5 is generated after deleting the MIB belonging to the prefix Prf1 generated the oldest. At this point, the occupancy of the MIB is 67% and 60%.
Is over.

In step ST6, the MIB belonging to the prefix Prf6 is generated after deleting the MIB belonging to the prefix Prf2 which has been generated next oldest. At this point, the MIB occupancy is 71%. In step ST7, the MIB belonging to the prefix Prf3
Is erased, the occupancy becomes 50%, which is reduced to less than 60%. Since the MIB erasure condition is not satisfied, the virtual MIB is held in this state (step ST8).
According to the erasing condition of the second modification, the occupancy of the memory of the management server 100 can be suppressed to a predetermined value or less.
Of course, the occupation rate applied as the erasing condition is not limited to 60%, and various values can be set.
It may be dynamically changed based on the operation status of another application running on the above.

The erasing conditions described in the above embodiments and modified examples may use any one of the conditions alone or a combination of a plurality of conditions. Further, these conditions may be switched and used.

G. Other Modifications: In the embodiment and the modification, the case where the printer is managed is illustrated. According to the present invention, not only a printer but also various devices can be managed. For example, various devices that transmit and receive digital data via the network, such as a display and other output devices connected to a network, a CD-ROM drive, and other input devices, can be managed. In the embodiment, a network connected by wire has been exemplified. The network may be built including a wireless part. The present invention can also be applied to mobile phones, in-vehicle devices, and other moving objects that wirelessly exchange information as management targets.

In the embodiment, the case where the MIB gateway 120 forms a virtual MIB on the management server 100 has been exemplified. The present invention provides a gateway that mediates information transfer between a management block and a device when information transfer protocols with a device to be managed are various, and transfers information between the management block and the gateway. It is significant that it can be realized with a unified protocol. In the above embodiment, the unified protocol is S
Although the case where the NMP is used has been described as an example, the invention is not limited thereto, and various protocols can be applied.

In the embodiment, management blocks 110 and M
The case where the IB gateway 120 is configured in the single management server 100 has been illustrated. Both may be configured in a plurality of servers operating in cooperation with each other. Each of the functional blocks shown in FIG. 2 may be configured in a separate server.

Although various embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and it goes without saying that various configurations can be adopted without departing from the spirit of the present invention. For example, the above-described control processing may be realized by software or by hardware.

[Brief description of the drawings]

FIG. 1 is an explanatory diagram illustrating a schematic configuration of a system according to an embodiment.

FIG. 2 is an explanatory diagram showing functional blocks of a management server 100;

FIG. 3 is an explanatory diagram showing a configuration of an MIB.

FIG. 4 is an explanatory diagram showing the contents of an MIB template.

FIG. 5 is a flowchart of management information generation processing.

FIG. 6 is an explanatory diagram illustrating a display example of printer management information.

FIG. 7 is an explanatory diagram illustrating a display example of individual management information of a printer.

FIG. 8 is an explanatory diagram showing the contents of a virtual MIB when management information is generated.

FIG. 9 shows a virtual MI based on an erasing condition as a first modification.
It is explanatory drawing which shows the change of B.

FIG. 10 shows a virtual M based on an erasing condition as a second modification.
It is explanatory drawing which shows the change of IB.

[Explanation of symbols]

 Reference Signs List 100 management server 102 control unit 110 management block 112 management database 114 Web data generation module 116 SNMP module 120 MIB gateway 122 MIB information generation unit 124 MIB template 126 SNMP module 128 command module 130 ... Network interface

Continued on the front page (51) Int.Cl. ⁷ Identification code FI Theme coat II (Reference) H04L 12/28 H04L 11/00 310Z F-term (Reference) 2C061 AP01 HQ01 HR07 5B021 BB01 BB10 EE02 NN16 5B089 GA13 HB06 JA35 JB14 KA13 KB04 LB12 5K033 AA02 BA04 CB06 CB14 DA01 DB12 DB14 DB20 EA03 EA07 EC03

Claims (13)

[Claims] 1. A management system for managing operation states of a plurality of devices connected to a network, comprising: device information storage means for storing device information indicating states of the plurality of devices; And management means for generating management information in a predetermined format for managing the operation of the device, wherein the device information is the management information as a management information generation target among all device information of the plurality of devices. A management system which is information obtained only in a part of a range including a specified item for a device specified by a means. 2. The management system according to claim 1, further comprising: erasing means for erasing the device information stored in said device information storing means based on a predetermined erasing condition set in advance. 3. The management system according to claim 1, wherein the device information is information in which items are set in a plurality of hierarchies, and the device information storage unit uses a predetermined lower hierarchy as a unit. A management system that stores the device information. 4. The management system according to claim 1, wherein, for a device specified by the management unit, when device information corresponding to a specified item is not stored in the device information storage unit. A management system including an acquisition unit that accesses a target device and acquires the device information. 5. The management system according to claim 1, wherein the device information includes dynamic information that fluctuates with time and static information that does not fluctuate. Irrespective of whether dynamic information is generated in the device information storage means or not, a management apparatus comprising a dynamic information acquisition means for accessing a device in response to a request from the management system and acquiring the device information. system. 6. The management system according to claim 1, wherein said device information is MIB information. 7. A management system for managing operation states of a plurality of devices connected to a network, comprising: an information exchange unit for exchanging device information with the plurality of devices; Management means for generating management information relating to the operation status of the device based on device information, wherein the information exchange means exchanges information with the management means according to a predetermined protocol set in advance A management system, comprising: an upper layer interface; and a lower layer interface for exchanging device information with the device in a method corresponding to the device. 8. An MIB information management system for managing MIB information of a plurality of devices connected to a network, wherein each of the items in a predetermined hierarchy below the hierarchically structured MIB information is assigned a lower level than the hierarchy. Storage means for grouping and storing items belonging to a hierarchy; and acquiring device information corresponding to the item to be managed according to a protocol corresponding to a device to be managed of the MIB information, and storing the device information in the storage area. Information generating means for generating MIB information by using the storage area and referring to the storage area to store the stored MIB information in the SNM.
An MIB information management system comprising: an MIB information output unit that outputs in accordance with a P protocol. 9. A management method for managing operation states of a plurality of devices connected to a network, comprising: (a) managing a device for which management information is to be generated among all device information on the plurality of devices; (B) storing, in a memory, device information indicating a state of the device only in a part of a range including a target item;
Generating management information in a predetermined format for managing the operation of the device based on the stored device information. 10. A device information transmission method for transmitting device information indicating operation statuses of a plurality of devices connected to a network via an intermediary means, wherein (a) generating management information relating to the operation statuses of the devices. Transmitting device information between the management means and the mediation means in a manner in accordance with a predetermined protocol set in advance; and (b) performing a communication between the mediation means and the plurality of devices. Converting the protocol according to the device to be transmitted, and transmitting the device information in a method according to the device. 11. A management method for managing MIB information of a plurality of devices connected to a network, comprising: (a)
Setting, for each item in a predetermined hierarchy below the hierarchically-structured MIB information, items belonging to a hierarchy lower than the hierarchy and setting a storage area capable of storing the items; Obtaining device information corresponding to the item to be managed according to a protocol corresponding to the device to be managed, storing the device information in the storage area and generating MIB information, and (c) referring to the storage area. And outputting the stored MIB information in accordance with the SNMP protocol. 12. A recording medium in which a computer-readable program for managing the operating status of a plurality of devices connected to a network by a computer is recorded in a computer-readable manner, and the management system according to claim 1, wherein A recording medium that stores a program that implements a function. 13. A recording medium on which a computer-readable program for recording MIB information of a plurality of devices connected to a network using a protocol corresponding to each device and realizing the function of outputting the information in accordance with the SNMP protocol by a computer is provided. A recording medium that records, as a database used in the program, an item database in which items belonging to a layer lower than the hierarchy are grouped for each item in a predetermined layer below the MIB information having a hierarchical structure.