KR100283396B1 - Network element interface method - Google Patents

Abstract

The interface structure facilitates the development of a general-purpose Q3-adapter that provides a Q3 interface for equipment that does not provide a Q3 interface. The management system detects a VC connection request applied through an F-interface from a GUI. When the M-ACTION command is assembled and generated by ICF and then applied to the NWMF through the IPC interface, the NWMF in the management system processes the M-ACTION command as the M-ACTION REQUEST command and Q3 through the Q3 interface. The process of applying to the QAF side in the adapter, the QAF in the Q3-adapter analyzes the applied M-ACTION REQUEST command, assembles it into RRI command through ICF, and transmits to the non-TMN NE through M-interface. The non-TMN NE, which receives an RRI command through the M-interface, analyzes the received RRI command and then executes a combination of NE special instructions to M-in the result. The process of transmitting to the ICF side of the Q3-adapter through the face, and receiving the execution result from the non-TMN NE, the Q3-adapter analyzes the result of the RRI received through the M-interface and reflects the result in the MIB. The result of M-ACTION REPLY command is formed through QAF and transmitted to the NWMF side of the management system through the Q3-interface, and the management system analyzes the M-ACTION REPLY command received through the Q3-interface and reflects it to the MIB. Next, the process of delivering the result of the requested VC to the GUI side through the F-interface.

Description

Network element interface method

The present invention relates to a network element interface method, and more particularly, to an interface structure for facilitating development of a general-purpose Q3-adapter that provides a Q3 interface for equipment that does not provide a Q3 interface. It is about.

In general, the Q3-Adapter is a system configured to provide a Q3 interface for equipment that does not provide a Q3 interface (hereinafter referred to as `` non-TMN NE ''). M.3010 describes the Q3-Adapter Function (QAF) and the Reference Point between a non-TMN NE.

As shown in FIG. 1, the reference point between the Q3-adapter management function 20 and the non-TMN NE 10 network element is called an M-interface, and the M-interface is defined by the equipment manufacturer. As a local interface that can be used as a service, it exists outside the Telecommunication Management Network (TMN) area and has not been standardized.

Therefore, the interfaces that non-TMN NE can provide include IPC (Inter Processor Communication) and Simple Network Management Protocol (SNMP), and they are equipped with SNMP, which has become a LAN (Local Area Network) management standard. In the case of a network element (NE), a Q3-adapter capable of converting the CMIP to the SNMP using the Common Management Interface Protocol (CMIP) is required.

In addition, there is a need for a Q3-adapter that can convert SNMP to the Common Object Request Brpker Architecture (CORBA) IDL specification, and convert the IDL specification to CMIP and vice versa, and this Q3-adapter introduces many implementation issues. Doing.

In case of NE equipped with IPC, Q3-Adapter can receive all management information of NE through IPC and transmit it to CMIP, but there is no specification defined for interface with NE.

For Q3-Adapter processing, how to convert Q3-Primitives into NE-dependent commands, how to express Q3 management information to the NE, and how the NE's status is displayed in MIB (Management Information Base) in real time The question is whether to reflect it.

Real-time state matching between the NE and the Q3-adapter MIB is very important and only works properly to play the role of a true Q3-adapter.

For example, in the case of M-GET delivered from the management system, the Q3-adapter can retrieve the value of NE or access and process only its own MIB. If the state matching problem is not solved in real time, the interface with the NE is inevitable in the case of M-GET, and the operator of the management system may not trust the NE and thus may not achieve the management purpose of the network.

Conventionally, in order to provide an interface with a non-TMN NE through a Q3-adapter, the management system receives management information through a CMIS (Common Management Interface Service) primitive from a management system to form a NE-dependent command to monitor the system through IPC. And controlled.

At this time, the most important part of the management system is the function of generating a command or interpreting the command by ICF (Information Conversion Function), and it is composed of a command parser and a mapping table. Convert directly to NE special command.

Hereinafter, a process of executing an operation of a network management element will be described with reference to FIG. 2.

When the operator interface (GUI) requests the connection of a virtual channel (VC) through the F-interface, the ICF of the management system assembles and generates an M-ACTION command to configure the virtual channel connection request signal as a PDU (Protocol Data Unit). When applied to the NWMF (Network Management Function) through the IPC interface, the NWMF converts the M-ACTION command into an M-ACTION REQUEST command and applies it to the QAF (Q3-Adaptor Function) side of the Q3-adapter through the Q3 interface.

