KR100228299B1 - Method for realizing tmn based network managing system supporting mmc in atm exchange - Google Patents

Abstract

The present invention introduces the transaction concept used in the database to support functional MMC commands in TMN-based network management and operation systems based on the ITU-T standard. How to match. By configuring several CMIP operations for a transaction corresponding to one MMC, the association and execution result between the CMIP operations are defined as one transaction. The parallel operation of the MMC, which is the operation and management message, executes these transactions simultaneously, and the progress of each of the transactions enables each transaction to be a basic finite state machine (FSM).

Description

Implementation Method of TMN-based Network Management System Supporting MMC in ATM Switching System

The present invention relates to a communication network management system supporting MMC (Man Machine Command) in an ATM exchange management system based on a Telecommunications Management Network (TMN), and in particular, a TMN-based network management and operating system based on a standard. In an ATM exchange system that allows management object management operations defined by Guidelines for the Definition of Managed Objects / Abstract Syntax Notation (GDMO / ANS.1) to be combined with MMC commands focused on management functions from the operator's point of view. The present invention relates to a method of implementing a network management system supporting MMC.

Conventional exchange operation systems that are subject to ATM ESS tasks use non-standardized operation messages that consider only the operation and management convenience of the exchange itself, namely MMC based on the ITU's Man-Machine Language (MML). As standard of management and operation is established, it is inevitable to introduce standardized network management interface into ATM element itself, which is a network element. Integrating TMN-based network management and operation systems based on model and information access is an important issue. However, the operation and management system of the conventional ATM switch uses commands that correspond one-to-one with the functions of the ATM switch defined from the operator's point of view. In other words, considering the convenience of the operator, it is mainly focused on the operation by operation for the operating system, and most of them are defined as MMC sets.On the contrary, the TMN-based network management and operation system divides the system into object units called managed objects (MO). The management and management operations are performed on this management object. In other words, the operation and management viewpoint that the operator sees is the functional unit of MMC by function-oriented management, whereas the operational and management viewpoint according to the TMN standard is the basic performance unit. The above-mentioned conventional problem is that the functional-oriented MMC instruction must first be analyzed by several CMIP operations from the operator's point of view, and the individual responses of these analyzed operations must be aggregated and combined into response messages required from the operator's point of view. In addition, since the operator can generate several operating commands at the same time, there is a problem that the support method for this should be considered.

Accordingly, an object of the present invention is to provide a method and system for creating, managing, and defining transactions to support functional MMC commands in a TMN based network management and operation system based on standards.

The present invention for the above purpose is to introduce a transaction concept used in the database to match the functional-oriented operation and management MMC from the operator's point of view to one transaction, and to multiple CMIP operations for a transaction corresponding to one MMC It is configured to show the association between the CMIP operation and the result of the operation. In addition, parallel operation of the operation and management messages is allowed to proceed simultaneously with each transaction, and each progress of the transaction is a basic finite state. It features a finite state machine (FSM).

1 is an overall configuration diagram of a communication management system applied to an embodiment of the present invention;

2 is a block diagram illustrating the internal structure of the management operation processing unit 121 of FIG. 1.

3 is a detailed flowchart of the message conversion management unit 123 of FIG. 1.

4 is a detailed flowchart of the message conversion graphic user interface unit 125 according to an embodiment of the present invention.

Figure 5 is a specific flow chart in the angle management application of Figure 2 according to an embodiment of the present invention

6 is a message format diagram of the management operation processing unit 121, the message conversion management unit 123, and the message conversion graphic user interface unit 125 of FIG.

7 is a configuration diagram of an operation code of FIG.

8 is a message format diagram of the management operation processing unit 121 of FIG. 1 of the present invention.

9 is a diagram illustrating a message conversion according to an embodiment of the present invention.

10 is a view illustrating definition and management of operation code conversion data according to the present invention.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

1 is a TWN-based network management system diagram applied to an embodiment of the present invention.

