A network automation management method and device

Abstract

A network automation management method and device are used to monitor the network closed-loop automation process, so as to achieve better network operation and maintenance effects and improve network operation and maintenance efficiency. The method is as follows: The closed-loop monitoring function unit obtains the closed-loop monitoring capability information of the closed-loop scenario, and determines at least one closed-loop monitoring point of the closed-loop scenario according to the closed-loop monitoring capability information of the closed-loop scenario; the closed-loop monitoring capability information represents the closed-loop monitoring capabilities supported by the closed-loop scenario; the closed-loop monitoring function unit sends a closed-loop monitoring request to the closed-loop execution function unit, and the closed-loop monitoring request includes the information of the closed-loop scenario and the information of at least one closed-loop monitoring point; during the closed-loop operation of the closed-loop scenario, when the closed-loop execution function unit executes to at least one closed-loop monitoring point, it obtains the monitoring information of the closed-loop monitoring point and sends a monitoring notification to the closed-loop monitoring function unit, and the monitoring notification carries the identifier and monitoring information of the closed-loop monitoring point. In this way, the network operation and maintenance effect is better and the network operation and maintenance efficiency is high.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the priority of a Chinese patent application with an application number of 202010277762.1, filed with the China National Intellectual Property Administration on April 8, 2020, the entire content of which is incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technologies, and particularly to a network automation management method and apparatus in a network closed-loop automation scenario. Background Art

[0004] With the development of communication technologies, the requirements for key performance indicators such as network latency, rate, and connection scale are continuously increasing. The application industries are also becoming more diverse and rich, and the performance guarantee and flexibility of services have undergone fundamental changes, resulting in an increase in network operation and maintenance difficulty.

[0005] The application of automation technologies in mobile communication networks has increasingly become the focus of industry attention and a research hotspot. The industry hopes to introduce automation technologies (such as artificial intelligence, machine learning, big data analysis, etc.) to help solve the current operation and maintenance efficiency and capacity problems in mobile communication networks.

