Handling alarms based on user session records

• US 8,804,492 B2
• Filed: 08/28/2009
• Issued: 08/12/2014
• Est. Priority Date: 08/28/2009
• Status: Expired due to Fees

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Veres, Andras, Valko, Andras, Bertze, Asa
• Primary Examiner(s): Moore, Ian N
• Assistant Examiner(s): Smith, Eric P
• Application Number:
  US13/392,936
• Publication Number:
  US 20120163194A1
• Time in Patent Office: 1,810 Days
• Field of Search: None
• US Class Current: 370/218
• 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/0654 using network fault recovery ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 41/507 Filtering out customers affected by service problems
• CPC Class Codes: H04L 45/28 using route fault recovery

Abstract

A method is provided in a network management node for handling an alarm caused by a fault in a communications system. An alarm caused by a fault in the communications system is received from a first network element within the communications system. The alarm is associated with an identity of the first network element, and an alarm time associated with the time when the alarm was active. After receiving the alarm, the network management node sends a request to a user activity database, requesting one or more matching records. Each of the matching records is requested to comprise an identity equal to the identity of the first network element associated with the alarm, and a record time period that comprises the time when the alarm was active. The network management node receives one or more matching records from the user activity database, which one or more matching user session records identify the user sessions being affected by the alarm, and then handles the alarm based on the one or more matching user session records.

Claims

1. A method in a network management node for handling an alarm caused by an associated fault in a communications system, the communications system comprising the network management node, a plurality of network elements, and a policy repository accessible by the network management node, the method comprising:

receiving from a first network element within the communications system, the alarm caused by the associated fault in the communications system, the alarm including an identity of the first network element and an alarm time indicating when the alarm was active;

determining which users and sessions are being affected by the fault associated with the alarm by performing the following;

sending a request to a user activity database, wherein the user activity database comprises user session records and is accessible by the network management node, each user session record including a user identity, a record time period during which an associated user session took place, and an identity of each network element involved in the associated user session, the request requesting one or more matching records, where each of the matching records includes a network element identity equal to the identity of the first network element associated with the alarm, and a record time period for an associated user session that includes the alarm time indicating when the alarm was active; and

receiving one or more matching records from the user activity database, wherein the one or more matching user session records identify the users and user sessions being affected by the fault;

sending a request to the policy repository, requesting information about user policies associated with each user affected by the fault;

receiving the requested user policy information from the policy repository;

establishing a priority of the alarm; and

handling the alarm based on the one or more matching user session records and the user policy information associated with each user affected by the fault.

2. The method according to claim 1, wherein the network management node has access to an alarm impact database, the method further comprising:

storing in the alarm impact database, a record for the received alarm and the associated user session records.

3. The method according to claim 1, wherein each user session record of the user activity database is further associated with service information related to the user session in the user session record;

wherein sending the request to the policy repository also includes requesting information about service policies relating to the service information; and

wherein handling the alarm includes handling the alarm based on the one or more matching user session records, the user policies associated with each user affected by the fault, and the service policies relating to the service information about one or more services related to the user session associated with the matching record.

4. The method according to claim 1, wherein the step of handling the alarm comprises one or more of:

analyzing users or services that are affected by alarms; and

analyzing parts of the network where a plurality of users are affected by alarms.

5. The method according to claim 4, further comprising:

storing the established priority of the alarm in the alarm impact database, associated with the record for the received alarm.

6. The method according to claim 1, wherein each user session record also includes object identities relating to identification of the parts of a network element involved in the user session;

wherein the received alarm is further associated with an object identity relating to an identification of a part of the network element that issued the alarm; and

wherein sending the request to the user activity database includes requesting matching records that include an object identity equal to the object identity received in the alarm.

7. The method according to claim 1, wherein the received alarm is further associated with a traffic impact factor, wherein the traffic impact factor comprises an estimate of the ratio of connections or sessions impacted by the fault associated with the alarm;

and

wherein handling the alarm is further based on the traffic impact factor.

8. A network management node within a communications system having a plurality of network elements configured to serve users, and a policy repository accessible by the network management node, the network management node comprising:

a receiving unit that receives from a first network element within the communications system, an alarm caused by an associated fault in the communications system, the alarm including an identity of the first network element and an alarm time indicating when the alarm was active;

wherein the network management node is configured to determine which users and sessions are being affected by the fault associated with the alarm utilizing the following;

a requesting unit configured that sends a request to a user activity database, wherein the user activity database comprises user session records and is accessible by the network management node, each user session record including a user identity, a record time period during which an associated user session took place, and an identity of each network element involved in the associated user session, the request requesting one or more matching records, where each of the matching records includes a network element identity equal to the identity of the first network element associated with the alarm, and a record time period for an associated user session that includes the alarm time indicating when the alarm was active; and

a receiving unit that receives one or more matching user session records from the user activity database, wherein the one or more matching user session records identify the users and user sessions being affected by the fault;

wherein the network management node further;

sends a request to the policy repository, requesting information about user policies associated with each user affected by the fault;

receives the requested user policy information from the policy repository;

establishes a priority of the alarm; and

handles the alarm based on the one or more matching user session records and the user policy information associated with each user affected by the fault.

9. The network management node according to claim 8, wherein the network management node has access to an alarm impact database, and the network management node further comprises a storing unit that stores in the alarm impact database, a record for the received alarm and the associated user session records.

10. The network management node according to claim 8, wherein each user session record of the user activity database is further associated with service information related to the user session in the user session record;

and

wherein sending the request to the policy repository also includes requesting information about service policies relating to the service information; and

wherein handling the alarm includes handling the alarm based on the one or more matching user session records, the user policies associated with each user affected by the fault, and the service policies relating to the service information about one or more services related to the user session associated with the matching record.

11. The network management node according to claim 8, wherein the handling unit further handles the alarm by one or more of:

analyzing users or services that are affected by alarms; and

analyzing parts of the network where a plurality of users are affected by alarms.

12. The network management node according to claim 11, wherein the storing unit further stores the established priority of the alarm in the alarm impact database, associated with the record for the received alarm.

13. The network management node according to claim 8, wherein each user session record also includes object identities relating to identification of the parts of a network element involved in the user session;

and

wherein the received alarm is further associated with an object identity relating to an identification of a part of the network element that issued the alarm; and

wherein the requesting unit sends to the user activity database, a request for matching user session records that include an object identity equal to the object identity received in the alarm.

14. The network management node according to claim 8, wherein the received alarm is further associated with a traffic impact factor, wherein the traffic impact factor comprises an estimate of the ratio of connections or sessions impacted by the fault associated with the alarm;

and

wherein the handling unit further handles the alarm based on the traffic impact factor.