KR101184916B1 - Method for generating data structure related fault process and method and apparatus for providing fault management information using the same - Google Patents

Abstract

The present invention discloses a method for generating a data structure related to failure processing information. More specifically, it provides graphic information and time series text information according to various types of failures occurring in the Multi-Sevice Provisioning Platform (MSPP) network and information on the response of the operator. It generates graphic and textual information (hereinafter referred to as 'snapshot') about alarm occurrence, operation action, and document status change that occur until then, and arranges one or more snapshots according to the time of creation. A stored trouble slip record is generated, and the lower node of the snapshot includes topology screen information, which is graphic information about a failure, and textual detailed failure slip screen information, which is arranged in time series with respect to the failure.

According to an exemplary embodiment of the present invention, the snapshot object is managed in a step-by-step manner according to the MSPP network topology, fault information, and action history, and the details are graphically displayed and the matrix type journal screen is displayed according to a time-series selectable interface. Through this, disability management information can be provided in a unified manner.

MSPP, Network, Failure Management, MVC, Topology

Description

Method for generating data structure related fault process and method and apparatus for providing fault management information using the same}

The present invention relates to a method for generating data structures related to error handling information. In particular, the present invention provides graphic information and time-series text information according to information on various types of failures and operators' responses occurring in a multi-sevice provisioning platform (MSPP) network. The present invention relates to a method of generating data structure related to fault handling information, and a method and apparatus for providing fault management information using the same.

Unlike the conventional SONET / SDH optical transmission device, in the field of information and communication network, the multi-service provisioning platform (MSPP) network device, which is recently attracting attention, has the function of the optical transmission device and the line distribution function in one device. It also includes a combination of data interfaces such as Plesiochronous Digital Hierarchy (PDH), Synchronous Digital Hierarchy (SDH), and Fast / Gigabit Ethernet. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a view for explaining a schematic structure of a conventional communication network and a corresponding MSPP network. As shown in FIG. 1, a conventional private line, a virtual privilege network (VPN), a broadband converged network (BcN), and a Kornet network are illustrated. In addition to providing a variety of services in the form of a simple network, the transmission and distribution is made in a single device, there is an advantage that can easily provide new services introduced in the future.

The MSPP network is particularly suitable for providing a dedicated corporate network service, and therefore, it is important to provide reliable services through efficient failure management and rapid recovery of the dedicated corporate circuit service.

2 is a diagram for explaining a failure case occurring in a general MSPP network.

First, in a general transmission network, in order to provide circuit service, a transmitting device bundles low level signals at a higher speed level through a multiplexing process, allocates a certain time slot, and transmits the intermediate devices. The line signal is transmitted through cross-connection of the input line signal, and finally, when the line signal reaches the receiver, the receiver device provides a service through demultiplexing of the signal.

According to the foregoing, the first and second voice terminal apparatuses A and H of DS1 (2M) / DS3 (45M) speeds and the 155M speeds will be described as an example of the MSPP network configuration shown in FIG. It consists of the first and second MSPP devices (B, G) and the third to sixth MSPP devices (C, D, E, F) of 2.5G speed, and the voice terminal devices (A, H) according to the customer's request. In case of providing 2M dedicated line service for financial institutions, 2M dedicated line signal is first multiplexed to 45M from the first voice end station (A) and then to the low speed port of the first MSPP device (B) with coaxial cable. This signal is connected to the 155M low speed port of the third MSPP device C through the high speed optical port after being multiplexed to 155M with a signal light input from another place. In the third MSPP apparatus C, after performing the cross linking function, the signal is multiplexed to 2.5G class and transmitted to the fourth MSPP apparatus D through the high speed part optical transmission unit. Is received and relayed to the fifth MSPP apparatus (E). The fifth MSPP apparatus E demultiplexes the signal to the 155M class via the high speed unit, and then transmits the signal to the sixth MSPP apparatus G from the low speed unit. The sixth MSPP apparatus G transmits the final signal to the second voice terminal apparatus H through demultiplexing, which is a reverse process of the aforementioned second MSPP apparatus B.

As described above, in the conventional MSPP network, since a dedicated line signal is transmitted through complex multiplexing, cross linking, transmission, cross linking, and demultiplexing, various types of devices may be used in various devices depending on the location and direction of a point where a failure occurs. An alarm will occur. Referring to the table of the figure, it shows an example of five circuit occurrence failures, for efficient failure management because the source information generated from one device propagates various alarms to a plurality of devices in the network topology Fault monitoring of entire topologies, not individual devices, is required.

As a prior art disclosed for more efficient network failure management, Korean Patent No. 0623261 provides a visual network diagram to a network administrator, and each of various managers and networks necessary for network management such as network setup, change, and release. Although there is a feature that provides an interface between objects, there is a limitation in that it cannot determine the topology when a failure occurs and provide the failure processing time series.

