CN113709777A

CN113709777A - Fault processing method, device and system

Info

Publication number: CN113709777A
Application number: CN202110516232.2A
Authority: CN
Inventors: 许瑞岳
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-05-21
Filing date: 2021-05-12
Publication date: 2021-11-26
Also published as: WO2021233224A1

Abstract

The application provides a fault processing method, a device and a system, wherein the method comprises the following steps: the method comprises the steps that domain management equipment obtains first fault information of a first network fault; the domain management equipment determines first fault delimiting information of the first network fault according to the first fault information, wherein the first fault delimiting information indicates the range of the first network fault; and the domain management equipment processes the first network fault according to the first fault delimitation information. By the method, the range of the first network fault can be determined by determining the first fault delimiting information of the first network fault, and the intra-domain fault, the extra-domain fault or the unknown fault can be distinguished, so that the fault is determined to be processed by the domain management equipment or the cross-domain management equipment, the cooperation of layered and domain-divided fault processing is realized, and the fault processing efficiency is improved.

Description

Fault processing method, device and system

The application requires that Chinese patent office, application number 202010437486.0, filed 21/05/2020 Priority of chinese patent application entitled "a method, apparatus and system for fault handling", the entire contents of which are incorporated by reference Incorporated in the present application.

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, and a system for processing a fault.

Background

The operator network has been developed to the fifth generation mobile communication technology (5G), the network architecture becomes more flexible, the requirements on key performance indexes such as time delay, speed, connection scale and the like of the network are continuously improved, the application industry is more and more abundant and diversified, the performance guarantee and flexibility of the service are fundamentally changed, and the difficulty in network operation and maintenance is increased.

Network failures can directly affect service performance and even cause service interruption, and how to quickly detect and eliminate failures is one of the main challenges of operation and maintenance. In the prior art, a network element, a domain management device, and a cross-domain management device all perform functions such as cause analysis and fault repair on collected faults/alarms, and how to improve the fault processing efficiency of the entire network in cooperation with the fault processing capabilities of the network element, the domain management device, and the cross-domain management device is a problem to be solved urgently.

Disclosure of Invention

The embodiment of the application provides a fault processing method, a fault processing device and a fault processing system, which are used for solving the problem of how to improve the fault processing efficiency of a network.

In a first aspect, the present application provides a method comprising: the method comprises the steps that domain management equipment obtains first fault information of a first network fault; the domain management equipment determines first fault delimitation information of the first network fault according to the first fault information; the first fault delimiting information indicates the range of the first network fault, and the first fault delimiting information is in a domain or outside the domain or an unknown domain; and the domain management equipment processes the first network fault according to the first fault delimitation information.

In the above process, the first fault delimiting information of the first network fault is determined, so that the range of the first network fault can be determined, the intra-domain fault, the extra-domain fault or the unknown fault can be distinguished, and further the fault is determined to be processed by the domain management equipment or the cross-domain management equipment, thereby realizing the cooperation of layered and domain-divided fault processing and improving the fault processing efficiency.

In one possible design, the determining, by the domain management device, first fault definition information of the first network fault according to the first fault information includes: the domain management equipment determines an abnormal network element corresponding to the first network fault according to the first fault information; and the domain management equipment determines first fault delimitation information of the first network fault according to the abnormal network element.

In a possible design, the determining, by the domain management device, an abnormal network element corresponding to the first network fault according to the first fault information includes: if the domain management device determines that the first network fault is caused by the abnormality of the local network element according to the fault type in the first fault information, determining the local network element 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 opposite-end network element of the local-end network element, the domain management device determines that the opposite-end network element is the abnormal network element; and the local network element is a network element which sends the first fault information to the domain management equipment.

In one possible design, the determining, by the domain management device, first fault definition information of the first network fault according to the abnormal network element includes: 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 delimiting information is in the domain; and when the abnormal network element is not the network element managed by the domain management device, the range of the first network fault indicated by the first fault delimiting information is out of domain.

In one possible design, the first fault information includes a fault type, and the determining, by the domain management device, first fault definition information of the first network fault according to the first fault information includes: the domain management equipment determines the first fault delimiting information according to a fault delimiting rule and the fault type; the fault delimiting rule comprises an incidence relation between the fault type and the first fault delimiting information.

In one possible design, the method further includes: the domain management equipment acquires configuration information and performance information of the first network fault associated object; the domain management device determines first fault definition information of the first network fault according to the first fault information, and the method comprises the following steps: and the domain management equipment determines 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.

In one possible design, the method further includes: the domain management equipment acquires at least one piece of second fault information, wherein one piece of second fault information in the at least one piece of second fault information corresponds to one second network fault; the domain management device determines first fault definition information of the first network fault according to the first fault information, and the method comprises the following steps: and the domain management equipment 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 piece of second fault information.

In one possible design, the processing, by the domain management device, the first network fault according to the first fault definition information includes: when the first fault delimiting information indicates that the range of the first network fault is in the domain, the domain management device performs root cause analysis or fault recovery processing on the first network fault; or, when the first fault delimiting information indicates that the range of the first network fault is outside the domain or an unknown domain, the domain management device sends the first fault delimiting information to a cross-domain management device.

In one possible design, the processing, by the domain management device, the first network fault according to the first fault definition information includes: and the domain management equipment sends the first fault delimiting information to cross-domain management equipment, and the cross-domain management equipment is instructed to process the first network fault according to the first fault delimiting information.

In one possible design, the domains include at least one of an access network domain, a core network domain, a transport domain, a data center domain, and a virtual resource domain.

In a second aspect, the present application further provides a communication device having any one of the methods provided for implementing the first aspect. The communication device may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units or units corresponding to the above functions.

In one possible implementation, the communication device includes: a processor configured to enable the communication apparatus to perform the respective functions of the network device in the above-illustrated method. The communication device may also include a memory, which may be coupled to the processor, that retains program instructions and data necessary for the communication device. Optionally, the communication apparatus further comprises an interface circuit, which is configured to support communication between the communication apparatus and a device such as a network device.

In one possible implementation, the communication device comprises corresponding functional units, each for implementing the steps in the above method. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

In a possible implementation manner, the structure of the communication device includes a processing unit and a communication unit, and these units may perform corresponding functions in the above method example, specifically refer to the description in the method provided in the first aspect, and are not described herein again.

In a third aspect, the present application provides a communication method, including: the method comprises the steps that cross-domain management equipment obtains at least one of first fault information and first fault delimiting information of a first network fault, wherein the first fault delimiting information is in a domain or outside the domain or an unknown domain; the cross-domain management equipment 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 delimiting information indicates whether the first network fault is located in the range of the cross-domain management equipment, and the second fault delimiting information is cross-domain and single-domain; or the second fault delimiting information indicates that the first network fault is located within the range of the first domain management device, and the second fault delimiting information is domain management device indicating information; and the cross-domain management equipment processes the first network fault according to the second fault delimitation information.

In the above process, the cross-domain fault or the single-domain fault is distinguished by determining the second fault delimiting information of the first network fault, so as to determine the equipment for processing the first network fault, thereby improving the fault processing efficiency.

In one possible design, the determining, by the cross-domain management device, second fault definition information of the first network fault according to the first fault definition information includes: when the first fault definition information is in a domain, the cross-domain management equipment determines that the second fault definition information indicates that the range of the first network fault is a single domain; or, when the first fault delimiting information is an out-of-domain or unknown domain, the first network fault has a related third network fault, and the fault delimiting information of the third network fault is in-domain, the cross-domain management device determines that the second fault delimiting information indicates that the range of the first network fault is a single domain; or, when the first fault delimiting information is an out-of-domain or unknown domain, the first network fault has a related third network fault, and the fault delimiting information of the third network fault is out-of-domain, the cross-domain management device determines that the second fault delimiting information indicates that the range of the first network fault is cross-domain.

