KR20040042344A - Assembled-facility based trouble ticket processing system and method thereof under toll backbone transmission network - Google Patents

Abstract

PURPOSE: A system and a method for processing a failure list based on a connection transmission line in a toll basic industry transmission network are provided to easily analyze failure by writing the failure list on the basis of the connection transmission line in the toll basic industry transmission network of multi-vendor environment. CONSTITUTION: A device alarm collecting unit(20) collects alarm information from transmitting devices(10). A failure alarm analyzing unit(30) analyzes collected alarm information on the basis of a connection transmission line. A failure list issuing unit(40) issues a failure list on the basis of analyzed information. A failure list processing unit(50) interworks with a client, and processes the failure list. A database(60) stores information used for issuing the failure list.

Description

Assembled-facility based trouble ticket processing system and method described under toll backbone transmission network}

The present invention relates to a failure slip processing system and method centered on a connection transmission path in a long distance transmission network, and more specifically, to a failure slip for failures generated in a long distance transmission network in a multi-vendor environment based on the connection transmission path of the transmission network. It relates to a trouble slip processing system and method to be created.

In the present invention, the multi-vendor environment means that various manufacturers exist for a single device type, and that communication interfaces and fault message formats used by each manufacturer vary.

Conventionally, the fault slip processing system can be largely classified into an apparatus-based fault slip processing system and an automatic fault slip processing system for analyzing alarm correlation.

The fault slip processing system based on the above device has the advantage that the fault slip processing system configuration is simple because the fault slip is issued for each independent device.However, in the current transmission network in which several transmission devices are complicated, it is difficult to identify the cause of the failure. There is a disadvantage of difficulty.

In addition, the alarm correlation analysis automatic failure slip processing system, which is widely used in recent years, has the advantage of providing a cause of failure by collecting a plurality of alarms generated in the transmission network and analyzing the correlation of the alarms. The disadvantage is that it is complex and puts a lot of load on the system.

In particular, creating rules that correlate alarms in long-distance transmission network environments in complex multivendor environments is not only difficult, but even if they provide the cause of failure, it is not reliable for operators to recover from them based on the results. There is a problem that falls.

Hereinafter, a conventional fault slip processing system will be described with reference to the drawings.

The system shown in FIG. 1A shows 2.5G transmission of multiplexers 3-1, 3-6, 155M transmitters 3-2, 3-5, and 2.5G transmitters 3-3, 3-4. The structure of the device, Figure 1b is a table showing the alarm that occurs in the relevant device in the event of failure of each point.

The abbreviation of the alarm described in FIG. 1B is as follows.

AU3-AIS (AU3 Alarm Indication Signal)

DS3 Alarm Indication Signal (DS3-AIS)

DS3-LOS (DS3 Loss Of Signal)

Loss of Signal (LOS)

Muliplex Section Alarm Indication Signal (MS-AIS)

Muliplex Section Remote Defect Indication (MS-RDI)

Muliplex Section Far End Receive Failure (MS-FERF)

Virtual Container Level 3 Far End Receive Failure (VC3-FERF)

When an alarm such as that shown in Fig. 1 occurs, the fault slip processing system based on the device issues a fault slip for each independent device. This is because when a fault alarm is derived from one device by one cause, such as when the optical path between the 2.5G transmitter 3-3 and the 2.5G transmitter 3-4 is cut. It is difficult to pinpoint the cause of the failure because it does not grasp all the alarms that compose the alarm and handles only the alarm that occurred in each device. In particular, the system configured for the long-distance circuit from Seoul to Busan has a disadvantage that it is difficult to accurately analyze the cause of failure because the number of devices constituting it is very large.

In the case of the automatic correlation system for alarm correlation analysis, which has been widely used recently, it has the advantage of collecting a plurality of alarms generated in the transmission network and analyzing the correlation of the alarms to clearly identify the cause of the failure. In addition to the large number of cases that can occur, the data generated from each device is different because there are many different types and types of devices currently used in long-distance transmission networks, and each device manufacturer uses a slightly different error alarm generation algorithm. There are many difficulties in identifying the cause of failure by making a rule that analyzes the correlation of alarms by collecting all of them. Even if the cause is provided directly, the operator is not reliable enough to recover the failure based on the result. There is this.

Accordingly, the present invention has been made to solve the above-described problems, and the operator prepares a failure slip based on a connection transmission line in a long-distance transmission network of a multi-vendor environment constructed with various kinds of devices to facilitate an operator to analyze the failure. Its purpose is to provide a system and method for handling trouble slips.

