KR20040001291A - Server And Method For Interworking System In Network Element Management - Google Patents

Abstract

PURPOSE: A system interworking server in an EMS(Element Management System) and a method therefor are provided to achieve interworking with network elements only through the modification of an access protocol file, without modifying a program, by creating and processing a thread for each node whenever a node is added, regardless of the number and kind of network elements. CONSTITUTION: An EMS based on CORBA environments consists of a management server(400) and a system interworking server(500). The management server(400) obtains network element management information for a plurality of network elements(600), and operates controls, and manages the network elements(600). The system interworking server(500) to interface the management server(400) with the network elements(600) collects network element management information from the network elements(600), converts relevant network management information in a suitable form, and provides it to the management server(400).

Description

Server And Method For Interworking System In Network Element Management

The present invention relates to a device interworking server and method in a network element management system, and in particular, a device interworking server in a network element management system (EMS: Element Management System) based on a CORBA (Common Object Request Broker) environment Network element management system that enables device interworking server to efficiently interwork between management server and network element by collecting network element management information necessary for overall maintenance and management function of network from network element (NE) The present invention relates to a device interworking server and method.

In general, Kovar refers to a common object request mediator structure, established by the Object Management Group (OMG), a non-profit organization that promotes the dissemination and standardization of object-oriented technologies, and mediates communication between objects in a distributed system environment. Refers to the standard specification of an object request broker (ORB), and network element management refers to real-time network monitoring and control for optimizing network performance in terms of operation of network elements, or configuration management information of the network element. B. It refers to performing network operation and maintenance by collecting performance management information or failure management information.

Hereinafter, a general configuration of network element management will be described with reference to FIG. 1.

1 is a block diagram showing a general configuration of network element management.

The general configuration of network element management includes a network element management system that performs a network element management function based on a COVA environment by including a management server and a device interworking server that links the management server with the network element, and the network element management system. It consists of network elements managed by.

Hereinafter, a network element management system to which a conventional device interworking server is applied will be described with reference to FIG. 2.

2 is a block diagram illustrating that a management server and a network element interoperate with each other through a device interworking server in a conventional network element management system.

The network element management system to which the conventional device interworking server 200 is applied includes a management server 100 for operating and controlling and managing a plurality of network elements 300 to be management subjects and the management server 100. By interworking with a plurality of network elements 300 receives the control command of the management server 100 through the management server interface 210 to the corresponding network element 300 through the network element interface 220. Device interworking server for delivering or transmitting the network element management information transmitted from the network element 300 through the network element interface 220 to the management server 100 through the management server interface 210 ( 200). Here, the network element 300 refers to equipment to be managed, such as a router, a switching hub, or an ATM switch.

The management server interface unit 210 includes a configuration information processor 211 for processing configuration information about the network element 300, a failure information processor 212 for processing failure information for the network element 300, and a network. It has a performance information processor 213 for processing the performance information for the element 300, receives the control command for the network element 300 from the management server 100 and delivers it to the network element interface unit 220 The network element management information of the configuration information, the fault information, and the performance information collected from the corresponding network element 300 is received through the network element interface unit 220 and transmitted to the management server 100.

In addition, the network element interface unit 220 includes a configuration information processor 222 for processing configuration information about the network element 300 and a failure information processor 223 for processing failure information for the network element 300. A plurality of network element interface modules 221 having a performance information processor 224 for processing performance information about the element 300 and having one-to-one correspondence with each network element 300 according to the characteristics of the network element 300. Including, a control command for the network element 300 from the management server interface unit 210 is received through the network element interface module 221 corresponding to the network element 300 in the corresponding network element 300 The management server interface unit 210 collects network element management information of configuration information, fault information, and performance information and transmits the collected network element management information to the network element interface module 221 corresponding to the network element 600. in To pass.

