KR100518450B1 - Customer network management system and method for processing and synchronizing fault information of different network - Google Patents

Abstract

There is provided a subscriber network management system for processing and synchronizing fault information on the failure and recovery status of one or more heterogeneous networks. In the subscriber network management system according to the present invention, if it is determined that the failure information receiving module, the subscriber identification module, and the failure information indicating the failure state of the subscriber, the failure counter is incremented and the failure information is analyzed. And a server operation state conversion module and a failure information providing module for converting the server operation state of the subscriber according to the result. In addition, the server operation state conversion module, based on the analysis of the failure information, if it is determined that the failure state of the subscriber or the failure state is restored, the server operating state of the subscriber according to the determination result, respectively, the failure state or recovery state And save the modified server operating status in the synchronization database. Network failure information is effectively managed and synchronized by the subscriber network management system and method according to the present invention.

Description

Subscriber network management system and method for processing and synchronizing heterogeneous network fault information {customer network management system and method for processing and synchronizing fault information of different network}

The present invention relates to a data communication network, and more particularly, to a subscriber network management system for effectively processing and synchronizing fault information of one or more sub-networks.

As information and communication technology develops, communication service users are demanding faster and more diverse services, and accordingly, the speed of communication network development is further accelerated. In addition, it is possible to collectively manage users connected to different types of networks to provide a common service.

In order to reliably manage such services and provide high quality services to subscribers, it manages its own virtual network by managing the inquiry of management information and other additional functions for the portion of the customer's virtual network configuration in the high-speed information communication network. A customer network management system (CNMS) is proposed for effective management. In the customer network management system, subscribers can be notified in real time of major failure events that affect the use of CNM services or services.

In general, network management refers to a series of activities required to control, coordinate, and monitor communication resources. Such network failure management information should be reported or responded in an appropriate manner. In other words, a notification of a failure of a network resource is delivered to a certain manager system and must be processed in real time so that such a failure can be reported immediately. Therefore, fault diagnosis and error notification must have the capability of management for real time processing. In the network management, the failure management is generated dynamically and the processing of the administrator system receiving the dynamic information, and a large number of failure data can be generated at the same time requires a management function that can efficiently manage the failure information. Therefore, in order to promptly notify the administrator about the failure in the network and to accurately analyze the information on the failure, it is necessary to deal with the failure efficiently so that the network can be quickly recovered.

Modern information and communication network has an open structure and is managed based on various and complicated communication network management techniques and various operating systems. Customer Network Management Service provides customers with management information about the part of their network in the public network in terms of configuration, performance, and faults, allowing customers to maintain their virtual networks more efficiently. It is a service to support. International standards for customer network management techniques are recommended for ATM, X.25data network and Frame Relay network respectively in ATM-Forum M3 specification, ITU-T X.16x Recommendation and FR Forum FRF.6 Recommendation.

However, these standard documents do not provide practical implementation methods for providing a service or concrete methods for failure synchronization. Therefore, the problem management method of the network management system that accommodates the switch according to the prior art has a problem of controlling the flow of the fault data in real time due to the interaction of the network management system and the decision of the operator rather than the efficient processing of the fault data. In addition, it becomes difficult to integrate fault management between the upper network accommodating the network management system and the lower network accommodating the switch, thereby causing inconsistency in the failure information between the upper network and the lower network. Therefore, the operator collects the fault information in real time and thus cannot accurately handle the fault information of the customer network. Thus, there is a disadvantage that the reliability of the failure notification function is low.

Therefore, there is an urgent need for a technique for efficient synchronization and management of fault information between the upper network and the lower network.

An object of the present invention is to receive and efficiently manage the failure information of the lower network to provide failure information for the management of the customer network, subscriber network management technology for synchronizing the failure information of the lower network with the failure information of the upper network. To provide.

