JP2885144B2 - Management information base system - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a management information base system, and more particularly to an OSI (Open Systems Interconnection).
and a management information base system for OSI (hereinafter, also simply referred to as a “management information base”) suitable for managing a network in accordance with the management system.

[0002]

2. Description of the Related Art A conventional management information base of this kind is disclosed, for example, in the document "Shimizu et al.," Method of arranging management information base in ATM transport network management ", IEICE CS94-21, 1994". As described above, the logical model of the monitored device of the network is used to realize the logical model on the storage area.

FIG. 20 is a block diagram for explaining a configuration of a conventional management information base.

Referring to FIG. 20, a conventional management information base includes a management information base (MIB) program 720 and a database management system (DBMS) 730.
And a database 740 built on the database management system 730. In addition,
As the database management system 730, a general-purpose relational DBMS, an object-oriented DBMS, or the like is used.
The MIB program 720 is connected to the manager 10 and the monitoring target device 110.

[0005] The manager 10 includes an MIB program 72.
0, the logically defined state of the monitored device 110 can be read or rewritten. Specifically, for the MIB program 720, the manager 10 sends the full destination name (“FDN”).
) And the attribute ID, the instance and the attribute in the instance are specified from the pair of the FDN and the attribute ID in the MIB program 720, and the DBMS 730 searches the database 740 using the specified value. .

The MIB program 720 appropriately accesses the monitored device 110 to read the status of the monitored device 110 and reflects the read status in the database 740.

[0007]

However, since the conventional management information base is generally constructed using a general-purpose DBMS, data management suitable for data used in OSI or the like can be performed. There is a problem that is difficult.

[0008] In particular, in a management information base constructed using a general-purpose DBMS, the storage capacity of data becomes large.
Also, since the program code of the DBMS itself becomes large, a large amount of storage devices are required for the management information base, and the price of the management information base increases.

In addition, a management information base constructed using a general-purpose DBMS has a function that is not necessarily required for a management information base such as OSI, so that there is a problem that the execution speed is reduced.

[0010] Accordingly, the present invention has been made in view of the above-mentioned problems, and has a management information particularly suitable for OSI-compliant network management that can reduce storage capacity and achieve high-speed processing. The purpose is to provide a base.

[0011]

In order to achieve the above object, the present invention manages an attribute representing a state of a device to be monitored in a network, and an instance including the attribute as a member, and stores an object identifier, an attribute value, One or more relative distinction names ("RD
N ") and an attribute ID representing the type of the attribute as inputs, the management information base system enabling access to a desired attribute. A directory storage device that stores information of a tree structure (containment tree) composed of: a directory storage device that receives the FDN as an input, and outputs a position of an instance corresponding to the FDN and a position of an attribute information table; Storing an attribute information table holding a correspondence relationship between the offset value to the attribute in the instance and the class to which the instance belongs; storing the attribute ID and the attribute output from the directory storage device; A class information storage device for receiving the position of the information table as an input and outputting the offset value; A data storage device that stores the attribute and stores the position of the instance output from the directory storage device and the offset value output from the class information storage device, and outputs the attribute. A management information base system is provided.

According to the present invention, the storage area of the management information base system is composed of a directory storage device, a data storage device, and a class information storage device, and manages information necessary for OSI in a necessary and sufficient manner without redundancy. Thus, various formats can be stored at the same time depending on the data, and the data can be handled uniformly.

Further, the present invention relates to ASN.1 / BER (Abst
Among the attributes stored in the form of aract Syntax Notation 1 / BasicEncoding Rule), the required storage capacity is reduced by grouping the tag field and the length field for each class.

Further, the present invention saves time for conversion by copying the state of a monitored device to a storage area without converting it to a predetermined format, and more generally realizes the monitoring target device. The required storage capacity is suppressed by utilizing the fact that the data format of the existing data format is smaller than the ASN.1 / BER format.

Further, according to the present invention, a method for collecting data is arranged for some attributes in the same manner as a normal attribute, and data is collected from the monitoring target device only when an access request to the attribute occurs. Thereby, the attribute in the storage area and the data only in the monitoring target device are uniformly accessed.

[0016]

Embodiments of the present invention will be described below in detail with reference to the drawings.

[0017]

First Embodiment First, a first embodiment of the present invention will be described with reference to FIGS.

FIG. 1 is a block diagram for explaining the configuration of the management information base according to the first embodiment of the present invention.

Referring to FIG. 1, the management information base according to the present embodiment includes a directory storage device 20, a data storage device 30, and a class information storage device 100 as main components. The manager 10 monitors the monitoring target device 110 via the management information base provided with.

The data storage device 30 includes an instance 50
It stores instances and attributes managed by the management information base according to the present embodiment, including attributes and attributes 60. An attribute is a member of any one instance. That is, the instance has a pointer to the attribute that is a member.

The class information storage device 100 has all attribute information tables managed by the management information base according to the present embodiment, including the attribute information table 70. One attribute information table exists for each class to which the instance managed by the management information base according to the present embodiment belongs.

The attribute information table records the correspondence between the attribute ID and the offset value (distance from the head of the instance to the pointer indicating the attribute) to the pointer indicating the attribute specified by the attribute ID. ing.

The directory storage device 20 stores in advance the correspondence between FDNs and instances and the correspondence between FDNs and attribute information tables. Therefore, by providing the FDN, the position of the corresponding instance in the data storage device 30 can be obtained, and the position of the corresponding attribute information table in the class information storage device 100 can be obtained.

The monitoring target device 110 is a device on a network that is monitored and managed by the management information base according to the present embodiment. In the management information base according to the present embodiment, the instances and attribute values stored in the data storage device 30 are changed based on the state of the monitoring target device 110, and conversely, the data storage device 30 stores the data according to a request from the manager 10. The attribute value is reflected on the monitoring target device 110.

FIG. 2 is a flowchart for explaining the operation of the management information base according to the first embodiment of the present invention.

The outline of the operation of the management information base according to the present embodiment will be described with reference to FIGS.

When the manager 10 accesses an attribute managed by the management information base according to the present embodiment, the manager 10 gives an FDN and an attribute ID to specify the attribute.

When the management information base according to this embodiment receives the FDN and the attribute ID from the manager 10 (step 1010), it inputs the given FDN to the directory storage device 20 and stores it in the class information storage device 100. Corresponding attribute information table 70 (“address”)
(Step 1020).

The obtained position of the attribute information table 70 and the given attribute ID are input to the class information storage device 100, and the offset value from the head of the instance to the pointer indicating the attribute is obtained (step 1030).

Then, the position of the corresponding instance is obtained by inputting the given FDN to the directory storage device 20 (step 1040).

The offset value obtained in step 1030 is added to the address of the instance 50 obtained in step 1040, and a pointer to the attribute 60 stored at the location indicated by the obtained address is obtained (step 1050). ).

