CN115336311A

CN115336311A - Network automation management method and device

Info

Publication number: CN115336311A
Application number: CN202180025160.XA
Authority: CN
Inventors: 许瑞岳
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-04-08
Filing date: 2021-04-02
Publication date: 2022-11-11
Also published as: WO2021204075A1

Abstract

A network automation management method and device are used for monitoring a network closed-loop automation process, so that a better network operation and maintenance effect is achieved, and the network operation and maintenance efficiency is improved. The method comprises the following steps: the closed-loop monitoring function unit acquires closed-loop monitoring capability information of a closed-loop scene, and determines at least one closed-loop monitoring point of the closed-loop scene according to the closed-loop monitoring capability information of the closed-loop scene; the closed-loop monitoring capability information represents the closed-loop monitoring capability supported by the closed-loop scene; the closed-loop monitoring function unit sends a closed-loop monitoring request to the closed-loop execution function unit, wherein the closed-loop monitoring request comprises information of a closed-loop scene and information of at least one closed-loop monitoring point; in the closed-loop operation process of the closed-loop scene, the closed-loop execution functional unit acquires the monitoring information of the closed-loop monitoring point when executing to at least one closed-loop monitoring point, and sends a monitoring notice to the closed-loop monitoring functional unit, wherein the closed-loop monitoring notice carries the identification and the monitoring information of the closed-loop monitoring point. Therefore, the network operation and maintenance effect is good, and the network operation and maintenance efficiency is high.

Description

[ correcting 15.04.2021 according to rule 91 ] network automation management method and device

Cross Reference to Related Applications

[ 15.04.2021 corrected by rules 91 ] this application claims priority of the chinese patent application having application number 202010277762.1, filed on 04/08 of 2020, the entire contents of which are incorporated herein by reference.

Technical Field

[ correct 15.04.2021 according to rules 91 ] the present application relates to the field of communications technologies, and in particular, to a method and an apparatus for network automation management in a network closed-loop automation scenario.

Background

With the development of communication technology, the requirements on key performance indexes such as time delay, speed, connection scale and the like of a network are continuously improved, the application industry is more and more abundant and diversified, and the performance guarantee and flexibility of services are fundamentally changed, so that the difficulty in operation and maintenance of the network is increased.

The application of automation technology in mobile communication networks is becoming an important focus of attention and research focus of the industry. The industry is expected to help solve the current operational efficiency and capacity problems encountered in mobile communication networks by introducing automation technologies (such as artificial intelligence, machine learning, big data analysis, etc.).

In order to improve the efficiency of network operation and maintenance, a device manufacturer introduces corresponding automation technology in the life cycle process (including four stages of planning, deployment, maintenance and optimization) of a network (including one or more network devices), and gradually realizes full-flow closed-loop automation from mapping, perception, analysis and decision making to execution of the intention requirement. For example, the specific process may be: the method comprises the following steps that operation and maintenance personnel issue an intention to management function equipment (such as an equipment manager management system), the management function equipment gradually executes intention translation (translates the intention into a network management task or strategy), network perception (collects corresponding network data), analysis (analyzes network performance according to the collected network data, identifies network problems and generates a network optimization or adjustment scheme according to the identified network problems), decision making (determines the network optimization or adjustment scheme according to the analysis result), and execution (executes the network optimization or adjustment scheme according to the determined result); and finally, the management function device feeds back an intention execution result (such as whether the intention is met) to the operation and maintenance personnel.

However, the whole automatic closed-loop process is completed inside the management function device, and operation and maintenance personnel cannot acquire the process information of the intention execution, cannot monitor the intention execution process, and cannot achieve a good network operation and maintenance effect.

Disclosure of Invention

[ correcting 15.04.2021 according to rules 91 ] the application provides a network automation management method and device for monitoring a network closed-loop automation process, thereby achieving a better network operation and maintenance effect and improving network operation and maintenance efficiency.

According to the first aspect of rules 91 for correcting 15.04.2021, the present application provides a network automation management method and apparatus applied to a network closed-loop automation process, the method may include: the closed-loop monitoring method comprises the steps that a closed-loop monitoring function unit obtains closed-loop monitoring capacity information of a closed-loop scene, and at least one closed-loop monitoring point of the closed-loop scene is determined according to the closed-loop monitoring capacity information of the closed-loop scene; the closed-loop monitoring function unit sends a closed-loop monitoring request to a closed-loop execution function unit, wherein the closed-loop monitoring request comprises the information of the closed-loop scene and the information of the at least one closed-loop monitoring point; receiving a monitoring notification corresponding to the at least one closed-loop monitoring point from the closed-loop execution functional unit, wherein the monitoring notification carries an identifier and monitoring information of the corresponding closed-loop monitoring point; and the closed-loop monitoring capability information is used for representing the closed-loop monitoring capability supported by the closed-loop scene.

By the method, the network closed-loop automation process can be monitored, so that a better network operation and maintenance effect is achieved, and the network operation and maintenance efficiency is improved. Meanwhile, operators can flexibly customize closed-loop monitoring information according to needs, so that the network closed-loop automation process is monitored and controlled to a certain extent, negative effects on network adjustment caused by the network closed-loop automation process are prevented, and the closed-loop capability of manufacturers can be evaluated according to the monitoring information.

In one possible design, the closed-loop monitoring capability information includes closed-loop monitoring points supported by the closed-loop scenario; or, the closed-loop monitoring capability information includes a closed-loop monitoring point supported by the closed-loop scene and a monitoring type corresponding to the closed-loop monitoring point. This enables the closed-loop monitoring function to accurately determine at least one closed-loop monitoring point of the closed-loop scene.

In one possible design, the closed-loop monitoring functional unit determines at least one closed-loop monitoring point of the closed-loop scene according to the closed-loop monitoring capability information of the closed-loop scene, and the specific method may be as follows: and the closed-loop monitoring functional unit determines the at least one closed-loop monitoring point according to the closed-loop monitoring capability information and the monitoring requirement of the closed-loop monitoring functional unit. Therefore, the closed-loop monitoring function unit can determine closed-loop monitoring points meeting the monitoring capability and the monitoring requirement of the closed-loop monitoring function unit.

In a possible design, the closed-loop monitoring function unit obtains the closed-loop monitoring capability information of the closed-loop scene, and the specific method may be: the closed-loop monitoring function unit acquires the closed-loop monitoring capability information from the closed-loop execution function unit; or the closed-loop monitoring functional unit acquires template information of the closed-loop scene, wherein the template information comprises the closed-loop monitoring capability information. Therefore, the closed-loop monitoring function unit can flexibly and accurately acquire the closed-loop monitoring capability information, and then subsequently and accurately determine the closed-loop monitoring point of the closed-loop scene.

In one possible design, the at least one closed-loop monitoring point may include at least one of: an intention translation monitoring point, a perception monitoring point, a network analysis monitoring point, a decision monitoring point or an execution monitoring point; wherein the intent translation monitoring point is used for indicating the process or result of monitoring intent translation into a management task or policy; the perception monitoring point is used for indicating the process or the result of the monitoring network perception; the network analysis monitoring point is used for indicating the process or the result of monitoring network analysis; the decision monitoring point is used for indicating the process or the result of the monitoring decision; the execution monitoring point is used for indicating the result of monitoring execution. Therefore, corresponding monitoring can be carried out according to different closed-loop monitoring points.

In one possible design, the intent translation monitor point may include at least one of: intention translation process or result monitoring points, intention satisfaction result monitoring points; wherein, the intention translation process or the result monitoring point is used for indicating and monitoring the process executed by the intention translation function or the result after the execution in the initial intention translation stage or the intention re-translation stage; the intent satisfaction result monitoring point is used to indicate a process for which the monitoring intent is not satisfied. Therefore, corresponding monitoring can be carried out according to different closed-loop monitoring points.

In one possible design, the perceptual monitoring point may include at least one of: network information acquisition process or result monitoring point, network anomaly discovery process or result monitoring point; the network information acquisition process or the result monitoring point is used for indicating the network information acquired by monitoring, and the network information is original network information or processed statistical network information; the network anomaly discovery process or the result monitoring point is used for indicating information for monitoring network anomaly. Therefore, corresponding monitoring can be carried out according to different closed-loop monitoring points.

In one possible design, the network analysis monitoring point may include at least one of: a network problem discovery monitoring point, a network problem analysis monitoring point, a network optimization or adjustment scheme generation monitoring point; the network problem discovery monitoring point is used for indicating a detection process or a result of a monitoring network problem; the network problem analysis monitoring point is used for indicating the analysis process or result of the monitoring network problem; the network optimization or adjustment scheme generation monitoring point is used for indicating the process or the result of monitoring the generated network optimization/adjustment scheme. Therefore, corresponding monitoring can be carried out according to different closed-loop monitoring points.

In one possible design, the monitoring information in the monitoring notification corresponding to the intention translation monitoring point includes at least one of a closed-loop scene identifier, an intention evaluation result and an intention translation result; the monitoring information in the monitoring notification corresponding to the perception monitoring point comprises at least one of closed-loop scene identification and network information; the monitoring information in the monitoring notification corresponding to the network analysis monitoring point comprises at least one of a closed-loop scene identifier and an analysis result; the monitoring information in the monitoring notification corresponding to the decision monitoring point comprises at least one of a closed-loop scene identifier and a determined solution of a network problem; the monitoring information in the monitoring notification corresponding to the execution monitoring point comprises at least one of a closed-loop scene identifier and a solution execution result of a network problem. Therefore, the monitoring content corresponding to the closed-loop monitoring point can be defined.

In one 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 controllable capability information; the monitoring type of any closed-loop monitoring point is monitoring or monitoring and controlling; when the monitoring type of one closed-loop monitoring point is monitoring, indicating that the interruption is not needed, and continuously executing a closed-loop process; when the monitoring type of a closed-loop monitoring point is monitoring and controlling, the closed-loop flow is interrupted by indication, and confirmation is waited. This may enable a closed loop procedure to be subsequently performed depending on the type of monitoring of the closed loop monitoring point.

In a possible design, the closed-loop monitoring request further includes a monitoring type corresponding to the at least one closed-loop monitoring point. Therefore, the closed-loop execution functional unit can execute the closed-loop process according to the monitoring type of the closed-loop monitoring point.

In one possible design, the closed-loop monitoring function unit sends monitoring confirmation information to the closed-loop execution function unit, wherein the monitoring confirmation information comprises an identifier of a monitoring point and a confirmation result; wherein the confirmation result includes at least one of: when the closed-loop monitoring point is an intention translation monitoring point, the closed-loop monitoring functional unit confirms an intention translation result of a closed-loop execution functional unit and instructs the closed-loop execution functional unit to continue executing a closed-loop process; when the closed-loop monitoring point is an intention perception monitoring point, the closed-loop monitoring functional unit confirms the network abnormity found 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 closed-loop monitoring function unit confirms one of the following items: confirming that the closed-loop execution functional unit detects or finds a network problem, and indicating the closed-loop execution functional unit to continue executing a closed-loop process; or, confirming the reason of the network problem analyzed by the closed-loop execution functional unit, and indicating the closed-loop execution functional unit to continue executing the closed-loop flow; or, confirming the network adjustment scheme suggested by the closed-loop execution functional unit, and instructing the closed-loop execution functional unit to continue executing the closed-loop process; when the closed-loop monitoring point is a decision monitoring point, the closed-loop monitoring functional unit confirms the network adjustment scheme selected by the closed-loop execution functional unit and instructs the closed-loop execution functional unit to continue executing a closed-loop process; and when the closed-loop monitoring point is an execution monitoring point, the closed-loop monitoring functional unit confirms an execution result of the closed-loop execution functional unit on a network adjustment scheme. This may enable the closed loop performing function to perform the closed loop flow according to the corresponding acknowledgement information.

In one 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 comprises at least one of a coverage problem detection monitoring point, an abnormal cell identification monitoring point and a coverage optimization scheme suggestion monitoring point; the decision monitoring point determines a monitoring point for a coverage optimization scheme; the execution monitoring point is a coverage optimization scheme execution monitoring point; the coverage optimization intention translation monitoring point is used for indicating and monitoring a coverage optimization intention translation execution result; the coverage performance detection monitoring point is used for indicating a monitoring coverage performance index; the coverage problem detection monitoring point is used for indicating the coverage problem of a monitoring cell or an area level; the abnormal cell identification monitoring point is used for indicating and monitoring an abnormal cell; the coverage optimization scheme suggests a monitoring point for indicating at least one coverage optimization scheme to be selected for monitoring and solving the coverage problem; the coverage optimization scheme determination monitoring point is used for indicating the monitoring to determine a coverage optimization scheme for solving the coverage problem; the coverage optimization scheme execution monitoring point is used for indicating the execution of the monitoring coverage optimization scheme. Therefore, corresponding monitoring can be carried out according to different closed-loop monitoring points in a coverage optimization scene.