[0006] To improve the efficiency of network operation and maintenance, equipment manufacturers introduce corresponding automation technologies during the life cycle of a network (including one or more network devices) (including four stages: planning, deployment, maintenance, and optimization), and gradually realize the full-process closed-loop automation from intention requirement mapping, perception, analysis, decision-making to execution. For example, the specific process can be as follows: An operation and maintenance personnel issues an intention to a management function device (such as an equipment manufacturer's management system), and the management function device gradually executes intention translation (translating the intention into a network management task or policy), network perception (collecting corresponding network data), analysis (performing network performance analysis based on the collected network data, identifying network problems, and generating a network optimization or adjustment plan based on the identified network problems), decision-making (determining the network optimization or adjustment plan based on the analysis result), and execution (executing the network optimization or adjustment plan based on the determined result); finally, the management function device feeds back the intention execution result (such as whether the intention is satisfied) to the operation and maintenance personnel.

[0007] However, the entire automation closed-loop process is completed inside the management function device, and the operation and maintenance personnel cannot obtain the process information of intention execution, cannot monitor the intention execution process, and cannot achieve a good network operation and maintenance effect. Summary of the Invention

[0008] The present application provides a network automation management method and device for monitoring the network closed-loop automation process, so as to achieve better network operation and maintenance effects and improve network operation and maintenance efficiency.

[0009] In a first aspect, the present application provides a network automation management method applied to the network closed-loop automation process. The method may include: the closed-loop monitoring function unit obtains the closed-loop monitoring capability information of the closed-loop scenario, and determines at least one closed-loop monitoring point of the closed-loop scenario according to the closed-loop monitoring capability information of the closed-loop scenario; the closed-loop monitoring function unit sends a closed-loop monitoring request to the closed-loop execution function unit, and the closed-loop monitoring request includes the information of the closed-loop scenario and the information of the at least one closed-loop monitoring point; and receives the monitoring notifications corresponding to the at least one closed-loop monitoring point from the closed-loop execution function unit, and the monitoring notifications carry the identifiers and monitoring information of the corresponding closed-loop monitoring points; wherein, the closed-loop monitoring capability information is used to characterize the closed-loop monitoring capabilities supported by the closed-loop scenario.

[0010] Through the above method, the monitoring of the network closed-loop automation process can be realized, so as to achieve better network operation and maintenance effects and improve network operation and maintenance efficiency. At the same time, it enables the operator to flexibly customize the closed-loop monitoring information according to the needs, monitors and controls the network closed-loop automation process to a certain extent, prevents the negative impact of the network closed-loop automation process on network adjustment, and can evaluate the closed-loop capabilities of manufacturers according to the monitoring information.

[0011] In a possible design, the closed-loop monitoring capability information includes the closed-loop monitoring points supported by the closed-loop scenario; or, the closed-loop monitoring capability information includes the closed-loop monitoring points supported by the closed-loop scenario and the monitoring types corresponding to the closed-loop monitoring points. This can enable the closed-loop monitoring function unit to accurately determine at least one closed-loop monitoring point of the closed-loop scenario.

[0012] In a possible design, the specific method for the closed-loop monitoring function unit to determine at least one closed-loop monitoring point of the closed-loop scenario according to the closed-loop monitoring capability information of the closed-loop scenario may be: the closed-loop monitoring function unit determines the at least one closed-loop monitoring point according to the closed-loop monitoring capability information and its own monitoring requirements. In this way, the closed-loop monitoring function unit can determine the closed-loop monitoring points that meet its own monitoring capabilities and monitoring requirements.

[0013] In a possible design, the closed-loop monitoring function unit obtains the closed-loop monitoring capability information of the closed-loop scenario. The specific method may be as follows: The closed-loop monitoring function unit obtains the closed-loop monitoring capability information from the closed-loop execution function unit; or, the closed-loop monitoring function unit obtains the template information of the closed-loop scenario, and the closed-loop monitoring capability information is included in the template information. In this way, the closed-loop monitoring function unit can flexibly and accurately obtain the closed-loop monitoring capability information, and then accurately determine the closed-loop monitoring points of the closed-loop scenario subsequently.

[0014] In a possible design, the at least one closed-loop monitoring point may include at least one of the following: an intent translation monitoring point, a perception monitoring point, a network analysis monitoring point, a decision-making monitoring point, or an execution monitoring point; wherein, the intent translation monitoring point is used to indicate the process or result of monitoring the translation of an intent into a management task or policy; the perception monitoring point is used to indicate the process or result of monitoring network perception; the network analysis monitoring point is used to indicate the process or result of monitoring network analysis; the decision-making monitoring point is used to indicate the process of monitoring decision-making; the execution monitoring point is used to indicate the result of monitoring execution. In this way, corresponding monitoring can be performed according to different closed-loop monitoring points.

[0015] In a possible design, the intent translation monitoring point may include at least one of the following: an intent translation process or result monitoring point, an intent satisfaction result monitoring point; wherein, the intent translation process or result monitoring point is used to indicate the process or result after the execution of the intent translation function each time in the initial intent translation stage or the intent retranslation stage; the intent satisfaction result monitoring point is used to indicate the process of monitoring the non-satisfaction of the intent. In this way, corresponding monitoring can be performed according to different closed-loop monitoring points.

[0016] In a possible design, the perception monitoring point may include at least one of the following: a network information collection process or result monitoring point, a network anomaly discovery process or result monitoring point; wherein, the network information collection process or result monitoring point is used to indicate the monitoring of the collected network information, and the network information is the original network information or the processed statistical network information; the network anomaly discovery process or result monitoring point is used to indicate the monitoring of the network anomaly information. In this way, corresponding monitoring can be performed according to different closed-loop monitoring points.

[0017] In a possible design, the network analysis monitoring points may include at least one of the following: network problem discovery monitoring points, network problem analysis monitoring points, and network optimization or adjustment plan generation monitoring points. Among them, the network problem discovery monitoring points are used to indicate the detection process or result of monitoring network problems; the network problem analysis monitoring points are used to indicate the analysis process or result of monitoring network problems; the network optimization or adjustment plan generation monitoring points are used to indicate the process or result of monitoring the generated network optimization / adjustment plan. In this way, corresponding monitoring can be performed according to different closed-loop monitoring points.

[0018] In a possible design, the monitoring information in the monitoring notification corresponding to the intent translation monitoring point includes at least one of a closed-loop scenario identifier, an intent evaluation result, and an intent translation result; the monitoring information in the monitoring notification corresponding to the perception monitoring point includes at least one of a closed-loop scenario identifier and network information; the monitoring information in the monitoring notification corresponding to the network analysis monitoring point includes at least one of a closed-loop scenario identifier and an analysis result; the monitoring information in the monitoring notification corresponding to the decision-making monitoring point includes at least one of a closed-loop scenario identifier and a solution to the determined network problem; the monitoring information in the monitoring notification corresponding to the execution monitoring point includes at least one of a closed-loop scenario identifier and an execution result of the solution to the network problem. In this way, the monitoring content corresponding to the closed-loop monitoring points can be clarified.

[0019] In a possible design, the closed-loop monitoring function unit determines the monitoring type corresponding to the at least one closed-loop monitoring point according to the closed-loop controllability capability information. The monitoring type of any closed-loop monitoring point is monitoring or monitoring and control. Among them, when the monitoring type of a closed-loop monitoring point is monitoring, it indicates that there is no need to interrupt and the closed-loop process continues to be executed; when the monitoring type of a closed-loop monitoring point is monitoring and control, it indicates that the closed-loop process is interrupted and waiting for confirmation. In this way, the subsequent closed-loop process can be executed according to the monitoring type of the closed-loop monitoring point.

[0020] In a possible design, the closed-loop monitoring request further includes the monitoring type corresponding to the at least one closed-loop monitoring point. In this way, the closed-loop execution function unit can execute the closed-loop process according to the monitoring type of the closed-loop monitoring point subsequently.

[0021] In a possible design, the closed-loop monitoring function unit sends monitoring confirmation information to the closed-loop execution function unit, and the monitoring confirmation information includes the identifier of the monitoring point and the confirmation result; wherein, the confirmation result includes at least one of the following: when the closed-loop monitoring point is an intended translation monitoring point, the closed-loop monitoring function unit confirms the intended translation result of the closed-loop execution function unit and instructs the closed-loop execution function unit to continue executing the closed-loop process; when the closed-loop monitoring point is an intended perception monitoring point, the closed-loop monitoring function unit confirms the network anomaly detected by the closed-loop execution function unit and instructs the closed-loop execution function unit to continue executing the closed-loop process; when the closed-loop monitoring point is a network analysis monitoring point, the closed-loop monitoring function unit confirms one of the following: confirms that the closed-loop execution function unit detects or discovers a network problem and instructs the closed-loop execution function unit to continue executing the closed-loop process; or, confirms the cause of the network problem analyzed by the closed-loop execution function unit and instructs the closed-loop execution function unit to continue executing the closed-loop process; or, confirms the network adjustment plan recommended by the closed-loop execution function unit and instructs the closed-loop execution function unit to continue executing the closed-loop process; when the closed-loop monitoring point is a decision-making monitoring point, the closed-loop monitoring function unit confirms the network adjustment plan selected by the closed-loop execution function unit and instructs the closed-loop execution function unit to continue executing the closed-loop process; when the closed-loop monitoring point is an execution monitoring point, the closed-loop monitoring function unit confirms the execution result of the network adjustment plan by the closed-loop execution function unit. This enables the closed-loop execution function unit to execute the closed-loop process according to the corresponding confirmation information.

[0022] In a possible design, when the closed-loop scenario is a coverage optimization scenario, the at least one closed-loop monitoring point is at least one coverage optimization closed-loop monitoring point, where: the intended translation monitoring point is a coverage optimization intended translation monitoring point; the perception monitoring point is a coverage performance detection monitoring point; the network analysis monitoring point includes at least one of a coverage problem detection monitoring point, an abnormal cell identification monitoring point, and a coverage optimization plan recommendation monitoring point; the decision-making monitoring point is a coverage optimization plan determination monitoring point; the execution monitoring point is a coverage optimization plan execution monitoring point; the coverage optimization intended translation monitoring point is used to indicate monitoring of the execution result of the coverage optimization intended translation; the coverage performance detection monitoring point is used to indicate monitoring of the coverage performance indicators; the coverage problem detection monitoring point is used to indicate monitoring of cell or area-level coverage problems; the abnormal cell identification monitoring point is used to indicate monitoring of abnormal cells; the coverage optimization plan recommendation monitoring point is used to indicate monitoring of at least one candidate coverage optimization plan for solving the coverage problem; the coverage optimization plan determination monitoring point is used to indicate monitoring of determining the coverage optimization plan for solving the coverage problem; the coverage optimization plan execution monitoring point is used to indicate monitoring of the execution of the coverage optimization plan. Thus, corresponding monitoring can be performed according to different closed-loop monitoring points in the coverage optimization scenario.

[0023] In a possible design, the monitoring notification corresponding to the coverage optimization intent translation monitoring point is a coverage intent translation monitoring notification, and the monitoring information of the coverage intent translation monitoring notification includes at least one of an intent identifier and an intent translation result; the monitoring notification corresponding to the coverage performance detection monitoring point is a coverage performance detection monitoring notification, and the monitoring information of the coverage performance detection monitoring notification includes at least one of an intent identifier and coverage performance information; the monitoring notification corresponding to the coverage problem detection monitoring point is a coverage problem detection monitoring notification, and the monitoring information of the coverage problem detection monitoring notification includes at least one of an intent identifier and a detected coverage problem; the monitoring notification corresponding to the abnormal cell identification monitoring point is an abnormal cell identification monitoring notification, and the monitoring information of the abnormal cell identification monitoring notification includes at least one of an intent identifier and a list of abnormal cells; the monitoring notification corresponding to the coverage optimization scheme determination monitoring point is a coverage adjustment scheme generation monitoring notification, and the monitoring information of the coverage adjustment scheme generation monitoring notification includes at least one of an intent identifier and at least one repair scheme; the monitoring notification corresponding to the coverage optimization scheme execution monitoring point is a coverage adjustment scheme execution monitoring notification, and the monitoring information of the coverage adjustment scheme execution monitoring notification includes at least one of an intent identifier and modified configuration information. This can clarify the monitoring content corresponding to the closed-loop monitoring points in the coverage optimization scenario.

[0024] In a possible design, when the closed-loop scenario is a coverage optimization scenario, the closed-loop monitoring capability information is coverage optimization closed-loop monitoring capability information.

[0025] In a possible design, when the closed-loop scenario is a coverage optimization scenario, the closed-loop monitoring request further includes at least one of a coverage optimization intent identifier, a coverage optimization object, or a coverage target.

[0026] In a possible design, when the closed-loop scenario is a coverage optimization scenario, and when the closed-loop monitoring point is a monitoring point for translating coverage optimization intent, the confirmation information is the confirmation information for the translated result of the coverage optimization intent, and the confirmation information for the translated result of the coverage optimization intent is used to instruct the closed-loop execution functional unit to continue executing the coverage optimization closed-loop process; when the closed-loop monitoring point is a monitoring point for detecting coverage problems, the confirmation information is the coverage problem confirmation information, and the coverage problem confirmation information is used to instruct the closed-loop execution functional unit to continue executing the coverage optimization closed-loop process to handle the coverage problem; when the closed-loop monitoring point is a monitoring point for identifying abnormal cells, the confirmation information is the abnormal cell identification confirmation information, and the abnormal cell identification confirmation information is used to instruct the closed-loop execution functional unit to continue executing the coverage optimization closed-loop process to handle the abnormal cell; when the closed-loop monitoring point is a monitoring point for determining the coverage optimization plan, the confirmation information is the confirmation information for the coverage adjustment plan, and the confirmation information for the coverage adjustment plan is used to instruct the closed-loop execution functional unit to continue executing the coverage adjustment plan. This enables the closed-loop execution functional unit to execute the closed-loop process according to the corresponding confirmation information in the coverage optimization scenario.

[0027] In a possible design, the information of the closed-loop scenario may include at least one of the following: the type of the closed-loop scenario, the identifier of the closed-loop scenario, or the goal of the closed-loop scenario.

[0028] In a possible design, the closed-loop scenario may be the scenario of any of the following closed-loop tasks: the closed-loop task in the planning phase, the closed-loop task in the deployment phase, the closed-loop task in the maintenance phase, or the closed-loop task in the optimization phase; among them, the closed-loop task in the planning phase includes at least one of service planning, network planning, and site planning; the closed-loop task in the deployment phase includes at least one of service delivery or deployment, network deployment, and site deployment; the closed-loop task in the maintenance phase includes at least one of service fault recovery, network fault recovery, and site fault recovery; the closed-loop task in the optimization phase includes at least one of service guarantee, network optimization, and site optimization; the network optimization includes at least one of network coverage optimization, network capacity optimization, and network quality optimization.

[0029] In a possible design, the closed-loop monitoring functional unit is a cross-domain management unit, and the closed-loop execution functional unit is a domain management unit.

[0030] Second aspect, the present application provides a network automation management method, which is applied to the network closed-loop automation process. The method may include: a closed-loop execution function unit receives a closed-loop monitoring request sent by a closed-loop monitoring function unit, and the closed-loop monitoring request includes information about a closed-loop scenario and information about at least one closed-loop monitoring point; during the closed-loop operation of the closed-loop scenario, when the closed-loop execution function unit reaches the at least one closed-loop monitoring point, it acquires monitoring information of the closed-loop monitoring point and sends a monitoring notification to the closed-loop monitoring function unit, and the monitoring notification carries the identifier of the closed-loop monitoring point and the monitoring information.

[0031] Through the above method, the monitoring of the network closed-loop automation process can be realized, so as to achieve a better network operation and maintenance effect and improve the network operation and maintenance efficiency. At the same time, it enables the operator to flexibly customize the closed-loop monitoring information as needed, to a certain extent monitor and control the network closed-loop automation process, prevent the negative impact brought by the network closed-loop automation process on network adjustment, and can evaluate the closed-loop ability of the manufacturer according to the monitoring information.

[0032] In a possible design, the closed-loop execution function unit sends the closed-loop monitoring ability information of the closed-loop scenario to the closed-loop monitoring function unit, and the closed-loop monitoring ability information is used to characterize the closed-loop monitoring ability supported by the closed-loop scenario; wherein, the closed-loop monitoring ability information includes the closed-loop monitoring points supported by the closed-loop scenario; or, the closed-loop monitoring ability information includes the closed-loop monitoring points supported by the closed-loop scenario and the monitoring types corresponding to the closed-loop monitoring points. In this way, the closed-loop monitoring function unit can accurately obtain the closed-loop monitoring ability information, and then accurately determine the closed-loop monitoring points of the closed-loop scenario subsequently.

[0033] In a possible design, the at least one closed-loop monitoring point may include at least one of the following: an intent translation monitoring point, a perception monitoring point, a network analysis monitoring point, a decision-making monitoring point, or an execution monitoring point; wherein, the intent translation monitoring point is used to indicate the process or result of monitoring the translation of an intent into a specific management task or policy; the perception monitoring point is used to indicate the process or result of monitoring network perception; the network analysis monitoring point is used to indicate the process or result of monitoring network analysis; the decision-making monitoring point is used to indicate the process or result of monitoring decision-making; the execution monitoring point is used to indicate the result of monitoring execution. In this way, corresponding monitoring can be carried out according to different closed-loop monitoring points.

[0034] In a possible design, the intent translation monitoring point may include at least one of the following: an intent translation process or result monitoring point, an intent satisfaction result monitoring point; wherein, the intent translation process or result monitoring point is used to indicate monitoring the process of the intent translation function execution or the result after execution each time in the initial intent translation stage or the intent re - translation stage; the intent satisfaction result monitoring point is used to indicate monitoring the process of intent dissatisfaction. In this way, corresponding monitoring can be carried out according to different closed - loop monitoring points.

[0035] In a possible design, the perception monitoring point may include at least one of the following: a network information collection process or result monitoring point, a network anomaly discovery process or result monitoring point; wherein, the network information collection process or result monitoring point is used to indicate monitoring the collected network information, and the network information is the original network information or the processed statistical network information; the network anomaly discovery process or result monitoring point is used to indicate monitoring the information of network anomalies. In this way, corresponding monitoring can be carried out according to different closed - loop monitoring points.

[0036] In a possible design, the network analysis monitoring point may include at least one of the following: a network problem discovery monitoring point, a network problem analysis monitoring point, a network optimization or adjustment plan generation monitoring point; wherein, the network problem discovery monitoring point is used to indicate monitoring the detection process or result of network problems; the network problem analysis monitoring point is used to indicate monitoring the analysis process or result of network problems; the network optimization or adjustment plan generation monitoring point is used to indicate monitoring the process or result of the generated network optimization / adjustment plan. In this way, corresponding monitoring can be carried out according to different closed - loop monitoring points.

[0037] In a possible design, when the closed - loop execution function unit executes to the intent translation monitoring point, the monitoring information notified by the monitoring includes at least one of the closed - loop scenario identifier, the intent evaluation result, and the intent translation result; when the closed - loop execution function unit executes to the perception monitoring point, the monitoring information notified by the monitoring includes at least one of the closed - loop scenario identifier and the network information; when the closed - loop execution function unit executes to the network analysis monitoring point, the monitoring information notified by the monitoring includes at least one of the closed - loop scenario identifier and the analysis result; when the closed - loop execution function unit executes to the decision - making monitoring point, the monitoring information notified by the monitoring includes at least one of the closed - loop scenario identifier and the solution to the determined network problem; when the closed - loop execution function unit executes to the execution monitoring point, the monitoring information notified by the monitoring includes at least one of the closed - loop scenario identifier and the execution result of the solution to the network problem. In this way, the monitoring content corresponding to the closed - loop monitoring point can be clarified.

[0038] In a possible design, the closed-loop monitoring request further includes the monitoring type corresponding to the at least one closed-loop monitoring point; the monitoring type of any closed-loop monitoring point is monitoring or monitoring and control; wherein, when the monitoring type of a closed-loop monitoring point is monitoring, it indicates that there is no need to interrupt and the closed-loop process continues to be executed; when the monitoring type of a closed-loop monitoring point is monitoring and control, it indicates that the closed-loop process is interrupted and waiting for confirmation. This enables the subsequent closed-loop execution functional unit to execute the closed-loop process according to the monitoring type of the closed-loop monitoring point.

[0039] In a possible design, the closed-loop execution unit receives monitoring confirmation information from the closed-loop monitoring functional unit, and the monitoring confirmation information includes a monitoring point identifier and a confirmation result. This enables the closed-loop execution functional unit to execute the closed-loop process according to the corresponding confirmation information.

[0040] In a possible design, when the closed-loop scenario is a coverage optimization scenario, the at least one closed-loop monitoring point is at least one coverage optimization closed-loop monitoring point, where: the intention translation monitoring point is a coverage optimization intention translation monitoring point; the perception monitoring point is a coverage performance detection monitoring point; the network analysis monitoring point includes at least one of a coverage problem detection monitoring point, an abnormal cell identification monitoring point, and a coverage optimization solution recommendation monitoring point; the decision monitoring point is a coverage optimization solution determination monitoring point; the execution monitoring point is a coverage optimization solution execution monitoring point; the coverage optimization intention translation monitoring point is used to indicate monitoring the execution result of the coverage optimization intention translation; the coverage performance detection monitoring point is used to indicate monitoring the coverage performance metrics; the coverage problem detection monitoring point is used to indicate monitoring the coverage problems at the cell or area level; the abnormal cell identification monitoring point is used to indicate monitoring abnormal cells; the coverage optimization solution recommendation monitoring point is used to indicate monitoring at least one candidate coverage optimization solution for solving the coverage problem; the coverage optimization solution determination monitoring point is used to indicate monitoring the determination of the coverage optimization solution for solving the coverage problem; the coverage optimization solution execution monitoring point is used to indicate monitoring the execution of the coverage optimization solution. This enables corresponding monitoring according to different closed-loop monitoring points in the coverage optimization scenario.

[0041] In a possible design, when the closed-loop scenario is a coverage optimization scenario, when the closed-loop execution function unit reaches the coverage optimization intent translation monitoring point, the monitoring notification is a coverage intent translation monitoring notification, and the monitoring information of the coverage intent translation monitoring notification includes at least one of an intent identifier and an intent translation result; when the closed-loop execution function unit reaches the coverage performance detection monitoring point, the monitoring notification is a coverage performance detection monitoring notification, and the monitoring information of the coverage performance detection monitoring notification includes at least one of an intent identifier and coverage performance information; when the closed-loop execution function unit reaches the coverage problem detection monitoring point, the monitoring notification is a coverage problem detection monitoring notification, and the monitoring information of the coverage problem detection monitoring notification includes at least one of an intent identifier and a detected coverage problem; when the closed-loop execution function unit reaches the abnormal cell identification monitoring point, the monitoring notification is an abnormal cell identification monitoring notification, and the monitoring information of the abnormal cell identification monitoring notification includes at least one of an intent identifier and an abnormal cell list; when the closed-loop execution function unit reaches the coverage optimization solution determination monitoring point, the monitoring notification is a coverage adjustment solution generation monitoring notification, and the monitoring information of the coverage adjustment solution generation monitoring notification includes at least one of an intent identifier and at least one repair solution; when the closed-loop execution function unit reaches the coverage optimization solution execution monitoring point, the monitoring notification is a coverage adjustment solution execution monitoring notification, and the monitoring information of the coverage adjustment solution execution monitoring notification includes at least one of an intent identifier and modified configuration information. This can clarify the monitoring content corresponding to the closed-loop monitoring points in the coverage optimization scenario.

[0042] In a possible design, when the monitoring type of a closed-loop monitoring point is monitoring, the closed-loop execution function unit continues to execute the closed-loop process when it reaches the closed-loop monitoring point; when the monitoring type of a closed-loop monitoring point is monitoring and control, the closed-loop execution function unit suspends the closed-loop process when it reaches the closed-loop monitoring point and waits for the confirmation information from the closed-loop monitoring function unit. This can execute the closed-loop process according to the monitoring type of the monitoring point.

[0043] In a possible design, when the closed-loop scenario is a coverage optimization scenario, the closed-loop monitoring capability information is coverage optimization closed-loop monitoring capability information.

[0044] In a possible design, when the closed-loop scenario is a coverage optimization scenario, the closed-loop monitoring request may further include at least one of a coverage optimization intent identifier, a coverage optimization object, or a coverage target.

[0045] In a possible design, the information of the closed-loop scenario may include at least one of the following: the type of the closed-loop scenario, the identifier of the closed-loop scenario, or the target of the closed-loop scenario.

[0046] In a possible design, the closed-loop monitoring functional unit may be a cross-domain management unit, and the closed-loop execution functional unit may be a domain management unit.

[0047] In a third aspect, the present application provides a closed-loop monitoring functional unit, which is used to implement the functions of the closed-loop monitoring functional unit in the above-mentioned first aspect or each possible design example of the first aspect. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0048] In a possible design, the structure of the closed-loop monitoring functional unit includes a communication unit and a processing unit, and these units can execute the corresponding functions of the closed-loop monitoring functional unit in the above-mentioned first aspect or each possible design example of the first aspect. For specific details, refer to the detailed description in the method examples and will not be elaborated here.

[0049] In a possible design, the structure of the closed-loop monitoring functional unit includes a communication interface and a processor, and optionally further includes a memory. The communication interface is used to send and receive information or data, and to communicate and interact with other devices in the system. The processor is configured to support the closed-loop monitoring functional unit to execute the corresponding functions of the closed-loop monitoring functional unit in the above-mentioned first aspect or each possible design example of the first aspect. The memory is coupled to the processor and stores the necessary program instructions and data of the closed-loop monitoring functional unit.

[0050] In a fourth aspect, the present application provides a closed-loop execution functional unit, which is used to implement the functions of the closed-loop execution functional unit in the above-mentioned second aspect or each possible design example of the second aspect. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0051] In a possible design, the structure of the closed-loop execution functional unit includes a communication unit and a processing unit, and these units can execute the corresponding functions of the closed-loop execution functional unit in the above-mentioned second aspect or each possible design example of the second aspect. For specific details, refer to the detailed description in the method examples and will not be elaborated here.

[0052] In a possible design, the structure of the closed-loop execution functional unit includes a communication interface and a processor, and optionally further includes a memory. The communication interface is used for receiving and transmitting information or data, and for communicating and interacting with other devices in the system. The processor is configured to support the closed-loop execution functional unit to execute the corresponding functions of the closed-loop execution functional unit in the above-mentioned second aspect or each possible design example of the second aspect. The memory is coupled to the processor and stores the necessary program instructions and data of the closed-loop execution functional unit.

[0053] In a fifth aspect, an embodiment of the present application provides a system, which may include the above-mentioned closed-loop monitoring functional unit, closed-loop execution functional unit, etc.

