A fault processing method, device and system

Abstract

The application provides a fault processing method, device and system, wherein the method comprises: a domain management device obtaining first fault information of a first network fault; the domain management device determining first fault delimitation information of the first network fault according to the first fault information, the first fault delimitation information indicating a range of the first network fault; and the domain management device processing the first network fault according to the first fault delimitation information. Through the above method, the range of the first network fault can be determined by determining the first fault delimitation information, so that the domain fault, the out-of-domain fault or the unknown fault can be distinguished, and then it is determined whether the fault is processed by the domain management device or the cross-domain management device, the cooperation of hierarchical and domain fault processing is realized, and the fault processing efficiency is improved.

Description

[0001] This application claims priority to the Chinese Patent Application No. 202010437486.0, filed on May 21, 2020, in the China Patent Office, entitled "A Fault Processing Method, Device and System", the entire contents of which are incorporated by reference in its entirety in the present application. The present application is related to the Chinese Patent Application No. 202010437486.0, filed on May 21, 2020, in the China Patent Office, entitled "A Fault Processing Method, Device and System", the entire contents of which are incorporated by reference in its entirety in the present application. The present application is related to the Chinese Patent Application No. 202010437486.0, filed on May 21, 2020, in the China Patent Office, entitled "A Fault Processing Method, Device and System", the entire contents of which are incorporated by reference in its entirety in the present application. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, in particular to a fault processing method, device and system. BACKGROUND

[0003] The operator network has developed to the 5th generation (5G), and the network architecture becomes more flexible. The demand for key performance indicators such as latency, rate, and connection scale of the network is increasing, and the application industry is becoming more and more rich and diverse. The performance guarantee and flexibility of the service have fundamentally changed, resulting in an increase in network operation and maintenance difficulty.

[0004] Network failure will directly affect the performance of the service, and even cause service interruption. How to quickly detect and eliminate the fault is one of the main challenges of operation and maintenance. In the prior art, the network element, the domain management device, and the cross-domain management device will perform cause analysis and fault repair functions on the collected faults / alarm. How to coordinate the fault processing capabilities of the network element, the domain management device, and the cross-domain management function to improve the overall network fault processing efficiency is a problem to be solved. SUMMARY

[0005] The embodiments of the present application provide a fault processing method, device and system to solve the problem of how to improve the fault processing efficiency of the network.

[0006] In a first aspect, the present application provides a method, comprising: a domain management device obtaining first fault information of a first network fault; the domain management device determining first fault delimitation information of the first network fault according to the first fault information; the first fault delimitation information indicating the range of the first network fault, and the first fault delimitation information being intra-domain or inter-domain or unknown domain; and the domain management device processing the first network fault according to the first fault delimitation information.

[0007] In the above process, by determining the first fault delimitation information of the first network fault, the range of the first network fault can be determined, and the intra-domain fault, the inter-domain fault or the unknown fault can be distinguished. Then it is determined whether the fault is processed by the domain management device or the cross-domain management device, the cooperation of hierarchical and domain fault processing is realized, and the fault processing efficiency is improved.

[0008] In a possible design, the domain management device determines first fault delimitation information of the first network fault according to the first fault information, including: the domain management device determines an abnormal network element corresponding to the first network fault according to the first fault information; and the domain management device determines the first fault delimitation information of the first network fault according to the abnormal network element.

[0009] In a possible design, the first fault information includes a fault type, and the domain management device determines an abnormal network element corresponding to the first network fault according to the first fault information, including: if the domain management device determines, according to the fault type in the first fault information, that the first network fault is caused by an abnormality of a local network element, the domain management device determines the local network element as the abnormal network element; or if the domain management device determines, according to the fault type in the first fault information, that the first network fault is caused by an abnormality of a peer network element of the local network element, the domain management device determines the peer network element as the abnormal network element; wherein the local network element is a network element that sends the first fault information to the domain management device.

[0010] In a possible design, the domain management device determines first fault delimitation information of the first network fault according to the abnormal network element, including: when the abnormal network element is a network element managed by the domain management device, the first fault delimitation information indicates that the range of the first network fault is within a domain; and when the abnormal network element is not a network element managed by the domain management device, the first fault delimitation information indicates that the range of the first network fault is outside the domain.

[0011] In a possible design, the first fault information includes a fault type, and the domain management device determines first fault delimitation information of the first network fault according to the first fault information, including: the domain management device determines the first fault delimitation information according to a fault delimitation rule and the fault type; and the fault delimitation rule includes an association relationship between a fault type and first fault delimitation information.

[0012] In a possible design, the method further includes: the domain management device acquires configuration information and performance information of the first network fault associated object; and the domain management device determines first fault delimitation information of the first network fault according to the first fault information, including: the domain management device determines the first fault delimitation information of the first network fault according to the first fault information of the first network fault, the configuration information and the performance information of the first network fault associated object.

[0013] In a possible design, the method further includes: the domain management device obtaining at least one second fault information, one second fault information in the at least one second fault information corresponding to a second network fault; and the domain management device determining first fault delimitation information of the first network fault according to the first fault information, including: the domain management device determining the first fault delimitation information of the first network fault according to the first fault information of the first network fault and the at least one second fault information.

[0014] In a possible design, the domain management device processes the first network fault according to the first fault delimitation information, including: when the first fault delimitation information indicates that the range of the first network fault is within the domain, the domain management device performs root cause analysis or fault recovery processing on the first network fault; or when the first fault delimitation information indicates that the range of the first network fault is outside the domain or unknown domain, the domain management device sends the first fault delimitation information to a cross-domain management device.

[0015] In a possible design, the domain management device processes the first network fault according to the first fault delimitation information, including: the domain management device sends the first fault delimitation information to a cross-domain management device, instructing the cross-domain management device to process the first network fault according to the first fault delimitation information.

[0016] In a possible design, the domain includes at least one of an access network domain, a core network domain, a transmission domain, a data center domain, and a virtual resource domain.

[0017] In a second aspect, the present application also provides a communication apparatus, which implements any method provided in the first aspect. The communication apparatus can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0018] In a possible implementation, the communication apparatus includes a processor configured to support the communication apparatus to perform the corresponding functions of the network device in the above method. The communication apparatus can further include a memory coupled to the processor, which stores program instructions and data necessary for the communication apparatus. Optionally, the communication apparatus further includes an interface circuit for supporting communication between the communication apparatus and devices such as network devices.

[0019] In a possible implementation, the communication apparatus includes corresponding functional units respectively for implementing the steps in the above method. The functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

[0020] In a possible implementation, the communication apparatus includes a processing unit and a communication unit in its structure, which can perform the corresponding functions in the above method examples, and details are described in the method provided in the first aspect, which will not be repeated here.

[0021] In a third aspect, the present application provides a communication method, comprising: a cross-domain management device acquiring at least one of first fault information and first fault delimitation information of a first network fault, wherein the first fault delimitation information is within a domain or outside a domain or unknown domain; the cross-domain management device determining second fault delimitation information of the first network fault according to the first fault information or the first fault delimitation information; the second fault delimitation information indicates whether the first network fault is within a range of the cross-domain management device, and the second fault delimitation information is cross-domain and single-domain; or the second fault delimitation information indicates that the first network fault is within a range of a first domain management device, and the second fault delimitation information is domain management device indication information; and the cross-domain management device processing the first network fault according to the second fault delimitation information.

[0022] In the above process, by determining the second fault delimitation information of the first network fault, it is distinguished whether it is a cross-domain fault or a single-domain fault, and then the device processing the first network fault is determined, thereby improving the fault processing efficiency.

[0023] In a possible design, the cross-domain management device determines the second fault delimitation information of the first network fault according to the first fault delimitation information, comprising: when the first fault delimitation information is within a domain, the cross-domain management device determines that the second fault delimitation information indicates that the range of the first network fault is single-domain; or when the first fault delimitation information is outside a domain or unknown domain, and there is an associated third network fault of the first network fault, and the fault delimitation information of the third network fault is within a domain, the cross-domain management device determines that the second fault delimitation information indicates that the range of the first network fault is single-domain; or when the first fault delimitation information is outside a domain or unknown domain, and there is an associated third network fault of the first network fault, and the fault delimitation information of the third network fault is outside a domain, the cross-domain management device determines that the second fault delimitation information indicates that the range of the first network fault is cross-domain.

[0024] In a possible design, the method further comprises: when the cross-domain management device determines that the second fault delimitation information is cross-domain, the cross-domain management device indicates to a first domain management device that the second fault delimitation information is cross-domain, or the cross-domain management device instructs the first domain management device to delete the first network fault, wherein the first domain management device is a device sending the first fault information or the first fault delimitation information.

