A method and apparatus for intent execution

Abstract

The application provides a method for executing an intention, which comprises the following steps: an intention execution network element receives execution sequence information from an intention knowledge base, the execution sequence information being used for indicating the sequence of executing a first operation of a first intention and a second operation of the first intention; the intention execution network element determines the sending sequence of the intention execution network element sending the first operation to a first network element and the intention execution network element sending the second operation to a second network element according to the execution sequence information; and the intention execution network element sends the first operation to the first network element and the second operation to the second network element according to the sending sequence, so that the failure of intention operation execution or the failure of reaching the expected effect caused by not executing in sequence is avoided, and the reliability of the system executing the intention is improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a method and apparatus for performing an intention. Background Technology

[0002] Currently, cognitive network management systems (CNNs) can be used to automate user tasks. CNNs support the processing of intentions, where an intention refers to a expectation of the system. To achieve an intention, multiple network devices need to execute multiple operations related to that intention; for example, multiple network devices may execute multiple sub-operations within an intention operation. The success or failure of each network device's operation affects the final result of the intention execution. However, current mechanisms for managing intention operations do not consider the coordination between multiple operations, resulting in low success rates and low effectiveness in achieving intentions. Therefore, there is an urgent need for a method to execute intentions that can improve the reliability of the system in executing intentions. Summary of the Invention

[0003] This application provides a method and apparatus for executing intent, which can improve the reliability of the system executing intent.

[0004] In a first aspect, a method for executing an intent is provided. This method can be executed by an intent execution network element or a chip within the intent execution network element. The method includes: the intent execution network element receiving execution order information from an intent knowledge base, the execution order information indicating the order of a first operation and a second operation of the first intent; the intent execution network element determining, based on the execution order information, the sending order of sending the first operation to the first network element and the sending order of sending the second operation to the second network element; and the intent execution 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.

[0005] Therefore, in this application, the intent execution network element can determine the sending order of multiple operations based on the order of execution of multiple operations, so that multiple operations can be executed in sequence and can cooperate with each other, avoiding the failure of intent operation execution or failure to achieve the expected effect due to non-sequential execution, thereby improving the reliability of the system's intent execution.

[0006] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the intention execution network element receiving the execution result information of the first operation from the first network element; and the intention execution network element determining whether the first operation was successfully executed based on the execution result information.

[0007] Therefore, in this application, the intent execution network element can receive the execution result information of the operation and determine whether the operation was successfully executed based on the execution result information, thereby enabling the monitoring of the execution status of the operation and improving the reliability of the system's execution intent.

[0008] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the intent execution network element receiving first instruction information from the intent knowledge base, the first instruction information being used to instruct the intent execution network element to determine whether the first operation was successfully executed.

[0009] Therefore, in this application, the intent execution network element can obtain first instruction information from the intent knowledge base, and determine whether the operation was successfully executed based on the first instruction information, thereby improving the reliability of the system's intent execution.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the intention execution 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, including: the intention execution network element sends the first operation to the first network element, and if the intention execution network element determines that the first operation was successfully executed, the intention execution network element sends the second operation to the second network element.

[0011] Therefore, in this application, the network element intending to execute can issue subsequent operations only after confirming that the preceding operations have been successfully executed, thus avoiding the failure of subsequent operations or poor execution results due to the preceding operations not being successfully executed.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the intention execution network element receiving progress indication information, the progress indication information indicating that the intention execution network element needs to provide progress information, the progress information indicating the execution progress of the first operation and the second operation; and the intention execution network element sending progress information according to the progress indication information.

[0013] Therefore, in this application, the network element intended to perform the operation can be required to provide feedback on the execution progress, thereby enabling monitoring of the operation's execution status and improving the reliability of the system's execution intent.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the progress indication information is also used to indicate the period or frequency at which the network element executing the schematic diagram needs to provide progress information.

[0015] Therefore, in this application, the execution progress of the network element intended to perform the operation can be required to be fed back periodically or at a frequency, thereby enabling the monitoring of the execution status of the operation and improving the reliability of the system's execution intent.

[0016] Secondly, an apparatus for executing an intent is provided. The apparatus includes a processing unit and a transceiver unit. The transceiver unit is configured to receive execution order information from an intent knowledge base. The execution order information is used to indicate the order of a first operation and a second operation of the first intent. The processing unit is configured to determine, based on the execution order information, the transmission order in which the intent-executing network element sends the first operation to the first network element and the intent-executing network element sends the second operation to the second network element. The transceiver unit is further configured to send the first operation to the first network element and the second operation to the second network element according to the transmission order.

[0017] Therefore, in this application, the intent execution network element can determine the sending order of multiple operations based on the order of execution of multiple operations, so that multiple operations can be executed in sequence and can cooperate with each other, avoiding the failure of intent operation execution or failure to achieve the expected effect due to non-sequential execution, thereby improving the reliability of the system's intent execution.

[0018] In conjunction with the second aspect, in some implementations of the second aspect, the transceiver unit is further configured to receive the execution result information of the first operation from the first network element; the processing unit is further configured to determine whether the first operation was successfully executed based on the execution result information.

[0019] In conjunction with 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, the first indication information being used to instruct the network element to determine whether the first operation has been successfully executed.

[0020] In conjunction with the second aspect, in some implementations of the second aspect, the transceiver unit is specifically used to send a first operation to the first network element, and if it is determined that the first operation was successfully executed, to send a second operation to the second network element.

[0021] In conjunction with the second aspect, in some implementations of the second aspect, the transceiver unit is further configured to receive progress indication information, which is used to indicate that the device needs to provide progress information and to indicate the execution progress of the first and second operations; the processing unit is further configured to send progress information according to the progress indication information.

[0022] In conjunction with the second aspect, in some implementations of the second aspect, the progress indication information is also used to indicate the period or frequency at which the device needs to provide progress information feedback.

[0023] Thirdly, a method for executing an intent is provided, which can be executed by an intent execution network element or a chip in the intent execution network element. The method includes: the intent execution network element receiving execution result information of a first operation of a first intent from a first network element; the intent execution network element determining, based on the execution result information, that an execution of the first operation has encountered an anomaly; and the intent execution network element sending rollback indication information to a second network element, the rollback indication information being used to indicate the rollback of a second operation of the first intent.

[0024] Therefore, in this application, if an abnormality occurs in the execution of a certain operation of the first intent, other operations of the first intent that have already been executed can be rolled back, avoiding the waste of resources and signaling caused by other operations of the first intent being in continuous execution, thereby improving the execution efficiency of the intent.

[0025] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: the intent execution network element receiving second instruction information from the intent knowledge base, the second instruction information being used to instruct the schematic diagram execution network element to determine that the execution of the first operation has encountered an anomaly.

[0026] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: the intent execution network element receiving rollback scheme information from the intent knowledge base, the rollback scheme information being used to indicate the rollback method of the second operation, and the rollback indication information also being used to indicate the rollback method of the second operation.

[0027] Therefore, in this application, the network element intending to execute the operation can instruct the network element performing the operation on the rollback method, thereby avoiding the failure of network elements without rollback capability to successfully roll back the operation and improving the reliability of the system's execution intent.

[0028] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: the intent execution network element determines the rollback method of the second operation based on the execution result information and the rollback scheme information.

[0029] Therefore, in this application, when the network element executing the intent determines that an anomaly has occurred in the execution of the first operation, the network element executing the intent can determine which type of anomaly it is based on the execution result information, and determine the rollback method of the second operation based on the rollback plan information under such an anomaly, thereby improving the reliability of the system's execution intent.

[0030] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: the intention execution network element receiving progress indication information, the progress indication information indicating that the intention execution network element needs to provide progress information, the progress information indicating the execution progress of the first operation and the second operation; and the intention execution network element sending progress information according to the progress indication information.

[0031] Therefore, in this application, the network element intended to perform the operation can be required to provide feedback on the execution progress, thereby enabling monitoring of the operation's execution status and improving the reliability of the system's execution intent.

[0032] In conjunction with the third aspect, in some implementations of the third aspect, the progress indication information is also used to indicate the period or frequency at which the network element executing the schematic diagram needs to provide progress information.

[0033] Therefore, in this application, the execution progress of the network element intended to perform the operation can be required to be fed back periodically or at a frequency, thereby enabling the monitoring of the execution status of the operation and improving the reliability of the system's execution intent.

[0034] Fourthly, an apparatus for executing an intent is provided. The apparatus includes a processing unit and a transceiver unit. The transceiver unit is configured to receive execution result information of a first operation of a first intent from a first network element. The processing unit is configured to determine, based on the execution result information, that an abnormality has occurred in the execution of the first operation. The transceiver unit is further configured to send rollback indication information to a second network element. The rollback indication information is used to indicate that a second operation of the first intent should be rolled back.

[0035] Therefore, in this application, if an abnormality occurs in the execution of a certain operation of the first intent, other operations of the first intent that have already been executed can be rolled back, avoiding the waste of resources and signaling caused by other operations of the first intent being in continuous execution, thereby improving the execution efficiency of the intent.

[0036] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is also used to receive second instruction information from the intent knowledge base. The second instruction information is used to indicate that the network element executing the schematic diagram has determined that the execution of the first operation has encountered an anomaly.

[0037] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is also used to receive rollback scheme information from the intent knowledge base. The rollback scheme information is used to indicate the rollback method of the second operation, and the rollback indication information is also used to indicate the rollback method of the second operation.

[0038] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the processing unit is also used to determine the rollback method of the second operation based on the execution result information and the rollback scheme information.

[0039] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is also used to receive progress indication information, which is used to indicate that the device needs to provide progress information, and the progress information is used to indicate the execution progress of the first operation and the second operation; the transceiver unit is also used to send progress information according to the progress indication information.

[0040] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the progress indication information is also used to indicate the period or frequency at which the network element executing the schematic diagram needs to provide progress information.

[0041] Fifthly, a communication device is provided, which may include a processing unit, a transmitting unit, and a receiving unit. Optionally, the transmitting unit and the receiving unit may also be transceivers.

[0042] When the device is an intended execution network element, the processing unit can be a processor, and the transmitting and receiving units can be transceivers. The device may also include a storage unit, which can be a memory. The storage unit stores instructions, and the processing unit executes the instructions stored in the storage unit to cause the intended execution network element to perform either the first or third aspect of the method. When the device is a chip within the intended execution network element, the processing unit can be a processor, and the transmitting and receiving units can be input / output interfaces, pins, or circuits, etc. The processing unit executes the instructions stored in the storage unit to cause the chip to perform either the first or third aspect of the method. The storage unit stores instructions and can be a storage unit within the chip (e.g., a register, cache, etc.) or a storage unit located outside the chip within the intended execution network element (e.g., a read-only memory, random access memory, etc.).

