JP2000215134A - Abstract syntax data storage device and management information base - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an abstract syntax data storage device which uses a memory area with high efficiency and processes values at high speed, and an MIB which is high in the use efficiency of the memory area. SOLUTION: An abstract syntax data conversion means 0102 receives transferring syntax data, discriminates whether the data are to be stored in the device or not, converts the data into the internal data to be used in the device if they need to be stored and further outputs an abstract syntax key which corresponds to the data. An abstract syntax data storage means 0103 stores transfer syntax data which are converted by the abstract syntax data conversion means 0102 into the internal data. An abstract syntax definition storing means 0104 stores a table which contains abstract syntax definitions and an integer values (index) corresponding to the definition as entries. An MO class definition storing means 0803 stores a zero ID given to each class definition for discriminating the MO class and a table which entries an integer values (index) corresponds to the ID and defines what attributes the MO instances which belong to respective MO classes have.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an apparatus for holding abstract syntax data, and more particularly to an international organization (International Organization).
abstract Syntax Notation 1 (Abstract Syntax Notation)
One, hereafter referred to as an abstract syntax data holding device that holds syntax data whose structure is defined by ASN.1).

[0002] The present invention also relates to a management information base (Management Information Base).
ent Information Base (MIB), specifically the Open System Interconnection (Open Sy
It relates to MIB used for managing a network according to stemsInterconnection (hereinafter referred to as OSI).

[0003]

2. Description of the Related Art Conventionally, as described in Japanese Patent Application Laid-Open No. 9-54722, this type of MIB abstracts a physical management target into a logical form when managing a communication network. This is used to realize a general model on a storage area. That is, each physical object to be managed is a managed object class (hereinafter referred to as MO).
Class), and an attribute (Attribute) corresponding to each physical management target is added.

[0004] For example, in the case of an MO class defined by abstracting a printer which is a physical management target, attributes include a printer type (inkjet, laser, etc.), a name, a startup time, the number of prints, and the like.

[0005] For the MO class defined in this way,
The one in which a specific value is assigned to each attribute is called a managed object instance (hereinafter, referred to as an MO instance). In the case of the above-described printer, examples of the MO instance include those having attributes such as “type is ink jet, name is printer 1” and “type is laser, name is printer 2”.

In network management according to OSI (hereinafter referred to as OSI management), not only a single physical management target but also a plurality of physical management targets can be managed. When a plurality of objects are managed, an inclusion relationship occurs between the respective physical management objects. Here, the inclusion relation is a relation that “computer is included in the network” when “the computer is connected to the network”. What expresses this containment relation as a tree structure is called a containment tree.

FIG. 19 shows an example of a simple containment tree. In the example of FIG. 19, the MO instance 5001 belonging to the MO class “network” includes the MO instances 5002 and 5003 belonging to the MO class “computer”, and the MO instance 5002 belongs to the MO class belonging to the MO class “network card”. Includes instance 5004, MO instance 50
03 is an MO belonging to the MO class called "Network Card"
Indicates that it includes the instance 5005 and the MO instance 5006 belonging to the MO class “printer”.

[0008] In FIG. 19, attributes surrounded by a solid frame are Relative Distinguished Names (RDNs).
If the instance "A" is included in the instance "B", the instance "B" can be created under the instance "B" by using the attribute value of the RDN.
A "can be uniquely identified. In the example of FIG.
In the MO instance belonging to the MO class “Network card”, the attribute “Interface name” is RDN
Becomes

[0009] However, the RDN alone is not enough to specify a certain instance in the containing tree.
Because, in the example of FIG. 19, "interface name = Et
The RDN "her0" is the MO instance 5002 in which it is contained
However, since the MO instance 5003 also includes the MO instance having the RDN of “interface name = Ether0”, the MO instance 5003 is not unique in the entire containing tree.

