Management method and apparatus for network management intent, and system

Abstract

A management method and apparatus for a network management intent, and a system. A consumption entity can indicate to a production entity a preference for solutions, and when an objective of an intent cannot be reached, the production entity can generate a solution that meets the preference, without the need to generate a solution that does not meet the preference. In this way, the invention facilitates preventing a production entity from generating solutions that a consumption entity will never consider, thereby reducing the waste of computing power resources, and alleviating the burden on the consumption entity.

Description

A management method, management device and system for network management intention

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on December 26, 2023, with application number 202311825090.3 and invention name “A management method, management device and system for network management intentions”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and more particularly, to a method, device, and system for managing network management intent. Background Art

[0003] With the advancement of network resource management, network management service consumers no longer need to directly manage network resources. Instead, they can send messages to network management service producers, enabling them to implement network management intents, aiming to achieve the desired performance targets for network devices within a specific scope. Furthermore, if the network management intent targets are not met, the network management service producer can generate potential solutions and recommend them to the network management service consumer.

[0004] Currently, there is a significant waste of computing resources in the process of generating solutions for network management service production entities. Therefore, how to reduce the waste of computing resources has become an urgent problem to be solved.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a method, device, and system for managing network management intentions, in order to reduce the waste of computing resources of production entities and reduce the burden on consumer entities.

[0007] On the first aspect, a method for managing network management intentions is provided, which can be executed by a production entity. Unless otherwise specified, "production entity" can refer to the production entity itself or a device that can support the production entity to realize its functions.

[0008] The method includes: receiving first information from a consumer entity, wherein the first information is used to indicate the consumer entity's preference for a solution, and the preference corresponds to a first network management intention; and in a case where a goal of the first network management intention cannot be achieved, sending second information to the consumer entity, wherein the second information is used to indicate one or more recommended solutions, and the one or more recommended solutions meet the preference.

[0009] The first information can also be described as: the first information is used to indicate the consumer entity's undesired intent expression, where the undesired intent expression corresponds to the first intent; or the first information is used to indicate the consumer entity's desired intent expression, where the desired intent expression corresponds to the first intent. One or more recommended solutions can also be described as: one or more recommended intent expressions. Intent expressions correspond to solutions, and intent expressions can be specific expressions of solutions.

[0010] Based on this approach, consuming entities can indicate their solution preferences to producing entities. This allows them to generate solutions that meet their preferences when the primary goal cannot be achieved, eliminating the need to generate solutions that do not. This helps prevent the producing entity from generating solutions that the consuming entity would never consider, thereby reducing wasted computing resources and alleviating the burden on the consuming entity.

[0011] With reference to the first aspect, in some possible implementations, the first information includes a first attribute of the first network management intention. The first attribute is an attribute that the consuming entity does not want to change, and the one or more recommended solutions do not change the first attribute; or the first attribute is a changeable attribute, and the one or more recommended solutions do not change attributes other than the first attribute.

[0012] The attribute that the consuming entity does not expect to change can also be described as: the attribute that the consuming entity expects or requires not to change, the attribute that the consuming entity expects to be guaranteed, or the attribute that the consuming entity expects to be maintained. The fact that one or more recommended solutions do not change the first attribute can also be described as: the fact that one or more recommended solutions guarantee or maintain the first attribute.

[0013] The first attribute is a changeable attribute, which can also be described as: an attribute that the consuming entity is allowed to change, an attribute that may not be guaranteed, or an attribute that may not be maintained. One or more recommended solutions do not change attributes other than the first attribute, which can also be described as: one or more recommended solutions change the first attribute, one or more recommended solutions only change the first attribute, one or more recommended solutions guarantee attributes other than the first attribute, or one or more recommended solutions maintain attributes other than the first attribute.

[0014] Based on the above implementation method, the consumer entity can reflect the consumer entity's preference for the solution by indicating the attributes that are not expected to be changed or the attributes that can be changed in the first intention, which helps to avoid the production entity from generating solutions that the consumer entity will not consider at all, thereby reducing the waste of computing resources and alleviating the burden on the consumer entity.

[0015] In combination with the first aspect or any implementation thereof, in some other possible implementations, the first attribute includes a target and / or an action object.

[0016] In combination with the first aspect or any implementation thereof, in some other possible implementations, the first attribute further includes a context.

[0017] In combination with the first aspect or any implementation thereof, in some other possible implementations, the method further includes: determining that a goal of the first network management intention cannot be achieved.

[0018] In combination with the first aspect or any implementation thereof, in some other possible implementations, the determination that the goal of the first network management intention cannot be achieved includes: after executing an action group for the first network management intention, determining that the goal of the first network management intention has not been achieved, wherein the action group includes one or more actions for managing the managed entity of the first network management intention.

[0019] Based on the above implementation, the production entity can determine that the goal of the first intention has not been achieved after the first intention is executed. In this way, the technical solution of the present application is applicable to the generation of recommended solutions for the intention that has been executed.

[0020] In combination with the first aspect or any implementation thereof, in some other possible implementations, the determining that the goal of the first network management intention cannot be achieved includes: performing a feasibility check on the first network management intention; when the result of the feasibility check is not feasible, determining that the goal of the first network management intention cannot be achieved.

[0021] Based on the above implementation, the production entity can determine that the goal of the first intention cannot be achieved based on the result of the feasibility check. In this way, the technical solution of the present application is applicable to the generation of recommended solutions for intentions that fail the feasibility check.

[0022] In combination with the first aspect or any implementation manner thereof, in some other possible implementation manners, sending the second information to the consuming entity includes: sending an intention report to the consuming entity, the intention report including the second information.

[0023] In combination with the first aspect or any implementation thereof, in some other possible implementations, the intention report includes at least one of the following reports: an intention satisfaction report, an intention conflict report, or an intention feasibility check report.

[0024] In combination with the first aspect or any implementation manner thereof, in some other possible implementation manners, obtaining the second information based on the first information includes: sending third information to the first network element based on the first information, wherein the third information is used to indicate the preference or the solution type corresponding to the preference, and the first network element includes a network twin production entity or a knowledge base; receiving the second information from the first network element.

[0025] In combination with the first aspect or any implementation manner thereof, in some other possible implementation manners, the sending of the third information to the first network element includes: sending a first message to the first network element, wherein the first message is used to request a feasibility check on the first network management intention, and the first message includes the third information; the receiving of the second information from the first network element includes: receiving a second message from the first network element, wherein the second message is used to indicate a result of the feasibility check, and the second message includes the second information.

[0026] In combination with the first aspect or any implementation thereof, in some other possible implementations, the receiving of the first information from the consuming entity includes: receiving a third message from the consuming entity, the third message being used to request creation of the first network management intention; wherein the third message includes the first network management intention, the first network management intention includes the first information, or the third message includes the first network management intention and the first information.

[0027] On the second aspect, a method for managing network management intentions is provided, which can be executed by a consumer entity. Unless otherwise specified, "consumer entity" can refer to the consumer entity itself or a device that can support the consumer entity to realize its functions.

[0028] The terms or features in the second aspect or its implementation that are the same as those in the first aspect or its implementation can refer to the first aspect or its implementation, and the technical effects of the second aspect or its implementation can refer to the technical effects in the first aspect or its implementation, and will not be repeated in the second aspect.

[0029] The method includes: sending first information to a production entity, the first information is used to indicate a consumer entity's preference for a solution, the preference corresponding to a first network management intention; receiving second information from the production entity, the second information is used to indicate one or more recommended solutions, the one or more recommended solutions satisfying the preference; and managing the first network management intention based on the second information.

[0030] In conjunction with the second aspect, in some possible implementations, the first information includes a first attribute of the first network management intention. The first attribute is an attribute that the consuming entity does not want to change, and the one or more recommended solutions do not change the first attribute; or the first attribute is a changeable attribute, and the one or more recommended solutions do not change attributes other than the first attribute.

[0031] In combination with the second aspect or any implementation thereof, in some other possible implementations, the first attribute includes a target or an object of action.

[0032] In combination with the second aspect or any implementation thereof, in some other possible implementations, the first attribute further includes a context.

[0033] In combination with the second aspect or any implementation thereof, in some other possible implementations, the receiving of the second information from the production entity includes: receiving an intention report from the production entity, the intention report including the second information.

[0034] In combination with the second aspect or any implementation thereof, in some other possible implementations, the intention report includes at least one of the following reports: an intention satisfaction report, an intention conflict report, or an intention feasibility check report.

[0035] In combination with the second aspect or any implementation thereof, in some other possible implementations, the sending of the first information to the production entity includes: sending a third message to the production entity, the third message being used to request creation of the first network management intention; wherein the third message includes the first network management intention, the first network management intention includes the first information, or the third message includes the first network management intention and the first information.

[0036] In a third aspect, a method for managing network management intent is provided. The method can be executed by a first network element. Unless otherwise specified, "first network element" can refer to the first network element itself or a device that can support the first network element to implement its functions. Optionally, the first network element can be a network twin production entity or knowledge base.

[0037] The terms or features in the third aspect or its implementation that are the same as those in the first aspect or its implementation can refer to the first aspect or its implementation, and the technical effects of the third aspect or its implementation can refer to the technical effects in the first aspect or its implementation, and will not be repeated in the third aspect.

[0038] The method includes: receiving third information from a production entity, wherein the third information is used to indicate a consumer entity's preference for a solution or a solution type corresponding to the preference, and the preference or the solution type corresponds to a first network management intention; determining second information based on the third information, wherein the second information is used to indicate one or more recommended solutions, and the one or more recommended solutions meet the preference; and sending the second information to the production entity.

[0039] In combination with the third aspect, in some possible implementations, the receiving of the third information from the production entity includes: receiving a first message from the production entity, wherein the first message is used to request a feasibility check on the first network management intention, and the first message includes the third information; and sending the second information to the production entity includes: sending a second message to the production entity, wherein the second message is used to indicate a result of the feasibility check, and the second message includes the second information.

[0040] On the fourth aspect, a method for managing network management intentions is provided, which can be executed by a production entity and a consumer entity. Unless otherwise specified, "production entity" or "consumer entity" may refer to the production entity or consumer entity itself, or may refer to a device that can support the production entity or consumer entity to realize its functions.

