KR100304104B1 - Toll transmission network fault log management method - Google Patents

Abstract

1. TECHNICAL FIELD OF THE INVENTION

The present invention relates to a long-distance transmission network failure history management method.

2. Technical problem to be solved by the invention

The present invention provides a method for efficiently performing tasks such as fault reception, history, damage line calculation, report data generation by inputting various fault-related details into a database in managing a long-distance transmission network using the inter-national trunk line management system. To provide.

3. Summary of the Solution of the Invention

1. A method for managing a long-distance network fault history in a long-distance network fault history management system, the method comprising: a first step of establishing a switching database in preparation for a change in a transmission path when a fault occurs and determining whether the transmission path is abnormal; A second step of inputting a result after troubleshooting at the operating station where the failure occurred, and generating a history at the receiving station that first received the failure, as a result of the determination in the first step; A third step of performing a repair by searching for the transfer database and instructing a transfer if the abnormality is determined as a result of the first step; And a fourth step of checking the transmission path recovery time according to the type of the damaged facility restored by the troubleshooting, and generating a history by inputting the recovery result.

4. Important uses of the invention

The present invention is used to manage the long distance transmission network.

Description

Toll transmission network fault log management method

In the present invention, when managing a long distance transmission network by using a trunk management system (Trunk Management System: hereinafter referred to as "TRUMAN"), various fault-related contents are inputted into a database to calculate fault reception, arrangement, history, and damage line. The present invention relates to a method for efficiently performing tasks such as generating report data, and more particularly, to a computer-readable recording medium recording a long-distance transmission network failure history management method and a program for realizing the same.

In general, the long-distance transmission network accommodates a large line via an optical cable, so that many failures occur when a failure occurs.

Therefore, the operation department should recognize the failure situation as soon as possible and report it to the head office, and the head office should establish appropriate countermeasures and instruct the operation department to minimize the time taken for recovery. As a result, a series of tasks related to failures are processed immediately online, reducing the recovery time and increasing the line usage fee, and all failure facilities have a history so that the operator can predict the possibility of future failures.

However, in the prior art, when the failure is recognized, the transfer plan finds the bypass transmission path, transfers it, and reports it to a higher authority or the head office by telephone. As a result, numerical or statistical data is incorrectly calculated or transmitted, and the failure is received. In addition to the longer time required for reporting, repair, and closing, it is also very important to identify damage lines due to breakdowns. Toll Circuit Administration System (TCAS) Because of the calculation through the lack of accuracy. It was also difficult to prepare fault statistics because there was no history management of the faults, and there was a problem that the data related to the faults were extremely inadequate.

The present invention devised to solve the above-mentioned problems, the long-distance transmission network for efficiently handling the fault-related tasks through the onlineization of fault reception, reporting, closing, etc., the accurate calculation of the damage line and the database of the history management It is an object of the present invention to provide a computer-readable recording medium recording a failure history management method and a program for realizing the failure history.

1 is a configuration diagram of an embodiment of a long-distance transmission network failure history management system to which the present invention is applied.

2 is a flowchart illustrating one embodiment of data to which the present invention is applied.

Figure 3 is an embodiment of a fault management task according to the present invention.

4 is a flow diagram of one embodiment of a general fault management task in accordance with the present invention.

According to the present invention for achieving the above object, in the long distance transmission network failure history management method in the long distance transmission network failure history management system, to establish a switching database for changing the transmission path when a failure occurs, and determines whether the transmission path is abnormal A first step of making; A second step of inputting a result after the troubleshooting at the operating station in which the failure occurs, as a result of the determination in the first step; A third step of generating a history at the receiving station that initially received the failure; A fourth step of, if the abnormality is determined as a result of the determination of the first step, searching for the transfer database to perform a changeover instruction, and performing a troubleshooting; And a fifth step of inputting a result and generating a history according to the type of the damage facility.

In addition, the present invention, in the long-distance transmission network failure history management system in the long-distance transmission network failure history management system, in the long-distance transmission network failure history management system equipped with a large-capacity processor, the transfer database for the change of the transmission path when a failure occurs, and transmits A first function of determining whether the furnace has an abnormality; A second function of inputting a result after troubleshooting at the operating station where the failure occurred, and generating a history at the receiving station that first received the failure, as a result of the determination of the first function; A third function of searching for the transfer database and instructing a transfer if the abnormality is determined as a result of the determination of the first function and repairing the failure; And a computer-readable recording medium having recorded a program for realizing a fourth function of confirming a transmission path recovery time and inputting the recovery result according to the type of the damaged facility restored by the troubleshooting, and generating a history. .

