Fault management method and device

Abstract

The invention provides a fault management method and device. The accuracy of fault processing can be improved. The method comprises the following steps: receiving fault management capability information from first management equipment, wherein the fault management capability information is used for indicating that the first management equipment supports to process alarms corresponding to at least one of a first alarm range, a first network range or a first fault management function; based on the fault management capability information, determining an alarm subscription request, the alarm subscription request being used for indicating a second management device to request to subscribe an alarm corresponding to at least one of alarm fields corresponding to a second alarm range, a second network range or a second fault management function; sending the alarm subscription request to the first management device; and receiving an alarm notification message from the first management device, the alarm notification message being used for notifying generation of a target alarm, and the target alarm being an alarm subscribed by a second management device.

Description

Technical Field

[0001] The present application relates to the field of network automation technology, and more specifically, to a fault management method and device in the field of network automation technology. Background Art

[0002] With the large-scale construction of the fifth generation mobile communication technology (5G) network, the scale and complexity of operators' networks are increasing, and they are faced with massive alarms every day. The identification and demarcation of important faults mainly rely on expert experience and manual analysis, which is time-consuming and inaccurate. The operation takes a long time and easily leads to a large number of invalid external lines and repeated work orders, increasing operation and maintenance costs.

[0003] The application of automation or intelligent technology (hereinafter referred to as autonomous technology) in mobile communication networks has gradually become the focus of attention and research hotspot of the industry. The industry hopes to help solve the operation and maintenance efficiency problems encountered by mobile communication networks by introducing autonomous technologies (such as artificial intelligence, machine learning, big data analysis, digital twins, etc.). As a typical operation and maintenance scenario that requires a lot of manpower and man-hours, fault handling needs to introduce autonomous technologies to improve the efficiency of fault handling, realize rapid fault discovery and handling, reduce invalid on-site work orders, and ensure the minimum impact on business. In order to improve operation and maintenance efficiency, the operator management system and the equipment vendor management system have introduced corresponding fault management autonomous functions (such as alarm correlation, fault root cause analysis, fault repair, etc.).

[0004] For example, the existing fault management process includes: the operator management system sends an alarm subscription request to the equipment vendor management system, subscribing to the alarm notification of a specific alarm type of a specific device (such as environment-related alarms, equipment-related alarms); the equipment vendor management system detects the equipment fault that the operator management system requests to subscribe to and analyzes it, generating an alarm; the equipment vendor management system sends an alarm notification to the operator management system, and the alarm notification carries information such as the alarm ID, device ID, alarm type, alarm generation time, cause, and possible repair suggestions. However, using the existing fault management process, since in actual application scenarios, the fault management functions implemented by the equipment vendor management system and the operator management system may be different, and the fault management capabilities provided may also be different, the operator management system cannot accurately subscribe to the alarm notification information of the corresponding equipment, and therefore the complexity of operation and maintenance is relatively high. Summary of the invention

[0005] The present application provides a fault management method and device, which can improve the accuracy of fault handling, thereby reducing the cost and complexity of operation and maintenance.

[0006] In a first aspect, the present application provides a fault management method, the method comprising: receiving fault management capability information from a first management device, the fault management capability information being used to indicate that the first management device supports processing an alarm corresponding to at least one of a first alarm range, a first network range, or a first fault management function, the first alarm range including a first alarm type and / or a first alarm scenario type; based on the fault management capability information, determining an alarm subscription request, the alarm subscription request being used to indicate that a second management device requests subscription to an alarm corresponding to at least one of an alarm field corresponding to a second alarm range, a second network range, or a second fault management function, wherein the first alarm range includes the second alarm range, the second alarm range includes the second alarm type and / or the second alarm scenario type, the first network range includes the second network range, and the first fault management function includes the second fault management function; sending the alarm subscription request to the first management device; receiving an alarm notification message from the first management device, the alarm notification message being used to notify the generation of a target alarm, the target alarm being the alarm subscribed to by the second management device.

[0007] Optionally, the method may be executed by a second management device. The second management device may be an operator management device.

[0008] By adopting the fault management method provided in the embodiment of the present application, an interface for fault management capability information is introduced between the first management device and the second management device, so that the second management device can accurately and in real time perceive the fault management capability of the first management device, and then combine the fault management capability information with the fault management requirements of the first management device to subscribe to alarm information, thereby improving the accuracy of fault handling and reducing the cost and complexity of operation and maintenance.

[0009] In one possible implementation, the fault management capability information includes at least one of alarm range information, network range information and fault management function information and a fault management capability information identifier. The alarm range information is used to indicate that the first management device supports processing alarms within the first alarm range, the network range information is used to indicate that the first management device supports processing alarms within the first network range, the fault management function information is used to indicate that the first management device supports processing alarms with the first fault management function, and the fault management capability information identifier is used to identify the fault management capability information.

[0010] In one possible implementation, the first alarm type includes: at least one of communication alarm, processing error alarm, environmental alarm, service quality alarm, equipment alarm, integrity alarm, operation alarm, physical resource alarm, security alarm or time domain alarm; or, the first alarm scenario type includes: at least one of base station out-of-control type failure, fronthaul / optical port type failure, clock type failure, cell decommissioning type failure or standing wave type failure; or, the first network range includes: at least one of network element list, network element type or frequency point list; or, the first fault management function includes: at least one of alarm association function, root cause analysis function, repair suggestion function or fault repair function.

[0011] In one possible implementation, the alarm subscription request includes at least one of an alarm range subscription requirement, a network range subscription requirement, and an alarm field subscription requirement corresponding to a fault management function. The alarm range subscription requirement is used to instruct the second management device to subscribe to alarms within the second alarm range, the network range subscription requirement is used to instruct the second management device to subscribe to alarms within the second network range, and the alarm field subscription requirement corresponding to the fault management function is used to instruct the second management device to subscribe to the alarm field corresponding to the second fault management function.

[0012] In a possible implementation, the method also includes: based on the alarm field corresponding to the second fault management function and the target alarm, sending a fault repair request to the first management device, the fault repair request being used to request repair of the fault corresponding to the first alarm, the first alarm including part or all of the alarms in the target alarm.

[0013] In a possible implementation manner, the method further includes: receiving a fault repair result from the first management device, where the fault repair result is used to indicate a fault that has been successfully repaired.

[0014] In a possible implementation, the fault repair request is also used to request clearing of the first alarm, and the method also includes: receiving a fault repair result from the first management device, the fault repair result is used to indicate that the fault has been successfully repaired, and the alarm corresponding to the successfully repaired fault has been cleared.

[0015] By adopting the fault management method provided in the embodiment of the present application, a fault repair task interface is introduced between the first management device and the second management device, so that the first management device can promptly repair the fault corresponding to the alarm subscribed by the second management device, thereby improving the accuracy and efficiency of fault repair, thereby reducing the cost and complexity of operation and maintenance.

[0016] In a second aspect, the present application also provides a fault management method, which includes: sending fault management capability information to a second management device, the fault management capability information being used to indicate that the first management device supports processing alarms corresponding to at least one of a first alarm range, a first network range, or a first fault management function, the first alarm range including a first alarm type and / or a first alarm scenario type; receiving an alarm subscription request from the second management device, the alarm subscription request being used to indicate that the second management device requests to subscribe to an alarm corresponding to at least one of the alarm fields corresponding to a second alarm range, a second network range, or a second fault management function, wherein the first alarm range includes the second alarm range, the second alarm range includes the second alarm type and / or the second alarm scenario type, the first network range includes the second network range, and the first fault management function includes the second fault management function; performing fault detection based on the alarm subscription request, determining to generate a target alarm, the target alarm being the alarm subscribed to by the second management device; sending an alarm notification message to the second management device, the alarm notification message being used to notify the generation of the target alarm.

[0017] Optionally, the method may be executed by a first management device. The second management device may be a device vendor management device.

[0018] By adopting the fault management method provided in the embodiment of the present application, an interface for fault management capability information is introduced between the first management device and the second management device, so that the second management device can accurately and in real time perceive the fault management capability of the first management device, and then combine the fault management capability information with the fault management requirements of the first management device to subscribe to alarm information, thereby improving the accuracy of fault handling and reducing the cost and complexity of operation and maintenance.

[0019] In one possible implementation, the fault management capability information includes at least one of alarm range information, network range information and fault management function information and a fault management capability information identifier. The alarm range information is used to indicate that the first management device supports processing alarms within the first alarm range, the network range information is used to indicate that the first management device supports processing alarms within the first network range, the fault management function information is used to indicate that the first management device supports processing alarms with the first fault management function, and the fault management capability information identifier is used to identify the fault management capability information.

[0020] In one possible implementation, the first alarm type includes: at least one of communication alarm, processing error alarm, environmental alarm, service quality alarm, equipment alarm, integrity alarm, operation alarm, physical resource alarm, security alarm or time domain alarm; or, the first alarm scenario type includes: at least one of base station out-of-control type failure, fronthaul / optical port type failure, clock type failure, cell decommissioning type failure or standing wave type failure; or, the first network range includes: at least one of network element list, network element type or frequency point list; or, the first fault management function includes: at least one of alarm association function, root cause analysis function, repair suggestion function or fault repair function.

[0021] In one possible implementation, the method also includes: receiving a fault repair request from the second management device, the fault repair request being used to request repair of the fault corresponding to the first alarm, the first alarm including part or all of the alarms in the target alarm; and based on the fault repair request, repairing the fault corresponding to the first alarm.

[0022] In a possible implementation manner, the method further includes: sending a fault repair result to the second management device, where the fault repair result is used to indicate a fault that has been successfully repaired.

[0023] In a possible implementation, the fault repair request is also used to request clearing of the first alarm. After the fault corresponding to the first alarm is repaired based on the fault repair request, the method further includes: clearing the first alarm based on the fault repair request.

[0024] In a possible implementation, the method further includes: sending a fault repair result to the second management device, where the fault repair result is used to indicate that the fault has been successfully repaired, and an alarm corresponding to the successfully repaired fault has been cleared.

[0025] By adopting the fault management method provided in the embodiment of the present application, a fault repair task interface is introduced between the first management device and the second management device, so that the first management device can promptly repair the fault corresponding to the alarm subscribed by the second management device, thereby improving the accuracy and efficiency of fault repair, thereby reducing the cost and complexity of operation and maintenance.

