KR100357867B1 - Managing method of a plurality of q3-adapter management agent system - Google Patents

Abstract

The present invention relates to a method of managing Q3-Adapter Management Agent Systems, comprising: a process manager for managing the Q3-Adapter Management Agent system in advance, so that the process manager is a NON_TMN network manager when a network component system of the NON_TMN environment is created. The Q3-Adapter Management Agent system is generated according to the signal generated from the system, and the process manager deletes the Q3-Adapter Management Agent system when the network component system of the NON_TMN environment is deleted.

Description

MANAGING METHOD OF A PLURALITY OF Q3-ADAPTER MANAGEMENT AGENT SYSTEM}

The present invention must exist in order to convert a network component composed of a non-telecommunication management network (NON_TMN) environment and a network management system managing the network components into a telecommunication management network (TMN) environment. The present invention relates to a technique for efficiently handling operations among multiple processes. In particular, the present invention relates to a time-critical method when the Q3-Adapter management agent system per network component of a NON_TMN environment operates organically between the two devices when operating as a bundle. Since it is a variable, it can be applied when you want to handle it automatically instead of manually to minimize the information loss caused by quick recovery.

In general, an OAM system that manages a network element (NE) is managed using a man-machine language (MML). These interfaces, which are available to all NEs, vary by vendor-specific system, and it's not easy to know and manage all of these MMLs where you need to manage different types of systems, such as network management centers. In this necessity, agents representing the system emerged, and agents of each system express the logical and physical resources of the NE in a standardized manner and execute the manager's request according to a predetermined agreement with the manager. Or, in order to provide an interface in the form of a GUI (Graphic User Interface) for the operator to use, MML analysis is required for each MML meaning and necessary operation. Therefore, one of the important roles of these applications is the ability to analyze system-dependant MML and convert it to perform the desired behavior.

In implementing agents (CMIP, SNMP, etc.) that support various protocols, or implementing GUI applications, each of them must communicate with the NE to parse and process messages to obtain the data they need. There is redundancy and inefficiency in doing the same thing many times in terms of implementation. In addition, the change of MML in NE means the change of each application, requiring modification of redundant functions, which makes the maintenance of each application difficult and difficult to manage.

1 is an overall block diagram of a conventional TMN management agent system. Referring to FIG. 1, the development of the Q3-adapter management agent systems 112, 114, and 116 to date is 1: 1 with the network manager system 300 of the NON_TMN environment that manages a plurality of network management element systems of the NON_TMN environment. Or mapped to a 1: N relationship. At this time, the initialization of the Q3-adapter management agent system (112, 114, 116) is sent when the network management element system (402, 404, 406) of the NON_TMN environment is running while the process corresponding to the system is already running. Q3-Adapter management agent system 112, through the signal and polling (signal) sent through the path [1-4]-> [1-3]-> [1-2] shown in FIG. 114/116 are created / deleted. In addition, the information required for initialization is transferred from the network manager system 200 of the NON_TMN environment when the network management element systems 402, 404, and 406 of the NON_TMN environment are generated or offline, and the generation signal is received in advance. Start initialization as soon as possible. In addition, the occurrence of a problem due to abnormal termination of the Q3-adapter management agent system 112, 114, and 116 during operation can be detected only by polling the TMN network manager system 200 or polling the network manager system 300 in a NON_TMN environment. Can be.

Thus, to date, the Q3-Adapter Management Agent system 112, 114, and 116 incurs an overhead in which a process must always be running regardless of the generation of the NON_TMN network component system 402, 404, and 406 mapped to it. do. That is, if the corresponding TMN network manager system 300 manages 10 network management equipment, 10 processes should always be run regardless of creation and deletion of the NON_TMN network component system. Also, when the Q3-adapter management agent system 112, 114, or 116 is abnormally terminated during operation, information on abnormal termination of the corresponding process may be known by polling the TMN network manager system 200 or the NON_TMN network manager system 300. Due to the time difference from abnormal termination to the time detected by polling, when the Q3-Adapter Manager system starts up again, information inconsistency between the Q3-Adapter Management Agent system and the network component system of the NON_TMN environment occurs.

Accordingly, an object of the present invention is to provide a plurality of Q3-adapter management agent systems that can reduce the overhead caused by the process always running regardless of the generation of the NON_TMN network component system to which the Q3-adapter management agent system is mapped. To provide a way to manage them.

Another object of the present invention is to detect information on abnormal termination of a process when abnormal termination of the Q3-adapter management agent system, and to minimize the time taken for recovery Q3-Adapter management agent system that can promote the efficiency of the overall system operation To provide a way to manage them.

