KR100861592B1 - Method and apparatus for managing fault in customer network management system - Google Patents

Abstract

The present invention relates to a failure management method and apparatus in a customer network management system (VPN) connected to a virtual private network (VPN). By receiving the fault information event, analyzing the message type, fault type and fault level of the fault information event, and storing the analysis result corresponding to the fault information event in the database as a history information, Through efficient fault management of subscriber network operation management, it is possible to improve service quality and customer reliability through rapid failure management and accurate analysis.

VPN, CNM, Virtual Private Network, Subscriber Network Management System

Description

Fault management method and device in subscriber network management system {METHOD AND APPARATUS FOR MANAGING FAULT IN CUSTOMER NETWORK MANAGEMENT SYSTEM}

1 is a diagram illustrating an interworking relationship between a subscriber network management system and a virtual private network (VPN) according to an embodiment of the present invention.

2 is a block diagram illustrating a failure management apparatus in a subscriber network management system according to an embodiment of the present invention.

3 is a flowchart illustrating a method of operating a subscriber network management system according to an embodiment of the present invention.

4 to 7 are flowcharts illustrating a failure management method in a subscriber network management system according to an embodiment of the present invention.

The present invention relates to a failure management method and apparatus in a customer network management system connected to a virtual private network (VPN).

In general, in the case of a corporate customer in a VPN, most of the corporate customers receive a failure report by telephone or e-mail to perform troubleshooting, thereby delaying network failure recovery time. Had serious operational problems.

In addition, the fault management system of the service provider that performs the fault handling work of most subscribers performs fault handling only with priority for the faults reported by the customer, thereby storing only the history of faults detected and detected in the network, The preventive functions that can occur are poorly managed. In addition, it was not integrated management (that is, integrated management of network detection automatic failure information and failure information reported by subscribers) for each system operating the network, and failed to provide reliable failure information to subscribers.

On the other hand, the CNM (Customer Network Management) service provides customers with more efficient management of their virtual networks by providing management information on the portion of the customer's network in the public network in terms of configuration, performance and failure. Service to support maintenance. International standards for management information for these CNMs include ATM, X.25 Data Network and Frame Relay, respectively, in the ATM Forum M3 specification, the ITU-T X.16x Recommendations and the FR Forum FRF.6 Recommendations, respectively. Relay) Recommended for the network. However, this standard does not provide practical implementation methods or management management methods for failure management.

It is an object of the present invention to provide a failure management method and apparatus in a subscriber network management system for efficiently performing failure management of a subscriber.

In order to solve this problem, the present invention can quickly and effectively analyze the failures reported by the customer, as well as automatic network detection failure in the system occurring in the subscriber network, thereby preventing the effect of the failure and subscriber network operation management. Perform efficient fault management.

According to an embodiment of the present invention, in performing a failure management in a subscriber network management system connected to a VPN, a failure information event is received and the failure information event is analyzed according to a message type, a failure type, and a failure level of the failure information event. And, it provides a failure management method that stores the result of analyzing the failure information event as history information in the database. Here, the process of analyzing the fault information event classifies the fault information event into the subscriber report fault event and the network detection fault event according to the message type, analyzes the subscriber report fault event, and analyzes the network detection fault event using the history information. do.

The failure management method further includes a step of storing the failure statistics for the failure information event in a database on a daily / weekly / monthly basis.

The process of analyzing the network detection failure event is to check whether the network detection failure event is a failure occurrence message according to the failure type, and if the failure information event is a failure occurrence message, the history information of the network detection failure event is Process the fault message. At this time, in the process of processing the failure occurrence message of the network detection failure event, check whether the failure level is a critical level, and if the failure level is a critical level, the failure information corresponding to the failure identifier of the network detection failure event is already recorded in the database. Check if the information exists, and if the fault information matching the fault identifier of the network detection fault event already exists in the database as the history information, check whether the fault level of the existing fault information is lower than the risk level and already exists. If the fault level of the fault information is low, change the fault level of the existing fault information into a risk level and store it in the database.

