JPH0954722A - Managing information base system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a managing information base system(managing information base) especially suitable for an OSI capable of reducing required memory capacity and performing fast access. SOLUTION: A manager 10, when making access attribute, supplies an FDN and an attribute ID to the managing information base. The managing information base acquires first the position of an instance 50 in a data storage device 30 with attribute set as an access target from a supplied FDH by using a directory storage device 20. Moreover, the manager acquires the position of an attribute information table 70 in a class information storage device 100 from a supplied attribute ID. An entry that coincides with the attribute ID is searched by retrieving an acquired attribute information table 70, and attribute 60 including the instance 50 as a member is acquired from an offset value included in the entry and the position of the instance 50.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a management information base system, and more particularly to OSI (Open Systems Interconnec).
and a management information base system for OSI (hereinafter also simply referred to as "management information base") suitable for network management in accordance with the open system interconnection.

[0002]

2. Description of the Related Art A conventional management information base of this type is shown in, for example, "Shimizu et al.," A method of arranging a management information base in ATM transport network management ", IEICE technique CS94-21, 1994". As described above, it is used to realize a logical model of a monitored device of a network in a storage area.

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

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

The manager 10 uses the MIB program 72
The logically defined state of the monitored device 110 can be read or rewritten via 0. Specifically, for the MIB program 720, the manager 10 uses the full distinction 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 monitoring target device 110 to read the status of the monitoring target device 110, and reflects the read status in the database 740.

[0007]

However, since the conventional management information base is generally constructed by using a general-purpose DBMS, it is possible to perform data management suitable for data used in OSI or the like. There is a problem that it is difficult.

Especially, in the management information base constructed by using a general-purpose DBMS, the data storage capacity becomes large,
Further, 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.

Further, the management information base constructed by using a general-purpose DBMS has a problem that the execution speed becomes slow because it has a function that is not necessarily required in the management information base such as OSI.

Therefore, the present invention has been made in view of the above problems, and is management information particularly suitable for network management according to OSI, which can reduce storage capacity and achieve high-speed processing. It is intended to provide a base.

[0011]