[0043] A sixth aspect provides a communication device, including a processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device, the processor being configured to implement any of the methods of the first or third aspect above through logic circuits or execution code instructions.

[0044] In a seventh aspect, a computer-readable storage medium is provided, which stores a computer program or instructions that, when executed, implement any of the methods described in the first or third aspect.

[0045] Eighthly, a computer program product containing instructions is provided, which, when executed, implement any of the methods described in the first or third aspect.

[0046] Ninthly, a computer program is provided, comprising code or instructions that, when executed, implement the methods in any possible implementation of the first or third aspect described above.

[0047] In a tenth aspect, a chip system is provided, comprising a processor and potentially a memory, for implementing at least one method described in the first or third aspect. The chip system may be composed of chips or may include chips and other discrete devices.

[0048] Eleventhly, a communication system is provided, the system including any of the means of the second or fourth aspect.

[0049] In some implementations, the first network element can be a first network device, and the second network element can be a second network device. Attached Figure Description

[0050] Figure 1 This is a schematic diagram of a system that is intended to be executed according to the embodiments of this application.

[0051] Figure 2 This is a schematic flowchart illustrating an example of an intent execution method provided in an embodiment of this application.

[0052] Figure 3 This is a schematic flowchart illustrating another example of an intent execution method provided in the embodiments of this application.

[0053] Figure 4 This is a schematic flowchart illustrating an example of a rollback operation method during execution provided in an embodiment of this application.

[0054] Figure 5 This is a schematic flowchart illustrating another example of a rollback operation method intended to be performed in an embodiment of this application.

[0055] Figure 6 This is an illustrative flowchart illustrating an example of an attempt to query network element information, provided in an embodiment of this application.

[0056] Figure 7 and Figure 8 This is a schematic diagram of the structure of a possible communication device provided in the embodiments of this application. Detailed Implementation

[0057] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0058] The technical solution of this application can be applied to various network function virtualization (NFV) systems. This system can use standard formal language to describe current operator service technology solutions, network construction solutions, and network operation and maintenance methods as patterns and strategies, and implement the technical solutions and construction solutions based on these patterns and strategies. For example, the technical solution of this application can be applied to one or more of the following systems: wireless intent-driven network (wIDN) systems, experiential networked intelligence (ENI) systems, intent-driven management service (IDMS) systems, or open network automation platform (ONAP) systems, etc.

[0059] For clarity, some terms in the embodiments of this application are explained below.

[0060] Intention: refers to the expectation of a system. Intention can include one or more of the following: requirements, intentional goals, and constraints.

[0061] Intent instance: The object that is instantiated from an intent. For example, in this application, an intent can be replaced with an intent instance.

[0062] Intent expression: An expression used to carry an intent. The expression includes one or more of the following: intent action name, intent action attribute, intent target name, or intent target attribute. Intent expressions have specific syntax and semantics.

[0063] Intended goal: This refers to the target value that the diagram needs to achieve.

[0064] Intent translation: The process of converting an intent into an executable command, rule, or sub-intent.

[0065] Intent execution: Distribute executable commands, sub-intents, and rules, and adjust them according to the network environment and intent achievement.

[0066] Intent-executable commands: A series of instructions formed by the translation of intent and other operations such as decision-making.

[0067] Intent Pattern: Defines the syntax and semantics of an intent expression. An intent pattern can include one or more of the following: fields, the range of values ​​for the fields, the types of the fields, and the hierarchical relationships between the fields. For example, fields can be used to describe the type, name, or consumer of the intent pattern.

[0068] Intent states: Intent states include active, conflicting, deactivated, and dormant states. An active intent is understood as being executed; a conflicting intent is understood as conflicting with other intents in the system; a deactivated intent is understood as not being executed; and a dormant intent is understood as its objective being temporarily suspended due to prolonged non-achievement.

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

[0070] Intent knowledge: Intent knowledge refers to the parameters related to intent patterns stored in the intent knowledge base. For example, the above-mentioned parameters may include one or more of the following: the executable operation corresponding to the intent, the identifier of the intent-acting entity, or the type of the intent-acting entity.

[0071] Intent action: The executable action corresponding to the intent target. An intent action includes one or more intent sub-actions.

[0072] Intent suboperation: A component of an intent operation. An intent suboperation may include one or more operation instructions, which are executed by an execution object.

[0073] Intent maintenance: Adjust the executable operations of the intent according to changes in the system network environment in order to achieve the intent goal.

[0074] Intent Achievement: The system detects that the KPI value in the network reaches the target value in the intent expression, or in other words, the intent goal is achieved.

[0075] To facilitate understanding of the embodiments of this application, firstly, in conjunction with... Figure 1 The system intended to be described in detail applies to the methods provided in the embodiments of this application. Figure 1 A schematic diagram of a system 100 illustrating the processing intent applicable to the methods provided in embodiments of this application is shown. For example... Figure 1 As shown, the system 100 includes an intent consumption network element 110, an intent provision network element 120, and a network device 130. The intent provision 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.

[0076] The intent-consuming network element 110, also known as the intent consumer, is the subject that consumes the intent. For example, the intent-consuming network element 110 can be an operations support system (OSS), a business support system (BSS), an application (APP), or other user equipment. For an IDMS system, the intent-consuming network element 110 can be a service consumer or a management service (MnS) network element, such as a network management system (NMS). The intent-consuming network element 110 can communicate with the intent-providing network element 120; for example, the intent-consuming network element 110 can send a request to the intent-providing network element 120 to create or implement an intent.

[0077] The intent management network element 121 can be used for intent pattern management. It can receive request information from the intent consumption network element 110 and process the request information. The intent management network element 121 may include an intent pattern library for storing intent patterns. The intent management network element 121 may also include an intent instance library, through which it can obtain the status information of the intent pattern, the intent target, and the corresponding operation.

[0078] The intent translation network element 122 can receive translation request information from the intent management network element 121 to realize the intent translation function. The intent translation network element 122 can also obtain the intent pattern from the intent management network element 121 and perform syntactic and semantic checks on the information provided by the intent consumption network element 110.

[0079] The intent execution network element 123 can receive commands from the intent management network element 122 and the intent translation network element 121, and implement the relevant operations of the intent.

[0080] The knowledge management network element 124 can manage the intent knowledge base, which stores relevant knowledge about intents. The knowledge management network element can also support other network elements in querying relevant knowledge about intents.

[0081] It should be noted that systems with different processing intentions may also include other network elements with corresponding functions.

[0082] For example, a WIDN system may also include a knowledge management network element and an intent knowledge base. The intent management network element manages intent knowledge. The intent knowledge base can be a submodule of the knowledge management network element, used to store intent knowledge. The intent management network element may also include an intent pattern library and an intent instance library; the intent pattern library stores intent patterns, and the intent instance library stores intents.

[0083] For an ENI system, it may also include one or more of the following: input function network elements, output function network elements, analysis function network elements, and decision function network elements. Input function network elements may include data collection network elements and normalization network elements, used to receive data from external systems and perform operations such as data normalization. Output function network elements may include output network elements and de-normalization network elements, used to convert internal system commands into a format that the external system can process and send them to the external system. Analysis function network elements can be used to perceive and analyze the current network state and predict the future network state. For example, analysis function network elements may include knowledge management network elements, context-aware network elements, and cognitive management network elements. The knowledge management network element can manage intent knowledge, the context-aware network element can perceive and analyze the current network state, and the cognitive management network element can perform management analysis. The aforementioned intent management network element and intent translation network element can be sub-network elements within this analysis function network element. The decision-making function network element is used to generate new operation commands based on the network status awareness and policy objectives, and to orchestrate the operation commands and send them to the output network element. The decision-making function network element can include a policy management network element, a context awareness network element, and a drive management network element. The policy management network element is used to manage intent policies, the context awareness network element is used to perceive and analyze the network status, and the drive management network element is used to drive and manage intents.

[0084] For an IDMS system, the intent-consuming network element can be a network management system (NMS), the intent-providing network element can be an element management system (EMS), and the intent-managing network element, intent-translating network element, and intent-executing network element can be sub-modules of the intent-providing network element.

[0085] The assistance system 130 may include at least one network device, each of which can communicate with the intent-providing network element 120. For example, the intent-executing network element 123 in the intent-providing network element 120 can send an intent execution operation request to any network device in the assistance system 130.

[0086] In this embodiment of the application, the network device in the assistance system 130 can be any device with wireless transceiver function. This equipment includes, but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home-evolved Node B, or home Node B, HNB), baseband unit (BBU), satellite, drone base station, access point (AP), wireless relay node, wireless backhaul node, transmission point (TP), or transmission and reception point (TRP) in a wireless fidelity (WiFi) system. It can also be a gNB in ​​a 5G system, such as NR, 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 a network node constituting a gNB or transmission point, such as a baseband unit (BBU) or a distributed unit (DU).

[0087] In some deployments, a gNB may include a centralized unit (CU) and a distribution unit (DU). The gNB may also include an active antenna unit (AAU). The CU implements some of the gNB's functions, and the DU implements others. For example, the CU handles non-real-time protocols and services, implementing radio resource control (RRC) and packet data convergence protocol (PDCP) layer functions. The DU handles physical layer protocols and real-time services, implementing radio link control (RLC), medium access control (MAC), and physical (PHY) layer functions. The AAU implements some physical layer processing functions, radio frequency processing, and active antenna-related functions. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can be considered to be sent by the DU, or by the DU+AAU. It is understood that network devices can be devices that include one or more of the following: CU nodes, DU nodes, and AAU nodes. In addition, the CU can be classified as a network device in the radio access network (RAN) or as a network device in the core network (CN), and this application does not limit this.

[0088] It should be noted that the solution of this application can be applied to other systems containing the corresponding network elements, and this application does not limit it. It is understood that the aforementioned network element or function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the aforementioned network element or function can be implemented by one device, multiple devices working together, or a functional module within a single device; this application does not specifically limit this aspect.

[0089] Currently, to achieve a desired outcome, multiple network devices need to execute various operations related to that intent. The success or failure of each operation affects the final result. However, current mechanisms for managing intent operations do not consider the coordination between operations, resulting in low success rates and poor outcomes. Therefore, there is an urgent need for a method to execute intents that can improve the reliability of the system in achieving its intended goals.

[0090] Figure 2An example schematic flowchart of the intent execution method 200 provided in this application is shown.

[0091] S201, the intent execution network element receives execution order information from the intent knowledge base.

[0092] This execution order information is used to indicate the order in which the first operation and the second operation of the first intent are performed.

[0093] The execution order information can be stored in the intent knowledge base during the intent knowledge base initialization and update process. The intent knowledge base can be a sub-module of the knowledge management network element.