Alternatively, the process of analyzing the network detection failure event may determine whether the network detection failure event is a failure recovery message according to the failure type, and if the network detection failure event is a failure recovery message, the network detection failure event matches the failure identifier of the network detection failure event. Check if the fault information already exists in the database as the history information.If the fault information matching the fault identifier of the network detection fault event already exists as the history information in the database, it is determined whether the threshold has been exceeded before performing the fault recovery process. If the threshold is not exceeded, the number of fault accumulation counters is increased, and the fault information with the fault information management system is matched. If the fault information with the fault information management system is matched, the historical information on the network detection fault event is displayed. Save it to the database. At this time, the process of analyzing the network detection failure event, if the threshold value is exceeded, increase the number of failure accumulation counters, perform a violation determination for the failure delay, check whether the failure information with the failure information management system matches, If the failure information is consistent with the information management system, the history information of the network detection failure event is stored in the database. Here, the process of performing the violation determination is to determine whether the service contract level time contracted with the customer is exceeded.

Alternatively, the process of analyzing a subscriber report failure event may include checking whether a subscriber report failure event is a failure message according to the failure type, and if the subscriber notification failure event is a failure message, the final failure handling status and history may be stored in a database. Store and reflect failure statistics on subscriber report failure events in database by day / week / month.

According to another embodiment of the present invention, when performing fault management in a subscriber network management system connected to a VPN, a fault receiving module that receives fault information events and classifies and stores them according to a fault level, changes a fault monitoring period, or fails Fault policy module to change the class reference time, fault monitoring module to monitor for faults exceeding the reference time according to fault monitoring cycle, fault handling module to process fault information received from fault receiving module, and fault handling module It provides a failure management apparatus including a DB processing module for storing in the database about the status and history of the failure processing processed in. Here, the failure reception module may include a failure message receiving module for receiving network detection failure information generated at a VPN, or a subscriber notification failure information reported from a subscriber, a failure message queue for temporarily storing failure information received at the failure message receiving module, And a secondary failure message queue that classifies and stores the failure information stored in the failure message queue according to the failure level.

The failure management device further includes an external event transmission module that transmits an event for a test for each failure section and a request for job arrangement to the outside under the control of the failure processing module.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and like reference numerals designate like parts throughout the specification.

Throughout the specification, when a part is said to "include" a certain component, it means that it can further include other components, without excluding other components unless specifically stated otherwise.

A failure management method and apparatus in a subscriber network management system according to an embodiment of the present invention will now be described in detail with reference to the accompanying drawings.

1 is a diagram illustrating an interworking relationship between a subscriber network management system and a VPN according to an embodiment of the present invention.

As shown in FIG. 1, the subscriber network management system 100 according to the embodiment of the present invention interworks with the VPN management system 101, the failure information management system 102, and the performance management system 103. Interworking with the failure task management system 104 through the failure information management system 102.

The subscriber network management system 100 performs a role of inquiring about the configuration / performance / failure and traffic information of the subscriber's VPN section through the web interface, and allows the CNM customer (that is, the operator or subscriber) to The network information, that is, the VPN 105 that connects the main office and branch offices, enables integrated management and operation of the company's network.

The VPN management system 101 accommodates the VPN 105 and manages network failure information (ie, network failure reception, network failure recovery, etc.) of the VPN 105. At this time, the VPN management system 101 collects network detection failure information generated in the facility and transmits it to the subscriber network management system 100 as a predetermined event (for example, M1 event).

The failure information management system 102 manages failure information (ie, failure reception, failure completion, etc.) reported by the subscriber. At this time, the failure information management system 102 collects the reported failure information when a failure reception is reported from the CNM subscriber, and transmits the reported failure information to the subscriber network management system 100 as an event different from the network detection failure information (for example, S1 event). send. In addition, the failure information management system 102 receives the failure information from the subscriber network management system 100 for the broken line and transmits a work processing message to the broken work management system 104, and then displays the work processing result. Received from the failure operation management system 104 to notify the subscriber network management system 100.

The performance management system 103 stores traffic information of the subscriber router 106 and traffic information of the backbone router 107.