[0054] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores program instructions. When the program instructions are run on a computer, the computer is caused to execute the method in any one of the possible designs in the above-mentioned first aspect or second aspect. Exemplarily, the computer-readable storage medium may be any available medium that can be accessed by a computer. By way of example but not limited to: the computer-readable medium may include a non-transitory computer-readable medium, random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disc storage, magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer.

[0055] In a seventh aspect, an embodiment of the present application provides a computer program product including computer program code or instructions. When it runs on a computer, the computer is caused to implement the method in any one of the possible designs in the above-mentioned first aspect or second aspect.

[0056] In an eighth aspect, the present application further provides a chip, including a processor and a communication interface. The processor is coupled to a memory and is configured to read and execute program instructions stored in the memory, so that the chip implements the method in any one of the possible designs in the above-mentioned first aspect or second aspect.

[0057] For the various aspects and the possible technical effects achieved by each aspect among the above-mentioned third aspect to eighth aspect, please refer to the technical effects that can be achieved by various possible solutions in the above-mentioned first aspect or second aspect, and will not be repeated here. Description of the Drawings

[0058] Figure 1An architecture schematic diagram provided for this application;

[0059] Figure 2 A schematic diagram of a network closed-loop automation process provided for this application;

[0060] Figure 3 A flowchart of a network automation management method provided for this application;

[0061] Figure 4 A flowchart of an example of a network automation management method provided for this application;

[0062] Figure 5 A schematic diagram of the structure of a closed-loop monitoring functional unit provided for this application;

[0063] Figure 6 A schematic diagram of the structure of a closed-loop execution functional unit provided for this application;

[0064] Figure 7 A structural diagram of a closed-loop monitoring functional unit provided for this application;

[0065] Figure 8 A structural diagram of a closed-loop execution functional unit provided for this application. Detailed implementation manners

[0066] The following will further describe this application in detail with reference to the accompanying drawings.

[0067] The embodiments of this application provide a network automation management method and apparatus to implement the monitoring of the network closed-loop automation process, so as to achieve a better network operation and maintenance effect and improve the network operation and maintenance efficiency. Among them, the method and apparatus in this application are based on the same inventive concept. Since the principles of the method and apparatus for solving problems are similar, the implementation of the apparatus and the method can be referred to each other, and the repeated parts will not be described again.

[0068] In the description of this application, terms such as "first" and "second" are only used for the purpose of distinguishing descriptions, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying an order.

[0069] It should be understood that in the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the association relationship of associated objects and indicates that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one (item) of the following" or a similar expression refers to any combination of these items, including any combination of a single item or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can be single or multiple.

[0070] In order to more clearly describe the technical solutions of the embodiments of the present application, the network automation management method and device provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0071] Figure 1 FIG. shows a possible architecture of a system to which the network automation management method provided by the embodiments of the present application is applicable. The architecture of the system includes a business support system (BSS), a cross-domain management function unit (CD-MnF), a domain management function unit (domain-MnF), and multiple network elements, where:

[0072] The BSS is oriented to operator services and can provide functions and services such as billing, settlement, accounting, customer service, business operation, and network monitoring.

[0073] The cross-domain management functional unit, which can also be called the network management function (NMF). The cross-domain management functional unit can provide one or more of the following management functions or management services: network lifecycle management, network deployment, network fault management, network performance management, network configuration management, network assurance, network optimization functions, translation of network intents (intents from communication service providers (Intent-CSP) or intents from communication service consumers (Intent-CSC)), etc.; the network here can include one or more network elements or sub-networks. The network management functional unit can be a network slice management function (NSMF) or a management data analytical function (MDAF) or a self-organization network function (SONF) or an intent-driven management function (Intent driven MnF). It should be noted that in some deployment scenarios, the cross-domain management functional unit can also provide sub-network lifecycle management, sub-network deployment, sub-network fault management, sub-network performance management, sub-network configuration management, sub-network assurance, sub-network optimization functions, translation of sub-network intents (Intent-CSP or Intent-CSC), etc., where the sub-network consists of multiple small sub-networks. For example, if a network slice only contains one network sub-slice network, the cross-domain management functional unit provides management for both the network slice and the network slice sub-network. The cross-domain management functional unit can be called the provider of the above management services, such as the network lifecycle management service provider.

[0074] The said domain management function unit can also be called the sub-network management function unit (network management function, NMF) or the network element management function unit. The domain management function unit can provide one or more of the following management functions or management services: life cycle management of the sub-network or network element, deployment of the sub-network or network element, fault management of the sub-network or network element, performance management of the sub-network or network element, assurance of the sub-network or network element, optimization function of the sub-network or network element, translation of the intent of the sub-network or network element (intent from the network operator, Intent-NOP), etc. Here, the sub-network includes one or more network elements. The sub-network can also include sub-networks, that is, one or more sub-networks form a larger sub-network. The domain management function unit can be called the provider of the above management services, such as the provider of the sub-network life cycle management service. The domain management function unit can be the network slice subnet management function (NSMF), the management data analytical function (MDAF), or the self-organization network function (SONF) or the intent-driven management function unit (Intent driven MnF). Among them, the domain management function unit can be deployed in, but not limited to, the following ways:

[0075] Classified by network type: radio access network (RAN) domain management function unit, core domain management function unit, transport domain management function unit; it can also be that a certain domain network management system can manage two or all of the radio access network, core network, and transport network;

[0076] Divided by administrative region: the domain management function unit of a certain region, such as the domain management function unit of Shanghai, the domain management function unit of Beijing, etc.

[0077] The entities that provide network services for the multiple network elements may include core network elements (for example, access and mobility management function (AMF) network elements, session management function (SMF) network elements, policy control function (PCF) network elements, network data analytic function (NWDAF) network elements, network repository function (NRF), gateways, etc.), access network elements (for example, base stations (such as generated node B (gNB), evolved node B (eNB)), centralized unit-control plane (CUCP), centralized unit (CU), distributed unit (DU), centralized user plane unit (CUUP)). The network elements may also provide one or more of the following management functions or management services: life cycle management of network elements, deployment of network elements, fault management of network elements, performance management of network elements, assurance of network elements, optimization function of network elements, intent translation of network elements, etc. The network elements may be referred to as providers of the above management services, such as providers of network element life cycle management services.

[0078] It should be noted that Figure 1 the names of the network elements or units shown are only for example, and may be referred to by other names in future communications, or the nodes or devices involved in this application in future communications may be replaced by other entities or devices with the same functions, and this application does not make any limitations in this regard. A unified description is made here and will not be repeated later.

[0079] It should be understood that in the service-oriented management architecture, focusing on management services, the above management functions can be described by management service providers or management service consumers:

[0080] When the management service is the management service provided by the above cross-domain management unit, the cross-domain management unit is the management service producer (MnS producer), and the BSS is the management service consumer (MnS consumer);

[0081] When the management service is the management service provided for the above domain management units, the domain management units are management service producers (MnS producers), and the cross-domain management units are management service consumers (MnS consumers).

[0082] When the management service is the management service provided for the above network elements, the network elements are management service producers (MnS producers), and the domain management units are management service consumers (MnS consumers).

[0083] Currently, in the network closed-loop automation process as Figure 2 shown, the entire network closed-loop automation process is completed within the management function. The operation and maintenance personnel cannot obtain the process information of the intended execution, and cannot monitor and control the intended execution process. For example, making network adjustments for a certain network problem will cause other network problems. Before adjusting the network, the operation and maintenance personnel need to manually confirm the execution of the network adjustment to prevent the management function from frequently adjusting the network. Or although some network problems are automatically identified by the management function, the operation and maintenance personnel do not think it needs to be optimized after comprehensive consideration (for example, the management function identifies a weak coverage area, but there are few terminals in this area or the packages subscribed by the terminals are very cheap. According to the business results, the operation and maintenance personnel will not consider optimizing this weak coverage area), and the process information of the intended execution cannot be obtained, and the automation ability of the management system cannot be evaluated. For example, how does the operation and maintenance personnel know whether the management function has performed network optimization and which network problems have been optimized, etc. In this way, in the current network closed-loop automation process, the intended execution process cannot be monitored, and a good network operation and maintenance effect cannot be achieved. Based on this, the present application proposes a network automation management method, which is applied to the network closed-loop automation process, can realize the monitoring of the network closed-loop automation process, thereby achieving a good network operation and maintenance effect and improving the network operation and maintenance efficiency.

[0084] A network automation management method provided by an embodiment of the present application is applied to the network closed-loop automation process and is applicable to the system as Figure 1 shown. Among them, the closed-loop monitoring function unit and the closed-loop execution function unit involved in this method can be one of the following combinations: the closed-loop execution function unit is Figure 1 the cross-domain management function unit shown, and the closed-loop monitoring function unit is Figure 1 the BSS shown; or, the closed-loop execution function unit is Figure 1 the domain management function unit shown, and the closed-loop monitoring function unit isFigure 1 the shown cross-domain management functional unit or BSS; or, the closed-loop execution functional unit is Figure 1 the shown network element, and the closed-loop monitoring functional unit is Figure 1 the shown domain management functional unit, cross-domain management functional unit or BSS. Refer to Figure 3 As shown, the specific process of this method may include:

[0085] Step 301: The closed-loop monitoring functional unit obtains the closed-loop monitoring capability information of the closed-loop scenario, and the closed-loop monitoring capability information is used to characterize the closed-loop monitoring capabilities supported by the closed-loop scenario.

[0086] Specifically, the closed-loop scenario refers to a certain closed-loop task. Exemplarily, the closed-loop scenario may be the scenario of any one of the following closed-loop tasks: closed-loop task in the planning stage, closed-loop task in the deployment stage, closed-loop task in the maintenance stage, or closed-loop task in the optimization stage, etc.

[0087] Among them, the closed-loop task in the planning stage includes at least one of service planning, network planning, and site planning; the closed-loop task in the deployment stage includes at least one of service delivery or deployment, network deployment, and site deployment; the closed-loop task in the maintenance stage includes at least one of service fault recovery, network fault recovery, and site fault recovery; the closed-loop task in the optimization stage includes at least one of service guarantee, network optimization, and site optimization. Specifically, the service guarantee includes service level agreement (SLA) quality guarantee and service traffic model guarantee, etc.; the network optimization includes at least one of coverage optimization, network capacity optimization, and network quality optimization; the site optimization includes physical cell ID (PCI) optimization of the site cell, neighboring cell optimization of the site, mobility robustness optimization (MRO) of the site, mobility load balancing (MLB) of the site, physical random access channel (PRACH) optimization of the site, etc.

[0088] Exemplarily, when the closed-loop scenario is the coverage optimization scenario of network optimization in the closed-loop task of the optimization stage, the closed-loop monitoring capability information is the coverage optimization closed-loop monitoring capability information.

[0089] In an alternative implementation manner, the closed-loop monitoring capability information may include the closed-loop monitoring points supported by the closed-loop scenario; or, the closed-loop monitoring capability information includes the closed-loop monitoring points supported by the closed-loop scenario and the monitoring types corresponding to the closed-loop monitoring points.

[0090] Specifically, the closed-loop monitoring points may include at least one of the following: intent translation monitoring point, perception monitoring point, network analysis monitoring point, decision-making monitoring point, or execution monitoring point. Among them, the intent translation monitoring point is used to indicate the process or result of monitoring the translation of an intent into a management task or policy; the perception monitoring point is used to indicate the process or result of monitoring network perception; the network analysis monitoring point is used to indicate the process or result of monitoring network analysis; the decision-making monitoring point is used to indicate the process or result of monitoring decision-making; the execution monitoring point is used to indicate the result of monitoring execution.

[0091] Specifically, the intent translation monitoring point may further include at least one of the following: intent translation process or result monitoring point, intent satisfaction result monitoring point; among them, the intent translation process or result monitoring point is used to indicate the process or result after the execution of the intent translation function each time in the initial intent translation stage or the intent retranslation stage; the intent satisfaction result monitoring point is used to indicate the process of monitoring the non-satisfaction of the intent, for example, which process or time point needs to be monitored for the non-satisfaction of the intent.

[0092] The perception monitoring point may further include at least one of the following: network information collection process or result monitoring point, network anomaly discovery process or result monitoring point; among them, the network information collection process or result monitoring point is used to indicate the monitoring of the collected network information, and the network information is the original network information or the processed statistical network information; the network anomaly discovery process or result monitoring point is used to indicate the monitoring of network anomaly information. Exemplarily, the original network information may be the original performance data of a cell, etc.; the processed statistical network information may be the statistical network information after primary analysis or calculation, such as the performance data aggregated by area granularity, etc.; the network anomaly information may be network performance degradation, network faults, etc.

[0093] The network analysis monitoring point may further include at least one of the following: network problem discovery monitoring point, network problem analysis monitoring point, network optimization or adjustment plan generation monitoring point; among them, the network problem discovery monitoring point is used to indicate the process or result of monitoring the detection of network problems; the network problem analysis monitoring point is used to indicate the process or result of monitoring the analysis of network problems; the network optimization or adjustment plan generation monitoring point is used to indicate the process or result of monitoring the generated network optimization / adjustment plan.

[0094] The execution monitoring point may further include a network adjustment plan execution result monitoring point, and the network adjustment plan execution result monitoring point is used to indicate the execution result of the network adjustment plan.

[0095] Exemplarily, when the closed-loop scenario is a coverage optimization scenario, the closed-loop monitoring point is a coverage optimization closed-loop monitoring point, where: the intended translation monitoring point is a coverage optimization intended translation monitoring point; the perception monitoring point is a coverage performance detection monitoring point; the network analysis monitoring point includes at least one of a coverage problem detection monitoring point, an abnormal cell identification monitoring point, and a coverage optimization solution recommendation monitoring point; the decision-making monitoring point is a coverage optimization solution determination monitoring point; the execution monitoring point is a coverage optimization solution execution monitoring point; specifically:

[0096] The coverage optimization intended translation monitoring point is used to indicate monitoring the execution result of the coverage optimization intended translation; the coverage performance detection monitoring point is used to indicate monitoring the coverage performance indicators; the coverage problem detection monitoring point is used to indicate monitoring the coverage problems at the cell or area level; the abnormal cell identification monitoring point is used to indicate monitoring abnormal cells; the coverage optimization solution recommendation monitoring point is used to indicate monitoring at least one candidate coverage optimization solution for solving the coverage problem; the coverage optimization solution determination monitoring point is used to indicate monitoring and determining the coverage optimization solution for solving the coverage problem; the coverage optimization solution execution monitoring point is used to indicate monitoring the execution of the coverage optimization solution.