As described above, the management server interface unit 210 includes a configuration information processor 211, a failure information processor 212, and a performance information processor 213 that process configuration information, failure information, and performance information, respectively. A plurality of network element interface modules 221 in the element interface unit 220 may include a configuration information processor 222, a failure information processor 223, and a performance information processor 224, which process configuration information, failure information, and performance information, respectively. In the related art, one processor 211, 212, 213, 222, 223, and 224 should all be in charge of processing an event from the network element 300 and a control command from the management server 100. In addition, when management of additional nodes is required during system operation, the node connection information is generated and the management server interface unit 210 and the network element interface unit 220 of the device interworking server 200 are restarted to recognize the node. Since the network element interface module 221 corresponding to the network element 300 is different according to the characteristics of the network element 300, the network element interface module 221 for each network element must be recoated.

Therefore, in the related art, a network element always needs to process control commands from the three processors and process events, that is, network element management information for the corresponding network element, and has to perform an inefficient operation. Because it needs to receive and process network element management information and process control commands at the same time, the processing speed was slowed and there was a possibility of losing network element management information. When adding or deleting new network elements, it was difficult to apply them to the management server. As a result, it was difficult to apply the test directly to the network when developing or maintaining the network element.

In order to solve the problems described above, an object of the present invention is to create and process a thread for each node whenever a node is added, regardless of the number and type of network elements, thereby interworking with the network element. In this way, it is possible to interwork by modifying the connection protocol file without modifying the program.

Another object of the present invention is to provide a separate network processor for each function, such as a state management module, a performance management module and an MMC interface module, so that the network element management information for a specific function when not configured for each function can be used. Minimize processing speed and loss of management information due to load.

It is still another object of the present invention to process each processing routine separately according to the characteristics of the network element management information to facilitate maintenance related to the interface with the network element according to the addition of the network element.

1 is a diagram showing a general configuration of network element management.

2 is a block diagram showing that a management server and a network element interoperate with each other through a device interworking server in a conventional network element management system.

3 is a block diagram illustrating that a management server and a network element interoperate with each other through a device interworking server in a network element management system according to an embodiment of the present invention.

4 is a diagram illustrating a packet structure table for interworking with devices.

FIG. 5 is a diagram showing an operation definition table of a packet type in FIG. 4; FIG.

6 is a diagram illustrating an initial connection information table of a network element interface unit.

7 is a flowchart illustrating a device interworking method in a network element management system according to an embodiment of the present invention.

FIG. 8 is a flowchart illustrating a process of processing an event from a network element in FIG. 7; FIG.

FIG. 9 is a flowchart illustrating a processing process when a COVA object is called from a management server in FIG. 7. FIG.

Explanation of symbols on the main parts of the drawings

400: management server 500: device interworking server

510: management server interface unit 511: event management module

512: control management module 520: network element interface unit

521: state management module 522: performance management module

523: MMC interface module 600: network element

In order to solve the above object, in the network element management system of the present invention, the device interlocking server in the network element management system having a device interlocking server for interworking a management server and a plurality of network elements, the device interlocking server is A network element interface unit configured to interface with the network element to collect and transmit network element management information; After calling the COVA object, the network element management information received from the network element interface unit is converted and returned to the management server, or when the registered COVA object is called, converted to MMC form and transmitted to the network element interface unit and then the network. And a management server interface unit converting the network element management information received from the element interface unit and returning it to the management server.

The device interworking method in the network element management system of the present invention is a network element management system having a device interworking server for interworking a plurality of network elements with a management server. Determining whether to process a COVA object from a call; In the event of event occurrence from the network element, calling a COVA object to analyze an input parameter value, receiving network element management information, and converting the result into an output parameter value of the COVA object; In the case of processing a COVA object call from the management server, if the corresponding COVA object is called after registering the COBA object, the input parameter value is analyzed and converted into MMC format and transmitted, and the network element management information is received and received. And converting the result into an output parameter value.

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

First, a network element management system to which a device interworking server according to an embodiment of the present invention is applied will be described with reference to FIG. 3.

3 is a block diagram illustrating that a management server and a network element interoperate with each other through a device interworking server in a network element management system according to an exemplary embodiment of the present invention.