[0041] The method includes: a consumer entity sends first information, and a production entity receives the first information, wherein the first information is used to indicate the consumer entity's preference for a solution, and the preference corresponds to a first network management intention; in a case where the goal of the first network management intention cannot be achieved, the production entity sends second information, and the consumer entity receives the second information, wherein the second information is used to indicate one or more recommended solutions, and the one or more recommended solutions meet the preference; and the consumer entity manages the first network management intention based on the second information.

[0042] The steps performed by the production entity in the fourth aspect or its implementation method may refer to the first aspect or its implementation method, the steps performed by the consumption entity in the fourth aspect or its implementation method may refer to the second aspect or its implementation method, the terms or features in the fourth aspect or its implementation method that are the same as those in the first aspect or its implementation method may refer to the first aspect or its implementation method, and the technical effects of the fourth aspect or its implementation method may refer to the technical effects in the first aspect or its implementation method, and will not be repeated in the fourth aspect.

[0043] In a fifth aspect, a communication device is provided, which is configured to execute the method provided in any of the above aspects or implementations thereof. Specifically, the device may include units and / or modules, such as a processing unit and / or a transceiver unit, configured to execute the method provided in any of the above aspects or implementations thereof. The processing unit is configured to execute the processing steps in the method provided in any of the above aspects or implementations thereof. The transceiver unit is configured to execute the transceiver steps in the method provided in any of the above aspects or implementations thereof.

[0044] In one implementation, the device is a production entity, a consumption entity, or a first network element. When the device is a production entity, a consumption entity, or a first network element, the transceiver unit may be a transceiver, an input / output interface, or a communication interface; and the processing unit may be at least one processor. Optionally, the transceiver is a transceiver circuit. Optionally, the input / output interface is an input / output circuit.

[0045] In another implementation, the device is a chip, chip system, or circuit used in a production entity, a consumption entity, or a first network element. When the device is a chip, chip system, or circuit used in a production entity, a consumption entity, or a first network element, the transceiver unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.

[0046] In a sixth aspect, a communication device is provided, which includes: a memory for storing programs; and at least one processor for executing computer programs or instructions stored in the memory to execute the method provided by any one of the above aspects or its implementation.

[0047] In one implementation, the device is a production entity, a consumption entity, or a first network element.

[0048] In another implementation, the device is a chip, a chip system, or a circuit used in a production entity, a consumption entity, or a first network element.

[0049] In a seventh aspect, a communication device is provided, comprising: at least one processor and a communication interface, wherein the at least one processor is configured to retrieve a computer program or instruction stored in a memory through the communication interface to execute the method provided by any one of the above aspects or implementations thereof. The communication interface may be implemented in hardware or software.

[0050] In one implementation, the device further includes the memory.

[0051] In an eighth aspect, a processor is provided for executing the methods provided in the above aspects.

[0052] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be understood as operations such as processor output, reception, and input, or as sending and receiving operations performed by the radio frequency circuit and antenna. This application does not limit this.

[0053] In a ninth aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, wherein the program code includes a method for executing any one of the above aspects or its implementation.

[0054] In a tenth aspect, a computer program product comprising instructions is provided, which, when run on a computer, enables the computer to execute the method provided by any one of the above aspects or its implementation.

[0055] In an eleventh aspect, a chip is provided, comprising a processor and a communication interface, wherein the processor reads instructions stored in a memory through the communication interface and executes the method provided by any of the above aspects or implementations thereof. The communication interface may be implemented in hardware or software.

[0056] Optionally, as an implementation method, the chip also includes a memory, in which a computer program or instruction is stored, and the processor is used to execute the computer program or instruction stored in the memory. When the computer program or instruction is executed, the processor is used to execute the method provided by any of the above aspects or its implementation methods.

[0057] When the method provided in this application is executed by a chip, this application does not limit the number of chips that implement the method. For example, the method can be executed by one chip or by two or more chips. Furthermore, when the number of chips implementing the method of this application is two or more, the chip manufacturers are not limited and can be the same manufacturer or different manufacturers.

[0058] In a twelfth aspect, a communication system is provided, comprising at least one of the production entity, consumption entity or first network element described above.

[0059] In a thirteenth aspect, a computer program is provided, which, when executed on a computer, enables the method provided by any one of the above aspects or its implementation to be executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] FIG1 is a schematic structural diagram of an information object class (IOC).

[0061] FIG2 is a schematic structural diagram of an intent reporting IOC.

[0062] FIG3 is a schematic structural diagram of a communication system applicable to an embodiment of the present application.

[0063] FIG4 is a schematic flowchart of a method 300 for managing network management intent provided in an embodiment of the present application.

[0064] FIG5 is a schematic flowchart of a method 400 for managing network management intent provided in an embodiment of the present application.

[0065] FIG6 is a schematic flowchart of a method 500 for managing network management intent provided in an embodiment of the present application.

[0066] FIG7 is a schematic structural diagram of a device provided in an embodiment of the present application.

[0067] FIG8 is another schematic structural diagram of the device provided in an embodiment of the present application.

[0068] FIG9 is a schematic diagram of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0069] Before introducing the embodiments of the present application, the following explanation is made.

[0070] "For indicating" or "indicating" can include direct indication and indirect indication, or "for indicating" or "indicating" can be explicitly and / or implicitly indicated. The various numerical numbers such as first, second, etc. are only used for the convenience of description and are not used to limit the scope of the embodiments of this application, such as distinguishing different messages, different information, etc. "Pre-definition" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in the device. This application does not limit its specific implementation method. The "protocol" involved may refer to a standard protocol in the field of communications, such as the Long Term Evolution (LTE) protocol, the New Radio (NR) protocol, and related protocols used in future communication systems. This application does not limit this. Words such as "exemplary", "for example", "exemplarily", "as (another) example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as an "example" in this application should not be construed as being preferred or advantageous over other embodiments or design schemes. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized. "Multiple" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c. Where a, b and c can be single or multiple. The description involving network element A sending a message, information or data to network element B, and network element B receiving a message, information or data from network element A, is intended to indicate to which network element the message, information or data is to be sent, and does not limit whether they are sent directly or indirectly via other network elements. Descriptions such as "when...", "in the case of...", "if...", and "if" all mean that the device will take corresponding actions under certain objective circumstances. They do not limit the time, nor do they require the device to make judgments when implementing them, nor do they imply the existence of other limitations.

[0071] In addition, the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

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

[0073] To facilitate understanding of the embodiments of the present application, some terms involved in the embodiments of the present application are first explained.

[0074] 1. Network management and network management services

[0075] 1.1 Network Management

[0076] Network management refers to the management of network resources, including but not limited to monitoring, controlling and recording the performance and usage of network resources, and issuing management action groups to network resources (such as devices in the network) based on the detected network status to enable the network to operate effectively. Exemplarily, network management can be at least one of monitoring, testing, configuring, analyzing, evaluating or controlling network resources. Network management can also be timely reporting and handling when network failures occur, and coordinating and maintaining the efficient operation of the network system. Among them, network resources are the objects of network management, which can also be called network objects or managed entities. Exemplarily, network resources can be base station equipment, routers, switches, core network equipment, etc. This is not particularly limited in the embodiments of the present application. For the convenience of description, the embodiments of the present application are described using managed entities as an example, but they can be replaced with other objects of network management.

[0077] 1.2 Network Management Services

[0078] A network management service refers to a service that provides network management functions. The service producing entity usually provides the network management functions to the service consuming entity through a network interface (eg, a service-based interface).

[0079] 2. Network Management Intent (abbreviated as Intent)

[0080] A network management intent refers to a demand for network management services by a network management service consuming entity, and may also be referred to as a network management service demand. This term is not limited in the embodiments of the present application. For example, the network management intent may be an optical dedicated line service intent or an energy-saving intent, such as the intent defined in 3rd Generation Partnership Project (3GPP) standard specification 28.312.

[0081] The intent-based interaction scenario mainly includes two roles, namely the network management service production entity and the network management service consumption entity. Among them, the network management service production entity can also be called the network management service provision entity, network management provider, or intent provider (intent provider), or intent handler (intent handler), etc. The network management service consumption entity can also be called the network management service consumer, or intent consumer (intent consumer), or intent owner (intent owner), etc. Among them, the network management service consumption entity can be the caller of the network management service, and can perform operations such as creating, modifying, deleting, and querying network management intent expressions. The network management service consumption entity can be configured in the network management system (network management system, NMS), or element management system (element management system, EMS), or network equipment (network equipment, NE). The network management service consumption entity can be a management function, or a management function entity, or a management entity, or a network equipment, or a network element, etc., which is not limited in this application. A more detailed description of the network management service production entity and the network management service consumption entity can be found in Figure 3 below.

[0082] Intents can be applied to network systems to achieve desired performance targets for specific network devices within a specific scope. Intents can express expectations for network systems through formal specifications and descriptive information. Formal specifications can refer to the intent's specific syntax or semantics, while descriptive information can describe at least one of the intent's requirements, goals, or constraints.

[0083] An intent can include at least one intent expectation. Each intent expectation can represent the performance requirements of a network management service consuming entity for a specific network object. An intent expectation can consist of at least one expected target and at least one expected object. Each expected target can represent the performance requirements of the network management service consuming entity for a specific attribute of the expected object. The expected object can be the network object on which the intent acts, and the expected object can also be called the action object. For example, an intent expectation can include two expected targets, one of which is an average downlink throughput greater than 5 Mbps and the other is an end-to-end latency less than 10 milliseconds. If the average downlink throughput of the expected object is greater than 5 Mbps, then the downlink throughput target is met. If the end-to-end latency of the expected object is less than 10 milliseconds, then the latency target is met. If both expected targets of an intent expectation are met, then the intent expectation is met. If one or more intent expectations are not met, or if one or more expected targets are not met, then the intent is not met.

[0084] In the embodiments of the present application, the intention, intention expectation or expected goal is met or not met, which can also be described as: the intention, intention expectation or expected goal is achieved or not achieved, the intention, intention expectation or expected goal is realized or not achieved, or the intention, intention expectation or expected goal is achieved or not achieved, etc.

[0085] An intent may also include an intent context. The intent context may represent constraints or conditions imposed by the network management service consumer on the intent. For example, the network management service consumer may constrain the duration of the intent through the intent context.

[0086] Intents may also include an expected context. The expected context may represent the constraints or conditions that a network management service consumer expects for an intent. For example, the network management service consumer may use the expected context to constrain the expected duration of the intent.

