KR100228401B1 - Method for controlling alarm log start in tmn managing system - Google Patents

Abstract

1. TECHNICAL FIELD OF THE INVENTION

Alarm log start control method in communication network manager system

2. The technical problem to be solved by the invention

Communication management network manager system is to provide alarm log start control method to control alarm log start operation not only at the element management layer level but also at the network management layer level.

3. Summary of Solution to Invention

A first step of extracting agent management object information for a plurality of agent systems when receiving an alarm log start request message; Creating a new log management object instance for the agent management object; A third step of requesting generation of an alarm log from the agent system after configuring and storing the alarm log information; And a fourth step of transmitting an alarm log start completion message when receiving the alarm log generation completion message to configure a response message.

4. Important uses of the invention

Used for communication management network (TMN).

Description

Alarm log start control method in communication network manager system

The present invention relates to an alarm log start control method for controlling alarm log start in a communication management network manager system for a telecommunications management network (TMN) of an asynchronous transfer mode (ATM) exchange.

Based on the Common Management Information Protocol (CMIP) standardized by the International Organization for Standardization (ITU-T) and the Asynchronous Exchange Mode (ATM) Exchange Forum, TMN functions are being implemented worldwide. Is implemented in the MSS (Metropolitan Switching System) exchange.

However, the MSS exchange also does not have a log control function for the alarm, so information on the alarm is not managed, and there is a problem that the communication management network operator cannot manage the alarm message efficiently.

If you do not log alarm messages received through an agent system from an Asynchronous Exchange (ATM) exchange, the communication management network operator must continuously monitor the operator terminal to see the generated alarm messages. However, in reality, it is impossible for telecommunications network operators to monitor the 24-hour terminal, and considering the aspect of storing the information even if the alarm message is confirmed, there is a need for a method that requires the manager system to start logging the alarm message to the agent system. do.

In order to solve the above problems, the present invention provides a communication log for the alarm message generated by the communication management network manager system at the asynchronous transfer mode (ATM) exchange as well as at the element management layer level of the communication management network. It is an object of the present invention to provide an alarm log start control method that maintains and manages a log of the entire network-level alarm of an asynchronous transfer mode (ATM) exchange by controlling the start operation.

1 is a structural diagram of a communication management network (TMN) manager system to which the present invention is applied,

2 is a block diagram of an alarm processing block in a communication management network manager system to which the present invention is applied;

3A and 3B are flowcharts illustrating an alarm log start control method in a communication management network manager system according to the present invention;

* Explanation of symbols for the main parts of the drawings

101: manager system 102: agent system

In order to achieve the above object, the present invention, in the alarm log start control method applied to the communication management network manager system, upon receiving an alarm log start request message from the communication management network operator for each agent (Agent) A first step of extracting managed object information; A second step of creating a new log managed object instance for an Agent managed object; A third step of requesting generation of an alarm log from the agent system after configuring and storing alarm log information to be requested to an agent system; And a fourth step of transmitting an alarm log start completion message when receiving the alarm log generation completion message from each agent system to configure a response message.

Hereinafter, with reference to the accompanying drawings will be described an embodiment according to the present invention;

1 is a structural diagram of a communication management network (TMN) manager system to which the present invention is applied, in which "101" represents an administrator system and "102" represents an agent system, respectively.

The communication management network (TMN) for managing an asynchronous delivery mode switch is composed of an administrator system 101 for requesting management operations and an agent system 102 for management.

The manager system 101 is composed of two subsystems: a Human Interface for Network Element Subsystem (HINES) 103 and a Network View Management Subsystem (NVMS) 104.

The HINES 103 performs a function for visually transmitting and receiving information to a communication management network operator and creating / managing an operator window, and includes five blocks, namely, a GUI MMC Input Block (GMIF) 106 and a GMOF (GUI MMC). Output Block (107), GUI Object Data Input Block (GOIF) 108, GUI Object Data Output Block (GOOF) 109, and GUI System Management Block (GSMF) 105.

The GMIF 106 provides a management network operator with a man-machine communication (MMC) input window, and separates the parameters in the MMC input message received from the management network operator and packs them into a path through message again. After packing), it is transmitted to the GSMF 105.

The GMOF 107 provides the MMC output window to the communication management network operator, unpacks the output message in the form of a path through received from the GSMF 105, and then combines it with the parameters in the MMC output message. Afterwards, it plays a role of outputting to the communication network operator.

The GOIF 108 provides an input window of a management object unit to the communication management network operator, receives an input of the management object unit from the communication management network operator, converts it into a CMIP message, and then transfers it to the GSMF 105.

The GOOF 109 provides the communication management network operator with an output window expressed in management object units, and analyzes CMIP messages received from the GSMF 105 to enable output of management object units.

The GSMF 105 is a function for managing a process, and after queuing a message received from the GMIF 106 and the GOIF 108, the GSMF 105 transmits the message to a message conversion to management block (MCMF) 110, and sends a message to the MCGF. After queuing the message received from the Conversion to GUI Block (111) 111, the message is transferred to the GMOF 107 or the GOOF 109. In addition, the alarm and failure message received from the NVMS 104 serves to store in the shared memory so that the GMOF (107) and GOOF (109) can be processed.