[0026] In a third aspect, the present application also provides a fault management device, which includes: a processor and a communication interface, the processor is coupled to the communication interface, and the processor is used to: receive fault management capability information from a first management device through the communication interface, the fault management capability information is used to indicate that the first management device supports processing alarms corresponding to at least one of a first alarm range, a first network range, or a first fault management function, the first alarm range includes a first alarm type and / or a first alarm scenario type; based on the fault management capability information, determine an alarm subscription request, the alarm subscription request is used to indicate that the second management device requests to subscribe to the alarms that meet the first An alarm corresponding to at least one of the alarm fields corresponding to the second alarm range, the second network range or the second fault management function, wherein the first alarm range includes the second alarm range, the second alarm range includes the second alarm type and / or the second alarm scenario type, the first network range includes the second network range, and the first fault management function includes the second fault management function; sending the alarm subscription request to the first management device through the communication interface; receiving an alarm notification message from the first management device through the communication interface, the alarm notification message being used to notify the generation of a target alarm, the target alarm being the alarm subscribed to by the second management device.

[0027] In one possible implementation, the fault management capability information includes at least one of alarm range information, network range information and fault management function information and a fault management capability information identifier. The alarm range information is used to indicate that the first management device supports processing alarms within the first alarm range, the network range information is used to indicate that the first management device supports processing alarms within the first network range, the fault management function information is used to indicate that the first management device supports processing alarms with the first fault management function, and the fault management capability information identifier is used to identify the fault management capability information.

[0028] In one possible implementation, the first alarm type includes: at least one of communication alarm, processing error alarm, environmental alarm, service quality alarm, equipment alarm, integrity alarm, operation alarm, physical resource alarm, security alarm or time domain alarm; or, the first alarm scenario type includes: at least one of base station out-of-control type failure, fronthaul / optical port type failure, clock type failure, cell decommissioning type failure or standing wave type failure; or, the first network range includes: at least one of network element list, network element type or frequency point list; or, the first fault management function includes: at least one of alarm association function, root cause analysis function, repair suggestion function or fault repair function.

[0029] In one possible implementation, the alarm subscription request includes at least one of an alarm range subscription requirement, a network range subscription requirement, and an alarm field subscription requirement corresponding to a fault management function. The alarm range subscription requirement is used to instruct the second management device to subscribe to alarms within the second alarm range, the network range subscription requirement is used to instruct the second management device to subscribe to alarms within the second network range, and the alarm field subscription requirement corresponding to the fault management function is used to instruct the second management device to subscribe to the alarm field corresponding to the second fault management function.

[0030] In one possible implementation, the processor is also used to: based on the alarm field corresponding to the second fault management function and the target alarm, send a fault repair request to the first management device through the communication interface, wherein the fault repair request is used to request repair of the fault corresponding to the first alarm, and the first alarm includes part or all of the alarms in the target alarm.

[0031] In a possible implementation manner, the processor is further used to: receive a fault repair result from the first management device through the communication interface, where the fault repair result is used to indicate a fault that has been successfully repaired.

[0032] In a possible implementation, the fault repair request is also used to request clearing of the first alarm, and the processor is also used to: receive a fault repair result from the first management device, the fault repair result is used to indicate that the fault has been successfully repaired, and the alarm corresponding to the successfully repaired fault has been cleared.

[0033] In a fourth aspect, the present application also provides a fault management device, which includes: a processor and a communication interface, the processor is coupled to the communication interface, and the processor is used to: send fault management capability information to a second management device through the communication interface, the fault management capability information is used to indicate that the first management device supports processing an alarm corresponding to at least one of a first alarm range, a first network range, or a first fault management function, the first alarm range includes a first alarm type and / or a first alarm scenario type; receive an alarm subscription request from the second management device through the communication interface, the alarm subscription request is used to indicate that the second management device requests a subscription to be full An alarm corresponding to at least one of the alarm fields corresponding to the second alarm range, the second network range or the second fault management function, wherein the first alarm range includes the second alarm range, the second alarm range includes the second alarm type and / or the second alarm scenario type, the first network range includes the second network range, and the first fault management function includes the second fault management function; performing fault detection based on the alarm subscription request to determine whether a target alarm is generated, the target alarm is the alarm subscribed to by the second management device; and sending an alarm notification message to the second management device through the communication interface, the alarm notification message being used to notify the generation of the target alarm.

[0034] In one possible implementation, the fault management capability information includes at least one of alarm range information, network range information and fault management function information and a fault management capability information identifier. The alarm range information is used to indicate that the first management device supports processing alarms within the first alarm range, the network range information is used to indicate that the first management device supports processing alarms within the first network range, the fault management function information is used to indicate that the first management device supports processing alarms with the first fault management function, and the fault management capability information identifier is used to identify the fault management capability information.

[0035] In one possible implementation, the first alarm type includes: at least one of communication alarm, processing error alarm, environmental alarm, service quality alarm, equipment alarm, integrity alarm, operation alarm, physical resource alarm, security alarm or time domain alarm; or, the first alarm scenario type includes: at least one of base station out-of-control type failure, fronthaul / optical port type failure, clock type failure, cell decommissioning type failure or standing wave type failure; or, the first network range includes: at least one of network element list, network element type or frequency point list; or, the first fault management function includes: at least one of alarm association function, root cause analysis function, repair suggestion function or fault repair function.

[0036] In one possible implementation, the alarm subscription request includes at least one of an alarm range subscription requirement, a network range subscription requirement, and an alarm field subscription requirement corresponding to a fault management function. The alarm range subscription requirement is used to instruct the second management device to subscribe to alarms within the second alarm range, the network range subscription requirement is used to instruct the second management device to subscribe to alarms within the second network range, and the alarm field subscription requirement corresponding to the fault management function is used to instruct the second management device to subscribe to the alarm field corresponding to the second fault management function.

[0037] In one possible implementation, the processor is also used to: receive a fault repair request from the second management device through the communication interface, the fault repair request being used to request repair of the fault corresponding to the first alarm, the first alarm including part or all of the alarms in the target alarm; and based on the fault repair request, repair the fault corresponding to the first alarm.

[0038] In a possible implementation manner, the processor is further configured to: send a fault repair result to the second management device through the communication interface, where the fault repair result is used to indicate a fault that has been successfully repaired.

[0039] In a possible implementation, the fault repair request is also used to request clearing of the first alarm, and the processor is further used to: after repairing the fault corresponding to the first alarm based on the fault repair request, clear the first alarm based on the fault repair request.

[0040] In a possible implementation, the processor is further used to: send a fault repair result to the second management device through the communication interface, where the fault repair result is used to indicate that the fault has been successfully repaired and an alarm corresponding to the successfully repaired fault has been cleared.

[0041] In a fifth aspect, the present application also provides a fault management device, which is used to implement the methods described in the above aspects or any possible implementation thereof, and the device includes a unit for implementing the methods described in the above aspects or any possible implementation thereof.

[0042] In a sixth aspect, the present application also provides a computer-readable storage medium for storing a computer program, characterized in that the computer program includes instructions for implementing the methods described in the above aspects or any possible implementation methods thereof.

[0043] In the seventh aspect, the present application also provides a computer program product, which includes instructions, characterized in that when the instructions are executed on a computer or a processor, the computer or the processor implements the method described in the first aspect or any possible implementation thereof.

[0044] The fault management device, computer storage medium and computer program product provided in this application are all used to execute the fault management method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the fault management method provided above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Figure 1 A schematic architecture diagram of an autonomous network 100 provided in an embodiment of the present application;

[0046] Figure 2 A schematic flow chart of a fault management method 200 provided in an embodiment of the present application;

[0047] Figure 3 A schematic flow chart of a fault management method 300 provided in an embodiment of the present application;

[0048] Figure 4 A schematic block diagram of a fault management device 400 provided in an embodiment of the present application;

[0049] Figure 5 A schematic block diagram of a fault management device 500 provided in an embodiment of the present application;

[0050] Figure 6 A schematic block diagram of a fault management device 600 provided in an embodiment of the present application;

[0051] Figure 7 A schematic block diagram of a fault management device 700 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0052] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0053] First, some professional terms involved in the embodiments of this application are introduced.

[0054] 1. Fault: A function cannot be implemented normally according to the specified operation. In the communication system, it refers to the failure of a function of a network element device or network element management device to be implemented normally according to the specified operation.

[0055] 2. Alarm: Information reported by network element equipment or network element management equipment when a fault is discovered during polling.

[0056] 3. Interface model information (Information Model): describes the interaction information between the two systems, where isReadable=True describes that the interface caller can read the parameter, and isReadable=False describes that the interface caller cannot read the parameter; isWritable=True describes that the interface caller can specify the parameter value, and isWritable=False describes that the interface caller cannot specify the parameter value.

[0057] Optionally, the interface model information may be carried in a management object.

[0058] 4. Management Function (MnF): refers to the logical function that provides specific network or service management capabilities.

[0059] 5. Managed Object: It is used to describe the information about a managed object or management task in the management system. The managed object information model can be used as an interaction parameter in the management interface. Creating a managed object means creating management information in the management system, so that the management system can manage the managed object or perform the management task based on the management information.

[0060] The following will further introduce the autonomous network to which the fault management method and device provided in the embodiments of the present application are applied.

[0061] Figure 1FIG. 1 shows a schematic architecture diagram of an autonomous network 100 provided in an embodiment of the present application, and the autonomous network 100 is suitable for application scenarios of network operation and maintenance. Figure 1 As shown, the autonomous network 100 may include: a service operation unit 110 , a cross-domain management function unit 120 , a domain management function unit 130 and a network element 140 .

[0062] Among them, the domain management function unit 130 and the network element 140 constitute a single-domain autonomous network A, the single-domain autonomous network A and the cross-domain management function unit 120 constitute a cross-domain autonomous network B, and the cross-domain autonomous network B and the service operation unit 110 constitute a service autonomous network C.

[0063] It should also be noted that Figure 1 In the description, only the autonomous network 100 including one business autonomous network (such as the business autonomous network C) is taken as an example. Optionally, the autonomous network 100 may also include other business autonomous networks, that is, the autonomous network 100 may include two or more business autonomous networks, which is not limited in the embodiments of the present application.

[0064] It should also be noted that Figure 1 In the description, only the service autonomous network C includes one cross-domain autonomous network (such as the cross-domain autonomous network B) as an example. Optionally, the service autonomous network C may also include other cross-domain autonomous networks, that is, the service autonomous network C may include two or more cross-domain autonomous networks, which is not limited to this embodiment of the present application.