Finally, the attribute 60 is accessed using the pointer obtained in step 1050 (step 1).
060).

In the operation shown in FIG. 2 of the management information base according to this embodiment, the operation of inputting the FDN and obtaining the position of the instance and the attribute information table corresponding to the class to which the instance belongs (step 1020 and step 1040) may be performed in parallel.

FIG. 3 is a block diagram for explaining in more detail the configuration of the management information base directory storage device 20 according to the first embodiment of the present invention.

Referring to FIG. 3, directory storage device 2
0 indicates a plurality of directory structures including the directory structures 240 and 260 and a directory sub-structure 2
And a plurality of directory sub-structures such as 50, and by using these structures, the position of the instance corresponding to the input FDN and the attribute information table corresponding to the class to which the instance belongs are stored. Position and
Is output.

Here, the directory structure and the directory sub-structure are combined to form a tree structure (“containment tree”).
Or "naming tree"). The directory structure 240 that stands at the top of the tree structure is also called a root directory structure.

In the directory structure, taking the directory structure 240 as an example, an instance pointer 242 which is a pointer to an instance, and an ID table 246 indicating the correspondence between the object identifier and the directory sub-structure.
And When an object identifier is given to a directory structure, an ID table is searched and a corresponding directory sub-structure is output. Also, an instance corresponding to the directory structure can be obtained.

The directory sub-structure is, for example, the directory sub-structure 250, a class tag 253 which is a pointer to the attribute information table 70, and an RDN attribute value indicating the correspondence between the attribute value and the directory structure. Table 257. When an attribute value is given to the directory sub-structure, the RDN attribute value table is searched and the corresponding directory structure is output. Also, an attribute information table corresponding to the directory substructure can be obtained.

The input FDN is composed of a list of relative distinction names (referred to as "RDN"). RDN is composed of a pair of an object identifier and an attribute value.

FIG. 4 is a flowchart for explaining the operation of the management information base directory storage device 20 according to the first embodiment of the present invention.

The operation of the management information base directory storage device 20 according to this embodiment will be described with reference to FIGS.

The directory storage device 20 is the manager 1
When FDN is received from 0 (step 1110), a root directory structure (here, directory structure 240) is searched for and set as the current directory (step 1120).

Then, it is checked whether or not the list of RDNs constituting the FDN is empty (step 1125). If it is not empty ("No" in step 1125), the flow advances to step 1130.

The directory storage device 20 extracts the RDN at the head of the FDN, gives the object identifier of the RDN to the directory structure as the current directory, and obtains a matching directory sub-structure (step 1130). Furthermore, RD is added to the directory substructure.
Given the attribute values of N, a directory structure is obtained (step 1140).

After the processing of steps 1130 and 1140 is completed, the obtained directory structure is set as the current directory (step 1150). And FDN
From which the leading RDN is removed is set as a new FDN, and the process returns to the determination of step 1125 (step 116).
0).

While the FDN list is not empty (while "No" in step 1125), the processing in steps 1130 to 1160 is repeated, and when the FDN list becomes empty (in the case of "Yes" in step 1125) ), The destination pointed to by the instance pointer of the current directory is set to the instance corresponding to the input FDN (step 1170).

On the other hand, an attribute information table is obtained based on the class tag of the directory sub-structure immediately before the current directory structure (step 1180). This is the attribute information table corresponding to the class to which the instance belongs.

With reference to FIGS. 3 and 4, the operation of the directory storage device 20 will be described in further detail using a specific example.

As an example, the FDN given from the manager 10 to the management information base according to the present embodiment is $ 12.
3.1.2−12.1.2. In addition, in the notation of FDN, the inside of the inside “｛｝” indicates RDN,
The former inside the RDN represents the object identifier, and the latter represents the attribute value. Although the FDN of this example includes only one RDN, it usually includes a plurality of RDNs.

First, upon receiving {12.3.1.2-12} as the FDN from the manager 10 (step 111)
0), the root directory structure 240 is set as the current directory (step 1120). In the initial state, the FDN is not empty, so "No" in step 1125.
It proceeds to step 1130.

The object identifier “12.3.1.2” is extracted from the first RDN of the FDN. The object identifier is provided to the directory structure 240, and a matching directory substructure 250 is obtained (step 1130).

Next, the attribute value “12” of the RDN is given to the directory substructure 250, and the directory structure 260 is obtained (step 1140). In addition,
The obtained directory structure 260 is set as a current directory (step 1150). Then, the first RDN is removed from the FDN (step 1160).

