JPH07239816A - Agent system - Google Patents

Abstract

PURPOSE:To suppress the expansion of a shared memory area and to shorten the time required for processing by executing the processing while making the item numbers of an OID managing table and a CMIP data base correspondent to keys. CONSTITUTION:With a managing rganization name GDMO document identifier, template identifier and the element number of a GDMO template, among OID identifiers, as keys, an OID managing function 212 classifies extracted OIDs, prepares a table for each key, prepares a link between respective tables and registers these results on an OID managing table 214. When executing a managing operation after CMIP data are completely converted, the OID for operating a managing object is dispatched to a CMIP data managing function 215. The CMIP data managing function 215 retrieves the item number of the OID dispatched from a CMISE 217 by using the pointer of the identifier table of the OID managing table 214, retrieves an attribute value corresponding to the retrieved item number from a CMIP data base 216 and dispatches the retrieved attribute value to the CMISE 217.

Description

Detailed Description of the Invention

[0001]

The present invention relates to OSI (Open Systems).
Interconnection) Common management information protocol (CMIP) in an agent system in a managed system for network management
Protocol) data management method, and more particularly, to a CMIP data management method in an agent system that enables reduction of a shared memory area in the agent system and improvement of processing efficiency in the agent system.

FIG. 8 shows an OS for OSI network management.
It is a model of I system management. In FIG. 8, 1 is a management system and 2 is a managed system. The managed system includes an agent system 21 that operates a management target in response to a request from the management system, and a management target 22.

In order for the management system to perform management, a command to the management target and notification information from the management target are communicated between the management system and the agent system in the managed system. CMIP is a protocol for carrying these commands and notification information. The management performed here relates to, for example, a communication function and a monitoring / control function, and the management target is, for example, a communication device or a communication terminal.

By the way, the communication functions and the monitoring / control functions handled by the OSI network are becoming more sophisticated, more complicated and faster, and the scale of the network is steadily expanding. Therefore, it is necessary to perform high-speed processing within the agent system. Therefore, it is important to improve the efficiency of CMIP data management, and it is also important to make the expansion rate of the agent system itself smaller than the expansion rate of the network.

[0005]

2. Description of the Related Art CMIP data communicated between a management system and a managed system is a managed object identifier (OI).
D; Object IDentifier) and a basic data type called an attribute value. This OID is defined for each management target. The managed system accommodates a huge number of management targets, and moreover, a plurality of operations are performed on one management target.

FIG. 9 shows a conventional managed system. In FIG. 9, 21 is an agent system, which is a CMI.
P termination function 211 and common management information service element (CMI
SE; Common Management Information Service Elemen
t) 217. Further, 22 is a management target.

In the conventional agent system in the managed system, the CMIP data is directly written into the shared memory area in the agent system for processing, so that the shared memory area requires an enormous memory size. The problem arises that the processing efficiency of the agent system is reduced.

[0008]

SUMMARY OF THE INVENTION An object of the present invention is to solve such problems and to reduce the shared memory area in the agent system and to improve the processing efficiency in the agent system. It is an object to provide a CMIP data management system in a system.

[0009]

FIG. 1 is a block diagram of a network management system according to the present invention, showing the configuration of a managed system in detail.

In FIG. 1, 1 is a management system and 2 is a managed system. 21 is an agent system,
Reference numeral 22 is a management target, which constitutes a managed system. Furthermore,
Reference numeral 211 denotes a CMIP sent from the management system for connection processing between the management system and the agent system.
A CMIP terminating function for receiving data and requesting a CMIP data management function, which will be described later, for data conversion processing, 21
2 is the definition of the management target (GDMO; Guideline for
OID from Definition of Management Object)
O to classify and add item numbers to convert to OID management table
An ID management function, 213 is a GDMO class definition in which a management target is described using GDMO, 214 is a table having a plurality of OID identifiers, and an item number management table in which OIDs and item numbers are associated, and the relationship of the OID identifiers. The OID management table 215 that searches the OID from the CMID and associates the searched OID with the item number is processed into the CMIP database by processing the CMIP data requested by the CMIP termination function, and the CMISE and CMIP termination function described later. A CMIP data management function 216 for mediating with the CMIP data management function 216 is a CMIP database 217 for storing the converted CMIP data into an OID relationship table and an actual data management table that associates OID item numbers with their attribute values. Is the common management information that controls the management target based on the CMIP data information. Service Element (CMISE; Common
Management Information Service Element) to configure the agent system.

[0011]

In the present invention, the OID management function is GDMO.
OID is extracted from the class definition, and the extracted OI
While classifying D with various identifiers as keys,
The item number is assigned and stored in the OID management table. When executing management operations, the OID management table and CMIP
Since the database is processed by comparing the item number with the key, the shared memory area in the agent system can be small, and the length of the transfer information accompanying the processing is reduced, so the processing efficiency is improved. improves.

[0012]