1 is composed of an ATM switching system 101 and a network management system 102. The ATM switching system 101 includes various application processing apparatuses such as the first to third processors 111-113 and 115 and operational maintenance. It is composed of a processor 117, the network management system 102 is connected through the operator interface system 127, the message conversion management unit 123 and the message conversion graphical user interface unit 125, management operation processing unit 121 In operation and management messages control the operation maintenance processor 117 in the ATM switching system (101). The operator interface system 127 defines several operational commands to effectively manage the resources of the ATM switching system 101 that are subject to operation and management, and enables the operator to use these commands. The ATM switching system 101 is not directly seen from the perspective of the network management system 102, but is replaced with another system that performs network operation and management, that is, replaced by a management agent (PROXY AGENT or AGENT) system. This system is present in the operation preservation processor 117 of the ATM switching system 101. Therefore, a substantial operation and management between the operator interface system 127 and the management agent system 117 of the ATM switching system 101 is performed. There is a management operation processing unit 121 to control the. The management operation processing unit 121 operates and manages the network according to the standard of the network management system 102. The management operation processing unit 121 is required to convert the message format in order to solve the problem caused by the difference between the operation and management form processed by the ATM switching system 101. To this end, a message conversion management unit 123 for converting an output message of the operator interface system 123 into a management function message required by the management operation processing unit 121, and an output signal of the management operation processing unit 121 to the operator interface system. A message conversion GUI unit 125 for converting into a message requested at 123 is used.

2 is a block diagram illustrating an internal configuration of the management operation processing unit 121 of FIG. 1.

Among the network management functions, a configuration management unit 201 in charge of the configuration management function, a connection management unit 202 in charge of the connection management function, and a failure management unit 203 in charge of the management function of the failure. The expansion management application unit (221, 223), the basic management application unit (231, 233) of each unit processes a function-oriented MMC command, the common management information protocol processing unit 213 is a standard command of the network management system 102 CMIP command Process.

3 is a detailed flowchart of the message conversion management unit 123 of FIG. 1.

A first process of generating and loading data for message conversion of the operator interface system 127 and receiving a message;

A second step of confirming that the received message of the first step is a configuration, connection, or failure MMC;

A third process of controlling an application according to configuration and date and time configuration management in the second process;

A fourth process of controlling an application according to connection temporary connection management in the second process;

The second process consists of a fifth process for controlling the application according to the temporary failure management.

4 is a detailed flowchart of the message conversion GUI unit 125 according to an embodiment of the present invention.

The first step of generating a message for the configuration, connection, failure in the extended management application unit (221, 223), basic management application unit (231.233) for the received message from the management operation processing unit 121,

A second step of converting the message generated in the first step into a format usable in the operator interface;

And a third step of delivering the message converted in the second step to the operator interface.

5 is a detailed flowchart of each management application of FIG. 2 according to an embodiment of the present invention.

A loading step of loading an extended MAF instruction,

A message receiving step of receiving a message;

Confirming whether the received message is an extended MAF command;

When it is not the MAF instruction in the confirmation process, it is processed as a basic MAF instruction, and when an extended MAF instruction, an extended MAF is generated to process an instruction thereof.

6 is a message format diagram of the management operation processing unit 121, the message conversion management unit 123, and the message conversion GUI unit 125 of FIG.

601 is the format from the user's point of view, 602 is the stream order from the provider's point of view, 603 is the currently defined message format diagram, 604 is the CMIP format used for the type of CMIP message among the defined message formats, and 605 is HML format used for HMI message types among the defined message formats.

7 is a configuration example of an operation code of FIG. 6.

8 is a message format diagram of the management operation processing unit 121 of FIG. 1 of the present invention.

9 is a diagram illustrating a message conversion according to an embodiment of the present invention;

10 is an example of definition and management of operation code conversion data.

Therefore, a specific embodiment of the present invention will be described in detail with reference to FIGS. 1 to 10.

Looking at the message processing process delivered from the operator interface system of Figure 1,

The operator's command transmitted from the operator interface system 127 of FIG. 1 is received and processed by the message conversion management unit 123 of the network management system 102. The message conversion management unit performs the conversion according to the received message. For this, before the MMC is input, as shown in the example of FIG. The delivered message follows the format of FIG. 6, and an important message necessary for the operation of the message conversion management unit 123 is in an operation code field, which is described in detail in FIG. 7. That is, an OP class field for determining a MAF and an OPid field corresponding to an operation FSM id are defined. The OPcode example is shown in Table 1 below.

TABLE 1

When the MMC generated by the operator interface system 127 is received by the message conversion management unit 123 in step 3b, the received message is defined in the format of the message in steps 3c1 and 3c3. Operation code (OP Code) is analyzed as in (7) and 3c1-3c3 is used to configure, connect and fail MAF (CF-MAF, FT-MAF, CN-MAF) in (3d)-(3i). ) Is passed to the MAF. When the processing of the MAF is completed, the basic configuration, connection, and failure MAF is called at (3f, 3h, 3i). The MAF receiving the message analyzes whether the corresponding instruction is an MMC instruction already promised. In this case, the MAF is extended from the message received in step 5b by the extended MAF instruction loaded in step 5a. Check the MAF instruction. When the extended MAF instruction is created in step (5e) and the finite state machine (FSM) defined in step (5f) is performed, and in step (5c), the message is a basic MAF instruction instead of an extended MAF. In step (5d), the basic MAF instruction is processed.

