WO2023072023A1 - Intention execution method and apparatus - Google Patents

Abstract

The present application provides an intention execution method. The method comprises: an intention execution network element receives execution sequence information from an intention knowledge base, the execution sequence information being used for indicating the sequence of executing a first operation of a first intention and a second operation of the first intention; the intention execution network element determines, according to the execution sequence information, a sending sequence of the intention execution network element sending the first operation to a first network element and the intention execution network element sending the second operation to a second network element; the intention execution network element sends the first operation to the first network element and sends the second operation to the second network element according to the sending sequence. The situation that the intention operation execution fails or does not achieve an expected effect due to the fact that execution is not performed in sequence is avoided, and the reliability of a system executing intentions is improved.

Description

A method and device for intent execution

This application claims priority to a Chinese patent application with application number 202111278495.0 and titled "A Method and Apparatus Intended to Perform" filed with the State Intellectual Property Office of China on October 30, 2021, the entire contents of which are incorporated by reference at In this application.

technical field

The present application relates to the field of communication technology, and more particularly, to a method and apparatus intended to be implemented.

Background technique

Cognitive network management systems are currently available as users automate work. Cognitive network management systems support the processing of intent, where intent is the expectation of an acting system. In order to achieve the intention, multiple network devices need to respectively perform multiple intended operations, for example, multiple network devices respectively perform multiple sub-operations in the intended operation. Whether each network device performs an operation successfully or not will affect the effect of the intention after execution. However, the current management mechanism for intention operations does not take into account the cooperative management between multiple operations, resulting in low success rate and effect of intention achievement. Therefore, there is an urgent need for an intention execution method that can improve the system Reliability of carrying out intentions.

Contents of the invention

The present application provides an intent execution method and device, which can improve the reliability of the intent execution system.

In the first aspect, there is provided an intent execution method, the method may be executed by an intent execution network element or a chip in the intent execution network element, the method includes: the intent execution network element receives execution sequence information from the intent knowledge base, the execution sequence The information is used to indicate the order of executing the first operation of the first intention and the second operation of the first intention; the intention execution network element determines the intention execution network element to send the first operation and the intention execution network element to the first network element according to the execution sequence information The sending order of sending the second operation to the second network element; the intention execution network element sends the first operation to the first network element and sends the second operation to the second network element according to the sending order.

Therefore, in this application, the intention execution network element can determine the sending order of multiple operations according to the order in which multiple operations are executed, so that multiple operations can be executed in order, so that multiple operations can cooperate with each other, avoiding due to Failure to execute in order leads to the failure of the execution of the intended operation or the failure to achieve the expected effect, which improves the reliability of the system to execute the intention.

With reference to the first aspect, in some implementations of the first aspect, the method further includes: the network element intending to execute receives the execution result information of the first operation from the first network element; the network element intending to execute determines the first operation according to the execution result information Whether the execution is successful.

Therefore, in this application, the intent execution network element can receive the execution result information of the operation, and judge whether the operation is successfully executed according to the execution result information, so as to monitor the execution status of the operation and improve the reliability of the system execution intent.

With reference to the first aspect, in some implementations of the first aspect, the method further includes: the intention execution network element receives first indication information from the intention knowledge base, and the first indication information is used to instruct the intention execution network element to determine whether the first operation execution succeed.

Therefore, in this application, the intention execution network element can obtain the first indication information from the intention knowledge base, and determine whether the operation is successfully executed according to the first indication information, so as to improve the reliability of the system for executing the intention.

With reference to the first aspect, in some implementation manners of the first aspect, sending the first operation to the first network element and sending the second operation to the second network element by the network element intending to execute according to the sending order includes: sending the operation to the second network element by the network element intended to execute The first network element sends the first operation, and in the case that the intended execution network element determines that the first operation is executed successfully, the intended execution network element sends the second operation to the second network element.

Therefore, in this application, the intent-executing network element can issue subsequent operations after determining that the pre-order operations are executed successfully, so as to avoid performing subsequent operations because the pre-order operations have not been successfully executed, resulting in operation failure or execution effect poor.

With reference to the first aspect, in some implementation manners of the first aspect, the method further includes: the intention execution network element receives progress indication information, the progress indication information is used to indicate that the intention execution network element needs to feed back progress information, and the progress information is used to indicate the first The execution progress of the first operation and the second operation; the intention execution network element sends progress information according to the progress indication information.

Therefore, in this application, the network element intending to execute can be required to feed back the execution progress of the operation, so that the execution status of the operation can be monitored and the reliability of the system executing the intent can be improved.

With reference to the first aspect, in some implementation manners of the first aspect, the progress indication information is further used to indicate the cycle or frequency at which the schematic execution network element needs to feed back the progress information.

Therefore, in this application, the network element intending to execute may be required to feed back the execution progress of the operation periodically or by frequency, so that the execution status of the operation can be monitored and the reliability of the system execution intent can be improved.

In a second aspect, an intention execution device is provided, the apparatus includes a processing unit and a transceiver unit, the transceiver unit is configured to receive execution sequence information from the intent knowledge base, and the execution sequence information is used to indicate the execution of the first operation of the first intent and the order of the second operation of the first intention; the processing unit is configured to determine, according to the execution sequence information, that the network element intending to execute sends the first operation to the first network element and that the network element intending to execute sends the second operation to the second network element Sequence; the transceiver unit is further configured to send the first operation to the first network element and send the second operation to the second network element according to the sending sequence.

Therefore, in this application, the intention execution network element can determine the sending order of multiple operations according to the order in which multiple operations are executed, so that multiple operations can be executed in order, so that multiple operations can cooperate with each other, avoiding due to Failure to execute in order leads to the failure of the execution of the intended operation or the failure to achieve the expected effect, which improves the reliability of the system to execute the intention.

With reference to the second aspect, in some implementations of the second aspect, the transceiver unit is further configured to receive execution result information of the first operation from the first network element; the processing unit is further configured to determine the first operation according to the execution result information Whether the execution is successful.

With reference to the second aspect, in some implementations of the second aspect, the transceiver unit is further configured to receive first indication information from the first network element, and the first indication information is used to instruct the schematic execution network element to determine whether the first operation is performed success.

With reference to the second aspect, in some implementation manners of the second aspect, the transceiver unit is specifically configured to send the first operation to the first network element, and when it is determined that the first operation is successfully performed, send the second operation to the second network element. Two operations.

With reference to the second aspect, in some implementations of the second aspect, the transceiver unit is further configured to receive progress indication information, the progress indication information is used to indicate that the device needs to feed back progress information, and the progress information is used to indicate the first operation and the second operation. The execution progress of the operation; the processing unit is also used to send progress information according to the progress indication information.

With reference to the second aspect, in some implementation manners of the second aspect, the progress indication information is also used to indicate the period or frequency at which the device needs to feed back the progress information.

In a third aspect, there is provided a method for executing an intent, the method may be executed by a network element for executing the intent or a chip in the network element for executing the intent, the method includes: the network element for executing the intent receives the first intent from the first network element Execution result information of an operation; the network element intending to execute determines that the execution of the first operation is abnormal according to the execution result information; the network element intending to execute sends rollback indication information to the second network element, and the rollback indication information is used to indicate rollback of the first operation The intent's second action.

Therefore, in this application, if the execution of a certain operation of the first intent is abnormal, other operations that have been executed by the first intent can be rolled back, so as to avoid the resources and signaling caused by other operations of the first intent being executed all the time. Waste, which in turn can improve the execution efficiency of intentions.

With reference to the third aspect, in some implementation manners of the third aspect, the method further includes: the intention execution network element receives second indication information from the intention knowledge base, and the second indication information is used to instruct the intention execution network element to determine the first operation An exception occurred during execution.

With reference to the third aspect, in some implementation manners of the third aspect, the method further includes: the intent execution network element receives fallback scheme information from the intent knowledge base, where the rollback scheme information is used to indicate the rollback mode of the second operation, and returns The rollback indication information is also used to indicate a rollback mode of the second operation.

Therefore, in this application, the intent execution network element can indicate the rollback mode of the rollback operation to the network element that performs the operation, so as to prevent the network element that does not have the rollback capability from being unable to roll back the operation successfully, and improves the reliability of the system to execute the intent .

With reference to the third aspect, in some implementation manners of the third aspect, the method further includes: the intended execution network element determines the fallback mode of the second operation according to the execution result information and the fallback scheme information.

Therefore, in this application, when the intended execution network element determines that the execution of the first operation is abnormal, the intended execution network element can determine which type of abnormality the exception belongs to according to the execution result information, and determine that in this abnormal situation according to the fallback plan information Next, determine the rollback scheme information of the second operation to determine the rollback mode of the second operation, which improves the reliability of the system execution intention.

With reference to the third aspect, in some implementation manners of the third aspect, the method further includes: the intention execution network element receives progress indication information, the progress indication information is used to indicate that the intention execution network element needs to feed back progress information, and the progress information is used to indicate the first The execution progress of the first operation and the second operation; the intention execution network element sends progress information according to the progress indication information.

Therefore, in this application, the network element intending to execute can be required to feed back the execution progress of the operation, so that the execution status of the operation can be monitored and the reliability of the system executing the intent can be improved.

With reference to the third aspect, in some implementation manners of the third aspect, the progress indication information is further used to indicate the period or frequency at which the schematic execution network element needs to feed back the progress information.

Therefore, in this application, the network element intending to execute may be required to feed back the execution progress of the operation periodically or by frequency, so that the execution status of the operation can be monitored and the reliability of the system execution intent can be improved.

In a fourth aspect, there is provided a device for intention execution, the device includes a processing unit and a transceiver unit, the transceiver unit is configured to receive execution result information of a first operation of the first intent from a first network element; the processing unit is configured to According to the execution result information, it is determined that the execution of the first operation is abnormal; the transceiver unit is further configured to send rollback instruction information to the second network element, where the rollback instruction information is used to indicate the rollback of the second operation with the first intention.

Therefore, in this application, if the execution of a certain operation of the first intent is abnormal, other operations that have been executed by the first intent can be rolled back, so as to avoid the resources and signaling caused by other operations of the first intent being executed all the time. Waste, which in turn can improve the execution efficiency of intentions.

With reference to the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to receive second indication information from the intent knowledge base, where the second indication information is used to indicate that the execution network element determines that the execution of the first operation is abnormal .

With reference to the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to receive rollback scheme information from the intent knowledge base, the rollback scheme information is used to indicate the rollback mode of the second operation, and the rollback indication The information is also used to indicate the fallback mode of the second operation.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, the processing unit is further configured to determine a rollback mode of the second operation according to the execution result information and the rollback scheme information.

With reference to the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to receive progress indication information, the progress indication information is used to indicate that the device needs to feed back progress information, and the progress information is used to indicate the first operation and the second operation. The execution progress of the operation; the sending and receiving unit is also configured to send progress information according to the progress indication information.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, the progress indication information is further used to indicate the period or frequency at which the schematic execution network element needs to feed back the progress information.

According to a fifth aspect, a communication device is provided, and the device may include a processing unit, a sending unit, and a receiving unit. Optionally, the sending unit and the receiving unit may also be transceiver units.

When the device is intended to execute a network element, the processing unit may be a processor, and the sending unit and the receiving unit may be transceivers; the device may also include a storage unit, which may be a memory; the storage unit is used for storing An instruction, the processing unit executes the instruction stored in the storage unit, so that the intent-to-execute network element executes any method of the first aspect or the third aspect. When the device is intended to execute a chip in a network element, the processing unit may be a processor, and the sending unit and receiving unit may be input/output interfaces, pins or circuits, etc.; the processing unit executes the instructions stored in the storage unit , so that the chip executes the method of the first aspect or the third aspect. The storage unit is used to store instructions, and the storage unit may be a storage unit in the chip (for example, a register, a cache, etc.), or a storage unit outside the chip in the intention execution network element (for example, a read-only memory, random access memory, etc.).

