Service monitoring and reporting system

• US 20020143920A1
• Filed: 03/28/2002
• Published: 10/03/2002
• Est. Priority Date: 03/30/2001
• Status: Abandoned Application

• Current Assignee: Opticom, Inc.
• Original Assignee: Opticom, Inc.
• Inventors: Pandre, Andrei, Dev, Roger, Matthews, Wallace, Rustici, Eric
• Application Number:
  US10/113,199
• Publication Number:
  US 20020143920A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/5045 Making service definitions prior to deployment
• CPC Class Codes: H04L 43/06 Generation of reports
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/0829 Packet loss
• CPC Class Codes: H04L 43/091 Measuring contribution of individual network components to actual service level

Abstract

A system and method for detecting or reporting service level or service outages on a network includes a meta service generator that operates on a network inventory to generate service definitions. The system is a server-based model, and each service definition includes usergroup and points of presence, thus instantiating multiple services in a manner that allows the definition to focus on relevant element events amid massive network event data, and detect service outages quickly and dependably. The outages, transaction spec outages and events so determined may be aggregated to provide overall measures that are compared with thresholds, performance criteria and other service metrics specified in a user Service Level Agreement (SLA) for billing, credit, evaluation or other purposes. Batch processing embodiments may operate with outage logs, and employ a concurrence algebra to correct outage intervals for planned and forced outages, providing a truer measure of performance that allows the system to generate multiple different reports reflecting different compensable or inconsequential outage states.

Claims

1. A system for use in a computer network to monitor and record outage status of a service provided on the network, wherein the system comprises:

a meta service generator operative on network inventory to define a service definition, each service definition including usergroup and point of presence;

a first module receiving element event data corresponding to changes in a state of elements associated with said defined service and creating element outage data indicating outage events associated with each of said elements;

a second module for receiving transaction data and determining transaction outages, and

a third module operative on output data from said first and second modules to determine sevice outages.

2. A system according to claim 1, wherein said first module includes an Event Stream Merger for receiving said element event data and creating a merged event stream containing said element event data in time sequence.

3. A system according to claim 1, wherein said first and second modules produce an element outage log and a transaction spec outage log, respectively, and further comprising a batch processing system operative on said logs for generating service outage reports.

4. A system according to claim 3, wherein said batch processing system includes an historical element outage generator, the historical element outage generator operating with said element outage logs and records of planned element outages to produce modified element outage data.

5. A system according to claim 4, wherein said batch processing system includes an historical service outage generator, the historical service outage generator operating with said modified element outage data and with said transaction spec outage logs to determine service outages.

6. A system according to claim 5, wherein said outage generator modifies service outage data in accordance with at least one of planned and forced outages to determine said service outages.

7. A system according to claim 1, wherein said meta service generator operates at a predefined period to define service objects for operation on a stream of element state data.

8. A system according to claim 1, further comprising a service outage reporting facility receiving data from said third module and presenting to a user an SLA based report.

9. In a network, a method for monitoring and recording outage status of a service provided on the network, said method comprising the steps of:

providing a meta service generator, said meta service generator periodically receiving a system inventory and operating thereon to determine service definitions;

providing a plurality of element event data streams, each indicating a change in status of a selected element associated with a service definition;

merging said element event streams into an output stream containing said event streams in time sequence and determining outage events of said selected elements from said merged output stream; and

using said outage events to create service reports.

10. A method according to claim 9, wherein a service definition includes usergroup and points of presence for selecting events relevant to the defined service.

11. A system for reporting service level and service outages on a network, wherein the system receives element outage logs and service outage logs, and produces a service outage output corrected for planned and/or forced outages so that the service outage output may better reflect at least one of

deficiencies under a contracted set of service levels, and

service outages actually experienced by users of the network.