Method for determining a severity of a network incident

US9680722B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9680722-B2
Application numberUS-201113876041-A
CountryUS
Kind codeB2
Filing dateJul 21, 2011
Priority dateSep 30, 2010
Publication dateJun 13, 2017
Grant dateJun 13, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

The invention relates to a method for determining a severity of a network incident causing a network alarm in a communication network. The method comprises obtaining ( 201 ) a severity attribute associated with the network alarm, the severity attribute indicating an impact of the network incident on a communication service in the communication network, and relating ( 203 ) the severity attribute to a severity indicator from a predetermined set of severity indicators to determine the severity of the network incident.

First claim

Opening claim text (preview).

The invention claimed is: 1. A method, in a domain manager in a communication network, for determining a severity of a network incident causing a network alarm in the communication network, the method comprising: obtaining, in the domain manager, a severity attribute associated with the network alarm, the severity attribute indicating an impact of the network incident on a communication service in the communication network, wherein said obtaining the severity attribute comprises receiving the network alarm together with the severity attribute over the communication network; and relating, in the domain manager, the severity attribute to a severity indicator from a predetermined set of severity indicators to determine the severity of the network incident. 2. The method of claim 1 , wherein the severity attribute indicates at least one of: a number of subscribers affected by the network incident, a type of a subscriber affected by the network incident, a number of network cells affected by the network incident, a number of communication sites affected by the network incident, a communication service, in particular a voice service or a packet data service, affected by the network incident, a degradation of a communication service, in particular of a voice service or of a packet data service, due to the network incident, an importance of a communication service affected by the network incident, a type of a communication service affected by the network incident, a duration of a disturbance caused by the network incident, a duration of the network incident, a remaining time until an occurrence of a disturbance caused by the network incident, and a remaining number of redundant communication resources which are available until an occurrence of a disturbance caused by the network incident. 3. The method of claim 1 , wherein the predetermined set of severity indicators comprises at least one of the following severity indicators: major service outage, critical, major, minor, and non service affecting. 4. The method of claim 1 , wherein the network incident causes a number of correlated network alarms, the method further comprising: correlating a plurality of network alarms with respect to the network incident to determine the number of correlated network alarms; obtaining a number of severity attributes for the number of network alarms; and relating the number of severity attributes to at least one severity indicator from the predetermined set of severity indicators to determine the severity of the network incident. 5. The method of claim 4 , wherein relating the number of severity attributes to the at least one severity indicator comprises: accumulating the number of severity attributes and relating the accumulated number of severity attributes to the at least one severity indicator; or relating a maximum severity attribute among the number of the severity attributes to the at least one severity indicator. 6. A method, in a domain manager in a communication network, for determining a severity of a network incident causing a network alarm in a communication network, the method comprising: obtaining, in the domain manager, a severity attribute associated with the network alarm, the severity attribute indicating an impact of the network incident on a communication service in the communication network, wherein obtaining the severity attribute comprises receiving network information relating to an impact of the network alarm on the communication service, in particular a network alarm type, the network information enabling to determine the severity attribute, and determining the severity attribute upon the basis of the received network information; and relating, in the domain manager, the severity attribute to a severity indicator from a predetermined set of severity indicators to determine the severity of the network incident. 7. The method of claim 6 , wherein the severity attribute indicates at least one of: a number of subscribers affected by the network incident, a type of a subscriber affected by the network incident, a number of network cells affected by the network incident, a number of communication sites affected by the network incident, a communication service, in particular a voice service or a packet data service, affected by the network incident, a degradation of a communication service, in particular of a voice service or of a packet data service, due to the network incident, an importance of a communication service affected by the network incident, a type of a communication service affected by the network incident, a duration of a disturbance caused by the network incident, a duration of the network incident, a remaining time until an occurrence of a disturbance caused by the network incident, and a remaining number of redundant communication resources which are available until an occurrence of a disturbance caused by the network incident. 8. The method of claim 6 , wherein the predetermined set of severity indicators comprises at least one of the following severity indicators: major service outage, critical, major, minor, and non service affecting. 9. The method of claim 6 , wherein the network incident causes a number of correlated network alarms, the method further comprising: correlating a plurality of network alarms with respect to the network incident to determine the number of correlated network alarms; obtaining a number of severity attributes for the number of network alarms; and relating the number of severity attributes to at least one severity indicator from the predetermined set of severity indicators to determine the severity of the network incident. 10. The method of claim 9 , wherein relating the number of severity attributes to the at least one severity indicator comprises: accumulating the number of severity attributes and relating the accumulated number of severity attributes to the at least one severity indicator; or relating a maximum severity attribute among the number of the severity attributes to the at least one severity indicator. 11. A method, in a network node apparatus, for characterizing a network incident indicated by a network alarm in a communication network, the method comprising: obtaining, in the network node apparatus, network information relating to an impact of the network alarm on a communication service to characterize the network incident; and transmitting the network information over the communication network. 12. The method of claim 11 , wherein the network information indicates a network alarm type enabling the determining of a severity attribute, the severity attribute characterizing the network incident. 13. The method of claim 11 , wherein the network information is transmitted together with the network alarm towards a domain manager in the communication network. 14. The method of claim 11 , wherein the network incident causes a number of correlated network alarms, the method further comprising: correlating network alarms to determine the number of correlated network alarms; analyzing an impact of the network incident as indicated by the number of correlated network alarms on the communication service, to obtain a number of severity attributes; and associating the number of correlated network alarms with a severity indicator. 15. A domain manager apparatus configured to determine a severity of a network incident causing one or several network alarms in a communication network, the domain manager apparatus comprising: a receiver adapted to receive a network alarm and a severity attribut

Assignees

Inventors

Classifications

  • 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 title

  • H04L43/08Primary

    Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9680722B2 cover?
The invention relates to a method for determining a severity of a network incident causing a network alarm in a communication network. The method comprises obtaining ( 201 ) a severity attribute associated with the network alarm, the severity attribute indicating an impact of the network incident on a communication service in the communication network, and relating ( 203 ) the severity attribut…
Who is the assignee on this patent?
Zee Oscar, Nylander Tomas, Pelecanos Dimitrios, and 2 more
What technology area does this patent fall under?
Primary CPC classification H04L41/0631. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Jun 13 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).