[0087] The intent may also include a target context, which may represent the constraints or conditions imposed by the network management service consumer on a desired target. For example, the network management service consumer may constrain the duration of the desired target through the target context.

[0088] The intent may also include an object context, which may indicate constraints or conditions on the network object to be acted upon by the network management service consumer. For example, the network management service consumer may use the object context to indicate the area where the intended network object is located.

[0089] For example, the intent may be expressed as:

[0090] For example, an intent can be expressed as: "Ensure that the handover failure rate of a certain cell is less than 2% when the load is greater than 80%." "Cell" is the expected object or action object, and "Cell" can correspond to Expectation Object O; "Load > 80%" is the target context, and "Load > 80%" can correspond to Target Context (such as C_1); "Handover failure rate < 2%" is the expected target, and "Handover failure rate < 2%" can correspond to Expectation Target (such as T_1).

[0091] The intent expectation, expected target and intent context introduced above can be used as information elements in the IOC in the intent creation request. The network management service consumer entity can express its demand for network management services by sending the above information elements to the network management service producer entity.

[0092] The information elements in the intent IOC can use a specific structure to express the demand for network management services.

[0093] Exemplarily, FIG1 shows a schematic structural diagram of an intention IOC.

[0094] Referring to Figure 1 , the intent IOC includes an intent expectation and an intent context. The intent expectation includes an expected object, an expected target, and an expected context. The expected object includes an expected object context, and the expected target includes a target context. It is understood that non-contextual information elements (such as intent IOC, intent expectation, expected object, or expected target) can include contextual information elements (such as intent context, expected object context, target context, expected context, etc.), and contextual information elements can be used to constrain non-contextual information elements.

[0095] It is understood that Figure 1 is a schematic illustration of the relationship between attributes in an intent IOC. Based on network management service requirements, the intent IOC may also include other attributes, and this application does not specifically limit this. It is also understood that this application does not specifically limit the number of attributes of the same type. For example, an intent IOC may include one or more parallel intent expectation attributes, and an intent expectation may also include one or more parallel desired target attributes.

[0096] 3. Network Management Intent Template

[0097] The network management intent template refers to the templated description information of the network management intent, which can also be called the network management service requirement template. The embodiment of the present application does not limit this name. The intent template can be used to specify the syntax and semantics of the various attribute expressions introduced above. For example, the intent template can specify the field type, value type, etc. that can be used for each attribute in the IOC. As an example, the intent template can include intent expectation description information for specifying how the intent expectation is expressed. The intent expectation description information can specify the type of expected target attributes that the intent expectation can contain, such as latency, bandwidth, maximum number of users, etc. The intent expectation description information can also specify the field type of each expected target, such as the field type of the expected target for latency is a string, the field type of the expected target for bandwidth is a string, and the field type of the expected target for the maximum number of users is an integer. As another example, the intent template can also include intent context description information that specifies how the intent context and the expected context are expressed. The intent context description information can be used to specify the field type of the intent context, etc., and the present application does not specifically limit this.

[0098] 4. Intent Expression

[0099] In the embodiment of the present application, the intent expression is an information formula that expresses the network management service intent, and can be the instantiation result of the network management intent template. Consumers of network management intent can instantiate the intent IOC according to the intent template to generate an intent expression, and the instantiated intent expression can be used for specific network services. For example, the intent expression can be represented by a list of a set of attribute and value key-value pairs (for example, a set of [attribute, value]) of the network management service intent.

[0100] Exemplarily, the intent expression includes a performance indicator information instance, a network object information instance, and a context information instance.

[0101] For example, a performance indicator information instance may include the value or value range of the target indicator requirement corresponding to the performance indicator information. For example, if the target indicator requirement corresponding to a performance indicator information template includes a bandwidth parameter, a performance indicator information instance may include a bandwidth parameter value of 20 Mbps, or a bandwidth parameter value range of 10 Mbps to 15 Mbps. For example, if the target indicator requirement corresponding to a performance indicator information template includes a latency parameter, a latency parameter instance may include a latency parameter value of 2 s, or a latency parameter value range of 1 s to 5 s.

[0102] The target network object indicated by the network object information instance is the instantiation result of the target network object indicated by the network object information template. Exemplarily, the target network object indicated by the network object information instance is one of the target network objects indicated by the network object information template, i.e., one of the physical or logical entities that implement the network management service. In this case, the network object information instance indicates a specific network object. For example, the network object information template indicates a network service, while the network object information instance indicates an energy-saving service.

[0103] The context information instance is used to indicate the constraints of the network management intent expression. Exemplarily, the context information instance includes the constraint parameters of the network management intent expression. For example, the context information instance may include the source and sink information corresponding to the target network object indicated by the network object instance.

[0104] Intent expectation information instances include performance indicator information instances and network object information instances.

[0105] In the embodiment of the present application, the "intention" transmitted through the message refers to the intention expression.

[0106] 5. Network Management Intent Examples

[0107] A network management intent instance refers to a network management intent processing process created locally by a network management service provider entity based on a received network management intent expression (e.g., a performance indicator information instance, a network object information instance, a context information instance).

[0108] The network management intent processing process is used to process network management intent expressions. For example, the network management intent processing process may include an identifier that identifies the process; computing resources that are used to perform operations such as network management intent translation and database query (e.g., a semantic knowledge base); and storage resources that are used to store network management intent expressions and network management intent translation results.

[0109] Among them, network management intent translation is used to convert the network management intent expression into a corresponding management action group, which can be an instruction acting on a physical entity or a logical entity, such as adjusting the antenna tilt angle of a base station or turning on the energy-saving switch of a cell.

[0110] 6. Network Management Action Group (actions)

[0111] A network management action group is one or more network management actions generated by a network management service producer based on an intent expression. The network management service producer executes one or more network management actions to fulfill the intent of a network management service consumer. A network management action group can also be referred to as a management operation or an intent operation. A network management action group can be a set of operational instructions for a desired object (e.g., a physical or logical entity in the network system intended to act upon), consisting of one or more instructions. For example, adjusting the antenna tilt of a base station or turning on the energy-saving switch of a cell can be performed.

[0112] Based on intent expressions, network management service production entities can generate multiple management action groups. During execution, network management service production entities can select some of these management action groups to execute at a time. In other words, the management action groups generated by network management service production entities based on the intent expression are optional operations that can be used to achieve the intent. A network management service production entity may select one of these network management action groups to execute in order to achieve the intent, or it may select multiple network management action groups to execute in order to achieve the intent.

[0113] 7. Intent Report

[0114] The intent report is used to describe the intent report information from the network management service production entity to the network management service consumption entity. Based on the intent report, the network management service production entity can provide the network management service consumption entity with some intent-related information, such as information that the network management service consumption entity needs to monitor.

[0115] The intent report IOC may include one or more of an intent fulfillment report (IntentFulfilmentReport), an intent conflict report (IntentConflictReport), or an intent feasibility check report (IntentFeasibilityCheckReport).

[0116] An intent achievement report, which may also be referred to as an intent satisfaction report, an intent realization report or intent realization information, is used to describe the evaluation of the degree of achievement of a specific aspect of the intent of a network management service production entity. An intent achievement report may include achievement information of a specific aspect of the intent, and the achievement information is used to describe the achievement status of a specific aspect, and the achievement status may be achieved or not achieved. A specific aspect may include one or more of an intent, an intent expectation and an expected target, that is, an intent achievement report may include one or more of the intent achievement information (intentFulfilmentInfo), the achievement information of the intent expectation of the intent (expectationfulfilmentInfo) or the achievement information of the expected target of the intent (targetfulfilmentInfo), such as an intent achievement report only including the achievement information of the intent, or an intent achievement report only including the achievement information of the expected target of the intent, or an intent achievement report including the achievement information of the intent, the achievement information of the intent expectation of the intent and the achievement information of the expected target of the intent. For example, an intent includes an intent expectation, which may include an expected target A and an expected target B, where expected target A has been achieved and expected target B has not been achieved. In the intention achievement report, the achievement status of the intention is not achieved, the achievement status of the intention expectation is not achieved, the achievement status of the expected target A is achieved, and the achievement status of the expected target B is not achieved. The achievement information of the intention expectation can also be called the intention expectation achievement result (ExpectationFulfilmentResult), and the achievement information of the expected target can also be called the intention expectation achievement result (TargetFulfilmentResult). The intention achievement report can also include the realization value of the expected target and the optional predicted value of the expected target. The realization value of the expected target is used to describe the current value of the expected target. The predicted value of the expected target is used to describe the final realization value of the expected target evaluated by the network management service production entity. Optionally, when the achievement status is not achieved, the intention achievement report can also include the specific status of not achieved. The specific status of not achieved can refer to the stage where the achievement status occurs, such as the stage where the intention is just created, the stage where the intention is suspended due to a conflict, or the stage where the action group corresponding to the intention is executed.

[0117] Intent conflict reports, also known as intent conflict information, describe detected intent conflicts. Intent conflict information includes the conflict type and possible conflict resolution options. Conflict types include, but are not limited to, conflicts between different intents (intent conflict), conflicts between different expectations of the same intent (expectation conflict), and conflicts between different desired targets of the same intent (target conflict).

[0118] An intent feasibility check report, also known as intent feasibility check information, indicates whether an intent is feasible or infeasible. Upon receiving an intent creation or modification request from a network management service consumer, a network management service producer can automatically perform an intent feasibility check, thereby generating an intent feasibility check report.

[0119] A network management service consumer can obtain intent reports from a network management service producer by querying or subscribing. For example, a network management service consumer can query intent reports using the "getMOIAttributeValue" operation to obtain intent reports. Another example is that a network management service consumer can subscribe to the "MOIAttributeValueChanges" notification to obtain intent reports.

[0120] Exemplarily, FIG2 shows a schematic structural diagram of an intention reporting IOC.

[0121] Referring to Figure 2, the Intent Reporting IOC includes an Intent Achievement Report, an Intent Conflict Report, and an Intent Feasibility Check Report. The Intent Achievement Report includes the Intent Expected Achievement Results. The Intent Expected Achievement Results include the Target Achievement Results. It will be appreciated that Figure 2 is a schematic illustration of the relationship between the attributes in the Intent Reporting IOC. Based on network management service requirements, the Intent Reporting IOC may also include other attributes, which are not specifically limited in this application.

[0122] 8. Intent Report Template