After the processing of step 1160 is completed, the process returns to step 1125 to determine whether or not the FDN is empty.
Here, since the FDN is empty, step 112
It is determined “Yes” in 5 and the process proceeds to step 1170.
Then, the position of the instance 50 corresponding to the directory structure 260 that is the current directory is obtained (step 1170). Further, the position of the corresponding attribute information table 70 is obtained from the directory substructure 250 used immediately before (step 1180).

FIG. 5 is a block diagram for explaining the configuration of the management information base class information storage device 100 according to the first embodiment of the present invention in further detail.

Referring to FIG. 5, class information storage device 10
0 stores a plurality of attribute information tables including the attribute information table 70. When the position of the attribute information table and the attribute ID are input to the class information storage device 100, the offset value to the corresponding attribute is output. The attribute held by the data storage device 30 is described in the ASN.1 / BER format, and includes three fields: a tag field (T), a length field (L), and a value field (V).

The attribute information table records the correspondence between the attribute ID and the offset value to the attribute. When the attribute ID is given, the corresponding offset value is output.

FIG. 6 is a flowchart for explaining the operation of the management information-based class information storage device 100 according to the first embodiment of the present invention.

The operation of the management information base class information storage device 100 according to this embodiment will be described with reference to FIGS.

Upon receiving the FDN and the attribute ID from the manager 10 (step 1201), first, the directory storage device 20 is provided with the FDN, and the position of the attribute information table 70 corresponding to the class to which the instance specified by the FDN belongs is determined. Is obtained (step 1202).

Thereafter, the position and attribute ID of the attribute information table obtained in step 1202 are given to the class information storage device 100 (step 1203). The class information storage device 100 gives an attribute ID to the attribute information table indicated by the position of the attribute information table, and obtains a corresponding offset value (step 1204).

On the other hand, the FDN is stored in the directory storage device 20.
To obtain the position of the corresponding instance (step 1205). Finally, the position of the instance obtained in step 1205 and the offset value obtained in step 1204 are given to the data storage device 30, and the data storage device 30 adds the offset value to the position of the instance. Obtains the position of the pointer to the attribute.
The position of the attribute is obtained by obtaining the pointer (step 1206).

With reference to FIGS. 5 and 6, the operation of the class information storage device 100 will be described in more detail using a specific example.

As an example, the FDN given from the manager 10 to the management information base according to the present embodiment is $ 12.
3.1.2-12} and the attribute ID is “12.1.2”.

First, the same procedure as in the above-described specific example (FIG. 4)
The positions of the instance 50 and the positions of the attribute information table 70 are obtained according to steps 1110 to 1180 (steps 1201, 1202, and 1205).

The class information storage device 100 stores the attribute information table 7
When the attribute ID is given to the attribute information table 70, the attribute ID
Is searched for an entry whose is "12.1.2". In this example,
The value held by the searched entry is “7”, and this value becomes the offset value (step 1204).

The retrieved offset value “7” and the position of the instance 50 are given to the data storage device 30. The data storage device 30 obtains the address storing the pointer to the attribute in the instance 50 by adding the offset value "7" to the position of the instance (step 1206). The attribute 60 indicated by the pointer stored at the obtained address is the attribute to be accessed.

[0067]

Second Embodiment FIG. 7 is a block diagram for explaining a configuration of a management information base according to a second embodiment of the present invention.

Referring to FIG. 7, the management information base according to the present embodiment includes a directory storage device 20, a tagless data storage device 350, a class information storage device with tag field 360, a tag adder 322, Is provided.

In the management information base according to the present embodiment, a column for a tag field is added to the attribute information table, and the attribute information table 70 is newly added to the attribute information table with tag field 37.
0 has been replaced. In the attribute information table with tag field 370, when an attribute ID is given, an offset value and a tag field that the attribute should have are output.

In the management information base according to the present embodiment, first, a class information storage device 360 with a tag field is newly used instead of the class information storage device 100.
The class information storage device with tag field 360 stores an attribute information table with tag fields instead of the attribute information table. When the position and attribute ID of the attribute information table with tag field are given to the class information storage device with tag field 360, the corresponding offset value and tag field are output.

Second, instead of the data storage device 30,
An untagged data storage device 350 is used. In the non-tagged data storage device 350, in addition to the attributes that the data storage device 30 holds, including the tag field, the length field, and the value field, the tag field is deleted and the length field and the value field are deleted. The configured attributes are also retained.

[0072] Thirdly, it tagged 32 2 is connected to the untagged data storage device 350 and the tag field with the class information storage device 360. If you enter an attribute value to the tag attacher 32 2 and a tag field for outputting a uniform attribute of the tag, length, value field.

FIG. 8 is a flowchart for explaining the operation of the management information base according to the second embodiment of the present invention.

Referring to FIGS. 7 and 8, the operation of the management information base according to the present embodiment will be described.

First, in steps 1210 and 1220, the same processing as in steps 1201 and 1202 shown in FIG.
Get the address of

Next, by giving an attribute ID to the attribute information table with tag field 370 obtained in step 1220, a tag field is obtained together with the offset value (step 1230).

In step 1240, the position of instance 310 obtained by performing the same processing as step 1204 shown in FIG. 6, and the tag field and offset value obtained in step 1230 are stored in untagged data storage device 350. (Step 1250). Then, the data storage device 350 without a tag performs step 1 shown in FIG.
By performing the same processing as in step 206, the position of the attribute is obtained from each value given in step 1250 (step 1260).
It gives the obtained attribute and the tag field obtained in step 1230 to the tag adder 32 2 (step 127
0).

Thereafter, it is determined whether or not the given tag field is empty (step 1280). If the tag field is empty (“Yes” in step 1280), the process ends, and the given attribute is left as it is. Make it the final attribute. On the other hand, when it is not empty (in the case of “No” in step 1280), the given attribute is composed of only the length field and the value field. Attribute value (step 12
90).