In order to achieve the above object, the present invention manages an attribute representing the state of a device to be monitored in a network and an instance including the attribute as a member, and manages an object identifier and an attribute value. One or more relative distinction names ("RD
In the management information base system in which a desired attribute can be accessed by inputting a full distinction name (referred to as “N”) (referred to as “FDN”) and an attribute ID indicating the type of the attribute, A directory storage device that stores information of a tree structure (containment tree) configured by, and outputs the position of the instance corresponding to the FDN and the position of the attribute information table, the attribute ID, An attribute information table holding a correspondence relationship between offset values to the attributes in the instance is stored in association with a class to which the instance belongs, and the attribute ID and the attribute output from the directory storage device are stored. A class information storage device which outputs the offset value by inputting the position of the information table; A data storage device that stores the attribute and 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. There is provided a management information base system characterized by including.

According to the present invention, the storage area of the management information base system is composed of three directories, a data storage device and a class information storage device, and in particular, information required by OSI is managed sufficiently and without redundancy. As a result, various formats can be stored simultaneously depending on the data, and the data can be handled in a unified manner.

The present invention also provides ASN.1 / BER (Abst
Among the attributes stored in aract Syntax Notation 1 / BasicEncoding Rule) format, the tag field and further the length field are grouped for each class to reduce the required storage capacity.

Furthermore, the present invention saves time for conversion by copying the state of the monitored device to the storage area as it is without converting it into a predetermined format, and is generally realized by the monitored device. The existing data format has a smaller data size than the ASN.1 / BER format, so that the required storage capacity is suppressed.

Furthermore, according to the present invention, a method for collecting data is arranged for some of the attributes as in the case of normal attributes, and data is collected from the monitored device only when an access request to the attribute occurs. As a result, the attributes in the storage area and the data only in the monitoring target device are accessed in a unified manner.

[0016]

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described 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 a 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 including the.

The data storage device 30 has an instance 50.
And the attribute 60, and the instances and attributes managed by the management information base according to the present embodiment are stored. 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 the attribute information tables managed by the management information base according to the present embodiment, including the attribute information table 70. There is one attribute information table for each class to which the instance managed by the management information base according to this embodiment belongs.

The attribute information table records the correspondence between the attribute ID and the offset value to the pointer pointing to the attribute designated by the attribute ID (the distance from the beginning of the instance to the pointer pointing to the attribute). 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 giving 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 monitored device 110 is a device on the network monitored and managed by the management information base according to this embodiment. The management information base according to the present embodiment changes the instance and attribute values stored in the data storage device 30 based on the state of the monitored device 110, and conversely stores the data in the data storage device 30 according to the request from the manager 10. The attribute value is reflected in the monitoring target device 110.

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

An outline of the operation of the management information base according to this embodiment will be described with reference to FIGS. 1 and 2.

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

When the management information base according to the present embodiment receives the FDN and the attribute ID from the manager 10 (step 1010), the given FDN is input to the directory storage device 20 and stored in the class information storage device 100. The corresponding position in the attribute information table 70 (“address”
(Also called) (step 1020).

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

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

The offset value obtained in step 1030 is added to the address of the instance 50 obtained in step 1040 to obtain a pointer to the attribute 60 stored in the location indicated by the resulting address (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 the configuration of the management information base directory storage device 20 according to the first embodiment of the present invention in more detail.

Referring to FIG. 3, the directory storage device 2
0 is a plurality of directory structures including the directory structures 240 and 260, and the directory substructure 2
A plurality of directory substructures including 50 are stored, 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 Position of
Is output.

Here, the directory structure and the directory substructure are combined to form a tree structure (“inclusion tree”).
Or "named tree"). The directory structure 240 at the top of the tree structure is also called a root directory structure.

Taking the directory structure 240 as an example, the directory structure has an instance pointer 242 which is a pointer to an instance, and an ID table 246 showing the correspondence between the object identifier and the directory substructure.
And When an object identifier is given to the directory structure, the ID table is searched and the corresponding directory substructure is output. You can also get an instance that corresponds to a directory structure.

Taking the directory substructure 250 as an example, the directory substructure is an RDN attribute value indicating the correspondence between the class tag 253, which is a pointer to the attribute information table 70, and the attribute value and the directory structure. The table 257 is composed. When an attribute value is given to the directory substructure, 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"). The RDN is composed of a pair of an object identifier and an attribute value.

FIG. 4 is a flow chart 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 the present embodiment will be described with reference to FIGS. 3 and 4.

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

Then, it is checked whether or not the list of RDNs forming the FDN is empty (step 1125). If it is not empty (in the case of "No" in step 1125), the process proceeds to step 1130.

The directory storage device 20 takes out the RDN at the head of the FDN, gives the object identifier of the RDN to the directory structure which is the current directory, and obtains the matching directory substructure (step 1130). In addition, the RD
The attribute value of N is given and the 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
A new FDN is obtained by removing the leading RDN from the above, and the process returns to the determination in step 1125 (step 116).
0).

While the FDN list is not empty (“No” in step 1125), the processes of steps 1130 to 1160 are repeated until the FDN list is empty (“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, the attribute information table is obtained based on the class tag of the directory substructure that has just pointed to 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 more detail using a specific example.

As an example, the FDN given from the manager 10 to the management information base according to this embodiment is {{12.
3.1.2-12}}. In the FDN notation, the inside “{}” inside represents the RDN,
The former inside the RDN represents an object identifier, and the latter represents an attribute value. The FDN of this example includes only one RDN, but normally includes a plurality of RDNs.

First, when {{12.3.1.2-12}} is received as 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.
Then, the process proceeds to step 1130.

The object identifier "12.3.1.2" is extracted from the RDN at the head of the FDN. The object identifier is provided to the directory structure 240 to obtain a matching directory substructure 250 (step 1130).

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

After the process of step 1160 is completed, the process returns to step 1125 and it is determined whether the FDN is empty.
Here, since the FDN is empty, step 112
In step 5, it is determined to be “Yes” and the process proceeds to step 1170.
Then, the position of the instance 50 corresponding to the directory structure 260 which is the current directory is obtained (step 1170). Also, 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-based class information storage device 100 according to the first embodiment of the present invention in more 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 for the corresponding attribute is output. The attributes held by the data storage device 30 are described in the ASN.1 / BER format, and are composed of 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 flow chart for explaining the operation of the management information base class information storage device 100 according to the first embodiment of the present invention.

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

When the FDN and the attribute ID are received from the manager 10 (step 1201), the FDN is given to the directory storage device 20, and the position of the attribute information table 70 corresponding to the class to which the instance designated by the FDN belongs is determined. It is obtained (step 1202).

After that, 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 the attribute ID to the attribute information table indicated by the position of the attribute information table and obtains the 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. The position of the pointer to the attribute is obtained by.
The position of the attribute is obtained by obtaining the pointer (step 1206).

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

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

First, the same procedure as that of the above-described concrete example (see FIG. 4).
(See steps 1110 to 1180), the position of the instance 50 and the position of the attribute information table 70 are obtained (steps 1201, 1202, and 1205).

The class information storage device 100 has the attribute information table 7
When the attribute ID is given to 0, the attribute ID is obtained from the attribute information table 70.
The entry with "12.1.2" is searched. In this example,
The value held by the retrieved 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 pointed to 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 the configuration of the management information base according to the 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 untagged data storage device 350, a tag field-added class information storage device 360, a tag adder 322, Equipped with.

In the management information base according to this 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.
Has been replaced by 0. In the attribute information table with tag field 370, when the attribute ID is given, the offset value and the tag field that the attribute should have are output.

In the management information base according to this embodiment, firstly, instead of the class information storage device 100, a class information storage device 360 with a tag field is newly used.
The class information storage device with tag field 360 stores the attribute information table with tag field instead of the attribute information table. When the position of the attribute information table with tag field and the attribute ID 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,
The untagged data storage device 350 is used. In the untagged data storage device 350, the tag field is deleted from the length field and the value field in addition to the attribute that the data storage device 30 holds, which is composed of the tag field, the length field, and the value field. Be sure to retain the configured attributes as well.

Thirdly, the tag adder 320 is connected to the untagged data storage device 350 and the class information storage device 360 with a tag field. When the attribute value and the tag field are input to the tag adder 320, the attributes in which the tag / length / value fields are complete are output.

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

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

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

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

In step 1240, the position of the instance 310 obtained by performing the same processing as step 1204 shown in FIG. 6, the tag field and offset value obtained in step 1230 are stored in the untagged data storage device 350. Give (step 1250). Then, the untagged data storage device 350 uses the step 1 shown in FIG.
The same process as 206 is performed to obtain the position of the attribute from each value given in step 1250 (step 1260),
The determined attribute and the tag field obtained in step 1230 are given to the tag adder 320 (step 127).
0).

Thereafter, it is judged whether or not the given tag field is empty (step 1280), and if it is empty (in the case of "Yes" in step 1280), the processing is terminated and the given attribute is left as it is. It is the final attribute. On the other hand, when the attribute is not empty (“No” in step 1280), the given attribute is composed of only the length field and the value field, and thus the tag field is combined with the given attribute to make the final attribute. Attribute value (step 12)
90).

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