One aspect of the present invention for achieving the above object is a subscriber network management system for processing and synchronizing the failure information on the failure occurrence and recovery status of one or more underlying networks, subscriber network according to one aspect of the present invention The management system includes a failure information receiving module for receiving failure information of a lower network, a subscriber identification module for determining whether the received failure information indicates a failure occurring for a subscriber of the subscriber network management system, and the failure information includes: If it is determined to indicate a failure state, a server operation state conversion module for converting the server operation state of the subscriber according to the result of analyzing the failure information by increasing the failure counter, a database storage module for storing the failure information in the synchronization database, and failure information To provide users with It includes a beam supplying module. In addition, the server operation state conversion module, based on the analysis of the failure information, if it is determined that the failure state of the subscriber or the failure state is restored, the server operating state of the subscriber according to the determination result, respectively, the failure state or recovery state And save the modified server operating status in the synchronization database. In particular, the failure information used in the subscriber network management system according to the present invention includes a failure class indicating the type of failure, a failure identifier indicating a target of failure, a failure status indicator indicating failure and recovery status of the underlying network, and failure occurrence. It is characterized in that the structure including at least one or more of time, failure recovery time and additional information. In addition, the server operational state conversion module compares the failure state indicator included in the received failure information with the failure state indicator of the subscriber previously stored in the synchronization database, and the stored failure state indicator is the first state, and the received failure state indicator is If it is the second state, it is determined that a failure state has occurred, and if the previously stored failure state indicator is the second state and the received failure state indicator is the first state, it is determined that the failure state has been recovered, otherwise the failure state or recovery state is It is characterized by determining that is maintained.

Another aspect of the present invention for achieving the object as described above relates to a subscriber network management method for processing and synchronizing failure information on the failure occurrence and recovery status of one or more underlying networks, according to another aspect of the present invention In the subscriber network management method, a failure information receiving step for receiving failure information of a lower network, a subscriber identification step for determining whether the received failure information indicates a failure occurring for a subscriber of the subscriber network management service, If it is determined that the failure status of the subscriber is determined, the server operational status transition step for converting the server operational status of the subscriber according to the result of analyzing the failure information by increasing the failure counter, storing the failure information in the synchronization database, and failure information Information for providing fault information to users It includes. In particular, the server operation state conversion step is to analyze the failure information to determine whether the failure state of the subscriber or whether the failure state is recovered, and if it is determined that the failure state of the subscriber occurs, the server operation of the subscriber Modify the status to failure status, save the modified server operation status in the synchronization database, and if the subscriber's failure status is recovered, modify the server operation status to the recovery status and synchronize the modified server operation status. The method further includes modifying a failure state stored in the database. In addition, the subscriber network management method according to another aspect of the present invention, the fault information receiving time storing step of storing the time when the failure information is received from the lower network, the failure information of the subscriber if the failure information is not received for a predetermined time Identifying failure information checking step, receiving downlink failure information for receiving subscriber failure information stored in lower network, failure information confirmed by failure information checking module (hereinafter referred to as "upper failure information") and lower network failure information Analysis of the results of the failure information comparison step and the comparison step for comparing the failure information (hereinafter referred to as "lower failure information") received by the receiving module, if it is determined that the upper failure information and the lower failure information is not the same The method may further include a synchronization step of correcting the upper fault information using the information. Furthermore, in the synchronization step, a search step for searching for a failure occurrence time and a recovery time included in the lower failure information, and if the failure of the lower network is determined as a result of analyzing the lower failure information, the upper failure information using the failure recovery time If it is determined that a failure has occurred in the lower network as a result of analyzing the lower fault information, characterized in that it further comprises the step of modifying the upper fault information to correct the upper fault information by using the failure time.

Network failure information is effectively managed and synchronized by the subscriber network management system and method according to the present invention.

In order to fully understand the present invention, the operational advantages of the present invention, and the objects achieved by the practice of the present invention, reference should be made to the accompanying drawings which illustrate preferred embodiments of the present invention and the contents described in the accompanying drawings.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. For each figure, like reference numerals denote like elements.

1 is a diagram conceptually illustrating a subscriber network management system according to an aspect of the present invention.

Subscriber network management system applied in the present invention is the lower network 150, 170, ATM network management system 150, FR network management system 170, subscriber network management system 110, subscriber interface 120 and synchronization database 130.

In the embodiment shown in Fig. 1, the underlying network includes a network management system 150 for accommodating an Asynchronous Transfer Mode (ATM) exchange, which is a high-speed network service, and a network management system 170 for accommodating a Frame Relay (FR) exchange. do. That is, the network management system 110, which is a higher management system, and the lower network management systems 150, 170 including an exchange are shown. Subscriber network management system 110 is connected to the synchronization database 130 and the management information about the components of the initial network to which the subscriber is connected through the distributed object CORBA (Common Object Request Broker Architecture) interface and database interworking Manage in conjunction. The subscriber network management system 110 may inquire through the subscriber interface 120 a function related to the configuration, performance, failure information, change of some information, and the like for the network section of the subscriber.