With reference to FIGS. 7 and 8, the operation of the management information base according to the present embodiment will be described in further detail using a specific example.

First, a first specific example will be described.

By giving a pair of the FDN and the attribute ID “12.1.2”, the position of the instance 50, the offset value “12”, and the tag field “0x02” are obtained (steps 1210 to 1240). Then, these values are given to the tagless data storage device 350 (step 125
0).

Using the instance position and the offset value, the tagless data storage device 350 obtains the attribute 310 (step 1260). Then, the tag adder 322 connected to the untagged data storage device 350 combines the given tag field “0x02”, the length field 320 of the attribute 310, and the value field 330 to obtain the ASN.1
/ BER format attribute (step 1270, step 1280, and 1290).

Next, a second specific example will be described.

From the given FDN, an instance 385
And the position of the attribute information table 380 are obtained (steps 1210, 1220, and 1240). The attribute ID “12.1.22” is given to the attribute information table 380, and the offset value “2
3 "and the tag field are obtained (step 1230).

Thereafter, the position, offset value, and tag field of the instance are given to the tagless data storage device 350 (step 1250), and the tagless data storage device 350 obtains the attribute 390 from the instance position and the offset value (step 1250). 1260).

[0086] The tagged 32 2 gives the attributes 390 and the tag field is (step 1270), since in this example the tag field is empty, and outputs the attribute 390 as the final attribute (at step 1280, "Yes" in the case of).

If the tag field is empty, the corresponding attribute is CHOICE type of ASN.1, ANY
Although the type is not determined in advance, such as the type, in such a case, the attribute 390 includes all of the tag field, the length field, and the value field. Output as final attributes.

Since the management information base according to the first embodiment has a configuration in which each attribute has a tag field, the storage capacity is increased. But,
Since the attributes of instances derived from a common class have the same type, even a plurality of attributes have the same tag field. In the management information base according to the present embodiment, focusing on the fact that the attribute indicated by the same entry in the same attribute information table often has the same tag field even if the instance is different, the tag field is embedded in the entry, and the attribute The structure which deletes a tag field from the side is adopted. Thereby, the storage capacity required in the management information base according to the present embodiment can be reduced.

[0089]

Third Embodiment FIG. 9 is a block diagram for explaining a configuration of a management information base according to a third embodiment of the present invention.

Referring to FIG. 9, the management information base according to the present embodiment includes a directory storage device 20, a tag / lengthless data storage device 355, a tag / length-attached class information storage device 365, and a tag storage device. A length adder 325;

Referring to FIGS. 7 and 9, the management information base according to the present embodiment is compared with the management information base according to the second embodiment. A column for a length field is added to the table 370, and the attribute information table 375 with a tag / length field is newly replaced. When the attribute information table with the tag / length field is provided with the attribute ID, the offset value, the tag field, and the length field are output.

Specifically, first, a class information storage device with tag / length field 365 is newly used instead of the class information storage device with tag field 360.
The class information storage device with tag / length field 365 outputs the offset value, the tag field, and the length field by giving the position of the attribute information table and the attribute ID.

Second, the tag field and the length field are deleted from the attribute composed of the tag field, the length field, and the value field, and the attribute is composed of only the value field. That is, it has a data storage device 355 without a tag / length field, stores various attributes such as a normal attribute, an attribute without a tag field, an attribute without a tag field and a length field, and gives an instance and an offset value. And output the corresponding attribute.

Third, a tag / length adder 325 is provided instead of the tag adder 322. The tag / length adder 325 includes the attribute output from the tag / lengthless data storage device 355 and the tag / length-attached class information storage device 36.
5, the tag field and the length field,
, And outputs an attribute with a complete tag, length, and value fields.

As described above, according to the management information base according to the present embodiment, if the length is statically determined data, compared with the management information base according to the second embodiment, The required storage capacity can be further reduced by the length field.

[0096]

Fourth Embodiment FIG. 10 is a block diagram for explaining a configuration of a management information base according to a fourth embodiment of the present invention.

Referring to FIG. 10, converter 540 is provided in data storage device 30 according to the present embodiment.
An attribute copy area 510 is provided in a part of the data storage device 30, and attributes such as an attribute 520 indicating a state in the monitoring target device 110 are managed. Also,
Instances such as the instance 550 having such an attribute as a member are stored in the data storage device 30 in the same manner as an instance having a normal attribute.

Attribute copy area 5 in data storage device 30
As in the first embodiment, the parts other than 10 are AS AS.
Attribute is stored in N.1 / BER format. Attribute copy area 5
The attributes in 10 are not converted into the ASN.1 / BER format, but are stored as register values indicating the state of the monitoring target device 110.

FIG. 11 is a flowchart for explaining the operation of the management information base according to the fourth embodiment of the present invention. FIG. 11A is a flowchart when the status of the monitoring target device 110 is periodically copied to the attribute copy area 510, and FIG. 11B is a flowchart when the attribute is accessed according to a request from the manager 10.

The operation of the management information base according to the present embodiment will be described with reference to FIGS.

First, the first operation according to FIG. 11A will be described.

The data storage device 30 is the monitored device 110
Is copied to the attribute copy area 510 (step 1410), a predetermined time elapses (step 142).
0), when the predetermined time has elapsed (in the case of “Yes” in step 1420), the process returns to step 1410 to copy to the attribute copy area 510 again. On the other hand, while the predetermined time has not elapsed (while “No” in step 1420), the determination in step 1420 is repeated.

Next, a second operation according to FIG. 11B will be described.