In one possible design, the monitoring notification corresponding to the coverage optimization intention translation monitoring point is a coverage intention translation monitoring notification, and the monitoring information of the coverage intention translation monitoring notification comprises at least one of an intention identification and an intention 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 comprises at least one of an intention 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 comprises at least one of an intention 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 comprises at least one of an intention identifier and an abnormal cell list; the coverage optimization scheme determines a monitoring notification corresponding to the monitoring point to be 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 intention identifier and at least one repair scheme; and 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 comprises at least one of an intention identifier and modified configuration information. Therefore, monitoring contents corresponding to the closed-loop monitoring points in the optimized scene can be clearly covered.

In one 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.

In one possible design, when the closed-loop scenario is a coverage optimization scenario, at least one of a coverage optimization intent identifier, a coverage optimization object, or a coverage goal is further included in the closed-loop monitoring request.

In one possible design, when the closed-loop scene is a coverage optimization scene and the closed-loop monitoring point is a coverage optimization intention translation monitoring point, the confirmation information is coverage optimization intention translation result confirmation information, and the coverage optimization intention translation result confirmation information is used for instructing 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 coverage problem confirmation information, and the coverage problem confirmation information is used for instructing a closed-loop execution functional unit to continue executing a coverage optimization closed-loop process to process 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 for instructing a closed-loop execution functional unit to continue executing a coverage optimization closed-loop process to process the abnormal cell; and when the closed-loop monitoring point determines the monitoring point for the coverage optimization scheme, the confirmation information is coverage adjustment scheme confirmation information, and the coverage adjustment scheme confirmation information is used for instructing the closed-loop execution functional unit to continue executing the coverage adjustment prevention scheme. This may enable the closed-loop performing functional unit to perform the closed-loop flow in the coverage optimization scenario according to the corresponding confirmation information.

In one possible design, the information of the closed-loop scenario may include at least one of: a type of the closed-loop scene, an identification of the closed-loop scene, or an object of the closed-loop scene.

In one possible design, the closed-loop scenario may be a scenario of any one of the following closed-loop tasks: planning, deploying, maintaining or optimizing a phase closed-loop task; wherein, the closed-loop task in the planning stage comprises at least one of service planning, network planning and site planning; the deployment stage closed-loop task comprises at least one of service delivery or deployment, network deployment and site deployment; the maintenance stage closed-loop task comprises at least one of service fault recovery, network fault recovery and site fault recovery; the closed-loop task in the optimization stage comprises at least one of service guarantee, network optimization and site optimization; the optimization of the network comprises at least one of network coverage optimization, network capacity optimization and network quality optimization.

In one possible design, the closed-loop monitoring function unit is a cross-domain management unit, and the closed-loop execution function unit is a domain management unit.

According to the second aspect of the rules 91 correction 15.04.2021, the application provides a network automation management method applied to a network closed-loop automation process, which may include: the closed-loop execution functional unit receives a closed-loop monitoring request sent by the closed-loop monitoring functional unit, wherein the closed-loop monitoring request comprises information of a closed-loop scene and information of at least one closed-loop monitoring point; in the closed-loop operation process of the closed-loop scene, the closed-loop execution functional unit acquires the monitoring information of the closed-loop monitoring point when executing to the at least one closed-loop monitoring point, and sends a monitoring notice to the closed-loop monitoring functional unit, wherein the closed-loop monitoring notice carries the identifier of the closed-loop monitoring point and the monitoring information.

In one possible design, the closed-loop execution functional unit sends closed-loop monitoring capability information of the closed-loop scene to the closed-loop monitoring functional unit, where the closed-loop monitoring capability information is used to represent the closed-loop monitoring capability supported by the closed-loop scene; wherein the closed-loop monitoring capability information comprises closed-loop monitoring points supported by the closed-loop scene; or, the closed-loop monitoring capability information includes a closed-loop monitoring point supported by the closed-loop scene and a monitoring type corresponding to the closed-loop monitoring point. Therefore, the closed-loop monitoring function unit can accurately acquire the closed-loop monitoring capability information, and then accurately determine the closed-loop monitoring points of the closed-loop scene in the follow-up process.

In one possible design, the at least one closed-loop monitoring point may include at least one of: an intention translation monitoring point, a perception monitoring point, a network analysis monitoring point, a decision monitoring point or an execution monitoring point; wherein the intent translation monitoring point is used to indicate a process or result of monitoring intent translation to a particular management task or policy; the perception monitoring point is used for indicating the process or the result of the monitoring network perception; the network analysis monitoring point is used for indicating the process or the result of monitoring network analysis; the decision monitoring point is used for indicating the process or the result of monitoring a decision; the execution monitoring point is used for indicating the result of monitoring execution. Therefore, corresponding monitoring can be carried out according to different closed-loop monitoring points.

In one possible design, the intent translation monitor point may include at least one of: an intention translation process or a result monitoring point, an intention satisfaction result monitoring point; wherein, the intention translation process or the result monitoring point is used for indicating and monitoring the process executed by the intention translation function or the result after the execution in the initial intention translation stage or the intention re-translation stage; the intent satisfaction result monitoring points are used to indicate a process for which monitoring intent is not satisfied. Therefore, corresponding monitoring can be carried out according to different closed-loop monitoring points.

In one possible design, when the closed-loop execution functional unit executes to the intention translation monitoring point, the monitoring information of the monitoring notification includes at least one of a closed-loop scene identification, an intention evaluation result, and an intention translation result; when the closed-loop execution functional unit executes the perception monitoring point, the monitoring information of the monitoring notice comprises at least one of closed-loop scene identification and network information; when the closed-loop execution functional unit executes to the network analysis monitoring point, the monitoring information of the monitoring notice comprises at least one of a closed-loop scene identifier and an analysis result; when the closed-loop execution functional unit executes to the decision monitoring point, the monitoring information of the monitoring notification includes: at least one of a closed-loop scenario identification and a determined solution to a network problem; when the closed-loop execution functional unit executes to the execution monitoring point, the monitoring information of the monitoring notification includes: at least one of a closed-loop scenario identification and a solution performance result of a network problem. Therefore, the monitoring content corresponding to the closed-loop monitoring point can be defined.

In one possible design, the closed-loop monitoring request further includes a 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; when the monitoring type of one closed-loop monitoring point is monitoring, indicating that the interruption is not needed, and continuously executing a closed-loop process; when the monitoring type of a closed-loop monitoring point is monitoring and controlling, the closed-loop flow is interrupted by indication, and confirmation is waited. Therefore, the closed-loop execution functional unit can execute the closed-loop process according to the monitoring type of the closed-loop monitoring point.

In one possible design, the closed-loop execution unit receives monitoring confirmation information from the closed-loop monitoring function unit, wherein the monitoring confirmation information comprises monitoring point identification and a confirmation result. This may enable the closed loop performing function to perform the closed loop flow according to the corresponding acknowledgement information.

In one possible design, when the closed-loop scene is a coverage optimization scene, the closed-loop execution functional unit executes to the coverage optimization intention translation monitoring point, the monitoring notification is a coverage intention translation monitoring notification, and monitoring information of the coverage intention translation monitoring notification includes at least one of an intention identifier and an intention translation result; when the closed-loop execution functional unit executes the coverage performance detection monitoring point, the monitoring notification is a coverage performance detection monitoring notification, and monitoring information of the coverage performance detection monitoring notification comprises at least one of an intention identifier and coverage performance information; when the closed-loop execution functional unit executes to the coverage problem detection monitoring point, the monitoring notification is a coverage problem detection monitoring notification, and monitoring information of the coverage problem detection monitoring notification comprises at least one of an intention identifier and a detected coverage problem; when the closed-loop execution functional unit executes the abnormal cell identification monitoring point, the monitoring notification is an abnormal cell identification monitoring notification, and monitoring information of the abnormal cell identification monitoring notification comprises at least one of an intention identifier and an abnormal cell list; when the closed-loop execution functional unit executes to the coverage optimization scheme to determine a monitoring point, the monitoring notification generates a monitoring notification for a coverage adjustment scheme, and monitoring information of the monitoring notification generated by the coverage adjustment scheme comprises at least one of an intention identifier and at least one repair scheme; when the closed-loop execution functional unit executes to the coverage optimization scheme execution monitoring point, the monitoring notification is a coverage adjustment scheme execution monitoring notification, and monitoring information of the coverage adjustment scheme execution monitoring notification includes at least one of an intention identifier and modified configuration information. Therefore, monitoring contents corresponding to the closed-loop monitoring points in the optimized scene can be clearly covered.

In one possible design, when the monitoring type of a closed-loop monitoring point is monitoring, the closed-loop execution functional unit continues to execute a closed-loop process when executing to the closed-loop monitoring point; when the monitoring type of a closed-loop monitoring point is monitoring and controlling, the closed-loop execution functional unit suspends the closed-loop flow when executing to the closed-loop monitoring point and waits for confirmation information of the closed-loop monitoring functional unit. This allows a closed loop flow to be performed depending on the type of monitoring at the monitoring point.

In one possible design, when the closed-loop scenario is a coverage optimization scenario, at least one of a coverage optimization intent identifier, a coverage optimization object, or a coverage goal may be further included in the closed-loop monitoring request.

In one possible design, the information of the closed-loop scenario may include at least one of: a type of the closed-loop scene, an identification of the closed-loop scene, or an objective of the closed-loop scene.

In one possible design, the closed-loop monitoring function unit may be a cross-domain management unit, and the closed-loop execution function unit may be a domain management unit.

In a third aspect, the present application provides a closed-loop monitoring function unit, where the closed-loop monitoring function unit is configured to implement the function of the closed-loop monitoring function unit in the first aspect or each possible design example of the first aspect. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions.

In a possible design, the structure of the closed-loop monitoring functional unit includes a communication unit and a processing unit, and these units may perform corresponding functions of the closed-loop monitoring functional unit in the first aspect or in each possible design example of the first aspect, for which specific reference is made to detailed description in the method example, which is not described herein again.

In one 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 for sending and receiving information or data, and is used for performing communication interaction with other devices in the system, and the processor is configured to support the closed-loop monitoring functional unit to perform the corresponding function of the closed-loop monitoring functional unit in the above first aspect or each possible design example of the first aspect. The memory is coupled to the processor and retains program instructions and data necessary for the closed-loop monitoring function.

In a fourth aspect, the present application provides a closed-loop execution functional unit, which is configured to implement the functions of the closed-loop execution functional unit in the second aspect or each possible design example of the second aspect. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions.

In a possible design, the structure of the closed-loop execution functional unit includes a communication unit and a processing unit, and these units may execute corresponding functions of the closed-loop execution functional unit in each possible design example of the second aspect or the second aspect, specifically refer to detailed descriptions in the method examples, and are not described herein again.

In one possible design, the structure of the closed-loop execution functional unit includes a communication interface and a processor, and optionally a memory, the communication interface is used for sending and receiving information or data, and for performing communication interaction with other devices in the system, and the processor is configured to support the closed-loop execution functional unit to execute the corresponding function of the closed-loop execution functional unit in the second aspect or each possible design example of the second aspect. The memory is coupled to the processor and retains program instructions and data necessary for the closed-loop execution functional unit.

In a fifth aspect, the present application provides a system, which may include the above-mentioned closed-loop monitoring function unit and closed-loop execution function unit.

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

In a seventh aspect, the present application provides a computer program product including computer program code or instructions, which when run on a computer, causes the computer to implement the method in any one of the possible designs of the first or second aspect.

In an eighth aspect, the present application further provides a chip, which includes a processor and a communication interface, where 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 of the first aspect or the second aspect.

For each of the third aspect to the eighth aspect and possible technical effects achieved by each aspect, please refer to the description of the possible technical effects achieved by the various possible schemes in the first aspect or the second aspect, and details are not repeated here.

Drawings

FIG. 1 is a block diagram of a system according to the present application;

FIG. 2 is a schematic diagram of a network closed loop automation process provided herein;

[ correct 15.04.2021 according to rules 91 ] fig. 3 is a flow chart of a network automation management method provided by the present application;

[ correct 15.04.2021 according to rules 91 ] fig. 4 is a flowchart of an example of a network automation management method provided by the present application;

fig. 5 is a schematic structural diagram of a closed-loop monitoring function unit provided in the present application;

FIG. 6 is a schematic diagram of a closed-loop execution functional unit according to the present application;

FIG. 7 is a block diagram of a closed loop monitor function provided herein;