[0025] In a possible design, the first fault information includes a fault type, and the cross-domain management device determines second fault delimitation information of the first network fault according to the first fault information, including: the cross-domain management device determines the second fault delimitation information according to a fault delimitation rule and the fault type; and the fault delimitation rule includes an association between a fault type and second fault delimitation information.

[0026] In a possible design, the cross-domain management device processes the first network fault according to the second fault delimitation information, including: when the second fault delimitation information is cross-domain, the cross-domain management device performs root cause analysis or fault recovery processing on the first network fault; or when the second fault delimitation information is single-domain, the cross-domain management device determines a domain management device that causes the first network fault according to the first fault information, and instructs the domain management device to process the first network fault.

[0027] In a possible design, the single-domain includes at least one of an access network domain, a core network domain, a transmission domain, a data center domain, and a virtual resource domain.

[0028] In a fourth aspect, the present application also provides a communication apparatus, which has any of the methods provided in the third aspect. The communication apparatus can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0029] In a possible implementation, the communication apparatus includes a processor configured to support the communication apparatus to perform the corresponding functions of the terminal device in the above method. The communication apparatus can also include a memory coupled to the processor, which stores the necessary program instructions and data of the communication apparatus. Optionally, the communication apparatus also includes an interface circuit for supporting the communication between the communication apparatus and devices such as network devices.

[0030] In a possible implementation, the communication apparatus includes corresponding functional units for implementing the steps in the above method. The functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

[0031] In a possible implementation, the structure of the communication apparatus includes processing units and communication units, which can perform the corresponding functions in the above method examples, and specific descriptions can be referred to the method provided in the third aspect, which will not be repeated here.

[0032] In a fifth aspect, a system is provided, comprising: a domain management device configured to acquire first fault information of a first network fault; determine first fault delimitation information of the first network fault according to the first fault information; the first fault delimitation information indicates a range of the first network fault, and the first fault delimitation information is intra-domain or inter-domain or unknown domain; when it is determined that the first fault delimitation information is inter-domain or unknown domain, send at least one of the first fault information and the first fault delimitation information to a cross-domain management device; and the cross-domain management device configured to acquire at least one of the first fault information and the first fault delimitation information of the first network fault, the first fault delimitation information is intra-domain or inter-domain or unknown domain; determine second fault delimitation information of the first network fault according to the first fault information or the first fault delimitation information; the second fault delimitation information indicates whether the first network fault is within a range of the cross-domain management device, and the second fault delimitation information is cross-domain or single-domain; or the second fault delimitation information indicates that the first network fault is within a range of the domain management device, and the second fault delimitation information is domain management device indication information; and process the first network fault according to the second fault delimitation information.

[0033] In a possible design, the domain management device is specifically configured to: when the first fault delimitation information indicates that the range of the first network fault is intra-domain, perform root cause analysis or fault recovery processing on the first network fault; or when the first fault delimitation information indicates that the range of the first network fault is inter-domain or unknown domain, send the first fault delimitation information to the cross-domain management device.

[0034] In a possible design, the cross-domain management device is specifically configured to: when the second fault delimitation information is cross-domain, perform root cause analysis or fault recovery processing on the first network fault; or when the second fault delimitation information is single-domain, determine a domain management device that causes the first network fault according to the first fault information, and instruct the domain management device to process the first network fault.

[0035] In a sixth aspect, a communication apparatus is provided, which can be a network device in the method embodiments, or a chip disposed in the network device. The communication apparatus includes an interface circuit and a processor, and optionally, a memory. The memory is configured to store a computer program or instructions, and the processor is coupled with the memory and the interface circuit. When the processor executes the computer program or instructions, the communication apparatus performs the method performed by the domain management device or the cross-domain management device in the method embodiments.

[0036] In a seventh aspect, a computer program product is provided, which includes computer program codes, when the computer program codes are run, the method performed by the domain management device in the above aspects is executed.

[0037] In an eighth aspect, a computer program product is provided, which includes computer program codes, when the computer program codes are run, the method performed by the cross-domain management device in the above aspects is executed.

[0038] In a ninth aspect, the present application provides a chip system, which includes a processor for implementing the function of the domain management device in the method of the above aspects. In a possible design, the chip system further includes a memory for storing program instructions and / or data. The chip system can be composed of a chip, or include a chip and other discrete devices.

[0039] In a tenth aspect, the present application provides a chip system, which includes a processor for implementing the function of the cross-domain management device in the method of the above aspects. In a possible design, the chip system further includes a memory for storing program instructions and / or data. The chip system can be composed of a chip, or include a chip and other discrete devices.

[0040] In an eleventh aspect, the present application provides a computer readable storage medium, which stores a computer program, when the computer program is run, the method performed by the domain management device in the above aspects is implemented.

[0041] In a twelfth aspect, the present application provides a computer readable storage medium, which stores a computer program, when the computer program is run, the method performed by the cross-domain management device in the above aspects is implemented. BRIEF DESCRIPTION OF DRAWINGS

[0042] Figure 1 A system architecture diagram suitable for the embodiments of the present application;

[0043] Figure 2 A fault processing method flowchart provided by the embodiments of the present application;

[0044] Figure 3 A fault processing flowchart provided by the embodiments of the present application;

[0045] Figure 4 A fault processing method flowchart provided by the embodiments of the present application;

[0046] Figure 5 A fault judgment diagram provided by the embodiments of the present application;

[0047] Figure 6 A system architecture diagram is provided for an embodiment of the present application.

[0048] Figure 7 A device structure diagram is provided for an embodiment of the present application.

[0049] Figure 8 A device structure diagram is provided for an embodiment of the present application. DETAILED DESCRIPTION

[0050] The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0051] The embodiments of the present application can be applied to various mobile communication systems, for example, a new radio (NR) system, a long term evolution (LTE) system, an advanced long term evolution (LTE-A) system, a future communication system, and other communication systems, without limitation.

[0052] To facilitate understanding of the embodiments of the present application, first, a system shown in FIG. 1 is taken as an example for detailed description. Figure 1 Figure 1 A system architecture diagram suitable for the method provided by the embodiments of the present application is shown. As shown in FIG. 2, the system includes a business support system (BSS), a cross domain management function (CD-MnF) unit, a domain management function (Domain-MnF) unit, and a plurality of network elements, etc. Figure 1

[0053] The BSS is oriented to operator business and service, and provides functions and services such as charging, settlement, accounting, customer service, business, network monitoring, etc. The BSS also includes a work order system, which is used for order processing according to fault information, and then a fault handling personnel.

[0054] ​​The cross-domain management function unit, which can be referred to as a network management function (NMF) unit, can also be a network slice management function (NSMF) unit or a cross-domain management data analysis function (MDAF) unit or a cross-domain self-organization network function (SON Function) unit or a cross-domain intent management function unit, etc. For the convenience of description, the following is referred to as a cross-domain management function unit. The cross-domain management function unit can provide one or more of the following management functions or management services:

[0055] Network lifecycle management; network deployment; network fault management, including but not limited to fault collection, fault identification, root cause analysis, and fault handling, etc.; network performance management; network configuration management; network assurance; network optimization function; network intent translation, etc.

[0056] Wherein, the network fault includes the fault of all components of the network, such as the fault of sub-network, network element, network function, cell, single board and chip, etc. The network involved in the embodiments of the present application can refer to one or more network elements or sub-networks. The "intent" here can refer to the intent of the communication service provider (Intent From Communication Service Provider, Intent-CSP) or the intent of the communication service consumer (Intent From Communication Service Consumer, Intent-CSC).

[0057] It should be noted that the cross-domain management function unit can also provide the following one management or service for the sub-network:

[0058] Network lifecycle management; network deployment; network fault management, including but not limited to fault collection, fault identification, root cause analysis, and fault handling, etc., the fault of the sub-network includes the fault of all components of the sub-network, such as the fault of sub-network, network element, network function, cell, single board and chip, etc.; sub-network performance management; sub-network configuration management; sub-network assurance; sub-network optimization function; sub-network intent translation, etc. The sub-network here can refer to a large sub-network composed of multiple small sub-networks

[0059] Domain management function unit, also called sub-network management function unit or network element management function unit, is called domain management function unit hereinafter. The domain management function unit can provide one or more of the following management functions or services: life cycle management of sub-network or network element; deployment of sub-network or network element; fault management of sub-network or network element, including but not limited to fault collection, fault identification, root cause analysis and fault handling, etc., wherein the fault of sub-network includes the fault of all components of the sub-network, such as the fault of sub-network, network element, network function, cell board, chip, etc.; the fault of network element includes the fault of all components of the network element, such as the fault of network function, cell board, chip, etc.; performance management of sub-network or network element; assurance of sub-network or network element; optimization function of sub-network or network element; intent translation of sub-network or network element, etc.