[0123] An intent report template refers to the templated description information of an intent report, which is used to specify the syntax and semantics of the intent report. For example, the intent report template can specify the field types or value types that can be used for each attribute in the intent report IOC. As an example, the intent report template can include one or more of the following: intent achievement description information for specifying how the intent achievement report is expressed, intent conflict description information for specifying how the intent conflict report is expressed, and intent feasibility check description information for specifying how the intent feasibility check report is expressed. The intent achievement description information can describe the field types and value types that can be used for each attribute contained in the intent achievement report. For example, the types of the achievement information attribute include intent achievement information, intent expected achievement information, and expected target achievement information. The optional values ​​of the achievement information are achieved or not achieved, and the value type is an integer. For example, the type of the expected target attribute includes throughput, and the value type of the achieved value of the throughput is an integer. The intent conflict description information is used to indicate how the schematic conflict report is expressed, such as the optional attributes and types of each field of the intent conflict. For example, the optional attribute of the intent conflict report is the conflict type, and the conflict types include intent conflict, expectation conflict, and target conflict. The intention feasibility check description information is used to indicate how the intention feasibility check report is presented.

[0124] 9. Intent Report Expression

[0125] The intent report expression is an information formula that expresses the network management service intent report, and can be the instantiation result of the intent report template. The intent report expression contains the network management service consumer entity's demand for monitoring intent and the report information that reflects the current intention achievement status. The network management service production entity can instantiate the intent report IOC according to the intent report template to generate an intent report expression. Exemplarily, the intent report expression includes the achievement information of the current intent and the realization value of the expected target. For example, if the expected target of the intent is a throughput rate > 10Mbps, based on the current intention achievement status, the network management service production entity will report the intent achievement information as: achieved, and the realization value of the expected target is 12Mbps.

[0126] 10. Intent Reporting Example

[0127] An intent report instance is an intent report processing process created locally by a network management service producer based on an intent report expression. An intent report instance can be automatically created by a network management service producer when creating a network management intent. When a network management service producer deletes a network management intent based on a request from a network management service consumer, the intent report instance corresponding to the network management intent is also deleted. Network management service consumers do not create or delete intent report instances.

[0128] The above describes the relevant terms involved in the embodiments of the present application. The following describes the application scenarios to which the embodiments of the present application are applicable in conjunction with Figure 3.

[0129] Figure 3 is a schematic structural diagram of a communication system applicable to an embodiment of the present application. First, the devices that may be involved in the communication system are described.

[0130] 1. Network Management Service Consuming Entity 210: The entity that invokes network management is called a network management service consuming entity. Network Management Service Consuming Entity 210 can be used to invoke management services, or intent services, to manage the network system. For example, Network Management Service Consuming Entity 210 can instantiate an intent template, set intent IOCs, generate intent expressions, and send these intent expressions to Network Management Service Producing NE 220 to implement expectations for the network system.

[0131] The network management service consumption entity 210 may also be referred to as a network management service consumption network element, a network management service consumer, an intent management service consumer, an intent service consumer, an intent consumer or an intent owner, etc. In future communication systems, the network management service consumption entity may also have other names, which is not specifically limited in this application.

[0132] The capabilities or functions of the network management service consumption entity can be deployed on a certain network element, which is called a network management service consumption network element; the capabilities or functions of the network management service consumption entity can also be deployed on other devices, which is not limited by the embodiments of the present application; for convenience of description, the embodiments of the present application take the network management service consumption entity as an example, but they can all be replaced by other devices that are deployed with the capabilities or functions of the network management service consumption entity.

[0133] 2. Network Management Service Producer 220: The entity that provides network management services is called a network management service producer. Network Management Service Producer 220 can be used to provide network management services. For example, Network Management Service Producer 220 can receive intent expressions from Network Management Service Consumer 210 and perform intent translation, intent management, and intent execution and maintenance based on the intent expressions.

[0134] The network management service production entity 220 may also be referred to as a network management service production network element, an intent management service provider, an intent service provider, a network management service producer, an intent provider, an intent handler, etc. In future communication systems, the network management service production entity may also have other names, and this application does not specifically limit this.

[0135] The capabilities or functions of the network management service production entity can be deployed on a certain network element, which is called the network management service production network element; the capabilities or functions of the network management service production entity can also be deployed on other devices, which is not limited by the embodiments of the present application; for convenience of description, the embodiments of the present application take the network management service production entity as an example, but they can all be replaced by other devices that are deployed with the capabilities or functions of the network management service production entity.

[0136] The above-mentioned entity can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (for example, a cloud platform). It is understandable that the above-mentioned entity can be implemented by one device, or it can be implemented by multiple devices together. In addition, the above-mentioned entity can also be a functional module within a system, such as a network management system (NMS), an equipment management system (EMS), or a functional module within a device, such as one or more functional modules within a network equipment (NE), and the network equipment can be a base station or a core network element.

[0137] As an example, the network management service consumption entity 210 can be deployed in the NMS, and the network management service production entity 220 can be deployed in different EMSs. The interaction between the network management service consumption entity 210 and the network management service production entity 220 can be carried out through information exchange through the interface between the NMS and the EMS.

[0138] As another example, the network management service consumption entity 210 can be deployed in the EMS, and the network management service production entity 220 can be deployed in different NEs. The interaction between the network management service consumption entity 210 and the network management service production entity 220 can be carried out through information exchange through the interface between the NMS and the EMS.

[0139] Optionally, the above-mentioned communication system may further include other devices or network elements, such as a knowledge base or a network twin service production entity. The network twin service production entity may be, for example, a network digital twin (NDT) system or an entity deployed with an NDT system, which may be used to provide network management services.

[0140] The solution of the present application can also be applied to other systems including corresponding entities, which is not limited in the present application and is not specifically limited in the embodiments of the present application.

[0141] For the sake of simplicity, the following description will refer to the network management intention as intention, the network management service consumption entity as consumption entity, the network management service production entity as production entity, and the expected goal as goal.

[0142] Currently, when the intention is not achieved due to conflicts or other reasons, the producing entity can generate possible solutions based on the current network status and recommend them to the consuming entity. Common solutions fall into three categories:

[0143] 1) suspend the whole intent;

[0144] 2) Recommend a new intent, such as adding a recommendation expectation or goal, or terminating a part of the intent;

[0145] 3) Suggest alternative intent fulfillment, such as updating the execution time of the intent.

[0146] For example, the intent goal is to ensure an uplink throughput of greater than 20 Mbps at a particular venue. The producing entity monitors the current network status and discovers that this goal is unattainable. Based on the current network status, the producing entity calculates the maximum achievable uplink throughput to be 15 Mbps. It also predicts future network conditions and estimates that the intent goal will be achieved in 5 hours. The producing entity can generate and recommend the following possible solutions to the consuming entity: 1. Terminate the intent; 2. Recommend a new intent with the goal of ensuring an uplink throughput of greater than 15 Mbps; 3. Update the intent's execution time to 5 hours from now.

[0147] However, the solutions generated by the production entity may include many useless solutions. Useless solutions can be understood as solutions that fail to meet the business needs of the consumer entity, that is, solutions that fail to meet the specific needs of the consumer entity in a specific business scenario, and solutions that the consumer entity would not consider at all. For example, in the case of a drone natural gas pipeline inspection scenario, when this intent cannot be achieved, the production entity recommends a solution with a new action object, which is a useless solution because the drone needs to inspect along the pipeline, and the action object cannot be changed. The generation of useless solutions consumes the production entity's computing resources, resulting in a waste of computing power. At the same time, useless solutions make it more difficult for the consumer entity to make a choice, increasing the burden on the consumer entity.

[0148] In response to the above problems, the present application provides a management method, management device and system for network management intention, in order to reduce the waste of computing resources of production entities and reduce the burden on consumer entities.

[0149] The following describes the method embodiments of the present application.

[0150] FIG4 is a schematic flow chart of a method 300 for managing network management intent provided in this application.

[0151] The method shown in FIG4 can be performed by a production entity and a consumer entity. Unless otherwise specified, "production entity" or "consumer entity" can refer to the production entity or consumer entity itself, or to a device that supports the production entity or consumer entity in performing its functions. For ease of description, the following description uses the production entity and consumer entity. Method 300 includes at least part of the following content.

[0152] Step 301: The consumer entity sends first information to the producer entity. Correspondingly, the producer entity receives the first information from the consumer entity.

[0153] The first information is used to indicate the consumer entity's preference for the solution, and the preference corresponds to the first intention.

[0154] The first intent can be of various types. The type of the first intent can be related to the goal included in the first intent. For example, the goal of the intent includes a performance indicator value reaching a corresponding performance indicator range. When the performance indicator is a throughput indicator, such as an average downlink throughput greater than or equal to 5 Mbps, the intent can be called a throughput intent; when the performance indicator is an energy saving indicator, such as energy saving greater than or equal to 10 kilowatts, the intent can be called an energy saving intent.

[0155] This preference corresponds to the first intent and can be understood as: this preference applies to the first intent, or in other words, it is used when the goal of the first intent cannot be achieved. The solution can be a solution to the situation where the goal of the first intent cannot be achieved, such as the aforementioned termination of the entire first intent, the recommendation of a new intent, or the recommendation of other feasible intention implementations. The preference for the solution can be understood as the consumer entity's preference for the solution to the situation where the goal of the first intent cannot be achieved. The consumer entity can use this preference to restrict the producer entity from generating solutions that do not meet this preference.

[0156] The embodiments of the present application do not limit the implementation method of the first information. In one possible implementation method, the first information may include the first attribute of the first intention. Among them, the first attribute is an attribute that the consumer entity does not expect to change. In this case, the consumer entity prefers a solution that does not change the first attribute, that is, the consumer entity expects the production entity to recommend a solution that meets the first attribute or a solution that does not change the first attribute when the first intention cannot be achieved. Alternatively, the first attribute is a changeable attribute. If the first intention also includes attributes other than the first attribute, the embodiments of the present application do not limit whether the attributes other than the first attribute can be changed. Taking the example that only the first attribute of the first intention can be changed, the consumer entity prefers a solution that does not change the attributes other than the first attribute or a solution that only changes the first attribute, that is, the consumer entity expects the production entity to recommend a solution that meets the attributes other than the first attribute, a solution that does not change the attributes other than the first attribute, or a solution that only changes the first attribute when the first intention cannot be achieved.

