JPH10228427A - Information processor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To simultaneously transmit and receive management information to/from plural managers by converting a device management information identifier based on a device management protocol into the one that does not depend on the protocol and carrying out a management operation by using an identifier that does not depend on the management protocol. SOLUTION: A management information identifier abstracting part 11 converts a management information identifier that depends on a management protocol into a management information identifier that does not depend on the management protocol and is abstracted. A management operation executing part 13 receives an abstract management information identifier from the part 11 and performs a prescribed operation of data of an information storing part 14. When a concrete management information value is outputted from the part 14, a management information value materializing part 15 converts it into a concrete management information value that depends on the management protocol in accordance with a management operation and returns it to a manager. Then, it can correspond to each used management protocol and a management operation can be performed through plural management protocols.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an information processing apparatus management system including an information processing apparatus and a manager for monitoring and controlling the information processing apparatus. And an agent system for transferring management information in response to a management operation from a manager.

[0002]

2. Description of the Related Art FIG. 1 illustrates the relationship between a management target processing device (information processing device) 4 and a manager 1. In FIG. 2a, and the management target processing device 4 returns a response 2b to the manager 1. The agent 3 of the management target processing device 4 performs management operation command 2a and response 2 between the manager 1 and the management target processing device 4.
b. The management operation command 2a
The management operation is to refer to or set a management information value by a management information identifier using a predetermined protocol, and the agent 3 responds to the management operation from the manager 1. It is.