The network element management system to which the device interworking server 500 is applied according to an exemplary embodiment of the present invention receives the network element management information for a plurality of network elements 600 to be managed as a management entity and corresponding network elements. Network element management required for network element management from the network element 600 by interlocking the management server 400 for operating control and management 600, the management server 400 and a plurality of network elements 600 And a device interworking server 500 which collects the information, converts the network element management information into an appropriate form, and provides the management server 400 to the management server 400. At this time, the network element management system is based on the COVA environment.

Here, the device interworking server 500 collects network element management information from the network element 600 by performing an interface with the network element 600 and then converts the network element management information to facilitate conversion of the network element management information. The network element interface unit 520 for transmitting the collected data for each characteristic of the caller and the COVA object registered in the management server 400 are analyzed to analyze input parameter values, and then, from the network element interface unit 520. Convert the received network element management information into an output parameter value of the COVA object and return it to the management server 400 or register the COBA object for each network element management information according to the network element 600 and then manage the management. When the COVA object is called from the server 400, the input parameter value is analyzed and converted into MMC (Man Machine Communication) form and then transmitted to the network element interface unit 520. It converts the network element management information transmitted from the network-based interface element 520 as an output parameter value of the object Kovar comprises a management server interface unit 510 to return to the management server 400.

Here, the network element interface unit 520 collects network element management information (alarm, fault and status message) related to the state of the network element 600 from the network element 600. A state management module (FGU) for transmitting the collected data to the management server interface 510 and periodically checking the connection state of the network element 600 to report whether the connection is to the management server interface 510. Fault Gateway Unit 521 and the network element management information (performance message) related to the network element 600 are collected from the network element 600, and the corresponding data is transmitted to the management server interface 510. And a state management module (SGU: Statistics Gateway Unit) 522 for periodically checking a connection state of the network element 600 and reporting whether it is connected to the management server interface unit 510, and related to network element management information. MMC For this purpose, the MMC type control command received from the management server interface unit 510 is transmitted to the network element 600 and the network element management information of the corresponding network element 600 is collected to manage the management server interface unit 510. MMC interface module (TGU: Transmit Gateway Unit) 523 which transmits the collected data and periodically checks the connection state of the network element 600 and reports whether it is connected to the management server interface unit 510. It is made to include.

The management server interface 510 receives network element management information from the state management module 521 and the performance management module 522 and calls a COVA object registered in the management server 400 to output an output parameter value. Event management module 511 which converts to the management server 400 and returns to the management server 400 and COBA IDL (Interface Definition Language) interface for each network element management information to register a COVA object and then applies the COVA to the management server 400. When the object is called, the input parameter value of the called COVA object is extracted, converted into an MMC for collecting network element management information, and then transmitted to the MMC interface module 523 and received from the MMC interface module 523. The control management module 512 converts network element management information into an output parameter value of the called COVA object and returns it to the management server 400. It is made to include.