First, the position of the attribute is obtained according to the processing of steps 1010 to 1050 shown in FIG. 2 of the first embodiment, and the attribute is accessed (step 1450). Next, it is checked whether the accessed attribute is data in the attribute copy area 510 (step 14).
55). If the attribute is data in the attribute copy area 510 ("Yes" in step 1455), the attribute is converted to ASN.1 / BER format using the converter 540. On the other hand, if the attribute is not the data in the attribute copy area 510 ("No" in step 1455), the attribute is accessed as it is as in the first embodiment.

Normally, since the data realized by the register of the monitored device 110 requires less storage area than the data in the ASN.1 / BER format, the management database according to the present embodiment is more It can be realized with a small storage area.

Normally, a regular copy operation is performed to reflect the state of the monitoring target device 110 to the attribute in the data storage device 30, and data conversion in ASN.1 / BER format is also performed. In the mode, the attribute copy area 510 is not converted to the ASN.1 / BER format unless accessed by the manager 10.
When there is little access to the attributes in the, the processing speed can be improved.

This embodiment can be similarly applied to the second and third embodiments in addition to the first embodiment.

[0108]

Fifth Embodiment FIG. 12 is a block diagram for explaining a configuration of a management information base according to a fifth embodiment of the present invention.

Referring to FIG. 12, the management information base according to the present embodiment includes a directory storage device 20, a data storage device 30, and a class information storage device 100.
An identifier converter 410 is provided between the manager 10 and the directory storage device 20.

The directory storage device 20 has an internal object identifier that guarantees uniqueness only among object identifiers used in the system. Since the uniqueness of the internal object identifier only needs to be guaranteed within the system, it is smaller than the object identifier that guarantees uniqueness in the whole world, and the structure is simple.

Internal identifier directory structures 420, 4
Object identifiers in the ID table of the internal identifier directory structure such as 60 are represented as internal object identifiers. The ID table held by the internal identifier directory structure according to the present embodiment is called an internal ID table. When an internal object identifier is given to the internal ID table, a corresponding (internal identifier) directory substructure is output.

The FD provided by the manager 10
N and the object identifier in the attribute ID are once converted into an internal object identifier by the identifier converter 410,
It is input to the directory storage device 20.

FIG. 13 is a flowchart for explaining the operation of the management information base according to the fifth embodiment of the present invention.

The operation of the management information base according to the present embodiment will be described with reference to FIGS.

First, the manager 10 sends the FDN and the attribute I
Upon receiving D (step 1310), the identifier converter 410 converts all object identifiers included in the FDN and the attribute ID into internal object identifiers (step 1320). Then, the attribute is accessed using the converted internal object identifier instead of the object identifier (step 1330). The access to the attribute is performed by, for example, the same processing as in steps 1110 to 1180 shown in FIG. 4 of the first embodiment.

According to the management information base of the present embodiment, the size of the internal object identifier used is smaller than that of a normal object identifier and the structure is simple, so that the required storage capacity can be reduced. be able to.

Further, since the comparison operation between the internal object identifiers can be performed faster than the comparison operation between the object identifiers, the processing speed can be improved.

This embodiment can be similarly applied to the second and third embodiments, in addition to the first embodiment, and can be used together with the fourth embodiment. It can also be applied.

[0119]

Sixth Embodiment FIG. 14 is a block diagram for explaining a configuration of a management information base according to a sixth embodiment of the present invention.

Referring to FIG. 14, the management information base data storage device according to the present embodiment is different from the management information base data storage device 30 according to the first embodiment, for example, in place of the attribute stored in the management information base data storage device 30. , Part of which has attribute acquisition function 6
Attribute acquisition functions such as 40 are stored.

When the attribute specified from the instance address and the offset value input from the directory storage device 20 is an attribute acquisition function, the data storage device 30 activates the attribute acquisition function. The activated attribute acquisition function acquires an attribute value that should originally be in place of the attribute acquisition function from the monitoring target device 110 and sets it as an attribute.

FIG. 15 is a flowchart for explaining the operation of the management information base according to the sixth embodiment of the present invention.

The operation of the management information base according to this embodiment will be described with reference to FIGS.

First, a pointer indicating an attribute is obtained according to the processing of steps 1010 to 1050 shown in FIG. 2 of the first embodiment (step 151).
0).

Next, it is checked whether the destination pointed to by the pointer is an attribute acquisition function (method) or an ordinary attribute (step 1).
515). Here, in the case of the attribute acquisition function (step 15
If “Yes” in 15), an attribute acquisition function is started (step 1520). The activated attribute acquisition function is F
An original attribute specified from the DN and the attribute ID is acquired from the monitoring target device 110 and is set as an attribute (step 1).
530).

On the other hand, if the destination pointed by the pointer is a normal attribute ("No" in step 1515), the attribute pointed to by the pointer is accessed as in step 1160 (step 1540).

According to the management information base according to the present embodiment, the attribute of which the status of the monitored
Moreover, an attribute acquisition function is used for an attribute for which it is important to maintain consistency between the state of the monitoring target device 110 and the corresponding attribute in the data storage device 30 so that the latest attribute is obtained when necessary. can do.

In addition, while maintaining the consistency between the state of the monitoring target device 110 and the data in the data storage device 30, the attribute acquisition function and the attribute are independently realized without changing the manager 10 or the directory storage device 20. can do. Further, changes in the data storage device 30 and the class information storage device 100 can be minimized.

This embodiment can be similarly applied to the second and third embodiments in addition to the first embodiment, and the fourth and fifth embodiments can be applied. It can be applied together with the embodiment.

[0130]

Seventh Embodiment FIG. 16 is a block diagram for explaining a configuration of a management information base according to a seventh embodiment of the present invention.

Referring to FIG. 16, in the management information base data storage device 30 according to this embodiment, for example, the first
In addition to the management information base according to the embodiment, a cache 910 connected to the manager 10 and the directory storage device 20, and a cache searcher 9 that searches the cache 910 and replaces the cache 910 according to a predetermined algorithm
00 is provided.

