CN112994917B

CN112994917B - Network management method and network management device

Info

Publication number: CN112994917B
Application number: CN201911302865.2A
Authority: CN
Inventors: 纪孟迪
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-12-17
Filing date: 2019-12-17
Publication date: 2022-12-13
Anticipated expiration: 2039-12-17
Also published as: CN112994917A

Abstract

The embodiment of the application discloses a network management method and a network management device, which are used for avoiding the problem of conflict or repeated processing of processing modes of a first management system and a second management system aiming at the same network fault so as to improve the network fault processing performance of a two-layer closed-loop architecture or a multi-layer closed-loop architecture. The method in the embodiment of the application comprises the following steps: a first management system sends a first request message to a second management system or first management equipment, wherein the first request message is used for requesting the second management system to execute first decision result information of management on a first abnormal event; the first management system receives first decision result information of the first abnormal event sent by the second management system or first management equipment; and the first management system executes management operation on a second abnormal event according to the parameter in the first decision result information, wherein the second abnormal event is associated with the first abnormal event.

Description

Network management method and network management device

Technical Field

The present application relates to communications technologies, and in particular, to a network management method and a network management apparatus.

Background

At present, zero-contact network and service management (ZSM) defines an end-to-end network and service management architecture, which is divided into two layers, an upper layer is an end-to-end management domain across domains, and a lower layer is a resource and service management domain of a single domain.

In order to realize automatic network and service management, a multilayer closed-loop architecture is defined, an end-to-end management domain and each management domain have a closed loop, and each management domain automatically processes the problems of network faults or network performance reduction and the like of the domain through the closed loop. The closed loop of the end-to-end management domain is a large closed loop, the problem of performance degradation of an end-to-end service layer is solved, and the closed loops of the management domains are coordinated; and the management domain is a small closed loop and processes the resources and services managed in the management domain, and the closed loop in the management domain is independent of the closed loops in other management domains.

When the end-to-end management domain and the sub-management domain receive the network fault at the same time, the end-to-end management domain and the sub-management domain can process the network fault at the same time, which can cause the problems of processing conflict or repeated operation, and the like, and reduce the network fault processing performance of the multilayer closed-loop architecture.

Disclosure of Invention

The embodiment of the application provides a network management method and a network management device, which are used for improving the network fault processing performance of a multilayer closed-loop architecture.

A first aspect of an embodiment of the present application provides a network management method, where the method includes:

the method comprises the steps that a first management system sends a first request message to a second management system, wherein the first request message is used for requesting the second management system to execute first decision result information of management on a first abnormal event; then, the first management system receives first decision result information of a first abnormal event sent by the second management system, wherein the first decision result information carries the first abnormal event, a management object managed by the first management service, and an execution action and an execution time of the second management system on the first abnormal event; and the first management system executes management operation on a second abnormal event according to the first decision result information, wherein the second abnormal event is associated with the first abnormal event. Therefore, the first management system receives the first decision result information sent by the second management system, and executes management operation on the second abnormal event associated with the first abnormal event according to the first decision result information, so that the problem that processing modes of the first management system and the second management system conflict or are processed repeatedly aiming at the same network fault is avoided, and the network fault processing performance of the two-layer closed-loop architecture or the multi-layer closed-loop architecture is improved.

In a possible implementation manner, the first request message carries at least one parameter of the first exception event, a decision type supported by a first management service, a management object managed by the first management service, an execution action of the second management system on the first exception event, and an action execution time period. In this possible implementation manner, some relevant parameters carried in the first request message are provided, so that the second management system or the first management device searches for an address of the first management service of the second management system according to these parameters to obtain the first decision result information, and thus the first management system can perform management operation on the second abnormal event associated with the first abnormal event according to the first decision result information, thereby avoiding the problem of processing mode conflict or repeated processing of the first management system and the second management system for the same network fault, and improving the network fault processing performance of the two-layer closed-loop architecture or the multi-layer closed-loop architecture.

In another possible implementation manner, the first decision result information carries the first exception event, a management object managed by a first management service, and an execution action and an execution time of the second management system on the first exception event, where the first management service is a management service in the second management system corresponding to the first exception event; the first management system executing management operation on the second abnormal event according to the parameter in the first decision result information comprises: the first management system does not execute the action on the second abnormal event according to the execution action, the execution time and the management object. In this possible implementation manner, a management manner for the second abnormal event by the first management system according to the first decision result information is provided, and mainly for the same network fault, under the condition that a conflict occurs or a repeated operation occurs in the processing manners of the two management systems, the first management system determines that no action is performed on the second abnormal event through analysis.

In another possible implementation manner, when the first management system sends the first request message to the first management device, the first request message also carries an identifier of the second management system. In this possible implementation manner, the identifier of the second management system is used by the first management device to determine the second management system, and request the first decision result information from the second management system through the first management device, so that the first management system receives the first decision result information sent by the first management device, and thus performs management operation on the second abnormal event according to the first decision result information, thereby avoiding a problem of processing mode conflict or repeated processing of the first management system and the second management system for the same network fault, and improving network fault processing performance of the two-layer closed-loop architecture or the multi-layer closed-loop architecture.

In another possible implementation manner, the first request message is a first query request message, and the first query request message is used to request to query the first decision result information. In the possible implementation manner, the first management system requests to query the first decision result information in a query manner, a possible implementation manner that the first management system requests the first decision result information is provided, and in practical application, the realizability of the scheme is improved.

In another possible implementation manner, the first request message is a first subscription request message, and the first subscription request message is used for subscribing to the first decision result information; the method further comprises the following steps: the first management system receives a first subscription response message sent by the second management system or the first management device; and the first management system determines that the first management system successfully subscribes the first decision result information according to the first subscription response message. In this possible implementation manner, the first management system requests to subscribe to the first decision result information in a subscription manner, and then in this manner, the first management system further receives the first subscription response message to indicate that the first management system successfully subscribes to the first decision result information, so that another possible implementation manner is provided in which the first management system requests the first decision result information, and in practical application, the diversity and the practicability of the scheme are improved.

In another possible implementation manner, the method further includes: the first management system receives abnormal information of a third abnormal event and second decision result information which are sent by the second management system or the first management device, wherein the second decision result information is decision result information of the third management system for managing the third abnormal event, and the third abnormal event is associated with the first abnormal event; the first management system executing management operation on the second abnormal event according to the first decision result information comprises the following steps: the first management system executes management operation on the second abnormal event according to the first decision result information, the abnormal information of the third abnormal event and the second decision result information. In this possible implementation manner, under the multilayer closed-loop architecture, the second management system sends the first decision result information, the second decision result information, and the abnormal information of the third abnormal event to the first management system together, so that the first management system can synthesize these information to perform management operations on the second abnormal event, and thus, the decision results of the abnormal events and the abnormal information of the abnormal events by different management systems can be combined to perform corresponding management operations accurately, thereby improving the processing performance of network faults under the multilayer closed-loop architecture.

In another possible implementation manner, the first management system is a master management system, the second management system is a first sub-management system, the third management system is a second sub-management system, the first sub-management system is a sub-management system of the master management system, and the second sub-management system is a sub-management system of the first sub-management system. In the possible implementation mode, an application scenario of management coordination among a plurality of management systems under a multilayer closed-loop architecture is provided, and the practicability of the scheme is improved.

In another possible implementation manner, the first management system is a master management system, the second management system is a first sub-management system, and the first sub-management system is a sub-management system of the master management system; or, the first management system is a first sub-management system, the second management system is a second sub-management system, and the second sub-management system is a sub-management system of the first sub-management system. In the possible implementation mode, two possible application scenarios of management coordination among a plurality of management systems under a two-layer closed-loop architecture or a multi-layer closed-loop architecture are provided, and the diversity and the practicability of the scheme in practical application are improved.

A second aspect of an embodiment of the present application provides a network management method, where the method includes:

the second management system receives a first request message sent by the first management system; the second management system sends first decision result information of a first abnormal event to the first management system according to the first request message, wherein the first decision result information is decision result information of the second management system for managing the first abnormal event. In this possible implementation manner, the second management system provides the first decision result information to the first management system, so that the first management system performs a management operation on the second abnormal event in combination with the first decision result information, thereby avoiding a problem that processing manners of the first management system and the second management system conflict or are processed repeatedly for the same network fault, and improving network fault processing performance of the two-layer closed-loop architecture or the multi-layer closed-loop architecture.

In a possible implementation manner, the first request message carries at least one parameter of a first exception event, a decision type supported by a first management service, a management object managed by the first management service, an execution action of the second management system on the first exception event, and an action execution time period; the second management system sending first decision result information of a first abnormal event to the first management system according to the first request message comprises: the second management system determines the first decision result information according to the parameters in the first request message; the second management system sends the first decision result information to the first management system. In this possible implementation manner, the second management system selects the first decision result information from the decision result information made in the second management system according to the parameter carried in the first request message, so that the first management system can obtain the first decision result information, and perform management operation on the second abnormal event according to the first decision result information, thereby avoiding the problem of processing mode conflict or repeated processing of the first management system and the second management system for the same network fault, so as to improve the network fault processing performance of the two-layer closed-loop architecture or the multi-layer closed-loop architecture.

In another possible implementation manner, the first decision result information carries the first exception event, a management object managed by a first management service, and an execution action and an execution time of the second management system on the first exception event, where the first management service is a management service in the second management system corresponding to the first exception event. In this possible implementation manner, the first decision result information carries some relevant information of the second management system for performing the management operation on the first abnormal event, such as an execution action, an execution time period, an execution object, and the like, so that the first management system can perform the management operation on the second abnormal event by combining these information, thereby avoiding the problem of conflict or repeated processing of processing manners of different management systems for the same network fault, so as to improve the network fault processing performance of the two-layer closed-loop architecture or the multi-layer closed-loop architecture.

In another possible implementation manner, the method further includes: the second management system acquires second decision result information, wherein the second decision result information is decision result information of a third management system for managing a third abnormal event, and the third abnormal event is associated with the first abnormal event; the second management system executes management operation on the first abnormal event according to the second decision result information to obtain first decision result information of the first abnormal event. In this possible implementation manner, under the multilayer closed-loop architecture, the second management system performs a management operation on the first abnormal event in combination with the second decision result information for performing management on the third abnormal event by the third management system, and then sends the first decision result information to the first management system, that is, under the multilayer closed-loop architecture, the management systems between different levels can perform a management operation on the abnormal event generated in the management system by applying the technical scheme of the embodiment of the present application, so that the multilayer management systems can achieve coordinated management therebetween, and the network fault handling performance of the multilayer closed-loop architecture is further improved.

In another possible implementation manner, the method further includes: and the second management system sends the abnormal information of the third abnormal event and the second decision result information to the first management system. Under the multilayer closed-loop architecture, the second management system sends the abnormal information of the third abnormal event and the second decision result information to the first management system, so that the first management system can synthesize the information to execute management operation on the second abnormal event, and corresponding management operation can be accurately performed by combining the decision results of different management systems on the abnormal event and the abnormal information of the abnormal event, and the processing performance of network faults under the multilayer closed-loop architecture is improved.

In another possible implementation manner, the first management system is a master management system, the second management system is a first sub-management system, the third management system is a second sub-management system, the first sub-management system is a sub-management system of the master management system, and the second sub-management system is a sub-management system of the first sub-management system. In the possible implementation manner, an application scenario of management coordination among a plurality of management systems under a multilayer closed-loop architecture is provided, and the practicability of the scheme is improved.

A third aspect of an embodiment of the present application provides a network management method, where the method includes:

the second management system receives a second request message sent by the first management equipment; the second management system sends first decision result information of a first abnormal event to the first management device according to the second request message, wherein the first decision result information is decision result information of the second management system for managing the first abnormal event. In this possible implementation manner, the second management system provides the first decision result information to the first management device, so that the first management device sends the first decision result information to the first management system, and thus the first management system can perform management operation on the second abnormal event in combination with the first decision result information, thereby avoiding the problem of processing mode conflict or repeated processing of the first management system and the second management system for the same network fault, and improving the network fault processing performance of the two-layer closed-loop architecture or the multi-layer closed-loop architecture.