In the interface between the management server 400 and the management server interface 510 of the device interworking server 500, a COVA interface is used, and the management server interface 510 of the device interworking server 500 and the network element interface unit ( A UDP protocol (User Datagram Protocal) is used in the interface between 520 and the state management module 521 and the performance management module 522 which are sub-modules in the management server interface 510 and the network element interface 520. Each of the MMC interface modules 523 has a unique port. The MMC interface modules 523 communicate with each other through a packet of a previously promised structure shown in FIG. 4. 4 is a diagram illustrating a packet structure table for interworking with devices. The packet type (Ptype) of FIG. 4 is represented by an operation shown in FIG. 5, and FIG. 5 is a diagram illustrating an operation definition table of a packet type in FIG. 4.

In addition, a TCP / IP protocol (Transmission Control Protocol / Internet Protocol) is used in the interface between the network element interface unit 520 and the network element 600 of the device interworking server 500, and the network element interface unit 520 is used. Is a socket client and the network element 600 is configured as a socket server. The network element interface unit 520 includes a state management module 521, a performance management module 522, and an MMC interface module 523, that is, modules divided by functions, each having a socket port. It communicates with each other via a packet of a structure promised in advance with the illustrated network element 600.

In addition, the device interworking server 500 may provide connection protocol configuration information between the management server interface unit 510 and the network element interface unit 520 and between the network element interface unit 520 and the network element 600 at initial startup. The access protocol configuration information should be in the form of a file as shown in FIG. 6 is a diagram illustrating an initial access information table of the network element interface unit 520. The table of FIG. 6 is configured as one file by the number of network elements 600.

The event management module 511 may add a node additional information to the file in the network element interface unit 520 by placing a temporary file for node addition information (Node ID) according to the node addition during operation. Each time the file is checked, a thread is created for each node, and a message transceiving procedure and a data conversion procedure with the network element interface unit 520 are performed in each generated thread.

In addition, the control management module 512 declares and registers a COVA object to process the COVA object in a multi-threaded format when the management server 400 calls it, and simultaneously transmits a message to the network element interface unit 520. And data conversion procedures are handled by each thread object.

Hereinafter, a device interworking method in a network element management system according to an embodiment of the present invention will be described with reference to FIG. 7.

7 is a flowchart illustrating a device interworking method in a network element management system according to an embodiment of the present invention.

First, the device interworking server 500 determines whether a process occurs when an event is generated from the network element 600 or when a COVA object is called by the management server 400 (S701). Here, event occurrence means that network element management information has occurred in the network element 600.

In this case, in the event of event generation from the fraudulent network element 600, the management server interface unit 510 of the device interworking server 500 calls the COVA object registered in the management server 400 to input an input parameter value. After the analysis, the network element management information is received from the network element interface unit 520 and converted to an output parameter value of the COVA object, and returned to the management server 400 (S702).

On the other hand, in the case of processing the call of the coba object from the management server 400, the management server interface unit 510 of the device interworking server 500 is a coba object for each network element management information according to the network element 600 After registering the COVA object from the management server 400, the input parameter value is analyzed and converted into MMC form and transmitted to the network element interface unit 520, and the network element management information from the corresponding network element interface unit 520. The received and converted to the output parameter value of the COVA object and returns to the management server 400 (S703). That is, the device interworking method in the network element management system according to an embodiment of the present invention is divided into a process of generating an event from the network element 600 and a process of calling a COVA object from the management server 400.

Hereinafter, a process of generating an event from the network element 600 will be described with reference to FIG. 8.

8 is a flowchart illustrating a process of processing an event from a network element in FIG. 7.

First, the state management module 521 and the performance management module 522 of the network element interface unit 520 have the connection protocol configuration information as shown in FIG. 6 and establish a TCP socket connection to the network element 600. Connect [TCP]) and generates a UDP socket for communication with the event management module 511 of the management server interface unit 510 (UDP socket open).

Accordingly, when the network element 600 receives the TCP socket connection establishment request and accepts the corresponding TCP socket connection establishment (S803), the state management module 521 and the performance management module 522 are node information. (NodeID) is added to the node addition information temporary file of the event management module 511 (NodeID file append).

Accordingly, the event management module 511 checks the added node addition information and creates a thread (Threadcreate [NodeID]) for data conversion and interface for the additional node (S805), and the state management module 521 And a UDP socket for communication with the performance management module 522 (S806).

Accordingly, the state management module 521 and the performance management module 522, after completing the TCP socket setting with the network element 600, the nucleus value of the transmission and reception preparation confirmation (PortTypeConfirm) operation to confirm the message transmission and reception preparation procedure The packet is allocated to the packet type region of the packet and then transmitted to the network element 600 through the socket (S807). In this case, the transmission and reception preparation confirmation (PortTypeConfirm) operation is transmitted from the state management module 521 and the performance management module 522 of the device interworking server 500 to the network element 600 to confirm the preparation procedure.

Accordingly, the network element 600 receives the transmission / reception ready operation packet and allocates a nucleus value of the transmission / reception preparation confirmation response (PortTypeConfirmAck) operation to the packet type region of the packet through the socket after the message transmission / reception preparation procedure is completed. The state management module 521 and the performance management module 522 are transmitted (S808). Accordingly, the state management module 521 and the performance management module 522 that have received the transmission / reception ready acknowledgment operation packet wait for receiving a message from the network element 600. Here, the transmission / reception ready response (PortTypeConfirmAck) operation is a response message of the transmission / reception ready confirmation (PortTypeConfirm) operation.