[0157] It should be noted that attributes that a consuming entity does not expect to change can also be described as attributes that the consuming entity expects or requires not to change, attributes that the consuming entity expects to be guaranteed, or attributes that the consuming entity expects to maintain. The first attribute is a changeable attribute, which can also be described as attributes that the consuming entity allows to change, attributes that may not be guaranteed, or attributes that may not be maintained.

[0158] The embodiments of the present application do not limit the specific type of the first attribute. Exemplarily, the first attribute may include at least one of a target, an object, or a context. The target may also be referred to as an expected target, and the object may also be referred to as an expected object. The object may be used to determine the intended expected managed entity. The first attribute may include at least one of a target, an object, or a context, and may also be described as: the value of the first attribute may be a target, an object, a context, or any combination of the three, or the value of the first attribute corresponds to a target, an object, a context, or any combination of the three.

[0159] Example 1: Taking the first attribute as an attribute that the consumer entity does not expect to change, when the first attribute is a target, it indicates that the consumer entity does not accept the downgrade of the intent target when the first intent cannot be achieved, or in other words, when the first intent cannot be achieved, the consumer entity expects the producer entity to recommend a solution that meets the target, that is, the consumer entity expects the producer entity to recommend a solution with the same target. For example, for the drone material delivery intent, the intent target is to ensure that the drone uplink bandwidth is greater than 300kbps, and the action object is the TAC area passed by the flight path. The first attribute is the target. After the intent is issued, the producer entity monitors the network status of the TAC area passed by the flight path and finds that the intent target cannot be achieved. Since the consumer entity's preference for solutions indicates that the intent target cannot be changed (that is, the goal of ensuring that the drone uplink bandwidth is greater than 300kbps cannot be changed), the producer entity can recommend other action objects, for example, updating the action object of the intent to another TAC area (such as a feasible TAC area near the infeasible TAC area). When the first attribute is the action object, it indicates that when the first intent cannot be achieved, the consumer entity expects the producer entity to recommend a solution that meets the action object, that is, the consumer entity expects the producer entity to recommend a solution with the same action object. For example, for the drone natural gas pipeline inspection intention, the goal of the intention is to ensure that the uplink throughput is greater than 25Mbps, and the target is the TAC area through which the flight path passes. The first attribute is the target. After the intention is issued, the production entity monitors the network status of the TAC area through which the flight path passes and finds that the goal of the intention cannot be achieved. Since the consumer entity's preference for the solution indicates that the target cannot be changed, the production entity does not change the TAC area as the target, but changes the goal of the intention. For example, it can be recommended to update the goal of the intention to ensure that the uplink throughput is greater than 20Mbps.

[0160] Example 2: Taking the case where the first attribute is a changeable attribute and the attributes other than the first attribute are unchangeable attributes, when the first attribute is a target, it indicates that when the first intent cannot be achieved, the consumer entity expects the producer entity to recommend a solution that meets the attributes other than the target. In other words, the consumer entity expects the producer entity to recommend a solution with the attributes other than the target unchanged. For example, for the drone natural gas pipeline inspection intent, the intent's goal is to ensure an uplink throughput greater than 25Mbps, and the target is the TAC area passed by the flight path. The first attribute is the target. After the intent is issued, the producer entity monitors the network status of the TAC area passed by the flight path and finds that the intent's goal cannot be achieved. Since the consumer entity's preference for solutions indicates that the intent's goal is changeable (i.e., the goal of ensuring an uplink throughput greater than 25Mbps is changeable, but the target TAC area is unchangeable), the producer entity can change the intent's goal without changing the target area. For example, it recommends updating the intent's goal to ensuring an uplink throughput greater than 20Mbps, while keeping the target TAC area unchanged. When the first attribute is the action object, it indicates that if the first intent cannot be achieved, the consumer entity expects the producer entity to recommend a solution that meets the attributes other than the action object. In other words, the consumer entity expects the producer entity to recommend a solution with the attributes other than the action object unchanged. For example, for the drone material delivery intent, the intent goal is to ensure the drone's uplink bandwidth is greater than 300kbps, the action object is the TAC area that the flight path passes through, and the first attribute is the action object. After the intent is issued, the producer entity monitors the network status of the TAC area that the flight path passes through and finds that the intent goal cannot be achieved. Because the consumer entity's preference for solutions indicates that the intent's action object can be changed (i.e., the action object TAC area can be changed, while the goal of ensuring the drone's uplink bandwidth is greater than 300kbps cannot be changed), the producer entity can change the action area without changing the intent's goal. For example, it can recommend updating the intent's action object to another TAC (such as a feasible TAC area near the infeasible TAC area) while keeping the goal of ensuring the drone's uplink bandwidth is greater than 300kbps unchanged.

[0161] It should be noted that the first attribute can be for the entire intention, or for a certain intention expectation or a certain expected goal of the intention, without limitation. For example, taking the first attribute as the action object and the first attribute as the attribute that the consumer entity does not expect to change as an example, when the first attribute is for the entire intention, the first attribute represents the action objects of all intention expectations of the intention, that is, the consumer entity expects the production entity to recommend a solution that does not change the action objects of all intention expectations when the intention cannot be achieved; when the first attribute is for a certain intention expectation, the first attribute represents the action object of the intention expectation, that is, the consumer entity expects the production entity to recommend a solution that does not change the action object of the intention expectation when the intention cannot be achieved. For example, taking the first attribute as the target and the first attribute as the attribute that the consumer entity does not expect to change as an example, when the first attribute is for the entire intention, the first attribute represents all expected goals of the intention, that is, the consumer entity expects the production entity to recommend solutions that do not change all expected goals when the intention cannot be achieved; when the first attribute is for a certain intention expectation, the first attribute represents all expected goals expected by the intention, that is, the consumer entity expects the production entity to recommend solutions that do not change all expected goals expected by the intention when the intention cannot be achieved; when the first attribute is for a certain expected goal, the first attribute represents the expected goal, that is, the consumer entity expects the production entity to recommend solutions that do not change the expected goal when the intention cannot be achieved.

[0162] The embodiments of the present application do not limit the manner in which the consuming entity sends the first information to the producing entity.

[0163] In one possible implementation, the consumer entity may send the first information as separate information to the producer entity.

[0164] In another possible implementation manner, the consumer entity may send a third message to the producer entity, where the third message includes the first information.

[0165] The embodiments of the present application do not limit the message type of the third message, and the third message can be any message related to intent management.

[0166] Exemplarily, the third message can be used to create or request the creation of an intent. For example, the third message is an intent creation request message. When the third message is used to create or request the creation of an intent, there are many ways for the third message to carry the first information, which are not limited. In one possible implementation, the third message may include an intent and the first information, wherein the intent may be expressed as an instantiated intent IOC (as shown in FIG1 ). In another possible implementation, the third message may include an intent, and the intent includes the first information, wherein the intent may be expressed as an instantiated intent IOC (as shown in FIG1 ). For example, the intent IOC corresponding to the intent includes an intent expectation and an intent context, and the intent context includes the first information. For another example, the intent IOC corresponding to the intent includes an intent expectation, the intent expectation includes an expected context, and the expected context includes the first information. For another example, the intent IOC corresponding to the intent includes an intent expectation, the intent expectation includes an expected target, the expected target includes a target context, and the target context includes the first information.

[0167] Exemplarily, the third message may be used to modify or request modification of the intent. For example, the third message is an intent modification request message. When the third message is used to modify or request modification of the intent, there are many ways for the third message to carry the first information, which are not limited. In one possible implementation, the third message may include an identifier of the intent and the first information. In another possible implementation, the third message may include an identifier of the intended target of the intent and the first information. In another possible implementation, the third message may include an identifier of the intended target of the intent and the first information. In another possible implementation, if the third message implements the modification function by carrying the modified intent IOC, then the first information may also be included in the intent IOC of the intent.

[0168] It should be noted that the first information can also be described as: the first information is used to indicate an expression of intent that is not expected by the consumer entity, and the unexpected expression of intent corresponds to the first intention, or the first information is used to indicate an expression of intent that is expected by the consumer entity, and the expected expression of intent corresponds to the first intention. The expression of intent corresponds to the solution, and the expression of intent can be a specific expression of the solution. In an embodiment of the present application, the solution includes a new expression of intent to replace the original intent. The new expression of intent can be a complete structured expression of intent, or it can only include expressions of intent that need to be modified, added, or deleted.

[0169] Step 302: When the goal of the first intention cannot be achieved, the production entity sends a second message to the consumption entity. Accordingly, the consumption entity receives the second message from the production entity.

[0170] The second information is used to indicate one or more recommended solutions.

[0171] The solution in the one or more recommended solutions is a solution to the situation where the goal of the first intention cannot be achieved, for example, it may include terminating the entire first intention, recommending a new intention, or recommending other feasible intention implementations, etc.

[0172] One or more recommended solutions satisfy the consumer entity's preference for solutions. Exemplarily, when the first information includes a first attribute that the consumer entity does not expect to change, the solution that satisfies the consumer entity's preference for solutions does not change the first attribute. In this case, the one or more recommended solutions do not change the first attribute. In conjunction with Example 1 in step 301, when the first attribute is a target, for the drone material transportation intention, one or more recommended solutions are: updating the action object of the first intention to another TAC area, that is, the second information indicates that the action object of the first intention is updated to another TAC area. When the first attribute is the action object, for the drone natural gas pipeline inspection intention, one or more recommended solutions are: updating the target of the first intention to ensure an uplink throughput greater than 20 Mbps, that is, the second information indicates that the target of the first intention is updated to ensure an uplink throughput greater than 20 Mbps. Exemplarily, when the first information includes a changeable first attribute, the solution that satisfies the consumer entity's preference for solutions does not change attributes other than the first attribute. In this case, the one or more recommended solutions do not change attributes other than the first attribute. In conjunction with Example 2 in step 301, when the first attribute is the target, for the drone's natural gas pipeline inspection intention, one or more recommended solutions are: updating the target of the first intention to ensure the uplink throughput is greater than 20Mbps, that is, the second information indicates that the target of the first intention is updated to ensure the uplink throughput is greater than 20Mbps. When the first attribute is the action object, for the drone's material transportation intention, one or more recommended solutions are: updating the action object of the first intention to another TAC, that is, the second information indicates that the action object of the first intention is updated to another TAC. For a more detailed description, please refer to Example 1 and Example 2 in step 301.