[0097] Specifically, the monitoring type of any closed-loop monitoring point may include, but is not limited to, monitoring or monitoring and controlling. Among them, monitoring and controlling can also be considered as interrupting or suspending.

[0098] Among them, when the monitoring type of a closed-loop monitoring point is monitoring, it indicates that there is no need to interrupt and the closed-loop process continues to execute; that is, it means that the closed-loop monitoring functional unit only senses the information of this closed-loop monitoring point. After the closed-loop execution functional unit sends the monitoring notification of this closed-loop monitoring point, the closed-loop execution functional unit can continue to execute the network closed-loop process without interrupting and waiting for the confirmation information of the closed-loop monitoring functional unit. When the monitoring type of a closed-loop monitoring point is monitoring and controlling, it indicates interrupting the closed-loop process and waiting for confirmation. Among them, the terminal closed-loop process means not continuing to execute the next step in the closed-loop process; that is, it also means that the closed-loop monitoring functional unit not only senses the information of this closed-loop monitoring point but also hopes to control this closed-loop monitoring point. After the closed-loop execution functional unit sends the monitoring notification corresponding to this closed-loop monitoring point, the closed-loop execution functional unit needs to interrupt the closed-loop process and wait for the confirmation information of the closed-loop monitoring functional unit.

[0099] Optionally, the monitoring type of the closed-loop monitoring point can also be before the closed-loop monitoring point and after the closed-loop monitoring point. Before the closed-loop monitoring point means monitoring or monitoring and controlling before the process corresponding to the closed-loop monitoring point; after the closed-loop monitoring point means monitoring and controlling after the process corresponding to the closed-loop monitoring point.

[0100] Exemplarily, generally, the monitoring type of the perception monitoring point is "monitoring". The monitoring type of the intention translation monitoring point can be "monitoring" or "monitoring and control". The monitoring type of the network analysis monitoring point can be "monitoring" or "monitoring and control". The monitoring type of the decision-making monitoring point is "monitoring and control", and the monitoring type of the execution monitoring point is "monitoring".

[0101] For example, taking the closed-loop scenario as Closed-loop Scenario 1, the description information of the closed-loop monitoring capability of Closed-loop Scenario 1 can be as shown in Table 1:

[0102] Table 1

[0103]

[0104] In an alternative embodiment, the closed-loop monitoring function unit obtains the closed-loop monitoring capability information of the closed-loop scenario. The specific method can be: the closed-loop monitoring function unit obtains the closed-loop monitoring capability information from the closed-loop execution function unit; or, the closed-loop monitoring function unit obtains the template information of the closed-loop scenario, and the template information includes the closed-loop monitoring capability information of the closed-loop scenario. Optionally, the template information of the closed-loop scenario can be the template of a certain closed-loop intention.

[0105] Step 302: The closed-loop monitoring function unit determines at least one closed-loop monitoring point of the closed-loop scenario according to the closed-loop monitoring capability information of the closed-loop scenario.

[0106] In an alternative embodiment, the closed-loop monitoring function unit determines at least one closed-loop monitoring point of the closed-loop scenario according to the closed-loop monitoring capability information of the closed-loop scenario. The specific method can be: the closed-loop monitoring function unit determines the at least one closed-loop monitoring point according to the closed-loop monitoring capability information and its own monitoring requirements.

[0107] Step 303: The closed-loop monitoring function unit sends a closed-loop monitoring request to the closed-loop execution function unit. The closed-loop monitoring request includes the information of the closed-loop scenario and the information of the at least one closed-loop monitoring point.

[0108] Specifically, the information of the closed-loop scenario may include at least one of the following: the type of the closed-loop scenario (such as the coverage optimization scenario, etc.), the identifier of the closed-loop scenario (used to uniquely identify a closed-loop scenario), or the goal of the closed-loop scenario (used to identify the execution goal of a closed-loop scenario).

[0109] In an alternative embodiment, the closed-loop monitoring function unit also determines the monitoring type corresponding to the at least one closed-loop monitoring point according to the closed-loop controllability capability information.

[0110] Further optionally, the closed-loop monitoring request may further include the monitoring type corresponding to the at least one closed-loop monitoring point.

[0111] Exemplarily, the closed-loop monitoring request may be at least one of the following: a closed-loop task creation request, a closed-loop task modification request, an intent creation request, an intent modification request, etc.

[0112] In one example, when the closed-loop scenario is a coverage optimization scenario, the closed-loop monitoring request further includes at least one of a coverage optimization intent identifier, a coverage optimization object, or a coverage target. Among them, the coverage optimization object may include any one of a cell, a sub-network, or a region; the coverage target may include at least one of no coverage holes, no over-coverage, no coverage interference, no weak coverage, a weak coverage ratio threshold, an over-coverage ratio threshold, a coverage hole threshold, an up / downlink coverage mismatch cell ratio threshold, a pilot contamination coverage area ratio threshold, an over-coverage cell ratio threshold, and a weak coverage cell ratio threshold. It should be noted that the intent involved in this application may also be a task. Specifically, the coverage optimization intent identifier may also be a coverage optimization task identifier, etc., and it is not limited to the coverage optimization intent identifier here. The same applies to the coverage intent identifier appearing elsewhere in the text, and the coverage optimization intent identifiers involved in the text will not be elaborated one by one.

[0113] Step 304: During the closed-loop operation of the closed-loop scenario, when the closed-loop execution function unit reaches the at least one closed-loop monitoring point, it acquires the monitoring information of the closed-loop monitoring point and sends a monitoring notification to the closed-loop monitoring function unit. The monitoring notification carries the identifier of the closed-loop monitoring point and the monitoring information.

[0114] Among them, the closed-loop execution function unit executes the closed-loop operation process. When it reaches the at least one closed-loop monitoring point, it determines the monitoring information of the at least one closed-loop monitoring point according to the monitoring requirement information of the at least one closed-loop monitoring point (including the closed-loop monitoring point and the monitoring type of the closed-loop monitoring point). The monitoring information of the closed-loop monitoring point is analyzed during the closed-loop operation process.

[0115] Specifically, when the closed-loop execution function unit reaches the intent translation monitoring point, that is, when the closed-loop execution function unit detects that the closed-loop operation process reaches the intent translation monitoring point, that is, after the closed-loop execution function unit determines the corresponding management task or policy according to the intent, it triggers the monitoring notification (intent execution monitoring notification) corresponding to the intent translation monitoring point. Among them, the monitoring information of the monitoring notification may include at least one of a closed-loop scenario identifier (closed-loop task identifier or intent identifier), an intent evaluation result (such as whether the intent can be executed), and an intent translation result (such as the management task or policy output after intent translation).

[0116] When the closed-loop execution functional unit reaches the sensing monitoring point, that is, when the closed-loop execution functional unit detects that the closed-loop operation process reaches the sensing monitoring point, that is, after the closed-loop execution functional unit performs network monitoring (including network information collection and network anomaly discovery) according to the monitoring rules or policies, it triggers the monitoring notification (sensing monitoring notification) corresponding to the sensing monitoring point. Among them, the monitoring information of the monitoring notification may include at least one of the closed-loop scenario identifier and network information; Exemplarily, the network information may be the originally collected network performance information, the network statistical information aggregated from the originally collected network performance information, the information of network anomalies, etc.

[0117] When the closed-loop execution functional unit reaches the network analysis monitoring point, that is, when the closed-loop execution functional unit detects that the closed-loop operation process reaches the network analysis monitoring point, that is, after the closed-loop execution functional unit performs any one of the network analysis processes of detecting or discovering network problems based on network information, analyzing the root cause of the network problems, and generating a network adjustment suggestion plan for solving the network problems, it triggers the monitoring notification (network analysis monitoring notification) corresponding to the network analysis monitoring point. Among them, the monitoring information of the monitoring notification may include at least one of the closed-loop scenario identifier and the analysis result; The analysis result may include network problems, the root cause of the network problems, the proposed solution to the network problems, etc.

[0118] When the closed-loop execution functional unit reaches the decision-making monitoring point, that is, when the closed-loop execution functional unit detects that the closed-loop operation process reaches the decision-making monitoring point, that is, after the closed-loop execution functional unit determines the solution to the network problems, it triggers the monitoring notification (decision-making monitoring notification) corresponding to the decision-making monitoring point. Among them, the monitoring information of the monitoring notification may include at least one of the closed-loop scenario identifier and the determined solution to the network problems;

[0119] When the closed-loop execution functional unit reaches the execution monitoring point, when the closed-loop execution functional unit detects that the closed-loop operation process reaches the execution monitoring point, that is, after the closed-loop execution functional unit executes the solution to the network problems, it triggers the monitoring notification (execution monitoring notification) corresponding to the execution monitoring point. Among them, the monitoring information of the monitoring notification may include at least one of the closed-loop scenario identifier and the execution result of the solution to the network problems (including which network configuration parameters are modified, etc.).

[0120] Specifically, during the above process, the closed-loop monitoring points respectively execute according to their monitoring types: when the monitoring type of a closed-loop monitoring point is monitoring, the closed-loop execution function unit continues to execute the closed-loop process; when the monitoring type of a closed-loop monitoring point is monitoring and control, the closed-loop execution function unit suspends the closed-loop process and waits for a message from the closed-loop monitoring function unit (i.e., subsequent confirmation information).

[0121] In one example, when the closed-loop scenario is a coverage optimization scenario:

[0122] When the closed-loop execution function unit executes to the coverage optimization intent translation monitoring point, the monitoring notification is a coverage intent translation monitoring notification, and the monitoring information of the coverage intent translation monitoring notification includes at least one of an intent identifier, an intent translation result (including whether the coverage optimization intent can be satisfied, the reasons for non-satisfaction, and corresponding coverage optimization strategies (such as performance metric monitoring strategies, coverage problem analysis strategies, etc.)); it should be noted that the intent identifier involved here is not restrictive and can also be a service optimization task or a scenario identifier, etc. The same applies to the intent identifiers appearing elsewhere in the text, and they will not be elaborated one by one in the places involved in the text.

[0123] When the closed-loop execution function unit executes to the coverage performance detection monitoring point, the monitoring notification is a coverage performance detection monitoring notification, and the monitoring information of the coverage performance detection monitoring notification includes at least one of an intent identifier and coverage performance information; the coverage performance information may include coverage performance metrics at the cell or area level, such as reference signal received power (RSRP), uplink and downlink throughput, radio resource control (RRC) establishment success rate, etc.;

[0124] When the closed-loop execution function unit executes to the coverage problem detection monitoring point, the monitoring notification is a coverage problem detection monitoring notification, and the monitoring information of the coverage problem detection monitoring notification includes at least one of an intent identifier and the detected coverage problems; the coverage problems may include coverage problems at the cell or area level, such as weak coverage, coverage holes, over-coverage, uplink and downlink coverage mismatch, etc.;

[0125] When the closed-loop execution function unit executes to the abnormal cell identification monitoring point, the monitoring notification is an abnormal cell identification monitoring notification, and the monitoring information of the abnormal cell identification monitoring notification includes at least one of an intent identifier and a list of abnormal cells; optionally, the monitoring information of the abnormal cell identification monitoring notification may also carry the coverage problems corresponding to the abnormal cells;

[0126] When the closed-loop execution function unit reaches the monitoring point of the coverage optimization plan determination, the monitoring notification generates a monitoring notification for the coverage adjustment plan. The monitoring information of the coverage adjustment plan generation monitoring notification includes an intention identifier and at least one of at least one repair plan; wherein, each repair plan may include a modification plan identifier and a set of coverage scenario information to be modified; a set of coverage scenario information to be modified includes a set of {proposed coverage scenario information (including beam identifier (common beam forming function Id), coverage shape, azimuth, and tilt)} and corresponding {current proposed coverage scenario information (including beam identifier, coverage shape, azimuth, and tilt)}.

[0127] When the closed-loop execution function unit reaches the monitoring point of the coverage optimization plan execution, the monitoring notification is a monitoring notification for the coverage adjustment plan execution. The monitoring information of the coverage adjustment plan execution monitoring notification includes an intention identifier and at least one of the modified configuration information; wherein, the modified configuration information includes a set of {proposed coverage scenario information (including beam identifier, coverage shape, azimuth, and tilt)}.

[0128] In an alternative embodiment, the closed-loop monitoring function unit sends monitoring confirmation information to the closed-loop execution function unit. The monitoring confirmation information includes the identifier of the closed-loop monitoring point and the confirmation result.

[0129] Specifically, the confirmation result may include at least one of the following:

[0130] When the closed-loop monitoring point is the intention translation monitoring point, the closed-loop monitoring function unit confirms the intention translation execution result of the closed-loop execution function unit and instructs the closed-loop execution function unit to continue executing the closed-loop process.

[0131] When the closed-loop monitoring point is the perception monitoring point, the closed-loop monitoring function unit confirms the network anomaly discovered by the closed-loop execution function unit and instructs the closed-loop execution function unit to continue executing the closed-loop process (i.e., analyze the confirmed network anomaly).

[0132] When the closed-loop monitoring point is a network analysis monitoring point, the closed-loop monitoring functional unit confirms one of the following: confirms that the closed-loop execution functional unit detects or discovers a network problem, and instructs the closed-loop execution functional unit to continue executing the closed-loop process (i.e., discovers the confirmed network problem); or, confirms the cause of the network problem analyzed by the closed-loop execution functional unit, and instructs the closed-loop execution functional unit to continue executing the closed-loop process (i.e., generates a network adjustment plan based on the root cause of the network problem); or, confirms the network adjustment plan recommended by the closed-loop execution functional unit, and instructs the closed-loop execution functional unit to continue executing the closed-loop process (i.e., selection and decision-making of the network adjustment plan).

[0133] When the closed-loop monitoring point is a decision-making monitoring point, the closed-loop monitoring functional unit confirms the network adjustment plan selected by the closed-loop execution functional unit, and instructs the closed-loop execution functional unit to continue executing the closed-loop process (i.e., execution of the network adjustment plan).

[0134] When the closed-loop monitoring point is an execution monitoring point, the closed-loop monitoring functional unit confirms the execution result of the network adjustment plan by the closed-loop execution functional unit.

[0135] In one example, when the closed-loop scenario is a coverage optimization scenario:

[0136] When the closed-loop monitoring point is a coverage optimization intent translation monitoring point, the confirmation information is coverage optimization intent translation result confirmation information, and the coverage optimization intent translation result confirmation information is used to instruct the closed-loop execution functional unit to continue executing the coverage optimization closed-loop process; the coverage optimization intent translation result confirmation information carries a coverage intent identifier and an acknowledge (ACK) confirmation.