[0094] The first operation may include multiple operation instructions, which can be fully executed by the first network element (e.g., network device #1); the second operation may also include multiple operation instructions, which can be fully executed by the second network element (e.g., network device #2).

[0095] There can be a dependency between the first and second operations.

[0096] For example, the second network element's execution of the second operation depends on the first network element's successful execution of the first operation.

[0097] The first operation and the second operation of the first intent can be one or more sub-operations of the intent operation corresponding to the first intent. For example, the intent operation corresponding to the first intent includes three sub-operations: 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 and third sub-operations are a second network element. If the three sub-operations are executed in the order of the first sub-operation, the second sub-operation, and the third sub-operation, then in the embodiments of this application, the first operation can be the first sub-operation, and the second operation can be a combined operation of the second and third sub-operations; if the three sub-operations are executed in the order of the second sub-operation, the first sub-operation, and the third sub-operation, then in the embodiments of this application, the first operation can be the first sub-operation, the second operation can be the second sub-operation, and the embodiments of this application also include a third operation of the first intent, where the third operation is a third sub-operation, and the execution order information can be used to indicate the order of the first, second, and third operations.

[0098] It should be understood that this application does not limit the number of operations in the execution sequence information indicating the order of multiple operations, nor does it limit the number of execution objects that need to perform the operations. It is used as an example, not a limitation, with the intent goal of the first intent being community relocation. The intent operation of the first intent includes 6 sub-operations, which are:

[0099] First sub-operation: Delete the neighbor relationship with cell A, executed by the first network element;

[0100] Second sub-operation: Deactivate cell A, executed by the second network element;

[0101] Third sub-operation: Delete cell A, executed by the second network element;

[0102] Fourth sub-operation: Create a new cell A, executed by the third network element;

[0103] Fifth sub-operation: Activate cell A, executed by the third network element;

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

[0105] The execution order information is used to indicate the order in which the six sub-operations are executed. It can be expressed as indicating the order in which the first operation, the second operation, the third operation, and the fourth operation are executed. Here, the first operation is the first sub-operation, the second operation is the combined operation of the second and third sub-operations, the third operation is the combined operation of the fourth and fifth sub-operations, and the fourth operation is the sixth sub-operation.

[0106] Additionally, it should be noted that when the operation in the embodiments of this application includes multiple sub-operations, such as when the second operation is a combined operation of the second and third sub-operations, the order of execution of the second and third sub-operations can be indicated by the operation instructions describing the second operation.

[0107] For clarity, the following explains how the execution sequence information indicates the order in which the first operation and the second operation of the first intent are executed.

[0108] Method 1:

[0109] The execution sequence information includes the step ID of the first operation and the step ID of the second operation.

[0110] The step identifier indicates the order in which the corresponding operation is performed among all operations. Operations with different step identifiers must be executed sequentially, while operations with the same step identifier can be executed in parallel. The step identifier of the first operation can be included in the description information of the first operation, and the step identifier of the second operation can be included in the description information of the second operation.

[0111] For example, the step identifier of the first operation is 1 (e.g., stepID=1), and the step identifier of the second operation is 2 (e.g., stepID=2), indicating that the second operation is performed after the first operation.

[0112] For example, if the step identifier of the first operation is 1 (e.g., stepID=1) and the step identifier of the second operation is also 1 (e.g., stepID=1), it means that the first operation and the second operation can be executed in parallel.

[0113] Method 2:

[0114] The execution order information includes the step ID and wait type of the first operation, as well as the step ID and wait type of the second operation.

[0115] The wait type indicates whether the corresponding operation needs to wait for the completion of a preceding operation, and the step identifier indicates the order in which the corresponding operation is executed. Multiple operations cannot have duplicate step identifier values. If multiple operations have consecutive step identifier values, and the wait types of all operations except the first one indicate that they do not need to wait for the completion of a preceding operation, then these operations with consecutive step identifier values ​​can be executed in parallel. The step identifier and wait type of the first operation can be included in the description information of the first operation, and the step identifier and wait type of the second operation can be included in the description information of the second operation.

[0116] For example, the first operation is identified by step ID 1 and the wait type is "no wait" (e.g., stepID = 1, waitType = not wait), and the second operation is identified by step ID 2 and the wait type is "no wait" (e.g., stepID = 2, waitType = not wait). This means that the second operation does not need to wait for the first operation to complete before it is executed, and the first and second operations can be executed in parallel.

[0117] For example, the first operation is identified by step 1 and the waiting type is no waiting (e.g., stepID=1, waitType=not wait), the second operation is identified by step 2 and the waiting type is waiting (e.g., stepID=2, waitType=wait), and there is a third operation identified by step 3 and the waiting type is no waiting (e.g., stepID=3, waitType=not wait). This means that the second and third operations can be executed in parallel after the first operation is completed.

[0118] Method 3:

[0119] The execution order information includes the mapping relationship between the identifier of the first operation and the order in which the first operation is executed, and the mapping relationship between the identifier of the second operation and the order in which the second operation is executed.

[0120] For example, the execution order information is a mapping table between the identifier of an operation and the execution order of the operations. The execution order of the first or second operation can be indexed by the identifier of the first or second operation.

[0121] The above description explains the method of indicating the order of execution of the first and second operations using execution order information. It should be understood that the above method is also applicable to scenarios where the execution order information indicates the order of execution of three or more operations, and this application does not make any special limitation in this regard.

[0122] S202, the intention execution network element determines the sending order of sending the first operation to the first network element and sending the second operation to the second network element based on the execution order information.

[0123] S203, the intention is to have the network element send the first operation to the first network element according to the transmission order.

[0124] S204, the intention is for the network element to send the second operation to the second network element according to the transmission order.

[0125] If the network element intending to execute determines, based on the execution order information, that the first operation needs to be executed first, followed by the second operation, then it determines to send the first operation to the first network element first, followed by the second operation to the second network element; that is, to execute step S203 first, followed by step S204. If the network element intending to execute determines, based on the execution order information, that the second operation needs to be executed first, followed by the first operation, then it determines to send the second operation to the second network element first, followed by the first operation to the first network element; that is, to execute step S204 first, followed by step S203. If the network element intending to execute determines, based on the execution order information, that the first and second operations can be executed in parallel, then the order in which the network element intends to execute sends the first operation to the first network element and the second operation to the second network element is not limited.

[0126] In one possible implementation, the network element intending to perform needs to determine whether the first operation was successfully performed, and the method may further include one or more steps in steps S205 to S207.

[0127] S205, the intention is for the network element to receive the execution result information of the first operation from the first network element.

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

[0129] For example, the execution result information includes an indicator of whether the first operation was executed successfully.

[0130] The execution result information can be carried in the operation execution response message in response to the first operation, or it can be carried in the response message in response to the query message.

[0131] S206, the intent execution network element determines whether the first operation was successfully executed based on the execution result information.

[0132] For example, the execution result information includes a field indicating whether the first operation was successful. The network element intending to execute the operation determines whether the first operation was successful based on this field. For example, if the field is 1, the first operation is considered successful, and if the field is 0, the first operation is considered unsuccessful.

[0133] In one possible implementation, the execution result information could be relevant system parameters after the first network element completes the first operation, or it could be the execution status of the first operation, such as an execution status indicator showing how many instructions have been executed within the first time period. In other words, if the execution result information does not indicate whether the first operation was successfully executed, then step S207 needs to be executed before step S206. In step S206, the network element intending to execute determines whether the first operation was successfully executed based on the execution result information and the first indication information.

[0134] S207, the intent execution network element receives the first instruction information from the intent knowledge base.

[0135] The first instruction information can be used to instruct the network element to determine whether the first operation was successfully performed.

[0136] Optionally, the first instruction information may be carried in the description information of the first operation.

[0137] Optionally, the first indication information may include criteria for determining whether the first operation was successfully performed.

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

[0139] It should be noted that this judgment criterion can implicitly instruct the schematic execution network element to determine whether the first operation was successfully executed. In other words, the intent execution network element can receive the judgment criterion from the intent knowledge base, and the intent execution network element needs to determine whether the first operation was successfully executed according to this judgment criterion by default.

[0140] Optionally, the first indication information may include a criterion for determining whether the first operation was successfully executed, and a judgment action that the network element intending to execute needs to perform to determine whether the first operation was successfully executed. For example, the judgment action may indicate that the network element intending to execute needs to send a query message to the first network element to obtain the execution result information of the first operation.

[0141] The network element intending to execute can determine whether the first operation has been successfully executed based on the first instruction information, and execute the indicated judgment action to obtain relevant execution result information after the first operation is executed. Then, based on the judgment criteria and the execution result information, it can determine whether the first network element has successfully executed the first operation.

[0142] Taking the determination action as an example, where the network element executing the action needs to send a query message to obtain the execution result information of the first operation: the network element executing the action sends a query message to the first network element based on the determination action. The first network element queries the execution result information of the first operation based on the query message and returns a response message to the network element executing the action, which carries the execution result information of the first operation. The network element executing the action determines whether the first operation was successfully executed based on the execution result information and the determination criteria. The query message may request the first network element to return specific parameters required by the determination criteria, or it may request the first network element to return all relevant parameters of the system after the execution of the first operation. This application does not impose any particular limitation on this.

[0143] The above describes how the network element executing the intent determines whether the first operation has been successfully executed. It should be understood that the network element executing the intent determines whether other operations (such as the second operation) have been successfully executed in a similar way to the description of determining the first operation. For the sake of simplicity, it will not be repeated here.

[0144] In one possible implementation, when the network element intending to execute first sends a first operation to a first network element and then sends a second operation to a second network element, the network element intending to execute can determine whether the first operation was successfully executed after sending it to the first network element. If it was successfully executed, then it sends the second operation to the second network element. In other words, in step S204, if the network element intending to execute determines that the first operation was successfully executed, then the network element intending to execute sends the second operation to the second network element.

[0145] The method by which the network element intends to determine whether the first operation has been successfully executed can be found in the description of steps S205 to S207. In other words, steps S205 to S207 can be executed between steps S203 and S204.

[0146] It should be understood that when an intent-executing network element first sends a second operation to a second network element and then sends a first operation to a first network element, the intent-executing network element can also determine whether the second operation was successfully executed after sending it to the second network element. If the second operation was successful, then it can send the first operation to the first network element. In other words, before sending an operation, the intent-executing network element can determine whether the preceding operation was successfully executed, and send the operation only if it was successful, thereby improving the reliability of intent execution.

[0147] In one possible implementation, if it is desired that the network element executing the intent provides feedback on the execution progress of the operation, the network element executing the intent can receive progress indication information from the network element translating the intent.

[0148] This progress indication information is used to indicate the progress information that the network element executing the schematic diagram needs to provide. This progress information is used to indicate the execution progress of the first operation and the second operation.

[0149] For example, the progress information is used to indicate the percentage of the first and second operations that have been executed, the estimated time remaining until completion, or the number of operation instructions that have been completed, etc. This application does not make any special limitations on this.

[0150] The progress indication information can be carried in the intent execution message sent by the intent translation network element to request the execution of the first intent. For example, if the intent consumption network element wants to obtain the execution progress of the operation, the intent consumption network element can carry the progress indication information in the intent implementation request message sent to the intent management network element, the intent management network element can carry the progress indication information in the intent translation message sent to the intent translation network element, and then the intent translation network element can carry the progress indication information in the intent execution message sent to the intent execution network element.

[0151] Optionally, the progress indication information can also be used to indicate the period or frequency at which the network element executing the schematic diagram needs to provide progress information.

[0152] Optionally, the progress indication information can also be used to indicate the triggering conditions under which the network element executing the schematic diagram needs to provide progress information. For example, the progress indication information can indicate that when a certain parameter of the current system reaches a predetermined triggering condition, the network element executing the schematic diagram needs to provide feedback on the execution progress of the current first and second operations.

[0153] The intent execution network element sends the progress information to the intent management network element based on the progress indication information.

[0154] Optionally, the intent management network element can also send progress information to the intent consumption network element.

[0155] Optionally, after receiving the progress indication information, the intent execution network element can determine the progress information based on the relevant information of the execution results returned by the first network element and / or the second network element, and return the progress information to the intent management network element. The intent execution network element can also send a query message to the first network element and / or the second network element to obtain the progress information based on the progress indication information.

[0156] If the progress indication information also indicates the period and frequency at which the intent execution network element needs to provide feedback, the intent execution network element can also send the progress information to the intent management network element according to the period and frequency.

[0157] In one possible implementation, in step S201, the intent execution network element can receive execution order information from the intent knowledge base in two ways: First, after receiving the intent translation message sent by the intent management network element, the intent translation network element sends an intent knowledge query message to the knowledge management network element based on the identifier information and intent expression of the first intent in the intent translation message. The knowledge management network element then queries the intent knowledge base based on the intent knowledge query message and sends an intent knowledge feedback message to the intent translation network element, carrying the execution order information in the intent knowledge feedback message, thereby enabling the intent execution network element to execute the execution order information. The translation network element can carry the execution order information in the intent execution request message sent to the intent execution network element; secondly, after receiving the intent execution request message sent by the intent translation network element, the intent translation network element can send an intent operation query message to the knowledge management network element according to the intent expression and / or operation identifier (the identifier of the first operation and / or the second operation) in the intent execution request message. The knowledge management network element performs a query in the intent knowledge base according to the operation query message and sends an intent operation feedback message to the intent execution network element, carrying the execution order information in the intent operation feedback message.

[0158] In other words, the intent execution network element receives execution order information from the intent knowledge base. This execution order information can be obtained from the intent knowledge base by other network elements through queries and then forwarded to the intent execution network element. Alternatively, the execution order information can be obtained from the intent knowledge base by the intent execution network element itself through queries.

[0159] It should be understood that the above describes how the intent execution network element receives execution order information from the intent knowledge base. In S205, the way the intent execution network element receives the first instruction information from the intent knowledge base can be similar to the description of receiving execution order information. For the sake of simplicity, it will not be described again here.

[0160] Therefore, in this application, the intent execution network element can determine the sending order of multiple operations based on the order of execution of multiple operations, so that multiple operations can be executed in sequence, and multiple operations can cooperate with each other, avoiding the failure of intent operation execution or failure to achieve the expected effect due to non-order execution.

[0161] Figure 3 Another illustrative flowchart of the intent execution method 300 provided in this application is shown.

[0162] Optionally, in S301, the intent-consuming network element sends an intent implementation request message to the intent-managing network element.

[0163] The intent enforcement request message is used to request the execution of a first intent, which may include the intent expression of the first intent.

[0164] Optionally, the intent implementation request message may also include progress notification information (progressNotify). For a description of the progress notification information, please refer to the description of the progress notification information in method 200. For simplicity, it will not be repeated here.

[0165] Optionally, in S302, the intent management network element sends an intent implementation request response message to the intent consumption network element in response to the intent implementation request message.

[0166] The intent implementation request-response message may include the identifier of the first intent (intentID) and the intent expression of the first intent.

[0167] For example, after receiving the intent implementation request message corresponding to the first intent, the intent management network element assigns an identifier to the first intent and sends the identifier in the intent implementation request response message to the intent consumption network element.

[0168] Optionally, in S303, the intent management network element sends an intent translation request message to the intent translation network element.

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

[0170] The intent translation request message may include an identifier of the first intent and an intent expression. If the intent implementation request message includes progress indication information, then the intent translation message also includes the progress indication information.

[0171] S304, the intent translation network element sends an intent knowledge query message to the intent knowledge base.

[0172] The intent knowledge query message may include the identifier of the first intent and the intent expression, as well as the query type.

[0173] The query type can indicate the parameters that need to be retrieved. For example, if the query type is all parameters (type=all), then the intent knowledge base needs to return all parameters related to the first intent.

[0174] Optionally, S305, retrieve query results from the intent knowledge base.

[0175] The intent knowledge base retrieves query results based on the intent query message.

[0176] The intent knowledge base can be understood as a sub-module of the knowledge management network element. During the initialization and update process of the intent knowledge base, relevant information about the first intent, such as execution order information (stepinfo) and first indication information, is stored in the intent knowledge base. The knowledge management network element can then query the intent knowledge base based on intent knowledge query messages. For example, the first indication information includes success indication information.

[0177] For example, if the query type is to query the operation of the first intent, the intent knowledge base retrieves the intent operation list (intentOperationList) for the first intent. This intent operation list includes a description of the first operation and a description of the second operation. It should be understood that if the first intent has other operations, the intent operation list also includes descriptions of those other operations.

[0178] Taking the description of the first operation as an example, the description information of the first operation may include one or more of the following: the operation instruction of the first operation, and the operation execution object of the first operation (entityIDList). If the indication method of method 1 or method 2 in method 200 is used, the description information of the first operation also includes the execution order information of the first operation (stepInfo), such as {step ID}, or {step ID, waitType}. The operation instruction describes the specific command to execute the first operation, and the operation execution object describes the first network element that needs to execute the first operation.

[0179] Optionally, if the network element intending to perform needs to determine whether the execution of the first operation is successful, the description information of the first operation may also include the first instruction information. For a description of the first instruction information, please refer to the description of the first instruction information in method 200. For the sake of simplicity, it will not be repeated here.

[0180] It should be understood that the description information of other operations can be similar to that of the first operation, and for the sake of simplicity, it will not be repeated here.

[0181] The list of intended operations may also include execution condition information, which describes the conditions that need to be met to execute the first and second operations. For example, the first and / or second operations may be executed when the network load is idle or low.

[0182] The list of intent actions may also include dependent event information, which describes the potential impact of executing the first intent on the system.

[0183] If the query type is to query all parameters, the intent knowledge base can include not only the intent operation list of the first intent, but also the intent fulfillment criterion. The intent fulfillment criterion can be used to indicate the conditions for achieving the first intent. For example, the intent fulfillment criterion can include an intent goal calculation formula to measure whether the intent goal has been achieved.

[0184] Optionally, if the indication method of method 3 in method 200 is adopted, the intent knowledge base can also obtain execution order information (stepInfo), which describes the execution order of multiple operations of the first intent.

[0185] For details regarding the first operation, the second operation, and the execution order information indicating the order in which the first and second operations are performed, please refer to the relevant description in method 200. For simplicity, these details will not be repeated here.

[0186] The above is merely an illustrative example of the search results, and this application does not impose any specific limitations on it.

[0187] S306, the intent translation network element receives intent knowledge feedback messages from the intent knowledge base.

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

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

[0190] S307, the intent translation network element sends execution order information to the intent execution network element.

[0191] This execution order information is used to indicate the order in which the first operation and the second operation of the first intent are performed.

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

[0193] The intent translation request message may also include an identifier of the first intent, as well as a list of intent operations and intent goal achievement criteria obtained by the intent translation network element from the intent knowledge feedback message.

[0194] Optionally, if the network element intending to perform needs to provide feedback on the progress of the first and second operations, the set of intended operations may also include progress indication information.

[0195] After receiving the intent execution request message, the intent execution network element can determine the first and second operations to be executed according to a predetermined decision algorithm.

[0196] S308, the intention execution network element determines the sending order of sending the first operation to the first network element and sending the second operation to the second network element based on the execution order information.

[0197] The description of how the network element executing the intent determines the transmission order of sending the first operation and the second operation can be found in method 300, and will not be repeated here for simplicity. The following example illustrates how the network element executing the intent first sends the first operation to the first network element, and then sends the second operation to the second network element.

[0198] S309, the intention is for the network element to send the first operation to the first network element according to the transmission order.

[0199] For example, the network element intends to send an operation execution request message corresponding to the first operation to the first network element. The operation execution request message includes information corresponding to the first operation, wherein the information corresponding to the first operation may include the operation identifier (operationID) and operation instruction (instruction) of the first operation.

[0200] The first network element can execute the first operation based on the information corresponding to the first operation.

[0201] Optionally, in step S310, the network element intends to receive the execution result information of the first operation from the first network element.

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

[0203] For example, the intention of the network element to receive the operation execution request message from the first network element is to execute an operation execution response message. The operation execution response message includes the execution result information of the first operation, and may also include the operation identifier of the first operation.

[0204] For example, the first instruction information is also used to instruct the schematic execution network element to determine whether the first operation was successfully executed. This determination action indicates that the schematic execution network element needs to query the first network element for the execution result information of the first operation. In this case, the intention execution network element can send an operation execution status query message to the first network element. This operation execution status query message is used to request the query of the execution result information. The execution result information received by the intention execution network element is carried in the operation execution status query response message that responds to the operation execution status query message.

[0205] Optionally, in step S311, the intent-executing network element determines whether the first operation was successfully executed based on the first instruction information and the execution result information.

[0206] For a description of whether the network element intending to perform the first operation has been successfully executed, please refer to the description in method 200. For the sake of simplicity, it will not be repeated here.

[0207] If the network element determines that the first operation has been successfully executed, the network element can execute S312.

[0208] S312, intending to execute the second operation by sending a second operation from the network element to the second network element.

[0209] For example, the network element intends to send an operation execution request message corresponding to the second operation to the second network element. The operation execution request message includes information corresponding to the second operation, wherein the information corresponding to the second operation may include the operation identifier (operationID) and operation instruction (instruction) of the second operation.

[0210] It should be understood that the intent execution network element can also receive the execution result information of the second operation from the second network element. The intent execution request message can also include the first instruction information of the second operation. The intent execution network element can also determine whether the second operation has been successfully executed based on the first instruction information and the execution result information of the second operation. If the operation corresponding to the first intent also has a third operation that the intent management network element needs to execute, and the execution order of the third operation is after the second operation, then the intent execution network element can also send the third operation to the intent management network element when it is determined that the second operation has been successfully executed. The implementation method is similar to that described above for the first operation. For the sake of simplicity, it will not be repeated here. This application does not impose any limitation on the number of operations corresponding to the first intent.

[0211] If the intention to execute request message also includes progress indication information, the method further includes step S313.

[0212] S313, the intent execution network element sends an operation execution progress notification message to the intent management network element.

[0213] The operation execution progress notification message may include the identifier of the first intent and progress information. For a description of the progress information, please refer to the relevant description in method 200. For the sake of simplicity, it will not be repeated here.

[0214] Optionally, if the progress indication information is also used to indicate the period or frequency at which the intention execution network element needs to provide progress information, the intention execution network element can monitor the progress of the operation execution according to the period or frequency, and send the operation execution progress notification message to the intention management network element according to the period or frequency.

[0215] If the intending consumer network element needs to obtain this progress information, the intending management network element can forward the operation execution progress notification message to the intending consumer network element.

[0216] Therefore, in this application, the intent execution network element can determine the sending order of multiple operations based on the order of execution of multiple operations, so that multiple operations can be executed in sequence, and multiple operations can cooperate with each other, avoiding the failure of intent operation execution or failure to achieve the expected effect due to non-order execution.

[0217] Figure 4 An example schematic flowchart of the intent execution method 400 provided in this application is shown.

[0218] S401, the network element intending to execute receives the execution result information of the first operation of the first intention from the first network element.

[0219] The execution result information is used to determine whether an anomaly occurred during the execution of the first operation.

[0220] The abnormality in the execution of the first operation can refer to any of the following situations: the first operation fails to execute, the first operation times out, the execution result of the first operation does not achieve the intended effect, or other situations that prevent the first intention from achieving the intended goal.

[0221] For example, the execution result information may include an indicator of whether an error occurred during the execution of the first operation.

[0222] S402, the network element intends to determine whether an abnormality occurred during the execution of the first operation based on the execution result information.

[0223] For example, the execution result information includes a field indicating whether an abnormality occurred during the execution of the first operation. The network element intending to execute determines whether an abnormality occurred during the execution of the first operation based on this field. For example, if the field is 1, it means that an abnormality occurred during the execution of the first operation, and if the field is 0, it means that no abnormality occurred during the execution of the first operation.

[0224] In one possible implementation, the execution result information could be relevant system parameters after the first network element completes the first operation, or it could be the execution status of the first operation. For example, the execution status could indicate how many instructions have been executed within the first time period. In other words, if the execution result information does not indicate whether an abnormality occurred during the execution of the first operation, then step S403 needs to be executed before step S402. In step S402, the network element intending to execute determines whether an abnormality occurred during the execution of the first operation based on the execution result information and the second indication information.

[0225] S403, the intent execution network element receives the second instruction information from the intent knowledge base.

[0226] The second instruction is used to instruct the network element in the schematic diagram to determine whether an abnormality has occurred in the execution of the first operation.

[0227] This second instruction information can be stored in the intent knowledge base during the intent knowledge base initialization and update process.

[0228] The second instruction information can be carried in the description information of the first operation.

[0229] Optionally, the second indication information may include criteria for determining whether an abnormality has occurred in the execution of the first operation.

[0230] The intent execution network element determines whether the execution of the first operation has encountered an anomaly based on the execution result information and judgment criteria. For example, the judgment criteria indicate that the first operation is judged to have encountered an anomaly when a certain parameter reaches a predetermined range. For example, the judgment criteria indicate that if the result of the first operation does not reach a predetermined result, it indicates that the execution of the first operation has encountered an anomaly. After receiving the execution result information, the intent execution network element determines whether the predetermined result has been reached based on the execution result information to determine whether the execution of the first operation has encountered an anomaly. For example, the judgment criteria indicate that if the first operation fails to execute successfully within a predetermined time, it indicates that the execution of the first operation has encountered an anomaly. If the execution result information received by the intent execution network element within the predetermined time indicates that the first operation failed, or if the intent execution network element does not receive execution result information indicating that the first operation was successful within the predetermined time, then the intent execution network element can determine that the execution of the first operation has encountered an anomaly.

[0231] It should be noted that this anomaly judgment criterion can implicitly indicate that the schematic execution network element can determine whether the execution of the first operation has encountered an anomaly. In other words, the intent execution network element can receive this judgment criterion from the intent knowledge base, and the intent execution network element is required by default to determine whether the execution of the first operation has encountered an anomaly based on this judgment criterion.

[0232] Optionally, the second indication information may include a criterion for determining whether an anomaly has occurred in the execution of the first operation, and a judgment action that the network element intending to execute needs to perform to determine whether an anomaly has occurred in the execution of the first operation. For example, the judgment action may indicate that the network element intending to execute needs to send a query message to the first network element to obtain the execution result information of the first operation.

[0233] The intent execution network element can determine whether the execution of the first operation has encountered an anomaly based on the second instruction information, and execute the indicated judgment action to obtain relevant execution result information after the execution of the first operation. Then, based on the anomaly judgment criteria and the execution result information, it can determine whether the execution of the first operation has been successful.

[0234] Taking the example of a network element executing an action request sending a query message to obtain the execution result information of a first operation: the network element executing the action requests a query message to the first network element. The first network element queries the execution result information of the first operation based on the query message and returns a response message to the network element executing the action request. This response message carries the execution result information of the first operation. The network element executing the action request determines whether an anomaly has occurred in the execution of the first operation based on this execution result information and the judgment criteria. The query message may request the first network element to return specific parameters required by the judgment criteria, or it may request the first network element to return all relevant parameters of the system after the execution of the first operation. This application does not impose any particular limitation on this.

[0235] The above describes how the network element intending to execute determines whether the execution of the first operation has encountered an anomaly. It should be understood that the network element intending to execute determines whether the execution of other operations has encountered an anomaly in a similar way to the description of determining the first operation. For the sake of simplicity, it will not be repeated here.

[0236] S404, when the network element intending to perform determines that an abnormality has occurred in the execution of the first operation, the network element intending to perform sends a rollback instruction to the second network element.

[0237] This rollback instruction information is used to indicate the second operation that reverses the first intention.

[0238] The first operation may include multiple operation instructions, which can be fully executed by the first network element (e.g., network device #1); the second operation may also include multiple operation instructions, which can be fully executed by the second network element (e.g., network device #2).

[0239] The second operation can be a preceding operation to the first operation, or a parallel operation to the first operation. In other words, the second operation can be an operation that the second network element has already successfully executed or is executing when the network element intending to execute determines that the execution of the first operation has encountered an error.

[0240] The first operation and the second operation of the first intent can be one or more sub-operations of the intent operation corresponding to the first intent. For example, the intent operation corresponding to the first intent includes three sub-operations: 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 and third sub-operations are a second network element. In this embodiment of the application, the first operation can be the first sub-operation, and the second operation can be a combined operation of the second and third sub-operations.

[0241] It should be understood that if other operations of the first intention exist in the system, and the network element executing the intention determines that the execution of the first operation has encountered an anomaly, while other network elements have already successfully executed or are in the process of executing operations, the network element executing the intention can also send rollback instruction information to other network elements to instruct them to roll back the operation. This is used as an example, not a limitation, with the intention goal of the first intention being cell relocation. The first intention has four operations:

[0242] First operation: Delete the neighbor relationship with cell A, executed by the first network element;

[0243] The second operation, deactivating and deleting cell A, is performed by the second network element.

[0244] The third operation: creating cell A and activating cell A, is performed by the third network element;

[0245] Fourth operation: Restore the neighbor relationship with cell A, executed by the first network element.

[0246] If the first and second operations have been successfully executed, but an error occurs in the execution of the third operation, the network element intends to send a rollback instruction to the second network element to roll back the second operation, and to the first network element to send a rollback instruction to roll back the first operation.

[0247] Rollback to the second operation can be understood as restoring the system to the state before the second operation was performed.

[0248] It should be understood that if other operations of the first intent exist in the system, and the intent-executing network element determines that the execution of the first operation has encountered an anomaly, but other network elements have already successfully executed or are currently executing operations, the intent-executing network element can also send rollback indication information to other network elements to instruct them to roll back the operation. For example, if the intent-management network element has successfully executed or is currently executing the third operation of the first intent, the intent-executing network element can also send indication information to the intent-management network element to instruct them to roll back the third operation. Optionally, the intent-executing network element can send the rollback indication information in reverse order of the order in which multiple operations were sent.

[0249] S405, the second network element performs a second rollback operation based on the rollback instruction information.

[0250] Among them, the method of rolling back the second operation can be determined based on whether the second network element has the ability to roll back the operation.

[0251] If the second network element has the ability to roll back operations, then after receiving the rollback instruction information, the second network element can call its own operation rollback capability to roll back the second operation.

[0252] If the second network element does not have the ability to roll back the operation, the rollback instruction information sent by the network element intending to execute the operation can also be used to instruct the second network element to roll back the second operation. In this case, the method 400 further includes step S406.

[0253] S406, the intent execution network element receives rollback scheme information from the intent knowledge base.

[0254] The rollback scheme information is used to indicate the rollback method of the second operation, and the rollback instruction information sent by the network element intending to perform the operation is also used to indicate the rollback method of the second operation.

[0255] It should be understood that the rollback instruction information can be the rollback method of the second operation, or in other words, the network element intending to perform the operation can send the rollback method of the second operation to the second network element, which implicitly indicates that the second network element needs to roll back the second operation.

[0256] The rollback scheme information can be stored in the intent knowledge base during the intent knowledge base initialization and update process.

[0257] The rollback plan information can be included in the description information of the corresponding second operation.

[0258] In one possible implementation, the rollback scheme information describes the rollback method for different second operations under different abnormal conditions. In this case, the method 400 further includes step S407.

[0259] S407, the network element intending to perform the operation determines the rollback method for the second operation based on the execution result information and the rollback scheme information.

[0260] For example, the rollback scheme information includes the mapping relationship between abnormal situations and rollback methods. Different abnormal situations correspond to different labels. The execution result information may include the label corresponding to the abnormal situation that occurred during the execution of the first operation. The network element intending to execute the operation indexes the rollback method of the second operation corresponding to the abnormal situation based on the label and sends the rollback method of the second operation to the second network element.

[0261] For example, the rollback scheme information includes the mapping relationship between abnormal situations and rollback methods, and the execution result information includes relevant parameters after the execution of the first operation. The network element intends to determine which abnormal situation it belongs to based on the relevant parameters, and then determine the rollback method of the second operation, and send the rollback method of the second operation to the second network element.

[0262] In one possible approach, when the intent-executing network element determines that the execution of the first operation has encountered an anomaly, the intent-executing network element may first query the intent-consuming network element whether a second operation needs to be rolled back. When the intent-consuming network element reports that a second operation needs to be rolled back, the intent-executing network element then sends a rollback instruction to the second network element. In this case, the method further includes step S408, which can be executed between steps S403 and S404, wherein in step S403, the intent-executing network element determines that the execution of the first operation has encountered an anomaly.

[0263] S408, the intent execution network element sends an intent operation rollback request message to the intent management network element.

[0264] The intention operation rollback request message is used to indicate whether the second network element needs to roll back the second operation.

[0265] Optionally, the intention operation rollback request message may include at least one of the following: identification information of the first intention, relevant information indicating that an exception occurred during the execution of the first operation, and rollback method of the second operation.

[0266] When the intent-consuming network element receives the intent operation rollback request message, it can determine whether to roll back the second operation based on the current system operation status or the abnormal situation of the first operation.

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

[0268] If the intention operation rollback response message indicates that the second operation does not need to be rolled back, then the network element that intends to execute the operation does not need to send rollback indication information to the second network element.

[0269] If the intention operation rollback response message indicates that the second operation needs to be rolled back, then step S404 can be executed, in which the intention execution network element sends rollback instruction information to the second network element.

[0270] In one possible approach, the intent translation network element carries expected processing type indication information in the intent execution request message sent to the intent execution network element. This expected processing type indication information is used to indicate whether the intent execution network element needs to query the intent consumption network element to see if a second operation needs to be rolled back if an abnormality is found in the execution of the first operation. If the processing type indication information indicates that it is not necessary to query the intent consumption network element to see if a second operation needs to be rolled back, the intent execution network element can directly send rollback indication information to the second network element. If the processing type indication information indicates that it is necessary to query the intent consumption network element to see if a second operation needs to be rolled back, the intent execution network element needs to execute step S408.

[0271] In one possible implementation, if it is desired that the network element executing the intent provides feedback on the execution progress of the operation, the network element executing the intent can receive progress indication information from the network element translating the intent.

[0272] This progress indication information is used to indicate the progress information that the network element executing the schematic diagram needs to provide. This progress information is used to indicate the execution progress of the first operation and the second operation.

[0273] For example, the progress information is used to indicate the percentage of the first and second operations that have been executed, the estimated time remaining until completion, or the number of operation instructions that have been completed, etc. This application does not make any special limitations on this.

[0274] The progress indication information can be carried in the intent execution message sent by the intent translation network element to request the execution of the first intent. For example, if the intent consumption network element wants to obtain the execution progress of the operation, the intent consumption network element can carry the progress indication information in the intent implementation request message sent to the intent management network element, the intent management network element can carry the progress indication information in the intent translation message sent to the intent translation network element, and then the intent translation network element can carry the progress indication information in the intent execution message sent to the intent execution network element.

[0275] Optionally, the progress indication information can also be used to indicate the period or frequency at which the network element executing the schematic diagram needs to provide progress information.

[0276] Optionally, the progress indication information can also be used to indicate the triggering conditions under which the network element executing the schematic diagram needs to provide progress information. For example, the progress indication information can indicate that when a certain parameter of the current system reaches a predetermined triggering condition, the network element executing the schematic diagram needs to provide feedback on the execution progress of the current first and second operations.

[0277] The intent execution network element sends the progress information to the intent management network element based on the progress indication information.

[0278] Optionally, if the intending consumer network element needs to obtain progress information, the intending management network element can send the progress information to the intending consumer network element.

[0279] Optionally, after receiving the progress indication information, the intent execution network element can determine the progress information based on the relevant information of the execution results returned by the first network element and / or the second network element, and return the progress information to the intent management network element. The intent execution network element can also send a query message to the first network element and / or the second network element to obtain the progress information based on the progress indication information.

[0280] If the progress indication information also indicates the period and frequency at which the intent execution network element needs to provide feedback, the intent execution network element can also send the progress information to the intent management network element according to the period and frequency.

[0281] In one possible implementation, in step S401, the intent execution network element can receive the second indication information from the intent knowledge base in two ways: First, after receiving the intent translation message sent by the intent management network element, the intent translation network element sends an intent knowledge query message to the knowledge management network element based on the identifier information and intent expression of the first intent in the intent translation message. The knowledge management network element then queries the intent knowledge base based on the intent knowledge query message and sends an intent knowledge feedback message to the intent translation network element, carrying the second indication information in the intent knowledge feedback message, thereby enabling intent execution. The translation network element can carry the second indication information in the intent execution request message sent to the intent execution network element; secondly, after receiving the intent execution request message sent by the intent translation network element, the intent translation network element can send an intent operation query message to the knowledge management network element according to the intent expression and / or operation identifier (identifier of the first operation and / or the second operation) in the intent execution request message. The knowledge management network element performs a query in the intent knowledge base according to the operation query message and sends an intent operation feedback message to the intent execution network element, carrying the second indication information in the intent operation feedback message.

[0282] In other words, the intent execution network element receives the second instruction information from the intent knowledge base. This second instruction information can be received from the intent knowledge base by other network elements through a query and then forwarded to the intent execution network element. Alternatively, the second instruction information can be received from the intent knowledge base by the intent execution network element itself through a query.

[0283] It should be understood that the above describes how the intent execution network element receives the second instruction information from the intent knowledge base. In S406, the way the intent execution network element receives the fallback scheme information from the intent knowledge base can be similar to the description of receiving the second instruction information. For the sake of simplicity, it will not be described again here.

[0284] Therefore, in this application, if an abnormality occurs in the execution of a certain operation of the first intent, other operations of the first intent that have already been executed can be rolled back, avoiding the waste of resources and signaling caused by other operations of the first intent being in continuous execution, thereby improving the execution efficiency of the intent.

[0285] Figure 5 A schematic flowchart illustrating yet another example of the intent execution method 500 provided in this application is shown.

[0286] Optionally, in S501, the intent-consuming network element sends an intent implementation request message to the intent-managing network element.

[0287] The intent enforcement request message is used to request the execution of a first intent, which may include the intent expression of the first intent.

[0288] Optionally, the intent implementation request message may also include progress notification information (progressNotify). For a description of the progress notification information, please refer to the description of the progress notification information in method 400. For the sake of simplicity, it will not be repeated here.

[0289] Optionally, in S502, the intent management network element sends an intent implementation request response message to the intent consumption network element in response to the intent implementation request message.

[0290] The intent implementation request-response message may include the identifier of the first intent (intentID) and the intent expression of the first intent.

[0291] For example, after receiving the intent implementation request message corresponding to the first intent, the intent management network element assigns an identifier to the first intent and sends the identifier in the intent implementation request response message to the intent consumption network element.

[0292] Optionally, in S503, the intent management network element sends an intent translation request message to the intent translation network element.

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

[0294] The intent translation request message may include an identifier of the first intent and an intent expression. If the intent implementation request message includes progress indication information, then the intent translation message also includes the progress indication information.

[0295] S504, the intent translation network element sends an intent knowledge query message to the intent knowledge base.

[0296] The intent knowledge query message may include the identifier of the first intent and the intent expression, as well as the query type.

[0297] The query type can indicate the parameters that need to be retrieved. For example, if the query type is all parameters (type=all), then the knowledge management network element needs to return all parameters related to the first intent.

[0298] Optionally, S505, retrieve query results from the intent knowledge base.

[0299] The intent knowledge base retrieves query results based on the intent query message.

[0300] The intent knowledge base can be understood as a sub-module of the knowledge management network element. During the initialization and update process of the intent knowledge base, relevant information of the first intent, such as the second instruction information and rollback solution list, is stored in the intent knowledge base. The knowledge management network element can then query the intent knowledge base based on intent knowledge query messages. For example, the second instruction information may include exception indication information.

[0301] For example, if the query type is to query the operation of the first intent, the intent knowledge base retrieves the intent operation list (intentOperationList) for the first intent. This intent operation list includes a description of the first operation and a description of the second operation. It should be understood that if the first intent has other operations, the intent operation list also includes descriptions of those other operations.

[0302] Taking the description of the first operation as an example, the description information of the first operation may include one or more of the following: the operation instruction of the first operation, the operation execution object of the first operation (entityIDList), the second indication information of the first operation, and the rollback solution list. The operation instruction describes the specific command to execute the first operation, the operation execution object describes the first network element that needs to execute the first operation, and the descriptions of the second indication information and the rollback solution list can be found in the corresponding descriptions in method 400; for simplicity, they will not be repeated here.

[0303] It should be understood that the description information of other operations can be similar to that of the first operation, and for the sake of simplicity, it will not be repeated here.

[0304] The list of intended operations may also include execution condition information, which describes the conditions that need to be met to execute the first and second operations. For example, the first and / or second operations may be executed when the network load is idle or low.

[0305] The list of intent actions may also include dependent event information, which describes the potential impact of executing the first intent on the system.

[0306] If the query type is to query all parameters, in addition to obtaining the intent operation list of the first intent, the intent knowledge base may also include an intent goal fulfillment criterion in the intent knowledge feedback message. The intent goal fulfillment criterion can be used to indicate the conditions for achieving the first intent. For example, the intent goal fulfillment criterion may include an intent goal calculation formula to measure whether the intent goal has been achieved.

[0307] The above is merely an illustrative example of the search results, and this application does not impose any specific limitations on it.

[0308] S506, the intent translation network element receives intent knowledge feedback messages from the intent knowledge base.

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

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

[0311] S507, the intent translation network element sends a second instruction message to the intent execution network element.

[0312] The second instruction is used to instruct the network element in the schematic diagram to determine whether an abnormality has occurred in the execution of the first operation.

[0313] For example, the intent translation network element sends an intent execution request message to the intent execution network element, and the intent execution request message includes the second instruction information.

[0314] The intent translation request message may also include an identifier of the first intent, as well as a list of intent operations and intent goal achievement criteria obtained by the intent translation network element from the intent knowledge feedback message.

[0315] Optionally, if the network element intending to perform needs to provide feedback on the progress of the first and second operations, the set of intended operations may also include progress indication information.

[0316] After receiving the intent execution request message, the intent execution network element can determine the first and second operations to be executed according to a predetermined decision algorithm.

[0317] S508, intends to execute the first operation sent by the network element to the first network element.

[0318] For example, the network element intends to send an operation execution request message corresponding to the first operation to the first network element. The operation execution request message includes information corresponding to the first operation, wherein the information corresponding to the first operation may include the operation identifier (operationID) and operation instruction (instruction) of the first operation.

[0319] The first network element can execute the first operation based on the information corresponding to the first operation.

[0320] S509, intending to execute a second operation by sending a second operation from a network element to a second network element.

[0321] For example, the network element intends to send an operation execution request message corresponding to the second operation to the second network element. The operation execution request message includes information corresponding to the second operation, wherein the information corresponding to the second operation may include the operation identifier (operationID) and operation instruction (instruction) of the second operation.

[0322] The second network element can execute the second operation based on the information corresponding to the second operation.

[0323] S510, the network element intending to execute receives the execution result information of the first operation of the first intention from the first network element.

[0324] The execution result information is used to determine whether an anomaly occurred during the execution of the first operation.

[0325] For example, the network element intends to receive an operation execution response message from the first network element in response to the operation execution request message. The operation execution response message includes the execution result information of the first operation, and may also include the operation identifier of the first operation.

[0326] For example, the second instruction information is also used to instruct the schematic execution network element to determine whether an abnormality has occurred in the execution of the first operation. This determination action indicates that the schematic execution network element needs to query the execution result information of the first operation from the first network element. In this case, the intention execution network element can send an operation execution status query message to the first network element. This operation execution status query message is used to request the query of the execution result information. The execution result information received by the intention execution network element is carried in the operation execution status query response message that responds to the operation execution status query message.

[0327] S511, the intent execution network element determines whether the execution of the first operation has encountered an anomaly based on the second instruction information and the execution result information.

[0328] For a description of whether an anomaly occurred during the execution of the first operation by the network element intending to perform the operation, please refer to the description in method 400. For the sake of simplicity, it will not be repeated here.

[0329] It should be understood that the intent execution network element can also receive the execution result information of the second operation from the second network element. The intent execution request message can also include the second instruction information of the second operation. The intent execution network element can also determine whether an abnormality has occurred in the execution of the second operation based on the second instruction information and the execution result information of the second operation. The implementation method is similar to that described above for the first operation, and will not be repeated here for simplicity.

[0330] It should be noted that this application does not impose any limitation on the number of operations corresponding to the first intent. In this embodiment, no limitation is imposed on the execution order of the first operation and the second operation. The following example illustrates that when the intent execution network element determines that the execution of the first operation has encountered an anomaly, the second operation is an operation that has been successfully executed or is being executed.

[0331] In one possible implementation, if the intention execution request message includes expected processing type indication information, the expected processing type indication information is used to indicate whether the schematic execution network element needs to query the intention consumption network element whether the second operation needs to be rolled back when it determines that the execution of the first operation has encountered an abnormality. If the processing type indication information indicates that the intention consumption network element needs to be queried whether the second operation needs to be rolled back, then steps S512 to S513 are executed.

[0332] S512, when the intent execution network element determines that an abnormality has occurred in the execution of the first operation, the intent execution network element sends an intent operation rollback request message to the intent management network element.

[0333] The intention operation rollback request message is used to indicate whether the second network element needs to roll back the second operation.

[0334] The description of the intention operation rollback request message is similar to that in method 400, and will not be repeated here for the sake of simplicity.

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

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

[0337] S514, the intention is for the network element to send a backoff instruction message to the second network element.

[0338] When the network element executing the intent determines that an abnormality has occurred in the execution of the first operation, or when the intent operation rollback response message is used to indicate that the second operation needs to be rolled back, the network element executing the intent sends rollback instruction information to the second network element.

[0339] This rollback instruction information is used to indicate the second operation that reverses the first intention.

[0340] The description of the rollback instruction information is similar to that in Method 400, and will not be repeated here for the sake of simplicity.

[0341] S515, the second network element performs a second rollback operation based on the rollback instruction information.

[0342] The description of the second network element's rollback of the second operation is similar to that in method 400, and will not be repeated here for the sake of simplicity.

[0343] If the intention to execute request message also includes progress indication information, the method further includes step S516.

[0344] S516, the intent execution network element sends an operation execution progress notification message to the intent management network element.

[0345] The progress notification message for this operation may include an identifier of the first intent and progress information. For a description of the progress information, please refer to the relevant description in method 400. For the sake of simplicity, it will not be repeated here.

[0346] Optionally, if the progress indication information is also used to indicate the period or frequency at which the intention execution network element needs to provide progress information, the intention execution network element can monitor the progress of the operation execution according to the period or frequency, and send the operation execution progress notification message to the intention management network element according to the period or frequency.

[0347] If the intending consumer network element needs to obtain this progress information, the intending management network element can forward the operation execution progress notification message to the intending consumer network element.

[0348] Therefore, in this application, if an abnormality occurs in the execution of a certain operation of the first intention, other operations of the first intention that have already been executed can be rolled back, avoiding unnecessary execution of other operations of the first intention and causing unnecessary impact on the system.

[0349] exist Figure 3 and Figure 5 In the described embodiments, the intent translation network element sends an intent knowledge query message to the intent knowledge base to query relevant information about the intent, and carries the relevant information about the intent in the intent execution request message sent to the intent execution network element. In this embodiment, the intent execution request message may also only carry the information needed in the intent decision-making process. If the intent execution network element needs to perform other processes, such as determining whether the operation was successfully executed, determining whether an abnormality occurred in the operation, and determining the order of executing multiple operations, the intent execution network element may query the knowledge management module as needed.

[0350] Figure 6 An example schematic flowchart of a method 600 for performing network element query information is shown.

[0351] S601, the intent execution network element sends an intent operation query message to the intent knowledge base.

[0352] This intent operation query message is used to query the first intent, or the first operation of the first intent.

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

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

[0355] As an example rather than a limitation, Table 1 illustrates a mapping relationship between query type, query input information, and query output information.

[0356] Table 1:

[0357]

[0358] Optionally, S602, retrieve query results from the intent knowledge base.

[0359] For example, the intent knowledge base retrieves the corresponding query results based on the query type and query input information in the intent operation query message.

[0360] S603, the intent knowledge base sends an intent operation feedback message to the intent execution network element in response to the intent operation query message.

[0361] The intention operation feedback message includes the identifier of the first operation and the query results obtained from the query.

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

[0363] Figure 7 and Figure 8The diagram illustrates the possible structures of communication devices provided in the embodiments of this application. These communication devices can be used to implement the functions of the intent execution network element, intent knowledge base, first network element, and second network element in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device can be the intent execution network element, intent knowledge base, first network element, and second network element, or it can be a module (such as a chip) applied to the intent execution network element, intent knowledge base, first network element, and second network element.

[0364] like Figure 7 As shown, the communication device 700 includes a processing unit 710 and a transceiver unit 720. The communication device 700 is used to implement the above-mentioned... Figure 2 The method embodiment shown is intended to perform the functions of a network element, an intent knowledge base, a first network element, and a second network element. Alternatively, the communication device 700 may include components for implementing the above. Figure 2 The module shown in the method embodiment is intended to perform any function or operation of the network element, the intent knowledge base, the first network element, and the second network element. This module can be implemented in whole or in part by software, hardware, firmware, or any combination thereof.

[0365] When the communication device 700 is used to implement Figure 2 In the method embodiment shown, when intending to execute the function of a network element, the transceiver unit 720 is used to receive execution order information from the intent knowledge base. The execution order information is used to indicate the order of the first operation and the second operation of the first intent. The processing unit 710 is used to determine the sending order of the intent execution network element sending the first operation to the first network element and the intent execution network element sending the second operation to the second network element according to the execution order information. The transceiver unit 910 is also used to send the first operation to the first network element and the second operation to the second network element according to the sending order.

[0366] Therefore, in this application, the intent execution network element can determine the sending order of multiple operations based on the order of execution of multiple operations, so that multiple operations can be executed in sequence and can cooperate with each other, avoiding the failure of intent operation execution or failure to achieve the expected effect due to non-sequential execution, thereby improving the reliability of the system's intent execution.

[0367] Optionally, when the communication device 700 is used to implement Figure 2 In the method embodiment shown, when intending to perform the function of a network element, the transceiver unit 720 is also used to receive the execution result information of the first operation from the first network element; the processing unit 710 is also used to determine whether the first operation was successfully executed based on the execution result information.

[0368] Therefore, in this application, the intent execution network element can receive the execution result information of the operation and determine whether the operation was successfully executed based on the execution result information, thereby enabling the monitoring of the execution status of the operation and improving the reliability of the system's execution intent.

[0369] Optionally, when the communication device 700 is used to implement Figure 2 In the method embodiment shown, when intending to execute the function of a network element, the transceiver unit 720 is also used to receive first instruction information from the intent knowledge base. The first instruction information is used to instruct the network element to determine whether the first operation has been successfully executed.

[0370] Therefore, in this application, the intent execution network element can obtain first instruction information from the intent knowledge base, and determine whether the operation was successfully executed based on the first instruction information, thereby improving the reliability of the system's intent execution.

[0371] Optionally, when the communication device 700 is used to implement Figure 2 In the method embodiment shown, when the intention is to perform the function of a network element, the transceiver unit 720 is specifically used to send a first operation to the first network element, and if the first operation is successfully executed, to send a second operation to the second network element.

[0372] Therefore, in this application, the network element intending to execute can issue subsequent operations only after confirming that the preceding operations have been successfully executed, thus avoiding the failure of subsequent operations or poor execution results due to the preceding operations not being successfully executed.

[0373] Optionally, when the communication device 700 is used to implement Figure 2 In the method embodiment shown, when the device intends to perform the function of the network element, the transceiver unit 720 is also used to receive progress indication information. The progress indication information is used to indicate that the device needs to provide progress information, and the progress information is used to indicate the execution progress of the first operation and the second operation.

[0374] Therefore, in this application, the network element intended to perform the operation can be required to provide feedback on the execution progress, thereby enabling monitoring of the operation's execution status and improving the reliability of the system's execution intent.

[0375] When the communication device 700 is used to implement Figure 2 When the intent knowledge base is functioning in the method embodiment shown, the transceiver unit 720 is used to send execution order information to the intent execution network element. The execution order information is used to indicate the order of the first operation and the second operation of the first intent.

[0376] Therefore, in this application, the intent execution network element can determine the sending order of multiple operations based on the order of execution of multiple operations, so that multiple operations can be executed in sequence and can cooperate with each other, avoiding the failure of intent operation execution or failure to achieve the expected effect due to non-sequential execution, thereby improving the reliability of the system's intent execution.

[0377] Optionally, when the communication device 700 is used to implement Figure 2 When the intent knowledge base is used in the method embodiment shown, the transceiver unit 720 is also used to send a first indication information to the intent execution network element. The first indication information is used to determine whether the first operation was successfully executed.

[0378] When the communication device 700 is used to implement Figure 2 In the method embodiment shown, when the first network element is functioning, the transceiver unit 720 is used to receive the first operation; the processing unit 710 is used to execute the first operation.

[0379] Optionally, when the communication device 700 is used to implement Figure 2 In the method embodiment shown, when the first network element is functioning, the transceiver unit 720 is also used to send the execution result information of the first operation, which is used to determine whether the first operation was successfully executed.

[0380] When the communication device 700 is used to implement Figure 2 In the method embodiment shown, when the second network element is functioning, the transceiver unit 910 is used to receive the second operation; the processing unit 710 is used to execute the second operation.

[0381] For a more detailed description of the processing unit 710 and the transceiver unit 720, please refer to [link / reference needed]. Figure 2 The relevant descriptions in the method embodiments shown are directly obtained and will not be repeated here.

[0382] like Figure 7 As shown, the communication device 700 includes a processing unit 710 and a transceiver unit 720. The communication device 700 is used to implement the above-mentioned... Figure 2 The method embodiment shown is intended to perform the functions of a network element, an intent knowledge base, a first network element, and a second network element. Alternatively, the communication device 700 may include components for implementing the above. Figure 4 The module shown in the method embodiment is intended to perform any function or operation of the network element, the intent knowledge base, the first network element, and the second network element. This module can be implemented in whole or in part by software, hardware, firmware, or any combination thereof.

[0383] When the communication device 700 is used to implement Figure 4In the method embodiment shown, when intending to execute the function of a network element, the transceiver unit 720 is used to receive the execution result information of the first operation of the first intention from the first network element; the processing unit 710 is used to determine that the execution of the first operation has encountered an abnormality based on the execution result information; the transceiver unit 720 is also used to send rollback indication information to the second network element, the rollback indication information being used to indicate the rollback of the second operation of the first intention.

[0384] Therefore, in this application, if an abnormality occurs in the execution of a certain operation of the first intent, other operations of the first intent that have already been executed can be rolled back, avoiding the waste of resources and signaling caused by other operations of the first intent being in continuous execution, thereby improving the execution efficiency of the intent.

[0385] Optionally, when the communication device 700 is used to implement Figure 4 In the method embodiment shown, when intending to perform the function of a network element, the transceiver unit 720 is also used to receive second indication information from the intent knowledge base. The second indication information is used to indicate that the network element in the schematic diagram has determined that the execution of the first operation has encountered an abnormality.

[0386] Optionally, when the communication device 700 is used to implement Figure 4 When the method embodiment shown intends to perform the function of the network element, the processing unit 710 is also used to determine the rollback method of the second operation based on the execution result information and the rollback scheme information.

[0387] Therefore, in this application, the network element intending to execute the operation can instruct the network element performing the operation on the rollback method, thereby avoiding the failure of network elements without rollback capability to successfully roll back the operation and improving the reliability of the system's execution intent.

[0388] Optionally, when the communication device 700 is used to implement Figure 4 In the method embodiment shown, when the intention is to perform the function of a network element, the transceiver unit 720 is specifically used to send a first operation to the first network element, and if the first operation is successfully executed, to send a second operation to the second network element.

[0389] Therefore, in this application, if an error occurs during the execution of a certain operation of the first intent, other operations of the first intent that have already been executed can be rolled back, avoiding the waste of resources and signaling caused by other operations of the first intent being in continuous execution, thereby improving the execution efficiency of the intent. Optionally, when the communication device 700 is used to implement... Figure 4 In the method embodiment shown, when the intention is to perform the function of the network element, the transceiver unit 720 is also used to receive progress indication information. The progress indication information is used to indicate that the device needs to provide progress information. The progress information is used to indicate the execution progress of the first operation and the second operation. It is also used to send progress information according to the progress indication information.

[0390] Therefore, in this application, the network element intended to perform the operation can be required to provide feedback on the execution progress, thereby enabling monitoring of the operation's execution status and improving the reliability of the system's execution intent.

[0391] When the communication device 700 is used to implement Figure 4 When the intent knowledge base is functioning in the method embodiment shown, the transceiver unit 720 is used to send second indication information to the intent execution network element. The second indication information is used to indicate whether an abnormality has occurred in the execution of the first operation.

[0392] Therefore, in this application, if an abnormality occurs in the execution of a certain operation of the first intention, other operations of the first intention that have already been executed can be rolled back, avoiding unnecessary execution of other operations of the first intention and causing unnecessary impact on the system, thereby improving the reliability of the system's execution intention.

[0393] Optionally, when the communication device 700 is used to implement Figure 4 In the method embodiment shown, when the intent knowledge base is functioning, the transceiver unit 720 is also used to send rollback scheme information to the intent execution network element. The rollback scheme information is used to determine the rollback method of the second operation.

[0394] When the communication device 700 is used to implement Figure 4 When the first network element functions as shown in the method embodiment, the transceiver unit 720 is used to send the execution result information of the first operation of the first intent.

[0395] When the communication device 700 is used to implement Figure 4 In the method embodiment shown, when the second network element functions, the transceiver unit 720 is used to receive rollback indication information, which is used to indicate the second operation of rolling back the first intention; the processing unit 710 is used to roll back the second operation.

[0396] For a more detailed description of the processing unit 710 and the transceiver unit 720, please refer to [link / reference needed]. Figure 3 The relevant descriptions in the method embodiments shown are directly obtained and will not be repeated here.

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

[0398] When the communication device 800 is used to implement Figure 2 or Figure 4In the method shown, 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.

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

[0400] When the communication device 800 is used to implement Figure 2 or Figure 4 In the method shown, 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.

[0401] When the aforementioned communication device is a chip applied to an intent execution network element, the intent execution network element chip implements the functions of the intent execution network element in the above method embodiments. The intent execution network element chip receives information from other modules (such as radio frequency modules or antennas) within the intent execution network element; this information is sent to the intent execution network element from the intent knowledge base. Alternatively, the intent execution network element chip sends information to other modules (such as radio frequency modules or antennas) within the intent execution network element; this information is sent by the intent execution network element to the first network element or the second network element.

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

[0403] It is understood that the processor in the embodiments of this application may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0404] In embodiments of this application, the memory may be random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and storage medium may reside in an ASIC. Additionally, the ASIC may reside in a network device or a terminal device. Alternatively, the processor and storage medium may exist as discrete components in the network device or terminal device.

[0405] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially 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 this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a terminal device, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a DVD; or it can be a semiconductor medium, such as a solid-state disk (SSD).

[0406] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0407] It should be understood that in the embodiments of this application, the designations "first", "second", etc. are only for distinguishing different objects, such as different network devices, and do not constitute a limitation on the scope of the embodiments of this application. The embodiments of this application are not limited thereto.