In addition, Korean Patent Laid-Open Publication No. 2007-0084594 provides an in-platform resource management method for network management, and collects performance data indicating processing execution and resource utilization for platform resource utilization for network management and re-uses resources according to the penalty clause. Although there is a feature of assigning, there is a disadvantage in that it does not provide information on the progress of the troubleshooting process.

Therefore, when a failure occurs in an MSPP network having a more complex structure than the existing network, failure related information is displayed in a simple text format or topology only showing the failure of the current situation as shown in FIG. There is a problem that it is not easy to identify the cause of failure and to check the details of the actions at the topology level.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problem, and manages a snapshot object step by step to manage the MSPP network topology, fault information, and action history, and graphically displays the snapshot object according to the time series according to a selectable interface. The purpose is to provide the screen and the matrix type journal screen in a unified manner.

In addition, the present invention, because the measures for the recovery of the fault depends on the network type, device type, fault location, fault signal constituting the topology, as well as efficient fault recovery occurs in the field for the rapid training of network operation management professionals The purpose of this study is to provide a knowledge management system and provide learning materials for the various disability situations and the resulting disability recovery.

In order to achieve the above object, a data structure generation method for fault management of a device connected to an MSPP network according to a preferred embodiment of the present invention, alarm generation, operation occurred until the first failure occurs in the network topology is released Generates graphical and textual information (hereinafter referred to as 'snapshots') on actions and document status changes, and generates fault slip records in which one or more of the snapshots are sorted and stored over time. The lower node of the snapshot includes topological screen information, which is graphic information about a fault, and textual detailed fault slip screen information arranged in time series with respect to the fault.

The lower node of the topology screen information is a node that stores data on location information, fault level, input content tooltip, and document status.

The lower node of the detailed trouble slip screen information is a node that stores location information, detailed alarm information, detailed action contents and slip state related input contents.

The fault information record includes a trace bar for selecting any one of the snapshots; Stereoscopic topology information which is information necessary for graphically displaying the topology screen information; Linear topology information which is information necessary for forming a column of the detailed trouble slip screen information; And a snapshot counter, which is a temporal identification information of the snapshot.

In order to achieve the above object, a failure management method using a data structure generated for failure management of a device connected to an MSPP network according to an embodiment of the present invention, (a) attempting to connect to one or more MSPP devices; ; (b) receiving network information from the MSPP device; (c) generating a snapshot corresponding to the network information; (d) generating and storing a trouble slip record in which one or more of said snapshots are sorted and stored according to a flow of time generated; And (e) providing the trouble slip record to an operator's terminal.

The snapshot may include topology screen information that is graphic information about a failure that has occurred; And textual detailed disability slip screen information arranged in time series with respect to the disability.

Between the step (d) and step (e), it characterized in that it further comprises the step of updating the fault slip record reflecting the change of the network information.

In order to achieve the above object, a failure management apparatus using a data structure generated for failure management of a device connected to an MSPP network according to a preferred embodiment of the present invention, receiving the connection and network information with one or more MSPP devices; Communication module; A topology collecting module and a fault information collecting module for collecting the network information; In response to the information collected by the topology collection module, graphically and textual information (hereinafter, referred to as 'snapshot') of alarm occurrence, operation action, and document state change that occurred until the first failure occurs and is released from the network topology. A topology analysis module for generating topology screen information, which is graphic information about a fault which has occurred; A fault information analysis module for generating textual detailed fault slip screen information arranged in time series with respect to the fault among the snapshots in response to the information collected by the fault information collecting module; A snapshot object management module configured to generate a failure slip record in which the topology screen information and the detailed failure slip screen information generated by the topology analysis module and the failure information analysis module are arranged and stored according to the generated time; A fault snapshot diagram module for providing the fault slip record to an operator's terminal; And a slip processing module for updating the trouble slip record by reflecting the change of the network information.

The disability statement record further includes a disability classification metadata that is a criterion for classifying each record according to a specific disability, and further includes a disability learning module that provides the disability statement record when the disability classification metadata is selected by a learner. It features.

According to a preferred embodiment of the present invention, data is structured as a snapshot object for events that occur until failure occurs and breaks down according to the network information of the MSPP network, and correspondingly, a graphic topology screen and time series are listed. By providing a detailed disability slip, there is an effect that can easily check the information related to the disability.

In addition, by using the disability-related information, the various disability situations and their disability recovery history are configured as a knowledge management system and provided as learning materials, which can be used as a more effective disability learning tool.

Hereinafter, with reference to the drawings will be described a method of generating a data structure related to fault handling information, a method and a device for providing fault management information using the same according to a preferred embodiment of the present invention.

Prior to the description, as used below, “snapshot” refers to an instant object that is configured based on events for alarms, operating actions, and document state changes that occur until the first failure occurs in the topology and is released. .