First, a first specific example will be described.

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

The untagged data storage device 350 obtains the attribute 310 using the position of the instance and the offset value (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 and the value field 330 of the attribute 310, and ASN.1
/ BER format attribute (steps 1270, 1280, and 1290).

Next, a second concrete example will be described.

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

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

Although the attribute 390 and the tag field are given to the tag adder 320 (step 1270), since the tag field is empty in this example, the attribute 390 is output as the final attribute ("Yes" in step 1280). If).

If the tag field is empty, the corresponding attribute is ASN.1 CHOICE type, ANY.
The type is not determined in advance like the type, but in such a case, the attribute 390 has all the tag field, length field, and value field, and thus the attribute 390 is left as it is. Output as the final attribute.

Since the management information base according to the first embodiment has a structure in which each of the attributes has a tag field, the storage capacity is increased. But,
Since the attributes of the instances derived from the common class have the same type, even multiple attributes have the same tag field. In the management information base according to this embodiment, attention is paid to the fact that the attributes pointed to by the same entry in the same attribute information table often have the same tag field even if the instances are different. Adopt a configuration in which the tag field is deleted from the user. As a result, the storage capacity required in the management information base according to this embodiment can be reduced.

[0089]

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

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

Referring to FIGS. 7 and 9, comparing the management information base according to the present embodiment with the management information base according to the second embodiment, attribute information in the management information base according to the present embodiment is compared. A column for the length field is further added to the table 370 and is newly replaced by the attribute information table 375 with tag / length field. The attribute information table with tag / length field outputs an offset value, a tag field, and a length field when an attribute ID is given.

