System and method for providing a mission based management system

• US 20050262397A1
• Filed: 01/13/2005
• Published: 11/24/2005
• Est. Priority Date: 05/04/2004
• Status: Active Grant

• Current Assignee: Northrop Grumman Systems Corporation (Northrop Grumman Corporation)
• Original Assignee: Northrop Grumman Systems Corporation (Northrop Grumman Corporation)
• Inventors: Fitzgerald, David J., Sage, Scott E., Lindorf, Daniel P., Jensen, Eric S.
• Granted Patent: US 8,347,145 B2
• Time in Patent Office: Days
• US Class Current: 714/31
• CPC Class Codes: H04L 41/0631 using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/0888 Throughput
• CPC Class Codes: H04L 43/091 Measuring contribution of individual network components to actual service level
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: Y04S 40/00 Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them

Abstract

An embodiment of the present invention may provide a method and system for event notification, performance and/or risk assessment based on mission impact that may be due to actual and/or potential info-structure disruptions. In one embodiment of the present invention, one or more network event messages may be received from a source or multiple sources. An operational mission impacted by a network event may be identified based on a received network event message and mapping with an operational architecture task identifier associated with the impacted operational mission and an element identifier associated with a source element.

Claims

1. A method comprising:

receiving one or more network event messages from a source;

identifying an operational mission impacted by an network event based on a received network event message and mapping with an operational architecture task identifier associated with the impacted operational mission and an element identifier associated with a source element.

2. The method of claim 1, further comprising:

queuing the one or more received network event messages based on priority.

3. The method of claim 2, wherein priority is based on a pre-determined potential for operational impact based on a change in performance.

4. The method of claim 2, wherein priority is based on a pre-determined potential for operational impact based on a change in risk.

5. The method of claim 1, wherein the source element is associated with an info-structure component having a performance value above or below a predetermined threshold.

6. The method of claim 1, wherein the source element is associated with an info-structure component having a risk assessment value above or below a predetermined threshold.

7. The method of claim 1, wherein the source element is associated with an interface.

8. The method of claim 1, wherein the source element is associated with a node.

9. The method of claim 1, further comprising:

mapping the element identifier with a corresponding service interface identifier.

10. The method of claim 9, further comprising:

mapping the service interface identifier with one or more operational task identifiers associated with an operational task.

11. The method of claim 9, further comprising:

mapping the service interface identifier with one or more operational mission identifiers associated with the impacted operational mission.

12. The method of claim 1, further comprising:

generating a report identifying the source element that caused the network event.

13. The method of claim 1, wherein the source is part of a telecommunications network.

14. The method of claim 1, wherein the source is part of an information technology network.

15. The method of claim 1, wherein the source is part of a power grid network.

16. A method monitoring a network comprising:

receiving one or more network event messages from a source;

mapping a source element identifier with a received network event message from the one or more network event messages received;

mapping the source element identifier with a corresponding service interface identifier;

mapping the service interface identifier with one or more operational task identifiers associated with an operational mission; and

identifying an operational mission impacted by a network event based on the received network event message, and the mapping of the service interface identifier with the one or more operational task identifiers, the mapping of the source element identifier with the corresponding service interface identifier and the mapping of the source element identifier with the received network event message.

17. The method of claim 16, wherein the source element identifier is associated with a network info-structure component.

18. The method of claim 16, further comprising:

generating the network event message if a performance value associated with a network info-structure component reaches a pre-determined performance threshold level.

19. The method of claim 16, further comprising:

generating the network event message if a risk value associated with a network info-structure component reaches a pre-determined risk threshold level.

20. The method of claim 16, further comprising:

prioritizing the one or more network event messages based on a pre-determined threshold value.

21. A network server comprising:

a receiver to receive one or more network event messages from a source; and

an event processor to identify an operational mission impacted by a network event based on a received network event message and mapping with an operational architecture task identifier associated with the impacted operational mission and an element identifier associated with a source element.

22. The network server of claim 21, further comprising:

a buffer to queue the one or more received network event messages based on priority.

23. The network server of claim 21, wherein the source element is associated with an interface.

24. The network server of claim 21, wherein the source element is associated with a node.

25. The network server of claim 21, wherein the event processor is to map the element identifier with a corresponding service interface identifier.

26. The network server of claim 21, wherein the event processor is to map the service interface identifier with one or more operational task identifiers associated with an operational task.

27. The network server of claim 21, wherein the event processor is to map the service interface identifier with one or more operational mission identifiers associated with the impacted operational mission.

28. The network server of claim 21, further comprising:

an output interface to generate a report to identify the source element that caused a network event.

29. The network management system, comprising:

a network management server to receive an event message associated with a network event and to identify an operational task that has been impacted as a result of the network event based on mapping between an identifier associated with the operational task and the event message; and

a client terminal coupled to the network management server, wherein the network management server to identify a network info-structure component associated with the event message and to output the identity of the network info-structure component to the client terminal.

30. The system of claim 29, further comprising:

a transmitter associated with a network info-structure component to transmit the event message to the network management server.