In a possible implementation, the method further includes: the second management system acquires second decision result information, wherein the second decision result information is decision result information of a third management system for managing a third abnormal event, and the third abnormal event is associated with the first abnormal event; the second management system executes management operation on the first abnormal event according to the second decision result information to obtain first decision result information of the first abnormal event. In this possible implementation manner, under the multilayer closed-loop architecture, the second management system performs a management operation on the first abnormal event in combination with the second decision result information for managing the third abnormal event by the third management system, and then sends the first decision result information to the first management device. In other words, under the multilayer closed-loop architecture, the management systems between different layers can apply the technical scheme of the embodiment of the application to execute management operation on the abnormal event generated in the management system, so that coordination management can be realized among the multilayer management systems, and the network fault processing performance of the multilayer closed-loop architecture is further improved.

In another possible implementation manner, the method further includes: and the second management system sends the abnormal information of the third abnormal event and the second decision result information to the first management device. Under the multilayer closed-loop architecture, the second management system sends the abnormal information of the third abnormal event and the second decision result information to the first management device, so that the first management system can synthesize the information to execute management operation on the second abnormal event, and corresponding management operation can be accurately performed by combining the decision results of different management systems on the abnormal event and the abnormal information of the abnormal event, and the processing performance of network faults under the multilayer closed-loop architecture is improved.

A fourth aspect of the present embodiment provides a network management method, including:

the method comprises the steps that a second management system sends a first event type creating request to a first management device, wherein the first event type creating request is used for requesting the first management device to create a first event type, the first event type aims at a first management service of the second management system, and the first management service is a management service corresponding to a first abnormal event; the second management system sends first decision result information of the first abnormal event to the first management device, wherein the first decision result information is decision result information of the second management system for managing the first abnormal event. In this possible implementation manner, the second management system actively initiates a request for creating the first event class to the first management device, and the second management system provides the first decision result information to the first management device, so that the first management device sends the first decision result information to the first management system, and thus the first management system can perform management operation on the second abnormal event in combination with the first decision result information, thereby avoiding the problem of processing mode conflict or repeated processing of the first management system and the second management system for the same network fault, and improving the network fault processing performance of the two-layer closed-loop architecture or the multi-layer closed-loop architecture.

In a possible implementation, the method further includes: the second management system acquires second decision result information, wherein the second decision result is decision result information of a third management system for executing management on a third abnormal event, and the third abnormal event is associated with the first abnormal event; the second management system executes management operation on the first abnormal event according to the second decision result information to obtain first decision result information of the first abnormal event. In this possible implementation manner, under the multilayer closed-loop architecture, the second management system performs a management operation on the first abnormal event in combination with the second decision result information for managing the third abnormal event by the third management system, and then sends the first decision result information to the first management device. In other words, under the multilayer closed-loop architecture, the management systems between different layers can apply the technical scheme of the embodiment of the application to execute management operation on the abnormal event generated in the management system, so that coordination management can be realized among the multilayer management systems, and the network fault processing performance of the multilayer closed-loop architecture is further improved.

A fifth aspect of the embodiments of the present application provides a network management method, including:

the first management equipment receives a first request message sent by the first management system; the first management device sends first decision result information of a first abnormal event to the first management system according to the first request message, wherein the first decision result information is decision result information of the second management system for managing the first abnormal event. Therefore, the first management device sends the first decision result information of the first abnormal event to the first management system, so that the first management system executes management operation on the second abnormal event related to the first abnormal event according to the first decision result information, thereby avoiding the problem that the processing modes of the first management system and the second management system conflict or are processed repeatedly aiming at the same network fault, and improving the network fault processing performance of a two-layer closed-loop architecture or a multi-layer closed-loop architecture.

In a possible implementation manner, the first decision result information carries the first abnormal event, a management object managed by a first management service, and an execution action and an execution time of the second management system on the first abnormal event, where the first management service is a management service in the second management system corresponding to the first abnormal event. In this possible implementation manner, the first decision result information carries some related information of the second management system performing the management operation on the first abnormal event, such as an execution action, an execution time period, an execution object, and the like, so that the first management system can perform the management operation on the second abnormal event by combining these information, thereby avoiding the problem of processing mode conflicts or repeated processing of different management systems for the same network fault, so as to improve the network fault processing performance of the two-layer closed-loop architecture or the multi-layer closed-loop architecture.

In another possible implementation manner, the first request message carries an identifier of the second management system; the first request message also carries at least one information of the first abnormal event, the decision type supported by the first management service, the management object managed by the first management service, the execution action of the second management system on the first abnormal event and the action execution time period. In this possible implementation manner, some relevant parameters carried in the first request message are provided, so that the first management device determines the first management service of the second management system according to these parameters to obtain the first decision result information, so that the first management system can obtain the first decision result information, and perform management operation on the second abnormal event according to the first decision result information, thereby avoiding a problem of processing mode conflict or repeated processing of the first management system and the second management system for the same network fault, and improving the network fault processing performance of the two-layer closed-loop architecture or the multi-layer closed-loop architecture.

In another possible implementation manner, the method further includes: the first management device determines the address of the first management service in the second management system according to the first request message; the first management device sends a second request message to the second management system through the address of the first management service, wherein the second request message is used for requesting the second management system to execute first decision result information of management on the first abnormal event; and the first management equipment receives first decision result information of the first abnormal event sent by the second management system. In this possible implementation manner, a specific manner is provided in which the first management device acquires the first decision result information after receiving the first request message, so that the implementability of the scheme is improved.

In another possible implementation manner, the method further includes: the first management device receives a first event type creation request sent by the second management system; the first management device creates a first event category according to the first event category creation request, the first event category being for a first management service of the second management system; and the first management equipment receives first decision result information of the first abnormal event sent by the second management system. In this possible implementation manner, another specific manner is provided for acquiring the first decision result information after the first management device receives the first request message, so that the diversity and the realizability of the scheme are improved.

In another possible implementation manner, the method further includes: the first management device receives exception information of a third exception event and second decision result information sent by the second management system, wherein the second decision result information is decision result information of the third management system for managing the third exception event, and the third exception event is associated with the first exception event; and the first management equipment sends the abnormal information of the third abnormal event and the second decision result information to the first management system. Under the multilayer closed-loop architecture, the first management device sends the abnormal information of the third abnormal event and the second decision result information to the first management system, so that the first management system can synthesize the information to execute management operation on the second abnormal event, and corresponding management operation can be accurately performed by combining the decision results of different management systems on the abnormal events and the abnormal information of the abnormal events, thereby improving the processing performance of network faults under the multilayer closed-loop architecture.

A sixth aspect of the embodiments of the present application provides a network management apparatus, including:

the system comprises a receiving and sending module, a judging module and a sending and receiving module, wherein the receiving and sending module is used for sending a first request message to a second management system, and the first request message is used for requesting the second management system to execute first decision result information of management on a first abnormal event; receiving first decision result information of a first abnormal event sent by a second management system, wherein the first decision result information carries the first abnormal event, a management object managed by a first management service, and an execution action and an execution time of the first abnormal event by the second management system;

and the processing module is used for executing management operation on a second abnormal event according to the first decision result information, wherein the second abnormal event is associated with the first abnormal event.

In a possible implementation manner, the first request message carries at least one parameter of the first exception event, a decision type supported by a first management service, a management object managed by the first management service, an execution action of the second management system on the first exception event, and an action execution time period.

In another possible implementation manner, the first decision result information carries the first exception event, a management object managed by a first management service, and an execution action and an execution time of the second management system on the first exception event, where the first management service is a management service in the second management system corresponding to the first exception event; the processing module is specifically configured to:

and performing no action on the second abnormal event according to the execution action, the execution time and the management object.

In another possible implementation manner, when the transceiver module sends the first request message to the first management device, the first request message also carries an identifier of the second management system.

In another possible implementation manner, the first request message is a first query request message, and the first query request message is used to request to query the first decision result information.

In another possible implementation manner, the first request message is a first subscription request message, and the first subscription request message is used for subscribing to the first decision result information; the transceiver module is further configured to:

receiving a first subscription response message sent by the second management system or the first management device;

the processing module is further configured to:

and determining that the first management system successfully subscribes the first decision result information according to the first subscription response message.

In another possible implementation manner, the transceiver module is further configured to:

receiving abnormal information and second decision result information of a third abnormal event sent by the second management system or the first management device, wherein the second decision result information is decision result information of the third management system for managing the third abnormal event, and the third abnormal event is associated with the first abnormal event;

the processing module is specifically configured to:

and executing management operation on the second abnormal event according to the first decision result information, the abnormal information of the third abnormal event and the second decision result information.

In another possible implementation manner, the network management apparatus is a master management system, the second management system is a first sub-management system, the third management system is a second sub-management system, the first sub-management system is a sub-management system of the master management system, and the second sub-management system is a sub-management system of the first sub-management system.

In another possible implementation manner, the network management apparatus is a master management system, the second management system is a first sub-management system, and the first sub-management system is a sub-management system of the master management system; or, the network management device is a first sub-management system, the second management system is a second sub-management system, and the second sub-management system is a sub-management system of the first sub-management system.

A seventh aspect of the embodiments of the present application provides a network management apparatus, including:

the system comprises a receiving and sending module, a processing module and a processing module, wherein the receiving and sending module is used for receiving a first request message sent by a first management system; and sending first decision result information of a first abnormal event to the first management system according to the first request message, wherein the first decision result information is decision result information of the network management device for managing the first abnormal event.

In a possible implementation manner, the first request message carries at least one parameter of a first exception event, a decision type supported by a first management service, a management object managed by the first management service, an execution action of the network management device on the first exception event, and an action execution time period; the transceiver module is specifically configured to:

determining the first decision result information according to the parameters in the first request message; and sending the first decision result information to the first management system.

In another possible implementation manner, the first decision result information carries the first abnormal event, a management object managed by a first management service, and an execution action and an execution time of the network management device on the first abnormal event, where the first management service is a management service in the network management device corresponding to the first abnormal event.

acquiring second decision result information, wherein the second decision result information is decision result information for a third management system to manage a third abnormal event, and the third abnormal event is associated with the first abnormal event;

the network management device also comprises a processing module;

the processing module is configured to perform a management operation on the first abnormal event according to the second decision result information to obtain first decision result information of the first abnormal event.

and sending the abnormal information of the third abnormal event and the second decision result information to the first management system.

In another possible implementation manner, the first management system is a master management system, the network management device is a first sub-management system, the third management system is a second sub-management system, the first sub-management system is a sub-management system of the master management system, and the second sub-management system is a sub-management system of the first sub-management system.

In another possible implementation manner, the first management system is a master management system, the network management device is a first sub-management system, and the first sub-management system is a sub-management system of the master management system; or, the first management system is a first sub-management system, the network management device is a second sub-management system, and the second sub-management system is a sub-management system of the first sub-management system.

An eighth aspect of the embodiments of the present application provides a network management apparatus, including:

the receiving and sending module is used for receiving a second request message sent by the first management equipment; and sending first decision result information of a first abnormal event to the first management device according to the second request message, wherein the first decision result information is decision result information of the network management device for managing the first abnormal event.

In a possible implementation manner, the transceiver module is further configured to:

the network management device also comprises a processing module;

the processing module is specifically configured to:

and executing management operation on the first abnormal event according to the second decision result information to obtain first decision result information of the first abnormal event.

In another possible implementation manner, the processing module is further configured to:

and sending the abnormal information of the third abnormal event and the second decision result information to the first management device.

A ninth aspect of the present embodiment provides a network management apparatus, including:

the receiving and sending module is used for sending a first event type creating request to the first management device, wherein the first event type creating request is used for requesting the first management device to create a first event type, the first event type is specific to a first management service of the second management system, and the first management service is a management service corresponding to a first abnormal event; and sending first decision result information of the first abnormal event to the first management device, wherein the first decision result information is decision result information of the network management device for managing the first abnormal event.

acquiring second decision result information, wherein the second decision result information is decision result information of a third management system for managing a third abnormal event, and the third abnormal event is associated with the first abnormal event;

the network management device also comprises a processing module;

the processing module is further configured to:

and sending the exception information of the third exception event and the second decision result information to the first management device.

A tenth aspect of the embodiments of the present application provides a network management apparatus, including:

the receiving and sending module is used for receiving a first request message sent by the first management system; and sending first decision result information of a first abnormal event to the first management system according to the first request message, wherein the first decision result information is decision result information of the second management system for managing the first abnormal event.

