KR100840085B1 - Device for managing fault of customer network management service in multi-domain data networks and method thereof - Google Patents

Abstract

The present invention relates to an integrated failure processing apparatus and method for a customer network management service in a high-speed information communication network that notifies a user of a failure of a customer network management service, and allows an operator to manage failure details for each management layer. Fault information storage means for storing fault handling details of a user's network; Network management system failure processing means for receiving a notification of a failure by communication using a CORBA (Common Object Request Broker) from each network management system; SNMP function means for processing the SNMP trap and the role of the SNMP manager using the Simple Network Management Protocol (SNMP) for each element management system; A failure filtering function means for receiving a failure from the network management system failure processing means and the SNMP function means and filtering the failure of the same network resource to control the congestion of the failure; Fault information function means for managing an SNMP item of the SNMP function means and managing a driving and processing cycle of fault filtering; It is characterized in that the integrated fault management in the high-speed information communication network is provided with a notification processing means for actually notifying the details of the failure by distinguishing the operator and the user and storing the notification result in the failure information storage means.

Description

Device for managing fault of customer network management service in high-speed information communication network and its method {device for managing fault of customer network management service in multi-domain data networks and method

1 is a configuration diagram of a system for providing a customer network management service in a high-speed information communication network.

2 is a block diagram of a customer network management system for integrated failure processing according to the present invention.

3 is a configuration diagram of a failure information processing unit of FIG. 2;

4 illustrates an SNMP management table in accordance with the present invention.

5 is a block diagram of the failure filtering function module of FIG. 3.

6 is a diagram illustrating the temporary failure processing table of FIG. 5;

7 is a flow chart of integrated failure processing in accordance with the present invention.

The present invention relates to an integrated failure handling apparatus and method of a customer network management service in a high-speed information communication network, and more particularly, to a user of a customer network management service in an information communication network to notify a user of a failure state of a use network, and to an operator. The present invention relates to an integrated failure handling apparatus and method for a customer network management service in a high-speed information communication network for managing a failure history for each management layer.

The Customer Network Management Service provides the management information on the part of the subscriber network in the public network in terms of configuration, performance, and failure so that customers can maintain their own virtual networks more efficiently. It is a supporting service that provides customers with the ability to monitor and control the use of their services to manage their own private network and the services provided.

Asynchronous Transfer Mode (ATM)-A general reference model of the Forum M3 specification, the architecture for service provision of the International Telecommunications Union-Telecommunication Standardization Sector (ITU-T) X.160 standard document, and the customer network of the ITU-T X.161 standard document. Like management services, ATM-forum and ITU-T standard documents define customer network management.

However, these standard documents do not describe actual implementation methods for providing services.

As shown in FIG. 1, the customer network management system 6 for providing a customer network management service is provided at the top of the network management system 16 that controls network resources 18 to manage portions corresponding to network elements. It occupies a part of the service management system 9, such as the billing management system 8 located.                         

The customer network management system 6 must exchange information with the underlying network management system 16 in order to monitor and control management information. Among these information, failure information is included.

However, since the failure information of the network management system 16 for each layer based on the network management function is not used in the customer network management system 6 as it is, the information not managed by the lower network management system 16 and For network resources 18 that must be managed intensively at the discretion of the operator 4, there must be its own information collection function within the customer network management system 6 to accommodate various requests from the users 2 who use the service. can do.

In addition, in a multi-layer data network such as a high-speed information communication network, existing network management technologies define and use different management information models and communicate using different management protocols. Therefore, compatibility problems and various management tools must be used interchangeably. However, there is a problem of scalability due to having a centralized structure.

In order to solve the above problems, an object of the present invention is to integrate and handle the obstacles for items belonging to each management layer.

Another object of the present invention is to enable the operator to isolate the failure from other network resources and take recovery measures by identifying the location and cause of the failure after the failure occurs.

Still another object of the present invention is to allow a user of a customer network management service to check in real time whether a network operator's network resource is being used and whether the corresponding failure is accurately reflected in the billing details of the service. have.

To this end, the present invention comprises a fault information storage means for storing a fault handling history of the user's network; Network management system failure processing means for receiving a notification of a failure by communication using a common object request broker (COBA) from each network management system; SNMP function means for processing the SNMP trap and the role of the SNMP manager using the Simple Network Management Protocol (SNMP) for each element management system; A failure filtering function means for receiving a failure from the network management system failure processing means and the SNMP function means and filtering the failure of the same network resource to control the congestion of the failure; Fault information function means for managing an SNMP item of the SNMP function means and managing a driving and processing cycle of fault filtering; The user of the customer network management service checks whether there is a failure of the network resource by providing a notification processing means for actually notifying the details of the failure by distinguishing the operator and the user and storing the notification result in the failure information storage means. Identify the location and cause of the failure so that recovery measures can be taken.

The customer network management system 100 according to the present invention includes a management information database 120 that stores various management information about a portion of the user's network occupying the public network, as shown in FIG. At 110, the failure information is notified from the ATM network management system 24, the frame relay network management system 26, and the IP (Internet Protocol) network management system 28, or element management using its own SNMP manager. The failure information is directly received from the system 30 to handle the failure, and the failure information is transmitted to the user 20, the operator 21, and the billing management system 22.

In addition, the performance information processing unit 140 serving as a general network management function is in charge of collecting and processing performance data on resources allocated for each user 20, and the configuration information processing unit 150 is configured as a user 20. ) Manages the configuration status of the port and connection determined at the time of joining the customer network management service, and is in charge of interworking with CORBA with the lower management system to configure the permanent virtual connection desired by the user 20 or change the settings.