Therefore, in OSI management, the MO
Fully Distinguished Name (Full
Distinguished Name (FDN) is used. FDN is
It is a list of RDNs of all MO instances from the root of the containing tree to the MO instance,
The FDN for identifying the MO instance 5004 in FIG. 19 is "
{{Network name = Network1}, {Computer name = Comput
er1}, {interface name = Ether0}} ".

As described above, in OSI management, the configuration of a physical management target is abstracted and expressed as an MO class. MI
In B, an MO instance in which a specific value is assigned to the MO class is stored. Physically managed properties are expressed as attribute values assigned to MO instances.

Conventionally, this kind of abstract syntax data holding device is used to store attribute values assigned to each MO instance in the above-mentioned MIB. The structure of the attribute value is defined by an abstract syntax as described in JP-A-8-106424, and particularly in the case of OSI management, is defined according to ASN.1 defined by OSI. In addition, when the attribute value is stored in the abstract syntax data holding device, it is encoded according to a rule called a basic encoding rule (hereinafter referred to as BER), and is stored in an encoded state.

The abstract syntax will be briefly described. FIG. 20 shows an example of the abstract syntax. As shown in FIG. 20, in the abstract syntax, an abstract syntax 5101 that defines a structure of an attribute value, a value notation 5102 in which a concrete value is assigned to an attribute whose structure is defined by the abstract syntax 5101, and a value There is a transfer syntax 5103 which is a result of encoding the notation 5102 according to the BER, and the transfer syntax is stored in the abstract syntax data holding device. As shown in the transfer syntax 5103, in the coding according to BER, it is possible to adopt a nested structure in which the value field includes the tag, the length, and the value field again.

An example of a conventional abstract syntax data holding device will be described with reference to the drawings.

FIG. 21 is a block diagram showing a schematic configuration of a conventional abstract syntax data holding device. As shown in FIG. 21, a conventional abstract syntax data holding device 5201 stores an attribute value 5204 encoded in a transfer syntax format according to BER.
Each attribute value is a pointer as an attribute 5203 of the MO instance 5202 existing outside the abstract syntax data holding device 5201.
Referenced and used at 5205.

However, when the abstract syntax data holding device 5201 shown in FIG. 21 is used, it is necessary to make the storage area in the abstract syntax data holding device 5201 correspond to each attribute value of the MO instance. That is, one storage area is always required for one attribute value, and even if a plurality of attributes have the same value, the
01 is stored in a separate storage area. Therefore, the use efficiency of the storage area decreases.

Therefore, in the method described in Japanese Patent Application Laid-Open No. 8-106424, an area for storing common attribute values is provided, and for attribute values that are known to be the same in advance, the common attribute value storage area is referred to. By doing so, the use efficiency of the storage area is improved.

Next, a network management system (Network
Management System (NMS) will be briefly described. FIG. 22 shows a configuration example of an NMS including a MIB. As shown in FIG. 22, the NMS includes a management manager 5301 that is a subject of management and has a function of requesting a management operation, and an NMS that actually accesses the managed device 1003 on behalf of the management manager 5301 and connects to the MIB 5302 connected thereto. A management agent 1002 that has the function of acquiring and updating management information, and a containment tree that abstracts and logically models the characteristics of the managed device 1003
MO class identifier (Identif
ier, hereafter referred to as ID), FDN, attribute ID, and scope / filter specification, etc., search the containment tree 5303, access the desired MO instance 5304, and operate the MIB 5302, which has the function of operating the attribute. It is composed of a managed device 1003.

Next, an example of a conventional MIB will be described with reference to the drawings. FIG. 23 is a block diagram showing a schematic configuration of a conventional MIB. As shown in FIG. 23, the conventional MIB 5401 includes a directory storage unit 5402, a data storage unit 5403, and a class information storage unit 5404. The management agent 1002, which has received a request from the management manager 5301, via the MIB 5401 thus configured,
Perform management operations on 03.

The directory storage means 5402 stores in advance the correspondence between the FDN and the MO instance and the correspondence between the FDN and the attribute information table. Therefore, FDN
Thus, the address in the data storage unit 5403 of the MO instance corresponding to the FDN can be obtained, and the address in the class information storage unit 5404 of the attribute information table corresponding to the FDN can be obtained.

The data storage means 5403 stores all the MO instances 5202 to be managed by the MIB 5401 and the abstract syntax data holding device 5201. Abstract syntax data storage device 52
In 01, all attribute values 5204 of all MO instances to be managed by the MIB are stored. The attribute 5203 is an element of any one MO instance, and the MO instance has a pointer 5205 pointing to an attribute value 5204 that is an element.

The class information storage means 5404 stores the attribute information table 54
Stores all attribute information tables that should be managed by MIB, including 09. One attribute information table exists for each MO class to which the MO instance managed by the MIB belongs.

Next, an outline of the operation of the conventional MIB will be described. FIG. 24 is a flowchart showing an outline of the operation of the conventional MIB. When the management agent 1002 accesses the attributes of the MO instance managed by the MIB 5401, the management agent 1002 specifies the MO instance and the attribute to be accessed.
Give FDN and attribute ID.

First, the MIB 5401 is managed by the management agent 100.
The FDN and attribute ID are input from 2 (step 5501). MIB540
1 inputs the given FDN to the directory storage unit 5402 and acquires the address of the attribute information table 5409 stored in the class information storage unit 5404 (step 5502). The obtained address of the attribute information table 5409 and the given attribute ID are input to the class information storage unit 5404, and the offset value from the head of the MO instance to the pointer indicating the attribute is obtained.
(Step 5503).

Then, by inputting the given FDN to the directory storage means 5402, the address of the corresponding MO instance 5202 in the data storage means 5403 is obtained (step 5504). The offset value obtained in step 5503 is added to the address of the MO instance 5202 obtained in step 5504, and a pointer 5205 pointing to the attribute value 5204 stored at the location indicated by the obtained address is obtained (step 5505).

Finally, the attribute 5204 is accessed using the pointer 5205 obtained in step 5505 (step 550).
6).

[0027]

As described above, the conventional abstract syntax data holding device holds each attribute value of the MO instance in the form of a transfer syntax which is a result of encoding according to BER. And has the following problems.

The first problem is that when a conventional abstract syntax data storage device is used, the use efficiency of the storage area is reduced. The reason is that when storing attribute values, one storage area is always required for one attribute value, and even if multiple attributes have the same value, they are stored in separate storage areas. That's because. In OSI management, attributes with different values for each MO instance are rare. Most attributes have the same attribute value even if the MO instance is different. Therefore, when the same attribute value is stored in different storage areas, a large number of redundant areas are generated, and the use efficiency of the storage area is extremely reduced.

In order to solve this problem, Japanese Patent Application Laid-Open No. 8-106424
In the method disclosed in Japanese Patent Application Laid-Open Publication No. H10-207, in the case of an attribute that is known to have the same value in advance, the use efficiency of the storage area is improved by referring to the common attribute value storage area. However, this method is a countermeasure before starting network management, and has the same attribute value in the process of performing network management.
When a large number of MO instances are generated, the use efficiency of the storage area is also lowered.

The second problem is that it is difficult to compare the values of attribute values at high speed. The reason for this is that in the abstract syntax data storage device, the attribute value is the ASN.1 BER
Is stored in the form of a transfer syntax coded according to, so when comparing values, the stored attribute values must be decoded once, returned to value notation, and then compared. It is. In OSI management, the scope filter processing, such as accessing only MO instances with specific attribute values in the containment tree, is performed very frequently. May be reduced.

The conventional MIB has the following problems. When the conventional MIB is used, the use efficiency of the storage area in the data storage means is insufficient. The first reason is that the use efficiency of the storage area is reduced in the above-described abstract syntax data holding device. The second reason is that when storing an MO instance in the data storage means, one storage area is always required for one MO instance, and a plurality of MO instances have exactly the same attribute value, This is because, even when only the attribute values of a set are different and other attribute values are the same, they are stored in different storage areas. In the OSI management, in the case of MO instances belonging to the same MO class, most attribute values are the same for all MO instances, and there are many attributes that have different values for each MO instance. In this case, the use efficiency of the storage area is extremely reduced.

Therefore, an object of the present invention is to provide an abstract syntax data holding device which solves the above-mentioned problems, has a high use efficiency of a storage area, and can process attribute values at high speed. Another object of the present invention is to provide an MIB with a high storage area use efficiency.

[0033]

An abstract syntax data holding device according to the present invention receives encoded transfer syntax data as an input, and determines whether the transfer syntax data is data stored in the abstract syntax data holding device. Whether the transfer syntax data is determined to be necessary or not is converted to internal data used in the abstract syntax data holding device, and the internal data is stored in the abstract syntax data storage means. Later, it has a function of outputting an address of the internal data in the abstract syntax data storage means as an abstract syntax key corresponding to the transfer syntax data. Abstract syntax data conversion means having a function of outputting an abstract syntax key to be converted, and the abstract syntax data conversion means determines that storage is necessary. Abstract syntax data storage means having a function of storing transfer syntax data converted into internal data, and an abstract syntax having a function of storing a table having an abstract syntax definition and an integer value (index) corresponding thereto as an entry. And a definition storage means.

Further, in addition to the three means, the abstract syntax data holding device of the present invention further comprises an object identifier (Objec) assigned to each class definition for identifying the MO class.
t Identifier, hereinafter referred to as OID) and a table with entries of integer values (indexes) for the OIDs as entries, and a function of storing an MO class definition that defines what attributes MO instances belonging to each MO class have. MO class definition storage means may be included therein.

Also, the MIB of the present invention uses the above-mentioned abstract syntax data holding device, receives transfer syntax data as input, determines whether or not the input data needs to be stored therein, Then, after storing, an abstract syntax data holding device having a function of outputting an abstract syntax key corresponding to an input transfer syntax, and a MO having a function of storing individual MO instance nodes constituting a containment tree It consists of instance storage means.