[0065] It should also be noted that Figure 1 In the description, only the example in which the cross-domain autonomous network B includes one single-domain autonomous network (such as the single-domain autonomous network A) is used for introduction. Optionally, the cross-domain autonomous network B may also include other single-domain autonomous networks, that is, the cross-domain autonomous network B may include two or more single-domain autonomous networks, which is not limited to this embodiment of the present application.

[0066] It should also be noted that Figure 1 In the description, only an example is given in which each single-domain autonomous network includes one network element (such as the single-domain autonomous network A1 includes the network element 141). Optionally, each single-domain autonomous network may also include network elements, that is, each single-domain autonomous network may include two or more network elements, which is not limited in the embodiments of the present application.

[0067] The following will introduce in detail the various units involved in the autonomous network 100.

[0068] The business operation unit described in the embodiments of the present application may also be referred to as a communication service management function unit. The business operation unit may provide functions and management services such as billing, settlement, accounting, customer service, operations, network monitoring, communication service life cycle management, and business intent translation.

[0069] For example, the business operation unit may include an operator's operation system or a vertical operational technology system.

[0070] The cross-domain management function unit described in the embodiment of the present application may also be referred to as a network management function unit (network management function, NMF), which may provide one or more of the following functions or management services: network lifecycle management, network deployment, network fault management, network performance management, network configuration management, network assurance, network optimization function, intent from communication service provider (intent-CSP), i.e., translation of business intent, intent from communication service consumer (intent-CSC), i.e., translation of business intent, etc. The network here may include one or more network elements, subnetworks, or network slices.

[0071] By way of example, the cross-domain management functional unit may be a network slice management function (NSMF), a management data analytical function (MDAF), a cross-domain self-organization network function (SON-function), or a cross-domain intent management functional unit.

[0072] It should be noted that in some deployment scenarios, the cross-domain management functional unit can also provide one or more of the following management functions or management services: sub-network lifecycle management, sub-network deployment, sub-network fault management, sub-network performance management, sub-network configuration management, sub-network assurance, sub-network optimization function, communication service provider sub-network intention translation, communication service user sub-network intention translation, etc. Among them, the sub-network can be composed of multiple small sub-networks or multiple network slice sub-networks.

[0073] The domain management function unit described in the embodiment of the present application may also be referred to as a subnetwork management function (NMF) or a network element management function unit (network element / function management function). The domain management function unit may provide one or more of the following functions or management services: lifecycle management of subnetworks or network elements, deployment of subnetworks or network elements, fault management of subnetworks or network elements, performance management of subnetworks or network elements, assurance of subnetworks or network elements, optimization management of subnetworks or network elements, intent translation of subnetworks or network elements, etc. The subnetwork here includes one or more network elements; or, the subnetwork here may also include one or more subnetworks, that is, one or more subnetworks form a subnetwork with a larger coverage; or, the subnetwork here may also include one or more network slice subnetworks.

[0074] For example, a subnetwork may include one of the following descriptions: a network in a certain technical domain, such as a wireless access network, a core network, a transmission network, etc.; a network of a certain standard, such as a GSM network, an LTE network, a 5G network, etc.; a network provided by a certain equipment vendor, such as a network provided by equipment vendor X, etc.; a network in a certain geographical area, such as a network in factory A, a network in prefecture-level city B, etc.

[0075] It should be noted that the domain management function unit described in the embodiment of the present application may be installed with software or hardware of a fault management function FaultHandlingFunction. Among them, one domain management function unit may implement multiple fault management functions FaultHandlingFunction, and each fault management function may handle a different scope, where the scope may be a geographical area, device type, network standard or fault type, etc.

[0076] For example, fault management function 1 handles wireless equipment faults within geographic area 1, fault management function 2 handles wireless equipment faults within geographic area 2, and fault management function 3 handles wireless performance faults within geographic area 2.

[0077] The network elements described in the embodiments of the present application may be entities that provide network services, including core network elements, access network elements, etc.

[0078] By way of example, core network elements may include, but are not limited to, access and mobility management function (AMF) entity, session management function (SMF) entity, policy control function (PCF) entity, network data analysis function (NWDAF) entity, network repository function (NRF), gateway, etc.