First, with reference to the drawings will be described a standard process performed by the operator in the event of a failure.

4 is a diagram illustrating a standard process performed by an operator when a failure occurs.

As shown, after the MSPP device is driven (S10), when an alarm for a failure occurs for the first time (S12), the network management system issues a failure slip and displays the status of the slip as "new" (S20). Alarms for other faults may occur before and after the slip is generated (S22), and the operator who recognizes the above-mentioned fault slip through the operation program (S25) may include a detailed description including device facilities and line information of the corresponding fault information. After confirming that the operator inputs the analysis of the fault into the system, the status of the fault slip becomes “check” (S30). In this case, alarms for other failures may be additionally generated from time to time (S32), and when the check is in the “checked” state, the operators take various measures for recovering from the failure (S34) through message communication and failure test between operators. . When the fault is recovered in step S34 (S36) and the cause of the failure and the repair history for the operator is inputted, the status of the fault slip is set to "close" (S40) and the management procedure for one fault is terminated. In the present invention, the management of the failure caused by the above-described steps is performed.

5 is a view showing the structure of a failure management apparatus according to an embodiment of the present invention.

As shown, the failure management apparatus 200 of the present invention, the communication module 210 to communicate with one or more MSPP device 100, topology collection module and topology analysis module (222, 224) for processing topology-related information, Fault information collection module and analysis module (232, 235) for processing fault-related information, snapshot object management module (241), document processing module (243), fault learning module for processing functions related to snapshots, slips and learning 245 and faulty snapshot depiction module 247.

In detail, the communication module 210 is connected to one or more MSPP devices 100 and performs a function of collecting network and fault related information from these devices. The communication module 210 transmits a predetermined command (RTRV-NET) to each MSPP device 100 and requests network information in response to the device driving. Such predetermined instructions are according to a grammar defined by the designer, and a preferred example thereof will be described later.

Referring back to FIG. 5, the topology collection module 222 collects network information received by the communication module 210 and performs a function of calling the topology analysis module 224.

The topology analysis module 224 analyzes network information and provides a function to the failure snapshot management module 241.

The failure information collection module 232 performs a function of collecting failure related information generated in the MSPP device 100 through the communication module 210.

The fault information analysis module 235 analyzes the fault related information collected by the fault information collecting module 232 and provides the fault snapshot management module 241.

The fault snapshot management module 241 includes a fault occurrence and a processing situation every moment of occurrence of an event in response to the topology information and fault related information analyzed from the above-described topology analysis module 224 and the fault information analysis module 235. Performs the function of configuring snapshot object information. Here, the snapshot is displayed through the fault snapshot showing module 247.

The document processing module 243 performs a function of processing the document confirmation and the history in response to the operator, and provides the result to the snapshot object management module 241. The snapshot object management module 241 updates the snapshot object information by reflecting the above-described result. The update result is also reflected in the next snapshot through the fault snapshot city module 247.

The disability learning module 245 provides a function for learning during the disability progression or after the disability ends. The failure learning module 245 supports displaying by snapshot on the screen through the failure snapshot city module 247 when the failure history is restored through the trace bar of the operation program.

The failure snapshot city module 247 displays a graphical topology screen and failure history information listed in time series in response to the snapshot object information generated by the failure snapshot management module 241. The failure snapshot showing module 247 is connected to the operator's terminal to display the above-described failure history information.

The aforementioned snapshot object management module 241, the document processing module 243, the disability learning module 245, and the disability snapshot city module 247 utilize the MVC (Model-View-Controller) pattern to manage the snapshot object. It is possible to quickly add completely different design forms that use the same information separately from the design such as various obstacle screens on the screen, and it is easy to modify because it is hardly influenced by anything except design elements. In other words, it is possible to output different results on the screen according to the change of the state of the information to be referred to, and to flexibly cope with structural changes required from the outside through the loose form of combination defined by software engineering. In the present invention, the trace bar, the topology screen, and the detailed failure slip screen correspond to views, the slip processing module or failure learning module corresponds to a controller, and the snapshot object management module (model) corresponds to a model.

6 is a diagram illustrating an example of a disability management and learning program screen according to an embodiment of the present invention.

As shown in the figure, a trace bar 300 is displayed on the top to track the failure situation step by step. At the bottom of the trace bar 300, a topology screen 320 showing graphical topology information and failure status of the MSPP network is displayed, and at the bottom of the topology screen 320, the topology information is linearly converted into rows, In the column, a two-dimensional detailed disability slip screen 330 representing time series disability / action information indicating an occurrence and processing of disability over time is displayed. The figure shows an event made in a total of nine steps from recovery to failure after the failure, and the topology bar 320 and the detailed failure slip screen 330 because the progress bar 310 of the trace bar 300 is currently selecting the fourth column. ) Will indicate the status of the fourth of nine steps. Steps other than these are displayed according to the operator's selection of the trace bar 300.