The abstract syntax data holding device according to the present invention determines whether or not the abstract syntax data needs to be stored before storing the abstract syntax data in the device. By storing only certain data, it is possible to reduce the storage area necessary to hold the abstract syntax data.

Furthermore, in the case of abstract syntax data that needs to be stored, it is converted into internal data, and an abstract syntax key is used to refer to the abstract syntax data from outside. The abstract syntax key has a feature that "when there are a plurality of abstract syntax data having the same value, there is only one abstract syntax key corresponding to the plurality of abstract syntax data". That is, a one-to-one correspondence is established between the abstract syntax key and the value of the abstract syntax data. Therefore, when storing a plurality of abstract syntax data having the same value, the internal data is stored only in one place in the device, and the external syntax is referred to using the abstract syntax key. It is not necessary to store a plurality of abstract syntax data having the same value in separate storage areas as in the abstract syntax data holding device, and the storage area can be reduced.

In addition, by using the feature of the abstract syntax key, it is possible to compare at a very high speed whether or not the values of a plurality of abstract syntax data are the same.

Further, the MIB of the present invention includes the above-mentioned abstract syntax data holding device therein, and generates a reference MO instance which is a MO instance having a standard attribute value for the MO instance belonging to each MO class, When storing the MO instance belonging to the MO class, the attribute value stored in the reference MO instance is referred to.

Further, when the MO instance has an attribute having a value different from the attribute value stored in the reference MO instance, only the attribute value corresponding to the attribute value having the different value is stored in another area. . Therefore, the storage area required for storing the MO instance can be reduced.

[0041]

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

FIG. 1 is a block diagram showing a schematic configuration of an abstract syntax data holding device according to an embodiment of the present invention. As shown in FIG. 1, an abstract syntax data holding device 0101 according to the present embodiment
, An abstract syntax data storage means 0103, and an abstract syntax definition storage means 0104.

The abstract syntax data conversion means 0102 uses the ASN.1 B
Receives the transfer syntax data encoded according to the ER as input, determines whether the input transfer syntax data is data stored in 0103 in the abstract syntax data storage means, and if the data does not need to be stored, Has a function of converting the transfer syntax data into an abstract syntax key and outputting the data, and if the transfer syntax data needs to be accumulated, searches the abstract syntax data hash table 0105 to correspond to the transfer syntax data. Upon detecting that the internal data has already been stored in the abstract syntax data storage means 0103,
It has the function of outputting the address of the internal data in the abstract syntax data storage unit 0103 as an abstract syntax key, and detects that the internal data corresponding to the transfer syntax data is not stored in the abstract syntax data storage unit 0103 Then, a function of storing the internal data corresponding to the transfer syntax data in the free space in the abstract syntax data storage means 0103, updating the abstract syntax data hash table 0105, and outputting the address storing the internal data as an abstract syntax key is provided. Have.

In the above-described determination of the necessity of storage, the data that needs to be stored in the abstract syntax data storage means 0103 is a large INTEGER that cannot be expressed in the abstract syntax key.
Type data, long string type data, OID type data,
Structured data. The other data is not stored in the abstract syntax data storage means 0103, but is represented by the abstract syntax key itself. Abstract syntax data storage means 01
03 has a function of storing internal data corresponding to transfer syntax data determined to be required to be stored by the abstract syntax data conversion means 0102.

FIG. 2 is a block diagram for describing in further detail the configuration of the abstract syntax data storage means 0103 included in the abstract syntax data holding device 0101 in the present embodiment.

As shown in FIG. 2, the abstract syntax data storage means 0103 in the present embodiment has an internal data storage table 0201
Is stored. The internal data storage table 0201 is a table having, as an entry, the internal data 0202 corresponding to the transfer syntax data determined to be required to be stored by the abstract syntax data conversion means 0102.

The abstract syntax definition storage means 0104 stores a table composed of abstract syntax definition names and their corresponding integer values (indexes) as entries in order to number and manage the abstract syntax definitions. Has the function of storing the abstract syntax definition itself.

FIG. 3 shows an abstract syntax definition storage means included in the abstract syntax data holding device 0101 in this embodiment.
FIG. 10 is a block diagram for explaining the configuration of 0104 in more detail. As shown in FIG. 3, the abstract syntax definition storage means 0104 in the present embodiment stores an abstract syntax definition-index correspondence table 0301 and an abstract syntax definition group 0302.

Abstract syntax definition-index correspondence table 0301
Is a table for holding the correspondence between the abstract syntax definitions and the indexes for all the abstract syntax definitions handled in the MIB to which the abstract syntax data holding device is applied. The abstract syntax definition name and the corresponding It is a table having a pair with an index as an entry. In the example of FIG. 3, the index “1” corresponds to the abstract syntax definition name “Attribute1”, and the index “2” corresponds to the abstract syntax definition “Attribute2”.

The abstract syntax definition group 0302 is an abstract syntax definition identified by an abstract syntax definition name, and is a syntax definition relating to all abstract syntaxes handled in the MIB to which the abstract syntax data holding device is applied.

Next, the format of each entry of the internal data storage table 0201 stored in the abstract syntax data storage means 0103 will be described.

FIGS. 4 and 5 show the present embodiment.
FIG. 4 is a block diagram for explaining in detail a format of each entry of an internal data storage table 0201 stored in an abstract syntax data storage unit 0103 included in the abstract syntax data holding device 0101.

As shown in FIGS. 4 and 5, there are two types of entries in the internal data storage table 0201: an octet column type entry 0401 and a structure type entry 0501.

The octet sequence type entry 0401 is composed of an abstract syntax index field 0402, an octet length field 0403, a reference count field 0404, and a transfer syntax data field 0405. For octet sequence entries, the abstract syntax index field 0402 is not used, so this field is always "
0 ".

The octet length field 0403 indicates the octet length of the transfer syntax data field 0405. The reference number field 0404 indicates whether the entry has a structure type in the internal data storage table 0201 included in the abstract syntax data storage unit 0103 from outside the abstract syntax data storage device 0101 or in the abstract syntax data storage device 0101. Indicates how many references from the entry.

In the conventional abstract syntax data holding device, a plurality of transfer syntax data having the same value are stored in separate storage areas, whereas in the abstract syntax data holding device according to the present embodiment, the reference data is referred to. By providing a number field, even if there are a plurality of transfer syntax data having the same value, the transfer syntax data is stored in a single storage area, and by controlling the number of times of reference from an external or another entry, the required storage area can be stored. Reduction is possible.

The transfer syntax data field 0405 stores transfer syntax data corresponding to this entry, and its length is the length indicated in the octet length field 0402.

