Intent processing method, apparatus and device

Abstract

This application discloses an intent processing method, an apparatus, and a device for ensuring the performance of a network to which a device executing an intent belongs. The method includes: after sending first information indicating an impact on at least one KPI when a solution to a first intent is executed to a second device, the first device receives information from the second device indicating an execution suggestion for the first intent. In this way, the second device may determine an execution suggestion for the first intent based on the impact on at least one KPI when a solution to the first intent is executed. This avoids a case where, when a solution to the first intent is executed, the at least one KPI does not satisfy the second device's requirement for at least one KPI in the network to which the device executing the first intent belongs, and thus can ensure the performance of the network to which the device executing the first intent belongs.

Description

[Technical Field]

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims priority to Chinese Patent Application No. 202111433699.7, entitled "INTENT PROCESSING METHOD, APPARATUS, AND DEVICE," filed with the State Intellectual Property Office of the People's Republic of China on November 29, 2021, the entire contents of which are incorporated by reference.

[0002] [Technical field] This application relates to the field of communication technology, and in particular to an intent processing method, apparatus and device. [Background technology]

[0003] Intent-Driven Management Services (IDMS) have been introduced into mobile communication systems (e.g., 5th generation (5G) communication systems) to reduce the complexity of managing cyberinfrastructure and improve the efficiency of operation and maintenance.

[0004] In an intent-driven management service, an intent consumer may send an intent expression for an intent to an intent producer, instructing the intent producer to generate a solution that can satisfy the intent. The intent producer then selects a solution to be used to satisfy the intent (i.e., a solution to be executed) from the generated solutions. An intent may be expressed by using an intent expression. An intent expression includes only a goal, not how to achieve the goal. In this way, intent producers of different device vendors may generate solutions to achieve a goal (in other words, generate solutions that satisfy the intent) to improve operation and maintenance efficiency.

[0005] Currently, when determining the solution to be used to satisfy an intent, the intent producer only considers whether the intent has syntax / behavior conflicts with other intents. When the selected solution is executed, the performance of the network to which the device executing the solution belongs (e.g., an access network (AN) device or a core network (CN) device) may be affected. Summary of the Invention

[0006] This application provides an intent processing method, apparatus and device for ensuring the performance of a network to which a device executing the intent belongs.

[0007] According to a first aspect, an embodiment of the present application provides an intent processing method, the method including:

[0008] After transmitting the first information to the second device, the first device may receive information from the second device indicating an implementation suggestion for the first intent. The first information may indicate an impact on at least one KPI when a solution to the first intent is implemented.

[0009] Optionally, the solution to the first intent is at least one solution that can satisfy the first intent.

[0010] Optionally, the implementation suggestion includes stopping implementing the first intent or implementing a first solution for the first intent.

[0011] According to the method, after receiving the first information, the second device may determine an execution suggestion for the first intent based on an effect on at least one KPI when the solution to the first intent is executed, which avoids a case where the at least one KPI does not satisfy the second device's requirement for the at least one KPI in the network to which the device executing the first intent belongs when the solution to the first intent is executed, and thus can ensure the performance of the network to which the device executing the first intent belongs.

[0012] In a possible design, before transmitting the first information to the second device, the first device may receive information from the second device indicative of at least one KPI.

[0013] Optionally, the information indicative of at least one KPI includes: At least one KPI, and an identifier and / or intent expression of a second intent indicating at least one KPI; Contains at least one of the following:

[0014] According to this design, the first device only needs to feed back to the second device the impact of implementing the solution to the first intent on at least one KPI indicated by the information indicating the at least one KPI, and does not need to feed back the impact of implementing the solution to the first intent on all KPIs, thereby saving transmission resources.

[0015] In a possible design, the at least one KPI includes at least one of the following: throughput, throughput volume, energy consumption, bandwidth utilization, delay, and packet loss rate.

[0016] In a possible design, the first piece of information is: Information indicative of the value of at least one KPI when the solution to the first intent is executed; and / or Information indicating an offset of at least one KPI when the solution to the first intent is executed, and information indicating a current value of the at least one KPI. Includes:

[0017] According to this design, the first device may flexibly indicate the value of the at least one KPI when the solution to the first intent is executed.

[0018] In a possible design, before transmitting the first information to the second device, the first device may receive second information from the third device, and the second information may indicate at least one of the following: an offset of the at least one KPI when a solution to the first intent is performed; and an offset of the at least one KPI when at least one action in the solution to the first intent is performed.

[0019] According to this design, the first device may obtain information used to determine an offset of the at least one KPI when the resolution of the first intent is performed to determine a value of the at least one KPI when the resolution of the first intent is performed.

[0020] According to a second aspect, an embodiment of the present application provides an intent processing method, the method including:

[0021] After receiving the first information from the first device, the second device transmits information indicating an execution suggestion for the first intent to the first device, and the first information may indicate an impact on at least one KPI when a solution to the first intent is executed.

[0022] Optionally, the solution to the first intent is at least one solution that can satisfy the first intent.

[0023] Optionally, the implementation suggestion includes stopping implementing the first intent or implementing a first solution for the first intent.

[0024] According to the method, after receiving the first information, the second device may determine an execution suggestion for the first intent based on an effect on at least one KPI when the solution to the first intent is executed, which avoids a case where the at least one KPI does not satisfy the second device's requirement for the at least one KPI in the network to which the device executing the first intent belongs when the solution to the first intent is executed, and thus can ensure the performance of the network to which the device executing the first intent belongs.

[0025] In a possible design, before receiving the first information from the first device, the second device may transmit information indicative of at least one KPI to the first device.

[0026] Optionally, the information indicative of at least one KPI includes: At least one KPI, and an identifier and / or intent expression of a second intent indicating at least one KPI; Contains at least one of the following:

[0027] According to this design, the second device transmits information indicating at least one KPI to the first device. In this way, the first device only needs to feed back to the second device the impact of implementing the solution to the first intent on the at least one KPI indicated by the information indicating the at least one KPI, rather than the impact of implementing the solution to the first intent on all KPIs, thereby saving transmission resources.

[0028] In a possible design, the at least one KPI includes at least one of the following: throughput, throughput amount, energy consumption, and bandwidth utilization.

[0029] In a possible design, the first piece of information is: Information indicative of the value of at least one KPI when the solution to the first intent is executed; and / or Information indicating an offset of at least one KPI when the solution to the first intent is executed, and information indicating a current value of the at least one KPI. Includes:

[0030] According to this design, the second device may flexibly obtain the value of the at least one KPI when the resolution of the first intent is executed.

[0031] According to a third aspect, an embodiment of the present application provides an intent processing method, the method including:

[0032] After the first device transmits the first information to the second device, the second device transmits information indicating an execution suggestion for the first intent to the first device, wherein the first information indicates an effect on at least one KPI when a solution to the first intent is executed.

[0033] According to the method, after receiving the first information, the second device may determine an execution suggestion for the first intent based on an effect on at least one KPI when the solution to the first intent is executed, which avoids a case where the at least one KPI does not satisfy the second device's requirement for the at least one KPI in the network to which the device executing the first intent belongs when the solution to the first intent is executed, and thus can ensure the performance of the network to which the device executing the first intent belongs.

[0034] In a possible design, before the first device transmits the first information to the second device, the second device may transmit information indicative of at least one KPI to the first device.

[0035] According to this design, the first device only needs to feed back to the second device the impact of implementing the solution to the first intent on at least one KPI indicated by the information indicating the at least one KPI, and does not need to feed back the impact of implementing the solution to the first intent on all KPIs, thereby saving transmission resources.

[0036] According to a fourth aspect, an embodiment of the present application provides an intent processing apparatus including a unit configured to perform the steps in any one of the above aspects.

[0037] According to a fifth aspect, an embodiment of the present application provides an intent processing device including at least one processing element and at least one storage element, wherein the at least one storage element is configured to store programs and data, and the at least one processing element is configured to read and execute the programs and data stored in the storage element, thereby realizing a method provided in any one of the above aspects of the present application.

[0038] According to a sixth aspect, an embodiment of the present application provides an intent processing system including a first device configured to perform a method provided in the first aspect, and a second device configured to perform a method provided in the second aspect.

[0039] According to a seventh aspect, an embodiment of the present application further provides a computer program, which when run on a computer enables the computer to perform the method provided in any one of the above aspects.

[0040] According to an eighth aspect, an embodiment of the present application further provides a computer-readable storage medium, which stores a computer program, which, when executed by a computer, enables the computer to perform the method provided in any one of the above aspects.

[0041] According to a ninth aspect, an embodiment of the present application further provides a chip, wherein the chip is configured to read a computer program stored in a memory to perform the method provided in any one of the above aspects.

[0042] According to a tenth aspect, an embodiment of the present application further provides a chip system. The chip system includes a processor configured to support a computer device in implementing a method provided in any one of the above aspects. In a possible design, the chip system further includes a memory configured to store programs and data required by the computer device. The chip system may include a chip, or may include a chip and other discrete components.

[0043] For the technical effects that can be achieved in any one of the fourth to tenth aspects, please refer to the description of the technical effects that can be achieved in any one of the possible designs of the first to third aspects. The repeated parts will not be described again here. [Brief explanation of the drawings]

[0044] [Figure 1] 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present application; [Figure 2] FIG. 2 is a schematic diagram of the architecture of another communication system according to an embodiment of the present application; [Figure 3] 2 is a flowchart of a first intent processing method according to an embodiment of the present application. [Figure 4]4 is a flowchart of a second intent processing method according to an embodiment of the present application. [Figure 5] 10 is a flowchart of a third intent processing method according to an embodiment of the present application. [Figure 6] 10 is a flowchart of a fourth intent processing method according to an embodiment of the present application. [Figure 7] 10 is a flowchart of a fifth intent processing method according to an embodiment of the present application. [Figure 8] 10 is a flowchart of a sixth intent processing method according to an embodiment of the present application. [Figure 9] FIG. 1 is a schematic diagram of the structure of an intent processing device according to an embodiment of the present application; [Figure 10] 1 is a schematic diagram of the structure of an intent processing device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0045] This application provides an intent processing method, an apparatus, and a device for ensuring the performance of a device that executes an intent solution. The method, the apparatus, and the device are based on the same technical idea. Since the method, the apparatus, and the device have similar principles for solving problems, the implementation manners of the apparatus, the device, and the method will refer to each other, and the repeated parts will not be described.