In one possible design, the method further includes: when the cross-domain management device determines that the second fault definition information is cross-domain, the cross-domain management device indicates to a first domain management device that the second fault definition information is cross-domain, or the cross-domain management device indicates to the first domain management device to delete the first network fault, and the first domain management device is a device for sending the first fault information or the first fault definition information.

In one possible design, the first fault information includes a fault type, and the cross-domain management device determines, according to the first fault information, second fault definition information of the first network fault, including: the cross-domain management equipment determines the second fault delimiting information according to a fault delimiting rule and the fault type; the fault delimitation rule comprises an incidence relation between the fault type and the second fault delimitation information.

In one possible design, the processing, by the cross-domain management device, the first network fault according to the second fault definition information includes: when the second fault delimiting information is cross-domain, the cross-domain management equipment performs root cause analysis or fault recovery processing on the first network fault; or, when the second fault delimiting information is a single domain, the cross-domain management device determines the domain management device with the first network fault according to the first fault information, and instructs the domain management device to process the first network fault.

In one possible design, the single domain includes at least one of an access network domain, a core network domain, a transport domain, a data center domain, and a virtual resource domain.

In a fourth aspect, the present application further provides a communication device having a function of implementing any one of the methods provided in the third aspect. The communication device may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units or units corresponding to the above functions.

In one possible implementation, the communication device includes: a processor configured to enable the communication apparatus to perform the respective functions of the terminal device in the above-illustrated method. The communication device may also include a memory, which may be coupled to the processor, that retains program instructions and data necessary for the communication device. Optionally, the communication apparatus further comprises an interface circuit, which is configured to support communication between the communication apparatus and a device such as a network device.

In a possible implementation manner, the structure of the communication device includes a processing unit and a communication unit, and these units may perform corresponding functions in the above method example, specifically refer to the description in the method provided in the third aspect, and are not described herein again.

In a fifth aspect, a system is provided, comprising: the domain management equipment is used for acquiring first fault information of the first network fault; determining first fault delimitation information of the first network fault according to the first fault information; the first fault delimiting information indicates the range of the first network fault, and the first fault delimiting information is in a domain or outside the domain or an 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 cross-domain management equipment; the cross-domain management equipment is used for acquiring at least one of first fault information and first fault delimiting information of a first network fault, wherein the first fault delimiting information is in-domain or out-of-domain or unknown domain; 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 delimiting information indicates whether the first network fault is located in the range of the cross-domain management equipment, and the second fault delimiting information is cross-domain and single-domain; or the second fault delimiting information indicates that the first network fault is located within the range of the first domain management device, and the second fault delimiting information is domain management device indicating information; and processing the first network fault according to the second fault delimitation information.

In one possible design, the domain management device is specifically configured to: when the first fault delimiting information indicates that the range of the first network fault is in the domain, root cause analysis or fault recovery processing is carried out on the first network fault; or, when the first fault delimiting information indicates that the range of the first network fault is outside the domain or an unknown domain, sending the first fault delimiting information to the cross-domain management device.

In one possible design, the cross-domain management device is specifically configured to: when the second fault delimiting information is cross-domain, root cause analysis or fault recovery processing is carried out on the first network fault; or when the second fault delimiting information is a single domain, determining the domain management equipment with the first network fault according to the first fault information, and indicating the domain management equipment to process the first network fault.

In a sixth aspect, a communication apparatus is provided, where the communication apparatus may be the network device in the above method embodiment, or a chip disposed in the network device. The communication device comprises an interface circuit, a processor and optionally a memory. Wherein the memory is used for storing a computer program or instructions, and the processor is coupled with the memory and the interface circuit, and when the processor executes the computer program or instructions, the communication apparatus is caused to execute the method performed by the domain management device or the cross-domain management device in the above method embodiments.

In a seventh aspect, a computer program product is provided, the computer program product comprising: computer program code which, when run, causes the method performed by the domain management device in the above aspects to be performed.

In an eighth aspect, there is provided a computer program product comprising: computer program code which, when run, causes the method performed by the cross-domain management device in the above aspects to be performed.

In a ninth aspect, the present application provides a chip system, which includes a processor for implementing the functions of the domain management device in the method of the above aspects. In one possible design, the system-on-chip further includes a memory for storing program instructions and/or data. The chip system may be formed by a chip, or may include a chip and other discrete devices.

In a tenth aspect, the present application provides a chip system comprising a processor for implementing the functions of the cross-domain management device in the methods of the above aspects. In one possible design, the system-on-chip further includes a memory for storing program instructions and/or data. The chip system may be formed by a chip, or may include a chip and other discrete devices.

In an eleventh aspect, the present application provides a computer-readable storage medium storing a computer program that, when executed, implements the method performed by the domain management device in the above-described aspects.

In a twelfth aspect, the present application provides a computer-readable storage medium storing a computer program that, when executed, implements the method performed by the cross-domain management device in the above-described aspects.

Drawings

FIG. 1 is a schematic diagram of a system architecture suitable for use in embodiments of the present application;

fig. 2 is a schematic flow chart of a fault handling method according to an embodiment of the present disclosure;

fig. 3 is a schematic diagram of a fault flow process provided in an embodiment of the present application;

fig. 4 is a schematic flow chart of a fault handling method according to an embodiment of the present application;

fig. 5 is a schematic diagram of a fault determination provided in an embodiment of the present application;

FIG. 6 is a block diagram of a system architecture according to an embodiment of the present application;

FIG. 7 is a schematic structural diagram of an apparatus according to an embodiment of the present disclosure;

fig. 8 is a schematic structural diagram of an apparatus according to an embodiment of the present disclosure.

Detailed Description

The embodiments of the present application will be described in detail below with reference to the drawings attached hereto.

The embodiment of the application can be applied to various mobile communication systems, such as: 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, which are not limited herein.

For the convenience of understanding the embodiments of the present application, the system shown in fig. 1 is first taken as an example for detailed description. Fig. 1 shows a system architecture diagram suitable for the method provided by the embodiment of the present application. As shown in fig. 1, 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.

The BSS is oriented to business services and services, and provides functions and services such as charging, settlement, accounting, customer service, business, network monitoring, and the like. The BSS also comprises a work order system which is used for dispatching orders according to the fault information so as to further process the fault.

The cross-domain Management Function unit may be referred to as a Network Management Function (NMF) unit, a Network Slice Management Function (NSMF) unit, a cross-domain Management Data Analysis Function (MDAF) unit, a cross-domain Self-organizing Network Function (SON Function) unit, a cross-domain intention Management Function (sfdm) unit, or the like, and for convenience of description, the cross-domain Management Function unit is hereinafter referred to as a cross-domain Management Function unit. The cross-domain management function may provide one or more of the following management functions or management services:

managing the life cycle of the network; deployment of a network; fault management of the network, including but not limited to fault collection, fault identification, root cause analysis and fault handling, etc.; performance management of the network; configuration management of the network; ensuring a network; an optimization function of the network; translation of network Intent (Intent), etc.

