KR19980038225A - Failure Management Method of Distributed Access Node System - Google Patents

Abstract

The present invention relates to a failure management method for performing a failure management function of a distributed access node system (DANS). In the related art, in order to determine whether a failure occurs in a DANS system and recover a failure caused by performing a failure management function independently. Since the system manager always resides around the DANS system, labor costs are high, and the fault management function of the conventional DANS system does not include the network management function through the communication management network (TMN) and therefore cannot be connected to the TMN. The present invention for solving the problem by the problem that can not be performed is added to the DANS TMN agent function block based on the management information (MIB) and provides an interface function using the common management information protocol (CMIP) It can be used to perform fault management function through TMN.

Description

Failure Management Method of Distributed Access Node System

By adding the function management network (TMN) agent function block proposed in the present invention to the distributed access node system (DANS), it is possible to perform fault management function for a plurality of DANS distributed in various locations at remote locations, and the distributed access node. An object of the present invention is to connect a system to a communication management network so as to perform a distributed access node system failure management function at the communication management network level.

The present invention relates to a failure management function of a distributed access node system (DANS). In the related art, in order to determine whether a failure occurs in a distributed access node system by performing a failure management function only on its own, Since the system administrator always resides around the distributed access node system, the system administrator must be maintained separately for each system, which is expensive.

In addition, the failure management function of the conventional distributed access node system does not include a network management function through a communication management network (TMN), and thus cannot be connected to the communication management network.

Therefore, the failure management function of the distributed access node system could not be performed at the communication management network level.

In order to achieve the above object, in the present invention, a distributed access node system includes a communication management network (TMN) agent function block that provides an interface function based on management information (MIB) and uses a common management information protocol (hereinafter referred to as CMIP). In addition to (DANS), this paper proposes a scheme for performing fault management functions through a communication management network.

The communication management network agent function receives the failure information when a failure occurs in the distributed access node system, changes the operation state information of the corresponding object from the management information (MIB) to a failure state, and transmits to the remote communication management network management function unit. Disability information is transmitted using common management information protocol.

Through this, it is possible to perform fault management functions of distributed access node systems in which the function block, which is a remote manager, is distributed in various regions.The distributed access node system is connected to the communication management network (TMN) to prevent failure at the communication management network level. Allow management functions to be performed.

1 is a connection diagram between systems to which the present invention is applied;

2 is a software configuration to which the present invention is applied;

3a to 3c are flow charts in accordance with the present invention;

Explanation of symbols for the main parts of the drawings

100: operation and management system of distributed access node system (DOMS)

110: communication management network (TMN) manager function

200: distributed access node system (DANS)

210: system software

220: communication management network (TMN) agent function unit

221: application unit 221a: system interface

221b: failure management unit 221c: performance management unit

221d: Configuration management unit 221e: Management information unit (MIB)

221f: Common Management Information Protocol (CMIP) interface

222: protocol stack unit 222a: common management information protocol (CMIP)

222b: connection control service element (ACSE)

222c: Remote operation service element (ROSE)

222d: Subprotocol 300: Ethernet

The present invention relates to a failure management method for performing a failure management function of a distributed access node system (DANS), and more particularly, to a failure management of a distributed access node system in which a function block that is a TMN agent is added.

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

1 is a diagram illustrating a connection between systems to which the present invention is applied.

The configuration is a system between a remote access node system operation and management system (DOMS Operation and Management System, referred to as DOMS) 100 and a distributed access node system (DAN) 200 that is a managed system. Will be connected.

The distributed access node system 200 is connected to up to eight distributed access node systems (DANS) and Ethernet (Ethernet) (300).

The manager function unit 110 in the distributed access node system 200 is common to the telecommunication management network (TMN) agent function unit (TMN AGent Block, hereinafter referred to as TAGB) 220 in the DANS 200. Receives fault information through the interface using the Common Management Information Protocol (CMIP) and performs the function of handling the fault.

The TMN agent function unit (TAGB) receives the failure information generated in the DANS 200 from the system software 210, and transmits the management information MIB existing in the TMN agent function unit TAGB. After correcting the corresponding contents with the received failure contents, the failure information is transmitted to the TMN manager function unit 110 in the operation and management system (DOMS) 100 of the distributed access node system through an interface using a common management information protocol. It performs the function.

2 is a software block diagram to which the present invention is applied.

The software configuration diagram is an internal software configuration diagram of the TMN agent function unit (TAGB) 220 to which the present invention is applied.