[0046] According to a solution provided in an embodiment of this application, after transmitting first information indicating an impact on at least one key performance indicator (KPI) when a solution to a first intent is executed to a second device, the first device receives information from the second device indicating an execution suggestion for the first intent. In this manner, the second device may determine an execution suggestion for the first intent based on an impact on the at least one KPI when a solution to the first intent is executed. This avoids a case where, when a solution to the first intent is executed, the at least one KPI does not satisfy the second device's requirement for the at least one KPI in the network to which the device executing the first intent belongs, thereby ensuring the performance of the network to which the device executing the first intent belongs.

[0047] In the following, some terms in the embodiments of this application will be explained to facilitate understanding by those skilled in the art.

[0048] (1) Intents are expectations about the system in which the intent producer is located and may include requirements, goals, and limitations (i.e., constraints).

[0049] An intent expression is an expression that conveys an intent. Therefore, an intent may be expressed by an intent expression. An intent expression may include an action and an object (also called an operation object). An action is an abstracted and simplified network operation based on an intent and may include an intent-driven action (IDA) name and a set of associated properties (e.g., IDA properties). An object is management object information provided based on an intent and may include an intent-driven object (IDO) name and a set of properties that identify the object (e.g., IDO properties). A target value of an intent may be included in an action or an object, or an intent expression includes an action, an object, and a target value. For example, an intent is to optimize the downlink rate of a cell. The action is "optimize," the object is "cell," and the target value is a specific value for the downlink rate of the cell.

[0050] The intent expression only contains a description of the goal, and the specific realization manner of the intent is obtained by the intent producer by analyzing and translating the intent expression. The intent producer can determine which solution is used to meet the expectation. In other words, the intent producer can determine which solution is used to fulfill the intent.

[0051] (2) Intent Conflict

[0052] Two intents have an intent conflict when both intents cannot be satisfied due to mutual exclusion.

[0053] Intent conflicts may include syntax conflicts and / or behavior conflicts.

[0054] A syntax conflict means that the intent expressions of two intents have a conflict. For example, the intent expressions of two intents describe mutually exclusive goals of the same object (such as a cell or a base station) under the same validity conditions. In one example, a syntax conflict exists between two intents when the intent expression of one intent reflects a goal of increasing the downlink rate of a cell and the intent expression of the other intent reflects a goal of decreasing the downlink rate of a cell.

[0055] An action conflict refers to a conflict between two intents for a translated intent operation. In other words, the actions of the two intents cannot be performed simultaneously. For example, solutions corresponding to two intents include mutually exclusive actions on the same parameter and / or property of the same network element. In one example, an action conflict exists between Intent 1 and Intent 2 when the solution for Intent 1 requires increasing network configuration parameter A and the solution for Intent 2 requires decreasing network configuration parameter A.

[0056] (3) Intent translation is the process of determining the policy of an intent.

[0057] A policy may be a condition that indicates that an intent is not satisfied. For example, when the intent is to save energy, policy A may be that the energy consumption is abnormal (i.e., energy is not saved) when the energy consumption is greater than a first threshold, and policy B may be that the energy consumption is abnormal (i.e., energy is not saved) when the energy consumption is greater than a second threshold.

[0058] It can be understood that even for the same intent, the solutions that can satisfy the intent and are determined by using different policies may be different.

[0059] (4) A solution to an intent is at least one solution that can satisfy the intent. Each solution may include at least one action.

[0060] For example, when the intent is to save energy, the solution to the intent may include:

[0061] Solution 1: Enable energy-saving scheduling, timing carrier shutdown and intelligent carrier shutdown.

[0062] Solution 2: Enable pico remote radio unit (pRRU) deep sleep and radio frequency module deep sleep.

[0063] Solution 3: Enabling multi-RAT cooperative symbol energy saving, low energy consumption mode and radio frequency channel intelligent shutdown.

[0064] A solution to an intent may be at least one solution generated by an intent producer and capable of fulfilling the intent, or may be a solution executed by a device fulfilling the intent and used to fulfill the intent. When a device fulfilling the intent executes a solution to the intent, the network in which the device fulfilling the intent is located can fulfill the intent.

[0065] (5) KPIs are key parameters in a system.

[0066] The KPIs may include network configuration parameters, for example, the KPIs may include at least one of the following: throughput, throughput volume, energy consumption, bandwidth utilization, delay, packet loss rate, etc.

[0067] (6) An intent consumer is a device that manages intents. Specifically, an intent consumer may generate an intent and send an intent expression used to convey the intent to an intent producer. An intent may be the intent consumer's requirements for a network to which a device that performs resolution of the intent belongs. For example, an intent may reflect the intent consumer's requirements for at least one KPI in a network to which a device that performs resolution of the intent belongs.

[0068] An intent producer is a device that processes intents. Specifically, after receiving an intent expression from an intent consumer, the intent producer may generate multiple solutions that can satisfy the intent and select one of the solutions for execution. The intent producer may then send the selected solution to a device that fulfills the intent, thereby causing the device that fulfills the intent to execute the selected solution.

[0069] The Intent Consumer and / or Intent Producer may be an AN device or a CN device. For example, the Intent Consumer may be a network management service (NMS), an IDMS consumer, or a management service consumer (MnS consumer) (hereinafter referred to as an MnS consumer for short). The Intent Producer may be an element management service (EMS), an IDMS producer, or a management service producer (MnS producer) (hereinafter referred to as an MnS producer for short).

[0070] It should be understood that the Intent Consumer and Intent Producer may alternatively use other names, provided that the same functionality is provided, and this is not a limitation in this application.

[0071] (7) An AN device is a device that connects a terminal device to a wireless network in a mobile communication system. As a node in a radio access network, an AN device may also be called a base station, a radio access network (RAN) node (or device), or an access point (AP).

[0072] Currently, some examples of AN devices are a new generation NodeB (gNB), a transmission reception point (TRP), an evolved NodeB (eNB), a radio network controller (RNC), a NodeB (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., a home evolved NodeB or home NodeB (HNB)), or a baseband unit (BBU).

[0073] Furthermore, in a network structure, an AN device may include a central unit (CU) node and a distributed unit (DU) node. In this structure, the protocol layers of the AN device are divided. Some functions of the protocol layers are controlled in a centralized manner by the CU. Some or all functions of the remaining protocol layers are distributed to the DUs, and the CU controls the DUs in a centralized manner.

[0074] (8) A CN device is a network element included in the CN part in a mobile communication system. The CN device connects a terminal device to different data networks and can perform services such as charging, mobility management, session management, and user plane forwarding. In different standard mobile communication systems, the names of CN devices with the same functions may be different. However, the specific names of CN devices with each function are not limited in the embodiments of this application.

[0075] For example, in a 4th generation (4G) mobile communication system (i.e., long term evolution (LTE)), a network element responsible for functions such as access control, security control, and signaling coordination is a mobility management entity (MME), a network element acting as a local mobility management anchor is a serving gateway (S-GW), a network element acting as a handover anchor for external data networks and responsible for internet protocol (IP) address allocation is a packet data network (PDN) gateway (P-GW), a network element storing user-related data and subscription data is a home subscriber server (HSS), and a network element responsible for policy and charging functions is called a policy and charging rule function (PCRF) network element.

[0076] In another example, in a fifth-generation (5G) mobile communication system, the core network may be divided into a control plane (CP) and a user plane (UP) based on a specific logical functional division. Network elements performing control plane functions in the CN may be collectively referred to as control plane network elements, and network elements performing user plane functions may be collectively referred to as user plane network elements. Specifically, a network element that functions as an interface with a data network on the user plane and performs functions such as user plane data forwarding is a user plane function (UPF) network element. On the control plane, a network element that performs access control and mobility management functions is called an access and mobility management function (AMF) network element, a network element that performs session management and policy enforcement control is called a session management function (SMF) network element, a network element that performs functions such as subscription data management and user access permissions is called a unified data management (UDM) network element, a network element that performs charging and policy control functions is called a policy and charging function (PCF) network element, and a network element that is responsible for transmitting application side requirements for the network side is called an application function (AF) network element.

[0077] In the embodiments of this application, unless otherwise specified, the number of nouns refers to "singular or plural," i.e., "one or more." "At least one" means one or more, and "plural" means two or more. The term "and / or" describes an associative relationship for describing related objects and indicates that three relationships may exist. For example, A and / or B may represent the following three cases: only A is present, both A and B are present, and only B is present. "At least one of the following items (elements)" or similar expressions refers to any combination of these items (elements), including any combination of a singular item (element) or multiple items (elements).

[0078] Furthermore, it should be understood that in the description of this application, terms such as "first" and "second" are used merely for purposes of distinction and explanation, and should not be understood as an indication or implication of relative importance, or as an indication or implication of sequence.

[0079] A communication system to which an embodiment of the present application is applied will be described below with reference to the accompanying drawings.

[0080]

[0023] Figure 1 shows a possible architecture of a communication system to which the intent processing method provided in the embodiments of this application can be applied. As shown in Figure 1, the communication system includes four parts: an IDMS consumer, an IDMS producer, a data collection and coordination function (DCCF) producer (DCCF producer), and a knowledge management (KM) producer (KM producer). The following describes the four parts separately.

[0081] The IDMS Consumer may implement the functionality of the Intent Consumer, and the IDMS Producer may implement the functionality of the Intent Producer. For details, please refer to the glossary section. The details will not be explained again here.

[0082] A DCCF producer is a device that provides DCCF services, which may include, but are not limited to, at least one of the following: data collection services, data sorting services, data provision services, etc.

[0083] A DCCF producer may provide a DCCF service to an IDMS producer via a DCCF consumer in the IDMS producer. Specifically, when the DCCF consumer invokes a DCCF service, the DCCF producer provides the DCCF service to the IDMS producer (e.g., provides data) via the DCCF consumer.

[0084] In this application, a DCCF producer may also be referred to as a DCCF.

[0085] A KM producer is a device that provides KM services, which may include, but are not limited to, at least one of the following: storing expert experience, storing information required for intent translation, providing the stored information, etc.

[0086] A KM producer may provide a KM service to an IDMS producer via a KM consumer in the IDMS producer. Specifically, when the KM consumer invokes a KM service, the KM producer may provide the KM service to the IDMS producer via the KM consumer.

[0087] In this application, a KM producer may also be referred to as a KM module, a KM function, a KM server, or a KM.

[0088] Optionally, the KM producer and DCCF producer may be separate entities or may be located in one entity together with the IDMS producer.