[0079] By way of example, the access network elements may include, but are not limited to, various types of base stations (e.g., next generation base stations (generationnode B, gNB), evolved base stations (evolved Node B, eNB), centralized control units (central unit control panel, CUCP), centralized units (central unit, CU), distributed units (distributed unit, DU), centralized user plane units (central unit user panel, CUUP), etc.

[0080] It should be noted that under the service-oriented management architecture, the focus is on management service providers (Management Service Producer, MnS Producer) and management service consumers (Management Service Consumer, MnS Consumer).

[0081] For example, when the management service is the management service provided by the above-mentioned business operation unit, the business operation unit may be the management service provider, and other business operator units may be the management service consumer; or, when the management service is the management service provided by the above-mentioned cross-domain management function unit, the cross-domain management function unit may be the management service provider, and the business operation unit may be the management service consumer; or, when the management service is the management service provided by the above-mentioned domain management function unit, the domain management function unit may be the management service provider, and the cross-domain management function unit or the business operation unit may be the management service consumer; or, when the management service is the management service provided by the above-mentioned network element, the network element may be the management service provider, and the domain management function unit, the cross-domain management function unit or the business operation unit may be the management service consumer.

[0082] The following will be combined Figure 1 The autonomous network 100 introduced in the specification further introduces the fault management method and device provided in the embodiments of the present application.

[0083] Figure 2 FIG. 2 shows a schematic flow chart of a fault management method 200 provided in an embodiment of the present application. Figure 2 As shown, the method 200 can be applied to Figure 1 The method 200 may include the following steps S210 to S212. It should be noted that the following steps may be performed in various orders and / or occur simultaneously, not limited to: Figure 2 The execution order shown.

[0084] S201. The domain management function unit sends fault management capability information (FaultHandling Capability) to the cross-domain management function unit, and the fault management capability information includes at least one of a fault management capability information identifier, alarm scope information, network scope information or fault management function information. The fault management capability information identifier is used to identify the fault management capability information, the alarm scope information is used to indicate the first alarm type (supported Alarm Type) or the first alarm scenario type (supported Alarm Scenario Type) supported by the domain management function unit, the network scope information is used to indicate the first network scope (supported Network Scope) supported by the domain management unit, and the fault management function information is used to indicate the first fault management function supported by the domain management function unit.

[0085] For example, the cross-domain management function unit can manage equipment for an operator, and the domain management function unit can manage equipment for an equipment manufacturer, and corresponding fault management functions are deployed on both the cross-domain management function unit and the domain management function unit.

[0086] For example, in a service-oriented management architecture, the cross-domain management functional unit may be a management service consumer, and the domain management functional unit may be called a management service provider.

[0087] For example, taking radio access network (RAN) domain fault management as an example, the domain management functional unit may be a RAN domain management functional unit, and the network element may be a base station.

[0088] Optionally, the alarm type described in the embodiment of the present application (such as the first alarm type) may include at least one of the following: communication alarm (Communications Alarm), processing error alarm (Processing Error Alarm), environmental alarm (Environmental Alarm), service quality alarm (Quality of Service Alarm), equipment alarm (Equipment Alarm), integrity alarm (Integrity Violation), operation alarm (Operational Violation), physical resource alarm (Physical Violation), security alarm (Security Service or Mechanism Violation) or time domain alarm (Time Domain Violation).

[0089] Optionally, the alarm scenario type described in the embodiment of the present application (such as the first alarm scenario type), which may also be referred to as a fault type, may include at least one of the following items: base station out-of-control type fault, fronthaul / optical port type fault, clock type fault, cell decommissioning type fault and standing wave type fault, etc.

[0090] It should be noted that the above-mentioned alarm scenario types may include one or more alarm types.

[0091] For example, base station out-of-control faults may include communication alarms and equipment alarms.

[0092] It should be noted that the first network scope supportedNetworkScope supported by the domain management function unit described in the embodiment of the present application may indicate that the domain management function unit supports handling of faults within the first network scope.

[0093] Optionally, the network range (such as the first network range) described in the embodiment of the present application may include at least one of the following three items (A) to (C):

[0094] (A) a network element list NEList, i.e., one or more network element identifiers; when the network range includes a network element list, it may indicate that the domain management function unit supports handling of faults of network elements in the network element list;

[0095] (B) network element type NEType, i.e., one or more network element types; when the network range includes a network type, it may indicate that the domain management function unit supports handling of faults of network elements of the network element type;

[0096] (C) FrequencyList, i.e., one or more network frequencies; when the network range includes the frequency list, it may indicate that the domain management function unit supports handling faults of network elements corresponding to the frequency list.

[0097] It should be noted that the first fault management function SupportedAlarmHandlingFuns supported by the domain management function unit described in the embodiment of the present application can indicate that the domain management function unit supports the processing function of the alarm with the first fault management function.

[0098] Optionally, the fault management function (such as the first fault management function) described in the embodiment of the present application may include at least one of the following four items (a) to (d):

[0099] (a) Alarm correlation function, which combines or compresses multiple alarms with correlation. For example, alarms are correlated or compressed based on a 2-minute time window, that is, if two alarms occur within 1 minute of each other, the two alarms are correlated;

[0100] (b) Root cause analysis function: to perform problem demarcation and location analysis based on the identified faults to determine the root cause of the fault;

[0101] (c) Repair suggestion function, which generates several alternative repair solutions based on the root cause analysis results (such as modifying the configuration, restarting the network element, isolating the network element, replacing the single board, etc.);

[0102] (d) Fault repair function: comprehensively evaluate the alternative modification plans and give the most effective plan to execute, thereby repairing the fault and eliminating the alarm.

[0103] Optionally, a fault management capability information may be: fault management capability information for a specific supported alarm type or alarm scenario type; fault management capability information for a specific supported fault management function;

[0104] For example, FaultHandlingCapability#1 is the fault management capability information of the alarm type "device alarm", and the supported fault management functions are "alarm correlation" + "root cause analysis".

[0105] For example, FaultHandlingCapability#2 is the fault management capability information of the alarm type "communication alarm", and the supported fault management functions are "alarm association" + "root cause analysis" + "repair suggestion" + "fault repair".

[0106] For example, FaultHandlingCapability#3 is the fault management capability information of the fault management function being "root cause analysis", and the supported alarm types are "communication alarm" + "processing error alarm" + "environment alarm" + "service quality alarm" + "equipment alarm" + "integrity alarm" + "operation alarm".

[0107] For example, FaultHandlingCapability#3 is the fault management capability information of the fault management function "fault repair", and the supported alarm types are "communication alarm" + "processing error alarm" + "operation alarm". ;

[0108] Optionally, the domain management function unit may also send a fault management function identifier corresponding to the fault management capability information to the cross-domain management function unit, where the fault management function identifier is used to identify a fault management function supported by the domain management function unit.

[0109] Optionally, a fault management object may support one or more fault management capability information.

[0110] Optionally, the fault management function identifier may be carried in the fault management capability information, or the domain management function unit may also send fault management function information to the cross-domain management function unit, and the fault management function identifier may be carried in the fault management function information.

[0111] Optionally, before S201, the method may further include: the domain management function unit configuring the fault management capability information in a management object of the fault management function.

[0112] As an example, Table 1 shows a management object of a fault management function, wherein the management object is configured with fault management capability information.

[0113] Table 1

[0114] property Is it readable? Is it compatible? Managed Object Id of the Alarm Handling Function yes no Fault management capability information (Alarm Handling Capabilities) yes no

[0115] For example, Table 2 shows the specific contents of the fault management capability information in Table 1.

[0116] Table 2

[0117]

[0118] Optionally, before 201, the method may further include: the cross-domain management function unit sends a fault management capability information query request to the domain management unit, where the fault management capability information query request is used to request to query the fault management capability information.

[0119] Optionally, the embodiment of the present application does not limit the specific format of the fault management capability information query request.

[0120] In one possible implementation, the fault management capability information query request may carry at least one of the following items: a fault management function identifier, used to query the fault management capability information of a specified fault management function; a network range, used to query the fault management capability information within a specified network range; an alarm type or alarm scenario type, used to query the fault management capability information of a specified alarm type or alarm scenario type.

[0121] In another possible implementation manner, the fault management capability information query request may not include the above information, that is, all fault management capability information supported by the domain management function unit is requested by default.

[0122] Optionally, the fault management capability information query request sent by the cross-domain management function unit to the domain management unit may be an information query request for a fault management function object, and the information query request for the fault management function object may carry the fault management function object identifier and indication information for indicating the query of fault management capability information.

[0123] S202. The cross-domain management function unit determines an alarm subscription request according to the fault management capability information, where the alarm subscription request includes at least one of a network scope subscription requirement, an alarm scope subscription requirement, or an alarm field subscription requirement corresponding to the fault management function.

[0124] It should be noted that the alarm range subscription requirement is used to instruct the operator management device to subscribe to the alarms within the second alarm range, the network range subscription requirement is used to instruct the operator management device to subscribe to the alarms within the second network range, and the alarm field subscription requirement corresponding to the fault management function is used to instruct the operator management device to subscribe to the alarm field corresponding to the second fault management function and the network range supported in the fault management capability information.

[0125] The alarm field requirements corresponding to the fault management function may include at least one of a correlated Notifications field, a probable Cause field, a specific Problem field, a root Cause Indication field, or a proposed Repair Actions field.

[0126] Optionally, the cross-domain management function unit may determine the alarm subscription request according to the fault management capability information in a variety of ways, which is not limited in the embodiment of the present application.

[0127] In a possible implementation, the cross-domain management function unit may determine the second alarm type subscription requirement in the alarm subscription request according to the first alarm type in the fault management capability information and its own alarm monitoring requirement.

[0128] Optionally, the alarm type in the alarm type subscription requirement may be part or all of the alarm types supported by the domain management function unit, which is not limited in this embodiment of the present application.

[0129] For example, if the operator does not pay attention to alarms of certain alarm types (such as environmental alarms), that is, there is no corresponding monitoring demand, the cross-domain management function unit does not need to subscribe to alarms of the alarm types.

[0130] In another possible implementation, the cross-domain management function unit may determine the alarm scenario type subscription requirement in the alarm subscription request according to the alarm scenario type in the fault management capability information and its own alarm monitoring requirement.

[0131] Optionally, the alarm scenario type in the alarm scenario type requirement may be part or all of the alarm scenario types supported by the domain management function unit.

[0132] For example, if the operator does not pay attention to alarms of certain alarm scenario types (such as clock failures), that is, there is no corresponding monitoring demand, the cross-domain management function unit does not need to subscribe to the alarm scenario of the alarm scenario type.

[0133] In yet another possible implementation, the cross-domain management function unit may determine the network scope subscription requirement in the alarm subscription request according to the network scope in the fault management capability information and its own alarm monitoring requirement.

[0134] Optionally, the network range in the network range subscription requirement may be part or all of the network range supported by the domain management functional unit.

[0135] For example, if the operator does not pay attention to the alarm of a certain network range (such as a certain network element), that is, there is no corresponding monitoring demand, then the cross-domain management function unit does not need to subscribe to the network range.

[0136] In another possible implementation, the cross-domain management function unit can determine the fault management function requirements of the domain management function unit based on the fault management function in the fault management capability information and its own fault management function; and based on the fault management function requirements, determine the alarm field subscription requirements corresponding to the fault management function in the alarm subscription request.

[0137] Optionally, the fault management function in the fault management function requirement may be part or all of the fault management functions supported by the domain management function unit.

[0138] For example, taking the domain management function unit supporting all fault management functions including alarm association, root cause analysis, repair suggestions and fault repair as an example, for the above-determined alarm type subscription requirements (or alarm scenario type subscription requirements) and the corresponding alarms (such as communication alarms) determined by the network scope subscription requirements, the cross-domain management function unit itself does not implement any fault management functions, then the cross-domain management function unit determines that the domain management function unit needs to provide all fault management functions, including alarm association, root cause analysis, repair suggestions and fault repair. Therefore, the corresponding alarm field subscription requirements include: the associated alarm field corresponding to the alarm association function, the possible cause field corresponding to the root cause analysis function, the specific problem field and the root alarm indication field and the recommended repair action field corresponding to the fault repair suggestion function;

[0139] For example, take the domain management function unit as an example, all fault management functions supported by the domain management function unit include: alarm correlation, root cause analysis, repair suggestions and fault repair. For the corresponding alarms (such as device alarms) determined by the determined alarm type subscription requirements (or alarm scenario type subscription requirements) and network scope subscription requirements, the cross-domain management function unit implements the repair suggestion and fault repair functions by itself, and then the cross-domain management function unit determines that the domain management function unit needs to provide alarm association, alarm prediction and root cause analysis functions. Therefore, the corresponding alarm field subscription requirements include: the associated alarm field corresponding to the alarm association function, the possible cause field corresponding to the root cause analysis function, the specific problem field and the root alarm indication field.

[0140] For example, all fault management functions supported by the domain management function unit include: alarm association, root cause analysis, repair suggestions and fault repair. For the corresponding alarms (such as environmental alarms) determined by the determined alarm type subscription requirements (or alarm scenario type subscription requirements) and network scope subscription requirements, the cross-domain management function unit implements the root cause analysis, repair suggestions and fault repair functions by itself, and the cross-domain management function unit determines that the domain management function unit needs to provide alarm association. Therefore, the corresponding alarm field subscription requirements include: the associated alarm field corresponding to the alarm association function.

[0141] For example, taking all the fault management functions supported by the domain management function unit including: alarm association, root cause analysis, repair suggestions and fault repair as an example, for the corresponding alarms determined by the determined alarm type subscription requirements (or alarm scenario type subscription requirements) and the network range subscription requirements (such as service quality alarms), the cross-domain management function unit itself implements the alarm association, root cause analysis, repair suggestions and fault repair functions. If the cross-domain management function unit determines that the domain management function unit does not need to provide any fault management functions, then there is no corresponding alarm field subscription requirement.

[0142] S203. The cross-domain management function unit sends the alarm subscription request to the domain management function unit.

[0143] Optionally, after S203, the method may further include: the domain management function unit sends an alarm subscription success confirmation message to the cross-domain management function unit, and the alarm subscription success confirmation message carries an alarm subscription identifier; accordingly, the cross-domain management function unit receives the alarm subscription success confirmation message from the domain management function unit.

[0144] S204. The domain management function unit performs fault detection according to the alarm subscription request and obtains alarm information, where the alarm information is used to indicate the generation of a target alarm.

[0145] Optionally, the alarm information may include at least one of an alarm identifier of the target alarm, an alarm type, an alarm generation time, or an identifier of a network element that generates the target alarm.

[0146] Optionally, the domain management functional unit may also receive alarm information from the network, that is, the alarm information is obtained by detecting a fault by a network element and sent to the domain management functional unit.

[0147] S205. The domain management function unit determines, according to the alarm subscription request, that the target alarm is an alarm subscribed by the cross-domain management function unit.

[0148] S206. The domain management function unit sends an alarm notification message to the cross-domain management function unit, wherein the alarm notification message carries the alarm information.

[0149] Optionally, the domain management function unit may determine whether the target alarm is an alarm subscribed to by the cross-domain management function unit according to the alarm subscription request in a variety of ways, which is not limited in this embodiment of the present application.

[0150] In one possible implementation, if the alarm information includes the alarm type of the target alarm and the network element identifier that generates the target alarm, the domain management functional unit determines that the target alarm is an alarm subscribed to by the cross-domain management functional unit based on the alarm type of the target alarm and the network element that generates the target alarm, which belong to the alarm type and network range subscribed to by the cross-domain management functional unit.

[0151] By adopting the fault management method provided in the embodiment of the present application, an interface for fault management capability information is introduced between the equipment vendor management equipment and the operator management equipment, so that the operator management equipment can accurately and in real time perceive the fault management capability of the equipment vendor management equipment, and then combine the fault management capability information with the fault management requirements of the equipment vendor management equipment to subscribe to alarm information, thereby improving the accuracy of fault handling and reducing the cost and complexity of operation and maintenance.

[0152] S207. The domain management function unit analyzes the fault corresponding to the target alarm according to the alarm subscription request, and obtains the alarm field corresponding to the second fault management function.

[0153] In one possible implementation, if the alarm field subscription requirement corresponding to the second fault management function includes the associated alarm field corresponding to the alarm association function, the domain management function unit performs a correlation analysis on the target alarm and other alarms, determines at least one alarm associated with the target alarm, and generates a value for the associated alarm field, where the value of the associated alarm field is the alarm identifier of the at least one alarm.

[0154] In another possible implementation, if the alarm field subscription requirement corresponding to the second fault management function includes the possible cause field, the specific problem field and the root alarm indication field corresponding to the root cause analysis function, the domain management function unit performs root cause analysis on the target alarm and other alarms, determines the root cause of the target alarm, and generates the value of the possible cause field, the value of the specific problem field and the value of the root alarm indication field. For example, the value of the possible cause field includes signal attenuation (DEGRADED SIGNAL), frame loss (LOSS OF FRAME), backup board failure (BACK PLANE FAILURE) and data set problem (DATASET PROBLEM), the specific problem field includes base station out of control and cell out of service, etc., and the value of the root alarm indication field is used to indicate whether the alarm is a root alarm.

[0155] In another possible implementation, if the alarm field subscription requirement corresponding to the second fault management function includes a field for a repair suggestion action corresponding to the repair suggestion function, the domain management function unit determines the value of the corresponding field covering the recommended action based on a pre-stored fault repair experience rule or model, and the value may be configuration modification, network element restart, network element isolation, and board replacement, etc.

[0156] S208. The domain management function unit sends an alarm change notification message to the cross-domain management function unit. The alarm change notification message is used to notify that the alarm notification message has changed. The alarm change notification message carries the alarm identifier of the target alarm and the alarm field corresponding to the second fault management function.

[0157] S209. The cross-domain management function unit determines whether to request the domain management function unit to repair the fault corresponding to the target alarm and clear the target alarm according to the alarm change notification message and the fault management capability information.

[0158] In one possible implementation, when the fault management capability information indicates that the domain management function unit supports the repair function of the fault of the target alarm, the cross-domain management function unit determines to request the domain management function unit to repair the fault corresponding to the target alarm based on the alarm field corresponding to the second fault management function.

[0159] Optionally, when the cross-domain management function unit obtains the value of the field of the proposed repair action (proposed Repair Actions) corresponding to the repair suggestion function, and determines that the value of the proposed repair action given by the domain management function unit complies with the preset policy or rule of the cross-domain management function unit, it determines to request the domain management function unit to repair the fault corresponding to the target alarm.

[0160] S210. The cross-domain management function unit sends a fault recovery request (FaultRecovery request) to the domain management function unit, where the fault recovery request is used to request to repair the fault corresponding to the first alarm, where the first alarm includes part or all of the target alarms.

[0161] Optionally, the fault repair request may include fault recovery task management object creation request information, and the fault recovery task management object creation request information is used to request the creation of a fault recovery task management object.

[0162] In a possible implementation, the fault recovery task management object creation request information may include an alarm identifier of the first alarm and alarm clear indication information Alarm Clear Indicator, where the alarm clear indication information is used to indicate clearing of the first alarm.

[0163] Optionally, the fault repair request may include an alarm identifier of the first alarm and / or alarm clear indication information Alarm Clear Indicator, where the alarm clear indication information is used to indicate clearing of the first alarm.

[0164] Optionally, the alarm clearing indication information is also used to instruct the domain management function unit whether to clear the alarm information immediately, that is, delete the alarm record, after the fault corresponding to the alarm identifier of the first alarm is repaired.

[0165] S211. The domain management function unit repairs the fault corresponding to the alarm identifier of the first alarm according to the fault repair request, and clears the first alarm.

[0166] Optionally, before S211, the domain management function unit creates a fault recovery task management object based on the fault recovery task management object creation request, and configures the alarm identifier of the first alarm and the alarm clearing indication information in the fault recovery task management object; accordingly, after S211, the domain management function unit configures the fault recovery result information in the fault recovery task management object.

[0167] For example, Table 3 shows a fault recovery task management object, wherein the fault recovery task management object is configured with fault recovery result information.

[0168] Table 3

[0169] property Is it readable? Is it compatible? Fault Recovery Job Managed Object Id yes no Alarm Ids yes no Alarm Clear Indicators yes no Fault Recovery Result yes no

[0170] S212. The domain management function unit sends a fault repair result to the cross-domain management function unit, where the fault repair result is used to indicate whether the fault is successfully repaired and the alarm corresponding to the successfully repaired fault is cleared, wherein the successfully repaired fault may include part or all of the faults corresponding to the first alarm.

[0171] In a possible implementation, the fault repair result may include an alarm identifier corresponding to the successfully repaired fault.

[0172] Optionally, if there are still faults that have not been repaired successfully, the fault repair result may also include an alarm identifier corresponding to the fault that has not been repaired successfully.

[0173] Optionally, the domain management function unit may also send a fault recovery task management object change notification to the cross-domain management function unit, where the fault recovery task management object change notification includes the fault recovery task identifier and the fault recovery result.

[0174] By adopting the fault management method provided in the embodiment of the present application, a fault repair task interface is introduced between the equipment manufacturer management device and the operator management device, so that the equipment manufacturer management device can promptly repair the faults corresponding to the alarms subscribed to by the operator management device, thereby improving the accuracy and efficiency of fault repair, thereby reducing the cost and complexity of operation and maintenance.

[0175] Figure 3 FIG. 3 is a schematic flow chart of a fault management method 300 provided in an embodiment of the present application. Figure 3 As shown, the method 300 can be applied to Figure 1 The method 300 may include the following steps S301 to S305. It should be noted that the following steps may be performed in various orders and / or occur simultaneously, not limited to: Figure 3 The execution order shown.

[0176] It should be noted that Figure 3 For parts not described in detail, please refer to Figure 2 To avoid repetition, the corresponding parts of the introduction will not be repeated here.

[0177] S301. The first management device sends fault management capability information to the second management device, where the fault management capability information is used to indicate that the first management device supports processing alarms corresponding to at least one of a first alarm range, a first network range, or a first fault management function, where the first alarm range includes a first alarm type and / or a first alarm scenario type; accordingly, the second management device receives the fault management capability information from the first management device.

[0178] In a possible implementation, the first management device may be Figure 1 The domain management functional unit in the second management device may be Figure 1 The cross-domain management functional unit in.

[0179] For example, the first management device may be a device management device of a device vendor, and the second management device may be a device management device of an operator.

[0180] In one possible implementation, the fault management capability information includes at least one of alarm range information, network range information and fault management function information and a fault management capability information identifier. The alarm range information is used to indicate that the first management device supports processing alarms within the first alarm range, the network range information is used to indicate that the first management device supports processing alarms within the first network range, the fault management function information is used to indicate that the first management device supports processing alarms with the first fault management function, and the fault management capability information identifier is used to identify the fault management capability information.

[0181] Optionally, before S301, the method may further include: the second management device sends a fault management capability information query request to the first management device, and the fault management capability information query request is used to request query of the fault management capability information; accordingly, S301 may include: the first management device sends the fault management capability information to the second management device based on the fault management capability information query request.

[0182] S302. The second management device determines an alarm subscription request based on the fault management capability information, and the alarm subscription request is used to indicate that the second management device requests to subscribe to an alarm corresponding to at least one of the alarm fields corresponding to the second alarm range, the second network range or the second fault management function, wherein the first alarm range includes the second alarm range, the second alarm range includes the second alarm type and / or the second alarm scenario type, the first network range includes the second network range, and the first fault management function includes the second fault management function; accordingly, the first management device receives the alarm subscription request from the second management device.

[0183] Optionally, the second management device may determine the alarm reading request based on the fault management capability information and its own alarm monitoring requirements.

[0184] In one possible implementation, the alarm subscription request includes at least one of an alarm range subscription requirement, a network range subscription requirement, and an alarm field subscription requirement corresponding to a fault management function. The alarm range subscription requirement is used to instruct the second management device to subscribe to alarms within the second alarm range, the network range subscription requirement is used to instruct the second management device to subscribe to alarms within the second network range, and the alarm field subscription requirement corresponding to the fault management function is used to instruct the second management device to subscribe to the alarm field corresponding to the second fault management function.

[0185] Optionally, the first network range may be the same as the second network range, or the second network range may include part or all of the first network range, which is not limited in this embodiment of the present application.

[0186] For example, the first range includes network element table A, the second range includes network element table B, and the network element table B includes part or all of the network elements in the network element table A.

[0187] Optionally, the first alarm type may be the same as the second alarm type, or the second alarm type may include part or all of the first alarm type, which is not limited in the embodiment of the present application.

[0188] Illustratively, the first alarm type includes communication alarms, equipment alarms, and integrity alarms, and the second alarm type includes communication alarms and integrity alarms.

[0189] Optionally, the first alarm scenario type may be the same as the second alarm scenario type, or the second alarm scenario type may include part or all of the first alarm scenario type, which is not limited in this embodiment of the present application.

[0190] For example, the first alarm scenario type includes base station out-of-control failures, fronthaul / optical port failures, clock failures, and cell out-of-service failures, and the second alarm scenario type is the same as the first alarm scenario type.

[0191] Optionally, the first fault management function may be the same as the second fault management function, or the second fault management function may include part or all of the first fault management function, which is not limited in the embodiment of the present application.

[0192] For example, the first fault management function includes an alarm correlation function, a root cause analysis function, and a repair suggestion function, and the second fault management function includes an alarm correlation function.

[0193] S303. The second management device sends the alarm subscription request to the first management device; correspondingly, the first management device receives the alarm subscription request from the operator device.

[0194] S304. The first management device performs fault detection based on the alarm subscription request and determines to generate a target alarm, where the target alarm is the alarm subscribed by the second management device.

[0195] In a possible implementation, S304 may include: the first management device performs fault monitoring based on the alarm subscription request to obtain alarm information, where the alarm information is used to indicate the generation of a target alarm; and the first management device determines, based on the alarm subscription request, that the target alarm is the alarm subscribed to by the second management device.

[0196] S305. The first management device sends an alarm notification message to the second management device, where the alarm notification message is used to notify the generation of the target alarm; correspondingly, the second management device receives the alarm notification message from the first management device.

[0197] Optionally, after SS305, the method also includes: the first management device analyzes the fault corresponding to the target alarm according to the alarm subscription request to obtain the alarm field corresponding to the second fault management function; the second management device determines whether to request the domain management function unit to repair the fault corresponding to the target alarm and clear the target alarm according to the alarm change notification message and the fault management capability information; when the fault management capability information indicates that the first management device supports the repair function of the fault of the target alarm, the second management device determines to request the first management device to repair the fault corresponding to the target alarm and clear the target alarm according to the alarm field corresponding to the second fault management function.

[0198] Optionally, after the second management device determines to request the first management device to repair the fault corresponding to the target alarm and clear the target alarm, the method also includes: the second management device sends a fault repair request to the first management device, the fault repair request is used to request to repair the fault corresponding to the first alarm and clear the first alarm, the first alarm includes part or all of the alarms in the target alarm; the first management device repairs the fault corresponding to the alarm identifier of the first alarm according to the fault repair request, and clears the first alarm; the first management device sends a fault repair result to the second management device, the fault repair result is used to indicate the fault that has been successfully repaired and whether the alarm corresponding to the successfully repaired fault has been cleared, wherein the successfully repaired fault may include part or all of the faults corresponding to the first alarm.

[0199] Combined with the above Figure 2 and Figure 3 The fault management method provided in the embodiment of the present application is introduced, and the fault management device provided in the embodiment of the present application will be further introduced below.

[0200] Figure 4 The structure diagram of the fault management device 400 provided in the embodiment of the present application is shown. The device 400 may include: a receiving unit 401, a processing unit 402 and a sending unit 403.

[0201] Optionally, the device 400 can be used in the above-mentioned autonomous network 100. Further, the device 400 can be used in the cross-domain management function unit 120 in the above-mentioned autonomous network 100, such as a virtual device formed by software executed by a processor or controller on the cross-domain management function unit 120.

[0202] The receiving unit 401 is used to receive fault management capability information from a first management device, and the fault management capability information is used to indicate that the first management device supports processing alarms corresponding to at least one of a first alarm range, a first network range or a first fault management function, and the first alarm range includes a first alarm type and / or a first alarm scenario type.

[0203] The processing unit 402 is used to determine an alarm subscription request based on the fault management capability information, and the alarm subscription request is used to indicate that the second management device requests to subscribe to an alarm corresponding to at least one of the alarm fields corresponding to the second alarm range, the second network range or the second fault management function, wherein the first alarm range includes the second alarm range, the second alarm range includes the second alarm type and / or the second alarm scenario type, the first network range includes the second network range, and the first fault management function includes the second fault management function.

[0204] The sending unit 403 is used for the first management device to send the alarm subscription request.

[0205] The receiving unit 401 is further configured to receive an alarm notification message from the first management device, wherein the alarm notification message is used to notify the generation of a target alarm, and the target alarm is an alarm subscribed by the second management device.

[0206] In one possible implementation, the fault management capability information includes at least one of alarm range information, network range information and fault management function information and a fault management capability information identifier. The alarm range information is used to indicate that the first management device supports processing alarms within the first alarm range, the network range information is used to indicate that the first management device supports processing alarms within the first network range, the fault management function information is used to indicate that the first management device supports processing alarms with the first fault management function, and the fault management capability information identifier is used to identify the fault management capability information.

[0207] In one possible implementation, the first alarm type includes: at least one of communication alarm, processing error alarm, environmental alarm, service quality alarm, equipment alarm, integrity alarm, operation alarm, physical resource alarm, security alarm or time domain alarm; or, the first alarm scenario type includes: at least one of base station out-of-control type failure, fronthaul / optical port type failure, clock type failure, cell decommissioning type failure or standing wave type failure; or, the first network range includes: at least one of network element list, network element type or frequency point list; or, the first fault management function includes: at least one of alarm association function, root cause analysis function, repair suggestion function or fault repair function.

[0208] In one possible implementation, the alarm subscription request includes at least one of an alarm range subscription requirement, a network range subscription requirement, and an alarm field subscription requirement corresponding to a fault management function. The alarm range subscription requirement is used to instruct the second management device to subscribe to alarms within the second alarm range, the network range subscription requirement is used to instruct the second management device to subscribe to alarms within the second network range, and the alarm field subscription requirement corresponding to the fault management function is used to instruct the second management device to subscribe to the alarm field corresponding to the second fault management function.

[0209] In one possible implementation, the sending unit 403 is also used to send a fault repair request to the first management device based on the alarm field corresponding to the second fault management function and the target alarm, and the fault repair request is used to request to repair the fault corresponding to the first alarm, and the first alarm includes part or all of the alarms in the target alarm.

[0210] In a possible implementation, the receiving unit 401 is further configured to receive a fault repair result from the first management device, where the fault repair result is used to indicate a fault that has been successfully repaired.

[0211] In a possible implementation, the fault repair request is also used to request clearing of the first alarm, and the receiving unit 401 is also used to: receive a fault repair result from the first management device, the fault repair result is used to indicate that the fault has been successfully repaired, and the alarm corresponding to the successfully repaired fault has been cleared.

[0212] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices are based on the same concept as the method embodiment of the present application, and their specific functions and technical effects can be specifically referred to in the method embodiment part, and will not be repeated here. In an optional example, the device 400 can be specifically the operator management device in the above-mentioned method 200 or the embodiment of the method 200, and the device 400 can be used to execute the various processes and / or steps corresponding to the operator management device in the above-mentioned method 200 or the embodiment of the method 300, and will not be repeated here to avoid repetition.

[0213] Figure 4One or more of the modules in the illustrated embodiments may be implemented by software, hardware, firmware, or a combination thereof. The software or firmware includes, but is not limited to, computer program instructions or codes, and may be executed by a hardware processor. The hardware includes, but is not limited to, various integrated circuits, such as a central processing unit (CPU), a digital signal processor (DSP), a field programmable gate array (FPGA), or an application specific integrated circuit (ASIC).

[0214] Figure 5 The structure diagram of a fault management device 500 provided in an embodiment of the present application is shown. The device 500 may include: a sending unit 501 , a receiving unit 502 , and a processing unit 503 .

[0215] Optionally, the device 500 can be used in the above-mentioned autonomous network 100. Further, the device 500 can be used in the domain management function unit 130 in the above-mentioned autonomous network 100, such as a virtual device formed by software executed by a processor or controller on the domain management function unit 130.

[0216] The sending unit 501 is used to send fault management capability information to the second management device, and the fault management capability information is used to indicate that the first management device supports processing alarms corresponding to at least one of a first alarm range, a first network range or a first fault management function, and the first alarm range includes a first alarm type and / or a first alarm scenario type.

[0217] The receiving unit 502 is used to receive an alarm subscription request from the second management device, and the alarm subscription request is used to indicate that the second management device requests to subscribe to an alarm corresponding to at least one of the alarm fields corresponding to the second alarm range, the second network range or the second fault management function, wherein the first alarm range includes the second alarm range, the second alarm range includes the second alarm type and / or the second alarm scenario type, the first network range includes the second network range, and the first fault management function includes the second fault management function.

[0218] The processing unit 503 is configured to perform fault detection based on the alarm subscription request and determine to generate a target alarm, where the target alarm is an alarm subscribed to by the second management device.

[0219] The sending unit 501 is further used to send an alarm notification message to the second management device, where the alarm notification message is used to notify that the target alarm is generated.

[0220] In one possible implementation, the fault management capability information includes at least one of alarm range information, network range information and fault management function information and a fault management capability information identifier. The alarm range information is used to indicate that the first management device supports processing alarms within the first alarm range, the network range information is used to indicate that the first management device supports processing alarms within the first network range, the fault management function information is used to indicate that the first management device supports processing alarms with the first fault management function, and the fault management capability information identifier is used to identify the fault management capability information.

[0221] In one possible implementation, the first alarm type includes: at least one of communication alarm, processing error alarm, environmental alarm, service quality alarm, equipment alarm, integrity alarm, operation alarm, physical resource alarm, security alarm or time domain alarm; or, the first alarm scenario type includes: at least one of base station out-of-control type failure, fronthaul / optical port type failure, clock type failure, cell decommissioning type failure or standing wave type failure; or, the first network range includes: at least one of network element list, network element type or frequency point list; or, the first fault management function includes: at least one of alarm association function, root cause analysis function, repair suggestion function or fault repair function.

[0222] In one possible implementation, the alarm subscription request includes at least one of an alarm range subscription requirement, a network range subscription requirement, and an alarm field subscription requirement corresponding to a fault management function. The alarm range subscription requirement is used to instruct the second management device to subscribe to alarms within the second alarm range, the network range subscription requirement is used to instruct the second management device to subscribe to alarms within the second network range, and the alarm field subscription requirement corresponding to the fault management function is used to instruct the second management device to subscribe to the alarm field corresponding to the second fault management function.

[0223] In one possible implementation, the receiving unit 502 is also used to receive a fault repair request from the second management device, where the fault repair request is used to request repair of the fault corresponding to the first alarm, where the first alarm includes part or all of the alarms in the target alarm; the processor 503 is also used to repair the fault corresponding to the first alarm based on the fault repair request.

[0224] In a possible implementation, the sending unit 501 is further configured to send a fault repair result to the second management device, where the fault repair result is used to indicate a fault that has been successfully repaired.

[0225] In a possible implementation, the fault repair request is also used to request clearing of the first alarm, and the processor 503 is further used to clear the first alarm based on the fault repair request after repairing the fault corresponding to the first alarm based on the fault repair request.

[0226] In a possible implementation, the sending unit 501 is further used to send a fault repair result to the second management device, where the fault repair result is used to indicate that the fault has been successfully repaired and an alarm corresponding to the successfully repaired fault has been cleared.

[0227] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices are based on the same concept as the method embodiment of the present application, and their specific functions and technical effects can be found in the method embodiment part, which will not be repeated here. In an optional example, the device 500 can be specifically the equipment vendor management device in the above-mentioned method 200 or the embodiment of the method 200. The device 500 can be used to execute the various processes and / or steps corresponding to the equipment vendor management device in the above-mentioned method 200 or the embodiment of the method 300. To avoid repetition, it will not be repeated here.

[0228] Figure 5 One or more of the modules in the illustrated embodiments may be implemented by software, hardware, firmware, or a combination thereof. The software or firmware includes, but is not limited to, computer program instructions or codes, and may be executed by a hardware processor. The hardware includes, but is not limited to, various integrated circuits, such as a CPU, a DSP, a FPGA, or an ASIC.

[0229] Figure 6 A schematic block diagram of a fault management device 600 provided in an embodiment of the present application is shown. The device 600 may include: a processor 601 and a communication interface 602, and the processor 601 and the communication interface 602 are coupled.

[0230] In an optional example, those skilled in the art can understand that the device 600 can be specifically the operator management device in the above method 200 or method 300, and the device 600 can be the physical hardware structure of the operator management device. The device 600 can be used to execute each process and / or step corresponding to the operator management device in the above method 200 or method 300 embodiment, and will not be described here to avoid repetition.

[0231] The processor 601 in the embodiment of the present application may include one or more processing units. Optionally, the processing unit includes but is not limited to a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, a discrete gate or transistor logic device or a discrete hardware component, etc. A general-purpose processor may be a microprocessor, a microcontroller or any conventional processor, etc.

[0232] For example, the processor 601 is used to receive fault management capability information from the equipment vendor management device through the communication interface 602, and the fault management capability information is used to indicate that the equipment vendor management device supports processing an alarm corresponding to at least one of a first alarm range, a first network range, or a first fault management function, and the first alarm range includes a first alarm type and / or a first alarm scenario type; based on the fault management capability information, determine an alarm subscription request, and the alarm subscription request is used to indicate that the operator management device requests to subscribe to the alarms that meet the second alarm range, the second network range, or the second fault management function. An alarm corresponding to at least one item in the corresponding alarm field, wherein the first alarm range includes the second alarm range, the second alarm range includes the second alarm type and / or the second alarm scenario type, the first network range includes the second network range, and the first fault management function includes the second fault management function; sending the alarm subscription request to the equipment vendor management device through the communication interface 602; receiving an alarm notification message from the first management device through the communication interface 602, the alarm notification message being used to notify the generation of a target alarm, the target alarm being the alarm subscribed to by the second management device.

[0233] In an optional example, a person skilled in the art may understand that the device 600 may be the operator management device described in the above-mentioned method 200 or 300 embodiments, and the device 600 may be used to execute each process and / or step corresponding to the operator management device in the method 200 or 300 embodiments, and will not be described again here to avoid repetition.

[0234] Optionally, the device 600 may further include a memory 603 .

[0235] The memory 603 may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the nonvolatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable programmable ROM (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DRRAM).

[0236] Specifically, the memory 603 is used to store program codes and instructions of the fault management device. Optionally, the memory 603 is also used to store data obtained during the execution of the above method 200 or 300 by the processor 601, such as fault management capability information.

[0237] Optionally, the memory 603 may be a separate device or integrated in the processor 601 .

[0238] It should be noted that Figure 6 Only a simplified design of the device 600 is shown. In practical applications, the device 600 may also include other necessary components, including but not limited to any number of communication interfaces, processors, selectors, memories, etc., and all devices 600 that can implement the present application are within the protection scope of the present application.

[0239] In one possible design, the device 600 may be a chip. Optionally, the chip may also include one or more memories for storing computer-executable instructions, and when the chip device is running, the processor may execute the computer-executable instructions stored in the memory to enable the chip to perform the steps performed by the operator management device described in the above method 200 or 300.

[0240] Optionally, the chip device may be a field programmable gate array, a dedicated integrated chip, a system chip, a central processing unit, a network processor, a digital signal processing circuit, a microcontroller, or a programmable controller or other integrated chips for realizing relevant functions.

[0241] Figure 7 A schematic block diagram of a fault management device 700 provided in an embodiment of the present application is shown. The device 700 may include: a processor 701 and a communication interface 702, and the processor 701 and the communication interface 702 are coupled.

[0242] In an optional example, those skilled in the art can understand that the device 700 can be specifically the equipment vendor management device in the above method 200 or method 300, and the device 700 can be the physical hardware structure of the equipment vendor management device. The device 700 can be used to execute the various processes and / or steps corresponding to the equipment vendor management device in the above method 200 or method 300 embodiments, and will not be described in detail here to avoid repetition.

[0243] The processor 701 in the embodiment of the present application may include one or more processing units. Optionally, the processing unit includes but is not limited to a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, a discrete gate or transistor logic device or a discrete hardware component, etc. A general-purpose processor may be a microprocessor, a microcontroller or any conventional processor, etc.

[0244] For example, the processor 701 is used to send fault management capability information to the operator management device through the communication interface 702, and the fault management capability information is used to indicate that the equipment vendor management device supports processing an alarm corresponding to at least one of a first alarm range, a first network range, or a first fault management function, and the first alarm range includes a first alarm type and / or a first alarm scenario type; receive an alarm subscription request from the operator management device through the communication interface 702, and the alarm subscription request is used to indicate that the operator management device requests to subscribe to a second alarm range, a second network range, or a second fault management function. An alarm corresponding to at least one item in the alarm field corresponding to the management function, wherein the first alarm range includes the second alarm range, the second alarm range includes the second alarm type and / or the second alarm scenario type, the first network range includes the second network range, and the first fault management function includes the second fault management function; performing fault detection based on the alarm subscription request, determining to generate a target alarm, the target alarm is the alarm subscribed to by the operator management device; sending an alarm notification message to the second management device through the communication interface 702, and the alarm notification message is used to notify the generation of the target alarm.

[0245] In an optional example, those skilled in the art may understand that the device 700 may be the equipment vendor management device described in the above-mentioned method 200 or 300 embodiments, and the device 700 may be used to execute the various processes and / or steps corresponding to the equipment vendor management device in the method 200 or 300 embodiments, which will not be described again here to avoid repetition.

[0246] Optionally, the device 700 may further include a memory 703 .

[0247] The memory 703 may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the nonvolatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DRRAM).

