CN116095706A

CN116095706A - Method and device for intention execution

Info

Publication number: CN116095706A
Application number: CN202111278495.0A
Authority: CN
Inventors: 王楚捷; 李贤明; 于益俊
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-10-30
Filing date: 2021-10-30
Publication date: 2023-05-09
Also published as: WO2023072023A1

Abstract

The present application provides a method intended to be performed, the method comprising: the intention execution network element receives execution order information from the intention knowledge base, the execution order information being used to indicate an order in which a first operation of the first intention and a second operation of the first intention are executed; the intention execution network element determines a transmission sequence of the intention execution network element for transmitting the first operation to the first network element and the intention execution network element for transmitting the second operation to the second network element according to the execution sequence information; 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, so that the problem that the intention operation fails to be executed or the expected effect is not achieved due to out-of-sequence execution is avoided, and the reliability of the system execution intention is improved.

Description

Method and device for intention execution

Technical Field

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

Background

At present, a cognitive network management system can be adopted when a user performs automation work. The cognitive network management system supports the processing of intents, where intent refers to a desire for an acting system. To achieve the intention, a plurality of network devices are required to perform a plurality of operations of the intention, respectively, for example, a plurality of network devices perform a plurality of sub-operations in the intention operation, respectively. Whether each network device performs an operation successfully or not affects the effect after the intention. However, the mechanism for managing the intended operation does not consider the cooperation management among the operations, which results in lower success rate and effect of the intended implementation, so a method for executing the intended operation is needed to improve the reliability of the system execution intention.

Disclosure of Invention

The application provides a method and a device for executing intention, which can improve the reliability of the execution intention of a system.

In a first aspect, a method intended for execution is provided, which may be performed by an intended execution network element or a chip in an intended execution network element, the method comprising: the intention execution network element receives execution order information from the intention knowledge base, the execution order information being used to indicate an order in which a first operation of the first intention and a second operation of the first intention are executed; the intention execution network element determines a transmission sequence of the intention execution network element for transmitting the first operation to the first network element and the intention execution network element for transmitting the second operation to the second network element according to the execution sequence information; the intention-to-perform network element sends a first operation to the first network element and a second operation to the second network element according to the sending order.

Therefore, in the application, the network element for intention execution can determine the sending sequence of sending the plurality of operations according to the sequence of executing the plurality of operations, so that the plurality of operations can be executed in sequence, the plurality of operations can be mutually matched, the problem that the intention operation fails to be executed or the expected effect is not achieved due to the fact that the operations are executed in sequence is avoided, and the reliability of the intention of system execution is improved.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the method comprises the steps that an intention execution network element receives execution result information of a first operation from a first network element; and the intention execution network element determines whether the first operation is successfully executed according to the execution result information.

Therefore, in the application, the network element which is intended to be executed can receive the execution result information of the operation, and judge whether the operation is executed successfully or not according to the execution result information, so that the execution state of the operation can be monitored, and the reliability of the system execution intention is improved.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the intention execution network element receives first indication information from an intention knowledge base, wherein the first indication information is used for indicating the intention execution network element to determine whether the first operation is successfully executed.

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

With reference to the first aspect, in certain implementation manners of the first aspect, the intention is to perform a sending, by the network element, a first operation to the first network element and a second operation to the second network element according to a sending order, including: the intention execution network element sends a first operation to the first network element, and if the intention execution network element determines that the first operation is successfully executed, the intention execution network element sends a second operation to the second network element.

Therefore, in the application, the network element which is intended to execute can issue the subsequent operation under the condition that the successful execution of the preamble operation is determined, so that the subsequent operation is prevented from being executed because the preamble operation is not executed successfully, and the operation failure or the execution effect is prevented from being poor.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the method comprises the steps that an intention execution network element receives progress indication information, the progress indication information is used for indicating that the intention execution network element needs feedback of the progress information, and the progress information is used for indicating execution progress of a first operation and a second operation; and the intention execution network element sends the progress information according to the progress indication information.

Therefore, in the application, the execution progress of the feedback operation of the network element is required, so that the execution state of the monitoring operation can be realized, and the reliability of the system execution intention is improved.

With reference to the first aspect, in certain implementations of the first aspect, the progress indication information is further used to indicate a period or a frequency at which the network element needs to feed back the progress information is intended to be performed.

Therefore, in the application, the execution progress of the operation can be required to be fed back periodically or according to the frequency by the network element, so that the execution state of the monitoring operation can be realized, and the reliability of the system execution intention is improved.

In a second aspect, there is provided an apparatus intended for execution, the apparatus comprising a processing unit and a transceiving unit for receiving execution order information from an intent knowledge base, the execution order information being for indicating an order in which a first operation of a first intent and a second operation of the first intent are executed; the processing unit is used for determining a sending sequence of the first operation which is sent to the first network element by the intention execution network element and the second operation which is sent to the second network element by the intention execution network element according to the execution sequence information; and the receiving and transmitting unit is also used for transmitting the first operation to the first network element and the second operation to the second network element according to the transmission sequence.

With reference to the second aspect, in some implementations of the second aspect, the transceiver is further configured to receive, from the first network element, execution result information of the first operation; and the processing unit is also used for determining whether the first operation is successfully executed according to the execution result information.

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, where the first indication information is used to indicate that the network element is intended to perform to determine whether the first operation is performed successfully.

With reference to the second aspect, in some implementations of the second aspect, the transceiver unit is specifically configured to send the first operation to the first network element, and send the second operation to the second network element if it is determined that the first operation is performed successfully.

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

With reference to the second aspect, in certain implementations of the second aspect, the progress indication information is further used to indicate a period or a frequency at which the device needs to feed back the progress information.

In a third aspect, there is provided a method intended for execution, the method being executable by an intended execution network element or a chip in an intended execution network element, the method comprising: the method comprises the steps that an intention execution network element receives execution result information of a first operation of a first intention from a first network element; the intention execution network element determines that the execution of the first operation is abnormal according to the execution result information; the intention execution network element sends back-off indication information to the second network element, wherein the back-off indication information is used for indicating a second operation for backing off the first intention.

Therefore, in the application, if the execution of a certain operation of the first intention is abnormal, other executed operations of the first intention can be rolled back, so that the waste of resources and signaling caused by the fact that other operations of the first intention are always executed is avoided, and further the execution efficiency of the intention can be improved.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the intention execution network element receives second indication information from the intention knowledge base, wherein the second indication information is used for indicating the intention execution network element to determine that the execution of the first operation is abnormal.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the intention execution network element receives back-off scheme information from the intention knowledge base, the back-off scheme information being used for indicating a back-off manner of the second operation, and the back-off indication information being further used for indicating the back-off manner of the second operation.

Therefore, in the application, the network element which is intended to execute can indicate the rollback mode of the rollback operation to the network element which executes the operation, so that the situation that the network element which does not have rollback capability cannot successfully rollback the operation is avoided, and the reliability of the system execution intention is improved.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: and the intention execution network element determines a rollback mode of the second operation according to the execution result information and the rollback scheme information.

Therefore, in the application, the network element which is intended to execute determines that the first operation is executed abnormally, the network element which is intended to execute can determine which abnormality the abnormality belongs to according to the execution result information, and determine the rollback mode of the second operation according to the rollback scheme information which determines the rollback scheme information of the second operation under the abnormal condition, so that the reliability of the system execution intention is improved.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the method comprises the steps that an intention execution network element receives progress indication information, the progress indication information is used for indicating that the intention execution network element needs feedback of the progress information, and the progress information is used for indicating execution progress of a first operation and a second operation; and the intention execution network element sends the progress information according to the progress indication information.

With reference to the third aspect, in some implementations of the third aspect, the progress indication information is further used to indicate a period or a frequency at which the network element needs to feed back the progress information is intended to be performed.

In a fourth aspect, an apparatus for performing a first operation is provided, the apparatus including a processing unit and a transceiver unit, the transceiver unit configured to receive, from a first network element, execution result information of a first operation of a first intention; the processing unit is used for determining that the execution of the first operation is abnormal according to the execution result information; the transceiver is further configured to send back-off indication information to the second network element, where the back-off indication information is used to indicate a second operation of backing off the first intention.

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 intention knowledge base, where the second indication information is used to indicate that the intention-to-execute 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 back-off scheme information from the intent knowledge base, where the back-off scheme information is used to indicate a back-off manner of the second operation, and the back-off indication information is further used to indicate the back-off manner of the second operation.

With reference to the fourth aspect, in some implementations of the fourth aspect, the processing unit is further configured to determine a fallback manner of the second operation according to the execution result information and the fallback 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, where the progress indication information is used to indicate that the device needs to feed back the progress information, and the progress information is used to indicate execution progress of the first operation and the second operation; and the receiving and transmitting unit is also used for transmitting the progress information according to the progress indication information.

With reference to the fourth aspect, in some implementations of the fourth aspect, the progress indication information is further used to indicate a period or a frequency at which the network element needs to feed back the progress information is intended to be performed.

In a fifth aspect, a communication apparatus is provided, which may include a processing unit, a transmitting unit, and a receiving unit. Alternatively, the transmitting unit and the receiving unit may also be transceiving units.