In a possible implementation manner, the first decision result information carries the first abnormal event, a management object managed by a first management service, and an execution action and an execution time of the second management system on the first abnormal event, where the first management service is a management service in the second management system corresponding to the first abnormal event.

In another possible implementation manner, the first request message carries an identifier of the second management system; the first request message also carries at least one piece of information of the first abnormal event, the decision type supported by the first management service, the management object managed by the first management service, the execution action of the second management system on the first abnormal event and the action execution time period.

In another possible implementation manner, the network management apparatus further includes a processing module;

the processing module is used for determining the address of the first management service in the second management system according to the first request message;

the transceiver module is further configured to:

sending a second request message to the second management system through the address of the first management service, wherein the second request message is used for requesting the second management system to execute first decision result information of management on the first abnormal event;

and receiving first decision result information of the first abnormal event sent by the second management system.

receiving a first event type creation request sent by the second management system;

the processing module is further configured to:

creating a first event category according to the first event category creation request, the first event category being for a first management service of the second management system;

the transceiver module is further configured to:

receiving exception information of a third exception event and second decision result information sent by the second management system, wherein the second decision result information is decision result information of the third exception event executed and managed by the third management system, and the third exception event is associated with the first exception event;

An eleventh aspect in an embodiment of the present application provides a network management apparatus, including: a processor, a memory, an input-output device, and a bus; the memory having stored therein computer instructions; when the processor executes the computer instructions in the memory, the memory stores the computer instructions; the processor, when executing the computer instructions in the memory, is adapted to implement any of the implementations as in the first aspect.

In a possible implementation manner of the eleventh aspect, the processor, the memory, and the input/output device are respectively connected to the bus.

A twelfth aspect of the embodiments of the present application provides a network management apparatus, including: a processor, a memory, an input-output device, and a bus; the memory having stored therein computer instructions; when the processor executes the computer instructions in the memory, the memory stores the computer instructions; the processor, when executing the computer instructions in the memory, is configured to implement any one of the implementations as in any one of the second, third or fourth aspects.

In a possible implementation manner of the twelfth aspect, the processor, the memory, and the input/output device are respectively connected to the bus.

A thirteenth aspect in an embodiment of the present application provides a network management apparatus, including: a processor, a memory, an input-output device, and a bus; the memory having stored therein computer instructions; when the processor executes the computer instructions in the memory, the memory stores the computer instructions; the processor, when executing the computer instructions in the memory, is configured to implement any of the implementations of the fifth aspect.

In a possible implementation manner of the thirteenth aspect, the processor, the memory, and the input/output device are respectively connected to the bus.

A fourteenth aspect of the present embodiment provides a chip system, where the chip system includes a processor and an input/output port, where the processor is configured to implement a processing function related to the network management method in the first aspect, and the input/output port is configured to implement a transceiving function related to the network management method in the first aspect.

In one possible design, the system-on-chip further includes a memory for storing program instructions and data for implementing the functions involved in the network management method described in the first aspect above.

The chip system may be constituted by a chip, or may include a chip and other discrete devices.

A fifteenth aspect of the embodiments of the present application provides a chip system, where the chip system includes a processor and an input/output port, where the processor is configured to implement a processing function according to the network management method in any one of the second, third, and fourth aspects, and the input/output port is configured to implement a transceiving function according to the network management method in any one of the second, third, and fourth aspects.

In one possible design, the chip system further includes a memory for storing program instructions and data for implementing the functions involved in the network management method according to any one of the second, third and fourth aspects.

A sixteenth aspect of the present embodiment provides a chip system, where the chip system includes a processor and an input/output port, where the processor is configured to implement the processing function related to the network management method in the fifth aspect, and the input/output port is configured to implement the transceiving function related to the network management method in the fifth aspect.

In one possible design, the system-on-chip further includes a memory for storing program instructions and data for implementing the functions involved in the network management method described in the fifth aspect above.

A seventeenth aspect of embodiments of the present application provides a computer-readable storage medium. The computer readable storage medium having stored therein computer instructions; the computer instructions, when executed on a computer, cause the computer to perform a network management method as described in any one of the possible implementations of the first, second, third, fourth, or fifth aspects.

An eighteenth aspect of embodiments of the present application provides a computer program product. The computer program product comprises a computer program or instructions which, when run on a computer, causes the computer to perform a network management method as described in any one of the possible implementations of any one of the first, second, third, fourth or fifth aspects.

A nineteenth aspect of embodiments of the present application provides a network management system including the network management apparatus according to the first aspect and the network management apparatus according to any one of the second, third, and fourth aspects.

In a possible implementation manner, the network management system further includes the network management apparatus according to the fifth aspect.

According to the technical scheme, the embodiment of the application has the following advantages:

according to the technical scheme, the first management system sends a first request message to the second management system, wherein the first request message is used for requesting the second management system to execute first decision result information of management on the first abnormal event; then, the first management system receives first decision result information of a first abnormal event sent by the second management system, wherein the first decision result information carries the first abnormal event, a management object managed by the first management service, and an execution action and an execution time of the second management system on the first abnormal event; and the first management system executes management operation on a second abnormal event according to the first decision result information, wherein the second abnormal event is associated with the first abnormal event. Therefore, the first management system receives the first decision result information sent by the second management system, and executes management operation on the second abnormal event associated with the first abnormal event according to the first decision result information, so that the problem that processing modes of the first management system and the second management system conflict or are processed repeatedly aiming at the same network fault is avoided, and the network fault processing performance of the two-layer closed-loop architecture or the multi-layer closed-loop architecture is improved.

Drawings

FIG. 1A is a schematic diagram of a network system according to an embodiment of the present application;

FIG. 1B is a schematic diagram of another network system according to an embodiment of the present application;

fig. 2A is a schematic diagram of an embodiment of a network management method according to the present application;

fig. 2B is a schematic view of a scenario of a network management method according to an embodiment of the present application;

fig. 3A is a schematic diagram of another embodiment of a network management method according to an embodiment of the present application;

fig. 4A is a schematic diagram of another embodiment of a network management method according to an embodiment of the present application;

fig. 5A is a schematic diagram of another embodiment of a network management method according to an embodiment of the present application;

fig. 6A is a schematic diagram of another embodiment of a network management method according to an embodiment of the present application;

fig. 7A is a schematic diagram of another embodiment of a network management method according to the embodiment of the present application;

fig. 8A is a schematic structural diagram of a network management device according to an embodiment of the present application;

fig. 9A is a schematic structural diagram of a network management apparatus according to an embodiment of the present application;

fig. 10A is a schematic structural diagram of a network management device according to an embodiment of the present application;

fig. 11A is a schematic structural diagram of a network management device according to an embodiment of the present application;

fig. 12A is a schematic structural diagram of a network management apparatus according to an embodiment of the present application;

fig. 13A is another schematic structural diagram of a network management device according to an embodiment of the present application;

fig. 14A is a schematic diagram of a network management system according to an embodiment of the present application.

Detailed Description

The embodiment of the application provides a network management method and a network management device, which are used for avoiding the problem of conflict or repeated processing of processing modes of a first management system and a second management system aiming at the same network fault so as to improve the network fault processing performance of a two-layer closed-loop architecture or a multi-layer closed-loop architecture.

The network architecture described in the embodiment of the present application is for more clearly illustrating the technical solution of the embodiment of the present application, and does not constitute a limitation to the technical solution provided in the embodiment of the present application, and it is known by a person skilled in the art that as the network architecture evolves, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

The first management system, the second management system, and the first management entity in the embodiment of the present application are described below with reference to fig. 1A and 1B. Fig. 1A is a schematic diagram of a network system according to an embodiment of the present application, where the network system is a two-layer closed-loop system under a ZSM architecture, as shown in fig. 1A, the network system includes an end-to-end management domain and a management domain 1, and the end-to-end management domain is connected with the management domain 1 through a cross-domain integration structure.

The end-to-end management domain and each management domain have a closed loop, and each management domain automatically processes the problems of network faults or network performance reduction and the like of the domain through the closed loop. The closed loop of the end-to-end management domain is a large closed loop, the problem of performance degradation of an end-to-end service layer is solved, and the closed loops of the management domains are coordinated; and the management domain is a small closed loop and processes the resources and services managed in the management domain, and the closed loop in the management domain and the closed loops in other management domains are independent.

Some management services provided by the end-to-end management domain in the present application are described below:

1. end-to-end data collection service group (E2E service data collection): data related to the end-to-end service, such as performance data, network failure data, etc., are collected. An end-to-end performance data reporting service (E2E performance data reporting service) is provided.

2. End-to-end analysis service set (E2E service analytics): providing analysis services (analytics services), providing end-to-end quality of service management services (E2E service quality management services), and providing end-to-end service condition detection services (E2E service condition detection services).

3. End-to-end intelligent service group (E2E service interference): the closed-loop automation of the end-to-end management domain is provided, the automatic decisions of different degrees are supported, and the fault detection and recovery can be performed under the condition of crossing the management domains. An artificial intelligence model management service (AI model management service), a Deployed artificial intelligence model assessment service (Deployed AI model assessment service), an artificial intelligence training data management service (AI training data management service), a decision making service (decision making service), and an end-to-end service health issue reporting service (E2E service health reporting service) are provided.

4. An end-to-end orchestration service group (E2E service organization) coordinates configuration and lifecycle management of services across multiple management domains. Management services such as an end-to-end service orchestration service (E2E service orchestration service), a feasibility check service (availability check service), an end-to-end test service (E2E testing service), and an end-to-end service topology information service (E2E service topology information service) are provided.

5. Support services (Supporting services): policy management service (policy management service) is provided.

Whereas administrative domain 1 provides some of the following administrative services, as described below:

1. domain data collection (Domain data collection) service group: managed entities and services are monitored, and real-time performance and fault data are provided to support closed-loop automation. An event notification service (event notification service), a performance measurement streaming service (performance measurements service), and a log collection service (log collection service) are provided.

2. Domain analytics (domains analytics) service group: the method comprises the steps of preprocessing data in a domain, analyzing and predicting the data, and providing analysis services (analytics services), domain condition detection services (domain condition detection services) and data optimization services (data optimization services).

3. Domain intelligence (Domain interference) service group: the support to the closed-loop decision and AI related technology in the domain provides artificial intelligence model management service (AI model management service), deployed artificial intelligence model assessment service (deployed AI model assessment service), artificial intelligence training data management service (AI training data management service), knowledge base management service (knowledge base service), decision service (decision mapping service) and health issue reporting service (health issue reporting service).

4. Domain organization (Domain organization) service group: the method comprises the steps of automatically managing the life cycle of the intra-domain service, maintaining the information of the intra-domain service and resources, and providing domain organization service (domain organization service), feasibility check service (reactive check service), testing service (testing service), and domain topology information service (domain topology information service).

5. Domain control (Domain control) service: resource configuration management service (resource configuration management service), resource life cycle management service (resource life management service) and configuration data generation service (configuration data generation service) are provided for the life cycle management and configuration of a single resource in a domain.

6. Support services (Supporting services): policy management services are provided.

Integrated architecture (Integration fabric): a management function provides interoperability and interoperability between a plurality of management services, registration, de-registration of management services, and discovery and access of registered services. The integrated architecture provides management service registration services, management service discovery services, management communication services, management service invocation routing services, and management capability open configuration services. Wherein, the integrated structure comprises a domain integrated structure and a cross-domain integrated structure. A Domain Integration fabric (Domain Integration fabric) provides registration and interoperability of intra-Domain services and open-to-the-outside capabilities of the local Domain management services. A Cross-domain Integration fabric (Cross-domain Integration fabric) is a registry for managing services across domains and interoperation across domains.

Data services (data services): data persistence and methods are provided and enable data sharing among multiple administrative domains. Providing data storage management service, data persistence service and data processing service.

The different management services may be provided by hardware such as the same network entity or multiple different network entities (e.g., network elements or controllers), or may be provided by the same network entity or multiple different network entities in combination with software.

In the network system shown in fig. 1A, a first management system in the embodiment of the present application is an end-to-end management domain, a second management system is a management domain 1, and a first management device is a Cross-domain Integration fabric (Cross-domain Integration fabric), where the end-to-end management domain is a main management domain, the management domain 1 is a first sub-management domain, and the end-to-end management domain manages the management domain 1. The end-to-end management service domain and the management domain 1 are then a collection of hardware and/or software, such as one or more network entities (e.g., network elements or controllers, etc.) that provide different management services.