[0137] When the closed-loop monitoring point is a coverage problem detection monitoring point, the confirmation information is coverage problem confirmation information, and the coverage problem confirmation information is used to instruct the closed-loop execution functional unit to continue executing the coverage optimization closed-loop process to handle the coverage problem; the coverage problem confirmation information carries a coverage intent identifier and an ACK confirmation. Optionally, the coverage problem confirmation information may further include indication information of the coverage problem to be processed, which is used to indicate the coverage problem to be processed.

[0138] When the closed-loop monitoring point is an abnormal cell identification monitoring point, the confirmation information is abnormal cell identification confirmation information, and the abnormal cell identification confirmation information is used to instruct the closed-loop execution functional unit to continue executing the coverage optimization closed-loop process to handle the abnormal cell; the abnormal cell identification confirmation information carries a coverage intent identifier and an ACK confirmation.

[0139] When the closed-loop monitoring point is the monitoring point determined by the coverage optimization solution, the confirmation information is the coverage adjustment solution confirmation information, and the coverage adjustment solution confirmation information is used to instruct the closed-loop execution functional unit to continue to execute the coverage adjustment solution; the coverage adjustment solution confirmation information carries a coverage intention identifier and an ACK confirmation; optionally, the coverage adjustment solution confirmation information may also carry one or more selected coverage adjustment solutions.

[0140] By using the network automation management method provided in the embodiments of the present application, it is possible to monitor the network closed-loop automation process, so as to achieve a better network operation and maintenance effect and improve the network operation and maintenance efficiency. At the same time, it enables the operator to flexibly customize the closed-loop monitoring information according to needs, to a certain extent monitor and control the network closed-loop automation process, prevent the negative impact brought by the network closed-loop automation process on network adjustment, and can evaluate the closed-loop ability of the manufacturer according to the monitoring information.

[0141] It should be noted that in the above embodiments, steps 301 and 302 can be an optional specific implementation manner for the closed-loop monitoring functional unit to determine at least one closed-loop monitoring point of the closed-loop scenario, that is, steps 301 and 302 can be generalized to the closed-loop monitoring functional unit to determine at least one closed-loop monitoring point of the closed-loop scenario, and then the specific implementation manners of steps 301 and 302 are introduced in detail. Specifically, the specific content can be referred to the above description, and will not be elaborated here.

[0142] Based on the above embodiments, the following uses a specific example, such as Figure 4 the example shown, to elaborate on the network automation management method provided in the embodiments of the present application. In this example, taking the closed-loop scenario as the coverage optimization scenario, the closed-loop monitoring functional unit as the cross-domain management unit, and the closed-loop execution functional unit as the domain management unit as an example to illustrate, that is, the domain management unit acts as the closed-loop execution functional unit to execute the closed-loop automation of coverage optimization, and the cross-domain management unit acts as the closed-loop monitoring functional unit to monitor the closed-loop automation of coverage optimization. Specifically, as Figure 4 shown, the specific process of the example of the network automation management method may include:

[0143] Step 401: The cross-domain management unit obtains the coverage optimization closed-loop monitoring capability information sent by the domain management unit, where the coverage optimization closed-loop monitoring capability information includes the coverage optimization closed-loop monitoring points supported by the domain management unit for coverage optimization and the monitoring types corresponding to the coverage optimization closed-loop monitoring points.

[0144] Specifically, the coverage optimization closed-loop monitoring points may include at least one of the following:

[0145] The coverage optimization intent translation monitoring point is used to monitor the execution result of the coverage optimization intent translation, that is, to instruct the domain management functional unit to report the coverage optimization translation intent result (including whether the coverage optimization intent can be satisfied, the reasons for the dissatisfaction of the coverage optimization intent, etc.) after executing the coverage optimization translation intent; the monitoring type of this coverage optimization intent translation monitoring point is monitoring and control; this coverage optimization intent translation monitoring point belongs to Figure 3 the intent translation monitoring point in the embodiment shown.

[0146] The coverage performance detection monitoring point is used to monitor the coverage performance metrics, that is, to instruct the domain management functional unit to report the corresponding coverage performance metrics when detecting the coverage performance metrics at a certain time period, including cell or area-level coverage performance metrics (such as: RSRP, uplink and downlink throughput, RRC establishment success rate, etc.). The monitoring type of this coverage performance detection monitoring point is monitoring; this coverage performance detection monitoring point belongs to Figure 3 the perception monitoring point in the embodiment shown.

[0147] The coverage problem detection monitoring point is used to monitor the coverage problems, that is, to instruct the domain management functional unit to report the corresponding coverage problems when detecting the coverage problems. The coverage problems can include cell or area-level coverage problems (such as: weak coverage, coverage holes, over-coverage, uplink and downlink coverage mismatch, etc.). The type of this coverage problem detection monitoring point is monitoring or monitoring and control; this coverage problem detection monitoring point belongs to Figure 3 the network analysis monitoring point in the embodiment shown.

[0148] The abnormal cell identification monitoring point is used to monitor the abnormal cells (the top N (Top N) abnormal cells causing the coverage problems), that is, to instruct the domain management functional unit to report the abnormal cell list when identifying the top N abnormal cells corresponding to the coverage problems. The type of this abnormal cell identification monitoring point is monitoring or monitoring and control; this abnormal cell identification monitoring point belongs to Figure 3 the network analysis monitoring point in the embodiment shown.

[0149] The coverage optimization solution suggestion monitoring point is used to monitor the possible coverage optimization solutions for solving the coverage problems (that is, the corresponding set of coverage scenario information (including beam (common beam forming function) identification, coverage shape, azimuth angle and tilt angle)), that is, to instruct the domain management functional unit to report the corresponding possible coverage optimization solutions when generating the coverage optimization solutions for the possible coverage problems. Note that there may be multiple coverage optimization solutions here. The type of this coverage optimization solution suggestion monitoring point is monitoring or monitoring and control; this coverage optimization solution suggestion monitoring point belongs to Figure 3 the network analysis monitoring point in the embodiment shown.

[0150] The coverage optimization solution determination monitoring point is used to monitor and determine the coverage optimization solution for solving the coverage problem, that is, when instructing the domain management function unit to determine the coverage optimization solution for solving the coverage problem, report the corresponding coverage optimization solution to be executed; the type of the coverage optimization solution determination monitoring point is monitoring or monitoring and control; the coverage optimization solution determination monitoring point belongs to Figure 3 the decision-making monitoring point in the embodiment shown.

[0151] The coverage optimization solution execution monitoring point is used to monitor the execution of the coverage optimization solution, that is, instruct the domain management function unit to report the corresponding execution result after executing the coverage optimization solution (for example, which coverage shape attributes of the common beam forming function instances have been modified). The type of the coverage optimization solution execution monitoring point is monitoring; the coverage optimization solution execution monitoring point belongs to Figure 3 the execution monitoring point in the embodiment shown.

[0152] It should be noted that the above step 401 belongs to the coverage optimization closed-loop monitoring capability acquisition process, and step 401 is an optional step.

[0153] Step 402: The cross-domain management unit determines the coverage optimization task or intention, and the coverage optimization intention carries information such as a coverage optimization intention identifier, a coverage optimization object, a coverage target, and a coverage optimization closed-loop monitoring point.

[0154] It should be noted that for the sake of simplicity of description, in this example, the coverage optimization intention is used for description. Note that in practice, it can also be a coverage optimization task, and this embodiment does not limit this.

[0155] Specifically, the coverage optimization intention identifier is used to uniquely identify a coverage optimization intention, which is an optional parameter; the coverage optimization object includes any one of a cell, a sub-network, or a region; the coverage target includes at least one of no coverage hole, no over-coverage, no coverage interference, no weak coverage, weak coverage ratio threshold, over-coverage ratio threshold, coverage hole threshold, up / downlink coverage mismatch cell ratio threshold, pilot pollution coverage area ratio threshold, over-coverage cell ratio threshold, and weak coverage cell ratio threshold.

[0156] Specifically, for the information of the coverage optimization closed-loop monitoring point here, refer to the relevant description of the coverage optimization closed-loop monitoring point described in step 401.

[0157] Step 403: The cross-domain management function unit sends the coverage optimization intention (i.e., the closed-loop monitoring request) to the domain management unit, and the coverage optimization intention carries information such as a coverage optimization intention identifier, a coverage optimization object, a coverage target, and a coverage optimization closed-loop monitoring point.

[0158] It should be noted that steps 402 and 403 belong to the process of issuing coverage optimization intentions.

[0159] Step 404: The domain management function unit starts to execute the coverage optimization closed-loop automation process according to the received coverage optimization intention. Specifically:

[0160] Steps 405a to 405c are the intention translation processes executed by the domain management function unit according to the received coverage optimization intention:

[0161] Step 405a: The domain management function unit determines the intention translation result (including whether the coverage optimization intention can be satisfied, the reasons for non-satisfaction, and the corresponding coverage optimization strategies (such as: performance metric monitoring strategy, coverage problem analysis strategy, etc.)); after the domain management function unit completes the coverage optimization intention translation process and detects that the cross-domain management function unit has set a coverage optimization intention translation monitoring point, it triggers a coverage intention translation monitoring notification.

[0162] Step 405b: The domain management function unit sends a coverage intention translation monitoring notification to the cross-domain management function unit. The coverage intention translation monitoring notification carries one or all of the intention identifier and the monitoring point identifier, as well as the intention translation result.

[0163] Step 405c: When the monitoring type of the coverage intention translation monitoring point is monitoring and control, the cross-domain management function unit sends a coverage optimization intention translation result confirmation message to the domain management function unit, instructing the domain management function unit to continue executing the coverage optimization closed-loop process; the coverage optimization intention translation result confirmation message carries the coverage intention identifier and the ACK confirmation.

[0164] Steps 406a to 406b are the coverage performance detection and monitoring processes executed by the domain management function unit:

[0165] Step 406a: The domain management function unit according to the coverage performance detection strategy (for example: collect coverage performance metrics (such as.RSRP) at a certain time period. The coverage performance detection strategy can be output by the coverage intention translation process or pre-set in the domain management function unit); after the domain management function unit completes the coverage performance detection process and detects that the cross-domain management function unit has set a coverage performance detection monitoring point, it triggers a coverage performance detection monitoring notification.

[0166] Step 406b: The domain management function unit sends a coverage performance detection and monitoring notice to the cross-domain management function unit. The coverage performance detection and monitoring notice carries one or both of the intention identifier and the monitoring point identifier, as well as coverage performance information (including cell or area-level coverage performance indicators (such as: RSRP, uplink and downlink throughput, RRC establishment success rate, etc.)).

[0167] Steps 407a to 407c are for the domain management function unit to execute the coverage problem detection and monitoring process:

[0168] Step 407a: The domain management function unit performs coverage problem detection, that is, detects a coverage problem according to the coverage performance information (see the description involved in Step 402 for specific coverage problems). After executing the coverage problem detection and monitoring process and detecting that the cross-domain management function unit has set a coverage problem detection and monitoring point, it triggers a coverage problem detection and monitoring notice.

[0169] Step 407b: The domain management function unit sends a coverage problem detection and monitoring notice to the cross-domain management function unit. The coverage problem detection and monitoring notice carries one or both of the intention identifier and the monitoring point identifier, as well as the detected coverage problem (including cell or area-level coverage problems (such as: weak coverage, coverage holes, over-coverage, uplink and downlink coverage mismatch, etc.)).

[0170] Step 407c: When the monitoring type of the coverage problem detection and monitoring point is monitoring and control, the cross-domain management function unit sends coverage problem confirmation information to the domain management function unit, instructing the domain management function unit to continue to execute the coverage optimization closed-loop process to handle the coverage problem; the coverage problem confirmation information carries a coverage intention identifier and an ACK confirmation. Optionally, the coverage problem confirmation information further includes indication information of the coverage problem to be processed, which is used to indicate the coverage problem that needs to be processed by the domain management function unit.

[0171] Steps 408a to 408c are for the domain management function unit to execute the abnormal cell identification and monitoring process corresponding to the coverage problem, and the main purpose is to identify the list of top N cells that cause the coverage problem:

[0172] Step 408a: The domain management function unit executes the abnormal cell identification and monitoring process, that is, determines the list of main cells that introduce the coverage problem. After executing the abnormal cell identification and monitoring process and detecting that the cross-domain management function unit has set an abnormal cell identification and monitoring point, it triggers an abnormal cell identification and monitoring notice.

[0173] Step 408b: The domain management functional unit sends an abnormal cell identification monitoring notification to the cross-domain management functional unit. The abnormal cell identification monitoring notification carries one or both of an intention identifier and a monitoring point identifier, and a list of abnormal cells; optionally, the abnormal cell identification monitoring notification may also carry the coverage problem corresponding to the abnormal cell.

[0174] Step 408c: When the monitoring type of the abnormal cell identification monitoring point is monitoring and control, the cross-domain management functional unit sends abnormal cell identification confirmation information to the domain management functional unit, instructing the domain management functional unit to continue to execute the coverage optimization closed-loop process to handle the abnormal cell; the abnormal cell identification confirmation information carries a coverage intention identifier and an ACK confirmation.

[0175] Steps 409a to 409c are the monitoring process for the domain management functional unit to execute the coverage adjustment plan generation.

[0176] Step 409a: The domain management functional unit executes the monitoring process for generating a coverage adjustment plan, that is, generates a set of possible repair plans to solve the coverage problem (each repair plan includes a modification plan identifier and a set of coverage scenario information to be modified, including a set of {proposed coverage scenario information (including beam identifier, coverage shape, azimuth angle, and tilt angle)} and the corresponding {currently proposed coverage scenario information (including beam identifier, coverage shape, azimuth angle, and tilt angle)}), and detects that the cross-domain management functional unit has set a monitoring point for generating a coverage adjustment plan, then triggers a coverage adjustment plan generation monitoring notification.

[0177] Step 409b: The domain management functional unit sends a coverage adjustment plan generation monitoring notification to the cross-domain management functional unit. The coverage adjustment plan generation monitoring notification carries one or both of an intention identifier and a monitoring point identifier, and a set of possible repair plans; optionally, the coverage adjustment plan generation monitoring notification may also include the coverage problem corresponding to the repair plan.