[0089] Optionally, the IDMS producer further includes an intent translation (IT) module, an intent evaluation (IEv) module, an intent conflict resolution (ICR) module, and an intent decision (ID) module. The IT module, IEv module, ICR module, and ID module may be independent entities or may be virtual modules within one or more entities. Each module is described in detail below.

[0090] The IT module may be configured to perform intent translation and generate a solution that can satisfy the intent. For example, the IT module may obtain information required for intent translation from a KM function. The information may be a correspondence between intents and policies. The IT module may determine a policy for the intent based on the correspondence and the intent obtained from the IDMS consumer. The IT module may then generate at least one solution that can satisfy the intent according to the policy for the intent.

[0091] The IEv module may evaluate the implementation method of the intent.

[0092] The ICR module may handle intent conflicts, for example, the ICR module may determine whether an intent conflict exists between two intents.

[0093] The ID module may determine which solution to the intent is executed. For example, when the IT module generates at least one solution that can satisfy the intent, the ID module may randomly select a solution that does not have an intent conflict with other intents from the at least one solution for execution, or may select a solution that does not have an intent conflict with other intents for execution according to a preset policy (e.g., selecting a solution with the lowest latency or the smallest energy consumption).

[0094] 2 shows another possible architecture of a communication system to which the intent processing method provided in the embodiment of this application can be applied. As shown in FIG. 2, the communication system includes an MnS consumer and an MnS producer.

[0095] The MnS consumer may implement the functions of the IDMS consumer in Fig. 1, and the MnS producer may implement the functions of the IDMS producer and the functions of the internal modules of the IDMS producer in Fig. 1. For details, please refer to the description of Fig. 1. The details will not be described again here.

[0096] It should be noted that the communication systems illustrated in Figures 1 and 2 do not constitute limitations on communication systems to which the embodiments of this application are applicable. Therefore, the methods provided in the embodiments of this application are further applicable to various standard communication systems, such as an LTE communication system, a 5th generation (5G) communication system, a 6th generation (6G) communication system, a future communication system, vehicle to everything (V2X), Long Term Evolution-Vehicle (LTE-V), vehicle to vehicle (V2V), Internet of Vehicles, Machine Type Communication (MTC), Internet of Things (IoT), Long Term Evolution-Machine to Machine (LTE-M), machine to machine (M2M), Internet of Things, etc. It should be further noted that the names of network elements in a communication system are also not limited in the embodiments of this application. For example, in a communication system of a different standard, a network element may have a different name. In another example, when multiple network elements are integrated into the same physical device, the physical device may have a different name.

[0097] The solution provided in this application will be described below with reference to the accompanying drawings.

[0098] An embodiment of this application provides an intent processing method, which may be applied to the communication system shown in Fig. 1 or Fig. 2. The steps of the method will be described in detail below with reference to the flowchart shown in Fig. 3.

[0099] S301: A first device transmits first information to a second device, and in response, the second device receives the first information from the first device.

[0100] The first device may be an intent producer and the second device may be an intent consumer.

[0101] The first information may indicate an impact on at least one KPI when a solution to the first intent is implemented.

[0102] A solution to the first intent may be at least one solution that can satisfy the first intent.

[0103] For example, a solution to a first intent may be at least one solution generated by a first device and capable of satisfying the first intent. The first device may generate at least one solution capable of satisfying the first intent after receiving a create intent request from a second device for the first intent.

[0104] In another example, the resolution of the first intent may be the resolution of the first intent currently being executed by the first device.

[0105] Optionally, the at least one KPI comprises at least one of the following: throughput, throughput volume, energy consumption, bandwidth utilization, delay, and packet loss rate.

[0106] Optionally, the impact on the at least one KPI when the solution to the first intent is executed is a value of the at least one KPI when the solution to the first intent is executed, and the first information includes information indicating a value of the at least one KPI when the solution to the first intent is executed and / or information indicating an offset of the at least one KPI when the solution to the first intent is executed and information indicating a current value of the at least one KPI.

[0107] The offset of the at least one KPI when the solution to the first intent is executed may be a value (which may be an integer, a negative number, or 0) of the change in the at least one KPI when the solution to the first intent is executed, or may be a percentage of the change in the at least one KPI when the solution to the first intent is executed.

[0108] Optionally, the first information may be carried in an existing message or may be carried in a new message, which is not limited in this application.

[0109] S302: The second device transmits information indicating an execution suggestion for the first intent to the first device. In response, the first device receives information indicating an execution suggestion for the first intent from the second device.

[0110] The implementation suggestion may include stopping the implementation of the first intent or implementing a first solution for the first intent.

[0111] For example, the information indicating the execution suggestion for the first intent includes a first field, and when the value of the first field is a first value, the execution suggestion is to stop executing the first intent.

[0112] In another example, the information indicating the execution suggestion for the first intent includes a first field and a second field, and when the value of the first field is the second value and the value of the second field is the first solution, the execution suggestion is to execute the first solution for the first intent.

[0113] In another example, the information indicating the execution suggestion for the first intent includes a second field, and when the value of the second field is the first solution, the execution suggestion is to execute the first solution for the first intent.

[0114] Optionally, after receiving information from the second device indicating an execution suggestion for the first intent, the first device may process the first intent based on the execution suggestion. For example, when the execution suggestion includes stopping executing the first intent, the first device may stop executing the first intent. In another example, when the execution suggestion includes executing a first solution for the first intent, the first device may execute the first solution to satisfy the first intent.

[0115] Optionally, the information indicating the execution suggestion for the first intent may be carried in an existing message (e.g., an intent change request) or may be carried in a new message, which is not limited in this application.

[0116] According to the above method embodiment, after transmitting first information indicating an impact on at least one KPI when a solution to the first intent is executed to the second device, the first device receives information from the second device indicating an execution suggestion for the first intent. In this manner, the second device may determine the execution suggestion for the first intent based on the impact on at least one KPI when a solution to the first intent is executed. For example, the second device may select a solution that can satisfy the second device's requirements for at least one KPI in a network to which the device executing the first intent belongs (in other words, a condition that the at least one KPI must satisfy), and suggest the first device to select the solution. Therefore, according to the above method embodiment, when a solution to the first intent is executed, it is possible to avoid a case where at least one KPI does not satisfy the second device's requirements for at least one KPI in a network to which the device executing the first intent belongs, thereby ensuring the performance of the network to which the device executing the first intent belongs.

[0117] Optionally, S301 may be realized in the following manner.

[0118] Implementation method 1: The first device may generate at least one solution that can satisfy the first intent based on an intent creation request from the second device, and then send the first information to the second device.

[0119] Optionally, in the first implementation, when the first information is sent to the second device, the first device has not started to execute a solution to the first intent, and the impact on the at least one KPI when the solution to the first intent is executed may be a predicted impact on the at least one KPI when the solution to the first intent is executed.

[0120] The first information may include information indicating a value of at least one KPI when a solution to the first intent is executed, and / or information indicating an offset of at least one KPI when a solution to the first intent is executed, and information indicating a current value of at least one KPI.

[0121] Optionally, the first device may determine the first information by using the following method.

[0122] A1: The first device receives second information from the third device.

[0123] The third device may be a KM.

[0124] Optionally, the second information indicates at least one of the following: an offset of at least one KPI when a solution to the first intent is executed, or an offset of at least one KPI when at least one action in the solution to the first intent is executed.

[0125] The offset of the at least one KPI when the at least one action in the solution to the first intent is executed may be one of the following: a value of the change of the at least one KPI when the at least one action in the solution to the first intent is executed (the value may be an integer, a negative number, or 0), or a percentage of the change of the at least one KPI when the at least one action in the solution to the first intent is executed.

[0126] Optionally, the second information in the third device may be pre-stored in the third device by the system manager, or may be detected by the first device or another device and sent to the third device when the first device or another device executes a solution to the first intent.

[0127] The system manager may store the second information in the third device by using the following method: The system manager sends an intent knowledge update request to the third device. The intent knowledge update request may include information indicating an offset of a KPI when a solution or an operation in the solution is executed. For example, the information indicates that energy consumption is reduced by 10% and throughput is increased by 15%. In another example, the information indicates that energy consumption is increased by 15% and throughput is reduced by 10%. After updating the database based on the intent knowledge update request, the third device may send an intent knowledge update response to the system manager to indicate that the update is complete.

[0128] A2: The first device receives third information from a fourth device indicating a current value of at least one KPI.

[0129] The fourth device may be a DCCF.

[0130] A3: The first device determines the first information based on the second information and the third information.

[0131] In some possible implementation manners, when the first information includes information indicating a value of at least one KPI when a solution to the first intent is executed, the first device may determine the value of the at least one KPI when a solution to the first intent is executed based on the second information and the third information, thereby determining the first information.

[0132] Specifically, the first device may determine an offset of the at least one KPI when the solution to the first intent is executed based on the second information, and may determine a current value of the at least one KPI based on the third information. The first device may then calculate a value of the at least one KPI when the solution to the first intent is executed based on the offset of the at least one KPI when the solution to the first intent is executed and the current value of the at least one KPI.

[0133] For example, when the third information indicates that the current value of the throughput is 10 kilobits per second (kps) and the second information indicates that the throughput offset when the first intent solution is executed is -2 kps, the throughput value when the first intent solution is executed is 8 kps.

[0134] In another example, when the third information indicates that the current value of the throughput is 10 kps and the second information indicates that the offset of the throughput when the solution to the first intent is executed is -10%, the value of the throughput when the solution to the first intent is executed is 9 kps.

[0135] Optionally, when the second information indicates an offset of the at least one KPI when the at least one action in the solution to the first intent is executed, the first device performs a weighting operation on the offset of the at least one KPI when the at least one action in the solution to the first intent is executed to determine an offset of the at least one KPI when the solution to the first intent is executed.

[0136] In some other possible implementation manners, when the first information includes information indicating an offset of at least one KPI when a solution to the first intent is executed, and the information indicates a current value of the at least one KPI, the first device may determine that the first information includes the second information and the third information.

[0137] According to the first implementation method, the second device may provide the first device with an execution suggestion for the first intent when the intent is created. The execution suggestion may be determined by the second device based on an impact on at least one KPI when a solution to the first intent is executed. This avoids a case where, when the intent is created and a solution to the first intent is executed, the at least one KPI does not satisfy the second device's requirements for the at least one KPI in the network to which the device executing the first intent belongs, thereby ensuring the performance of the network to which the device executing the first intent belongs.

[0138] Implementation method 2: When the first device executes a solution to the first intent, the first device may send the first information to the second device.