The subscriber network management system 110 shown in FIG. 1 receives failure information from the lower network management systems 150 and 170, analyzes the received failure information, and types the failure state. That is, when a failure occurs in the lower network management system, when the generated failure is maintained, when the failure is recovered, and when the restored normal state is maintained, the failure state is divided and managed and stored in the synchronization database 130. Therefore, fault information can be managed efficiently. A detailed description of the failure information management and storage operation of the subscriber network management system 110 will be described later in detail in the relevant part of the present specification.

In addition, the subscriber network management system 110, if the failure information is not received from the lower network management system (150, 170) for a predetermined time or more, receives the failure information from the lower network management system (150, 170), By comparing the failure information with the failure information previously stored in the synchronization database 130, when the two failure information are different, the failure information may be synchronized by updating the failure information stored in the synchronization database 130. Detailed description of the failure information synchronization function of the subscriber network management system 110 will be described later in detail in the relevant part of the present specification. Therefore, duplicate description is omitted for the sake of brevity of the specification.

2 is a diagram illustrating an embodiment of a failure information structure used in a subscriber network management system according to an aspect of the present invention.

A description of the structure and class of the KOVA IDL 200 shown in FIG. 2 is as follows. The IDL 200 is preferably transmitted through a cobar interface between the heterogeneous network management system for interworking and the subscriber network management system, which is an upper system.

The failure information structure 200 includes a failure class (ObjectClass), a failure identifier (ObjectId), a failure state indicator (operatonalState), a failure occurrence time (eventTime), a failure recovery time, and additional information (auxinfo). The object class transferred from the ATM network, which is a high-speed network, to the subscriber network management system is Uni port, Fr port, Vp connection, Vc connection, etc. The object class type transferred from the FR network to the subscriber network management system is Fr port. And an Fr subport type. The failure identifier (ObjectId) is divided into a port identifier or a connection identifier and identifies a resource in which a failure occurs. The failure state indicator (operatonalState) indicates the operating state of the exchange of the network management system. That is, when the operation state of the exchange is changed, the subscriber network management system notifies the failure or recovery state information. In the embodiment as shown in Figure 2, in the network management system, if the operating state of the exchange is active means to deliver a recovery message, inactive means to deliver a failure message to the subscriber network management system.

3 is a block diagram illustrating an operation of the subscriber network management system 300 according to an aspect of the present invention. The subscriber network management system 300 shown in FIG. 3 includes the switches 352, 354, 372, and 374 constituting the lower network, the FR network management system 350, the ATM network management system 370, and the fault information receiving module. 310, subscriber identification module 360, server operation state conversion module 362, database storage module 364 and failure information providing module, failure information providing module alarm log storage module 344, client module 342 and graphical interface 340.

The failure management module 330 of the subscriber network management system 300 includes an ATM network management system 350 and an FR network management system that accommodate ATM switches 352 and 354 and FR switches 372 and 374 in high-speed network service. 370 receives port and connection failure information of the subscriber through the COVA interface 305. The failure management module 330, which receives the subscriber's failure information from the ATM network management system 350 and the FR network management system 370 through the COVA interface 305, performs a conversion procedure for delivering the failure information to the subscriber. The information is transmitted to the graphical interface 340 of the subscriber network management system 300 to display failure information. The failure information receiving module 310 receives failure information from a lower network management system such as the FR network management system 350 and the ATM network management system 370. The subscriber identification module 360 confirms whether a port or connection corresponding to the received failure information is disabled for the subscriber of the subscriber network management system.