Figure 1a is a block diagram of a conventional fault slip processing system.

Figure 1b is a table showing the alarm that occurs in the relevant device in the event of failure of each point.

2 is a block diagram of a transmission network managed by a fault slip processing system of the present invention.

3A, 3B, and 3C are exemplary views of a system configuring a transmission network.

4 is a block diagram of a fault slip processing system centered on a connection path in a long-distance transmission network according to an embodiment of the present invention.

5 is a detailed configuration diagram of the device alert collection unit shown in FIG.

FIG. 6 is a correlation diagram of tables constructed in the database shown in FIG. 4. FIG.

7 is a detailed breakdown of each table shown in FIG. 6;

8 to 9 are flowcharts for explaining a failure slip processing method centered on the connection transmission line in the long-distance transmission network according to an embodiment of the present invention.

FIG. 10 is a diagram illustrating a field value change of a failure slip record applied to the present invention.

11 is a diagram for a failure slip processing state.

12 is a trouble slip processing authority table.

Figure 13 is a screen display example of the slip detail according to the present invention.

In the long-distance transmission network according to a preferred embodiment of the present invention for realizing the above object, the failure slip processing system centered on the connection transmission path,

A device alarm collection unit for collecting alarms by collecting transmission devices;

A failure alarm analysis unit analyzing the collected alarm based on a connection transmission path;

A fault slip issuing unit for issuing a fault slip based on the analyzed alarm;

A fault slip processing unit which processes the fault slip in association with a client;

It characterized in that it comprises a database for storing the information used for issuing the fault slip.

In the long distance transmission network according to a preferred embodiment of the present invention for realizing the above object, a failure slip processing method centered on a connection transmission path,

A first step of extracting a logical slot number for the alert by analyzing an alert occurrence location indicating a physical location of the transmitter where the alert is generated when alerts are collected from the transmitters;

Extracting a connection transmission path for the slot number;

And a third process of issuing a fault slip for the extracted connection transmission line.

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

2 is a block diagram of a transmission network managed by a fault slip processing system centered on a connection transmission line in an inter-urban transmission network according to a preferred embodiment of the present invention.

According to Fig. 2, it is composed of one long-distance transmission network and a plurality of downtown transmission networks divided by administrative districts. When providing a line from one downtown area to another downtown area for unification of management, the long-term transmission network must be used. have.

For example, the path used to transfer data from node 1-9 of local transport network A to node 1-14 of local transport network C is node (1-9) → node (1-21) → subordinate. Subunit (1-1) → transmission path 1 → transmission path 2 → subordinate unit (1-6) → node (1-25) → node (1-14).

As shown in the figure, the transmission path is installed between the transmission devices 1-17, 1-18, 1-19, 1-20, and the transmission devices 1-17, 1-18, 1-19, Enable data transmission between 1-20).

The transmission apparatuses 1-17, 1-18, 1-19, and 1-20 are subordinate units 1-1, 1-2, 1-3, 1-4, 1-5, 1-6, 1-7, 1-8) is used to branch (ADD / DROP) the data of the local transport network.

In FIG. 2, in order to service four lines required by the downtown area headquarters, the long-distance transmission network provides routes of ①, ②, ③, and ④, which is a connection transmission path.

More specifically, the configuration of the connection transmission line ① is composed of the subordinate unit (1-3), the transmission path 1 and the subordinate unit (1-4), which is a node (1-11) in the local transmission network A. C) configured to provide circuit service connected to nodes 1-24 in the local transport network B).

The configuration of the connection transmission line ② is composed of the subordinate unit (1-5), the transmission path 2, the transmission path 3, and the subordinate unit (1-7), which is the node (1-13) in the local transmission network B. Connection path configured to provide circuit service connected to nodes 1-15 in the local transmission network D.

The configuration of the connection transmission path ③ is composed of the subordinate unit 1-1, the transmission path 1, the transmission path 2, and the subordinate unit 1-6, which are located at the node 1-9 in the local transmission network A. Connection path configured to provide circuit service connected to nodes 1-14 in local transmission network C.

The configuration of the connection transmission path ④ is composed of the subordinate unit (1-2), the transmission path 1, the transmission path 2, the transmission path 3, and the subordinate unit (1-8). -10) is a connection transmission path configured to provide a circuit service connected to the nodes 1-16 in the local transmission network D.