The cache 910 records a part of the three correspondences between the FDN, the position of the instance, and the position of the attribute information table. The cache searcher 900
Are connected to the manager 10, the directory storage device 20, and the class information storage device 100, respectively.

The cache search unit 900 is the manager 10
, First, the cache search unit 90
0 searches the cache 910 for an entry that matches the given FDN. If a matching entry is found, the position of the instance and the position of the attribute information table are obtained from the entry.

On the other hand, if the cache searcher 900 cannot find an entry matching the given FDN from the cache 910, it gives the directory storage device 20 an FDN, for example, as shown in FIG. 2 of the first embodiment. In accordance with the above processing, the position of the instance and the position of the attribute information table are searched for using the directory storage device 20. Then, the position of the instance and the position of the attribute information table obtained as a result are made one entry corresponding to the given FDN, and are replaced with the already stored entry in the cache 910.

FIG. 17 is a flowchart for explaining the operation of the management information base according to the seventh embodiment of the present invention.

The operation of the management information base according to the present embodiment will be described with reference to FIGS.

First, when the cache search device 900 receives the FDN from the manager 10 (step 1910),
The cache searcher 900 searches the cache 910,
A search is made for an entry that matches the given FDN (step 1920).

If an entry that matches the given FDN is found (“Yes” in step 1925), the position of the instance held by the entry and the position of the attribute information table are used, and Steps 1030, 1050, and 106 shown in FIG. 2 of one embodiment
The attribute is accessed in accordance with the processing of 0 (step 196).
0).

On the other hand, if an entry that matches the given FDN cannot be found (“N” in step 1925)
o)), the FDN is stored in the directory storage device 20.
And, for example, steps 1020 and 1020 shown in FIG.
The position of the instance and the position of the attribute information table are obtained in accordance with the processing of Step 40 (Step 1930).

Then, for example, step 10 shown in FIG.
The attribute is accessed according to the processing of 30, 1050, and 1060 (step 1940). Step 19
The three correspondences between the FDN obtained in step 30, the position of the instance, and the position of the attribute information table are as follows.
It is replaced with one entry in the cache 910 using 0 (step 1950).

Referring to FIGS. 16 and 17, the operation of the management information base according to the present embodiment will be described in further detail using a specific example.

As a first specific example, the cache search unit 9
00 from the manager 10 {12.3.1.2-12}, {12.
It is assumed that an FDN composed of 3.1-91} and {12.1.2-1} has been received (step 1910). In this case, as a result of the cache search device 900 searching the cache 910 (step 1920), an entry that matches the given FDN is searched for (“Ye” in step 1925).
s "), the attribute is directly accessed based on the position of the instance on the entry and the position of the attribute information table (step 1960).

As a second specific example, the cache search unit 9
00 from the manager 10 {12.3.1.2-11}, {12.
It is assumed that an FDN composed of 3.1-91} and {12.1.2-1} has been received (step 1910). As shown in FIG.
It is assumed that the FDN of this example is not stored in the cache 910, and a matching entry cannot be found even if the cache searcher 900 searches the cache 910. In this case (in the case of “No” in step 1925), the cache search device 900 stores the FD in the directory storage device 20.
N, and access the attribute according to the same processing as in the first embodiment (steps 1930 and 1940).
Then, based on the given FDN, the position of the instance and the position of the attribute information table output from the directory storage device 20 are replaced with one of the entries stored in the cache 910 together with the FDN (step 19).
50).

According to the management information base according to the present embodiment, the conversion from the FDN to the position of the instance and the position of the attribute information table does not take a long time via the directory storage device, but is performed in part of the FDN. Can be temporarily stored in a cache, and the FDN stored in the cache can be directly converted without going through a directory device, so that the processing speed can be increased.

This embodiment can be applied to the second and third embodiments in addition to the first embodiment, and the fourth to sixth embodiments can be applied. It can be applied together with the embodiment.

[0146]

Eighth Embodiment FIG. 18 is a block diagram for explaining a configuration of a management information base according to an eighth embodiment of the present invention.

Referring to FIG. 18, the management information base according to the present embodiment is different from the management information base cache 910 according to the seventh embodiment in that a part of the FDN and a directory structure position are stored. A new cache 950 for holding the correspondence is provided.

FIG. 19 is a flowchart for explaining the operation of the management information base according to the eighth embodiment of the present invention.

The operation of the management information base according to this embodiment will be described with reference to FIGS.

First, when the cache search unit 900 receives the FDN from the manager 10 (step 2050),
The cache searcher 900 searches the cache 950,
From the head of the given FDN, an entry that partially matches is searched for (step 2060).

If an entry having a partial match from the beginning of the given FDN is found ("Yes" in step 2065), the directory obtained from the position of the directory structure held by the entry is found. The structure is set as a root directory structure, a part other than the part where the FDN is matched is given to the directory storage device 20, and the position of the instance and the position of the attribute information table are obtained using the directory storage device 20 (step 2100). Then, step 103 shown in FIG. 2 of the first embodiment is performed.
The attributes are accessed according to the processing of 0, 1050, and 1060 (step 2110).

On the other hand, if a matching entry cannot be found even at a part of the given FDN from the top (in the case of “No” in step 2065), the FDN is given to the directory storage device 20, and for example, as shown in FIG. Step 1
According to the processing of 020 and 1040, the position of the instance and the position of the attribute information table are obtained (step 2070).

Then, for example, step 10 shown in FIG.
The attribute is accessed according to the processing of 30, 1050, and 1060 (step 2080). Note that a part of the head of the FDN and the directory structure corresponding thereto are replaced with one entry of the cache 950 by using the cache searcher 900 (step 2090).

Referring to FIGS. 18 and 19, the operation of the management information base according to the present embodiment will be described in further detail using a specific example.