When the apparatus is intended to perform a network element, the processing unit may be a processor and the transmitting unit and the receiving unit may be transceivers; the apparatus may further include a storage unit, which may be a memory; the storage unit is configured to store instructions, and the processing unit executes the instructions stored by the storage unit, so that the network element is intended to execute any method of the first aspect or the third aspect. When the apparatus is a chip intended to execute within a network element, the processing unit may be a processor, and the transmitting unit and the receiving unit may be input/output interfaces, pins or circuits, etc.; the processing unit executes instructions stored by the storage unit to cause the chip to perform the method of the first or third aspect. The storage unit is used for storing instructions, and the storage unit may be a storage unit (for example, a register, a cache, etc.) in the chip, or may be a storage unit (for example, a read-only memory, a random access memory, etc.) located outside the chip in the network element for which execution is intended.

In a sixth aspect, there is provided a communication device comprising a processor and interface circuitry for receiving signals from or transmitting signals to the processor from or to other communication devices than the communication device, the processor being operable to implement any of the methods of the first or third aspects described above by logic circuitry or executing code instructions.

In a seventh aspect, there is provided a computer readable storage medium having stored therein a computer program or instructions which, when executed, implement any of the methods of the first or third aspects described above.

In an eighth aspect, there is provided a computer program product comprising instructions which, when executed, implement any of the methods of the preceding first or third aspects.

In a ninth aspect, there is provided a computer program comprising code or instructions which, when executed, implement the method of any possible implementation of the first or third aspect described above.

In a tenth aspect, a chip system is provided, the chip system comprising a processor and possibly a memory, for implementing at least one of the methods described in the foregoing first or third aspects. The chip system may be formed of a chip or may include a chip and other discrete devices.

In an eleventh aspect, there is provided a communication system comprising the apparatus of any of the second or fourth aspects.

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

Drawings

FIG. 1 is a schematic diagram of a system intended for execution as provided by embodiments of the application.

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

Fig. 3 is a schematic flow chart of another example intended to perform a method provided by an embodiment of the present application.

Fig. 4 is a schematic flowchart of an example of a method for performing rollback operations according to an embodiment of the present application.

Fig. 5 is a schematic flow chart of another example of an in-execution rollback operation method provided by an embodiment of the present application.

Fig. 6 is a schematic flowchart of an embodiment of the present application for performing network element query information.

Fig. 7 and 8 are schematic structural diagrams of possible communication devices according to embodiments of the present application.

Detailed Description

The technical solutions in the present application will be described below with reference to the accompanying drawings.

The technical scheme of the application can be applied to various network function virtualization (network function virtualization, NFV) systems, and the system can describe the service technical scheme, the network construction scheme and the network operation and maintenance method of the current operators into modes and strategies by using standard formal languages, and realize the technical scheme and the construction scheme based on the modes and the strategies. For example, the technical solution of the present application may be applied to one or more of the following systems: wireless intent driven network (wireless intent driven network, widnn) systems, experiential network intelligence (experiential networked intelligence, ENI) systems, intent driven management services (intent driven management service, IDMS) systems or open network automation platform (open network automation platform, ONAP) systems, and the like.

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

The intention is: refers to the desire for a system of action. The intent may include one or more of the following: requirements, intent targets, and constraints.

Intent example: objects after the intent is instantiated. For example, in this application, intent may be replaced with an intended instance.

The intended expression: the expression used for bearing the intention comprises one or more of the following: an intent action name, an intent action attribute, an intent action object name, or an intent action object attribute. The intent expression has a specific syntax and semantics.

Intent targets: for indicating the target value that is intended to be achieved.

Intent translation: the intent is translated into a flow of intent executable commands or rules or sub-intents.

The intention is to perform: issuing the intention executable command, the sub intention and the rule, and adjusting the intention executable command, the sub intention and the rule according to the network environment and the intention achievement condition.

Intent executable command: a series of instructions are intended to be formed by operations such as translation decisions.

Intention mode: the syntax and semantics of the intended expression are specified. The intent pattern may include one or more of the following: the field, the value range of the field, the type of the field and the hierarchical relationship among the fields. For example, the field may be used to describe the type, name, or consumer of the intent pattern.

Intent state: the intent states include an active state, a conflict state, a deactivated state, a sleep state, etc. Wherein, the intent is in an active state may be understood as the intent being performed; the intent being in a conflict state may be understood as the intent being in conflict with the intent in the system; the intention being in a deactivated state may be understood as the intention not being performed; the intention in the sleep state may be understood as that the intended target of the intention is temporarily stopped from being executed because it is not achieved for a long period of time.

Intent creation: creating an intention in the intention system and creating a corresponding intention context.

Knowledge of intent: the intent knowledge is a relevant parameter 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: an intent corresponding executable operation, an intent acting entity identification, or an intent acting entity type.

Intent operation: executable operations corresponding to the intent targets. The intent operations include one or more intent sub-operations.

Intention operation: an intended sub-operation may include one or more operation instructions that are executed by an execution object.

Intent maintenance: the intent executable operations are adjusted according to changes in the system network environment to expect to achieve the intent goal.

The intention is to achieve: the system detects that the KPI values in the network reach target values in the intent expression, or achieve the intent goal.

To facilitate an understanding of the embodiments of the present application, an intentional system suitable for use in the methods provided by the embodiments of the present application is first described in detail in connection with FIG. 1. Fig. 1 shows a schematic diagram of a system 100 suitable for processing intent of the methods provided by embodiments of the present application. As shown in fig. 1, the system 100 includes an intended consumer network element 110, an intended provider network element 120, and a network device 130. Wherein the intent providing network element may include an intent management network element 121, an intent translation network element 122, an intent execution network element 123, and a knowledge management network element 124. The knowledge management network element 124 may include an intent knowledge base therein.

The intended-consumer network element 110, which may also be referred to as an intended consumer, is the intended consumer entity. For example, the intended-to-consume network element 110 may be an operation support system (operations support systems, OSS), a service support system (business support systems, BSS), an Application (APP), or other user equipment. For an IDMS system, the intended-consumption network element 110 may be a service consumer or management service (management service, mnS) network element, such as a network management system (network management system, NMS). The intent-to-consume network element 110 may be in communication with the intent-to-provide network element 120, e.g., the intent-to-consume network element 110 may send a request to the intent-to-provide network element 120 to create an intent or to implement an intent.

The intention management network element 121 may be used for management of an intention mode, and it may receive request information from the intention consumption network element 110 and process the request information. The intention management network element 121 may comprise an intention pattern library for storing intention patterns. The intention management network element 121 may further include an intention instance library, through which the intention management network element 121 may acquire state information of an intention pattern, an intention target, and an operation corresponding to the intention.

The intent translation network element 122 may receive translation request information from the intent management network element 121, implementing the intent translation function. The intent translation network element 122 may also obtain intent patterns from the intent management network element 121, and check the syntax semantics of the information provided by the intent consumption network element 110.

The intention execution network element 123 may receive commands from the intention management network element 122 and the intention translation network element 121 and implement the relevant operations of the intention.

The knowledge management network element 124 may manage an intent knowledge base, where the intent knowledge base stores knowledge about the intent, and may support other network elements to query for knowledge about the intent.

It should be noted that the system for processing different intents may also include other network elements having corresponding functions.

For instance, for a wIDN system, the system may also include a knowledge management network element and an intent knowledge base. Wherein the intention management network element is used for managing intention knowledge. The intent knowledge base may be a sub-module of a knowledge management network element for storing the intent knowledge. The intention management network element may further comprise an intention pattern library for storing intention patterns and an intention instance library for storing intents.

For an ENI system, the ENI system may further comprise one or more of the following: an input functional network element, an output functional network element, an analysis functional network element and a decision functional network element. The input functional network element may include a data collection network element and a normalization network element, which are configured to receive data of an external system and normalize the data. The output functional network element may include an output network element and a denormalization network element, which are configured to convert an internal command of the system into a format that can be processed by an external system and send the converted command to the external system. The analysis function network element may be used to perform a perceptual analysis of existing network states and to predict future network states. For example, the analysis function network element may include a knowledge management network element, a context aware network element, and a cognitive management network element. The knowledge management network element can manage the intention knowledge, the context awareness network element can conduct awareness analysis on the existing network state, and the cognition management network element can conduct management analysis. The intention management network element and the intention translation network element may be sub-network elements in the analysis function network element. The decision function network element is used for generating a new operation command according to a strategy target and arranging the operation command on the basis of network state awareness, and sending the operation command to the output network element, and the decision function network element can comprise a strategy management network element, a situation awareness network element and a driving management network element, wherein the strategy management network element is used for managing an intention strategy, the situation awareness network element is used for carrying out perception analysis on the network state, and the driving management network element is used for carrying out driving management of intention.

For an IDMS system, the intended consumption network element may be a network management system (network management system, NMS), the intended providing network element may be a device management system (element management system, EMS), the intended management network element, the intended translation network element, and the intended execution network element may be sub-modules of the intended providing network element.