As can be seen from the above description, the long-distance transmission network can be regarded as a set of transmission paths prepared for data transmission between the local transmission networks. Therefore, when the long-distance transmission network that provides a large capacity transmission path can have a big impact on the entire transmission network itself, the most important factor of the network management is the connection transmission path allocated to support the circuits currently in service. admit.

The types of systems constituting the long-distance transmission network and the local transmission network are as shown in FIGS. 3A to 3C.

FIG. 3A is an end-to-end system configured by directly connecting two nodes, FIG. 3B is an advanced end-to-end form, and is a linear ADM (Add Drop Multiplexer) structure in which a branching function is performed at an intermediate node. It is a ring type system in which two nodes are connected in a ring shape. The ring system is the most used form recently.

As shown in FIG. 4, a system for processing a fault slip based on a connection transmission path for a transmission network configured as described above includes a device alarm collection unit 20 for collecting alarms by concentrating the transmission devices 10; Fault alarm analysis unit 30 for analyzing the collected alarms, fault slip issuer 40 for issuing fault slips based on the analyzed alarms, fault slips such as fault check, deadline for the issued fault slips The fault slip processing unit 50 performs a processing function, and a database 60 in which data used in the system is stored.

Detailed configuration of the device alarm collection unit 20 will be described with reference to FIG.

If the transmission apparatus 10 constituting the current transmission network is largely classified, it may be divided into a digital circuit distribution apparatus 10a, a synchronous transmission apparatus 10b, and a wavelength division transmission apparatus 10c. The interface 21 used to collect alarms by collecting the transmission device 10 is Byte-Oriented type interface 21a, which is a message form defined by the manufacturer, and TL (Transaction Language) / 1 (which is widely used in North America). 21b) and Common Object Request Broker Architecture (21BA) and Common Management Information Protocol (CMIP) 21d.

The server unit 22 is composed of a plurality of servers 22a-22h for collecting alerts or transmitting commands to the device by collecting the alarm 10 through the interface 21. The server unit 22 transmits the collected alarms to the failure alarm analysis unit 30.

The function of each server constituting the server unit 22 will be described below.

The Sm16 server 22a collects alerts from the synchronous transmitter 10b via the Byte-Oriented interface 21a, and the Dxc server 226 receives the digital line distribution device 10a via the TL / 1 interface 21b. Collecting alerts from Wdm server 22c collects alerts from synchronous transmitter 10b and wavelength splitter 10c via CORBA interface 21c.

The Smot server 22d collects the alerts from the synchronous transmitter 10b through the Byte-Oriented interface 21a, and the Smt4 server 22e collects the alerts collected by the Sm16 server 22a. Lu25 server 22f collects alerts from synchronous transmitter 10b and wavelength splitter 10c via CORBA interface 21c, and Nt10 server 22g collects alerts collected by Wdm server 22c. Sm64 22h collects alerts from the synchronous transmitter 10b via the CMIP interface 21d.

On the other hand, the correlation of the table built in the database 60 shown in FIG. 4 is as shown in FIG.

First, the alarm status table 61 is a table for storing the current alarms generated in the transmission apparatus associated with the connection transmission path, the failure slip table 62 stores information on the failure slip issued based on the connection transmission path. . Also, the relevant local table 63 is a locality associated with the linkage failure slip, and this data is a table which is later referred to to transmit a failure slip only to the local operator associated with the connection transmission line. The slip detail table 64 is a table that stores a brief description of the link failure slip, the configuration of the link transmission path, and two-dimensional failure analysis data using alarms generated by all devices configuring the link transmission path. The slip repair table 65 is a table that records the details of the cause of the failure and repaired by the operator based on the slip after the breakdown slip is issued.

Details of the tables 61-65 are as shown in FIG. 7.

First, the serial number of the alarm status table 61 indicates the unique number assigned to the fault alarm, and the wide station is the name of the broad station of the telephone station where the alarm occurred, and the occurrence date and time means the time when the alarm occurred, and the connection transmission path has occurred. Indicates the connection channel name associated with the alert. The type indicates the level of connection transmission path (D3, S1, S4, S6, etc.), and the system name and local name mean the device that generated the alarm by combining the two fields. Slot means a logical port number used by a connection channel. System type refers to the system configuration type (end-to-end, linear ADM, ring) and device type refers to the type of transmission device (SMT1, SMT4, SM16, NT25, SM16B, FLCB, DXC13, WDCS3, WDCS7, WDCS8…). . The node number represents the node number of the device that is currently alerted in the system. The unit indicates the physical unit (TIU, TI1U, TI4U…) where the alarm occurred in the device, the signal type means the alarm signal type (MS, OPTICAL, UNIT…) and the occurrence point indicates the alarm occurrence point (DS3 / 11, G3 / TIU.2A…) and the alarm items represent the generated alarm items (LOS, AIS…). In addition, alarm level indicates alarm level such as CL, WR, MN, MJ, CR, and service effect indicates whether it is affecting the service in use.