The network element 600 allocates a nucleus value of an output message (OutputMsg) operation to a packet type region of a packet, assigns a status message and a performance message to a data region as a string value, and then sizes the data message. The data is transmitted to the state management module 521 and the performance management module 522 in the data length region (S809). Here, the output message (OutputMsg) operation carries network element management information when transmitting data.

Accordingly, after receiving the output message operation packet, the state management module 521 and the performance management module 522 extract and store actual network element management information allocated to the data area (S810), and output the output message. When reception is completed, the file is read and transmitted to the event management module 511 through a UDP socket (S811). In this case, the state management module 521 and the performance management module 522 check a segment indicator region of the output message operation packet to check whether the packet is a divided packet, and in the case of the divided packet, split the output message. Wait for all packets to be received. Here, the segment indicator is used to inform segmentation transmission when one output message exceeds the packet size.

Accordingly, the event management module 511 receives the output message and calls the COVA object registered in the management server 400 (S812), and then converts the received output message to the output parameter of the corresponding COVA object. After assigning a value (S813), the called COVA object is returned to the management server 400 (S814).

In addition, during the process of generating an event from the network element 600, the state management module 521 and the performance management module 522 periodically check a connection state with the network element 600 to determine whether to connect the event. Report to management module 511.

That is, the state management module 521 and the performance management module 522 periodically check the connection state with the network element 600, and when the message transmission / reception procedure is not performed with the network element 600 for a predetermined time. Assigns a nucleus value of an access status check (AppStatusCheck) operation to the packet type region of the packet, and transmits it to the network element 600. Here, the AppStatusCheck operation may be performed by the status management module 521 and the performance management module 522 of the device interworking server 500 to confirm the connection status with the network element 600. 600).

In this case, when the connection status check acknowledgment (AppStatusCheckAck) operation packet is not received from the network element 600 that has received the connection status check operation packet, the status management module 521 and the performance management module 522 After reporting the disconnected state to the event management module 511, it attempts to reconnect with the network element 600. Here, the connection status check check response (AppStatusCheckAck) operation is a response message of the connection status check check (AppStatusCheckAck) operation.

On the other hand, when receiving a connection status check acknowledgment (AppStatusCheckAck) operation packet from the network element 600 receiving the connection status check operation packet, the status management module 521 and the performance management module 522 The connection status is reported to the event management module 511.

Hereinafter, a process of calling a COVA object from the management server 400 will be described with reference to FIG. 9.

FIG. 9 is a flowchart illustrating a process of calling a COVA object from a management server in FIG. 4.

First, the MMC interface module 523 of the network element interface unit 520 requests a TCP socket connection establishment (Connect [TCP]) to the network element 600 with the connection protocol configuration information as shown in FIG. 6. In operation S901, a UDP socket for communication with the control management module 512 of the management server interface unit 510 is generated (UDP socket open).

The control management module 512 registers a CORBA object in a multi-threaded format for each network element management information required for network element management (S903).

Accordingly, when the network element 600 receives the TCP socket connection establishment request and accepts the corresponding TCP socket connection establishment (S904), the MMC interface module 523 transmits and receives to confirm a message transmission preparation procedure. After allocating the nucleus value of the preparation confirmation (PortTypeConfirm) operation to the packet type (Ptype) region of the packet, it transmits to the network element 600 through the socket (S905). In this case, the transmission and reception preparation confirmation (PortTypeConfirm) operation is transmitted from the MMC interface module 523 of the device interworking server 500 to the network element 600 to confirm the transmission and reception preparation procedure.

Accordingly, the network element 600 receives the transmission / reception ready operation packet and allocates a nucleus value of the transmission / reception preparation confirmation response (PortTypeConfirmAck) operation to the packet type region of the packet through the socket after the message transmission / reception preparation procedure is completed. It transmits to the MMC interface module 523 (S906). Here, the transmission / reception preparation confirmation (PortTypeConfirmAck) operation is a response message of the transmission / reception preparation confirmation (PortTypeConfirm) operation.

