Sign In to Follow Application
View All Documents & Correspondence

Service Impact Analysis And Root Cause Analysis For Services Traversing Multi Domain Networks

Abstract: The present subject matter relates to fault monitoring in multi-domain networks. In an example, alarm messages associated with multiple network entities in the multi-domain network are received. Upon receiving the alarm messages, state information of network entities traversed by services across the multi-domain network prior to receiving the alarm messages is acquired. The state information of the network entities for each of the services comprises hierarchical relationships between physical level entities, logical level entities, and service level entities traversed by a respective service. A network entity is identified from the acquired state information that matches with the faulty network entity corresponding to each of the alarm messages. Services that are impacted by the faulty network entity are determined based on traversing the state information of the network entities, through the hierarchical relationships, from the identified network entity to the service level entities.

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
08 September 2014
Publication Number
36/2016
Publication Type
INA
Invention Field
PHYSICS
Status
Email
Parent Application

Applicants

ALCATEL LUCENT
148/152 ROUTE DE LA REINE 92100 BOULOGNE-BILLANCOURT, FRANCE.

Inventors

1. DESAI, MAYANK
ALCATEL-LUCENT INDIA LIMITED NAGAWARA VILLAGE, KASABA TALUK OUTER RING ROAD, MANYATA EMBASSY BUSINESS PK 560045 BANGALORE, INDIA.
2. ANTONY, SAJI
ALCATEL-LUCENT INDIA LIMITED NAGAWARA VILLAGE, KASABA TALUK OUTER RING ROAD, MANYATA EMBASSY BUSINESS PK 560045 BANGALORE, INDIA.

Specification