The breakdown work management system 104 manages the troubleshooter work for the subscriber facility and serves to notify the completion after the breakdown action. At this time, the failure operation management system 104 performs a job according to the job processing message received from the failure information management system 102 and transmits a job completion result to the failure information management system 102.

2 is a block diagram illustrating a failure management apparatus of the subscriber network management system 100 according to an exemplary embodiment of the present invention.

As shown in Figure 2, the failure management device of the subscriber network management system 100 according to an embodiment of the present invention receives and processes a failure information event, the failure reception module 210, failure policy module 220, The fault monitoring module 230, a fault handling module 240, and a DB (Database) processing module 250 are included. In addition, the failure management apparatus further includes an external event transmission module 260.

The failure reception module 210 receives a failure reception event received from the failure information management system 102, temporarily stores the received failure information, and classifies and stores the temporarily stored failure information according to a failure level. In addition, the failure reception module 210 includes a failure message receiving module 211, a failure message queue 212, and an auxiliary failure message queue 213. The fault message receiving module 211 receives a fault reception event received from the fault information management system 102, the fault message queue 212 temporarily stores fault information received by the fault message receiving module 211, The secondary failure message queue 213 classifies and stores the failure information temporarily stored in the failure message queue 212 according to the failure level.

The failure policy module 220 plays a role of changing a failure monitoring cycle of the CNM failure management module 200, changing a reference time (ie, a threshold) of a failure grade, and transmitting and receiving an event.

The fault monitoring module 230 may receive a fault reception module 210 (that is, a fault message) for a fault in violation of the reference time set by the fault policy module 220 according to the fault monitoring period set by the fault policy module 220. Periodically monitors the failure event information stored in the queue (212) and the secondary failure message queue (213).

The fault handling module 240 processes the fault information event received from the fault receiving module 210.

The DB processing module 250 stores failure information in the CNM database with respect to the failure processing state and history processed by the failure processing module 240.

The external event transmission module 260 transmits an event for a failure task to the outside under the control of the failure processing module 240. The external event transmission module 260 requests the failure information management system 102 to request a test and request an arrangement (or troubleshoot status inquiry) for each failure section when the failure threshold value violates the reference failure time.

The operation method of the subscriber network management system according to an embodiment of the present invention will be described with reference to the flowchart of FIG. 3.

The VPN management system 101 collects the network detection failure information of the subscriber occurring in the facility and transmits it to the subscriber network management system 100 as a predetermined event M1 (S301). In addition, in the failure information management system 102, when a failure reception is notified to the CNM subscriber, the failure information reported from the subscriber is collected and the subscriber network management system 100 as an event (S1) different from the network detection failure information. It is transmitted to (S302).

Accordingly, the CNM failure management module 200 of the subscriber network management system 100 receives the failure information events S1 and M1 through the failure reception module 210 (S303), and receives the received failure information events S1 and M1. After analyzing the message type, failure type, failure level, etc. (S304), the analysis result corresponding to the received failure information event (S1, M1) is stored in the database through the DB processing module 250 as history information. It becomes (S305).

In addition, the CNM fault management module 200 performs a periodic monitoring function through the fault monitoring module 230 to determine whether the fault threshold value violates the reference fault time (S306). If the failure time has been violated, the failure information management system 102 and the database are interlocked through the external event transmission module 260 to perform the section-by-section failure test for the subscriber facility (S307). At this time, the external event transmission module 260 transmits an event for the failure operation to the outside (that is, the failure information management system 102).

Accordingly, the failure information management system 102 receives the failure information from the external event transmission module 260 with respect to the broken line, generates a job processing message, and transmits the generated job processing message to the failure job management system 104.

Then, the failure operation management system 104 performs a failure test for each section of the subscriber facility according to the job processing message received from the failure information management system 102, and then displays the result of the processing of the performed operation. (S308).

Then, the failure information management system 102 receives the job processing result from the failure work management system 104 and notifies the subscriber network management system 100, and the subscriber network management system 100 receives the failure information management system ( Receiving the result of the work processing through 102) (S309) and stores the failure processing state and history for the failure test for each section (S310).