The failure of the network includes failures of all components of the network, such as failures of components of sub-networks, network elements, network functions, cells, boards, chips, and the like. The network referred to in the embodiments of the present application may refer to a network including one or more network elements or sub-networks. The "intention" herein may refer to an intention of a Communication Service Provider (Intent-CSP) or an intention of a Communication Service Consumer (Intent-CSC).

It should be noted that the cross-domain management function unit may also provide one of the following management or services for the sub-networks:

lifecycle management of subnetworks; deployment of a subnetwork; fault management of a sub-network, including but not limited to fault collection, fault identification, root cause analysis, fault handling, etc., where a fault of a sub-network includes faults of all components of the sub-network, such as components of sub-networks, network elements, network functions, cells, boards, and chips, etc.; performance management of subnetworks; configuration management of subnetworks; ensuring a sub-network; optimization functions of the sub-networks; translation of sub-network intents, etc. A sub-network may here mean a sub-network consisting of a plurality of small sub-networks

The domain management function unit may also be referred to as a sub-network management function unit or a network element management function unit, and is hereinafter referred to as a domain management function unit. The domain management function unit may provide one or more of the following management functions or management services: lifecycle management of sub-networks or network elements; deployment of sub-networks or network elements; fault management of a sub-network or a network element, including but not limited to fault collection, fault identification, root cause analysis, fault handling, etc., wherein a fault of a sub-network includes faults of all components of the sub-network, such as faults of components of the sub-network, network elements, network functions, cell boards, chips, etc.; the failure of the network element includes the failure of all components of the network element, such as the failure of components of network function, cell single board, chip, etc.; performance management of sub-networks or network elements; ensuring a sub-network or a network element; optimization functions of a sub-network or network element, intent translation of a sub-network or network element, etc.

Wherein a sub-network here comprises one or more network elements. The sub-networks may also comprise sub-networks, i.e. one or more sub-networks constitute one larger sub-network.

Wherein the domain management function unit can be deployed in the following manner, but is not limited to the following:

1. classifying according to network types: an Access Network (RAN) Domain Management Function unit (Domain Management Function), a Core Domain Management Function unit (Core Domain Management Function), and a Transport Domain Management Function unit (Transport Domain Management Function); or a certain domain network management system can manage two or all of an access network, a core network and a transmission network;

2. dividing according to administrative regions: and a domain management function unit in a certain region, such as a shanghai domain management function unit, a beijing domain management function unit, and the like.

In the embodiment of the present application, a network element is an entity providing a network service, and includes a core network element, an access network element, and the like.

The core network elements include, but are not limited to: access and Mobility Management Function (AMF) Network elements, Session Management Function (SMF) Network elements, Policy Control Function (PCF) Network elements, Network data analysis Function (NWDAF) Network elements, Network warehouse Function (NRF) Network elements, gateways, and the like. The access network element includes, but is not limited to, a radio access device in various formats, for example, a next Generation base station (gNB) in an NR system, a next Generation Node B (evolved Node B, eNB), a Radio Network Controller (RNC) or a Node B (NB), a gNB or a transmission point (TRP or TP) in a 5G (NR) system, an antenna panel or a group (including multiple antenna panels) of base stations in the 5G system, or a network Node forming the gNB or the transmission point, such as a baseband device (BBU), or a DU under a centralized-distributed (CU-DU) architecture.

The network element may also provide one or more of the following management functions or management services: the method comprises the following steps of management of the life cycle of the network element, deployment of the network element, fault management of the network element, performance management of the network element, guarantee of the network element, optimization function of the network element, intention 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, fault processing, and the like, and the fault of the network element includes faults of all components of the network element, such as faults of components of a sub-network, a network element, a network function, a board, a chip, and the like.

It should be understood that the service management architecture focuses on the provider of the management service and the caller of the management service, as follows:

when the management service is the management service provided by the above cross-domain management unit, the cross-domain management unit is a management service provider (MnS provider), and the BSS is a management service provider (MnS provider).

When the management service is the management service provided by the domain management unit, the domain management unit is the management service provider, and the cross-domain management unit is the management service caller.

When the management service is the management service provided by the above network element, the network element is the management service provider, and the domain management unit is the management service caller.

In addition, in the embodiments of the present application, the word "exemplary" is used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, the term using examples is intended to present concepts in a concrete fashion.

The network architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person of ordinary skill in the art knows that along with the evolution of the network architecture and the appearance of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

The first embodiment is as follows:

referring to fig. 2, a schematic flow chart of a fault handling method provided in the embodiment of the present application is shown.

In fig. 2, the domain management device may refer to a domain management function unit in fig. 1. Of course, the cross-domain management function unit in fig. 1 may also execute the flow shown in fig. 2.

Step 201: the domain management device acquires first failure information of the first network failure.

Step 202: and the domain management equipment determines first fault delimitation information of the first network fault according to the first fault information.

Wherein the first fault delimiting information indicates a range of the first network fault.

Step 203: and the domain management equipment processes the first network fault according to the first fault delimitation information.

In the above process, the range of the first network fault can be determined by determining the first fault delimiting information of the first network fault, so that the first network fault can be further processed according to the range of the first network fault, and the fault processing efficiency can be improved.

In the first embodiment, the first fault definition information may be in-domain or out-of-domain or unknown domain, and is specifically determined according to actual conditions. The domain comprises 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: describing a radio access network provided by one or more radio access network devices (e.g. base stations); core network domain: describing a core network provided by one or more core network devices (e.g. Mobility Management Entity (MME), access and Mobility Management function (AMF)); a transmission network domain: describing a transport network provided by one or more transport devices (e.g. optical devices); in the data center domain: describe one or more data center provided Internet Protocol (IP) networks; virtual resource domain: a virtual network provided by one or more virtual resources (e.g. virtual machines) is described.

When the first fault delimiting information is in the domain, the first network fault is a fault caused by the abnormality of an object or a network element managed by the domain management equipment; when the first fault delimiting information is outside the domain, the first network fault is not a fault caused by the abnormality of the object or the network element managed by the domain management equipment; and when the first fault delimiting information is an unknown domain, the first network fault is represented as whether the first network fault is uncertain or not due to the fault caused by the abnormality of the object or the network element managed by the domain management equipment.

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

As can be seen from fig. 1, when the domain management device is a domain management functional unit, the domain management device manages a plurality of network elements.

In step 201, the first fault information acquired by the domain management device may include, but is not limited to, one or more of the following:

identifying a fault; a fault type; a fault generation network element indicating a network element in which a fault occurs; a root cause of the fault; the time of failure; a network element associated with a fault; and (4) fault grade.

The above is merely an example, and other contents may also be included in the first failure information, which is not illustrated herein one by one.

In this embodiment of the application, the domain management device may obtain the first fault information in a plurality of ways.

In a possible implementation manner, the device that generates the first fault information may actively report the first fault information to the domain management device.

For example, when the domain management device is a domain management functional 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 practical application, the domain management device may receive a plurality of fault information reported by a plurality of network elements.

Alternatively, the domain management device may also actively request the first fault management information from the network element it manages. For example, the domain management device may periodically send a request message, where the request message is used to request fault information, and a network element managed by the domain management device may report the fault information to the domain management device.

The above are only examples, and other cases are not described again.

In another possible implementation manner, the domain management device may collect at least one piece of network alarm information, and the domain management device may determine the first network fault corresponding to the at least one piece of network alarm information and obtain first fault information of the first network fault.

It should be noted that the domain management device may include a preset network fault template, where the network fault template includes network alarm information corresponding to a network fault. The domain management device may determine a network fault corresponding to the at least one piece of network alarm information in a preset network fault template as the first network fault.