[0248] Specifically, the memory 703 is used to store program codes and instructions of the fault management device. Optionally, the memory 703 is also used to store data obtained during the execution of the above method 200 or 300 by the processor 701, such as fault management capability information.

[0249] Optionally, the memory 703 may be a separate device or integrated in the processor 701 .

[0250] It should be noted that Figure 7Only a simplified design of the device 700 is shown. In practical applications, the device 700 may also include other necessary components, including but not limited to any number of communication interfaces, processors, selectors, memories, etc., and all devices 700 that can implement the present application are within the protection scope of the present application.

[0251] In one possible design, the device 700 may be a chip. Optionally, the chip may also include one or more memories for storing computer-executable instructions. When the chip device is running, the processor may execute the computer-executable instructions stored in the memory to enable the chip to perform the steps performed by the equipment vendor management device described in the above method 200 or 300.

[0252] Optionally, the chip device may be a field programmable gate array, a dedicated integrated chip, a system chip, a central processing unit, a network processor, a digital signal processing circuit, a microcontroller, or a programmable controller or other integrated chips for realizing relevant functions.

[0253] The embodiment of the present application also provides a terminal, which may include: Figure 4 or Figure 5 The fault management device may include: Figure 6 or Figure 7 The fault management device.

[0254] An embodiment of the present application further provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions are executed on a computer, the fault management method described in the above method embodiment is implemented.

