KR100270702B1 - Management method to update m.i.t. of telecommunication management network agent - Google Patents

Abstract

end. TECHNICAL FIELD OF THE INVENTION The invention described in the claims relates to a demand dense optical subscriber transmission system based on a telecommunications management network (TMN).

I. The technical problem to be solved by the present invention is to provide a method for registering and managing changes to the system configuration during the initialization of the agent in the demand dense optical subscriber transmission system based on the communication management network.

All. SUMMARY OF THE INVENTION A system based on a communication management network (TMN), comprising: creating a request message corresponding to a command received through a CIT access device and transmitting the request message to an operation management processor of the system; A response message corresponding to the request message is received and analyzed, and the result message of completion of execution of the command is transmitted to an agent of the communication management network. In this case, when the agent transmits the result message during initialization, the agent creates or deletes a management object corresponding to the result message and updates the M. MIT related information to update the M. MIT. It features a management box.

la. Significant Use of the Invention: Can be used in TN-based optical transmission systems.

Description

How to manage M.I.T of Communication Management Network Agent

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an optical transmission system, and more particularly, to a method for managing a management information tree (MIT) of a communication management network agent (Agent) for normally managing changes in an optical transmission system configuration.

Telecommunications Management Network (hereinafter referred to as TMN) is designed to solve the difficulties of equipment compatibility and equipment management due to different management methods provided by manufacturers when different manufacturers of communication equipment or the same equipment are different. It is a raised concept. The TMN technology is applied to general synchronous optical transmission systems (for example, FLC (Fiber Loop Carrier)) and demand dense optical subscriber transmission systems, but there are differences in structural aspects. In general synchronous optical transmission system, TMN manager and agent are embedded in the same unit of system unlike demand-intensive optical subscriber transmission system, and OAMP is a sub-management system that manages the overall operation and management of the system. (Operation, Administration & Maintenance Processor) and the Man-Machine Interface (MMI), which provides an interface between the operator and the system, are generally located and operated in a different kind of process unit.

FIG. 1 is a diagram illustrating a system implementation location of a communication management network manager and an agent in a general synchronous optical transmission system. In FIG. 1, communication between a data communication unit (DCU) 10 performing a manager and an agent function and a message communication unit (MCU) 20 in charge of a system OAM function is defined in advance through a predetermined interprocessor communication (IPC). It takes the form of a message. That is, the IPC message is read / written in the DPRAM 22 located in the MCU 20, so that the communication between the DCU 10 and the MCU 20 is possible. Meanwhile, when the DCU 10 is mounted in a slot, TMN related tasks are generated and initialized. The agent 14 generates a management information tree (MIT) by generating system information as a management object. Since the management objects are generated based on system configuration information and the like, the agent 14 obtains the necessary information from the OAMP 26 in advance. Upon receiving a response from the OAMP 26 on demand, the agent 14 creates management objects based on this and registers them with the MIT. This process must be completed until the initialization of the agent 14 is terminated.

However, in the general optical transmission system, if an operator command is requested to change the system configuration during agent initialization, information about the system configuration change is not registered in the MIT, and the actual state of the system and the contents inquired by the operator are inconsistent. The problem often arises. The only way to prevent such discrepancies is to force the operator to refrain from executing commands that result in changes in the system configuration during the agent 14 initialization period.

Accordingly, an object of the present invention is to provide a method for registering and managing changes in system configuration that occurs during agent initialization in a demand dense optical subscriber transmission system based on a communication management network.

Another object of the present invention is to provide a MIT management method that can minimize the inconsistency of the system configuration query through the administrator of the demand dense optical subscriber transmission system and the query history through the interface between the operator and the system.

In order to achieve the above object, the present invention provides an agent M.I. (MIT) management method of a demand dense optical subscriber transmission system based on a communication management network (TMN),

A request message corresponding to the command received through the CIT access device is prepared and transmitted to the operation management processor of the system, and from the processor, a response message corresponding to the request message is received and analyzed to determine whether the command is completed. Transmitting a message to the agent of the communication management network;

MIT update process of updating M. MIT related information by creating or deleting a management object corresponding to the transmitted result message when the result message is transmitted. Characterized in that made.

1 is a view showing a system mounting position of a communication management network Manager and an agent in a general synchronous optical transmission system.