[0178] Step 409c: When the monitoring type of the monitoring point for generating a coverage adjustment plan is monitoring and control, the cross-domain management functional unit sends coverage adjustment plan confirmation information to the domain management functional unit, instructing the domain management functional unit to continue to execute the coverage adjustment plan; the coverage adjustment plan confirmation information carries a coverage intention identifier and an ACK confirmation. Optionally, when multiple sets of possible coverage adjustment plans are carried in Step 409a, the coverage adjustment plan confirmation information may also carry one or more selected coverage adjustment plans.

[0179] Steps 410a to 410b are the monitoring process for the domain management functional unit to execute the coverage adjustment plan:

[0180] Step 410a: The domain management functional unit executes the coverage adjustment plan execution monitoring process, that is, executes the confirmed coverage repair plan (configures a set of coverage scenario information, including a set of {recommended coverage scenario information (including beam identifier, coverage shape, azimuth angle, and tilt angle)}), and detects that the cross-domain management functional unit has set a coverage adjustment plan execution monitoring point, then triggers a coverage adjustment plan execution monitoring notification.

[0181] Step 410b: The domain management functional unit sends a coverage adjustment plan execution monitoring notification to the cross-domain management functional unit. The coverage adjustment plan execution monitoring notification carries one or all of the intention identifier and the monitoring point identifier, and the modified configuration information, including a set of {recommended coverage scenario information (including beam identifier, coverage shape, azimuth angle, and tilt angle)}.

[0182] Based on the above example, it is possible to monitor the closed-loop automation process of coverage optimization, so as to achieve a better network operation and maintenance effect and improve the network operation and maintenance efficiency. At the same time, it enables the operator to flexibly customize the coverage optimization closed-loop monitoring information on demand, to a certain extent monitor and control the closed-loop automation process of coverage optimization, prevent the negative impact of the closed-loop automation process of coverage optimization on network adjustment, and can evaluate the coverage optimization closed-loop ability of the manufacturer according to the monitoring information.

[0183] Based on the above embodiments, the embodiments of the present application further provide a closed-loop monitoring functional unit, which is applied to the system as Figure 1 shown, and is used to implement the functions of the closed-loop monitoring functional unit in the network automation management method as Figure 3 shown and the functions of the cross-domain management unit in the embodiments as Figure 4 shown. Referring to Figure 5 shown, the closed-loop monitoring functional unit 500 includes: a processing unit 501 and a communication unit 502, where:

[0184] The processing unit 501 is used to obtain the closed-loop monitoring capability information of the closed-loop scenario, and the closed-loop monitoring capability information is used to characterize the closed-loop monitoring capabilities supported by the closed-loop scenario; and determine at least one closed-loop monitoring point of the closed-loop scenario according to the closed-loop monitoring capability information of the closed-loop scenario; the communication unit 502 is used to send a closed-loop monitoring request to the closed-loop execution functional unit, and the closed-loop monitoring request includes the information of the closed-loop scenario and the information of the at least one closed-loop monitoring point; and receive the monitoring notification corresponding to the at least one closed-loop monitoring point from the closed-loop execution functional unit, and the monitoring notification carries the identifier of the corresponding closed-loop monitoring point and the monitoring information.

[0185] In an alternative embodiment, the closed-loop monitoring capability information includes the closed-loop monitoring points supported by the closed-loop scenario; or, the closed-loop monitoring capability information includes the closed-loop monitoring points supported by the closed-loop scenario and the monitoring types corresponding to the closed-loop monitoring points.

[0186] In a specific embodiment, when determining at least one closed-loop monitoring point of the closed-loop scenario according to the closed-loop monitoring capability information of the closed-loop scenario, the processing unit 501 is specifically configured to: determine the at least one closed-loop monitoring point according to the closed-loop monitoring capability information and its own monitoring requirements.

[0187] Exemplarily, the at least one closed-loop monitoring point may include at least one of the following: an intent translation monitoring point, a perception monitoring point, a network analysis monitoring point, a decision-making monitoring point, or an execution monitoring point; wherein, the intent translation monitoring point is used to indicate the process or result of monitoring the translation of an intent into an administrative task or policy; the perception monitoring point is used to indicate the process or result of monitoring network perception; the network analysis monitoring point is used to indicate the process or result of monitoring network analysis; the decision-making monitoring point is used to indicate the process or result of monitoring a decision; the execution monitoring point is used to indicate the result of monitoring an execution.

[0188] In an alternative embodiment, the processing unit 501 is further configured to determine the monitoring types corresponding to the at least one closed-loop monitoring point according to the closed-loop controllability capability information; the monitoring type of any closed-loop monitoring point is monitoring or monitoring and control; wherein, when the monitoring type of a closed-loop monitoring point is monitoring, it indicates that there is no need to interrupt and the closed-loop process continues to be executed; when the monitoring type of a closed-loop monitoring point is monitoring and control, it indicates that the closed-loop process is interrupted and waiting for confirmation.

[0189] Exemplarily, the closed-loop monitoring request further includes the monitoring types corresponding to the at least one closed-loop monitoring point.

[0190] In an alternative embodiment, the communication unit 502 is further configured to send monitoring confirmation information to the closed-loop execution function unit, where the monitoring confirmation information includes the identifier of the monitoring point and the confirmation result; wherein, the confirmation result includes at least one of the following: when the closed-loop monitoring point is an intent translation monitoring point, the processing unit 501 confirms the intent translation result of the closed-loop execution function unit, and instructs the processing unit 501 to continue executing the closed-loop process; when the closed-loop monitoring point is an intent perception monitoring point, the processing unit 501 confirms the network anomaly discovered by the closed-loop execution function unit, and instructs the closed-loop execution function unit to continue executing the closed-loop process; when the closed-loop monitoring point is a network analysis monitoring point, the processing unit 501 confirms one of the following: confirms that the closed-loop execution function unit detects or discovers a network problem, and instructs the closed-loop execution function unit to continue executing the closed-loop process; or, confirms the cause of the network problem analyzed by the closed-loop execution function unit, and instructs the closed-loop execution function unit to continue executing the closed-loop process; or, confirms the network adjustment plan recommended by the closed-loop execution function unit, and instructs the closed-loop execution function unit to continue executing the closed-loop process; when the closed-loop monitoring point is a decision-making monitoring point, the processing unit 501 confirms the network adjustment plan selected by the closed-loop execution function unit, and instructs the closed-loop execution function unit to continue executing the closed-loop process; when the closed-loop monitoring point is an execution monitoring point, the processing unit 501 confirms the execution result of the network adjustment plan by the closed-loop execution function unit.

[0191] In one example, when the closed-loop scenario is a coverage optimization scenario, the at least one closed-loop monitoring point is at least one coverage optimization closed-loop monitoring point, where: the intent translation monitoring point is a coverage optimization intent translation monitoring point; the perception monitoring point is a coverage performance detection monitoring point; the network analysis monitoring point includes at least one of a coverage problem detection monitoring point, an abnormal cell identification monitoring point, and a coverage optimization plan recommendation monitoring point; the decision-making monitoring point is a coverage optimization plan determination monitoring point; the execution monitoring point is a coverage optimization plan execution monitoring point; the coverage optimization intent translation monitoring point is used to indicate monitoring the execution result of the coverage optimization intent translation; the coverage performance detection monitoring point is used to indicate monitoring the coverage performance index; the coverage problem detection monitoring point is used to indicate monitoring the coverage problem at the cell or area level; the abnormal cell identification monitoring point is used to indicate monitoring the abnormal cell; the coverage optimization plan recommendation monitoring point is used to indicate monitoring at least one candidate coverage optimization plan for solving the coverage problem; the coverage optimization plan determination monitoring point is used to indicate monitoring the determined coverage optimization plan for solving the coverage problem; the coverage optimization plan execution monitoring point is used to indicate monitoring the execution of the coverage optimization plan.

[0192] Exemplarily, when the closed-loop scenario is a coverage optimization scenario, the closed-loop monitoring capability information is coverage optimization closed-loop monitoring capability information.

[0193] In an exemplary embodiment, when the closed-loop scenario is a coverage optimization scenario, and when the closed-loop monitoring point is a monitoring point for translating coverage optimization intent, the confirmation information is the confirmation information for the translation result of coverage optimization intent, and the confirmation information for the translation result of coverage optimization intent is used to instruct the closed-loop execution functional unit to continue executing the coverage optimization closed-loop process; when the closed-loop monitoring point is a monitoring point for detecting coverage problems, the confirmation information is the coverage problem confirmation information, and the coverage problem confirmation information is used to instruct the closed-loop execution functional unit to continue executing the coverage optimization closed-loop process to handle the coverage problem; when the closed-loop monitoring point is a monitoring point for identifying abnormal cells, the confirmation information is the abnormal cell identification confirmation information, and the abnormal cell identification confirmation information is used to instruct the closed-loop execution functional unit to continue executing the coverage optimization closed-loop process to handle the abnormal cell; when the closed-loop monitoring point is a monitoring point for determining a coverage optimization plan, the confirmation information is the confirmation information for the coverage adjustment plan, and the confirmation information for the coverage adjustment plan is used to instruct the closed-loop execution functional unit to continue executing the coverage adjustment plan.

[0194] In a specific embodiment, the closed-loop monitoring functional unit is a cross-domain management unit, and the closed-loop execution functional unit is a domain management unit.

[0195] Based on the above embodiments, the embodiments of the present application further provide a closed-loop execution functional unit, which is applied to the system as shown in Figure 1 and is used to implement the functions of the closed-loop execution functional unit in the network automation management method as shown in Figure 3 and the functions of the domain management unit in the embodiments as shown in Figure 4 . Referring to Figure 6 , the closed-loop execution functional unit 600 includes: a communication unit 601 and a processing unit 602, where:

[0196] The communication unit 601 is configured to receive a closed-loop monitoring request sent by the closed-loop monitoring functional unit, and the closed-loop monitoring request includes information about the closed-loop scenario and information about at least one closed-loop monitoring point; the processing unit 602 is configured to obtain monitoring information of the closed-loop monitoring point when the at least one closed-loop monitoring point is reached during the closed-loop operation of the closed-loop scenario; the communication unit 601 is further configured to send a monitoring notification to the closed-loop monitoring functional unit, and the monitoring notification carries the identifier of the closed-loop monitoring point and the monitoring information.

[0197] In an alternative implementation, the communication unit 601 is further configured to send the closed-loop monitoring capability information of the closed-loop scenario to the closed-loop monitoring function unit, where the closed-loop monitoring capability information is used to characterize the closed-loop monitoring capabilities supported by the closed-loop scenario; wherein, the closed-loop monitoring capability information includes the closed-loop monitoring points supported by the closed-loop scenario; or, the closed-loop monitoring capability information includes the closed-loop monitoring points supported by the closed-loop scenario and the monitoring types corresponding to the closed-loop monitoring points.

[0198] Exemplarily, the at least one closed-loop monitoring point includes at least one of the following: an intent translation monitoring point, a perception monitoring point, a network analysis monitoring point, a decision-making monitoring point, or an execution monitoring point; wherein, the intent translation monitoring point is used to indicate the process or result of monitoring the translation of an intent into a specific management task or policy; the perception monitoring point is used to indicate the process or result of monitoring network perception; the network analysis monitoring point is used to indicate the process or result of monitoring network analysis; the decision-making monitoring point is used to indicate the process or result of monitoring decision-making; the execution monitoring point is used to indicate the result of monitoring execution.

[0199] In an alternative implementation, the closed-loop monitoring request further includes the monitoring types corresponding to the at least one closed-loop monitoring point; the monitoring type of any closed-loop monitoring point is monitoring or monitoring and control; wherein, when the monitoring type of a closed-loop monitoring point is monitoring, it indicates that there is no need to interrupt and the closed-loop process continues to execute; when the monitoring type of a closed-loop monitoring point is monitoring and control, it indicates that the closed-loop process is interrupted and waiting for confirmation.

[0200] In a specific implementation, the communication unit 601 is further configured to receive monitoring confirmation information from the closed-loop monitoring function unit, where the monitoring confirmation information includes a monitoring point identifier and a confirmation result.

[0201] In one example, when the closed-loop scenario is a coverage optimization scenario, the at least one closed-loop monitoring point is at least one coverage optimization closed-loop monitoring point, where: the intended translation monitoring point is a coverage optimization intended translation monitoring point; the perception monitoring point is a coverage performance detection monitoring point; the network analysis monitoring point includes at least one of a coverage problem detection monitoring point, an abnormal cell identification monitoring point, and a coverage optimization solution suggestion monitoring point; the decision-making monitoring point is a coverage optimization solution determination monitoring point; the execution monitoring point is a coverage optimization solution execution monitoring point; the coverage optimization intended translation monitoring point is used to indicate monitoring the execution result of the coverage optimization intended translation; the coverage performance detection monitoring point is used to indicate monitoring the coverage performance metrics; the coverage problem detection monitoring point is used to indicate monitoring the coverage problems at the cell or area level; the abnormal cell identification monitoring point is used to indicate monitoring abnormal cells; the coverage optimization solution suggestion monitoring point is used to indicate monitoring at least one candidate coverage optimization solution for solving the coverage problem; the coverage optimization solution determination monitoring point is used to indicate monitoring the determination of the coverage optimization solution for solving the coverage problem; the coverage optimization solution execution monitoring point is used to indicate monitoring the execution of the coverage optimization solution.

[0202] Specifically, when the monitoring type of a closed-loop monitoring point is monitoring, the processing unit 602 is further configured to continue executing the closed-loop process when reaching the closed-loop monitoring point; when the monitoring type of a closed-loop monitoring point is monitoring and controlling, the processing unit 602 is further configured to suspend the closed-loop process when reaching the closed-loop monitoring point and wait for the confirmation information from the closed-loop monitoring functional unit.

[0203] Exemplarily, when the closed-loop scenario is a coverage optimization scenario, the closed-loop monitoring capability information is coverage optimization closed-loop monitoring capability information.

[0204] In a specific implementation manner, the closed-loop monitoring functional unit is a cross-domain management unit, and the closed-loop execution functional unit is a domain management unit.

[0205] It should be noted that the division of units in the embodiments of the present application is illustrative only, and is only a logical function division. In actual implementation, there may be other division methods. In the embodiments of the present application, each functional unit may be integrated in one processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit. The above integrated units may be implemented in the form of hardware or in the form of software functional units.