[0139] The first information may include information indicating a value of at least one KPI when a solution to the first intent is executed.

[0140] The value of the at least one KPI when the solution to the first intent is executed may be a value of the at least one KPI detected by the first device when the solution to the first intent is executed.

[0141] According to embodiment 2, the first device may detect a value of at least one KPI when a solution to the first intent is executed, and may transmit the detected value of the at least one KPI to the second device. In this manner, the second device may determine an execution suggestion for the first intent based on the detected value of the at least one KPI. This avoids a case where, when a solution to the first intent is executed, the at least one KPI does not satisfy the second device's requirement for the at least one KPI in the network to which the device executing the first intent belongs, thereby ensuring the performance of the network to which the device executing the first intent belongs.

[0142] Optionally, in the implementation scenario of the above embodiment, before S301, the method further includes the following steps:

[0143] S300: The second device transmits information indicating at least one KPI to the first device. In response, the first device receives information from the second device indicating the at least one KPI.

[0144] Optionally, the information indicative of at least one KPI includes: At least one KPI, and an identifier and / or intent expression of a second intent indicating at least one KPI; Contains at least one of the following:

[0145] The first device may determine at least one KPI based on the information indicating the at least one KPI. For example, when the first device determines, based on the identifier and / or intent expression of the second intent, that the second intent is to ensure throughput of 10 kps or more, the first device may determine that the at least one KPI includes throughput. In another example, when the first device determines, based on the identifier and / or intent expression of the second intent, that the second intent is to ensure latency of <5 milliseconds (ms), the first device may determine that the at least one KPI includes latency.

[0146] Optionally, the information indicative of the at least one KPI may be carried in an existing message (e.g., a create intent request or a change intent request) or may be carried in a new message, which is not a limitation of this application.

[0147] According to this method, the first device only needs to feed back to the second device the impact of implementing the solution to the first intent on at least one KPI indicated by the information indicating the at least one KPI, and does not need to feed back the impact of implementing the solution to the first intent on all KPIs, thereby saving transmission resources.

[0148] Optionally, before S302, the second device may determine the execution suggestion by using the following method.

[0149] B1: The second device determines, based on the first information, an impact on at least one KPI when a solution to the first intent is executed.

[0150] The impact on the at least one KPI when the solution to the first intent is executed may be a value of the at least one KPI when the solution to the first intent is executed.

[0151] B2: The second device determines an execution suggestion depending on whether a value of the at least one KPI when the solution to the first intent is executed satisfies a first condition.

[0152] The first condition is a condition that must be met by at least one KPI (in other words, a requirement of the second device for at least one KPI in the network to which the device that executes the resolution of the intent belongs).

[0153] Optionally, the second device may obtain the condition that the at least one KPI needs to satisfy in the following manner: The condition that the at least one KPI needs to satisfy may be a value range of the at least one KPI.

[0154] Method 1: The second device obtains a condition that at least one KPI must satisfy by using a second intent.

[0155] Specifically, when the intent expression of the second intent includes information that can indicate a target value, the target value may be used to reflect a condition that at least one KPI must satisfy. For example, when the second intent is to ensure that the throughput is 10 kps or more, the target value of the throughput is 10 kps or more, and the throughput must satisfy the condition of being 10 kps or more. In another example, when the second intent is to ensure that the latency is <5 ms, the target value of the latency is less than 5 ms, and the latency must satisfy the condition of being less than 5 ms.

[0156] Method 2: The second device obtains, based on the network configuration, a condition that at least one KPI must satisfy.

[0157] For example, when the bandwidth utilization configured for the device by the network is 10% or more, the bandwidth utilization must meet the condition of being 10% or more.

[0158] Optionally, B2 may be realized in the following manner.

[0159] Optionally, when a solution that satisfies the second condition exists in the solutions for the first intent, the second device selects a first solution to be used to satisfy the first intent from the solutions that satisfy the second condition, and based on this, determines that the execution suggestion is to execute the first solution for the first intent. The second condition is that at least one KPI satisfies the first condition when the solution for the first intent is executed.

[0160] For example, if the solutions for the first intent include Solution 1 and Solution 2, and at least one KPI is throughput, and the throughput value is 8 kps when Solution 1 is executed and 10 kps when Solution 2 is executed, and a condition that the throughput is 10 kps or more needs to be met, the second device may determine that the execution suggestion is to execute Solution 2 for the first intent.

[0161] When there are multiple solutions for the first intent that satisfy the second condition, the second device may randomly select one solution (i.e., the first solution) from the multiple solutions, or the second device may select one solution (i.e., the first solution) from the multiple solutions according to a preset policy (e.g., selecting the solution with the lowest delay or the solution with the smallest energy consumption).

[0162] Optionally, when there is no solution that satisfies the second condition in the solutions to the first intent, the second device may determine that the execution suggestion is to stop executing the first intent, and the second condition is that at least one KPI satisfies the first condition when the solution to the first intent is executed.

[0163] For example, if the solutions for the first intent include solution a and solution b, and at least one KPI is throughput, and the throughput value is 8 kps when solution a is executed and the throughput value is 9 kps when solution b is executed, and the condition that the throughput is 10 kps or more needs to be met, the second device may determine that the execution suggestion is to stop executing the first intent.

[0164] Optionally, when there is no solution that satisfies the second condition among the solutions for the first intent, the second device may determine that the execution suggestion is to execute the first solution for the first intent by using at least one of the following methods: selecting a solution (i.e., the first solution) that has the minimum number of first KPIs from the solutions for the first intent; selecting a solution (i.e., the first solution) that has the minimum number of third intents from the solutions for the first intent; and selecting a solution (i.e., the first solution) that has the minimum difference between the first KPI and a condition that the first KPI must satisfy when the solution for the first intent is executed. The second condition is that at least one KPI satisfies the first condition when the solution for the first intent is executed, and the first KPI does not satisfy the condition that the first KPI must satisfy when the solution for the first intent is executed, and the third intent is an intent associated with the first KPI.

[0165] For example, solutions for the first intent include Solution 3 and Solution 4, and at least one KPI is throughput and delay. When Solution 3 is executed, the throughput value is 8 kps and the delay is 6 ms, and when Solution 4 is executed, the throughput value is 9 kps and the delay is 4 ms. The throughput must satisfy the condition of being 10 kps or more, and the delay must satisfy the condition of being less than 5 ms. In this case, when Solution 3 is executed, the first KPI includes throughput and delay, and when Solution 4 is executed, the first KPI includes throughput. Therefore, the second device may select the solution having the smallest number of first KPIs (i.e., Solution 4) and determine that the execution suggestion is to execute Solution 4 for the first intent.

[0166] In another example, solutions for the first intent include Solution 5 and Solution 6, and at least one KPI is throughput and latency. When Solution 5 is executed, the throughput value is 8 kps and the latency is 6 ms. When Solution 6 is executed, the throughput value is 9 kps and the latency is 4 ms. The throughput must satisfy the condition of 10 kps or more, and the latency must satisfy the condition of less than 5 ms. In this case, when Solution 5 is executed, the first KPI includes throughput and latency, and when Solution 6 is executed, the first KPI includes throughput. The throughput is associated with Intent 1, and the latency is associated with Intent 2. Therefore, when Solution 5 is executed, the third intent includes Intent 1 and Intent 2, and when Solution 6 is executed, the third intent includes Intent 1. The second device may select the solution with the smallest number of third intents (i.e., Solution 6) and determine that the execution suggestion is to execute Solution 6 for the first intent.

[0167] In another example, the solutions for the first intent include Solution 7 and Solution 8, and at least one KPI is throughput and delay. When Solution 7 is executed, the throughput value is 8 kps and the delay is 3 ms. When Solution 8 is executed, the throughput value is 9 kps and the delay is 4 ms. The throughput must satisfy a condition of 10 kps or more, and the delay must satisfy a condition of less than 5 ms. In this case, when Solution 7 is executed, the difference between the throughput of the first KPI and the condition that the throughput of the first KPI must satisfy is −2 kps. When Solution 8 is executed, the difference between the throughput of the first KPI and the condition that the throughput of the first KPI must satisfy is −1 kps. Therefore, the second device may determine that the execution suggestion is to execute Solution 8 for the first intent.

[0168] According to the method, the second device may determine an execution suggestion for the first intent based on an effect on at least one KPI when a solution for the first intent is executed. For example, the second device may select a solution that can satisfy the requirements of the second device for at least one KPI in a network to which the device executing the first intent belongs (in other words, a condition that the at least one KPI must satisfy), and suggest to the first device to select the solution. Thus, according to the method, when a solution for the first intent is executed, a case in which the at least one KPI does not satisfy the requirements of the second device for at least one KPI in a network to which the device executing the first intent belongs can be avoided, thereby ensuring the performance of the network to which the device executing the first intent belongs.

[0169] Optionally, in an implementation scenario of the above embodiment, after the first device executes the first solution, the method further includes: the first device sends information to the KM indicating an offset of at least one KPI when the first solution is executed.

[0170] An offset of the at least one KPI when the first solution is executed may be detected by the first device when the first solution is executed.

[0171] According to the method, the first device may update the offset of at least one KPI in the KM based on the detected data when the first solution is executed to improve the accuracy of the data in the KM.

[0172] An embodiment of the present application further provides an intent processing method, which may be applied to the communication system shown in Fig. 1 or Fig. 2. The steps of the method will be described in detail below with reference to the flowchart shown in Fig. 4.

[0173] S401: The second device transmits fourth information to the first device. In response, the first device receives the fourth information from the second device.

[0174] The first device may be an intent producer and the second device may be an intent consumer.

[0175] The fourth information may indicate a condition (for ease of explanation, hereinafter referred to as the first condition) that at least one KPI must satisfy.

[0176] For the specific content of the at least one KPI and the conditions that the at least one KPI must meet, please refer to the method shown in Figure 3. The details will not be described again here.

[0177] Optionally, the fourth information is: information indicating at least one KPI and a first condition that the at least one KPI must satisfy; and / or a second intent identifier and / or intent expression indicating a first condition that at least one KPI must satisfy; Includes:

[0178] The first device may determine a first condition that at least one KPI must satisfy based on the fourth information. For example, when the first device determines, based on the identifier and / or intent expression of the second intent, that the second intent is to ensure throughput of 10 kps or more, the first device may determine that at least one KPI must include throughput and that the condition that the throughput is 10 kps or more must be satisfied. In another example, when the first device determines, based on the identifier and / or intent expression of the second intent, that the second intent is latency < 5 ms, the first device may determine that at least one KPI must include latency and that the condition that the latency is less than 5 ms must be satisfied.