The TMN agent function unit 220 is largely composed of an application program unit 221 and a protocol stack unit 222.

The application program unit 221 again includes a system interface unit 221a in charge of the interface function with the system software 210, a failure management unit 221b for performing a failure management function, and a performance management unit 221c for performing a performance management function. And management information (MIB) 221e, which stores information about management objects in the distributed access node system (DANS), which performs configuration management functions, and a manager function block at a remote location. It consists of a CMIP interface unit 211f that handles management information protocol (CMIP) interface functions.

In addition, the protocol stack unit 222 includes a common management information protocol unit (CMIP) 222a, an association control service entity (ACSE0 222b), and a remote operation service entity (ROSE). 222c and lower protocol stack 222d.

The CMIP interface 221f performs a function of transmitting or receiving a CMIP message, and a connection establishment control service element (ACSE) 222a is a TMGB manager function unit 110 and a TAGB 220 in the DANS 200. Performs a function of establishing and releasing a connection with a.

The remote operation service element (ROSE) 222c enables the operation command and reporting function between the TMN manager function block 110 and the TAGB 220 at the remote location.

When exchanging data between the TMN manager function block of the lower protocol 222d and the TAGB 220, an error monitoring function and a function of controlling data flow are performed.

3A to 3C are flow charts in accordance with the present invention.

After performing the initialization (S1) of the system, the TAGB 220 waits for an event report input from the system software 210 or a command input from the TMN manager function block 110 (S2).

Receiving an event report message from the system software 210 (S3) by analyzing the contents of the message (S4), if the contents of the port failure (S5) by analyzing the identifier of the failed port to identify the failed port ( S6) Determine the level of disability by analyzing the type of disability (S7).

If the result of the message analysis (S4) received from the system software 210 is about a board failure (S8), the failure board is analyzed to identify a board having a failure (S9), and a failure level is determined ( S10)

If the message received from the system software 210 is a virtual path failure (S11) or a virtual channel failure (S12), the failed virtual path identifier and the virtual channel identifier are analyzed to identify the failed virtual path or virtual channel. (S13, S14), the type of disability is analyzed to determine the corresponding disability level (S15, S16).

After identifying the object and the type of the failure and the failure level as described above (S5 ~ S16), the information on the object is retrieved from the management information (MIB) 221e managed by the TAGB 220, The contents of the failure state information of the corresponding object are corrected according to the contents of the failure found in the process of S5 to S16 (S17).

After modifying the contents of the management information (MIB) (221e), the received failure is to check the disabled person to report to the TMN manager function unit (110) (S18), if the disabled person to report the connection settings with the TMN manager function unit 110 Investigate whether this has been done (S19), and if it is not a failure to report, check whether to store the contents of the failure (S20).

Investigate whether the connection is established with the TMN manager function unit 110 (S19). If the connection is not established, try to establish a connection with the TMN manager function unit 110 (S21). Configure and transmit (S22).

In addition, if the result of determining the connection with the TMN manager function unit 110 is determined (S23), and transmits a failure report message to the remote manager's function block (S24). Give up reporting of disability.

After the process of reporting the contents of the disability to the TMN manager function block (S18 to S22), it is determined whether to store the contents of the disability (S23). If it is not a failure to be stored (S2), the command and incident report is immediately waited without storing the details of the failure (S2).

If the message is received from the TMN manager function unit 110 while waiting for the command and the incident report (S2) (S25), the contents of the message are analyzed (S26).

If the content of the message is a connection establishment request (S27), after the connection establishment is performed (S28), the command and the incident report are waited again (S2).

And if the contents of the received message to change the condition of the failure to be reported to the TMN manager function unit (110) (S29) and retrieves the corresponding information from the management information (MIB) 221e in the TAGB (220) Correct the content of the information (S30).

If it is determined that the correction result (S31) succeeds in correcting the contents of the information, a response message indicating that the change of the failure reporting condition is successful is created (S32), and transmitted to the TMN manager function unit 110 (S34), and If the information content fails to be modified, a response message indicating that the change of the failure reporting condition has failed is generated (S33), and transmitted to the TMN manager function unit 110 (S34).

If the content of the received message is a change request (S35) for a failure condition to store the contents of the failure, the corresponding information is retrieved from the management information (MIB) 221e in the TAGB 220, and the contents of the information are corrected. (S36).