fig. 8 is a block diagram of a closed-loop execution functional unit provided in the present application.

Detailed Description

The present application will be described in further detail below with reference to the accompanying drawings.

[ amend 15.04.2021 according to rules 91 ] the embodiment of the present application provides a method and an apparatus for network automation management, which are used to monitor a network closed-loop automation process, thereby achieving a better network operation and maintenance effect and improving network operation and maintenance efficiency. The method and the device are based on the same inventive concept, and because the principle of solving the problems of the method and the device is similar, the implementation of the device and the method can be mutually referred, and repeated parts are not described again.

In the description of the present application, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying relative importance, nor order.

It should be understood that "at least one" in the embodiments of the present application means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists singly, A and B exist simultaneously, and B exists singly, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, a and b, a and c, b and c, or a, b and c, wherein a, b and c can be single or multiple.

To more clearly describe the technical solution of the embodiment of the present application, the following describes in detail a network automation management method and apparatus provided by the embodiment of the present application with reference to the accompanying drawings.

[ correction 15.04.2021 according to rules 91 ] fig. 1 shows a possible architecture of a system to which the network automation management method provided in the embodiment of the present application is applicable, where the architecture of the system includes a Business Support System (BSS), a cross-domain management function (CD-MnF), a domain management function (domain-MnF), and multiple network elements, where:

the BSS is oriented to operator services and services, and can provide functions and services such as charging, settlement, accounting, customer service, business, network monitoring and the like.

The cross-domain management function unit may also be called a Network Management Function (NMF). The cross-domain management function unit may provide one or more of the following management functions or management services: the network management system comprises the following components of network life cycle management, network deployment, network fault management, network performance management, network configuration management, network guarantee, network optimization function, network intention (intention from communication service provider, intention-CSP) translation of service user intention (intention from communication service provider, intention-CSC)) and the like; a network here may comprise one or more network elements or sub-networks. The network management function unit may be a network slice management function unit (NSMF) or a cross-domain management data analysis function unit (MDAF), or a self-organization network function unit (son f) or a cross-domain intention management function unit (intdrven MnF)). It should be noted that, in some deployment scenarios, the cross-domain management function unit may also provide lifecycle management of a sub-network, deployment of the sub-network, fault management of the sub-network, performance management of the sub-network, configuration management of the sub-network, guarantee of the sub-network, optimization function of the sub-network, translation of sub-network intentions (Intent-CSP or Intent-CSC), and the like, where the sub-network is composed of a plurality of small sub-networks. For example, a network slice contains only one network subslice net, then the cross-domain management function provides for management of both network slices and network slice subnets. The cross-domain management function may be referred to as a provider of the above management service, such as a network lifecycle management service provider.

The domain management function unit may also be called a Network Management Function (NMF) or a network element management function. The domain management unit function may provide one or more of the following management functions or management services: lifecycle management of a sub-network or network element, deployment of a sub-network or network element, fault management of a sub-network or network element, performance management of a sub-network or network element, provisioning of a sub-network or network element, optimization of a sub-network or network element, intent-to-network operator (Intent-to-NOP) translation of a sub-network or network element, and the like, where a sub-network includes one or more network elements. The sub-networks may also comprise sub-networks, i.e. one or more sub-networks constitute one larger sub-network. The domain management function may be referred to as a provider of the above management service, such as a sub-network lifecycle management service provider. The domain management function unit may be a network slice sub-network management function (NSMF), a domain Management Data Analysis Function (MDAF), or a domain-organization network function (son f), or a domain intention management function (intdrven MnF). Wherein, the domain management function unit can be deployed according to, but not limited to, the following ways:

classifying according to network types: access network domain management function unit (RAN), core network domain management function unit (core domain management function), and transport network domain management function unit (transport domain management function); or a certain domain network management system can manage two or all of an access network, a core network and a transmission network;

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

The entity of the plurality of network elements providing the network service may include a core network element (e.g., an access and mobility management function (AMF) network element, a Session Management Function (SMF) network element, a Policy Control Function (PCF) network element, a network data analysis unit (NWDAF) network element, a network warehouse unit (network relocation function, NRF), a gateway, etc.), an access network element (e.g., a base station (e.g., a new generation node B (generic node B, gNB), an evolved node B (eNB)), a centralized control unit (centralized unit-control plane, CUCP), a centralized unit (centralized unit, CU), a distributed unit (distributed unit, centralized DU), a centralized user plane unit (user plane, ups), etc.). The network element may also provide one or more of the following management functions or management services: the method comprises the following steps of management of the life cycle of the network element, deployment of the network element, fault management of the network element, performance management of the network element, guarantee of the network element, optimization function of the network element, intention translation of the network element and the like. The network element may be referred to as a provider of the above management service, such as a network element lifecycle management service provider.

It should be noted that the names of the network elements or units shown in fig. 1 are only used as examples, and may also be referred to as other names in future communications, or nodes or devices related to the present application in future communications may also be replaced by other entities or devices with the same functions, and the like, and the present application is not limited to this. The unified description is made here, and the description is not repeated.

It should be understood that under a service-oriented management architecture, focusing on managing services, the above management functions can be described by a management service provider or a management service user:

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

when the management service is a management service provided by the domain management unit, the domain management unit is a management service provider (MnS provider), and the cross-domain management unit is a management service caller (MnS provider);

when the management service is a management service provided by the above network element, the network element is a management service provider (MnS provider), and the domain management unit is a management service caller (MnS provider).

To correct 15.04.2021 according to rules 91, currently, in the network closed-loop automation process shown in fig. 2, the entire network closed-loop automation process is completed inside the management function, and the operation and maintenance personnel cannot know the process information intended to be executed, and cannot monitor and control the intended execution process, for example, when network adjustment is performed for a certain network problem, other network problems may be caused, and the operation and maintenance personnel need to manually confirm to execute the network adjustment before adjusting the network, so as to prevent the management function from frequently adjusting the network. Or some network problems are automatically identified by the management function, but the operation and maintenance personnel feel that optimization is not needed after comprehensive consideration (for example, the management function identifies a weak coverage area, but the terminals of the area are few or packages ordered by the terminals are cheap, and the operation and maintenance personnel do not consider optimizing the weak coverage area according to business results), and cannot acquire process information intended to be executed, and cannot evaluate the automation capacity of the management system, for example, how the operation and maintenance personnel know whether the management function executes network optimization, which network problems are optimized, and the like. Therefore, the intention execution process cannot be monitored in the current network closed-loop automation process, and a better network operation and maintenance effect cannot be achieved. Based on the network closed-loop automation process, the network automation management method is applied to the network closed-loop automation process, and the network closed-loop automation process can be monitored, so that a good network operation and maintenance effect is achieved, and the network operation and maintenance efficiency is improved.

[ correction 15.04.2021 according to rules 91 ] the embodiment of the present application provides a network automation management method, which is applied to a network closed-loop automation process and is suitable for the system shown in fig. 1. Wherein, the closed loop monitoring function unit and the closed loop execution function unit related in the method can be one of the following combinations: the closed-loop execution functional unit is the cross-domain management functional unit shown in fig. 1, and the closed-loop monitoring functional unit is the BSS shown in fig. 1; or, the closed-loop execution functional unit is the domain management functional unit shown in fig. 1, and the closed-loop monitoring functional unit is the cross-domain management functional unit or BSS shown in fig. 1; or, the closed-loop execution functional unit is the network element shown in fig. 1, and the closed-loop monitoring functional unit is the domain management functional unit, the cross-domain management functional unit, or the BSS shown in fig. 1. Referring to fig. 3, a specific process of the method may include:

step 301: the closed-loop monitoring function unit acquires closed-loop monitoring capability information of a closed-loop scene, wherein the closed-loop monitoring capability information is used for representing the closed-loop monitoring capability supported by the closed-loop scene.

Specifically, the closed-loop scenario refers to a certain closed-loop task, and for example, the closed-loop scenario may be a scenario of any one of the following closed-loop tasks: a planning stage closed-loop task, a deployment stage closed-loop task, a maintenance stage closed-loop task or an optimization stage closed-loop task, etc.

Wherein, the closed-loop task in the planning stage comprises at least one of service planning, network planning and site planning; the deployment stage closed-loop task comprises at least one of service delivery or deployment, network deployment and site deployment; the maintenance stage closed-loop task comprises at least one of service fault recovery, network fault recovery and site fault recovery; the optimization stage closed-loop task comprises at least one of service guarantee, network optimization and site optimization. Specifically, the service guarantee includes Service Level Agreement (SLA) quality guarantee, service traffic model guarantee, and the like; the optimization of the network comprises at least one of coverage optimization, network capacity optimization, network quality optimization and the like; the optimization of the site includes site cell physical identifier (PCI) optimization, site neighbor optimization, site Mobility Robustness Optimization (MRO), site Mobility Load Balancing (MLB), site Physical Random Access Channel (PRACH) optimization, and the like.

Illustratively, when the closed-loop scenario is an optimized coverage optimization scenario of a network in the closed-loop task in the optimization stage, the closed-loop monitoring capability information is coverage optimization closed-loop monitoring capability information.

In an optional embodiment, the closed-loop monitoring capability information may include closed-loop monitoring points supported by the closed-loop scenario; or, the closed-loop monitoring capability information includes a closed-loop monitoring point supported by the closed-loop scene and a monitoring type corresponding to the closed-loop monitoring point.

Specifically, the closed-loop monitoring point may include at least one of: an intent translation monitor point, a perception monitor point, a network analysis monitor point, a decision monitor point, or an execution monitor point. The intention translation monitoring point is used for indicating the process or result of monitoring the intention translation into the management task or the strategy; the perception monitoring point is used for indicating the process or the result of monitoring network perception; the network analysis monitoring point is used for indicating the process or the result of monitoring the network analysis; the decision monitoring point is used for indicating the process or the result of monitoring a decision; the execution monitoring point is used for indicating the result of monitoring execution.

Specifically, the intention translation monitoring point may further include at least one of: an intention translation process or a result monitoring point, an intention satisfaction result monitoring point; wherein, the intention translation process or the result monitoring point is used for indicating and monitoring the process executed by the intention translation function or the result after the execution in the initial intention translation stage or the intention re-translation stage; the intent satisfaction result monitoring point is used to indicate processes for which the monitoring intent is not satisfied, such as which process needs to be monitored or which the intent is not satisfied at a point in time.

The perceptual monitoring point may further comprise at least one of: network information acquisition process or result monitoring point, network anomaly discovery process or result monitoring point; the network information acquisition process or the result monitoring point is used for indicating the network information acquired by monitoring, and the network information is original network information or processed statistical network information; the network anomaly discovery process or the result monitoring point is used for indicating information for monitoring network anomaly. Illustratively, the original network information may be original performance data of a cell, etc.; the processed statistical network information may be statistical network information subjected to primary analysis or calculation, such as performance data aggregated according to the region granularity; the information of the network anomaly may be network performance attenuation, network failure and the like.

The network analysis monitoring point may further include at least one of: a network problem discovery monitoring point, a network problem analysis monitoring point, a network optimization or adjustment scheme generation monitoring point; the network problem discovery monitoring point is used for indicating a detection process or a result of a monitoring network problem; the network problem analysis monitoring point is used for indicating the analysis process or result of the monitoring network problem; the network optimization or adjustment scheme generation monitoring point is used for indicating the process or the result of monitoring the generated network optimization/adjustment scheme.

The execution monitoring point may further include a network adjustment scheme execution result monitoring point, where the network adjustment scheme execution result monitoring point is configured to indicate an execution result of the network adjustment scheme.

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 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 comprises at least one of a coverage problem detection monitoring point, an abnormal cell identification monitoring point and a coverage optimization scheme suggestion monitoring point; the decision monitoring point determines a monitoring point for a coverage optimization scheme; the execution monitoring point is a coverage optimization scheme execution monitoring point; specifically, the method comprises the following steps:

the coverage optimization intention translation monitoring point is used for indicating and monitoring a coverage optimization intention translation execution result; the coverage performance detection monitoring point is used for indicating a monitoring coverage performance index; the coverage problem detection monitoring point is used for indicating the coverage problem of a monitoring cell or a monitoring area level; the abnormal cell identification monitoring point is used for indicating and monitoring an abnormal cell; the coverage optimization scheme suggests that the monitoring point is used for indicating at least one coverage optimization scheme to be selected for monitoring and solving the coverage problem; the coverage optimization scheme determination monitoring point is used for indicating the monitoring to determine a coverage optimization scheme for solving the coverage problem; the coverage optimization scheme execution monitoring point is used for indicating the execution of the monitoring coverage optimization scheme.

