# US 11,909,581 B2 · Cross-domain fault analysis method and system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,909,581 B2 - Document ID: US11909581B2 - Status: Granted - Kind: B2 - Application number: 18/319,883 - Filed: 2023-05-18 - Published: 2023-09-14 - Granted: 2024-02-20 - Earliest claimed: 2020-11-20 - Assignees: Huawei Technologies Co., Ltd. - Applicants: Huawei Technologies Co., Ltd. - Inventors: Qing Xie; Jiandong Ye - Web page: https://patentgrep.com/patent/US11909581B2 ## CPC - H04L 41/0677: Localisation of faults - 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 - H04L 41/065: {involving logical or physical relationship, e.g. grouping and hierarchies} - H04L 41/12: Discovery or management of network topologies - H04L 41/044: comprising hierarchical management structures - H04L 41/064: {involving time analysis} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract The present disclosure relates to cross-domain fault analysis methods and systems. According to the methods and the systems, whether a first single-domain network fault and a second single-domain network fault are caused by a same fault is determined based on correlation analysis on the first single-domain network fault and the second single-domain network fault in time dimension and service dimension. ## Claims ### Claim 1 A method, comprising: obtaining information about a first fault in a first network domain and information about a second fault in a second network domain, wherein the information about the first fault comprises a first time of the first fault and first service information of the first fault, and the information about the second fault comprises a second time of the second fault and second service information of the second fault; determining a time correlation based on the first time and the second time, wherein the time correlation is that the first time and the second time meet a time constraint condition; determining a service information correlation based on the first service information and the second service information, wherein the service information correlation is that the first service information and the second service information meet a service information constraint condition; and determining, based on the time correlation and the service information correlation, that the first fault in the first network domain and the second fault in the second network domain are caused by a same fault. ### Claim 2 (depends on 1) The method according to claim 1, wherein the method further comprises: determining cause information of the same fault based on the information about the first fault and the information about the second fault; and sending the cause information of the same fault to a third-party system through a northbound interface. ### Claim 3 (depends on 1) The method according to claim 1, wherein the time constraint condition is that an absolute value of a difference between the first time and the second time is less than a time threshold or that the first time and the second time are within a same time window. ### Claim 4 (depends on 1) The method according to claim 1, wherein: the first time comprises at least one of a time at which the first fault occurs, a time at which the information about the first fault is generated, a time at which the information about the first fault is sent, or a time at which the information about the first fault is received; and the second time comprises at least one of a time at which the second fault occurs, a time at which the information about the second fault is generated, a time at which the information about the second fault is sent, or a time at which the information about the second fault is received. ### Claim 5 (depends on 1) The method according to claim 1, wherein: the first service information comprises at least one of service type information of the first fault, network topology information of the first network domain in which the first fault occurs, information about a network device in which the first fault occurs, or information about a service procedure in which the first fault occurs; and the second service information comprises at least one of service type information of the second fault, the network topology information of the first network domain in which the second fault occurs, information about a network device in which the second fault occurs, or information about a service procedure in which the second fault occurs. ### Claim 6 (depends on 1) The method according to claim 1, wherein the service information constraint condition is: that service type information of the first service information and service type information of the second service information belong to a same service type or correlated service types; that network topology information of the first service information and network topology information of the second service information are network topology information of a same network topology; or that service procedure information of the first service information and service procedure information of the second service information belong to a same service procedure or belong to a fault causality. ### Claim 7 (depends on 1) The method according to claim 1, wherein obtaining the information about the first fault in the first network domain and the information about the second fault in the second network domain comprises: receiving the information about the first fault from a fault analysis system of the first network domain; and receiving the information about the second fault from a fault analysis system of the second network domain. ### Claim 8 (depends on 1) The method according to claim 1, wherein obtaining the information about the first fault in the first network domain and the information about the second fault in the second network domain comprises: receiving, from a fault analysis system of the first network domain, first basic information for generating the information about the first fault; receiving, from a fault analysis system of the second network domain, second basic information for generating the information about the second fault; generating the information about the first fault based on the first basic information; and generating the information about the second fault based on the second basic information. ### Claim 9 (depends on 1) The method according to claim 1, wherein the method is executed by a cross-domain fault analysis system. ### Claim 10 An apparatus, wherein the apparatus comprises: at least one processor; and at least one non-transitory computer-readable storage medium storing programming instructions for execution by the at least one processor to: obtain information about a first fault in a first network domain and information about a second fault in a second network domain, wherein the information about the first fault comprises a first time of the first fault and first service information of the first fault, and the information about the second fault comprises a second time of the second fault and second service information of the second fault; determine a time correlation based on the first time and the second time, wherein the time correlation is that the first time and the second time meet a time constraint condition; determine a service information correlation based on the first service information and the second service information, wherein the service information correlation is that the first service information and the second service information meet a service information constraint condition; and determine, based on the time correlation and the service information correlation, that the first fault in the first network domain and the second fault in the second network domain are caused by a same fault. ### Claim 11 (depends on 10) The apparatus according to claim 10, wherein the programming instructions are for execution by the at least one processor to: determine cause information of the same fault based on the information about the first fault and the information about the second fault; and send the cause information of the same fault to a third-party system through a northbound interface. ### Claim 12 (depends on 10) The apparatus according to claim 10, wherein the time constraint condition is that an absolute value of a difference between the first time and the second time is less than a time threshold or an absolute value of a difference between the first time and the second time is less than a time threshold or that the first time and the second time are within a same time window. ### Claim 13 (depends on 10) The apparatus according to claim 10, wherein: the first time comprises at least one of a time at which the first fault occurs, a time at which the information about the first fault is generated, a time at which the information about the first fault is sent, or a time at which the information about the first fault is received; and the second time comprises at least one of a time at which the second fault occurs, a time at which the information about the second fault is generated, a time at which the information about the second fault is sent, or a time at which the information about the second fault is received. ### Claim 14 (depends on 10) The apparatus according to claim 10, wherein: the first service information comprises at least one of service type information of the first fault, network topology information of the first network domain in which the first fault occurs, information about a network device in which the first fault occurs, or information about a service procedure in which the first fault occurs; and the second service information comprises at least one of service type information of the second fault, the network topology information of the first network domain in which the second fault occurs, information about a network device in which the second fault occurs, or information about a service procedure in which the second fault occurs. ### Claim 15 (depends on 10) The apparatus according to claim 10, wherein the service information constraint condition is: that service type information of the first service information and service type information of the second service information belong to a same service type or correlated service types; that network topology information of the first service information and network topology information of the second service information are network topology information of a same network topology; or that service procedure information of the first service information and service procedure information of the second service information belong to a same service procedure or belong to a fault causality. ### Claim 16 (depends on 10) The apparatus according to claim 10, wherein the programming instructions are for execution by the at least one processor to: receive the information about the first fault from a fault analysis system of the first network domain; and receive the information about the second fault from a fault analysis system of the second network domain. ### Claim 17 (depends on 10) The apparatus according to claim 10, wherein the programming instructions are for execution by the at least one processor to: receive, from a fault analysis system of the first network domain, first basic information for generating the information about the first fault; receive, from a fault analysis system of the second network domain, second basic information for generating the information about the second fault; generate the information about the first fault based on the first basic information; and generate the information about the second fault based on the second basic information. ### Claim 18 A non-transitory storage medium storing a program which, when executed by one or more processors, cause the one or more processors to perform operations, the operations comprising: obtaining information about a first fault in a first network domain and information about a second fault in a second network domain, wherein the information about the first fault comprises a first time of the first fault and first service information of the first fault, and the information about the second fault comprises a second time of the second fault and second service information of the second fault; determining a time correlation based on the first time and the second time, wherein the time correlation is that the first time and the second time meet a time constraint condition; determining a service information correlation based on the first service information and the second service information, wherein the service information correlation is that the first service information and the second service information meet a service information constraint condition; and determining, based on the time correlation and the service information correlation, that the first fault in the first network domain and the second fault in the second network domain are caused by a same fault. ### Claim 19 (depends on 18) The non-transitory storage medium according to claim 18, wherein the operations further comprise: determining cause information of the same fault based on the information about the first fault and the information about the second fault; and sending the cause information of the same fault to a third-party system through a northbound interface. ### Claim 20 (depends on 18) The non-transitory storage medium according to claim 18, wherein the time constraint condition is that an absolute value of a difference between the first time and the second time is less than a time threshold or that the first time and the second time are within a same time window.