As an example, the cache retrieving device 900 sends a message from the manager 10 to {12.3.1.2-12}, {12.3.1-9}.
It is assumed that an FDN composed of {1} and {12.1.2-1} has been received (step 2050). The cache search unit 900 searches the cache 910 (step 2060), and a part {12.3.1.2-12}, {12.3.1} of the head of the given FDN.
It is assumed that an entry matching −91｝｝ has been found (in the case of “Yes” in step 2065). In this case, a root directory structure is obtained based on the position of the directory structure stored in the found entry, and the remaining part of the FDN, {12.1.2-1}, is stored in the directory storage device 20. Is given, and the position of the instance and the position of the attribute information table are obtained using the directory storage device 20 (step 2100). Then, the attribute is finally accessed (step 2110).

According to the management information base of this embodiment, the hit ratio in the cache can be further improved, as compared with the seventh embodiment, as long as the part of the RDN included in the FDN matches. be able to.

This embodiment can be applied to the second and third embodiments in addition to the first embodiment, and the fourth to sixth embodiments can be applied. It can be applied together with the embodiment.

As described above, various preferred embodiments of the present invention have been described. However, the present invention is not limited to these embodiments, but includes various embodiments according to the principle of the present invention.

For example, the management information base of the present invention is the OS
I is particularly suitable as a management information base for a network according to ASN. SNMP (Simple Network Management Protocol) that manages data in 1 / BER format
It can also be used as a management information base for a network of a type, and can be applied to a more general network management information base.

[0160]

As described above, according to the management information base system of the present invention, storage areas are classified into three types: a directory storage device, a data storage device, and a class information storage device. Since information is divided into three types of independent information, detailed information management according to attributes can be realized.

According to the management information base system of the present invention, the tag field is separated from the attribute expressed in the ASN.1 / BER format, and the common tag field is arranged in the attribute information table. The required storage capacity can be reduced by omitting the tag field.

Further, according to the management information base system of the present invention, the length field is separated from the attribute whose length is statically determined, and the common length field is arranged in the attribute information table. The storage capacity can be reduced.

In the management information base system according to the present invention, it is necessary to store some attributes in the data storage device in the form of a register indicating the state of the monitored device instead of the ASN.1 / BER format. Storage capacity can be reduced, and when the frequency of accessing the attribute is low, the cost required for converting the attribute format can be reduced.

Further, in the management information base system of the present invention, the required storage capacity can be reduced by using an internal object identifier which guarantees uniqueness only in the system instead of the object identifier, and furthermore, the instance and the The search speed of the attribute can be improved.

Furthermore, in the management information base system of the present invention, by arranging an attribute acquisition function in front of a pointer indicating an attribute instead of an attribute, it is possible to effectively cope with a rapidly changing attribute. A case where a normal attribute is accessed and a case where an attribute is accessed via an attribute acquisition function can be unified.

[Brief description of the drawings]

FIG. 1 is a block diagram for explaining a configuration of a management information base according to a first embodiment of the present invention.

FIG. 2 is a flowchart illustrating an operation of a management information base according to the first embodiment of the present invention.

FIG. 3 is a block diagram for explaining a configuration of a management information base directory storage device 20 according to the first embodiment of the present invention.

FIG. 4 is a flowchart for explaining the operation of the management information base directory storage device 20 according to the first embodiment of the present invention.

FIG. 5 is a block diagram for explaining a configuration of a management information base class information storage device 100 according to the first embodiment of the present invention.

FIG. 6 is a flowchart for explaining an operation of the management information-based class information storage device 100 according to the first embodiment of the present invention.

FIG. 7 is a block diagram illustrating a configuration of a management information base according to a second embodiment of the present invention.

FIG. 8 is a flowchart for explaining an operation of a management information base according to the second embodiment of the present invention.

FIG. 9 is a block diagram illustrating a configuration of a management information base according to a third embodiment of the present invention.

FIG. 10 is a block diagram illustrating a configuration of a management information base according to a fourth embodiment of the present invention.

FIG. 11 is a flowchart illustrating an operation of a management information base according to a fourth embodiment of the present invention.

FIG. 12 is a block diagram illustrating a configuration of a management information base according to a fifth embodiment of the present invention.

FIG. 13 is a flowchart illustrating an operation of a management information base according to a fifth embodiment of the present invention.

FIG. 14 is a block diagram illustrating a configuration of a management information base according to a sixth embodiment of the present invention.

FIG. 15 is a flowchart illustrating an operation of a management information base according to a sixth embodiment of the present invention.

FIG. 16 is a block diagram illustrating a configuration of a management information base according to a seventh embodiment of the present invention.

FIG. 17 is a flowchart illustrating an operation of a management information base according to the seventh embodiment of the present invention.

FIG. 18 is a block diagram illustrating a configuration of a management information base according to an eighth embodiment of the present invention.

FIG. 19 is a flowchart illustrating an operation of a management information base according to the eighth embodiment of the present invention.

FIG. 20 is a block diagram for explaining a configuration of a conventional management information base.

[Explanation of symbols]

10 Manager 20 Directory storage device 30 Data storage device 50 Instance 60, 310, 345 Attributes held by instance 50 70 Attribute information table 100 Class information storage device 110 Monitored device 240 Directory structure (root directory structure) 242 Instance pointer 246 ID table 250 Directory substructure 253 Class tag 257 RDN attribute value table 260 Directory structure 302 Tag field 320 Length field 330 Value field 322 Tag adder 325 Tag / length adder 350 Tagless data storage device 355 Tag / length Data storage device without field 360 Class information storage device with tag field 365 Class information storage device with tag / length field 370, 380 Tag file Attribute information table with fields 375 Attribute information table with tag field and length field 385 Instance 390 Attributes held by instance 385 410 Identifier converter 420, 440 Internal identifier directory structure 425 Internal ID table 510 Attribute copy area 520 Attribute copy area 510 540 Transformer 550 Instance 640 Attribute acquisition function 720 MIB program 730 Database management system (DBMS) 740 Database 900 Cache searcher 910, 950 Cache