Next, a management protocol will be described.
As a protocol for managing devices, IETF (Inter
SNMP (RFC1157-M. Schoffstall, M. Fedor, J.
Davin, J. Case, "A SimpleNetwork Management Protoc
ol (SNMP) ", 05/10/1990) and its improved version SNMPv
2 (RFC1901-J. Case, K. McCloghrie, M. Rose, S. Wa
ldbusser, "Introduction to Community-based SNMPv
2 ", 01/22/1996) or DMTF (Desktop Management
DMI v2.0 (D
esktop Management Interface Specification Version
2.00, Desktop Management TaskForce, 27 March 19
96. WEB server http://www.dmtf.org) is known. In such a management protocol, management information is defined in a format unique to each protocol, an identifier unique to each protocol is assigned for identification, reference or setting of management information is instructed based on the identifier, and the result is referred to. Defines the response management operation.

[0004] In SNMP and SNMPv2, management information is basically identified by an object identifier. The object identifier is an identifier for uniquely identifying an object to be identified, is managed in a tree structure, assigns a name and a number to each node of the tree, and expresses the identifier by a sequence of numbers from the root of the tree to the leaves. Is what you do. For example, a printer MIB (RFC1759-
R. Smith, F. Wright, T. Hastings, S. Zilles, J. G
yllenskog, "Printer MIB", 03/28/1995), the management information indicating the "maximum capacity of the paper tray" of the printer is:
It is defined as follows:

[0005]

[Table 1] prtInputMaxCapacity OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS current DESCRIPTION "The maximum capacity of the input sub-unit in input sub-unit capacity units (CapacityUnit) .There is no convention associated with the media itself so this value reflects claimed capacity.If this input sub-unit can reliably sense this value, the value is sensed by the printer and may not be changed by management requests; otherwise, the value may be written (by a Remote Control Panel or a Management Application) .The value (-1) means other and specifically indicates that the sub-unit places no restrictions on this parameter.The value (-2) means unknown. ":: = {prtInputEntry 9} Notation used to define information (RFC1902-J. Case, K. McCloghrie, M. Ros
e, S. Waldbusser, "Structure of ManagementInformat
ion for Version 2 of the Simple Network Management
Protocol (SNMPv2) ", 01/22/1996), where {prtInputEntry 9} represents the object identifier of the management information indicating" the maximum capacity of the paper feed tray ". This "prtInputEntry" is defined in RFC1759 as follows.

[0006]

[Table 2] prtInputEntry OBJECT-TYPE SYNTAX PrtInputEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Attributes of a device capable of providing media for input to the printing process.Entries may exist in the table for each device index who's device type is printer '. "INDEX {hrDeviceIndex, prtInputIndex} :: = {prtInputTable 1} where the object identifier of" prtInputEntry "is {prtInp
utTable 1}, and in RFC1759, "prtInputT
"able" is defined as {mib-2 43 8 2}. This "mib-2"
RFC 1213 (K. McCloghrie, M. Rose, "Management Inf
ormation Basefor Network Management of TCP / IP-base
d internets: MIB-II ", 03/26/1991), {mgmt
1}, and “mgmt” is defined as {1 3 6 1 2} in RFC1155, and the leading 1 indicates a route number. That is, the identifier of the management information indicating “the maximum capacity of the paper feed tray” is {1 3 6 1 2 1 438
2 1 9}.

[0007] The "maximum capacity of the paper feed tray" is collective information identified by an index, and is referred to as "hrDeviceIndex" and "prtInputIndex" according to the INDEX clause in the definition of "prtInputEntry" in RFC1759. It is defined that indexing is performed by the value of the management information defined by the name. In this example, hrD
It is defined that there is a management information value "maximum capacity of paper feed tray" for each prtInputIndex paper feed tray of the eviceIndex-th printer. Note that hrDevi
ceIndex is RFC1514 (P. Grillo, S. Waldbusser, "Host R
esources MIB ", 09/23/1993), which is the index information that identifies the device to be managed.
utIndex is index information for identifying each paper feed tray defined in RFC1759.

On the other hand, the above-described DMI basically defines an interface for managing a desktop (a personal computer or a workstation) and various devices (a memory, a disk, a printer, etc.) connected to the desktop. Is defined in MIF (Management Information F
ormat) format, with components, groups,
Defined hierarchically by attributes. Here, a component represents a device to be managed, an attribute represents individual management information, and a group represents a group of the attributes. In DMI, basically,
Component-id, which is an identifier assigned to each layer,
Management information is identified by a combination of Group-id and Attribute-id.

For example, if a printer is to be managed, the DM
The definition related to “Maximum capacity of paper tray” defined in Printer MIF of I is defined as follows.

[0010]

[Table 3] start component name = "FX Printer 1" description = "This is a FX office printer." Start group name = "Printer Input Table" id = 8 class = "DMTF | Input Table | 001" description = "A list of input devices capable of providing "" printing media resources to this printer including "" information regarding their identity, possible and "" current configuration, and status. "key = 1 START ATTRIBUTE name =" Index "id = 1 description =" A unique value used by this printer to identify an "" associated input device.Although these values may "" change due to a major reconfiguration of the "" printer (eg the addition of new input devices to "" the printer), values are expected to remain stable "" across successive printer power cycles. "access = READ-ONLY storage = SPECIFIC type = INTEGER END ATTRIBUTE START ATTRIBUTE name =" Maximum Capacity "id = 9 description =" The maximum capacity of the input device in Input ""Capacity Units. There is no convention""associated with the media it self so this value is "" claimed capacity.If the input device can reliably "" sense this value, the value is sensed by the printe r "" and is read-only: otherwise the value may be writte n "" by a management or control console application.Th e "" value (-1) means other and specifically indicates "" that the input device places no restrictions on this "" parameter.The value (-2) means unknown. "access = READ-WRITE storage = SPECIFIC type = INTEGER END ATTRIBUTE end group end component In this example, from start component to end component is the definition of the printer component. In this case, it means the definition of the printer named "FX Printer1". From the end group to the end group are the paper tray group ("Printer Input Table") definition. The attributes from START ATTRIBUTE to END ATTRIBUTE are attribute definitions. In this example, an attribute named "Index" and "Maximum C" indicating "maximum capacity of paper tray" are used.
An attribute named "apacity" is defined.

[0011] In DMI, Compo for identifying components is used.
Since the nent-id is determined when the device to be managed is registered as a management target, its value is not specified in the definition by the MIF. "Maximum Paper Tray Capacity" for a Printer
Is the Component-id determined at the time of registration, and "Printer Inp
Group-id "8" to identify the group "ut Table"
And an Attribute-id set of “9” that identifies an attribute of “Maximum Capacity”.

The “maximum capacity of the paper feed tray” is collective information identified by an index, and is a key clause in the definition of the MIF definition group (the group named “Printer Input Table”). Defines that indexing is performed by the value of the first attribute, that is, the attribute named "Index". That is, in this example, for each printer identified by Component-id, for each attribute value identified by the name "Index", the "maximum capacity of the paper feed tray"
It is defined that the value of the management information exists.

By the way, the information processing device management system includes:
Usually, an agent specializing in a management protocol used by a manager is prepared, and a management target device on which the agent is mounted is managed. Therefore, when managing only managed devices equipped with agents corresponding to the same protocol and managing managed devices equipped with agents corresponding to other protocols, it is necessary to separately manage by a manager using the corresponding management protocol There is.

In particular, as shown in FIG. 2, a manager 1 and a managed device 4 are connected via a network, and a plurality of managed devices 4 (a, b, c) are connected to a plurality of managers 1 (a, b). ), The manager 1 (a, b) performs a management operation using different protocols. In other words, a plurality of managers 1 (a, b) that handle different management protocols on one network and a managed device 4 (a, b) equipped with agents 3 (a, b) for each protocol.
b, c) may exist in plurality. In this case, one manager 1 (a or b) is in a state where it can manage only the management target device equipped with the agent (a or b) corresponding to the protocol to be used.

In order for a single manager 1 to manage all the devices to be managed, as shown in FIG.
It is necessary to perform a management operation according to a protocol corresponding to each installed agent. Alternatively, as shown in FIG. 4, it is necessary to mount the agents 3 (a, b) for each protocol handled by each manager 1 on all the managed devices 4 (a, b, c).

[0016] Patent documents related to the present invention include JP-A-6-214901 and JP-B-8-148.
No. 10 publication. In JP-A-6-214901, a management system of information resources via a network is realized. Here, in order to manage information resources distributed on the network, each agent is integrated and managed in the upper part of the agent for managing each information resource,
By providing a dialogue transmission and management unit for performing a dialogue with the management manager, it is possible to perform management operations on distributed information resources.

However, in this management system, information resources are consistently managed from a management manager to an agent handling each information resource via a specific standard protocol, and the management manager handles a protocol other than the specific standard protocol. It is not stipulated for the case where the management is performed by a different management protocol or when there are a plurality of management managers that handle different management protocols.

In this management system, a management operation cannot be performed under a management manager that handles a management protocol other than a specific standard protocol. There was a need to respond. Further, when there are a plurality of management managers handling different management protocols, it is necessary to prepare a dialogue transmission and management unit corresponding to each management protocol for each protocol handled by the management manager.

In Japanese Patent Publication No. 8-14810,
A printer control device supporting a multi-protocol has been realized. This printer control device realizes a multi-protocol by using a plurality of conversion tables set in advance corresponding to the use of a plurality of protocols and a conversion table selecting unit for selecting a conversion table corresponding to the use of the protocol in the information processing apparatus. ing.

However, this system describes only one-way transmission and reception of control information from an information processing apparatus to a printer, and a method for transmitting and receiving management information and bidirectionally exchanging information, which are problems in the present invention. Is not mentioned.

[0021]

SUMMARY OF THE INVENTION The present invention has been made in view of the above circumstances, and instead of a management target device having a plurality of agents mounted thereon (FIG. 4), one agent uses a plurality of protocols. By responding, when a plurality of managers handling different management protocols manage the managed device, it is intended to realize a management system in which each manager can centrally manage the managed device. Therefore, an object of the present invention is to realize a multi-protocol compatible agent system which enables simultaneous transmission and reception of management information to and from the plurality of managers. Another object of the present invention is to realize an agent system that can quickly and easily respond to a new protocol even when a manager that handles a new management protocol is introduced.

Still another object of the present invention is to realize efficient processing or data mounting when handling a management information group when realizing the agent system.

[0023]

SUMMARY OF THE INVENTION In order to achieve the above object, the present invention provides an information processing apparatus which is managed based on at least one device management protocol among a plurality of types of device management protocols. Means for converting a first device management information identifier generated according to one device management protocol into a second device management information identifier independent of any of the at least one device management protocol; Means for holding an information identifier and a device management information value corresponding to the second device management information identifier; and the second device management information identifier and the second device held by the device management information holding means A method for executing a predetermined management operation on the device management information value corresponding to the management information identifier based on the second device management information identifier. And it is provided with a door.

In this configuration, the device management information identifier based on the device management protocol is converted so as not to depend on the protocol, and the management operation is executed using the identifier that does not depend on the management protocol. Therefore, it is possible to correspond to each device management protocol to be used, and management operations using a plurality of device management protocols become possible. Also, even when a manager that handles a new management protocol is introduced, there is no need to prepare agents corresponding to the new management protocol in parallel, and the management information identifier of the new management protocol is simply managed independently of the management protocol. It only needs to be able to be converted into an information identifier.

Further, in this configuration, the information processing apparatus further includes a device management information value corresponding to the first device management information identifier and a device management information value corresponding to the second device management information identifier. And a device management information corresponding to the second device management information identifier held in the device management information holding unit, based on the device management information value of the second device management information identifier after the conversion. Means for updating the value may be provided. in this case,
The device management information value can be set independently of the protocol.

Further, the information processing device further stores the device management information value of the second device management information identifier read from the device management information holding means into the device corresponding to the first device management information identifier. Means for converting to a management information value may be provided. In this case, the device management information value can be referred to regardless of the protocol.

According to the present invention, in order to achieve the above object, at least one information processing device is connected to at least one manager that manages the information processing device based on a unique management protocol. Converting the first device management information identifier generated according to the at least one device management protocol into a second device management information identifier independent of any of the at least one device management protocol. A device management information holding unit that holds the second device management information identifier and a device management information value corresponding to the second device management information identifier; and a device management information holding unit that holds the device management information value. For the second device management information identifier and the device management information value corresponding to the second device management information identifier, And it is provided with a means for executing a predetermined management operations based on the second device management information identifier.

Also in this configuration, management operations using a plurality of device management protocols are possible. Further, even when a manager that handles a new management protocol is introduced, there is no need to prepare agents corresponding to the new management protocol in parallel.

According to the present invention, in order to achieve the above-mentioned object, the information processing apparatus is provided in the information processing apparatus, and is provided to the information processing apparatus in response to a management operation command based on the manager-specific device management protocol from the manager. A first device management information identifier generated according to at least one device management protocol of a plurality of types of device management protocols is transmitted to an agent device that performs a corresponding management operation on the agent device from any of the at least one device management protocol. Means for converting the second device management information identifier into an independent second device management information identifier, and device management information holding means for holding the second device management information identifier and a device management information value corresponding to the second device management information identifier. The second device management information identifier and the second device management stored in the device management information holding unit. To the device management information value corresponding to the information identifier and be provided with a means for executing a predetermined management operations based on the second device management information identifier.

Also in this configuration, management operations using a plurality of device management protocols are possible. Further, even when a manager that handles a new management protocol is introduced, there is no need to prepare agents corresponding to the new management protocol in parallel.

According to the present invention, in order to achieve the above-described object, a predetermined device management device is provided to an information processing apparatus managed based on at least one device management protocol among a plurality of types of device management protocols. Means for converting the first device management information identifier generated according to the protocol into a second device management information identifier independent of the predetermined device management protocol; and a means for converting the second device management information identifier and the second device management information identifier Means for holding a device management information value corresponding to the device management information identifier, and the second device management information identifier and the device corresponding to the second device management information identifier held in the device management information holding means Means for executing a predetermined management operation on the management information value based on the second device management information identifier.

Also in this configuration, management operations using a plurality of device management protocols are possible. Further, even when a manager that handles a new management protocol is introduced, there is no need to prepare agents corresponding to the new management protocol in parallel.

[0033]

Embodiments of the present invention will be described below. FIG. 5 shows the agent system of this embodiment. The other configuration is the same as that of the conventional system (FIGS. 1 to 4), and the description is omitted.

In FIG. 5, the agent section of this embodiment includes a management information identifier abstraction section 11, a management information value abstraction section 12, a management operation execution section 13, and a management information storage section 14.
And a management information value materializing section 15 and the like.

When a manager (not shown) instructs management information operation, for example, acquisition (GET) of management information, the management information identifier is sent to the management information identifier abstraction unit 11 and, if necessary (for example, management information). Setting: At the time of SET operation, the management information value dependent on the management protocol is input to the management information value abstraction unit 12. Management information identifier abstraction unit 1
1 is a management information identifier (DepI
D, hereinafter referred to as a specific management information identifier) is an abstract management information identifier (IndepI
D, hereinafter referred to as an abstract management information identifier). The management information value abstraction unit 11 converts a management information value dependent on the management protocol (referred to as a specific management information value) into a management information value independent of the management protocol (referred to as an abstract management information value).

The management information storage unit 14 stores an abstract management information identifier and an abstract management information value in a manner independent of the management protocol. The management operation execution unit 13 receives the abstract management information identifier from the management information identifier abstraction unit 11 and, if necessary, receives the abstract management information value from the management information value abstraction unit 12 and stores it in the data of the management information storage unit 14. Then, a predetermined operation is performed. When the abstract management information value is output from the management information storage unit 14 in response to the management operation, the management information value materializing unit 15 converts the abstract management information value into a specific management information value depending on the management protocol and returns it to the manager.

FIG. 6 shows an embodiment of the above conversion. As shown in FIG. 6, by converting each specific management information identifier 21 that depends on the management protocol into an abstract management information identifier 22 that does not depend on the management protocol, the management operation is performed by using the identifier. Protocols and agents
The dependency with the system can be reduced.

Next, the device identifier will be described. The management information identifier abstraction unit 11 converts the protocol-dependent concrete management information identifier (DepID) 21 into an abstract management information identifier (IndepID) 22 (FIG. 7) independent of the protocol. IndepID) 22, a device identifier (CompID) 23 for inquiring the management information value
(FIG. 8). For this reason, as shown in FIG. 5, the management information identifier abstraction unit 11 has a device identification unit 111 for extracting a management target device having the management information indicated by the specific management information identifier (DepID) 21, and the management target device. An information identifier extraction unit 112 for uniquely identifying management information is included. On the other hand, the management operation execution unit 13 executes a management operation on the management target device indicated by the device identifier (CompID) 23. Accordingly, when there are a plurality of managed devices having the same management information, the information identifier extracting unit 112 included in the management information identifier abstraction unit 11 can be shared between the managed devices. Also, when a similar device is deleted or added, it can be dealt with only by changing the device determination unit 111.

That is, the abstract management information identifier
The IndepID group is classified by device, and when there are a plurality of devices having the same management information, the identifiers of the management information existing in each device are integrated, and each is arbitrarily identified by the device identifier CompID23. It is possible to do. Also, when a similar device is deleted or added, the process of deleting and adding the abstract management information identifier IndepID 22 to be handled by the agent is not necessary, and the process of deleting and adding the device becomes easy.

Next, the definition (DEF) of the management information value will be described. When converting from the specific management information identifier (DepID) 21 to the abstract management information identifier (IndepID) 22 performed by the management information value abstraction unit 11, the definition of the management information value corresponding to the abstract management information identifier (IndepID) 22 ( DE
F) Perform abstraction by referring to 24. The definition (DEF) 24 may be included in the abstract management information identifier (IndepID) 22 (FIG. 9), but in this embodiment, it is separately stored in another area using the pointer information (pointDEF) 25. The structure has a structure (FIG. 10) having a correspondence with the abstract management information identifier (IndepID) 22.

The definition (DEF) 24 of the management information value is semi-fixed information that is not changed unless the target management item is changed, and is an abstract management information identifier (E) that is required every time a management operation is executed. It is not necessary to have this information for each IndepID) 22, and effective use of memory can be achieved. In addition, the same definition (DE
F) If there are 24 (FIG. 10), they are integrated, and the abstract management information identifier (IndepID) 22 has a correspondence with the common definition (DEF) 24, and the abstract management information identifier (IndpID)
epID) 22 and a device identifier (CompID) 23 that has a separate correspondence
(FIG. 11).