[0255] The embodiment of the present application also provides a computer program product, which, when executed on a processor, implements the fault management method described in the above method embodiment.

[0256] The fault management device, computer-readable storage medium, computer program product or chip provided in the embodiments of the present application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects described in the corresponding methods provided above, and will not be repeated here.

[0257] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0258] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0259] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0260] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0261] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0262] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0263] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

[0264] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A fault management method, characterized in that: include: receiving fault management capability information from a first management device, the fault management capability information being used to indicate that the first management device supports processing an alarm corresponding to at least one of a first alarm range, a first network range, or a first fault management function, the first alarm range including a first alarm type and / or a first alarm scenario type; Based on the fault management capability information, determine an alarm subscription request, where the alarm subscription request is used to indicate that the second management device requests to subscribe to an alarm corresponding to at least one of the alarm fields corresponding to a second alarm range, a second network range, or a second fault management function, wherein the first alarm range includes the second alarm range, the second alarm range includes a second alarm type and / or a second alarm scenario type, the first network range includes the second network range, and the first fault management function includes the second fault management function; Sending the alarm subscription request to the first management device; An alarm notification message is received from the first management device, where the alarm notification message is used to notify the generation of a target alarm, where the target alarm is an alarm subscribed by the second management device.

2. The method according to claim 1, characterized in that The fault management capability information includes at least one of alarm range information, network range information and fault management function information and a fault management capability information identifier. The alarm range information is used to indicate that the first management device supports processing alarms within the first alarm range, the network range information is used to indicate that the first management device supports processing alarms within the first network range, the fault management function information is used to indicate that the first management device supports processing alarms with the first fault management function, and the fault management capability information identifier is used to identify the fault management capability information.