The fault number field of the fault slip table 62 is a fault slip identifier created by linking an 8-digit occurrence date and a 5-digit serial number. The link path is the link path name associated with this fault document. The fault spot indicates the fault spot where the cumulative alarm occurred and the cumulative grade indicates the highest status among the alarms that occurred in the fault document. The current class indicates the highest status among the alarms currently occurring in the fault document. The failure period indicates the duration (in seconds) of the failure grade recorded in the cumulative grade. This value is calculated as the current failure time minus the previous failure time using the failure time when the cumulative grade of the document decreases. The number of failures is the number of times the state recorded in the cumulative grade is repeated, and the failure time represents the tick value of the current time to calculate the failure period. Cumulative alarms are alarms corresponding to the status recorded in the cumulative class and current alarms are alarms corresponding to the status recorded in the current class. The processing status indicates the processing status of the trouble slip. The values are new (0), confirmation (1), and closing (2). The update time represents the update time of the fault slip.

For reference, the tick value is used as a unit of time, and the tick value is a term commonly used in a Unix environment, and is a cumulative number of seconds since January 1, 1970.

The fault number field of the related station table 63 is the same as the fault number format of the fault slip, and the telephone station name is the number of the fault slip, that is, the name of the telephone station associated with the fault slip issued based on the connection transmission path. The country name is the name of the country concerned. The classification shall be made of the station where the failure occurs, among the stations constituting the connection path, with the other station.

The fault number of the document detail table 64 is the same as the fault number format of the fault document, and the document content has detailed information on the fault document.

The fault number of the document repair table 65 is also the same as the fault number form of the fault document. The deadline and the deadline indicate the date on which the operator has repaired and removed all alarms associated with the trouble slip, and the name of the operator. The fault grade, fault time, and number of faults are identical to those in the fault slip table. The cause of the fault indicates the cause of the fault slip and the repair indicates the repair taken by the operator for the fault.

Hereinafter, a failure alarm analysis procedure will be described in detail with reference to the flowchart shown in FIG. 8.

When the failure alarm generated from the transmission device 10 is collected by the device alarm collection unit 20 (S8-1), the alarm state table 61 is searched to determine whether the failure alarm is a new alarm (S8-2). ). As a result of the determination, if it is a new alarm, the alarm record for the fault alarm is stored in an alarm state table (S8-3). If the fault alarm exists, the occurrence date and alarm level are updated (S8-4).

Then, the alarm state table 61 is searched to determine whether the failure alarm affects the service (S8-6), and when the determination result determines that the failure alarm does not affect the service, the analysis is finished. do. On the other hand, if it affects the service (Yes in S8-6), the logical slot which is an important key for searching the connection transmission path stored in the database by analyzing the alarm occurrence location indicating the physical location of the transmission device where the failure alarm occurred Obtain the number (S8-7). Search for the connection transmission path using the slot number (S8-8), if there is a connection transmission path (Yes in S809), perform a trouble slip issue process (S8-9), and if the connection transmission path does not exist (S8-8), In S809, the analysis of No) is finished.

Next, the process of issuing a fault slip will be described in detail with reference to the flowchart shown in FIG. 9.

If the fault alarm is associated with a specific connection transmission path (S9-1), the failure transmission table table 62 is searched for the connection transmission path as a key value (S9-2), and if the new failure document does not exist (S9-2). Yes) In S9-3, a unique fault document number is generated by concatenating the 8-digit occurrence date and 5-digit serial number (eg 20020809-00001) (S9-4).

Based on the fault alarm, necessary information is stored in the fault slip table 62 (S9-5), and then a list of related locations constituting the connection transmission path is obtained (S9-6).