The definition (DEF) 24 may have a hierarchical structure. That is, the definition (DEF) 24 has a definition for each management information value. However, each definition (DEF) 24 often has a portion common to other DEFs (FIG. 12). Instead of having this common part in each definition (DEF) 24, each definition (DEF) is separated and held as a common Def 26 that is separately held.
24 (FIG. 13).
Here, when the common Def 26 is separated and further has a common definition part 27, the common part is similarly separated to have a structure corresponding to each other (FIG. 1).
4). As a result, the definition (DEF) 24 has a multi-level hierarchical structure. As a result, it is not necessary to have the definitions separated as the common Def 26 in each definition (DEF) 24, and it is possible to effectively use the memory.

Next, the attribute definition (AttrDef) 28 will be described. When the abstract management information identifier (IndepID) 22 identifies each of the collective management information having the same definition (AttrDef) and uniquely identified by the index (FIG. 15), the abstract management information identifier (IndepID) 22 IndepID)
22, index information (Index) 29, and an attribute definition (AttrDef) 28 which is a common definition of collective management information
(FIG. 16). That is, the attribute definition (AttrDef) 28 is separated as the common Def 26, and the common attribute definition (AttrDef) 28 and the corresponding abstract management information identifier (IndepID) 22 have a structure identified by their respective index information (Index) 29. . This eliminates the need to have an attribute definition (AttrDef) 28 for each of the abstract management information identifiers (IndepID) 22, and enables effective use of memory.