If the operator sets the progress bar of the trace bar 300 to select the first column, the topology screen 322 shows a new document occurrence notification button 322 and a “Loss of Signal” alarm “Major” alarm. The circle corresponding to the grade is displayed on the “kisti4” device (D), and the message “LOS” is displayed on the detailed trouble slip screen 330. The circle described above may have a different color depending on the alarm grade. The higher the value is, the closer it is displayed to red.When the operator selects a cell, the device name, device type, customer name, installation name, occurrence location, alarm details, alarm class, service effect, occurrence time and original alarm information are displayed. Provides detailed alarm information, including.

In addition, when the operator sets the progress bar of the trace bar 300 in the second column, the topology screen 320 generates an alarm "AIS (Alarm Indication Signal)" of a lower level corresponding to "Minor" in the same MSPP device. Keep red, the color of “Major” grade, which is the current alarm status. In general network management, use “Critical”, “Major”, “Minor”, “Warning”, “Clear”, and the priority is “ Critical ”is the highest and“ Clear ”is the lowest. The detailed document screen 330 may display“ AIS ”in orange in the corresponding column.

In addition, when the operator sets the progress bar of the trace bar 300 in the third column, the topology screen 320 shows a red circle corresponding to the alarm level of “Major” of the “Remote Defect Indication (RDI)” alarm. (A) is displayed on the detailed disability statement screen 330, only the message "RDI" is displayed in the corresponding column.

Then, when the operator recognizes the failure situation and places the progress bar at the fourth stage in which the failover recovery action is first performed (310), the button indicating the status of the document changes to “OK” on the topology screen 320, and the “kisti4” device is displayed. In (D), a tooltip called "Action" is displayed to indicate that the operator's failover action has been implemented. In this case, it is preferable that the above-described tool tip is displayed in a flickering form to focus the operator's eyes. These tooltips are implemented in such a way that when the operator selects the tooltip and sees the details of what action was taken, the tooltip is automatically released. In the detailed trouble slip screen 330, only simple action summary information such as “loopback” is displayed. When the operator selects a cell, the detailed trouble slip screen 330 displays the same detailed information as when the tooltip is pressed.

If the above-described series of fault handling processes continue and all faults are recovered, the fault slip is closed and the final event is provided by placing the progress bar of the trace bar 300 in the ninth stage. In the topology screen 330, the button indicating the document status is changed to "Finish", and a text tooltip of "Finish" is displayed to inform the operator that the operator has entered the document closing details in the "kisti4" device (D). The detailed disability slip screen 330 displays “construction damage recovery” which is information input by the operator after closing the slip in the column.

7 illustrates an example of a command and network information used in an MSPP network according to an embodiment of the present invention.

As shown, when the operator sends a "RTRV-NET" command to the MSPP device in the program, the MSPP device provides a response to the command. Among the responses provided, “tid” is a target id uniquely set for each device connected to the human network. "Nename" is the name given to the device in text form. "Speed" is the speed provided by the device, and "devtype" is the manufacturer's unique model number for MSPP devices in the 155M, 622M, and 2.5G class. "Gne" indicates whether the device is directly connected to the EMS network. “Ip” means the IP set in the device. If it is not “gne”, it is omitted because it is not directly connected to EMS network. "Connstat" means connection status between MSPP device and server. "Disconn_reason" indicates the cause of disconnection when "connstat" is disconnected and "disconn". "Nettype" indicates the type of the MSPP network. In the figure, there are two types of RING and PTP (Point To Point). "Netname" is the name of the topology assigned to the MSPP network in text form. “Topology info” indicates the topology information to which the device belongs and its meaning is as follows.

1) The “kisti1” device is marked “1-1” and is the first device in the 1G ring network at 2.5G speed.

2) The "kisti2" device is labeled "1-2" and is the second device of the ring-type network at 2.5G speed.

3) The “kisti3” device is indicated as “1-3 1-1-1” and is the third device of the 1G ring network with 2.5G speed, and the low speed unit of the device is connected to the network 1-1. . With the above information, the speed and type of the lower network “1-1” connected to network 1 cannot be determined.

4) The “kisti4” device is indicated as “1-4 1-2-1”. It is the fourth device of the ring-type network of 2.5G speed and the low speed unit of the device is connected to the network of 1 and 2. With the above information, the speed and type of the lower network "1-2" connected to the network 1 cannot be determined.

5) The “kisti5” device is labeled “1-1-2” and is the second device of linear network 1-1 at 155M speed. At this time, it is possible to know the network speed and type “1-1” which was not understood when analyzing the “kisti3” device described above.

6) The “kisti6” device is indicated as “1-2-2 1-2-1-1” and is the second device of the 1-2 ring network at 622M speed, and the low speed unit of the device is 1-2- You are connected to network 1. At this time, it is possible to determine the speed and type of the lower network "1-2-1" connected to the network "1-2" described above.