Specifically, first, a class information storage device 365 with a tag / length field is newly used instead of the class information storage device 360 with a tag field.
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.

Secondly, 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 only of the value field. That is, when the tag / length field-less data storage device 355 is provided and various attributes such as normal attributes, attributes without tag fields, attributes without tag fields and length fields are stored, and instances and offset values are given. , Output the corresponding attributes.

Third, a tag / length adder 325 is provided instead of the tag adder 322. The tag / length adder 325 includes the attributes output from the tag / lengthless data storage device 355 and the class information storage device 36 with a tag / length.
The tag field and length field output from 5,
Input as and output the attributes with the tag, length, and value fields.

As described above, according to the management information base according to the present embodiment, if the data has a statically fixed length, as compared with the management information base according to the second embodiment, Further reduction in the required storage capacity can be realized by the length field.

[0096]

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

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

Attribute copy area 5 in the data storage device 30
As for parts other than 10, as in the first embodiment, the AS
Stores attributes in N.1 / BER format. Attribute copy area 5
The attribute in 10 is stored as the register value representing the state of the monitoring target device 110 without being converted into the ASN.1 / BER format.

FIG. 11 is a flow chart for explaining the operation of the management information base according to the fourth embodiment of the present invention. FIG. 11A is a flowchart for copying the status of the monitored device 110 to the attribute copy area 510 on a regular basis, and FIG. 11B is a flowchart for accessing the attribute in accordance with the request from the manager 10.

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

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

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

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

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

Generally, since the storage area required for the data realized by the register of the monitored device 110 is smaller than that for the ASN.1 / BER format data, the management database according to the present embodiment is more efficient. It can be realized with a small storage area.

In addition, normally, in order to reflect the status of the monitored device 110 in the attribute in the data storage device 30, a periodical copy operation is performed and data conversion in ASN.1 / BER format is also performed. In the form, the attribute copy area 510 from the manager 10 is not converted to the ASN.1 / BER format unless it is accessed from the manager 10.
The processing speed can be improved when there are few accesses to the attributes.

The present 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 the configuration of the management information base according to the fifth embodiment of the present invention.

Referring to FIG. 12, the management information base according to this 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 the object identifiers used in the system. Since the internal object identifier only needs to guarantee uniqueness within the system, it is smaller than the object identifier that guarantees uniqueness in the whole world, and its structure is simple.

Internal identifier directory structure 420, 4
Object identifiers in the ID table included in 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 this embodiment is called an internal ID table. Note that the internal ID table outputs a corresponding (internal identifier) directory substructure when an internal object identifier is given.

The FD given by the manager 10
The object identifier in N or the attribute ID is 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 flow chart 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 this embodiment will be described with reference to FIGS. 12 and 13.

First, the manager 10 sends the FDN and the attribute I
Upon receiving D and (step 1310), the identifier converter 410 converts all the 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, for example, by the same processing as steps 1110 to 1180 shown in FIG. 4 of the first embodiment.

According to the management information base of this 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 calculation between the internal object identifiers can be performed at a higher speed than the comparison calculation between the object identifiers, the processing speed can be improved.

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

[0119]

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