[0060] Herein, the sub-network includes one or more network elements. The sub-network can also include sub-network, i.e., one or more sub-networks form a larger sub-network.

[0061] The domain management function unit can be deployed in the following manner, but not limited to the following:

[0062] 1. Classification according to network type: Radio Access Network (RAN) domain management function unit, Core Domain Management Function, Transport Domain Management Function; or a certain domain network management system can manage two or all of the access network, core network and transport network.

[0063] 2. Classification according to administrative region: domain management function unit of a certain region, such as Shanghai domain management function unit, Beijing domain management function unit, etc.

[0064] In the embodiments of the present application, the network element is an entity providing network service, including core network element and access network element, etc.

[0065] The core network element includes, but is not limited to, an access and mobility management function (AMF) network element, a session management function (SMF) network element, a policy control function (PCF) network element, a network data analysis function (NWDAF) network element, a network repository function (NRF) network element, a gateway, and the like. The access network element includes, but is not limited to, various types of wireless access devices, for example, a next generation node B (gNB) in an NR system, an evolved node B (eNB), a radio network controller (RNC), or a node B (NB), and can be a gNB or a transmission point (TRP or TP) in a 5G (NR) system, one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a baseband device (BBU), or a DU in a central unit-distributed (CU-DU) architecture, and the like.

[0066] The network element can also provide one or more of the following management functions or management services: lifecycle management of the network element, deployment of the network element, fault management of the network element, performance management of the network element, assurance of the network element, optimization function of the network element, intent translation of the network element, and the like. The fault management of the network element includes, but is not limited to, fault collection, fault identification, root cause analysis, and fault handling, and the like, and the fault of the network element includes faults of all components of the network element, such as faults of sub-networks, network elements, network functions, single boards, chips, and the like.

[0067] It should be understood that the service-based management architecture focuses on the provider and the invoker of the management service, as follows:

[0068] When the management service is the management service provided by the cross-domain management unit, the cross-domain management unit is the management service producer (MnS producer), and the BSS is the management service invoker (MnS consumer).

[0069] When the management service is a management service provided by the above domain management unit, the domain management unit is a management service provider, and the cross-domain management unit is a management service invoker.

[0070] When the management service is a management service provided by the above network element, the network element is a management service provider, and the domain management unit is a management service invoker.

[0071] In addition, in the embodiments of the present application, the word "example" is used to mean by way of example, illustration, or description. Any embodiment or design solution described in the present application as "example" should not be interpreted as being more preferred or having more advantages than other embodiments or design solutions. Rather, the word "example" is used as a specific manner to present the concept.

[0072] The network architecture and service scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation to the technical solutions provided by the embodiments of the present application. It can be known by those skilled in the art that, with the evolution of network architecture and the appearance of new service scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0073] Embodiment one:

[0074] Referring to Figure 2 , a flowchart of a fault processing method provided by the embodiments of the present application is shown.

[0075] Figure 2 In the embodiments of the present application, the domain management device can refer to Figure 1 the domain management function unit in the domain management device. Of course Figure 1 the cross-domain management function unit in the domain management device can also execute Figure 2 the flow shown in the figure.

[0076] Step 201: The domain management device acquires first fault information of a first network fault.

[0077] Step 202: The domain management device determines first fault delimitation information of the first network fault according to the first fault information.

[0078] The first fault delimitation information indicates the range of the first network fault.

[0079] Step 203: The domain management device processes the first network fault according to the first fault delimitation information.

[0080] In the above flow, by determining the first fault delimitation information of the first network fault, the range of the first network fault can be determined, and the first network fault can be further processed according to the range of the first network fault, so that the fault processing efficiency can be improved.

[0081] In the first embodiment, the first fault delimitation information can be in-domain or out-of-domain or unknown domain, which is determined according to actual conditions. The in-domain includes at least one of an access network domain, a core network domain, a transmission domain, a data center domain and a virtual resource domain. For example, the access network domain describes a wireless access network provided by one or more wireless access network devices (e.g., a base station); the core network domain describes a core network provided by one or more core network devices (e.g., a mobility management entity (MME) or an access and mobility management function (AMF)); the transmission network domain describes a transmission network provided by one or more transmission devices (e.g., an optical device); the data center domain describes an internet protocol (IP) network provided by one or more data centers; and the virtual resource domain describes a virtual network provided by one or more virtual resources (e.g., a virtual machine).

[0082] When the first fault delimitation information is in-domain, it indicates that the first network fault is caused by an abnormality of an object or a network element managed by the domain management device; when the first fault delimitation information is out-of-domain, it indicates that the first network fault is not caused by an abnormality of an object or a network element managed by the domain management device; and when the first fault delimitation information is unknown domain, it indicates that it is uncertain whether the first network fault is caused by an abnormality of an object or a network element managed by the domain management device.

[0083] Optionally, when the range of the first network fault is in-domain, it can be further divided into an in-domain network element fault and an in-domain cross-network element fault; the in-domain network element fault indicates a fault caused by an abnormality of an object in a network element, and the in-domain cross-network element fault indicates a fault caused by an abnormality of an object between different network elements in the domain.

[0084] In combination with Figure 1 It can be known that when the domain management device is a domain management function unit, the domain management device manages a plurality of network elements.

[0085] In step 201, the first fault information obtained by the domain management device can include but is not limited to one or more of the following:

[0086] A fault identifier; a fault type; a fault generating network element, indicating a network element where a fault occurs; a fault root cause; a time when a fault occurs; a network element related to the fault; and a fault level.

[0087] The above is only an example, and the first fault information can further include other contents, which will not be illustrated one by one here.

[0088] In the embodiments of the present application, the domain management device can obtain the first fault information in multiple ways.

[0089] In a possible implementation, the device generating the first fault information can actively report the first fault information to the domain management device.

[0090] For example, when the domain management device is a domain management function unit, the network element managed by the domain management device reports the first fault information to the domain management device. It should be noted that in actual application, the domain management device can receive multiple fault information reported by multiple network elements.

[0091] Alternatively, the domain management device can also actively request the first fault management information from the network element managed thereby. For example, the domain management device can periodically send a request message, the request message being used to request fault information, and the network element managed by the domain management device can thus report the fault information to the domain management device.

[0092] The above is only an example, and other cases will not be described herein.

[0093] In another possible implementation, the domain management device can collect at least one network alarm information, determine the first network fault corresponding to the at least one network alarm information, and obtain the first fault information of the first network fault.

[0094] It should be noted that the domain management device can include a pre-set network fault template, and the network fault template includes network alarm information corresponding to a network fault. The domain management device can determine the network fault corresponding to the at least one network alarm information in the pre-set network fault template as the first network fault.

[0095] Since different types of alarm information frequently appear in the existing network, these alarm information can be caused by a network fault, and therefore a network fault template can be pre-set, so as to quickly locate the network fault. For example, the network fault template can be as shown in Table 1.

[0096] Table 1

[0097]

[0098] Table 1 is only an example, and other network fault templates can also exist, which will not be described herein.

[0099] In step 202, the domain management device can determine the first fault delimitation information in multiple ways, which will be described in detail below.

[0100] In a first possible implementation, the domain management device can determine the first fault delimitation information according to at least one of the fault type in the first fault delimitation information and the fault generating network element.

[0101] For example, if according to the fault type of the first network fault, it is determined that the first network fault is caused by a fault of a network element or an abnormality of a component in the fault network element, the first network fault can be determined as an in-domain fault, i.e., the first fault delimiting information is determined as in-domain. For example, when the fault type of the first network fault is any of the following, the first network fault can be determined as an in-domain fault: a radio frequency unit standing wave fault; a radio frequency unit software running abnormality fault; a battery fault; a single board clock input abnormality fault; a configuration file damage fault, and the like.

[0102] For another example, the domain management device can determine an abnormal network element according to the fault type in the first fault delimiting information, so as to determine the first fault delimiting information according to the abnormal network element.

[0103] How the domain management device determines the abnormal network element is not limited. For example, if the domain management device determines, according to the fault type in the first fault information, that the first network fault is caused by an abnormality of a local network element, the local network element is determined as the abnormal network element; if the domain management device determines, according to the fault type in the first fault information, that the first network fault is caused by an abnormality of a peer network element of the local network element, the peer network element is determined as the abnormal network element; wherein the local network element is a network element that sends the first fault information to the domain management device, and the peer network element can be a network element that has a physical connection or data interaction with the local network element. The local network element and the peer network element are relative concepts, not absolute concepts.

[0104] When the abnormal network element is determined as a network element managed by the domain management device, the first fault delimiting information can be determined as in-domain, i.e., the first network fault is an in-domain fault; when the abnormal network element is determined as not a network element managed by the domain management device, the first fault delimiting information can be determined as out-of-domain, i.e., the first network fault is an out-of-domain fault.