[0206] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0207] Based on the above embodiments, the embodiments of this application also provide a closed-loop monitoring functional unit, which is applied to a system as shown in Figure 1 to implement the functions of the closed-loop monitoring functional unit in the network automation management method as shown in Figure 3 and the functions of the cross-domain management unit in the embodiments as shown in Figure 4 . Referring to Figure 7 , the closed-loop monitoring functional unit 700 may include a communication interface 701 and a processor 702. Optionally, the closed-loop monitoring functional unit 700 may further include a memory 703. Among them, the memory 703 may be disposed inside the closed-loop monitoring functional unit 700 or outside the closed-loop monitoring functional unit 700. Among them, the processor 702 may control the communication interface 701 to receive and send information or data.

[0208] Specifically, the processor 702 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor 702 may further include a hardware chip. The above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0209] Among them, the communication interface 701, the processor 702, and the memory 703 are interconnected with each other. Optionally, the communication interface 701, the processor 702, and the memory 703 are interconnected through a bus 704; the bus 704 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of convenience of representation, Figure 7 only a thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.

[0210] In an alternative embodiment, the memory 703 is used to store programs, etc. Specifically, the program may include program code, and the program code includes computer operation instructions. The memory 703 may include a RAM, and may also include a non-volatile memory, such as one or more disk memories. The processor 702 executes the application program stored in the memory 703 to implement the above functions, thereby implementing the functions of the closed-loop monitoring functional unit 700.

[0211] Specifically, the closed-loop monitoring functional unit 700 is used to implement the above Figure 3 or Figure 4 When implementing the functions of the closed-loop monitoring functional unit (such as the cross-domain management unit) in the above-mentioned embodiments, it may specifically include:

[0212] The processor 702 is used to obtain the closed-loop monitoring capability information of the closed-loop scenario, where the closed-loop monitoring capability information is used to characterize the closed-loop monitoring capabilities supported by the closed-loop scenario; and determine at least one closed-loop monitoring point of the closed-loop scenario according to the closed-loop monitoring capability information of the closed-loop scenario; the communication interface 701 is used to send a closed-loop monitoring request to the closed-loop execution functional unit, where the closed-loop monitoring request includes the information of the closed-loop scenario and the information of the at least one closed-loop monitoring point; and receive the monitoring notifications corresponding to the at least one closed-loop monitoring point from the closed-loop execution functional unit, where the monitoring notifications carry the identifiers and monitoring information of the corresponding closed-loop monitoring points.

[0213] In an alternative embodiment, the closed-loop monitoring capability information includes the closed-loop monitoring points supported by the closed-loop scenario; or, the closed-loop monitoring capability information includes the closed-loop monitoring points supported by the closed-loop scenario and the monitoring types corresponding to the closed-loop monitoring points.

[0214] In a specific embodiment, when the processor 702 determines at least one closed-loop monitoring point of the closed-loop scenario according to the closed-loop monitoring capability information of the closed-loop scenario, it is specifically configured to: determine the at least one closed-loop monitoring point according to the closed-loop monitoring capability information and its own monitoring requirements.

[0215] Exemplarily, the at least one closed-loop monitoring point may include at least one of the following: an intent translation monitoring point, a perception monitoring point, a network analysis monitoring point, a decision-making monitoring point, or an execution monitoring point; where the intent translation monitoring point is used to indicate the process or result of monitoring the translation of an intent into an administrative task or policy; the perception monitoring point is used to indicate the process or result of monitoring network perception; the network analysis monitoring point is used to indicate the process or result of monitoring network analysis; the decision-making monitoring point is used to indicate the process or result of monitoring decision-making; the execution monitoring point is used to indicate the result of monitoring execution.

[0216] In an alternative embodiment, the processor 702 is further used to determine the monitoring types corresponding to the at least one closed-loop monitoring point according to the closed-loop controllability capability information; the monitoring type of any closed-loop monitoring point is monitoring or monitoring and control; where when the monitoring type of a closed-loop monitoring point is monitoring, it indicates that there is no need to interrupt and the closed-loop process continues to execute; when the monitoring type of a closed-loop monitoring point is monitoring and control, it indicates that the closed-loop process is interrupted and waiting for confirmation.

[0217] Exemplarily, the closed-loop monitoring request further includes the monitoring types corresponding to the at least one closed-loop monitoring point.

[0218] In an alternative embodiment, the communication interface 701 is further configured to send monitoring confirmation information to the closed-loop execution functional unit, where the monitoring confirmation information includes the identifier of the monitoring point and the confirmation result; wherein, the confirmation result includes at least one of the following: when the closed-loop monitoring point is an intended translation monitoring point, the processor 702 confirms the intended translation result of the closed-loop execution functional unit, and instructs the processor 702 to continue executing the closed-loop process; when the closed-loop monitoring point is an intended perception monitoring point, the processor 702 confirms the network anomaly discovered by the closed-loop execution functional unit, and instructs the closed-loop execution functional unit to continue executing the closed-loop process; when the closed-loop monitoring point is a network analysis monitoring point, the processor 702 confirms one of the following: confirms that the closed-loop execution functional unit detects or discovers a network problem, and instructs the closed-loop execution functional unit to continue executing the closed-loop process; or, confirms the cause of the network problem analyzed by the closed-loop execution functional unit, and instructs the closed-loop execution functional unit to continue executing the closed-loop process; or, confirms the network adjustment plan recommended by the closed-loop execution functional unit, and instructs the closed-loop execution functional unit to continue executing the closed-loop process; when the closed-loop monitoring point is a decision-making monitoring point, the processor 702 confirms the network adjustment plan selected by the closed-loop execution functional unit, and instructs the closed-loop execution functional unit to continue executing the closed-loop process; when the closed-loop monitoring point is an execution monitoring point, the processor 702 confirms the execution result of the network adjustment plan by the closed-loop execution functional unit.

[0219] In one example, when the closed-loop scenario is a coverage optimization scenario, the at least one closed-loop monitoring point is at least one coverage optimization closed-loop monitoring point, where: the intended translation monitoring point is a coverage optimization intended translation monitoring point; the perception monitoring point is a coverage performance detection monitoring point; the network analysis monitoring point includes at least one of a coverage problem detection monitoring point, an abnormal cell identification monitoring point, and a coverage optimization plan recommendation monitoring point; the decision-making monitoring point is a coverage optimization plan determination monitoring point; the execution monitoring point is a coverage optimization plan execution monitoring point; the coverage optimization intended translation monitoring point is used to indicate monitoring the execution result of the coverage optimization intended translation; the coverage performance detection monitoring point is used to indicate monitoring the coverage performance index; the coverage problem detection monitoring point is used to indicate monitoring the coverage problem at the cell or area level; the abnormal cell identification monitoring point is used to indicate monitoring the abnormal cell; the coverage optimization plan recommendation monitoring point is used to indicate monitoring at least one candidate coverage optimization plan for solving the coverage problem; the coverage optimization plan determination monitoring point is used to indicate monitoring the coverage optimization plan for solving the coverage problem; the coverage optimization plan execution monitoring point is used to indicate monitoring the execution of the coverage optimization plan.

[0220] Exemplarily, when the closed-loop scenario is a coverage optimization scenario, the closed-loop monitoring capability information is coverage optimization closed-loop monitoring capability information.

[0221] In an exemplary embodiment, when the closed-loop scenario is a coverage optimization scenario, and when the closed-loop monitoring point is a coverage optimization intention translation monitoring point, the confirmation information is a coverage optimization intention translation result confirmation information, and the coverage optimization intention translation result confirmation information is used to instruct the closed-loop execution functional unit to continue executing the coverage optimization closed-loop process; when the closed-loop monitoring point is a coverage problem detection monitoring point, the confirmation information is a coverage problem confirmation information, and the coverage problem confirmation information is used to instruct the closed-loop execution functional unit to continue executing the coverage optimization closed-loop process to handle the coverage problem; when the closed-loop monitoring point is an abnormal cell identification monitoring point, the confirmation information is an abnormal cell identification confirmation information, and the abnormal cell identification confirmation information is used to instruct the closed-loop execution functional unit to continue executing the coverage optimization closed-loop process to handle the abnormal cell; when the closed-loop monitoring point is a coverage optimization scheme determination monitoring point, the confirmation information is a coverage adjustment scheme confirmation information, and the coverage adjustment scheme confirmation information is used to instruct the closed-loop execution functional unit to continue executing the coverage adjustment scheme.

[0222] In a specific embodiment, the closed-loop monitoring functional unit is a cross-domain management unit, and the closed-loop execution functional unit is a domain management unit.

[0223] Based on the above embodiments, the embodiments of the present application further provide a closed-loop execution functional unit, which is applied to the system as shown in Figure 1 and is used to implement the functions of the closed-loop execution functional unit in the network automation management method as shown in Figure 3 and the functions of the domain management unit in the embodiments as shown in Figure 4 . Referring to Figure 8 as shown, the closed-loop execution functional unit 800 may include a communication interface 801 and a processor 802. Optionally, the closed-loop execution functional unit 800 may further include a memory 803. Among them, the memory 803 may be disposed inside the closed-loop execution functional unit 800, or may be disposed outside the closed-loop execution functional unit 800. Among them, the processor 802 may control the communication interface 801 to receive and send information or data.

[0224] Specifically, the processor 802 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor 802 may further include a hardware chip. The above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0225] Among them, the communication interface 801, the processor 802, and the memory 803 are interconnected with each other. Optionally, the communication interface 801, the processor 802, and the memory 803 are interconnected through a bus 804; the bus 804 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, Figure 8 only a thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.

[0226] In an alternative embodiment, the memory 803 is used to store programs, etc. Specifically, the program may include program code, and the program code includes computer operation instructions. The memory 803 may include a RAM, and may also include a non-volatile memory, such as one or more disk memories. The processor 802 executes the application program stored in the memory 803 to implement the above functions, thereby implementing the functions of the closed-loop execution functional unit 800.

[0227] Specifically, the closed-loop execution functional unit 800 is used to implement the above Figure 3 or Figure 4 When implementing the functions of the closed-loop execution functional unit (such as the domain management unit) in the above-mentioned embodiments, it may specifically include:

[0228] The communication interface 801 is used to receive a closed-loop monitoring request sent by a closed-loop monitoring functional unit. The closed-loop monitoring request includes information about a closed-loop scenario and information about at least one closed-loop monitoring point. The processor 802 is used to obtain monitoring information of a closed-loop monitoring point when the at least one closed-loop monitoring point is executed during the closed-loop operation of the closed-loop scenario. The communication interface 801 is further used to send a monitoring notification to the closed-loop monitoring functional unit. The closed-loop monitoring notification carries an identifier of the closed-loop monitoring point and the monitoring information.

[0229] In an optional implementation manner, the communication interface 801 is further used to send closed-loop monitoring capability information of the closed-loop scenario to the closed-loop monitoring functional unit. The closed-loop monitoring capability information is used to characterize the closed-loop monitoring capabilities supported by the closed-loop scenario. Wherein, the closed-loop monitoring capability information includes the closed-loop monitoring points supported by the closed-loop scenario; or, the closed-loop monitoring capability information includes the closed-loop monitoring points supported by the closed-loop scenario and the monitoring types corresponding to the closed-loop monitoring points.

[0230] Exemplarily, the at least one closed-loop monitoring point includes at least one of the following: an intent translation monitoring point, a perception monitoring point, a network analysis monitoring point, a decision-making monitoring point, or an execution monitoring point. Wherein, the intent translation monitoring point is used to indicate the process or result of monitoring the translation of an intent into a specific management task or policy. The perception monitoring point is used to indicate the process or result of monitoring network perception. The network analysis monitoring point is used to indicate the process or result of monitoring network analysis. The decision-making monitoring point is used to indicate the process or result of monitoring decision-making. The execution monitoring point is used to indicate the result of monitoring execution.

[0231] In an optional implementation manner, the closed-loop monitoring request further includes the monitoring types corresponding to the at least one closed-loop monitoring point. The monitoring type of any closed-loop monitoring point is monitoring or monitoring and control. Wherein, when the monitoring type of a closed-loop monitoring point is monitoring, it indicates that there is no need to interrupt and the closed-loop process continues to execute. When the monitoring type of a closed-loop monitoring point is monitoring and control, it indicates that the closed-loop process is interrupted and waiting for confirmation.

[0232] In a specific implementation manner, the communication interface 801 is further used to receive monitoring confirmation information from the closed-loop monitoring functional unit. The monitoring confirmation information includes a monitoring point identifier and a confirmation result.

[0233] In one example, when the closed-loop scenario is a coverage optimization scenario, the at least one closed-loop monitoring point is at least one coverage optimization closed-loop monitoring point, where: the intent translation monitoring point is a coverage optimization intent translation monitoring point; the perception monitoring point is a coverage performance detection monitoring point; the network analysis monitoring point includes at least one of a coverage problem detection monitoring point, an abnormal cell identification monitoring point, and a coverage optimization solution recommendation monitoring point; the decision-making monitoring point is a coverage optimization solution determination monitoring point; the execution monitoring point is a coverage optimization solution execution monitoring point; the coverage optimization intent translation monitoring point is used to indicate monitoring the execution result of the coverage optimization intent translation; the coverage performance detection monitoring point is used to indicate monitoring the coverage performance metrics; the coverage problem detection monitoring point is used to indicate monitoring the coverage problems at the cell or area level; the abnormal cell identification monitoring point is used to indicate monitoring abnormal cells; the coverage optimization solution recommendation monitoring point is used to indicate monitoring at least one candidate coverage optimization solution for solving the coverage problem; the coverage optimization solution determination monitoring point is used to indicate monitoring and determining the coverage optimization solution for solving the coverage problem; the coverage optimization solution execution monitoring point is used to indicate monitoring the execution of the coverage optimization solution.

[0234] Specifically, when the monitoring type of a closed-loop monitoring point is monitoring, the processor 802 is further configured to continue executing the closed-loop process when reaching the closed-loop monitoring point; when the monitoring type of a closed-loop monitoring point is monitoring and controlling, the processor 802 is further configured to suspend the closed-loop process when reaching the closed-loop monitoring point and wait for the confirmation information from the closed-loop monitoring functional unit.

[0235] Exemplarily, when the closed-loop scenario is a coverage optimization scenario, the closed-loop monitoring capability information is coverage optimization closed-loop monitoring capability information.

[0236] In a specific implementation manner, the closed-loop monitoring functional unit is a cross-domain management unit, and the closed-loop execution functional unit is a domain management unit.

[0237] Based on the above embodiments, an embodiment of the present application provides a system, which may include the closed-loop monitoring functional unit and the closed-loop execution functional unit involved in the above embodiments, etc.

[0238] An embodiment of the present application further provides a computer-readable storage medium, which is used to store a computer program. When the computer program is executed by a computer, the computer can implement any network automation management method provided in the above method embodiments.