Next, the key definition (KeyDef) 30 will be described. The attribute definition (AttrDef) 28 defines index information (KeyDef) 3 for identifying a unique management information value.
When 0 is included (FIG. 17), the attribute definition (AttrDef) 28 and the key definition (KeyDef) 30 are separated to have a structure having the correspondence (FIG. 18). As a result, the common key definition (KeyDef) 30 is changed to the respective attribute definitions (AttrDef) 28
It is not necessary to have it every time, and effective use of memory can be achieved. Next, the management information value abstraction unit 12 and the management information value specification unit 15 will be described. As shown in FIG. 21, the protocol-dependent concrete management information value 31 is stored in the management information value abstraction unit 12.
The protocol-independent abstract management information value (O
bjectInstance) 32. Also, as shown in FIG. 19, the management operation executed by the management operation
When a response of the management information value is caused, such as information reference, the management information value materializing unit 15 converts the abstract management information value (ObjectInstance) 32 into a protocol-dependent management information value 31. That is, the management operation execution unit 13 returns an abstracted management information value (ObjectInstance) 32 corresponding to the abstract management information identifier (IndepID) 21 and converts the abstract management information value (ObjectInstance) 32 to management information materialization. It is converted into a management information value 31 depending on the protocol input by the unit 15.

Abstract management information value (ObjectInstance) 32
Has achieved an abstraction of the management information value by holding an abstracted syntax (Syntax) 35 independent of the management protocol and a module (valueInstance) 34 for storing the value abstracted thereby. It has a configuration.

The management information value instantiating unit 15 has means for associating the abstract management information value (ObjectInstance) 32 with the syntax (DepSyntax) of the management information definition in each management protocol. The syntax type value (valueInstance) 34 held in the management information value (ObjectInstance) 32 is changed to DepSyntax
The structure is such that it is converted into a type of management information value (FIG. 19).