[0105] Further, some network faults are caused by an abnormality of a peer network element of a fault network element, if the peer network element is an in-domain network element, the first network fault can be determined as an in-domain fault or an in-domain cross-network element fault. For example, the following are several possible faults of this type: a peer certificate expiration fault, a base station control plane transmission interruption alarm fault, and the like.

[0106] The above are only examples, and other cases can also exist, which are not illustrated one by one here.

[0107] In a second possible implementation, the domain management device can determine the first fault delimiting information according to a fault delimiting rule.

[0108] The fault delimiting rule can include an associated relationship between a fault type and first fault delimiting information, and the domain management device can determine the first fault delimiting information associated with the fault type of the first network fault in the fault delimiting rule as the first fault delimiting information.

[0109] For example, the fault delimiting rule includes the following associated relationship: radio frequency unit software running abnormal fault, associated fault in the domain. Then, when the first network fault is a radio frequency unit software running abnormal fault, the first fault delimiting information can be determined as in-domain.

[0110] Optionally, the fault delimiting rule can also include an associated relationship between a network fault and a first fault delimiting information judgment process.

[0111] Some network faults can be caused by abnormality of a local network element, or caused by abnormality of a peer network element, or caused by other reasons, and some network faults can exist in an associated first fault delimiting information judgment process, so that the first fault delimiting information of the network fault can be determined according to the first fault delimiting information judgment process.

[0112] For example, the Xn interface is an interface between access network network elements, and when the network fault is an Xn interface fault, the causes of the Xn interface fault include the following possibilities:

[0113] 1. Xn interface configuration error, that is, the EP_Xn object configuration information contained in the local base station object or the peer base station object is incorrect, for example, the local Internet Protocol (IP) address, Virtual Local Area Network (VLAN) identifier, Remote IP address, and the like are incorrectly configured;

[0114] 2. The local base station or the peer base station does not have a complete cell list;

[0115] 3. The local base station is blacklisted in the peer base station;

[0116] 4. Transmission link state abnormality.

[0117] Therefore, as shown in Figure 3 , when the network fault is an Xn interface fault, the first fault delimiting information judgment process can include the following steps:

[0118] Step 301: Obtain fault information of the Xn interface fault.

[0119] Step 302: judging whether the Xn interface configuration information and the cell list information of the local base station corresponding to the network fault are correct according to the fault information. If not, it is determined that the Xn interface fault is an intra-domain fault or a fault of an intra-domain network element; if yes, step 303 is performed.

[0120] The local base station can refer to a base station that generates the Xn interface fault.

[0121] Step 303: judging whether the opposite end base station is in the same domain. If not, it is determined that the fault is an inter-domain fault; if yes, step 304 is performed.

[0122] The opposite end base station can refer to a base station that communicates with the local base station.

[0123] Step 304: judging whether the Xn interface information and the cell list information of the opposite end base station are correct. If not, it is determined that the Xn interface fault is an intra-domain fault or an intra-domain cross-network element fault; if yes, it is determined that the Xn interface fault is an inter-domain fault.

[0124] It should be noted that the fault delimitation rule can be preconfigured or obtained by other devices. For example, when the domain management device is a domain management function unit, the fault delimitation rule can be received by a cross-domain management function unit.

[0125] In the third possible implementation, the domain management device can obtain configuration information and performance information of the first network fault associated object. The configuration information can be configuration parameters of the first network fault associated object, such as the IP address = X and the VLAN ID = 2 of the network element 1 associated object of the Xn fault; the performance information can be a performance measurement quantity or a key performance indicator (KPI) of the first network fault associated object, such as a packet loss rate, a delay, a transmission success rate, etc.

[0126] The domain management device determines the first fault delimitation information of the first network fault according to the first fault information of the first network fault, the configuration information and the performance information of the first network fault associated object.

[0127] In the fourth possible implementation, the domain management device can determine the first fault delimitation information of the first network fault according to the fault information of other network faults.

[0128] Specifically, the domain management device can obtain at least one second fault information, one second fault information in the at least one second fault information corresponding to one second network fault, and determine the first fault delimitation information of the first network fault according to the first fault information of the first network fault and the at least one second fault information.

[0129] For example, the first network fault is a configuration error of the Xn interface, for example, the configured IP address and the planned IP address are inconsistent, and the second network fault is a transmission link fault. If the first network fault is associated with the second network fault, it can be determined that the first network fault is an intra-domain fault.

[0130] The above is only an example, and the domain management device can also determine the first fault delimitation information of the first network fault in other ways, which will not be illustrated one by one here.

[0131] In step 203, the domain management device can have one or more of the following ways to specifically process the first network fault.

[0132] Method one: when the first fault delimitation information is intra-domain, that is, the first network fault is an intra-domain fault, the domain management device further processes the first network fault, including but not limited to root cause analysis, fault recovery processing, and dispatch triggering manual intervention processing, and the like.

[0133] Method two: when the first fault delimitation information is out-of-domain or unknown domain, that is, the first network fault is an out-of-domain fault or an unknown domain fault, the domain management device does not perform root cause analysis, fault recovery processing, and dispatch triggering manual intervention processing on the first network fault, but sends the first fault delimitation information to other devices. For example, when the domain management device is a domain management function unit, the domain management device can send the first fault delimitation information to a cross-domain management function unit that manages the domain management device, and the domain management device can also send the first fault information to the cross-domain management function unit.

[0134] Method three: regardless of whether the first fault delimitation information is intra-domain, out-of-domain, or unknown domain, the domain management device sends the first fault delimitation information to the cross-domain management device, instructing the cross-domain management device to process the first network fault according to the first fault delimitation information.

[0135] Further, in the embodiment of the present application, the cross-domain management function unit can process the first network fault according to the first fault delimitation information as follows:

[0136] When the first fault delimitation information is out-of-domain or unknown domain, the cross-domain management function unit triggers a corresponding fault analysis process. Specifically, the cross-domain management function unit can perform correlation analysis on the first network fault and the fault (hereinafter referred to as the second network fault) reported by the other domain management function unit.

[0137] If the first network fault is a fault in an unknown domain, and the second network fault is associated with the first network fault, and the second network fault is a fault in a domain, it can be determined that the first network fault is a fault in an unknown domain, and no further processing is performed on the first network fault, including root cause analysis, fault recovery processing, or dispatching (triggering manual intervention processing) and the like.

[0138] If the first network fault is a fault in an unknown domain, and the second network fault is associated with the first network fault, and the second network fault is a fault in a domain, it can be determined that the first network fault is a fault in an unknown domain, and no further processing is performed on the first network fault, including root cause analysis, fault recovery processing, or dispatching (triggering manual intervention processing) and the like.

[0139] If the first network fault is a fault in an unknown domain, and the second network fault is associated with the first network fault, and the second network fault is a fault in a domain, it can be determined that the first network fault is a fault in an unknown domain, and no further processing is performed on the first network fault, including root cause analysis, fault recovery processing, or dispatching (triggering manual intervention processing) and the like.

[0140] Optionally, if the first network fault is a fault in a domain, the cross-domain management function unit managing the domain management device can monitor the first network fault, and no further processing is performed on the first network fault.

[0141] Embodiment Two:

[0142] Referring to Figure 4 , a flowchart of a fault processing method provided in an embodiment of the present application.

[0143] Figure 4 In the embodiment, the cross-domain management device can refer to Figure 1 the cross-domain management function unit in

[0144] Step 401: The cross-domain management device acquires at least one of first fault information and first fault delimitation information of a first network fault.

[0145] The first fault delimitation information is in a domain, or out of a domain, or unknown.

[0146] In Embodiment Two, the specific content of the first fault delimitation information can refer to the description in Embodiment One, which will not be described here.

[0147] Step 402: The cross-domain management device determines second fault delimitation information of the first network fault according to the first fault information or the first fault delimitation information.

[0148] In a possible implementation, the second fault delimitation information indicates whether the first network fault is within the scope of the cross-domain management device, and the second fault delimitation information is cross-domain and single-domain; in another possible implementation, the second fault delimitation information indicates that the first network fault is within the scope of the first domain management device, and the second fault delimitation information is domain management device indication information.

[0149] In an example, the single domain includes at least one of an access network domain, a core network domain, a transmission domain, a data center domain, and a virtual resource domain. For example, the access network domain describes a wireless access network provided by one or more wireless access network devices (e.g., a base station); the core network domain describes a core network provided by one or more core network devices (e.g., an MME or an AMF); the transmission network domain describes a transmission network provided by one or more transmission devices (e.g., an optical device); the data center domain describes an IP network provided by one or more data centers; and the virtual resource domain describes a virtual network provided by one or more virtual resources (e.g., a virtual machine).