In order to achieve the above object, the present invention provides a process manager to solve the problem of overhead and information inconsistency of the idle process in the management method of the Q3-adapter management agent systems. When the element system is created, the process manager receives the signal for creation from the NON_TMN network manager system and creates a Q3-Adapter management agent system. Also, when the network component system of the NON_TMN environment is deleted from the network diagram, the process manager The Q3-Adapter Management Agent system is deleted, and upon abnormal termination of the Q3-Adapter Management Agent system, the Q3-Adapter Management Agent system can be driven immediately by automatic reporting of the operating system.

1 is an overall block diagram of a conventional TMN management agent system.

2 is a block diagram of an entire TMN management agent system equipped with a process manager according to an embodiment of the present invention.

3 and 4 are flowcharts of a processing procedure for reducing process overhead through a process manager according to an embodiment of the present invention.

5 is a flowchart of a regeneration process of the Q3-adapter management agent system for efficient management of the TMN management agent system through automatic detection at abnormal termination of the Q3-adapter management agent system.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description, specific details such as specific components are shown, which are provided to help a more general understanding of the present invention, and it is understood that these specific details may be changed or changed within the scope of the present invention. It is self-evident to those of ordinary knowledge in Esau.

2 is a block diagram of an entire TMN management agent system equipped with a process manager according to an embodiment of the present invention. 2 is a diagram illustrating the overall structure of the plurality of Q3-adapter management agent systems. The process manager 130 and the plurality of Q3- controlling the generation / deletion and abnormal termination of each Q3-adapter management agent system 110 are illustrated in FIG. The adapter management agent systems 110 may include a message conversion block 120 for converting information of the TMN environment into information of the NON_TMN environment or converting information of the NON_TMN environment to information of the TMN environment.

Referring to FIG. 2, in the method of using process management by polling during initialization and operation among a plurality of processes as shown in FIG. In order to prevent efficiency loss, the present invention introduces the concept of a process manager 130. The process manager 130 is responsible for the initialization process used in the existing NON_TMN network manager system 300, the message conversion block 120 and the Q3-adapter management agent system 110 by the following operation.

Through the process manager 130, first, the corresponding Q3-adapter management agent system 110 is generated when the NON_TMN network component system 400 is created. Second, when the NON_TMN network component system 400 is deleted, the corresponding Q3-adapter management agent system 110 is deleted. Third, the TMN management agent system 100 does not have the initialization information necessary for generating the network component system 400 of the NON_TMN environment separately from the NON_TMN network manager system 300 when the NON_TMN network component system 400 is generated. The information is transferred to ON LINE and applied by the process manager 130 as initialization information when the Q3-Adapter Management Agent System 110 is generated. Fourth, the Q3-adapter management agent system 110 is automatically regenerated by the process manager 130 through automatic detection by the operating system at abnormal termination of the system. Fifth, the process manager 130 is only responsible for the creation / deletion of the Q3-adapter management agent system 110, and the rest is the Q3-adapter management agent system 110, the message conversion block 120 and the NON_TMN. Through the message transmission / reception between the network manager system 300.

Referring to FIG. 2, messages transmitted between blocks are as follows. The request / response / notification message [2-1] between the TMN network manager system 200 and the Q3-adapter management agent system 110, and the message of the TMN environment requiring control of the network component system [2-2]. ], A message in the NON_TMN environment requiring control of the network component system [2-3], and a request / response / notification message between the network manager system 300 and the network component system 400 in the NON_TMN environment [ 2-4] and a message for transmitting initialization / deletion / initialization related information of the network component system 400 of the NON_TMN environment between the NON_TMN network manager system 300 and the process manager system 130 during initialization [2- 5] and the creation / deletion message [2-6] of the Q3-adapter management agent system 110 from the process manager 130.

3 is a flowchart of a processing procedure for reducing process overhead through the process manager 130 according to an embodiment of the present invention. A description of a process of generating a plurality of Q3-adapter management agent systems is as follows. First, in step [3-1], a message conversion block 120 for converting a TMN message and a NON_TMN message is generated. Next, in the processes [3-2], [3-7], and [3-12], the NON_TMN network component system 402, 404, 406 sends its own creation request message to the NON_TMN network manager system 300. Accordingly, the NON_TMN network manager system 300 sends a request message to the process manager 130 to generate the Q3-adapter system in the process [3-3], [3-8], or [3-13]. Accordingly, the process manager 130 generates the respective Q3-adapter management agent processes 112, 114, and 116 in the processes [3-4], [3-9], and [3-14], [3-5] ], [3-10], and [3-15] send a Q3-Adapter system creation confirmation message to the NON_TMN network manager system 300. Thereafter, in the processes [3-6], [3-11], and [3-16], the NON_TMN network manager system 300 transmits a creation confirmation message to the NON_TMN network component systems 402, 404, and 406.