The assistance system 130 may include at least one network device therein, each of which may be in communication with the intent providing network element 120, e.g., the intent execution network element 123 in the intent providing network element 120 may send an intent execution operation request to any network device in the assistance system 130.

In the embodiment of the present application, the network device in the assistance system 130 may be any device with a wireless transceiver function. The apparatus includes, but is not limited to: an evolved Node B (eNB), a radio network controller (radio network controller, RNC), a Node B (Node B, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home base station (home evolved NodeB, or home Node B, HNB, for example), a Base Band Unit (BBU), a satellite, an unmanned base station, an Access Point (AP) in a wireless fidelity (wireless fidelity, wiFi) system, a wireless relay Node, a wireless backhaul Node, a transmission point (transmission point, TP), or a transmission reception point (transmission and reception point, TRP), etc., may also be 5G, such as NR, a gNB in a system, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or may also be a network Node, such as a baseband unit (BBU), or a Distributed Unit (DU), etc., constituting a gNB or a transmission point.

In some deployments, the gNB may include a Centralized Unit (CU) and DUs. The gNB may also include an active antenna unit (active antenna unit, AAU). The CU implements part of the functionality of the gNB and the DU implements part of the functionality of the gNB, e.g. the CU is responsible for handling non-real time protocols and services, implementing radio resource control (radio resource control, RRC), packet data convergence layer protocol (packet data convergence protocol, PDCP) layer functions. The DUs are responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (radio link control, RLC), medium access control (medium access control, MAC) and Physical (PHY) layers. The AAU realizes part of physical layer processing function, radio frequency processing and related functions of the active antenna. Since the information of the RRC layer may eventually become information of the PHY layer or be converted from the information of the PHY layer, under this architecture, higher layer signaling, such as RRC layer signaling, may also be considered to be transmitted by the DU or by the du+aau. It is understood that the network device may be a device comprising one or more of a CU node, a DU node, an AAU node. In addition, the CU may be divided into network devices in an access network (radio access network, RAN), or may be divided into network devices in a Core Network (CN), which is not limited in this application.

It should be noted that the solution of the present application may be applied to other systems including corresponding network elements, and the present application is not limited thereto. It will be appreciated that the network elements or functions described above may be either network elements in a hardware device, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). Alternatively, the network element or the function may be implemented by one device, or may be implemented by a plurality of devices together, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.

Currently, in order to achieve the intended goal, a plurality of network devices are required to perform a plurality of operations of the intention, respectively. The success or failure of each operation will have an impact on the effect after the intended execution. However, the mechanism for managing the intended operation does not consider the cooperation management between operations, resulting in lower success rate and effect of the intended execution, so there is a need for an intended execution method that can improve the reliability of the system execution intention.

Fig. 2 shows an exemplary flow chart of an intended execution method 200 provided herein.

S201, the intention execution network element receives execution sequence information from an intention knowledge base.

The execution order information is used to indicate an order in which a first operation of the first intention and a second operation of the first intention are performed.

The execution order information may be stored in the intent knowledge base in an intent knowledge base initialization and update procedure, wherein the intent knowledge base may be a sub-module of the knowledge management network element.