If it is determined that the failure information indicates the failure state of the subscriber, the server operation state conversion module 362 increments the failure counter and converts the subscriber's server operation state according to the result of analyzing the failure information. That is, if it is determined that the failure state of the subscriber is generated or the failure state is restored, based on the result of analyzing the failure information, the server operation state conversion module 362 may determine the failure state of the server operation state of each subscriber according to the determination result. Alternatively, modify the recovery state and save the modified server operation state in the synchronization database. The method of determining whether or not a failure state occurs or is recovered by the server operating state conversion module 362 is as follows. That is, the server operation state conversion module 362 compares the failure state indicator (corresponding to operationState of FIG. 2) included in the received failure information and the failure state indicator of the subscriber previously stored in the synchronization database. As a result of the comparison, if the stored fault status indicator is 'enable' and the received fault status indicator is 'disable', it is determined that a fault condition has occurred, and the saved fault status indicator is inactive and received If the failure state indicator is active, it may be determined that the failure state has been recovered. In addition, it is determined that the recovery state is maintained when both the stored failure state indicator and the received failure state indicator are 'active', and when the stored failure state indicator and the received failure state indicator are both 'inactive', It is determined that the state is maintained.

If the server operating state conversion module 362 determines that a failure or recovery state is maintained, the server operating state conversion module 362 marks this matter in a database field and increments a failure counter. On the other hand, if it is determined that a failure state or a recovery state occurs, only the failure counter is incremented.

The failure information providing module further includes a threshold determination module (not shown) that determines whether the failure counter is greater than or equal to a predetermined value, and if the failure counter is determined to be greater than or equal to the predetermined value, the client module 342 to notify the operator of the failure information. Call

In addition, when it is determined that the subscriber is logged in, the failure information providing module provides failure information to the subscriber in real time. On the other hand, if the subscriber has not logged in, the failure information is stored in the database, and the subscriber is notified of the stored failure information when the subscriber later logs in.

The subscriber network management system according to the present invention as shown in FIG. 3 receives a recovery message from the lower network management systems 350 and 370 again after the failure information of the subscriber has already been restored or the failure information of the subscriber has already failed. In this case, an accurate fault management method is proposed considering the case where a failure message is received from the lower network management systems 350 and 370 again. Therefore, the present invention provides a method for efficiently managing / operating subscriber's failure information in real time by presenting a method for handling an abnormally provided failure message.

In addition, the failure management module 330 shown in FIG. 3 synchronizes failure information through the following operation. First, the failure management module 330 stores the time when the failure information is received from the lower network, and checks the failure information of the subscriber when the failure information is not received for a predetermined time. Thus, by receiving the subscriber failure information stored in the lower network (350, 370), the failure information previously stored in the database (hereinafter referred to as "upper failure information") and the failure information received from the lower network (hereinafter referred to as "lower failure information" Comparison). If the upper fault information and the lower fault information are the same, the two fault information are already synchronized. However, if the upper fault information and the lower fault information is not the same, a synchronization operation for correcting the upper fault information is performed using the lower fault information.

In addition, the failure management module 330 searches for a failure occurrence time and a failure recovery time included in the lower failure information, and if it is determined that the failure of the lower network is recovered as a result of analyzing the lower failure information, Correct fault information. Therefore, the failure recovery time is written in the upper failure information. On the other hand, if it is determined that a failure has occurred in the lower network as a result of analyzing the lower fault information, the upper fault information may be corrected using the fault occurrence time.

4 is a flowchart illustrating an embodiment of a subscriber network management method according to another aspect of the present invention.

First, when the network management method is started (S400), information on the failure of the subscriber is received from the lower network management system (S405). As described above, the lower network management system may include a network management system that accommodates an ATM switch or an FR switch, and a fault information of a subscriber is generated when a failure or recovery of a corresponding port or connection occurs. In this case, it is preferable that the failure information of the subscriber be received through the COVA interface, which is a distributed object for integrating various types of application programs in a heterogeneous distributed environment. Then, the received failure information is analyzed (S410), and a failure class is determined (S415).

The subscriber network management system classifies the failure information according to the received class information of the failure information (S415) and checks the subscriber identifier whether the failure information of the subscriber of the subscriber network management system through the port or the connection identifier (S420). The failure information received from the lower network management system is analyzed to determine whether the failure state information is enabled or disabled (S425). If the failure state is inactive, it is notified that the failure of the subscriber has occurred from the lower network management system to the upper subscriber network management system, and when the failure state is active, it is as described above. Then, the failure information received from the lower network management system is compared with the current subscriber's failure information recorded in the synchronization database of the upper subscriber network management system (S430). In this case, the failure state may be classified into four types.