EXAMPLE FIG. 2 shows C in the managed system in FIG.
The MIP data conversion process is shown. In FIG. 2, 1 is a management system and 21 is an agent system. or,
211 is a CMIP termination function, 212 is an OID management function,
213 is a GDMO class definition, 214 is an OID management table, 215 is a CMIP data management function, and 216 is a CM.
Configure the agent system with the IP database.

GDMO that describes the management target
The class definition contains multiple GDs, as shown in Figure 2.
MO document is stored. The contents described in the GDMO document include the definition of the name of the management target, the definition of the operation of the management target, and the definition of the state of the management target. The document that defines the operation or state of these management controls is the template, and the elements of the template express the individual operation or state in the template. A specific management target is defined by a combination of these definitions. For each GDMO document with such a GDMO class definition, "REGIST
The character string "ERED AS" is searched, and the OID that follows it is extracted by the OID management function. This extraction processing is performed for all GDMO documents registered in the GDMO class definition.

FIG. 3 shows the structure of the extracted OID.
As shown in FIG. 3, the OID is (1) the management institution name (for example, I
SO), (2) Name of the organization whose name management has been entrusted by the management organization (for example, national telecommunication administration), (3) Organization name (for example, telecommunications carrier, manufacturer), (4) Document identifier, (5) Template Identifier, (6) An identifier representing the element number of the GDMO template. CMIP data is OID
And the attribute value (Value) added after the OID. This attribute value represents control information.

Of the above OID identifiers, the management institution name,
The OID management function classifies the extracted OIDs by using the GDMO document identifier, the template identifier, and the element number of the GDMO template as keys, creates a table for each key, creates a link between the tables, and outputs these results to the OI.
Register in the D management table.

FIG. 4 shows the structure of the OID management table, which comprises a management institution name table, a GDMO document identifier table, a template type identifier table, and an item number management table. The management institution name table, the GDMO document identifier table, and the template type identifier table are represented by the respective identifiers and pointers that make up the OID. Here, the pointer represents the correspondence between the identifiers by the line number of each table. For example, for a certain management institution registered in the management institution name table, p rows of the GDMO document identifier table, Assuming that the GDMO identifier registered in the qth row corresponds to the above, p and q are written in the pointer column of the row in which the management institution name is registered.

The process described so far is re-explained in the OID management table creation flowchart of FIG. The table creation process will be described below with reference to the reference numerals in FIG. A. From the GDMO class definition, select the top GDMO document. B. The selected GDMO document is searched for the character string "REGISTERED AS" that identifies the description of the OID. C. The part enclosed in {} following "REGISTERED AS" is extracted as an OID and registered in the OID management table. D. It is determined whether or not all the selected GDMO documents have been searched. When there is a part that has not been searched yet (No), the process returns to B and continues the search. E. When the search of the selected GDMO document is completed (Yes
In s), it is determined whether there is any GDMO document that has not been selected yet. F. When there is an unsearched GDMO document (Yes), the next GDMO document is selected and the process returns to B. G. When it is determined in E that the search has been completed for all GDMO documents (No), first, the OID management table is classified by management organization name, and only the management organization name is registered in the management organization table. H. Each management organization is classified by each GDMO document identifier, and the portion of the GDMO document identifier is registered in the GDMO document identifier table. I. Each GDMO document identifier is classified by the template identifier, and the template type portion is registered in the template type identifier table. J. Each OID is associated with the item number and registered in the item number management table. K. Write a pointer in each identifier table row as described above.

Now the OID in the GDMO class definition
The classification and registration of are completed. This OID management table is
It is used in comparison with a CMIP database, which will be described later, in which CMIP data sent from the management system is analyzed when executing a management operation.

Returning to FIG. 2, the CMIP terminating function receives the CMIP data sent from the management system, and
A CMIP data conversion request is issued to the P data management function. Upon receiving the CMIP data conversion request, the CMIP management function analyzes the OID in the CMIP data,
Management institution name table in the ID management table, GDMO document identifier table, template type identifier table,
Use the item number management table to set the item number of the corresponding OID to O.
Search from the ID management table.

The internal data structure of the CMIP data sent from the management system is converted using the item number of the OID searched above. FIG. 6 is a diagram for explaining the data structure of CMIP data. FIG. 6A is a tree showing the relationship of OIDs in CMIP data, and FIG.
The contents of the MIP database are shown.

In FIG. 6A, each OID of CMIP data is converted into an item number, and the relationship of each OID is clarified. For example, OID (1) is the same as OID (2)
It is composed of ID (3). OID (2) is an OID that cannot be decomposed any more. And OID (3) is OID
(4) and OID (5), and OID (4) and OID
ID (5) is an OID that cannot be decomposed any further. Then, a combination of OIDs (for example, the OID in FIG.
(1), OID (3), and OID (5)] enable the management target to be recognized.