4 illustrates a process of deleting a plurality of Q3-adapter management agents systems 112, 114, and 116, and an internal processing routine is processed through the following process. First, in the process [4-1], the NON_TMN network manager system 300 deletes when any of the NON_TMN network component systems 402, 404, and 406 managed by the NON_TMN network component system is no longer a target to be managed. The NON_TMN network component system sends a delete message indicating that it is not managed. Thereafter, in the process [4-2], the NON_TMN network manager system 300 sends a delete request message of the Q3-Adapter management agent system 114 mapped to the NON_TMN network component system 404 deleted by the process manager 130. Ask. Accordingly, in the process [4-3], the process manager 130 deletes the required Q3-adapter management agent system 114. Thereafter, in the process [4-4], the process manager 130 transmits a deletion confirmation message of the requested Q3-adapter management agent system 114 to the NON_TMN network manager system 300.

5 is a flowchart of a regeneration process of the Q3-adapter management agent system for efficient management of the TMN management agent system through automatic detection at abnormal termination of the Q3-adapter management agent system. Referring to FIG. 5, a process of abnormal termination of the Q3-adapter management agent system is as follows. First, in step [5-1], the operating system notifies the process manager of abnormal termination of the Q3-Adapter management agent system. Subsequently, in [5-2], the process identifier and status value received from the operating system are analyzed to create a new Q3-Adapter management agent system. Subsequently, in the process [5-3], the Q3-Adapter management agent system requests data from the database that it had until just before the abnormal termination. Then, in the process [5-4], the database transmits the data requested by the Q3-adapter management agent system to the corresponding Q3-adapter management agent system. Then, using the data received in the process [5-5], the Q3-Adapter management agent system generates an MIT. That is, managed object instances that have been created so far are generated from the received data. Subsequently, in [5-6], internal threads that exist in the manager's own block are created.

By the above configuration, the management of the plurality of Q3-adapter management agent systems according to the features of the present invention can be made.

Meanwhile, in the above description of the present invention, specific embodiments have been described, but various modifications may be made without departing from the scope of the present invention. Therefore, the scope of the present invention should not be defined by the described embodiments, but by the claims and equivalents of the claims.

As described above, the present invention has the following effects. First, the NON_TMN network component system and the Q3-Adapter management agent system are mapped 1: 1 so that the creation / deletion time of the NON_TMN network component system matches the mapped Q3-Adapter management agent system. The head can be solved. Second, the system automatically reports the operating system in case of abnormal termination of the Q3-Adapter Management Agent system to immediately operate the abnormally terminated Q3-Adapter Management Agent system, thereby minimizing the time required for recovery. And information inconsistency.

Claims (6)

A non-communication management network component system capable of creating or deleting, a non-communication management network manager system managing the non-communication management network component systems, and a corresponding non-communication management network component system, respectively. A method for managing the Q3-adapter management agent systems in a system consisting of a TMN management agent system having a process manager for managing the Q3-adapter management agent system A first step of receiving a generation request message from a non-communication management network component system in which the non-communication management network manager system is generated; A second step of the non-communication management network manager system receiving the generation request message transmitting a Q3-Adapter system generation request message to the process manager; And a third step of the process manager generating a Q3-adapter management agent system according to the received Q3-adapter creation request message. The management method as claimed in claim 1, further comprising a regeneration process for driving the abnormally terminated Q3-adapter management agent system through automatic reporting of the operating system when the Q3-adapter management agent system abnormally terminates. . The method of claim 1, After performing the third step, the process manager sends a Q3-Adapter system creation confirmation message to the non-communication management network manager system so that the non-communication management network manager system generates the non-communication management network component system. And sending the message. delete A non-communication management network component system capable of creating or deleting, a non-communication management network manager system managing the non-communication management network component systems, and a corresponding non-communication management network component system, respectively. A method for managing the Q3-adapter management agent systems in a system consisting of a TMN management agent system having a process manager for managing the Q3-adapter management agent system The non-communication management network manager system transmits a deletion message to a non-communication management network component that is no longer a target to be managed, and sends a Q3-adapter system deletion request message corresponding to the non-communication management network component. A first step of transmitting to the process manager; And a second step of the process manager deleting the Q3-adapter management agent system corresponding to the non-communication management network network element according to the received Q3-adapter system deletion request message. The method of claim 6, After performing the second step, the process manager sends a Q3-adapter system deletion confirmation message to the non-communication management network manager system, thereby confirming that the non-communication management network manager system is deleted from the non-communication management network component system. And sending the message.