KR100579394B1 - Method and apparatus for state management of generating trouble ticket in tele-communication networks - Google Patents

Abstract

The present invention provides a trouble ticket to a maintenance management system for issuing a work instruction for instructing failure recovery to maintenance personnel in order to recover a failure in a component such as a port or a board constituting a network in a communication network. : Regarding the status management method and device for efficiently issuing TT), it prevents unnecessary TT issuance by combining the fault information and TT issuance information and managing the status of network components in consideration of the interrelationship between the components. By avoiding duplicate TT issuance, failure recovery can be performed quickly by efficiently collecting a series of tasks leading to the collection, analysis, status management, TT issuance, and work order of failure information generated from the network components. Prevents the issuance of automated TT and eliminates inefficient elements, thereby reducing the maintenance costs and time of the network. There is a saving effect.

Trouble ticket, issue, status management

Description

Method and apparatus for state management for generating trouble ticket for trouble recovery in telecommunication network {method and apparatus for generating management ticket in tele-communication networks}

1 is a conceptual schematic diagram of a state management device for failover of a communication network.

2 is a state transition diagram used for state analysis and update.

3 shows a state transition mechanism in consideration of the relationship between network elements.

Figure 4 is a flow diagram of the failure information collection, status analysis, trouble ticket issuance mechanism.

<Description of Symbols for Main Parts of Drawings>

100: network management and device management module

101: Asynchronous transmission mode network management and device management system

102: Frame relay network management and device management system

103: Internet protocol network management and device management system

104: disability collection unit 105: status analysis unit

106: configuration information management unit 107: status information management unit

108: trouble ticket management unit 109: status management module

110: maintenance management system

The present invention provides a communication network for efficiently issuing a trouble ticket to a maintenance management system for issuing a work instruction ordering a repair worker to repair a failure in case of a network component failure in the communication network. The present invention relates to a state management method and apparatus for issuing trouble tickets in a disaster recovery system.

In general, in order to recover a failed network component, it is necessary to first identify the failed network component. Most network management systems (NMS) or element management systems (EMS) have a failure monitoring function. Is provided. In the event of a network component failure, maintenance personnel should go to where the network component is located and repair it or replace it. In this case, the work order is given to the maintenance personnel. The work order is issued by the maintenance management system. The maintenance management system issues work orders to the operation maintenance personnel, and is in charge of a series of tasks related to maintenance, such as writing a work completion confirmation, work history management, and work statistics after work completion.

In the conventional system configured as described above, many parts are automated, which significantly reduces maintenance time, thereby contributing to providing smooth network service. However, NMS or EMS operator issuing TT for failback of network components. There is a problem in that TT is repeatedly issued or multiplely issued by intervening or simply converting and publishing disability information into TT.

Accordingly, the present invention has been made to solve the above problems, the present invention is to reduce the issuance of trouble tickets in the process from the occurrence of the failure to the maintenance personnel issuance of work orders for the recovery of trouble and duplicate trouble tickets It is an object of the present invention to provide a status management method and apparatus for issuing trouble ticket for trouble recovery in a communication network to suppress a publication and to provide a smooth communication network service with efficient and quick failure recovery.

Here, in order to achieve the above object, the present invention should consider whether a trouble ticket issuance is issued based on the failure information of the network element and the previously generated failure information. In addition, a trouble ticket issuance method should be presented that considers the correlations among network components in a comprehensive manner.The specific configuration should include: a) Checking if a failure component is registered in the status information list and collecting the failure information. If not registered, newly registering and setting a status to a failure state; b) collecting the event after setting the current state to the fault state in step (a), and setting and determining a new state by analyzing current state information, collected events, and state of upper and lower components; c) issuing a trouble ticket from the maintenance system when the new state set as a result of the determination in step (b) is a trouble ticket issuing state; And d) canceling the trouble ticket issuing and returning to the normal state according to the canceling status if the new state set as a result of the determination in step (b) is not a trouble ticket issuing state and deleting the status information from the list. It features.