Next, the syntax (Syntax) 35 will be described. The syntax (Syntax) 35 does not hold for each abstract management information value (ObjectInstance) 32 but has a structure in which it is associated with the definition (DEF) of the corresponding abstract management information identifier (IndepID) 22. The unit 15 obtains the obtained abstract management information value (ObjectInstance) 3
The value (valueInst) is obtained by the syntax (Syntax) 35 obtained from the definition (DEF) of the abstract management information identifier (IndepID) 22 corresponding to No. 2 and the specific syntax (DepSyntax).
ance) 34 (FIG. 20). The value (valueInstance) 34 includes a value (Value) 37 and a size (size) 38. Pointer information (pointIndep
ID) 33 points to the abstraction management information identifier. Further, the pointer information 36 includes an attribute definition (Attr
Def).

As a result, it is not necessary to hold the syntax 35 for each abstract management information value (ObjectInstance) 32 created each time a management operation is executed, and the memory can be effectively used.

When the management operation executed by the management operation execution unit 13 requires input of a management information value such as information setting, the management information value abstraction unit 12 , Is converted to an abstracted management information value independent of the protocol. That is, the management information value abstraction unit 12 converts the management information value dependent on the management protocol into an abstracted management information value (ObjectInstance) 32 having a correspondence with the abstract management information identifier (IndepID) 22. The management operation executing unit 13 sets the abstract management information value (Obje
ctInstance) 32 and the corresponding abstract management information identifier (IndepID) 22 to execute a management operation.

Next, an abstract management information value (ObjectInstance)
32 will be described. Abstract management information value (ObjectInstan
ce) 32 holds an abstracted syntax (Syntax) 35 independent of the management protocol and a value (valueInstance) 34 abstracted thereby.
The configuration is such that the management information value is abstracted.

The management information value abstraction unit 12 has means for associating the specific syntax (DepSyntax) of the input management information value with the syntax (Syntax) 35, and converts the management information value to the abstract management information. Value (ObjectInstance) 3
2 (FIG. 21). As described in the syntax, in this case, the syntax 35 is
Instead of holding for each abstract management information value (ObjectInstance) 32, a corresponding abstract management information identifier (IndepID) 2
The management information value abstraction unit 12 acquires a syntax (Syntax) 35 from the definition (DEF) corresponding to the abstract management information identifier (IndepID), and receives the input management. Performs abstraction of information value (Fig. 2
2). Thereby, it is not necessary to hold the syntax 35 for each abstract management information value (ObjectInstance) 32 created each time a management operation is executed, and the memory can be used effectively.

Next, the management operation execution section 13 will be described. The management operation execution unit 13 has a structure in which the management operation is executed by dispatching the management operation to each management target device by using an information access interface included in the management target device. In this case, the abstract management information identifier (IndepID) 22 has a correspondence with information for dispatch (DispatchInfo) 40 for each managed device, and the management operation execution unit 13 receives the input abstract management information identifier (IndepID). ) 22, the corresponding dispatch information (Dis
patchInfo) 40, and dispatches to the device to be managed based on it to execute a management operation (FIG. 23). The dispatch information (DispatchInfo) 40 is not prepared for each abstract management information identifier (IndepID) 22, but the definition DEF and the dispatch information (DispatchInfo) 40 having a correspondence with the abstract management information identifier (IndepID) 22.
(FIG. 24). The dispatch information (DispatchInfo) 40 is semi-fixed information that does not change as long as the definition of the management information value is not changed. Therefore, an abstract management information identifier (IndepID) prepared every time a management operation is executed. 2) Dispatch information (DispatchInfo) does not need to be prepared for each 22, and the memory can be effectively used.

When the definition (DEF) has a hierarchical structure, the lowest level (leaf) not only has a correspondence with the dispatch information (DispatchInfo) 40, but also has Also dispatch information (Disp
atchInfo) 40, and the management operation execution unit 13
May be configured to dispatch the management operation to the management target device based on the information when the management operation is executed (FIG. 25). As a result, a management operation according to a processing unit (for example, individual management information items, a group thereof, or the entire device) of the information access interface included in the management target device can be performed.

In the configuration of FIG. 25, the abstract management information identifier (IndepID) 22 is replaced by an attribute definition (AttrDef) 28.
And the index information for identifying individual information, the attribute definition (AttrDef) 28 and the dispatch information (DispatchInfo) 40 have a correspondence. Management information identifier (Inde
It is also possible to adopt a structure in which a management operation is dispatched to the management target device from the dispatch information (DispatchInfo) 40 of the corresponding attribute definition (AttrDef) 28 from the pID) 22 and the index information (FIG. 26).

In FIG. 26, dispatch information (DispatchInfo) 40 has not only information corresponding to attribute definition (AttrDef) 28 but also dispatch information (DispatchInfo) 40 corresponding to key definition (KeyDef) 30.
When executing management operations, these dispatch information (Disp.
The management operation is performed based on (atchInfo) 40. As a result, it becomes possible to execute a management operation such as operating the index information defined by the key definition (KeyDef) 30.

In FIG. 23, dispatch information (DispatchInfo) 40 is prepared not only for each device to be managed, but also for each type of management operation.
atchInfo), and the management operation execution unit 13 handles dispatch information (Dispatch
Info) may be selected and dispatched to the management target device.

Next, the embodiment of FIG. 1 will be described in detail with reference to FIGS.

FIG. 27 shows a part of the configuration of the agent system relating to the case where the management operation causes a response of the management information value, such as reference to information, in the configuration of the agent system of the embodiment. FIG.
Reference numeral 8 denotes a part of the configuration of the agent unit related to a case where the management operation requires input of a management information value such as setting of information.

In FIG. 27 and FIG. 28, as described above, the agent system determines the specific management information identifier depending on the management protocol sent from the manager.
A management information identifier abstraction unit 11 that converts the (DepID) 21 into an abstract identifier (IndepID) 22 that does not depend on a protocol, and a management operation execution unit 13 that executes a management operation using the abstract identifier 22. Having. The abstracted identifier (IndepID) 22 has a correspondence with the identifier (compID) 23 of the device inquiring about the management information value, and further has a correspondence with the definition (DEF) 24 of the management information. Definition (DE
F) 24 is an attribute definition (AttrDef) 28 that has the same definition when the management information has the same definition and is uniquely determined by the index information 29;
It has a two-stage hierarchical structure consisting of a key definition (KeyDef) 30 which is the definition of 9. Abstract management information identifier (IndepID)
22 is an attribute definition (AttrDe) of the definition (DEF) 24.
f) It has a correspondence with 28 and has index information 29 for uniquely identifying management information.