In particular, the monitoring type of any closed-loop monitoring point may include, but is not limited to, monitoring or monitoring and controlling. Wherein monitoring and control may also be considered as an interrupt or a suspension.

When the monitoring type of one closed-loop monitoring point is monitoring, indicating that the interruption is not needed, and continuously executing a closed-loop process; that is, the closed-loop monitoring functional unit only senses the information of the closed-loop monitoring point, and after the closed-loop execution functional unit sends the monitoring notification of the closed-loop monitoring point, the closed-loop execution functional unit can continue to execute the network closed-loop process without interrupting the confirmation information of the closed-loop monitoring functional unit. When the monitoring type of a closed-loop monitoring point is monitoring and controlling, indicating to interrupt a closed-loop process and waiting for confirmation, wherein the closed-loop process of the terminal indicates not to continue to execute the next step in the closed-loop process; that is, it means that the closed-loop monitoring function unit, in addition to sensing the information of the closed-loop monitoring point, also wants to control the closed-loop monitoring point, and after the closed-loop execution function unit sends the monitoring notification corresponding to the closed-loop monitoring point, the closed-loop execution function unit needs to interrupt the closed-loop flow and wait for the confirmation information of the closed-loop monitoring function unit.

Optionally, the monitoring types of the closed-loop monitoring points may also be before the closed-loop monitoring points and after the closed-loop monitoring points, and before the closed-loop monitoring points, the monitoring or the monitoring and the controlling before the processes corresponding to the closed-loop monitoring points are indicated; the closed loop monitor point is followed by monitoring and control after the process corresponding to the closed loop monitor point is shown.

For example, it is generally perceived that the monitoring type of a monitoring point is "monitoring", it is intended to translate that the monitoring type of a monitoring point may be "monitoring" or "monitoring and controlling", the monitoring type of a network analysis monitoring point may be "monitoring" or "monitoring and controlling", the monitoring type of a decision monitoring point is "monitoring and controlling", and the monitoring type of an execution monitoring point is "monitoring".

For example, taking a closed-loop scenario as a closed-loop scenario 1 as an example, the description information of the closed-loop monitoring capability of the closed-loop scenario 1 may be as shown in table 1:

TABLE 1

In an optional implementation manner, the closed-loop monitoring functional unit obtains the closed-loop monitoring capability information of the closed-loop scene, and the specific method may be: the closed-loop monitoring function unit acquires the closed-loop monitoring capability information from the closed-loop execution function unit; or the closed-loop monitoring function unit acquires template information of the closed-loop scene, wherein the template information comprises the closed-loop monitoring capability information of the closed-loop scene. Optionally, the template information of the closed-loop scene may be a template of a certain closed-loop intention.

Step 302: and the closed-loop monitoring functional unit determines at least one closed-loop monitoring point of the closed-loop scene according to the closed-loop monitoring capability information of the closed-loop scene.

In an optional implementation manner, the closed-loop monitoring functional unit determines at least one closed-loop monitoring point of the closed-loop scene according to the closed-loop monitoring capability information of the closed-loop scene, and a specific method may be as follows: and the closed-loop monitoring functional unit determines the at least one closed-loop monitoring point according to the closed-loop monitoring capability information and the monitoring requirement of the closed-loop monitoring functional unit.

Step 303: and the closed-loop monitoring function unit sends a closed-loop monitoring request to a closed-loop execution function unit, wherein the closed-loop monitoring request comprises the information of the closed-loop scene and the information of the at least one closed-loop monitoring point.

Specifically, the information of the closed-loop scenario may include at least one of the following: the type of closed-loop scene (e.g., coverage optimization scene, etc.), the identification of the closed-loop scene (used to uniquely identify a closed-loop scene), or the goal of the closed-loop scene (used to identify the execution goal of a closed-loop scene).

In an optional implementation manner, the closed-loop monitoring function unit further determines a monitoring type corresponding to the at least one closed-loop monitoring point according to the closed-loop controllable capability information.

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

Illustratively, the closed-loop monitoring request may be at least one of: a closed-loop task creation request, a closed-loop task modification request, an intent creation request, or an intent modification request, etc.

In one example, when the closed-loop scenario is a coverage optimization scenario, at least one of a coverage optimization intent identifier, a coverage optimization object, or a coverage goal is further included in the closed-loop monitoring request. Wherein the coverage optimization object may comprise any one of a cell, a sub-network or a region; the coverage target may include at least one of no coverage hole, no over coverage, no coverage interference, no weak coverage, a weak coverage proportion threshold, an over coverage proportion threshold, a coverage hole threshold, an uplink and downlink coverage unmatched cell proportion threshold, a pilot frequency pollution coverage area proportion threshold, an over coverage cell proportion threshold, and a weak coverage cell proportion threshold. It is to be noted that the intention referred to in the present application may be a task. Specifically, the coverage optimization intention identifier may also be a coverage optimization task identifier, and the like, and is not limited to the coverage optimization intention identifier here. Similarly, the coverage optimization intention identifiers mentioned in the text are not explained one by one.

Step 304: in the closed-loop operation process of the closed-loop scene, the closed-loop execution functional unit acquires the monitoring information of the closed-loop monitoring point when executing to the at least one closed-loop monitoring point, and sends a monitoring notification to the closed-loop monitoring functional unit, wherein the closed-loop monitoring notification carries the identifier of the closed-loop monitoring point and the monitoring information.

The closed-loop execution functional unit executes the closed-loop operation process, and when the closed-loop operation process is executed to the at least one closed-loop monitoring point, the monitoring information of the at least one closed-loop monitoring point is determined according to the monitoring requirement information (including the closed-loop monitoring point and the monitoring type of the closed-loop monitoring point) of the at least one closed-loop monitoring point. The monitoring information of the closed-loop monitoring point is obtained by analyzing in the closed-loop operation process.

Specifically, when the closed-loop performing functional unit executes to the intention translation monitoring point, that is, when the closed-loop performing functional unit detects that a closed-loop running process reaches the intention translation monitoring point, that is, after the closed-loop performing functional unit determines a corresponding management task or policy according to an intention, a monitoring notification (intention execution monitoring notification) corresponding to the intention translation monitoring point is triggered, where monitoring information of the monitoring notification may include at least one of a closed-loop scene identifier (closed-loop task identifier or intention identifier), an intention evaluation result (whether a wish graph can be executed), and an intention translation result (a management task or policy output after the wish graph is translated).

When the closed-loop execution functional unit executes to the perception monitoring point, that is, when the closed-loop execution functional unit detects that a closed-loop operation process reaches the perception monitoring point, that is, after the closed-loop execution functional unit performs network monitoring (including network information acquisition and network anomaly discovery) according to a monitoring rule or strategy, triggering a monitoring notification (perception monitoring notification) corresponding to the perception monitoring point, wherein the monitoring information of the monitoring notification may include at least one of a closed-loop scene identifier and network information; for example, the network information may be originally acquired network performance information, network statistical information obtained by aggregating the originally acquired network performance information, network anomaly information, and the like.

When the closed-loop execution functional unit is executed to the network analysis monitoring point, that is, when the closed-loop execution functional unit detects that a closed-loop operation process reaches the network analysis monitoring point, that is, after the closed-loop execution functional unit executes any network analysis process in a network adjustment proposal scheme for detecting or finding a network problem, analyzing a root cause of the network problem and generating a network problem, a monitoring notification (network analysis monitoring notification) corresponding to the network analysis monitoring point is triggered, wherein the monitoring information of the monitoring notification may include at least one of a closed-loop scene identifier and an analysis result; the analysis results may include network problems, root causes of network problems, suggested solutions to network problems, and the like.

When the closed-loop execution functional unit executes to the decision monitoring point, that is, when the closed-loop execution functional unit detects that a closed-loop operation process reaches the decision monitoring point, that is, after the closed-loop execution functional unit determines a solution to a network problem, a monitoring notification (decision monitoring notification) corresponding to the decision monitoring point is triggered. Wherein the monitoring information of the monitoring notification may include at least one of a closed-loop scenario identification and a determined solution to a network problem;

when the closed-loop execution functional unit executes to the execution monitoring point, and 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 a solution of a network problem, a monitoring notification (execution monitoring notification) corresponding to the execution monitoring point is triggered. Wherein the monitoring information of the monitoring notification may include at least one of a closed-loop scenario identification and a solution execution result of the network problem (including which network configuration parameters are modified, etc.).

Specifically, in the foregoing process, the closed-loop monitoring point respectively executes, according to the monitoring type of the closed-loop monitoring point: when the monitoring type of the closed-loop monitoring point is monitoring, the closed-loop execution functional unit continues to execute a closed-loop process; when the monitoring type of the closed-loop monitoring point is monitoring and controlling, the closed-loop execution functional unit suspends the closed-loop flow and waits for the message (i.e. the subsequent confirmation information) of the closed-loop monitoring functional unit.

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

when the closed-loop execution functional unit executes to the coverage optimization intention translation monitoring point, the monitoring notification is a coverage intention translation monitoring notification, and monitoring information of the coverage intention translation monitoring notification comprises at least one of intention identification, intention translation results (including whether coverage optimization intention can be met or not, reasons of non-satisfaction, and corresponding coverage optimization strategies (such as performance index monitoring strategies, coverage problem analysis strategies, and the like)); it should be noted that the intention identifier mentioned here is not limited, and may also be a service optimization task or a scene identifier, and the like, and the intention identifiers appearing elsewhere in this text are similar, and the places mentioned in this text are not described one by one.

When the closed-loop execution functional unit executes to the coverage performance detection monitoring point, the monitoring notification is a coverage performance detection monitoring notification, and monitoring information of the coverage performance detection monitoring notification includes at least one of an intention identifier and coverage performance information; the coverage performance information may include coverage performance indicators at a cell or area level, such as Reference Signal Received Power (RSRP), uplink and downlink throughput, radio Resource Control (RRC) establishment success rate, and the like;

when the closed-loop execution functional unit executes to the coverage problem detection monitoring point, the monitoring notification is a coverage problem detection monitoring notification, and monitoring information of the coverage problem detection monitoring notification comprises at least one of an intention identifier and a detected coverage problem; the coverage problem may include a coverage problem at a cell or area level, such as weak coverage, coverage hole, over coverage, uplink and downlink coverage mismatch, and the like;

when the closed-loop execution functional unit executes to the abnormal cell identification monitoring point, the monitoring notification is an abnormal cell identification monitoring notification, and monitoring information of the abnormal cell identification monitoring notification comprises at least one of an intention identifier and an abnormal cell list; optionally, the monitoring information of the abnormal cell identification monitoring notification may also carry a coverage problem corresponding to the abnormal cell;

when the closed-loop execution functional unit executes to the coverage optimization scheme to determine a monitoring point, the monitoring notification generates a monitoring notification for a coverage adjustment scheme, and monitoring information of the monitoring notification generated by the coverage adjustment scheme comprises at least one of an intention identifier and at least one repair scheme; each repair scheme can comprise a modification scheme identifier and a group of coverage scene information to be modified; the set of coverage scene information to be modified comprises a set of { proposed coverage scene information (including a common beam forming function Id), a coverage shape (coverage shape), an azimuth angle (azimuth) and a tilt angle (tilt)) } and corresponding { current proposed coverage scene information (including a beam identifier, a coverage shape, an azimuth angle and a tilt angle) };

when the closed-loop execution functional unit executes to the coverage optimization scheme execution monitoring point, the monitoring notification is a coverage adjustment scheme execution monitoring notification, and monitoring information of the coverage adjustment scheme execution monitoring notification comprises at least one of an intention identifier and modified configuration information; wherein the modified configuration information comprises a set of { proposed coverage scenario information (including beam identity, coverage shape, azimuth and tilt) }.

In an optional embodiment, the closed-loop monitoring function unit sends monitoring confirmation information to the closed-loop execution function unit, where the monitoring confirmation information includes an identifier of a closed-loop monitoring point and a confirmation result.

Specifically, the confirmation result may include at least one of:

when the closed-loop monitoring point is an intention translation monitoring point, the closed-loop monitoring function unit confirms an intention translation execution result of the closed-loop execution function unit and instructs the closed-loop execution function unit to continue executing a closed-loop process;

when the closed-loop monitoring point is a sensing monitoring point, the closed-loop monitoring function unit confirms the network abnormity found by the closed-loop execution function unit and instructs the closed-loop execution function unit to continue executing a closed-loop process (namely, analyzes the confirmed network abnormity);