Wherein the first operation may include a plurality of operation instructions, which may be performed entirely by the first network element (e.g., network device # 1); the second operation may also include a plurality of operation instructions, which may be performed entirely by the second network element (e.g., network device # 2).

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

For example, the second network element performing the second operation needs to rely on the first network element performing the first operation successfully.

The first operation of the first intent and the second operation of the first intent may be one or more sub-operations of the intended operation corresponding to the first intent. For example, the first intent corresponding intent operation includes three sub-operations, respectively: a first sub-operation, a second sub-operation, and a third sub-operation. The execution object of the first sub-operation is a first network element, and the execution objects of the second sub-operation and the third sub-operation are second network elements. If the three sub-operations are executed in the order of the first sub-operation, the second sub-operation, and the third sub-operation, the first operation in the embodiment of the present application may be the first sub-operation, and the second operation may be a merging operation of the second sub-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 may be the first sub-operation, the second operation may be the second sub-operation, and the embodiment of the present application further 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 order of the first operation, the second operation, and the third operation.

It should be understood that the present application does not limit the execution order information to indicate the number of the plurality of operations in the order in which the plurality of operations are executed, nor the number of execution objects that need to execute the operations, as an example and not by way of limitation, and as an example, the cell relocation is taken as an intended target of the first intention. The first intended intent operation includes 6 sub-operations, the 6 sub-operations being:

first sub-operation: deleting the adjacent cell relation with the cell A, which is executed by a first network element;

second sub-operation: deactivating cell a, performed by the second network element;

third sub-operation: deleting the cell A, which is executed by the second network element;

fourth sub-operation: newly creating a cell A, which is executed by a third network element;

fifth sub-operation: activating a cell A, which is executed by a third network element;

sixth sub-operation: restoring the neighbor relation with cell a is performed by the first network element.

The intended execution order information for indicating an order of executing the 6 sub-operations may be expressed as an order for indicating execution of a first operation, a second operation, a third operation, and a fourth operation, wherein the first operation is a first sub-operation, the second operation is a merging operation of the second sub-operation and the third sub-operation, the third operation is a merging 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 of the embodiment of the present application includes a plurality of sub-operations, for example, the second operation is a merging operation of the second sub-operation and the third sub-operation, the order in which the second sub-operation and the third sub-operation are performed may be indicated by an operation instruction describing the second operation.

For clarity, a manner in which the execution order information indicates an order in which the first operation of the first intention and the second operation of the first intention are executed is described below.

Mode 1:

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

The step identifiers are used for indicating the sequence of executing corresponding operations in executing all operations, the operations with different step identifiers need to be executed in sequence, and the operations with the same step identifiers 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 of the first operation is identified as 1 (e.g., stepid=1), the step of the second operation is identified as 2 (e.g., stepid=2), indicating that the order in which the second operation is performed follows the order in which the first operation is performed.

For another example, the step of the first operation is identified as 1 (e.g., stepid=1), and the step of the second operation is also identified as 1 (e.g., stepid=1), indicating that the first operation and the second operation may be performed in parallel.

Mode 2:

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

The waiting type is used for indicating whether the execution of the corresponding operation needs to wait for the execution of the preamble operation to finish, and the step identifier is used for indicating the sequence of the execution of the corresponding operation in the execution of all the operations. If the step identifier of the plurality of operations does not allow repeated value taking, and the step identifier of the plurality of operations is continuous value taking, and the waiting types of other operations except the first operation in the plurality of operations indicate that the execution of the preamble operation is not required to be completed, the step identifier of the plurality of operations with continuous value taking can be executed in parallel. The step identifier and the waiting type of the first operation may be carried in the description information of the first operation, and the step identifier and the waiting type of the second operation may be carried in the description information of the second operation.

For example, the step of the first operation is identified as 1, the waiting type is no waiting (e.g., stepid=1, waittype=not wait), the step of the second operation is identified as 2, the waiting type is no waiting (e.g., stepid=2, waittype=not wait), which means that the second operation is not executed after the first operation is executed, and the first operation and the second operation may be executed in parallel.

For another example, the step of the first operation is identified as 1, the waiting type is no waiting (e.g., stepid=1, waittype=not wait), the step of the second operation is identified as 2, the waiting type is waiting (e.g., stepid=2, waittype=wait), the step of the third operation is also identified as 3, the waiting type is no waiting (e.g., stepid=3, waittype=not wait), indicating that the second operation and the third operation need to wait for the first operation to be performed in parallel after completion.

Mode 3:

the execution order information includes a mapping relationship of an identification of the first operation and an order in which the first operation is executed, and a mapping relationship of an identification of the second operation and an order in which the second operation is executed.

For example, the execution sequence information is a mapping table of an identification of an operation and an execution sequence of the operation, and the identification of the first operation or the second operation can index the execution sequence of the first operation or the second operation.

The manner in which the order information indicates the order in which the first operation and the second operation are performed is described above, and it should be understood that the above-described method is equally applicable to a scenario in which the order information indicates the order in which three or more operations are performed, which is not particularly limited in this application.

S202, the intention execution network element determines a transmission sequence of the intention execution network element for transmitting the first operation to the first network element and the intention execution network element for transmitting the second operation to the second network element according to the execution sequence information.

S203, the intention execution network element sends a first operation to the first network element according to the sending sequence.

S204, the intention execution network element sends a second operation to the second network element according to the sending sequence.

If the network element is about to execute, according to the execution sequence information, it is determined that the first operation needs to be executed first, and then the second operation is executed, it is determined that the first operation is sent to the first network element, and then the second operation is sent to the second network element, that is, step S203 is executed first, and step S204 is executed later; if the network element is about to execute, according to the execution sequence information, it is determined that the second operation needs to be executed first, and then the first operation is executed, it is determined that the second operation is sent to the second network element first, and then the first operation is sent to the first network element, that is, step S204 is executed first, and step S203 is executed later; if the network element for intention execution determines that the first operation and the second operation can be executed in parallel according to the execution sequence information, the sequence of the network element for intention execution sending the first operation to the first network element and the second operation to the second network element is not limited.

In one possible implementation, the network element is intended to perform a determination of whether the first operation performed successfully, the method may further comprise one or more of steps S205 to S207.

S205, the intention execution network element receives execution result information of the first operation from the first network element.

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

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

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 be carried in a response message in response to the query message.

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

For example, the execution result information includes a field indicating whether the first operation is successful, and the network element for executing is intended to determine whether the first operation is successful according to the field, for example, if the field is 1, it is determined that the first operation is successful, and if the field is 0, it is determined that the first operation is unsuccessful.

In one possible implementation, the execution result information may be a parameter related to the system after the first network element has performed the first operation, or may be an execution state of the first operation, for example, the execution state indicates how many instructions have been performed in the first time. In other words, the execution result information is not displayed to indicate whether the first operation is successfully executed, and then step S207 is further required to be executed before step S206 is executed, and in step S206, the intended execution network element determines whether the first operation is successfully executed according to the execution result information and the first instruction information.

S207, the intention execution network element receives first indication information from an intention knowledge base.

The first indication information may indicate that the network element is intended to perform a determination whether the first operation performed successfully.

Alternatively, the first indication information may be carried in descriptive information of the first operation.

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

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

It should be noted that, the determining criterion may implicitly indicate to the intention-to-execute network element whether the first operation is executed successfully, in other words, the intention-to-execute network element may receive the determining criterion from the intention knowledge base, and the intention-to-execute network element needs to determine whether the first operation is executed successfully according to the determining criterion by default.

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

The network element for intention execution can determine whether the first operation is required to be successfully executed according to the first indication information, execute the indicated judging action to obtain relevant execution result information after the first operation is executed, and then determine whether the first operation is successfully executed by the first network element according to the judging criterion and the execution result information.

Taking as an example that the judging action indicates that the network element is about to send a query message to obtain the execution result information of the first operation: the method comprises the steps that an intention execution network element sends a query message to a first network element according to a judging action, the first network element queries execution result information of a first operation according to the query message, and returns a response message of the query message to the intention execution network element, wherein the response message carries the execution result information of the first operation, and the intention execution network element determines whether the first operation is executed successfully or not according to the execution result information and a judging criterion. The query message may request the first network element to return the specific parameter required by the judgment criterion, or may request the first network element to return all relevant parameters of the system after the first operation is executed, which is not limited in this application.

The manner in which the network element is intended to perform to determine whether the first operation is performed successfully is described above, and it should be understood that the manner in which the network element is intended to perform to determine whether other operations (e.g., the second operation) are performed successfully is similar to the description of determining the first operation, and is not repeated herein for brevity.

In one possible implementation manner, when the network element is intended to perform first sending the first operation to the first network element and then sending the second operation to the second network element, the network element is intended to perform, after sending the first operation to the first network element, determining whether the first operation is performed successfully, and if so, sending the second operation to the second network element. In other words, in step S204, in the case where the intended execution network element determines that the first operation is successfully executed, the intended execution network element transmits the second operation to the second network element.

The manner in which the network element is intended to perform to determine whether the first operation is performed successfully may be described with reference to steps S205 to S207, in other words, steps S205 to S207 may be performed between step S203 and step S204.

It should be understood that, when the network element is intended to perform the second operation first to the second network element and then to send the first operation to the first network element, the network element is also intended to perform the second operation after sending the second operation to the second network element, to determine whether the second operation is performed successfully, and if the second operation is performed successfully, to send the first operation to the first network element. In other words, the network element which is intended to perform the operation may determine whether the preamble operation is performed successfully before the transmission operation, and transmit the operation if the execution is successful, thereby improving the reliability of the intended execution.

In one possible implementation, if it is desired to intend to perform the execution progress of the network element feedback operation, the intended execution network element may receive progress indication information from the intended translation network element.

The progress indication information is used for indicating that the network element which is intended to be executed needs feedback progress information, and the progress information is used for indicating execution progress of the first operation and the second operation.

For example, the progress information is used to indicate the percentage that the first operation and the second operation have been performed, respectively, the estimated time from completion, the number of completed operation instructions, or the like, which is not particularly limited in this application.

The progress indication information may be carried in an intention execution message sent by the intention translation network element for requesting execution of the first intention. 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 an intention implementation request message sent to the intention management network element, the intention management network element carries the progress indication information in an intention translation message sent to the intention translation network element, and then the intention translation network element may carry the progress indication information in an intention execution message sent to the intention execution network element.

Optionally, the progress indication information may also be used to indicate a period or frequency at which the network element is intended to perform the feedback of the progress information.

Optionally, the progress indication information may be further used to indicate a trigger condition that the network element is intended to perform the feedback of the progress information, for example, the progress indication information may indicate that the network element is intended to perform the feedback of the execution progress of the current first operation and the second operation when a certain parameter of the current system reaches a predetermined trigger condition.

And 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, the progress information may be determined according to the relevant information of the execution result returned by the first network element and/or the second network element, and the progress information may be returned to the intention management network element. The intention-to-execute network element may also send a query message to the first network element and/or the second network element according to the progress indication information to obtain the progress information.

If the progress indication information indicates the period and the frequency of the feedback needed by the network element for executing the intention, the network element for executing the intention can also send the progress information to the network element for managing the intention according to the period and the frequency.

In one possible implementation, in step S201, the intention execution network element receives the execution order information from the intention knowledge base in two ways: firstly, after receiving an intention translation message sent by an intention management network element, the intention translation network element sends an intention knowledge query message to a knowledge management network element according to identification information of a first intention and an intention expression of the first intention in the intention translation message, the knowledge management network element queries in an intention knowledge base according to the intention knowledge query message and sends an intention knowledge feedback message to the intention translation network element, the intention knowledge feedback message carries the execution sequence information, and then the intention translation network element can carry the execution sequence information in an intention execution request message sent to an intention execution network element; secondly, after receiving the intention execution request message sent by the intention translation network element, the intention translation network element can send an intention operation query message to the knowledge management network element according to an intention expression and/or an operation identifier (an identifier of a first operation and/or a second operation) in the intention execution request message, the knowledge management network element queries in an intention knowledge base according to the operation query message, and sends an intention operation feedback message to the intention execution network element, wherein the intention operation feedback message carries the execution sequence information.

In other words, the intention execution network element receives execution order information from the intention knowledge base, the execution order information may be that other network elements initiate a query to be received from the intention knowledge base and then forwarded to the intention execution network element, or the intention execution network element initiates a query to be received from the intention knowledge base.

It should be understood that, in the foregoing description 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, which is not repeated herein for brevity.

Therefore, in the application, the network element for intention execution can determine the sending sequence of sending the plurality of operations according to the sequence of executing the plurality of operations, so that the plurality of operations can be executed in sequence, and the plurality of operations can be mutually matched, so that the failure of execution of the intention operation or the unexpected effect caused by out-of-sequence execution is avoided.

Fig. 3 shows another exemplary flow chart of an intent to perform method 300 provided herein.

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

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

Optionally, the intent implementation request message further includes progress indication information (progress notification), and the description of the progress indication information can be referred to in the method 200, which is not described herein for brevity.

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

The intent-to-implement request response message may include an identification (intetID) of the first intent and may also include an intent expression of the first intent.

For example, after receiving the intention implementation request message corresponding to the first intention, the intention management network element allocates an identifier of the first intention to the first intention, carries the identifier in an intention implementation request response message, and sends the identifier to the intention 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 for requesting an intent translation network element to translate a first intent.

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

S304, the intention translation network element sends an intention knowledge query message to the intention knowledge base.

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

Wherein the query type may indicate that the parameters obtained by the query are needed, 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 obtains the query result.

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

The intention knowledge base may be understood as a sub-module of a knowledge management network element, and in the process of initializing and updating the intention knowledge base, relevant information of the first intention, such as execution sequence information (stepinfo), first indication information, etc., is stored in the intention knowledge base, and the knowledge management network element may query in the intention knowledge base according to an intention knowledge query message. For example, the first indication information includes success judgment information (success indication),

For example, if the query type is an operation to query for a first intent, the intent knowledge base obtains a list of intended operations (intetOperationList) for the first intent, the list of intended operations including a description of the first operation and a description of the second operation. It should be understood that if the first intent is further operations, the list of intended operations also includes descriptions of the further operations.

Wherein, by way of example, the description of the first operation may include one or more of the following: an operation instruction (instruction) of the first operation, and an operation execution object (entityIDList) of the first operation. If the indication manner of the mode 1 or the mode 2 in the method 200 is adopted, the description information of the first operation further includes execution sequence information (stepInfo) of the first operation, for example { step identifier (stepID) }, or { step identifier (stepID), wait type (waitType) }. The operation instruction is used for describing a specific command for executing the first operation, and the operation execution object is used for describing a first network element which needs to execute the first operation.

Optionally, if the network element is to be executed, whether the execution of the first operation is successful or not needs to be judged, the description information of the first operation further includes first indication information, and for the description of the first indication information, the description of the first indication information in the method 200 may be referred to, which is not repeated herein for brevity.

It should be appreciated that the description information of the other operations may be similar to the description information of the first operation, and for brevity, will not be described in detail herein.

The intended operation list may further include execution condition (execution condition) information for describing conditions that need to be satisfied to execute the first operation and the second operation, for example, the first operation and/or the second operation may be executed when the network load condition is no-load or low-load.

The list of intended operations may also include dependency event (events) information describing the impact that execution of the first intent may have on the system.

If the query type is query full parameters, the intent knowledge base may further include an intent target achievement criterion (fulfillmentCriterion) in addition to the first intent operation list (eventoperation list), which may be used to indicate achievement conditions of the first intent, for example, the intent target achievement criterion may include an intent target calculation formula that measures whether the intent target is achieved.

Alternatively, if the manner of indication of the mode 3 in the method 200 is adopted, the intention knowledge base may also obtain execution order information (stepInfo), which describes the execution order of the plurality of operations of the first intention.

The first operation, the second operation, and the manner in which the order information indicates the order in which the first operation and the second operation are performed may be referred to as related descriptions in the method 200, and are not described herein for brevity.

The above is merely an exemplary description of the query results, which is not particularly limited in this application.

S306, the intention translation network element receives an intention knowledge feedback message from the intention knowledge base.

The intention knowledge feedback message comprises a query result obtained by an intention knowledge base.

The intent knowledge feedback message may also include an identification (intetID) of the first intent.

S307, the intention translation network element sends execution order information to the intention execution network element.

For example, the intention translation network element sends an intention execution request message to the intention execution network element, the intention execution request message including the execution order information (steplnfo).

The intent translation request message may also include an identification of the first intent, and a list of intent operations and intent target achievement criteria obtained by the intent translation network element from the intent knowledge feedback message.

Optionally, if the network element is intended to perform the first operation and the second operation 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 the intention execution network element receives the intention execution request message, it may be determined that the first operation and the second operation are to be executed according to a predetermined decision algorithm.

S308, the intention execution network element determines a transmission sequence of the intention execution network element for transmitting the first operation to the first network element and the intention execution network element for transmitting the second operation to the second network element according to the execution sequence information.

For a description of the method 300, reference may be made to the description of the method 300 for determining the transmission order of the first operation and the second operation by the network element, and for brevity, the description will not be repeated here. The following exemplifies the intention to perform the first operation of the network element to the first network element and then the second operation to the second network element.

S309, the intention execution network element sends the first operation to the first network element according to the sending sequence.

For example, the intention execution network element sends an operation execution request message corresponding to a first operation to the first network element, where the operation execution request message includes information corresponding to the first operation, and the information corresponding to the first operation may include an operation identifier (operation id) and an operation instruction (instruction) of the first operation.

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

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

For example, the intention 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 including execution result information of the first operation, the operation execution response message may further include an operation identification of the first operation.

For another example, the first indication information is further used for indicating that the network element is intended to execute a judging action that determines whether the first operation is executed successfully, where the judging action indicates that the network element is intended to execute the first operation needs to query the first network element for execution result information of the first operation. In this case, the intention-to-execute network element may send an operation execution state query message to the first network element, where the operation execution state query message is used to request to query the execution result information, and the execution result information received by the intention-to-execute network element is carried in an operation execution state query response message that responds to the operation execution state query message.

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

For a description of whether the first operation is successfully performed by the network element, reference is made to the method 200, and for brevity, details are omitted here.

In case the intention-to-execute network element determines that the first operation execution was successful, the intention-to-execute network element may execute S312.

S312, the intention execution network element sends a second operation to the second network element.

For example, the network element for performing the operation 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, and the information corresponding to the second operation may include an operation identifier (operation id) and an operation instruction (instruction) of the second operation.

It should be understood that, the network element for intention execution may also receive the execution result information of the second operation from the second network element, the request message for intention execution may also include the first indication information of the second operation, and the network element for intention execution may also determine whether the second operation is executed successfully according to the first indication information and the execution result information of the second operation, if the operation corresponding to the first intention also includes the third operation that the network element for intention management needs to execute, and the execution sequence of the third operation is after the second operation, the network element for intention execution may also send the third operation to the network element for intention management if it is determined that the second operation is executed successfully, which implementation method is similar to that described above for the first operation, and for brevity and brevity, the application does not make any limitation on the number of operations corresponding to the first intention.

If the progress indication information is also included in the intended 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 an identification of the first intention and progress information, and description of the progress information refers to description in the method 200, and for brevity, will not be repeated herein.

Optionally, if the progress indication information is further used for indicating a period or a frequency of the feedback progress information required by the network element for executing the operation, the network element for executing the operation may monitor the progress of the operation according to the period or the frequency, and send the notification message of the progress of executing the operation to the network element for managing the operation according to the period or the frequency.

If the intention consumption network element needs to acquire the progress information, the intention management network element can forward the operation execution progress notification message to the intention consumption network element.

Fig. 4 shows an exemplary flow chart of a method 400 intended to be performed by the present application.

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

The execution result information is used to determine whether an abnormality occurs in the execution of the first operation.

Wherein, the occurrence of the abnormality in the execution of the first operation may refer to any one of the following cases: failure of the first operation, timeout of the first operation, failure of the execution result of the first operation to achieve a predetermined effect, or other situations that result in the first intention failing to achieve a predetermined intended target.

For example, the execution result information may include an identification of whether or not an abnormality occurs in the execution of the first operation.

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 network element for executing is intended to determine whether the execution of the first operation is abnormal according to the field, for example, the field indicates that the execution of the first operation is abnormal when the field is 1, and indicates that the execution of the first operation is not abnormal when the field is 0.

In one possible implementation, the execution result information may be a parameter related to the system after the first network element has performed the first operation, or may be an execution state of the first operation, for example, the execution state indicates how many instructions have been performed in the first time. In other words, the execution result information does not show whether or not the execution of the first operation is abnormal, and then step S403 is also required to be executed before step S402 is executed, and in step S402, the intended execution network element determines whether or not the execution of the first operation is abnormal based on the execution result information and the second instruction information.

S403, the intention execution network element receives second instruction information from the intention knowledge base.

The second indication information is used for indicating that the network element is intended to execute to determine whether the execution of the first operation is abnormal or not.

The second indication information may be stored in the intent knowledge base in an intent knowledge base initialization and update procedure.

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

Alternatively, the second indication information may include a judgment criterion for determining whether or not an abnormality occurs in the execution of the first operation.

The intended execution network element determines whether or not the execution of the first operation is abnormal based on the execution result information and a judgment criterion indicating, for example, that the first operation is judged to be abnormal when a certain parameter reaches a predetermined range. For example, the judging criterion indicates that if the result after the execution of the first operation does not reach the predetermined result, it indicates that the execution of the first operation is abnormal, and after the network element for intention execution receives the execution result information, whether the result reaches the predetermined result is judged according to the execution result information, and whether the execution of the first operation is abnormal is determined; for example, the determining criterion indicates that if the first operation is not successfully executed within a predetermined time, the first operation is abnormally executed, the execution result information received by the network element for intention to execute indicates that the first operation is failed to execute, or the network element for intention to execute does not receive the execution result information for indicating that the first operation is successfully executed within the predetermined time, and the network element for intention to execute may determine that the first operation is abnormally executed.

It should be noted that, the anomaly determination criterion may implicitly indicate that the network element for performing the first operation may determine whether an anomaly occurs in the execution of the first operation, in other words, the network element for performing the first operation may receive the determination criterion from the intention knowledge base, and the network element for performing the first operation needs to determine whether an anomaly occurs in the execution of the first operation according to the determination criterion by default.

Alternatively, the second indication information may include a judgment criterion for determining whether an abnormality occurs in the execution of the first operation, and a judgment action that is required to be performed by the network element for which the execution of the first operation is intended to be performed. For example, the determining action indicates that the network element intended to execute needs to send a query message to the first network element to obtain execution result information of the first operation.

The network element for executing intention can determine whether the execution of the first operation needs to be determined to be abnormal according to the second indication information, execute the indicated judging action to acquire the related execution result information after the first operation is executed, and then determine whether the execution of the first operation is successful according to the abnormal judging criterion and the execution result information.

Taking as an example that the judging action indicates that the network element is about to send a query message to obtain the execution result information of the first operation: the method comprises the steps that an intention execution network element sends a query message to a first network element according to a judging action, the first network element queries execution result information of a first operation according to the query message, and returns a response message of the query message to the intention execution network element, wherein the response message carries the execution result information of the first operation, and the intention execution network element determines whether the execution of the first operation is abnormal or not according to the execution result information and a judging criterion. The query message may request the first network element to return the specific parameter required by the judgment criterion, or may request the first network element to return all relevant parameters of the system after the first operation is executed, which is not limited in this application.

The manner in which the network element is intended to perform to determine whether the first operation is abnormal is described above, and it should be understood that the manner in which the network element is intended to perform to determine whether other operations are abnormal is similar to the description of determining the first operation, and is not described herein for brevity.

S404, when the intention execution network element determines that the execution of the first operation is abnormal, the intention execution network element sends back indication information to the second network element.

The rollback indication information is used to indicate a second operation to rollback the first intention.

The second operation may be a preamble operation of the first operation, or the second operation may be a parallel operation of the first operation, or the second operation may be an operation that the second network element has executed successfully or is executing when the network element is intended to execute to determine that the execution of the first operation is abnormal.

The first operation of the first intent and the second operation of the first intent may be one or more sub-operations of the intended operation corresponding to the first intent. For example, the first intent corresponding intent operation includes three sub-operations, respectively: a first sub-operation, a second sub-operation, and a third sub-operation. The execution object of the first sub-operation is a first network element, and the execution objects of the second sub-operation and the third sub-operation are second network elements. The first operation in the embodiment of the present application may be the first sub-operation, and the second operation may be a merging 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-to-execute network element determines that the execution of the first operation is abnormal, the other network element has executed the operation that is successful or is being executed, the intention-to-execute network element may also send, to the other network element, by way of example and not limitation, back-off indication information for indicating that the operation is backed off, taking the intention of the first intention as an example of cell relocation. The first intention has four operations:

a first operation: deleting the adjacent cell relation with the cell A, which is executed by a first network element;

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

third operation: newly creating a cell A and activating the cell A, which are executed by a third network element;

fourth operation: restoring the neighbor relation with cell a is performed by the first network element.

If the first operation and the second operation have been successfully executed, but the execution of the third operation is abnormal, the intention execution network element sends back-off indication information for backing off the second operation to the second network element, and sends back-off indication information for backing off the first operation to the first network element.

Rollback the second operation may be understood as restoring the system to a state prior to performing the second operation.

It should be understood that if there are other operations of the first intention in the system, when the network element for performing the intention determines that the execution of the first operation is abnormal, the other network elements have already performed the operation that is successful or is being performed, the network element for performing the intention may also send back indication information to the other network elements for indicating to back the operation. For example, if the intention management network element has successfully performed or is performing the third operation of the first intention, the intention execution network element may also send indication information indicating to the intention management network element to rollback the third operation. Alternatively, the network element intended to perform the operations may transmit the back-off indication information in reverse order of the transmission order in which the plurality of operations are transmitted.

And S405, the second network element rolls back the second operation according to the roll-back indication information.

Wherein the manner of rollback of the second operation may be determined based on whether the second network element has the capability of operating rollback.

If the second network element has the capability of operation rollback, the second network element can call the self operation rollback capability to rollback the second operation after receiving the rollback indication information.

If the second network element does not have the capability of operating fallback, the fallback indication information that is intended to be sent by the network element may also be used to indicate the manner in which the second network element rolls back the second operation, where the method 400 further includes step S406.

S406, the intention execution network element receives the rollback scheme information from the intention knowledge base.

The fallback scheme information is used for indicating the fallback mode of the second operation, and the fallback indication information which is sent by the network element is intended to be executed is also used for indicating the fallback mode of the second operation.

It should be understood that the fallback indication information may be a fallback manner of the second operation, or the network element that is intended to perform may send the fallback manner of the second operation to the second network element, where the fallback manner of the second operation implicitly indicates that the second network element needs to fallback the second operation.

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

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

In a possible implementation, the rollback scheme information describes rollback schemes corresponding to different second operations in different abnormal situations, where the method 400 further includes step S407.

S407, the intention execution network element determines a rollback mode of the second operation according to the execution result information and the rollback scheme information.

For example, the fallback scheme information includes a mapping relationship between an abnormal situation and a fallback manner, different abnormal situations correspond to different labels, the execution result information may include labels corresponding to abnormal situations occurring when executing the first operation, and the network element intends to execute the fallback manner of the second operation corresponding to the abnormal situation according to the index of the labels, and send the fallback manner of the second operation to the second network element.

For another example, the rollback scheme information includes a mapping relationship between an abnormal situation and a rollback mode, the execution result information includes a relevant parameter after executing the first operation, and the network element is intended to execute to determine which abnormal situation belongs to according to the relevant parameter, further determine a rollback mode of the second operation, and send the rollback mode of the second operation to the second network element.

In one possible manner, when the network element for executing intention determines that the execution of the first operation is abnormal, the network element for executing intention also can inquire whether the second operation needs to be backed up from the network element for consuming intention, and when the network element for consuming intention feeds back that the second operation needs to be backed up, the network element for executing intention sends back indication information to the second network element. In this case, the method further comprises a step S408, which step S408 may be performed between step S403 and step S404, wherein in step S403, the intended execution network element 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 fallback request message is used to indicate whether the second network element needs to fallback the second operation.

Optionally, the intended operation back-off request message may include at least one of the following information: the first intention identification information is included, related information indicating that an abnormality occurs in the execution of the first operation, and a rollback manner of the second operation.

The network element for consuming intention receives the request message for returning the operation of intention, and can determine whether the second operation needs to be returned according to the running condition of the system at the time or the abnormal condition of the first operation.

S409, the intention management network element transmits an intention operation fallback response message in response to the intention operation fallback request message to the intention execution network element, the intention operation fallback response message indicating whether the second operation needs to be fallback.

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

If the intended operation fallback response message indicates that the second operation needs to be fallback, step S404 may be executed, where the intended execution network element sends fallback indication information to the second network element.

In one possible manner, the intention translation network element carries, in the intention execution request message sent to the intention execution network element, the expectation processing type indication information, where the expectation processing type indication information is used to indicate whether the intention execution network element needs to inquire about whether the second operation needs to be rolled back to the intention consumption network element if it is determined that the first operation is abnormal, if the processing type indication information indicates that the second operation does not need to be rolled back to the intention consumption network element, the intention execution network element may send the rollback indication information directly to the second network element, and if the processing type indication information indicates that the second operation needs to be rolled back to the intention consumption network element, the intention execution network element needs to execute step S408.

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

In one possible implementation manner, in step S401, the intention execution network element may receive the second instruction information from the intention knowledge base in two ways, one of which is that, after the intention translation network element receives the intention translation message sent by the intention management network element, the intention translation network element sends an intention knowledge query message to the knowledge management network element according to the identification information of the first intention and the intention expression of the first intention in the intention translation message, the knowledge management network element queries in the intention knowledge base according to the intention knowledge query message, and sends an intention knowledge feedback message to the intention translation network element, the second instruction information is carried in the intention knowledge feedback message, and then the intention translation network element may carry the second instruction information in an intention execution request message sent to the intention execution network element; secondly, after receiving the intention execution request message sent by the intention translation network element, the intention translation network element can send an intention operation query message to the knowledge management network element according to an intention expression and/or an operation identifier (an identifier of a first operation and/or a second operation) in the intention execution request message, the knowledge management network element queries in an intention knowledge base according to the operation query message, and sends an intention operation feedback message to the intention execution network element, wherein the intention operation feedback message carries the second instruction information.

In other words, the intention execution network element receives second indication information from the intention knowledge base, where the second indication information may be that other network elements initiate a query to be received from the intention knowledge base and then forwarded to the intention execution network element, and the second indication information may also be that the intention execution network element initiates a query to be received from the intention knowledge base.

It should be understood that, in the above description of the intention execution network element receiving the second indication information from the intention knowledge base, in S406, the manner in which the intention execution network element receives the fallback scheme information from the intention knowledge base may be similar to the description of receiving the second indication information, which is not repeated herein for brevity.

Fig. 5 shows a further exemplary flow chart of a method 500 intended to be performed as provided herein.

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

Optionally, the intent implementation request message further includes progress indication information (progress notification), and the description of the progress indication information can be referred to in the method 400, which is not described herein for brevity.

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

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

S504, the intention translation network element sends an intention knowledge query message to the intention knowledge base.

The query type may indicate a parameter that needs to be obtained by the query, 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 intention.

Optionally, S505, the intent knowledge base obtains the query result.

The intention knowledge base may be understood as a sub-module of a knowledge management network element, in the process of initializing and updating the intention knowledge base, relevant information of the first intention, such as second instruction information, rollback solution information (rollback solution), and the like, is stored in the intention knowledge base, and the knowledge management network element may query in the intention knowledge base according to an intention knowledge query message. For example, the second instruction information may include abnormality determination information (exception).

Wherein, by way of example, the description of the first operation may include one or more of the following: an operation instruction (instruction) of a first operation, an operation execution object (entityIDList) of the first operation, second instruction information of the first operation, and rollback scheme information (rollback solution list). The operation instruction is used to describe a specific command for executing the first operation, the operation execution object is used to describe a first network element that needs to execute the first operation, and description of the second instruction information and the fallback scheme information can be referred to corresponding description in the method 400, which is not repeated herein for simplicity.

If the query type is query total parameters, the intent knowledge base may further include an intent goal achievement criterion (fulfillmentCriterion) in the intent knowledge feedback message in addition to acquiring the intent operation list (eventoperationlist) of the first intent, where the intent goal achievement criterion may be used to indicate achievement conditions of the first intent, for example, the intent goal achievement criterion may include an intent goal calculation formula for measuring whether the intent goal is achieved.

S506, the intention translation network element receives an intention knowledge feedback message from the intention knowledge base.

S507, the intention translation network element sends the second instruction information to the intention execution network element.

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

S508, the intention execution network element sends a first operation to the first network element.

S509, the intention execution network element sends a second operation to the second network element.

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

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

For another example, the second indication information is further used for indicating a judgment action of determining whether the first operation is abnormal by the intention execution network element, where the judgment action indicates that the intention execution network element needs to query the first network element for the execution result information of the first operation. In this case, the intention-to-execute network element may send an operation execution state query message to the first network element, where the operation execution state query message is used to request to query the execution result information, and the execution result information received by the intention-to-execute network element is carried in an operation execution state query response message that responds to the operation execution state query message.

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

For a description of the network element intended to perform the first operation to determine whether an abnormality occurs in the execution of the first operation, reference may be made to the description in the method 400, and for brevity, a description thereof will not be repeated here.

It should be understood that the network element that is intended to execute may also receive the execution result information of the second operation from the second network element, where the request message that is intended to execute may also include the second indication information of the second operation, and the network element that is intended to execute may also determine whether the execution of the second operation is abnormal according to the second indication information of the second operation and the execution result information, where the implementation method is similar to that described above for the first operation, and for brevity, the description is omitted here again

It should be noted that the present application does not make any limitation on the number of operations corresponding to the first intention. In the present embodiment, without any limitation on the execution order of the first operation and the second operation, the second operation is exemplified as an operation that has been executed successfully or is being executed when the intention is that the execution network element determines that the execution of the first operation is abnormal.

In one possible implementation manner, if the request message for executing the request includes the expected processing type indication information, where the expected processing type indication information is used to indicate whether the network element for executing the request needs to inquire about whether the second operation needs to be rolled back from the network element for consuming the request if it is determined that the first operation is abnormal, and if the processing type indication information indicates that the network element for consuming the request needs to inquire about whether the second operation needs to be rolled back from the network element for consuming the request, steps S512 to S513 are executed.

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

The description of the intended operation back-off request message is similar to that of method 400 and is not repeated here for brevity.

S513, the intention management network element sends an intention operation fallback response message to the intention execution network element in response to the intention operation fallback request message, the intention operation fallback response message being used to indicate whether the second operation needs to be fallback.

The description of the intended operational fallback response message is similar to that of method 400 and is not repeated here for brevity.

S514, the intention execution network element sends back-off indication information to the second network element.

When the network element which is intended to execute determines that the execution of the first operation is abnormal, or the network element which is intended to execute is used for indicating that the second operation needs to be rolled back, the network element which is intended to execute sends rollback indication information to the second network element.

The description of the back-off indication information is similar to that of the method 400, and is not repeated here for brevity.

And S515, the second network element rolls back the second operation according to the roll-back indication information.

The description of the second operation of the second network element is similar to that of the method 400, and is not repeated here for brevity.

If the progress indication information is also included in the 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 an identification of the first intention and progress information, and a description of the progress information is referred to as a description of the method 400, and is not repeated herein for simplicity.

Therefore, in the application, if the execution of a certain operation of the first intention is abnormal, other executed operations of the first intention can be rolled back, so that the other operations of the first intention are prevented from being in unnecessary execution all the time, and unnecessary influence is generated on the system.

In the embodiments described in fig. 3 and fig. 5, the intention translation network element may send an intention knowledge query message to the intention knowledge base, where the query message is used to query relevant information about an intention, and the relevant information about the intention is carried in an intention execution request message sent to the intention execution network element.

Fig. 6 shows a schematic flow chart of an example of a method 600 for attempting to perform network element querying information.

S601, the intention execution network element sends an intention operation query message to an intention knowledge base.

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

Optionally, the intent operation query message comprises at least one of the following information: the identification of the first operation, the expression of the first intent, and the query type.

For example, the intention knowledge base includes a mapping relation of a query type, query input information and query output information, wherein the query input information may refer to information required to be input for querying the type, the query output information may refer to information required to be output for querying the type, and the intention execution network element determines the query type according to the requirement and carries the required query input in the intention operation query message.

By way of example and not limitation, table 1 shows a mapping relationship of query types, query input information, and query output information.

Table 1:

optionally, S602, the intent knowledge base obtains a query result.

For example, the intent knowledge base queries corresponding query results 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 responding to the intention operation query message to the intention execution network element.

The intent operation feedback message includes an identification of the first operation and a query result obtained by the query.

Therefore, in the application, the intention execution network element can inquire the required information from the intention knowledge base according to the requirement, and unnecessary information is prevented from being carried in the intention translation request message, so that the flexibility of the system for processing the intention can be improved.

Fig. 7 and fig. 8 are schematic structural diagrams of a possible communication device according to an embodiment of the present application. These communication devices may be used to implement the functions of the network element, the intention knowledge base, the first network element, and the second network element in the above method embodiments, so that the beneficial effects of the above method embodiments may also be implemented. In the embodiment of the application, the communication device may be an intention execution network element, an intention knowledge base, a first network element, a second network element, or may be a module (such as a chip) applied in the intention execution network element, the intention knowledge base, the first network element, and the second network element.

As shown in fig. 7, the communication apparatus 700 includes a processing unit 710 and a transceiving unit 720. The communication device 700 is configured to implement the functions of the network element, the intention knowledge base, the first network element, and the second network element in the method embodiment shown in fig. 2. Alternatively, the communication apparatus 700 may include a module for implementing any of the functions or operations of the network element, the intention knowledge base, the first network element, the second network element, which is intended to be performed in the method embodiment shown in fig. 2 and which may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.

When the communication device 700 is used to implement the function of the network element intended to be performed in the method embodiment shown in fig. 2, the transceiving unit 720 is used to receive execution order information from the intended knowledge base, the execution order information being used to indicate an order in which a first operation of the first intention and a second operation of the first intention are performed; the processing unit 710 is configured to determine, according to the execution order information, a transmission order in which the network element is intended to perform sending the first operation to the first network element and the network element is intended to perform sending the second operation to the second network element; 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.

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

Optionally, when the communication device 700 is configured to implement the function of the network element intended to be performed in the method embodiment shown in fig. 2, the transceiver unit 720 is further configured to receive first indication information from the intended knowledge base, where the first indication information is used to indicate that the network element is intended to be performed to determine whether the first operation is performed successfully.

Optionally, when the communication device 700 is configured to implement the function of the network element intended to be executed 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, and send the second operation to the second network element if it is determined that the first operation is executed successfully.

Optionally, when the communication device 700 is configured to implement the function of the network element in the method embodiment shown in fig. 2, the transceiver unit 720 is further configured to receive progress indication information, where the progress indication information is used to indicate that the device needs to feed back the progress information, and the progress information is used to indicate the execution progress of the first operation and the second operation.

When the communication device 700 is used to implement the function of the intent knowledge base in the method embodiment shown in fig. 2, the transceiving unit 720 is used to send execution order information to the intent execution network element, the execution order information being used to indicate the order in which the first operation of the first intent and the second operation of the first intent are performed.

Optionally, when the communication device 700 is configured to implement the function of the intended repository in the method embodiment shown in fig. 2, the transceiver unit 720 is further configured to send first indication information to the intended execution network element, where the first indication information is used to determine whether the first operation is executed successfully.

The transceiver unit 720 is configured to receive a first operation when the communication device 700 is configured to implement the function of the first network element in the method embodiment shown in fig. 2; the processing unit 710 is configured to perform a first operation.

Optionally, when the communication device 700 is configured to implement the function of the first network element in the method embodiment shown in fig. 2, the transceiver unit 720 is further configured to send execution result information of the first operation, where the execution result information is used to determine whether the first operation is executed successfully.

The transceiver unit 910 is configured to receive a second operation when the communication apparatus 700 is configured to implement the function of the second network element in the method embodiment shown in fig. 2; the processing unit 710 is configured to perform a second operation.

The above-mentioned more detailed descriptions of 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. 2, which are not repeated herein.

As shown in fig. 7, the communication apparatus 700 includes a processing unit 710 and a transceiving unit 720. The communication device 700 is configured to implement the functions of the network element, the intention knowledge base, the first network element, and the second network element in the method embodiment shown in fig. 2. Alternatively, the communication apparatus 700 may comprise means for implementing any of the functions or operations of the network element, the intention knowledge base, the first network element, the second network element, which are intended to be performed in the method embodiment shown in fig. 4 and which may be implemented in whole or in part by software, hardware, firmware or any combination thereof.

When the communication device 700 is configured to implement the function of the network element intended to be executed in the method embodiment shown in fig. 4, the transceiver unit 720 is configured to receive, from the first network element, execution result information of the first operation intended to be executed; the processing unit 710 is configured to determine that an abnormality occurs in the execution of the first operation according to the execution result information; the transceiver unit 720 is further configured to send back-off indication information to the second network element, where the back-off indication information is used to indicate a second operation of backing off the first intention.

Optionally, when the communication device 700 is configured to implement the function of the network element intended to be performed in the method embodiment shown in fig. 4, the transceiver unit 720 is further configured to receive second indication information from the intended knowledge base, where the second indication information is used to indicate that the network element intended to be performed determines that the first operation is performed abnormally.

Optionally, when the communication apparatus 700 is configured to implement the function of the network element in the method embodiment shown in fig. 4, the processing unit 710 is further configured to determine the fallback manner of the second operation according to the execution result information and the fallback scheme information.

Optionally, when the communication device 700 is configured to implement the function of the network element intended to be executed 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, and send the second operation to the second network element if it is determined that the first operation is executed successfully.

Therefore, in the application, if the execution of a certain operation of the first intention is abnormal, other executed operations of the first intention can be rolled back, so that the waste of resources and signaling caused by the fact that other operations of the first intention are always executed is avoided, and further the execution efficiency of the intention can be improved. Optionally, when the communication device 700 is configured to implement the function of the network element in the method embodiment shown in fig. 4, the transceiver unit 720 is further configured to receive progress indication information, where the progress indication information is used to indicate that the device needs to feed back the progress information, the progress information is used to indicate the execution progress of the first operation and the second operation, and is further used to send the progress information according to the progress indication information.

When the communication device 700 is used to implement the function of the intent knowledge base in the method embodiment shown in fig. 4, the transceiver unit 720 is configured to send second indication information to the intended execution network element, where the second indication information is configured to indicate whether the execution of the first operation is abnormal.

Therefore, in the application, if the execution of a certain operation of the first intention is abnormal, other executed operations of the first intention can be rolled back, so that the other operations of the first intention are prevented from being in unnecessary execution all the time, the system is unnecessarily influenced, and the reliability of the execution intention of the system is improved.

Optionally, when the communication apparatus 700 is configured to implement the function of the intended knowledge base in the method embodiment shown in fig. 4, the transceiver unit 720 is further configured to send back-off scheme information to the intended performing network element, where the back-off scheme information is used to determine a back-off manner of the second operation.

When the communication device 700 is configured to implement the function of the first network element in the method embodiment shown in fig. 4, the transceiver unit 720 is configured to send the execution result information of the first operation of the first intention.

When the communication device 700 is configured to implement the function of the second network element in the method embodiment shown in fig. 4, the transceiver unit 720 is configured to receive back-off indication information, where the back-off indication information is used to indicate a second operation of backing off the first intention; the processing unit 710 is configured to rollback the second operation.

The above-mentioned more detailed descriptions of the processing unit 710 and the transceiver unit 720 may be directly obtained by referring to the related descriptions in the method embodiment shown in fig. 3, which are not repeated herein.

As shown in fig. 8, the communication device 800 includes a processor 810 and an interface circuit 820. Processor 810 and interface circuit 820 are coupled to each other. It is understood that the interface circuit 820 may be a transceiver or an input-output interface. Optionally, the communication device 800 may further comprise a memory 830 for storing instructions to be executed by the processor 810 or for storing input data required by the processor 810 to execute instructions or for storing data generated after the processor 810 executes 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 1010, and the interface circuit 820 is used to implement the functions of the 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. Processor 810 and interface circuit 820 are coupled to each other. It is understood that the interface circuit 820 may be a transceiver or an input-output interface. Optionally, the communication device 800 may further comprise a memory 830 for storing instructions to be executed by the processor 810 or for storing input data required by the processor 810 to execute instructions or for storing data generated after the processor 810 executes 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 communication device is a chip applied to an intended execution network element, the intended execution network element chip implements the function of the intended execution network element in the embodiment of the method. The intention execution network element chip receives information from other modules (such as a radio frequency module or an antenna) in the intention execution network element, wherein the information is sent to the intention execution network element by an intention knowledge base; or, the network element chip for intention execution sends information to other modules (such as a radio frequency module or an antenna) in the network element for intention execution, wherein the information is sent to the first network element or the second network element by the network element for intention execution.

When the communication device is a chip applied to the intended knowledge base, the intended knowledge base chip realizes the function of the intended knowledge base in the embodiment of the method. The intention knowledge base chip receives information from other modules (such as a radio frequency module or an antenna) in the intention knowledge base, wherein the information is sent to the intention knowledge base by the intention execution network element; alternatively, the intention knowledge base chip sends information to other modules (e.g., radio frequency modules or antennas) in the intention knowledge base, which is sent to the intended execution network element.

It is to be appreciated that the processor in embodiments of the present application may be a central processing unit (Central Processing Unit, CPU), but may 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 arrays (Field Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general purpose processor may be a microprocessor, but in the alternative, it may be any conventional processor.

The Memory in embodiments of the present application may be in random access Memory (Random Access Memory, RAM), flash Memory, read-Only Memory (ROM), programmable ROM (PROM), erasable Programmable ROM (EPROM), electrically Erasable Programmable EPROM (EEPROM), registers, hard disk, a removable disk, a 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. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may reside in a network device or terminal device. The processor and the storage medium may reside as discrete components in a network device or terminal device.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed 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 apparatus. The computer program or instructions may be stored in or transmitted across 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 that integrates one or more available media. The usable medium may be a magnetic medium, e.g., floppy disk, hard disk, tape; but also optical media such as DVD; but also semiconductor media such as Solid State Disks (SSDs).

In the various embodiments of the application, if there is no specific description or logical conflict, terms and/or descriptions between the various embodiments are consistent and may reference each other, and features of the various embodiments may be combined to form new embodiments according to their inherent logical relationships.

It should be understood that, in the embodiments of the present application, the numbers "first" and "second" … are merely for distinguishing different objects, such as for distinguishing different network devices, and are not limited to the scope of the embodiments of the present application, but are not limited thereto.

It should also be understood that, in this application, "when …", "if" and "if" all refer to a corresponding process that the network element will make under some objective condition, are not limited in time, nor do it require that the network element be implemented with a judging action, nor are other limitations meant to be present.

It should also be understood that in various embodiments of the present application, "B corresponding to a" means that B is associated with a from which B may be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may also determine B from a and/or other information.

It should also be understood that the term "and/or" is merely one association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

Similar to the term "appearing in this application includes one or more of the following: the meaning of the expressions a, B, and C "generally means that the item may be any one of the following unless otherwise specified: a, A is as follows; b, a step of preparing a composite material; c, performing operation; 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 and C, C and C; c, C and C, and other combinations of a, B and C. The above is an optional entry for the item exemplified by 3 elements a, B and C, when expressed as "the item includes at least one of the following: a, B, … …, and X ", i.e. when there are more elements in the expression, then the entry to which the item is applicable can also be obtained according to the rules described above.

It will be appreciated that the various numerical numbers referred to in the embodiments of the present application are merely for ease of description and are not intended to limit the scope of the embodiments of the present application. The sequence number of each process does not mean the sequence of the execution sequence, and the execution sequence of each process should be determined according to the function and the internal logic.

Claims

1. A method intended for execution, the method comprising:

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

the intention execution network element determines a sending sequence of the intention execution network element for sending a first operation to a first network element and the intention execution network element for sending a second operation to a second network element according to the execution sequence information;

and 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.

2. The method of claim 1, wherein the method further comprises:

the intention execution network element receives execution result information of the first operation from the first network element;

and the intention execution network element determines whether the first operation is successfully executed according to the execution result information.

3. The method of claim 2, wherein the method further comprises:

the intention execution network element receives first indication information from an intention knowledge base, wherein the first indication information is used for indicating the intention execution network element to determine whether the first operation is executed successfully or not.

4. A method according to any one of claims 1 to 3, wherein the intention-to-perform network element sending the first operation to the first network element and the second operation to the second network element according to the sending order comprises:

the intention 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 under the condition that the intention execution network element determines that the first operation is successfully executed.

5. The method of any one of claims 1 to 4, wherein the method further comprises:

the intention execution network element receives progress indication information, wherein the progress indication information is used for indicating that the intention execution network element needs feedback of the progress information, and the progress information is used for indicating execution progress of the first operation and the second operation;

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

6. The method of claim 5, wherein the progress indication information is further for indicating a period or frequency at which the intention-to-perform network element needs to feed back the progress information.

7. An apparatus intended to be executed, characterized in that it comprises a transceiver unit and a processing unit,

The transceiver unit is configured to receive execution order information from an intention knowledge base, where the execution order information is used to indicate an order of executing a first operation of a first intention and a second operation of the first intention;

the processing unit is used for determining a sending sequence of the intention execution network element to send a first operation to a first network element and the intention execution network element to send a second operation to a second network element according to the execution sequence information;

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.

8. The apparatus of claim 7, wherein,

the receiving and transmitting 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 successfully executed according to the execution result information.

9. The apparatus of claim 8, wherein,

the transceiver unit is further configured to receive first indication information from an intention knowledge base, where the first indication information is used to instruct the intention execution network element to determine whether the first operation is executed successfully.

10. The apparatus according to any one of claim 7 to 9, wherein,

the transceiver 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 successfully executed.

11. The device according to any one of claim 7 to 10, wherein,

the transceiver unit is further configured to receive progress indication information, where 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 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.

12. The apparatus of claim 11, wherein the progress indication information is further for indicating a period or a frequency at which the apparatus needs to feed back the progress information.

13. A communication device comprising at least one processor for executing a computer program stored in a memory, to cause the device to implement the method of any one of claims 1 to 6.

14. A computer readable storage medium comprising a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 6.