The relevant local list is used to deliver a new fault record or an updated fault slip only to a locality related to the fault slip, or to be used for the authority check for authority to process fault slips. The database is searched to obtain a list of devices constituting the connection transmission path (S9-7). The device list is used as the X-axis indicating the configuration of the connection transmission path in the fault slip details. The details of the trouble slip are stored in the slip detail table 64, and the related countries are notified (S9-9).

If, as a result of the determination in step S9-3, a failure slip associated with the connection transmission path already exists (No), the current highest alarm level (hereinafter referred to as the current rating) and the failure slip that bring the connection transmission path as a key value from the alarm status table are present. In the table, the previous cumulative alarm class (hereinafter, referred to as "cumulative class") which obtained the connection path as a key value is compared (S9-10). As a result of the comparison, if a failure grade rise occurs because the current grade is higher than the previous cumulative grade (Yes in S9-10), the cumulative grade and the cumulative alarm are updated (S9-11, S9-12). The number of faults is reset to zero, the fault duration is set to 1, and the fault time is reset to the current tick value (S9-13, S9-14, S9-15). Subsequently, the failure slip record 62 is updated on the basis of the change data (S9-3), and the update failure slip details are notified to the relevant station (S9-24).

On the other hand, in the state where the failure grade is not increased (No) as a result of the determination in step S9-10, the previous current alarm grade (hereinafter referred to as current grade) and previous cumulative grade which brought the connection transmission path as a key value from the failure slip table 62 If a different recurrence situation with the same current rating and previous cumulative rating occurs (Yes in S9-16), increase the number of failures by one (S9-17), reset the failure time to the current tick value (S9-18), The processes of steps S9-23 and S9-24 described above are performed.

In addition, if a failure recovery situation occurs (No in S9-16), and a failure recovery situation occurs in which the previous and previous cumulative grades are the same and the current and previous cumulative grades differ (Yes in S9-19), the tick value of the current time ( Calculate the failure period by subtracting the previous failure time tick value (hereinafter referred to as the previous tick value) from which the connection transmission path is obtained as a key value from the failure slip table (S9-20), and setting the failure time as the current tick value (S9-). 21), the processes of steps S9-23 and S9-24 described above are performed.

Then, if a state change occurs in which the current rating differs from the previous current rating or a condition that does not satisfy all of the above conditions is maintained (Yes in S9-22), the failure time is set to the current tick value (S9-21). The process of step S9-23 and step S9-24 is performed.

FIG. 10 is a diagram illustrating a change in the field value of the failure slip record 65 when a failure slip is newly issued and the failure slip is updated through the failure slip issuance procedure shown in FIG. 9.

In FIG. 10, the current class is the current recall alarm class in which the connection path is searched as a key value in the alarm status table 61, and the previous cumulative class is the previous cumulative class in which the connection path is searched as the key value in the fault slip table 62. The previous current rating is the previous current rating that retrieved the connection path as a key value from the fault slip table 62, the number of failures is the number of times the cumulative rating is repeated, and the failure period is the duration of the failure rating recorded in the cumulative rating. (In seconds), and the fault time represents the current time in ticks.

11 is a diagram of a fault slip processing state.

As shown in Fig. 11, when the connection slip is issued for the first time, the processing state becomes new (11-1), and the operator of the telephone station executes a slip processing command for confirming the failure details through the trouble slip operation program. The status changes to OK (11-2). At this time, this checking function can be performed several times by multiple operators. The purpose is to post their opinions on the trouble slip by chatting with several operators in the relevant places in the transmission line. I want to help. Finally, when the operator identifies the cause of the failure, completes troubleshooting, and executes a document processing command that closes the trouble slip, the state transitions to the deadline (11-3).

12 is a trouble slip processing authority table.

The trouble slip processing command has a list, confirmation, and deadline. The user login authority used in the trouble slip processing system is divided into a telephone station, a wide area station, and a center. A user logged in with the authority of the telephone company can see only the trouble slip list related to his locality and can check and close the slip. A user logged in with the authority of a wide area station can view a list of trouble slips generated by a telephone station under his jurisdiction, but cannot check or close the function. A user logged in with center authority can see a list of fault documents from all telephone offices, but cannot check or close them. This is intended to assign fault slip processing functions only to the telephone company employees who operate the equipment directly.

Hereinafter, with reference to the block diagram shown in Figure 4 will be described the overall operation of the fault slip processing system centered on the connection transmission line in the long-distance transmission network according to an embodiment of the present invention.