The NVMS 104 processes a management object of a manager and requests a management operation. The NVMS 104 includes three blocks: a message conversion to management block (MCMF) 110 and a message conversion to GUI block (MCGF) 111. , And a Management Operation Handling Block (MOHF) 112.

The MCMF 110 converts an operator input message received from the HINES 103 into management object information that can be processed by the MOHF 112.

The MCGF 111 converts the management object information received from the MOHF 112 into generalized information that can be processed by the HINES 103.

The MOHF 112 performs configuration management, connection management, and failure management functions that are unique to the communication management network manager.

Agent system 102 is composed of two subsystems: Network Element Agent Subsystem (NEAS) 113 and Connector for Agent and Switch Subsystem (CAS).

The NEAS 113 receives a management operation request from the manager system 101, analyzes the received management operation request, passes the result to the CASS 114, and reports a management operation result to the manager system 101. It analyzes the management information from the delivery mode exchange to change the management information data in the agent system 102, and loads initial data of the agent system 102 from the exchange.

The CASS 114 performs a matching function with an asynchronous transfer mode switch, a parsing between the communication management network command and a human-machine interface (HMI) command of the asynchronous transfer mode switch, and performs an encoding / decoding function. .

2 is a configuration diagram of an alarm processing block in a communication management network manager system to which the present invention is applied, and is a connection diagram showing a relationship between subblocks in an MOHF 204 block for processing management operations in a communication management network manager system. .

MOHF 204 is composed of three sub-blocks: ConFiguration MAF (CFMAF) 205, CoNnection MAF (206), and FTMAF (FaulT MAF) 207.

The CFMAF 205 initializes the configuration related management objects of the agent system 208, receives the configuration related communication management network operator command, requests the management operation to the agent system 208, and notifies the result from the agent system 208. Receive and process.

The CNMAF 206 initializes connection-related managed objects of the agent system 208, receives a connection-related communication management network operator command, requests a management operation to the agent system 208, and notifies the result from the agent system 208. Receive and process.

The FTMAF 207 to which the present invention is applied performs a function of receiving and processing a message related to an alarm and a failure from an agent system 208, and receiving an alarm log start message through the MCMF 202 from a communication management network operator. The alarm log start is requested to the agent system 208 according to the alarm log start control procedure. When receiving the alarm log start request completion message from the agent system 208, the result is outputted to the communication management network operator through the MCGF 203.

3A and 3B are flowcharts illustrating an alarm log start control method in a communication management network manager system according to the present invention, and an operation flowchart for controlling alarm log start in an alarm processing subblock (FTMAF) in the communication management network manager system. .

When receiving the alarm log start request message from the MCMF block (301), FTMAF creates an internal thread to process one new request message so that multiple alarm log start request messages received from the MCMF block can be processed in parallel. Process the request message (302). Counting information on the number of agents (Agent) that should start the alarm log in the received request message (303) and repeats the following operation for each agent.

When the target agent (Agent) to request the start of the alarm log is determined, the index information of the management objects managed by the manager is searched to search for management object information corresponding to the target agent (304). In order to start an alarm log for a specific agent, a new log management object instance is created in the agent management object (305) and an operation of defining an association between them is required. Associations between specific agent-managed objects and log-managed objects are made possible through the attribute log number, which exists within a log-managed object instance. The log number identifying a specific log management object instance of a specific agent managed object is called a log relative distinguish name (RDN). However, since the communication management network operator manages the alarm log and the fault log independently, the log numbers are also managed independently of each other. However, in the case of communication management network, since alarm log and fault log managed objects are not distinguished and represented by the same log managed object, the alarm log and fault log are mixed in consecutively assigned log numbers (that is, log RDN). do. In the present invention, in order to maintain and manage the continuous log number for each while expressing the alarm log and the fault log as the same log management object, the start number of the alarm log is set as the base alarm log number and the start number of the fault log. Is set as the base fault log number. The alarm log number continuously assigned by the communication management network operator is received in the request message from the MCMF, and the log RDN is determined by adding the base alarm log number to the log number set by the communication management network operator (306). This log RDN is assigned to the log number attribute in the newly created log management object instance (307).

If an error occurs because a log number already exists during the creation of a new log management object instance (308), the error output information is configured (314), and an error message is transmitted to the network management network operator through MCGF (315). The internal thread that was being processed is deleted and terminated (316).

However, when the log management object instance creation is successful (308), an alarm log condition is configured to request the alarm log to be started by the agent (309). In the alarm log condition, various alarm logs can be started depending on the type of alarm and the alarm class. For example, you can start logging only for events with an alarm type of board hernia and an alarm class of critical, or you can start logging for all types of alarms. That is, the alarm log condition can be set to any one of a combination of alarm types and alarm classes. In case of alarm log start, since the property information of alarm log is received from the network management network operator, FTMAF temporarily stores these alarm log property information (310) and re-transmits this property information when transmitting a request completion message afterward (310). The operator of the communication network should output it for confirmation.