The definition (DEF) 24 has a hierarchical structure including the attribute definition (AttrDef) 28 and the key definition (KeyDef) 30 as described above, and the management operation is executed by the management operation execution unit 13 for each of them. It has a correspondence with the dispatch information (DispatchInfo) 40 used in such a case. Further, the attribute definition (AttrDef) 28 has a correspondence with syntax information (Syntax) 35 used when the management information value is abstracted.

The management information value handled by the management operation execution unit 13 is
Abstracted value (ObjectIns
The management information value abstraction unit 12 and the management information value materialization unit 15 that perform conversion with the management information value depending on the protocol are provided to perform the conversion.

An abstracted value (ObjectInstance) 32
Has a correspondence with an abstract management information identifier (IndepID) 22 that is an identifier of the corresponding management information, and has a correspondence with a value (valueInstance) 34 that is an abstracted value, so that the management information value The abstraction of is realized.

Next, an outline of the operation in this embodiment will be described. Here, the management protocol described earlier
When SNMP is used and the object identifier is used as the specific management information identifier (DepID), when the management operation refers to the information (GET) and when the management operation sets the information (SET) explain. First, the case of GET will be described with reference to FIGS. Here, the maximum capacity of the paper feed tray 1 is taken as an example of the management information value for performing the GET operation. As described above, this object identifier in the SNMP protocol is {1 3 6 1 2 1
438 2 1 9 1 1} and the first 11 elements {1
3 6 1 2 1 43 8 2 1 9} indicates the value of the maximum capacity of the paper feed tray. The next element "1" is an identifier of the device, and the last element "1" is an identifier indicating the first tray of the plurality of paper feed trays.

In FIG. 29, the agent that has received the identifier of the management information dependent on the protocol performs conversion to an abstracted identifier (IndepID) independent of the protocol (S50, S51). Thereafter, a management operation is executed to materialize the obtained management information value (S52, S5).
3). Hereinafter, each of these steps will be described in detail.

FIG. 30 shows the steps of identifier abstraction. In FIG. 30, the identifier abstraction first extracts an identifier (CompID) 23 of a device to be a management device from a given specific management information identifier (DepID) 21 (S54). In this embodiment, the device identifier (CompID) 23 is hrDev which is the device identifier in the specific management information identifier (DepID) 21.
Since it matches the value of iceIndex, it is the twelfth element of the given specific management information identifier (DepID) 21.
1 "is extracted as the device identifier (CompID) 23.

Next, the identifier abstraction unit 11 searches for which attribute definition (AttrDef) 28 the management information indicated by the specific management information identifier (DepID) 21 corresponds to. In this case, a search is made to determine which of the attribute definition (AttrDef) groups in the agent matches the definition of the management information “maximum capacity of the paper feed tray” indicated by the specific management information identifier (DepID) 21. Matching attribute definition (AttrDe
f) When 28 is found, the pointer is acquired (S55). Further, "1" indicating the first tray, which is the last element of the specific management information identifier (DepID) 21, is extracted as index information (S56). An abstracted identifier (IndepID) 22 is created from the device identifier (CompID) 23, the attribute definition (AttrDef) 28, and the index information (Index) 29 (S57).

FIG. 31 shows steps for executing a management operation. If the management operation is GET, the agent system
The management operation is executed by passing the abstract management information identifier (IndepID) 22 created by the identifier abstraction unit 11 to the management operation execution unit 13. In FIG. 31, the management operation execution unit 13 first extracts the device identifier (Com) from the abstract management information identifier (IndepID) 22 given in the GET operation.
pID) 23 is extracted (S58). Next, an attribute definition (AttrDef) 28 included in the abstract management information identifier (IndepID)
The attribute definition (AttrDef) 28 is obtained from the pointer 36 to the destination (S59). The attribute definition (AttrDef) 28 is associated with dispatch information (DispatchInfo) 40 for performing a management operation on the corresponding management information.
Since the dispatch information (DispatchInfo) 40 is separated for each device to be managed and for each type of management operation, the corresponding dispatch information (DispatchInfo) 40 is assigned to the device identifier (CompID) 23 and the GET operation. Acquire (S60). The abstract management information identifier (IndepI
D) Index information 29 included in 22 is extracted for use in dispatch (S61). Based on the acquired dispatch information (DispatchInfo) 40, the management operation is executed by dispatching the management operation to the target device together with the index information (Index) 29 (S62). In the GET operation, by executing this management operation, a value (ObjectInstance) 32, which is a management information value abstracted from the management target device, can be obtained. In this example, assuming that the maximum capacity of the paper feed tray 1 is 300 sheets, the value returned from the management operation execution unit 13 (ObjectInst
ance) 32, the value (value) 37 in the value (valueInstance) 34 contains a value of 300.

The value (Object)
Instance) 32, the agent system
In order to convert the abstracted management information value into a form corresponding to each protocol, it is passed to the management information materializing unit 15 (S
63).

FIG. 32 shows the steps for embodying the management information value. In FIG. 32, the management information materializing unit sets the value (Obje
In order to obtain the type (Syntax) 35 in which the management information value included in the ctInstance) 32 is stored, first, the value (ObjectInstan
ce) corresponding to the abstract management information identifier (IndepID) 22, and an attribute definition (AttrDef) 28 corresponding to the abstract management information identifier (IndepID) 22 (S64,
S65). Further, by obtaining the type (Syntax) 35 corresponding to the attribute definition (AttrDef) 28, the value (ObjectInst
ance) 32 to obtain the type of the management information value (S
66). In this example, the value (ObjectInstance) 32
Is stored as a 4-byte integer value, and the acquired type (Syntax)
35 stores information indicating that it is a 4-byte integer value. The management information value instantiation unit 15
The stored management information value is converted into a DepSyntax type depending on the protocol according to the x type, and the converted management information value is returned (S67, S68). In the case of this embodiment,
pSyntax is defined as “Integer32” in the printer MIB, and is a 4-byte integer value same as Syntax here.