Referring to FIG. 14, the management information-based data storage device according to the present embodiment is replaced with the attributes stored in the management information-based data storage device 30 according to the first embodiment, for example. , Part of it is attribute acquisition function 6
The attribute acquisition functions including 40 are stored.

If the attribute designated by the instance address and offset value input from the directory storage device 20 is the 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 flow chart 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. 14 and 15.

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

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

On the other hand, if the destination pointed to by the pointer has a normal attribute ("No" in step 1515), the destination 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 the status change in the monitored device 110 is drastic,
Moreover, the attribute acquisition function is used for an attribute for which it is important to maintain the consistency between the state of the monitored device 110 and the corresponding attribute in the data storage device 30, and the latest attribute is obtained when necessary. can do.

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

The present 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 similarly applied. It can also be applied together with the embodiment.

[0130]

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

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

The cache 910 records a part of three correspondences between the FDN, the instance position, and the attribute information table position. 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 searcher 900 is the manager 10
When the FDN is given from the cache searcher 90,
0 searches the cache 910 for an entry that matches the given FDN. When 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 in the cache 910 that matches the given FDN, it gives the FDN to the directory storage device 20, for example, as shown in FIG. 2 of the first embodiment. The location of the instance and the location of the attribute information table are searched for using the directory storage device 20 in accordance with the processing described above. Then, the position of the instance and the position of the attribute information table obtained as a result are made one entry in correspondence with the given FDN and replaced with the entry already stored in the cache 910.

FIG. 17 is a flow chart 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 this embodiment will be described with reference to FIGS. 16 and 17.

First, when the cache searcher 900 receives an FDN from the manager 10 (step 1910),
The cache searcher 900 searches the cache 910,
Find an entry that matches the given FDN (step 1920).

When an entry that matches the given FDN is found (in the case of "Yes" in step 1925), the position of the instance held by the entry and the position of the attribute information table are used, for example, the above-mentioned Steps 1030, 1050, and 106 shown in FIG. 2 for one embodiment.
The attribute is accessed according to the processing of 0 (step 196).
0).

On the other hand, if no entry matching the given FDN can be found ("N" in step 1925).
In the case of “o”), the FDN is stored in the directory storage device 20.
, For example steps 1020 and 10 shown in FIG.
According to the processing of 40, the position of the instance and the position of the attribute information table are obtained (step 1930).

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

With reference to FIGS. 16 and 17, the operation of the management information base according to this embodiment will be described in more 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}} is received (step 1910). In this case, as a result of the cache searcher 900 searching the cache 910 (step 1920), an entry matching the given FDN is searched for (“Yes” 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}} is received (step 1910). As shown in FIG.
It is assumed that the FDN of this example is not stored in the cache 910, and even if the cache search unit 900 searches the cache 910, a matching entry cannot be found. In this case (“No” in step 1925), the cache searcher 900 stores the FD in the directory storage device 20.
N is given and the attribute is accessed 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 by the directory storage device 20 are replaced with any 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 is not performed through the directory storage device over time, but a part of the FDN is used. Is temporarily stored in the cache, and the FDN stored in this cache can be directly converted without using the directory device, so that the processing speed can be increased.

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

[0146]

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

Referring to FIG. 18, the management information base according to the present embodiment includes a part of the FDN and the position of the directory structure instead of the management information base cache 910 according to the seventh embodiment. A new cache 950 that holds the correspondence relationship is provided.

FIG. 19 is a flow chart 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. 18 and 19.

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

When a partially matching entry is found from the beginning of the given FDN (in the case of "Yes" in step 2065), the directory obtained from the position of the directory structure held by the entry. The structure is used as a root directory structure, a part other than the part where the FDN matches 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, the step 103 shown in FIG. 2 of the first embodiment.
The attribute is accessed according to the processing of 0, 1050, and 1060 (step 2110).

On the other hand, if no matching entry can be found from the beginning of the given FDN (if No in step 2065), the FDN is given to the directory storage device 20, 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). A part of the head of the FDN and the corresponding directory structure are replaced with one entry in the cache 950 using the cache searcher 900 (step 2090).