In a sixth aspect, a communication device is provided, including a processor and an interface circuit, and the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or send signals from the processor For other communication devices other than the communication device, the processor is used to implement any method of the aforementioned first aspect or third aspect through a logic circuit or executing code instructions.

In a seventh aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored, and when the computer program or instruction is executed, any one of the aforementioned first aspect or third aspect can be realized. method.

In an eighth aspect, a computer program product containing instructions is provided, and when the instructions are executed, any method of the aforementioned first aspect or third aspect is implemented.

In a ninth aspect, a computer program is provided, the computer program includes codes or instructions, and when the codes or instructions are executed, the method in any possible implementation manner of the aforementioned first aspect or the third aspect is implemented.

In a tenth aspect, a chip system is provided, and the chip system includes a processor and may further include a memory, configured to implement at least one method described in the foregoing first aspect or third aspect. The system-on-a-chip may consist of chips, or may include chips and other discrete devices.

In an eleventh aspect, a communication system is provided, and the system includes the device in any one of the second aspect or the fourth aspect.

In some implementation manners, the first network element may be a first network device, and the second network element may be a second network device.

Description of drawings

Fig. 1 is a schematic diagram of a system applicable to the implementation of the intention provided by the embodiment of the present application.

Fig. 2 is a schematic flowchart of an example of an intent execution method provided by an embodiment of the present application.

Fig. 3 is a schematic flowchart of another example of an intention execution method provided by an embodiment of the present application.

Fig. 4 is a schematic flowchart of an example of an operation method for rollback during intent execution provided by an embodiment of the present application.

FIG. 5 is a schematic flowchart of another example of an operation method for rollback during intent execution provided by an embodiment of the present application.

Fig. 6 is a schematic flowchart of an example of information query by network elements intended to be executed according to the embodiment of the present application.

FIG. 7 and FIG. 8 are schematic structural diagrams of a possible communication device provided by an embodiment of the present application.

Detailed ways

The technical solution in this application will be described below with reference to the accompanying drawings.

The technical solution of this application can be applied to various types of network function virtualization (network function virtualization, NFV) systems, and the system can use standard formal language to integrate the current operator's business technical solutions, network construction solutions and network operation and maintenance methods It is described as patterns and strategies, and based on these patterns and strategies, technical solutions and construction plans are realized. For example, the technical solution of the present application can be applied to one or more of the following systems: wireless intent driven network (wireless intent driven network, wIDN) system, experiential networked intelligence (ENI) system, intent driven management service ( intent driven management service (IDMS) system or open network automation platform (open network automation platform, ONAP) system, etc.

For clarity, some terms in the embodiments of the present application are explained below.

Intent: Refers to the expectations of the acting system. An intent can include one or more of the following: requirements, intent goals, and constraints.

Intent instance: the object after instantiating the intent. For example, in this application, an intent can be replaced with an instance of an intent.

Intent expression: an expression used to carry an intention, and the expression includes one or more of the following: intention action name, intention action attribute, intention action object name or intention action object attribute. Intent expressions have specific syntax and semantics.

Intent goal: used to indicate the target value that the intention needs to achieve.

Intent translation: the process of converting an intent into an intent executable command or rule or sub-intent.

Intention execution: issue the executable commands, sub-intents, and rules of the intent, and adjust the executable commands, sub-intents, and rules according to the network environment and the achievement of the intent.

Intention-executable commands: A series of instructions formed by intentions through operations such as translation decisions.

Intent mode: specifies the syntax and semantics of intent expressions. The intent pattern may include one or more of the following: fields, value ranges of fields, types of fields, and hierarchical relationships between fields. For example, fields can be used to describe the type, name, or consumer of the intent schema.

Intent state: Intent state includes activation state, conflict state, deactivation state or sleep state, etc. Among them, the intention being in the active state can be understood as the intention being executed; the intention being in the conflicting state can be understood as the intention conflicting with the intention in the system; the intention being in the deactivated state can be understood as the intention not being executed; the intention being in the sleeping state can be understood It is understood that the intended goal of the intention has been temporarily suspended due to long-term failure to achieve it.

Intent creation: Create a new intent in the intent system and create a corresponding intent context.

Intention knowledge: Intent knowledge is the relevant parameters of the intent pattern stored in the intent knowledge base. For example, the above-mentioned relevant parameters may include one or more of the following: the executable operation corresponding to the intent, the identifier of the entity that acts on the intent, or the type of the entity that acts on the intent.

Intent operation: the executable operation corresponding to the intent target. An intent action consists of one or more intent sub-actions.

Intention sub-operation: a component of an intention operation, an intent sub-operation may include one or more operation instructions, and the one or more operation instructions are executed by an execution object.

Intention maintenance: adjust the executable operations of the intention according to the changes of the system network environment, in order to achieve the intention goal.

Intention achievement: the system detects that the KPI value in the network reaches the target value in the intention expression, or the intention goal is achieved.

In order to facilitate the understanding of the embodiment of the present application, the intended system applicable to the method provided by the embodiment of the present application will first be described in detail with reference to FIG. 1 . FIG. 1 shows a schematic diagram of a system 100 suitable for processing intentions of the method provided by the embodiment of the present application. As shown in FIG. 1 , the system 100 includes an intended consumption network element 110 , an intended provision network element 120 , and a network device 130 . The intention providing network element may include an intention management network element 121 , an intention translation network element 122 , an intention execution network element 123 , and a knowledge management network element 124 . Wherein, the knowledge management network element 124 may include an intent knowledge base.

The intended consumption network element 110, also called the intended consumer, is the intended consumer. For example, the intended consumption network element 110 may be an operation support system (operations support systems, OSS), a business support system (business support systems, BSS), an application (application, APP) or other user equipment. For an IDMS system, the intended consumption network element 110 may be a service consumer or a management service (management service, MnS) network element, such as a network management system (network management system, NMS). The intention consuming network element 110 may communicate with the intention providing network element 120 , for example, the intention consuming network element 110 may send a request for creating or implementing an intention to the intention providing network element 120 .

The intention management network element 121 can be used for managing the intention mode, it can receive the request information from the intention consumption network element 110, and process the request information. The intent management network element 121 may include an intent schema library, which is used to store intent schemas. The intent management network element 121 may also include an intent instance library, through which the intent management network element 121 may obtain state information of an intent mode, an intent target, and an operation corresponding to the intent.

The intent translation network element 122 may receive translation request information from the intent management network element 121 to implement the intent translation function. The intent translation network element 122 can also acquire the intent pattern from the intent management network element 121 , and check the syntax and semantics of the information provided by the intent consumption network element 110 .

The intent execution network element 123 may receive commands from the intent management network element 122 and the intent translation network element 121, and implement operations related to the intent.

The knowledge management network element 124 can manage the intent knowledge base, which stores the relevant knowledge of the intent, and the knowledge management network element can support other network elements to query the relevant knowledge of the intent.

It should be noted that systems with different processing intents may also include other network elements with corresponding functions.

For example, for a wIDN system, the system may also include a knowledge management network element and an intent knowledge base. Wherein, the intent management network element is used for managing intent knowledge. The intent knowledge base may be a sub-module of the knowledge management network element, and is used to store intent knowledge. The intent management network element may also include an intent pattern repository and an intent instance repository, where the intent pattern repository is used to store intent patterns, and the intent instance repository is used to store intents.

For the ENI system, the ENI system may also include one or more of the following: an input function network element, an output function network element, an analysis function network element, and a decision function network element. Wherein, the input function network element may include a data collection network element and a normalization network element, which are used for receiving data from an external system and performing operations such as normalizing the data. The output function network element may include an output network element and a denormalization network element, which are used to convert the system internal command into a format that the external system can process and send it to the external system. The analysis function network element can be used to sense and analyze the existing network state and predict the future network state. For example, the analysis function network element may include a knowledge management network element, a context awareness network element and a cognitive management network element. Among them, the knowledge management network element can manage the intention knowledge, the context awareness network element can perceive and analyze the existing network status, and the cognitive management network element can perform management analysis. The aforementioned intent management network element and intent translation network element may be sub-network elements in the analysis function network element. The decision-making function network element is used to generate new operation commands according to the policy target on the basis of awareness of the network state, arrange the operation commands, and send the operation commands to the output network element. The decision-making function network element can include policy management network elements , a context-aware network element and a drive management network element, wherein the policy management network element is used to manage intent policies, the context-aware network element is used to sense and analyze network status, and the drive management network element is used to perform drive management of intent.

For the IDMS system, the intended consumption network element can be the network management system (network management system, NMS), the intended provision network element can be the equipment management system (element management system, EMS), the intention management network element, the intention translation network element and the intention execution A network element may be a sub-module intended to provide a network element.

The assistance system 130 may include at least one network device, and each network device may communicate with the intent providing network element 120, for example, the intent execution network element 123 in the intent providing network element 120 may send a message to any network device in the assistance system 130 An intent to perform an action request.

In this embodiment of the present application, the network device in the assistance system 130 may be any kind of device with a wireless transceiver function. The equipment includes but is not limited to: evolved Node B (evolved Node B, eNB), radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (base station controller, BSC) , base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), satellite, drone base station, wireless fidelity (wireless access point (access point, AP), wireless relay node, wireless backhaul node, transmission point (transmission point, TP) or transmission and reception point (transmission and reception point, TRP) in the fidelity (WiFi) system, etc. It can be 5G, such as NR, a gNB in the system, or a transmission point (TRP or TP), one or a group (including multiple antenna panels) antenna panels of a base station in a 5G system, or it can also be an antenna panel that constitutes a gNB Or a network node of a transmission point, such as a baseband unit (BBU), or a distributed unit (distributed unit, DU), etc.

In some deployments, a gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). CU implements some functions of gNB, and DU implements some functions of gNB. For example, CU is responsible for processing non-real-time protocols and services, implementing radio resource control (radio resource control, RRC), packet data convergence protocol (packet data convergence protocol, PDCP) layer function. The DU is responsible for processing physical layer protocols and real-time services, realizing the functions of the radio link control (radio link control, RLC) layer, medium access control (medium access control, MAC) layer and physical (physical, PHY) layer. The AAU implements some physical layer processing functions, radio frequency processing and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be transformed from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU , or, sent by DU+AAU. It can be understood that the network device may be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU can be divided into network devices in an access network (radio access network, RAN), and the CU can also be divided into network devices in a core network (core network, CN), which is not limited in this application.

It should be noted that the solution of this application can be applied to other systems including corresponding network elements, which is not limited in this application. It can be understood that the above-mentioned network element or function may be a network element in a hardware device, or a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform). Optionally, the foregoing network element or function may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.

At present, in order to achieve the goal of the intent, multiple network devices need to perform multiple operations of the intent respectively. The success or failure of each operation will affect the effect of the intention after execution. However, the current management mechanism for intention operation does not take into account the cooperative management between operations, resulting in low success rate and effect of intention achievement. reliability.

FIG. 2 shows a schematic flowchart of an example of an intent execution method 200 provided by the present application.

S201. The intent execution network element receives execution sequence information from the intent knowledge base.

The execution sequence information is used to indicate the sequence of executing the first operation of the first intent and the second operation of the first intent.

The execution sequence information may be stored in the intent knowledge base during the initialization and update process of the intent knowledge base, where the intent knowledge base may be a submodule of the knowledge management network element.