The agent system returns the management information value stored in each protocol-dependent type obtained by the management information value specifying unit 15 to the manager, thereby completing the GET operation.

Next, the operation of the agent in the case of the SET operation will be described with reference to FIGS. Here, a reset of the management target device is taken as an example of the management information value to be set. This object identifier in the SNMP protocol is represented by {1 3 6 1 2 1 43 5 1 1 3 1},
As in the case of the maximum capacity of the paper tray described in the GET example, {1 3 6 1 2 1 43 5 1 1 3} which is the first 11 elements
Indicates that the management target is reset.
The last element "1" is a device identifier. This management information indicates a reset state of the managed device, and in the case of a SET operation, causes the managed device to perform a reset operation according to an input value to be set.

In FIG. 33, in the case of a SET operation, the agent sends the management information identifier (DepID) from the manager.
A management information value as an input value to be set together with the information is received (S69, S70). Then, the management information identifier and the management information value are abstracted (S71, S72), and a management operation (SET) is executed (S73).

The step of management information abstraction is the same as in the case of the GET operation, and the description will not be repeated.

FIG. 34 shows steps of management information value abstraction. In FIG. 34, the input value to be set is a value (ObjectInstanc) corresponding to the abstract management information identifier (IndepID) 22.
The data is passed to the management information value abstraction unit 12 for conversion to e). In the management information value abstraction unit 12, as in the case of the management information value realization unit 15, the abstract management information identifier (IndepI
D) The corresponding attribute definition (AttrDef) 28 is acquired from 22 (S74), and the acquired attribute definition (AttrDef) 28 is further acquired.
Is acquired (S75), and the type of the management information value included in the value to be created (ObjectInstance) is obtained. Next, the given management information value is converted from the protocol-dependent type (DepSyntax) to the acquired Syntax type (S76). Then, the abstract management information identifier (Inde
From the converted management information value, the value (ObjectInstanc
e) is created (S77).

FIG. 35 shows steps for executing a management operation.
In FIG. 35, as in the case of GET, the management operation execution unit 13 converts the abstract management information identifier (IndepID) 22 to the attribute definition (AttrDef) 28 and further dispatch information (Dispa
tchInfo) 40 is acquired (S78, S79, S80,
S81). Obtained dispatch information (DispatchInfo)
40, a value (Obje) which is a management information value to be set.
The management operation is executed by dispatching the management operation to the management target device together with the ctInstance) (S8).
2). When the execution of the management operation ends, the operation of the SET as the agent system is completed.

[0076]

As described above, according to the present invention, a management information identifier based on a management protocol is converted so as to be independent of the protocol, and the management operation is executed using the identifier independent of the management protocol. I have to. Therefore, it is possible to cope with each management protocol to be used, and management operations using a plurality of management protocols become possible. Also, even when a manager that handles a new management protocol is introduced, there is no need to prepare agents corresponding to the new management protocol in parallel, and the management information identifier of the new management protocol is simply managed independently of the management protocol. It only needs to be able to be converted into an information identifier.

[Brief description of the drawings]

FIG. 1 is a conceptual diagram of a device management system.

FIG. 2 is a conceptual diagram of a device management system on a network.

FIG. 3 is a conceptual diagram of a conventional device management system when unified management is realized by changing a manager.

FIG. 4 is a conceptual diagram of a conventional device management system when unified management is realized by mounting a plurality of agents.

FIG. 5 is a block diagram showing a configuration of an embodiment of the present invention.

FIG. 6 is a diagram illustrating a form of conversion of management information according to the embodiment.

FIG. 7 is an abstract management information identifier (Inde
It is a conceptual diagram of (pID).

FIG. 8 is a conceptual diagram showing a configuration in which the above-described abstract management information identifier (IndepID) is associated with an identifier (CompID) of a device to be managed.

FIG. 9 is a conceptual diagram of a configuration in which an abstract management information identifier (IndepID) includes a device identifier (CompID) and a definition (DEF) of management information.

FIG. 10: Abstract management information identifier (IndepID) and definition (D
EF), and is a conceptual diagram of a configuration having each correspondence.

FIG. 11 is a conceptual diagram of a configuration in which a definition (DEF) is shared between managed devices.

FIG. 12 is a conceptual diagram of a configuration including a definition (common Def) of contents common to a plurality of definitions (DEF).

FIG. 13 is a conceptual diagram of a configuration in which a common Def is separated from a definition (DEF) and each of them has a correspondence.

FIG. 14 is a conceptual diagram of a configuration in which a common part of a definition (DEF) is separated and each DEF is made to have a corresponding hierarchical structure of a multi-stage layer.

FIG. 15 is a conceptual diagram of a configuration in which an abstract management information identifier (IndepID) has a common definition (AttrDef) and indicates a management information value uniquely identified by index information (Index).

FIG. 16 is a conceptual diagram of a configuration in which an abstract management information identifier (IndepID) indicates a management information value identified by an attribute definition (AttrDef) and index information (Index).

FIG. 17 is a conceptual diagram of a configuration in which a plurality of attribute definitions (AttrDef) have a common index information definition (KeyDef).

FIG. 18 Attribute definition (AttrDef) and key definition (KeyDe)
FIG. 4 is a conceptual diagram of a configuration in which a key definition (KeyDef) is shared by separating the functions shown in FIG.

FIG. 19 is a diagram showing a management information value instantiating unit provided in an agent system.
It is an agent operation | movement conceptual diagram at the time of management information value reference when using e).