Because different kinds of alarm information frequently appear in the existing network, the alarm information may be caused by a network fault, a network fault template can be preset, and the network fault can be rapidly positioned. For example, the network failure template may be as shown in table 1.

TABLE 1

Table 1 is merely an example, and other network failure templates may exist, which are not described herein.

In step 202, the domain management device may determine the first fault definition information in various ways, which is described in detail below.

In a first possible implementation manner, the domain management device may determine the first fault definition information according to at least one of a fault type and a fault generating network element in the first fault definition information.

For example, if it is determined that the first network fault is a fault due to a fault generating network element or a component abnormality in the fault generating network element according to the fault type of the first network fault, the first network fault may be determined to be a fault within the domain, that is, the first fault delimiting information is determined to be within the domain. For example, when the failure type of the first network failure is any one of the following, it may be determined that the first network failure is a failure within a domain: standing wave failure of the radio frequency unit; abnormal operation fault of radio frequency unit software; a battery failure; a single board clock input abnormal fault; configuration file corruption failures, etc.

For another example, the domain management device may determine the abnormal network element according to the fault type in the first fault delimiting information, so that the first fault delimiting information may be determined according to the abnormal network element.

How the domain management device determines the abnormal network element is not limited. For example, if it is determined 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 that the local network element is the abnormal local network element; if the domain management device determines that the first network fault is caused by the abnormality of the opposite-end network element of the local-end network element according to the fault type in the first fault information, determining the opposite-end network element as the abnormal network element; the local network element is a network element that sends the first fault information to the domain management device, and the opposite network element may be a network element that has a physical connection or data interaction with the local network element. The home network element and the opposite network element are relative concepts, and are not absolute concepts.

When it is determined that the abnormal network element is the network element managed by the domain management device, it may be determined that the first fault delimiting information is in a domain, that is, the first network fault is a fault in the domain; when it is determined that the abnormal network element is not the network element managed by the domain management device, it may be determined that the first fault delimiting information is outside the domain, that is, the first network fault is an outside-domain fault.

Further, some network faults are caused by the abnormality of the opposite-end network element of the network element due to the fault, and if the opposite-end network element is the network element in the local domain, it can be determined that the first network fault is a fault in the domain or a fault crossing the network element in the domain. Several possible faults of this type are exemplified below: and the terminal certificate expiration fault, the base station control plane transmission interruption alarm fault and the like.

The above are examples only, and other situations may exist, which are not illustrated one by one.

In a second possible implementation manner, the domain management device may determine the first fault definition information according to a fault definition rule.

The domain management device may determine, as the first fault delimiting information, the first fault delimiting information associated with the fault type of the first network fault in the fault delimiting rule.

For example, the fault definition rule includes the following association relations: and (4) the radio frequency unit software runs abnormal faults and associates the faults in the domain. When the first network fault is an abnormal operation fault of the radio frequency unit software, the first fault definition information can be determined to be in the domain.

Optionally, the fault delimiting rule may further include an association relationship between the network fault and the first fault delimiting information determining process.

Some network faults may be caused by the abnormality of the local network element, or may be caused by the abnormality of the opposite network element, or caused by other reasons, and there may be a related first fault delimiting information judgment flow for some network faults, so that the first fault delimiting information of the network fault can be determined according to the first fault delimiting information judgment flow.

For example, an Xn interface is an interface between network elements of an access network, and when a network failure is an Xn interface failure, the reasons for the Xn interface failure include the following possibilities:

1. an Xn interface configuration error, that is, an EP _ Xn object configuration information error included in the Local base station object or the peer base station object, such as a Local Internet Protocol (IP) address, a Virtual Local Area Network (VLAN) identifier, a Remote (Remote) IP address, and other configuration errors;

2. the local terminal base station or the opposite terminal base station is not configured with a complete cell list;

3. the home terminal base station is in a blacklist of the opposite terminal base stations;

4. the transmission link status is abnormal.

Therefore, as shown in fig. 3, when the network fault is an Xn interface fault, the first fault definition information determination process may include the following steps:

step 301: and acquiring fault information of the Xn interface fault.

Step 302: and judging whether the Xn interface configuration information and the cell list information of the local base station corresponding to the network fault are correct or not according to the fault information. If not, determining that the Xn interface fault is a fault in the domain or a fault of a network element in the domain; if so, step 303 is performed.

The home base station may refer to a base station that generates an Xn interface failure.

Step 303: judging whether the opposite terminal base station is in the local domain, if not, determining the opposite terminal base station is out of the domain as a fault; if so, step 304 is performed.

The opposite-end base station may refer to a base station with which the local-end base station has communication interaction.

Step 304: judging whether Xn interface information and cell list information of an opposite terminal base station are correct or not; if not, determining that the Xn interface fault is a fault in the domain or a fault of a cross network element in the domain; and if the failure is correct, determining that the Xn interface failure is out-of-domain failure.

It should be noted that the fault definition rule may be preconfigured, or may be obtained through other devices, for example, when the domain management device is a domain management functional unit, the fault definition rule may be received through a cross-domain management functional unit.

In a third possible implementation manner, the domain management device may obtain configuration information and performance information of the first network fault associated object. The configuration information may be a configuration parameter of a first network fault associated object, for example, an Xn fault associated object is a network element 1, a configuration parameter of the network element 1 is an IP address ═ X, and a VLAN ID ═ 2; the Performance information may be a Performance measurement quantity or a Key Performance Indicator (KPI) of the first network fault-related object, such as a packet loss rate, a delay, a transmission success rate, and the like.

And the domain management equipment determines 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.

In a fourth possible implementation manner, the domain management device may determine, according to the fault information of the other network faults, first fault definition information of the first network fault.

Specifically, the domain management device may obtain at least one piece of second fault information, where one piece of second fault information in the at least one piece of second fault information corresponds to one piece of second network fault, and the domain management device may determine, according to the first fault information of the first network fault and the at least one piece of second fault information, first fault definition information of the first network fault.

For example, the first network failure is a configuration error of the Xn interface, which may be, for example, that the configured IP address is inconsistent with the planned IP address, and the second network failure is a transmission link failure. If the first network failure is associated with a second network failure, the first network failure may be determined to be a failure within a domain.

The above is only an example, and the domain management device may also determine the first fault definition information of the first network fault according to other manners, which are not illustrated herein one by one.

In step 203, there may be one or more of the following ways for the domain management device to specifically handle the first network failure.

The first method is as follows: when the first fault definition information is in a domain, that is, a first network fault is a fault in the domain, the domain management device further processes the first network fault, including but not limited to root cause analysis, fault recovery processing, dispatch triggering manual intervention processing, and the like.

The second method comprises the following steps: when the first fault delimiting information is an 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, dispatching order triggering manual intervention and the like on the first network fault, but sends the first fault delimiting information to other devices. For example, when the domain management device is a domain management functional unit, the first fault definition information may be sent to a cross-domain management functional unit that manages the domain management device, and the domain management device may also send the first fault information to the cross-domain management functional unit.

The third method comprises the following steps: whether the first fault delimiting information is in a domain, outside the domain or unknown domain, the domain management equipment sends the first fault delimiting information to the cross-domain management equipment, and the cross-domain management equipment is instructed to process the first network fault according to the first fault delimiting information.

Further, in this embodiment of the application, the cross-domain management functional unit may perform the following processing on the first network fault according to the first fault definition information:

and when the first fault definition information is outside the domain or unknown domain, the cross-domain management functional unit triggers a corresponding fault analysis process. Specifically, the cross-domain management functional unit may perform a correlation analysis on the first network fault and a fault reported by another domain management functional unit (hereinafter, referred to as a second network fault).

If the first network failure is a failure of an unknown domain, is associated with a second network failure, and the second network failure is a failure in a domain, it may be determined that the first network failure is a failure outside the domain, and no further processing, including root cause analysis, failure recovery processing, or dispatching (triggering manual intervention processing), may be performed on the first network failure.

If the first network fault is a fault outside the domain or a fault of an unknown domain, is associated with the second network fault, and the second network fault is also a fault outside the domain or a fault of the unknown domain, it is determined that further processing needs to be performed on the first network fault, including cross-domain fault definition analysis, root cause analysis, fault recovery processing, or dispatching (triggering manual intervention processing), and the like.

If the first network fault is a fault outside the domain or a fault of an unknown domain and is not associated with a fault reported by any other domain management functional unit, it is determined that the first network fault needs to be further processed, including cross-domain fault delimitation analysis, root cause analysis, fault recovery processing or dispatching (triggering manual intervention processing) and the like.

Optionally, if the first network fault is a fault in the domain, the cross-domain management functional unit managing the domain management device may monitor the first network fault without further processing the first network fault.

Example two:

referring to fig. 4, a schematic flow chart of a fault handling method provided in the embodiment of the present application is shown.

In fig. 4, the cross-domain management device may refer to a cross-domain management functional unit in fig. 1.

Step 401: the cross-domain management device acquires at least one of first fault information and first fault definition information of the first network fault.

The first fault definition information is in-domain or out-of-domain or unknown domain;

in the second embodiment, the specific content of the first fault delimiting information may refer to the description in the first embodiment, and is not described herein again.

Step 402: and the cross-domain management equipment determines second fault delimitation information of the first network fault according to the first fault information or the first fault delimitation information.

In a possible implementation manner, the second fault delimiting information indicates whether the first network fault is located within a range of the cross-domain management device, and the second fault delimiting information is a cross-domain and a single-domain; in another possible implementation manner, the second fault delimiting information indicates that the first network fault is located within the range of the first domain management device, and the second fault delimiting information is domain management device indicating information.

The single domain comprises 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: describing a radio access network provided by one or more radio access network devices (e.g. base stations); core network domain: describing a core network provided by one or more core network devices (e.g. mme, AMF); a transmission network domain: describing a transport network provided by one or more transport devices (e.g. optical devices); in the data center domain: describing an IP network provided by one or more data centers; virtual resource domain: a virtual network provided by one or more virtual resources (e.g. virtual machines) is described.

In the second embodiment, when the second fault delimiting information corresponding to the first network fault is a single domain, it indicates that the first network fault is a fault caused by an abnormality occurring in an object or a network element managed by one domain management device managed by the cross-domain management device; when the second fault delimiting information corresponding to the first network fault is cross-domain, it indicates that the first network fault is a fault 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.

Further, when the second fault delimiting information is a single domain, the cross-domain management device may further determine, according to the first fault information, a network element in which the first network fault occurs, and information such as a domain management device that manages the network element, which may be specifically determined according to an actual situation, and is not described herein again.

Step 403: and the cross-domain management equipment processes the first network fault according to the second fault delimitation information.

As can be known from the above description, in the second embodiment, the first network failure may correspond to at least two types of second failure delimiting information, that is, the second failure delimiting information and the first failure delimiting information. The second fault delimiting information is used for describing the fault of the first network fault in which range of the cross-domain management device, and the first fault delimiting information is used for describing the fault of the first network fault in which range of the domain management functional unit managed by the cross-domain management device.

In step 401, at least one of the first fault information and the first fault delimiting information may be reported to the cross-domain management device by a domain management device managed by the cross-domain management device, and how the cross-domain management device specifically obtains at least one of the first fault information and the first fault delimiting information.

In step 402, the cross-domain management device may determine the second fault definition information in various ways, which is described in detail below.

In a first possible implementation manner, the cross-domain management device may determine the second fault definition information according to at least one of a fault type in the first fault information and a fault generating network element.

For example, if the fault type of the first network fault is a fault caused by an abnormality of a fault-generating network element or a component of the fault-generating network element, the first network fault may be determined to be a single-domain fault, that is, the second fault-delimiting information is determined to be a single domain. For example, when the failure type of the first network failure is any one of the following failures, the first network failure is a failure of a single domain: standing wave failure of the radio frequency unit; abnormal operation fault of radio frequency unit software; a battery failure; a single board clock input abnormal fault; configuration file corruption failures, etc.

In a second possible implementation manner, the cross-domain management device may determine the second fault definition information according to a fault definition rule.

The cross-domain management device may determine, as the second fault definition information, the fault definition information associated with the fault type of the first network fault in the fault definition rule.

Optionally, the fault definition rule may include an association relationship between the network fault and the second fault definition information judgment process.

Some network faults may be caused by the abnormality of the local network element, or may be caused by the abnormality of the opposite network element, or caused by other reasons, and there may be a second fault delimiting information judgment process associated with some network faults, so that the second fault delimiting information of the network fault can be determined according to the second fault delimiting information judgment process.

It should be noted that the fault definition rule may be preconfigured or acquired through other devices.

In a third possible implementation manner, the cross-domain management device may perform delimitation analysis according to the received at least one piece of fault information, so as to determine second fault delimitation information of the first network fault.

For example, as shown in fig. 5, the cross-domain management device manages 3 domain management function units, namely, a domain management function unit 1, a domain management function unit 2, and a domain management function unit 3. The cross-domain management device acquires the first failure information from the domain management functional unit 1. The cross-domain management device may further acquire 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.

Assuming 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.

If the first network fault is associated with both an Xn interface fault and a transmission link fault, 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 is matched with the Xn interface corresponding to the third network fault, it may be determined that the second fault definition information is a single domain, that is, the first network fault is a single domain fault; further, the first network failure is a failure of a single domain of the domain management function unit 3.

If the first network fault is associated with the third network fault, and there is no association relationship with a fourth network fault, and the Xn interface corresponding to the first network fault is not matched with the Xn interface corresponding to the third network fault, it may be determined that the second fault definition information is cross-domain, that is, the first network fault is a cross-domain fault;

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 wrong, for example, the configured IP address is inconsistent with the planned IP address, it may be determined that the second fault definition information is a single domain, that is, the first network fault is a single domain fault. Further, the first network failure is a failure of a single domain of the domain management function unit 1.

In a fourth possible implementation manner, the cross-domain management device may determine, according to the first fault definition information, second fault definition information of the first network fault.

For example, when the first fault definition information in the first fault information is an intra-domain fault, that is, the first network fault is an intra-domain fault, the cross-domain management device may determine that the second fault definition information is a single-domain fault, that is, the first network fault is a single-domain fault.

When the first network fault is a fault outside the domain or an unknown domain, that is, the first network fault is a fault outside the domain or a fault of the unknown domain, and when the first network fault has a related third network fault and the fault delimiting information of the third network fault is in the domain, the cross-domain management device may determine that the second fault delimiting information is a single domain, that is, the first network fault is a single-domain fault.

It should be noted that, in this case, the second fault delimiting information is a single domain, which indicates that the first network fault is a single domain fault of the domain management device reporting the third network fault, that is, the first network fault is a fault caused by an abnormality occurring to an object or a network element managed by the domain management device reporting the third network fault.