Wherein, the first operation may include multiple operation instructions, and may be completely executed by the first network element (for example, network device #1); the second operation may also include multiple operation instructions, and may be completely executed by the second network element (for example, network device #1). Device #2) is fully implemented.

There may be a dependency between the first operation and the second operation.

For example, the execution of the second operation by the second network element depends on the successful execution of the first operation by the first network element.

The first operation of the first intent and the second operation of the first intent may be one or more sub-operations of the intent operation corresponding to the first intent. For example, the intent operation corresponding to the first intent includes three sub-operations, namely: a first sub-operation, a second sub-operation, and a third sub-operation. The execution object of the first sub-operation is the first network element, and the execution object of the second sub-operation and the third sub-operation is the second network element. If the three sub-operations are performed in the order of the first sub-operation, the second sub-operation, and the third sub-operation, the first operation in this embodiment of the application may be the first sub-operation, and the second operation may be the second sub-operation A combined operation of the operation and the third sub-operation; if the three sub-operations are performed in the order of the second sub-operation, the first sub-operation, and the third sub-operation, the first operation in the embodiment of the present application can be the first sub-operation , the second operation may be the second sub-operation, and the embodiment of the present application also includes a third operation of the first intention, the third operation is the third sub-operation, and the execution order information may be used to indicate the first operation, the second operation and the order of the third operation.

It should be understood that the present application does not limit the number of multiple operations in the order in which the execution sequence information indicates the execution of multiple operations, nor does it limit the number of execution objects that need to perform operations. This is an example rather than a limitation, with the first intention The intended target is the relocation of the community as an example. The intention operation of the first intention includes 6 sub-operations, and the 6 sub-operations are:

The first sub-operation: delete the neighbor relationship with cell A, which is executed by the first network element;

The second sub-operation: deactivate cell A, performed by the second network element;

The third sub-operation: delete cell A, performed by the second network element;

The fourth sub-operation: create a new cell A, which is executed by the third network element;

Fifth sub-operation: activate cell A, executed by the third network element;

The sixth sub-operation: restore the neighbor relationship with cell A, which is performed by the first network element.

The intended execution order information is used to indicate the order in which the six sub-operations are executed, which can be expressed as indicating the order in which the first operation, the second operation, the third operation, and the fourth operation are executed, wherein the first operation is the first sub-operation , the second operation is a combination operation of the second sub-operation and the third sub-operation, the third operation is a combination operation of the fourth sub-operation and the fifth sub-operation, and the fourth operation is a sixth sub-operation.

In addition, it should be noted that when the operation in the embodiment of the present application includes multiple sub-operations, for example, the second operation is a combination operation of the second sub-operation and the third sub-operation, an operation instruction describing the second operation may be used to indicate the execution of the second sub-operation. The order of the second sub-operation and the third sub-operation.

For clarity, the manner in which the execution sequence information indicates the order of executing the first operation of the first intent and the second operation of the first intent will be described below.

Method 1:

The execution sequence information includes a step identifier (stepID) of the first operation and a step identifier (stepID) of the second operation.

Wherein, the step identifier is used to indicate the order in which the corresponding operations are executed in all operations. Operations with different step identifiers need to be executed in sequence, and operations with the same step identifier can be executed in parallel. The step identifier of the first operation may be carried in the description information of the first operation, and the step identifier of the second operation may be carried in the description information of the second operation.

For example, the step identifier of the first operation is 1 (for example, stepID=1), and the step identifier of the second operation is 2 (for example, stepID=2), indicating that the sequence for executing the second operation is after the sequence for executing the first operation.

For another example, the step identifier of the first operation is 1 (for example, stepID=1), and the step identifier of the second operation is also 1 (for example, stepID=1), indicating that the first operation and the second operation can be executed in parallel.

Method 2:

The execution sequence information includes the step ID (stepID) and wait type (waitType) of the first operation, and the step ID (stepID) and wait type (waitType) of the second operation.

Wherein, the waiting type is used to indicate whether the execution of the corresponding operation needs to wait for the execution of the preceding operation to be completed, and the step identifier is used to indicate the order in which the corresponding operation is executed in performing all the operations. The step identifiers of multiple operations are not allowed to have repeated values. If there are multiple operations whose step identifiers are continuous values, and the wait types of the operations except the first operation indicate that there is no need to wait for the preorder After the operation is completed, multiple operations marked as consecutive values in this step can be executed in parallel. The step identification and waiting type of the first operation may be carried in the description information of the first operation, and the step identification and waiting type of the second operation may be carried in the description information of the second operation.

For example, the step ID of the first operation is 1, and the wait type is no need to wait (for example, stepID=1, waitType=not wait), the step ID of the second operation is 2, and the wait type is no need to wait (for example, stepID=2, waitType=not wait), indicating that the second operation does not need to wait for the first operation to be executed before executing, and the first operation and the second operation can be executed in parallel.

For another example, the step identification of the first operation is 1, and the waiting type is no need to wait (for example, stepID=1, waitType=not wait), the step identification of the second operation is 2, and the waiting type is needing to wait (for example, stepID=2 , waitType=wait), there is also a step ID of the third operation is 3, and the waiting type is no waiting (for example, stepID=3, waitType=not wait), which means that the second operation and the third operation need to wait for the completion of the first operation can then be executed in parallel.

Method 3:

The execution order information includes a mapping relationship between identifiers of the first operations and the order in which the first operations are executed, and a mapping relationship between identifiers of the second operations and the order in which the second operations are executed.

For example, the execution order information is a mapping table of operation identifiers and operation execution order, and the execution order of the first operation or the second operation can be indexed by the identifier of the first operation or the second operation.

The above describes the way in which the execution order information indicates the order in which the first operation and the second operation are performed. It should be understood that the above method is also applicable to the scenario where the execution order information indicates the order in which three or more operations are performed. Not particularly limited.

S202. The intended execution network element determines, according to the execution sequence information, a sending sequence in which the intended execution network element sends the first operation to the first network element and the intention execution network element sends the second operation to the second network element.

S203. The intent-to-execute network element sends the first operation to the first network element according to the sending order.

S204. The intent-to-execute network element sends the second operation to the second network element according to the sending order.

If the network element that intends to execute determines that the first operation needs to be performed first and then the second operation according to the execution order information, it is determined to first send the first operation to the first network element, and then send the second operation to the second network element, that is to say Execute step S203 first, and then execute step S204; if the network element intending to execute determines that the second operation needs to be executed first according to the execution order information, and then the first operation is executed, then it is determined to first send the second operation to the second network element, and then send the second operation to the first The network element sends the first operation, that is to say, step S204 is executed first, and then step S203 is executed; if the intention execution network element determines that the first operation and the second operation can be executed in parallel according to the execution sequence information, then the intent execution network element sends the first operation to the first operation. The order in which the network element sends the first operation and sends the second operation to the second network element is not limited.

In a possible implementation manner, the intent execution network element needs to determine whether the first operation is executed successfully, and the method may further include one or more steps from steps S205 to S207.

S205. The network element intending to execute receives the execution result information of the first operation from the first network element.

The execution result information is used to determine whether the first operation is executed successfully.

For example, the execution result information includes an indication of whether the first operation is executed successfully.

The execution result information may be carried in an operation execution response message in response to the first operation, and the execution result information may also be carried in a response message in response to the query message.

S206. The intent execution network element determines whether the first operation is executed successfully according to the execution result information.

For example, the execution result information includes a field indicating whether the first operation is successful, and the intended execution network element determines whether the first operation is successfully executed according to this field. For example, when the field is 1, it is determined that the first operation is successfully executed, and when the field is 0 It is determined that the execution of the first operation is unsuccessful.

In a possible implementation manner, the execution result information may be related parameters of the system after the first network element executes the first operation, and may also be the execution status of the first operation, for example, the execution status indicates that the How many instructions were executed. In other words, if the execution result information is not displayed to indicate whether the first operation is successfully executed, then step S207 needs to be executed before step S206 is executed. In step S206, the intended execution network element determines the Whether the operation is executed successfully.

S207. The intent execution network element receives first indication information from the intent knowledge base.

The first indication information may indicate that the schematic execution network element determines whether the first operation is executed successfully.

Optionally, the first indication information may be carried in description information of the first operation.

Optionally, the first indication information may include a criterion for determining whether the first operation is performed successfully.

For example, the execution result information includes relevant parameters of the system after the first operation is executed, and the judgment criterion indicates that when a certain parameter reaches a predetermined range, the first operation is determined to be executed successfully.

It should be noted that the judgment criterion may implicitly indicate that the intent execution network element determines whether the first operation is executed successfully. The judgment criterion determines whether the first operation is performed successfully.

Optionally, the first indication information may include a judgment criterion for determining whether the first operation is successfully performed, and an action intended to be performed by the network element to determine whether the first operation is successfully performed. For example, the judging action indicates that the execution network element needs to send a query message to the first network element to acquire the execution result information of the first operation.

The intent execution network element may determine, according to the first indication information, that it is necessary to determine whether the first operation is executed successfully, and perform the indicated judgment action to obtain relevant execution result information after the first operation is executed, and then determine the second operation according to the judgment criterion and the execution result information. Whether a network element executes the first operation successfully.

Taking the judgment action to indicate that the execution network element needs to send a query message to obtain the execution result information of the first operation. For example: the intention execution network element sends a query message to the first network element according to the judgment action, and the first network element queries the first operation according to the query message. The execution result information of the operation, and return the response message of the query message to the intended execution network element, the response message carries the execution result information of the first operation, and the intended execution network element determines whether the first operation is executed successfully according to the execution result information and the judgment criterion . Wherein, the query message may request the first network element to return specific parameters required by the judgment criterion, or may request the first network element to return all relevant parameters of the system after performing the first operation, which is not particularly limited in this application.

The method for determining whether the first operation is successfully executed by the intended execution network element is described above. It should be understood that the method for the intended execution network element to judge whether other operations (such as the second operation) is executed successfully is similar to the description of judging the first operation. It is simple and will not be repeated here.

In a possible implementation manner, when the intention execution network element first sends the first operation to the first network element, and then sends the second operation to the second network element, the intention execution network element may send the first operation to the first network element. After one operation, it is determined whether the first operation is executed successfully, and if the execution is successful, then the second operation is sent to the second network element. In other words, in step S204, in the case that the intended execution network element determines that the first operation is performed successfully, the intended execution network element sends the second operation to the second network element.

Wherein, the manner in which the intended execution network element determines whether the first operation is performed successfully may refer to the description of steps S205 to S207, in other words, steps S205 to S207 may be performed between steps S203 and S204.

It should be understood that, when the intent-to-execute network element first sends the second operation to the second network element, and then sends the first operation to the first network element, the intent-to-execute network element may also determine Whether the second operation is successfully executed, and if the execution is successful, send the first operation to the first network element. In other words, before sending the operation, the intent execution network element may first judge whether the preceding operation is executed successfully, and send the operation if the execution is successful, thereby improving the reliability of intent execution.

In a possible implementation manner, if it is desired that the intention execution network element feed back the execution progress of the operation, the intention execution network element may receive progress indication information from the intention translation network element.

The progress indication information is used to indicate that the schematic execution network element needs to feed back progress information, and the progress information is used to indicate the execution progress of the first operation and the second operation.

For example, the progress information is used to indicate the executed percentages of the first operation and the second operation, the estimated remaining time until completion, or the number of completed operation instructions, etc., which are not particularly limited in the present application.

The progress indication information may be carried in the intent execution message sent by the intent translation network element for requesting the execution of the first intent. For example, if the intention consumption network element wishes to obtain the execution progress of the operation, the intention consumption network element may carry the progress indication information in the intention implementation request message sent to the intention management network element, and the intention management network element sends the intention translation network element The progress indication information is carried in the intention translation message, and then the intention translation network element may carry the progress indication information in the intention execution message sent to the intention execution network element.

Optionally, the progress indication information may also be used to indicate the period or frequency at which the schematic execution network element needs to feed back the progress information.

Optionally, the progress indication information can also be used to indicate the trigger condition that the intention execution network element needs to feed back the progress information. For example, the progress indication information can indicate that when a certain parameter of the current system reaches the predetermined trigger condition, the intention execution network element needs to feedback The current execution progress of the first operation and the second operation.

The intention execution network element sends the progress information to the intention management network element according to the progress indication information.

Optionally, the intention management network element may also send progress information to the intention consumption network element.

Optionally, after the intention execution network element receives the progress indication information, it may determine the progress information according to the execution result information returned by the first network element and/or the second network element, and return the progress information to the intention management network Yuan. The intention execution network element may also send a query message to the first network element and/or the second network element to obtain the progress information according to the progress indication information.

If the progress indication information indicates the period and frequency at which the intention execution network element needs to feedback at the same time, the intention execution network element may also send the progress information to the intention management network element according to the period and frequency.

In a possible implementation, in step S201, the intention execution network element receives the execution order information from the intention knowledge base in two ways: first, the intention translation network element receives the intention translation message sent by the intention management network element Finally, according to the identification information of the first intention and the intention expression of the first intention in the intention translation message, an intention knowledge query message is sent to the knowledge management network element, and the knowledge management network element performs a query in the intention knowledge base according to the intention knowledge query message , and send the intent knowledge feedback message to the intent translation network element, and carry the execution sequence information in the intent knowledge feedback message, and then the intent translation network element can carry the execution sequence information in the intent execution request message sent to the intent execution network element Second, after the intention translation network element receives the intention execution request message sent by the intention translation network element, the intention translation network element can execute the intention according to the intention expression and/or the operation identifier (the first operation and/or The identification of the second operation) sends an intention operation query message to the knowledge management network element, and the knowledge management network element performs a query in the intention knowledge base according to the operation query message, and sends an intention operation feedback message to the intention execution network element. The execution sequence information is carried in the feedback message.

In other words, the intent execution network element receives the execution sequence information from the intent knowledge base. The execution sequence information can be received from the intent knowledge base by other network elements initiating a query, and then forwarded to the intent execution network element. The execution sequence information can also be The intent execution network element itself initiates the query received from the intent knowledge base.

It should be understood that the above is an explanation of the intention execution network element receiving the execution order information from the intention knowledge base. In S205, the manner in which the intention execution network element receives the first indication information from the intention knowledge base may be similar to the description of receiving the execution order information. For the sake of brevity, details are omitted here.

Therefore, in this application, the intention execution network element can determine the sending order of multiple operations according to the order in which multiple operations are executed, so that multiple operations can be executed in order, so that multiple operations can cooperate with each other, avoiding due to Execution not in order causes the intended operation to fail or not achieve the desired effect.

FIG. 3 shows another example of a schematic flowchart of an intent execution method 300 provided by the present application.

Optionally, S301. The intention consumption network element sends an intention implementation request message to the intention management network element.

The intent implementation request message is used to request execution of the first intent, and the intent implementation request message may include an intent expression (intentExpression) of the first intent.

Optionally, the intent implementation request message further includes progress indication information (progressNotify). For a description of the progress indication information, refer to the description of the progress indication information in method 200. For simplicity, details are not repeated here.

Optionally, S302. The intention management network element sends an intention implementation request response message for responding to the intention implementation request message to the intention consumption network element.

The intent implementation request response message may include an identifier (intentID) of the first intent, and may also include an intent expression of the first intent.

For example, after receiving the intent implementation request message corresponding to the first intent, the intent management network element assigns the identifier of the first intent to the first intent, and carries the identifier in the intent implementation request response message and sends it to the intent consumption network element.

Optionally, S303. The intent management network element sends an intent translation request message to the intent translation network element.

The intent translation request message is used to request the intent translation network element to translate the first intent.

The intent translation request message may include an identifier of the first intent and an intent expression, and if progress indication information is included in the intent implementation request message, the intent translation message also includes the progress indication information.

S304. The intent translation network element sends an intent knowledge query message to the intent knowledge base.

The intent knowledge query message may include an identifier of the first intent, an intent expression, and a query type.

Wherein, the query type may indicate parameters that need to be obtained by querying. For example, if the query type is all parameters (type=all), the intent knowledge base needs to return all parameters related to the first intent.

Optionally, S305, the intent knowledge base acquires the query result.

The intent knowledge base obtains the query result according to the intent query message.

Wherein, the intent knowledge base can be understood as a sub-module of the knowledge management network element. During the initialization and update process of the intent knowledge base, the relevant information of the first intent, such as execution sequence information (stepinfo), first instruction information, etc., is stored. In the intent knowledge base, the knowledge management network element can query the intent knowledge base according to the intent knowledge query message. For example, the first indication information includes success judgment information (success indication),

For example, if the query type is querying operations of the first intent, the intent knowledge base acquires an intent operation list (intentOperationList) of the first intent, and the intent operation list includes a description of the first operation and a description of the second operation. It should be understood that if the first intent has other operations, the intent operation list also includes descriptions of other operations.

Wherein, taking the description of the first operation as an example, the description information of the first operation may include one or more of the following information: the operation instruction (instruction) of the first operation, the operation execution object (entityIDList) of the first operation . If the indication method of mode 1 or mode 2 in method 200 is adopted, the description information of the first operation also includes the execution sequence information (stepInfo) of the first operation, such as {step identification (stepID)}, or {step identification (stepID), waitType(waitType)}. Wherein, the operation instruction is used to describe a specific command for executing the first operation, and the operation execution object is used to describe the first network element that needs to execute the first operation.

Optionally, if the intended execution network element needs to judge whether the execution of the first operation is successful, the description information of the first operation also includes the first indication information. For the description of the first indication information, please refer to the first indication information in method 200. The description of , for the sake of brevity, will not be repeated here.

It should be understood that the description information of other operations may be similar to the description information of the first operation, and details are not repeated here for simplicity.

The intended operation list may also include execution condition (executioncondition) information, which is used to describe the conditions that need to be met for executing the first operation and the second operation, for example, the first operation may be executed when the network load is no-load or low-load operation and/or a second operation.

The intent operation list may also include dependent event (events) information, and the dependent event information is used to describe the impact that the execution of the first intent may have on the system.

If the query type is to query all parameters, the intent knowledge base can not only obtain the intent operation list (intentOperationList) of the first intent, but also include the fulfillment criterion (fulfillmentCriterion), which can be used to indicate the fulfillment condition of the first intent For example, the criterion for achieving the intended goal may include an intended goal calculation formula for measuring whether the intended goal is achieved.

Optionally, if the indication manner of mode 3 in method 200 is adopted, the intent knowledge base may also obtain execution sequence information (stepInfo), which describes the execution sequence of multiple operations of the first intent.

Regarding the first operation, the second operation, and the manner in which the execution order information indicates the order of executing the first operation and the second operation, reference may be made to the relevant description in the method 200 , and details are not repeated here for brevity.

The above is only an exemplary description of the query results, and the present application does not make any special limitation thereto.

S306. The intent translation network element receives an intent knowledge feedback message from the intent knowledge base.

The intent knowledge feedback message includes query results obtained from the intent knowledge base.

The intent knowledge feedback message may also include an identifier (intentID) of the first intent.

S307. The intent translation network element sends the execution order information to the intent execution network element.

The execution sequence information is used to indicate the sequence of executing the first operation of the first intent and the second operation of the first intent.

For example, the intent translation network element sends an intent execution request message to the intent execution network element, and the intent execution request message includes the execution sequence information (stepInfo).

The intent translation request message may also include the identifier of the first intent, and the intent operation list and intent goal achievement criteria obtained by the intent translation network element from the intent knowledge feedback message.

Optionally, if the intended execution network element needs to feed back the progress information of the execution of the first operation and the second operation, the set of intended operations further includes progress indication information.

After receiving the intent execution request message, the intent execution network element may determine to execute the first operation and the second operation according to a predetermined decision algorithm.

S308. The network element intending to execute determines the sending order of the network element intending to execute sending the first operation to the first network element and the network element intending executing the network element sending the second operation to the second network element according to the execution sequence information.

For the description about the network element intended to execute determining the sending order of sending the first operation and sending the second operation, refer to the description in the method 300 , and details are not repeated here for simplicity. The following uses an example in which the intention execution network element first sends the first operation to the first network element, and then sends the second operation to the second network element.

S309. The intent-to-execute network element sends the first operation to the first network element according to the sending order.

For example, the intended execution network element sends an operation execution request message corresponding to the first operation to the first network element, and the operation execution request message includes information corresponding to the first operation, where the information corresponding to the first operation may include Operation ID (operationID) and operation instruction (instruction).

The first network element may execute the first operation according to the information corresponding to the first operation.

Optionally, S310, the network element intended to perform receives the execution result information of the first operation from the first network element.

The execution result information is used to determine whether the first operation is executed successfully.

For example, the intended execution network element receives an operation execution response message from the first network element in response to the operation execution request message, the operation execution response message includes the execution result information of the first operation, and the operation execution response message may also include the first operation Action ID.

For another example, the first indication information is also used to instruct the schematic execution network element to determine whether the first operation is successfully executed, and the judgment action indicates that the schematic execution network element needs to query the first network element for the execution result information of the first operation. In this case, the intention execution network element may send an operation execution status query message to the first network element, and the operation execution status query message is used to request to query the execution result information, and the execution result information received by the intention execution network element is carried in the In response to the Operation Execution Status Query message, the Operation Execution Status Query Response message.

Optionally, in S311, the intended execution network element determines whether the first operation is executed successfully according to the first indication information and the execution result information.

For a description of determining whether the first operation is successfully performed by the intended network element, reference may be made to the description of the method 200, and details are not repeated here for simplicity.

In a case where the intention-performing network element determines that the first operation is successfully performed, the intention-performing network element may perform S312.

S312. The intent-to-execute network element sends a second operation to the second network element.

For example, the intended execution network element sends an operation execution request message corresponding to the second operation to the second network element, where the operation execution request message includes information corresponding to the second operation, where the information corresponding to the second operation may include Operation ID (operationID) and operation instruction (instruction).

It should be understood that the intention execution network element may also receive the execution result information of the second operation from the second network element, the intention execution request message may also include the first indication information of the second operation, and the intention execution network element may also receive the execution result information of the second operation according to the second operation The first indication information and the execution result information determine whether the second operation is executed successfully. If the operation corresponding to the first intention also has a third operation that needs to be performed by the intention management network element, and the execution sequence of the third operation is after the second operation, Then the intent execution network element may also send the third operation to the intent management network element after determining that the second operation is executed successfully. The implementation method is similar to that described above for the first operation. The application does not impose any limitation on the number of operations corresponding to the first intent.

If progress indication information is also included in the intention execution request message, the method further includes step S313.

S313. The intention execution network element sends an operation execution progress notification message to the intention management network element.

The operation execution progress notification message may include the identifier of the first intent and progress information. For the description of the progress information, refer to the relevant description in the method 200, and for simplicity, details are not repeated here.

Optionally, if the progress indication information is also used to indicate the cycle or frequency at which the intended execution network element needs to feed back progress information, the intended execution network element can monitor the progress of the operation execution according to the cycle or frequency, and according to the cycle or frequency The frequency sends the operation execution progress notification message to the intent management network element.

If the intended consumption network element needs to obtain the progress information, the intended management network element may forward the operation execution progress notification message to the intended consumption network element.

Therefore, in this application, the intention execution network element can determine the sending order of multiple operations according to the order in which multiple operations are executed, so that multiple operations can be executed in order, so that multiple operations can cooperate with each other, avoiding due to Execution not in order causes the intended operation to fail or not achieve the desired effect.

FIG. 4 shows a schematic flowchart of an example of an intent execution method 400 provided by the present application.

S401. The intention execution network element receives execution result information of the first operation of the first intention from the first network element.

The execution result information is used to determine whether the execution of the first operation is abnormal.

Wherein, the abnormality in the execution of the first operation may refer to any of the following situations: the execution of the first operation fails, the execution of the first operation times out, the execution result of the first operation does not achieve the predetermined effect, or other causes the first intention to fail to achieve the predetermined The situation of the intended target.

For example, the execution result information may include an indication of whether the execution of the first operation is abnormal.

S402. The intention execution network element determines whether the execution of the first operation is abnormal according to the execution result information.

For example, the execution result information includes a field indicating whether the execution of the first operation is abnormal, and the intended execution network element determines whether the execution of the first operation is abnormal according to this field. For example, when the field is 1, it means that the execution of the first operation occurs Abnormal, when this field is 0, it means that the execution of the first operation has no abnormality.

In a possible implementation manner, the execution result information may be related parameters of the system after the first network element executes the first operation, and may also be the execution status of the first operation, for example, the execution status indicates that the How many instructions were executed. In other words, if the execution result information does not indicate whether the execution of the first operation is abnormal, then step S403 needs to be performed before performing step S402. It is determined whether the execution of the first operation is abnormal.

S403. The intent execution network element receives second indication information from the intent knowledge base.

The second indication information is used to instruct the schematic execution network element to determine whether the execution of the first operation is abnormal.

The second indication information may be stored in the intent knowledge base during the process of initializing and updating the intent knowledge base.

The second indication information may be carried in the description information of the first operation.

Optionally, the second indication information may include a judgment criterion for determining whether the execution of the first operation is abnormal.

The network element intending to execute determines whether the execution of the first operation is abnormal according to the execution result information and the judgment criterion. For example, the judgment criterion indicates that when a certain parameter reaches a predetermined range, the execution of the first operation is judged to be abnormal. For example, the judgment criterion indicates that if the execution result of the first operation does not reach the predetermined result, it means that the execution of the first operation is abnormal. As a result, it is determined whether the execution of the first operation is abnormal; for example, the judgment criterion indicates that if the first operation is not successfully executed within the predetermined time, it means that the execution of the first operation is abnormal, and the intended execution network element receives the The execution result information indicates that the execution of the first operation failed, or the intended execution network element does not receive the execution result information indicating that the execution of the first operation is successful within a predetermined time, then the intended execution network element may determine the execution of the first operation Abnormal.

It should be noted that the abnormality judgment criterion may implicitly indicate that the intention execution network element can determine whether the execution of the first operation is abnormal, in other words, the intention execution network element may receive the judgment criterion from the intention knowledge base, and the intention execution network element By default, it is necessary to determine whether the execution of the first operation is abnormal according to the judgment criterion.

Optionally, the second indication information may include a judging criterion for determining whether the execution of the first operation is abnormal, and an action intended to be performed by the network element to determine whether the execution of the first operation is abnormal. For example, the judging action indicates that the schematic execution network element needs to send a query message to the first network element to acquire the execution result information of the first operation.

The intention execution network element can determine whether it is necessary to determine whether the execution of the first operation is abnormal according to the second instruction information, and execute the indicated judgment action to obtain the relevant execution result information after the first operation is executed, and then according to the abnormal judgment criterion and the execution result Information to determine whether execution of the first operation occurred successfully.

Taking the judgment action to indicate that the execution network element needs to send a query message to obtain the execution result information of the first operation. For example: the intention execution network element sends a query message to the first network element according to the judgment action, and the first network element queries the first operation according to the query message. The execution result information of the operation, and return the response message of the query message to the intended execution network element, the response message carries the execution result information of the first operation, and the intended execution network element determines whether the execution of the first operation is based on the execution result information and the judgment criterion Abnormal. Wherein, the query message may request the first network element to return specific parameters required by the judgment criterion, or may request the first network element to return all relevant parameters of the system after performing the first operation, which is not particularly limited in this application.

The method for determining whether the execution of the first operation is abnormal by the intended execution network element is described above. It should be understood that the method for the intended execution network element to determine whether the execution of other operations is abnormal is similar to the description of judging the first operation. For simplicity, I won't repeat them here.

S404. When the intended execution network element determines that the execution of the first operation is abnormal, the intended execution network element sends rollback indication information to the second network element.

The rollback instruction information is used to indicate rollback of the second operation of the first intention.

Wherein, the first operation may include multiple operation instructions, and may be completely executed by the first network element (for example, network device #1); the second operation may also include multiple operation instructions, and may be completely executed by the second network element (for example, network device #1). Device #2) is fully implemented.

The second operation may be a preorder operation of the first operation, or the second operation may be a parallel operation of the first operation, or in other words, the second operation may be when the network element intending to execute determines that the execution of the first operation is abnormal, The second network element has successfully performed or is currently performing an operation.

The first operation of the first intent and the second operation of the first intent may be one or more sub-operations of the intent operation corresponding to the first intent. For example, the intent operation corresponding to the first intent includes three sub-operations, namely: a first sub-operation, a second sub-operation, and a third sub-operation. The execution object of the first sub-operation is the first network element, and the execution object of the second sub-operation and the third sub-operation is the second network element. Then the first operation in this embodiment of the present application may be the first sub-operation, and the second operation may be a combination operation of the second sub-operation and the third sub-operation.

It should be understood that if there are other operations of the first intention in the system, when the intention execution network element determines that the execution of the first operation is abnormal, other network elements have successfully executed or are executing the operation, the intention execution network element can also report to other network elements The unit sends the rollback instruction information used to indicate rollback of the operation. As an example but not a limitation, the intended target of the first intention is cell relocation as an example. The first intent has four actions which are:

The first operation: delete the neighbor relationship with cell A, which is performed by the first network element;

The second operation: deactivating cell A and deleting cell A, performed by the second network element;

The third operation: creating a new cell A, and activating the cell A, performed by the third network element;

The fourth operation: restore the neighbor relationship with cell A, which is performed by the first network element.

If the first operation and the second operation have been executed successfully, but the execution of the third operation is abnormal, the intended execution network element sends the rollback indication information for rolling back the second operation to the second network element, and sends the rollback indication information to the first network element The element sends rollback indication information for rolling back the first operation.

Rolling back the second operation may be understood as restoring the system to a state before the second operation is performed.

It should be understood that if there are other operations of the first intention in the system, when the intention execution network element determines that the execution of the first operation is abnormal, other network elements have successfully executed or are executing the operation, the intention execution network element can also report to other network elements The unit sends rollback indication information for indicating rollback of the operation. For example, if the intention management network element has successfully performed the third operation of the first intention or is currently performing the third operation, the intention execution network element may also send indication information indicating to roll back the third operation to the intention management network element. Optionally, the intent execution network element may send the rollback indication information in a reverse order of the sending order of sending multiple operations.

S405. The second network element rolls back the second operation according to the rollback instruction information.

Wherein, the manner of rolling back the second operation may be determined based on whether the second network element has the capability of rolling back the operation.

If the second network element has an operation rollback capability, the second network element may call its own operation rollback capability to roll back the second operation after receiving the rollback instruction information.

If the second network element does not have the ability to roll back the operation, the rollback indication information sent by the network element intended to execute can also be used to indicate the way the second network element rolls back the second operation. At this time, the method 400 also includes step S406 .

S406. The intent execution network element receives fallback solution information from the intent knowledge base.

The fallback scheme information is used to indicate the fallback mode of the second operation, and the fallback indication information sent by the intended network element is also used to indicate the fallback mode of the second operation.

It should be understood that the fallback indication information may be the fallback mode of the second operation, or in other words, the intention execution network element may send the fallback mode of the second operation to the second network element, and the fallback mode of the second operation is implicitly indicates that the second network element needs to roll back the second operation.

The fallback scheme information may be stored in the intent knowledge base during the initialization and update process of the intent knowledge base.

The fallback scheme information may be carried in the description information of the corresponding second operation.

In a possible implementation manner, the rollback solution information describes rollback modes corresponding to different second operations in different abnormal situations, and in this case, the method 400 further includes step S407.

S407. The intended execution network element determines a fallback mode of the second operation according to the execution result information and the fallback scheme information.

For example, the rollback plan information includes the mapping relationship between abnormal conditions and rollback methods. Different abnormal conditions correspond to different labels. The execution result information may include labels corresponding to abnormal conditions that occur when executing the first operation. The element indexes to the fallback mode of the second operation corresponding to the abnormal condition according to the label, and sends the fallback mode of the second operation to the second network element.

For another example, the fallback scheme information includes the mapping relationship between the abnormal situation and the fallback mode, the execution result information includes the relevant parameters after the first operation is executed, and the intended execution network element judges which abnormal situation it belongs to according to the relevant parameters, Further, the fallback mode of the second operation is determined, and the fallback mode of the second operation is sent to the second network element.

In a possible manner, when the intention execution network element determines that the execution of the first operation is abnormal, the intention execution network element may first ask the intention consumption network element whether the second operation needs to be rolled back, and when the intention consumption network element When the feedback needs to roll back the second operation, the intention execution network element sends the rollback indication information to the second network element. In this case, the method further includes step S408, which may be executed between step S403 and step S404, wherein, in step S403, the network element intending to execute determines that the execution of the first operation is abnormal.

S408. The intention execution network element sends an intention operation rollback request message to the intention management network element.

The intended operation rollback request message is used to indicate whether the second network element needs to roll back the second operation.

Optionally, the intent operation rollback request message may include at least one of the following information: identification information including the first intent, relevant information indicating that an exception occurs in the execution of the first operation, and a rollback mode of the second operation.

The intended consumption network element receives the intended operation rollback request message, and may determine whether to roll back the second operation according to the current system running status or the abnormality of the first operation.

S409. The intent management network element sends an intent operation rollback response message in response to the intent operation rollback request message to the intent execution network element, where the intent operation rollback response message is used to indicate whether the second operation needs to be rolled back.

If the intended operation rollback response message indicates that the second operation does not need to be rolled back, the intended execution network element does not need to send rollback instruction information to the second network element.

If the intended operation rollback response message indicates that the second operation needs to be rolled back, step S404 may be performed, and the intention execution network element sends rollback instruction information to the second network element.

In a possible manner, the intention translation network element carries expected processing type indication information in the intention execution request message sent to the intention execution network element, and the expected processing type indication information is used to indicate that the intention execution network element determines the first operation In the case of abnormal execution, whether it is necessary to ask the intended consumption network element whether the second operation needs to be rolled back, if the processing type indication information indicates that it is not necessary to ask the intended consumption network element whether the second operation needs to be rolled back, then the intended execution The network element may directly send the rollback indication information to the second network element, and if the processing type indication information indicates that it is necessary to inquire whether the intended consumption network element needs to roll back the second operation, the intended execution network element needs to perform step S408.

In a possible implementation manner, if it is desired that the intention execution network element feed back the execution progress of the operation, the intention execution network element may receive progress indication information from the intention translation network element.

The progress indication information is used to indicate that the schematic execution network element needs to feed back progress information, and the progress information is used to indicate the execution progress of the first operation and the second operation.

For example, the progress information is used to indicate the executed percentages of the first operation and the second operation, the estimated remaining time until completion, or the number of completed operation instructions, etc., which are not particularly limited in the present application.

The progress indication information may be carried in the intent execution message sent by the intent translation network element for requesting the execution of the first intent. For example, if the intention consumption network element wishes to obtain the execution progress of the operation, the intention consumption network element may carry the progress indication information in the intention implementation request message sent to the intention management network element, and the intention management network element sends the intention translation network element The progress indication information is carried in the intention translation message, and then the intention translation network element may carry the progress indication information in the intention execution message sent to the intention execution network element.

Optionally, the progress indication information may also be used to indicate the period or frequency at which the schematic execution network element needs to feed back the progress information.

Optionally, the progress indication information can also be used to indicate the trigger condition that the plan execution network element needs to feed back the progress information. For example, the progress indication information can indicate that when a certain parameter of the current system reaches the predetermined trigger condition, the intention execution network element needs to feedback The current execution progress of the first operation and the second operation.

The intention execution network element sends the progress information to the intention management network element according to the progress indication information.

Optionally, if the intended consumption network element needs to obtain progress information, the intention management network element may send the progress information to the intended consumption network element.

Optionally, after the intention execution network element receives the progress indication information, it may determine the progress information according to the execution result information returned by the first network element and/or the second network element, and return the progress information to the intention management network Yuan. The intention execution network element may also send a query message to the first network element and/or the second network element to obtain the progress information according to the progress indication information.

If the progress indication information indicates the period and frequency at which the intention execution network element needs to feedback at the same time, the intention execution network element may also send the progress information to the intention management network element according to the period and frequency.

In a possible implementation, in step S401, there are two ways for the intent execution network element to receive the second indication information from the intent knowledge base. First, the intent translation network element receives the intent translation sent by the intent management network element After the message, according to the identification information of the first intent and the intent expression of the first intent in the intent translation message, the intent knowledge query message is sent to the knowledge management network element, and the knowledge management network element performs the query in the intent knowledge base according to the intent knowledge query message. query, and send an intent knowledge feedback message to the intent translation network element, and carry the second indication information in the intent knowledge feedback message, and then the intent translation network element may carry the second instruction information in the intent execution request message sent to the intent execution network element Two indication information; second, after the intention translation network element receives the intention execution request message sent by the intention translation network element, the intention translation network element can execute the intention expression and/or the operation identifier (the first operation) in the intention execution request message according to the intention and/or the identification of the second operation) sends an intention operation query message to the knowledge management network element, and the knowledge management network element performs a query in the intention knowledge base according to the operation query message, and sends an intention operation feedback message to the intention execution network element, and then The intention operation feedback message carries the second indication information.

In other words, the intention execution network element receives the second indication information from the intention knowledge base, the second indication information may be received from the intention knowledge base by other network elements initiating a query, and then forwarded to the intention execution network element, the second indication information It may also be received from the intent knowledge base by initiating a query by the intent execution network element itself.

It should be understood that the above is an illustration of the intention execution network element receiving the second indication information from the intention knowledge base, and in S406, the manner in which the intention execution network element receives the fallback solution information from the intention knowledge base may be the same as the description of receiving the second indication information Similarly, for the sake of brevity, details are not repeated here.

Therefore, in this application, if the execution of a certain operation of the first intent is abnormal, other operations that have been executed by the first intent can be rolled back, so as to avoid the resources and signaling caused by other operations of the first intent being executed all the time. Waste, which in turn can improve the execution efficiency of intentions.

FIG. 5 shows a schematic flowchart of another example of an intent execution method 500 provided by the present application.

Optionally, S501. The intention consumption network element sends an intention implementation request message to the intention management network element.

The intent implementation request message is used to request execution of the first intent, and the intent implementation request message may include an intent expression (intentExpression) of the first intent.

Optionally, the intent implementation request message further includes progress indication information (progressNotify). For a description of the progress indication information, refer to the description of the progress indication information in method 400. For simplicity, details are not repeated here.

Optionally, S502. The intention management network element sends an intention implementation request response message for responding to the intention implementation request message to the intention consumption network element.

The intent implementation request response message may include an identifier (intentID) of the first intent, and may also include an intent expression of the first intent.

For example, after receiving the intent implementation request message corresponding to the first intent, the intent management network element assigns the identifier of the first intent to the first intent, and carries the identifier in the intent implementation request response message and sends it to the intent consumption network element.

Optionally, S503. The intent management network element sends an intent translation request message to the intent translation network element.

The intent translation request message is used to request the intent translation network element to translate the first intent.

The intent translation request message may include an identifier of the first intent and an intent expression, and if progress indication information is included in the intent implementation request message, the intent translation message also includes the progress indication information.

S504. The intent translation network element sends an intent knowledge query message to the intent knowledge base.

The intent knowledge query message may include an identifier of the first intent, an intent expression, and a query type.

Wherein, the query type may indicate parameters that need to be obtained by querying, for example, if the query type is all parameters (type=all), the knowledge management network element needs to return all parameters related to the first intent.

Optionally, S505, the intent knowledge base acquires a query result.

The intent knowledge base obtains the query result according to the intent query message.

Among them, the intent knowledge base can be understood as a sub-module of the knowledge management network element. During the initialization and update process of the intent knowledge base, the relevant information of the first intent, such as the second instruction information, rollback solution list, etc. Stored in the intent knowledge base, the knowledge management network element can query the intent knowledge base according to the intent knowledge query message. For example, the second indication information may include exception judgment information (exception indication).

For example, if the query type is querying operations of the first intent, the intent knowledge base acquires an intent operation list (intentOperationList) of the first intent, and the intent operation list includes a description of the first operation and a description of the second operation. It should be understood that if the first intent has other operations, the intent operation list also includes descriptions of other operations.

Wherein, taking the description of the first operation as an example, the description information of the first operation may include one or more of the following information: the operation instruction (instruction) of the first operation, the operation execution object (entityIDList) of the first operation , the second indication information of the first operation and the rollback solution information (rollbacksolutionlist). Wherein, the operation instruction is used to describe the specific command to perform the first operation, and the operation execution object is used to describe the first network element that needs to perform the first operation. For the description of the second instruction information and the fallback scheme information, please refer to the method 400 The corresponding description in , for the sake of brevity, will not be repeated here.

It should be understood that the description information of other operations may be similar to the description information of the first operation, and for the sake of simplicity, details are not repeated here.

The intended operation list may also include execution condition (executioncondition) information, which is used to describe the conditions that need to be met for executing the first operation and the second operation, for example, the first operation may be executed when the network load is no-load or low-load operation and/or a second operation.

The intent operation list may also include dependent event (events) information, and the dependent event information is used to describe the impact that the execution of the first intent may have on the system.

If the query type is to query all parameters, in addition to obtaining the intent operation list (intentOperationList) of the first intent in the intent knowledge base, the intent knowledge feedback message may also include an intent goal fulfillment criterion (fulfillmentCriterion), which can be used to indicate The achievement condition of the first intention, for example, the intention goal achievement criterion may include an intention goal calculation formula to measure whether the intention goal is achieved.

The above is only an exemplary description of the query results, and the present application does not make any special limitation thereto.

S506. The intent translation network element receives an intent knowledge feedback message from the intent knowledge base.

The intent knowledge feedback message includes query results obtained from the intent knowledge base.

The intent knowledge feedback message may also include an identifier (intentID) of the first intent.

S507. The intent translation network element sends the second indication information to the intent execution network element.

The second indication information is used to instruct the schematic execution network element to determine whether the execution of the first operation is abnormal.

For example, the intent translation network element sends an intent execution request message to the intent execution network element, where the intent execution request message includes the second indication information.

The intent translation request message may also include the identifier of the first intent, and the intent operation list and intent goal achievement criteria obtained by the intent translation network element from the intent knowledge feedback message.

Optionally, if the intended execution network element needs to feed back the progress information of the execution of the first operation and the second operation, the set of intended operations further includes progress indication information.

After receiving the intent execution request message, the intent execution network element may determine to execute the first operation and the second operation according to a predetermined decision algorithm.

S508. The intent-to-execute network element sends the first operation to the first network element.

For example, the intended execution network element sends an operation execution request message corresponding to the first operation to the first network element, and the operation execution request message includes information corresponding to the first operation, where the information corresponding to the first operation may include Operation ID (operationID) and operation instruction (instruction).

The first network element may execute the first operation according to the information corresponding to the first operation.

S509. The intent-to-execute network element sends the second operation to the second network element.

For example, the intended execution network element sends an operation execution request message corresponding to the second operation to the second network element, where the operation execution request message includes information corresponding to the second operation, where the information corresponding to the second operation may include Operation ID (operationID) and operation instruction (instruction).

The second network element may execute the second operation according to the information corresponding to the second operation.

S510. The intention execution network element receives execution result information of the first operation of the first intention from the first network element.

The execution result information is used to determine whether the execution of the first operation is abnormal.

For example, the intended execution network element receives an operation execution response message from the first network element in response to the operation execution request message, the operation execution response message includes the execution result information of the first operation, and the operation execution response message may also include the first operation Action ID.

For another example, the second indication information is also used to refer to the execution network element to determine whether the execution of the first operation is abnormal, and the judgment action indicates that the execution network element needs to query the execution result of the first operation from the first network element information. In this case, the intention execution network element may send an operation execution status query message to the first network element, and the operation execution status query message is used to request to query the execution result information, and the execution result information received by the intention execution network element is carried in the In response to the Operation Execution Status Query message, the Operation Execution Status Query Response message.

S511. The intention execution network element determines whether the execution of the first operation is abnormal according to the second indication information and the execution result information.

For the description about whether the execution of the first operation by the network element intending to perform is abnormal, refer to the description in the method 400, and for simplicity, details are not repeated here.

It should be understood that the intention execution network element may also receive the execution result information of the second operation from the second network element, the intention execution request message may also include the second indication information of the second operation, and the intention execution network element may also receive the execution result information of the second operation according to the second operation The second indication information and the execution result information determine whether the execution of the second operation is abnormal. The implementation method is similar to that described above for the first operation. For the sake of simplicity, it will not be repeated here.

It should be noted that the present application does not set any limitation on the number of operations corresponding to the first intent. In this embodiment, no limitation is made on the execution order of the first operation and the second operation. In the following, when the execution network element determines that the execution of the first operation is abnormal, the second operation is performed successfully or is being executed. example.

In a possible implementation, if the intended execution request message includes expected processing type indication information, the expected processing type indication information is used to indicate whether the intended execution network element needs to Inquiring whether the intended consumption network element needs to roll back the second operation, if the processing type indication information indicates that it is necessary to ask the intended consumption network element whether the second operation needs to be rolled back, then execute steps S512 to S513.

S512. When the intent execution network element determines that the execution of the first operation is abnormal, the intent execution network element sends an intent operation rollback request message to the intent management network element.

The intended operation rollback request message is used to indicate whether the second network element needs to roll back the second operation.

The description of the intention operation rollback request message is similar to the description of the intention operation rollback request message in method 400, and for simplicity, details are not repeated here.

S513. The intent management network element sends an intent operation rollback response message in response to the intent operation rollback request message to the intent execution network element, where the intent operation rollback response message is used to indicate whether the second operation needs to be rolled back.

The description of the intended operation rollback response message is similar to the description of the intention operation rollback response message in method 400 , and will not be repeated here for simplicity.

S514, the intention execution network element sends fallback instruction information to the second network element.

When the intended execution network element determines that the execution of the first operation is abnormal, or when the intended operation rollback response message is used to indicate that the second operation needs to be rolled back, the intended execution network element sends the rollback indication information to the second network element .

The rollback instruction information is used to indicate rollback of the second operation of the first intention.

The description of the rollback indication information is similar to the description of the rollback indication information in method 400, and for simplicity, details are not repeated here.

S515. The second network element rolls back the second operation according to the rollback instruction information.

The description about the rollback of the second operation by the second network element is similar to the description in method 400, and for simplicity, details are not repeated here.

If progress indication information is also included in the intention execution request message, the method further includes step S516.

S516. The intention execution network element sends an operation execution progress notification message to the intention management network element.

The operation execution progress notification message may include the identifier of the first intent and progress information. For a description of the progress information, refer to the relevant description in method 400 , and details are not repeated here for simplicity.

Optionally, if the progress indication information is also used to indicate the cycle or frequency at which the intended execution network element needs to feed back progress information, the intended execution network element can monitor the progress of the operation execution according to the cycle or frequency, and according to the cycle or frequency The frequency sends the operation execution progress notification message to the intent management network element.

If the intended consumption network element needs to obtain the progress information, the intended management network element may forward the operation execution progress notification message to the intended consumption network element.

Therefore, in this application, if there is an abnormality in the execution of a certain operation of the first intent, other operations that have been executed by the first intent can be rolled back to avoid unnecessary execution of other operations of the first intent. produce unnecessary effects.

In the embodiment described in Fig. 3 and Fig. 5, the intent translation network element will send an intent knowledge query message to the intent knowledge base to query relevant information about the intent, and the intent execution request message sent to the intent execution network element Carry the relevant information of the intention. In the embodiment of this application, the intention execution request message may only carry the information required in the intention decision-making process. If the intention execution network element needs to perform other processes, such as judging whether the operation is executed successfully, judging the operation Whether there is an exception and determine the sequence of executing multiple operations, etc., the intent execution network element can query the knowledge management module as needed.

Fig. 6 shows a schematic flowchart of an example of a method 600 intended to perform network element query information.

S601. The intent execution network element sends an intent operation query message to the intent knowledge base.

The intent-operation query message is used to query the first intent, or the first operation of the first intent.

Optionally, the intent operation query message includes at least one of the following information: an identifier of the first operation, an expression of the first intent, and a query type.

For example, the intent knowledge base includes a mapping relationship between query types, query input information, and query output information, where the query input information can refer to the information that needs to be input for the query type, and the query output information can refer to the output information that the query type will output. information, the intent execution network element determines the query type as required, and carries the required query input in the intent operation query message.

As an example but not a limitation, Table 1 shows a mapping relationship among query types, query input information, and query output information.

Table 1:

Query Type Query Input Information Query Output Information

type1/all intent expression intent goal achievement criterion (fulfillmentCriterion), execution condition (executioncondition), dependent events (events), operation execution object (entityIDList), operation instruction (instruction), execution sequence information (stepInfo), first instruction information (for example, successindication), second indication information (for example, exceptionindication), rollback scheme information (rollbacksolutionlist);

type2 intent expression execution condition (executioncondition), dependent events (events), operation execution object (entityIDList);

type3 operation identification operation execution object (entityIDList), operation instruction (instruction), execution sequence information (stepInfo), first indication information (for example, success indication), second indication information (for example, exception indication);

type4 operation identification operation execution object (entityIDList), operation instruction (instruction), execution sequence information (stepInfo), first indication information (for example, successindication), second indication information (for example, exceptionindication), rollback scheme information (rollbacksolutionlist) ;

type5 operation identifier rollback solution information (rollbacksolutionlist);

Optionally, in S602, the intent knowledge base acquires a query result.

For example, the intent knowledge base queries the corresponding query result according to the query type and query input information in the intent operation query message.

S603. The intention knowledge base sends an intention operation feedback message in response to the intention operation query message to the intention execution network element.

The intended operation feedback message includes an identifier of the first operation and a query result obtained by querying.

Therefore, in this application, the intent execution network element can query the intent knowledge base for required information as needed, avoiding carrying unnecessary information in the intent translation request message, thereby increasing the flexibility of the system for processing intents.

FIG. 7 and FIG. 8 are schematic structural diagrams of a possible communication device provided by an embodiment of the present application. These communication devices can be used to implement the functions of the intention execution network element, the intention knowledge base, the first network element, and the second network element in the above method embodiments, and thus can also realize the beneficial effects of the above method embodiments. In the embodiment of the present application, the communication device may be an intention-executing network element, an intention knowledge base, a first network element, or a second network element, or it may be an intention-executing network element, an intention knowledge base, or a , a module (such as a chip) in the second network element.

As shown in FIG. 7 , a communication device 700 includes a processing unit 710 and a transceiver unit 720 . The communication device 700 is configured to implement the functions of the intent execution network element, the intent knowledge base, the first network element, and the second network element in the above method embodiment shown in FIG. 2 . Alternatively, the communication device 700 may include a module for implementing any function or operation of the intention execution network element, the intention knowledge base, the first network element, and the second network element in the method embodiment shown in FIG. 2 above, the module It can be fully or partially realized by software, hardware, firmware or any combination thereof.

When the communication device 700 is used to implement the function of the intent execution network element in the method embodiment shown in FIG. An order of an operation and a second operation of the first intention; the processing unit 710 is configured to determine, according to the execution order information, that the network element intending to execute sends the first operation to the first network element and that the network element intending to execute sends the second operation to the second network element the sending order; the transceiver unit 910 is further configured to send the first operation to the first network element and send the second operation to the second network element according to the sending order.

Therefore, in this application, the intention execution network element can determine the sending order of multiple operations according to the order in which multiple operations are executed, so that multiple operations can be executed in order, so that multiple operations can cooperate with each other, avoiding due to Failure to execute in order leads to the failure of the execution of the intended operation or the failure to achieve the expected effect, which improves the reliability of the system to execute the intention.

Optionally, when the communication device 700 is used to implement the function intended to execute the network element in the method embodiment shown in FIG. 2 , the transceiver unit 720 is also used to receive the execution result information of the first operation from the first network element; Unit 710 is further configured to determine whether the first operation is executed successfully according to the execution result information.

Therefore, in this application, the intent execution network element can receive the execution result information of the operation, and judge whether the operation is successfully executed according to the execution result information, so as to monitor the execution status of the operation and improve the reliability of the system execution intent.

Optionally, when the communication device 700 is used to implement the function of the intention execution network element in the method embodiment shown in FIG. The execution network element determines whether the first operation is executed successfully in the instruction scheme.

Therefore, in this application, the intention execution network element can obtain the first indication information from the intention knowledge base, and determine whether the operation is successfully executed according to the first indication information, so as to improve the reliability of the system for executing the intention.

Optionally, when the communication device 700 is used to implement the function intended to execute a network element in the method embodiment shown in FIG. 2 , the transceiver unit 720 is specifically configured to send the first operation to the first network element. If the execution is successful, the second operation is sent to the second network element.

Therefore, in this application, the intent-executing network element can issue subsequent operations after determining that the pre-order operations are executed successfully, so as to avoid performing subsequent operations because the pre-order operations have not been successfully executed, resulting in operation failure or execution effect poor.

Optionally, when the communication device 700 is used to implement the function intended to execute the network element in the method embodiment shown in FIG. 2 , the transceiver unit 720 is also used to receive progress indication information, which is used to indicate that the device needs to feedback progress Information, the progress information is used to indicate the execution progress of the first operation and the second operation.

Therefore, in this application, the network element intending to execute can be required to feed back the execution progress of the operation, so that the execution status of the operation can be monitored and the reliability of the system executing the intent can be improved.

When the communication device 700 is used to realize the function of the intention knowledge base in the method embodiment shown in FIG. The sequence of one operation and the second operation for the first intent.

Therefore, in this application, the intention execution network element can determine the sending order of multiple operations according to the order in which multiple operations are executed, so that multiple operations can be executed in order, so that multiple operations can cooperate with each other, avoiding due to Failure to execute in order leads to the failure of the execution of the intended operation or the failure to achieve the expected effect, which improves the reliability of the system to execute the intention.

Optionally, when the communication device 700 is used to realize the function of the intent knowledge base in the method embodiment shown in FIG. for determining whether the first operation is performed successfully.

When the communication device 700 is used to realize the function of the first network element in the method embodiment shown in FIG. 2 , the transceiver unit 720 is used to receive the first operation; the processing unit 710 is used to execute the first operation.

Optionally, when the communication device 700 is used to realize the function of the first network element in the method embodiment shown in FIG. It is determined whether the first operation was performed successfully.

When the communication device 700 is used to realize the function of the second network element in the method embodiment shown in FIG. 2 , the transceiver unit 910 is used to receive the second operation; the processing unit 710 is used to execute the second operation.

More detailed descriptions about the processing unit 710 and the transceiver unit 720 can be directly obtained by referring to the relevant descriptions in the method embodiment shown in FIG. 2 , and will not be repeated here.

As shown in FIG. 7 , a communication device 700 includes a processing unit 710 and a transceiver unit 720 . The communication device 700 is configured to implement the functions of the intent execution network element, the intent knowledge base, the first network element, and the second network element in the above method embodiment shown in FIG. 2 . Alternatively, the communication device 700 may include a module for implementing any function or operation of the intention execution network element, the intention knowledge base, the first network element, and the second network element in the method embodiment shown in FIG. 4 above, the module It can be fully or partially realized by software, hardware, firmware or any combination thereof.

When the communication device 700 is used to implement the function of the intended execution network element in the method embodiment shown in FIG. 4 , the transceiver unit 720 is configured to receive the execution result information of the first operation of the first intention from the first network element; It is configured to determine that the execution of the first operation is abnormal according to the execution result information; the transceiving unit 720 is further configured to send rollback indication information to the second network element, where the rollback indication information is used to indicate rollback of the second operation with the first intention.

Therefore, in this application, if the execution of a certain operation of the first intent is abnormal, other operations that have been executed by the first intent can be rolled back, so as to avoid the resources and signaling caused by other operations of the first intent being executed all the time. Waste, which in turn can improve the execution efficiency of intentions.

Optionally, when the communication device 700 is used to implement the function of the intention execution network element in the method embodiment shown in FIG. The execution network element of the instruction map determines that the execution of the first operation is abnormal.

Optionally, when the communication device 700 is used to implement the function intended to execute the network element in the method embodiment shown in FIG. back way.

Therefore, in this application, the intent execution network element can indicate the rollback mode of the rollback operation to the network element that performs the operation, so as to prevent the network element that does not have the rollback capability from being unable to roll back the operation successfully, and improves the reliability of the system to execute the intent .

Optionally, when the communication device 700 is used to implement the function intended to execute a network element in the method embodiment shown in FIG. 4 , the transceiver unit 720 is specifically configured to send the first operation to the first network element. If the execution is successful, the second operation is sent to the second network element.

Therefore, in this application, if the execution of a certain operation of the first intent is abnormal, other operations that have been executed by the first intent can be rolled back, so as to avoid the resources and signaling caused by other operations of the first intent being executed all the time. Waste, which in turn can improve the execution efficiency of intentions. Optionally, when the communication device 700 is used to implement the function intended to execute the network element in the method embodiment shown in FIG. 4 , the transceiver unit 720 is also used to receive progress indication information, which is used to indicate that the device needs to feedback progress The progress information is used to indicate the execution progress of the first operation and the second operation, and is also used to send the progress information according to the progress indication information.

Therefore, in this application, the network element intending to execute can be required to feed back the execution progress of the operation, so that the execution status of the operation can be monitored and the reliability of the system executing the intent can be improved.

When the communication device 700 is used to realize the function of the intention knowledge base in the method embodiment shown in FIG. Whether the execution is abnormal.

Therefore, in this application, if there is an abnormality in the execution of a certain operation of the first intent, other operations that have been executed by the first intent can be rolled back to avoid unnecessary execution of other operations of the first intent. Create unwanted effects that increase the reliability of the system's ability to carry out its intent.

Optionally, when the communication device 700 is used to realize the function of the intent knowledge base in the method embodiment shown in FIG. Used to determine the fallback mode of the second operation.

When the communication device 700 is used to implement the function of the first network element in the method embodiment shown in FIG. 4 , the transceiving unit 720 is used to send execution result information of the first operation of the first intent.

When the communication device 700 is used to realize the function of the second network element in the method embodiment shown in FIG. Two operations; the processing unit 710 is configured to roll back the second operation.

More detailed descriptions about the processing unit 710 and the transceiver unit 720 can be directly obtained by referring to the related descriptions in the method embodiment shown in FIG. 3 , and will not be repeated here.

As shown in FIG. 8 , the communication device 800 includes a processor 810 and an interface circuit 820 . The processor 810 and the interface circuit 820 are coupled to each other. It can be understood that the interface circuit 820 may be a transceiver or an input/output interface. Optionally, the communication device 800 may further include a memory 830 for storing instructions executed by the processor 810 or storing input data required by the processor 810 to execute the instructions or storing data generated after the processor 810 executes the instructions.

When the communication device 800 is used to implement the method shown in FIG. 2 or FIG. 4 , the processor 810 is used to implement the functions of the above-mentioned processing unit 1010 , and the interface circuit 820 is used to implement the functions of the above-mentioned transceiver unit 1020 .

When the communication device 800 is used to implement the method shown in FIG. 2 or FIG. 4 , the communication device 800 includes a processor 810 and an interface circuit 820 . The processor 810 and the interface circuit 820 are coupled to each other. It can be understood that the interface circuit 820 may be a transceiver or an input/output interface. Optionally, the communication device 800 may further include a memory 830 for storing instructions executed by the processor 810, or storing input data required by the processor 810 to execute the instructions, or storing data generated by the processor 810 after executing the instructions.

When the communication device 800 is used to implement the method shown in FIG. 2 or FIG. 4 , the processor 810 is used to implement the functions of the processing unit 710 , and the interface circuit 820 is used to implement the functions of the transceiver unit 720 .

When the above-mentioned communication device is a chip applied to a network element intended to execute, the chip of the network element intended to execute implements the function of the network element intended to execute in the above method embodiment. The intention execution network element chip receives information from other modules (such as radio frequency modules or antennas) in the intention execution network element, and the information is sent to the intention execution network element by the intention knowledge base; Other modules in the network element (such as a radio frequency module or an antenna) send information, and the information is intended to be sent by the network element to the first network element or the second network element.

When the communication device is a chip applied to an intent knowledge base, the intent knowledge base chip implements the functions of the intent knowledge base in the foregoing method embodiments. The intention knowledge base chip receives information from other modules (such as radio frequency modules or antennas) in the intention knowledge base, and the information is sent to the intention knowledge base by the intention execution network element; or, the intention knowledge base chip sends information to the intention knowledge base Other modules (such as radio frequency modules or antennas) send information, which is sent from the intent knowledge base to the intent execution network element.

It can be understood that the processor in the embodiments of the present application can be a central processing unit (Central Processing Unit, CPU), and can also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application-specific integrated circuits (Application Specific Integrated Circuit, ASIC), Field Programmable Gate Array (Field Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. A general-purpose processor can be a microprocessor, or any conventional processor.

Memory in the embodiment of the present application can be random access memory (Random Access Memory, RAM), flash memory, read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable Programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), registers, hard disk, mobile hard disk, CD-ROM or any other form of storage medium known in the art . An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be a component of the processor. The processor and storage medium can be located in the ASIC. In addition, the ASIC can be located in a network device or a terminal device. Of course, the processor and the storage medium may also exist in the network device or the terminal device as discrete components.

In the above embodiments, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer programs or instructions. When the computer program or instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are executed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a terminal device, or other programmable devices. The computer program or instructions may be stored in or transmitted via a computer-readable storage medium. The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server integrating one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a DVD; it may also be a semiconductor medium, such as a solid state disk (solid state disk, SSD).

In each embodiment of the present application, if there is no special explanation and logical conflict, the terms and/or descriptions between different embodiments are consistent and can be referred to each other, and the technical features in different embodiments are based on their inherent Logical relationships can be combined to form new embodiments.

It should be understood that in this embodiment of the application, the numbers "first", "second"... are only used to distinguish different objects, such as different network devices, and do not limit the scope of the embodiment of this application. Examples are not limited to this.

It should also be understood that in this application, "when", "if" and "if" all mean that the network element will make corresponding processing under certain objective circumstances, and it is not a limited time, and it does not require the network element to There must be an action of judgment during implementation, and it does not mean that there are other restrictions.

It should also be understood that in each embodiment of the present application, "A corresponds to B" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B may also be determined according to A and/or other information.

It should also be understood that the term "and/or" in this article is only an association relationship describing associated objects, indicating that there may be three relationships, for example, A and/or B may indicate: A exists alone, and A and B exist simultaneously. B, there are three situations of B alone. In addition, the character "/" in this article generally indicates that the contextual objects are an "or" relationship.

The meaning of the expression similar to "the item includes one or more of the following: A, B, and C" appearing in this application, unless otherwise specified, usually means that the item can be any of the following: A; B ;C;A and B;A and C;B and C;A,B and C;A and A;A,A and A;A,A and B;A,A and C,A,B and B;A , C and C; B and B, B, B and B, B, B and C, C and C; C, C and C, and other combinations of A, B and C. The above is an example of the three elements of A, B and C to illustrate the optional items of the project. When the expression is "the project includes at least one of the following: A, B, ..., and X", it is in the expression When there are more elements, then the applicable entries for this item can also be obtained according to the aforementioned rules.

It can be understood that the various numbers involved in the embodiments of the present application are only for convenience of description, and are not used to limit the scope of the embodiments of the present application. The size of the serial numbers of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its functions and internal logic.

Claims (20)

1. A method intended to be performed, characterized in that the method comprises:

   The intention execution network element receives execution order information from the intention knowledge base, where the execution order information is used to indicate the order of executing the first operation of the first intention and the second operation of the first intention;

   determining, according to the execution sequence information, a sending sequence in which the intention-to-execute network element sends the first operation to the first network element and the intention-to-execute network element sends the second operation to the second network element;

   The intent execution network element sends the first operation to the first network element and sends the second operation to the second network element according to the sending order.
2. The method of claim 1, further comprising:

   receiving, by the intention execution network element, execution result information of the first operation from the first network element;

   The intention execution network element determines whether the first operation is executed successfully according to the execution result information.
3. The method of claim 2, further comprising:

   The intent execution network element receives first indication information from the intent knowledge base, where the first indication information is used to instruct the intent execution network element to determine whether the first operation is executed successfully.
4. The method according to any one of claims 1 to 3, wherein the intent execution network element sends the first operation to the first network element and sends the operation to the second network element according to the sending order. The element sends the second operation, including:

   The intent execution network element sends the first operation to the first network element, and if the intent execution network element determines that the first operation is successfully executed, the intention execution network element sends the second operation to the second The network element sends the second operation.
5. The method according to any one of claims 1 to 4, further comprising:

   The intention execution network element receives progress indication information, the progress indication information is used to indicate that the intention execution network element needs to feed back progress information, and the progress information is used to indicate the execution of the first operation and the second operation schedule;

   The intention execution network element sends the progress information according to the progress indication information.
6. The method according to claim 5, wherein the progress indication information is further used to indicate the period or frequency at which the intention execution network element needs to feed back the progress information.
7. A method intended to be performed, characterized in that the method comprises:

   The intent knowledge base sends execution sequence information to the intent execution network element, and the intent execution network element receives the execution sequence information from the intent knowledge base, where the execution sequence information is used to indicate the execution of the first operation of the first intent and a sequence of second operations of said first intent;

   determining, according to the execution sequence information, a sending sequence in which the intention-to-execute network element sends the first operation to the first network element and the intention-to-execute network element sends the second operation to the second network element;

   The intent execution network element sends the first operation to the first network element and sends the second operation to the second network element according to the sending order.
8. The method of claim 7, further comprising:

   The first network element sends the execution result information of the first operation to the intended execution network element, and the intended execution network element receives the execution result information from the first network element;

   The intention execution network element determines whether the first operation is executed successfully according to the execution result information.
9. The method of claim 8, further comprising:

   The intention knowledge base sends first indication information to the intention execution network element, and the intention execution network element receives the first indication information from the intention knowledge base, the first indication information is used to indicate the The intent execution network element determines whether the first operation is executed successfully.
10. The method according to any one of claims 7 to 9, wherein the intention execution network element sends the first operation to the first network element and the second network element to the second network element according to the sending order. The element sends the second operation, including:

    The intent execution network element sends the first operation to the first network element, and if the intent execution network element determines that the first operation is successfully executed, the intention execution network element sends the second operation to the second The network element sends the second operation.
11. The method according to any one of claims 7 to 10, characterized in that, the method further comprises: the intention execution network element receiving progress indication information, the progress indication information being used to indicate the intention execution network element It is necessary to feed back progress information, where the progress information is used to indicate the execution progress of the first operation and the second operation;

    The intention execution network element sends the progress information according to the progress indication information.
12. The method according to claim 11, wherein the progress indication information is further used to indicate the period or frequency at which the intention execution network element needs to feed back the progress information.
13. A device intended to be executed, characterized in that the device comprises a transceiver unit and a processing unit,

    The transceiving unit is configured to receive execution sequence information from the intent knowledge base, where the execution sequence information is used to indicate the sequence of executing the first operation of the first intent and the second operation of the first intent;

    The processing unit is configured to determine, according to the execution order information, a sending order in which the intention-to-execute network element sends the first operation to the first network element and the intention-to-execute network element sends the second operation to the second network element;

    The transceiving unit is further configured to send the first operation to the first network element and send the second operation to the second network element according to the sending sequence.
14. The apparatus of claim 13 wherein,

    The transceiving unit is further configured to receive execution result information of the first operation from the first network element;

    The processing unit is further configured to determine whether the first operation is executed successfully according to the execution result information.
15. The apparatus of claim 14 wherein,

    The transceiving unit is further configured to receive first indication information from an intent knowledge base, where the first indication information is used to instruct the intent execution network element to determine whether the first operation is executed successfully.
16. Apparatus according to any one of claims 13 to 15, characterized in that

    The transceiving unit is specifically configured to send the first operation to the first network element, and send the second operation to the second network element when it is determined that the first operation is performed successfully.
17. Apparatus according to any one of claims 13 to 16, characterized in that

    The transceiving unit is further configured to receive progress indication information, the progress indication information is used to indicate that the device needs to feed back progress information, and the progress information is used to indicate the execution progress of the first operation and the second operation ;

    The processing unit is further configured to send the progress information according to the progress indication information.
18. The device according to claim 17, wherein the progress indication information is further used to indicate the period or frequency at which the device needs to feed back the progress information.
19. A communication device, characterized in that it includes at least one processor, and the at least one processor is used to execute a computer program stored in a memory, so that the device implements the method according to any one of claims 1 to 6 , or to enable the device to implement the method according to any one of claims 7 to 12.
20. A computer-readable storage medium, characterized by comprising a computer program, which, when the computer program is run on a computer, causes the computer to execute the method according to any one of claims 1 to 6, or causes the The computer executes the method according to any one of claims 7 to 12.

Images