In addition, since the customer network management system 100 is also a service management system, there is a user information processing unit 170 that manages information on the customer network user 20 and is in charge of access status and statistics, and for the operator 21. The statistics function processing unit 130 and other server management and subscribers that generate statistical data of service failures, resource failures, configurations, and performance related to each service 20 connected to each other, and process report data. An additional function processing unit 160 in charge of additional functions provided for convenience is provided.

In more detail, the failure information processing unit 110 according to the present invention receives a notification of a failure about a network resource used by the customer network user 20 through communication using the network management system 24 to 28 with CORBA. For the management items of network resources which are processed into fault data for providing customer network service and are not provided by the network management systems 24 to 28 or must be centrally managed from the operator 21's perspective, the SNMP manager directly uses the SNMP manager. The user 20 and the operator 21 are notified of exceeding a set value of a management item set for a specific management item, analyzing the correlation between various types of failures, and filtering function. Functions include additional functions and automatic report generation.

3 illustrates an internal function module of the failure information processing unit 110 of the customer network management system 100.

The failure information processing unit 110 is a network management system failure processing module 210 that receives notification of a failure from each network management system 24 to 28, an SNMP manager role and an SNMP function module 220 that processes an SNMP trap. By receiving the fault from the network management system fault handling module 210 and the SNMP function module 220, the fault filtering function module 230 for filtering the fault on the same network resource and controlling the congestion of the fault is provided. A failure information function module 240 that manages, manages the operation and processing cycles of failure filtering, and notifies the details of the failures by actually distinguishing between the operator and the user, and notifying the processing of storing the facts in the management information database 120. Module 250.

The network management system failure processing module 210 receives a failure notification from each network management system 24 to 28 that manages a corresponding network by using the information of the element management system 30. It is responsible for the function of passing on.

That is, it primarily plays a role of primarily identifying the faults reported by each network management system 24 to 28.

As an example, a failure on a port is accompanied by a failure on all persistent virtual connections belonging to the port.

At this time, if a port failure occurs, the network management system failure processing module 210 is notified of all the failures of the permanent virtual connection to the corresponding port, and eventually receives the same contents of the failure several times.

Thus, the network management system failure processing module 210 finds the virtual connection information on the corresponding port by using internal information of the customer network management system 100, and the failure of the permanent virtual connection is integrated with the failure on the corresponding port. And the failure event for the virtual connection received from each network management system 24 to 28 is discarded.

In addition, if the network resource managed by the customer network management system 100 is not among the details of the failure notified by each network management system 24 to 28, the failure event is discarded here.