[0150] In the second embodiment, when the second fault delimitation information corresponding to the first network fault is single-domain, it indicates that the first network fault is caused by an abnormality of an object or a network element managed by a domain management device managed by the cross-domain management device; and when the second fault delimitation information corresponding to the first network fault is cross-domain, it indicates that the first network fault is caused by an abnormality of an object or a network element managed by at least two domain management devices managed by the cross-domain management device.

[0151] Further, when the second fault delimitation information is single-domain, the cross-domain management device can further determine, according to the first fault information, a network element that causes the first network fault and a domain management device that manages the network element, and the like, which can be determined according to actual conditions and will not be described herein again.

[0152] In step 403, the cross-domain management device processes the first network fault according to the second fault delimitation information.

[0153] As can be known from the above description, in the second embodiment, the first network fault can correspond to at least two second fault delimitation information, i.e., the second fault delimitation information and the first fault delimitation information. The second fault delimitation information is used to describe the fault of the first network fault within the scope of the cross-domain management device, and the first fault delimitation information is used to describe the fault of the first network fault within the scope of the domain management function unit managed by the cross-domain management device.

[0154] At least one of the first fault information and the first fault delimitation information can be reported to the cross-domain management device by a domain management device managed by the cross-domain management device. The cross-domain management device specifically how to obtain at least one of the first fault information and the first fault delimitation information is not limited in the embodiments of the present application, and will not be described here.

[0155] At step 402, the cross-domain management device can determine the second fault delimitation information in multiple ways, which will be described in detail below.

[0156] In a first possible implementation, the cross-domain management device can determine the second fault delimitation information according to at least one of the fault type and the fault generated network element in the first fault information.

[0157] For example, if the fault type of the first network fault is a fault caused by an abnormality of the fault generated network element or a component of the fault generated network element, it can be determined that the first network fault is a single-domain fault, i.e., the second fault delimitation information is single domain. For example, the first network fault is a single-domain fault when the fault type of the first network fault is any of the following: a radio frequency unit standing wave fault; a radio frequency unit software running abnormality fault; a battery fault; a single-board clock input abnormality fault; a configuration file damage fault, etc.

[0158] In a second possible implementation, the cross-domain management device can determine the second fault delimitation information according to a fault delimitation rule.

[0159] The fault delimitation rule can include an association relationship between the fault type and the second fault delimitation information, and the cross-domain management device can determine the fault delimitation information associated with the fault type of the first network fault in the fault delimitation rule as the second fault delimitation information.

[0160] Optionally, the fault delimitation rule can include an association relationship between the network fault and a second fault delimitation information judgment process.

[0161] Some network faults can be caused by an abnormality of a local network element, or can be caused by an abnormality of a peer network element, or other reasons, and some network faults can exist in an associated second fault delimitation information judgment process, so that the second fault delimitation information of the network fault can be determined according to the second fault delimitation information judgment process.

[0162] It should be noted that the fault delimitation rule can be preconfigured or obtained by other devices.

[0163] In a third possible implementation, the cross-domain management device can perform delimitation analysis according to the received at least one fault information, thereby determining the second fault delimitation information of the first network fault.

[0164] For example, as shown in Figure 5 The cross-domain management device manages three domain management function units, i.e., a domain management function unit 1, a domain management function unit 2, and a domain management function unit 3. The cross-domain management device obtains first fault information from the domain management function unit 1. The cross-domain management device can also obtain third fault information of a third network fault through the domain management function unit 2 and fourth fault information of a fourth network fault through the domain management function unit 3.

[0165] It is assumed that the first network fault and the third network fault are both Xn interface faults, and the fourth network fault is a transmission link fault.

[0166] If the first network fault is associated with both Xn interface faults and transmission link faults, for example, the first network fault is associated with the third network fault and the fourth network fault, and the Xn interface corresponding to the first network fault matches the Xn interface corresponding to the third network fault, it can be determined that the second fault delimitation information is single-domain, i.e., the first network fault is a single-domain fault; further, the first network fault is a single-domain fault of the domain management function unit 3.

[0167] If the first network fault is associated with the third network fault and there is no association relationship with the fourth network fault, and the Xn interface corresponding to the first network fault does not match the Xn interface corresponding to the third network fault, it can be determined that the second fault delimitation information is cross-domain, i.e., the first network fault is a cross-domain fault.

[0168] If the first network fault is associated with the third network fault and there is no association relationship with the fourth network fault, and the configuration of the Xn interface corresponding to the first network fault is incorrect, for example, the configured IP address does not match the planned IP address, it can be determined that the second fault delimitation information is single-domain, i.e., the first network fault is a single-domain fault. Further, the first network fault is a single-domain fault of the domain management function unit 1.

[0169] In a fourth possible implementation, the cross-domain management device can determine second fault delimitation information of the first network fault according to the first fault delimitation information.

[0170] For example, when the first fault delimitation information in the first fault information is intra-domain, i.e., the first network fault is an intra-domain fault, the cross-domain management device can determine that the second fault delimitation information is single-domain, i.e., the first network fault is a single-domain fault.

[0171] When the first fault delimitation information in the first fault information is out-of-domain or unknown domain, i.e., the first network fault is an out-of-domain fault or an unknown domain fault, when the first network fault exists an associated third network fault, and the fault delimitation information of the third network fault is in-domain, the cross-domain management device can determine that the second fault delimitation information is single domain, i.e., the first network fault is a single domain fault.

[0172] It should be noted that in this case, the second fault delimitation information is single domain, which indicates that the first network fault is a single domain fault of the domain management device reporting the third network fault, i.e., the first network fault is caused by an abnormality of an object or a network element managed by the domain management device reporting the third network fault.

[0173] When the first fault delimitation information in the first fault information is out-of-domain or unknown domain, i.e., the first network fault is an out-of-domain fault or an unknown domain fault, when the first network fault exists an associated third network fault, and the fault delimitation information of the third network fault is out-of-domain, the cross-domain management device can determine that the second fault delimitation information is cross-domain, i.e., the first network fault is a cross-domain fault.

[0174] The above is only an example, and other determination manners can also exist, which will not be illustrated one by one here.

[0175] It should be noted that when the cross-domain management device determines that the second fault information is cross-domain, the cross-domain management device can indicate the domain management device that the second fault information is cross-domain, or the cross-domain management device instructs the domain management device to delete the first network fault, and the domain management device is the device sending the first fault information.

[0176] When the cross-domain management device determines that the second fault delimitation information is single domain, the cross-domain management device can also determine the network element causing the first network fault according to the first fault information. How to determine can be determined according to actual conditions.

[0177] In step 403, how the cross-domain management device processes the first network fault according to the second fault delimitation information can exist in multiple manners.

[0178] In one possible implementation manner, when the second fault delimitation information is cross-domain, i.e., the first network fault is a cross-domain fault, the cross-domain management device performs root cause analysis on the first network fault.

[0179] In a possible implementation, the second fault delimitation information is a single domain, that is, the first network fault is a single-domain fault, and the cross-domain management device can determine, according to the first fault information, a network element that has the first network fault, and instruct the network element that has the first network fault to process the first network fault. The network element that has the first network fault can perform root cause analysis, fault recovery processing, and order dispatching (triggering manual intervention processing) and the like on the first network fault, and the cross-domain management device monitors the first network fault and does not further process the first network fault.

[0180] It should be noted that the network element that has the first network fault can be a network element that sends the first fault information to the cross-domain management device, or can be another cross-domain management functional unit, which can be determined according to actual conditions, and will not be described here.

[0181] It can be known from the process of Embodiment Two that, by further distinguishing whether the first network fault is a single-domain fault or a cross-domain fault, and further determining which domain the single-domain fault is in, it is determined whether the first network fault is processed by the cross-domain management functional unit or the domain management functional unit that has the first network fault, so that it can be accurately determined how to process the first network fault, and the fault processing efficiency is improved.

[0182] Embodiment Three:

[0183] In the embodiments of the present application, the cross-domain management functional unit or the domain management functional unit can open a fault query interface for specific first fault delimitation information; the fault query interface for specific first fault delimitation information is applicable to the following two deployment scenarios:

[0184] Scenario One: The cross-domain management functional unit provides the fault query interface for specific first fault delimitation information to a work order system or an operation and maintenance personnel for query;

[0185] Scenario Two: The domain management functional unit provides the fault query interface for specific first fault delimitation information to the cross-domain management functional unit for query.

[0186] The work order system or the operation and maintenance personnel can send a fault query or a subscription request to the cross-domain management functional unit or the domain management functional unit through the fault query interface, the fault query or the subscription request carries the first fault delimitation information, and the fault query or the subscription request is used to request fault information corresponding to the first fault delimitation information.

