Data management system for a telecommunications signaling system 7(SS#7)

• US 5,799,317 A
• Filed: 11/08/1995
• Issued: 08/25/1998
• Est. Priority Date: 11/08/1995
• Status: Expired due to Term

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: MCI Communications Corporation (Verizon Communications Inc.)
• Inventors: Shen, Yi-Shang, He, Jingsha
• Primary Examiner(s): Lintz, Paul R.
• Application Number:
  US08/555,422
• Time in Patent Office: 1,021 Days
• Field of Search: 395/615, 379/230, 370/410, 370/426
• US Class Current: 1/1
• CPC Class Codes: G06F 11/2268 Logging of test results
• CPC Class Codes: H04Q 3/0025 Provisions for signalling
• CPC Class Codes: H04Q 3/0075 Fault management techniques

Abstract

A data management system is connected to a Signaling System 7 telecommunications network (SS#7). Network elements and other data sources of the SS#7 network provide alarm data to the management system when problems occur with the network. The data management system includes a database library that classifies the problem and provides prioritized resolutions, based on past historical events. The library continues to expand with data each time an alarm is resolved. Data from the network elements are also stored for generation of reports, such as those dealing with configuration, performance, faults, and security.

Claims

1. A data management system for an SS#7 network that contains network elements, including SS#7 nodes and protocol monitoring units (PMUs), and comprising:

interconnection means for connecting data from the network elements to a central relational database for storing the data;

means for storing a problem/resolution library of historical network alarm events and their resolutions;

server means interposed between the central relational data base and the interconnection means and including

(a) means for connecting the central relational database to the problem/resolution library for selectively adding an event, derived from the central relational database to the problem/resolution library;

(b) data processing means connected to the central relational database for generating preselected reports from the data derived from the network elements; and

first client means connected to the interconnection means for accessing the server means and maintaining the central relational database; and

second client means connected to the interconnection means for managing the SS#7 network.

2. The system set forth in claim 1 further comprising workstation means, connected between the network elements and the interconnection means for monitoring the operation of the network elements.

3. A method for intelligently managing data derived from an SS#7 network that contains network elements, including SS#7 nodes, and comprising the steps:

monitoring the network elements of an SS#7 network;

generating data indicative of the monitored network elements;

storing the generated data;

processing the generated data to detect an active alarm condition;

comparing the alarm condition to previously received and stored active alarm data;

during comparing, consolidating an active alarm with all active alarms previously received and terminating further processing of the alarm in the event the alarm is correlated with another active alarm previously received;

and if no consolidation occurs, retrieving possible resolutions of the alarm condition based on stored historical data of previous alarm conditions and their resolutions,

determining whether an automated procedure should be invoked to resolve the alarm, and if in the affirmative, resolving the alarm;

and if the aforementioned determining of an automated procedure is negative, pausing to permit non-automated resolution; and

updating the problem/resolution library with data relating to the present alarm condition and its ultimate non-automated resolution.

4. The method set forth in claim 3 further comprising the step of presenting a user, during the monitoring step, with a graphical interface that presents data relative to the alarm condition and the resolution to the user.

5. The method set forth in claim 3 further comprising the step of presenting a user, during the monitoring step, with a graphical interface that presents network element data for permitting the user to conduct data management of the network.

6. The method set forth in claim 5 wherein the data management is conducted in at least one of the areas of network performance, configuration, accounting and security.

7. A method for intelligently managing data derived from an SS#7 network that contains network elements, including SS#7 nodes and protocol monitoring units (PMUs), the method including four principal parts including a data processing part (DPP), a database management part (DMP), a monitor management (MMP) part, and a user presentation part (UPP), the method comprising the steps:

initializing a central data repository in a database through the DMP;

initializing a problem/resolution data library (PR library) with problem/resolution rules, through the DMP;

monitoring preselected events and network parameters through the MMP, the occurrence of specified network events triggering the generation of alarms that are captured by the MMP, as well as status and performance indicators related to the monitored events and parameters;

activating daemon processes on behalf of DPP, DMP, and MMP;

capturing, through the MMP, an alarm generated due to the occurrence of a predefined network event;

forwarding of alarm data from the MMP to the DPP daemon process;

as a result of processing by the DPP, determining when an alarm should be sent to the DMP;

selectively sending alarm information from the DPP to the DMP;

the DMP causing the storing of the alarm information in the central data repository database;

the DPP invoking the DMP to search the resolution rules in the PR library for resolutions to the alarm;

sending a list of resolutions from the DMP to the DPP which then forwards them to the UPP to display the alarm information and resolutions to a user.

8. The method set forth in claim 7 together with the steps of:

determining whether an automated procedure should be invoked to resolve the alarm, and if in the affirmative

involving the DPP to resolve the alarm and generating a message that is connected to the UPP so as to confirm the action taken by the DPP.

9. The method set forth in claim 7 wherein the DPP invokes the DMP to apply aliasing rules in the PR library to consolidate the alarm with all active alarms previously received after the DMP causes the storing of alarm information in the central data repository database;

and

terminating further processing of the alarm in the event the alarm is correlated with another active alarm previously received.

10. The method set forth in claim 8, wherein, if an automated procedure is not to be followed, the DPP monitors user action from the UPP;

sending a named alarm from the user and a list of resolutions to the DPP;

matching of the named alarm by the DPP and the one in a list of active alarms maintained by the DPP; and

deleting the named alarm from the list of active alarms considered currently resolved.

11. The method set forth in claim 8 further comprising the steps of:

deleting the alarm from a list of active alarms because the alarm is considered to be resolved;

invoking the DMP functions by the DPP to search all the resolutions to the named alarm in the PR library; and

for any resolution that is submitted by the user that is not in the PR library, the DPP invoking the DMP to add that resolution to the PR library for that particular type of alarm.