[0179] The fourth information may be carried in an existing message (e.g., a create intent request or a change intent request) or may be carried in a new message, which is not limited in this application.

[0180] S402: The first device processes the first intent depending on whether a value of at least one KPI satisfies a first condition when a solution to the first intent is executed.

[0181] Specifically, when a solution that satisfies the second condition exists among the solutions for the first intent, the first device selects a first solution to be used to satisfy the first intent from the solutions that satisfy the second condition and executes the first solution. When a solution that satisfies the second condition does not exist among the solutions for the first intent, the first device may decide not to execute the first intent. The second condition is that at least one KPI satisfies the first condition when the solution for the first intent is executed.

[0182] Optionally, when there are multiple solutions to the first intent that satisfy the second condition, the first device may randomly select one solution (i.e., the first solution) from the multiple solutions, or the first device may select one solution (i.e., the first solution) from the multiple solutions according to a preset policy (e.g., selecting the solution with the lowest delay or the solution with the smallest energy consumption).

[0183] For a method in which the first device determines the value of at least one KPI when the resolution of the first intent is executed, refer to the method shown in Figure 3. For specific content of the resolution of the first intent, refer to the method shown in Figure 3. The details will not be described again here.

[0184] Optionally, after S402, the method further includes: the first device sends information to the KM indicating an offset of at least one KPI when the first solution is executed. For specific content, please refer to the method shown in Fig. 3. The details will not be described again here.

[0185] Optionally, after S402, after executing the first solution, the first device may adjust the solution for the first intent based on an effect of executing the first solution on the at least one KPI. Specifically, the first device may detect a value of the at least one KPI when the first solution is executed. When the detected value of the at least one KPI when the first solution is executed satisfies the first condition, the first device may continue to execute the first solution, and / or when the detected value of the at least one KPI when the first solution is executed does not satisfy the first condition, the first device may execute S402, in other words, reselect a solution for the first intent.

[0186] According to the above method embodiment, the first device may process the first intent based on an effect on at least one KPI when a solution to the first intent is executed. For example, the first device may select a solution that can satisfy the requirements of the second device for at least one KPI in the network to which the device executing the first intent belongs for execution (in other words, the conditions that the at least one KPI must satisfy). Thus, according to the above method embodiment, when a solution to the first intent is executed, it is possible to avoid a case where the at least one KPI does not satisfy the requirements of the second device for at least one KPI in the network to which the device executing the first intent belongs, thereby ensuring the performance of the network to which the device executing the first intent belongs.

[0187] An embodiment of this application further provides an intent processing method, which may be applied to the communication system shown in Figure 1 or Figure 2. The method illustrates a possible implementation of the methods shown in Figures 3 and 4. With reference to the flowchart shown in Figure 5, an example in which a first device is an IDMS producer, a second device is an IDMS consumer, a third device is a KM, and a fourth device is a DCCF will be used below to explain this embodiment of this application.

[0188] S501: The IDMS consumer sends an intent creation request to the IT module.

[0189] The create intent request may be used to request an IDMS producer to fulfill a first intent.

[0190] Optionally, the intent creation request includes an intent expression of the first intent.

[0191] S502: The IT module performs intent translation on the first intent and determines a policy for the first intent.

[0192] Optionally, the IT module may obtain a policy for the first intent from the KM.

[0193] S503: The IT module sends an intent evaluation message to the IEv module.

[0194] The intent evaluation message may include an identifier of the first intent and is used to request the IEv module to evaluate the completion status of the first intent.

[0195] S504: The IEv module transmits a notification of the intent evaluation result to the IT module.

[0196] The intent evaluation result notification may include an identifier of the first intent and information indicating the fulfillment state of the first intent.

[0197] Optionally, when the information indicating the fulfillment state of the first intent indicates that the first intent is not fulfilled, steps S505 to S515 may be executed. When the information indicating the fulfillment state of the first intent indicates that the first intent has already been fulfilled, before stopping realizing the first intent, the IEv module may periodically or aperiodically determine the fulfillment state of the first intent and send an intent evaluation result notification to the IT module.

[0198] S505: The IT module generates a solution that can satisfy the first intent.

[0199] The IT module may generate at least one solution that can satisfy the first intent according to the policy determined in S502.

[0200] S506: The IT module sends a solution determination message to the ID module.

[0201] The solution determination message may include at least one solution and is used to request the ID module to determine a solution to be executed for the first intent.

[0202] S507: The ID module obtains, from the KM, second information indicating an offset of the at least one KPI when the at least one solution is executed.

[0203] For the specific content of the second information, please refer to the method shown in Figure 3. The details will not be described again here.

[0204] S507 may be achieved by using the following procedure.

[0205] E1: The ID module sends a first request to the KM.

[0206] The first request may include at least one solution.

[0207] E2: The KM sends the first response to the ID module.

[0208] The first response may include the second information.

[0209] For example, when the solutions for the first intent include Solution 1 and Solution 2, and at least one KPI includes KPI1 and KPI2, the representation format of the second information is as follows: (<Solution 1:<KPI1,オフセット> ,<KPI2,オフセット> > and < Solution 2:<KPI1,オフセット> ,<KPI2,オフセット> >) is also acceptable.

[0210] S508: The ID module obtains third information indicating the current value of at least one KPI from the DCCF.

[0211] S508 may be achieved by using the following procedure.

[0212] F1: The ID module sends the second request to the DCCF.

[0213] The second request may include at least one KPI for indicating a KPI whose current value needs to be obtained.

[0214] F2: The DCCF sends the second response to the ID module.

[0215] The second response may include third information. The third information may include at least one KPI and the current value corresponding to at least one KPI.

[0216] For example, when at least one KPI includes KPI1 and KPI2, the expression form of the third information may be (<KPI1, value>, <KPI2, value>).

[0217] S509: The ID module determines the value of at least one KPI when at least one solution is executed based on the second information and the third information, and determines fifth information indicating the value of at least one KPI when at least one solution is executed.

[0218] The fifth information may be the first information in implementation method 1 of the method shown in FIG. 3.

[0219] For the specific implementation of S509, refer to the method shown in FIG. 3. Details are not described again here.

[0220] S510: The ID module sends the fifth information to the ICR module.

[0221] For example, when the solution of the first intent includes solution 1 and solution 2, and at least one KPI includes KPI1 and KPI2, the expression form of the fifth information may be (<solution 1: <KPI1, value>, <KPI2, value>> and <solution 2: <KPI1, value>, <KPI2, value>>).

[0222] <S511: The ICR module determines whether the value of the at least one KPI satisfies a condition (i.e., a first condition) that the at least one KPI needs to satisfy when the at least one solution is executed.

[0223] For the specific content of S511, please refer to the method in Figure 4. The details will not be described again here.

[0224] Furthermore, depending on whether the value of the at least one KPI satisfies a first condition when a solution to the first intent is executed, the ICR module may determine whether the solution affects the fulfillment of the intent associated with the at least one KPI.

[0225] Specifically, when the solution to the first intent is executed and the value of the at least one KPI satisfies the first condition, the solution to the first intent does not affect the fulfillment of the intent associated with the at least one KPI, or when the solution to the first intent is executed and the value of the at least one KPI does not satisfy the first condition, the solution to the first intent affects the fulfillment of the intent associated with the at least one KPI.

[0226] For example, if at least one KPI includes throughput and the fourth intent is to ensure that the throughput is 10 kps or greater, then if the throughput is 10 kps or greater when the solution to the first intent is executed, then execution of the solution to the first intent does not affect fulfillment of the fourth intent. If the throughput is less than 10 kps when the solution to the first intent is executed, then execution of the solution to the first intent does affect fulfillment of the fourth intent.

[0227] S512: The ICR module sends a first message to the ID module.

[0228] The first message may include information indicating whether a value of the at least one KPI satisfies a first condition when a solution to the first intent is executed.

[0229] For example, when the solution to the first intent includes solution 1 and solution 2, and at least one KPI includes KPI1 and KPI2, the expression format of the information indicating whether the value of at least one KPI satisfies the first condition when the solution to the first intent is executed may be (<Solution 1: whether the value of KPI1 satisfies the condition that KPI1 needs to satisfy, and whether the value of KPI2 satisfies the condition that KPI2 needs to satisfy>, and <Solution 2: whether the value of KPI1 satisfies the condition that KPI1 needs to satisfy, and whether the value of KPI2 satisfies the condition that KPI2 needs to satisfy>).

[0230] Optionally, the first message further includes information indicating whether the execution of the solution to the first intent affects the fulfillment of other intents.

[0231] For example, when solutions for a first intent include solution 1 and solution 2, and the intents associated with at least one KPI include intent 1 and intent 2, the expression format of the information indicating whether execution of the solution for the first intent will affect the fulfillment of other intents may be (<Solution 1:<Intent 1, whether fulfillment of intent 1 will be affected (yes / no)><Intent 2, whether fulfillment of intent 1 will be affected (yes / no)>> and <Solution 2:<Intent 1, whether fulfillment of intent 1 will be affected (yes / no)><Intent 2, whether fulfillment of intent 1 will be affected (yes / no)>>).

[0232] S513: The ID module processes the first intent based on the first message.

[0233] For example, the ID may select a solution that satisfies the first intent and that does not affect the satisfaction of other intents.

[0234] For the specific content of S513, please refer to the method in Figure 4. The details will not be described again here.

[0235] Optionally, S514 and S515 may be executed when the ID module does not select a solution to be used to satisfy the first intent (corresponding to stopping executing the first intent in the method shown in FIG. 4).

[0236] S514: The ID module sends a second message to the IDMS consumer.

[0237] The second message may include an identifier of the first intent and the fifth information.

[0238] Optionally, the second message further includes information indicating whether the execution of the solution to the first intent affects the fulfillment of other intents.

[0239] S515: The IDMS consumer sends information indicating an execution suggestion of the first intent to the ID module.

[0240] For the specific content of S515, please refer to the method in Figure 3. The details will not be described again here.

[0241] Optionally, when the ID module fails to select a solution to be used to satisfy the first intent in accordance with S505-S515, S505-S515 may be repeatedly executed until the ID module selects a solution to be used to satisfy the first intent.