Accordingly, when the control management module 512 receives a call of a specific COBA object registered in the control management module 512 for the management operation from the management server 400 (S907), the MMC interface A UDP socket for communication with the module 523 is created (UDP socket open) (S908).

Then, the control management module 512 allocates the value of the input parameter of the called COVA object as a parameter of a specific MMC and transmits it to the MMC interface module 523 through a socket (S909).

Accordingly, the MMC interface module 523 assigns a nucleus value of an InputCommand operation to a packet type region of a packet and receives an actual MMC string in a data region to receive the transmitted MMC and request an MMC. After assigning the value to the network element 600 through the socket (S910). In this case, the InputCommand operation is a command transmitted from the MMC interface module 523 of the device interworking server 500 to the network element 600 when the MMC is requested.

Accordingly, the network element 600 receives an MMC request by receiving the input command operation packet, allocates a nucleus value of an InputCommandAck operation to the packet type region of the packet, and then connects the MMC interface module through a socket. In operation S 911, the mobile terminal transmits to step 523. Accordingly, the MMC interface module 523 receiving the input command response operation packet waits for receiving a message from the network element 600. Here, the input command response operation InputCommandAck is a response message of the input command operation.

The network element 600 allocates a nucleus value of an output message (OutputMsg) operation to a packet type region of a packet, assigns a response message for an MMC to a data region as a string value, and then converts the size of the data message to a data length ( Length) is transmitted to the MMC interface module 523 (S912). Here, the output message (OutputMsg) operation carries network element management information when transmitting data.

Accordingly, after receiving the output message operation packet, the MMC interface module 523 extracts and stores network element management information, which is a message in a string form, as a result value for the actual MMC allocated to the data area (S913). When the reception of the output message is completed, the corresponding file is read and transmitted to the control management module 512 through the UDP socket (S914). At this time, the control management module 512 checks whether the segmentation indicator region of the output message operation packet is a segmentation packet and waits until all segmentation packets for one output message are received. . Here, the segment indicator is used to inform segmentation transmission when one output message exceeds the packet size.

Accordingly, the control management module 512 receives the output message and converts the received output message to an output parameter of the COVA object registered in the control management module 512 to allocate a value (S915). The called COVA object is returned to the management server 400 (S916).

In addition, the MMC interface module 523 periodically checks the connection state with the network element 600 during the process of invoking the COVA object from the management server 400, and determines whether the connection is performed by the event management module 511. Report as.

That is, when the connection status with the network element 600 is periodically checked, when the message transmission / reception procedure is not performed with the network element 600 for a predetermined time, the MMC interface module 523 checks the connection status (AppStatusCheck). After assigning the nucleus value of the operation to the packet type region of the packet and transmits to the network element 600. Here, the AppStatusCheck operation is to transmit from the MMC interface module 523 of the device interworking server 500 to the network element 600 in order to confirm the connection status with the network element 600.

In this case, when the connection status check acknowledgment (AppStatusCheckAck) operation packet is not received from the network element 600 that has received the connection status check operation packet, the MMC interface module 523 is the event management module 511. After reporting the disconnected status, the network element 600 attempts to reconnect. Here, the connection status check check response (AppStatusCheckAck) operation is a response message of the connection status check check (AppStatusCheckAck) operation.

On the other hand, when receiving a connection status check acknowledgment (AppStatusCheckAck) operation packet from the network element 600 receiving the connection status check operation packet, the MMC interface module 523 is the event management module 511. Report the Connect Status.

In addition, the embodiment according to the present invention is not limited to the above-mentioned, and can be implemented by various alternatives, modifications, and changes within the scope apparent to those skilled in the art.

As described above, the present invention is configured to generate and process a thread for each node whenever a node is added, regardless of the number and type of network elements, so that the connection protocol file can be modified without program modification in interworking with the network elements. The network element management information for a specific function when it is not configured for each function can be made by interworking only by modifying it, and by setting a processor by function such as a state management module, a performance management module, and an MMC interface module. The processing speed can be minimized due to the load during processing and network element management information loss can be minimized, and each processing routine is processed separately according to the characteristics of the network element management information. The associated maintenance can be facilitated.

Claims (20)