Type 1 indicates that the current failure state information of the subscriber of the upper subscriber network management system is a failure state and the failure state information received from the network management system, which is the lower system, is inactive. If the failure status information is normal and the failure status information received from the sub network management system is the active recovery state, Type 3 receives from the sub network management system the current failure status of the subscriber of the subscriber network management system is the failure status. When the received failure state information is the active recovery state, and type 4 is applied when the current failure state information of the subscriber of the subscriber network management system is normal and the failure state information received from the lower network management system is the inactive failure state. do.

If it is determined that it is Type 1, this means that the current port or connection of the subscriber in the upper subscriber network management system is currently in a failure state and a failure message is transmitted from the lower network management system instead of a recovery message. Or, if it is determined that the type is 2, this means that the port or connection of the subscriber in the current upper subscriber network management system is now in a normal state, but a recovery state is transmitted from the lower network management system, not a failure state. If it is determined that the result is Type 1 or Type 2, these items are recorded in the database field of the subscriber network management system (S440). The reason for storing in the database field is for later synchronization of failure information of the subscriber network management system. In addition, the failure counter of the current failure information (port or connection) is incremented (S445).

When the type is 3 or 4, it corresponds to a general failure situation. That is, when a failure occurs and is recovered, or a failure occurs in a restored state. In this case, the counter of the failure information is incremented (S445).

If the number of failure counters for the subscriber's port or connection exceeds the threshold (S450), the operator is immediately notified (S455) to analyze the failure information and perform an action (S460). This allows the operator to monitor the failure information of the subscriber from time to time to efficiently manage the failure of the subscriber, as well as to perform accurate failure management functions. After increasing the failure counter, the operating state of the subscriber network management system for the port or connection of the subscriber is changed (S465). That is, in the case of a failure state, the port or connection operation state of the subscriber network management system is changed to inactive, and in the case of a restored state, the change is made to active and then the failure information of the subscriber is stored in a related database (S470). After storing the failure information in the database, check whether the subscriber or the operator is logged in to the web (S475) and if the login state is displayed in real time in the web window (S480). If not, the information is stored in the database (S485), and if a user or an operator logs in later, the failure information that is not notified is searched for and displayed.

As described above, the subscriber network management method according to the present invention provides a method for efficiently managing and operating a subscriber's failure information in real time by presenting a method of handling abnormal upcoming failure messages.

5 is a flowchart illustrating another embodiment of a subscriber network management method according to another aspect of the present invention. That is, the subscriber network management method illustrated in FIG. 5 illustrates a method of synchronizing failure information of the lower network management system with failure information of the upper network management system.

If the subscriber network management system does not receive the subscriber's failure message or recovery message from the data network (ATM, FR), the method for synchronizing the failure information is as follows. First, when the subscriber's failure information is not received from the lower network management system for a predetermined time, the operator checks the subscriber's failure information (501). As a result of checking the fault information, if the fault type stored in the subscriber network management system's database is type 1 or type 2, the operator can check the current fault status information from the network management system of the data network (ATM, FR), which is the sub-system providing the subscriber's service. Can be retrieved. Thus, the failure information stored in the subscriber's network management system database is compared with the failure information of the lower network management system (502). If the lower fault information is the same as the upper fault information, since the fault state of the network is in a synchronized state, the process ends (509). However, if the lower fault information and the upper fault information is not the same, in order to match the failure information of the subscriber network, the failure occurrence time and failure recovery time are searched for in the failure log table of the corresponding lower network management system (504). First, when the failure information of the upper subscriber network management system is in a failure state and the state of the lower network management system is restored and the service is available, the failure recovery time is read from the failure log table of the lower network management system. Updates the relevant database and reflects the status information. On the other hand, when the failure status information of the subscriber network management system is normal and the status of the lower network management system is failure, the failure time is read from the failure log table of the network management system and the database of the subscriber network management system is updated. Reflect the information. However, if there is no failure time and recovery time information in the failure log table of the lower network management system, after the correct analysis and judgment of the operator, the failure time and recovery time information is input for the system synchronization directly (507), or the correct subscriber through the history management. It maintains the fault information and stores logs and data in all relevant databases (508).

By the failure information synchronization method as illustrated in FIG. 5, the operator may synchronize failure information between the lower network management system and the upper subscriber network management system according to the current failure state of the subscriber.

6 is a diagram illustrating an embodiment of a failure information display screen provided by a subscriber network management system according to the present invention.