The structure type entry 0501 further has two types, a SET type entry 0502 and a CHOICE type entry 0503. The SET type entry 0502 includes four types of fields: an abstract syntax index field 0504, an element count field 0505, a reference count field 0506, and an element field 0507. Abstract syntax index field 0504
Indicates an index of an abstract syntax that is managed in the abstract syntax definition storage means 0104 and defines the transfer syntax corresponding to this entry. An element number field 0505 indicates how many elements are included in the abstract syntax corresponding to this entry. The reference number field 0506 indicates the structure type in the internal data storage table 0201 included in the abstract syntax data storage unit 0103 included in the abstract syntax data storage device 0101 from the outside of the abstract syntax data storage device 0101. Indicates how many references from the entry. Element field
The number 0507 is the same as the number indicated by the element number field 0505, and stores an abstract syntax key indicating the element.

The abstract syntax data stored as a SET type entry includes a SEQUENCE type, a SET type, a SEQUENCE OF type, and a SET type.
There is OF type data.

The CHOICE type entry 0503 includes an abstract syntax index field 0508, an element position field 0509,
It comprises four types of fields, a reference number field 0510 and an element field 0511. The abstract syntax index field 0508 indicates an index of an abstract syntax that is managed in the abstract syntax definition storage unit 0104 and defines the transfer syntax corresponding to this entry. The element position field 0509 indicates which element of the abstract syntax corresponding to this entry is stored in the element field 0511. The number-of-references field 0510 indicates the structure type in the internal data storage table 0201 included in the abstract syntax data storage unit 0103 included in the abstract syntax data storage device 0101 from the outside of the abstract syntax data storage device 0101. Indicates how many references from the entry. Element field 0511 is just
There is one, and an abstract syntax key indicating the element indicated by the element position field 0509 is stored in the abstract syntax definition.

The abstract syntax data stored as a CHOICE type entry includes CHOICE type and ANY type data. However, when storing ANY type data, the contents of element position field 0509 in CHOICE type entry 0503 must be "
1 ".

Next, how the abstract syntax data holding device 0101 operates in the present embodiment will be described.

First, an operation when transfer syntax data that is not structured type data is received will be described. FIG. 6 is a flowchart for explaining the operation of abstract syntax data holding apparatus 0101 when transfer syntax data that is not structured data is received in the present embodiment. Using FIGS. 1 and 6,
In the present embodiment, an outline of the operation of the abstract syntax data holding device 0101 when transfer syntax data that is not structured data is received will be described.

First, the transfer syntax data is input to the abstract syntax data holding device 0101 (step 0601). Next, the abstract syntax data conversion unit 0102 determines whether or not the input transfer syntax data needs to be stored in the abstract syntax data storage unit 0103 (step 0602). As a result of the determination, if the data does not need to be stored, the abstract syntax data conversion means
0102 converts the input transfer syntax data into an abstract syntax key and outputs it (step 0603).

On the other hand, if the result of the determination is that the data needs to be stored, the abstract syntax data conversion means 0102 searches the abstract syntax data hash table 0105 and finds that the entry corresponding to the input transfer syntax data is an abstract syntax data. Data storage means 01
It is determined whether or not it exists within 03 (step 0604 and step 0605).

As a result of the determination, if there is an entry corresponding to the input transfer syntax data, "1" is added to the reference number field of the entry. Thereafter, the address of the entry in the abstract syntax data storage means 0103 is output as an abstract syntax key (step 0606 and step 0606).
607).

If the result of determination in step 0605 is that there is no entry corresponding to the input transfer syntax data, an entry corresponding to the input transfer syntax data is newly created. Here, the value of the reference count field of the newly created entry is “1” (step 0608).

Next, the created entry is stored in a free area in the abstract syntax data storage means 0103 (step 0609), and the contents of the abstract syntax data hash table 0105 are updated.
(Step 0610) Finally, the address of the entry stored in Step 0609 is output as an abstract syntax key
(Step 0611).

Next, an operation when transfer syntax data which is structured type data is received will be described. FIG. 7 is a flowchart illustrating the operation of abstract syntax data holding device 0101 when transfer syntax data that is structured data is received in the present embodiment. With reference to FIG. 1 and FIG. 7, an outline of the operation of the abstract syntax data holding device 0101 when transfer syntax data that is structured data is received in the present embodiment will be described.

First, the transfer syntax data is input to the abstract syntax data holding device 0101 (step 0701), and the abstract syntax conversion means 0102 searches the abstract syntax data hash table 0105 and finds an entry corresponding to the input transfer syntax data. Is determined in the abstract syntax data storage means 0103 (step 0702 and step 0703).

As a result of the determination, if there is an entry corresponding to the input transfer syntax data, "1" is added to the reference number field of the entry. Thereafter, the address of the entry in the abstract syntax data storage unit 0103 is output as an abstract syntax key (step 0704 and step 0704).
705).

On the other hand, if the result of the determination is that there is no entry corresponding to the input transfer syntax data, the abstract syntax conversion means 0102 searches the abstract syntax definition storage means 0104 and finds an entry corresponding to the input transfer syntax data. An index assigned to the abstract syntax definition to be obtained is obtained (step 0706).

The abstract syntax conversion means 0102 newly creates an entry corresponding to the input transfer syntax data, and sets the index acquired in step 0706 in the abstract syntax index field. Here, the value of the reference count field of the newly created entry is "1" (step 070).
7).

Next, the abstract syntax conversion means 0102 determines whether or not processing of all elements of the abstract syntax corresponding to the index indicated in the abstract syntax index field has been completed (step 0708). If all elements have been processed as a result of the determination, the created entry is stored in the abstract syntax data storage means 0103 (step 0709), and the contents of the abstract syntax data hash table 0105 are updated (step 0710).
Finally, the address of the entry stored in step 0709 is output as an abstract syntax key (step 0711).

On the other hand, as a result of the determination in step 0708,
If the processing of all elements has not been completed, it is determined whether or not the element to be processed next is a structural element (step 0712). As a result of the determination, if the element to be processed next is the structural type, the flow is recursively executed (step 0713).

On the other hand, if the result of the determination is that the element to be processed next is not of the structured type, the processing flow of transfer syntax data not of the structured type shown in FIG.

The abstract syntax key output in step 0713 or 0714 is set as the content of the element field corresponding to the element being processed (step 0715). afterwards,
Returning to step 0708, the processing is continued.

Next, an abstract syntax data holding device according to a second embodiment of the present invention will be described. Fig. 8
FIG. 7 is a block diagram illustrating a schematic configuration of an abstract syntax data holding device according to a second embodiment of the present invention. As shown in FIG. 8, the abstract syntax data holding device 0801 according to the second embodiment includes an abstract syntax data conversion unit 0802, an abstract syntax data storage unit 0103, and an abstract syntax definition storage unit 01.
04 and MO class definition storage means 0803.