Hereinafter, a failure management method in a subscriber network management system according to an embodiment of the present invention will be described in detail with reference to the flowcharts of FIGS. 4 to 7.

4 to 7 are flowcharts of the failure management processing of the subscriber network management system applied in the embodiment of the present invention.

The failure information of the subscriber managed by the subscriber network management system 100 is a linkage system (i.e., VPN management system 101) between the network detection failure information generated from the actual facility information accommodating the subscriber network and the failure information reported by the subscriber. And failure information management system 102), respectively.

As illustrated in FIG. 4, the VPN management system 101 collects failure information that may occur in the VPN 105 and transmits the collected failure information to the network management failure event M1 to the subscriber network management system 100. In addition, the failure information management system 102 collects the failure information reported by the subscriber and transmits the collected failure information to the subscriber network management system 100 as a subscriber report failure event (S1).

Accordingly, the failure reception module 210 provided in the CNM failure management module 200 in the subscriber network management system 100 receives a message for the network detection failure event M1 from the VPN management system 101 and fails. Receive a message for the subscriber report failure event (S1) from the information management system 102. At this time, the failure message receiving module 211 of the failure reception module 210 is a message for the network detection failure event (M1) received from the VPN management system 101, and the subscriber report received from the failure information management system 102 Receiving a message for the failure event (S1) is temporarily stored through the failure message queue 212 of the failure reception module 210 (S401). In addition, the fault message receiving module 211 receives an event by the fault handling processor, and the fault information of the received events M1 and S1 includes fault time, fault content, fault identifier, fault section, fault. This includes the type, flag, customer grade, and emergency handling.

Then, the failure processing module 240 included in the CNM failure management module 200 analyzes the type of the fault message temporarily stored in the fault message queue 212, and the type of the fault message analyzed is a network detection fault event. Whether or not (M1) or subscriber report failure event (S1) (S402).

At this time, if the type of the failure message in the above-described step S402 network detection failure event (M1), the failure processing module 240 analyzes the failure type, the failure flag of the failure type analysis is True (True) or error ( False) is checked (S403). Here, if the failure flag of the failure type analysis is normal, a failure message temporarily stored in the failure message queue 212 means a failure occurrence message, and if it is an error, a failure message temporarily stored in the failure message queue 212 means a failure recovery message. .

Thus, when the failure flag of the failure type analysis is normal in the above-described step S403, that is, when the failure message is a failure message, the failure processing module 240 determines the failure level of the failure message temporarily stored in the failure message queue 212. By analyzing, it is checked whether the analyzed failure class is a type A or a type B or C (S404). Here, the failure level may be classified into a type A of a risk level and a type B or C of a lower level of the risk level, and the type A is the most critical level of failure that may occur in the VPN 105. In the case of type B, a major failure level is classified, and in the case of type C, a minor failure level is classified into a failure message temporarily stored in the failure message queue 212.

When the failure class analysis type is a type A (ie, a risk level) in the above-described step S404, the failure processing module 240 may identify the failure information (corresponding to the failure identifier of the failure message temporarily stored in the failure message queue 212). That is, it is checked whether a failure message) already exists in the database (S405).

Accordingly, if the failure information corresponding to the failure identifier already exists in step S405 described above, the failure processing module 240 checks whether the failure grade of the failure information already existing in the database is type B, C or type A. It is made (S406). At this time, if the failure level of the failure information already present in the database in step S406 is type B or type C, the failure level is changed to type A and stored in the database (S407).

On the other hand, if the failure information corresponding to the failure identifier does not exist in the above-described step S405, or the failure class of the failure information already existing in the database in the above-mentioned step S406 is type A, or after performing the above-described step S407 The failure processing module 240 checks whether a message for the subscriber notification failure event S1 already exists in the database at this time zone (ie, the current time zone) (S408).

Therefore, when the message for the subscriber report failure event (S1) already exists in the database in the above-described step S408, the failure processing module 240 is currently undergoing arrangement for a failure on this line or a failure test. Since it can be determined through the failure test status field of the database, the current state of the network detection failure event M1 (that is, the network detection failure occurrence message) is stored in the database (S409). Thereafter, the failure processing module 240 reflects the failure statistics on a daily / weekly / monthly basis for the message for the network detection failure event M1 (or subscriber report failure event S1) and stores them in the database. It becomes (S410).