As shown in Fig. 6, subscriber identification information, port identifier, connection identifier, time, cause, message, and connection status between the web and the koba are provided. The subscriber or system operator can systematically manage the network by using the failure information as shown in FIG.

Although the present invention has been described with reference to the embodiments shown in the drawings, this is merely exemplary, and it will be understood by those skilled in the art that various modifications and equivalent other embodiments are possible.

Therefore, the true technical protection scope of the present invention will be defined by the technical spirit of the appended claims.

In the network where the failure occurred according to the present invention, when the recovery has already been received but the recovery message has not yet been received from the network management system, that is, when the subscriber network management system, which is the upper system, is still recognized as the failure, the relevant field is stored as a database for later failure. A network service was provided for the synchronization of information.

In addition, the present invention provides a real-time communication through the CORBA interface, an object-oriented open data exchange technology, for efficient integrated network management between the heterogeneous network management systems between the subscriber network management system and the network management system constituting the subscriber network. As a result, a synchronization method for maintaining fault information and maintaining consistent fault information between the subscriber network management system and the interworking system of the public data network was provided.

1 is a diagram conceptually illustrating a subscriber network management system according to an aspect of the present invention.

2 is a diagram illustrating an embodiment of a failure information structure used in a subscriber network management system according to an aspect of the present invention.

3 is a block diagram illustrating an operation of a subscriber network management system according to an aspect of the present invention.

4 is a flowchart illustrating an embodiment of a subscriber network management method according to another aspect of the present invention.

5 is a flowchart illustrating another embodiment of a subscriber network management method according to another aspect of the present invention.

6 is a diagram illustrating an embodiment of a failure information display screen provided by a subscriber network management system according to the present invention.

Claims (14)