7) The “kisti7” device is indicated as “1-2-3 1-2-2-1” and is the third device of the ring network No. 1-2 at 622M and the low speed unit of the device is 1-2-2. Connected to the network With the above information, the speed and type of the lower network "1-2-2" connected to the network "1-2" cannot be determined.

8) The “kisti8” device is labeled “1-2-1-2” and is the second device of the linear network No. 1-2-1 at 155M speed. Here, we can see the network speed and type "1-2-1" which we did not grasp when analyzing the "kisti6" device described above.

9) The “kisti9” device is labeled “1-2-2-2” and is the second device of the 1-2-2 linear network at 155M speed. Here, we can see the network speed and type "1-2-2" which we did not grasp when analyzing the "kisti7" device described above.

8 is a diagram illustrating an initialization process required for using an operation program for managing and learning a disability according to an embodiment of the present invention.

As shown, first, when the operator executes the program (S110), the program attempts to connect to the MSPP device (S120), and depending on whether the connection is successful (S123), the topology information through the aforementioned "RTRV-NET" command. Collect (S130), if the connection fails in step S123 and attempts to access again. However, excessive reconnection attempts can put a load on the server, so if the number of attempts set by the designer is greater than N (N is a natural number of 1 or more), the device sets the connection failure and informs the operator of the details (S126). Thereafter, the failure processing apparatus analyzes the collected topology information to generate a tree object for the topology (S140), and displays it on the top of the failure information screen (S150). In response to the tree object for the aforementioned topology, the stereoscopic topology information is converted into linear topology information to obtain final linear topology information (S160). These steps S140, S150 and S160 will be described later with reference to the accompanying drawings.

Also, based on the data, the detailed detailed disability statement screen corresponding to the disability information screen is initialized (S170). Thereafter, the records of the trace bar and the detailed trouble slip screen are initialized (S180 and S190) to prepare an operator to display a corresponding snapshot when the trace bar is operated.

Hereinafter, a method of generating and displaying a tree object of the above-described topology will be described in detail with reference to the accompanying drawings.

9 is a diagram for describing a method of generating a tree object of a topology according to an embodiment of the present invention. For convenience of description, each node uses the same reference numerals as in FIG. 6.

As shown, the root network of the topology has an identifier of "1" and the network consists of four devices in a 2.5G class ring. In addition, the root network "1" is connected to the "1-1" and "1-2" networks at low speed parts of the "kisti3" (C) device and the kisti4 "(D) device, respectively. Network “1-1” is a 155M linear network consisting of two devices, with no subnetwork connected. And network “1-2” is composed of three nodes in 622M ring, and “1-2-1” and “1-” are attached to low speed part of “kisti6” (F) device and “kisti7” (G) device, respectively. Network 2-2 ”is connected. Also, networks “1-2-1” and “1-2-2” are 155M linear networks, consisting of two devices, with no subnetwork connected.

Topology analysis and tree objects are generated in the above-described order. After the topology display is completed, the linear topology information constituting the X axis of the detailed fault message window is obtained. First, the results of the linearly transformed linear topology are shown in Table 1 below.

order Network identifier One 1-1 2 1-2 3 1-3 4 1-4 5 1-1-1 6 1-1-2 7 1-2-1 8 1-2-2 9 1-2-3 10 1-2-1-1 11 1-2-1-2 12 1-2-2-1 13 1-2-2-2

If the nodes connecting the upper network and the lower network are removed from the transformed primary result, it is shown in Table 2 below.

order Network identifier One 1-1 2 1-2 3 1-3 4 1-4 5 1-1-1 6 1-2-2 7 1-2-3 8 1-2-1-2 9 1-2-2-2

Thus, the final linear topology information described above is obtained. On the basis of the above information, the detailed failure slip screen (330 of FIG. 6) is initialized. Initialization begins by listing nodes of linear topology in individual cells from left to right on the detailed fault slip screen, then “1-2”, “1-3”, “1-2-2”, “1-2-3” Likewise, when an alarm occurs, a connection node included in several networks divides the cell into two cells so that the alarm can be analyzed and identified as a high speed alarm belonging to a higher network or a low speed alarm belonging to a lower network. In addition, the fault warning that occurred or the operator's action history information on the Y axis is displayed in the order of occurrence.

Hereinafter, a process of displaying graphicized topology information on the top of the fault information screen will be described in detail with reference to the accompanying drawings.

FIG. 10 is a diagram for describing a method of displaying graphicized topology information step by step according to an exemplary embodiment of the present invention. In the following description, a method of displaying the top topology screen shown in FIG. 6 will be described as an example.

As shown in the figure, a ring-type network corresponding to the root node in the tree structure is drawn in the center of the screen. The information needed to draw a ring network is as follows.

