WO2021233224A1 - 一种故障处理方法、装置及系统 - Google Patents

一种故障处理方法、装置及系统 Download PDF

Info

Publication number
WO2021233224A1
WO2021233224A1 PCT/CN2021/093822 CN2021093822W WO2021233224A1 WO 2021233224 A1 WO2021233224 A1 WO 2021233224A1 CN 2021093822 W CN2021093822 W CN 2021093822W WO 2021233224 A1 WO2021233224 A1 WO 2021233224A1
Authority
WO
WIPO (PCT)
Prior art keywords
fault
domain
information
network
management device
Prior art date
Application number
PCT/CN2021/093822
Other languages
English (en)
French (fr)
Inventor
许瑞岳
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2021233224A1 publication Critical patent/WO2021233224A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/22—Arrangements for supervision, monitoring or testing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices

Definitions

  • This application relates to the field of communication technology, and in particular to a method, device and system for troubleshooting.
  • Network faults will directly affect business performance, and even cause business interruption. How to quickly detect and eliminate faults is one of the main challenges of operation and maintenance. In the prior art, network elements, domain management equipment, and cross-domain management equipment will perform cause analysis and fault repair functions on the collected faults/alarms. How to coordinate the fault handling capabilities of network elements, domain management equipment, and cross-domain management functions It is an urgent problem to improve the efficiency of overall network troubleshooting.
  • the embodiments of the present application provide a fault handling method, device and system to solve the problem of how to improve the efficiency of network fault handling.
  • the present application provides a method, including: a domain management device obtains first failure information of a first network failure; and the domain management device determines the first failure of the first network failure according to the first failure information Delimitation information; the first fault delimitation information indicates the scope of the first network failure, and the first fault delimitation information is within a domain or outside a domain or an unknown domain; the domain management device determines according to the first fault The boundary information processes the first network failure.
  • the domain management device determining the first fault delimitation information of the first network fault according to the first fault information includes: the domain management device determining the first fault delimitation information of the first network fault according to the first fault information The abnormal network element corresponding to the first network failure; the domain management device determines the first fault delimitation information of the first network failure according to the abnormal network element.
  • the first fault information includes a fault type
  • the domain management device determines the abnormal network element corresponding to the first network fault according to the first fault information, including: if the domain management device According to the failure type in the first failure information, it is determined that the first network failure is caused by the abnormality of the local network element, then the local network element is determined to be the abnormal network element; or, the domain management device If it is determined according to the fault type in the first fault information that the first network fault is caused by the abnormality of the opposite end network element of the local network element, then the opposite end network element is determined to be the abnormal network element. Element; wherein, the local network element is a network element that sends the first fault information to the domain management device.
  • the domain management device determines the first fault delimitation information of the first network failure according to the abnormal network element, including: when the abnormal network element is a network managed by the domain management device Element, the first network fault indicated by the first fault delimitation information is within the domain; when the abnormal network element is not a network element managed by the domain management device, the first fault delimitation information The indicated range of the first network failure is outside the domain.
  • the first fault information includes a fault type
  • the domain management device determines the first fault delimitation information of the first network fault according to the first fault information, including: the domain management The device determines the first fault delimitation information according to the fault delimitation rule and the fault type; the fault delimitation rule includes an association relationship between the fault type and the first fault delimitation information.
  • the method further includes: the domain management device obtains configuration information and performance information of the first network fault-associated object; and the domain management device determines the first network fault information according to the first fault information.
  • the first fault delimitation information of a network fault includes: the domain management device determines the first fault information according to the first fault information of the first network fault, the configuration information and performance information of the first network fault-associated object The first fault delimitation information of the network fault.
  • the method further includes: the domain management device acquires at least one second failure information, and one second failure information in the at least one second failure information corresponds to a second network failure; the The domain management device determines the first fault delimitation information of the first network fault according to the first fault information, including: the domain management device determines the first fault delimitation information of the first network fault according to the first fault information of the first network fault and the at least one first The second fault information determines the first fault delimitation information of the first network fault.
  • the domain management device processes the first network failure according to the first failure delimitation information, including: when the first failure delimitation information indicates the first network failure When the range is within a domain, the domain management device performs root cause analysis or failure recovery processing on the first network failure; or, when the first fault delimitation information indicates that the range of the first network failure is outside the domain or unknown In the domain, the domain management device sends the first fault demarcation information to the cross-domain management device.
  • the domain management device processing the first network fault according to the first fault delimitation information includes: the domain management device sends the first fault delimitation information to the cross-domain The management device instructs the cross-domain management device to process the first network fault according to the first fault delimitation information.
  • the domain includes at least one of an access network domain, a core network domain, a transmission domain, a data center domain, and a virtual resource domain.
  • the present application also provides a communication device that has any method provided in the first aspect.
  • the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or units corresponding to the above-mentioned functions.
  • the communication device includes a processor configured to support the communication device to perform the corresponding function of the network device in the method shown above.
  • the communication device may further include a memory, and the storage may be coupled with the processor, which stores program instructions and data necessary for the communication device.
  • the communication device further includes an interface circuit for supporting communication between the communication device and equipment such as network equipment.
  • the communication device includes corresponding functional units, which are respectively used to implement the steps in the above method.
  • the function can be realized by hardware, or the corresponding software can be executed by hardware.
  • the hardware or software includes one or more units corresponding to the above-mentioned functions.
  • the structure of the communication device includes a processing unit and a communication unit, and these units can perform corresponding functions in the foregoing method examples.
  • these units can perform corresponding functions in the foregoing method examples.
  • the present application provides a communication method, including: a cross-domain management device acquires at least one of first fault information of a first network fault and first fault delimitation information, where the first fault delimitation information is in-domain Or outside the domain or unknown domain; the cross-domain management device determines the second fault delimitation information of the first network fault according to the first fault information or the first fault delimitation information; the second fault delimitation The information indicates whether the first network fault is within the scope of the cross-domain management device, and the second fault delimitation information is cross-domain and single-domain; or, the second fault delimitation information indicates that the first The network fault is located within the range of the first domain management device, and the second fault delimitation information is domain management device indication information; the cross-domain management device performs operations on the first network fault according to the second fault delimitation information deal with.
  • the cross-domain fault or the single-domain fault is distinguished, and then the equipment that handles the first network fault is determined, and the efficiency of fault handling is improved.
  • the cross-domain management device determining the second fault delimitation information of the first network fault according to the first fault delimitation information includes: when the first fault delimitation information is in-domain When the cross-domain management device determines that the second fault delimitation information indicates that the range of the first network failure is a single domain; or, when the first fault delimitation information is an out-of-domain or unknown domain, and all When the first network fault has an associated third network fault, and when the fault delimitation information of the third network fault is within a domain, the cross-domain management device determines that the second fault delimitation information indicates the first network The scope of the fault is a single domain; or, when the first fault delimitation information is an out-of-domain or unknown domain, and the first network fault has an associated third network fault, the fault delimitation information of the third network fault When it is outside the domain, the cross-domain management device determines that the second fault delimitation information indicates that the range of the first network fault is cross-domain.
  • the method further includes: when the cross-domain management device determines that the second fault demarcation information is cross-domain, the cross-domain management device instructs the first domain management device to The second fault delimitation information is cross-domain, or the cross-domain management device instructs the first domain management device to delete the first network fault, and the first domain management device sends the first fault information or the first Equipment for fault delimitation information.
  • the first fault information includes a fault type
  • the cross-domain management device determines the second fault delimitation information of the first network fault according to the first fault information, including: The domain management device determines the second fault delimitation information according to the fault delimitation rule and the fault type; the fault delimitation rule includes an association relationship between the fault type and the second fault delimitation information.
  • the cross-domain management device processes the first network fault according to the second fault delimitation information, including: when the second fault delimitation information is cross-domain, the cross-domain The domain management device performs root cause analysis or fault recovery processing on the first network failure; or, when the second fault delimitation information is a single domain, the cross-domain management device determines the occurrence of the fault based on the first fault information.
  • the domain management device of the first network failure and instruct the domain management device to handle the first network failure.
  • the single domain includes at least one of an access network domain, a core network domain, a transmission domain, a data center domain, and a virtual resource domain.
  • the present application also provides a communication device having any method provided in the third aspect.
  • the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or units corresponding to the above-mentioned functions.
  • the communication device includes: a processor configured to support the communication device to perform corresponding functions of the terminal device in the method shown above.
  • the communication device may also include a memory, which may be coupled with the processor, which stores program instructions and data necessary for the communication device.
  • the communication device further includes an interface circuit for supporting communication between the communication device and equipment such as network equipment.
  • the communication device includes corresponding functional units, which are respectively used to implement the steps in the above method.
  • the function can be realized by hardware, or the corresponding software can be executed by hardware.
  • the hardware or software includes one or more units corresponding to the above-mentioned functions.
  • the structure of the communication device includes a processing unit and a communication unit, and these units can perform corresponding functions in the foregoing method examples.
  • these units can perform corresponding functions in the foregoing method examples.
  • a system including: a domain management device for acquiring first failure information of a first network failure; and determining first failure delimitation information of the first network failure according to the first failure information
  • the first fault delimitation information indicates the scope of the first network failure, and the first fault delimitation information is within the domain or outside the domain or unknown domain; when it is determined that the first fault delimitation information is outside the domain or unknown domain At least one of the first fault information and the first fault delimitation information is sent to the cross-domain management device; the cross-domain management device is used to obtain the first fault information and the first fault determination of the first network fault At least one of the boundary information, the first fault delimitation information is within the domain or outside the domain or unknown domain; the second fault of the first network fault is determined according to the first fault information or the first fault delimitation information Delimitation information; the second fault delimitation information indicates whether the first network fault is within the scope of the cross-domain management device, and the second fault delimitation information is cross-domain and single-domain;
  • the domain management device is specifically configured to perform root cause analysis on the first network failure when the first failure delimitation information indicates that the range of the first network failure is within the domain, or Fault recovery processing; or, when the first fault delimitation information indicates that the scope of the first network failure is outside the domain or an unknown domain, the first fault delimitation information is sent to the cross-domain management device.
  • the cross-domain management device is specifically configured to: when the second fault demarcation information is cross-domain, perform root cause analysis or failure recovery processing on the first network failure; or, the When the second fault delimitation information is a single domain, determine the domain management device where the first network fault has occurred according to the first fault information, and instruct the domain management device to handle the first network fault.
  • a communication device may be the network device in the foregoing method embodiment, or a chip set in the network device.
  • the communication device includes an interface circuit and a processor, and optionally, a memory.
  • the memory is used to store computer programs or instructions
  • the processor is coupled with the memory and the interface circuit.
  • the communication device is caused to execute the domain management equipment or cross-domain management in the above method embodiments. The method performed by the device.
  • a computer program product includes: computer program code, which when the computer program code is running, causes the methods executed by the domain management device in the above aspects to be executed.
  • a computer program product comprising: computer program code, when the computer program code is executed, the method executed by the cross-domain management device in the above aspects is executed.
  • the present application provides a chip system, which includes a processor, and is configured to implement the functions of the domain management device in the methods of the foregoing aspects.
  • the chip system further includes a memory for storing program instructions and/or data.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the present application provides a chip system, which includes a processor, and is configured to implement the functions of the cross-domain management device in the methods of the foregoing aspects.
  • the chip system further includes a memory for storing program instructions and/or data.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • this application provides a computer-readable storage medium that stores a computer program, and when the computer program is executed, the method executed by the domain management device in the above aspects is implemented.
  • this application provides a computer-readable storage medium that stores a computer program, and when the computer program is executed, the method executed by the cross-domain management device in the above aspects is implemented.
  • FIG. 1 is a schematic diagram of a system architecture applicable to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a fault handling method provided by an embodiment of the application
  • FIG. 3 is a schematic diagram of a failure process processing provided by an embodiment of the application.
  • FIG. 4 is a schematic flowchart of a fault handling method provided by an embodiment of the application.
  • FIG. 5 is a schematic diagram of a fault judgment provided by an embodiment of the application.
  • FIG. 6 is a schematic diagram of a system architecture provided by an embodiment of the application.
  • FIG. 7 is a schematic structural diagram of a device provided by an embodiment of the application.
  • FIG. 8 is a schematic structural diagram of an apparatus provided by an embodiment of the application.
  • NR new radio
  • LTE long term evolution
  • LTE-A advanced long term evolution
  • future communication systems future communication systems, and other communication systems, specifically, are not limited here.
  • FIG. 1 shows a schematic diagram of a system architecture suitable for the method provided in the embodiment of the present application.
  • the system includes a business support system (Business Support System, BSS), a cross-domain management function (Cross Domain Management Function, CD-MnF) unit, a domain management function (Domain Management Function, Domain-MnF) unit, and Multiple network elements, etc.
  • BSS Business Support System
  • CD-MnF Cross-domain management function
  • Domain Management Function Domain Management Function
  • Domain-MnF Domain Management Function
  • Multiple network elements etc.
  • BSS is oriented to operators' businesses and services, and provides functions and services such as billing, settlement, accounting, customer service, business, and network monitoring.
  • BSS also includes a work order system.
  • the work order system is used to dispatch orders based on the fault information, and then the fault handlers.
  • the cross-domain management function unit may be called a network management function (NMF) unit, a network slice management function (NSMF) unit or a cross-domain management data analysis function (Management data analysis function, MDAF) unit or cross-domain self-organization network function (Self-Organization Network Function, SON Function) unit or cross-domain intention management functional unit, etc., for convenience of description, are referred to as cross-domain management functional unit below.
  • NMF network management function
  • NSMF network slice management function
  • MDAF cross-domain management data analysis function
  • SON Function Self-Organization Network Function
  • cross-domain intention management functional unit etc.
  • the cross-domain management function unit can provide one or more of the following management functions or management services:
  • Network life cycle management ; network deployment; network fault management, including but not limited to fault collection, fault identification, root cause analysis and fault handling, etc.; network performance management; network configuration management; network guarantee; network optimization Function; translation of network intent, etc.
  • network failures include failures of all components of the network, such as failures of sub-networks, network elements, network functions, cells, boards, and chips.
  • the network involved in the embodiments of the present application may refer to one or more network elements or sub-networks.
  • the "intent” here may refer to the intent of the communication service provider (Intent From Communication Service Provider, Intent-CSP), or the intent of the communication service consumer (Intent From Communication Service Consumer, Intent-CSC).
  • cross-domain management function unit can also provide one of the following management or services for the sub-network:
  • the faults of the sub-network include the faults of all components of the sub-network, for example Sub-networks, network elements, network functions, cells, boards, chips and other components; performance management of sub-networks; configuration management of sub-networks; guarantee of sub-networks; optimization functions of sub-networks; translation of sub-network intents, etc.
  • the sub-network here may refer to a plurality of small sub-networks.
  • the domain management functional unit may also be referred to as a sub-network management functional unit or a network element management functional unit, and is referred to as a domain management functional unit hereinafter.
  • the domain management function unit can provide one or more of the following management functions or management services: life cycle management of sub-networks or network elements; deployment of sub-networks or network elements; fault management of sub-networks or network elements, including but not limited to failures Collection, fault identification, root cause analysis and fault handling, etc.
  • the faults of the sub-network include the faults of all components of the sub-network, such as the faults of the sub-networks, network elements, network functions, cell boards, chips and other components; Failures include failures of all components of this network element, such as failures of network functions, cell boards, chips and other components; performance management of sub-networks or network elements; protection of sub-networks or network elements; optimization functions of sub-networks or network elements, Intent translation of sub-networks or network elements, etc.
  • sub-network here includes one or more network elements.
  • Sub-networks can also include sub-networks, that is, one or more sub-networks form a larger sub-network.
  • the domain management functional unit can be deployed in the following ways, but not limited to the following:
  • Access Network Radio Access Network, RAN
  • domain management function unit Domain Management Function
  • core domain management function unit Core Domain Management Function
  • transmission network domain management function unit Transport Domain Management Function
  • domain management functional unit in a certain area such as Shanghai domain management functional unit, Beijing domain management functional unit, etc.
  • the network element is an entity that provides network services, including core network network elements and access network network elements.
  • 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 (Policy Control Function) , PCF) network elements, network data analysis function (NWDAF) network elements, network repository function (Network Repository Function, NRF) network elements, gateways, etc.
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • Policy Control Function Policy Control Function
  • PCF Policy Control Function
  • NWDAF network data analysis function
  • NRF Network Repository Function
  • the access network elements include, but are not limited to, wireless access equipment under various standards, such as the next-generation base station (next Generation node B, gNB) in the NR system, or evolved Node B (evolved Node B, eNB) , Radio network controller (RNC) or node B (Node B, NB), it can also be the gNB or transmission point (TRP or TP) in the 5G (NR) system, one or one of the base stations in the 5G system A set of antenna panels (including multiple antenna panels), or, it can also be a network node that constitutes a gNB or transmission point, such as a baseband equipment (BBU), or in a centralized unit-distributed (CU-DU) DU etc. under the architecture.
  • next-generation base station gNB
  • eNB evolved Node B
  • RNC Radio network controller
  • Node B, NB Node B
  • TRP transmission point
  • TP transmission point
  • BBU baseband equipment
  • Network elements can also provide one or more of the following management functions or management services: network element life cycle management, network element deployment, network element fault management, network element performance management, network element protection, and network element optimization Function, intention translation of network elements, etc.
  • the fault management of the network element includes, but is not limited to, fault collection, fault identification, root cause analysis, and fault handling.
  • the fault of the network element includes the faults of all components of the network element, such as sub-networks, network elements, network functions, The board, chip, and other components are faulty.
  • the cross-domain management unit is the management service producer (management service producer, MnS producer), and the BSS is the management service consumer (management service consumer, MnS consumer).
  • the domain management unit is the management service provider
  • the cross-domain management unit is the management service caller
  • the management service is the management service provided by the above network elements
  • the network element is the management service provider
  • the domain management unit is the management service caller
  • the word "exemplary” is used to mean serving as an example, illustration, or illustration. Any embodiment or design solution described as an "example” in this application should not be construed as being more preferable or advantageous than other embodiments or design solutions. Rather, the term example is used to present the concept in a concrete way.
  • FIG. 2 is a schematic flowchart of a fault handling method provided by an embodiment of this application.
  • the domain management device may refer to the domain management functional unit in FIG. 1.
  • the cross-domain management function unit in FIG. 1 can also execute the process shown in FIG. 2.
  • Step 201 The domain management device obtains the first failure information of the first network failure.
  • Step 202 The domain management device determines first fault delimitation information of the first network fault according to the first fault information.
  • the first fault delimitation information indicates the range of the first network fault.
  • Step 203 The domain management device processes the first network fault according to the first fault delimitation information.
  • the scope of the first network fault can be determined, so that the first network fault can be further processed according to the scope of the first network fault, and the fault handling can be improved. efficient.
  • the first fault delimitation information may be in-domain or outside-domain or unknown domain, which is specifically determined according to actual conditions.
  • the domain includes at least one of an access network domain, a core network domain, a transmission domain, a data center domain, and a virtual resource domain.
  • access network domain describes the wireless access network provided by one or more wireless access network devices (eg base stations); core network domain: describes one or more core network devices (eg mobility management entities) Management Entity, MME), access and mobility management function (access and mobility management function (AMF)) provided by the core network; transmission network domain: describes the transmission network provided by one or more transmission equipment (eg optical equipment); data In the central domain: describe the internet protocol (IP) network provided by one or more data centers; virtual resource domain: describe the virtual network provided by one or more virtual resources (eg virtual machines).
  • IP internet protocol
  • virtual resource domain describe the virtual network provided by one or more virtual resources (eg virtual machines).
  • the scope of the first network failure when the scope of the first network failure is within a domain, it can also be divided into failures of intra-domain network elements and intra-domain cross-network element failures; among them, the failure of intra-domain network elements indicates that an object in the network element is abnormal. Faults, and cross-network element faults within a domain indicate a fault caused by an abnormality of objects between different network elements in the domain.
  • the domain management device when the domain management device is a domain management functional unit, the domain management device manages multiple network elements.
  • the first fault information acquired by the domain management device may include, but is not limited to, one or more of the following:
  • fault identification Fault identification; fault type; fault-generating network element, indicating the network element that failed; the root cause of the failure; the time of the failure; the network element related to the failure; the level of the failure.
  • first fault information may also include other content, which will not be illustrated one by one here.
  • the domain management device may obtain the first fault information in multiple ways.
  • the device that generates the first failure information can actively report the first failure information to the domain management device.
  • the domain management device 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 applications, the domain management device can receive multiple fault information reported by multiple network elements.
  • 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, the request message is used to request fault information, and the network element managed by the domain management device can thereby report the fault information to the domain management device management.
  • the domain management device may collect at least one piece of network alarm information, and the domain management device may determine the first network failure corresponding to the at least one piece of network alarm information, and obtain information about the first network failure. The first fault information.
  • the domain management device may include a preset network failure template, and the network failure template includes network alarm information corresponding to the network failure.
  • the domain management device may determine a network failure corresponding to the at least one piece of network alarm information in a preset network failure template as the first network failure.
  • a network failure template can be set in advance, so that the network failure can be quickly located.
  • the network fault template can be as shown in Table 1.
  • Table 1 is just an example, and there may be other network fault templates, so I won't repeat them here.
  • the domain management device may determine the first fault delimitation information in multiple ways, which will be described in detail below.
  • the domain management device may determine the first fault delimitation information according to at least one of the fault type and the fault generating network element in the first fault delimitation information.
  • the first network fault is an intra-domain fault , That is, the first fault delimitation information is determined to be within the domain.
  • the failure type of the first network failure is any of the following, it can be determined that the first network failure is an intra-domain failure: standing wave failure of the radio frequency unit; abnormal operation of the radio frequency unit software failure; battery failure; abnormal single board clock input failure; The configuration file is damaged, etc.
  • the domain management device may determine the abnormal network element according to the fault type in the first fault delimitation information, so that the first fault delimitation information may be determined according to the abnormal network element.
  • the domain management device determines the abnormal network element is not limited. For example, if the domain management device determines that the first network failure is caused by the abnormality of the local network element according to the failure type in the first failure information, it determines that the local network element is the abnormal network element ; If the domain management device determines that the first network failure is caused by the abnormality of the opposite network element of the local network element according to the fault type in the first fault information, then the opposite network element Determined to be the abnormal network element; wherein, the local network element is the network element that sends the first fault information to the domain management device, and the opposite network element may be physically connected to the local network element Or the network element for data interaction.
  • the local network element and the opposite network element are relative concepts, not absolute concepts.
  • the first fault delimitation information is within the domain, that is, the first network failure is an intra-domain failure; when it is determined that the abnormal network element is not the When the domain manages the network element managed by the device, it may be determined that the first fault delimitation information is outside the domain, that is, the first network fault is an outside fault.
  • some network failures are caused by the abnormality of the opposite network element of the network element that caused the fault. If the opposite network element is a network element in the local domain, it can be determined that the first network fault is an intra-domain fault or a cross-network element in the domain. Fault.
  • the domain management device may determine the first fault delimitation information according to the fault delimitation rule.
  • the fault delimitation rule may include an association relationship between the fault type and the first fault delimitation information
  • the domain management device may include the first fault delimitation information associated with the fault type of the first network fault in the fault delimitation rule Determined as the first fault delimitation information
  • the fault delimitation rules include the following association relationships: abnormal operation of the radio frequency unit software, and faults in the associated domain. Then, when the first network failure is an abnormal operation of the radio frequency unit software, it can be determined that the first failure delimiting information is within the domain.
  • the fault delimitation rule may also include an association relationship between the network fault and the first fault delimitation 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 peer network element, or caused by other reasons. Some network faults may have an associated first fault delimitation information judgment process, thus The first fault delimitation information of the network fault can be determined according to the first fault delimitation information judgment process.
  • the Xn interface is the interface between the network elements of the access network.
  • the causes of the Xn interface failure include the following possibilities:
  • Xn interface configuration error that is, the EP_Xn object configuration information contained in the local base station object or the opposite base station object is incorrect, such as the local Internet Protocol (IP) address, virtual local area network (Virtual Local Area Network, VLAN) identification , Remote (Remote) IP address and other configuration errors;
  • IP Internet Protocol
  • VLAN Virtual Local Area Network
  • Remote (Remote) IP address and other configuration errors
  • the local base station or the opposite base station is not configured with a complete cell list
  • the transmission link status is abnormal.
  • the first fault delimitation information judgment process may include the following steps:
  • Step 301 Obtain the fault information of the Xn interface fault.
  • Step 302 Determine whether the Xn interface configuration information and cell list information of the local base station corresponding to the network fault are correct according to the fault information. If it is not correct, it is determined that the Xn interface failure is an intra-domain failure or an intra-domain network element failure; if it is correct, step 303 is executed.
  • the local base station may refer to the base station that has the Xn interface failure.
  • Step 303 Determine whether the peer base station is in the local domain, if not, it is determined as an out-of-domain fault; if it is, then step 304 is executed.
  • the opposite base station may refer to a base station that communicates with the local base station.
  • Step 304 Determine whether the Xn interface information and cell list information of the peer base station are correct; if they are not correct, determine that the Xn interface failure is an intra-domain failure or a cross-network element failure within the domain; if it is correct, determine that the Xn interface failure is an out-of-domain failure Fault.
  • the fault delimitation rule can be pre-configured or acquired through other devices.
  • the domain management device is a domain management functional unit
  • the fault delimitation rule can be received through a cross-domain management functional unit.
  • the domain management device may obtain the configuration information and performance information of the first network fault-associated object.
  • KPI Key Performance Indicator
  • the domain management device determines the first fault delimitation information of the first network fault according to the first fault information of the first network fault, and the configuration information and performance information of the object associated with the first network fault.
  • the domain management device may determine the first fault delimitation information of the first network fault according to the fault information of other network faults.
  • the domain management device may obtain at least one second failure information, one of the second failure information in the at least one second failure information corresponds to a second network failure, and the domain management device may obtain the first network failure according to the first network failure.
  • a fault information and the at least one second fault information determine the first fault delimitation information of the first network fault.
  • the first network failure is a configuration error of the Xn interface, for example, the configured IP address may be inconsistent with the planned IP address, and the second network failure is a transmission link failure. If the first network failure is associated with the second network failure, it can be determined that the first network failure is an intra-domain failure.
  • the domain management device may also determine the first fault delimitation information of the first network fault according to other methods, which will not be described one by one here.
  • step 203 there may be one or more of the following methods for specifically how the domain management device handles the first network failure.
  • Method 1 When the first fault delimitation information is within a domain, that is, when the first network fault is an intra-domain fault, the domain management device performs further processing on the first network fault, including but not limited to root cause analysis, Fault recovery processing and dispatching orders trigger manual intervention processing and other operations.
  • the domain management device When the first fault delimitation information is an out-of-domain or unknown domain, that is, when 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 and fault recovery processing on the first network fault Dispatch orders to trigger manual intervention and other processing, but send the first fault demarcation information to other devices.
  • the domain management device is a domain management function unit
  • the first fault delimitation information may be sent to the cross-domain management function unit that manages the domain management device, and the domain management device may also send the first fault information to the cross-domain management function. unit.
  • the domain management device sends the first fault delimitation information to the cross-domain management device, and instructs the cross-domain management device according to the first fault
  • the delimitation information processes the first network failure.
  • the cross-domain management function unit may perform the following processing on the first network fault according to the first fault delimitation information:
  • the cross-domain management function unit triggers the corresponding fault analysis process.
  • the cross-domain management function unit may perform correlation analysis on the first network fault and the faults reported by other domain management function units (hereinafter referred to as the second network fault).
  • the first network failure is a failure of an unknown domain and is associated with a second network failure
  • the second network failure is an intra-domain failure
  • the first network fault is an out-of-domain fault or a fault in an unknown domain, and is associated with a second network fault, and the second network fault is also an out-of-domain fault or an unknown domain fault, it is determined that further processing is required for the first network fault, Including cross-domain fault delimitation analysis, root cause analysis, fault recovery processing or dispatching (triggering manual intervention processing) and other processing.
  • the first network fault is an out-of-domain fault or an unknown domain fault, and is not associated with any fault reported by any other domain management function unit, it is determined that further processing of the first network fault is required, including cross-domain fault delimitation analysis and root cause Analysis, fault recovery processing or dispatching (triggering of manual intervention processing) and other processing.
  • the cross-domain management function unit that manages the domain management device may monitor the first network fault and not perform further processing on the first network fault.
  • FIG. 4 is a schematic flowchart of a fault handling method provided by an embodiment of this application.
  • the cross-domain management device may refer to the cross-domain management functional unit in FIG. 1.
  • Step 401 The cross-domain management device acquires at least one of the first fault information of the first network fault and the first fault delimiting information.
  • the first fault delimitation information is in-domain or outside-domain or unknown domain
  • the specific content of the first fault delimitation information can be referred to the description in the first embodiment, which will not be repeated here.
  • Step 402 The cross-domain management device determines second fault demarcation information of the first network fault according to the first fault information or the first fault delimitation information.
  • the second fault delimitation information indicates whether the first network fault is within the scope of the cross-domain management device, and the second fault delimitation information is cross-domain and single Domain;
  • the second fault delimitation information indicates that the first network fault is located within the range of the first domain management device, and the second fault delimitation information is the domain management device indication information .
  • a single domain includes at least one of an access network domain, a core network domain, a transmission domain, a data center domain, and a virtual resource domain.
  • access network domain describes the wireless access network provided by one or more wireless access network equipment (eg base stations);
  • core network domain describes the wireless access network provided by one or more core network equipment (egMME, AMF) Core network;
  • Transmission network domain Describe the transmission network provided by one or more transmission equipment (eg optical equipment);
  • In the data center domain Describe the IP network provided by one or more data centers;
  • Virtual resource domain Describe one or more virtual The virtual network provided by the resource (eg virtual machine).
  • the second fault delimitation information corresponding to the first network fault when the second fault delimitation information corresponding to the first network fault is a single domain, it means that the first network fault is caused by an abnormality in an object or network element managed by a domain management device managed by a cross-domain management device
  • the second fault delimitation information corresponding to the first network fault is cross-domain, it means that the first network fault is caused by an abnormality in the objects or network elements managed by at least two domain management devices managed by the cross-domain management device Fault.
  • the cross-domain management device can also determine the network element where the first network failure occurs according to the first fault information, and the domain management device that manages the network element, etc., which can be specifically based on The actual situation is determined, so I won't repeat it here.
  • Step 403 The cross-domain management device processes the first network fault according to the second fault demarcation information.
  • the first network fault may correspond to at least two types of second fault delimitation information, that is, the second fault delimitation information and the first fault delimitation information.
  • the second fault delimitation information is used to describe the first network fault within which range of the cross-domain management device fault
  • the first fault delimitation information is used to describe the first network fault in the domain management function unit managed by the cross-domain management device Within which range of the fault.
  • step 401 at least one of the first fault information and the first fault delimitation information may be reported to the cross-domain management device by the domain management device managed by the cross-domain management device. How does the cross-domain management device obtain the first At least one of the fault information and the first fault delimitation information is not limited in this embodiment of the present application, and will not be repeated here.
  • the cross-domain management device may determine the second fault delimitation information in multiple ways, which will be described in detail below.
  • the cross-domain management device may determine the second fault delimitation information according to at least one of the fault type and the fault generating network element in the first fault information.
  • the fault type of the first network fault is a fault caused by a fault-generating network element or an abnormal component of the fault-generating network element
  • the first network fault is a single-domain fault, that is, the second fault setting can be determined.
  • the world information is a single domain.
  • the fault type of the first network fault is any of the following faults
  • the first network fault is a single-domain fault: standing wave failure of the radio frequency unit; abnormal operation of the radio frequency unit software; battery failure; abnormal single board clock input failure; configuration File damage failure, etc.
  • the cross-domain management device may determine the second fault delimitation information according to the fault delimitation rule.
  • the fault delimitation rule may include an association relationship between the fault type and the second fault delimitation information
  • the cross-domain management device may determine the fault delimitation information associated with the fault type of the first network fault in the fault delimitation rule Delimit information for the second fault.
  • the fault delimitation rule may include an association relationship between the network fault and the second fault delimitation information judgment process.
  • Some network failures may be caused by the abnormality of the local network element, or may be caused by the abnormality of the peer network element, or caused by other reasons. Some network failures may have an associated second fault delimitation information judgment process, thus The second fault delimitation information of the network fault can be determined according to the second fault delimitation information judgment process.
  • fault delimitation rules can be pre-configured or acquired through other devices.
  • the cross-domain management device may perform delimitation analysis according to the received at least one failure information, so as to determine the second failure delimitation information of the first network failure.
  • the cross-domain management device manages three domain management functional units, which are domain management functional unit 1, domain management functional unit 2, and domain management functional unit 3.
  • the cross-domain management device obtains the first fault information from the domain management functional unit 1.
  • the cross-domain management device may also obtain the third fault information of the third network fault through the domain management function unit 2 and the fourth fault information of the fourth network fault through the domain management function unit 3.
  • the fourth network failure is a transmission link failure.
  • the first network failure is associated with the Xn interface failure and the transmission link failure, for example, the first network failure is associated with the third network failure and the fourth network failure, and the first network failure corresponds to If the Xn interface matches the Xn interface corresponding to the third network fault, it can be determined that the second fault demarcation information is a single domain, that is, the first network fault is a single domain fault; further, the first network fault It is the failure of the single domain of the domain management functional unit 3.
  • the second fault demarcation information is cross-domain, that is, the first network fault is a cross-domain fault
  • the first network failure is associated with the third network failure, there is no association relationship with the fourth network failure, and the configuration of the Xn interface corresponding to the first network failure is incorrect, such as the configured IP address and the planned IP If the addresses are inconsistent, it can be determined that the second fault delimitation information is a single domain, that is, the first network fault is a single domain fault. Further, the first network failure is a single domain failure of the domain management function unit 1.
  • the cross-domain management device may determine the second fault delimitation information of the first network fault according to the first fault delimitation information.
  • the first fault demarcation information in the first fault information is within a domain, that is, when the first network fault is an intra-domain fault
  • the cross-domain management device may determine that the second fault delimitation information is a single domain, that is, the first network fault is a single domain.
  • a network failure is a single domain failure.
  • the first fault delimitation information in the first fault information is an out-of-domain or unknown domain, that is, when the first network fault is an out-of-domain fault or an unknown domain fault, when the first network fault has an associated third network fault, the first network fault
  • the cross-domain management device may determine that the second fault delimitation information is a single domain, that is, the first network fault is a single domain fault.
  • the second fault delimitation information is a single domain, which means that the first network fault is a single domain fault of the domain management device that reported the third network fault, that is, the first network fault is the third network reported.
  • the first fault delimitation information in the first fault information is an out-of-domain or unknown domain, that is, when the first network fault is an out-of-domain fault or an unknown domain fault, when the first network fault has an associated third network fault, the first network fault 3.
  • the cross-domain management device may determine that the second fault delimitation information is cross-domain, that is, the first network fault is a cross-domain fault.
  • the cross-domain management device may indicate to the domain management device that the second fault information is cross-domain, or the cross-domain
  • the domain management device instructs the domain management device to delete the first network fault, and the domain management device is a device that sends the first fault information.
  • the cross-domain management device may also determine the network element where the first network fault has occurred according to the first fault information. The specific determination may be determined according to actual conditions.
  • step 403 how the cross-domain management device handles the first network fault according to the second fault demarcation information may exist in multiple ways.
  • the second fault delimitation information is cross-domain, 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;
  • the second fault delimitation information is a single domain, that is, the first network fault is a single domain fault
  • the cross-domain management device can determine the network element where the first network fault occurs according to the first fault information, and The domain management device may instruct the network element that has the first network failure to handle the first network failure.
  • the network element that has the first network failure can perform root cause analysis, failure recovery processing, and dispatching (triggering manual intervention processing) for the first network failure, and the cross-domain management device monitors this first network failure. This first network failure is further processed.
  • the network element where the first network failure occurs may be the network element that sends the first failure information to the cross-domain management device, or other cross-domain management functional units, which can be determined according to actual conditions. This will not be repeated here.
  • the first network fault is a single-domain fault or a cross-domain fault, and further determining which domain is the single-domain fault, it is determined that the first network fault is caused by the cross-domain management function unit. Whether to handle the domain management function unit where the first network failure occurs, it can accurately determine how to deal with the first network failure and improve the efficiency of failure processing.
  • the cross-domain management function unit or the domain management function unit may open a fault query interface for specific first fault demarcation information; the fault query interface for specific first fault delimitation information is applicable to the following two deployment scenarios :
  • Scenario 1 The cross-domain management function unit provides a fault query interface for specific first fault demarcation information for the work order system or operation and maintenance personnel to query;
  • Scenario 2 The domain management function unit provides a fault query interface for specific first fault demarcation information for the cross-domain management function unit to query.
  • the work order system or the operation and maintenance personnel can send a fault query or a subscription request to the cross-domain management function unit or the domain management function unit through the fault query interface, and the fault query or the subscription request carries the first fault delimitation information, and the fault query Or the subscription request is used to request the fault information corresponding to the first fault delimitation information.
  • the first fault delimitation information includes at least one of the following: faults in the domain, faults outside the domain, single network element faults in the domain, faults across network elements in the domain, unknown Failure of the domain.
  • the first fault delimitation information includes at least one of the following: single-domain fault, cross-domain fault, single-network element fault, single-domain multi-network element Failure, failure of unknown domain.
  • the cross-domain management function unit or the domain management function unit determines corresponding fault information according to the first fault delimitation information, and returns at least one fault information corresponding to the first fault delimitation information.
  • the first fault delimitation information is introduced as the fault filter condition, which can meet the needs of different users for network fault query.
  • some cross-domain management function units only care about cross-domain faults, and you can only query or subscribe to cross-domain faults. The failure to improve query efficiency.
  • the embodiment of the present application also provides a system, which is shown in FIG. 6 for details.
  • the system includes a cross-domain management device and at least one domain management device.
  • the cross-domain management device can manage the at least one domain management device, and each domain management device can manage at least one network element.
  • step 601 the cross-domain management device sends a fault demarcation rule to the domain management device.
  • the fault delimitation rule can also be pre-configured in the domain management device in other ways.
  • the cross-domain management device may also send a network fault template to the domain management device.
  • Step 602 The domain management device acquires at least one piece of fault information, and one piece of fault information in the at least one piece of fault information is information corresponding to a network fault.
  • the domain management device can obtain the at least one fault information from the network element it manages in multiple ways. For details, reference may be made to the foregoing description, and details are not described herein again.
  • a description is made by taking the domain management device processing the first failure information in the at least one failure information as an example, where the first failure information is any failure information in the at least one failure information.
  • Step 603 The domain management device determines the first fault delimitation information of the first network fault according to the first fault information.
  • the first fault delimitation information may be within the domain or outside the domain or unknown domain.
  • Step 604 The domain management device sends at least one of the first fault information and the first fault delimitation information to the cross-domain management device.
  • the domain management device may not send the first fault information and the first fault delimitation information to the cross-domain management device.
  • Step 605 The domain management device processes the first network fault according to the first fault information.
  • the domain management device when the first fault delimitation information is within a domain, the domain management device further processes the first network fault, including but not limited to operations such as root cause analysis, fault recovery, and dispatch of orders to trigger manual intervention processing. .
  • the domain management device When the first fault delimitation information is outside the domain or unknown domain, the domain management device does not perform root cause analysis, fault recovery, and dispatch of orders to trigger manual intervention for the first network fault, but monitors the first network fault.
  • Step 606 The cross-domain management device may determine the second fault delimitation information of the first network fault according to the first fault information or the first fault delimitation information, and compare the first fault delimitation information to the first network fault according to the second fault delimitation information. Network faults are dealt with.
  • step 606 For the specific content of step 606, reference may be made to the description in step 402 and step 403, which will not be repeated here.
  • the cross-domain management device may process the first network fault according to the first fault information. Specifically, when the first fault delimitation information is outside the domain or unknown domain, the cross-domain management device triggers the corresponding fault analysis process. Specifically, the cross-domain management device may perform correlation analysis on the first network fault and the faults reported by other domain management devices (hereinafter referred to as the second network fault).
  • first network failure is a failure of an unknown domain and is associated with a second network failure
  • second network failure is a failure within the domain
  • no further processing is required for the first network failure, including root cause analysis, failure recovery, or dispatch ( Trigger manual intervention processing) and other processing.
  • the first network fault is an out-of-domain fault or a fault in an unknown domain, and is associated with a second network fault, and the second network fault is also an out-of-domain fault or an unknown domain fault
  • the first network fault can be further processed, including Cross-domain fault demarcation analysis, root cause analysis, fault recovery or dispatching (triggering manual intervention processing) and other processing.
  • the first network fault is an out-of-domain fault or an unknown domain fault, and is not associated with any fault reported by any other domain management equipment, the first network fault can be further processed, including cross-domain fault delimitation analysis, root cause analysis, Processing such as fault recovery or dispatching (triggering manual intervention processing).
  • the cross-domain management device may monitor the first network fault and not perform further processing on the first network fault.
  • the methods provided by the embodiments of the present application are respectively introduced from the perspective of interaction between the domain management device and the cross-domain management device.
  • the domain management device and the cross-domain management device may include a hardware structure and/or a software module, which are implemented in the form of a hardware structure, a software module, or a hardware structure plus a software module The above functions. Whether a certain function among the above-mentioned functions is executed by a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraint conditions of the technical solution.
  • FIG. 7 and FIG. 8 are schematic structural diagrams of possible communication devices provided by embodiments of this application. These communication devices can implement the functions of the domain management device or the cross-domain management device in the foregoing method embodiment, and therefore can also achieve the beneficial effects of the foregoing method embodiment.
  • the communication device 700 includes a communication unit 701 and a processing unit 702.
  • the communication device 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 above.
  • the communication unit is used to obtain the first failure information of the first network failure
  • a processing unit configured to determine first fault delimitation information of the first network fault according to the first fault information; the first fault delimitation information indicates the scope of the first network fault, and the first fault The delimitation information is within the domain or outside the domain or an unknown domain; the first network fault is processed according to the first fault delimitation information.
  • the processing unit is specifically used for:
  • the first fault information includes a fault type
  • the processing unit is specifically configured to:
  • the local network element is determined to be the abnormal network element
  • the opposite network element is determined to be the Abnormal network element
  • the local network element is a network element that sends the first fault information to the domain management device.
  • the processing unit is specifically used for:
  • the range of the first network fault indicated by the first fault delimitation information is within the domain
  • the first fault information includes a fault type
  • the processing unit is specifically configured to:
  • the first fault delimitation information is determined according to the fault delimitation rule and the fault type; the fault delimitation rule includes an association relationship between the fault type and the first fault delimitation information.
  • the communication unit is also used for:
  • the processing unit is specifically used for:
  • the first fault delimitation information of the first network fault is determined according to the first fault information of the first network fault, the configuration information and performance information of the first network fault-associated object.
  • the communication unit is also used for:
  • the processing unit is also used for:
  • the first fault delimitation information of the first network fault is determined according to the first fault information of the first network fault and the at least one second fault information.
  • the processing unit is specifically used for:
  • the first fault delimitation information indicates that the range of the first network failure is within a domain, perform root cause analysis or failure recovery processing on the first network failure; or, when the first fault delimitation information indicates When the scope of the first network failure is outside the domain or an unknown domain, the first fault delimitation information is sent to the cross-domain management device.
  • a communication unit configured to obtain at least one of first fault information and first fault delimitation information of a first network failure, where the first fault delimitation information is in-domain or out-of-domain or unknown domain;
  • a processing unit configured to determine second fault delimitation information of the first network fault according to the first fault information or the first fault delimitation information; the second fault delimitation information indicates the first network Whether the fault is within the scope of the cross-domain management device, the second fault delimitation information is cross-domain and single-domain; or, the second fault delimitation information indicates that the first network fault is in the first domain management Within the scope of the device, the second fault delimitation information is domain management device indication information; the first network fault is processed according to the second fault delimitation information.
  • the processing unit is specifically used for:
  • the first fault demarcation information is outside the domain or unknown domain, and the first network fault has an associated third network fault, and the fault delimitation information of the third network fault is outside the domain, it is determined that all The second fault delimitation information indicates that the scope of the first network fault is cross-domain.
  • the first fault information includes a fault type
  • the processing unit is specifically configured to:
  • the second fault delimitation information is determined according to the fault delimitation rule and the fault type; the fault delimitation rule includes an association relationship between the fault type and the second fault delimitation information.
  • the processing unit is specifically used for:
  • the second fault delimitation information is a single domain
  • the communication device 800 includes a processor 810 and an interface circuit 820.
  • the processor 810 and the interface circuit 820 are coupled to each other.
  • the interface circuit 820 may be a transceiver or an input/output interface.
  • the communication device 800 may further include a memory 830 for storing instructions executed by the processor 810 or storing input data required by the processor 810 to run the instructions or storing data generated after the processor 810 runs the instructions.
  • the processor 810 is used to perform the function of the foregoing processing unit 702
  • the interface circuit 820 is used to perform the function of the foregoing communication unit 701.
  • the terminal device chip When the aforementioned communication device is a chip applied to a terminal device, the terminal device chip implements the function of the terminal device in the foregoing method embodiment.
  • the terminal device chip receives information from other modules in the terminal device (such as a radio frequency module or antenna), and the information is sent by the network device to the terminal device; or, the terminal device chip sends information to other modules in the terminal device (such as a radio frequency module or antenna).
  • the antenna sends information, which is sent by the terminal device to the network device.
  • the network device chip implements the function of the network device in the foregoing method embodiment.
  • the network device chip receives information from other modules in the network device (such as radio frequency modules or antennas), and the information is sent by the terminal device to the network device; or, the network device chip sends information to other modules in the network device (such as radio frequency modules or antennas).
  • the antenna sends information, which is sent by the network device to the terminal device.
  • the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (digital signal processors, DSP), and application-specific integrated circuits. (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • the method steps in the embodiments of the present application can be implemented by hardware, and can also be implemented by a processor executing software instructions.
  • Software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (programmable ROM) , PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), register, hard disk, mobile hard disk, CD-ROM or well-known in the art Any other form of storage medium.
  • An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the ASIC can be located in an access network device or a terminal device.
  • the processor and the storage medium may also exist as discrete components in the access network device or the terminal device.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer programs or instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer program or instruction may be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server integrating one or more available media.
  • the usable medium may be a magnetic medium, such as a floppy disk, a hard disk, and a magnetic tape; it may also be an optical medium, such as a DVD; and it may also be a semiconductor medium, such as a solid state disk (SSD).
  • “at least one” refers to one or more, and “multiple” refers to two or more.
  • “And/or” describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated object before and after is an “or” relationship; in the formula of this application, the character “/” indicates that the associated object before and after is a kind of "division" Relationship.
  • this application can be provided as methods, systems, or computer program products. Therefore, this application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) containing computer-usable program codes.
  • a computer-usable storage media including but not limited to disk storage, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Abstract