The embodiment of the present application is also applicable to a multilayer closed-loop architecture, which is described below with reference to fig. 1B, where fig. 1B is a schematic diagram of another network system in the embodiment of the present application, the network system is a multilayer closed-loop system under a ZSM architecture, as shown in fig. 1B, the network system includes an end-to-end management domain, a management domain 1 and a management domain 2, the end-to-end management service domain is connected to the management domain 1 through a cross-domain integration structure 1, and the management domain 1 is connected to the management domain 2 through a cross-domain integration structure 2.

The management service provided by the end-to-end management domain is similar to the management service provided by the end-to-end management domain in fig. 1A, and specific reference may be made to the foregoing detailed description of the management service provided by the end-to-end management domain in fig. 1A, which is not repeated here. The management service domains provided by the management domains 1 and 2 are similar to the management service domain provided by the management domain in fig. 1A, and specific reference may be made to the foregoing detailed description of the management service provided by the management domain 1 in fig. 1A, which is not described herein again.

Under the network system shown in fig. 1B, the following situations may exist in the first management system, the second management system, and the first management device in the embodiment of the present application:

in case 1, the first management system is an end-to-end management domain, the second management system is a management domain 1, and the first management device is a cross-domain integrated structure 1. The end-to-end management domain is a main management domain, the management domain 1 is a first sub-management domain, and the main management domain manages the first sub-management domain.

In case 2, the first management system is a management domain 1, the second management system is a management domain 2, and the first management device is a cross-domain integrated structure 2. The end-to-end management domain is a main management domain, the management domain 1 is a first sub-management domain, the management domain 2 is a second sub-management domain, the end-to-end management domain manages the management domain 1, and the management domain 1 manages the management domain 2.

The embodiment of the application is suitable for management coordination between any two closed loops in a multilayer closed loop architecture, and in a subsequent multilayer closed loop architecture, the case 1 is taken as an example for description, and the case 2 is also suitable, and the application is not described one by one.

Second, the first management system and the second management system of the embodiments of the present application are a set of hardware and/or software, such as one or more network entities (e.g., network elements or controllers).

In this embodiment, when performing network management on an exception event, a first management system and a second management system make a decision to perform an action by using a decision making service (decision making service) of the first management system and a decision making service of the second management system, where the decision making service of the first management system is a management service in the first management system corresponding to the second exception event, and the decision making service of the second management system is a management service in the second management system corresponding to the first exception event. For example, data collected by data collection services of the first management system, data of the data services, and a data analysis result obtained by analyzing analysis of the analysis services are input into the determination mapping service of the first management system, and then a management action is executed through a determination mapping service decision of the first management system to perform network management.

In the embodiment of the present application, the interaction between the first management system and the second management system refers to the interaction between the determination mapping service of the first management system and the determination mapping service of the second management system, and for convenience of description, in the following embodiments, the interaction between the determination mapping service of the first management system and the determination mapping service of the second management system is referred to as the interaction between the first management system and the second management system for short, and the interaction between the determination mapping service of the second management system and the determination mapping service of the third management system is referred to as the interaction between the second management system and the third management system for short, where the determination mapping service of the third management system is the management service corresponding to the third abnormal event.

The embodiment of the application is suitable for a two-layer closed-loop architecture and a multi-layer closed-loop architecture, and the following description is respectively combined with the embodiments one by one:

1. the method comprises the steps that a first management system sends a first request message to a second management system, wherein the first request message is used for requesting first decision result information of the second management system to a first abnormal event; then, the first management system receives the first decision result information sent by the second management system, and performs a management operation on the second abnormal event associated with the first abnormal event according to the first decision result information, which is described by the embodiment shown in fig. 2A and the embodiment shown in fig. 5A.

2. A first management system sends a first request message to first management equipment, wherein the first request message is used for requesting first decision result information of a first abnormal event of a second management system; then, the first management device determines an address of a first management service of the first management system according to the first request message, and sends a second request message to the first management system through the address of the first management service, wherein the second request message is used for requesting the first decision result information of the second management system to the first abnormal event. Then, the first management system receives the first decision result information sent by the first management device, and performs a management operation on a second abnormal event associated with the first abnormal event according to the first decision result information, which is described by the embodiment shown in fig. 3A and the embodiment shown in fig. 6A.

3. A first management system sends a first request message to first management equipment, wherein the first request message is used for requesting first decision result information of a first abnormal event of a second management system; the method comprises the steps that a first management device receives a first event type creation request sent by a second management system, the first event type creation request is used for requesting creation of a first event type, the first event type aims at a first management service of the second management system, and the first management service is a management service corresponding to a first abnormal event; then, the first management device creates the first event category and receives the first decision result information sent by the second management system. The first management device sends the first decision result information to the first management system, and the first management system performs a management operation on the second abnormal event associated with the first abnormal event according to the first decision result information, which is described in detail by the embodiment shown in fig. 4A and the embodiment shown in fig. 7A.

Referring to fig. 2A, fig. 2A is a schematic diagram of an embodiment of a network management method according to the present application, the method including:

201. the first management system sends a first request message to the second management system.

The first request message is used for requesting the second management system to determine result information of the first abnormal event.

Wherein the first request message carries at least one of the following parameters:

1. a first exception event;

2. a decision type supported by the first management service;

the first management service is a management service in the second management system corresponding to the first abnormal event. For example, the first abnormal event is that the VNF resource occupancy is too high, the decision type of the first management service is resource optimization, and then the first management service is a decision making service in the second management system for resource optimization.

3. A management object managed by a first management service;

for example, the decision type of the first management service is resource optimization, and the management object managed by the first management service is VNF.

4. The execution action of the first abnormal event by the second management system;

5. the second management system performs a time period for the action of the first exception event.

Optionally, the first request message carries a filter of the first decision result information, where the filter includes the at least one parameter.

For example, the first management system acquires a second abnormal event, where the second abnormal event is service performance degradation, and then the first management system determines, through analysis, that a first abnormal event associated with the second abnormal event is that the VNF resource occupancy is too high, the decision type supported by the first management service is resource optimization, and the management object managed by the first management service is VNF, and then the first management system may send a first request message to the second management system to request to acquire first decision result information of the second management system for performing management on the first abnormal event.

Optionally, the first request message is a first query request message, where the first query request message is used to request to query first decision result information for the second management system to perform management on the first abnormal event; or, the first request message is a first subscription request message, and the first subscription request message is used for subscribing to first decision result information for the second management system to manage the first abnormal event.

It should be noted that, when the first request message is a first subscription request message, the method further includes step 201a and step 201b.

Step 201a: the second management system sends a first subscription response message to the first management system.

The first subscription response message is used for indicating that the first management system successfully subscribes to the first decision result information of the first abnormal event.

Step 201b: and the first management system determines that the first management system successfully subscribes the first decision result information according to the first subscription response message.

In this embodiment, before step 201, the first management system obtains an address of the first management service; the first management system sending the first request message to the second management system comprises: the first management system sends the first request message to the second management system through the address of the first management service. And the first management system obtaining the address of the first management service comprises:

step 201c: the first management system sends a second query request message to the first management device.

Wherein the second query request message is used for requesting to query the address of the first management service.

The second query request message carries at least one parameter of an identifier (domain id) of the second management system, a management object managed by the first management service and a decision type supported by the first management service.

For example, the first query request message carries the decision type supported by the first management service as resource optimization; the management object managed by the first management service is a VNF.

Step 201d: the first management system receives the address of the first management service sent by the first management device.

Specifically, the first management system determines, according to the second query request message, an address of the first management service that the first management system requests for querying, and sends the address of the first management service to the first management device.

For example, the first management system determines that the decision type of the first management service is resource optimization, and then the first management system searches for an address of the decision type management service in the second management system, that is, an address of the first management service (i.e., a corresponding determination mapping service) in the second management system, so that the first management system can send the first request message to the first management service.

202. The second management system performs a management operation on the first exception event.

For example, as shown in fig. 2B, when the anomaly detection service in the management domain 1 detects a network anomaly notification (e.g., the VNF1 resource occupancy is too high), the decision service in the management domain 1 expands the capacity of the VNF1 according to the VNF resource status.

It should be noted that, step 202 and step 201 do not have a fixed execution sequence, and step 201 may be executed first, or step 202 may be executed first, or step 201 to step 202 may be executed at the same time according to the circumstances, which is not limited in this application.

203. And the second management system sends the first decision result information to the first management system according to the first request message.

The first decision result information carries a first abnormal event, a management object managed by the first management service, and an execution action and an execution time period of the first abnormal event by the second management system.

Specifically, the second management system determines first decision result information according to the parameter in the first request message, and then sends the first decision result information to the first management system. Optionally, the second management system filters the decision result information made in the second management system according to the filter carried in the first request message, so as to obtain the first decision result information.

For example, as shown in fig. 2B, the decision type of the first management service is resource optimization, the management object of the first management service is VNF1, and the first abnormal event is that the resource occupancy of VNF1 is too high, the decision service in the management domain 1 may select, according to the information, the first decision result information of the first abnormal event from the decision result information made, and notify the decision service in the end-to-end management domain of the first abnormal event. For example, the first decision result information includes: and executing the action: capacity expansion of the VNF1, execution time: time point a.

204. And the first management system executes management operation on the second abnormal event according to the parameters in the first decision result information.

Wherein the second exception event is associated with the first exception event.

Optionally, the first decision result information carries a first abnormal event, a management object managed by the first management service, an execution action of the second management system on the first abnormal event, and an execution time period; the first management system executing management operation on the second abnormal event according to the first decision result information comprises the following steps: the first management system does not execute action on the second abnormal event according to the management object, the execution action and the execution time period. The following is described in connection with two examples:

example one: the first management system collects a second abnormal event (service performance reduction), and the first management system determines through analysis that the service performance reduction is caused by excessively high resource occupancy rate of the VNF 1. Thus, the first management system may determine that the first exception event is associated with the second exception event, i.e., that the two exception events are alarm information received at different management systems for the same network fault. As shown in step 203, the first decision result information is: and executing the action: capacity expansion of the VNF1, execution time: at time point a, the first management system determines that the second management system has expanded the capacity of the VNF1 according to the first decision result information, and then the management operation performed by the first management system on the second abnormal event according to the first decision result information may be: and checking whether the problem of the service performance reduction is solved after waiting for a period of time, and if the problem is solved, not doing any action. Specifically, as shown in table 1:

TABLE 1

As can be seen from table 1, in the existing process, if the second management system commissions the first management system to expand the volume of the VNF1 again, the VNF1 may be repeatedly expanded, and the management operations executed by the second management system in this embodiment of the present application are: and checking whether the problem of service performance reduction is solved or not after waiting for a period of time, and if the problem is solved, not doing any action, thereby avoiding the problems of repeated capacity expansion operation and resource waste caused by the fact that the first management system entrusts the second management system to expand the VNF1 again.

Example two: the first management system acquires a second abnormal event (the service flow packet loss rate is higher), and the first management system determines that the excessively high service flow packet loss rate is caused by the excessively high VNF1 resource occupancy rate through analysis. Accordingly, the first management system may determine that the first exception event is associated with the second exception event. And the first management system determines that the second management system expands the volume of the VNF1 according to the first decision result information, and then the first management system does not execute actions on the second abnormal event according to the first decision result information. Specifically, as shown in table 2:

TABLE 2

As can be seen from table 2, in the existing process, the second management system migrates the service data on the VNF1 to another VNF, and the management operations performed by the second management system in the embodiment of the present application are: and after waiting for a period of time, checking whether the problem of the overhigh packet loss rate of the service flow is solved, and if the problem is solved, not doing any action. In the existing process, the first management system has already expanded the capacity of the VNF1, and at this time, the second management system migrates the service data on the VNF1 to other VNFs, so that a conflict occurs in the management operation performed by two different management systems on the same network fault, but in the technical scheme of the embodiment of the present application, the second management system makes a decision to check whether the problem of the too high packet loss rate of the service flow is solved after waiting for a period of time, and if the problem is solved, no action is made, so that the problem that the processing modes of the first management system and the second management system conflict for the same network fault is avoided, and the network fault processing performance of the two-layer closed-loop architecture is improved.