[0187] If the fault query or the subscription request is sent to the domain management functional unit, the first fault delimitation information includes at least one of the following: a fault in a domain, a fault outside a domain, a single-network-element fault in a domain, a cross-network-element fault in a domain, and a fault in an unknown domain.

[0188] If a fault query or a subscription request is sent to the cross-domain management function unit, the first fault delimitation information includes at least one of the following: a single-domain fault, a cross-domain fault, a single-network-element fault, a single-domain multi-network-element fault, and an unknown-domain fault.

[0189] The cross-domain management function unit or the domain management function unit determines corresponding fault information according to the first fault delimitation information, and returns at least one fault information corresponding to the first fault delimitation information.

[0190] Through the above method, the first fault delimitation information is introduced as a fault screening condition, which can meet the needs of different users for network fault queries. For example, some cross-domain management function units only care about cross-domain faults, and thus only cross-domain faults can be queried or subscribed, thereby improving the query efficiency.

[0191] Embodiment Four

[0192] The embodiments of the present application also provide a system, which can be specifically referred to as Figure 6 The system includes a cross-domain management device and at least one domain management device. The cross-domain management device can manage the at least one domain management device, and each domain management device can manage at least one network element.

[0193] Optionally, in step 601, the cross-domain management device sends a fault delimitation rule to the domain management device.

[0194] If the cross-domain management device does not send the fault delimitation rule, the fault delimitation rule can also be preconfigured in the domain management device through other manners.

[0195] Optionally, the cross-domain management device can also send a network fault template to the domain management device.

[0196] In step 602, the domain management device acquires at least one fault information, and one fault information in the at least one fault information is information corresponding to one network fault.

[0197] The domain management device can acquire the at least one fault information from the network elements managed by the domain management device through various manners, which can be specifically referred to as the foregoing description, and will not be described here.

[0198] For the convenience of description, the first fault information in the at least one fault information processed by the domain management device is taken as an example for description, and the first fault information is any fault information in the at least one fault information.

[0199] In step 603, the domain management device determines first fault delimitation information of a first network fault according to the first fault information.

[0200] The first fault delimitation information can be a domain, an out-of-domain, or an unknown domain.

[0201] Step 604: The domain management device sends at least one of the first fault information and the first fault delimitation information to the cross-domain management device.

[0202] It should be noted that when the first fault delimitation information is a domain, the domain management device can not send the first fault information and the first fault delimitation information to the cross-domain management device.

[0203] Step 605: The domain management device processes the first network fault according to the first fault information.

[0204] Specifically, when the first fault delimitation information is a domain, the domain management device further processes the first network fault, including but not limited to root cause analysis, fault recovery, and dispatch triggering manual intervention processing, etc.

[0205] When the first fault delimitation information is a domain or unknown domain, the domain management device does not perform root cause analysis, fault recovery, and dispatch triggering manual intervention processing on the first network fault, but monitors the first network fault.

[0206] Step 606: The cross-domain management device can determine second fault delimitation information of the first network fault according to the first fault information or the first fault delimitation information, and process the first network fault according to the second fault delimitation information.

[0207] The specific content of step 606 can refer to the description in steps 402 and 403, which will not be repeated here.

[0208] Optionally, the cross-domain management device can process the first network fault according to the first fault information. Specifically, when the first fault delimitation information is a domain or unknown domain, the cross-domain management device triggers a corresponding fault analysis process. Specifically, the cross-domain management device can perform correlation analysis on the first network fault and the fault (hereinafter referred to as the second network fault) reported by other domain management devices.

[0209] If the first network fault is a fault of an unknown domain, is correlated with the second network fault, and the second network fault is a fault in a domain, the first network fault can not be further processed, including root cause analysis, fault recovery, or dispatch (triggering manual intervention processing) and the like.

[0210] If the first network fault is a fault of an unknown domain, is correlated with the second network fault, and the second network fault is a fault in a domain, the first network fault can not be further processed, including root cause analysis, fault recovery, or dispatch (triggering manual intervention processing) and the like.

[0211] If the first network fault is a fault out of a domain or a fault out of an unknown domain, and no fault reported by any other domain management device is associated with the first network fault, further processing can be performed on the first network fault, including cross-domain fault delimiting analysis, root cause analysis, fault recovery, or dispatching (triggering manual intervention processing) and the like.

[0212] Optionally, if the first network fault is a fault within a domain, the cross-domain management device can monitor the first network fault, and no further processing is performed on the first network fault.

[0213] In the embodiments provided in the present application, the method provided in the embodiments of the present application is introduced from the perspective of interaction between the domain management device and the cross-domain management device. In order to realize the functions in the method provided in the embodiments of the present application, the domain management device and the cross-domain management device can include hardware structures and / or software modules, and the above functions can be realized in the form of hardware structures, software modules, or hardware structures and software modules. Whether a certain function in the above functions is executed in the form of hardware structure, software module, or hardware structure and software module depends on the specific application of the technical solution and the design constraint conditions.

[0214] Figure 7 And Figure 8 The structure of the possible communication device provided in the embodiments of the present application is shown. These communication devices can realize the functions of the domain management device or the cross-domain management device in the above method embodiments, and thus can also realize the beneficial effects possessed by the above method embodiments.

[0215] As Figure 7 shown, the communication device 700 includes a communication unit 701 and a processing unit 702. The communication device 700 can be used to realize the functions of the domain management device or the cross-domain management device in the method embodiments shown in the above Figure 2 .

[0216] When the communication device 700 is used to realize the functions of the domain management device in the method embodiments shown in the above Figure 2 :

[0217] The communication unit is configured to obtain first fault information of a first network fault.

[0218] The processing unit is configured to determine first fault delimiting information of the first network fault according to the first fault information, the first fault delimiting information indicating a range of the first network fault, the first fault delimiting information being within a domain or out of a domain or unknown domain, and performing processing on the first network fault according to the first fault delimiting information.

[0219] In a possible design, the processing unit is specifically configured to:

[0220] determine an abnormal network element corresponding to the first network fault according to the first fault information;

[0221] determine first fault delimitation information of the first network fault according to the abnormal network element.

[0222] In a possible design, the first fault information includes a fault type, and the processing unit is specifically configured to:

[0223] if it is determined according to the fault type in the first fault information that the first network fault is caused by an abnormal local network element, the local network element is determined as the abnormal network element;

[0224] or, if it is determined according to the fault type in the first fault information that the first network fault is caused by an abnormal peer network element of the local network element, the peer network element is determined as the abnormal network element.

[0225] The local network element is a network element that sends the first fault information to the domain management device.

[0226] In a possible design, the processing unit is specifically configured to:

[0227] when the abnormal network element is a network element managed by the domain management device, the first fault delimitation information indicates that the range of the first network fault is within a domain.

[0228] when the abnormal network element is not a network element managed by the domain management device, the first fault delimitation information indicates that the range of the first network fault is outside the domain.

[0229] In a possible design, the first fault information includes a fault type, and the processing unit is specifically configured to:

[0230] determine the first fault delimitation information according to a fault delimitation rule and the fault type; the fault delimitation rule includes an association relationship between a fault type and first fault delimitation information.

[0231] In a possible design, the communication unit is further configured to:

[0232] obtain configuration information and performance information of the first network fault associated object;

[0233] The processing unit is specifically configured to:

[0234] determine first fault delimitation information of the first network fault according to first fault information of the first network fault, configuration information and performance information of the first network fault associated object.

[0235] In a possible design, the communication unit is further configured to:

[0236] obtaining at least one second fault information, one of the at least one second fault information corresponding to one second network fault;

[0237] The processing unit is further configured to:

[0238] determine first fault delimitation information of the first network fault according to the first fault information of the first network fault and the at least one second fault information.

[0239] In a possible design, the processing unit is specifically configured to:

[0240] when the first fault delimitation information indicates that the first network fault is within a domain, perform root cause analysis or fault recovery processing on the first network fault; or,

[0241] when the first fault delimitation information indicates that the first network fault is outside a domain or unknown domain, send the first fault delimitation information to a cross-domain management device.

[0242] when the communication apparatus 700 is configured to implement Figure 4 the function of the cross-domain management device in the method embodiment:

[0243] a communication unit, configured to obtain at least one of first fault information and first fault delimitation information of a first network fault, the first fault delimitation information being within a domain or outside a domain or unknown domain;

[0244] a processing unit, configured to determine second fault delimitation information of the first network fault according to the first fault information or the first fault delimitation information; the second fault delimitation information indicates whether the first network fault is within a range of the cross-domain management device, and the second fault delimitation information is cross-domain and single-domain; or the second fault delimitation information indicates that the first network fault is within a range of a first domain management device, and the second fault delimitation information is domain management device indication information; and perform processing on the first network fault according to the second fault delimitation information.

[0245] In a possible design, the processing unit is specifically configured to:

[0246] when the first fault delimitation information is within a domain, determine that the second fault delimitation information indicates that the first network fault is within a single domain;

[0247] or, when the first fault delimitation information is outside a domain or unknown domain, and the first network fault has an associated third network fault, and fault delimitation information of the third network fault is within a domain, determine that the second fault delimitation information indicates that the first network fault is within a single domain;

[0248] Alternatively, when the first fault delimitation information is outside the domain or an unknown domain, and the first network fault has an associated third network fault, and the fault delimitation information of the third network fault is outside the domain, then the second fault delimitation information indicates that the scope of the first network fault is cross-domain.

[0249] In one possible design, the first fault information includes a fault type, and the processing unit is specifically used for:

[0250] The second fault delimitation information is determined based on the fault delimitation rules and the fault type; the fault delimitation rules include the correlation between the fault type and the second fault delimitation information.

[0251] In one possible design, the processing unit is specifically used for:

[0252] When the second fault delimitation information is cross-domain, the first network fault undergoes root cause analysis or fault recovery processing;

[0253] Alternatively, when the second fault delimitation information is a single domain, the domain management device that caused the first network fault is determined based on the first fault information, and the domain management device is instructed to handle the first network fault.

[0254] For a more detailed description of the communication unit 701 and the processing unit 702 described above, please refer to the relevant descriptions in the above method embodiments, which will not be repeated here.

[0255] like Figure 8 As shown, the communication device 800 includes a processor 810 and an interface circuit 820. The processor 810 and the interface circuit 820 are coupled to each other. It is understood that the interface circuit 820 can be a transceiver or an input / output interface. Optionally, the communication device 800 may also include a memory 830 for storing instructions executed by the processor 810, or storing input data required by the processor 810 to execute instructions, or storing data generated after the processor 810 executes instructions.

[0256] When the communication device 800 is used to implement the method in the above method embodiment, the processor 810 is used to execute the function of the processing unit 702, and the interface circuit 820 is used to execute the function of the communication unit 701.

[0257] When the aforementioned communication device is a chip applied to a terminal device, the terminal device chip implements the functions of the terminal device in the above method embodiments. The terminal device chip receives information from other modules (such as an RF module or antenna) in the terminal device, the information being sent to the terminal device by the network device; or, the terminal device chip sends information to other modules (such as an RF module or antenna) in the terminal device, the information being sent to the network device by the terminal device.

[0258] When the communication device is a chip applied to a network device, the network device chip implements the functions of the network device in the method embodiments. The network device chip receives information from other modules (such as a radio frequency module or an antenna) in the network device, and the information is sent by the terminal device to the network device. Alternatively, the network device chip sends information to other modules (such as a radio frequency module or an antenna) in the network device, and the information is sent by the network device to the terminal device.

[0259] It can be understood that the processor in the embodiments of the present application can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor.

[0260] The method steps in the embodiments of the present application can be implemented in the form of hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically EPROM (EEPROM), a register, a hard disk, a mobile hard disk, a CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in an access network device or a terminal device. Of course, the processor and the storage medium can also exist as discrete components in the access network device or the terminal device.

[0261] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer programs or instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are performed. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer programs or instructions can be stored in or transmitted by a computer readable storage medium. The computer readable storage medium can be any available medium or a data storage device integrated with one or more available media, which is accessible by a computer. The available medium can be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; an optical medium, such as a DVD; or a semiconductor medium, such as a solid state disk (SSD).

[0262] In various embodiments of the present application, the terms and / or descriptions of different embodiments are consistent and can be referred to each other if there is no special description and logical conflict. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0263] In the present application, "at least one" means one or more, and "multiple" means two or more. The association relationship of the associated objects is described, which means that there can be three kinds of relationships, for example, A and / or B, which can represent the following three cases: A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. In the textual description of the present application, the character " / ", generally represents that the associated objects before and after are in an "or" relationship; in the formula of the present application, the character " / ", represents that the associated objects before and after are in a "division" relationship.

[0264] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer usable storage media (including but not limited to magnetic disk storage, optical storage, etc.) containing computer usable program code.

[0265] The computer program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other processing device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other processing device to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions specified in the flowchart block or blocks. Figure 1 The flowchart and / or block diagram in the variation of the present application can describe any device, apparatus, and / or process that is / are configured to perform the functions described in the flowchart and / or block diagram. That is, the flowchart and / or block diagram in the variation of the present application can describe functions described as being performed by one or more specific devices, apparatus, and / or processes. Figure 1 The flowchart and / or block diagram in the variation of the present application can describe any device, apparatus, and / or process that is / are configured to perform the functions described in the flowchart and / or block diagram. That is, the flowchart and / or block diagram in the variation of the present application can describe functions described as being performed by one or more specific devices, apparatus, and / or processes.

[0266] The computer program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other processing device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other processing device to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions specified in the flowchart block or blocks. Figure 1 The flowchart and / or block diagram in the variation of the present application can describe any device, apparatus, and / or process that is / are configured to perform the functions described in the flowchart and / or block diagram. That is, the flowchart and / or block diagram in the variation of the present application can describe functions described as being performed by one or more specific devices, apparatus, and / or processes. Figure 1 The flowchart and / or block diagram in the variation of the present application can describe any device, apparatus, and / or process that is / are configured to perform the functions described in the flowchart and / or block diagram. That is, the flowchart and / or block diagram in the variation of the present application can describe functions described as being performed by one or more specific devices, apparatus, and / or processes.

[0267] Obviously, numerous modifications and variations of the present application are possible in light of the above teachings. It is therefore to be understood that within the scope of the application, the application can be practiced otherwise than as specifically described. Thus, the application should be considered as limited only by the scope of the following claims, and their equivalents.

Claims

1. A failure handling method characterized by, The method comprises: a domain management device obtaining first fault information of a first network fault; the domain management device determining first fault delimitation information of the first network fault according to the first fault information; the first fault delimitation information indicating a range of the first network fault, the first fault delimitation information being intra-domain or inter-domain or unknown domain; when the first fault delimitation information indicates that the range of the first network fault is intra-domain, the domain management device performing root cause analysis or fault recovery processing on the first network fault; or when the first fault delimitation information indicates that the range of the first network fault is inter-domain or unknown domain, the domain management device sending the first fault delimitation information to a cross-domain management device.

2. The method of claim 1, wherein, The domain management device determines first fault delimitation information of the first network fault according to the first fault information, comprising: the domain management device determining an abnormal network element corresponding to the first network fault according to the first fault information; the domain management device determining the first fault delimitation information of the first network fault according to the abnormal network element.

3. The method of claim 2, wherein, The first fault information comprises a fault type, and the domain management device determines the abnormal network element corresponding to the first network fault according to the first fault information, comprising: if the domain management device determines that the first network fault is caused by an abnormal local network element according to the fault type in the first fault information, the domain management device determines the local network element as the abnormal network element; or, if the domain management device determines that the first network fault is caused by an abnormal peer network element of the local network element according to the fault type in the first fault information, the domain management device determines the peer network element as the abnormal network element; wherein the local network element is a network element sending the first fault information to the domain management device.

4. The method of claim 3, wherein, The domain management device determines the first fault delimitation information of the first network fault according to the abnormal network element, comprising: when the abnormal network element is a network element managed by the domain management device, the range of the first network fault indicated by the first fault delimitation information is intra-domain; when the abnormal network element is not a network element managed by the domain management device, the range of the first network fault indicated by the first fault delimitation information is inter-domain.

5. The method of claim 1, wherein, The first fault information comprises a fault type, and the domain management device determines the first fault delimitation information of the first network fault according to the first fault information, comprising: the domain management device determines the first fault delimitation information according to a fault delimitation rule and the fault type; the fault delimitation rule comprises an association relationship between the fault type and the first fault delimitation information.

6. The method of claim 1, wherein, The method further comprises: the domain management device obtaining configuration information and performance information of the first network fault associated object; the domain management device determines the first fault delimitation information of the first network fault according to the first fault information of the first network fault, the configuration information and the performance information of the first network fault associated object, comprising: the domain management device determines the first fault delimitation information of the first network fault according to the first fault information of the first network fault, the configuration information and the performance information of the first network fault associated object.

7. The method of claim 1, wherein, The method further comprises: The domain management device acquires at least one second fault information, one of the at least one second fault information corresponding to one second network fault; The domain management device determines first fault delimitation information of the first network fault according to the first fault information, comprising: The domain management device determines first fault delimitation information of the first network fault according to the first fault information of the first network fault and the at least one second fault information.

8. The method according to any one of claims 1 to 7, characterized in that, The domain includes at least one of an access network domain, a core network domain, a transmission domain, a data center domain and a virtual resource domain.