[0242] According to the method, when selecting a solution to be used to satisfy the first intent, the IDMS producer may select a solution that can satisfy the requirements of the IDMS consumer for at least one KPI (in other words, the conditions that the at least one KPI must satisfy) in the network to which the device executing the first intent belongs. Thus, according to the method, when the solution to the first intent is executed, it is possible to avoid a case where the at least one KPI does not satisfy the requirements of the IDMS consumer for at least one KPI in the network to which the device executing the first intent belongs, and therefore it is possible to ensure the performance of the network to which the device executing the first intent belongs.

[0243] Furthermore, in the intent creation process, the IDMS producer may preferentially select a solution that does not affect the fulfillment of other intents, in other words, a solution that does not have a conflict with other intents in effect, which can avoid affecting the fulfillment of other intents and further ensure the performance of the network to which the device executing the first intent belongs.

[0244] Furthermore, when the IDMS producer does not select an appropriate solution, the IDMS producer may send information to the IDMS consumer indicating an impact on at least one KPI when the solution for the first intent is executed. The IDMS consumer may determine an execution suggestion for the first intent based on the impact on the at least one KPI when the solution for the first intent is executed, and send the execution suggestion information to the IDMS producer. This avoids a case where, when the solution for the first intent is executed, the at least one KPI does not satisfy the IDMS consumer's requirements for the at least one KPI in the network to which the device executing the first intent belongs, thereby ensuring the performance of the network to which the device executing the first intent belongs.

[0245] An embodiment of this application further provides an intent processing method. The method may be applied to the communication system shown in FIG. 1 or FIG. 2. The method illustrates another possible implementation of the method shown in FIG. 3. Referring to the flowchart shown in FIG. 6, an example in which a first device is an IDMS producer, a second device is an IDMS consumer, a third device is a KM, and a fourth device is a DCCF is used below to describe this embodiment of this application. Compared with the embodiment shown in FIG. 5, in the method shown in FIG. 6, in the intent creation process, the IDMS consumer provides an execution suggestion for the first intent to the IDMS producer. After executing the solution for the first intent, the IDMS producer may feedback information to the IDMS consumer indicating the impact on at least one KPI when the solution for the first intent is executed. Furthermore, an IT module in the IDMS producer may send information indicating the offset of at least one KPI when the solution for the first intent is executed to the KM.

[0246] S601: The IDMS consumer sends an intent creation request to the IT module.

[0247] The create intent request may be used to request an IDMS producer to fulfill a first intent.

[0248] Optionally, the intent creation request includes an intent expression of the first intent.

[0249] Additionally, the intent creation request may further include a first instruction instructing the IDMS producer to feedback sixth information, the sixth information indicating an impact on at least one KPI when a solution to the first intent is implemented.

[0250] The sixth information may be the first information in the second implementation of the method shown in FIG.

[0251] Optionally, the first instruction includes information indicating at least one KPI. For specific content of the information indicating at least one KPI, please refer to the method shown in Figure 3. Details will not be described again here.

[0252] Optionally, the first instruction may alternatively be included in another message (eg, an intent change request) sent by the IDMS consumer to the IT module.

[0253] S602: The IT module performs intent translation on the first intent and determines a policy for the first intent.

[0254] S603: The IT module sends an intent evaluation message to the IEv module.

[0255] The intent evaluation message may include an identifier of the first intent and is used to request the IEv module to evaluate the completion status of the first intent.

[0256] Optionally, the intent evaluation message further includes a first instruction to instruct the IEv module to evaluate an impact on at least one KPI when a solution to the first intent is executed.

[0257] S604: The IEv module transmits a notification of the intent evaluation result to the IT module.

[0258] For the specific content of S604, refer to S504. Only the differences will be explained below.

[0259] Optionally, the intent evaluation result notification further includes sixth information.

[0260] For example, if the currently executed solution of the first intent is solution 1 and at least one KPI includes KPI1 and KPI2, the representation format of the sixth information is (identifier of the first intent:<Solution 1:<KPI1,オフセット> and<KPI2,オフセット> >) is also acceptable.

[0261] Optionally, when the intent evaluation result notification includes information indicating that the first intent has not been satisfied, steps S605 to S615 may be executed. When the intent evaluation result notification includes information indicating that the first intent has already been satisfied, before stopping realizing the first intent, the IEv module may periodically or aperiodically determine whether the first intent has been satisfied and send an intent evaluation result notification to the IT module.

[0262] S605: The IT module requests the KM to update the impact on at least one KPI when the solution to the first intent is executed.

[0263] S605 may be implemented by using the following procedure.

[0264] G1: The IT module sends a third request to the KM.

[0265] The third request may include a sixth piece of information.

[0266] G2: The KM sends a third response to the IT module.

[0267] The third response indicates that the KM has already updated the impact on at least one KPI when the solution to the first intent is executed.

[0268] S606: The IT module generates a solution that can satisfy the first intent.

[0269] S607: The IT module sends a solution determination message to the ID module.

[0270] S608: The ID module obtains, from the KM, second information indicating an offset of the at least one KPI when the at least one solution is executed.

[0271] S609: The ID module obtains third information indicating the current value of at least one KPI from the DCCF.

[0272] S610: The ID module determines, based on the second information and the third information, a value of the at least one KPI when the at least one solution is executed, and determines fifth information indicating the value of the at least one KPI when the at least one solution is executed.

[0273] S611: The ID module sends the fifth information to the ICR module.

[0274] S612: The ICR module determines whether the value of the at least one KPI satisfies a condition (i.e., a first condition) that the at least one KPI needs to satisfy when the at least one solution is executed.

[0275] S613: The ICR module sends a first message to the ID module.

[0276] For the specific content of S606 to S613, refer to S505 to S512, and the details will not be explained again here.

[0277] S614: The ID module sends a third message to the IDMS consumer.

[0278] The third message may include an identifier of the first intent and the fifth information.

[0279] Optionally, the third message further includes information indicating whether the execution of the solution to the first intent affects the fulfillment of other intents.

[0280] S615: The IDMS consumer sends information indicating an execution suggestion of the first intent to the ID module.

[0281] For the specific contents of S614 and S615, please refer to the method in Fig. 3. The details will not be described again here.

[0282] Optionally, when the IDMS consumer fails to select a solution to be used to satisfy the first intent for the IDMS producer according to S605-S615, S605-S615 may be executed repeatedly until a solution to be used to satisfy the first intent is selected.

[0283] Optionally, when the execution suggestion is to execute a first solution of a first intent, the method further includes S616 to S618.

[0284] S616: The ID module sends a fourth request to the IEv module.

[0285] The fourth request may be used to request the IEv module to determine a value of at least one KPI when the first solution is executed.

[0286] Optionally, the fourth request includes at least one of the following: an identifier of the first intent, an identifier of an intent that needs to be determined to be affected by the first solution, and at least one KPI.

[0287] The S617.IEv module sends the fourth message to the IDMS consumer.

[0288] The fourth message may include an identifier of the first intent and the sixth information.

[0289] The sixth information may indicate a value of at least one KPI when the first solution is executed. It can be understood that the sixth information is the first information in the second implementation of the method shown in FIG.

[0290] Optionally, the fourth message further includes information indicating whether the execution of the first solution for the first intent affects the fulfillment of other intents.

[0291] S618: The IDMS consumer sends information indicating an execution suggestion for the first intent to the ID module.

[0292] The information indicating the suggestion for the first intent may be carried in an intent deactivation or intent change notification message.

[0293] For the specific contents of S617 and S618, please refer to the method in Figure 3. The details will not be described again here.

[0294] According to the method, in the intent creation process, the IDMS producer may send information to the IDMS consumer indicating an impact on at least one KPI when the solution to the first intent is executed. The IDMS consumer then determines an execution suggestion for the first intent based on the impact on the at least one KPI when the solution to the first intent is executed, and sends information indicating the execution suggestion to the IDMS producer. This avoids a case where, when the solution to the first intent is executed, the at least one KPI does not satisfy the IDMS consumer's requirements for the at least one KPI in the network to which the device executing the first intent belongs, thereby ensuring the performance of the network to which the device executing the first intent belongs.

[0295] Furthermore, based on the first instruction from the IDMS consumer, the IDMS producer may monitor an impact of at least one KPI indicated by the first instruction when the first solution for the first intent is executed, and feed the impact back to the IDMS consumer. In this way, the IDMS consumer can determine an execution suggestion for the first intent based on the impact, thereby improving the accuracy of determining the execution suggestion.

[0296] Additionally, the IDMS producer may update the data in the KM based on the detected offset of the at least one KPI when the solution to the first intent is performed to improve the accuracy of the data in the KM.

[0297] An embodiment of this application further provides an intent processing method. The method may be applied to the communication system shown in Figure 1 or Figure 2. The method illustrates another possible implementation of the methods shown in Figures 3 and 4. With reference to the flowchart shown in Figure 7, an example in which the first device is an IDMS producer, the second device is an IDMS consumer, the third device is a KM, and the fourth device is a DCCF is used below to explain this embodiment of this application. Compared with the embodiment shown in Figure 5, in this embodiment, when the ID module in the IDMS producer fails to select a solution for the first intent, the IT module re-translates the first intent.

[0298] S701: The IDMS consumer sends an intent creation request to the IT module.

[0299] S702: The IT module performs intent translation on the first intent and determines a first policy for the first intent.

[0300] S703: The IT module sends an intent evaluation message to the IEv module.

[0301] S704: The IEv module transmits a notification of the intent evaluation result to the IT module.

[0302] Optionally, when the intent evaluation result notification includes information indicating that the first intent has not been satisfied, steps S705 to S717 may be executed. When the intent evaluation result notification includes information indicating that the first intent has already been satisfied, before stopping realizing the first intent, the IEv module may periodically or aperiodically determine whether the first intent has been satisfied and send an intent evaluation result notification to the IT module.

[0303] S705: The IT module generates a solution that can satisfy the first intent.

[0304] S706: The IT module sends a solution determination message to the ID module.

[0305] S707: The ID module obtains, from the KM, second information indicating an offset of the at least one KPI when the at least one solution is executed.

[0306] S708: The ID module obtains third information indicating the current value of the at least one KPI from the DCCF.

[0307] S709: The ID module determines, based on the second information and the third information, a value of the at least one KPI when the at least one solution is executed, and determines fifth information indicating the value of the at least one KPI when the at least one solution is executed.

[0308] S710: The ID module sends the fifth information to the ICR module.

[0309] S711: The ICR module determines whether the value of the at least one KPI satisfies a condition (i.e., a first condition) that the at least one KPI needs to satisfy when the at least one solution is executed.

[0310] S712: The ICR module sends a first message to the ID module.