When the first network fault is a fault outside the domain or an unknown domain, that is, the first network fault is a fault outside the domain or a fault of the unknown domain, and when the first network fault has a related third network fault and the fault delimiting information of the third network fault is outside the domain, the cross-domain management device may determine that the second fault delimiting information is cross-domain, that is, the first network fault is a cross-domain fault.

The above are examples only, and other ways of determining may exist, which are not illustrated herein in a particular order.

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 may indicate to a domain management device that the second fault information is cross-domain, or the cross-domain management device indicates the domain management device to delete the first network fault, where the domain management device is a device that sends the first fault information.

When the cross-domain management device determines that the second fault definition information is a single domain, the cross-domain management device may also determine, according to the first fault information, a network element in which the first network fault occurs, and specifically how to determine, may be determined according to an actual situation.

In step 403, how the cross-domain management device processes the first network fault according to the second fault definition information may have multiple modes.

In a possible implementation manner, when the second fault delimiting information is a cross-domain fault, that is, when the first network fault is a cross-domain fault, the cross-domain management device performs root cause analysis on the first network fault;

in a possible implementation manner, the second fault delimiting information is a single domain, that is, the first network fault is a single domain fault, the cross-domain management device may determine, according to the first fault information, a network element in which the first network fault occurs, and the cross-domain management device may instruct the network element in which the first network fault occurs to process the first network fault. The network element with the first network fault may perform root cause analysis, fault recovery processing, and dispatching (triggering manual intervention processing) on the first network fault, and the cross-domain management device monitors the first network fault without further processing the first network fault.

It should be noted that the network element where the first network fault occurs may be a network element that sends the first fault information to the cross-domain management device, or may be another cross-domain management functional unit, which may be specifically determined according to an actual situation, and is not described herein again.

Through the process of the second embodiment, it can be known that how to process the first network fault can be accurately determined and the fault processing efficiency can be improved by further distinguishing whether the first network fault is a single-domain fault or a cross-domain fault, and further determining which domain the first network fault is, and further determining whether the first network fault is processed by the cross-domain management functional unit or the domain management functional unit in which the first network fault occurs.

Example three:

in the embodiment of the application, a cross-domain management functional unit or a domain management functional unit can open a fault query interface aiming at specific first fault delimiting information; the fault query interface for specific first fault delimiting information is applicable to the following two deployment scenarios:

scene one: the cross-domain management functional unit provides a fault query interface aiming at specific first fault delimiting information for a work order system or operation and maintenance personnel to query;

scene two: and the domain management functional unit provides a fault query interface aiming at the specific first fault definition information to the cross-domain management functional unit for querying.

The work order system or operation and maintenance personnel can send a fault query or subscription request to the cross-domain management function unit or the domain management function unit through a fault query interface, the fault query or subscription request carries first fault definition information, and the fault query or subscription request is used for requesting fault information corresponding to the first fault definition information.

If a fault query or a subscription request is sent to the domain management function unit, the first fault definition information includes at least one of the following: faults in the domain, faults outside the domain, faults of single network elements in the domain, faults of cross network elements in the domain, and faults of unknown domains.

If a fault query or a subscription request is sent to the cross-domain management function unit, the first fault definition information comprises at least one of the following: single domain fault, cross-domain fault, single network element fault, single domain multi-network element fault, unknown domain fault.

And the cross-domain management functional unit or the domain management functional unit determines corresponding fault information according to the first fault delimiting information and returns at least one piece of fault information corresponding to the first fault delimiting information.

By the method, the first fault definition information is introduced as the fault screening condition, so that the requirements of different users on network fault query can be met, for example, some cross-domain management functional units only care about cross-domain faults and only query or subscribe the cross-domain faults, and the query efficiency is improved.

Example four:

the embodiment of the present application further provides a system, which may specifically refer to fig. 6. The system comprises cross-domain management equipment and at least one domain management equipment. Wherein the cross-domain management device may manage the at least one domain management device, and each domain management device may manage at least one network element.

Optionally, step 601: and the cross-domain management equipment sends the fault delimiting rule to the domain management equipment.

If the cross-domain management device does not send the fault definition rule, the fault definition rule can be pre-configured in the domain management device in other ways.

Optionally, the cross-domain management device may further send a network failure template to the domain management device.

Step 602: the domain management equipment acquires at least one piece of fault information, wherein one piece of fault information in the at least one piece of fault information is information corresponding to one network fault.

The domain management device may obtain the at least one fault information from the network element managed by the domain management device in a plurality of ways, which may specifically refer to the foregoing description and will not be described herein again.

For convenience of description, the domain management device is described as an example of processing first failure information in the at least one piece of failure information, where the first failure information is any one of the at least one piece of failure information.

Step 603: and the domain management equipment determines first fault delimitation information of the first network fault according to the first fault information.

The first fault-delimiting information may be in-domain or out-of-domain or unknown domain.

Step 604: and the domain management equipment sends at least one item of the first fault information and the first fault delimitation information to cross-domain management equipment.

It should be noted that, when the first fault definition information is an intra-domain, the domain management device may not send the first fault information and the first fault definition information to the cross-domain management device.

Step 605: the domain management device processes the first network failure according to the first failure information.

Specifically, when the first fault definition information is in 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.

When the first fault delimiting information is outside the domain or unknown domain, the domain management equipment does not perform root cause analysis, fault recovery, dispatching sheet triggering manual intervention and other processing on the first network fault, but monitors the first network fault.

Step 606: the cross-domain management device may determine second fault delimiting information of the first network fault according to the first fault information or the first fault delimiting information, and process the first network fault according to the second fault delimiting information.

The specific content of step 606 may refer to the description in step 402 and step 403, and is not described herein again.

Optionally, the cross-domain management device may process the first network fault according to the first fault information. Specifically, when the first fault definition information is outside the domain or an unknown domain, the cross-domain management device triggers a corresponding fault analysis process. Specifically, the cross-domain management device may perform association analysis on the first network fault and a fault reported by another domain management device (hereinafter referred to as a second network fault).

If the first network failure is a failure of an unknown domain, is associated with a second network failure, and the second network failure is a failure within the domain, no further processing may be performed on the first network failure, including root cause analysis, failure recovery, or dispatching (triggering manual intervention processing).

If the first network fault is a fault outside the domain or a fault of an unknown domain, and is associated with the second network fault, and the second network fault is also a fault outside the domain or a fault of an unknown domain, the first network fault can be further processed, including cross-domain fault definition analysis, root cause analysis, fault recovery or dispatching (triggering manual intervention processing), and the like.

If the first network fault is a fault outside the domain or a fault of an unknown domain and is not associated with a fault reported by any other domain management device, the first network fault can be further processed, including cross-domain fault definition analysis, root cause analysis, fault recovery or dispatching (triggering manual intervention processing) and the like.

Optionally, if the first network fault is a fault in the domain, the cross-domain management device may monitor the first network fault and not further process the first network fault.

In the embodiments provided in the present application, the methods provided in the embodiments of the present application are introduced from the perspective of interaction between the domain management device and the cross-domain management device. In order to implement the functions in the method provided by the embodiment of the present application, the domain management device and the cross-domain management device may include a hardware structure and/or a software module, and the functions are implemented in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether any of the above-described functions is implemented as a hardware structure, a software module, or a hardware structure plus a software module depends upon the particular application and design constraints imposed on the technical solution.