In a network element management system having a device interworking server for interworking a management server and a plurality of network elements, The device interworking server, A network element interface unit configured to interface with the network element to collect and transmit network element management information; After calling the COVA object, the network element management information received from the network element interface unit is converted and returned to the management server, or when the registered COVA object is called, converted to MMC form and transmitted to the network element interface unit and then the network. And a management server interface unit for converting network element management information received from the element interface unit to return to the management server. The method of claim 1, The network element interface unit, A state management module which collects state related network element management information from the network element and transmits the state related network element management information to the management server interface unit and periodically checks the connection state of the network element and reports whether it is connected to the management server interface unit; Collecting and transmitting performance related network element management information from the network element to the management server interface unit and periodically checking a connection state of the network element to report whether the connection is to the management server interface unit; The MMC type control command received from the management server interface unit is transmitted to the network element, network element management information is collected and transmitted to the management server interface unit, and the connection state of the network element is periodically checked to determine whether the connection is made. Device interworking server in the network element management system, characterized in that it comprises an MMC interface module to report to the interface. The method of claim 1, The management server interface unit, An event management module which receives network element management information from the state management module and the performance management module, calls the COVA object, converts it into an output parameter value, and returns it to the management server; When the COVA object is registered and the COVA object is called by the management server, the input parameter value of the called COBA object is extracted, converted into an MMC for collecting network element management information, and then transmitted to the MMC interface module and the corresponding MMC. And a control management module for converting network element management information received from an interface module into an output parameter value of the called COVA object and returning it to the management server. In a network element management system having a device interworking server for interworking a management server and a plurality of network elements, Determining whether the processing occurs when an event from the network element occurs or when a COVA object is called from the management server; In the event of event occurrence from the network element, calling a COVA object to analyze an input parameter value, receiving network element management information, and converting the result into an output parameter value of the COVA object; In the case of processing a COVA object call from the management server, if the corresponding COVA object is called after registering the COBA object, the input parameter value is analyzed and converted into MMC format and transmitted, and the network element management information is received and received. Device interworking method in the network element management system comprising the step of converting and returning to the output parameter value. The method of claim 4, wherein When an event occurs from the network element, Establishing a socket with the connection protocol configuration information, adding node information, and creating a thread for the additional node; Confirming a message transmission and reception preparation procedure by transmitting a transmission and reception preparation confirmation operation packet through the set socket; Extracting and storing network element management information from an output message operation packet after the message transmission / reception preparation procedure is completed; And invoking a COVA object, converting the output message to an output parameter of the corresponding COVA object, allocating the output message, and returning the same. The method of claim 5, Setting the socket and creating a thread, Requesting to establish a TCP socket connection to the network element with the connection protocol configuration information, and creating a UDP socket for communication with an event management module; If the network element accepts the TCP socket connection establishment, adding node information to a node addition information temporary file of the event management module; Device for the network element management system comprising the step of generating a thread for the additional node by checking the added node additional information, and generating a UDP socket for communication with the state management module and the performance management module Interlock method. The method of claim 5, Checking the transmission and reception preparation procedure, Allocating a nucleus value of a transmission / reception ready operation to a packet type region of a packet to confirm the preparation procedure for transmitting and receiving the message, and then transmitting it to the network element through a socket; And assigning a nucleus value of the transmission / reception ready acknowledgment operation to the packet type region of the packet to transmit the message to the state management module and the performance management module through a socket. How to link devices in element management systems. The method of claim 5, Extracting and storing the network element management information, After assigning the nucleus value of the output message operation to the packet type area of the packet, assigning the status message and the performance message to the data area as a string value, the size of the data message is transmitted to the status management module and the performance management module. Making a step; After receiving the output message operation packet, extract the actual network element management information allocated to the data area and store it as a file, and when the reception of the output message is completed, read the file and transmit it to the event management module through a UDP socket. Device interworking method in a network element management system, characterized in that consisting of. In claim 5, Calling and returning the COVA object, After receiving the output message and calling a COVA object registered in the management server, converting the received output message to an output parameter of the corresponding COVA object, assigning a value, and then calling the called COBA object to the management server. Device interworking method in a network element management system, characterized in that for returning. The method of claim 5, When an event occurs from the network element, Periodically checking a connection state with the network element and reporting whether the connection is made to the event management module. The method of claim 10, Checking and reporting the connection state with the network element, Periodically checks the connection state with the network element, and if the message transmission and reception procedure with the network element is not performed for a predetermined time, assigning the nucleus value of the connection state check operation to the packet type region of the packet to the network element Transmitting; If a connection status check acknowledgment operation packet is not received from the network element, reporting a connection status to the event management module and attempting to reconnect with the network element; And reporting a connection status to the event management module when a connection status check acknowledgment operation packet is received from the network element. The method of claim 4, wherein The process of invoking a COVA object from the management server, Registering a KOVA object of a multi-threaded type by setting a socket with the connection protocol configuration information; Confirming a message transmission and reception preparation procedure by transmitting a transmission and reception preparation confirmation operation packet through the set socket; Receiving the call of the registered COVA object and assigning an input parameter of the corresponding COVA object as a parameter of MMC; Requesting the MMC by transmitting an input command operation packet after receiving the MMC; Extracting and storing network element management information from an output message operation packet in response to the requested MMC; And converting the output message into an output parameter of the called COVA object and allocating the output message and returning the output message. The method of claim 12, Setting the socket and registering the COVA object, Requesting to establish a TCP socket connection to the network element with the connection protocol configuration information and creating a UDP socket for communication with a control management module; The method of interworking a device in a network element management system, comprising the step of registering a multi-threaded COVA object for each network element management information required for network element management. The method of claim 12, Checking the transmission and reception preparation procedure, If the network element accepts the TCP socket connection setting, allocating a nucleus value of a transmit / receive preparation check operation to a packet type region of a packet to confirm the preparation procedure for transmitting and receiving a message, and then transmitting to the network element through a socket; ; In the network element management system comprising the step of assigning the nucleus value of the transmission and reception preparation confirmation response operation to the MMC interface module through the socket after the message transmission preparation preparation procedure is completed. How to link devices. The method of claim 12, Receiving a call of the COVA object and assigning an input parameter, Generating a UDP socket for communication with the MMC interface module when receiving a call of a specific COVA object registered in the control management module from the management server; And assigning a value of an input parameter of the called COVA object as a parameter of a specific MMC and transmitting the value to an MMC interface module through a socket. The method of claim 12, The requesting the MMC, Receiving the transmitted MMC and assigning a nucleus value of an input command operation to a packet type region of a packet and assigning an actual MMC as a string value to a data region to request the MMC, and then transmitting to the network element through a socket; ; And receiving the input command operation packet and assigning a nucleus value of an input command response operation to the packet type region of the packet to transmit the received MMC request to the MMC interface module through a socket. Device interworking method in network element management system. The method of claim 12, Extracting and storing the network element management information, Assigning a nucleus value of an output message operation to a packet type region of a packet, assigning a response message to the MMC as a string value in a data region, and transmitting the size of the data message to the data length region to the MMC interface module; ; After receiving the output message operation packet, the network element management information, which is a string message, is extracted and stored as a result value for the actual MMC allocated to the data area, and when the output message is received, the corresponding file is read. The method of interlocking a device in a network element management system comprising the step of transmitting to the control management module via a UDP socket. The method of claim 12, Returning the called COVA object, Receiving the output message, converting the received output message to an output parameter of a COVA object registered in the control management module, assigning a value, and returning the called COVA object to the management server How to link devices in element management systems. The method of claim 12, The process of invoking a COVA object from the management server, Periodically checking a connection state with the network element and reporting whether the connection is made to the event management module. The method of claim 19, Checking and reporting the connection state with the network element, Periodically checks the connection state with the network element, and if the message transmission and reception procedure with the network element is not performed for a predetermined time, assigning the nucleus value of the connection state check operation to the packet type region of the packet to the network element Transmitting; If a connection status check acknowledgment operation packet is not received from the network element, reporting a connection status to the event management module and attempting to reconnect with the network element; And reporting a connection status to the event management module when a connection status check acknowledgment operation packet is received from the network element.