In addition, the SNMP function module 220 serves two functions.

First, the time that is periodically set a value corresponding to the corresponding SNMP OID (Object Identification (Object ID)) from the element management system 30 for the role of the SNMP manager, that is, the resources and the period set in the fault information function module 240 While searching.

SNMP manager plays a role of processing device information by periodically importing management information through SNMP through remote communication with device configuration, failure, and performance information through polling method.

The SNMP agent reads the SNMP management information value periodically and has it on the memory. The SNMP agent mainly exists in the memory of the element management system 30 that exists inside or controls the device.

Information required at this time is a resource ID, an SNMP OID, an IP address, a community, a cycle, a start time, and an end time as shown in FIG.

Secondly, the SNMP trap is directly notified from the device, delivered to the operator 21, and stored in the management information database 120 to provide data for generating a report on the failure.

The method of obtaining the management information is not only the above-mentioned polling method, but also has a function of allowing the generated contents to be delivered to a specific host for a specific kind of failure in the device called a trap.

The setting of such a trap is limited only to the operator 21 which plays an administrator role.

Such a function occurs frequently in network operation, and when the same or similar failure occurs repeatedly in a specific device, it is impossible to implement the function by preparing all the cases in advance due to functional constraints in the network management system 24 to 28. .

However, this is a very important factor in network operation, and therefore, a tool is needed to analyze information related to the operation and failure of the device and performance and stability related to the failure.                     

This function is in charge of the SNMP function module 220.

The failure filtering function module 230 handles failures raised from the network management system failure processing module 210 and the SNMP function module 220, and stores the failure data in the management information database 120 and sends the notification data to the notification processing module 250. It is a functional module that transmits failure information to the operator 21 and the user 20 by notifying the failure details, and is driven by the failure information function module 240.

The failure filtering function module 230 may filter excessive failure information on the same network resource and transmit the filtered failure information to the operator 21 and the user 20.

If a network is initially installed or a large number of facilities are installed at once, a large number of failures occur at the same time, causing a large load on the network management and higher service management systems.

In this case, it is a problem to notify the user 20 of the customer network management service as it occurs and to reflect the charging information as the billing information in the billing management system 22. Therefore, it should be converted into useful information.

To this end, the fault filtering function module 230 stores the fault information transmitted from the classifier 320 and the classifier 320 which selects and stores the fault information of the buffer 310, the fault information of the buffer as shown in FIG. 5. A table processor 340 manages the temporary failure processing table 330 and the temporary failure processing table 330 and transmits the temporary failure processing table 330 to the notification processing module according to the type of failure of the temporary failure processing table 330.

First, the buffer 310 receives failure information from the network management system failure processing module 210 and the SNMP function module 220 which are lower systems.

Next, the classifier 320 that processes this pulls out the failure events one by one from the buffer 310 and checks in the temporary failure processing table 330 whether a failure notification for the same resource has been received within a period, and then fails the corresponding resource. If the item does not exist, the item is added to the list of the temporary failure processing table 330.

Related details are resource ID, failure type, failure reason, start time, end time, processing history, and count.

If a failure exists for the corresponding resource, the count value in the temporary failure processing table 330 is increased by one, and if the failure type and failure reason are different from the previous values, the count value is added and stored.

The apparatus for managing the temporary failure processing table 330 is a table processor 340, and the table processor 340 sends the failure details as shown in FIG. 6 to the notification processing module 250 according to the type of failure. To pass.

The table processor 340 uses the system timer to periodically check the port and permanent virtual items for which the failure start time in the temporary failure processing table 330 does not fall within the table processing cycle defined in the failure information function module 240 from now. Each connection is stored in the failure log table 350 that exists, and the corresponding item is deleted from the temporary failure processing table 330.

The failure log table 350 is a table in charge of failure processing in the management information database 120.                     

In this case, when the details are recovery of the failure, only the failure end time and the processing details are recorded in the corresponding item of the failure log table 350.

Then, the failure details are transmitted to the notification processing module 250 to notify the user 20 and the operator 21 of the failure details.