[0173] It should be noted that the phrase "one or more recommended solutions do not change the first attribute" can also be described as: "one or more recommended solutions guarantee or maintain the first attribute." The phrase "one or more recommended solutions do not change attributes other than the first attribute" can also be described as: "one or more recommended solutions change the first attribute," "one or more recommended solutions only change the first attribute," "one or more recommended solutions guarantee attributes other than the first attribute," or "one or more recommended solutions maintain attributes other than the first attribute."

[0174] In some embodiments, the production entity may determine that the goal of the first intention cannot be achieved. The embodiments of the present application do not limit the implementation method of determining that the goal of the first intention cannot be achieved. In one possible implementation method, the production entity performs a feasibility check on the first intention, and determines that the goal of the first intention cannot be achieved when the result of the feasibility check is infeasible. In another possible implementation method, after executing the action group for the first intention, the production entity determines that the goal of the first intention has not been achieved, that is, after the first intention is executed, the production entity determines that the goal of the first intention has not been achieved based on the realization value of the goal of the intention.

[0175] The embodiments of the present application do not limit the implementation method of the production entity performing the feasibility check for the first intention. In one possible implementation method, the production entity performs the feasibility check for the first intention itself. In another possible implementation method, the production entity requests the first network element to perform the feasibility check for the first intention, wherein the first network element can be a knowledge base or a network twin service production entity, etc.

[0176] In some embodiments, if the first intention cannot be achieved, the production entity can obtain the second information based on the first information. The embodiments of the present application do not limit the implementation method of the production entity obtaining the second information based on the first information.

[0177] In one possible implementation, the production entity may determine the second information based on the first information. For example, the production entity may generate a solution that satisfies the consumer entity's solution preferences based on the current network state and the first information, and then determine the second information. The network state refers to the state of a network performance indicator related to the intended target. For example, for a throughput intent, the current network state may include the current network throughput. For another example, for an energy-saving intent, the current network state may include the current network energy consumption.

[0178] In another possible implementation, the production entity may obtain the second information from the first network element, where the first network element may be a knowledge base or a network twin service production entity, etc. Exemplarily, the production entity may send third information to the first network element based on the first information, where the third information is used to indicate the consumer entity's preference for the solution or the third information is used to indicate the type of solution corresponding to the preference; after receiving the third information, the first network element may generate a solution that satisfies the consumer entity's preference for the solution based on the third information, and then determine the second information; the first network element sends the second information to the production entity, and accordingly, the production entity receives the second information from the first network element.

[0179] When the third information is used to indicate a consumer entity's preference for a solution, the third information may be in the same or different format as the first information. For example, when a production entity forwards the first information to a first network element, the third information may be in the same format as the first information. In another example, the production entity may convert the first information into third information that the first network element can recognize and use. The third information may be used to instruct the first network element to perform a query or simulation operation that satisfies the consumer entity's preference for a solution.

[0180] When the third information is used to indicate the solution type corresponding to the preference, the production entity also determines the solution type corresponding to the preference based on the first information, wherein the solution type corresponding to the preference can indicate the operations that the first network element needs to perform, such as feasible objects for detecting intentions, feasible time for detecting intentions, etc.

[0181] The embodiments of the present application do not limit the manner in which the production entity sends the third information to the first network element, and the manner in which the first network element sends the second information to the production entity. The third information and the second information can be carried in any message exchanged between the production entity and the first network element. For example, in a case where the first network element performs a feasibility check on the first intention, the production entity can send a first message to the first network element, wherein the first message is used to request a feasibility check on the first intention and the first message includes the third information, and the first network element can send a second message to the production entity, wherein the second message is used to indicate the result of the feasibility check and the second message includes the second information. In one embodiment, when the result of the feasibility check on the first intention is not feasible, the first network element sends the above-mentioned second message to the production entity.

[0182] It should be noted that one or more recommended solutions can also be described as: one or more recommended intent expressions. For the intent expressions and the relationship between the intent expressions and the solutions, please refer to the description in step 301.

[0183] The embodiments of the present application do not limit the manner in which the production entity sends the second information to the consumer entity. The second information can be carried in any message exchanged between the production entity and the consumer entity. In one possible implementation, the production entity sends an intent report to the consumer entity, where the intent report includes the second information. The intent report includes at least one of the following reports: an intent satisfaction report, an intent conflict report, or an intent feasibility check report. For descriptions of intent reports, intent satisfaction reports, intent conflict reports, or intent feasibility check reports, please refer to the term explanation section. For example, if the production entity determines that the goal of the first intent cannot be achieved based on the results of the feasibility check, the production entity may send an intent feasibility check report to the consumer entity, where the intent feasibility check report indicates the results of the feasibility check and includes the second information. For example, if the production entity determines that the goal of the first intent cannot be achieved based on the achieved value of the goal of the first intent, the production entity may send an intent satisfaction report to the consumer entity, where the intent satisfaction report includes the second information. For example, if the production entity determines that there is a conflict in the first intent (such as a conflict between the first intent and other intents, a conflict within the first intent, etc.), the production entity may send an intent conflict report to the consumer entity, where the intent conflict report includes the second information.

[0184] Step 303: The consuming entity manages the first intent according to the second information.

[0185] In an embodiment of the present application, the consumer entity manages the first intent based on the second information, which may refer to: the consumer entity determines to accept or reject one or more recommended solutions indicated by the second information, and indicates it to the production entity. Moreover, when the consumer entity accepts or rejects one of the one or more recommended solutions indicated by the second information, the consumer entity, the production entity, the optional first network element, and the managed entity execute the solution accepted by the consumer entity, such as executing the updated intent. The consumer entity manages the first intent based on the second information, which may refer to: the consumer entity requests the production entity to create a new intent or requests the production entity to modify the first intent based on the second information, and subsequently the consumer entity, the production entity, the optional first network element, and the managed entity may execute the new intent or the modified first intent.

[0186] In method 300, a consuming entity can indicate its solution preferences to a producing entity. If the intended goal cannot be achieved, the producing entity can generate a solution that satisfies the preferences, rather than generating a solution that does not. This helps prevent the producing entity from generating solutions that the consuming entity would not consider, thereby reducing the waste of computing resources and alleviating the burden on the consuming entity.

[0187] The method 300 is described in detail below by taking the example of carrying the first information in the intention creation request message and the production entity obtaining the second information from the network twin production entity during the feasibility check process.

[0188] Figure 5 is a schematic flow chart of a method 400 for managing network management intents provided in this application. In method 400, the intent service consumer, intent service producer, network twin service producer, solution preference attributes, intent creation request message, feasibility check request message, feasibility check response message, message #1, and information #1 correspond to the consumer entity, producer entity, network twin producer entity, first information, third message, first message, second message, intent feasibility check report, and third information described above, respectively.

[0189] In step 401, the intent service consumer sends an intent creation request message to the intent service producer. Correspondingly, the intent service producer receives the intent creation request message from the intent service consumer.

[0190] The intent creation request message is used to request the creation of an intent. The intent creation request message includes the intent's target, the object of the intent, and the solution preference attributes.

[0191] Among them, the solution preference attribute (solutionPreference) is used to describe the preference of the intent service consumer for the solution recommended by the intent service producer. The intent service consumer can use this attribute to restrict the intent service producer from generating certain solutions, thereby assisting the intent service producer to optimize the recommended solutions.

[0192] The optional value of the solution preference attribute can be [target, object], with the following meanings:

[0193] 1) The value of the solution preference attribute is the action object, indicating that when the intent cannot be achieved, a solution that meets the action object is recommended. In other words, a solution with the same action object is recommended. This value can be the default value. When the value of the solution preference attribute is the action object, the new intent after the intent service consumer accepts the recommendation has the same action object as the original intent.

[0194] 2) The solution preference attribute is set to a target, indicating that when the intent cannot be achieved, a solution that meets the goal is recommended. This means that the solution with the same goal is recommended. When the solution preference attribute is set to a target, the new intent after the intent service consumer accepts the recommendation has the same goal as the original intent.

[0195] The specific meaning of the optional values ​​of the solution preference attribute can be referred to step 301 and will not be described in detail.

[0196] It should be noted that the solution preference attribute can also be called by other names, as long as its function is to describe the intent service consumer's preference for the solution recommended by the intent service producer, such as the recommendation preference attribute. It should also be noted that the solution preference attribute can be specific to the entire intent or to a specific intent expectation or desired goal within the intent, without limitation. For details, please refer to the description of the first attribute section.

[0197] For example, the intent service consumer may be the information technology (IT) system independently developed by the customer, and the intent service producer may be the manufacturer's equipment network management, such as the mobile broadband automation engine (MAE).

[0198] There are many ways to carry the solution preference attribute in the intent creation request message, which are not limited. For specific implementation methods, please refer to the sending method of the first information.

[0199] In step 402, the intent service producer creates and configures an intent managed object instance (MOI) according to the intent creation request message.

[0200] In step 403, the intent service producer sends an intent creation response message to the intent service consumer. Correspondingly, the intent service consumer receives the intent creation response message from the intent service producer.

[0201] The intent creation response message includes an identifier of the intent and indication information #1. Indication information #1 is used to indicate whether the intent is created successfully. In method 400, the indication information indicates that the intent is created successfully.

[0202] In step 404, the intent service producer sends a feasibility check request message to the network twin service producer. Correspondingly, the network twin service producer receives the feasibility check request message from the intent service producer to perform a feasibility check on the intent.

[0203] In addition to requesting a feasibility check on the intent, the feasibility check request message may also include information #1, which is used to indicate the service consumer's preference for the solution to the network twin service producer. The feasibility check may include checking the satisfaction of intent fulfillment, or whether there are potential conflicts between one or more intent instances, etc. Potential conflicts include at least one of conflicts between different intents, conflicts between different intent expectations of the same intent, or conflicts between different expected goals of the same intent.

[0204] Exemplarily, information #1 includes a recommended solution type, which is used to describe the type of recommended solution that can be generated and can indicate to the network twin service producer the operations that need to be performed, such as feasible objects for detecting intent, feasible time for detecting intent, etc. The recommended solution type can be determined by the intent service producer based on the solution preference attributes from the intent service consumer.

[0205] Illustratively, information # 1 may also include the solution preference attributes received in step 401 .

[0206] In step 405, the network twin service producer performs a feasibility check on the intent.

[0207] When the result of the feasibility check of the intent is failed (or not feasible), the network twin service producer can generate a recommended solution based on information #1.