2 is a view showing the configuration of a demand-dense optical subscriber transmission system according to an embodiment of the present invention.

3 is an agent MIT configuration related message flow diagram performed in the CIT MML Interface 24 task of FIG.

4 is a MIT management flow diagram for a system configuration change during agent initialization in accordance with an embodiment of the present invention.

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

First, the demand-intensive optical subscriber transmission system provides the operator with the method through the FMS (FLC Management System) and the CIT access device of the host digital terminal (HDT) as the system operation management interface. The operator can request the HDT MCU's agent to execute system management commands through the Q3 interface provided by the FMS. In contrast, commands input through the CIT interface of the HDT MCU are processed and executed by their own OAMP, not by the Q3 interface. In this case, if the system configuration is changed by the execution of the command input through the CIT access device, the information about the changed system configuration is not registered in the agent's MIT. The details may differ. Therefore, in the following description, when the system configuration is changed by the execution of a command input through the CIT access device, a method of registering information related to the changed system configuration to the agent's MIT will be described in detail.

FIG. 2 is a diagram illustrating a configuration of a demand dense optical subscriber transmission system according to an exemplary embodiment of the present invention, and FIG. 3 is a flowchart illustrating a message processing related to an agent MIT configuration performed in the CIT MML interface 24 task of FIG. 2. 4 illustrates a MIT management flow diagram for a system configuration change during agent initialization according to an embodiment of the present invention. First, referring to FIG. 2, unlike the general optical transmission system illustrated in FIG. 1, the demand-dense optical subscriber transmission system has a functional block of the manager 12 and the agent 21 separated from each other, and only the agent 21 is an MCU 20. It is mounted and driven. The FMS 30 provides a function for the operator to simultaneously manage multiple demand dense optical subscriber transmission systems. However, in the event that management failure occurs in the FMS 30 or the system management through the FMS 30 is difficult due to an abnormality such as a LAN (①) state, the operator may use the CIT of the HDT (Host Digital Terminal) MCU 20 of each system. The system can be operated via the interface. Looking at the configuration in the MCU 20, first the agent 21 transmits messages to the OAMP 26 to obtain the information necessary for the creation of management objects when the system is running, and based on the information transmitted from the OAMP 26 Create managed objects and register them with MIT. In the embodiment of the present invention, the MIT is managed through the steps as shown in FIG. 4. The CIT MML interface 24 interprets the command received from the operator through the CIT interface, converts it into a request message, and transmits it to the OAMP 26. The request message includes a message requesting a change in the system configuration. The CIT MML interface 24 analyzes the unique ID of the response message sent from the OAMP 26, and if the response message is related to the agent MIT configuration, the request message may be an agent_CIT queue 23 or an agent queue. 25). At this time, the agent_CIT queue 23 is used only during the initialization of the agent 21, and the agent queue 25 is used during normal driving. The operation of the CIT MML interface 24 as described above will be described in detail later with reference to FIG. 3. On the other hand, OAMP 26 is responsible for the overall operation and management of the system. The queue interface 27 interfaces various request messages and corresponding response messages transmitted between the operator, the agent 21 and the OAMP 26.

Hereinafter, the MIT management method when a command causing a change in the system configuration is received through the CIT access apparatus will be described with reference to FIGS. 3 and 4.