QAF analyzes the authorized M-ACTION REQUEST command, then assembles a Man Machine Command (MMC) or Human Machine Interface (HMI) command via ICF, and then has an M-interface with the structure of header + NE-specific connands & parameters. Pass through to the non-TMN NE.

When the non-TMN NE that received the MMC or HMI through the M-interface executes the received MMC or HMI and transmits the result to the ICF side of the Q3-adapter through the M-interface, the Q3-adapter is M -Analyze the result of MMC or HMI received through the interface and reflect it in the MIB shown in FIG. 1 and form the M-ACTION REPLY command through QAF to form the NWMF side of the management system through the Q3-interface. To transmit.

The operator interface GUI side that analyzes the M-ACTION REPLY command received through the Q3-interface of the management system and reflects it to the MIB, and then acquires the virtual channel occupancy result via the F-interface through the IC-F. To pass on.

The network interface through the conventional Q3-adapter as described above has Q3 primitives and Q3 management information because NE-Special Commands (MMC, HMI) are easily understood by humans and there are hundreds or thousands of kinds or numbers of them. Extracting the relevant commands from and extracting the necessary parameters for the commands has a problem that the developer of the Q3-adapter requires a lot of effort and time.

In addition, since the results obtained by executing the NE special command also have various forms of syntax, parsing the result syntax and extracting desired information also requires a lot of time and effort.

Therefore, when developing a Q3-adapter, the NE software developer has to be put into the development process of the Q3-adapter or maintains a very close relationship.

The present invention has been made in view of the above-mentioned general problems, and its object is to provide a PRI interface structure that enables easy conversion of PREMIDI and Q3 management information, and is independent of work sharing effects and NE development in the development of the Q3-adapter. In addition, it is possible to develop Q3-Adapter, and to provide network interface structure that can implement Q3-Adapter more effectively and use widely when non-TMN NE supports TCP / IP protocol.

1 is a general configuration diagram showing equipment and interface reference points that do not provide a Q3 interface.

2 is a process flow diagram for a conventional network element interface implementation.

3 is a process flow diagram for network element interface execution in accordance with the present invention.

<Explanation of symbols for main parts of drawing>

10: network element 20: Q3-adapter

30: management system

According to the present invention for achieving the above object, when the VC connection request applied through the F-interface is detected in the GUI, the management system assembles and generates an M-ACTION command through the ICF, and then the NWMF side through the IPC interface. The NWMF in the management system processes the M-ACTION command as an M-ACTION REQUEST command and applies it to the QAF side of the Q3-adapter through the Q3 interface, and the QAF in the Q3-adapter is applied. The process of analyzing the ACTION REQUEST command, then assembling it into an RRI command via ICF, then sending it to the non-TMN NE via the M-interface, and the corresponding non TMN NE that received the RRI command via the M-interface are received RRI instructions. After analyzing and executing a combination of NE special instructions, the result is transmitted to the ICF side of the Q3-adapter through the M-interface, and the Q3-adapter receives the execution result from the non-TMN NE. The RRI received through the interface is analyzed and reflected in the MIB, and the analyzed result is formed through the QAF to form the M-ACTION REPLY command and transmitted to the NWMF side of the management system through the Q3-interface. The method includes analyzing the M-ACTION REPLY command received through the Q3-interface, reflecting the result in the MIB, and delivering the result of the requested VC to the GUI through the F-interface.

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

The RRI interface according to the present invention has information shared by the Q3-Adapter and the NE (Shared Management Knowledge), and converts the Q3 primitive and Q3 management information into the RRI primitive and the system ID format and delivers it to the NE through the RRI interface. RRI converts RRI primitives and system ID formats into NE special instructions or executes them directly as control instructions.

The RRI interface of the present invention converts and transfers to a pyritic as shown in Table 1 below for the Q3 primitive.