[0408] It should also be understood that in this application, “when…”, “if” and “if” all refer to the network element making a corresponding processing under certain objective circumstances, and are not time-limited, nor do they require the network element to make a judgment when it is implemented, nor do they mean that there are other limitations.

[0409] It should also be understood that in the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0410] It should also be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0411] In this application, expressions such as "the item includes one or more of the following: A, B, and C" generally mean, unless otherwise specified, that the item can be any one of the following: A; B; C; A and B; A and C; B and C; A, B and C; A and A; A, A and A; A, A and B; A, A and C, A, B and B; A, C and C; B and B, B, B and B, B, B and C, C and C; C, C and C, and other combinations of A, B, and C. The above example uses three elements, A, B, and C, to illustrate the possible entries for the item. When expressed as "the item includes at least one of the following: A, B, ..., and X," that is, when the expression contains more elements, then the applicable entries for the item can also be obtained according to the aforementioned rules.

[0412] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A method for executing an intent, characterized in that, The method includes: The intent execution network element receives execution order information from the intent knowledge base, the execution order information being used to indicate the order of the first operation and the second operation of the first intent; The intent execution network element determines the sending order of sending the first operation to the first network element and the second operation to the second network element based on the execution order information; The intent-executing network element sends the first operation to the first network element and the second operation to the second network element according to the sending order.