First, when the MCU 20 is driven by the power supply and the initialization of the OAMP 26 function is performed, the operator can manage the demand dense optical subscriber transmission system through the CIT access device. Specifically, when an operator requests execution of a command for changing the configuration of a system using a computer terminal connected to a CIT interface, the CIT MML interface 24 receives a command in step 40 of FIG. After the received command is interpreted, the process proceeds to step 42. In operation 42, the CIT MML interface 24 assigns a job ID to a request message corresponding to the received command and transmits the job ID to the OAMP 26. Accordingly, the OAMP 26 task performs a function according to the transmitted request message and transmits a response message according to the completion result to the CIT MML interface 24. In step 46, the CIT MML interface 24 checks whether there is a request message having the same job ID in the message management list (MML). If there is a request message having the same job ID as the ID assigned to the response message, the CIT MML interface 24 proceeds to step 48 and outputs a response message to the operator. In this case, the outputted response message is a message indicating the completion of the command received in step 40. In this way, the CIT MML interface 24 outputting the response message to the operator proceeds to step 50 and checks the completion of the command by checking the flag of the response message transmitted from the OAMP 26. If the command received in step 40 is normally completed, the CIT MML interface 24 proceeds to step 52 to check whether the response message sent from the OAMP 26 is a response message related to the agent MIT configuration. That is, the CIT MML interface 24 checks whether the system configuration has been changed in step 52. If the result of the check in step 52 is a response message related to the MIT configuration, the CIT MML interface 24 proceeds to step 54 to check whether the agent initialization end flag is set through the queue interface 27. The agent initialization end flag indicates whether or not the agent 21 is initialized. If the agent initialization end flag of step 54 is set, the CIT MML interface 24 proceeds to step 56 and transmits a request message for the response message to the agent queue 25. If the agent initialization end flag is not set, the agent 21 is currently being initialized, and the CIT MML interface 24 proceeds to step 58 to transmit a request message for the response message to the agent_CIT queue 23. . As described above, the CIT MML interface 24 analyzes the response message transmitted from the OAMP 26 task accordingly when receiving a command that causes a change in the system configuration from the operator, and analyzes the result of the execution of the command. _CIT queue 23 is sent. Therefore, the agent 21 is able to register the information related to the system change to the MIT.

Hereinafter, the steps up to registering information related to a system change in the MIT using the request message transmitted by the CIT MML interface 24 will be described with reference to FIG. 4.

First, when the initialization of the OAMP 26 function is completed, the agent 21 prepares request messages for reading information related to the system configuration in step 60 of FIG. 4, transmits them to the OAMP 26, and receives a response message accordingly. . The agent 21 generates management objects required for each unit of the Self using the information obtained from the received response message in step 62. The location information of the managed object currently being created is managed by currenSid and currentCid. Thereafter, the agent 21 proceeds to step 64 to check whether management objects have been created. If the location information currentSid is FINISHED_SID and currentCid is FINISHED_CID, this indicates that creation of management objects has been completed. Accordingly, the agent 21 may know that generation of the management objects is finished through the location information. If creation of the managed objects is terminated in step 64, the agent 21 proceeds to step 66 and checks whether there is a request message transmitted from the MMI, that is, the CIT MML interface 24 through the agent_CIT queue 23. Proceed to step. In step 68, the agent 21 checks whether the message transmitted from the CIT MML interface 24 is a request message related to MIT management. If the result of the check is a message related to the MIT management, the agent 21 proceeds to step 70 and generates a management object according to the request message or deletes the management object that has already been generated, and proceeds to step 70. If there is no request message sent from the MMI in step 70, the agent 21 proceeds to step 72, sets the initialization end flag, and ends the MIT management method according to the embodiment of the present invention.

As described above, the agent 21 creates or deletes a management object by checking whether there is a request message transmitted to the agent_CIT queue 23 before the initialization ends. That is, the agent 21 creates or deletes a management object according to whether or not the command is completed if there is a command for changing the system configuration from the operator during initialization. Therefore, it is possible to minimize the inconsistency between the system configuration inquiry through the administrator and the inquiry through the interface between the operator and the system.

As described above, in the present invention, in the demand-dense optical subscriber transmission system based on the communication management network, the present invention is accurate to the operator by minimizing the inconsistency between the system configuration inquiry through the administrator and the inquiry through the interface between the operator and the system. It has the advantage of providing system information. In addition, there is an advantage in that the efficiency of system management can be improved because a separate synchronization process is not required to solve the inconsistency of the inquiry details.

Claims (3)

In the agent M. MIT management method of demand dense optical subscriber transmission system based on communication management network (TMN), A request message corresponding to the command received through the CIT access device is prepared and transmitted to the operation management processor of the system, and from the processor, a response message corresponding to the request message is received and analyzed to determine whether the command is completed. Transmitting a message to the agent of the communication management network; MIT update process of updating MIT related information by creating or deleting a management object corresponding to the transmitted result message when the result message is transmitted. Agent M. I. (MIT) management method, characterized in that consisting of. The method of claim 1, wherein the M. MIT update process is performed before the initialization of the agent is completed. The method of claim 1, wherein the result message transmitted to the agent in the message transmission process is limited to the result messages resulting from the change of the system configuration.