3. The method according to claim 1 or 2, characterized in that: The first alarm type includes at least one of a communication alarm, a processing error alarm, an environmental alarm, a service quality alarm, a device alarm, an integrity alarm, an operation alarm, a physical resource alarm, a security alarm or a time domain alarm; or, The first alarm scenario type includes: at least one of a base station out-of-control failure, a fronthaul / optical port failure, a clock failure, a cell out-of-service failure, or a standing wave failure; or, The first network range includes: at least one of a network element list, a network element type, or a frequency point list; or, The first fault management function includes: at least one of an alarm correlation function, a root cause analysis function, a repair suggestion function or a fault repair function.

4. The method according to any one of claims 1 to 3, characterized in that The alarm subscription request includes at least one of an alarm range subscription requirement, a network range subscription requirement, and an alarm field subscription requirement corresponding to a fault management function. The alarm range subscription requirement is used to instruct the second management device to subscribe to alarms within the second alarm range. The network range subscription requirement is used to instruct the second management device to subscribe to alarms within the second network range. The alarm field subscription requirement corresponding to the fault management function is used to instruct the second management device to subscribe to the alarm field corresponding to the second fault management function.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: Based on the alarm field corresponding to the second fault management function and the target alarm, a fault repair request is sent to the first management device, wherein the fault repair request is used to request repair of the fault corresponding to the first alarm, and the first alarm includes part or all of the alarms in the target alarm.

6. The method according to claim 5, characterized in that The method further comprises: A fault repair result is received from the first management device, where the fault repair result is used to indicate a fault that has been successfully repaired.

7. The method according to claim 5, characterized in that The fault repair request is also used to request to clear the first alarm, and the method further includes: A fault repair result is received from the first management device, where the fault repair result is used to indicate that the fault has been successfully repaired, and an alarm corresponding to the successfully repaired fault has been cleared.