Fig. 7 and 8 are schematic structural diagrams of a possible communication device provided in an embodiment of the present application. These communication devices can implement the functions of the domain management device or the cross-domain management device in the above method embodiments, and therefore, the advantageous effects of the above method embodiments can also be achieved.

As shown in fig. 7, the communication apparatus 700 includes a communication unit 701 and a processing unit 702. The communication apparatus 700 may be used to implement the functions of the domain management device or the cross-domain management device in the method embodiment shown in fig. 2.

When the communication apparatus 700 is used to implement the function of the domain management device in the embodiment of the method described in fig. 2:

a communication unit configured to acquire first failure information of a first network failure;

the processing unit is used for determining first fault delimitation information of the first network fault according to the first fault information; the first fault delimiting information indicates the range of the first network fault, and the first fault delimiting information is in a domain or outside the domain or an unknown domain; and processing the first network fault according to the first fault delimitation information.

In one possible design, the processing unit is specifically configured to:

determining an abnormal network element corresponding to the first network fault according to the first fault information;

and determining first fault delimitation information of the first network fault according to the abnormal network element.

In one possible design, the first failure information includes a failure type, and the processing unit is specifically configured to:

if the first network fault is determined to be caused by the abnormality of the local network element according to the fault type in the first fault information, determining the local network element 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 opposite-end network element of the local-end network element, determining the opposite-end network element as the abnormal network element;

and the local network element is a network element which sends the first fault information to the domain management equipment.

In one possible design, the processing unit is specifically configured to:

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 delimiting information is in the domain;

and when the abnormal network element is not the network element managed by the domain management device, the range of the first network fault indicated by the first fault delimiting information is out of domain.

determining the first fault delimiting information according to a fault delimiting rule and the fault type; the fault delimiting rule comprises an incidence relation between the fault type and the first fault delimiting information.

In one possible design, the communication unit is further configured to:

acquiring configuration information and performance information of the first network fault associated object;

the processing unit is specifically configured to:

and determining 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.

In one possible design, the communication unit is further configured to:

acquiring at least one piece of second fault information, wherein one piece of second fault information in the at least one piece of second fault information corresponds to one second network fault;

the processing unit is further to:

and determining 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 piece of second fault information.

In one possible design, the processing unit is specifically configured to:

when the first fault delimiting information indicates that the range of the first network fault is in the domain, root cause analysis or fault recovery processing is carried out on the first network fault; alternatively, the first and second electrodes may be,

and when the first fault delimitation information indicates that the range of the first network fault is out of the domain or an unknown domain, sending the first fault delimitation information to cross-domain management equipment.

When the communication apparatus 700 is used to implement the functions of the cross-domain management device in the method embodiment shown in fig. 4:

the communication unit is used for 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 in a domain or outside the domain or an unknown domain;

the processing unit is used for 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 delimiting information indicates whether the first network fault is located in the range of the cross-domain management equipment, and the second fault delimiting information is cross-domain and single-domain; or the second fault delimiting information indicates that the first network fault is located within the range of the first domain management device, and the second fault delimiting information is domain management device indicating information; and processing the first network fault according to the second fault delimitation information.

In one possible design, the processing unit is specifically configured to:

when the first fault delimiting information is in the domain, determining that the second fault delimiting information indicates that the range of the first network fault is in the single domain;

or, when the first fault delimiting information is an out-of-domain or unknown domain, the first network fault has a related third network fault, and the fault delimiting information of the third network fault is in-domain, determining that the second fault delimiting information indicates that the range of the first network fault is a single domain;

or, when the first fault delimiting information is an out-of-domain or unknown domain, the first network fault has a related third network fault, and the fault delimiting information of the third network fault is out-of-domain, it is determined that the second fault delimiting information indicates that the range of the first network fault is a cross-domain.

determining the second fault delimiting information according to a fault delimiting rule and the fault type; the fault delimitation rule comprises an incidence relation between the fault type and the second fault delimitation information.

In one possible design, the processing unit is specifically configured to:

when the second fault delimiting information is cross-domain, the first network fault is subjected to root cause analysis or fault recovery processing;

or when the second fault delimiting information is a single domain, determining the domain management equipment with the first network fault according to the first fault information, and indicating the domain management equipment to process the first network fault.

For a more detailed description of the communication unit 701 and the processing unit 702, reference may be made to the related description of the above method embodiments, which is not described herein.

As shown in fig. 8, communications device 800 includes a processor 810 and an interface circuit 820. Processor 810 and interface circuit 820 are coupled to each other. It is understood that interface circuit 820 may be a transceiver or an input-output interface. Optionally, the communication device 800 may further include a memory 830 for storing instructions to be executed by the processor 810 or for storing input data required by the processor 810 to execute the instructions or for storing data generated by the processor 810 after executing the instructions.

When the communication device 800 is configured to implement the method in the above method embodiments, the processor 810 is configured to perform the functions of the processing unit 702, and the interface circuit 820 is configured to perform the functions of the communication unit 701.

When the 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 embodiment. The terminal device chip receives information from other modules (such as a radio frequency module or an antenna) in the terminal device, wherein the information is sent to the terminal device by the network device; or, the terminal device chip sends information to other modules (such as a radio frequency module or an antenna) in the terminal device, where the information is sent by the terminal device to the network device.

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 above method embodiments. The network device chip receives information from other modules (such as a radio frequency module or an antenna) in the network device, wherein the information is sent to the network device by the terminal 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.

It is understood that the processor in the embodiments of the present application may be a Central Processing Unit (CPU), other general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The general purpose processor may be a microprocessor, but may be any conventional processor.

The method steps in the embodiments of the present application may be implemented by hardware, or may be implemented by software instructions executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash Memory, Read-Only Memory (ROM), programmable ROM, Erasable PROM (EPROM), Electrically EPROM (EEPROM), registers, a hard disk, a removable hard disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may reside in an access network device or a terminal device. Of course, the processor and the storage medium may reside as discrete components in an access network device or a terminal device.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer program or instructions may be stored in or transmitted over a computer-readable storage medium. The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server that integrates one or more available media. The usable medium may be a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape; or an optical medium, such as a DVD; it may also be a semiconductor medium, such as a Solid State Disk (SSD).

In the embodiments of the present application, unless otherwise specified or conflicting with respect to logic, the terms and/or descriptions in different embodiments have consistency and may be mutually cited, and technical features in different embodiments may be combined to form a new embodiment according to their inherent logic relationship.

In the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. In the description of the text of the present application, the character "/" generally indicates that the former and latter associated objects are in an "or" relationship; in the formula of the present application, the character "/" indicates that the preceding and following related objects are in a relationship of "division".

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method of fault handling, comprising:

the method comprises the steps that domain management equipment obtains first fault information of a first network fault;

the domain management equipment determines first fault delimitation information of the first network fault according to the first fault information; the first fault delimiting information indicates the range of the first network fault, and the first fault delimiting information is in a domain or outside the domain or an unknown domain;

and the domain management equipment processes the first network fault according to the first fault delimitation information.

2. The method of claim 1, wherein the determining, by the domain management device, first fault definition information of the first network fault according to the first fault information comprises:

the domain management equipment determines an abnormal network element corresponding to the first network fault according to the first fault information;

and the domain management equipment determines first fault delimitation information of the first network fault according to the abnormal network element.

3. The method according to claim 2, wherein the first fault information includes a fault type, and the determining, by the domain management device, an abnormal network element corresponding to the first network fault according to the first fault information includes:

if the domain management device determines that the first network fault is caused by the abnormality of the local network element according to the fault type in the first fault information, determining the local network element 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 opposite-end network element of the local-end network element, the domain management device determines that the opposite-end network element is the abnormal network element;

4. The method of claim 3, wherein the determining, by the domain management device, the first fault definition information of the first network fault according to the abnormal network element includes:

5. The method of claim 1, wherein the first fault information includes a fault type, and wherein the determining, by the domain management device and according to the first fault information, first fault definition information of the first network fault includes:

the domain management equipment determines the first fault delimiting information according to a fault delimiting rule and the fault type; the fault delimiting rule comprises an incidence relation between the fault type and the first fault delimiting information.

6. The method of claim 1, further comprising:

the domain management equipment acquires configuration information and performance information of the first network fault associated object;

the domain management device determines first fault definition information of the first network fault according to the first fault information, and the method comprises the following steps:

7. The method of claim 1, further comprising:

the domain management equipment acquires at least one piece of second fault information, wherein one piece of second fault information in the at least one piece of second fault information corresponds to one second network fault;

and the domain management equipment 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 piece of second fault information.

8. The method according to any one of claims 1 to 7, wherein the processing, by the domain management device, the first network fault according to the first fault definition information includes:

when the first fault delimiting information indicates that the range of the first network fault is in the domain, the domain management device performs root cause analysis or fault recovery processing on the first network fault; alternatively, the first and second electrodes may be,

and when the first fault delimitation information indicates that the range of the first network fault is out of the domain or an unknown domain, the domain management equipment sends the first fault delimitation information to cross-domain management equipment.

9. The method according to any one of claims 1 to 7, wherein the processing, by the domain management device, the first network fault according to the first fault definition information includes:

and the domain management equipment sends the first fault delimiting information to cross-domain management equipment, and the cross-domain management equipment is instructed to process the first network fault according to the first fault delimiting information.

10. The method of any of claims 1-9, wherein the domain comprises at least one of an access network domain, a core network domain, a transport domain, a data center domain, and a virtual resource domain.

11. A method of fault handling, comprising:

the method comprises the steps that cross-domain management equipment obtains at least one of first fault information and first fault delimiting information of a first network fault, wherein the first fault delimiting information is in a domain or outside the domain or an unknown domain;

the cross-domain management equipment 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 delimiting information indicates whether the first network fault is located in the range of the cross-domain management equipment, and the second fault delimiting information is cross-domain and single-domain; or the second fault delimiting information indicates that the first network fault is located within the range of the first domain management device, and the second fault delimiting information is domain management device indicating information;

and the cross-domain management equipment processes the first network fault according to the second fault delimitation information.

12. The method of claim 11, wherein the determining, by the cross-domain management device, second fault definition information of the first network fault according to the first fault definition information comprises:

when the first fault definition information is in a domain, the cross-domain management equipment determines that the second fault definition information indicates that the range of the first network fault is a single domain;

or, when the first fault delimiting information is an out-of-domain or unknown domain, the first network fault has a related third network fault, and the fault delimiting information of the third network fault is in-domain, the cross-domain management device determines that the second fault delimiting information indicates that the range of the first network fault is a single domain;

or, when the first fault delimiting information is an out-of-domain or unknown domain, the first network fault has a related third network fault, and the fault delimiting information of the third network fault is out-of-domain, the cross-domain management device determines that the second fault delimiting information indicates that the range of the first network fault is cross-domain.

13. The method of claim 12, further comprising:

when the cross-domain management device determines that the second fault definition information is cross-domain, the cross-domain management device indicates to a first domain management device that the second fault definition information is cross-domain, or the cross-domain management device indicates to the first domain management device to delete the first network fault, and the first domain management device is a device for sending the first fault information or the first fault definition information.

14. The method of claim 11, wherein the first fault information comprises a fault type, and wherein the cross-domain management device determines second fault definition information of the first network fault according to the first fault information, and wherein the determining comprises:

the cross-domain management equipment determines the second fault delimiting information according to a fault delimiting rule and the fault type; the fault delimitation rule comprises an incidence relation between the fault type and the second fault delimitation information.

15. The method according to any one of claims 11 to 14, wherein the processing, by the cross-domain management device, the first network fault according to the second fault definition information includes:

when the second fault delimiting information is cross-domain, the cross-domain management equipment performs root cause analysis or fault recovery processing on the first network fault;

or, when the second fault delimiting information is a single domain, the cross-domain management device determines the domain management device with the first network fault according to the first fault information, and instructs the domain management device to process the first network fault.

16. The method of any of claims 11-15, wherein the single domain comprises at least one of an access network domain, a core network domain, a transport domain, a data center domain, and a virtual resource domain.

17. A system, comprising:

the domain management equipment is used for acquiring first fault information of the first network fault; determining first fault delimitation information of the first network fault according to the first fault information; the first fault delimiting information indicates the range of the first network fault, and the first fault delimiting information is in a domain or outside the domain or an 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 cross-domain management equipment;

the cross-domain management equipment is used for acquiring at least one of first fault information and first fault delimiting information of a first network fault, wherein the first fault delimiting information is in-domain or out-of-domain or unknown domain; 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 delimiting information indicates whether the first network fault is located in the range of the cross-domain management equipment, and the second fault delimiting information is cross-domain and single-domain; or the second fault delimiting information indicates that the first network fault is located within the range of the first domain management device, and the second fault delimiting information is domain management device indicating information; and processing the first network fault according to the second fault delimitation information.

18. The system according to claim 17, wherein the domain management device is specifically configured to:

and when the first fault delimiting information indicates that the range of the first network fault is out of the domain or unknown domain, sending the first fault delimiting information to the cross-domain management equipment.

19. The system according to any one of claims 17 to 18, wherein the cross-domain management device is specifically configured to:

when the second fault delimiting information is cross-domain, root cause analysis or fault recovery processing is carried out on the first network fault;

20. A communications apparatus, comprising:

21. The apparatus according to claim 20, wherein the processing unit is specifically configured to:

22. The apparatus according to claim 21, wherein the first failure information includes a failure type, and the processing unit is specifically configured to:

23. The apparatus according to claim 22, wherein the processing unit is specifically configured to:

24. The apparatus according to claim 20, wherein the first failure information includes a failure type, and the processing unit is specifically configured to:

25. The apparatus of claim 20, wherein the communication unit is further configured to:

the processing unit is specifically configured to:

26. The apparatus of claim 20, wherein the communication unit is further configured to:

the processing unit is further to:

27. The apparatus according to any one of claims 20 to 26, wherein the processing unit is specifically configured to:

28. The apparatus according to any of claims 20-27, wherein the domain comprises at least one of an access network domain, a core network domain, a transport domain, a data center domain and a virtual resource domain.

29. A communications apparatus, comprising:

30. The apparatus according to claim 29, wherein the processing unit is specifically configured to:

31. The apparatus according to claim 29, wherein the first failure information includes a failure type, and the processing unit is specifically configured to:

32. The apparatus according to any of claims 29-31, wherein the single domain comprises at least one of an access network domain, a core network domain, a transport domain, a data center domain and a virtual resource domain.

33. A communications apparatus, comprising a processor and a memory:

the processor for executing a computer program or instructions stored in the memory, the computer program or instructions, when executed, causing the method of any one of claims 1 to 10 or 11 to 16 to be performed.

34. A chip comprising a processor coupled to a memory for executing a computer program or instructions stored in the memory, the method of any one of claims 1 to 10 or 11 to 16 being performed when the processor executes the computer program or instructions.