DESC:FAULT MONITORING IN MULTI-DOMAIN NETWORKS ,CLAIMS:1. A method for monitoring faults in a multi-domain network, the method comprising:
receiving, by a processor (110), alarm messages associated with multiple network entities in the multi-domain network, wherein each of the alarm messages is indicative of a faulty network entity;
upon receiving the alarm messages, acquiring, by the processor (110), state information of network entities traversed by services across the multi-domain network prior to receiving the alarm messages, wherein the state information of the network entities for each of the services comprises hierarchical relationships between physical level entities, logical level entities, and service level entities traversed by a respective service;
identifying, by the processor(110), a network entity from the acquired state information that matches with the faulty network entity corresponding to each of the alarm messages; and
determining, by the processor (110), services that are impacted by the faulty network entity based on traversing the state information of the network entities, through the hierarchical relationships, from the identified network entity to the service level entities.
2. The method as claimed in claim 1, further comprising identifying, by the processor (110), an actual faulty network entity in the multi-domain network based on traversing the state information of the network entities, through the hierarchical relationships, from the service level entities associated with the determined services towards the physical level entities, wherein the state information is traversed till a network entity that matches with the faulty network entity corresponding to the each of the alarm messages is reached.
3. The method as claimed in claim 2, wherein the actual faulty network entity is the network entity at a lower most level based on the hierarchical relationships.
4. The method as claimed in claim 1, wherein the traversing the state information of the network entities comprises keeping a track of the network entities that are already traversed in the state information.
5. The method as claimed in claim 1, wherein the traversing the state information of the network entities comprises parsing the network entities that lead to the service level entities.
6. The method as claimed in claim 1, further comprises:
setting, by the processor (110), a flag with a status indicative of a non-traversing entity for a predefined set of network entities in the state information, wherein the traversing the state information of the network entities comprises parsing the network entities in the state information that are without the flag set with the status indicative of the non-traversing entity.
7. The method as claimed in claim 1, wherein the hierarchical relationships comprises:
relations between network equipment, physical terminations associated with the network equipment, links between the physical terminations, logical terminations corresponding to the physical terminations, paths between the logical terminations, and service types associated with the paths.
8. The method as claimed in claim 7, wherein the paths between the logical terminations comprises child paths and parent paths in a parent-child relationship, wherein each of the child paths is a direct path between two logical terminations, and wherein each of the parent paths is an aggregate path of at least two child paths.
9. A fault monitoring system (102) comprising:
a processor (110); and
a service impact analyzer (120) coupled to the processor (110) to:
receive alarm messages associated with multiple network entities in the multi-domain network, wherein each of the alarm messages is indicative of a faulty network entity;
acquire, upon receiving the alarm messages, state information of network entities traversed by services across the multi-domain network prior to receiving the alarm messages, wherein the state information of the network entities for each of the services comprises hierarchical relationships between physical level entities, logical level entities, and service level entities traversed by a respective service;
identify a network entity from the acquired state information that matches with the faulty network entity corresponding to each of the alarm messages,; and
determine services that are impacted by the faulty network entity based on traversing the state information of the network entities, through the hierarchical relationships, from the identified network entity to the service level entities.
10. The fault monitoring system (102) as claimed in claim 9, further comprising:
a root cause analyzer (122) coupled to the processor (110) to identify an actual faulty network entity in the multi-domain network based on traversing the state information of the network entities, through the hierarchical relationships, from the service level entities associated with the determined services towards the physical level entities, wherein the state information is traversed till a network entity that matches with the faulty network entity corresponding to the each of the alarm messages is reached.
11. The fault monitoring system (102) as claimed in claim 10, wherein the actual faulty network entity is the network entity at a lower most level based on the hierarchical relationships.
12. The fault monitoring system (102) as claimed in claim 9, wherein the service impact analyzer (120) is to keep a track of the network entities that are already traversed in the state information.
13. The fault monitoring system (102) as claimed in claim 9, wherein the service impact analyzer (120) is to:
set a flag with a status indicative of a non-traversing entity for a predefined set of network entities in the state information; and
parse the network entities in the state information that are without the flag set with the status indicative of the non-traversing entity.
14. A non-transitory computer-readable medium having embodied thereon a computer program for executing a method for monitoring faults in a multi-domain network, the method comprising:
receiving alarm messages associated with multiple network entities in the multi-domain network, wherein each of the alarm messages is indicative of a faulty network entity;
upon receiving the alarm messages, acquiring state information of network entities traversed by services across the multi-domain network prior to receiving the alarm messages, wherein the state information of the network entities for each of the services comprises hierarchical relationships between physical level entities, logical level entities, and service level entities traversed by a respective service;
identifying a network entity from the acquired state information that matches with the faulty network entity corresponding to each of the alarm messages; and
determining services that are impacted by the faulty network entity based on traversing the state information of the network entities, through the hierarchical relationships, from the identified network entity to the service level entities.
15. The non-transitory computer-readable medium as claimed in claim 14, wherein the method further comprises identifying an actual faulty network entity in the multi-domain network based on traversing the state information of the network entities, through the hierarchical relationships, from the service level entities associated with the determined services towards the physical level entities, wherein the state information is traversed till a network entity that matches with the faulty network entity corresponding to the each of the alarm messages is reached.

Documents

Application Documents

# Name Date
1 2554-del-2014-GPA.pdf 2014-11-14
1 REQUEST FOR CERTIFIED COPY [16-09-2015(online)].pdf 2015-09-16
2 2554-del-2014-Form-3.pdf 2014-11-14
2 Description(Complete) [01-09-2015(online)].pdf 2015-09-01
3 Drawing [01-09-2015(online)].pdf 2015-09-01
3 2554-del-2014-Form-2.pdf 2014-11-14
4 2554-del-2014-Form-1.pdf 2014-11-14
4 2554-DEL-2014-Correspondence-021214.pdf 2014-12-10
5 2554-del-2014-Correspondence Others.pdf 2014-11-14
5 2554-del-2014-Drawings.pdf 2014-11-14
6 2554-del-2014-Description (Provisional).pdf 2014-11-14
7 2554-del-2014-Correspondence Others.pdf 2014-11-14
7 2554-del-2014-Drawings.pdf 2014-11-14
8 2554-DEL-2014-Correspondence-021214.pdf 2014-12-10
8 2554-del-2014-Form-1.pdf 2014-11-14
9 2554-del-2014-Form-2.pdf 2014-11-14
9 Drawing [01-09-2015(online)].pdf 2015-09-01
10 Description(Complete) [01-09-2015(online)].pdf 2015-09-01
10 2554-del-2014-Form-3.pdf 2014-11-14
11 REQUEST FOR CERTIFIED COPY [16-09-2015(online)].pdf 2015-09-16
11 2554-del-2014-GPA.pdf 2014-11-14