The fault information function module 240 is provided to control and manage the SNMP function module 220 and the fault filtering function module 230 as described above.

The failure information function module 240 first stores and manages the details to be processed by the SNMP function module 220 for the management items registered for each user 20 allowed by the end operator 21.

Second, it manages the processing cycle required to handle the same number of failures used in the failure filtering function module 230.

Third, it is responsible for driving the functional operation of the fault filtering function module 230.

The failure filtering function module 230 does not operate at all times, and if a failure occurs more than any number of failures by the count defined by the operator 21 in the failure information function module 240, the failure filtering function is regarded as a kind of failure congestion. .

The termination of the filtering function is that the failure information function module 240 transmits the release of the filtering function to the failure filtering function module 230 when the number of cases coming up within a predetermined period falls within a range preset by the operator.

At this time, if the set period is too long, the congestion is over but the notification of the disability is delayed because it waits in the disability filtering function module and is notified. If it is too short, the filtering function is terminated even if the congestion continues. Will repeat the operation again, resulting in poor performance of the filtering function.

The minimum value of the processing period is a period for managing the temporary failure processing table 330 in the table processor 340 of the failure filtering function module 230.

In addition, the notification processing module 230 that receives the failure details from the failure filtering function module 230 classifies the details of the received failure into three types according to the type of failure, and reports the result of the management. ) In the fault log table 350.

The first is a method for notifying the operator 21 and the user 20, the second is a method for notifying the user 20 only that the operator 21 is notified and confirmed, and the third is a method for notifying the user 20.

First, notifying the operator 21 and the user 20 of the failure at the same time is that the matter of the disability is urgent so that the operator 21 and the user 20 can immediately check the situation of the failure to take action. This informs the billing management system 22 of the failure.

In the second case, the operator 21 is notified of the failure, and only the number of confirmed cases of the operator 21 is transferred to the user 20 and the billing management system 22.

This includes notification of SNMP traps.

Third, the user 20 registers a user-specific check item in the failure information function module 240 and collects the failure details directly from the SNMP function module 220 and receives a notification, which is the billing management system 22. The failure details are not reported.

Of course, with respect to the items that can be registered, it is possible only with respect to the contents designated by the final operator 21.

At this time, there are three methods used as a means of notification: synchronous notification, asynchronous notification, and E-mail notification.

Synchronous notification means that a CORBA function is called by a dedicated client or CORBA enabled Java applet that enables CORBA communication. Asynchronous notification means polling the server to read the results.

When the fault information processing unit 110 configured as described above summarizes the processing flow of the fault information generated in the lower network management systems 24 to 28 as follows.

Determine whether the failure notification reported by each network management system (24 to 28) corresponds to the resource for the customer network management service (S801), if it does not correspond to the resource for the customer network management service (S802), and the customer network management If it corresponds to a resource for the service, it is checked whether the failure filtering function module 230 is driven (S803).

If the failure filtering function module 230 is not driven, the operator 21 and the user 20 are notified according to the type of notification, and the corresponding failure details are stored in the management information database 120 (S804).

If the failure filtering function is driven, it is checked whether the corresponding failure exists in the list of the temporary failure processing table 330 (S805).

If the corresponding item exists, the count is increased by 1 for the corresponding item in the temporary failure processing table 330, and the failure details are added (S806).

If the item does not exist, a failure item is added to the temporary failure processing table 330 (S807).

The table processor 340 checks whether filtering is completed in the list of the temporary failure processing table 330 by using a system timer (S808).

The filtered items are stored in the fault log table 350 for each port and virtual connection, deleted from the temporary fault handling table 330, and the fault details are delivered to the notification processing module 250 to the operator and the user according to the notification type. By notifying (S809), the series of processing flows for one failure is terminated.

As described above, the present invention has an effect of stably providing a customer network management service and guaranteeing smooth network management to an operator by integrating and managing obstacles to operating facilities and multi-layer management items.

In addition, the user of the customer network management service has the effect of confirming in real time the failure of the network resources of the network operator that he is using and the management details of the corresponding failure.

Claims (10)