9. A fault handling method characterized by, Comprising: The cross-domain management device acquires at least one of the first fault information and the first fault delimitation information of the first network fault, the first fault delimitation information being domain, or domain, or unknown domain; The cross-domain management device determines second fault delimitation information of the first network fault according to the first fault information or the first fault delimitation information; The second fault delimitation information indicates whether the first network fault is within the scope of the cross-domain management device, and the second fault delimitation information is cross-domain and single-domain; or the second fault delimitation information indicates that the first network fault is within the scope of the first domain management device, and the second fault delimitation information is domain management device indication information; When the second fault delimitation information is cross-domain, the cross-domain management device performs root cause analysis or fault recovery processing on the first network fault; Or, when the second fault delimitation information is single-domain, the cross-domain management device determines the domain management device that occurs the first network fault according to the first fault information, and instructs the domain management device that occurs the first network fault to process the first network fault.

10. The method of claim 9, wherein, The cross-domain management device determines second fault delimitation information of the first network fault according to the first fault delimitation information, comprising: When the first fault delimitation information is domain, the cross-domain management device determines that the second fault delimitation information indicates that the scope of the first network fault is single-domain; Or, when the first fault delimitation information is domain or unknown domain, and the first network fault exists associated third network fault, and the fault delimitation information of the third network fault is domain, the cross-domain management device determines that the second fault delimitation information indicates that the scope of the first network fault is single-domain; Or, when the first fault delimitation information is domain or unknown domain, and the first network fault exists associated third network fault, and the fault delimitation information of the third network fault is domain, the cross-domain management device determines that the second fault delimitation information indicates that the scope of the first network fault is cross-domain.

11. The method of claim 10, wherein, The method further comprises: When the cross-domain management device determines that the second fault delimitation information is cross-domain, the cross-domain management device indicates to the first domain management device that the second fault delimitation information is cross-domain, or the cross-domain management device instructs the first domain management device to delete the first network fault, the first domain management device being the device that sends the first fault information or the first fault delimitation information.

12. The method of claim 9, wherein, The first fault information includes a fault type, and the cross-domain management device determines second fault delimitation information of the first network fault according to the first fault information, including: The cross-domain management device determines the second fault delimitation information according to a fault delimitation rule and the fault type; the fault delimitation rule includes an association relationship between the fault type and the second fault delimitation information.

13. The method according to any one of claims 9-12, characterized in that, The single domain includes at least one of an access network domain, a core network domain, a transmission domain, a data center domain, and a virtual resource domain.

14. A system, characterized by Including: A domain management device, configured to acquire first fault information of a first network fault; Determine first fault delimitation information of the first network fault according to the first fault information; The first fault delimitation information indicates a range of the first network fault, and the first fault delimitation information is in-domain, out-of-domain, or unknown domain; when the first fault delimitation information is determined to be out-of-domain or unknown domain, at least one of the first fault information and the first fault delimitation information is sent to a cross-domain management device; The cross-domain management device is configured to acquire at least one of first fault information and first fault delimitation information of a first network fault, and the first fault delimitation information is in-domain, out-of-domain, or unknown domain; determine second fault delimitation information of the first network fault according to the first fault information or the first fault delimitation information; The second fault delimitation information indicates whether the first network fault is within the range of the cross-domain management device, and the second fault delimitation information is cross-domain and single-domain; or, the second fault delimitation information indicates that the first network fault is within the range of a first domain management device, and the second fault delimitation information is domain management device indication information; When the second fault delimitation information is cross-domain, the first network fault is analyzed for root cause or fault recovery processing; or, when the second fault delimitation information is single-domain, a domain management device that causes the first network fault is determined according to the first fault information, and the domain management device that causes the first network fault is instructed to process the first network fault.

15. The system of claim 14, wherein, The domain management device is specifically configured to: When the first fault delimitation information indicates that the range of the first network fault is in-domain, the first network fault is analyzed for root cause or fault recovery processing; or, When the first fault delimitation information indicates that the range of the first network fault is out-of-domain or unknown domain, the first fault delimitation information is sent to the cross-domain management device.

16. A communications device, characterized by Including: A communication unit, configured to acquire first fault information of a first network fault; A processing unit, configured to determine first fault delimitation information of the first network fault according to the first fault information; The first fault delimitation information indicates a range of the first network fault, and the first fault delimitation information is in-domain, out-of-domain, or unknown domain; when the first fault delimitation information indicates that the range of the first network fault is in-domain, root cause analysis or fault recovery processing is performed on the first network fault; or when the first fault delimitation information indicates that the range of the first network fault is out-of-domain or unknown domain, the first fault delimitation information is sent to a cross-domain management device.

17. The apparatus of claim 16, wherein, The processing unit is specifically configured to: determine an abnormal network element corresponding to the first network fault according to the first fault information; determine first fault delimitation information of the first network fault according to the abnormal network element.

18. The apparatus of claim 17, wherein, The first fault information includes a fault type, and the processing unit is specifically configured to: if it is determined according to the fault type in the first fault information that the first network fault is caused by an abnormal local network element, the local network element is determined as the abnormal network element; or, if it is determined according to the fault type in the first fault information that the first network fault is caused by an abnormal peer network element of the local network element, the peer network element is determined as the abnormal network element; wherein the local network element is a network element that sends the first fault information to the communication device.

19. The apparatus of claim 18, wherein, The processing unit is specifically configured to: when the abnormal network element is a network element managed by the communication device, the range of the first network fault indicated by the first fault delimitation information is in-domain; when the abnormal network element is not a network element managed by the communication device, the range of the first network fault indicated by the first fault delimitation information is out-of-domain.

20. The apparatus of claim 16, wherein, The first fault information includes a fault type, and the processing unit is specifically configured to: determine the first fault delimitation information according to a fault delimitation rule and the fault type; the fault delimitation rule includes an association relationship between a fault type and first fault delimitation information.

21. The apparatus of claim 16, wherein, The communication unit is further configured to: obtain configuration information and performance information of the first network fault associated object; The processing unit is specifically configured to: determine first fault delimitation information of the first network fault according to first fault information of the first network fault, configuration information and performance information of the first network fault associated object.

22. The apparatus of claim 16, wherein, The communication unit is further configured to: obtain at least one second fault information, one second fault information in the at least one second fault information corresponding to one second network fault; The processing unit is further configured to: determine first fault delimitation information of the first network fault according to first fault information of the first network fault and the at least one second fault information.

23. The apparatus of any of claims 16-22, wherein, The in-domain includes at least one of an access network domain, a core network domain, a transmission domain, a data center domain, and a virtual resource domain.

24. A communications device, characterized by It includes: a communication unit configured to obtain at least one of first fault information and first fault delimitation information of a first network fault, the first fault delimitation information being in-domain, out-of-domain, or unknown domain; a processing unit configured to determine second fault delimitation information of the first network fault according to the first fault information or the first fault delimitation information; The second fault localization information indicates whether the first network fault is within a range of the communication device, and the second fault localization information is cross-domain and single-domain; or the second fault localization information indicates that the first network fault is within a range of a first domain management device, and the second fault localization information is domain management device indication information. When the second fault localization information is cross-domain, root cause analysis or fault recovery processing is performed on the first network fault; or when the second fault localization information is single-domain, a domain management device that causes the first network fault is determined according to the first fault information, and the domain management device that causes the first network fault is instructed to process the first network fault.

25. The apparatus of claim 24, wherein, The processing unit is specifically configured to: When the first fault localization information is within a domain, it is determined that the second fault localization information indicates that the range of the first network fault is single-domain. Or, when the first fault localization information is outside a domain or unknown domain, and there is a third network fault associated with the first network fault, and the fault localization information of the third network fault is within a domain, it is determined that the second fault localization information indicates that the range of the first network fault is single-domain. Or, when the first fault localization information is outside a domain or unknown domain, and there is a third network fault associated with the first network fault, and the fault localization information of the third network fault is outside a domain, it is determined that the second fault localization information indicates that the range of the first network fault is cross-domain.

26. The apparatus of claim 24, wherein, The first fault information includes a fault type, and the processing unit is specifically configured to: Determine the second fault localization information according to a fault localization rule and the fault type; the fault localization rule includes an association relationship between a fault type and second fault localization information.

27. The apparatus of any of claims 24-26, wherein, The single-domain includes at least one of an access network domain, a core network domain, a transmission domain, a data center domain, and a virtual resource domain.

28. A communications device, characterized by It includes a processor and a memory: The processor is configured to execute a computer program or instructions stored in the memory, and when the computer program or instructions are executed, the method in any one of claims 1 to 13 is executed.

29. A chip, characterized by It includes a processor, and the processor is coupled with the memory and is configured to execute a computer program or instructions stored in the memory, and when the processor executes the computer program or instructions, the method in any one of claims 1 to 13 is executed.

Images