In the embodiment of the application, a first management system sends a first request message to a second management system, wherein the first request message is used for requesting the second management system to execute first decision result information of management on a first abnormal event; then, the first management system receives first decision result information of the first abnormal event sent by the second management system, wherein the first decision result information carries the first abnormal event, a management object managed by the first management service, and an execution action and an execution time of the second management system on the first abnormal event; and the first management system executes management operation on a second abnormal event according to the first decision result information, wherein the second abnormal event is associated with the first abnormal event. Therefore, the first management system receives the first decision result information sent by the second management system, and the first management system executes management operation on the second abnormal event related to the first abnormal event according to the first decision result information, so that the problem that the processing modes of the first management system and the second management system conflict or are processed repeatedly aiming at the same network fault is avoided, and the network fault processing performance of the two-layer closed-loop architecture is improved.

Referring to fig. 3A, fig. 3A is a schematic diagram of another embodiment of a network management method according to an embodiment of the present application, where the method includes:

301. the first management system sends a first request message to the first management device.

The first request message is used for requesting the second management system to execute first decision result information of management on the first abnormal event.

Wherein, the first request message carries the identification (domain id) of the second management system. The first request message also carries at least one of the following parameters:

1. a first exception event;

2. a decision type supported by the first management service;

3. A management object managed by a first management service;

4. The execution action of the second management system on the first abnormal event;

5. the second management system executes the time period for the action of the first exception event.

For example, the first management system collects a second abnormal event (service performance degradation), and then the first management system determines, through analysis, that the second abnormal event is caused by a first abnormal event (VNF resource occupancy is too high), that is, the first abnormal event is associated with the second abnormal event, a decision type supported by a first management service corresponding to the first abnormal event is resource optimization, and a management object managed by the first management service is a VNF, and then the first management system may send a first request message to the first management device to request to acquire first decision result information of management performed on the first abnormal event by the second management system.

Optionally, the first request message is a first query request message, where the first query request message is used to request to query first decision result information for managing, by the second management system, the first abnormal event; or, the first request message is a first subscription request message, and the first subscription request message is used for subscribing to first decision result information for the second management system to manage the first abnormal event.

It should be noted that, when the first request message is a first subscription request message, the method further includes step 301a and step 301b.

Step 301a: the first management device sends a first subscription response message to the first management system.

Step 301b: and the first management equipment determines that the first management system successfully subscribes the first decision result information according to the first subscription response message.

In this embodiment, before step 301, the method further includes step 301c.

Step 301c: the first management device creates a first event class.

The first event type is specific to a first management service of the second management system, and the first management service is a management service corresponding to the first abnormal event.

Optionally, the creating granularity of the first event category is specific to a management service in the management system, or specific to an abnormal event in the management service, which is not limited in this application.

302. The first management device sends a second request message to the second management system.

The second request message is used for requesting the second management system to execute first decision result information of management on the first abnormal event. The second request message carries at least one of the following parameters:

1. a first exception event;

2. a decision type supported by the first management service;

3. A management object managed by a first management service;

Optionally, the second request message carries a filter of the first decision result information, where the filter includes the at least one parameter.

Specifically, when the first management device receives the first request message, the first management device determines an address of the first management service of the second management system according to the first request message, and sends the second request message to the second management system through the address of the first management service of the first management system. For example, the second request message carries an identifier of the management domain 1, a decision type of the first management service, a management object managed by the first management service, an execution action on the first abnormal event, and at least one parameter in an execution time period, so that the first management device first determines the management domain 1 according to the identifier of the management domain 1, and then determines an address of the first management service according to the decision type of the first management service, the management object managed by the first management service, the execution action on the first abnormal event, and the at least one parameter in the execution time period. For example, if the decision type of the first management service is resource optimization, and the first abnormal event is that the VNF1 resource occupancy is too high, the first management device may determine that the first management service is a precision mapping service for resource optimization, and determine an address of the precision mapping service.

Optionally, the second request message is a third query request message, where the third query request message is used to request to query first decision result information for managing the first abnormal event executed by the second management system; or the second request message is a second subscription request message, and the second subscription request message is used for requesting to subscribe to first decision result information for the second management system to manage the first abnormal event.

It should be noted that, when the second request message is a second subscription request message, the method further includes:

step 302a: and the second management system sends a second subscription response message to the first management device.

The second subscription response message is used for indicating that the first management device successfully subscribes to the first decision result information.

Step 302b: and the first management equipment determines that the first decision result information is successfully subscribed according to the second subscription response message.

Steps 302a to 302b are performed before steps 301a to 301b, and then steps 301a to 301b are performed.

303. The second management system performs a management operation on the first exception event.

Step 303 is similar to step 202 in fig. 2A, and please refer to the related description of step 202 in fig. 2A for details, which are not repeated herein.

304. And the second management system sends the first decision result information to the first management equipment.

The second management system executes management operation on the first abnormal event to obtain first decision result information; then, the second management system sends the first decision result information to the first management device.

305. And the first management equipment sends the first decision result information to the first management system.

306. And the first management system executes management operation on the second abnormal event according to the parameters in the first decision result information.

Step 306 is similar to step 204 in the embodiment shown in fig. 2A, and please refer to the related description of step 204 in the embodiment shown in fig. 2A, which is not repeated herein.

In the embodiment of the application, a first management system sends a first request message to a first management device, wherein the first request message is used for requesting a first decision result message of a first abnormal event from a second management system; then, the first management device determines an address of a first management service of the first management system according to the first request message, and sends a second request message to the first management system through the address of the first management service, wherein the second request message is used for requesting first decision result information of the second management system on the first abnormal event; the first management equipment receives first decision result information sent by the second management equipment and sends the first decision result information to the first management system, and the first management system executes management operation on a second abnormal event related to the first abnormal event according to the first decision result information. Therefore, the first management system receives the first decision result information sent by the first management device, and executes management operation on the second abnormal event associated with the first abnormal event according to the first decision result information, so that the problem that processing modes of the first management system and the second management system conflict or are processed repeatedly aiming at the same network fault is avoided, and the network fault processing performance of the two-layer closed-loop architecture is improved.

Referring to fig. 4A, fig. 4A is a schematic diagram of another embodiment of a network management method according to an embodiment of the present application, the method including:

401. the second management system transmits a first event category creation request to the first management device.

The first event type creating request is used for requesting the first management device to create a first event type (event category), the first event type is specific to a first management service of the second management system, and the first management service is a management service corresponding to the first abnormal event. The creating granularity of the first event type is similar to that in the step 301c, and please refer to the description in the step 301c, which is not described herein again.

402. The first management device creates a first event class according to the first event class creation request.

Specifically, the first management device creates a first event category according to a first event category creation request actively initiated by the second management system, where the first event category is used to store information of a decision result made in the first management service of the second management system.

403. The first management system sends a first request message to the first management device.

Step 403 is similar to step 301 in the embodiment shown in fig. 3A, and please refer to the description of step 301 in the embodiment shown in fig. 3A for details, which is not repeated herein.

404. The first management system performs a management operation on the first exception event.

Step 404 is similar to step 303 in the embodiment shown in fig. 3A, and please refer to the description of step 303 in the embodiment shown in fig. 3A for details, which are not repeated herein.

It should be noted that there is no fixed execution sequence between step 404 and steps 401 to 403, specifically, step 404 may be executed first, or step 401 to step 403 may be executed first, or step 404 and step 401 to step 403 may be executed simultaneously according to the circumstances, which is not limited in this application.

405. And the second management system sends the first decision result information to the first management equipment.

Step 405 is similar to step 304 in the embodiment shown in fig. 3A, and please refer to the related description of step 304 in the embodiment shown in fig. 3A for details, which are not repeated herein.

406. And the first management equipment sends the first decision result information to the first management system.

407. And the first management system executes management operation on the second abnormal event according to the parameters in the first decision result information.

Step 407 is similar to step 204 in the embodiment shown in fig. 2A, and please refer to the related description of step 204 in the embodiment shown in fig. 2A for details, which are not repeated herein.

In the embodiment of the application, a first management system sends a first request message to a first management device, wherein the first request message is used for requesting a first decision result message of a first abnormal event from a second management system; the method comprises the steps that a first management device receives a first event type creating request sent by a second management system, the first event type creating request is used for requesting creation of a first event type, the first event type aims at a first management service of the second management system, and the first management service is a management service corresponding to a first abnormal event; then, the first management device creates the first event category and receives the first decision result information sent by the second management system. The first management device sends the first decision result information to a first management system, and the first management system executes management operation on a second abnormal event related to the first abnormal event according to the first decision result information. Therefore, the first management system receives the first decision result information sent by the first management device, and executes management operation on the second abnormal event associated with the first abnormal event according to the first decision result information, so that the problem that processing modes of the first management system and the second management system conflict or are processed repeatedly aiming at the same network fault is avoided, and the network fault processing performance of the two-layer closed-loop architecture is improved.

Referring to fig. 5A, fig. 5A is a schematic diagram of another embodiment of a network management method according to an embodiment of the present application, the method including:

501. the first management system sends a first request message to the second management system.

Step 501 is similar to step 201 in the embodiment shown in fig. 2A, and please refer to the description of step 201 in the embodiment shown in fig. 2A, which is not repeated here.

502. The second management system sends a third request message to a third management system.

The third request message is used for requesting a third management system to execute second decision result information of management on a third abnormal event, and the third abnormal event is associated with the first abnormal event.

Wherein the third request message carries at least one of the following parameters:

1. a third exception event;

2. a decision type supported by the second management service;

the second management service is a management service in the second management system corresponding to the third abnormal event. For example, the third abnormal event is that the VNF1 resource occupancy is too high, the decision type of the second management service is resource optimization, and then the second management service is a decision making service in a third management system for resource optimization.

3. A management object managed by a second management service;

for example, the decision type of the second management service is resource optimization, and the management object managed by the second management service is VNF.

4. An execution action of the third management system on the third exception event;

5. the third management system executes the time period for the action of the third exception event.

Specifically, the second management system may determine, through analysis, that the third exception is associated with the first exception, and then obtain, by the second management system, an address of a second management service of the third management system corresponding to the third exception, and send the third request message to the third management system through the address of the second management service.

For example, the first abnormal event is that the user registration success rate of the second management system (core network management domain) is low or the call completing rate is low, the third abnormal event is that the VNF1 resource occupancy rate in the third management system (NFV management domain) is too high, the second abnormal event is that the network slice 1 performance of the first management system (end-to-end management domain) is degraded, and the second management system determines through analysis that the user registration success rate is low or the call completing rate is low and is caused by the VNF1 resource occupancy rate being too high.

The address for the second management system to acquire the second management service is similar to the address for the first management system to acquire the first management service in steps 201c to 201d in the embodiment shown in fig. 2A, and details are not repeated here.

Optionally, the third request message is a fourth query request message, and the fourth query request message is used to request to query the second decision result information; or the third request message is a third subscription request message, and the third subscription request message is used for subscribing the second decision result information.

It should be noted that, when the third request message is a third subscription request message, the method further includes:

step 502a: and the third management system sends a third subscription response message to the second management system.

And the third subscription response message is used for indicating that the subscription of the second decision result information is successful.

Step 502b: and the second management system determines that the subscription of the second decision result information is successful according to the third subscription response message.

503. The third management system performs a management operation on the third exception event.

For example, the third abnormal event is that the VNF1 resource occupancy rate is too high, the NFV management domain determines that the VNF1 resource is insufficient through analysis, the NFV management domain expands the VNF1 resource, and the execution time is time point B.

It should be noted that there is no fixed execution sequence between step 503 and steps 501 to 502, step 503 may be executed first, step 501 to step 502 may be executed first, or step 503 and step 501 to step 502 may be executed simultaneously according to the circumstances, and the present application is not limited in this respect.

504. And the third management system sends the second decision result information to the second management system.

Optionally, the third management system further sends exception information of a third exception event to the second management system.

505. And the second management system executes management operation on the first abnormal event according to the parameters in the second decision result information.