The relationship of the tree in FIG. 6A is converted, and
The CMIP database in FIG. 6B is a table in which the relationship between each OID and the attribute value of the OID described after the OID is tabulated. OID in CMIP database
The relationship table expresses the tree relationship of FIG. That is, OID (1) is OID (2) and OID (3)
OID in the column of level (n)
Register the item number of (1) and enter the OID in the level (n + 1) column.
Register the item numbers of (2) and OID (3). Since OID (2) is a terminal OID that cannot be decomposed any more, it is not registered in the inter-OID relationship table. Similarly, the item number of OID (3) is registered in the level (n) column of the OID relationship table, and O
The item numbers of ID (4) and OID (5) are registered in the level (n + 1) column of the inter-OID relationship table. OID (4) and OID
Since (5) is the end OID, it is not registered in the level (n) column of the inter-OID relationship table.

Then, the relationship between all the OIDs and the attribute values is registered in the actual data management table. FIG. 7 is a flowchart of the CMIP data conversion described in FIG.
CMIP data conversion will be described below with reference to the reference numerals in FIG. 7. L. Each OID of CMIP data is converted into an item number with reference to the OID management table. M. It is determined whether or not it is the terminal OID. Terminal OI
If D (Yes), jump to Q. N. When it is not the terminal OID (No), the OID converted into the item number is registered in the level (n) of the inter-OID relation table of the CMIP database. P. The OIDs that make up each level (n) OID are OIDs
It is registered in the level (n + 1) column of the relationship table. Q. The attribute value corresponding to the item number of the OID is registered in the actual data management table. R. It is determined whether or not registration has been completed for all OIDs, and if not completed (No), the process jumps to L and continues registration. When all the OIDs have been registered (Yes), the conversion of CMIP data is completed.

When the management operation is executed after the conversion of the CMIP data is completed, the procedure is as follows. That is, CMISE
Passes the OID for operating the management target to the CMIP data management function in order to obtain the attribute value assigned to the OID necessary for operating the management target. CMIP data management function is CMIS
The item number of the OID passed from E is searched using the pointer of the identifier table of the OID management table, the attribute value corresponding to the searched item number is searched from the CMIP database, and the searched attribute value is CMISE. Pass to. In this way, the management operation can be performed without directly using the OID identifier and the attribute value added to the OID.

[0025]

As described above, according to the present invention, GDM is used.
A table is formed by classifying the O document OIDs for each identifier, and each OID is converted into an item number, and the relationship between each OID sent from the management system and the attribute value of each OID are registered in the table. Using these, the agent system performs management operation based on the request of the management system. Therefore, it is possible to suppress the expansion of the shared memory area and reduce the time required for the processing, as compared with the case where the management operation is directly performed using the OID itself and the attribute value.

[Brief description of drawings]

FIG. 1 shows the configuration of a network management system of the present invention.

FIG. 2 is a conversion process of CMIP data.

FIG. 3 Structure of OID.

FIG. 4 is an OID management table.

FIG. 5 is a flowchart for creating an OID management table.

FIG. 6 Structure of CMIP database.

FIG. 7 is a flowchart of CMIP database conversion.

FIG. 8: OSI system management model.

FIG. 9 Conventional managed system

[Explanation of symbols]

 1 Management System 2 Managed System 21 Agent System 22 Management Target 211 CMIP Termination Function 212 OID Management Function 213 GDMO Class Definition 214 OID Management Table 215 CMIP Data Management Function 216 CMIP Database 217 CMISE

Claims (3)

[Claims] 1. An OSI (Open Systems Interconnecti) comprising a management system (1) and a managed system (2).
on) an GDMO class definition (213) that defines a control target, which is an agent system in a managed system of the network management system, and a management target identifier (OID) described in the GDMO class definition, Is converted into an OID management table including a plurality of identifier tables that classify each of the plurality of identifiers that compose the above-mentioned identifier and that expresses the relationship between the plurality of identifiers, and an item number management table that associates the OIDs with item numbers.
The ID management function (212), the converted OID management table (214), and the common management information protocol (CMI) from the management system.
P) receives the CMIP data sent via the CMIP terminating function and sends the received CMIP data to the O
An agent system comprising a CMIP data management function (215) for converting to a CMIP database by referring to an ID management table and a converted CMIP database (216). 2. The agent system according to claim 1, wherein the OID management table includes a management institution name table forming an OID, a GDMO document identifier table, and a template type identifier table in a GDMO document. , OID and item number management table for associating item numbers with each other. In the management institution name table, the GDMO document identifier table, and the template type identifier table, pointers representing the identifiers and the correspondence relationships between the identifiers are provided. An agent characterized by being a registered management table in which the OID and the item number are registered in the item number management table.
system. 3. The agent system according to claim 1, wherein the CMIP database receives an OID relationship table expressing a relationship between OIDs in the received CMIP data, an item number of all OIDs, and an OID received. OID in CMIP data
An agent system characterized by being a CMIP database composed of an actual data management table that associates attribute values associated with the.