The abstract syntax data conversion means 0802 according to the first embodiment of the present invention
As described above, transfer syntax data encoded according to the BER of ASN.1 is received as input, and it is determined whether or not the input transfer syntax data is data to be stored in the abstract syntax data storage unit 0103, and stored. If the data does not need to be transferred, it has a first function of converting the transfer syntax data into an abstract syntax key and outputting it. If the transfer syntax data needs to be stored, the abstract syntax data hash table 0105 is searched, and the internal data corresponding to the transfer syntax data is already stored in the abstract syntax data storage unit 0103. Is detected, the abstract syntax data storage means 01
It has a second function of outputting the address of the internal data in 03 as an abstract syntax key. Further, the internal data corresponding to the transfer syntax data is stored in the abstract syntax data storage means 0103.
When it is detected that the transfer syntax data is not stored in the abstract syntax data storage means 0103, the internal data corresponding to the transfer syntax data is stored in the free space, and the abstract syntax data hash table 0105 is stored.
And a third function of updating an address of the internal data as an abstract syntax key.

The MO class definition storage means 0803 stores an OID assigned to each class definition for identifying the MO class and an integer value (index) corresponding to the OID in order to perform management by numbering the MO class. It has a function of storing a table configured as an entry and storing an MO class definition itself that defines what attributes the MO instances belonging to each MO class have.

FIG. 9 is a block diagram for explaining in further detail the configuration of the MO class definition storage means 0803 included in the abstract syntax data holding device 0801 in the second embodiment. As shown in FIG. 9, the MO class definition storage means 0803 in the second embodiment stores an OID-index correspondence table 0901 and an MO class definition group 0902.

The OID-index correspondence table 0901 shows OIDs assigned to all MO class definitions handled in the MIB to which the abstract syntax data holding device is applied.
This is a table for holding the correspondence between the OID and the index corresponding thereto, and is a table having a pair of the OID and the corresponding index as an entry. In the example of FIG. 9, the index “1” corresponds to OID “1.2.513.9.12”, and the index “2” corresponds to OID “1.2.513.9.13”.

The MO class definition group 0902 indicates what attributes each MO class identified by the OID is actually defined as having. Referring to the example in FIG. 9, the MO class to which OID "1.2.513.9.12" is assigned has attributes identified by OID "1.2.120.1.22", OID "1.2.120.2.33",. And the structure of each attribute is defined by the abstract syntax "Attribute1", the abstract syntax "Attribute2", and so on.

The difference between the abstract syntax data conversion means 0802 in the second embodiment and the abstract syntax data conversion means 0102 in the first embodiment lies in the handling of OID type data. In the abstract syntax data conversion means 0102 in the first embodiment, the OID type data is converted into an octet string type entry, and the abstract syntax data storage means 0103
Stored inside. On the other hand, in the abstract syntax data conversion unit 0802 in the second embodiment, the OID type data is searched in the MO class definition storage unit 0803, and the input OI
The index value corresponding to the D data is used as an abstract syntax key, and no accumulation is required.

Therefore, when compared with the abstract syntax data holding device 0101 in the first embodiment, the abstract syntax data holding device 0801 in the second embodiment saves a necessary storage area in the abstract syntax data storage means 0103. It is possible to reduce. However, if the index corresponding to the above-mentioned OID data does not exist in the MO class definition storage means 0803, it is converted into an octet string type entry and stored in the abstract syntax data storage means 0103.

Next, the MIB according to the embodiment of the present invention will be described in detail. FIG. 10 is a block diagram showing a schematic configuration of the MIB according to the embodiment of the present invention.

As shown in FIG. 10, in this embodiment,
The MIB 1001 includes an abstract syntax data storage device 0101, an MO class definition storage unit 0803, and an MO instance storage unit 1004. The management agent 1002 manages the managed device 1003 in accordance with a request from the management manager 5301 via the MIB having such a configuration.

Further, in the embodiment of the present invention, MIB1
001 may be configured as shown in a block diagram showing a schematic configuration in FIG. The MIB 1001 shown in FIG. 11 includes an abstract syntax data holding device 0801 and MO instance storage means 1004.

The MIB 1001 shown in FIG. 10 and the MIB 1001 shown in FIG.
The difference between the two is that the device according to the first embodiment of the present invention or the device according to the second embodiment is used as an abstract syntax data holding device. That is, since the abstract syntax data holding device 0101 in the first embodiment of the present invention does not include the MO class definition storage means 0803, the MIB 1001 shown in FIG. MO class definition storage means 0803 is included.

The abstract syntax data holding units 0101 and 0801
It is necessary to receive as input the transfer syntax data encoded according to the BER of ASN.1 as input, determine whether the transfer syntax data needs to be stored internally, and store it. If it is data, it has a function of outputting an abstract syntax key corresponding to transfer syntax data after storing it.

As described above, the MO class definition storage means 0803 assigns the MO class number, and is attached to each class definition to identify the MO class.
It has a function to store a table composed of an OID and an integer value (index) corresponding to the entry as an entry, and a MO class definition that defines what attributes the MO instances belonging to each MO class have.

[0092] The MO instance storage means 1004 has a function of storing the individual MO instance nodes constituting the containment tree. In each MO instance node, the attribute value of the MO instance is stored in the form of an abstract syntax key.

FIG. 12 shows the MIB 1001 in this embodiment.
FIG. 4 is a block diagram for explaining in further detail the configuration of MO instance storage means 1004 included in. As shown in FIG. 12, MO instance storage means in the present embodiment
1004 stores an FDN hash table 1201, an MO instance node table 1202, and an MO instance attribute table 1203.

The FDN hash table 1201 stores the abstract syntax key corresponding to the FDN and the MO of the MO instance node corresponding to the FDN.
Address in the instance node table (this address is MO
This is a table in which a pair of (instance node key) is an entry, and is used to check whether the MO instance node corresponding to the FDN is already stored in the MO instance node table.

[0095] The MO instance node table 1202 is a table for storing each MO instance node constituting the containment tree. The MO instance nodes 1204 and 1205 in the MO instance node table 1202 correspond one-to-one with the MO instance nodes in the containment tree. That is, one MO in the containing tree
For an instance node, there is one corresponding MO instance node in the MO instance node table.

[0096] The MO instance attribute table 1203 is a table for storing attributes corresponding to each MO instance stored in the MO instance node table 1202. In the MO instance attribute table 1203, there are two types of entries, a reference MO instance 1206 and a difference attribute 1207. Reference MO
Since there is only one instance 1206 per MO class and has a role as a representative value of the attribute of the MO instance belonging to the MO class, the MO instance belonging to the MO class always includes the reference MO instance 1206. refer
(Shown by a dotted line with an arrow in FIG. 12). The difference attribute 1207 is the reference MO
Only the attribute values different from the attribute values represented by the reference MO instance are stored, which are referred to only from the MO instances having attribute values different from the attribute values represented by the instance 1206 (shown by a solid line with an arrow in FIG. 12). ).