[0239] An embodiment of the present application further provides a computer program product, which is used to store a computer program. When the computer program is executed by a computer, the computer can implement any network automation management method provided in the above method embodiments.

[0240] An embodiment of the present application further provides a chip, including a processor and a communication interface. The processor is coupled to a memory and is configured to call a program in the memory to enable the chip to implement any of the network automation management methods provided in the above method embodiments.

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

[0242] The present application is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, as well as the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate a device for implementing the functions specified in Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0243] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including an instruction device that implements the functions specified in Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0244] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are performed on the computer or other programmable device to generate a computer-implemented process. Thus, the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0245] Obviously, those skilled in the art can make various changes and modifications to this application without departing from the scope of protection of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, this application is also intended to cover these modifications and variations.

Claims

1. A network automation management method is applied to the network closed-loop automation process. Characterized in that: It includes: The closed-loop monitoring function unit obtains the closed-loop monitoring capability information of the closed-loop scenario, and the closed-loop monitoring capability information is used to characterize the closed-loop monitoring capabilities supported by the closed-loop scenario; The closed-loop monitoring function unit determines at least one closed-loop monitoring point of the closed-loop scenario according to the closed-loop monitoring capability information of the closed-loop scenario; The closed-loop monitoring function unit sends the information of the closed-loop scenario and the information of the at least one closed-loop monitoring point to the closed-loop execution function unit; The closed-loop monitoring function unit receives the monitoring information corresponding to the at least one closed-loop monitoring point from the closed-loop execution function unit.

2. The method according to claim 1, Characterized in that: The method further includes: The closed-loop monitoring capability information includes the closed-loop monitoring points supported by the closed-loop scenario; or The closed-loop monitoring capability information includes the closed-loop monitoring points supported by the closed-loop scenario and the monitoring types corresponding to the closed-loop monitoring points.

3. The method according to claim 1 or 2, Characterized in that: The closed-loop monitoring function unit determines at least one closed-loop monitoring point of the closed-loop scenario according to the closed-loop monitoring capability information of the closed-loop scenario, including: The closed-loop monitoring function unit determines the at least one closed-loop monitoring point according to the closed-loop monitoring capability information and its own monitoring requirements.

4. The method according to any one of claims 1-2, Characterized in that: The at least one closed-loop monitoring point includes at least one of the following: intent translation monitoring point, perception monitoring point, network analysis monitoring point, decision-making monitoring point or execution monitoring point; Wherein, the intent translation monitoring point is used to indicate the process or result of monitoring the translation of intent into management tasks or policies; the perception monitoring point is used to indicate the process or result of monitoring network perception; the network analysis monitoring point is used to indicate the process or result of monitoring network analysis; the decision-making monitoring point is used to indicate the process or result of monitoring decision-making; the execution monitoring point is used to indicate the result of monitoring execution.

5. The method according to any one of claims 1-2, Characterized in that: The method further includes: The closed-loop monitoring function unit determines the monitoring types corresponding to the at least one closed-loop monitoring point according to the closed-loop monitoring capability information; the monitoring type of any one closed-loop monitoring point is monitoring or monitoring and control; Wherein, when the monitoring type of a closed-loop monitoring point is monitoring, it indicates that there is no need to interrupt and the closed-loop process continues to execute; when the monitoring type of a closed-loop monitoring point is monitoring and control, it indicates that the closed-loop process is interrupted and waiting for confirmation.

6. The method according to claim 5, Characterized in that: The information of the closed-loop scenario and the information of the at least one closed-loop monitoring point are carried in the closed-loop monitoring request sent by the closed-loop monitoring function unit to the closed-loop execution function unit, and the closed-loop monitoring request also includes the monitoring types corresponding to the at least one closed-loop monitoring point.

7. The method according to any one of claims 1-2, Characterized in that: The monitoring information is carried in the monitoring notification corresponding to at least one closed-loop monitoring point sent by the closed-loop execution function unit to the closed-loop monitoring function unit, and the monitoring notification also carries the identifier of the corresponding closed-loop monitoring point; the method further includes: The closed-loop monitoring function unit sends monitoring confirmation information to the closed-loop execution function unit, and the monitoring confirmation information includes the identifier of the closed-loop monitoring point and the confirmation result; Wherein, the confirmation result includes at least one of the following: When the closed-loop monitoring point is an intent translation monitoring point, the closed-loop monitoring function unit confirms the intent translation result of the closed-loop execution function unit and instructs the closed-loop execution function unit to continue executing the closed-loop process; When the closed-loop monitoring point is an intent perception monitoring point, the closed-loop monitoring function unit confirms the network anomaly detected by the closed-loop execution function unit and instructs the closed-loop execution function unit to continue executing the closed-loop process; When the closed-loop monitoring point is a network analysis monitoring point, the closed-loop monitoring function unit confirms one of the following: confirms that the closed-loop execution function unit detects or discovers a network problem and instructs the closed-loop execution function unit to continue executing the closed-loop process; or, confirms the cause of the network problem analyzed by the closed-loop execution function unit and instructs the closed-loop execution function unit to continue executing the closed-loop process; or, confirms the network adjustment plan recommended by the closed-loop execution function unit and instructs the closed-loop execution function unit to continue executing the closed-loop process; When the closed-loop monitoring point is a decision-making monitoring point, the closed-loop monitoring function unit confirms the network adjustment plan selected by the closed-loop execution function unit and instructs the closed-loop execution function unit to continue executing the closed-loop process; When the closed-loop monitoring point is an execution monitoring point, the closed-loop monitoring function unit confirms the execution result of the network adjustment plan by the closed-loop execution function unit.

8. The method according to claim 4, characterized in that when the closed-loop scenario is a coverage optimization scenario, the at least one closed-loop monitoring point is at least one coverage optimization closed-loop monitoring point, wherein: The intent translation monitoring point is a coverage optimization intent translation monitoring point; the perception monitoring point is a coverage performance detection monitoring point; the network analysis monitoring point includes at least one of a coverage problem detection monitoring point, an abnormal cell identification monitoring point, and a coverage optimization plan recommendation monitoring point; the decision-making monitoring point is a coverage optimization plan determination monitoring point; the execution monitoring point is a coverage optimization plan execution monitoring point; The coverage optimization intent translation monitoring point is used to indicate monitoring the execution result of the coverage optimization intent translation; The coverage performance detection monitoring point is used to indicate monitoring the coverage performance index; The coverage problem detection monitoring point is used to indicate monitoring the coverage problem at the cell or area level; The abnormal cell identification monitoring point is used to indicate monitoring abnormal cells; The coverage optimization plan recommendation monitoring point is used to indicate monitoring at least one candidate coverage optimization plan for solving the coverage problem; The coverage optimization plan determination monitoring point is used to indicate monitoring the determined coverage optimization plan for solving the coverage problem; The coverage optimization plan execution monitoring point is used to indicate monitoring the execution of the coverage optimization plan.

9. The method according to any one of claims 1-2, characterized in that when the closed-loop scenario is a coverage optimization scenario, the closed-loop monitoring capability information is coverage optimization closed-loop monitoring capability information.

10. The method according to claim 7, characterized in that when the closed-loop scenario is a coverage optimization scenario, when the closed-loop monitoring point is a coverage optimization intent translation monitoring point, the confirmation information is coverage optimization intent translation result confirmation information, and the coverage optimization intent translation result confirmation information is used to instruct the closed-loop execution functional unit to continue to execute the coverage optimization closed-loop process; when the closed-loop monitoring point is a coverage problem detection monitoring point, the confirmation information is coverage problem confirmation information, and the coverage problem confirmation information is used to instruct the closed-loop execution functional unit to continue to execute the coverage optimization closed-loop process to handle the coverage problem; when the closed-loop monitoring point is an abnormal cell identification monitoring point, the confirmation information is abnormal cell identification confirmation information, and the abnormal cell identification confirmation information is used to instruct the closed-loop execution functional unit to continue to execute the coverage optimization closed-loop process to handle the abnormal cell; when the closed-loop monitoring point is a coverage optimization plan determination monitoring point, the confirmation information is coverage adjustment plan confirmation information, and the coverage adjustment plan confirmation information is used to instruct the closed-loop execution functional unit to continue to execute the coverage adjustment plan.

11. The method according to any one of claims 1-2, characterized in that the closed-loop monitoring functional unit is a cross-domain management unit, and the closed-loop execution functional unit is a domain management unit.

12. A network automation management method applied to a network closed-loop automation process, characterized in that comprising: The closed-loop execution functional unit receives the information of the closed-loop scenario and the information of at least one closed-loop monitoring point sent by the closed-loop monitoring functional unit; During the closed-loop operation of the closed-loop scenario, when the closed-loop execution functional unit reaches the at least one closed-loop monitoring point, it acquires the monitoring information of the closed-loop monitoring point and sends the monitoring information to the closed-loop monitoring functional unit.

13. The method according to claim 12, characterized in that the method further comprises: The closed-loop execution functional unit sends the closed-loop monitoring capability information of the closed-loop scenario to the closed-loop monitoring functional unit, and the closed-loop monitoring capability information is used to characterize the closed-loop monitoring capabilities supported by the closed-loop scenario; wherein, the closed-loop monitoring capability information includes the closed-loop monitoring points supported by the closed-loop scenario; or, the closed-loop monitoring capability information includes the closed-loop monitoring points supported by the closed-loop scenario and the monitoring types corresponding to the closed-loop monitoring points.

14. The method according to any one of claims 12-13, characterized in that the at least one closed-loop monitoring point includes at least one of the following: intent translation monitoring point, perception monitoring point, network analysis monitoring point, decision-making monitoring point or execution monitoring point; Among them, the intention translation monitoring point is used to indicate the process or result of monitoring the translation of an intention into a specific management task or policy; the perception monitoring point is used to indicate the process or result of monitoring network perception; the network analysis monitoring point is used to indicate the process or result of monitoring network analysis; the decision-making monitoring point is used to indicate the process or result of monitoring decision-making; the execution monitoring point is used to indicate the result of monitoring execution.

15. The method according to any one of claims 12-13, characterized in that the information of the closed-loop scenario and the information of the at least one closed-loop monitoring point are carried in a closed-loop monitoring request received by the closed-loop execution function unit from the closed-loop monitoring function unit, and the closed-loop monitoring request further includes the monitoring type corresponding to the at least one closed-loop monitoring point; the monitoring type of any closed-loop monitoring point is monitoring or monitoring and controlling; wherein, when the monitoring type of a closed-loop monitoring point is monitoring, it indicates that there is no need to interrupt and the closed-loop process continues to be executed; when the monitoring type of a closed-loop monitoring point is monitoring and controlling, it indicates that the closed-loop process is interrupted and waiting for confirmation.

16. The method according to any one of claims 12-13, characterized in that the monitoring information is carried in the monitoring notification corresponding to the at least one closed-loop monitoring point received by the closed-loop monitoring function unit from the closed-loop execution function unit, and the monitoring notification also carries the identifier of the corresponding closed-loop monitoring point; the method further includes: the closed-loop execution unit receives monitoring confirmation information from the closed-loop monitoring function unit, and the monitoring confirmation information includes the identifier of the closed-loop monitoring point and the confirmation result.

17. The method according to claim 14, characterized in that when the closed-loop scenario is a coverage optimization scenario, the at least one closed-loop monitoring point is at least one coverage optimization closed-loop monitoring point, wherein: the intention translation monitoring point is a coverage optimization intention translation monitoring point; the perception monitoring point is a coverage performance detection monitoring point; the network analysis monitoring point includes at least one of a coverage problem detection monitoring point, an abnormal cell identification monitoring point, and a coverage optimization solution suggestion monitoring point; the decision-making monitoring point is a coverage optimization solution determination monitoring point; the execution monitoring point is a coverage optimization solution execution monitoring point; the coverage optimization intention translation monitoring point is used to indicate the monitoring of the execution result of the coverage optimization intention translation; the coverage performance detection monitoring point is used to indicate the monitoring of coverage performance indicators; the coverage problem detection monitoring point is used to indicate the monitoring of coverage problems at the cell or area level; the abnormal cell identification monitoring point is used to indicate the monitoring of abnormal cells; the coverage optimization solution suggestion monitoring point is used to indicate the monitoring of at least one candidate coverage optimization solution for solving coverage problems; the coverage optimization solution determination monitoring point is used to indicate the monitoring of determining a coverage optimization solution for solving coverage problems; the coverage optimization solution execution monitoring point is used to indicate the monitoring of the execution of the coverage optimization solution.

18. The method according to claim 15, characterized in that the method further includes: when the monitoring type of a closed-loop monitoring point is monitoring, the closed-loop execution function unit continues to execute the closed-loop process when it reaches the closed-loop monitoring point; When the monitoring type of a closed-loop monitoring point is monitoring and control, the closed-loop execution function unit suspends the closed-loop process when it reaches the closed-loop monitoring point and waits for the confirmation information from the closed-loop monitoring function unit.

19. The method according to claim 13, wherein, when the closed-loop scenario is a coverage optimization scenario, the closed-loop monitoring capability information is coverage optimization closed-loop monitoring capability information.

20. The method according to any one of claims 12-13, wherein, the closed-loop monitoring function unit is a cross-domain management unit, and the closed-loop execution function unit is a domain management unit.

21. A closed-loop monitoring function unit, wherein, it includes a unit or module for executing the method according to any one of claims 1-11.

22. A closed-loop execution function unit, wherein, it includes a unit or module for executing the method according to any one of claims 12-20.

23. A closed-loop monitoring function unit, wherein, it includes a processor and a communication interface, wherein: the communication interface is used for receiving and transmitting data or information; the processor is coupled to a memory and is used for calling a program in the memory to make the closed-loop monitoring function unit execute the method according to any one of claims 1-11.

24. A closed-loop execution function unit, wherein, it includes a processor and a communication interface, wherein: the communication interface is used for receiving and transmitting data or information; the processor is coupled to a memory and is used for calling a program in the memory to make the closed-loop execution function unit execute the method according to any one of claims 12-20.

25. A computer-readable storage medium, wherein, it includes instructions that, when running on a computer, cause the computer to execute the method according to any one of claims 1-11, or when running on a computer, cause the computer to execute the method according to any one of claims 12-20.

26. A communication system, wherein, it includes the closed-loop monitoring function unit according to claim 21 and the closed-loop execution function unit according to claim 22.

27. A computer program product, wherein, it includes instructions that, when running on a communication device, cause the communication device to execute the method according to any one of claims 1-11, or execute the method according to any one of claims 12-20.

Images