when the closed-loop monitoring point is a network analysis monitoring point, the closed-loop monitoring functional unit confirms one of the following items: confirming that the closed-loop executive function unit detects or discovers a network problem, and instructing the closed-loop executive function unit to continue executing a closed-loop flow (namely discovering the confirmed network problem); or, confirming the reason of the network problem analyzed by the closed-loop execution functional unit, and instructing the closed-loop execution functional unit to continue executing the closed-loop flow (that is, generating a network adjustment scheme according to the reason of the network problem); or, confirming the network adjustment scheme suggested by the closed-loop execution functional unit, and instructing the closed-loop execution functional unit to continue executing the closed-loop flow (namely, selection and decision of the network adjustment scheme);

when the closed-loop monitoring point is a decision monitoring point, the closed-loop monitoring functional unit confirms the network adjustment scheme selected by the closed-loop execution functional unit and instructs the closed-loop execution functional unit to continue executing a closed-loop process (i.e. execution of the network adjustment scheme);

and when the closed-loop monitoring point is an execution monitoring point, the closed-loop monitoring functional unit confirms an execution result of the closed-loop execution functional unit on a network adjustment scheme.

when the closed-loop monitoring point is a coverage optimization intention translation monitoring point, the confirmation information is coverage optimization intention translation result confirmation information, and the coverage optimization intention translation result confirmation information is used for indicating a closed-loop execution functional unit to continue executing a coverage optimization closed-loop process; the coverage optimization intention translation result confirmation information carries a coverage intention identifier and an Acknowledgement (ACK) confirmation;

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 for instructing a closed-loop execution functional unit to continue executing a coverage optimization closed-loop process to process the coverage problem; the coverage problem acknowledgement information carries a coverage intention identifier and an ACK acknowledgement, and optionally, the coverage problem acknowledgement information may further include indication information of a coverage problem to be processed, which is used to indicate the coverage problem to be processed;

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 for instructing a closed-loop execution functional unit to continue executing a coverage optimization closed-loop process to process the abnormal cell; the abnormal cell identification confirmation information carries a coverage intention identifier and an ACK confirmation;

when the closed-loop monitoring point is a monitoring point determined by a coverage optimization scheme, the confirmation information is coverage adjustment scheme confirmation information, and the coverage adjustment scheme confirmation information is used for instructing a closed-loop execution functional unit to continue executing the coverage adjustment prevention scheme; the coverage adjustment scheme confirmation information carries a coverage intention identifier and an ACK confirmation; optionally, the coverage adjustment scheme confirmation information may also carry one or more selected coverage adjustment schemes.

[ correct 15.04.2021 according to rules 91 ] by using the network automation management method provided by the embodiment of the application, the monitoring of the network closed-loop automation process can be realized, so that a better network operation and maintenance effect is achieved, and the network operation and maintenance efficiency is improved. Meanwhile, operators can flexibly customize closed-loop monitoring information according to needs, so that the network closed-loop automation process is monitored and controlled to a certain extent, negative effects on network adjustment caused by the network closed-loop automation process are prevented, and the closed-loop capability of manufacturers can be evaluated according to the monitoring information.

It should be noted that, in the foregoing embodiment, step 301 and step 302 may be an optional specific implementation manner for the closed-loop monitoring function unit to determine at least one closed-loop monitoring point of the closed-loop scene, that is, the closed-loop monitoring function unit formed in step 301 and step 302 may determine at least one closed-loop monitoring point of the closed-loop scene, and then detailed descriptions are provided according to the specific implementation manner of step 301 and step 302, specific contents may refer to the above description, and detailed descriptions are not described here.

[ 15.04.2021 corrected according to the rule 91 ] based on the above embodiments, the following describes in detail the network automation management method provided by the embodiment of the present application by using a specific example, as an example shown in fig. 4. In this example, a closed-loop scene is taken as an example of a coverage optimization scene, a closed-loop monitoring functional unit is a cross-domain management unit, and a closed-loop execution functional unit is taken as an example of a domain management unit, that is, the domain management unit is taken as a closed-loop execution functional unit to execute closed-loop automation of coverage optimization, and the cross-domain management unit is taken as a closed-loop monitoring functional unit to monitor closed-loop automation of coverage optimization. Specifically, the specific process of the example of the network automation management method shown in fig. 4 may include:

step 401: the method comprises the steps that a cross-domain management unit obtains coverage optimization closed-loop monitoring capability information sent by a domain management unit, wherein the coverage optimization closed-loop monitoring capability information comprises coverage optimization closed-loop monitoring points supported by the domain management unit aiming at coverage optimization and monitoring types corresponding to the coverage optimization closed-loop monitoring points.

Specifically, the coverage optimization closed-loop monitoring point may include at least one of the following:

a coverage optimization intention translation monitoring point, configured to monitor a coverage optimization intention translation execution result, that is, report a coverage optimization translation intention result (including whether a coverage optimization intention can be satisfied, a reason why the coverage optimization intention is not satisfied, and the like) after instructing a domain management functional unit to execute the coverage optimization translation intention; the coverage optimization intention translates the monitoring type of the monitoring point into monitoring and control; the coverage optimization intent translation monitor point belongs to the intent translation monitor point in the embodiment shown in FIG. 3;

the coverage performance detection monitoring point is used for monitoring a coverage performance index, namely, when the indication domain management functional unit detects the coverage performance index according to a certain time period, reporting the corresponding coverage performance index, including the coverage performance index (such as RSRP, uplink and downlink throughput rate, RRC establishment success rate and the like) of a cell level or an area level. The monitoring type of the coverage performance detection monitoring point is monitoring; the coverage performance detection monitoring point belongs to the sensing monitoring point of the embodiment shown in fig. 3;

and the coverage problem detection monitoring point is used for monitoring the coverage problem, namely reporting the corresponding coverage problem when the domain management function unit is indicated to detect the coverage problem. The coverage problem may include a coverage problem at a cell or area level (e.g., weak coverage, coverage holes, over coverage, uplink and downlink coverage mismatch, etc.). The type of the coverage problem detection monitoring point is monitoring or monitoring and controlling; the coverage problem detection monitoring point belongs to the network analysis monitoring point of the embodiment shown in fig. 3;

the abnormal cell identification monitoring point is configured to monitor an abnormal cell (an abnormal cell of a Top N (Top N) that causes the coverage problem), that is, to report an abnormal cell list when the domain management function unit identifies a Top N abnormal cell that has a corresponding coverage problem. The abnormal cell identifies the type of the monitoring point as monitoring or monitoring and controlling; the abnormal cell identification monitoring point belongs to the network analysis monitoring point of the embodiment shown in fig. 3;

the coverage optimization scheme suggests monitoring points for monitoring possible coverage optimization schemes (i.e. a corresponding set of coverage scenario information (including beam (common beam forming function) identification, coverage shape, azimuth angle and tilt angle) for solving the coverage problem), i.e. reporting the corresponding possible coverage optimization schemes when instructing the domain management function unit to generate the coverage optimization schemes for the possible coverage problem;

a coverage optimization scheme determining monitoring point, configured to monitor and determine a coverage optimization scheme for solving the coverage problem, that is, to report a corresponding coverage optimization scheme to be executed when instructing a domain management functional unit to determine the coverage optimization scheme for solving the coverage problem; the coverage optimization scheme determines the type of the monitoring point to be monitoring or monitoring and controlling; the coverage optimization scheme determines that a monitoring point belongs to a decision monitoring point in the embodiment shown in fig. 3;

the coverage optimization scheme execution monitoring point is used for monitoring the execution of the coverage optimization scheme, namely instructing the domain management functional unit to report the corresponding execution result (for example, which common beam forming function instances have the modified coverage shape attribute) after the coverage optimization scheme is executed. The type of the monitoring point executed by the coverage optimization scheme is monitoring; the coverage optimization scheme execution monitoring point belongs to the execution monitoring point in the embodiment shown in fig. 3.

It should be noted that the step 401 belongs to a coverage optimization closed-loop monitoring capability obtaining process, and the step 401 is an optional step.

Step 402: and the cross-domain management unit determines a coverage optimization task or intention, wherein the coverage optimization intention carries information of a coverage optimization intention identifier, a coverage optimization object, a coverage target and a coverage optimization closed-loop monitoring point.

It should be noted that, for simplicity of description, the coverage optimization purpose is used in this example to describe, note that in practice, the coverage optimization task may also be used, and this embodiment does not limit this.

Specifically, the coverage optimization intent identification is used to uniquely identify a coverage optimization intent, which is an optional parameter; the coverage optimization object comprises any one of a cell, a sub-network or a region; the coverage target comprises at least one of a no-coverage hole threshold, no over-coverage, no-coverage interference, no weak coverage, a weak coverage proportion threshold, an over-coverage proportion threshold, a coverage hole threshold, an uplink and downlink coverage unmatched cell proportion threshold, a pilot frequency pollution coverage area proportion threshold, an over-coverage cell proportion threshold and a weak coverage cell proportion threshold.

Specifically, the information of the coverage optimization closed-loop monitoring point is described in step 401 with reference to the related description of the coverage optimization closed-loop monitoring point.

Step 403: and the cross-domain management function unit sends the coverage optimization intention (namely a closed-loop monitoring request) to the domain management unit, wherein the coverage optimization intention carries information of a coverage optimization intention identifier, a coverage optimization object, a coverage target and a coverage optimization closed-loop monitoring point.

It should be noted that, the step 402 and the step 403 belong to a coverage optimization intention issuing process.

Step 404: and the domain management functional unit starts to execute a coverage optimization closed-loop automatic flow according to the received coverage optimization intention. Specifically, the method comprises the following steps:

steps 405a to 405c execute an intent translation procedure for the domain management functional unit according to the received coverage optimization intent:

step 405a: the domain management functional unit determines an intention translation result (including whether a coverage optimization intention can be met or not, reasons of non-satisfaction and corresponding coverage optimization strategies (such as a performance index monitoring strategy, a coverage problem analysis strategy and the like)); and the domain management functional unit executes the coverage optimization intention translation process, and triggers a coverage intention translation monitoring notice when detecting that a coverage optimization intention translation monitoring point is set in the cross-domain management functional unit.

Step 405b: and the domain management functional unit sends a coverage intention translation monitoring notice to the cross-domain management functional unit, wherein the coverage intention translation monitoring notice carries one or both of an intention identifier and a monitoring point identifier, and the intention translation result.

Step 405c: when the monitoring type of the coverage intention translation monitoring point is monitoring and controlling, the cross-domain management functional unit sends coverage optimization intention translation result confirmation information to the domain management functional unit, and instructs the domain management functional unit to continuously execute a coverage optimization closed-loop process; and the coverage optimization intention translation result confirmation information carries a coverage intention identifier and an ACK confirmation.

Steps 406a to 406b execute a coverage performance detection monitoring procedure for the domain management functional unit:

step 406a: the domain management function unit acquires a coverage performance index (e.g.,. RSRP) according to a coverage performance detection policy (e.g., acquiring the coverage performance index at a certain time period), where the coverage performance detection policy may be output by a coverage intention translation process or may be preset in the domain management function unit); after the domain management functional unit executes the coverage performance detection process, triggering a coverage performance detection monitoring notification when detecting that the cross-domain management functional unit is provided with a coverage performance detection monitoring point.