If, in the above-described step S408, the embodiment of the present invention for the case where the message for the time zone subscriber notification failure event S1 for the type A does not exist in the database corresponds to the 'A' code shown in FIG. It will be described as follows with reference to the flow chart of FIG.

In this case, the fault monitoring module 230 performs a monitoring function under the control of the fault handling module 240 (S501), and determines whether a threshold value of type A violates the reference failure time in fault state monitoring. It is made (S502).

At this time, if the threshold value of type A has not yet violated the reference failure time, the process returns to step S501 described above to repeat the periodic monitoring function. On the other hand, if the type A threshold value violates the reference failure time, the failure processing module 240 uses the external event transmission module 260 included in the CNM failure management module 200 to manage the failure information management system 102. ) And the failure test for each section of the subscriber facility through the interworking between the database and the database (S503).

After the failure test, the code value is analyzed through the analysis of the failure test result (that is, the cause and phenomenon) (S504), and the failure work for each section of the subscriber facility of the current failure management system 104 of this line is performed. It is determined whether this is in progress (S505).

Thus, if a failure operation is in progress in the failure task management system 104 in step S505 described above, the operator is notified in real time of the failure handling state for the current failure task stage (S506), and the final failure treatment state and The history is stored in the database (S507). Thereafter, referring to the flowchart of FIG. 4 corresponding to the symbol 'B' shown in FIG. 5, the process returns to the above-described step S410 and the message of the network detection failure event M1 (or the subscriber report failure event S1). Failure statistics for each day / week / month will be stored and reflected.

However, if the fault work is not in progress in the fault work management system 104 in step S505 described above, the request message for arrangement of fault work through the external event transmission module 260 is sent to the fault information management system 102. After the transmission (S508), the process returns to the above-described step S507 to store the failure processing state and history in the database.

On the other hand, as a result of the failure grade analysis in step S404 described above, an embodiment of the present invention for the case where the failure grade analysis type is Type B or Type C, the flowchart of FIG. 6 corresponding to the 'C' code shown in FIG. This will be described as follows.

In this case, according to the flowchart as shown in FIG. 6, the fault message temporarily stored in the fault message queue 212 is transmitted to the secondary fault message queue 213 and stored (S601).

The failure state monitoring determines whether a failure has occurred above a threshold value for the application of the reference values for each type (types B and C) (S602). At this time, in the embodiment of the present invention, the threshold value may be set differently with respect to the reference violation time value for each failure level. In other words, it should be understood that an effective failure management process may be performed by assigning different threshold values of the failure criteria for serious and alarm failures.

Therefore, when a failure does not occur above the threshold in step S602 described above, referring to the flowchart of FIG. 4 corresponding to the 'D' code shown in FIG. 6, the flow returns to the above-described step S409 and does not exceed the threshold. Information on the history, that is, history information on the network detection failure event M1 (that is, network detection failure occurrence message) is stored in the database.

On the other hand, if a failure occurs above the threshold in step S602 described above, the operator is notified in real time of the violation of the reference value for each type (S603). In addition, since it is not a critical fault like Type A, the operator has to manually select whether to perform a failure test for each section through a real-time window or a failure test later, and then decide whether to perform a failure test for each section. Check whether the selection (S604).

Accordingly, in the case of performing the section-by-section failure test in step S604 described above, referring to the flowchart of FIG. 5 corresponding to the 'E' code shown in FIG. 6, the process returns to step S503 described above, and the failure information management system ( 102) and the failure test for each section of the subscriber facility through interworking with the database.

On the other hand, if the failure test for each section is not carried out in the above-described step S604, it is recognized that the failure continues to occur internally above the threshold, the failure information for the failure identifier is consistent with that of the failure information management system 102 It is checked whether or not (S605). This is because the failure information inconsistency between the subscriber network management system 100 and the failure information management system 102 due to the case where the failure has already been recovered but the failure of the failure completion message due to network failure and process abnormality or other conditions is not satisfied. May occur, you must ensure that the fault information is consistent. In other words, this is to prevent problems that may occur due to failure to provide accurate information on subscriber networks due to failure data mismatch between heterogeneous systems.