2. The method as described in claim 1, characterized in that, The method further includes: The intent execution network element receives the execution result information of the first operation from the first network element; The intent execution network element determines whether the first operation was successfully executed based on the execution result information.

3. The method as described in claim 2, characterized in that, The method further includes: The intent execution network element receives first instruction information from the intent knowledge base. The first instruction information is used to instruct the intent execution network element to determine whether the first operation was successfully executed.

4. The method according to any one of claims 1 to 3, characterized in that, The intent-executing network element sends the first operation to the first network element and the second operation to the second network element according to the sending order, including: The intent execution network element sends the first operation to the first network element, and if the intent execution network element determines that the first operation was successfully executed, the intent execution network element sends the second operation to the second network element.

5. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The intent execution network element receives progress indication information, which is used to indicate that the intent execution network element needs to provide progress information, and the progress information is used to indicate the execution progress of the first operation and the second operation; The intent execution network element sends the progress information according to the progress indication information.

6. The method as described in claim 5, characterized in that, The progress indication information is also used to indicate the period or frequency at which the intention execution network element needs to provide the progress information.

7. An apparatus for performing an intention, characterized in that, The device includes a transceiver unit and a processing unit. The transceiver unit is configured to receive execution order information from an intent knowledge base, 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 executed; The processing unit is configured to determine, based on the execution order information, the order in which the intent execution device sends the first operation to the first network element and the order in which the intent execution device sends the second operation to the second network element; The transceiver unit is further configured to send the first operation to the first network element and the second operation to the second network element according to the transmission order.