The second decision result information comprises a third abnormal event, a management object managed by the second management service, an execution action of a third management system on the third abnormal event and an execution time period; the second management system executing management operation on the first abnormal event according to the parameter in the second decision information comprises: and the second management system does not execute the action on the first abnormal event according to the management object, the execution action and the execution time period.

Optionally, the second management system receives exception information of a third exception event sent by the third management system; the second management system executing management operation on the first abnormal event according to the second decision result information comprises the following steps: and the second management system executes management operation according to the second decision result information and the abnormal information of the third abnormal event.

For example, the first abnormal event is that the registration success rate of the user is low or the call completing rate is low, and the second decision result information includes: and executing the action: expanding the volume of the VNF 1; the execution time is a time point B; then, the core network management domain determines that the capacity of the VNF1 has been expanded according to the execution action and the execution time, and the core network management domain does not execute the action on the first abnormal event, or checks whether the user registration success rate or the call completing rate returns to normal after waiting for a period of time, and if so, does not execute the action; if not, further analyzing other reasons causing low success rate of user registration or low call completing rate.

506. And the second management system sends the first decision result information to the first management system.

507. And the first management system executes management operation on the first abnormal event according to the parameters in the first decision result information.

Steps 506 to 507 are similar to steps 203 to 204 in the embodiment shown in fig. 2A, and please refer to descriptions of steps 203 to 204 in the embodiment shown in fig. 2A, which are not described herein again.

The following describes, with reference to an example, technical effects brought by the embodiments of the present application on processing results of a first exception event, a second exception event, and a third exception event through the technical solution of the present embodiment, please refer to table 3:

TABLE 3

As can be seen from table 3, in the multi-layer closed-loop architecture, the coordination among the management systems handles the abnormal event, so as to avoid the problem of repeated operation or conflict in handling.

In the embodiment of the application, a first management system sends a first request message to a second management system, wherein the first request message is used for requesting the second management system to execute first decision result information of management on a first abnormal event; then, the first management system receives first decision result information of a first abnormal event sent by the second management system, wherein the first decision result information carries the first abnormal event, a management object managed by the first management service, and an execution action and an execution time of the second management system on the first abnormal event; and the first management system executes management operation on a second abnormal event according to the first decision result information, wherein the second abnormal event is associated with the first abnormal event. Therefore, the first management system receives the first decision result information sent by the second management system, and executes management operation on the second abnormal event associated with the first abnormal event according to the first decision result information, so that the problem that processing modes of the first management system and the second management system conflict or are processed repeatedly aiming at the same network fault is avoided, and the network fault processing performance of the multilayer closed-loop architecture is improved.

Another possible implementation manner is provided in the embodiment of the present application, which is similar to the embodiment shown in fig. 5A, and the difference is in steps 506 and 507; wherein step 506 is replaced by: and the second management system sends the first decision result information, the abnormal information of the third abnormal event and the information of the second abnormal event to the first management system. Step 507 is replaced by: and the first management system executes management operation on the first abnormal event according to the first decision result information, the abnormal information of the third abnormal event and the information of the second abnormal event.

Referring to fig. 6A, fig. 6A is a schematic diagram of another embodiment of a network management method according to an embodiment of the present application, where the method includes:

601. the first management system sends a first request message to the first management device.

602. The first management device sends a second request message to the second management system.

Steps 601 to 602 are similar to steps 301 to 302 in the embodiment shown in fig. 3A, and please refer to the descriptions of steps 301 to 302 in the embodiment shown in fig. 3A for details, which are not described herein again.

603. The second management system transmits a third request message to the second management device.

The third request message is used for requesting the third management system to execute second decision result information of management on a third abnormal event, and the third abnormal event is associated with the first abnormal event.

Wherein the third request message carries an identifier of the third management system. The third request message also carries at least one of the following parameters:

1. a third exception event;

2. a decision type supported by the second management service;

3. A management object managed by a second management service;

5. the third management system performs a time period for an action of the third exception event.

Specifically, the second management system may determine, through analysis, that the third exception event is associated with the first exception event, and then the second management system transmits the third request message to the second management apparatus.

For example, the first abnormal event is that the user registration success rate of the second management system (core network management domain) is low or the call completing rate is low, the third abnormal event is that the VNF1 resource occupancy rate in the third management system (NFV management domain) is too high, and the second management system determines through analysis that the user registration success rate is low or the call completing rate is caused by the VNF1 resource occupancy rate being too high.

Optionally, the third request message is a fourth query request message, and the fourth query request queries the second decision result information; or the third request message is a third subscription request message, and the third subscription request message is used for subscribing the second decision result information.

step 603a: the second management device sends a third subscription response message to the second management system.

Step 603b: and the second management system determines that the subscription of the second decision result information is successful according to the third subscription response message.

604. The second management device transmits a fourth request message to the third management system.

The fourth request message is used for requesting the third management system to execute second decision result information of management on the third exception event. The fourth request message carries at least one of the following parameters:

1. a third exception event;

2. a decision type supported by the second management service;

3. A management object managed by a second management service;

Optionally, the fourth request message is a fifth query request message, and the fifth query request message is used to request to query the second decision result information; or the fourth request message is a fourth subscription request message, and the fourth subscription request message is used for subscribing the second decision result information.

It should be noted that, when the fourth request message is a fourth subscription request message, the method further includes:

step 604a: the third management system sends a fourth subscription response message to the second management device.

And the fourth subscription response message is used for indicating that the subscription of the second decision result information is successful.

Step 604b: and the second management equipment determines that the second decision result information is successfully subscribed according to the fourth subscription response message.

605. The third management system performs a management operation on the third exception event.

Step 605 is similar to step 503 in the embodiment shown in fig. 5A, and please refer to the description of step 503 in the embodiment shown in fig. 5A for details, which is not repeated herein.

Step 605 and steps 601 to 604 are not performed in a fixed order, step 605 may be performed first, step 601 to step 604 may be performed, or step 605 and steps 601 to 604 may be performed simultaneously according to the situation, which is not limited in the present application.

606. And the third management system sends the second decision result information to the second management equipment.

607. The second management equipment sends second decision result information to the second management system

608. And the second management system executes management operation on the first abnormal event according to the parameters in the second decision result information.

Step 608 is similar to step 505 in the embodiment shown in fig. 5A, and please refer to the description of step 505 in the embodiment shown in fig. 5A in detail, which is not repeated here.

Step 608 and steps 601 to 602 do not have a fixed execution sequence, and step 608 may be executed first, or step 601 to step 602 may be executed first, or step 608 and steps 601 to step 602 may be executed simultaneously according to the circumstances, which is not limited in the present application.

609. And the second management system sends the first decision result information to the first management equipment.

610. And the first management equipment sends the first decision result information to the first management system.

611. And the first management system executes management operation on the second abnormal event according to the parameters in the first decision result information.

Step 611 is similar to step 507 in the embodiment shown in fig. 5A, and please refer to the description of step 507 in the embodiment shown in fig. 5A for details, which is not repeated herein.

In the embodiment of the application, a first management system sends a first request message to a first management device, wherein the first request message is used for requesting first decision result information of a first abnormal event from a second management system; then, the first management device determines an address of a first management service of the first management system according to the first request message, and sends a second request message to the first management system through the address of the first management service, wherein the second request message is used for requesting the first decision result information of the second management system to the first abnormal event; the first management equipment receives first decision result information sent by the second management equipment and sends the first decision result information to the first management system, and the first management system executes management operation on a second abnormal event related to the first abnormal event according to the first decision result information. Therefore, the first management system receives the first decision result information sent by the first management device, and executes management operation on the second abnormal event associated with the first abnormal event according to the first decision result information, so that the problem that processing modes of the first management system and the second management system conflict or are processed repeatedly aiming at the same network fault is avoided, and the network fault processing performance of the multilayer closed-loop architecture is improved.

Another possible implementation manner is provided in the embodiment of the present application, which is similar to the embodiment shown in fig. 6A, and the differences are step 606, step 607, step 608, step 609, step 610, and step 611; wherein step 606 is replaced with: the third management system sends the second decision result information and the abnormal information of the third abnormal event to the second management device; step 607 is replaced by that the second management device sends the second decision result information and the abnormal information of the third abnormal event to the second management system; step 608 is replaced with: the second management system executes management operation on the first abnormal event according to the second decision result information and the abnormal information of the third abnormal event; step 609 is replaced by: the second management system sends the first decision result information, the abnormal information of the third abnormal event and the abnormal information of the first abnormal event to the first management device; step 610 is replaced by: the second management system sends the first decision result information, the abnormal information of the third abnormal event and the abnormal information of the first abnormal event to the first management device; step 611 is replaced with: and the first management system executes management operation on the first abnormal event according to the first decision result information, the second decision result information, the abnormal information of the third abnormal event and the abnormal information of the first abnormal event.

Referring to fig. 7A, fig. 7A is a schematic diagram of another embodiment of a network management method according to an embodiment of the present application, the method including:

701. the second management system transmits a first event category creation request to the first management device.

702. The first management system creates a first event class according to the first event class creation request.

Steps 701 to 702 are similar to steps 401 to 402 in the embodiment described in fig. 4A, and please refer to the descriptions of steps 401 to 402 in the embodiment shown in fig. 4A for details, which are not described herein again.

703. The third management system transmits a second event category creation request to the second management device.

The second event category creating request is used for requesting the second management device to create a second event category, the second event category is specific to a third management service of a third management system, and the third management service is a management service corresponding to a third abnormal event.

For example, if the third abnormal event is a low registration success rate or a low call completing rate, the precision mapping service of the third management system for performing management operation on the third abnormal event serves the second management service.

The creating granularity of the second event category is similar to that in the step 301c, and please refer to the description in the step 301c, which is not described herein again.

704. The second management device creates a second event category according to the second event category creation request.

Step 704 is similar to step 402 in the embodiment described in fig. 4A, and please refer to the description of step 402 in the embodiment described in fig. 4A, which is not repeated herein.

It should be noted that, the steps 703 to 704 and the steps 701 to 702 do not have a fixed execution sequence, the steps 703 to 704 may be executed first, the steps 701 to 702 may be executed first, or the steps 703 to 704 and the steps 701 to 702 may be executed simultaneously according to the situation, and the specific application is not limited thereto.

705. The first management system sends a first request message to the first management device.

Step 705 is similar to step 403 in the embodiment shown in fig. 4A, and please refer to the related description of step 403 in the embodiment shown in fig. 4A for details, which are not repeated herein.

706. The first management device sends a third request message to the second management system.

Step 706 is similar to step 603 in the embodiment shown in fig. 6A, and please refer to related descriptions of step 603 and step 605 in the embodiment shown in fig. 6A, which is not repeated herein.

707. The third management system performs a management operation on the third exception event.

Step 707 is similar to step 503 in the embodiment shown in fig. 5A, and please refer to the description of step 503 in the embodiment shown in fig. 5A for details, which is not repeated herein.

708. And the third management system sends the second decision result information to the second management equipment.

709. And the second management equipment sends second decision result information to the second management system.

710. And the second management system executes management operation on the first abnormal event according to the parameters in the second decision result information.

Step 710 is similar to step 505 in the embodiment shown in fig. 5A, and please refer to the description of step 505 in the embodiment shown in fig. 5A, which is not repeated here.

711. And the second management system sends the first decision result information to the first management equipment.

712. And the first management equipment sends the first decision result information to the first management system.

713. And the first management system executes management operation on the second abnormal event according to the parameters in the first decision result information.

Step 713 is similar to step 507 in the embodiment shown in fig. 5A, and please refer to the description of step 507 in the embodiment shown in fig. 5A for details, which will not be described herein again.

In the embodiment of the application, a first management system sends a first request message to a first management device, wherein the first request message is used for requesting a first decision result message of a first abnormal event from a second management system; the method comprises the steps that a first management device receives a first event type creation request sent by a second management system, the first event type creation request is used for requesting creation of a first event type, the first event type aims at a first management service of the second management system, and the first management service is a management service corresponding to a first abnormal event; then, the first management device creates the first event category and receives the first decision result information sent by the second management system. And the first management equipment sends the first decision result information to a first management system, and the first management system executes management operation on a second abnormal event related to the first abnormal event according to the first decision result information. Therefore, the first management system receives the first decision result information sent by the first management device, and executes management operation on the second abnormal event associated with the first abnormal event according to the first decision result information, so that the problem that processing modes of the first management system and the second management system conflict or are processed repeatedly aiming at the same network fault is avoided, and the network fault processing performance of the multilayer closed-loop architecture is improved.