[0208] In step 406, the network twin service producer sends a feasibility check response message to the intention service producer. Accordingly, the intention service producer receives the feasibility check response message from the network twin service producer.

[0209] Among them, the feasibility check response message includes indication information #2 and an optional recommended solution, and indication information #2 is used to indicate the result of the intended feasibility check. When the result of the intended feasibility check is passed (or feasible), the feasibility check response message may not include the recommended solution. When the result of the intended feasibility check is failed (or not feasible), the feasibility check response message includes the recommended solution. In addition, when indication information #2 indicates that the result of the intended feasibility check is failed (or not feasible), the feasibility check response message may also include the reason for failure.

[0210] Step 407: The intent service producer sends message #1 to the intent service consumer. Correspondingly, the intent service consumer receives message #1 from the intent service producer.

[0211] Among them, message #1 is the feedback message of the intention feasibility check, which can carry the intention feasibility check report, and can include the intention identification, indication information #3 and optional recommended solutions. When the inspection result of the feasibility check of the intention is passed (or feasible), message #1 may not include the recommended solution. When the inspection result of the feasibility check of the intention is failed (or not feasible), message #1 includes the recommended solution. When indication information #3 indicates that the result of the feasibility check of the intention is failed (or not feasible), message #1 may also include the reason for failure.

[0212] It should be noted that the embodiments of the present application do not limit the order of step 403 and the feasibility check process (such as steps 404, 405, and 406). When step 403 is executed after the feasibility check process, the intent to create response message and message #1 can be the same message (i.e., step 403 and step 407 are the same step), or the intent to create response message and message #1 can also be different messages, without limitation.

[0213] Optionally, in step 408 , the intent service consumer sends message # 2 to the intent service producer, and accordingly, the intent service producer receives message # 2 from the intent service consumer.

[0214] Message #2 is used to indicate whether the service consumer accepts or rejects the recommended solution.

[0215] Optionally, in step 409 , when the intent service consumer accepts the recommended solution, the intent service consumer, the intent service producer, the network twin service producer, and the managed entity execute the updated intent.

[0216] Specifically, the intent service producer can update the intent based on message #2, generate a network deployment based on the updated intent, and configure and deploy the managed entity based on the generated network deployment, and then the intent service consumer, intent service producer, network twin service producer and managed entity execute the updated intent.

[0217] After step 407 , the intent service consumer may indicate to the intent service producer whether to accept or reject the recommended solution as shown in steps 408 and 409 , or may issue a new intent or modify the intent to the intent service producer based on the recommended solution.

[0218] In method 400, a solution preference attribute can be added to the intent model. The intent service consumer can use this attribute to restrict the intent service producer from generating certain solutions, thereby assisting the intent service producer in optimizing the recommended solutions, helping to avoid the intent service producer from consuming computing resources on the generation of useless solutions, and also reducing the burden of selection on the intent service consumer.

[0219] The method 300 is described in detail below by taking the example of carrying the first information in the intention creation request message, the production entity obtaining the second information from the network twin production entity, and feeding back the second information in the production entity intention report.

[0220] Figure 6 is a schematic flow chart of a method 500 for managing network management intents provided in this application. In method 500, the intent service consumer, intent service producer, network twin service producer, solution preference attributes, intent creation request message, message #3, message #4, and message #2 correspond to the consumer entity, producer entity, network twin producer entity, first information, third message, first message, second message, and third information described above, respectively.

[0221] In step 501, the intent service consumer sends an intent creation request message to the intent service producer. Correspondingly, the intent service producer receives the intent creation request message from the intent service consumer.

[0222] The intent creation request message is used to request the creation of an intent. The intent creation request message includes the intent's target, the object of the intent, and the solution preference attributes.

[0223] Step 502: The intent service producer creates and configures the intent MOI according to the intent creation request message.

[0224] Step 503: The intent service producer sends an intent creation response message to the intent service consumer. Correspondingly, the intent service consumer receives the intent creation response message from the intent service producer.

[0225] The intent creation response message includes an identifier of the intent and indication information #1. Indication information #1 is used to indicate whether the intent is created successfully. In method 500, the indication information indicates that the intent is created successfully.

[0226] Steps 501 to 503 may refer to steps 401 to 403 and will not be described in detail.

[0227] Step 504: The intent service producer performs a feasibility check on the intent.

[0228] In method 500 , the result of the intended feasibility check is a pass.

[0229] It should be noted that the embodiment of the present application does not limit the order of step 503 and step 504. Step 503 can be executed before step 503 as shown in Figure 5, or after step 504, without limitation.

[0230] Step 505: The intent service producer executes the intent and monitors the fulfillment of the intent.

[0231] Step 506, when the intent service producer determines that the intent has not been achieved, the intent service producer sends message #3 to the network twin service producer, and accordingly, the network twin service producer receives message #3 from the intent service producer.

[0232] Among them, message #3 is used to obtain recommended solutions.

[0233] Message #3 may include information #2, which is used to indicate the network twin service producer's preference for solutions to the intent service consumer. Exemplarily, information #2 may include a recommended solution type, which is used to describe the type of recommended solution that can be generated, and may indicate to the network twin service producer the operations that need to be performed, such as feasible objects for detecting intent, feasible time for detecting intent, etc. The recommended solution type can be determined by the intent service producer based on the solution preference attributes from the intent service consumer. Exemplarily, information #2 may also include the solution preference attributes received in step 501.

[0234] In step 507 , the network twin service producer generates a recommended solution for the intent based on message #3.

[0235] In step 508 , the network twin service producer sends message #4 to the intent service producer, and accordingly, the intent service producer receives message #4 from the network twin service producer.

[0236] Among them, message #4 recommends a solution.

[0237] In step 509 , the intent service producer sends an intent satisfaction report to the intent service consumer. Correspondingly, the intent service consumer receives the intent satisfaction report from the intent service producer.

[0238] The intention satisfaction report is used to indicate whether the intended goal has not been achieved and the recommended solution. For example, the intention satisfaction report includes the intention identifier, achievement information, the reason for non-achievement, and the recommended solution. The achievement information is used to indicate that the intention has not been achieved.

[0239] Optionally, in step 510 , the intent service consumer sends message # 5 to the intent service producer, and accordingly, the intent service producer receives message # 5 from the intent service consumer.

[0240] Message #5 indicates whether the intent service consumer accepts or rejects the recommended solution. When the intent service consumer accepts the recommended solution, message #5 includes the intent derived based on the recommended solution. The intent service producer can modify or configure the intent according to message #5.

[0241] Optionally, in step 511, when the intent service consumer accepts the recommended solution, the intent service consumer, the intent service producer, the network twin service producer and the managed entity execute the updated intent.

[0242] Specifically, the intent service producer can update the intent based on message #5, generate a network deployment based on the updated intent, and configure and deploy the managed entity based on the generated network deployment, and then the intent service consumer, intent service producer, network twin service producer and managed entity execute the updated intent.

[0243] After step 509 , the intent service consumer may indicate to the intent service producer whether to accept or reject the recommended solution as shown in steps 510 and 511 , or may issue a new intent or modify the intent to the intent service producer based on the recommended solution.

[0244] In method 500, a solution preference attribute can be added to the intent model. The intent service consumer can use this attribute to restrict the intent service producer from generating certain solutions, thereby assisting the intent service producer in optimizing the recommended solutions, helping to avoid the intent service producer from consuming computing resources on the generation of useless solutions, and also reducing the burden of selection on the intent service consumer.

[0245] The above describes in detail the method embodiment provided by the present application in conjunction with Figures 1 to 6 , and the following describes the device embodiment of the present application in conjunction with Figures 7 to 9 .

[0246] It is understood that, in order to implement the functions in the above embodiments, the apparatuses in Figures 7 to 9 include hardware structures and / or software modules corresponding to the functions. Those skilled in the art should readily appreciate that, in conjunction with the various exemplary units and method steps described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software.

[0247] Figures 7 and 8 are schematic diagrams of possible apparatuses provided in embodiments of the present application. These apparatuses can be used to implement the functions of the production entity, consumption entity, or first network element in the above method embodiments, thereby also achieving the beneficial effects of the above method embodiments.

[0248] As shown in FIG7 , the device 10 includes a transceiver unit 11 and a processing unit 12 .

[0249] When the apparatus 10 is used to implement the functions of the production entity in the above-mentioned method embodiments, the transceiver unit 11 is used to execute the production entity's transceiver steps, such as steps 301, 302, 401, 403, 404, 406, 407, 408, 501, 503, 506, 508, 509, or 510, and the processing unit 12 is used to execute the production entity's processing steps, such as steps 402, 409, 502, 504, 505, 511, or 511. When the apparatus 10 is used to implement the functions of the consumption entity in the above-mentioned method embodiments, the transceiver unit 11 is used to execute the consumption entity's transceiver steps, such as steps 301, 302, 401, 403, 407, 408, 501, 503, 509, or 510, and the processing unit 12 is used to execute the consumption entity's processing steps, such as steps 303, 409, or 511. When the device 10 is used to implement the functions of the first network element in the above-mentioned method embodiments, the transceiver unit 11 is used to execute the transceiver steps of the first network element, such as steps 404, 406, 506 or 508, and the processing unit 12 is used to execute the processing steps of the first network element, such as steps 405, 409, 504, 505, 507 or 511.

[0250] For a more detailed description of the transceiver unit 11 and the processing unit 12 , please refer to the relevant description in the above method embodiment, which will not be described again here.

[0251] As shown in FIG8 , the apparatus 20 includes a processor 21. The processor 21 is coupled to a memory 23, which is used to store instructions. When the apparatus 20 is used to implement the method described above, the processor 21 is used to execute the instructions in the memory 23 to implement the functions of the processing unit 12 described above.

[0252] Optionally, the device 20 further includes a memory 23 .

[0253] Optionally, the apparatus 20 further includes an interface circuit 22. The processor 21 and the interface circuit 22 are coupled to each other. It will be appreciated that the interface circuit 22 may be a transceiver or an input / output interface. When the apparatus 20 is used to implement the method described above, the processor 21 is configured to execute instructions to implement the functions of the processing unit 12, and the interface circuit 22 is configured to implement the functions of the transceiver unit 11.