8. The apparatus as claimed in claim 7, characterized in that, The transceiver unit is further configured to receive the execution result information of the first operation from the first network element; The processing unit is further configured to determine whether the first operation was successfully executed based on the execution result information.

9. The apparatus as claimed in claim 8, characterized in that, The transceiver unit is further configured to receive first instruction information from the intent knowledge base, the first instruction information being used to instruct the intent execution device to determine whether the first operation was successfully executed.

10. The apparatus according to any one of claims 7 to 9, characterized in that, The transceiver unit is specifically used to send the first operation to the first network element, and, if the first operation is successfully executed, to send the second operation to the second network element.

11. The apparatus as claimed in any one of claims 7 to 9, characterized in that, The transceiver unit is also configured to receive progress indication information, which indicates that the device needs to provide progress information and indicates the execution progress of the first operation and the second operation. The processing unit is also configured to send the progress information according to the progress indication information.

12. The apparatus as claimed in claim 11, characterized in that, The progress indication information is also used to indicate the period or frequency at which the device needs to provide progress information feedback.

13. A communication device, characterized in that, The device includes at least one processor for executing a computer program stored in a memory, such that the device implements the method as described in any one of claims 1 to 6.

14. A computer-readable storage medium, characterized in that, Includes a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1 to 6.

Images