Another possible implementation manner is provided in the embodiment of the present application, which is similar to the embodiment shown in fig. 6A, and the difference is that steps 708 to 713; wherein step 708 is replaced by: the third management system sends the second decision result information and the abnormal information of the third abnormal event to the second management device; step 709, the second management device sends the second decision result information and the abnormal information of the third abnormal event to the second management system; step 710 is replaced with: the second management system executes management operation on the first abnormal event according to the second decision result information and the abnormal information of the third abnormal event; step 711 is replaced with: the second management system sends the first decision result information, the abnormal information of the third abnormal event and the abnormal information of the first abnormal event to the first management device; step 712 is replaced with: the second management system sends the first decision result information, the abnormal information of the third abnormal event and the abnormal information of the first abnormal event to the first management device; step 713 is replaced by: and the first management system executes management operation on the first abnormal event according to the first decision result information, the second decision result information, the abnormal information of the third abnormal event and the abnormal information of the first abnormal event.

It should be noted that, in the embodiments shown in fig. 5A to fig. 7A, only under the multilayer closed-loop architecture, the abnormal event execution management operation is described between the multiple management systems through the technical solution of the embodiment of the present application as an example, and in an actual application, any two-layer management system under the multilayer closed-loop architecture may also execute the management operation on the abnormal event through the technical solution of the embodiment of the present application, and the present application is not limited specifically.

Next, in the examples in the above embodiments, the end-to-end management domain is used as the first management system, the management domain 1 is used as the second management system, the management domain 2 is used as the second management system, and the end-to-end management domain manages the management domain 1. Optionally, under the multi-layer closed-loop architecture, the management domain 2 is a third management system, and the management domain 1 manages the management domain 2. In practical application, the coordination between any two layers of management systems under a two-layer or multi-layer closed-loop architecture may be performed, that is, the management relationship between the two coordinated management systems is not limited, and specifically, the coordination management may be initiated in combination with the time when the actual management systems of each layer receive the network fault (usually, the management system close to the network fault source receives the network fault first, and processes the network fault). For example, the first management system is management domain 1 and the second management system is an end-to-end management domain.

A network management apparatus provided in an embodiment of the present application is described below. Referring to fig. 8A, in an embodiment of a network management apparatus in the present application, the network management apparatus may be a first management system, or a chip or a system-on-chip on the first management system, and the network management apparatus may be configured to perform steps performed by the first management system in the embodiments shown in fig. 2A, fig. 3A, fig. 4A, fig. 5A, fig. 6A, and fig. 7A, which may be referred to in the description related to the above method embodiments.

The network management device comprises a transceiver module 801 and a processing module 802;

a transceiver module 801, configured to send a first request message to a second management system, where the first request message is used to request the second management system to execute first decision result information for managing a first abnormal event; receiving first decision result information of a first abnormal event sent by a second management system, wherein the first decision result information carries the first abnormal event, a management object managed by a first management service, and an execution action and an execution time of the first abnormal event by the second management system;

the processing module 802 is configured to perform a management operation on a second exception event according to the first decision result information, where the second exception event is associated with the first exception event.

In another possible implementation manner, the first decision result information carries the first exception event, a management object managed by a first management service, and an execution action and an execution time of the second management system on the first exception event, where the first management service is a management service in the second management system corresponding to the first exception event; the processing module 802 is specifically configured to:

In another possible implementation manner, when the transceiver module 801 sends the first request message to the first management device, the first request message also carries an identifier of the second management system.

In another possible implementation manner, the first request message is a first subscription request message, and the first subscription request message is used for subscribing to the first decision result information; the transceiver module 801 is further configured to:

the processing module 802 is further configured to:

In another possible implementation manner, the transceiver module 801 is further configured to:

the processing module 802 is specifically configured to:

In another possible implementation manner, the network management device is a master management system, the second management system is a first sub-management system, the third management system is a second sub-management system, the first sub-management system is a sub-management system of the master management system, and the second sub-management system is a sub-management system of the first sub-management system.

In this embodiment of the application, the transceiver module 801 sends a first request message to the second management system or the first management device, where the first request message is used to request the second management system to execute first decision result information for managing the first abnormal event; then, the transceiver module 801 receives first decision result information of a first abnormal event sent by a second management system or a first management device, where the first decision result information carries the first abnormal event, a management object managed by a first management service, and an execution action and an execution time of the first abnormal event by the second management system; the processing module 802 performs a management operation on a second exception event according to the first decision result information, wherein the second exception event is associated with the first exception event. Therefore, the transceiver module 801 receives the first decision result information sent by the second management system or the first management device, and the processing module 802 performs a management operation on the second abnormal event associated with the first abnormal event according to the first decision result information, so as to avoid the problem that the processing modes of the network management apparatus and the second management system conflict or are processed repeatedly for the same network fault, thereby improving the network fault processing performance of the two-layer closed-loop architecture.

A network management apparatus provided in an embodiment of the present application is described below. Referring to fig. 9A, in an embodiment of a network management apparatus in the present application, the network management apparatus may be a second management system, or a chip or a system-on-chip on the second management system, and the network management apparatus may be configured to perform steps performed by the second management system in the embodiments shown in fig. 2A, fig. 3A, fig. 4A, fig. 5A, fig. 6A, and fig. 7A, which may refer to relevant descriptions in the above method embodiments.

The network management device comprises a transceiver module 901; optionally, the network management apparatus further includes a processing module 902.

A transceiver module 901, configured to receive a first request message sent by a first management system; and sending first decision result information of a first abnormal event to the first management system according to the first request message, wherein the first decision result information is decision result information of the network management device for managing the first abnormal event.

In a possible implementation manner, the first request message carries at least one parameter of a first exception event, a decision type supported by a first management service, a management object managed by the first management service, an execution action of the network management device on the first exception event, and an action execution time period; the transceiver module 901 is specifically configured to:

In another possible implementation manner, the transceiver module 901 is further configured to:

the processing module 902 is configured to perform a management operation on the first exception event according to the second decision result information, so as to obtain first decision result information of the first exception event.

In this embodiment of the application, the transceiver module 901 receives a first request message sent by a first management system; the transceiver module 901 sends first decision result information of a first abnormal event to the first management system according to the first request message, where the first decision result information is decision result information of the network management device performing management on the first abnormal event. In this possible implementation manner, the transceiver module 901 provides the first decision result information to the first management system, so that the first management system performs a management operation on the second abnormal event by combining with the first decision result information, thereby avoiding a problem that processing manners of the first management system and the network management apparatus conflict or are processed repeatedly for the same network fault, so as to improve network fault processing performance of the two-layer closed-loop architecture or the multi-layer closed-loop architecture.

Optionally, the network management apparatus shown in fig. 9A is further configured to execute the following scheme:

a transceiver module 901, configured to receive a second request message sent by a first management device; and sending first decision result information of a first abnormal event to the first management device according to the second request message, wherein the first decision result information is decision result information of the network management device for managing the first abnormal event.

In a possible implementation manner, the transceiver module 901 is further configured to:

the network management apparatus further includes a processing module 902;

the processing module 902 is specifically configured to:

In another possible implementation manner, the processing module 902 is further configured to:

In this embodiment of the application, the transceiver module 901 receives a second request message sent by the first management device; the transceiver module 901 sends first decision result information of a first abnormal event to the first management device according to the second request message, where the first decision result information is decision result information of the network management apparatus for performing management on the first abnormal event. In this possible implementation manner, the transceiver module 901 provides the first decision result information to the first management device, so that the first management device can send the first decision result information to the first management system, and thus the first management system can perform management operation on the second abnormal event by combining the first decision result information, thereby avoiding the problem of processing mode conflict or repeated processing of the first management system and the network management apparatus for the same network fault, so as to improve the network fault processing performance of the two-layer closed-loop architecture or the multi-layer closed-loop architecture.

a transceiver module 901, configured to send a first event category creation request to a first management device, where the first event category creation request is used to request the first management device to create a first event category, where the first event category is for a first management service of a second management system, and the first management service is a management service corresponding to a first abnormal event; and sending first decision result information of the first abnormal event to the first management device, wherein the first decision result information is decision result information of the second management system for managing the first abnormal event.

acquiring second decision result information, wherein the second decision result is decision result information of a third management system for managing a third abnormal event, and the third abnormal event is associated with the first abnormal event;

the network management device further comprises a processing module 902;

the processing module 902 is further configured to:

In this embodiment of the application, the transceiver module 901 sends a first event category creation request to a first management device, where the first event category creation request is used to request the first management device to create a first event category, the first event category is specific to a first management service of a second management system, and the first management service is a management service corresponding to a first abnormal event; the transceiver module 901 sends the first decision result information of the first exception event to the first management device, where the first decision result information is the decision result information of the second management system performing management on the first exception event. In this possible implementation manner, the transceiver module 901 actively initiates a request for creating a first event class to the first management device, and the transceiver module 901 provides the first decision result information to the first management device, so that the first management device sends the first decision result information to the first management system, so that the first management system can perform management operation on the second abnormal event by combining the first decision result information, thereby avoiding a problem of processing mode conflict or repeated processing of the first management system and the network management apparatus for the same network fault, and improving network fault processing performance of the two-layer closed-loop architecture or the multi-layer closed-loop architecture.

A network management apparatus provided in an embodiment of the present application is described below. Referring to fig. 10A, in an embodiment of a network management apparatus in the present application, the network management apparatus may be a first management device, or a chip system located on the first management device, and the network management apparatus may be configured to perform steps performed by the first management device in the embodiments shown in fig. 3A, fig. 4A, fig. 6A, and fig. 7A, which may refer to relevant descriptions in the foregoing method embodiments.

A transceiver module 1001, configured to receive a first request message sent by the first management system; and sending first decision result information of a first abnormal event to the first management system according to the first request message, wherein the first decision result information is decision result information of the second management system for managing the first abnormal event.

In another possible implementation manner, the network management apparatus further includes a processing module 1002;

the processing module 1002 is configured to determine an address of a first management service in the second management system according to the first request message;

the transceiving module 1001 is further configured to:

In another possible implementation manner, the transceiver module 1001 is further configured to:

the processing module 1002 is further configured to:

the transceiving module 1001 is further configured to:

receiving exception information of a third exception event and second decision result information sent by the second management system, wherein the second decision result information is decision result information for the third management system to manage the third exception event, and the third exception event is associated with the first exception event;

In this embodiment, the transceiver module 1001 receives a first request message sent by the first management system; the transceiver module 1001 sends first decision result information of a first abnormal event to the first management system according to the first request message, where the first decision result information is decision result information of the second management system performing management on the first abnormal event. Therefore, the transceiver module 1001 sends the first decision result information of the first abnormal event to the first management system, so that the first management system performs a management operation on the second abnormal event associated with the first abnormal event according to the first decision result information, thereby avoiding a problem of processing mode conflict or repeated processing of the first management system and the second management system for the same network fault, and improving the network fault processing performance of the two-layer closed-loop architecture or the multi-layer closed-loop architecture.

Referring to fig. 11A, the network management apparatus 1100 according to an embodiment of the present application may be a first management system, or a chip or a system-on-chip on the first management system, and the network management apparatus may be configured to execute steps executed by the first management system in the embodiments shown in fig. 2A, fig. 3A, fig. 4A, fig. 5A, fig. 6A, and fig. 7A, which may refer to relevant descriptions in the foregoing method embodiments.

The network management apparatus 1100 includes: a processor 1101, a memory 1102, an input-output device 1103, and a bus 1104.

In one possible implementation, the processor 1101, the memory 1102 and the input/output device 1103 are each coupled to the bus 1104, and the memory stores computer instructions.

The processing module 802 in the embodiment shown in fig. 8A may be specifically the processor 1101 in this embodiment, and therefore, detailed implementation of the processor 1101 is not described again. The transceiver module 801 in the embodiment shown in fig. 8A may specifically be the input/output device 1103 in this embodiment, and therefore details of the specific implementation of the input/output device 1103 are not repeated.