Next, a process of transmitting an individual CMIP message response from the management agent system of the ATM switch 101 to the operator interface system 127 is as follows. The network operation and management paradigm in the TMN based network management system 102 environment is basically achieved through the exchange of CMIP messages. The CMIP message transmitted to the management operation processing unit 121 of the network management system 102 is delivered to the message conversion GUI unit 125, which is similar to the function of the message conversion management function unit 123 and plays the opposite role. . That is, as described above, the basic MAF or extended MAF generates a message to be delivered to the operator interface system 127, converts it appropriately, and then transfers the message to the message conversion GUI unit 125. In the process, the message conversion GUI received the message. The unit 125 converts this back into a message format usable by the operator interface system 127 and delivers it to the operator interface system 127. The message used between the message conversion GUI unit 125 and the operator interface system 127 is shown in FIG. 6, and the message format between each MAF and the message conversion GUI unit 125 is shown in FIG. 8. . All messages transmitted from the management counterpart system of the ATM switch 101 to the management operation processor 121 of the network management system 102 correspond to the CMIP. There are two types of these CMIP messages arriving at the management operation processing unit 121. One is a response message to a command issued by the network management system 102, and the other is a report command transmitted from the ATM switching system 101 or the management agent system 117. In the case of the report command, a MAF block that arrives according to the type of the corresponding report command is defined, which is already databased in the initialization in FIGS. 3 and 5. Therefore, for a report command of a defined type, the determination of the type of report command is simply a database reference. In contrast, the response message is automatically delivered to the MAF that issued the command by the ROSE (Remote Operation Service Element) service used by the CMIP. Therefore, whether the corresponding message is a command delivered from an extended MAF or a command transmitted from a basic MAF is a branch of the CMIP protocol environment of the communication management network 102 environment or the common management information protocol processing unit of FIG. 213). Therefore, in the case of any of the message types, the message is automatically branched to a basic MAF or extended MAF block, and each MAF processes the message as follows and forwards it to the operator interface system 127. In the case of a message corresponding to a basic MAF block, the related processing routine is aquatic and then transmitted to the message conversion GUI unit 125. In the case of a message corresponding to the extended MAF block, the message is processed according to the associated finite state machine. If no further message processing is required, it is transmitted to the message conversion GUI unit 125. The extended MAF block transmitted to the message conversion GUI unit 125 is destroyed because all processing routines defined in the self-defined finite state machine have been performed. Regardless of each message classification, the message conversion GUI unit 125 converts the corresponding message and simply transmits the message to the operator interface system 127. The operation relationship of the management operation processing unit 121 is shown in FIG. It analyzes the offset code defined in Table 1 as shown in the example of FIG. 6, and then the message conversion management unit 123 transmits it to the MAF block capable of processing it. The MAF block basically creates a new extended MAF of the finite state machine corresponding to the offset code when one basic MAF block is an extended MAF instruction (MMC instruction) that can be processed by message analysis and extended MAF. . Therefore, the message is processed and reported in a separate block. In order to generate, load, and initialize the converted data, the most important part of generating the converted data is the process of packing / unpacking the definition of the FSM for each MMC instruction and a corresponding message. The generation of the conversion data is performed before the system is driven. The generation of the conversion data for each opcode, packing / unpacking of related messages, and definition and retrieval of the finite state machine are shown in FIG. As shown in FIG. 10, a message structure is defined for each MMC opcode, and a library for packaging / unpacking the defined message is defined. In addition, an associated finite state machine is defined for each MMC opcode. The generation, definition and management of these conversion data takes place before the system is run. Therefore, each block that processes these messages for each MMC opcode uses transform data as follows. Between the message conversion GUI unit 125 and the message conversion management unit 123, the operating system corresponds to a field corresponding to each MMC instruction (the definition of the field is the same as the parameter data structure of the opcode descriptor corresponding to the opcode). The values obtained are obtained from the operator through the GUI interface. In order to transmit the obtained message to the message conversion management unit 123, a related packaging routine is called to char stream each message. The message conversion management unit 123 analyzes the received message to transmit the message received by the operating system to the management system 121 and obtains an operation code (opcode) of the corresponding message. Each field value of the message is obtained using the unpacking routine of the obtained opcode. The message conversion between the message conversion management unit 123 / message conversion GUI unit 125 and the management operation processing unit 121 has almost one-to-one correspondence between the two blocks. Convert to GDMO / ASN.1 model used by CMIP. Simultaneously with the data conversion, each MAF of the management operation processing unit 121 loads a finite state machine capable of processing the corresponding message when the corresponding message is an extended command. Therefore, the command is executed.