That is, the MO instance node 1204 belonging to a certain MO class is referred to as the reference MO instance 12 storing the attribute value representing the MO instance belonging to the MO class.
MO instance node if it has an attribute value different from 06
1204 refers to the reference MO instance 1206 and the difference attribute 1207.

On the other hand, if the MO instance node 1205 belonging to a certain MO class has exactly the same attribute values as the reference MO instance 1206 storing the attribute values representing the MO instances belonging to the MO class, the MO instance node 1212
05 refers only to the reference MO instance 1206.

Next, MO instance node storage means 1004
The format of each entry of the MO instance node table 1202 and the MO instance attribute table 1203 stored therein will be described.

FIG. 13 is a block diagram for explaining in detail the format of an entry of the MO instance node table 1202 stored in the MO instance node storage means 1004 in the present embodiment.

As shown in FIG. 13, the MO instance node
The entry 1204 includes a field 1301 for storing an abstract syntax key corresponding to the OID of the attribute to be an RDN, and a field for storing an abstract syntax key corresponding to the attribute value of the attribute to be an RDN.
1302, a field 1303 for storing an abstract syntax key corresponding to the MO class OID, a field 1304 for storing a MO instance node key indicating a child node of the MO instance node in the containing tree,
A field 1305 storing an MO instance node key indicating the same level node of the instance node, and a MO indicating a parent node of the MO instance node in the containing tree
A field 1306 for storing an instance node key,
Reference MO corresponding to the MO class to which the MO instance belongs
Number of attributes whose values differ from the attribute values in the instance
Field 1307 for storing (this number is called the number of difference attributes)
And a field 1308 for storing the address in the MO instance attribute table of the difference attribute field corresponding to the MO instance node.

If the MO instance node is the MO instance node 1205 having exactly the same attribute values as the reference MO instance 1206, the fields 1307 and
The content of 1308 becomes "0".

FIG. 14 is a block diagram for explaining in detail the format of the reference MO instance 1206 of the MO instance attribute table 1203 stored in the MO instance storage means 1004 in the present embodiment. As shown in FIG. 14, the entry of the reference MO instance 1206 has the MO class OI
Field 1401 for storing abstract syntax key corresponding to D
And a field 1402 for storing the number of attributes of the MO instance belonging to the MO class, and a field 1403 for storing abstract syntax keys corresponding to the attribute values of the number indicated by the field 1402.

FIG. 15 is a diagram for explaining in detail the format of the difference attribute 1207 of the MO instance attribute table 1203 stored in the MO instance storage means 1004 in this embodiment. As shown in FIG. 15, the entry of the difference attribute 1207 includes a field 1501 for storing the position of an attribute having a different value from the reference MO instance, and a field 15 for storing an abstract syntax key corresponding to the attribute value for each of the attributes.
It consists of 02. Here, the position of the attribute is the MO in the MO class definition storage unit 0803 that defines the MO class.
Indicates the order of the attribute in the class definition. In the example of FIG. 9, the identifier OID "1.2.513.9.12" is assigned.
In the MO class definition, the attribute "Attribute2" indicated by the attribute ID "1.2.120.2.33" is defined second.

Next, how the MIB 1001 operates in the present embodiment will be described. Figure 16, Figure 17 and Figure
FIG. 18 is a flowchart for explaining the operation of the MIB 1001 in the present embodiment. Since the MIBs shown in FIGS. 10 and 11 basically perform the same operation, the MIBs shown in FIGS.
Using FIG. 18 and MIB 1001 in the present embodiment,
An outline of the operation will be described.

First, the MIB 1001 is the management agent 100
From step 2, the MO class ID (OID assigned to the MO class definition that defines the attributes of the MO instance to be accessed), FDN, and attribute ID are input (step 1601). The MIB 1001 inputs the given MO class ID to the abstract syntax data holding device 0801, and acquires the abstract syntax key corresponding to the MO class ID (step 1602).

Next, the MIB 1001 inputs the given FDN to the abstract syntax data holding device 0801, acquires an abstract syntax key corresponding to the FDN (step 1603), and corresponds to the FDN obtained in step 1603. Using the abstract syntax key, the FDN hash table 1 stored in the MO instance storage unit 1004
201 is retrieved, and an MO instance node key indicating the MO instance specified by the FDN is obtained (step 1604).

Further, the MIB 1001 inputs the given attribute ID to the abstract syntax data holding device 0801 and acquires the abstract syntax key corresponding to the attribute ID (step 1605).
Stored in the MO class definition storage means 0803 using the abstract syntax key corresponding to the MO class ID obtained in 02 and the abstract syntax key corresponding to the attribute ID obtained in step 1605.
The MO class definition group 0902 is searched to obtain the number of the attribute of the MO class definition identified by the MO class ID (step 1606).

Further, the MIB 1001 uses the MO instance node key obtained in step 1604 to correspond to the MO instance node key in the MO instance node table 1202 stored in the MO instance storage means 1004.
An MO instance node is obtained (step 1607), and it is checked whether or not a field 1307 indicating the number of difference attributes in the MO instance node obtained in step 1607 is "0".
(Step 1608). If the result of the inspection indicates that the number of difference attributes is “0”, the MIB 1001 uses the MO class ID obtained in step 1602
The MO instance attribute table 1203 stored in the MO instance storage means 1004 using the abstract syntax key corresponding to
To obtain a reference MO instance corresponding to the MO class (step 1701).

Next, the MIB 1001 accesses the attribute of the reference MO instance using the information of the attribute number of the attribute obtained in step 1606, and obtains the abstract syntax key corresponding to the attribute value. (Step 1702), and MI
B1001 inputs the abstract syntax key obtained in step 1702 to the abstract syntax data holding device 0801, and acquires an attribute value to be accessed (step 1703).

On the other hand, as a result of the inspection in step 1608,
If the number of difference attributes is not "0", the MIB 1001 proceeds to step 16
Field 1308 indicating the address in the MO instance attribute table of the difference attribute in the MO instance node obtained in 07
Using the contents of (1), a difference attribute in the MO instance attribute table 1203 stored in the MO instance storage means 1004 is obtained (step 1801).

Next, the MIB 1001 searches the field 1501 indicating the position of the attribute different from the reference MO instance in the difference attribute, using the information of the attribute number of the attribute obtained in step 1606. Then, it is checked whether or not the attribute number indicated by the information exists in the searched field (step 1802). As a result of the inspection, if the attribute number exists, the MIB 1001 accesses the field 1502 storing the abstract syntax key corresponding to the attribute in the difference attribute, and acquires the abstract syntax key (step 180).
3), the abstract syntax key obtained in step 1803 is input to the abstract syntax data holding device 0801, and the attribute value to be accessed is obtained (step 1804).