When the manager is ready for the alarm log start request, it sends an alarm log generation request message to the agent system (311) and sets a timer for the alarm log generation request (312), waiting for the agent system to respond (313). To transition to.

When the alarm log generation completion message is received from the agent system in the standby state (318), the set timer is released and the alarm log number to be output from the log RDN is output to the communication management network operator (319). That is, the log number to be transmitted to the MCGF is calculated by subtracting the base alarm log number from the log number in the log RDN. After configuring the response information to be transmitted to MCGF (320), if the processing is completed for all agent systems requested by MCMF at the first startup (321), after sending the alarm log start completion message to MCGF (322), the internal thread currently being processed Delete (323) and the operation ends. However, if the process has not been completed for all the agent systems requested by the MCMF at the first startup (321), it repeats from the agent information retrieval process (304).

If there is no response from the agent system in the standby state and a time out occurs (324), it is determined whether to send again (325). Repeat it. However, when the timeout occurs and ends without retrying, the error output information is configured (314) and an error message is transmitted to the communication network operator through the MCGF (315). Delete the thread and exit (316).

When the alarm log generation failure is received from the agent system in the standby state (317), the error output information is configured (314) and an error message is transmitted to the communication network operator through the MCGF (315). Delete and terminate (316).

The present invention described above is capable of various substitutions, modifications, and changes without departing from the spirit of the present invention for those skilled in the art to which the present invention pertains, and the above-described embodiments and accompanying It is not limited to the drawing.

The present invention as described above can obtain the following effects.

First, the International Standardization Organization (ITU-T), which is a standard of the communication management network (TMN), is modeled as a single log management object without separating the alarm log and the fault log. However, in the present invention, the asynchronous transmission mode (ATM) is used by using the log number. ) You can control the alarm log start and fault log start of the exchange separately.

Second, the log management of the alarm message is enabled, so that the communication network operator can manage the network without monitoring the terminal.

Third, since alarm log start control is possible at the network management layer level, the network manager can request several agent systems in the communication network to start the alarm log at the same time. Is done.

Claims (6)

In the alarm log start control method applied to the communication management network manager system, A first step of extracting agent management object information for each of a plurality of agent systems upon receiving an alarm log start request message from a communication management network operator; A second step of creating a new log managed object instance for an Agent managed object; A third step of requesting generation of an alarm log from the agent system after configuring and storing alarm log information to be requested to an agent system; And a fourth step of transmitting an alarm log start completion message when receiving an alarm log generation completion message from each agent system to configure a response message. The method of claim 1, wherein the first step comprises: a fifth step of allowing a telecommunication network operator to control alarm log start for a plurality of agent systems with one alarm log start request message; A sixth step of counting information on the number of alert log agents to be started in the received request message; And a seventh step of retrieving managed object information of the target agent by retrieving the index information of the managed objects managed by the administrator, when the target agent to determine the start of the alarm log is determined. How to control log start. 3. The method of claim 1 or 2, wherein the second step comprises: an eighth step of creating a new log management object instance in the agent management object to start an alarm log for the agent; A ninth step of calculating a base alarm log number to an alarm log number continuously assigned by a communication management network operator and a base error log number to a fault log number to determine a log number; And assigning the determined log number to a log number attribute in the newly created log management object instance. The method of claim 3, wherein the third step comprises: an eleventh step of determining whether an error has occurred in the process of creating a new log management object instance of the second step; A twelfth step of configuring an error output information if the error is determined as the result of the eleventh step and deleting the internal thread after transmitting an error message to the communication management network operator; And as a result of the determination in the eleventh step, if it is not an error, configure an alarm log condition to temporarily store alarm log characteristic information, transmit an alarm log generation request message to the agent system, and set a timer for the alarm log generation request. And a thirteenth step of transitioning to a response waiting state. The alarm log of claim 4, wherein in the fourth step, when the alarm log generation completion message is received from the agent system in the response waiting state of the thirteenth step, the alarm log is released and the alarm log to be output to the communication management network operator from the log number. If the processing is completed for the requested agent systems after constructing the response information by reversing the number, if the processing is completed, the internal thread is deleted after sending the alarm log start completion message. If the processing is not completed for the requested agent systems, A fourteenth step of repeating the operation from the seventh step; If the timeout occurs in the response waiting state of the thirteenth step, it is determined whether to retransmit. If retransmission, the alarm log generation request is repeatedly transmitted to the agent system of the thirteenth step. A fifteenth step of configuring information and deleting an internal thread after transmitting an error message to a communication management network operator; And a sixteenth step of configuring an error output information upon receiving an alarm log generation failure from the agent system in the waiting state of the thirteenth step, and transmitting an error message to the communication management network operator, and then deleting the internal thread. Alarm log start control method. The alarm log condition of claim 13, wherein Alarm log start control method comprising a combination of alarm types and alarm classes.