When the message " TICKET LIST " according to the document list command is sent from the document processing client 70 to the fault document processing section 50, the fault document processing section 50 according to the user authority can display the fault document table 62 and the associated local table ( 63) and transmits the trouble slip list to the slip processing client 70.

In addition, when a TICKETCHECKED message for checking the trouble slip is input from the slip processing client 70, the trouble slip processing portion 50 changes the processing status of the trouble slip from "new" to "check" and the slip detail table The checker, the confirmation location, the confirmation date and time, and the result of the confirmation are transmitted to the document processing client 70.

When the trouble slip processing unit 50 transmits a TICKET CLOSED message corresponding to the document closing command from the slip processing client 70, the failure slip processing unit 50 first performs an authority check to determine whether the user can close the trouble slip, and the corresponding trouble slip in the failure slip table. Checks for the existence of. If the current grade of the fault document is not CL, reject the document closing command. If the fault document exists and the current grade is CL or higher, delete the document from the fault document table and insert the repaired document in the document repair table. Add the breakdown details to the following table detail table. Finally, the result is transmitted to the document processing client 70.

Figure 13 shows an example of the screen display of the slip details according to the present invention. According to FIG. 13, a schematic description of the fault slip is displayed at the top of the screen, and details of the selected slip are displayed at the bottom of the screen.

According to the present invention as described above, in a complex transmission network consisting of synchronous transmission equipment, digital line distribution devices and wavelength division transmission devices provided by a number of equipment manufacturers, As the operator can easily identify the cause of the failure alarm and cope with it quickly, the reliability of network management can be improved.

On the other hand, the present invention is not limited to the above-described embodiment, but can be modified and modified within the scope not departing from the gist of the present invention, such modifications and changes should be regarded as belonging to the following claims. will be.

Claims (8)

A device alarm collection unit for collecting alarms by collecting transmission devices; A failure alarm analysis unit analyzing the collected alarm based on a connection transmission path; A fault slip issuing unit for issuing a fault slip based on the analyzed alarm; A fault slip processing unit which processes the fault slip in association with a client; And a database for storing the information used for issuing the fault slip. The method of claim 1, The device alarm collector An interface unit with the transmitters; Connection system based on the fault transmission line in the long distance transmission network, characterized in that the server unit consisting of a plurality of servers to collect the alarm by collecting the alarm or transmit a predetermined command to the transmission device through the interface unit. The method of claim 1, The database is Alarm status table that stores the current alarms generated by the transmission device related to the connection channel, fault table table which stores information on the trouble slip generated based on the connection path, and locality having a connection with the connection path. Table that stores two-dimensional failure analysis data using relevant local table for storing information, brief description of connection route fault slip, configuration of connection route, and alarms generated by all devices in the connection route. Table, a slip repair center processing system of the connection transmission line in the long-distance transmission network, characterized in that consisting of a table repair table for storing information about the failure slip connection route issued. A first step of extracting a logical slot number for the alert by analyzing an alert occurrence location indicating a physical location of the transmitter where the alert is generated when alerts are collected from the transmitters; Extracting a connection transmission path for the slot number; And a third process of issuing a trouble slip for the extracted connection transmission line. The method of claim 4, wherein In the third process If the fault document for the extracted connection transmission path is new, after generating a new fault document number, the information on the alarm is stored in a database, If a failure slip for the extracted connection transmission path already exists, the failure slip centered on the connection transmission path in the long-distance transmission network is characterized in that the database is updated by comparing the current rating with the previous cumulative rating and reflecting the result of the comparison. Treatment method. The method of claim 5, wherein As a result of the comparison between the current grade and the previous cumulative grade, if the failure grade is increased, the failure frequency is reset to 0, the failure period is set to 1, the failure time is reset to the current tick value, and the database is updated based on the change data. And afterward, notifying the relevant branch of the updated failure slip. The method of claim 5, wherein As a result of the comparison between the current grade and the previous cumulative grade, if the failure occurs, the number of failures is increased by one, the failure time is initialized to the current tick value, the database is updated based on the change data, and then updated in the relevant station. A failure slip processing method centered on a connected transmission line in a long distance transmission network, wherein the failure slip is notified. The method of claim 5, wherein As a result of the comparison between the current grade and the previous cumulative grade, in a failure recovery situation, a failure period is calculated by subtracting a tick value of a previous failure time from a tick value of a current time, setting the failure period as a current tick value, and based on the change data. And updating the database, and notifying the relevant branch of the updated failure slip.