[0311] S713: The ID module processes the first intent based on the first message.

[0312] For the specific content of S701 to S713, refer to S501 to S513, and the details will not be explained again here.

[0313] S714: When the ID module does not select a solution to be used to satisfy the first intent, the ID module sends a fifth request to the IT module.

[0314] The fifth request is used to request the IT module to retranslate the first intent.

[0315] Optionally, the fifth request includes an identifier of the first intent.

[0316] S715: The IT module re-translates the first intent by using the second policy.

[0317] Optionally, before the policy of the first intent is not traversed, the IT module retranslates the first intent by using a second policy different from the first policy to generate a solution for the first intent, and executes S706 to S713. When the policy of the first intent has already been traversed, the IT module no longer retranslates the first intent. In this case, the IT module may send a message to the ID module to trigger the ID module to execute S716.

[0318] S716: The ID module sends a second message to the IDMS consumer.

[0319] S717: The IDMS consumer sends information indicating an execution suggestion for the first intent to the ID module.

[0320] For the specific contents of S716 and S717, please refer to S514 and S515, and the details will not be described again here.

[0321] Optionally, when the ID module fails to select a solution to be used to satisfy the first intent in accordance with S705-S717, S705-S717 may be repeatedly executed until the ID module selects a solution to be used to satisfy the first intent.

[0322] The method may achieve the effect of the method shown in Figure 5. The details will not be described again here.

[0323] Further, in the method, when the ID module does not select a solution to be used to satisfy the first intent, the IT module may be triggered to re-translate the first intent and generate a solution for the first intent, thereby enabling the ID module to increase the probability of selecting an appropriate solution.

[0324] An embodiment of this application further provides an intent processing method, which may be applied to the communication system shown in Figure 1 or Figure 2. This method illustrates another possible implementation of the methods shown in Figures 3 and 4. With reference to the flowchart shown in Figure 8, an example in which the first device is an IDMS producer, the second device is an IDMS consumer, the third device is a KM, and the fourth device is a DCCF is used below to explain this embodiment of this application. Compared with the embodiment shown in Figure 5, in this embodiment, an ICR module in the IDMS producer interacts with the KM and the DCCF.

[0325] S801: The IDMS consumer sends an intent creation request to the IT module.

[0326] S802: The IT module performs intent translation on the first intent and determines a policy for the first intent.

[0327] S803: The IT module sends an intent evaluation message to the IEv module.

[0328] S804: The IEv module transmits a notification of the intent evaluation result to the IT module.

[0329] Optionally, when the intent evaluation result notification includes information indicating that the first intent has not been satisfied, steps S805 to S814 may be executed. When the intent evaluation result notification includes information indicating that the first intent has already been satisfied, before stopping realizing the first intent, the IEv module may periodically or aperiodically determine whether the first intent has been satisfied and send an intent evaluation result notification to the IT module.

[0330] S805: The IT module generates a solution that can satisfy the first intent.

[0331] S806: The IT module sends a solution determination message to the ID module.

[0332] For the specific content of S801 to S806, refer to S501 to S506, and the details will not be explained again here.

[0333] S807: The ID module sends a sixth request to the ICR.

[0334] The sixth request is used to trigger the ICR module to determine an impact on at least one KPI when the solution to the first intent is executed.

[0335] For specific details of the impact on at least one KPI when the solution of the first intent is executed, please refer to the method shown in Figure 3. The details will not be described again here.

[0336] Optionally, the sixth request includes information indicating a solution to the first intent.

[0337] S808: The ICR module obtains, from the KM, second information indicating an offset of the at least one KPI when the at least one solution is executed.

[0338] S809: The ICR module obtains third information indicating the current value of at least one KPI from the DCCF.

[0339] For the specific contents of S808 and S809, please refer to S507 and S508. The only difference is that the ID module in S507 and S508 is replaced with an ICR module.

[0340] S810: The ICR module determines whether the value of the at least one KPI satisfies a condition (i.e., a first condition) that the at least one KPI needs to satisfy when the at least one solution is executed.

[0341] For the specific content of S810, please refer to the method in Figure 3. The details will not be described again here.

[0342] S811: The ICR module sends a first message to the ID module.

[0343] S812: The ID module processes the first intent based on the first message.

[0344] Optionally, S813 and S814 may be executed when the ID module does not select a solution to be used to satisfy the first intent (corresponding to stopping executing the first intent in the method shown in FIG. 4).

[0345] S813: The ID module sends a second message to the IDMS consumer.

[0346] S814: The IDMS consumer sends information indicating an execution suggestion for the first intent to the ID module.

[0347] For specific details of S811 to S814, refer to S512 to S515, and the details will not be explained again here.

[0348] Optionally, when the ID module fails to select a solution to be used to satisfy the first intent in accordance with S805-S814, S805-S814 may be repeatedly executed until the ID module selects a solution to be used to satisfy the first intent.

[0349] The method may achieve the effect of the method shown in Figure 5. The details will not be described again here.

[0350] Furthermore, compared to the method shown in FIG. 5, the ICR module interacts directly with the KM and DCCF, reducing the number of messages and saving signaling overhead.

[0351] Based on the same technical concept, this application also provides an intent processing device. The structure of the device is shown in Fig. 9, including a communication unit 901 and a processing unit 902. The intent processing device 900 may be used in an intent producer (e.g., an IDMS producer in the communication system shown in Fig. 1 or an MnS producer in the communication system shown in Fig. 2) or an intent consumer (e.g., an IDMS consumer in the communication system shown in Fig. 1 or an MnS consumer in the communication system shown in Fig. 2), and may implement the intent processing methods provided in the above embodiments and instances of this application. The functions of the units of the intent processing device 900 are described below.

[0352] The communication unit 901 is configured to receive and transmit data.

[0353] The communication unit 901 may be embodied through a physical interface, a communication module, a communication interface, or an input / output interface. The intent processing device 900 may be connected to a network cable or cables by using the communication unit to establish a physical connection to other devices.

[0354] In the implementation, the intent processing unit 900 is used in the first device in the embodiment of this application shown in Figure 3, or in the IDMS producer in the embodiment of this application shown in any one of Figures 5 to 8. The specific functions of the processing unit 902 in this implementation will be described below.

[0355] The processing unit 902 is configured to send first information to the second device by using the communication unit 901, the first information indicating an impact on at least one key performance indicator KPI when a solution to the first intent is executed, and is configured to receive information from the second device by using the communication unit 901 indicating an execution suggestion for the first intent.

[0356] Optionally, the first processing unit 902 is further configured to receive, by using the communication unit 901, information from the second device indicating the at least one KPI before sending, by using the communication unit 901, the first information to the second device.

[0357] Optionally, the information indicative of at least one KPI includes: At least one KPI, and an identifier and / or intent expression of a second intent indicating at least one KPI; Contains at least one of the following:

[0358] Optionally, the at least one KPI comprises at least one of the following: throughput, throughput volume, energy consumption, bandwidth utilization, delay, and packet loss rate.

[0359] Optionally, the first information is: Information indicative of the value of at least one KPI when the solution to the first intent is executed; and / or Information indicating an offset of at least one KPI when the solution to the first intent is executed, and information indicating a current value of the at least one KPI. Includes:

[0360] Optionally, the processing unit 902 is further configured to receive second information from a third device by using the communication unit 901 before sending the first information to the second device by using the communication unit 901, wherein the second information indicates at least one of the following: an offset of at least one KPI when a solution to the first intent is executed, or an offset of at least one KPI when at least one action in the solution to the first intent is executed.

[0361] Optionally, the solution to the first intent is at least one solution that can satisfy the first intent.

[0362] Optionally, the implementation suggestion includes stopping implementing the first intent or implementing a first solution for the first intent.

[0363] In the implementation, the intent processing device 900 is used in the second device in the embodiment of this application shown in Figure 3, or in the IDMS consumer in the embodiment of this application shown in any one of Figures 5 to 8. The specific functions of the processing unit 902 in this implementation will be described below.

[0364] The processing unit 902 is configured to receive first information from the first device by using the communication unit 901, the first information indicating an impact on at least one key performance indicator KPI when a solution to the first intent is executed, and to send information indicating an execution suggestion for the first intent to the first device by using the communication unit 901.

[0365] Optionally, the processing unit 902 is specifically configured to, before receiving the first information from the first device by using the communication unit 901, send information indicative of the at least one KPI to the first device by using the communication unit 901.

[0366] Optionally, the information indicative of at least one KPI includes: At least one KPI, and an identifier and / or intent expression of a second intent indicating at least one KPI; Contains at least one of the following:

[0367] Optionally, the at least one KPI comprises at least one of the following: throughput, throughput amount, energy consumption, and bandwidth utilization.

[0368] Optionally, the first information is: Information indicative of the value of at least one KPI when the solution to the first intent is executed; and / or Information indicating an offset of at least one KPI when the solution to the first intent is executed, and information indicating a current value of the at least one KPI. Includes:

[0369] Optionally, the solution to the first intent is at least one solution that can satisfy the first intent.

[0370] Optionally, the implementation suggestion includes stopping implementing the first intent or implementing a first solution for the first intent.

[0371] It should be noted that in the above embodiments of this application, the division into modules is merely an example and is merely a logical division of functions, and other divisions may be used in actual implementation. Furthermore, the functional units in the embodiments of this application may be integrated into one processing unit, may exist physically alone, or two or more units may be integrated into one unit. The integrated unit may be realized in the form of hardware or in the form of a software functional unit.

[0372] When an integrated unit is realized in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application may essentially, or the portion contributing to the prior art or all or part of the technical solution may be realized in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device, etc.) or a processor to execute all or part of the steps of the method described in the embodiments of this application. The above storage medium includes any medium capable of storing program code, such as a USB flash drive, a removable hard disk drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0373] Based on the same technical concept, this application further provides an intent processing device. The intent processing device may be used in an intent producer (e.g., an IDMS producer in the communication system shown in FIG. 1 or an MnS producer in the communication system shown in FIG. 2) or an intent consumer (e.g., an IDMS consumer in the communication system shown in FIG. 1 or an MnS consumer in the communication system shown in FIG. 2), may implement the intent processing method provided in the above embodiments and instances of this application, and has the functionality of the intent processing apparatus shown in FIG. 9. Referring to FIG. 10, the intent processing device 1000 includes a communication module 1001, a processor 1002, and a memory 1003. The communication module 1001, the processor 1002, and the memory 1003 are connected to each other.