In addition, the present invention provides a fault collection unit 104 for collecting fault information from an asynchronous transmission mode network, a frame relay network, an IP network, etc. for failing back a faulty network component in a communication network; A configuration information management unit 106 which performs a function of constructing, changing, and inquiring configuration information of each network; A state information management unit 107 which performs a state management function of generating, deleting, changing, and storing state information of network elements; The status information is updated by comparing and analyzing the fault event input from the fault collection unit 104, the timer event and the task completion event set therein with the current state stored in the configuration information management unit 106 and the state information management unit 107. A state analysis unit 105 for requesting ticket issuance and cancellation; And a function of issuing or canceling a trouble ticket to the maintenance management system 110 at the request of the state analysis unit 105, and being notified of the end result of the work based on the trouble ticket in the maintenance management system 110. Characterized in that the trouble ticket management unit 108 to perform a management function for sending a task completion event to the analysis unit 105.

The present invention relates to a state management method and apparatus for collecting trouble information of various network elements constituting a communication network and issuing a trouble ticket to a maintenance management system. Explain.

1 is a schematic diagram conceptually illustrating a network component state management and trouble ticket management apparatus for failover of a communication network to which the present invention is applied.

Multi-layer networks consist of Asynchronous Transfer Mode (ATM) networks, Frame Relay (FR) networks, and Internet Protocol (IP) networks established in accordance with ITU-T G.805, which defines a hierarchical network structure. Etc. form a multi-layer network by interworking with a network or a server network providing a service and a network or a client network receiving the service. The specific configuration here includes a multi-layer network 100, a state management module 109 and a maintenance management system 110.

The multi-layer network 100 is asynchronous transmission mode network management and device management system (101: ATM NMS / EMS), frame relay network management and device management system (102: FR NMS / EMS) and Internet protocol network management and The device management system 103 is configured to include IP NMS / EMS, and each system is individually managed.

The state management module 109 is composed of a fault collecting unit 104, a state analysis unit 105, a configuration information management unit 106, a state information management unit 107 and a trouble ticket management unit 108.

The fault collection unit 104 collects fault information according to network elements from each system of the multi-layer network 100 and transmits a fault event to the state analyzer 104. The configuration information management unit 106 performs a function of constructing, changing, and inquiring configuration information of each network. The state information management unit 107 performs a state management function of generating, deleting, changing, and storing state information of network elements.

The state analysis unit 105 includes a fault event input from the fault collection unit 104, a timer event set therein, a task completion event coming from the trouble ticket management unit 108, and the like. The status information is updated and analyzed by comparing with the current state stored in 107, and if necessary, requests the trouble ticket management unit 108 to issue a trouble ticket or to cancel the issued trouble ticket.

The trouble ticket management unit 108 issuing or canceling a trouble ticket to the maintenance management system 110 at the request of the state analysis unit 105 and a task based on the trouble ticket in the maintenance management system 110. In response to the termination result of the state analysis unit 105 performs a series of management functions associated with the trouble ticket, such as sending a job completion event.

2 shows the state information of the network component stored in the state information management unit 107 and the state transition mechanism used in the state update in the state analysis unit 105 according to the present invention.

Each network component combines the fault information and the trouble ticket issuance information, which is the normal state (P1), fault state (P2), trouble ticket issuance state (P3), recovery state (P4), and trouble ticket operation completion state ( P5) and trouble ticket canceled state P6. Each state transitions to another when it receives an event. The event includes a failure event (Down, Up), a timer event (T1 TimeOut, T2 TimeOut) and a trouble ticket work completion event (WorkDone).