[0254] Exemplarily, when device 20 is a chip applied to a production entity, a consumer entity, or a first network element, the chip implements the functions of the production entity, the consumer entity, or the first network element in the above-mentioned method embodiments. The chip receives information from other modules (such as a radio frequency module or antenna) in the production entity, the consumer entity, or the first network element, where the information is sent by other devices to the production entity, the consumer entity, or the first network element; or the chip sends information to other modules (such as a radio frequency module or antenna) in the production entity, the consumer entity, or the first network element, where the information is sent by the production entity, the consumer entity, or the first network element to other devices.

[0255] 9 is a schematic diagram of a chip system 30 provided in an embodiment of the present application. The chip system 30 (or also referred to as a processing system) includes a logic circuit 31 and an input / output interface 32.

[0256] The logic circuit 31 may be a processing circuit in the chip system 30. The logic circuit 31 may be coupled to a storage unit and call instructions in the storage unit so that the chip system 30 can implement the methods and functions of the various embodiments of the present application. The input / output interface 32 may be an input / output circuit in the chip system 30, outputting information processed by the chip system 30 or inputting data or signaling information to be processed into the chip system 30 for processing.

[0257] As a solution, the chip system 30 is used to implement the operations performed by the production entity, the consumption entity, or the first network element in the above various method embodiments.

[0258] For example, the logic circuit 31 is used to implement the processing-related operations performed by the production entity, the consumption entity, or the first network element in the above method embodiment; the input / output interface 32 is used to implement the sending and / or receiving-related operations performed by the production entity, the consumption entity, or the first network element in the above method embodiment.

[0259] The present application also provides a communication device, comprising a processor coupled to a memory, the memory being configured to store computer programs or instructions and / or data, the processor being configured to execute the computer programs or instructions stored in the memory, or to read data stored in the memory, to perform the methods described in the above method embodiments. Optionally, there are one or more processors. Optionally, the communication device includes a memory. Optionally, there are one or more memories. Optionally, the memory is integrated with the processor or provided separately.

[0260] The present application also provides a chip, including a processor, which is coupled to a memory, the memory is used to store computer programs or instructions, and the processor is used to execute the computer programs or instructions stored in the memory to implement the methods performed by the production entity, the consumer entity, or the first network element in the above-mentioned method embodiments.

[0261] The present application also provides a computer-readable storage medium on which are stored computer instructions for implementing the methods executed by the production entity, the consumption entity, or the first network element in the above-mentioned method embodiments.

[0262] The present application also provides a computer program product comprising instructions, which, when executed by a computer, implement the methods performed by the production entity, the consumption entity, or the first network element in the above-mentioned method embodiments.

[0263] The present application also provides a communication system, which includes at least one of the production entity, consumption entity, or first network element in the above embodiments.

[0264] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

[0265] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0266] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk, mobile hard disk, compact disc read-only memory (CD-ROM) or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a production entity, a consumption entity, or a first network element. Of course, the processor and the storage medium can also exist as discrete components in a production entity, a consumption entity, or a first network element.

[0267] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive.

[0268] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0269] Unless otherwise indicated, all technical and scientific terms used in the embodiments of the present application have the same meaning as those generally understood by those skilled in the art of the technical field of the application. The terms used in this application are only for the purpose of describing specific embodiments and are not intended to limit the scope of the application. It should be understood that the above are for illustration, and the examples above are only for helping those skilled in the art to understand the embodiments of the present application, rather than limiting the application embodiments to the specific numerical values ​​or specific scenarios illustrated. Those skilled in the art can obviously carry out various equivalent modifications or changes based on the examples given above, and such modifications and changes also fall within the scope of the embodiments of the present application.

Claims

1. A management method for network management intent, characterized in that The method includes: Receiving first information from a consuming entity, where the first information is used to indicate the consuming entity's preference for a solution, and the preference corresponds to a first network management intent; When the goal of the first network management intent cannot be achieved, sending second information to the consuming entity, where the second information is used to indicate one or more recommended solutions that meet the preference.

2. The method according to claim 1, wherein: The first information includes a first attribute of the first network management intent, where: The first attribute is an attribute that the consuming entity does not expect to change, and the one or more recommended solutions do not change the first attribute; or, The first attribute is an attribute that can be changed, and the one or more recommended solutions do not change attributes other than the first attribute.

3. The method according to claim 2, wherein: The first attribute includes a target and / or an object of action.

4. The method according to claim 3, wherein: The first attribute further includes context.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Determining that the goal of the first network management intent cannot be achieved.

6. The method according to claim 5, wherein The determining that the goal of the first network management intent cannot be achieved includes: After performing an action group for the first network management intent, determining that the goal of the first network management intent has not been achieved, where the action group includes one or more actions for managing the managed entities of the first network management intent.

7. The method according to claim 5, wherein The determining that the goal of the first network management intent cannot be achieved includes: Performing a feasibility check for the first network management intent; When the result of the feasibility check is infeasible, determining that the goal of the first network management intent cannot be achieved.

8. The method according to any one of claims 1 to 7, characterized in that The sending the second information to the consuming entity includes: Sending an intent report to the consuming entity, where the intent report includes the second information.

9. The method according to claim 8, wherein The intent report includes at least one of the following reports: an intent satisfaction report, an intent conflict report, or an intent feasibility check report.

10. The method according to any one of claims 1 to 9, characterized in that The method further includes: According to the first information, sending third information to a first network element, where the third information is used to indicate the preference or the solution type corresponding to the preference, and the first network element includes a network twin production entity or a knowledge base; Receiving the second information from the first network element.

11. The method according to claim 10, wherein: The sending the third information to the first network element includes: sending a first message to the first network element, where the first message is used to request a feasibility check for the first network management intent, and the first message includes the third information; The receiving the second information from the first network element includes: receiving a second message from the first network element, where the second message is used to indicate the result of the feasibility check, and the second message includes the second information.

12. The method according to any one of claims 1 to 11, characterized in that, The receiving the first information from the consuming entity includes: Receive a third message from the consuming entity, the third message being used to request the creation of the first network management intent; Wherein, the third message includes the first network management intent, the first network management intent includes the first information, or the third message includes the first network management intent and the first information.

13. A management method for network management intents, characterized in that, The method includes: Send first information to the producing entity, the first information being used to indicate the consuming entity's preference for a solution, the preference corresponding to the first network management intent; Receive second information from the producing entity, the second information being used to indicate one or more recommended solutions that meet the preference; Manage the first network management intent according to the second information.

14. The method according to claim 13, wherein The first information includes a first attribute of the first network management intent, wherein: The first attribute is an attribute that the consuming entity does not expect to change, and the one or more recommended solutions do not change the first attribute; or, The first attribute is an attribute that can be changed, and the one or more recommended solutions do not change attributes other than the first attribute.

15. The method according to claim 14, wherein The first attribute includes a target or an object of action.

16. The method according to claim 15, wherein The first attribute further includes context.

17. The method according to any one of claims 13 to 16, characterized in that The receiving the second information from the producing entity includes: Receive an intent report from the producing entity, the intent report including the second information.

18. The method according to claim 17, wherein The intent report includes at least one of the following reports: an intent satisfaction report, an intent conflict report, or an intent feasibility check report.

19. The method according to any one of claims 13 to 18, characterized in that, The sending the first information to the producing entity includes: Send a third message to the producing entity, the third message being used to request the creation of the first network management intent; Wherein, the third message includes the first network management intent, the first network management intent includes the first information, or the third message includes the first network management intent and the first information.

20. A management method for network management intents, characterized in that, The method includes: Receive third information from the producing entity, wherein the third information is used to indicate the consuming entity's preference for a solution or the solution type corresponding to the preference, the preference or the solution type corresponding to the first network management intent; Determine second information according to the third information, wherein the second information is used to indicate one or more recommended solutions that meet the preference; Send the second information to the producing entity.

21. The method according to claim 20, wherein The receiving the third information from the producing entity includes: receiving a first message from the producing entity, wherein the first message is used to request a feasibility check on the first network management intent, and the first message includes the third information; Sending the second information to the production entity includes: sending a second message to the production entity, where the second message is used to indicate the result of the feasibility check, and the second message includes the second information.

22. A management method for network management intents, characterized in that, The method includes: A consuming entity sends first information, and a production entity receives the first information. The first information is used to indicate the preference of the consuming entity for a solution, and the preference corresponds to a first network management intention. In a case where the goal of the first network management intention cannot be achieved, the production entity sends second information, and the consuming entity receives the second information. The second information is used to indicate one or more recommended solutions that satisfy the preference. The consuming entity manages the first network management intention according to the second information.

23. A management device for network management intents, characterized in that, The device includes a transceiver unit and a processing unit; The transceiver unit is configured to receive first information from a consuming entity, where the first information is used to indicate the preference of the consuming entity for a solution, and the preference corresponds to a first network management intention. The processing unit is configured to, in a case where the goal of the first network management intention cannot be achieved, send second information to the consuming entity, where the second information is used to indicate one or more recommended solutions that satisfy the preference.

24. A management device for network management intents, characterized in that, The device includes a transceiver unit and a processing unit; The transceiver unit is configured to send first information to a production entity, where the first information is used to indicate the preference of the management device for a solution, and the preference corresponds to a first network management intention. The transceiver unit is further configured to receive second information from the production entity, where the second information is used to indicate one or more recommended solutions that satisfy the preference. The processing unit is configured to manage the first network management intention according to the second information.

25. A management device for network management intents, characterized in that, The device includes a transceiver unit and a processing unit; The transceiver unit is configured to receive third information from a production entity, where the third information is used to indicate the preference of a consuming entity for a solution or the solution type corresponding to the preference, and the preference or the solution type corresponds to a first network management intention. The processing unit is configured to determine second information according to the third information, where the second information is used to indicate one or more recommended solutions that satisfy the preference. The transceiver unit is further configured to send the second information to the production entity.

26. A communication device, characterized in that, It includes a processor and an interface circuit. The interface circuit is configured to receive a signal from another communication device outside the communication device and transmit it to the processor or send a signal from the processor to another communication device outside the communication device. The processor is configured to implement the method according to any one of claims 1 to 22 through logic circuits or by executing code instructions.

27. The communication device according to claim 26, wherein The communication device is a chip or a chip system.

28. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method according to any one of claims 1 to 22.

29. A communication system, characterized in that, A communication device for executing the method according to any one of claims 1 to 12 and a communication device for executing the method according to any one of claims 13 to 19 are included.

30. A computer program product, characterized in that, It contains instructions which, when executed by a computer, implement the method according to any one of claims 1 to 22.

Images