[0374] Optionally, the communication module 1001, the processor 1002, and the memory 1003 are connected to each other via a bus 1004. The bus 1004 may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, etc. The bus may be classified into an address bus, a data bus, a control bus, etc. For ease of representation, in Fig. 10 there is only one thick line to represent the bus, but this does not mean that there is only one bus or only one type of bus.

[0375] The communication module 1001 is configured to receive and transmit data to realize communication interaction with other devices. For example, the communication module 1001 may be realized through a physical interface, a communication module, a communication interface, or an input / output interface.

[0376] In the implementation, the intent processing device 900 is used in the first device in the embodiment of this application shown in FIG. 3, or in the IDMS producer in the embodiment of this application shown in any one of FIGS. 5 to 8. Specific functions of the processor 1002 in this implementation will be described below. The processor 1002: The communication module 1001 is specifically configured to send first information to a second device, the first information indicating an impact on at least one key performance indicator KPI when a solution to the first intent is executed, and the communication module 1001 is specifically configured to receive information from the second device indicating an execution suggestion for the first intent.

[0377] In an implementation, the intent processing device 900 is used in the second device in the embodiment of this application shown in Figure 3, or in the IDMS consumer in the embodiment of this application shown in any one of Figures 5 to 8. The processor 1002 The communication module 1001 is specifically configured to receive first information from a first device, the first information indicating an impact on at least one key performance indicator (KPI) when a solution to the first intent is executed, and the communication module 1001 is specifically configured to send information indicating an execution suggestion for the first intent to the first device.

[0378] For specific functions of the processor 1002, please refer to the description in the intent processing method provided in the above embodiments and instances of this application, and the specific function description of the intent processing device 900 in the embodiment of this application shown in Figure 9. The details will not be described again here.

[0379] The memory 1003 is configured to store program instructions, data, etc. Specifically, the program instructions may include program code, which includes computer operation instructions. The memory 1003 may include a RAM and may further include a non-volatile memory, for example, at least one magnetic disk memory. The processor 1002 executes the program instructions stored in the memory 1003 and uses the data stored in the memory 1003 to realize the above functions and realize the intent processing methods provided in the above embodiments of this application.

[0380] 10 of this application, it can be understood that memory 1003 may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. Nonvolatile memory may be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be RAM, which acts as an external cache. By way of example and not limitation, many types of RAM may be used, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct Rambus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein includes, but is not limited to, these and any other suitable types of memory.

[0381] Based on the above embodiments, an embodiment of this application further provides a computer program, which, when executed on a computer, enables the computer to perform the methods provided in the above embodiments.

[0382] Based on the above embodiments, an embodiment of this application further provides a computer-readable storage medium, which stores a computer program, which, when executed by a computer, enables the computer to perform the method provided in the above embodiments.

[0383] A storage medium may be any available medium that can be accessed by a computer. The following provides examples, but is not limited to: A computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical or disk storage media, or other magnetic storage devices, or any other medium that can carry or store program code in the form of instructions or data structures and that can be accessed by a computer.

[0384] Based on the above embodiments, an embodiment of this application further provides a chip, which is configured to read a computer program stored in a memory to implement the method provided in the above embodiments.

[0385] Based on the above embodiments, an embodiment of this application provides a chip system. The chip system includes a processor configured to support a computer device in implementing functions related to the device in the above embodiments. In a possible design, the chip system further includes a memory configured to store programs and data required by the computer device. The chip system may include a chip, or may include a chip and other discrete components.

[0386] In conclusion, embodiments of this application provide an intent processing method, an apparatus, and a device. In the method, after transmitting first information indicating an impact on at least one KPI when a solution to a first intent is executed to a second device, the first device receives information from the second device indicating an execution suggestion for the first intent. In this manner, the second device may determine an execution suggestion for the first intent based on the impact on the at least one KPI when a solution to the first intent is executed. This avoids a case where, when a solution to the first intent is executed, the at least one KPI does not satisfy the second device's requirements for the at least one KPI in the network to which the device executing the first intent belongs, thereby ensuring the performance of the network to which the device executing the first intent belongs.

[0387] In various embodiments of this application, unless otherwise stated or unless there is a logical contradiction, the terms and / or descriptions in different embodiments are consistent and may be cross-referenced, and the technical features in different embodiments may be combined based on their internal logical relationships to form new embodiments.

[0388] Those skilled in the art should understand that the embodiments of this application may be provided as a method, a system, or a computer program product. Therefore, this application may take the form of a hardware-only embodiment, a software-only embodiment, or an embodiment having a combination of software and hardware. Furthermore, this application may take the form of a computer program product embodied in one or more computer-usable storage media (including, but not limited to, disk memory, CD-ROM, optical memory, etc.) containing computer-usable program code.

[0389] This application is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to this application. It should be understood that computer program instructions may be used to implement each process and / or each block in the flowcharts and / or block diagrams, and combinations of processes and / or blocks in the flowcharts and / or block diagrams. These computer program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or any other programmable data processing device to produce a machine, whereby the instructions, executed by the processor of the computer or any other programmable data processing device, produce an apparatus for implementing the particular functionality of one or more processes in the flowcharts and / or one or more blocks in the block diagrams.

[0390] These computer program instructions may be stored in a computer-readable memory that can direct a computer or any other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable memory generate an artifact that includes an instruction apparatus that implements a particular function in one or more processes in the flowcharts and / or one or more blocks in the block diagrams.

[0391] The computer program instructions may alternatively be loaded into a computer or other programmable data processing device such that a sequence of operations and steps are executed on the computer or other programmable device, thereby creating a computer-implemented process. Thus, the instructions executed on the computer or other programmable device provide steps for implementing a particular function in one or more procedures in the flowcharts and / or one or more blocks in the block diagrams.

[0392] It is obvious that those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. This application intends to cover these modifications and variations of this application, provided that they fall within the scope of protection defined by the following claims and their equivalent technologies.

Claims

1. 1. An intent processing method applied to a first device, comprising: determining first information, the first information including information indicative of a value of at least one key performance indicator (KPI) when a solution to the first intent is executed; transmitting the first information to a second device, wherein the first information is further used by the second device to determine information indicative of an execution suggestion for the first intent; receiving the information from the second device indicating the execution suggestion for the first intent; Including, The method, wherein the first device is an intent producer and the second device is an intent consumer.

2. The method of claim 1 , wherein the execution suggestion includes stopping execution of the first intent or executing a first solution of the first intent.

3. The method of claim 1 , wherein the solutions to the first intent are at least one solution that can satisfy the first intent.

4. The at least one KPI may be one of the following: The method of claim 1 , comprising at least one of throughput, throughput volume, power consumption, bandwidth utilization, delay, and packet loss rate.

5. 1. An intent processing method applied to a second device, comprising: receiving first information from a first device, the first information including information indicative of a value of at least one key performance indicator (KPI) when a solution to the first intent is executed; determining information indicative of an execution suggestion for the first intent; transmitting the information indicating the execution suggestion for the first intent to the first device; Including, The method, wherein the first device is an intent producer and the second device is an intent consumer.

6. The method of claim 5 , wherein the execution suggestion includes stopping execution of the first intent or executing a first solution of the first intent.

7. The method of claim 5 , wherein the solutions to the first intent are at least one solution that can satisfy the first intent.

8. before receiving the first information from the first device; transmitting information indicative of the at least one KPI to the first device. The method of claim 5 further comprising:

9. The at least one KPI may be one of the following: The method of claim 5 , comprising at least one of throughput, throughput volume, power consumption, and bandwidth utilization.

10. 1. An intent processing method, comprising: determining, by the first device, first information, the first information including information indicative of a value of at least one key performance indicator (KPI) when a solution to the first intent is executed; transmitting, by the first device, the first information to a second device; receiving, by the second device, the first information from the first device; determining, by the second device, information indicative of an execution suggestion for the first intent; transmitting, by the second device, the information indicating the execution suggestion for the first intent to the first device; Including, The method, wherein the first device is an intent producer and the second device is an intent consumer.

11. by the first device, before transmitting the first information to the second device; transmitting, by the second device, information indicative of the at least one KPI to the first device. The method of claim 10 further comprising:

12. 1. An apparatus including at least one processor and one or more memories, the one or more memories are coupled to the at least one processor; determining first information, the first information including information indicative of a value of at least one key performance indicator (KPI) when a solution to the first intent is executed; transmitting the first information to a second device, wherein the first information is further used by the second device to determine information indicative of an execution suggestion for the first intent; receiving the information from the second device indicating the execution suggestion for the first intent; storing programming instructions for execution by said at least one processor to perform The device is an intent producer and the second device is an intent consumer.

13. The apparatus of claim 12 , wherein the execution suggestion includes stopping execution of the first intent or executing a first solution of the first intent.

14. The one or more memories receiving information from the second device indicative of the at least one KPI; 13. The apparatus of claim 12, further comprising: storing the programming instructions for execution by the at least one processor to perform:

15. 1. An apparatus including at least one processor and one or more memories, the one or more memories are coupled to the at least one processor; receiving first information from a first device, the first information including information indicative of a value of at least one key performance indicator (KPI) when a solution to the first intent is executed; determining information indicative of an execution suggestion for the first intent; transmitting the information indicating the execution suggestion for the first intent to the first device; storing programming instructions for execution by said at least one processor to perform The first device is an intent producer and the device is an intent consumer.

16. The one or more memories transmitting information indicative of the at least one KPI to the first device.

16. The apparatus of claim 15, further comprising: storing the programming instructions for execution by the at least one processor to perform:

17. 1. An intent processing system, comprising: a first device configured to determine and transmit first information, the first information including information indicative of a value of at least one key performance indicator (KPI) when a solution to a first intent is performed; a second device configured to receive the first information, determine information indicative of an execution suggestion for the first intent, and transmit the information indicative of the execution suggestion for the first intent; and Including, the first device is further configured to receive the information; The system, wherein the first device is an intent producer and the second device is an intent consumer.

18. 1. A computer-readable storage medium, comprising: The computer-readable storage medium stores a computer program that, when executed on a computer, enables the computer to perform the method of any one of claims 1 to 4.

19. A computer-readable storage medium, comprising: The computer-readable storage medium stores a computer program that, when executed on a computer, enables the computer to perform the method of any one of claims 5 to 9.

20. A chip, The chip is coupled to a memory, the chip reading a computer program stored in the memory to perform the method of any one of claims 1 to 4.

21. A chip comprising: The chip is coupled to a memory, the chip reading a computer program stored in the memory to perform the method of any one of claims 5 to 9.

Images