At this time, when the failure information between the subscriber network management system 100 and the failure information management system 102 in step S605 described above, referring to the flowchart of FIG. 4 corresponding to the 'D' code shown in FIG. Returning to step S409 described above, the history information for the network detection failure event M1 (that is, the network detection failure occurrence message) is stored in the database.

If the failure information between the subscriber network management system 100 and the failure information management system 102 does not match in step S605, the flag is set to 'F' in the database of the subscriber network management system 100 (that is, In order to set the inconsistency flag (S606), and to match the failure information through the database interworking, the failure information synchronization function between the subscriber network management system 100 and the failure information management system 102 is performed (S607).

Then, the details of the failure information synchronization is notified to the operator in real time (S608), and the log and cause analysis for the mismatch is performed (S609). Thus, referring to the flowchart of FIG. 4 corresponding to the 'D' code shown in FIG. 6, the process returns to step S409 described above, and records historical information on the network detection failure event M1 (that is, network detection failure occurrence message). Save it to the database.

On the other hand, as a result of the failure type analysis in step S403 described above, an embodiment of the present invention for the case where the failure flag of the failure type analysis is an error (that is, the failure message is a failure recovery message) is shown in Fig. 4. A description with reference to the flowchart of FIG. 7 corresponding to the 'F' code as follows.

In this case, according to the flowchart shown in FIG. 7, it is checked whether a failure message corresponding to the failure identifier analyzed by the failure processing module 240 already exists in the CNM database (S701).

At this time, when there is no failure message corresponding to the failure identifier analyzed in the above-described step S701, the failure management processing of the subscriber network management system applied in the above-described embodiment of the present invention is terminated. On the other hand, if a failure message corresponding to the failure identifier analyzed in the above-described step S701 already exists, it is determined whether the type-specific threshold has been exceeded before performing the failure recovery process (S702).

Therefore, when the threshold is not exceeded in the above-described step S702, the number of fault accumulation counters is increased (S703), and then referring to the flowchart of FIG. 6 corresponding to the 'G' sign shown in FIG. 7, the above-described step S605 Returning to, to confirm whether the failure information for the failure identifier matches that of the failure information management system 102.

On the other hand, if the threshold is exceeded in the above-described step S702, the number of fault accumulation counters is increased, the violation determination for the fault delay is performed (S704), and then the corresponding 'G' code shown in FIG. Referring to the flowchart, the flow returns to the above-described step S605 to check whether the failure information for the failure identifier matches that of the failure information management system 102. Here, the violation determination for the failure delay is the task of determining whether the service contract level time contracted with the customer is exceeded.

On the other hand, if the type of failure message in the step S402 described above is the subscriber report failure event (S1), as shown in Figure 4, the failure processing module 240 analyzes the failure type, the failure of the failure type analysis It is checked whether the flag is True or False (S411).

In this case, when the failure flag of the failure type analysis is normal in the above-described step S411 (that is, when the failure message is a failure occurrence message), referring to the flowchart of FIG. 5 corresponding to the 'H' sign shown in FIG. Returning to step S507, the failure processing state and failure history are stored in the database.

On the other hand, if the failure flag of the failure type analysis is an error in the above-described step S411 (that is, the failure message is a failure recovery message), the number of failure accumulation counters is increased, and the violation determination for the failure delay is performed. (S412), referring to the flow chart of Fig. 6 corresponding to the 'G' sign shown in Fig. 4, the process returns to the above-described step S605 to confirm whether the fault information for the fault identifier corresponds to that of the fault information management system 102. Do it. Then, after performing the operations from the above steps S606 to S609, the history information about the subscriber report failure event S1 (that is, the subscriber report failure occurrence message) is stored in the database as in the above-described step S409. Then, as shown in step S410 described above, the failure statistics regarding the message for the subscriber report failure event S1 (or the network detection failure event M1) are finally reflected on a daily / weekly / monthly basis and stored in the database. And exit.

In the embodiment of the present invention, the subscriber network management system 100, which is a higher network management system, receives failure information notified from the failure information management system 102 for all the failure information of the subscriber, and accepts the VPN 105. Receiving a network detection failure message from the VPN management system 101 to perform the integrated operation management of the failure information, such as the fault monitoring function through the threshold value according to the fault level, the effective fault management function of the operator, the synchronization processing function, etc. The method and system were described. In addition, the embodiment of the present invention has described a method of performing a monitoring function for automatic network detection failure that may occur in the subscriber network before the customer reports the failure to the service provider. Unlike the embodiment of the present invention, by applying the embodiment of the present invention, for the subscriber report failure information received by the subscriber network management system 100, the customer can directly query the status and history of the failure handling, in particular The network automatic detection failure can be prioritized according to the threshold value to manage the failure efficiently.

The components described in the embodiments of the present invention may include at least one digital signal processor (DSP), a processor, a controller, an application specific integrated circuit (ASIC), a programmable logic device such as a field programmable gate array (FPGA), and other electronic devices. Or it may be implemented in hardware consisting of a combination thereof. In addition, at least some of the functions or processing procedures described in the embodiments of the present invention may be implemented in software, and such software may be recorded in a recording medium. In addition, the components, functions, and processing procedures described in the embodiments of the present invention may be implemented in a combination of hardware and software.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concepts of the present invention defined in the following claims are also provided. It belongs to the scope of rights.

As described above, according to the embodiment of the present invention, as well as the automatic detection of network failures in the system generated in the subscriber network, as well as to quickly process and analyze the failures reported by the customer, it has a precautionary effect on the failures, and efficient failure management. Through this, it is possible to improve service quality and improve customer reliability through quick trouble shooting and accurate analysis.

Claims (17)

In the failure management method in a subscriber network management system connected to a VPN (Virtual Private Network), Receiving a fault information event, Analyzing the fault information event according to the message type, fault type and fault level of the fault information event, and Storing the result of analyzing the failure information event as history information in a database; Analyzing the failure information event, Classifying the failure information event into a subscriber report failure event and a network detection failure event according to the message type; Analyzing the subscriber report failure event, and Analyzing the network detection failure event using the history information Management method comprising a. The method of claim 1, And storing the failure statistics for the failure information event in the database on a daily / weekly / month basis. The method of claim 1, Analyzing the network detection failure event, Checking whether the network detection failure event is a failure occurrence message according to the failure type, and If the network detection failure event is the failure occurrence message, processing the failure occurrence message of the network detection failure event according to the failure level by using the history information; Management method comprising a. The method of claim 3, Processing the failure occurrence message of the network detection failure event, Checking whether the failure level is a dangerous level, If the failure level is the risk level, checking whether failure information corresponding to a failure identifier of the network detection failure event already exists as the history information in the database; If failure information corresponding to the failure identifier of the network detection failure event already exists in the database, checking whether the failure level of the existing failure information is lower than the risk level, and If the failure level of the already existing failure information is the low level, changing the failure level of the already existing failure information to the risk level and storing it in the database. Management method comprising a. The method of claim 3, Processing the failure occurrence message of the network detection failure event, Checking whether the failure level is a dangerous level, If the failure level is the risk level, checking whether a message for the subscriber notification failure event corresponding to a current time already exists in the database as the history information, and If a message for the subscriber notification failure event corresponding to the current time already exists in the database, storing history information on the failure occurrence message of the network detection failure event in the database; Management method comprising a. The method of claim 5, Processing the failure occurrence message of the network detection failure event, If there is no message for the subscriber report failure event corresponding to the current time in the database, determining whether the threshold of the risk level violates a reference failure time; If the threshold value violates the reference failure time, interfacing the failure information management system to perform a section failure test for the subscriber facility; Determining whether a breakdown operation for each section of a subscriber facility of a current line is in progress through analyzing the result of the failure test; and If the troubleshooting is in progress, notifying an operator of a failure handling status of the failure, and storing a final failure handling status and history in the database. Management method further comprising. The method of claim 6, Processing the failure occurrence message of the network detection failure event, If the fault operation is not in progress, the method further comprises the step of transmitting a request for action on the fault work arrangement to the fault information management system, and storing the fault processing status and history in the database. The method of claim 5, Processing the failure occurrence message of the network detection failure event, If the failure level is lower than the risk level, determining whether a failure has occurred above a threshold value, If a failure occurs above the threshold, notifying the operator of the violation, and then checking whether or not to choose whether to proceed with the failure test for each section, If the progress of the failure test for each section is selected, interfacing the failure information management system to perform a failure test for each section of the subscriber facility, Determining whether a breakdown operation for each section of a subscriber facility of a current line is in progress through analyzing the result of the failure test; and If the troubleshooting is in progress, notifying an operator of a failure handling status of the failure, and storing a final failure handling status and history in the database. Management method further comprising. The method of claim 8, Processing the failure occurrence message of the network detection failure event, If the failure test for each section is not performed, confirming whether the failure information with the failure information management system is identical, If the failure information with the failure information management system does not match, performing a failure information synchronization function with the failure information management system, and Notifying the details of the failure information synchronization to the operator, performing a log and cause analysis on the inconsistency, and storing history information on the network detection failure event in the database; Management method further comprising. The method of claim 3, Analyzing the network detection failure event, Checking whether the network detection failure event is a failure recovery message according to the failure type; If the network detection failure event is the failure recovery message, checking whether failure information corresponding to the failure identifier of the network detection failure event already exists as the history information in the database; If failure information corresponding to the failure identifier of the network detection failure event already exists in the database as the history information, determining whether the threshold is exceeded before performing the failure recovery process; If not exceeding the threshold, increasing the number of fault accumulation counters, and then checking whether the fault information with the fault information management system is consistent, and Storing the history information of the network detection failure event in the database if the failure information with the failure information management system matches. Management method further comprising. The method of claim 10, Analyzing the network detection failure event, If the threshold is exceeded, increasing the number of fault accumulation counters and performing a violation determination for the fault delay; Confirming whether the failure information with the failure information management system is identical; and Storing the history information of the network detection failure event in the database if the failure information with the failure information management system matches. Management method further comprising. The method of claim 11, The violation determination step is a management method for determining whether or not the service contract level time contracted with the customer. The method of claim 1, Analyzing the subscriber report failure event, Checking whether the subscriber report failure event is a failure occurrence message according to the failure type; If the subscriber report failure event is the failure occurrence message, storing a final failure handling status and history in the database; and Storing and reflecting failure statistics on the subscriber reporting failure event in the database on a daily / weekly / monthly basis Management method comprising a. The method of claim 13, Analyzing the subscriber report failure event, Checking whether the subscriber report failure event is a failure recovery message according to the failure type; If the subscriber report failure event is the failure recovery message, increasing the number of failure accumulation counters and performing a violation determination for the failure delay; Confirming whether the fault information matches with the fault information management system, and Storing the history information on the subscriber report failure event in the database when the failure information with the failure information management system matches. Management method further comprising. A failure management apparatus in a subscriber network management system connected to a VPN (Virtual Private Network), Fault receiving module that receives fault information event and classifies and stores it according to fault level, Failure policy module for changing the fault monitoring interval or changing the reference time of the fault grade, A fault monitoring module for monitoring a fault breached for more than the reference time according to the fault monitoring cycle; A fault handling module for processing fault information received by the fault receiving module, and DB processing module for storing in the database about the status and history of the failure processing processed by the failure processing module Management device comprising a. The method of claim 15, And an external event transmission module for transmitting an event for a test for each fault section and request for arranging work to the outside under the control of the fault handling module. The method of claim 15, The fault reception module, Failure message receiving module for receiving the network detection failure information generated in the VPN, or subscriber notification failure information reported from the subscriber, A fault message queue for temporarily storing fault information received from the fault message receiving module, and Secondary failure message queue which classifies and stores the failure information stored in the failure message queue according to the failure level. Management device comprising a.

Images