As described above, the present invention defines the creation and management of a transaction for supporting a functional MMC command in a TMN based network management and operation system based on a standard, and has an advantage of easily incorporating and driving an arbitrary command operator MMC. .

Claims (10)

In the men machine command (MMC) support system composed of the ATM switching system 101, the operator interface system (127) Operators of the network management system 102 connected to the 1-3 processor 111-113 and 115, the operation maintenance processor 117, and the ATM switching system 101, which are various application processing apparatuses of the ATM switching system 101; From the interface system 127, the message conversion management unit 123 and the message conversion GUI unit 125 are connected to form a network management system 101 for managing the ATM switching system 101 by the management operation processing unit 121. Network management implementation system supporting MMC in ATM switching system According to claim 1, wherein the management operation processing unit 121 is responsible for the configuration management unit 201 in charge of the configuration function, the connection management unit 202 in charge of the connection function according to each network management function area, and the fault function Network management implementation system supporting the MMC in the ATM switching system, characterized in that consisting of a failure management unit (203). 3. The network of claim 2, wherein each management application function unit comprises extended management application units (221, 223) and basic management application units (231, 233) for processing functional-oriented MMC commands. Management implementation system. According to claim 1, the message conversion management unit 123 is Means for generating and loading data for message conversion from the operator interface system 127 and receiving messages; Means for confirming that the received message is a configuration, connection, faulty MMC, Means for controlling the application according to the configuration date and time configuration management; Means for controlling an application according to the connection temporary connection management; Network management implementation system supporting the MMC in the ATM switching system, characterized in that configured as a means for controlling the application according to the temporary failure management. The method of claim 1, Message conversion GUI unit 125 means for generating a message for configuration, connection, failure in the extended management application unit 221, 223, basic management application unit 231.233 for the signal from the management operation processing unit 121; Means for converting the generated message into a format usable in the operator interface, The network management implementation system supporting the MMC in the ATM switching system, characterized in that the means for delivering the converted message to the operator interface unit. According to claim 5, Each management application portion loading means for loading an extended MAF instruction, Message receiving means for receiving a message; Confirmation means for confirming whether the received message is an extended MAF command; The network management supporting the MMC in the ATM switching system, characterized in that it consists of a command processing means for processing the instruction by generating an extended MAF when processing the basic MAF instruction when the MAF instruction is not in the confirmation process. Implementation system. Operator interface system of the network management system 102 connected to the 1-3 processor 111-113, 115, the operation maintenance processor 117, and the ATM switching system 101, which are various application processing apparatuses of the ATM switching system 101; In the message conversion management unit 123 and the message conversion GUI unit 125 is connected from (127) in the method for supporting the Men Machine Command (MMC) of the system consisting of the ATM switching system 101, the operator interface system 127 , It has a management operation processing unit 121, thereby operating management with the operation maintenance processor 117, the operator interface system 127 effectively manages the resources of the ATM switching system 101 that is subject to operation and management A method for network management that supports MMC in an ATM switching system, characterized by defining operational commands to enable the user to use these commands. The method of claim 7, wherein each management application comprises an extended management application process for processing a function-oriented MMC command, and a common management information protocol processing process for processing a CMIP command, which is a standard command of the communication management network. A method for implementing network management supporting MMC in an ATM switching system. According to claim 7, Message conversion management is the process of generating and loading data for message conversion from the operator interface system 127 and receiving a message, Confirming that the received message is configured, connected, or failed MMC; The process of controlling the application according to the configuration date and time configuration management, Controlling the application according to the connection date and time connection management; The network management implementation method for supporting MMC in the ATM switching system, characterized in that the process of controlling the application according to the temporary management of the failure. The method of claim 7, wherein Message conversion graphical user interfacing is the step of generating a message for configuration, connection, failure in the extended management application unit (221, 223), basic management application unit (231.233) for the signal from the management operation processing unit 121; Converting the generated message into a format usable in the operator interface, And transmitting the converted message to an operator interface unit, wherein the MMC supports the MMC in the ATM switching system.

Images