Claims (9)

(57) [Claims] An object that manages an attribute representing a state of a device to be monitored in a network and an instance including the attribute as a member, and has one or more relative distinction names ("RDN") having an object identifier and an attribute value. ), And an attribute I representing the type of the attribute.
D, and inputting a desired attribute to the management information base system, wherein information of a tree structure (containment tree) constituted by the instances is stored, and the FDN is input and the FDN corresponds to the FDN. A directory storage device that outputs the position of the instance and the position of the attribute information table; and an attribute information table that holds a correspondence relationship between the attribute ID and an offset value to the attribute in the instance. A class information storage device that stores the attribute ID and the position of the attribute information table output from the directory storage device and outputs the offset value, as input, the class and the instance; And the position of the instance output from the directory storage device and the class information And the offset value output from the device, as input, the management information base system characterized in that it comprises a data storage device for outputting the attribute. 2. An apparatus for managing an attribute representing a state of a device to be monitored in a network and an instance including the attribute as a member, and having one or more relative distinction names ("RDN") having an object identifier and an attribute value. ), And an attribute I representing the type of the attribute.
D, wherein a desired attribute can be accessed by using D as an input. The attribute includes a tag field indicating a type, a length field indicating a length, and a value field indicating a value. AS
N.1 / BER format, stores information of a tree structure (containment tree) composed of the instances, receives the FDN as an input, and stores the position of the instance corresponding to the FDN and the position of the attribute information table A directory storage device that outputs the attribute information, an attribute information table holding a correspondence relationship between the attribute ID, an offset value to the attribute in the instance, and the tag field corresponding to the class to which the instance belongs. A class information storage device that receives the attribute ID and the position of the attribute information table output from the directory storage device and outputs the offset value and the tag field, and the instance; The attribute having no tag field, and the instance output from the directory storage device. And a data storage device that outputs the attribute having the length field and the value field by using the position of the position information and the offset value output from the class information storage device as an input, and output from the data storage device. A tag adder for adding the tag field output from the class information storage device to the attribute having the length field and the value field. 3. An attribute representing a state of a device to be monitored in a network and an instance including the attribute as a member, and one or more relative distinction names (“RDN”) having an object identifier and an attribute value. ), And an attribute I representing the type of the attribute.
D, wherein a desired attribute can be accessed by using D as an input. The attribute includes a tag field indicating a type, a length field indicating a length, and a value field indicating a value. AS
N.1 / BER format, stores information on a tree structure (containment tree) composed of the instances, receives the FDN as an input, and stores the position of the instance corresponding to the FDN and the position of the attribute information table A directory storage device that outputs the attribute information, an attribute ID, an offset value to the attribute in the instance, the tag field, and the length field. Is stored in correspondence with the class to which the attribute I belongs.
D and a position of the attribute information table output from the directory storage device, a class information storage device that outputs the offset value, the tag field and the length field, and the instance; The attribute having no tag field and the length field is stored, and the position of the instance output from the directory storage device and the offset value output from the class information storage device are input. A data storage device for outputting the attribute having the value field; a tag field and the length field output from the class information storage device for the attribute having the value field output from the data storage device. And a tagging device for adding a tag to the management information base system. Beam. 4. The directory storage device includes one or a plurality of directory structures representing information of a tree structure (containment tree) constituted by the instances and a directory sub-structure. An instance pointer that holds the position of the instance, and an I that holds the correspondence between the object identifier and the directory substructure.
And a table that receives the object identifier and outputs the position of a directory sub-structure corresponding to the object identifier. The directory sub-structure is a class that holds the position of the attribute information table. A tag, and an RDN attribute value table holding a correspondence relationship between the attribute value and the directory structure. The attribute value is input, and the position of the directory structure corresponding to the attribute value is output. The management information base system according to any one of claims 1 to 3, wherein 5. The data storage device stores an attribute copy area holding the value of a register of the monitoring target device as the attribute as it is, and an access to the attribute held in the attribute copy area occurs. The management information base system according to any one of claims 1 to 4, further comprising a converter for converting the attribute into a predetermined format. 6. A tree structure (containment tree) in which the directory storage device is constituted by the instances using an internal object identifier that guarantees uniqueness only in a system.
6. An identifier converter that expresses the information of the FDN and converts the object identifier included in the FDN into the internal object identifier and inputs the internal object identifier to the directory storage device. The management information base system according to one of the above. 7. The data storage device stores an attribute acquisition function for directly acquiring an attribute from the monitoring target device instead of the attribute, and when the attribute is accessed, executes the attribute acquisition function. 7. The management information base system according to claim 1, wherein the management information base system is activated to acquire an attribute. 8. A cache for storing, as a history, a correspondence between the FDN input to the directory storage device, the position of the instance corresponding to the FDN, and the position of the attribute information table, and Search and replace processing, and the FDN input to the directory storage device.
The management information base system according to any one of claims 1 to 7, further comprising: a cache searcher that previously acquires a position of the object and a position of the attribute information table corresponding to the following. 9. A cache for storing, as a history, a correspondence relationship between a part of the RDN included in the FDN input to the directory storage device from the head and a directory structure corresponding to the part of the RDN, A predetermined search and replacement process is performed on the cache, and the FDN input to the directory storage device is performed.
The management information base system according to any one of claims 1 to 7, further comprising: a cache searcher that previously acquires the directory structure corresponding to a part of the RDN included in the management information base.