Here, the P1 state indicates the normal function of the network component, and when the cause of failure is solved in an abnormal state, the state returns to the P1 state. When P1 state receives Down event that causes network component failure, it transitions to P2 state. The P2 state is a preliminary state for issuing a trouble ticket and sets timer 1 (T1) in order to withhold the issue of a trouble ticket in case of a temporary failure. In the P2 state, if the Up event is received when the fault of the network component is resolved, the T1 is canceled and the P1 state is entered. Therefore, when the set T1 time passes (T1 TimeOut), the state transitions to P3 state, and a trouble ticket is issued. If Up event is received in P3 state, it is in P4 state and timer 2 (T2) is set. If the WorkDone event occurs, cancel T1 and return to P1 state. Otherwise, if T2 time passes (T2 TimeOut), request for canceling the trouble ticket in P6 state and return to P1 state. The P5 state takes into account the order in which the WorkDone and Up events occur.

3 shows a state transition mechanism in consideration of the relationship between network components that are related to each other.

A communication network usually consists of nodes and links, which have components such as ports, boards, shelves, and racks. There is more than one port on a board, and multiple boards make up a self. In the case of a board, it is a component above (inclusive) for the port or child (included) for the self. When one network component is in a failure state (P2), the trouble ticket is ready to be issued. Therefore, trouble ticket issue of the lower component should be suppressed. This is solved by deactivating T1 of the subcomponent in the fault state and preventing the subcomponent from transitioning to the P3 state. The P1 state of the network component is divided into a lower normal state (P11) and a lower fault state (P12) according to whether a lower component of a fault state exists. The P11 state indicates that all subcomponents are normal, and P12 indicates that one or more subcomponents are in a fault state. In P11 state, if the first failure event Down1 (F) among the subcomponents is received and transitions to P2, the upper component transitions to P12, and after that, even if another subcomponent receives Down1 and transitions to P2, the upper component is in P12 state. Keep it. Even if the subcomponent receives the Up1 event and transitions to the P1 state, the parent component remains in the P12 state unless the last subcomponent transitions to the P1 state. When the last lower component transitions to P1 by Up1 (L), the upper component transitions to P11. If the upper component transitions from P1 (P11 or P12) state to P2 state, even if the lower component transitions to P2, T1 cannot be set and it cannot transition to P3 state.

An example of a board component having two ports is described below. Initially, the states of board B, port 1 (P1), and port 2 (P2) are the same as <P1, P1, P11>. If P1 fails, it goes to <P2 + T1, P1, P12> (+ T1 is set with timer T1). In this case, after the timer T1 time of P1 elapses, a trouble ticket related to P1 is issued and becomes <P3, P1, P12>, but when B fails, it becomes <P2, P1, P2 + T1> and T1 set in P1. Disable to prevent P1 from transitioning to P3. In the initial state, B occurs first and P1 fails, but <P2, P1, P2 + T1> states. Since B is P2, T1 is not set in P1. As such, by setting the relationship between the upper and lower components, it is possible to suppress the trouble ticket issuance for the lower priority components.

4 is an overall flowchart of a mechanism for setting a state of a network component from the collected fault information and issuing a trouble ticket.

When the failure information is collected from the configuration information management unit (S1), it is determined whether the failure component is registered in the status information list (S2). Then, if it is determined in step S2 that is not registered in the status information list, it is newly registered and sets the status to a failure state (S3). Then, when setting to the fault state is completed in step S3, the timer event time T1 is set in consideration of the state of the upper component. Once registered in the status information list, the status information is updated by a failure, timer, and trouble ticket work completion event (S4, S5). At this time, T1 is set in consideration of the relationship between the upper and lower components, and it is determined whether the updated state is the trouble ticket issuing state (S6). Then, if it is determined in step S6 that the updated state is the trouble ticket issuing state, a trouble ticket is issued to the maintenance management system (S7), and it is determined whether the new state is a normal state (S10).

On the other hand, if it is determined in step S6 that the updated status is not the trouble ticket issuing status, it is determined whether the current status is the trouble ticket canceling status (S8). If it is determined in step S8 that the current state is a trouble ticket canceling state, the issue of the trouble ticket is canceled and returned to the normal state (S9), and then, the state is deleted from the state information list and the state management of the component is terminated ( S11).

If it is determined in step S8 that the current state is not the trouble ticket cancellation state, it is determined whether the state is normal again (S10). At this time, if it is determined in step S10 that the normal state is not returned to step S4 to repeat the loop to perform the next event.