Hereinafter, a preferred embodiment of the present invention will be described in detail with reference to FIGS. 1 to 4.

1 is a configuration diagram of an embodiment of a long-distance transmission network failure history management system to which the present invention is applied.

The database is stored in the main computer of the center 101, the operator station 103 is connected to a remote local area network (hereinafter referred to as "LAN") 102, the operator performs a fault-related operation. There is no limit to the number of operating stations.

2 is a flowchart illustrating an embodiment of data to which the present invention is applied.

When the operator 201 receives a fault (210), the operator 201 inputs a breakdown of the fault (202).

After the repair is completed, the result is input (211) to generate a failure history (203). The failure history is used when calculating the failure statistics 204 later.

In addition, the operator 201 calculates the damage line 206 (212) with reference to the TRUMAN facility database 205 (212) to generate the damage line details (207).

In order to transfer the circuit in the event of a failure, the transfer transmission path is established in advance in the transfer database 208, the transfer plan is output (209), and the transfer database is input, modified, and retrieved (214).

The other available transmission path used to recover a failure when a long-distance transmission network connecting any two points is called a transfer transmission path is called switching.

For fast and accurate transfer, transfer routes are selected in advance and corrected when there is a change of transmission facility or other transmission network. In the past, the transfer route was printed and published annually, so the transfer route, which is frequently changed, could not be properly managed and used by the operating station.

In the present invention, such a transfer channel was constructed as a database 208 to allow all operators in the country to input, modify, search, and print in real time (214). This reduces the cost of booklet printing and enables quick and accurate transfer transfers.

3 is a flowchart of an exemplary fault management task according to the present invention, which is handled by the person in charge of the center 101.

Abnormal failure means failure of DS3 (Digital Signal Level 3) or higher or five or more DS1 lines. Other failures are called general failures.

Failure of class DS3 means that at least one class DS3 line has failed. There are 28 DS1 lines in a DS3 transmission line, and when five or more DS1 lines fail, a DS1 failure is called.

Facilities categorized as faults shall be treated as faults in the event of a fault in the DS3 or higher or five or more DS1 transmission lines as cables, cable transmission lines, transmission lines, systems, leased lines, or trunks of exchanges. If you enter an exchange trunk failure, you must enter the trunk type.

When an abnormal failure is reported and the abnormal failure is recognized (301), the switching database 208 is searched (302) to give a switching instruction (303), and the damage line details (207) are calculated at the failure facility (or line). (304) Report the failure to the head office (305).

On the other hand, when the fault facility is restored or switched over by the transfer instruction in the process 303, and the line is communicated, the fault and repair result are input (306), and it is determined whether the damage facility is the exchange device (307).

As a result of the determination in the process 307, if the damage facility is the switching device or the DCS, the recovery time of the corresponding DS1 transmission path is checked (308), and it is determined whether all are restored at the same time (309). If it is input to the exchange, DCS (310), and if recovered at a different time is input in units of the DS1 transmission path (311).

On the other hand, the determination result in step 307, if the damage facility is not the switching device or DCS, that is, if the damage facility is cable, cable transmission path, B-DCS, DS3 transmission path, optical end station, optical repeater, the corresponding DS3 transmission path Determine the recovery time of (312) to determine whether all are recovered at the same time (313), if the recovery at the same time input to the cable transmission line (314), if it was restored at a different time in units of DS3 Enter (315).

In any case, when the failure input is completed, the result is input (316), and the failure history (203) is generated so that the failure statistics work can be used to close the failure.

Here, the damage line calculations 207 and 304 utilize the TRUMAN facility database 205 with accurate line data to calculate the damage line.

Damaged lines shall include all line details and the number of lines contained in the facility if any facility fails. The line details include the name of the transmission line, the name of the line, the number of facilities per line, whether to operate them, and the distinction between stations.

For example, if the facility that houses the DS3 transmission line is broken, the number of damage lines is 672 (28 * 24, T1) channel lines. Therefore, the method of calculating the damage line calculates and sums all the sub-lines of the line accommodated by the facility inputted as failure in the line database.

The result input 316 is a process of inputting the repair history according to the failure, the action history, the repairman, the repair station, and the like, and the repair time is automatically input. The hysteresis can only be generated at the local site that receives the failure. If repair is requested from another locality, only the repair results are entered.

4 is a flowchart illustrating one embodiment of a general failure management task according to the present invention, which is handled by a person in charge of the relay station.

When a failure is received or a repair request is received (401), it is determined whether the failure of the local station (402).