With reference to FIGS. 18 and 19, the operation of the management information base according to this embodiment will be described in more detail using a specific example.

As an example, the cache searcher 900 receives from the manager 10 {{12.3.1.2-12}, {12.3.1-9].
It is assumed that the FDN including 1} and {12.1.2-1}} is received (step 2050). The cache searcher 900 searches the cache 910 (step 2060), and a part of the beginning of the given FDN {{12.3.1.2-12}, {12.3.1].
It is assumed that an entry matching -91}} is found (in the case of "Yes" in step 2065). In this case, the 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 is stored in the directory storage device 20 {{12.1.2-1}. } And the position of the instance and the position of the attribute information table are obtained using the directory storage device 20 (step 2100). Finally, the attributes are accessed (step 2110).

According to the management information base according to the present embodiment, as compared with the seventh embodiment, it is sufficient that the RDNs included in the FDN coincide with each other in the middle, so that the hit rate in the cache is further improved. be able to.

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

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

For example, the management information base of the present invention is an OS
It is particularly suitable as a management information base for networks according to I.I. SNMP (Simple Network Management Protocol) that manages data in 1 / BER format
It can also be used as a management information base of a type network, and can also 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, the storage area is classified into three types, that is, the directory storage device, the data storage device, and the class information storage device, and the management information base is required. Since the information is divided into three types of independent information, detailed information management according to the attribute can be realized.

Further, 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 tag field can be omitted to reduce the required storage capacity.

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

In the management information base system of the present invention, it is necessary to store some attributes in the data storage device as they are, not in the ASN.1 / BER format but in the form of the register representing the state of the monitored device. It is possible to reduce the required storage capacity, and further, it is possible to reduce the cost required for converting the attribute format when the access frequency to the attribute is low.

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

Further, in the management information base system of the present invention, by disposing the attribute acquisition function at the end of the pointer pointing to the attribute instead of the attribute, it is possible to effectively cope with the attribute that changes drastically. It is possible to handle the case of accessing a normal attribute and the case of accessing an attribute through an attribute acquisition function in a unified manner.

[Brief description of drawings]

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

FIG. 2 is a flowchart for explaining the operation of the 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 illustrating an operation of the management information base directory storage device 20 according to the first exemplary embodiment of the present invention.

FIG. 5 is a block diagram illustrating 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 illustrating an operation of the management information base class information storage device 100 according to the first embodiment of the present invention.

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

FIG. 8 is a flowchart illustrating an operation of a management information base according to the second exemplary 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 the fourth exemplary embodiment of the present invention.

FIG. 12 is a block diagram for explaining 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 the fifth exemplary 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 the sixth exemplary 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 exemplary 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 exemplary embodiment of the present invention.

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

[Explanation of symbols]

10 Manager 20 Directory Storage Device 30 Data Storage Device 50 Instances 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 Untagged data storage device 355 Tag / length Data storage device without field 360 class information storage device with tag field 365 tag / class information storage device with length field 370, 380 tag file Attribute information table with field 375 Attribute information table with tag field / length field 385 Instance 390 Attribute 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 Attribute in 540 Converter 550 Instance 640 Attribute acquisition function 720 MIB program 730 Database management system (DBMS) 740 Database 900 Cache searcher 910, 950 cache

Claims (9)