If it is determined that the corrected result of the information of the corresponding information is corrected (S37), a response message indicating that the change of the error storage condition is successful is written (S38). After creating a response message indicating failure (S39), the message is transmitted to the TMN manager function unit 110 (S34), and waits for a command and an incident report (S2).

By applying the present invention to an existing DANS system, it is possible to manage a plurality of DANS systems at a remote location, so that it is not necessary to maintain a separate system administrator for each DANS system, thereby reducing the operating cost of the DANS system.

In addition, by applying the present invention, it is possible to access the DANS system to the communication management network (TMN) to perform the fault management function of the DANS system at the overall network level.

Claims (1)

Adds a function management unit (TMN) agent to the distributed access node system (DANS) to transmit information on failures in the distributed access node system to the TMN manager function unit using the Common Management Information Protocol (CMIP) and to access distributed access. In the failure management that stores failure information generated in the node system, after performing the system initialization (S1) process, the event report input from the system software 210 or the command input from the TMN manager function block 110 is waited ( S2) the first process; Receiving an event report message from the system software 210 (S3) to analyze the content of the message (S4) if the contents of the port failure (S5) by analyzing the identifier of the failed port to identify the failed port (S6) A second step of determining a disability level by analyzing the type of disability (S7); If the result of the message analysis (S4) received from the system software 210 is about the board failure (S8) to identify the failure board by analyzing the identifier of the failure board (S9), to determine the failure grade ( S10) a third process; If the message received from the system software 210 is a virtual path failure (S11) or a virtual channel failure (S12), the failed virtual path identifier and the virtual channel identifier are analyzed to identify the failed virtual path or virtual channel. (S13, S14), a fourth step of analyzing the type of disability to determine the corresponding disability level (S15, S16); After grasping the object, the type of failure, and the corresponding failure level of the failure (S5 through S16), the information about the corresponding object is retrieved from the management information (MIB) 221e managed by the TAGB 220 (S5 through S16). A fifth step of modifying the contents of the failure state information of the corresponding object according to the contents of the failure identified in step S16); After modifying the contents of the management information (MIB) 221e, the received disability is examined for the disabled person to report to the TMN manager function unit 110 (S18), if the disabled person to report the connection setting with the TMN manager function unit 110 (S20) checking whether it has been done (S19), and if it is not a failure to report, checking whether to store the contents of the failure (S20); Investigate whether the connection is established with the TMN manager function unit 110 (S19). If the connection is not established, try to establish a connection with the TMN manager function unit 110 (S21). Constructing and transmitting (S22) a seventh process; The result of determining the connection establishment with the TMN manager function unit 110 is determined (S23). If the result is successful, a failure report message is transmitted to the remote manager function block (S24). If the connection establishment fails, the TMN manager function block 110 is transferred to the TMN manager function block 110. An eighth process for giving up disability reporting; After the process of reporting the contents of the disability to the TMN manager function block (S18 to S22), it is determined whether to store the contents of the disability (S23). And (S2) a ninth step of waiting for a command and an incident report without storing the details of the failure if the failure is not to be stored; If the message is received from the TMN manager function unit 110 while waiting for the command and the incident report (S2) (S25), the content of the message is analyzed (S26) and the content of the message is a connection establishment request (S27). 10) performing a connection establishment (S28), and waiting for a command and an event report again (S2); When the content of the received message is to change the condition of the failure to be reported to the TMN manager function unit 110 (S29), the corresponding information is retrieved from the management information (MIB) 221e in the TAGB 220, and the corresponding information is retrieved. An eleventh step of modifying the content of the information (S30); If it is determined that the corrected result is corrected (S31), and successfully corrects the contents of the information, a response message indicating that the change of the failure reporting condition is successful is created (S32) and transmitted to the TMN manager function unit 110 (S33). A twelfth step of creating a response message indicating that the change of the failure reporting condition has failed (S34) and transmitting the result to the TMN manager function unit 110 (S35) if the modification fails; If the content of the received message is a change request for a failure condition to store the contents of the failure (S36), the corresponding information is retrieved from the management information (MIB) 221e in the TAGB 220, and the contents of the information are corrected. (S37) a thirteenth process; If it is determined that the corrected result of the content of the corresponding information is corrected (S38), a response message indicating that the change of the fault storage condition is successful is written (S39). And a 14th step of creating a response message indicating failure (S40), transmitting a message to the TMN manager function unit 110 (S35), and waiting for a command and an incident report (S2). How to manage failure of access node system.