On the other hand, as a result of the inspection in step 1802,
If the attribute number does not exist, the MIB 1001 searches the MO instance attribute table 1203 stored in the MO instance storage means 1004 using the abstract syntax key corresponding to the MO class ID obtained in step 1602. To obtain a reference MO instance corresponding to the MO class (step 180
Five).

Next, the MIB 1001 accesses the attribute of the reference MO instance using the information on the attribute number of the attribute ID obtained in step 1606 and obtains the abstract syntax key corresponding to the attribute value. Is obtained (step 1806). Finally, the abstract syntax key obtained in step 1806 is input to the abstract syntax data holding device 0801, and the attribute value to be accessed is obtained (step 1807).

[0115]

The first effect of the present invention is that the storage area required to hold the abstract syntax data can be reduced.

The first reason is that the transfer syntax data is represented as an abstract syntax key, and a small INTEGER type value or a short character string type data is represented by embedding a value in the abstract syntax key itself. This is because accumulation in the abstract syntax data holding device is unnecessary. The second reason is that
For data having a large value that cannot be embedded in the abstract syntax key, the data is stored as internal data in the abstract syntax data storage means, and the address of the storage location is used as the abstract syntax key. In the case of storing data, in the present invention, data having the same value is stored in a separate area even if the value is the same. This is because the reference is made by using.

The second effect is that comparison between attribute values of MO instances can be performed at high speed.

The reason for this is that, as described above, when storing attribute values, data having the same value is stored so as to occupy only one place in the abstract syntax storage means, and is stored using an abstract syntax key. This is because they are referred to.
As a result, the abstract syntax key has a feature that "when there are a plurality of abstract syntax data having the same value, there is only one abstract syntax key corresponding to the plurality of abstract syntax data". A one-to-one correspondence is established between the key and the value of the abstract syntax data. Therefore, it is possible to compare the value of the abstract syntax data, that is, the attribute value only by comparing the abstract syntax key, and it is necessary to decrypt the data stored in the transfer syntax format as in the related art. Absent.

The third effect is that the storage area required to hold the MO instance can be reduced.

The reason for this is that a reference MO instance which is a MO instance having a standard attribute value for a MO instance belonging to each MO class is generated in advance, and when an MO instance belonging to the MO class is stored, the reference MO instance must be stored. reference
This is because the attribute value stored in the MO instance is referred to.
This is because only when the attribute value is different from the attribute value stored in the reference MO instance, only the attribute value corresponding to the attribute value having the different value is stored in another area.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a first embodiment of an abstract syntax data holding device of the present invention.

FIG. 2 is a block diagram showing a configuration of an abstract syntax data storage unit in the first embodiment of the abstract syntax data holding device of the present invention.

FIG. 3 is a block diagram showing a configuration of an abstract syntax definition storage unit in the first embodiment of the abstract syntax data holding device of the present invention.

FIG. 4 is a diagram showing a configuration of an octet column type entry of an internal data storage table stored in an abstract syntax data storage unit in the first embodiment of the abstract syntax data holding device of the present invention.

FIG. 5 is a diagram showing a configuration of a structure type entry of an internal data storage table stored in an abstract syntax data storage unit in the first embodiment of the abstract syntax data holding device of the present invention.

FIG. 6 is a flowchart showing an operation when data having a non-structured type is received in the first embodiment of the abstract syntax data holding device of the present invention.

FIG. 7 is a flowchart showing an operation when data of a structured type is received in the first embodiment of the abstract syntax data holding device of the present invention.

FIG. 8 is a block diagram showing a second embodiment of the abstract syntax data holding device of the present invention.

FIG. 9 is a block diagram showing a configuration of an MO class definition storage unit in the second embodiment of the abstract syntax data holding device of the present invention.

FIG. 10 is a block diagram showing an embodiment of the MIB of the present invention.

FIG. 11 is a block diagram showing another embodiment of the MIB of the present invention.

FIG. 12 is a block diagram showing a configuration of MO instance storage means in the embodiment of the MIB of the present invention.

FIG. 13 is a block diagram showing a format of an entry of a MO instance node table stored in the MO instance storage means in the embodiment of the MIB of the present invention.

FIG. 14 is a block diagram showing a format of a reference MO instance entry of a MO instance attribute table stored in a MO instance storage means in the embodiment of the MIB of the present invention.

FIG. 15 is a block diagram showing a format of a difference attribute entry of the MO instance attribute table stored in the MO instance storage means in the embodiment of the MIB of the present invention.

FIG. 16 is a flowchart showing the first half of the operation of the MIB embodiment of the present invention.

FIG. 17 is a flowchart showing the latter half of the operation when the number of difference attributes is “0” in the MIB embodiment of the present invention.

FIG. 18 is a flowchart showing the latter half of the operation when the number of difference attributes is not “0” in the MIB embodiment of the present invention.

FIG. 19 is a diagram showing a containment tree configured with an MO instance as each node.

FIG. 20 is a diagram showing an example of an abstract syntax.

FIG. 21 is a block diagram showing an example of the configuration of a conventional abstract syntax data holding device.

FIG. 22 is a block diagram showing a configuration of a network management system.

FIG. 23 is a block diagram showing an example of the configuration of a conventional MIB.

FIG. 24 is a flowchart showing the operation of a conventional MIB.

[Explanation of symbols]

 0101 Abstract syntax data storage device 0102 Abstract syntax data conversion means 0103 Abstract syntax data storage means 0104 Abstract syntax definition storage means 0105 Abstract syntax data hash table 0201 Internal data storage table 0301 Abstract syntax definition-index correspondence table 0302 Abstract syntax definition group 0401 octet Column type entry 0501 Structure type entry 0502 SET type entry 0503 CHOICE type entry 0801 Abstract syntax data storage device 0802 Abstract syntax data conversion device 0803 MO class definition storage device 0901 OID-index correspondence table 0902 MO class definition group 1001 MIB 1002 Management agent 1003 Managed device 1004 MO instance storage means 1201 FDN hash table 1202 MO instance node table 1203 MO instance attribute table 1204 MO instance node 1205 MO instance node 1206 Reference MO instance 1207 Difference attribute 5101 Abstract syntax 5102 Value notation 5103 Transfer syntax 5201 Abstract syntax data Security Apparatus 5301 manager 5401 MIB 5402 directory storing unit 5403 data storing unit 5404 class information storage unit

Claims (12)