Fault information storage means for storing fault handling details of a user's network; Network management system failure processing means for receiving a notification of a failure by communication using a common object request broker (COBA) from each network management system; SNMP function means for processing the SNMP trap and the role of the SNMP manager using the Simple Network Management Protocol (SNMP) for each element management system; A failure filtering function means for receiving a failure from the network management system failure processing means and the SNMP function means and filtering the failure of the same network resource to control the congestion of the failure; Fault information function means for managing an SNMP item of the SNMP function means and managing a driving and processing cycle of fault filtering; An integrated fault handling apparatus for a customer network management service in a high-speed information communication network including a notification processing means for actually notifying a breakdown of a failure by distinguishing an operator from a user and storing a notification result in the failure information storage means. The method of claim 1, The network management system failure processing means, If a port fails, the fault on the permanent virtual connection of the port can be integrated and handled along with the fault on the port, and the fault notification on the unmanaged network is deleted by the customer network management service. Integrated fault handling device of customer network management service in high-speed information network. The method of claim 1, The SNMP function means, The value corresponding to the corresponding SNMP OID (Object Identification) is searched by the polling method for the item and the period set by the fault information function means, and the SNMP trap is notified directly from the network and delivered to the operator. The information is a resource ID, SNMP OID, IP address, community, cycle, start time, end time integrated failure management apparatus of the customer network management service in the high-speed information network. The method of claim 1, The fault filtering function means, Temporary storage unit for receiving the fault information for a while; A classification processing unit for selecting and processing failure information of the temporary storage unit; A temporary failure processing table for storing failure information transmitted from the classification processing unit; Integrated failure of the customer network management service in the high-speed information communication network, characterized in that it comprises a table processor for managing the temporary failure processing table, and forwarded to the failure information storage means and notification processing means according to the type of failure of the temporary failure processing table. Processing unit. The method of claim 4, wherein The classification processing unit, By taking out the failure events one by one from the temporary storage unit and checking in the temporary failure processing table whether a failure notification for the same resource has been received within the period defined by the failure information function means, there is no failure item for the corresponding resource. If not, add the corresponding item to the list of the temporary failure processing table, and if there is a failure for the corresponding resource, increase the count value in the temporary failure processing table and add and store if the failure type and failure reason are different from the previous values. The necessary details are resource ID, type of failure, reason for failure, start time, end time, processing history, count. The method of claim 4, wherein The table processor, By using a system timer to periodically store in the fault information storage means an item in which the fault start time does not fall within the processing period defined by the fault information function means from the present time in each of the fault information storage means. The corresponding item is deleted from the temporary failure processing table. In this case, when the failure is recovery of the failure, only the failure end time and the processing history are recorded in the corresponding item of the management information storage means. Integrated failure handling unit for services. If the failure notification reported by each network management system corresponds to the resource for the customer network management service, it is discarded if it does not correspond to the resource for the customer network management service, and if it corresponds to the resource for the customer network management service, the error filtering function is driven. Determining whether there is a first process; As a result of the determination of the first process, if the failure filtering function is not driven, the second and second operations of notifying the operator and the user according to the notification type, storing the corresponding failure details, and confirming the existence of the corresponding failure if the failure filtering function is activated. process; A third step of increasing the count for the corresponding disability item if there is a corresponding disability item as a result of the checking of the second process, adding a disability history if the disability reason is different, and adding the disability item if the disability item does not exist; Integrated failure processing of the customer network management service in the high-speed information communication network, comprising a fourth process of periodically notifying the operator and user of the failure history according to the notification type for each port and virtual connection, and deleting the reported failure item. Way. The method of claim 7, wherein The notification method is a synchronous notification made by calling a CORBA function by a CORBA-enabled dedicated client or a CORBA enabled Java applet (CBA) enabled, characterized in that the customer network management service in the high-speed information network. The method of claim 7, wherein The notification method is an asynchronous notification method for accessing a customer network management service in a high-speed information communication network, characterized in that the asynchronous notification that reads the result by polling. The method of claim 7, wherein The notification method is an integrated error handling method of a customer network management service in a high-speed information communication network, characterized in that the e-mail (E-Mail) notification.

Images