“Number of devices making up the ring (nodenum)”

“Angles and coordinates (x, y) of the individual devices in the ring relative to the center point (cx, cy), radius (r)

In the case of the root node, the center point of the circle is the center point of the top of the screen where the topology is drawn, and the initial value is set, and the radius is set according to the intention of the operator. For example, it is preferable to set it as 100G for a 2.5G ring, 80 for a 622M ring, and 60 for a 155M ring to be distinguished according to the speed of the ring. The number of devices making up the ring is already included in the tree node information, and the information to be calculated to draw the ring is the "angle and coordinate (x, y) of the individual devices making up the ring." This is obtained by looping the number of individual devices constituting the ring according to Equation 1 below.

angle = ((nodeindex * 360) / nodenum) + (270% 360)

x = cx + COS (angle * 3.14 / 180) * r

y = cy + SIN (angle * 3.14 / 180) * r

In Equation 1, the variable "angle" is the angle of the "nodeindex" device, "x" is the X coordinate of the "nodeindex" device, "y" is the Y coordinate of the nodeindex device. In addition, the variable "nodenum" is the number of devices constituting the ring, and the "nodeindex" is assigned a number in the clockwise direction starting from the north pole (0) of the circle in the order of the devices constituting the ring. In addition, "cx" and "cy" are the center points of a circle, and cx = width / 2 and cy = height / 2, respectively. In addition, "r" is the radius of the circle and is set to the initial value 100. However, it is set to 80 for 622M network and 60 for 155M network. The ring network of the root node is drawn with the value obtained by the above equation (1).

After that, we draw the subnetwork connected to the root node's network. To easily draw the lower network connected to the upper network, first divide the upper ring network into four sections (step 2).

315 degrees <= 1 slope <45 degrees

45 degrees <= 2 slope <135 degrees

135 degrees <= 3 slope <225 degrees

225 degrees <= 4 slope <315 degrees

In addition, a template is formed to determine how to display the linear and ring subnetwork connected to the devices on each slope (step 3).

In detail, when the lower network is linear, when connected to the upper network node of the 1/2/3/4 slope, each node draws the length corresponding to the network type of the device from the node to north / east / south / west. (Step 4).

Next, if the lower network is a ring type, set the coordinates of the center point to the same size as the screen size, and then obtain the data structure of the ring according to the above-described method, and then place one on the opposite slope to the slope to which the connecting node of the upper network belongs. Select the node of. For example, when a lower ring network is connected to a device of an upper ring network, the lower network selects a device belonging to four slopes because the angle of the device corresponds to two slopes. Then, the coordinates of the device are matched with the coordinates of the device, and then the coordinates of the devices constituting the nodes of the lower ring network are redrawn to the east (steps 5 to 7). If is present, select an arbitrary node. Repeat this process to draw all the subnetwork to complete the topology screen (steps 8 ~ 13).

According to the above-described steps, the fault management apparatus of the present invention displays a topology screen.

Hereinafter, with reference to the drawings will be described the term concept and configuration method of the data structure according to the embodiment of the present invention.

11 is a view for explaining the concept of terms and configuration method of the data structure according to an embodiment of the present invention.

As shown, one fault slip record 610 has the same number of snapshot objects 616 as the event (N, N is one or more natural numbers), and the trace bar 612 has one snapshot. If pointed to (614), the screen displays information based on the snapshot object.

In addition, the internal structure 620 of the fault slip record 610 stored for fault management and learning is displayed on the X-axis at the bottom of the screen and the stereoscopic topology information 621 displayed on the upper screen obtained through the initialization process. Linear topology information 623, snapshot counter 625 indicating the number of snapshot objects contained in fault slip record 610, and snapshot 616 corresponding to the event that occurred until the first failure occurred and was released. Is composed of a set of objects 627.

Referring to the data connection structure 630 of the snapshot, one snapshot 616 is composed of the topological screen information 640 to be displayed at the top of the screen, and the detailed fault slip screen information 650 to be displayed at the bottom. .

The topology screen information 640 includes a fault level 642 occurring in the device, tooltip information 643 showing briefly the action taken by the operator or the entry related to the document state, the document state 644, and the above-described information. Location information 641 of the device to be displayed.

The detailed trouble slip screen information 650 includes detailed alarm information 652, detailed action contents 653, operator inputs 654 related to the status of the document, and a cell of the lower metric to display such information. Includes location information 651.

According to the above-described structure, fault information according to an embodiment of the present invention is configured, the fault management method of the present invention will be described with reference to the drawings.

12 is a diagram illustrating a failure management method according to an embodiment of the present invention.

The failure management method is performed after the initialization of the above-described topology screen and the detailed trouble slip screen. As shown, the operating program connected to the MSPP device collects an alert from the MSPP device (S710). If an alarm occurs, check whether the alarm is the first alarm in the corresponding topology (S720). If it is the first alarm, proceed with the steps for issuing a fault slip in the topology, and perform a failure management procedure according to the MVC pattern. In case of failure, immediately proceed with the fault management procedure.