8. A fault management method, characterized in that: include: Sending fault management capability information to the second management device, where the fault management capability information is used to indicate that the first management device supports processing an alarm corresponding to at least one of a first alarm range, a first network range, or a first fault management function, where the first alarm range includes a first alarm type and / or a first alarm scenario type; receiving an alarm subscription request from the second management device, the alarm subscription request being used to indicate that the second management device requests to subscribe to an alarm corresponding to at least one of the alarm fields corresponding to a second alarm range, a second network range, or a second fault management function, wherein the first alarm range includes the second alarm range, the second alarm range includes a second alarm type and / or a second alarm scenario type, the first network range includes the second network range, and the first fault management function includes the second fault management function; Performing fault detection based on the alarm subscription request, determining to generate a target alarm, the target alarm being an alarm subscribed to by the second management device; An alarm notification message is sent to the second management device, where the alarm notification message is used to notify that the target alarm is generated.

9. The method according to claim 8, characterized in that The fault management capability information includes at least one of alarm range information, network range information and fault management function information and a fault management capability information identifier. The alarm range information is used to indicate that the first management device supports processing alarms within the first alarm range, the network range information is used to indicate that the first management device supports processing alarms within the first network range, the fault management function information is used to indicate that the first management device supports processing alarms with the first fault management function, and the fault management capability information identifier is used to identify the fault management capability information.

10. The method according to claim 8 or 9, characterized in that: The first alarm type includes at least one of a communication alarm, a processing error alarm, an environmental alarm, a service quality alarm, a device alarm, an integrity alarm, an operation alarm, a physical resource alarm, a security alarm or a time domain alarm; or, The first alarm scenario type includes: at least one of a base station out-of-control failure, a fronthaul / optical port failure, a clock failure, a cell out-of-service failure, or a standing wave failure; or, The first network range includes: at least one of a network element list, a network element type, or a frequency point list; or, The first fault management function includes: at least one of an alarm correlation function, a root cause analysis function, a repair suggestion function or a fault repair function.

11. The method according to any one of claims 8 to 10, characterized in that: The alarm subscription request includes at least one of an alarm range subscription requirement, a network range subscription requirement, and an alarm field subscription requirement corresponding to a fault management function. The alarm range subscription requirement is used to instruct the second management device to subscribe to alarms within the second alarm range. The network range subscription requirement is used to instruct the second management device to subscribe to alarms within the second network range. The alarm field subscription requirement corresponding to the fault management function is used to instruct the second management device to subscribe to the alarm field corresponding to the second fault management function.

12. The method according to any one of claims 8 to 11, characterized in that The method further comprises: receiving a fault repair request from the second management device, the fault repair request being used to request repair of a fault corresponding to a first alarm, the first alarm including part or all of the target alarms; Based on the fault repair request, the fault corresponding to the first alarm is repaired.

13. The method according to claim 12, characterized in that The method further comprises: A fault repair result is sent to the second management device, where the fault repair result is used to indicate a fault that has been successfully repaired.

14. The method according to claim 12, characterized in that The fault repair request is also used to request to clear the first alarm. After repairing the fault corresponding to the first alarm based on the fault repair request, the method further includes: Based on the fault repair request, the first alarm is cleared.

15. The method according to claim 14, characterized in that The method further comprises: A fault repair result is sent to the second management device, where the fault repair result is used to indicate that the fault has been successfully repaired and an alarm corresponding to the successfully repaired fault has been cleared.

16. A fault management device, characterized in that: include: a processor and a communication interface, the processor and the communication interface being coupled, The processor is used to: receiving fault management capability information from a first management device through the communication interface, the fault management capability information being used to indicate that the first management device supports processing an alarm corresponding to at least one of a first alarm range, a first network range, or a first fault management function, the first alarm range including a first alarm type and / or a first alarm scenario type; Based on the fault management capability information, determine an alarm subscription request, where the alarm subscription request is used to indicate that the second management device requests to subscribe to an alarm corresponding to at least one of the alarm fields corresponding to a second alarm range, a second network range, or a second fault management function, wherein the first alarm range includes the second alarm range, the second alarm range includes a second alarm type and / or a second alarm scenario type, the first network range includes the second network range, and the first fault management function includes the second fault management function; Sending the alarm subscription request to the first management device through the communication interface; An alarm notification message is received from the first management device through the communication interface, where the alarm notification message is used to notify the generation of a target alarm, where the target alarm is an alarm subscribed by the second management device.

17. The device according to claim 16, characterized in that The fault management capability information includes at least one of alarm range information, network range information and fault management function information and a fault management capability information identifier. The alarm range information is used to indicate that the first management device supports processing alarms within the first alarm range, the network range information is used to indicate that the first management device supports processing alarms within the first network range, the fault management function information is used to indicate that the first management device supports processing alarms with the first fault management function, and the fault management capability information identifier is used to identify the fault management capability information.

18. The device according to claim 16 or 17, characterized in that The first alarm type includes at least one of a communication alarm, a processing error alarm, an environmental alarm, a service quality alarm, a device alarm, an integrity alarm, an operation alarm, a physical resource alarm, a security alarm or a time domain alarm; or, The first alarm scenario type includes: at least one of a base station out-of-control failure, a fronthaul / optical port failure, a clock failure, a cell out-of-service failure, or a standing wave failure; or, The first network range includes: at least one of a network element list, a network element type, or a frequency point list; or, The first fault management function includes: at least one of an alarm correlation function, a root cause analysis function, a repair suggestion function or a fault repair function.

19. The device according to any one of claims 16 to 18, characterized in that The alarm subscription request includes at least one of an alarm range subscription requirement, a network range subscription requirement, and an alarm field subscription requirement corresponding to a fault management function. The alarm range subscription requirement is used to instruct the second management device to subscribe to alarms within the second alarm range. The network range subscription requirement is used to instruct the second management device to subscribe to alarms within the second network range. The alarm field subscription requirement corresponding to the fault management function is used to instruct the second management device to subscribe to the alarm field corresponding to the second fault management function.

20. The device according to any one of claims 16 to 19, characterized in that The processor is further configured to: Based on the alarm field corresponding to the second fault management function and the target alarm, a fault repair request is sent to the first management device through the communication interface, and the fault repair request is used to request to repair the fault corresponding to the first alarm, and the first alarm includes part or all of the alarms in the target alarm.

21. The device according to claim 20, characterized in that The processor is further configured to: A fault repair result is received from the first management device through the communication interface, where the fault repair result is used to indicate a fault that has been successfully repaired.

22. The device according to claim 20, characterized in that The fault repair request is further used to request clearing of the first alarm, and the processor is further used to: A fault repair result is received from the first management device through the communication interface, where the fault repair result is used to indicate that the fault has been successfully repaired, and an alarm corresponding to the successfully repaired fault has been cleared.

23. A fault management device, characterized in that: include: a processor and a communication interface, the processor and the communication interface being coupled, The processor is used to: Sending fault management capability information to the second management device through the communication interface, the fault management capability information being used to indicate that the first management device supports processing an alarm corresponding to at least one of a first alarm range, a first network range, or a first fault management function, wherein the first alarm range includes a first alarm type and / or a first alarm scenario type; Receiving an alarm subscription request from the second management device through the communication interface, the alarm subscription request is used to indicate that the second management device requests to subscribe to an alarm corresponding to at least one of the alarm fields corresponding to a second alarm range, a second network range, or a second fault management function, wherein the first alarm range includes the second alarm range, the second alarm range includes a second alarm type and / or a second alarm scenario type, the first network range includes the second network range, and the first fault management function includes the second fault management function; Performing fault detection based on the alarm subscription request, determining to generate a target alarm, the target alarm being an alarm subscribed to by the second management device; An alarm notification message is sent to the second management device through the communication interface, where the alarm notification message is used to notify that the target alarm is generated.

24. The device according to claim 23, characterized in that The fault management capability information includes at least one of alarm range information, network range information and fault management function information and a fault management capability information identifier. The alarm range information is used to indicate that the first management device supports processing alarms within the first alarm range, the network range information is used to indicate that the first management device supports processing alarms within the first network range, the fault management function information is used to indicate that the first management device supports processing alarms with the first fault management function, and the fault management capability information identifier is used to identify the fault management capability information.

25. The device according to claim 23 or 24, characterized in that The first alarm type includes at least one of a communication alarm, a processing error alarm, an environmental alarm, a service quality alarm, a device alarm, an integrity alarm, an operation alarm, a physical resource alarm, a security alarm or a time domain alarm; or, The first alarm scenario type includes: at least one of a base station out-of-control failure, a fronthaul / optical port failure, a clock failure, a cell out-of-service failure, or a standing wave failure; or, The first network range includes: at least one of a network element list, a network element type, or a frequency point list; or, The first fault management function includes: at least one of an alarm correlation function, a root cause analysis function, a repair suggestion function or a fault repair function.

26. The device according to any one of claims 23 to 25, characterized in that The alarm subscription request includes at least one of an alarm range subscription requirement, a network range subscription requirement, and an alarm field subscription requirement corresponding to a fault management function. The alarm range subscription requirement is used to instruct the second management device to subscribe to alarms within the second alarm range. The network range subscription requirement is used to instruct the second management device to subscribe to alarms within the second network range. The alarm field subscription requirement corresponding to the fault management function is used to instruct the second management device to subscribe to the alarm field corresponding to the second fault management function.

27. The device according to any one of claims 23 to 26, characterized in that The processor is further configured to: receiving a fault repair request from the second management device through the communication interface, the fault repair request being used to request repair of a fault corresponding to the first alarm, the first alarm including part or all of the target alarms; Based on the fault repair request, the fault corresponding to the first alarm is repaired.

28. The device according to claim 27, characterized in that The processor is further configured to: A fault repair result is sent to the second management device, where the fault repair result is used to indicate a fault that has been successfully repaired.

29. The device according to claim 27, characterized in that The fault repair request is further used to request clearing of the first alarm, and the processor is further used to: After the fault corresponding to the first alarm is repaired based on the fault repair request, the first alarm is cleared based on the fault repair request.

30. The device according to claim 29, characterized in that The processor is further configured to: A fault repair result is sent to the second management device through the communication interface, where the fault repair result is used to indicate that the fault has been successfully repaired and an alarm corresponding to the successfully repaired fault has been cleared.

31. A computer-readable storage medium for storing a computer program, characterized in that: The computer program comprises instructions for implementing the method of any one of claims 1 to 15 above.

32. A computer program product, comprising instructions, characterized in that: When the instructions are executed on a computer or a processor, the computer or the processor is enabled to implement the method according to any one of claims 1 to 15.

Images