FIG. 20 is an operation conceptual diagram of the agent system when referring to a management information value when syntax information (Syntax) in the management information value (ObjectInstance) is associated with an attribute definition (AttrDef).

FIG. 21 is a conceptual diagram of the operation of the agent system when a management information value is set when a management information value abstraction unit is provided and a management information value (ObjectInstance) is used in the agent system.

FIG. 22 is an operation conceptual diagram of the agent system when setting a management information value in a case where syntax information (Syntax) in the management information value (ObjectInstance) is associated with an attribute definition (AttrDef).

[Fig. 23] Fig. 23 is a diagram showing a case where the management operation is defined by an abstract management information identifier (IndepI
FIG. 9 is an operation conceptual diagram of an agent system when dispatching to a device to be managed based on dispatch information (DispatchInfo) corresponding to D).

FIG. 24 is an operation conceptual diagram of an agent system when there is a correspondence between dispatch information (DispatchInfo) and a definition (DEF).

FIG. 25 is a conceptual diagram of the operation of the agent system when each node of the definition (DEF) has a correspondence with dispatch information (DispatchInfo) when the definition (DEF) has a multi-stage hierarchical structure. It is.

FIG. 26: When the definition (DEF) has a hierarchical structure consisting of an attribute definition (AttrDef) and a key definition (KeyDef),
FIG. 11 is an operation conceptual diagram of an agent system when each node of an attribute definition (AttrDef) and a key definition (KeyDef) has a correspondence with dispatch information (DispatchInfo).

FIG. 27 is an operation conceptual diagram when the management information value is referred to in the above embodiment.

FIG. 28 is a conceptual diagram of an operation when setting a management information value in the above embodiment.

FIG. 29 is a flowchart when referring to a management information value in the above embodiment.

FIG. 30 is a flowchart of management information identifier abstraction in the above embodiment.

FIG. 31 is a flowchart of a management operation execution when referring to a management information value in the above embodiment.

FIG. 32 is a flowchart of a management information value embodiment in the above embodiment.

FIG. 33 is a flowchart at the time of setting a management information value in the above embodiment.

FIG. 34 is a flowchart of management information value abstraction in the above embodiment.

FIG. 35 is a flowchart of execution of a management operation when setting a management information value in the above embodiment.

[Explanation of symbols]

1 Manager (Manager) 3 Agent (Agent) 4 Managed device 11 Management information identifier abstraction unit 12 Management information value abstraction unit 13 Operation execution unit 14 Management information storage unit 15 Management information value instantiation unit 21 Concrete management information identifier ( DepID) 22 Abstract management information identifier (IndepID) 23 Device identifier (CompID) 24 Definition of management information (DEF) 25 Pointer to definition of management information (pointDEF) 26 Common part of definition of management information (Common Def) 28 Attribute definition (AttrDef) 29 Index information (Index) 30 Key definition of index information (KeyDef) 31 Management information value 32 Abstracted management information value (ObjectInstance) 33 Pointer to abstract management information identifier (IndepID) (po)
intIndepID) 34 Management information value storage module (valueInstance) of management information value (ObjectInstance) 35 Syntax information (Syntax) of management information value stored in management information value (ObjectInstance) 36 Pointer (pointAttrDe) to attribute definition (AttrDef)
f) 37 Management information value (ObjectInstance) management information value (v
alue) 38 Management information value (ObjectInstance) management information value size (size) 40 Dispatch information (DispatchInfo)

Claims (6)

[Claims] 1. An information processing apparatus managed based on at least one device management protocol among a plurality of types of device management protocols, comprising: a first device management information identifier generated according to the at least one device management protocol; , The at least one
Means for converting into a second device management information identifier independent of any of the two device management protocols; and holding the second device management information identifier and a device management information value corresponding to the second device management information identifier. Means, and the second information stored in the device management information storage means.
Means for executing a predetermined management operation on the device management information identifier and the device management information value corresponding to the second device management information identifier based on the second device management information identifier. Information processing device. Means for converting a device management information value corresponding to the first device management information identifier to a device management information value corresponding to the second device management information identifier; and And means for updating a device management information value corresponding to the second device management information identifier held in the device management information holding means, with the device management information value of the device management information identifier of (1). Information processing device. 3. A device for converting a device management information value of the second device management information identifier read from the device management information holding device into a device management information value corresponding to the first device management information identifier. Claim 1 or 2 which further has
An information processing apparatus according to claim 1. 4. A network system in which at least one information processing device is connected to at least one manager that manages the information processing device based on a unique management protocol, wherein the at least one device management is performed. The first device management information identifier generated according to the protocol is
Means for converting into a second device management information identifier independent of any of the two device management protocols; and holding the second device management information identifier and a device management information value corresponding to the second device management information identifier. Device management information holding means; and the second device management information holding device,
Means for executing a predetermined management operation on the device management information identifier and the device management information value corresponding to the second device management information identifier based on the second device management information identifier. Network system. 5. An agent device provided in an information processing apparatus and performing a corresponding management operation on said information processing apparatus in response to a management operation command from a manager based on a device management protocol unique to said manager, comprising: Means for converting a first device management information identifier generated according to at least one device management protocol of the device management protocols into a second device management information identifier independent of any of the at least one device management protocol; A device management information holding unit that holds the second device management information identifier and a device management information value corresponding to the second device management information identifier; and a second device management information holding unit that holds the second device management information identifier.
Means for executing a predetermined management operation on the device management information identifier and the device management information value corresponding to the second device management information identifier based on the second device management information identifier. Agent device. 6. An information processing apparatus managed based on at least one device management protocol among a plurality of types of device management protocols, wherein the first device management information identifier generated according to a predetermined device management protocol is replaced with the first device management information identifier. Means for converting into a second device management information identifier independent of a predetermined device management protocol; means for holding the second device management information identifier and a device management information value corresponding to the second device management information identifier The second information stored in the device management information storage means.
Means for executing a predetermined management operation on the device management information identifier and the device management information value corresponding to the second device management information identifier based on the second device management information identifier. Information processing device.