The above-described failure management procedure consists of three actions of MVC pattern, firstly, a step of constructing a snapshot object by an event of failure / action / status change (S760), and secondly, the top and bottom of the program with the created snapshot data. The step of displaying the details on the lower screen (S762), the third step is to update the trace bar in accordance with the corresponding snapshot counter (S764).

In detail, the failure management procedure configures a snapshot object for a failure based on the generated failure information. The contents of the failure management procedure include “location information (641 in FIG. 11) and failure grade ( 642 in FIG. 11), the document state (644 in FIG. 11) ”is set, and“ location information (651 in FIG. 11) and detailed alarm (652 in FIG. 11) are set in the detailed trouble slip screen information. When the snapshot object is created based on the newly generated alarm, the details are displayed at the top and bottom of the operating program. Then, the snapshot counter (625 in FIG. 11) in the fault slip record record is increased by 1 and the details are applied to the trace bar. do.

After step S730, the operator detects the alarm and checks whether the action has been taken to resolve it (S740). Operators enter a fault management procedure when they perform actions such as “loopback” or “unit transfer”. In the problem management procedure after performing this step, when the snapshot object is configured based on the operator's action information, the location information (641 in FIG. 11) and the input content tooltip (643 in FIG. 11) are included in the topology screen information in the snapshot data structure. The location information (651 in FIG. 11) and the detailed action contents (653 in FIG. 11) are set in the detailed trouble slip screen information. The subsequent procedure is the same as described above.

After S740, when the operator recognizes the issued document and enters the details while performing the "confirmation" or "close" action, the above-described trouble management procedure is entered. In the failure management procedure after performing this step, a snapshot object is constructed based on the operator's input information. In the snapshot data structure, the topology screen information includes location information (641 in FIG. 11), an input tooltip (643 in FIG. 11), and a slip. A state (644 of FIG. 11) is set, and position information (653 of FIG. 11) and input contents related to the document state (654 of FIG. 11) are set in the detailed trouble slip screen information. The subsequent procedure is the same as described above.

If it is determined that the fault slip has been closed through the above-mentioned steps, the cause of failure is identified, and the deadline, fault cause, fault recovery history, and deadline information are stored in the memory of the operating program. Save (S780).

Thereafter, the learner may further include a procedure for inputting the knowledge management system so that it can be reused in learning disabilities.

Fault management and learning When storing fault record records in the database of the knowledge management system, network types such as ring and linear, and device types such as 155M, 622M and 2.5G can be configured to enable learners to search with various conditions. It also stores fault classification metadata information including fault location such as high speed part, cross link part and slave part, and fault signal such as LOS, AIS and RDI. If the operator moves the trace bar in order to analyze the previous failure information even at the stage of proceeding without closing the failure management function (S790), the display is displayed on the screen based on the snapshot information corresponding to the corresponding number (S795).

13 is a diagram illustrating a method for providing disability learning by a learning knowledge management system according to an embodiment of the present invention.

As shown, the network management operator or learner executes the learning program to manage and learn the faults generated in the MSPP network (S810), and stores the fault classification metadata input when the fault slip record is saved by the fault processing deadline. Select (S820). The aforementioned failure classification metadata is a criterion for classifying each record according to a specific failure. In step S820, in response to the learner's selection, the program calls the failure slip record record corresponding to the condition selected in the database to the program (S830), and sequentially displays all snapshot objects included in the failure slip record on the screen (S840). The program reads the snapshot counter from the fault record record, initializes the trace bar to track the fault condition step by step, and reads the topological information of the fault record record to display the topology on top of the operating program. Initialization is performed by reading the linear topology information and arranging the information on the X axis at the bottom of the operating program. Finally, the snapshot objects are called one by one and displayed in the detailed document contents step by step. When the fault document record is displayed in the program, the trace bar selects the last position. Then, when the operator or learner changes the selection of the trace bar for disability learning (S850), the screen is cleared and displayed on the screen sequentially from the first snapshot to the corresponding snapshot object of the number where the trace bar is located (S852). If there is no change in the trace bar, the snapshot currently displayed on the screen is maintained (S855).

The above-described method for generating a data structure related to the error handling information and a method for providing the error handling information using the same include a CD-ROM, a RAM, a ROM, a floppy disk, a hard disk, a magneto-optical disk, and the like, implemented as a program. It can be stored in the recording medium.

The technical spirit of the present invention has been described above with reference to the accompanying drawings, but this is by way of example only and not intended to limit the present invention. In addition, it is a matter of course that various modifications and variations are possible without departing from the scope of the technical idea of the present invention by anyone having ordinary skill in the art.