In the subscriber network management system for processing and synchronizing failure information on the failure and recovery status of one or more sub-networks, A fault information receiving module for receiving fault information of the lower network; A subscriber identification module for determining whether the received failure information indicates a failure occurring for a subscriber of the subscriber network management system; If it is determined that the failure information indicates a failure state of the subscriber, a server operation state conversion module for increasing a failure counter and converting a server operation state of the subscriber according to a result of analyzing the failure information; A database storage module for storing the failure information in a synchronization database; And A failure information providing module for providing the failure information to the user, The server operating state conversion module is configured to fail the server operating state of the subscriber according to a determination result when it is determined that a fault state of the subscriber is generated or the fault state is restored based on a result of analyzing the fault information. Subscriber network management system, characterized in that to modify the state or recovery state, and to store the modified server operating state in the synchronization database. The method of claim 1, wherein the failure information, At least one of a failure class indicating a type of failure, a failure identifier indicating a target of failure, a failure status indicator indicating a failure and recovery status of the underlying network, a failure occurrence time, a failure recovery time, and incidental information Subscriber network management system, characterized in that the structure (structure). The server operating state conversion module of claim 2, Comparing the failure status indicator included in the received failure information with the failure status indicator of the subscriber previously stored in the synchronization database, If the previously stored fault state indicator is the first state and the received fault state indicator is the second state, it is determined that a fault state has occurred. If the previously stored fault state indicator is the second state and the received fault state indicator is the first state, it is determined that the fault state is recovered. In other cases, the subscriber network management system, characterized in that it is determined that the failure state or recovery state is maintained. The fault information providing module of claim 3, A threshold determination module that determines whether the failure counter is greater than or equal to a predetermined value; A client module for notifying an operator of the failure information when the failure counter is determined to be greater than or equal to a predetermined value; And Further comprising an alarm log storage module for determining whether the subscriber is logged in, The client module notifies the failure information in real time when the subscriber is logged in, and stores the failure information when the subscriber is not logged in, and notifies the subscriber when the subscriber logs in. Management system. According to claim 3, The subscriber network management system, A fault information receiving time storage module storing a time at which the fault information is received from the lower network; A failure information checking module for checking failure information of the subscriber when the failure information is not received for a predetermined time; A lower network failure information receiving module for receiving subscriber failure information stored in the lower network; Comparison for comparing the failure information (hereinafter referred to as "upper failure information") confirmed by the failure information confirming module and the failure information (hereinafter referred to as "lower failure information") received by the lower network failure information receiving module. module; And And a synchronization module for modifying the upper fault information by using the lower fault information if it is determined that the upper fault information and the lower fault information are not the same. The method of claim 5, wherein the synchronization module, Search for the fault occurrence time and the fault recovery time included in the lower fault information; If it is determined that the failure of the lower network is recovered as a result of analyzing the lower failure information, the upper failure information is corrected by using the failure recovery time, And analyzing the lower fault information, if it is determined that the lower fault occurs, the upper fault information is corrected using the fault occurrence time. The method of claim 1, The lower network includes an ATM network including an ATM exchanger and an FR data network including a frame relay (FR) exchange. The failure information is transmitted and received in real time through a common object request broker architecture (CORBA) interface. Claims [1] A subscriber network management method for processing and synchronizing failure information on failure and recovery states of at least one lower network, Fault information receiving step for receiving fault information of the lower network; A subscriber verification step of determining whether the received failure information indicates a failure occurring for the subscriber of the subscriber network management service; If it is determined that the failure information indicates a failure state of the subscriber, a server operation state conversion step of increasing a failure counter and converting a server operation state of the subscriber according to a result of analyzing the failure information; Storing the failure information in a synchronization database; And A failure information providing step of providing the failure information to the user, wherein the server operation state conversion step includes: A failure state determination step of determining whether a failure state of the subscriber is generated or the failure state is recovered by analyzing the failure information; If it is determined that a failure state of the subscriber is generated, the server operation state of the subscriber is corrected to a failure state, and the modified server operation state is stored in the synchronization database, If it is determined that the failure state of the subscriber is restored, the subscriber further comprises a failure state modification step of modifying the server operating state of the subscriber to the recovery state, and storing the modified server operating state in the synchronization database. How to manage your network. The method of claim 8, wherein the failure information, At least one of a failure class indicating a type of failure, a failure identifier indicating a target of failure, a failure status indicator indicating a failure and recovery status of the underlying network, a failure occurrence time, a failure recovery time, and incidental information Subscriber network management method characterized in that the structure (structure). The method of claim 9, wherein the determining of the fault condition comprises: A failure status indicator comparing step of comparing the failure status indicator included in the received failure information with a failure status indicator of the subscriber previously stored in the synchronization database; A failure occurrence determining step of determining that a failure state has occurred when the previously stored failure state indicator is a first state and the received failure state indicator is a second state; A failure recovery determining step of determining that a failure state has been restored when the previously stored failure state indicator is a second state and the received failure state indicator is a first state; And In other cases, the subscriber network management method comprising a failure state maintenance step of determining that the failure state or recovery state is maintained. The method of claim 10, wherein the providing of the failure information comprises: A threshold determination step of determining whether the failure counter is greater than or equal to a predetermined value; A client notification step of notifying an operator of the failure information when the failure counter is determined to be equal to or greater than a predetermined value; An alarm log determination step of determining whether the subscriber is logged in; And And if the subscriber is logged in, notifying the subscriber of the failure information in real time, and if the subscriber is not logged in, storing the failure information in the synchronization database. The method of claim 10, wherein the subscriber network management method comprises: A fault information receiving time storing step of storing the time at which the fault information is received from the lower network; A failure information checking step of checking failure information of the subscriber when the failure information is not received for a predetermined time; Receiving lower network failure information for receiving subscriber failure information stored in the lower network; Disability to compare the failure information (hereinafter referred to as "upper fault information") confirmed by the fault information check module and the failure information received by the lower network fault information receiving module (hereinafter referred to as "lower fault information") Information comparing step; And And analyzing the result of the comparing step and, if it is determined that the upper fault information and the lower fault information are not the same, a synchronization step of correcting the upper fault information by using the lower fault information. How to manage. The method of claim 12, wherein the synchronizing step, A search step of searching for the fault occurrence time and the fault recovery time included in the lower fault information; If it is determined that the failure of the lower network is recovered as a result of analyzing the lower failure information, the upper failure information is corrected by using the failure recovery time, And analyzing the lower fault information, if it is determined that a fault has occurred in the lower network, further comprising modifying the upper fault information by using the fault occurrence time. The method of claim 8, The lower network includes an ATM network including an ATM exchanger and an FR data network including a frame relay (FR) exchange. The failure information is transmitted and received in real time through a common object request broker architecture (CORBA) interface.