Referring to fig. 12A, in an embodiment of the network management apparatus in the present application, the network management apparatus may be a second management system, or a chip or a system-on-chip on the second management system, and the network management apparatus may be configured to execute steps executed by the second management system in the embodiments shown in fig. 2A, fig. 3A, fig. 4A, fig. 5A, fig. 6A, and fig. 7A, which may refer to relevant descriptions in the above method embodiments.

The network management apparatus 1200 includes: a processor 1201, a memory 1202, an input output device 1203, and a bus 1204.

In one possible implementation, the processor 1201, the memory 1202 and the input/output device 1203 are each coupled to the bus 1204, and the memory has stored therein computer instructions.

The processing module 902 in the embodiment shown in fig. 9A may specifically be the processor 1201 in this embodiment, and therefore specific implementation of the processor 1201 is not described again. The transceiver module 901 in the embodiment shown in fig. 9A may specifically be an input/output device 1203 in this embodiment, and therefore details of the specific implementation of the input/output device 1203 are not described herein again.

Referring to fig. 13A, the present application further provides a network management apparatus 1300, referring to the related description in the foregoing method embodiment, where the network management apparatus in this embodiment may be a first management device, or a chip system located on the first management device, and the network management apparatus may be configured to execute the steps executed by the first management device in the embodiments shown in fig. 3A, fig. 4A, fig. 6A, and fig. 7A.

The network management apparatus 1300 includes: a processor 1301, a memory 1302, an input-output device 1303, and a bus 1304.

In one possible implementation, the processor 1301, the memory 1302, and the input/output device 1303 are respectively connected to a bus 1304, and the memory stores computer instructions.

The processing module 1002 in the embodiment shown in fig. 10A may be specifically the processor 1301 in this embodiment, and therefore, detailed implementation of the processor 1301 is not described again. The transceiver module 1001 in the embodiment shown in fig. 10A may specifically be the input/output device 1303 in this embodiment, and therefore detailed implementation of the input/output device 1303 is not described again.

Referring to fig. 14A, an embodiment of the present application further provides a network management system, where the network management system includes a network management device, and specifically, the network management device may include a first management system and a second management system; optionally, the network management system further includes a first management device; wherein, the first management system may be configured to execute all or part of the steps executed by the first management system in the embodiments shown in fig. 2A, fig. 3A, fig. 4A, fig. 5A, fig. 6A and fig. 7A, and the second management system is configured to execute all or part of the steps executed by the second management system in the embodiments shown in fig. 2A, fig. 3A, fig. 4A, fig. 5A, fig. 6A and fig. 7A; the first management device is configured to perform all or part of the steps performed by the first management device in the embodiments illustrated in fig. 3A, 4A, 6A, and 7A.

An embodiment of the present application provides a chip system, which includes a processor and an input/output port, where the processor is configured to implement the processing functions related to the embodiments shown in fig. 2A, fig. 3A, fig. 4A, fig. 5A, fig. 6A, and fig. 7A, and the input/output port is configured to implement the transceiving functions related to the embodiments shown in fig. 2A, fig. 3A, fig. 4A, fig. 5A, fig. 6A, and fig. 7A.

In one possible design, the system-on-chip further includes a memory for storing program instructions and data implementing the functions involved in the embodiments illustrated in fig. 2A, 3A, 4A, 5A, 6A, and 7A described above.

According to the method provided by the embodiment of the present application, the present application further provides a computer program product, which includes: computer program code which, when run on a computer, causes the computer to perform the method of the embodiment shown in fig. 2A, 3A, 4A, 5A, 6A and 7A.

There is also provided a computer readable medium storing program code, which when run on a computer causes the computer to perform the method of the embodiments shown in fig. 2A, fig. 3A, fig. 4A, fig. 5A, fig. 6A and fig. 7A, according to the method provided by the embodiments of the present application.

The embodiment of the application also provides a processing device, which comprises a processor and an interface; the processor is configured to perform the method of any of the above method embodiments.

It should be understood that the processing means may be a chip. For example, the processing device may be a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), a system on chip (SoC), a Central Processing Unit (CPU), a Network Processor (NP), a digital signal processing circuit (DSP), a Microcontroller (MCU), a Programmable Logic Device (PLD), or other integrated chips.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor. To avoid repetition, it is not described in detail here.

It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip having signal processing capability. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor described above may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and combines hardware thereof to complete the steps of the method.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

The first management system and the second management system in the network management apparatus and method embodiments of the above-mentioned respective apparatus embodiments completely correspond to the first management device, and corresponding modules or units execute corresponding steps, for example, a communication unit (transceiver) executes a step of receiving or transmitting in the method embodiments, and other steps except for transmitting and receiving may be executed by a processing unit (processor). The functions of the specific elements may be referred to in the respective method embodiments. The number of the processors may be one or more.

Those of ordinary skill in the art will appreciate that the various illustrative logical blocks and steps (step) described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk, and various media capable of storing program codes.

Claims

1. A method of network management, the method comprising:

a first management system sends a first request message to a second management system or first management equipment, wherein the first request message is used for requesting first decision result information of the second management system for managing a first abnormal event;

the first management system receives first decision result information of the first abnormal event sent by the second management system or first management equipment;

the first management system executes management operation on a second abnormal event according to parameters in the first decision result information, wherein the second abnormal event is associated with the first abnormal event;

the first decision result information carries the first abnormal event, a management object managed by a first management service, and an execution action and an execution time of the first abnormal event by the second management system, wherein the first management service is a management service in the second management system corresponding to the first abnormal event;

the first management system executing management operation on the second abnormal event according to the parameter in the first decision result information comprises the following steps:

and the first management system does not execute the action on the second abnormal event according to the execution action, the execution time and the management object.

2. The method of claim 1, wherein the first request message carries at least one parameter of the first exception event, a decision type supported by a first management service, a management object managed by the first management service, an action performed by the second management system on the first exception event, and an action execution time period.

3. The method according to claim 1 or 2, wherein when the first management system sends the first request message to the first management device, the first request message further carries an identifier of the second management system.

4. The method according to claim 1 or 2, wherein the first request message is a first query request message, and the first query request message is used for requesting to query the first decision result information.

5. The method according to claim 1 or 2, wherein the first request message is a first subscription request message, and the first subscription request message is used for subscribing to the first decision result information; the method further comprises the following steps:

the first management system receives a first subscription response message sent by the second management system or the first management device;

and the first management system determines that the first management system successfully subscribes the first decision result information according to the first subscription response message.

6. The method according to claim 1 or 2, characterized in that the method further comprises:

the first management system receives exception information and second decision result information of a third exception event sent by the second management system or the first management device, wherein the second decision result information is decision result information of the third management system for executing management on the third exception event, and the third exception event is associated with the first exception event;

the first management system executing management operation on the second abnormal event according to the first decision result information comprises the following steps:

and the first management system executes management operation on the second abnormal event according to the first decision result information, the abnormal information of the third abnormal event and the second decision result information.

7. The method of claim 6, wherein the first management system is a master management system, the second management system is a first sub-management system, the third management system is a second sub-management system, the first sub-management system is a sub-management system of the master management system, and the second sub-management system is a sub-management system of the first sub-management system.

8. The method according to claim 1 or 2,

the first management system is a main management system, the second management system is a first sub-management system, and the first sub-management system is a sub-management system of the main management system; alternatively, the first and second electrodes may be,

the first management system is a first sub-management system, the second management system is a second sub-management system, and the second sub-management system is a sub-management system of the first sub-management system.

9. A method for network management, the method comprising:

the second management system receives a first request message sent by the first management system;

the second management system sends first decision result information of a first abnormal event to the first management system according to the first request message, wherein the first decision result information is decision result information of the second management system for managing the first abnormal event; the first decision result information carries the first abnormal event, the management object managed by the first management service, and the execution action and execution time of the second management system on the first abnormal event, and the first management service is a management service in the second management system corresponding to the first abnormal event.

10. The method of claim 9, wherein the first request message carries at least one parameter of a first exception event, a decision type supported by a first management service, a management object managed by the first management service, an action performed by the second management system on the first exception event, and an action execution time period; the sending, by the second management system, first decision result information of the first abnormal event to the first management system according to the first request message includes:

the second management system determines the first decision result information according to the parameters in the first request message;

and the second management system sends the first decision result information to the first management system.

11. The method according to claim 9 or 10, characterized in that the method further comprises:

the second management system acquires second decision result information, wherein the second decision result information is decision result information of a third management system for managing a third abnormal event, and the third abnormal event is associated with the first abnormal event;

and the second management system executes management operation on the first abnormal event according to the second decision result information to obtain first decision result information of the first abnormal event.

12. The method of claim 11, further comprising:

and the second management system sends the abnormal information of the third abnormal event and the second decision result information to the first management system.

13. The method according to claim 9 or 10,

14. A method for network management, the method comprising:

the second management system receives a second request message sent by the first management equipment;

the second management system sends first decision result information of a first abnormal event to the first management device according to the second request message, wherein the first decision result information is decision result information of the second management system for managing the first abnormal event; the first decision result information carries the first abnormal event, a management object managed by a first management service, and an execution action and an execution time of the first abnormal event by the second management system, and the first management service is a management service in the second management system corresponding to the first abnormal event.

15. The method of claim 14, further comprising:

16. The method of claim 15, further comprising:

and the second management system sends the abnormal information of the third abnormal event and the second decision result information to the first management device.

17. A method of network management, the method comprising:

a second management system sends a first event type creating request to a first management device, wherein the first event type creating request is used for requesting the first management device to create a first event type, the first event type is specific to a first management service of the second management system, and the first management service is a management service corresponding to a first abnormal event;

the second management system sends first decision result information of the first abnormal event to the first management device, wherein the first decision result information is decision result information of the second management system for managing the first abnormal event; the first decision result information carries the first abnormal event, the management object managed by the first management service, and the execution action and execution time of the first abnormal event by the second management system.

18. The method of claim 17, further comprising:

the second management system acquires second decision result information, wherein the second decision result is decision result information of a third management system for executing management on a third abnormal event, and the third abnormal event is associated with the first abnormal event;

19. The method of claim 18, further comprising:

20. A method for network management, the method comprising:

the method comprises the steps that first management equipment receives a first request message sent by a first management system;

the first management device sends first decision result information of a first abnormal event to the first management system according to the first request message, wherein the first decision result information is decision result information of a second management system for managing the first abnormal event; the first decision result information carries the first abnormal event, the management object managed by the first management service, and the execution action and execution time of the second management system on the first abnormal event, and the first management service is a management service in the second management system corresponding to the first abnormal event.

21. The method of claim 20, wherein the first request message carries an identification of the second management system; the first request message also carries at least one piece of information of the first abnormal event, the decision type supported by the first management service, the management object managed by the first management service, the execution action of the second management system on the first abnormal event and the action execution time period.

22. The method of claim 20, further comprising:

the first management equipment determines the address of the first management service in the second management system according to the first request message;

the first management device sends a second request message to the second management system through the address of the first management service, wherein the second request message is used for requesting the second management system to execute first decision result information of management on a first abnormal event;

and the first management equipment receives first decision result information of the first abnormal event sent by the second management system.

23. The method of claim 20, further comprising:

the first management device receives a first event type creation request sent by the second management system;

the first management device creates a first event category according to the first event category creation request, the first event category being for a first management service of the second management system;

24. The method of claim 20, further comprising:

the first management device receives exception information of a third exception event and second decision result information sent by the second management system, wherein the second decision result information is decision result information of the third management system for managing the third exception event, and the third exception event is associated with the first exception event;

and the first management equipment sends the abnormal information of the third abnormal event and the second decision result information to the first management system.

25. A network management apparatus, characterized in that the network management apparatus comprises: a processor coupled with a memory;

the memory for storing a computer program;

the processor configured to execute the computer program stored in the memory to cause the network management apparatus to perform the network management method according to any one of claims 1 to 8.

26. A network management apparatus, characterized in that the network management apparatus comprises: a processor coupled with a memory;

the memory for storing a computer program;

the processor configured to execute the computer program stored in the memory to cause the network management apparatus to perform the network management method according to any one of claims 9 to 13 or claims 14 to 16 or claims 17 to 19.

27. A network management apparatus, characterized in that the network management apparatus comprises: a processor coupled with a memory;

the memory for storing a computer program;

the processor configured to execute the computer program stored in the memory to cause the network management apparatus to perform the network management method according to any one of claims 20 to 24.