Step 406b: the domain management function unit sends a coverage performance detection monitoring notification to the cross-domain management function unit, wherein the coverage performance detection monitoring notification carries one or both of an intention identifier and a monitoring point identifier, and coverage performance information (including coverage performance indexes of a cell or an area level (such as RSRP, uplink and downlink throughput rate, RRC establishment success rate and the like).

Steps 407a to 407c execute a coverage problem detection monitoring procedure for the domain management functional unit:

step 407a: the domain management functional unit performs coverage problem detection, that is, detects a coverage problem according to the coverage performance information (see the description in step 402), completes a coverage problem detection monitoring process, and triggers a coverage problem detection monitoring notification when detecting that a coverage problem detection monitoring point is set in the cross-domain management functional unit.

Step 407b: the domain management function unit sends a coverage problem detection monitoring notification to the cross-domain management function unit, wherein the coverage problem detection monitoring notification carries one or both of an intention identifier and a monitoring point identifier, and a detected coverage problem (including a coverage problem of a cell or a region level (such as weak coverage, coverage holes, over coverage, uplink and downlink coverage mismatch, and the like)).

Step 407c: when the monitoring type of the coverage problem detection monitoring point is monitoring and controlling, the cross-domain management functional unit sends coverage problem confirmation information to the domain management functional unit and instructs the domain management functional unit to continuously execute a coverage optimization closed-loop process to process the coverage problem; the coverage problem acknowledgement information carries a coverage intention identifier and an ACK acknowledgement, and optionally, the coverage problem acknowledgement information further includes indication information of a coverage problem that needs to be processed, and the indication information is used for indicating the coverage problem that needs to be processed by the domain management function unit.

Steps 408a to 408c execute an abnormal cell identification monitoring procedure corresponding to the coverage problem for the domain management functional unit, mainly aiming at identifying a ToP N cell list causing the coverage problem:

step 408a: and the domain management functional unit executes an abnormal cell identification monitoring process, namely, determines to introduce the main cell list of the coverage problem, executes the abnormal cell identification monitoring process, and triggers an abnormal cell identification monitoring notice when detecting that the cross-domain management functional unit is provided with an abnormal cell identification monitoring point.

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

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

Steps 409a to 409c generate a monitoring procedure for the domain management function unit to execute the coverage adjustment scheme.

Step 409a: the domain management functional unit executes a coverage adjustment scheme generation monitoring process, that is, a group of possible repair schemes for solving the coverage problem is generated (each repair scheme includes a modification scheme identifier and a group of coverage scenario information to be modified, including a group of { proposed coverage scenario information (including a beam identifier, a coverage shape, an azimuth angle and a tilt angle) } and corresponding { currently proposed coverage scenario information (including a beam identifier, a coverage shape, an azimuth angle and a tilt angle) }, and when it is detected that a cross-domain management functional unit sets a coverage adjustment scheme generation monitoring point, the coverage adjustment scheme is triggered to generate a monitoring notification.

Step 409b: the domain management function unit sends a coverage adjustment scheme to the cross-domain management function unit to generate a monitoring notification, wherein the coverage adjustment scheme generates the monitoring notification and carries one or both of an intention identifier and a monitoring point identifier, and a group of possible repair schemes; optionally, the coverage adjustment scheme generating the monitoring notification may further include a coverage problem corresponding to the repair scheme.

Step 409c: when the monitoring type of a monitoring point generated by the coverage adjustment scheme is monitoring and controlling, the cross-domain management functional unit sends coverage adjustment scheme confirmation information to the domain management functional unit and instructs the domain management functional unit to continue executing the coverage adjustment prevention scheme; the coverage adjustment scheme acknowledgement information carries a coverage intention identifier and an ACK acknowledgement. Optionally, when multiple groups of possible coverage adjustment schemes are carried in step 409a, the coverage adjustment scheme confirmation information may also carry one or more selected coverage adjustment schemes.

Steps 410a to 410b perform a monitoring procedure for the domain management function unit to perform the coverage adjustment scheme:

step 410a: the domain management functional unit executes a coverage adjustment scheme execution monitoring process, that is, executes the confirmed coverage repair scheme (a group of coverage scenario information is configured, which includes a group of { proposed coverage scenario information (including a beam identifier, a coverage shape, an azimuth angle and an inclination angle) }, and triggers a coverage adjustment scheme execution monitoring notification when detecting that a coverage adjustment scheme execution monitoring point is set by the cross-domain management functional unit.

Step 410b: the domain management function unit sends a coverage adjustment scheme execution monitoring notification to the cross-domain management function unit, wherein the coverage adjustment scheme execution monitoring notification carries one or both of an intention identifier and a monitoring point identifier, and modified configuration information, including a set of { proposed coverage scenario information (including a beam identifier, a coverage shape, an azimuth angle and a tilt angle) }.

Based on the above example, the monitoring of the coverage optimization closed-loop automation process can be realized, so that a better network operation and maintenance effect is achieved, and the network operation and maintenance efficiency is improved. Meanwhile, operators can flexibly customize coverage optimization closed-loop monitoring information according to needs, so that the coverage optimization closed-loop automation process is monitored and controlled to a certain extent, negative effects on network adjustment caused by the coverage optimization closed-loop automation process are prevented, and the coverage optimization closed-loop capacity of manufacturers can be evaluated according to the monitoring information.

Based on the above embodiments, the embodiment of the present application further provides a closed-loop monitoring function unit, which is applied to the system shown in fig. 1, and is used to implement the functions of the closed-loop monitoring function unit in the network automation management method shown in fig. 3 and the functions of the cross-domain management unit in the embodiment shown in fig. 4. Referring to fig. 5, the closed-loop monitoring function unit 500 includes: a processing unit 501 and a communication unit 502, wherein:

the processing unit 501 is configured to obtain closed-loop monitoring capability information of a closed-loop scene, where the closed-loop monitoring capability information is used to represent a closed-loop monitoring capability supported by the closed-loop scene; determining at least one closed-loop monitoring point of the closed-loop scene according to the closed-loop monitoring capability information of the closed-loop scene; the communication unit 502 is configured to send a closed-loop monitoring request to a closed-loop execution function unit, where the closed-loop monitoring request includes information of the closed-loop scene and information of the at least one closed-loop monitoring point; and receiving a monitoring notification corresponding to the at least one closed-loop monitoring point from the closed-loop execution functional unit, wherein the monitoring notification carries the identifier and the monitoring information of the corresponding closed-loop monitoring point.

In an optional embodiment, the closed-loop monitoring capability information includes closed-loop monitoring points supported by the closed-loop scenario; or, the closed-loop monitoring capability information includes a closed-loop monitoring point supported by the closed-loop scene and a monitoring type corresponding to the closed-loop monitoring point.

In a specific embodiment, when determining at least one closed-loop monitoring point of the closed-loop scene according to the closed-loop monitoring capability information of the closed-loop scene, the processing unit 501 is specifically configured to: and determining the at least one closed-loop monitoring point according to the closed-loop monitoring capability information and the monitoring requirement of the closed-loop monitoring point.

Illustratively, the at least one closed-loop monitoring point may include at least one of: an intention translation monitoring point, a perception monitoring point, a network analysis monitoring point, a decision monitoring point or an execution monitoring point; wherein the intent translation monitoring point is used for indicating the process or result of monitoring intent translation into a management task or policy; the perception monitoring point is used for indicating the process or the result of the monitoring network perception; the network analysis monitoring point is used for indicating the process or the result of monitoring network analysis; the decision monitoring point is used for indicating the process or the result of the monitoring decision; the execution monitoring point is used for indicating the result of monitoring execution.

In an optional embodiment, the processing unit 501 is further configured to determine a monitoring type corresponding to the at least one closed-loop monitoring point according to the closed-loop controllable capability information; the monitoring type of any closed-loop monitoring point is monitoring or monitoring and controlling; when the monitoring type of one closed-loop monitoring point is monitoring, indicating that interruption is not needed, and continuously executing a closed-loop process; when the monitoring type of a closed loop monitoring point is monitoring and controlling, the closed loop flow is indicated to be interrupted to wait for confirmation.

Illustratively, the closed-loop monitoring request further includes a monitoring type corresponding to the at least one closed-loop monitoring point.

In an optional implementation manner, the communication unit 502 is further configured to send monitoring confirmation information to the closed-loop execution functional unit, where the monitoring confirmation information includes an identifier of a monitoring point and a confirmation result; wherein the confirmation result includes at least one of: when the closed-loop monitoring point is an intention translation monitoring point, the processing unit 501 confirms an intention translation result of the closed-loop execution functional unit, and instructs the processing unit 501 to continue executing the closed-loop process; when the closed-loop monitoring point is an intention perception monitoring point, the processing unit 501 determines that the network found by the closed-loop execution functional unit is abnormal, and instructs the closed-loop execution functional unit to continue executing a closed-loop process; when the closed-loop monitoring point is a network analysis monitoring point, the processing unit 501 determines one of the following items: confirming that the closed-loop execution functional unit detects or finds a network problem, and indicating the closed-loop execution functional unit to continue executing a closed-loop process; or, confirming the reason of the network problem analyzed by the closed-loop execution functional unit, and indicating the closed-loop execution functional unit to continue executing the closed-loop flow; or, confirming the network adjustment scheme suggested by the closed-loop execution functional unit, and instructing the closed-loop execution functional unit to continue executing the closed-loop process; when the closed-loop monitoring point is a decision monitoring point, the processing unit 501 determines the network adjustment scheme 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 processing unit 501 determines an execution result of the closed-loop execution functional unit on the network adjustment scheme.

In one example, when the closed-loop scenario is a coverage optimization scenario, the at least one closed-loop monitor point is at least one coverage optimization closed-loop monitor 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 points comprise at least one of coverage problem detection monitoring points, abnormal cell identification monitoring points and coverage optimization scheme suggestion monitoring points; the decision monitoring point determines a monitoring point for a coverage optimization scheme; the execution monitoring point is a coverage optimization scheme execution monitoring point; the coverage optimization intention translation monitoring point is used for indicating and monitoring a coverage optimization intention translation execution result; the coverage performance detection monitoring point is used for indicating a monitoring coverage performance index; the coverage problem detection monitoring point is used for indicating the coverage problem of a monitoring cell or a monitoring area level; the abnormal cell identification monitoring point is used for indicating to monitor an abnormal cell; the coverage optimization scheme suggests a monitoring point for indicating at least one coverage optimization scheme to be selected for monitoring and solving the coverage problem; the coverage optimization scheme determination monitoring point is used for indicating the monitoring to determine a coverage optimization scheme for solving the coverage problem; the coverage optimization scheme execution monitoring point is used for indicating the execution of the monitoring coverage optimization scheme.

Illustratively, when the closed-loop scenario is a coverage optimization scenario, the closed-loop monitoring capability information is coverage optimization closed-loop monitoring capability information.

In an exemplary embodiment, when the closed-loop scene is a coverage optimization scene, and when the closed-loop monitoring point is a coverage optimization intention translation monitoring point, the confirmation information is coverage optimization intention translation result confirmation information, and the coverage optimization intention translation result confirmation information is used for instructing a closed-loop execution functional unit to continue executing a 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 for instructing a closed-loop execution functional unit to continue executing a coverage optimization closed-loop process to process 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 for instructing a closed-loop execution functional unit to continue executing a coverage optimization closed-loop process to process the abnormal cell; and when the closed-loop monitoring point is a monitoring point determined by a coverage optimization scheme, the confirmation information is coverage adjustment scheme confirmation information, and the coverage adjustment scheme confirmation information is used for indicating a closed-loop execution functional unit to continue executing the coverage adjustment prevention scheme.

In a specific embodiment, the closed-loop monitoring function unit is a cross-domain management unit, and the closed-loop execution function unit is a domain management unit.

Based on the above embodiments, the present application further provides a closed-loop executive function unit, which is applied to the system shown in fig. 1, for implementing the functions of the closed-loop executive function unit in the network automation management method shown in fig. 3 and the functions of the domain management unit in the embodiment shown in fig. 4. Referring to fig. 6, the closed loop execution function unit 600 includes: a communication unit 601 and a processing unit 602, wherein:

the communication unit 601 is configured to receive a closed-loop monitoring request sent by a closed-loop monitoring function unit, where the closed-loop monitoring request includes information of a closed-loop scene and information of at least one closed-loop monitoring point; the processing unit 602 is configured to, in a closed-loop operation process of the closed-loop scene, obtain monitoring information of a closed-loop monitoring point when the at least one closed-loop monitoring point is reached; the communication unit 601 is further configured to send a monitoring notification to the closed-loop monitoring function unit, where the closed-loop monitoring notification carries the identifier of the closed-loop monitoring point and the monitoring information.

In an optional implementation manner, the communication unit 601 is further configured to send closed-loop monitoring capability information of the closed-loop scenario to the closed-loop monitoring functional unit, where the closed-loop monitoring capability information is used to characterize a closed-loop monitoring capability supported by the closed-loop scenario; wherein the closed-loop monitoring capability information comprises closed-loop monitoring points supported by the closed-loop scene; or, the closed-loop monitoring capability information includes a closed-loop monitoring point supported by the closed-loop scene and a monitoring type corresponding to the closed-loop monitoring point.

Illustratively, the at least one closed-loop monitoring point includes at least one of: an intention translation monitoring point, a perception monitoring point, a network analysis monitoring point, a decision monitoring point or an execution monitoring point; wherein the intent translation monitoring point is used to indicate a process or result of monitoring intent translation to a particular management task or policy; the perception monitoring point is used for indicating the process or the result of monitoring network perception; the network analysis monitoring point is used for indicating the process or the result of monitoring the network analysis; the decision monitoring point is used for indicating the process or the result of the monitoring decision; the execution monitoring point is used for indicating the result of monitoring execution.

In an optional embodiment, the closed-loop monitoring request further includes a 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; when the monitoring type of one closed-loop monitoring point is monitoring, indicating that the interruption is not needed, and continuously executing a closed-loop process; when the monitoring type of a closed-loop monitoring point is monitoring and controlling, the closed-loop flow is interrupted by indication, and confirmation is waited.

In a specific implementation manner, 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.

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, 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 comprises at least one of a coverage problem detection monitoring point, an abnormal cell identification monitoring point and a coverage optimization scheme suggestion monitoring point; the decision monitoring point determines a monitoring point for a coverage optimization scheme; the execution monitoring point is a coverage optimization scheme execution monitoring point; the coverage optimization intention translation monitoring point is used for indicating and monitoring a coverage optimization intention translation execution result; the coverage performance detection monitoring point is used for indicating a monitoring coverage performance index; the coverage problem detection monitoring point is used for indicating the coverage problem of a monitoring cell or an area level; the abnormal cell identification monitoring point is used for indicating to monitor an abnormal cell; the coverage optimization scheme suggests that the monitoring point is used for indicating at least one coverage optimization scheme to be selected for monitoring and solving the coverage problem; the coverage optimization scheme determination monitoring point is used for indicating the monitoring to determine a coverage optimization scheme for solving the coverage problem; the coverage optimization scheme execution monitoring point is used for indicating the execution of the monitoring coverage optimization scheme.

Specifically, when the monitoring type of a closed-loop monitoring point is monitoring, the processing unit 602 is further configured to continue to execute a closed-loop process when the closed-loop monitoring point is reached; 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 the closed-loop monitoring point is reached, and wait for a confirmation message of the closed-loop monitoring functional unit.

It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. The functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or may also be implemented in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application, which are essential or contributing to the prior art, or all or part of the technical solutions may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a portable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.

Based on the foregoing embodiments, the present application further provides a closed-loop monitoring functional unit, where the closed-loop monitoring functional unit is applied to the system shown in fig. 1, and is used to implement the functions of the closed-loop monitoring functional unit in the monitoring method shown in fig. 3 and the functions of the cross-domain management unit in the embodiment shown in fig. 4. Referring to fig. 7, the closed loop monitor function 700 may include a communication interface 701 and a processor 702. Optionally, the closed-loop monitoring function unit 700 may further include a memory 703. The memory 703 may be disposed inside the closed-loop monitoring function unit 700, or may be disposed outside the closed-loop monitoring function unit 700. The processor 702 may control the communication interface 701 to receive and transmit information or data.

Specifically, the processor 702 may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of the CPU and the NP. The processor 702 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof.

The communication interface 701, the processor 702 and the memory 703 are connected to each other. Optionally, the communication interface 701, the processor 702 and the memory 703 are connected to each other through a bus 704; the bus 704 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 ease of illustration, only one thick line is shown in FIG. 7, but this is not intended to represent only one bus or type of bus.

In an alternative embodiment, the memory 703 is used for storing programs and the like. In particular, the program may include program code comprising computer operating instructions. The memory 703 may include RAM, and may also include non-volatile memory (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 function unit 700.

Specifically, when the closed-loop monitoring functional unit 700 is used to implement the functions of the closed-loop monitoring functional unit (such as a cross-domain management unit) in the embodiment described in fig. 3 or fig. 4, the method may specifically include:

the processor 702 is configured to obtain closed-loop monitoring capability information of a closed-loop scene, where the closed-loop monitoring capability information is used to represent a closed-loop monitoring capability supported by the closed-loop scene; determining at least one closed-loop monitoring point of the closed-loop scene according to the closed-loop monitoring capability information of the closed-loop scene; the communication interface 701 is configured to send a closed-loop monitoring request to a closed-loop execution function unit, where the closed-loop monitoring request includes information of the closed-loop scene and information of the at least one closed-loop monitoring point; and receiving a monitoring notification corresponding to the at least one closed-loop monitoring point from the closed-loop execution function unit, wherein the monitoring notification carries the identifier and the monitoring information of the corresponding closed-loop monitoring point.

In a specific embodiment, when determining at least one closed-loop monitoring point of the closed-loop scene according to the closed-loop monitoring capability information of the closed-loop scene, the processor 702 is specifically configured to: and determining the at least one closed-loop monitoring point according to the closed-loop monitoring capability information and the monitoring requirement of the closed-loop monitoring point.

Illustratively, the at least one closed-loop monitoring point may include at least one of: an intention translation monitoring point, a perception monitoring point, a network analysis monitoring point, a decision monitoring point or an execution monitoring point; the intention translation monitoring point is used for indicating the process or result of monitoring the intention translation into the management task or the strategy; the perception monitoring point is used for indicating the process or the result of monitoring network perception; the network analysis monitoring point is used for indicating the process or the result of monitoring network analysis; the decision monitoring point is used for indicating the process or the result of the monitoring decision; the execution monitoring point is used for indicating the result of monitoring execution.

In an optional embodiment, the processor 702 is further configured to determine a monitoring type corresponding to the at least one closed-loop monitoring point according to the closed-loop controllability information; the monitoring type of any closed-loop monitoring point is monitoring or monitoring and controlling; when the monitoring type of one closed-loop monitoring point is monitoring, indicating that the interruption is not needed, and continuously executing a closed-loop process; when the monitoring type of a closed-loop monitoring point is monitoring and controlling, the closed-loop flow is interrupted by indication, and confirmation is waited.

In an optional implementation manner, 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 an identifier of a monitoring point and a confirmation result; wherein the confirmation result includes at least one of: when the closed-loop monitoring point is an intention translation monitoring point, the processor 702 confirms an intention translation result of a closed-loop execution functional unit and instructs the processor 702 to continue to execute a closed-loop process; when the closed-loop monitoring point is an intention perception monitoring point, the processor 702 confirms the network abnormality found by the closed-loop execution functional unit and instructs the closed-loop execution functional unit to continue executing the closed-loop flow; when the closed-loop monitoring point is a network analysis monitoring point, the processor 702 determines one of the following: confirming that the closed-loop execution functional unit detects or finds a network problem, and indicating the closed-loop execution functional unit to continue executing a closed-loop process; or, confirming the reason of the network problem analyzed by the closed-loop execution functional unit, and indicating the closed-loop execution functional unit to continue executing the closed-loop flow; or, confirming the network adjustment scheme suggested by the closed-loop execution functional unit, and instructing the closed-loop execution functional unit to continue executing the closed-loop process; when the closed-loop monitoring point is a decision monitoring point, the processor 702 determines the network adjustment scheme 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 closed-loop execution functional unit on the network adjustment scheme.

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, 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 comprises at least one of a coverage problem detection monitoring point, an abnormal cell identification monitoring point and a coverage optimization scheme suggestion monitoring point; the decision monitoring point determines a monitoring point for a coverage optimization scheme; the execution monitoring point is a coverage optimization scheme execution monitoring point; the coverage optimization intention translation monitoring point is used for indicating and monitoring a coverage optimization intention translation execution result; the coverage performance detection monitoring point is used for indicating a monitoring coverage performance index; the coverage problem detection monitoring point is used for indicating the coverage problem of a monitoring cell or a monitoring area level; the abnormal cell identification monitoring point is used for indicating to monitor an abnormal cell; the coverage optimization scheme suggests a monitoring point for indicating at least one coverage optimization scheme to be selected for monitoring and solving the coverage problem; the coverage optimization scheme determination monitoring point is used for indicating the monitoring to determine a coverage optimization scheme for solving the coverage problem; the coverage optimization scheme execution monitoring point is used for indicating the execution of the monitoring coverage optimization scheme.

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 coverage optimization intention translation result confirmation information, and the coverage optimization intention translation result confirmation information is used for instructing a closed-loop execution functional unit to continue executing a 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 for instructing a closed-loop execution functional unit to continue executing a coverage optimization closed-loop process to process 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 for instructing a closed-loop execution functional unit to continue executing a coverage optimization closed-loop process to process the abnormal cell; and when the closed-loop monitoring point is a monitoring point determined by a coverage optimization scheme, the confirmation information is coverage adjustment scheme confirmation information, and the coverage adjustment scheme confirmation information is used for indicating a closed-loop execution functional unit to continue executing the coverage adjustment prevention scheme.

Based on the above embodiments, the present application further provides a closed-loop executive function unit, which is applied to the system shown in fig. 1, for implementing the functions of the closed-loop executive function unit in the network automation management method shown in fig. 3 and the functions of the domain management unit in the embodiment shown in fig. 4. Referring to fig. 8, the closed loop execution function 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. The memory 803 may be disposed inside the closed-loop execution function unit 800, or may be disposed outside the closed-loop execution function unit 800. The processor 802 may control the communication interface 801 to receive and transmit information or data.

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 hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof.

Wherein, the communication interface 801, the processor 802 and the memory 803 are connected with each other. Optionally, the communication interface 801, the processor 802 and the memory 803 are connected to each other 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 ease of illustration, only one thick line is shown in FIG. 8, but this is not intended to represent only one bus or type of bus.

In an alternative embodiment, the memory 803 is used for storing programs and the like. In particular, the program may include program code comprising computer operating instructions. The memory 803 may include RAM, and may also include non-volatile memory (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.

Specifically, when the closed-loop execution functional unit 800 is used to implement the functions of the closed-loop execution functional unit (such as the domain management unit) in the embodiment described in fig. 3 or fig. 4, the method may specifically include:

the communication interface 801 is configured to receive a closed-loop monitoring request sent by a closed-loop monitoring function unit, where the closed-loop monitoring request includes information of a closed-loop scene and information of at least one closed-loop monitoring point; the processor 802 is configured to obtain monitoring information of a closed-loop monitoring point when the closed-loop monitoring point is reached in a closed-loop operation process of the closed-loop scene; the communication interface 801 is further configured to send a monitoring notification to the closed-loop monitoring function unit, where the closed-loop monitoring notification carries the identifier of the closed-loop monitoring point and the monitoring information.

In an optional implementation manner, the communication interface 801 is further configured to send closed-loop monitoring capability information of the closed-loop scenario to the closed-loop monitoring functional unit, where the closed-loop monitoring capability information is used to characterize a closed-loop monitoring capability supported by the closed-loop scenario; wherein the closed-loop monitoring capability information comprises closed-loop monitoring points supported by the closed-loop scene; or, the closed-loop monitoring capability information includes a closed-loop monitoring point supported by the closed-loop scene and a monitoring type corresponding to the closed-loop monitoring point.

Illustratively, the at least one closed-loop monitoring point includes at least one of: an intention translation monitoring point, a perception monitoring point, a network analysis monitoring point, a decision monitoring point or an execution monitoring point; wherein the intent translation monitoring point is used to indicate a process or result of monitoring intent translation to a particular management task or policy; the perception monitoring point is used for indicating the process or the result of the monitoring network perception; the network analysis monitoring point is used for indicating the process or the result of monitoring the network analysis; the decision monitoring point is used for indicating the process or the result of monitoring a decision; the execution monitoring point is used for indicating the result of monitoring execution.

In an optional embodiment, the closed-loop monitoring request further includes a 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; when the monitoring type of one closed-loop monitoring point is monitoring, indicating that the interruption is not needed, and continuously executing a closed-loop process; when the monitoring type of a closed loop monitoring point is monitoring and controlling, the closed loop flow is indicated to be interrupted to wait for confirmation.

In a specific implementation manner, the communication interface 801 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.

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, 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 points comprise at least one of coverage problem detection monitoring points, abnormal cell identification monitoring points and coverage optimization scheme suggestion monitoring points; the decision monitoring point determines a monitoring point for a coverage optimization scheme; the execution monitoring point is a coverage optimization scheme execution monitoring point; the coverage optimization intention translation monitoring point is used for indicating and monitoring a coverage optimization intention translation execution result; the coverage performance detection monitoring point is used for indicating a monitoring coverage performance index; the coverage problem detection monitoring point is used for indicating the coverage problem of a monitoring cell or a monitoring area level; the abnormal cell identification monitoring point is used for indicating to monitor an abnormal cell; the coverage optimization scheme suggests that the monitoring point is used for indicating at least one coverage optimization scheme to be selected for monitoring and solving the coverage problem; the coverage optimization scheme determination monitoring point is used for indicating the monitoring to determine a coverage optimization scheme for solving the coverage problem; the coverage optimization scheme execution monitoring point is used for indicating the execution of the monitoring coverage optimization scheme.

Specifically, when the monitoring type of a closed-loop monitoring point is monitoring, the processor 802 is further configured to continue to execute a closed-loop process when the closed-loop monitoring point is reached; 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 the closed-loop monitoring point is reached, and wait for confirmation information of the closed-loop monitoring functional unit.

Based on the above embodiments, the present application provides a system, which may include the closed-loop monitoring function unit and the closed-loop execution function unit related to the above embodiments.

[ claim 15.04.2021 according to rules 91 ] embodiments of the present application further provide a computer-readable storage medium for storing a computer program, where when the computer program is executed by a computer, the computer can implement any one of the network automation management methods provided by the above method embodiments.

[ claim 1] correct 15.04.2021 according to rules 91 ] this application further provides a computer program product, where the computer program product is used to store a computer program, and when the computer program is executed by a computer, the computer can implement any one of the network automation management methods provided by the above method embodiments.

[ claim 15.04.2021 according to rules 91 ] this application further provides a chip, including a processor and a communication interface, where the processor is coupled to a memory, and is configured to call a program in the memory, so that the chip implements any one of the network automation management methods provided by the above method embodiments.

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

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

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

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

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

Claims

[ correction according to rule 91 15.04.2021]
A network automation management method is applied to a network closed loop automation process, and is characterized by comprising the following steps:

the method comprises the steps that a closed-loop monitoring function unit obtains closed-loop monitoring capacity information of a closed-loop scene, wherein the closed-loop monitoring capacity information is used for representing the closed-loop monitoring capacity supported by the closed-loop scene;

the closed-loop monitoring functional unit determines at least one closed-loop monitoring point of the closed-loop scene according to the closed-loop monitoring capability information of the closed-loop scene;

the closed-loop monitoring function unit sends a closed-loop monitoring request to a closed-loop execution function unit, wherein the closed-loop monitoring request comprises the information of the closed-loop scene and the information of the at least one closed-loop monitoring point;

and the closed-loop monitoring function unit receives a monitoring notice corresponding to the at least one closed-loop monitoring point from the closed-loop execution function unit, wherein the monitoring notice carries the identification and the monitoring information of the corresponding closed-loop monitoring point.
The method of claim 1, wherein the method further comprises:

the closed-loop monitoring capability information comprises closed-loop monitoring points supported by the closed-loop scene; or

The closed-loop monitoring capability information comprises closed-loop monitoring points supported by the closed-loop scene and monitoring types corresponding to the closed-loop monitoring points.
The method of claim 1 or 2, wherein determining, by a closed-loop monitoring function, at least one closed-loop monitoring point of the closed-loop scenario according to closed-loop monitoring capability information of the closed-loop scenario comprises:

and the closed-loop monitoring functional unit determines the at least one closed-loop monitoring point according to the closed-loop monitoring capability information and the monitoring requirement of the closed-loop monitoring functional unit.
A method according to any one of claims 1-3, wherein the at least one closed-loop monitoring point comprises at least one of: an intention translation monitoring point, a perception monitoring point, a network analysis monitoring point, a decision monitoring point or an execution monitoring point;

wherein the intent translation monitoring point is used for indicating the process or result of monitoring intent translation into a management task or policy; the perception monitoring point is used for indicating the process or the result of the monitoring network perception; the network analysis monitoring point is used for indicating the process or the result of monitoring network analysis; the decision monitoring point is used for indicating the process or the result of the monitoring decision; the execution monitoring point is used for indicating the result of monitoring execution.
The method of any one of claims 1-4, further comprising:

the closed-loop monitoring functional unit determines a monitoring type corresponding to the at least one closed-loop monitoring point according to the closed-loop controllable capability information; the monitoring type of any closed-loop monitoring point is monitoring or monitoring and controlling;

when the monitoring type of one closed-loop monitoring point is monitoring, indicating that interruption is not needed, and continuously executing a closed-loop process; when the monitoring type of a closed loop monitoring point is monitoring and controlling, the closed loop flow is indicated to be interrupted to wait for confirmation.
The method of claim 5, wherein the closed-loop monitoring request further comprises a monitoring type corresponding to the at least one closed-loop monitoring point.
The method of any one of claims 1-6, further comprising:

the closed-loop monitoring function unit sends monitoring confirmation information to the closed-loop execution function unit, wherein the monitoring confirmation information comprises identification and a confirmation result of a monitoring point;

wherein the confirmation result includes at least one of:

when the closed-loop monitoring point is an intention translation monitoring point, the closed-loop monitoring functional unit confirms an intention translation result of a closed-loop execution functional unit and instructs the closed-loop execution functional unit to continue executing a closed-loop process;

when the closed-loop monitoring point is an intention perception monitoring point, the closed-loop monitoring functional unit confirms the network abnormity found 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 closed-loop monitoring functional unit confirms one of the following items: confirming that the closed-loop execution functional unit detects or finds a network problem, and indicating the closed-loop execution functional unit to continue executing a closed-loop process; or, confirming the reason of the network problem analyzed by the closed-loop execution functional unit, and indicating the closed-loop execution functional unit to continue executing the closed-loop flow; or, confirming the network adjustment scheme suggested by the closed-loop execution functional unit, and instructing the closed-loop execution functional unit to continue executing the closed-loop process;

when the closed-loop monitoring point is a decision monitoring point, the closed-loop monitoring functional unit confirms the network adjustment scheme selected by the closed-loop execution functional unit and instructs the closed-loop execution functional unit to continue executing a closed-loop process;

and when the closed-loop monitoring point is an execution monitoring point, the closed-loop monitoring functional unit confirms an execution result of the closed-loop execution functional unit on a network adjustment scheme.
The method of claim 4, wherein the at least one closed-loop monitoring point is at least one coverage-optimized closed-loop monitoring point when the closed-loop scenario is a coverage-optimized scenario, 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 comprises at least one of a coverage problem detection monitoring point, an abnormal cell identification monitoring point and a coverage optimization scheme suggestion monitoring point; the decision monitoring point determines a monitoring point for a coverage optimization scheme; the execution monitoring point is a coverage optimization scheme execution monitoring point;

the coverage optimization intention translation monitoring point is used for indicating and monitoring a coverage optimization intention translation execution result;

the coverage performance detection monitoring point is used for indicating a monitoring coverage performance index;

the coverage problem detection monitoring point is used for indicating the coverage problem of a monitoring cell or an area level;

the abnormal cell identification monitoring point is used for indicating to monitor an abnormal cell;

the coverage optimization scheme suggests a monitoring point for indicating at least one coverage optimization scheme to be selected for monitoring and solving the coverage problem;

the coverage optimization scheme determination monitoring point is used for indicating the monitoring to determine a coverage optimization scheme for solving the coverage problem;

the coverage optimization scheme execution monitoring point is used for indicating the execution of the monitoring coverage optimization scheme.
The method of any one of claims 1-8, wherein the closed-loop monitoring capability information is coverage optimization closed-loop monitoring capability information when the closed-loop scenario is a coverage optimization scenario.
The method of claim 7, wherein when the closed-loop scenario is a coverage optimization scenario,

when the closed-loop monitoring point is a coverage optimization intention translation monitoring point, the confirmation information is coverage optimization intention translation result confirmation information, and the coverage optimization intention translation result confirmation information is used for indicating a closed-loop execution functional unit to continue executing a 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 for instructing a closed-loop execution functional unit to continue executing a coverage optimization closed-loop process to process 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 for instructing a closed-loop execution functional unit to continue executing a coverage optimization closed-loop process to process the abnormal cell;

and when the closed-loop monitoring point determines the monitoring point for the coverage optimization scheme, the confirmation information is coverage adjustment scheme confirmation information, and the coverage adjustment scheme confirmation information is used for instructing the closed-loop execution functional unit to continue executing the coverage adjustment prevention scheme.
The method of any of claims 1-10, wherein the closed-loop monitoring function is a cross-domain management unit and the closed-loop execution function is a domain management unit.
[ correction according to rule 91 15.04.2021]
A network automation management method is applied to a network closed loop automation process, and is characterized by comprising the following steps:

the closed-loop execution functional unit receives a closed-loop monitoring request sent by the closed-loop monitoring functional unit, wherein the closed-loop monitoring request comprises information of a closed-loop scene and information of at least one closed-loop monitoring point;

in the closed-loop operation process of the closed-loop scene, the closed-loop execution functional unit acquires the monitoring information of the closed-loop monitoring point when executing to the at least one closed-loop monitoring point, and sends a monitoring notice to the closed-loop monitoring functional unit, wherein the closed-loop monitoring notice carries the identifier of the closed-loop monitoring point and the monitoring information.
The method of claim 12, wherein the method further comprises:

the closed-loop execution functional unit sends closed-loop monitoring capability information of the closed-loop scene to the closed-loop monitoring functional unit, wherein the closed-loop monitoring capability information is used for representing the closed-loop monitoring capability supported by the closed-loop scene; wherein the closed-loop monitoring capability information comprises closed-loop monitoring points supported by the closed-loop scene; or, the closed-loop monitoring capability information includes a closed-loop monitoring point supported by the closed-loop scene and a monitoring type corresponding to the closed-loop monitoring point.
The method of any of claims 12-13, wherein the at least one closed-loop monitoring point comprises at least one of: an intention translation monitoring point, a perception monitoring point, a network analysis monitoring point, a decision monitoring point or an execution monitoring point;

wherein the intent translation monitoring point is used to indicate a process or result of monitoring intent translation to a particular management task or policy; the perception monitoring point is used for indicating the process or the result of the monitoring network perception; the network analysis monitoring point is used for indicating the process or the result of monitoring the network analysis; the decision monitoring point is used for indicating the process or the result of the monitoring decision; the execution monitoring point is used for indicating the result of monitoring execution.
The method according to any one of claims 12-14, wherein the closed-loop monitoring request further includes a 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;

when the monitoring type of one closed-loop monitoring point is monitoring, indicating that interruption is not needed, and continuously executing a closed-loop process; when the monitoring type of a closed loop monitoring point is monitoring and controlling, the closed loop flow is indicated to be interrupted to wait for confirmation.
The method of any one of claims 12-15, further comprising:

and the closed-loop execution unit receives monitoring confirmation information from the closed-loop monitoring function unit, wherein the monitoring confirmation information comprises a monitoring point identifier and a confirmation result.
The method of claim 14, wherein the at least one closed-loop monitor point is at least one coverage-optimized closed-loop monitor point when the closed-loop scenario is a coverage-optimized scenario, 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 comprises at least one of a coverage problem detection monitoring point, an abnormal cell identification monitoring point and a coverage optimization scheme suggestion monitoring point; the decision monitoring point determines a monitoring point for a coverage optimization scheme; the execution monitoring point is a coverage optimization scheme execution monitoring point;

the coverage optimization intention translation monitoring point is used for indicating and monitoring a coverage optimization intention translation execution result;

the coverage performance detection monitoring point is used for indicating a monitoring coverage performance index;

the coverage problem detection monitoring point is used for indicating the coverage problem of a monitoring cell or an area level;

the abnormal cell identification monitoring point is used for indicating to monitor an abnormal cell;

the coverage optimization scheme suggests that the monitoring point is used for indicating at least one coverage optimization scheme to be selected for monitoring and solving the coverage problem;

the coverage optimization scheme determination monitoring point is used for indicating the monitoring to determine a coverage optimization scheme for solving the coverage problem;

the coverage optimization scheme execution monitoring point is used for indicating the execution of the monitoring coverage optimization scheme.
The method of claim 15, wherein the method further comprises:

when the monitoring type of a closed-loop monitoring point is monitoring, the closed-loop execution functional unit continues to execute a closed-loop process when executing to the closed-loop monitoring point;

when the monitoring type of a closed-loop monitoring point is monitoring and controlling, the closed-loop execution functional unit suspends the closed-loop flow when executing to the closed-loop monitoring point, and waits for the confirmation information of the closed-loop monitoring functional unit.
The method of claim 13, wherein the closed-loop monitoring capability information is coverage optimization closed-loop monitoring capability information when the closed-loop scenario is a coverage optimization scenario.
The method of any of claims 12-19, wherein the closed-loop monitoring function is a cross-domain management unit and the closed-loop execution function is a domain management unit.
A closed loop monitoring function comprising means or modules for performing the method of any one of claims 1-11.
A closed loop execution function comprising means or modules for performing the method of any of claims 12-20.
A closed-loop monitor function comprising a processor and a communication interface, wherein:

the communication interface is used for receiving and transmitting data or information;

the processor, coupled to the memory, for invoking a program in the memory to cause the closed-loop monitoring function to perform the method of any of claims 1-11.
A closed-loop executive function unit comprising a processor and a communication interface, wherein:

the communication interface is used for receiving and transmitting data or information;

the processor, coupled to the memory, to invoke the program in the memory to cause the closed-loop execution functional unit to perform the method of any of claims 12-20.
A computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the method of any of claims 1-11, or that, when executed on a computer, cause the computer to perform the method of any of claims 12-20.
A communication system comprising a closed-loop supervision function according to claim 21 and a closed-loop execution function according to claim 22.
A computer program product comprising instructions which, when run on a communication apparatus, cause the communication apparatus to perform the method of any one of claims 1-11 or to perform the method of any one of claims 12-20.