[Claims] 1. One or a plurality of relative distinction names (“RDN”) that manages an attribute indicating the state of a monitored device of a network and an instance including the attribute as a member and have an object identifier and an attribute value. A full distinction name (referred to as "FDN") and an attribute I indicating the type of the attribute.
In a management information base system that allows access to desired attributes by inputting D and D, information of a tree structure (containment tree) configured by the instances is stored, and the FDN is input and corresponding to the FDN. The directory storage device that outputs the position of the instance and the position of the attribute information table, the attribute information table that holds the correspondence relationship between the attribute ID and the offset value to the attribute in the instance belongs to the instance. A class information storage device that stores in correspondence with a class and outputs the offset value by inputting the attribute ID and the position of the attribute information table output from the directory storage device, the instance and the attribute And the location of the instance output from the directory storage device and the class information class. 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. One or more relative distinction names (“RDN”) that manage an attribute representing the state of a monitored device in a network and an instance including the attribute as a member and have an object identifier and an attribute value. A full distinction name (referred to as "FDN") and an attribute I indicating the type of the attribute.
In a management information base system that enables access to a desired attribute by inputting D and D, the attribute includes a tag field indicating a type, a length field indicating a length, and a value field indicating a value. AS
It is expressed in N.1 / BER format, stores information of a tree structure (container tree) formed by the instances, inputs the FDN, and the position of the instance corresponding to the FDN and the position of the attribute information table. A directory storage device which outputs the attribute ID, an attribute ID, an offset value to the attribute in the instance, and a tag field, which are associated with an attribute information table that corresponds to a class to which the instance belongs. A class information storage device that stores the attribute value and the position of the attribute information table output from the directory storage device as input, and outputs the offset value and the tag field; The attribute that does not have the tag field and the instance that is output from the directory storage device. , And a data storage device that outputs the attribute having the length field and the value field, and the offset value output from the class information storage device as an input, and the data storage device outputs the attribute. A management information base system, comprising: 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. One or a plurality of relative distinction names (“RDN”) that manages an attribute indicating the state of a monitored device of a network and an instance including the attribute as a member and have an object identifier and an attribute value. A full distinction name (referred to as "FDN") and an attribute I indicating the type of the attribute.
In a management information base system that enables access to a desired attribute by inputting D and D, the attribute includes a tag field indicating a type, a length field indicating a length, and a value field indicating a value. AS
It is expressed in N.1 / BER format, stores information of a tree structure (container tree) formed by the instances, inputs the FDN, and the position of the instance corresponding to the FDN and the position of the attribute information table. A directory storage device for outputting the attribute information table, the attribute ID, an offset value for the attribute in the instance, the tag field, and the length field. Corresponding to the class to which the
A class information storage device that outputs the offset value, the tag field, and the length field by inputting D and the position of the attribute information table output from the directory storage device, the instance, and The attribute without the 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, and the 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. Management information base system characterized by including a tag adder for adding Beam. 4. The directory storage device includes one or more directory structures that represent information of a tree structure (inclusive tree) configured by the instances, and a directory substructure, and the directory structure includes: 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
D table, and outputs the position of the directory substructure corresponding to the object identifier with the object identifier as an input, and the directory substructure holds the position of the attribute information table. It is composed of a tag and an RDN attribute value table that holds the correspondence relationship between the attribute value and the directory structure, and inputs the attribute value and outputs the position of the directory structure corresponding to the attribute value. 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 that holds the register value of the monitored 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 that converts the attribute into a predetermined format. 6. A tree structure (inclusion tree) in which the directory storage device is constituted by the instances using an internal object identifier that guarantees uniqueness only in the system.
6. The method according to claim 1, further comprising an identifier converter that expresses the information of the above, converts the object identifier included in the FDN into the internal object identifier, and inputs the internal object identifier into the directory storage device. The management information base system described in 1. 7. The data storage device stores an attribute acquisition function for directly acquiring an attribute from the monitored device instead of the attribute, and stores the attribute acquisition function when an access to the attribute occurs. The management information base system according to any one of claims 1 to 6, wherein the management information base system is activated to acquire an attribute. 8. A cache that stores, as a history, a correspondence relationship 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 a predetermined value for the cache. The FDN that has been searched for and replaced and is 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 acquires in advance the position of the object and the position of the attribute information table corresponding to. 9. A cache that stores, as a history, a correspondence relationship between a part from the beginning of an RDN included in the FDN input to the directory storage device and a directory structure corresponding to the part of the RDN, The FDN is input to the directory storage device by performing a predetermined search and replace process on the cache.
The management information base system according to any one of claims 1 to 7, further comprising: a cache searcher that acquires in advance the directory structure corresponding to a part of the RDN included in.