RRI primitive Corresponding Q3 Primitives Functions of RRI Primitives function MC-INIT none Management Information Initial Data Transfer Q3-Adapter → NE MC-CREATE M-CREATE Add management information Q3 adapter → NENE → Q3- adapter MC-DELETE M-DELETE Delete management information Q3 adapter → NENE → Q3- adapter MC-NOTI M-NOTIFICATION Notification of failure / status / property change NE → Q3-Adapter MC-REPLACE M-SET Change management information Q3-Adapter → NE MC-ACTION M-ACTION Management function processing Q3 Adapter → NE

In addition, the Q3 management information is expressed using the system ID format, which means that the attribute of the MO is assigned to a non-negative integer, so that the attribute of the MO is not used in the NE without using a complex OID. Can be identified.

In this case, the attribute type (Syntax) and the value are represented by the type and value, and the type is {SystemID: Type: Value}, and the types of the types are divided as shown in Table 2 below.

Syntax Types Integer ″ I ″ Float ″ F ″ Characters ″ C ″ Date Time ″ D ″ Structure ″ S ″

Since the system ID is a unique integer assigned to each property, it does not have to deal with unwieldy OIDs.It manages a table that converts OIDs to system IDs in the ICF of the Q3-Adapter. Has a table that converts to commands.

Therefore, the RRI interface has shared management knowledge (Q3-Adapter and NE), converts Q3 primitives and Q3 management information into RRI primitives and system ID formats, and passes them to the NE via the RRI interface. Convert primitives and system ID formats to NE special instructions or execute them directly as control commands.

This will be described with reference to FIG. 3.

When the operator interface (GUI) requests the connection of the virtual channel (VC) through the F-interface, the ICF of the management system assembles and generates the M-ACTION command to configure the virtual channel connection request signal into the CMIP PDU. The NWMF applies the M-ACTION command to the QAF side of the Q3-adapter via the Q3 interface.

The QAF in the Q3-Adapter analyzes the authorized M-ACTION REQUEST command, then assembles it into an RRI command with the structure {Header + {SystemID: Type: Value:} +} via ICF and then via the M-interface. Deliver by non-TMN NE.

As described above, the corresponding non TMN NE receiving the RRI command through the M-interface analyzes the received RRI command and executes a combination of NE special instructions, and then returns the result through the corresponding non TMN NE through the M-interface of the RRI. Management information is transmitted to the ICF side of the Q3-Adapter in the form of {Header + {SystemID: Type: Value:} +}, the Q3-Adapter analyzes the result of the RRI received through the M-Interface and reflects the result in the MIB. The analyzed result is formed through the QAF to form the M-ACTION REPLY command and transmitted to the NWMF side of the management system through the Q3-interface.

The operator interface GUI side that analyzes the M-ACTION REPLY command received through the Q3-interface of the management system and reflects it to the MIB, and then acquires the virtual channel occupancy result via the F-interface through the IC-F. To pass on.

As described above, the present invention facilitates Q3-Adapter development through the RRI interface structure and provides flexibility to the protocol conversion system structure in the future.

In addition, the RRI interface structure according to the present invention can easily perform primitive conversion and Q3 management information expression, and can independently proceed with the development of NE through the division of work during development of the Q3-adapter.

Claims (2)

In the network management element interface method through the Q3-adapter, an M-ACTION command is assembled to configure the VC as a CMIS protocol PDU through the ICF when a VC connection request applied from the GUI through the F-interface is detected. Generating and applying to the NWMF side through the IPC interface; The NWMF in the management system processing the M-ACTION command as an M-ACTION REQUEST command and applying it to the QAF side in the Q3-adapter through the Q3 interface; The QAF in the Q3-adapter analyzes an applied M-ACTION REQUEST command, assembles it into an RRI command through ICF, and then transmits the M-ACN NE to a non-TMN NE through an M-interface; The non TMN NE, which receives the RRI command through the M-interface, analyzes the received RRI command, executes a combination of NE special instructions, and transmits the result to the ICF side of the Q3-adapter through the M-interface. Process; Q3-Adapter, which receives the execution result from the non-TMN NE, analyzes the RRI received through the M-interface and reflects the result in the MIB, and forms the M-ACTION REPLY command through QAF to form the Q3 adapter. Transmitting to the NWMF side of the management system via an interface; The management system includes a process of analyzing the M-ACTION REPLY command received through the Q3-interface and reflecting the result in the MIB, and delivering the result of the requested VC to the GUI through the F-interface. . The method of claim 1, wherein the RRI command comprises a header and a system ID.