If it is determined in the process 402 that the local station has failed, the result is repaired (403) and the result is input (404). As a result of the determination in step 402, if it is not a fault of its own station, it is requested to repair the fault to another station (breakdown) and waits for the result notification. If the local is requested to repair, it checks whether it is its own fault (406), and if it is its own fault, it sends the result to the local who requested the repair (407). If it is not the local station, request repair to another station (405).

Finally, when the fault is repaired and the result is entered, if the local that inputs the result is a local (408) if it is the first local to receive the fault (409), it ends if not. Here, a series of procedures for requesting repairs to other local sites or being notified of the results are carried out in real time.

The process is described in detail as follows.

First of all, in the process of inputting the data related to the failure first by recognizing a general failure (401), the failure facility inputs a cable, a cable transmission path, a transmission path, a system, a dedicated line, and the like. Enter. When the input is completed, a request number is generated, in the format of the relay station code-YYYYMMDD-NNNN, where NNNN is the serial number.

General failure is input at the operating station 103 and abnormal failure is input at the center 101. The received fault request number is listed in the operator terminal of the receiving station, enters the repair result, and once the history 203 is generated, disappears from the list and is stored in the database 208. Faults whose history has been generated can be retrieved later to retrieve the contents.

The troubleshooter 405 refers to testing a local facility and sending a troubleshooting request to another local if it is not a local failure.

Enter the test details, test notes, wanted local name, repair room, wanted sender, and contact information. Once the input result is saved, the wanted local terminal will generate an alarm, and the screen will show the broken details. If you request an arrangement, wait for the wanted site to enter the results.

Result input 404 is a process of inputting the repair history according to the failure, input the action history, the repairman, the repair station, and the repair time is automatically input. The history generation 409 can only be generated at the locality where the failure is received. If repair is requested from another locality, only the repair results are entered.

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

According to the present invention as described above, through the database of the fault reception, reporting, damage line accurate calculation and history management, there is an excellent effect that can efficiently handle the failure-related tasks.

Claims (5)

In the long distance network failure history management method in the long distance network failure history management system, A first step of establishing a transfer database in preparation for a change of a transmission path when a failure occurs and determining whether the transmission path is an abnormal failure; A second step of inputting a result after troubleshooting at the operating station where the failure occurred, and generating a history at the receiving station that first received the failure, as a result of the determination in the first step; A third step of performing a repair by searching for the transfer database and instructing a transfer if the abnormality is determined as a result of the first step; And The fourth step of checking the transmission path recovery time and inputting the recovery result according to the type of the damaged facility restored by the troubleshooting Intermittent transmission network failure history management method comprising a. The method of claim 1, The fault failure management method of the first stage means at least one of faults of a line (DS3-class) having more than 672 channels (DS3-class) or five or more DS1-class lines. The method of claim 1, The second step, A fifth step of judging whether the reception and the request for the failure are a domestic failure; A sixth step of generating a history in the receiving station that first received the failure by inputting a result after the troubleshooting, if the local station has failed as a result of the determination in the fifth step; And If the result of the determination in the fifth step is not a fault of the own country, request a repair of the fault to the corresponding operation station, and receive a notification of the result and generate a history in the receiving station that first received the fault. Intermittent transmission network failure history management method comprising a. The method according to any one of claims 1 to 3, The fourth step, An eighth step of determining the type of the damaged facility; A ninth step of determining whether the damaged facilities are restored at the same time by checking the recovery time of the corresponding DS1 transmission path when the damage facility is at least one of the switching device or the DCS; A tenth step of inputting a failure for at least one of the exchange or the DCS if the recovery time is the same, and inputting the failure in units of a DS1 transmission path if the recovery time is different; As a result of the determination in the eighth step, if the damage facility is at least one of a cable, a cable transmission path, a B-DCS, a DS3 transmission path, an optical end station, and an optical repeater, the recovery time of the corresponding DS3 transmission path is confirmed, and all are the same. An eleventh step of determining whether it is restored at a time; And As a result of the determination in the eleventh step, if the recovery time is the same, a twelfth step is input to the cable transmission path; Intermittent transmission network failure history management method comprising a. In order to manage the long-distance network failure history management system in the long-distance transmission network failure history management system, A first function of establishing a switching database in preparation for a change in a transmission path when a failure occurs and determining whether the transmission path is an abnormal failure; A second function of inputting a result after troubleshooting at the operating station where the failure occurred, and generating a history at the receiving station that first received the failure, as a result of the determination of the first function; A third function of searching for the transfer database and instructing a transfer if the abnormality is determined as a result of the determination of the first function and repairing the failure; And Fourth function of checking the transmission path recovery time according to the type of the damaged facility restored by the troubleshooting and inputting the recovery result to generate a history A computer-readable recording medium having recorded thereon a program for realizing this.