本申请提供一种故障处理方法、装置及系统，其中方法包括: 域管理设备获取第一网络故障的第一故障信息; 所述域管理设备根据所述第一故障信息确定所述第一网络故障的第一故障定界信息，所述第一故障定界信息指示所述第一网络故障的范围；所述域管理设备根据所述第一故障定界信息对所述第一网络故障进行处理。通过上述方法，通过确定第一网络故障的第一故障定界信息，从而可以确定第一网络故障的范围，区分域内故障，域外故障还是未知故障，进而确定故障由域管理设备处理还是跨域管理设备处理，实现分层分域故障处理的协同，提升故障处理效率。

Description

一种故障处理方法、装置及系统
本申请要求在2020年05月21日提交中国专利局、申请号为202010437486.0、申请名称为“一种故障处理方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中；以及本申请要求在2021年05月12日提交中国专利局、申请号为202110516232.2、申请名称为“一种故障处理方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种故障处理方法、装置及系统。
背景技术
运营商网络已发展到第五代移动通信技术(the 5th generation，5G)，网络架构变得更灵活，对网络的时延、速率、连接规模等关键性能指标需求不断提升，应用行业也越来越丰富和多样性，对业务的性能保障，灵活性均发生根本性改变，导致网络运维难度的增加。
网络故障会直接影响业务性能，甚至导致业务中断，如何快速检测并排除故障是运维的主要挑战之一。现有技术中，网元、域管理设备、跨域管理设备都会对收集到的故障/告警进行原因分析和故障修复等功能，如何协同网元、域管理设备和跨域管理功能的故障处理能力来提高整体网络的故障处理效率，是一个亟待解决的问题。
发明内容
本申请实施例提供一种故障处理方法、装置及系统，用以解决如何提高网络的故障处理效率的问题。
第一方面，本申请提供一种方法，包括：域管理设备获取第一网络故障的第一故障信息；所述域管理设备根据所述第一故障信息确定所述第一网络故障的第一故障定界信息；所述第一故障定界信息指示所述第一网络故障的范围，所述第一故障定界信息为域内或者域外或者未知域；所述域管理设备根据所述第一故障定界信息对所述第一网络故障进行处理。
上述流程中，通过确定第一网络故障的第一故障定界信息，从而可以确定第一网络故障的范围，区分域内故障，域外故障还是未知故障，进而确定故障由域管理设备处理还是跨域管理设备处理，实现分层分域故障处理的协同，提升故障处理效率。
一种可能的设计中，所述域管理设备根据所述第一故障信息确定所述第一网络故障的第一故障定界信息，包括：所述域管理设备根据所述第一故障信息确定所述第一网络故障对应的异常网元；所述域管理设备根据所述异常网元确定所述第一网络故障的第一故障定界信息。
一种可能的设计中，所述第一故障信息包括故障类型，所述域管理设备根据所述第一故障信息确定所述第一网络故障对应的异常网元，包括：所述域管理设备若根据所述第一故障信息中的故障类型确定所述第一网络故障是由本端网元异常引起的，则将所述本端网元确定为所述异常网元；或者，所述域管理设备若根据所述第一故障信息中的故障类型确 定所述第一网络故障是由所述本端网元的对端网元异常引起的，则将所述对端网元确定为所述异常网元；其中，所述本端网元为向所述域管理设备发送所述第一故障信息的网元。
一种可能的设计中，所述域管理设备根据所述异常网元确定所述第一网络故障的第一故障定界信息，包括：当所述异常网元为所述域管理设备管理的网元，则所述第一故障定界信息指示的所述第一网络故障的范围为域内；当所述异常网元不是所述域管理设备管理的网元，则所述第一故障定界信息指示的所述第一网络故障的范围为域外。
一种可能的设计中，所述第一故障信息包括故障类型，所述域管理设备根据所述第一故障信息确定所述第一网络故障的第一故障定界信息，包括：所述域管理设备根据故障定界规则和所述故障类型确定所述第一故障定界信息；所述故障定界规则包括故障类型和第一故障定界信息的关联关系。
一种可能的设计中，所述方法还包括：所述域管理设备获取所述第一网络故障关联对象的配置信息和性能信息；所述域管理设备根据所述第一故障信息确定所述第一网络故障的第一故障定界信息，包括：所述域管理设备根据所述第一网络故障的第一故障信息、所述第一网络故障关联对象的配置信息和性能信息确定所述第一网络故障的第一故障定界信息。
一种可能的设计中，所述方法还包括：所述域管理设备获取至少一个第二故障信息，所述至少一个第二故障信息中的一个第二故障信息对应一个第二网络故障；所述域管理设备根据所述第一故障信息确定所述第一网络故障的第一故障定界信息，包括：所述域管理设备根据所述第一网络故障的第一故障信息和所述至少一个第二故障信息确定所述第一网络故障的第一故障定界信息。
一种可能的设计中，所述域管理设备根据所述第一故障定界信息对所述第一网络故障进行处理，包括：当所述第一故障定界信息指示所述第一网络故障的范围为域内时，所述域管理设备对所述第一网络故障进行根因分析或者故障恢复处理；或者，当所述第一故障定界信息指示所述第一网络故障的范围为域外或者未知域时，所述域管理设备发送所述第一故障定界信息给跨域管理设备。
一种可能的设计中，所述域管理设备根据所述第一故障定界信息对所述第一网络故障进行处理，包括：所述域管理设备发送所述第一故障定界信息给跨域管理设备，指示所述跨域管理设备根据所述第一故障定界信息对所述第一网络故障进行处理。
一种可能的设计中，所述域内包括接入网域，核心网域内，传输域内，数据中心域内和虚拟资源域内中的至少一个。
第二方面，本申请还提供一种通信装置，该通信装置具有实现上述第一方面提供的任一方法。该通信装置可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或单元。
在一种可能的实现方式中，该通信装置包括：处理器，该处理器被配置为支持该通信装置执行以上所示方法中网络设备的相应功能。该通信装置还可以包括存储器，该存储可以与处理器耦合，其保存该通信装置必要的程序指令和数据。可选地，该通信装置还包括接口电路，该接口电路用于支持该通信装置与网络设备等设备之间的通信。
在一种可能的实现方式中，该通信装置包括相应的功能单元，分别用于实现以上方法中的步骤。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的单元。
在一种可能的实施方式中，通信装置的结构中包括处理单元和通信单元，这些单元可以执行上述方法示例中相应功能，具体参见第一方面提供的方法中的描述，此处不做赘述。
第三方面，本申请提供一种通信方法，包括：跨域管理设备获取第一网络故障的第一故障信息和第一故障定界信息中的至少一个，所述第一故障定界信息为域内或者域外或者未知域；所述跨域管理设备根据所述第一故障信息或所述第一故障定界信息确定所述第一网络故障的第二故障定界信息；所述第二故障定界信息指示所述第一网络故障是否位于所述跨域管理设备的范围内，所述第二故障定界信息为跨域和单域；或者，所述第二故障定界信息指示所述第一网络故障位于第一域管理设备的范围内，所述第二故障定界信息为域管理设备指示信息；所述跨域管理设备根据所述第二故障定界信息对所述第一网络故障进行处理。
上述流程中，通过确定第一网络故障的第二故障定界信息，区分跨域故障还是单域故障，进而确定处理第一网络故障的设备，提升故障处理效率。
一种可能的设计中，所述跨域管理设备根据所述第一故障定界信息确定所述第一网络故障的第二故障定界信息，包括：当所述第一故障定界信息为域内时，则所述跨域管理设备确定所述第二故障定界信息指示所述第一网络故障的范围为单域；或者，当所述第一故障定界信息为域外或者未知域，且所述第一网络故障存在关联的第三网络故障，所述第三网络故障的故障定界信息为域内时，则所述跨域管理设备确定所述第二故障定界信息指示所述第一网络故障的范围为单域；或者，当所述第一故障定界信息为域外或者未知域，且所述第一网络故障存在关联的第三网络故障，所述第三网络故障的故障定界信息为域外时，则所述跨域管理设备确定所述第二故障定界信息指示所述第一网络故障的范围为跨域。
一种可能的设计中，所述方法还包括：当所述跨域管理设备确定所述第二故障定界信息为跨域时，所述跨域管理设备向第一域管理设备指示所述第二故障定界信息为跨域，或者所述跨域管理设备指示所述第一域管理设备删除所述第一网络故障，所述第一域管理设备为发送所述第一故障信息或第一故障定界信息的设备。
一种可能的设计中，所述第一故障信息包括故障类型，所述跨域管理设备根据所述第一故障信息确定所述第一网络故障的第二故障定界信息，包括：所述跨域管理设备根据故障定界规则和所述故障类型确定所述第二故障定界信息；所述故障定界规则包括故障类型和第二故障定界信息的关联关系。
一种可能的设计中，所述跨域管理设备根据所述第二故障定界信息对所述第一网络故障进行处理，包括：所述第二故障定界信息为跨域时，所述跨域管理设备对所述第一网络故障进行根因分析或者故障恢复处理；或者，所述第二故障定界信息为单域时，所述跨域管理设备根据所述第一故障信息确定发生所述第一网络故障的域管理设备，并指示所述域管理设备处理所述第一网络故障。
一种可能的设计中，所述单域包括接入网域，核心网域内，传输域内，数据中心域内和虚拟资源域内中的至少一个。
第四方面，本申请还提供一种通信装置，该通信装置具有实现上述第三方面提供的任一方法。该通信装置可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或单元。
在一种可能的实现方式中，该通信装置包括：处理器，该处理器被配置为支持该通信装置执行以上所示方法中终端设备的相应功能。该通信装置还可以包括存储器，该存储可 以与处理器耦合，其保存该通信装置必要的程序指令和数据。可选地，该通信装置还包括接口电路，该接口电路用于支持该通信装置与网络设备等设备之间的通信。
在一种可能的实现方式中，该通信装置包括相应的功能单元，分别用于实现以上方法中的步骤。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的单元。
在一种可能的实施方式中，通信装置的结构中包括处理单元和通信单元，这些单元可以执行上述方法示例中相应功能，具体参见第三方面提供的方法中的描述，此处不做赘述。
第五方面，提供了一种系统，包括：域管理设备，用于获取第一网络故障的第一故障信息；根据所述第一故障信息确定所述第一网络故障的第一故障定界信息；所述第一故障定界信息指示所述第一网络故障的范围，所述第一故障定界信息为域内或者域外或者未知域；当确定所述第一故障定界信息为域外或者未知域时，向跨域管理设备发送所述第一故障信息和第一故障定界信息中的至少一个；所述跨域管理设备，用于获取第一网络故障的第一故障信息和第一故障定界信息中的至少一个，所述第一故障定界信息为域内或者域外或者未知域；根据所述第一故障信息或所述第一故障定界信息确定所述第一网络故障的第二故障定界信息；所述第二故障定界信息指示所述第一网络故障是否位于所述跨域管理设备的范围内，所述第二故障定界信息为跨域和单域；或者，所述第二故障定界信息指示所述第一网络故障位于第一域管理设备的范围内，所述第二故障定界信息为域管理设备指示信息；根据所述第二故障定界信息对所述第一网络故障进行处理。
一种可能的设计中，所述域管理设备具体用于：当所述第一故障定界信息指示所述第一网络故障的范围为域内时，对所述第一网络故障进行根因分析或者故障恢复处理；或者，当所述第一故障定界信息指示所述第一网络故障的范围为域外或者未知域时，发送所述第一故障定界信息给所述跨域管理设备。
一种可能的设计中，所述跨域管理设备具体用于：所述第二故障定界信息为跨域时，对所述第一网络故障进行根因分析或者故障恢复处理；或者，所述第二故障定界信息为单域时，根据所述第一故障信息确定发生所述第一网络故障的域管理设备，并指示所述域管理设备处理所述第一网络故障。
第六方面，提供了一种通信装置，该通信装置可以为上述方法实施例中的网络设备，或者为设置在网络设备中的芯片。该通信装置包括接口电路以及处理器，可选的，还包括存储器。其中，该存储器用于存储计算机程序或指令，处理器与存储器、接口电路耦合，当处理器执行所述计算机程序或指令时，使通信装置执行上述方法实施例中由域管理设备或者跨域管理设备所执行的方法。
第七方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码并运行时，使得上述各方面中由域管理设备执行的方法被执行。
第八方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码被运行时，使得上述各方面中由跨域管理设备执行的方法被执行。
第九方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于实现上述各方面的方法中域管理设备的功能。在一种可能的设计中，所述芯片系统还包括存储器，用于保存程序指令和/或数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于实现上述各方面的方法中跨域管理设备的功能。在一种可能的设计中，所述芯片系统还包括存储器，用 于保存程序指令和/或数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十一方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，当该计算机程序被运行时，实现上述各方面中由域管理设备执行的方法。
第十二方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，当该计算机程序被运行时，实现上述各方面中由跨域管理设备执行的方法。
附图说明
图1为适用于本申请实施例的一种系统架构示意图；
图2为本申请实施例提供的一种故障处理方法流程示意图；
图3为本申请实施例提供的一种故障流程处理示意图；
图4为本申请实施例提供的一种故障处理方法流程示意图；
图5为本申请实施例提供的一种故障判断示意图；
图6为本申请实施例提供的一种系统架构示意图；
图7为本申请实施例提供的一种装置结构示意图；
图8为本申请实施例提供的一种装置结构示意图。
具体实施方式
下面结合说明书附图对本申请实施例做详细描述。
本申请实施例可以应用于各种移动通信系统，例如：新无线(new radio，NR)系统、长期演进(long term evolution，LTE)系统、先进的长期演进(advanced long term evolution，LTE-A)系统、未来通信系统等其它通信系统，具体的，在此不做限制。
为便于理解本申请实施例，首先以图1中示出的系统为例详细说明。图1示出了一种适用于本申请实施例提供的方法的系统架构示意图。如图1所示，该系统包括业务支撑系统(Business Support System,BSS)，跨域管理功能(Cross Domain Management Function,CD-MnF)单元，域管理功能(Domain Management Function,Domain-MnF)单元以及多个网元等。
其中，BSS是面向运营商业务和服务的，提供计费、结算、帐务、客服、营业、网络监控等功能和服务。BSS也包括工单系统，工单系统用于根据故障信息进行派单处理，进而故障处理人员。
跨域管理功能单元，可以称为网络管理功能(Network Management Function,NMF)单元，还可以是网络切片管理功能(Network Slice Management Function，NSMF)单元或者跨域管理数据分析功能(Management data analytical Function，MDAF)单元或者跨域自组织网络功能(Self-Organization Network Function，SON Function)单元或者跨域意图管理功能单元等，为了描述方便，以下均称为跨域管理功能单元。跨域管理功能单元可以提供以下一项或者多项管理功能或者管理服务：
网络的生命周期管理；网络的部署；网络的故障管理，包括但不限于故障采集、故障识别、根因分析和故障处理等；网络的性能管理；网络的配置管理；网络的保障；网络的优化功能；网络意图(Intent)的翻译等。
其中，网络的故障包括此网络所有组件的故障，例如子网络、网元、网络功能、小区、单板以及芯片等组件的故障。本申请实施例所涉及的网络，可以是指包括一个或者多个网元或者子网络。这里的“意图”，可以是指通信服务提供商的意图(Intent From Communication Service Provider，Intent-CSP)，或者通信服务消费者的意图(Intent From Communication Service Consumer，Intent-CSC)。
需要说明的是，跨域管理功能单元还可以针对子网络提供以下一项管理或服务：
子网络的生命周期管理；子网络的部署；子网络的故障管理，包括但不限于故障采集，故障识别，根因分析和故障处理等，子网络的故障包括此子网络所有组件的故障，例如子网络、网元、网络功能、小区、单板以及芯片等组件；子网络的性能管理；子网络的配置管理；子网络的保障；子网络的优化功能；子网络意图的翻译等。这里的子网络可以是指由多个小的子网络组成。
域管理功能单元，也可以称为子网络管理功能单元或者网元管理功能单元，以下均称为域管理功能单元。域管理功能单元可以提供以下一项或者多项管理功能或者管理服务：子网络或者网元的生命周期管理；子网络或者网元的部署；子网络或者网元的故障管理，包括但不限于故障采集、故障识别、根因分析和故障处理等，其中子网络的故障包括此子网络所有组件的故障，例如子网络、网元、网络功能、小区单板、芯片等组件的故障；网元的故障包括此网元所有组件的故障，例如网络功能、小区单板、芯片等组件的故障；子网络或者网元的性能管理；子网络或者网元的保障；子网络或者网元的优化功能，子网络或者网元的意图翻译等。
其中，这里的子网络包括一个或者多个网元。子网络也可以包括子网络，即一个或者多个子网络组成一个更大的子网络。
其中域管理功能单元可以按以下方式部署，但不仅限于以下：
1、按网络类型分类：接入网(Radio Access Network，RAN)域管理功能单元(Domain Management Function)，核心网域管理功能单元(Core Domain Management Function)，传输网域管理功能单元(Transport Domain Management Function)；也可以是某个域网络管理系统可以管理接入网，核心网和传输网的两种或者全部；
2、按行政区域划分：某个地区的域管理功能单元，比如上海域管理功能单元，北京域管理功能单元等。
本申请实施例中，网元是提供网络服务的实体，包括核心网网元以及接入网网元等。
其中，核心网网元包括但不限于：接入和移动性管理功能(Access and Mobility Management Function，AMF)网元,会话管理功能(Session Management Function，SMF)网元,策略控制功能(Policy Control Function，PCF)网元，网络数据分析功能(network data analytical Function，NWDAF)网元，网络仓库功能(Network Repository Function，NRF)网元，网关等。接入网网元包括但不限各种制式下无线接入设备，例如可以是NR系统中的下一代基站(next Generation node B，gNB)，可以是演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)或节点B(Node B，NB)，还可以为5G(NR)系统中的gNB或传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带设备(BBU)，或在集中式-分布式(central unit-distributed,CU-DU)架构下的DU等。
网元也可以提供以下一项或者多项管理功能或者管理服务：网元的生命周期管理，网 元的部署，网元的故障管理，网元的性能管理，网元的保障，网元的优化功能，网元的意图翻译等。其中，网元的故障管理，包括但不限于故障采集、故障识别、根因分析和故障处理等，网元的故障包括此网元的所有组件的故障，例如子网络、网元、网络功能、单板、芯片等组件的故障。
应理解，服务化管理架构聚焦于管理服务的提供者和管理服务调用者，具体如下：
当管理服务为以上跨域管理单元提供的管理服务，则跨域管理单元为管理服务提供者(management service producer,MnS producer)，BSS为管理服务调用者(management service consumer,MnS consumer)。
当管理服务为以上域管理单元提供的管理服务，则域管理单元为管理服务提供者，跨域管理单元为管理服务调用者。
当管理服务为以上网元提供的管理服务，则网元为管理服务提供者，域管理单元为管理服务调用者。
另外，在本申请实施例中，“示例的”一词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
实施例一：
参见图2，为本申请实施例提供的一种故障处理方法流程示意图。
图2中，域管理设备可以是指图1中的域管理功能单元。当然图1中的跨域管理功能单元也可以执行图2所示的流程。
步骤201：域管理设备获取第一网络故障的第一故障信息。
步骤202：域管理设备根据所述第一故障信息确定所述第一网络故障的第一故障定界信息。
其中，所述第一故障定界信息指示所述第一网络故障的范围。
步骤203：域管理设备根据所述第一故障定界信息对所述第一网络故障进行处理。
上述流程中，通过确定第一网络故障的第一故障定界信息，从而可以确定第一网络故障的范围，从而可以根据第一网络故障的范围对第一网络故障做进一步处理，可以提升故障处理效率。
实施例一中，第一故障定界信息可以为域内或者域外或者未知域，具体根据实际情况确定。其中，域内包括接入网域，核心网域内，传输域内，数据中心域内和虚拟资源域内中的至少一个。举例来说，接入网域：描述一个或者多个无线接入网设备(e.g.基站)提供的无线接入网络；核心网域：描述一个或者多个核心网设备(e.g.移动性管理实体(Mobility Management Entity，MME),接入和移动性管理功能(access and mobility management function,AMF))提供的核心网络；传输网域：描述一个或者多个传输设备(e.g.光设备)提供的传输网络；数据中心域内：描述一个或者多个数据中心提供的互联网协议(internet protocol，IP)网络；虚拟资源域：描述一个或者多个虚拟资源(e.g.虚拟机)提供的虚拟网络。
其中，第一故障定界信息为域内时，表示第一网络故障是由于域管理设备管理的对象或网元发生异常导致的故障；第一故障定界信息为域外时，表示第一网络故障不是由于域管理设备管理的对象或网元发生异常导致的故障；第一故障定界信息为未知域时，表示第一网络故障不确定是否是由于域管理设备管理的对象或网元发生异常导致的故障。
可选的，第一网络故障的范围为域内时，还可以分为域内网元的故障和域内跨网元的故障；其中，域内网元的故障表示是由于网元内的对象发生异常导致的故障，而域内跨网元的故障表示是由于域内不同网元之间的对象发生异常导致的故障。
结合图1可知，域管理设备为域管理功能单元时，域管理设备管理多个网元。
步骤201中，域管理设备获取到的第一故障信息可以包括但不限于以下一项或多项：
故障标识；故障类型；故障产生网元，表示发生故障的网元；故障根因；发生故障的时间；与故障相关的网元；故障等级。
以上只是示例，第一故障信息中还可以包括其他内容，在此不再逐一举例说明。
本申请实施例中，域管理设备可以通过多种方式获取第一故障信息。
一种可能的实现方式中，可以由产生第一故障信息的设备主动向域管理设备上报第一故障信息。
例如，域管理设备为域管理功能单元时，由域管理设备管理的网元向域管理设备上报第一故障信息。需要说明的是，在实际应用中，域管理设备可以接收到多个网元上报的多个故障信息。
或者，域管理设备也可以主动向其管理的网元请求第一故障管理信息。例如，域管理设备可以周期性的发送请求消息，请求消息用于请求故障信息，域管理设备管理的网元从而可以向域管理设备管理上报故障信息。
以上只是示例，其他情况不再赘述。
另一种可能的实现方式中，域管理设备可以收集至少一条网络告警信息，域管理设备可以确定所述至少一条网络告警信息对应的所述第一网络故障，并获取所述第一网络故障的第一故障信息。
需要说明的是，域管理设备中可以包括预先设置的网络故障模板，所述网络故障模板中包括网络故障对应的网络告警信息。域管理设备可以将预先设置的网络故障模板中与所述至少一条网络告警信息对应的网络故障确定为所述第一网络故障。
由于现网中，不同种类告警信息频繁出现，这些告警信息可能是由一个网络故障引起的，因此可以预先设置一个网络故障模板，从而可以快速的定位网络故障。举例来说，网络故障模板可以如表1所示。
表1
Figure PCTCN2021093822-appb-000001
表1只是示例，还可能存在其他网络故障模板，在此不再赘述。
步骤202中，域管理设备可以通过多种方式确定第一故障定界信息，下面详细描述。
第一种可能的实现方式中，域管理设备可以根据第一故障定界信息中的故障类型和故 障产生网元中的至少一项确定第一故障定界信息。
举例来说，如果根据第一网络故障的故障类型，确定第一网络故障是由于故障产生网元或者该故障产生网元中的组件异常引起的故障，则可以确定第一网络故障为域内的故障，即确定第一故障定界信息为域内。例如，第一网络故障的故障类型为以下任一项时，可以确定第一网络故障为域内的故障：射频单元驻波故障；射频单元软件运行异常故障；电池故障；单板时钟输入异常故障；配置文件损坏故障等。
再举例来说，域管理设备可以根据第一故障定界信息中的故障类型确定异常网元，从而可以根据异常网元确定第一故障定界信息。
域管理设备如何确定异常网元，并不限定。例如，所述域管理设备若根据所述第一故障信息中的故障类型确定所述第一网络故障是由本端网元异常引起的，则将所述本端网元确定为所述异常网元；所述域管理设备若根据所述第一故障信息中的故障类型确定所述第一网络故障是由所述本端网元的对端网元异常引起的，则将所述对端网元确定为所述异常网元；其中，所述本端网元为向所述域管理设备发送所述第一故障信息的网元，对端网元可以是与所述本端网元存在物理连接或者数据交互的网元。本端网元和对端网元是相对的概念，并不是绝对的概念。
当确定异常网元为所述域管理设备管理的网元时，可以确定所述第一故障定界信息为域内，即第一网络故障为域内的故障；当确定所述异常网元不是所述域管理设备管理的网元时，可以确定所述第一故障定界信息为域外，即第一网络故障为域外的故障。
进一步的，有些网络故障是由于故障产生网元的对端网元异常引起的，如果对端网元是本域内的网元，则可以确定第一网络故障为域内的故障或者域内跨网元的故障。以下举例几种可能的此类型故障：对端证书过期故障，以及基站控制面传输中断告警故障等。
以上只是示例，还可能存在其他情况，在此不再逐一举例说明。
第二种可能的实现方式中，域管理设备可以根据故障定界规则确定第一故障定界信息。
其中，所述故障定界规则可以包括故障类型和第一故障定界信息的关联关系，域管理设备可以将故障定界规则中，与第一网络故障的故障类型关联的第一故障定界信息确定为第一故障定界信息。
举例来说，故障定界规则中包括以下关联关系：射频单元软件运行异常故障，关联域内的故障。那么当第一网络故障为射频单元软件运行异常故障时，则可以确定第一故障定界信息为域内。
可选的，故障定界规则还可以包括网络故障和第一故障定界信息判断流程的关联关系。
有些网络故障可能是本端网元的异常引起的，或者可能是对端网元的异常引起的，或者其他原因引起的，有的网络故障可能存在关联的第一故障定界信息判断流程，从而可以根据第一故障定界信息判断流程确定网络故障的第一故障定界信息。
举例来说，Xn接口为接入网网元之间的接口，当网络故障为Xn接口故障时，Xn接口故障引起的原因包括以下几种可能：
1、Xn接口配置错误，即本端基站对象或者对端基站对象包含的EP_Xn对象配置信息错误，例如本地网际互连协议(Internet Protocol，IP)地址、虚拟局域网(Virtual Local Area Network，VLAN)标识、远程(Remote)IP地址等配置错误；
2、本端基站或者对端基站没有配置完整的小区列表；
3、本端基站在对端基站的黑名单；
4、传输链路状态异常。
为此，如图3所示，网络故障为Xn接口故障时，第一故障定界信息判断流程可以包括以下步骤：
步骤301：获取Xn接口故障的故障信息。
步骤302：根据故障信息判断该网络故障对应的本端基站的Xn接口配置信息和小区列表信息是否正确。如果不正确，则确定此Xn接口故障为域内的故障或者域内网元的故障；如果正确，则执行步骤303。
本端基站可以是指产生Xn接口故障的基站。
步骤303：判断对端基站是否是在本域内，如果不在，则确定为域外的故障；如果在，则执行步骤304。
对端基站可以是指与本端基站存在通信交互的基站。
步骤304：判断对端基站的Xn接口信息和小区列表信息是否正确；如果不正确，则确定Xn接口故障为域内的故障或者域内跨网元的故障；如果正确，则确定Xn接口故障为域外的故障。
需要说明的，故障定界规则可以为预配置的，也可以为通过其他设备获取到的，例如域管理设备为域管理功能单元时，可以通过跨域管理功能单元接收所述故障定界规则。
第三种可能的实现方式中，域管理设备可以获取所述第一网络故障关联对象的配置信息和性能信息。配置信息可以为第一网络故障关联对象的配置参数，比如Xn故障的关联对象为网元1，网元1的配置参数为IP地址＝X，VLAN ID＝2；性能信息可以为第一网络故障关对象的性能测量量或者关键绩效指标(Key Performance Indicator，KPI),比如丢包率，延时，发送成功率等。
所述域管理设备根据所述第一网络故障的第一故障信息、所述第一网络故障关联对象的配置信息和性能信息确定所述第一网络故障的第一故障定界信息。
第四种可能的实现方式中，域管理设备可以根据其它网络故障的故障信息确定第一网络故障的第一故障定界信息。
具体的，域管理设备可以获取至少一个第二故障信息，所述至少一个第二故障信息中的一个第二故障信息对应一个第二网络故障，域管理设备可以根据所述第一网络故障的第一故障信息和所述至少一个第二故障信息确定所述第一网络故障的第一故障定界信息。
举例来说，第一网络故障为Xn接口的配置错误，例如可以是配置的IP地址和规划的IP地址不一致，第二网络故障为传输链路故障。如果第一网络故障与第二网络故障关联，则可以确定第一网络故障为域内的故障。
以上只是示例，域管理设备还可以根据其它方式确定第一网络故障的第一故障定界信息，在此不再逐一举例说明。
步骤203中，域管理设备具体如何对第一网络故障进行处理，可能存在以下一种或多种方式。
方式一：当所述第一故障定界信息为域内，即第一网络故障为域内的故障时，所述域管理设备对所述第一网络故障进行进一步处理，包括但不限于根因分析、故障恢复处理和派单触发人工干预处理等操作。
方式二：当所述第一故障定界信息为域外或者未知域，即第一网络故障为域外的故障 或未知域的故障时，域管理设备不对第一网络故障进行根因分析、故障恢复处理和派单触发人工干预等处理，而是发送所述第一故障定界信息给其他设备。例如域管理设备为域管理功能单元时，可以将第一故障定界信息给管理所述域管理设备的跨域管理功能单元，域管理设备还可以将第一故障信息也发送给跨域管理功能单元。
方式三：不论第一故障定界信息为域内、域外，还是未知域，域管理设备发送所述第一故障定界信息给跨域管理设备，指示所述跨域管理设备根据所述第一故障定界信息对所述第一网络故障进行处理。
进一步的，本申请实施例中，跨域管理功能单元可以根据第一故障定界信息对第一网络故障做以下处理：
当第一故障定界信息为域外或者未知域时，跨域管理功能单元触发相应故障分析流程。具体地，跨域管理功能单元可以对第一网络故障和其他域管理功能单元上报的故障(下文简称第二网络故障)做关联分析。
如果第一网络故障为未知域的故障，和第二网络故障关联，并且第二网络故障为域内的故障，则可以确定第一网络故障为域外的故障，不对第一网络故障做进一步处理，包括根因分析、故障恢复处理或者派单(触发人工干预处理)等处理。
如果第一网络故障为域外的故障或未知域的故障，和第二网络故障关联，并且第二网络故障也为域外的故障或未知域的故障，则确定需要对第一网络故障做进一步处理，包括跨域故障定界分析、根因分析、故障恢复处理或者派单(触发人工干预处理)等处理。
如果第一网络故障为域外的故障或未知域的故障，没有和任何其他域管理功能单元上报的故障关联，则确定需要对第一网络故障做进一步处理，包括跨域故障定界分析、根因分析、故障恢复处理或者派单(触发人工干预处理)等处理。
可选的，如果第一网络故障为域内的故障时，管理所述域管理设备的跨域管理功能单元可以对第一网络故障监控，不对第一网络故障做进一步处理。
实施例二：
参见图4，为本申请实施例提供的一种故障处理方法流程示意图。
图4中，跨域管理设备可以是指图1中的跨域管理功能单元。
步骤401：跨域管理设备获取第一网络故障的第一故障信息和第一故障定界信息中的至少一个。
其中，所述第一故障定界信息为域内或者域外或者未知域；
实施例二中，第一故障定界信息的具体内容可以参考实施例一中的描述，在此不再赘述。
步骤402：跨域管理设备根据所述第一故障信息或第一故障定界信息确定所述第一网络故障的第二故障定界信息。
其中，一种可能的实现方式中，所述第二故障定界信息指示所述第一网络故障是否位于所述跨域管理设备的范围内，所述第二故障定界信息为跨域和单域；另一种可能的实现方式中，所述第二故障定界信息指示所述第一网络故障位于第一域管理设备的范围内，所述第二故障定界信息为域管理设备指示信息。
其中，单域包括接入网域，核心网域内，传输域内，数据中心域内和虚拟资源域内中的至少一个。举例来说，接入网域：描述一个或者多个无线接入网设备(e.g.基站)提供的无线接入网络；核心网域：描述一个或者多个核心网设备(e.g.MME,AMF)提供的核心 网络；传输网域：描述一个或者多个传输设备(e.g.光设备)提供的传输网络；数据中心域内：描述一个或者多个数据中心提供的IP网络；虚拟资源域：描述一个或者多个虚拟资源(e.g.虚拟机)提供的虚拟网络。
在实施例二中，第一网络故障对应的第二故障定界信息为单域时，表示第一网络故障是由于跨域管理设备管理的一个域管理设备所管理的对象或网元发生异常导致的故障；第一网络故障对应的第二故障定界信息为跨域时，表示第一网络故障是由于跨域管理设备管理的至少两个域管理设备所管理的对象或网元发生异常导致的故障。
进一步的，第二故障定界信息为单域时，跨域管理设备还可以根据第一故障信息确定发生第一网络故障的网元，以及管理该网元的域管理设备等信息，具体可以根据实际情况确定，在此不再赘述。
步骤403：跨域管理设备根据所述第二故障定界信息对所述第一网络故障进行处理。
结合上面的描述可知，在实施例二中，第一网络故障可能对应至少两种第二故障定界信息，即第二故障定界信息和第一故障定界信息。第二故障定界信息用于描述第一网络故障在跨域管理设备的哪个范围内的故障，第一故障定界信息用于描述第一网络故障在跨域管理设备所管理的域管理功能单元的哪个范围内的故障。
步骤401中，第一故障信息和第一故障定界信息中的至少一个，可以是由跨域管理设备管理的域管理设备上报至所述跨域管理设备的，跨域管理设备具体如何获取第一故障信息和第一故障定界信息中的至少一个，本申请实施例对此并不限定，在此不再赘述。
步骤402中，跨域管理设备可以通过多种方式确定第二故障定界信息，下面详细描述。
第一种可能的实现方式中，跨域管理设备可以根据第一故障信息中的故障类型和故障产生网元中的至少一项确定第二故障定界信息。
举例来说，如果第一网络故障的故障类型是由于故障产生网元或者该故障产生网元的组件异常引起的故障，则可以确定第一网络故障为单域的故障，即确定第二故障定界信息为单域。例如，第一网络故障的故障类型为以下任一故障时，第一网络故障为单域的故障：射频单元驻波故障；射频单元软件运行异常故障；电池故障；单板时钟输入异常故障；配置文件损坏故障等。
第二种可能的实现方式中，跨域管理设备可以根据故障定界规则确定第二故障定界信息。
其中，所述故障定界规则可以包括故障类型和第二故障定界信息的关联关系，跨域管理设备可以将故障定界规则中，与第一网络故障的故障类型关联的故障定界信息确定为第二故障定界信息。
可选的，故障定界规则可以包括网络故障和第二故障定界信息判断流程的关联关系。
有些网络故障可能是本端网元的异常引起的，或者可能是对端网元的异常引起的，或者其他原因引起的，有的网络故障可能存在关联的第二故障定界信息判断流程，从而可以根据第二故障定界信息判断流程确定网络故障的第二故障定界信息。
需要说明的，故障定界规则可以为预配置的，也可以为通过其他设备获取到的。
第三种可能的实现方式中，跨域管理设备可以根据接收到的至少一个故障信息进行定界分析，从而确定第一网络故障的第二故障定界信息。
举例来说，如图5所示，跨域管理设备管理3个域管理功能单元，分别为域管理功能单元1、域管理功能单元2以及域管理功能单元3。跨域管理设备从域管理功能单元1获 取第一故障信息。跨域管理设备还可以通过域管理功能单元2获取第三网络故障的第三故障信息以及通过域管理功能单元3获取第四网络故障的第四故障信息。
假设所述第一网络故障和所述第三网络故障均为Xn接口故障，所述第四网络故障为传输链路故障。
若所述第一网络故障与Xn接口故障以及传输链路故障均存在关联，例如第一网络故障与所述第三网络故障、所述第四网络故障关联，且所述第一网络故障对应的Xn接口与所述第三网络故障对应的Xn接口匹配，则可以确定所述第二故障定界信息为单域，即所述第一网络故障为单域的故障；进一步的，第一网络故障为域管理功能单元3的单域的故障。
若所述第一网络故障与所述第三网络故障关联，和第四网络故障不存在关联关系，且所述第一网络故障对应的Xn接口与所述第三网络故障对应的Xn接口不匹配，则可以确定所述第二故障定界信息为跨域，即所述第一网络故障为跨域的故障；
若所述第一网络故障与所述第三网络故障关联，和第四网络故障不存在关联关系，且所述第一网络故障对应的Xn接口的配置错误，例如配置的IP地址和规划的IP地址不一致，则可以确定所述第二故障定界信息为单域，即所述第一网络故障为单域的故障。进一步的，第一网络故障为域管理功能单元1的单域的故障。
第四种可能的实现方式中，跨域管理设备可以根据第一故障定界信息确定第一网络故障的第二故障定界信息。
举例来说，第一故障信息中的第一故障定界信息为域内，即第一网络故障为域内的故障时，跨域管理设备可以确定所述第二故障定界信息为单域，即第一网络故障为单域的故障。
第一故障信息中的第一故障定界信息为域外或者未知域，即第一网络故障为域外的故障或未知域的故障时，当第一网络故障存在关联的第三网络故障，所述第三网络故障的故障定界信息为域内时，跨域管理设备可以确定第二故障定界信息为单域，即第一网络故障为单域的故障。
需要说明的是，在该情况下，第二故障定界信息为单域，表示第一网络故障为上报第三网络故障的域管理设备的单域故障，即第一网络故障为上报第三网络故障的域管理设备所管理的对象或网元所发生异常导致的故障。
第一故障信息中的第一故障定界信息为域外或者未知域，即第一网络故障为域外的故障或未知域的故障时，当第一网络故障存在关联的第三网络故障，所述第三网络故障的故障定界信息为域外时，跨域管理设备可以确定第二故障定界信息为跨域，即第一网络故障为跨域的故障。
以上只是示例，还可能存在其他确定方式，在此不再逐一举例说明。
需要说明的是，当所述跨域管理设备确定所述第二故障信息为跨域时，所述跨域管理设备可以向域管理设备指示所述第二故障信息为跨域，或者所述跨域管理设备指示所述域管理设备删除所述第一网络故障，所述域管理设备为发送所述第一故障信息的设备。
跨域管理设备确定第二故障定界信息为单域时，还可以根据第一故障信息确定发生第一网络故障的网元，具体如何确定，可以根据实际情况确定。
步骤403中，跨域管理设备如何根据所述第二故障定界信息对所述第一网络故障进行处理，可能存在多种方式。
一种可能的实现方式中，第二故障定界信息为跨域，即第一网络故障为跨域的故障时，所述跨域管理设备对所述第一网络故障进行根因分析；
一种可能的实现方式中，第二故障定界信息为单域，即第一网络故障为单域的故障，跨域管理设备可以根据第一故障信息确定发生第一网络故障的网元，跨域管理设备可以指示所述发生第一网络故障的网元处理所述第一网络故障。所述发生第一网络故障的网元可以对第一网络故障进行根因分析、故障恢复处理和派单(触发人工干预处理)等处理，跨域管理设备对此第一网络故障进行监控，不对此第一网络故障进行进一步处理。
需要说明的是，所述发生第一网络故障的网元，可以是向跨域管理设备发送第一故障信息的网元，也可以是其他跨域管理功能单元，具体可以根据实际情况确定，在此不再赘述。
通过实施例二的过程可知，通过进一步区分第一网络故障是单域的故障还是跨域的故障，并且进一步确定是哪个域的单域的故障，进而确定第一网络故障由跨域管理功能单元处理还是发生第一网络故障的域管理功能单元处理，可以准确的确定如何处理第一网络故障，提升故障处理效率。
实施例三：
本申请实施例中，跨域管理功能单元或者域管理功能单元可以开放针对特定第一故障定界信息的故障查询接口；针对特定第一故障定界信息的故障查询接口适用于以下两个部署场景：
场景一：跨域管理功能单元提供针对特定第一故障定界信息的故障查询接口给工单系统或者运维人员查询；
场景二：域管理功能单元提供针对特定第一故障定界信息的故障查询接口给跨域管理功能单元查询。
工单系统或者运维人员可以通过故障查询接口向跨域管理功能单元或者域管理功能单元发送故障查询或者订阅请求，所述故障查询或者订阅请求中携带第一故障定界信息，所述故障查询或者订阅请求用于请求所述第一故障定界信息对应的故障信息。
如果向域管理功能单元发送故障查询或者订阅请求，则第一故障定界信息包括以下中的至少一个：域内的故障，域外的故障，域内单网元的故障，域内跨网元的故障，未知域的故障。
如果向跨域管理功能单元发送故障查询或者订阅请求，则第一故障定界信息包括以下中的至少一个：单域的故障，跨域的故障，单网元的故障，单域多网元的故障，未知域的故障。
跨域管理功能单元或者域管理功能单元根据第一故障定界信息确定对应的故障信息，返回第一故障定界信息对应的至少一个故障信息。
通过上面的方法，引入第一故障定界信息作为故障筛选条件，可以满足不同用户对网络故障查询的需求，比如有些跨域管理功能单元只关心跨域的故障，就可以只查询或者订阅跨域的故障，从而提高查询效率。
实施例四：
本申请实施例还提供一种系统，具体可以参考图6所示。该系统中包括跨域管理设备、至少一个域管理设备。其中跨域管理设备可以管理所述至少一个域管理设备，每个域管理设备可以管理至少一个网元。
可选的，步骤601：跨域管理设备向域管理设备发送故障定界规则。
如果跨域管理设备不发送故障定界规则，也可以通过其他方式在域管理设备中预配置故障定界规则。
可选的，跨域管理设备还可以向域管理设备发送网络故障模板。
步骤602：域管理设备获取至少一个故障信息，所述至少一个故障信息中的一个故障信息为一个网络故障对应的信息。
域管理设备可以通过多种方式，从其所管理的网元获取所述至少一个故障信息，具体可以参考前面的描述，在此不再赘述。
为了描述方便，以域管理设备对至少一个故障信息中的第一故障信息进行处理为例进行描述，第一故障信息为所述至少一个故障信息中的任一故障信息。
步骤603：域管理设备根据第一故障信息确定第一网络故障的第一故障定界信息。
第一故障定界信息可以为域内或者域外或者未知域。
步骤604：域管理设备向跨域管理设备发送所述第一故障信息以及所述第一故障定界信息中的至少一项。
需要说明的是，当第一故障定界信息为域内域时，域管理设备可以不向跨域管理设备发送所述第一故障信息以及所述第一故障定界信息。
步骤605：域管理设备根据第一故障信息处理第一网络故障。
具体的，当所述第一故障定界信息为域内，所述域管理设备对所述第一网络故障进行进一步处理，包括但不限于根因分析、故障恢复和派单触发人工干预处理等操作。
当所述第一故障定界信息为域外或者未知域，域管理设备不对第一网络故障进行根因分析、故障恢复和派单触发人工干预等处理，而是对第一网络故障监控。
步骤606：跨域管理设备可以根据第一故障信息或所述第一故障定界信息确定第一网络故障的第二故障定界信息，并根据所述第二故障定界信息对所述第一网络故障进行处理。
步骤606的具体内容可以参考步骤402和步骤403中的描述，在此不再赘述。
可选的，跨域管理设备可以根据第一故障信息处理第一网络故障。具体的，当第一故障定界信息为域外或者未知域时，跨域管理设备触发相应故障分析流程。具体地，跨域管理设备可以对第一网络故障和其他域管理设备上报的故障(下文简称第二网络故障)做关联分析。
如果第一网络故障为未知域的故障，和第二网络故障关联，并且第二网络故障为域内的故障，则可以不对第一网络故障做进一步处理，包括根因分析、故障恢复或者派单(触发人工干预处理)等处理。
如果第一网络故障为域外的故障或未知域的故障，和第二网络故障关联，并且第二网络故障也为域外的故障或未知域的故障，则可以对第一网络故障做进一步处理，包括跨域故障定界分析、根因分析、故障恢复或者派单(触发人工干预处理)等处理。
如果第一网络故障为域外的故障或未知域的故障，没有和任何其他域管理设备上报的故障关联，则可以对第一网络故障做进一步处理，包括跨域故障定界分析、根因分析、故障恢复或者派单(触发人工干预处理)等处理。
可选的，如果第一网络故障为域内的故障时，跨域管理设备可以对第一网络故障监控，不对第一网络故障做进一步处理。
上述本申请提供的实施例中，分别从域管理设备和跨域管理设备之间交互的角度对本 申请实施例提供的方法进行了介绍。为了实现上述本申请实施例提供的方法中的各功能，域管理设备和跨域管理设备可以包括硬件结构和/或软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能以硬件结构、软件模块、还是硬件结构加软件模块的方式来执行，取决于技术方案的特定应用和设计约束条件。
图7和图8为本申请的实施例提供的可能的通信装置的结构示意图。这些通信装置可以实现上述方法实施例中域管理设备或跨域管理设备的功能，因此也能实现上述方法实施例所具备的有益效果。
如图7所示，通信装置700包括通信单元701和处理单元702。通信装置700可用于实现上述图2所示的方法实施例中域管理设备或跨域管理设备的功能。
当通信装置700用于实现图2所述方法实施例中域管理设备的功能时：
通信单元，用于获取第一网络故障的第一故障信息；
处理单元，用于根据所述第一故障信息确定所述第一网络故障的第一故障定界信息；所述第一故障定界信息指示所述第一网络故障的范围，所述第一故障定界信息为域内或者域外或者未知域；根据所述第一故障定界信息对所述第一网络故障进行处理。
一种可能的设计中，所述处理单元具体用于：
根据所述第一故障信息确定所述第一网络故障对应的异常网元；
根据所述异常网元确定所述第一网络故障的第一故障定界信息。
一种可能的设计中，所述第一故障信息包括故障类型，所述处理单元具体用于：
若根据所述第一故障信息中的故障类型确定所述第一网络故障是由本端网元异常引起的，则将所述本端网元确定为所述异常网元；
或者，若根据所述第一故障信息中的故障类型确定所述第一网络故障是由所述本端网元的对端网元异常引起的，则将所述对端网元确定为所述异常网元；
其中，所述本端网元为向所述域管理设备发送所述第一故障信息的网元。
一种可能的设计中，所述处理单元具体用于：
当所述异常网元为域管理设备管理的网元，则所述第一故障定界信息指示的所述第一网络故障的范围为域内；
当所述异常网元不是所述域管理设备管理的网元，则所述第一故障定界信息指示的所述第一网络故障的范围为域外。
一种可能的设计中，所述第一故障信息包括故障类型，所述处理单元具体用于：
根据故障定界规则和所述故障类型确定所述第一故障定界信息；所述故障定界规则包括故障类型和第一故障定界信息的关联关系。
一种可能的设计中，所述通信单元还用于：
获取所述第一网络故障关联对象的配置信息和性能信息；
所述处理单元具体用于：
根据所述第一网络故障的第一故障信息、所述第一网络故障关联对象的配置信息和性能信息确定所述第一网络故障的第一故障定界信息。
一种可能的设计中，所述通信单元还用于：
获取至少一个第二故障信息，所述至少一个第二故障信息中的一个第二故障信息对应一个第二网络故障；
所述处理单元还用于：
根据所述第一网络故障的第一故障信息和所述至少一个第二故障信息确定所述第一网络故障的第一故障定界信息。
一种可能的设计中，所述处理单元具体用于：
当所述第一故障定界信息指示所述第一网络故障的范围为域内时，对所述第一网络故障进行根因分析或者故障恢复处理；或者，当所述第一故障定界信息指示所述第一网络故障的范围为域外或者未知域时，发送所述第一故障定界信息给跨域管理设备。
当通信装置700用于实现图4所述方法实施例中跨域管理设备的功能时：
通信单元，用于获取第一网络故障的第一故障信息和第一故障定界信息中的至少一个，所述第一故障定界信息为域内或者域外或者未知域；
处理单元，用于根据所述第一故障信息或所述第一故障定界信息确定所述第一网络故障的第二故障定界信息；所述第二故障定界信息指示所述第一网络故障是否位于所述跨域管理设备的范围内，所述第二故障定界信息为跨域和单域；或者，所述第二故障定界信息指示所述第一网络故障位于第一域管理设备的范围内，所述第二故障定界信息为域管理设备指示信息；根据所述第二故障定界信息对所述第一网络故障进行处理。
一种可能的设计中，所述处理单元具体用于：
当所述第一故障定界信息为域内时，则确定所述第二故障定界信息指示所述第一网络故障的范围为单域；
或者，当所述第一故障定界信息为域外或者未知域，且所述第一网络故障存在关联的第三网络故障，所述第三网络故障的故障定界信息为域内时，则确定所述第二故障定界信息指示所述第一网络故障的范围为单域；
或者，当所述第一故障定界信息为域外或者未知域，且所述第一网络故障存在关联的第三网络故障，所述第三网络故障的故障定界信息为域外时，则确定所述第二故障定界信息指示所述第一网络故障的范围为跨域。
一种可能的设计中，所述第一故障信息包括故障类型，所述处理单元具体用于：
根据故障定界规则和所述故障类型确定所述第二故障定界信息；所述故障定界规则包括故障类型和第二故障定界信息的关联关系。
一种可能的设计中，所述处理单元具体用于：
所述第二故障定界信息为跨域时，所述第一网络故障进行根因分析或者故障恢复处理；
或者，所述第二故障定界信息为单域时，根据所述第一故障信息确定发生所述第一网络故障的域管理设备，并指示所述域管理设备处理所述第一网络故障。
关于上述通信单元701和处理单元702更详细的描述，可参考上述方法实施例中的相关描述，在此不再说明。
如图8所示，通信装置800包括处理器810和接口电路820。处理器810和接口电路820之间相互耦合。可以理解的是，接口电路820可以为收发器或输入输出接口。可选的，通信装置800还可以包括存储器830，用于存储处理器810执行的指令或存储处理器810运行指令所需要的输入数据或存储处理器810运行指令后产生的数据。
当通信装置800用于实现上述方法实施例中的方法时，处理器810用于执行上述处理单元702的功能，接口电路820用于执行上述通信单元701的功能。
当上述通信装置为应用于终端设备的芯片时，该终端设备芯片实现上述方法实施例中 终端设备的功能。该终端设备芯片从终端设备中的其它模块(如射频模块或天线)接收信息，该信息是网络设备发送给终端设备的；或者，该终端设备芯片向终端设备中的其它模块(如射频模块或天线)发送信息，该信息是终端设备发送给网络设备的。
当上述通信装置为应用于网络设备的芯片时，该网络设备芯片实现上述方法实施例中网络设备的功能。该网络设备芯片从网络设备中的其它模块(如射频模块或天线)接收信息，该信息是终端设备发送给网络设备的；或者，该网络设备芯片向网络设备中的其它模块(如射频模块或天线)发送信息，该信息是网络设备发送给终端设备的。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其它通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的方法步骤可以通过硬件的方式来实现，也可以由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(random access memory，RAM)、闪存、只读存储器(Read-Only Memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于接入网设备或终端设备中。当然，处理器和存储介质也可以作为分立组件存在于接入网设备或终端设备中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，DVD；还可以是半导体介质，例如，固态硬盘(solid state disk，SSD)。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A,B可以是单数或者复数。在本申请的文字描述中，字符“/”，一般表示前后关联对象是一种“或”的关系；在本申请的公式中，字符“/”，表示前后关联对象是一种“相除”的关系。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产 品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (34)

  1. 一种故障处理方法，其特征在于，包括：
    域管理设备获取第一网络故障的第一故障信息；
    所述域管理设备根据所述第一故障信息确定所述第一网络故障的第一故障定界信息；所述第一故障定界信息指示所述第一网络故障的范围，所述第一故障定界信息为域内或者域外或者未知域；
    所述域管理设备根据所述第一故障定界信息对所述第一网络故障进行处理。
  2. 根据权利要求1所述的方法，其特征在于，所述域管理设备根据所述第一故障信息确定所述第一网络故障的第一故障定界信息，包括：
    所述域管理设备根据所述第一故障信息确定所述第一网络故障对应的异常网元；
    所述域管理设备根据所述异常网元确定所述第一网络故障的第一故障定界信息。
  3. 根据权利要求2所述的方法，其特征在于，所述第一故障信息包括故障类型，所述域管理设备根据所述第一故障信息确定所述第一网络故障对应的异常网元，包括：
    所述域管理设备若根据所述第一故障信息中的故障类型确定所述第一网络故障是由本端网元异常引起的，则将所述本端网元确定为所述异常网元；
    或者，所述域管理设备若根据所述第一故障信息中的故障类型确定所述第一网络故障是由所述本端网元的对端网元异常引起的，则将所述对端网元确定为所述异常网元；
    其中，所述本端网元为向所述域管理设备发送所述第一故障信息的网元。
  4. 根据权利要求3所述的方法，其特征在于，所述域管理设备根据所述异常网元确定所述第一网络故障的第一故障定界信息，包括：
    当所述异常网元为所述域管理设备管理的网元，则所述第一故障定界信息指示的所述第一网络故障的范围为域内；
    当所述异常网元不是所述域管理设备管理的网元，则所述第一故障定界信息指示的所述第一网络故障的范围为域外。
  5. 根据权利要求1所述的方法，其特征在于，所述第一故障信息包括故障类型，所述域管理设备根据所述第一故障信息确定所述第一网络故障的第一故障定界信息，包括：
    所述域管理设备根据故障定界规则和所述故障类型确定所述第一故障定界信息；所述故障定界规则包括故障类型和第一故障定界信息的关联关系。
  6. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述域管理设备获取所述第一网络故障关联对象的配置信息和性能信息；
    所述域管理设备根据所述第一故障信息确定所述第一网络故障的第一故障定界信息，包括：
    所述域管理设备根据所述第一网络故障的第一故障信息、所述第一网络故障关联对象的配置信息和性能信息确定所述第一网络故障的第一故障定界信息。
  7. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述域管理设备获取至少一个第二故障信息，所述至少一个第二故障信息中的一个第二故障信息对应一个第二网络故障；
    所述域管理设备根据所述第一故障信息确定所述第一网络故障的第一故障定界信息，包括：
    所述域管理设备根据所述第一网络故障的第一故障信息和所述至少一个第二故障信息确定所述第一网络故障的第一故障定界信息。
  8. 根据权利要求1至7任一所述的方法，其特征在于，所述域管理设备根据所述第一故障定界信息对所述第一网络故障进行处理，包括：
    当所述第一故障定界信息指示所述第一网络故障的范围为域内时，所述域管理设备对所述第一网络故障进行根因分析或者故障恢复处理；或者，
    当所述第一故障定界信息指示所述第一网络故障的范围为域外或者未知域时，所述域管理设备发送所述第一故障定界信息给跨域管理设备。
  9. 根据权利要求1至7任一项所述的方法，其特征在于，所述域管理设备根据所述第一故障定界信息对所述第一网络故障进行处理，包括：
    所述域管理设备发送所述第一故障定界信息给跨域管理设备，指示所述跨域管理设备根据所述第一故障定界信息对所述第一网络故障进行处理。
  10. 根据权利要求1-9任一项所述的方法，其特征在于，所述域内包括接入网域内，核心网域内，传输域内，数据中心域内和虚拟资源域内中的至少一个。
  11. 一种故障处理方法，其特征在于，包括：
    跨域管理设备获取第一网络故障的第一故障信息和第一故障定界信息中的至少一个，所述第一故障定界信息为域内或者域外或者未知域；
    所述跨域管理设备根据所述第一故障信息或所述第一故障定界信息确定所述第一网络故障的第二故障定界信息；所述第二故障定界信息指示所述第一网络故障是否位于所述跨域管理设备的范围内，所述第二故障定界信息为跨域和单域；或者，所述第二故障定界信息指示所述第一网络故障位于第一域管理设备的范围内，所述第二故障定界信息为域管理设备指示信息；
    所述跨域管理设备根据所述第二故障定界信息对所述第一网络故障进行处理。
  12. 根据权利要求11所述的方法，其特征在于，所述跨域管理设备根据所述第一故障定界信息确定所述第一网络故障的第二故障定界信息，包括：
    当所述第一故障定界信息为域内时，则所述跨域管理设备确定所述第二故障定界信息指示所述第一网络故障的范围为单域；
    或者，当所述第一故障定界信息为域外或者未知域，且所述第一网络故障存在关联的第三网络故障，所述第三网络故障的故障定界信息为域内时，则所述跨域管理设备确定所述第二故障定界信息指示所述第一网络故障的范围为单域；
    或者，当所述第一故障定界信息为域外或者未知域，且所述第一网络故障存在关联的第三网络故障，所述第三网络故障的故障定界信息为域外时，则所述跨域管理设备确定所述第二故障定界信息指示所述第一网络故障的范围为跨域。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    当所述跨域管理设备确定所述第二故障定界信息为跨域时，所述跨域管理设备向第一域管理设备指示所述第二故障定界信息为跨域，或者所述跨域管理设备指示所述第一域管理设备删除所述第一网络故障，所述第一域管理设备为发送所述第一故障信息或第一故障定界信息的设备。
  14. 根据权利要求11所述的方法，其特征在于，所述第一故障信息包括故障类型，所述跨域管理设备根据所述第一故障信息确定所述第一网络故障的第二故障定界信息，包括：
    所述跨域管理设备根据故障定界规则和所述故障类型确定所述第二故障定界信息；所述故障定界规则包括故障类型和第二故障定界信息的关联关系。
  15. 根据权利要求11至14任一所述的方法，其特征在于，所述跨域管理设备根据所述第二故障定界信息对所述第一网络故障进行处理，包括：
    所述第二故障定界信息为跨域时，所述跨域管理设备对所述第一网络故障进行根因分析或者故障恢复处理；
    或者，所述第二故障定界信息为单域时，所述跨域管理设备根据所述第一故障信息确定发生所述第一网络故障的域管理设备，并指示所述域管理设备处理所述第一网络故障。
  16. 根据权利要求11-15任一项所述的方法，其特征在于，所述单域包括接入网域，核心网域内，传输域内，数据中心域内和虚拟资源域内中的至少一个。
  17. 一种系统，其特征在于，包括：
    域管理设备，用于获取第一网络故障的第一故障信息；根据所述第一故障信息确定所述第一网络故障的第一故障定界信息；所述第一故障定界信息指示所述第一网络故障的范围，所述第一故障定界信息为域内或者域外或者未知域；当确定所述第一故障定界信息为域外或者未知域时，向跨域管理设备发送所述第一故障信息和第一故障定界信息中的至少一个；
    所述跨域管理设备，用于获取第一网络故障的第一故障信息和第一故障定界信息中的至少一个，所述第一故障定界信息为域内或者域外或者未知域；根据所述第一故障信息或所述第一故障定界信息确定所述第一网络故障的第二故障定界信息；所述第二故障定界信息指示所述第一网络故障是否位于所述跨域管理设备的范围内，所述第二故障定界信息为跨域和单域；或者，所述第二故障定界信息指示所述第一网络故障位于第一域管理设备的范围内，所述第二故障定界信息为域管理设备指示信息；根据所述第二故障定界信息对所述第一网络故障进行处理。
  18. 根据权利要求17所述的系统，其特征在于，所述域管理设备具体用于：
    当所述第一故障定界信息指示所述第一网络故障的范围为域内时，对所述第一网络故障进行根因分析或者故障恢复处理；或者，
    当所述第一故障定界信息指示所述第一网络故障的范围为域外或者未知域时，发送所述第一故障定界信息给所述跨域管理设备。
  19. 根据权利要求17至18任一所述的系统，其特征在于，所述跨域管理设备具体用于：
    所述第二故障定界信息为跨域时，对所述第一网络故障进行根因分析或者故障恢复处理；
    或者，所述第二故障定界信息为单域时，根据所述第一故障信息确定发生所述第一网络故障的域管理设备，并指示所述域管理设备处理所述第一网络故障。
  20. 一种通信装置，其特征在于，包括：
    通信单元，用于获取第一网络故障的第一故障信息；
    处理单元，用于根据所述第一故障信息确定所述第一网络故障的第一故障定界信息；所述第一故障定界信息指示所述第一网络故障的范围，所述第一故障定界信息为域内或者域外或者未知域；根据所述第一故障定界信息对所述第一网络故障进行处理。
  21. 根据权利要求20所述的装置，其特征在于，所述处理单元具体用于：
    根据所述第一故障信息确定所述第一网络故障对应的异常网元；
    根据所述异常网元确定所述第一网络故障的第一故障定界信息。
  22. 根据权利要求21所述的装置，其特征在于，所述第一故障信息包括故障类型，所述处理单元具体用于：
    若根据所述第一故障信息中的故障类型确定所述第一网络故障是由本端网元异常引起的，则将所述本端网元确定为所述异常网元；
    或者，若根据所述第一故障信息中的故障类型确定所述第一网络故障是由所述本端网元的对端网元异常引起的，则将所述对端网元确定为所述异常网元；
    其中，所述本端网元为向所述域管理设备发送所述第一故障信息的网元。
  23. 根据权利要求22所述的装置，其特征在于，所述处理单元具体用于：
    当所述异常网元为域管理设备管理的网元，则所述第一故障定界信息指示的所述第一网络故障的范围为域内；
    当所述异常网元不是所述域管理设备管理的网元，则所述第一故障定界信息指示的所述第一网络故障的范围为域外。
  24. 根据权利要求20所述的装置，其特征在于，所述第一故障信息包括故障类型，所述处理单元具体用于：
    根据故障定界规则和所述故障类型确定所述第一故障定界信息；所述故障定界规则包括故障类型和第一故障定界信息的关联关系。
  25. 根据权利要求20所述的装置，其特征在于，所述通信单元还用于：
    获取所述第一网络故障关联对象的配置信息和性能信息；
    所述处理单元具体用于：
    根据所述第一网络故障的第一故障信息、所述第一网络故障关联对象的配置信息和性能信息确定所述第一网络故障的第一故障定界信息。
  26. 根据权利要求20所述的装置，其特征在于，所述通信单元还用于：
    获取至少一个第二故障信息，所述至少一个第二故障信息中的一个第二故障信息对应一个第二网络故障；
    所述处理单元还用于：
    根据所述第一网络故障的第一故障信息和所述至少一个第二故障信息确定所述第一网络故障的第一故障定界信息。
  27. 根据权利要求20至26任一所述的装置，其特征在于，所述处理单元具体用于：
    当所述第一故障定界信息指示所述第一网络故障的范围为域内时，对所述第一网络故障进行根因分析或者故障恢复处理；或者，
    当所述第一故障定界信息指示所述第一网络故障的范围为域外或者未知域时，发送所述第一故障定界信息给跨域管理设备。
  28. 根据权利要求20-27任一项所述的装置，其特征在于，所述域内包括接入网域，核心网域内，传输域内，数据中心域内和虚拟资源域内中的至少一个。
  29. 一种通信装置，其特征在于，包括：
    通信单元，用于获取第一网络故障的第一故障信息和第一故障定界信息中的至少一个，所述第一故障定界信息为域内或者域外或者未知域；
    处理单元，用于根据所述第一故障信息或所述第一故障定界信息确定所述第一网络故障的第二故障定界信息；所述第二故障定界信息指示所述第一网络故障是否位于所述跨域 管理设备的范围内，所述第二故障定界信息为跨域和单域；或者，所述第二故障定界信息指示所述第一网络故障位于第一域管理设备的范围内，所述第二故障定界信息为域管理设备指示信息；根据所述第二故障定界信息对所述第一网络故障进行处理。
  30. 根据权利要求29所述的装置，其特征在于，所述处理单元具体用于：
    当所述第一故障定界信息为域内时，则确定所述第二故障定界信息指示所述第一网络故障的范围为单域；
    或者，当所述第一故障定界信息为域外或者未知域，且所述第一网络故障存在关联的第三网络故障，所述第三网络故障的故障定界信息为域内时，则确定所述第二故障定界信息指示所述第一网络故障的范围为单域；
    或者，当所述第一故障定界信息为域外或者未知域，且所述第一网络故障存在关联的第三网络故障，所述第三网络故障的故障定界信息为域外时，则确定所述第二故障定界信息指示所述第一网络故障的范围为跨域。
  31. 根据权利要求29所述的装置，其特征在于，所述第一故障信息包括故障类型，所述处理单元具体用于：
    根据故障定界规则和所述故障类型确定所述第二故障定界信息；所述故障定界规则包括故障类型和第二故障定界信息的关联关系。
  32. 根据权利要求29-31任一项所述的装置，其特征在于，所述单域包括接入网域，核心网域内，传输域内，数据中心域内和虚拟资源域内中的至少一个。
  33. 一种通信装置，其特征在于，包括处理器和存储器：
    所述处理器，用于执行所述存储器中存储的计算机程序或指令，当执行所述计算机程序或指令时，如权利要求1至10或11至16中任意一项所述的方法被执行。
  34. 一种芯片，其特征在于，包括处理器，所述处理器与存储器耦合，用于执行所述存储器中存储的计算机程序或指令，当所述处理器执行所述计算机程序或指令时，如权利要求1至10或11至16中任意一项所述的方法被执行。
PCT/CN2021/093822 2020-05-21 2021-05-14 一种故障处理方法、装置及系统 WO2021233224A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202010437486.0 2020-05-21
CN202010437486 2020-05-21
CN202110516232.2 2021-05-12
CN202110516232.2A CN113709777A (zh) 2020-05-21 2021-05-12 一种故障处理方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2021233224A1 true WO2021233224A1 (zh) 2021-11-25

Family

ID=78648177

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/093822 WO2021233224A1 (zh) 2020-05-21 2021-05-14 一种故障处理方法、装置及系统

Country Status (2)

Country Link
CN (1) CN113709777A (zh)
WO (1) WO2021233224A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114520994A (zh) * 2022-02-18 2022-05-20 华为技术有限公司 一种确定根因故障的方法及装置
CN115242621B (zh) * 2022-07-21 2024-01-02 北京天一恩华科技股份有限公司 网络专线监控方法、装置、设备及计算机可读存储介质
CN115988438A (zh) * 2022-12-14 2023-04-18 中国联合网络通信集团有限公司 呼叫业务数据处理方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101015157A (zh) * 2004-05-10 2007-08-08 阿尔卡特朗讯 以太网oam网络中的告警指示与抑制（ais）机制
EP2654310A1 (en) * 2010-12-15 2013-10-23 Huawei Technologies Co., Ltd. Lossy link detection method, apparatus, node and system
CN106059813A (zh) * 2016-06-14 2016-10-26 西安电子科技大学 一种基于动态时间间隔的综合探测方法
CN106301548A (zh) * 2016-07-29 2017-01-04 董小方 一种通信光缆故障定位的系统和方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101015157A (zh) * 2004-05-10 2007-08-08 阿尔卡特朗讯 以太网oam网络中的告警指示与抑制（ais）机制
EP2654310A1 (en) * 2010-12-15 2013-10-23 Huawei Technologies Co., Ltd. Lossy link detection method, apparatus, node and system
CN106059813A (zh) * 2016-06-14 2016-10-26 西安电子科技大学 一种基于动态时间间隔的综合探测方法
CN106301548A (zh) * 2016-07-29 2017-01-04 董小方 一种通信光缆故障定位的系统和方法

Also Published As

Publication number Publication date
CN113709777A (zh) 2021-11-26

Similar Documents

Publication Publication Date Title
WO2021233224A1 (zh) 一种故障处理方法、装置及系统
EP2681870B1 (en) Technique for determining correlated events in a communication system
WO2017041406A1 (zh) 一种故障定位方法及装置
CN105052076B (zh) 一种基于云计算的网元管理系统及网元管理方法
WO2022061900A1 (zh) 故障自治能力的确定方法以及相关设备
US20230281071A1 (en) Using User Equipment Data Clusters and Spatial Temporal Graphs of Abnormalities for Root Cause Analysis
US20230100296A1 (en) Communication method, apparatus, and system
CN109873730B (zh) 一种网络切片测试管理方法及相关产品
CN111586740B (zh) 最小化路测技术配置方法和基站
WO2022170921A1 (zh) 网络问题信息获取方法、装置及系统
WO2021208979A1 (zh) 一种网络故障的处理方法及装置
WO2023045931A1 (zh) 一种网络性能异常分析方法、装置及可读存储介质
US11533247B2 (en) Methods, systems, and computer readable media for autonomous network test case generation
EP3673686A1 (en) Automatic evaluation and management of slice reselection experiences
WO2021204075A1 (zh) 一种网络自动化管理方法及装置
CN115150298B (zh) 虚拟网关的测试方法及装置、存储介质、电子设备
CN116963038B (zh) 基于o-ran设备的数据处理方法和o-ran设备
CN111835534B (zh) 一种用于集群控制的方法，网络设备，主控节点装置及计算机可读存储介质
US11329868B2 (en) Automated network monitoring and control
WO2023174287A1 (zh) 一种时延分析方法及装置
Zhou et al. A Method of 5G Core Network Service Fault Diagnosis
CN115348161A (zh) 日志告警信息生成方法、装置、电子设备及存储介质
WO2022022806A1 (en) Appararus, method, and computer program
CA3234663A1 (en) Action execution system and control method thereof
CN115277357A (zh) 网络故障分析方法、装置、设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21808607

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21808607

Country of ref document: EP

Kind code of ref document: A1