As described in detail above, the present invention collects, analyzes, and manages fault information generated in a component of a network, and automatically executes a series of tasks leading to a trouble ticket. It is a state management method that combines upper and lower components and trouble ticket issuance to prevent unnecessary issuance of trouble tickets and trouble tickets, thereby eliminating inefficient elements, thereby reducing the maintenance cost and time of communication network. .

In addition, preferred embodiments of the present invention are disclosed for the purpose of illustration, those skilled in the art will be able to various modifications, changes, additions, etc. within the spirit and scope of the present invention, such modifications and modifications belong to the following claims You will have to look.

Claims (6)

a) checking that failure components are registered in the status information list when collecting the failure information, and registering new status and setting the status to the failure status if not registered in the status information list; b) collecting the event after setting the current state to the fault state in step (a), and setting and determining a new state by analyzing current state information, collected events, and state of upper and lower components; c) issuing a trouble ticket from the maintenance system when the new state set as a result of the determination in step (b) is a trouble ticket issuing state; And d) canceling the trouble ticket issuance and returning to the normal state according to the issue cancellation status and deleting the status information from the list if the new state set as a result of the determination in step (b) is not a trouble ticket issuing state; State management method for issuing trouble tickets for failover in a communication network. The method of claim 1, If the trouble ticket is not canceled in step (d), it is determined whether the current status is normal. If the status is normal, the status information is deleted from the list. If the status is not normal, the event information is collected and analyzed again. The state management method for the trouble ticket for troubleshooting in the communication network further comprising the step of setting a. The method of claim 1, In order to automatically determine whether the trouble ticket is issued and manage the failure information and the trouble ticket issuing information by combining the status of the network components in the normal state (P1), failure state (P2), trouble ticket issuing state (P3), A status management method for troubleshooting trouble ticket issuance in a communication network, characterized in that the management status (P4), trouble ticket operation completion state (P5) and trouble ticket cancellation state (P6). The method of claim 1, The analysis of the state of the lower component is analyzed by managing the normal state (P1) of the upper component encompassing the individual states of the lower components divided into the lower normal state (P11) and the lower fault state (P12), When a state of a component becomes a failure state (P2), trouble recovery for communication in the communication network, characterized in that the state of the lower component is prevented from changing from the trouble state (P2) to the trouble ticket issuing state (P3) State management method for ticket issuance. a) means for confirming that the faulty component is registered in the status information list upon collecting the fault information, and registering a new and setting the state to the fault state if it is not registered in the status information list; b) means for setting and determining a new state by collecting the event and analyzing the current state information, the collected events, and the state of upper and lower components after setting the current state to the fault state in the (a) means; c) means for issuing a trouble ticket when the new state set as a result of the determination in said (b) means is a trouble ticket issuing state; And d) means for canceling the trouble ticket issuance and returning to the normal state and deleting the status information from the list if the new state is not determined as the trouble ticket issuing state determined by the means (b). A state management device for issuing trouble tickets for failover in a communication network. A fault collecting unit 104 for collecting fault information from an asynchronous transmission mode network, a frame relay network, an IP network, etc. for failback of a faulty network component in a communication network; A configuration information management unit 106 which performs a function of constructing, changing, and inquiring configuration information of each network; A state information management unit 107 which performs a state management function of generating, deleting, changing, and storing state information of network elements; The status information is updated by comparing and analyzing the fault event input from the fault collection unit 104, the timer event and the task completion event set therein with the current state stored in the configuration information management unit 106 and the state information management unit 107. A state analysis unit 105 for requesting ticket issuance and cancellation; And At the request of the state analysis unit 105, a function of issuing or canceling a trouble ticket to the maintenance management system 110 and the end result of the operation based on the trouble ticket in the maintenance management system 110 are notified of the state analysis. A trouble management system for trouble recovery trouble communication in a communication network, comprising a trouble ticket management unit 108 which performs a management function of sending a work completion event to the unit 105.

Images