[Claims] An abstract syntax data holding device for storing abstract syntax data whose structure is defined by an abstract syntax,
Receives the transfer syntax data as input, determines whether the transfer syntax data is data stored in the device, and converts the transfer syntax data into an abstract syntax key if the data does not need to be stored. Has a function to output,
If the transfer syntax data needs to be accumulated, the transfer syntax data is converted into internal data, stored in the device, and then the address where the internal data is stored in the device is output as an abstract syntax key. Abstract syntax data conversion means having a function; abstract syntax data storage means having a function of storing internal data corresponding to transfer syntax data determined to be required to be stored by the abstract syntax data conversion means; An abstract syntax definition that has a function to store a table composed of abstract syntax definition names and their corresponding integer values (indexes) as entries in order to manage them by numbering them. An abstract syntax data holding device comprising: a storage unit. 2. An abstract syntax data holding device for storing abstract syntax data whose structure is defined by an abstract syntax, wherein transfer syntax data is received as an input, and whether the transfer syntax data is data stored in the device. Has the function of converting the transfer syntax data into an abstract syntax key and outputting the data if the data does not need to be stored,
If the transfer syntax data needs to be accumulated, the transfer syntax data is converted into internal data, stored in the device, and then the address where the internal data is stored in the device is output as an abstract syntax key. Abstract syntax data conversion means having a function; abstract syntax data storage means having a function of storing internal data corresponding to transfer syntax data determined to be required to be stored by the abstract syntax data conversion means; An abstract syntax definition that has a function to store a table composed of abstract syntax definition names and their corresponding integer values (indexes) as entries in order to manage them by numbering them. Each class definition to identify the MO class, for storage means and MO class numbering and management It has been granted
MO that stores a table composed of OIDs and their integer values (indexes) as entries, and that stores the MO class definition itself that defines what attributes the MO instances belonging to each MO class have. An abstract syntax data holding device comprising: a class definition storage unit. 3. The abstract syntax data conversion means includes an abstract syntax data hash table composed of transfer syntax data and internal data corresponding thereto as an entry, and the internal data corresponding to the input transfer syntax data is already stored. If it exists in the abstract syntax data hash table, it has a function of outputting the address at which the internal data is stored as an abstract syntax key, and the internal data corresponding to the transfer syntax data is stored in the abstract syntax data hash table. If it does not exist, the internal data corresponding to the transfer syntax data is stored in a free space in the abstract syntax data storage means, the abstract syntax data hash table is updated, and the address at which the internal data is stored is abstracted. 3. The abstract syntax data storage according to claim 1, wherein the function has an output function as a syntax key. Location. 4. The abstract syntax data storage means includes an internal data storage table configured as an entry with internal data corresponding to the transfer syntax data determined to need to be stored, and the internal data storage table can be taken. As an entry, an abstract syntax index field whose content is always "0", an octet length field indicating the octet length of the transfer syntax field, a reference count field indicating the number of times of reference from an external or other entry, and a transfer corresponding to the entry An octet sequence type entry composed of a transfer syntax field for storing syntax data, an abstract syntax index field indicating an index of an abstract syntax defining a transfer syntax corresponding to this entry,
Consisting of an element count field indicating the number of elements of the abstract syntax, a reference count field indicating the number of references from the outside or from another entry, and an element field which is present for the number of elements and stores an abstract syntax key indicating the element. An abstract syntax index field indicating an index of an abstract syntax defining a transfer syntax corresponding to this entry,
An element position field indicating which element of the abstract syntax is stored in the element field, a reference number field indicating the number of references from the outside or another entry,
3. The abstract syntax data holding device according to claim 1, wherein there is a CHOICE type entry including an element field storing an abstract syntax key indicating an element indicated by the element position field. 5. An abstract syntax having a pair of an abstract syntax definition name and an index corresponding thereto, as an entry, wherein said abstract syntax definition storage means is used to hold a correspondence between an abstract syntax definition and an index corresponding thereto. 3. The abstract syntax data holding device according to claim 1, wherein a definition-index correspondence table and an abstract syntax definition group that is the definition itself of the abstract syntax are stored. 6. An MO class definition storing means for storing, for each OID assigned to an MO class definition, a correspondence between an OID and an index corresponding to the OID.
An OID-index correspondence table having, as entries, pairs of OIDs assigned to class definitions and corresponding indexes, and MO class definitions themselves that define what attributes each MO class actually has. 3. The abstract syntax data holding device according to claim 2, wherein the MO class definition group is stored. 7. An abstract syntax data holding device for storing abstract syntax data whose structure is defined by an abstract syntax, wherein it is necessary to store the abstract syntax data before storing the abstract syntax data in the device. Determine whether
When only the data that needs to be accumulated is accumulated, and when it is necessary to accumulate the abstract syntax data internally, the data is converted into internal data, and the abstract syntax data is referred to from the outside. An abstract syntax data holding device, which outputs an abstract syntax key having a one-to-one correspondence, and does not store abstract syntax data having the same value in separate storage areas. 8. A management information base used in a network management system for abstracting a physical management target and realizing it as a logical model, comprising: an abstract syntax data holding device; A management information base comprising MO instance storage means having a function of storing MO instance nodes. 9. The MO instance node, wherein the MO instance storing means is used to check whether the MO instance node corresponding to the FDN is already stored in the MO instance node table. FDN hash table composed of key pairs as entries, MO instance node table used to store each MO instance node that constitutes the containment tree, and MO instance node table The management information base according to claim 8, wherein a MO instance attribute table, which is a table used to store an attribute corresponding to each MO instance, is stored. 10. The MO instance storage means includes a MO instance node table, which is a table used to store each MO instance node constituting a containment tree,
An entry of the MO instance node table includes a field for storing an abstract syntax key corresponding to an OID of an attribute serving as an RDN, a field for storing an abstract syntax key corresponding to an attribute value of an attribute serving as an RDN, and an MO class OID. A field for storing a corresponding abstract syntax key, a field for storing a MO instance node key indicating a child node of the MO instance node in the containing tree, and a MO instance node indicating the same level node of the MO instance node in the containing tree A field for storing a key; a field for storing a MO instance node key indicating a parent node of the MO instance node in the containing tree; a field for storing the number of differential attributes of the MO instance corresponding to the entry; and the MO instance MO of the difference attribute field corresponding to the node 10. The management information base according to claim 9, comprising a field for storing an address in the instance attribute table. 11. The MO instance storing means includes a MO instance attribute table which is a table used to store attributes corresponding to each MO instance stored in a MO instance node table. As a possible entry of the table, there is a reference MO instance and a difference attribute, and the reference MO instance entry is a field for storing an abstract syntax key corresponding to the MO class OID, and an attribute of the MO instance belonging to the MO class. A field for storing the number of abstract syntax keys corresponding to the attribute values of the number indicated by the field, wherein the difference attribute entry stores the position of the attribute having a different value from the reference MO instance And a field storing an abstract syntax key corresponding to an attribute value for each of said attributes. Management information base according to claim 9, characterized in that they are composed of. 12. A management information base used in a network management system for abstracting a physical management target and realizing it as a logical model, having a standard attribute value for MO instances belonging to each MO class. A reference MO instance that is an MO instance is generated, and when an MO instance belonging to the MO class is stored, the attribute value stored in the reference MO instance is referred to. Only when there is an attribute having a different value from the attribute value stored in the reference MO instance, only the attribute value corresponding to the attribute value having a different value is stored in another area. Information base.