1 is a view for explaining a schematic structure of a conventional communication network and the corresponding MSPP network.

2 is a diagram for explaining a failure case occurring in a general MSPP network.

3 is a diagram illustrating an example of a method for displaying a conventional disability related history.

4 is a diagram illustrating a standard process performed by an operator when a failure occurs.

5 is a view showing the structure of a failure management apparatus according to an embodiment of the present invention.

6 is a diagram illustrating an example of a disability management and learning program screen according to an embodiment of the present invention.

7 is a diagram illustrating an example of a command and network information used in an MSPP network according to an embodiment of the present invention.

8 is a diagram illustrating an initialization process required for using an operation program for managing and learning a disability according to an embodiment of the present invention.

9 is a diagram for describing a method of generating a tree object of a topology according to an embodiment of the present invention.

FIG. 10 is a diagram for describing a method of displaying graphicized topology information step by step according to an exemplary embodiment of the present invention.

11 is a view for explaining the concept of terms and configuration method of the data structure according to an embodiment of the present invention.

12 is a diagram illustrating a failure management method according to an embodiment of the present invention.

13 is a diagram illustrating a method for providing disability learning by a learning knowledge management system according to an embodiment of the present invention.

<Explanation of symbols for the main parts of the drawings>

100: MSPP device 200: failure management device

210: communication module 222: topology acquisition module

224: topology analysis module 232: fault information collection module

235: failure information analysis module 241: snapshot object management module

243: document processing module 245: disability learning module

247: fault snapshot city module

Claims (9)

As a method of creating data structures for fault management of devices connected to MSPP network The failure management device generates graphical and textual information (hereinafter referred to as 'snapshot') on the occurrence of alarms, operational actions, and document status changes that occur until the first failure of the network topology occurs. Generate the fault slip records in which the above snapshots are arranged and stored according to the flow of time, Subnodes of the snapshot, Topology screen information, which is graphical information about a fault that has occurred, Textual detailed disability slip screen information arranged in time series for the disability Method of generating a failure handling information data structure comprising a. The method of claim 1, The lower node of the topology screen information, Method for generating a fault handling information data structure, characterized in that the node for storing the position information, fault level, input tooltips and data about the document status. The method of claim 1, The lower node of the detailed trouble slip screen information, And a node for storing location information, detailed alarms, detailed action contents and document state related inputs. The method of claim 1, The trouble slip record, A trace bar for selecting any one of the snapshots; Stereoscopic topology information which is information necessary for graphically displaying the topology screen information; Linear topology information which is information necessary for forming a column of the detailed trouble slip screen information; And Snapshot counter which is a temporal identification information of the snapshot Disability processing information data structure generation method further comprising. MSPP is a fault management method that is executed in a fault management device using data structures created for fault management of devices connected to a network. (a) attempting to connect with one or more MSPP devices; (b) receiving network information from the MSPP device; (c) Graphical and textual representations of alerts, operational actions, and document state changes that occur until the first failure occurs in the network topology in response to the network information (hereinafter referred to as 'snapshot'). Generating a; (d) generating and storing a trouble slip record in which one or more of said snapshots are sorted and stored according to a flow of time generated; And (e) providing the trouble slip record to an operator's terminal; Disability management information providing method using a data structure related to disability processing, including. 6. The method of claim 5, The snapshot, Topology screen information, which is graphic information about a fault that has occurred; And Textual detailed disability slip screen information arranged in time series for the disability Disability management information providing method using a disability processing information related data structure comprising a. The method of claim 6, Between step (d) and step (e), And updating the fault slip record to reflect the change of the network information. MSPP Disability management device using data structure created for fault management of devices connected to network. A communication module for receiving connection and network information with at least one MSPP device; A topology collecting module and a fault information collecting module for collecting the network information; In response to the information collected by the topology collection module, graphically and textual information (hereinafter, referred to as 'snapshot') of alarm occurrence, operation action, and document state change that occurred until the first failure occurs and is released from the network topology. A topology analysis module for generating topology screen information, which is graphic information about a fault which has occurred; A fault information analysis module for generating textual detailed fault slip screen information arranged in time series with respect to the fault among the snapshots in response to the information collected by the fault information collecting module; A snapshot object management module configured to generate a failure slip record in which the topology screen information and the detailed failure slip screen information generated by the topology analysis module and the failure information analysis module are arranged and stored according to the generated time; A fault snapshot diagram module for providing the fault slip record to an operator's terminal; And Document processing module for updating the trouble slip record to reflect the change of the network information Disability management information providing apparatus using a data structure related to disability processing information, including. 9. The method of claim 8, The trouble slip record further includes a failure classification metadata that is a criterion for classifying each record according to a specific failure. The disability learning module provides the disability document record when the disability classification metadata is selected by the learner. Disability management information providing apparatus using a disability processing information related data structure further comprising.

Images