Management method, management device and system of network management intention

Abstract

A network management intent management method, management apparatus and system, a consumer entity may indicate a preference for a solution to a production entity, and when a target of an intent cannot be achieved, the production entity may generate a solution that satisfies the preference without generating a solution that does not satisfy the preference. Therefore, the production entity is prevented from generating a solution which is not considered by the consumption entity at all, so that the waste of computing power resources is reduced, and the burden of the consumption entity is relieved.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and more specifically, to a method, apparatus, and system for managing network management intents. Background Art

[0002] With the development of network resource management, network management service consuming entities may not directly manage network resources. A network management service consuming entity may send a message to a network management service producing entity, causing the network management service producing entity to execute a network management intent, with the expectation that specified performance metrics of network devices within a specific range reach an expected goal. And when the goal of the network management intent is not achieved, the network management service producing entity may generate possible solutions and recommend them to the network management service consuming entity.

[0003] Currently, there is a significant waste of computing power resources in the process of generating solutions by network management service producing entities. Therefore, how to reduce the waste of computing power resources has become an urgent problem to be solved. Summary of the Invention

[0004] Embodiments of this application provide a method, apparatus, and system for managing network management intents, with the expectation of reducing the waste of computing power resources of producing entities and reducing the burden on consuming entities.

[0005] In a first aspect, a method for managing network management intents is provided. The method may be executed by a producing entity. Without special instructions, "producing entity" may refer to the producing entity itself or a device capable of supporting the producing entity in realizing its functions.

[0006] 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; and 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.

[0007] The first information may also be described as: the first information is used to indicate an intent expression that the consuming entity does not expect, and the intent expression that is not expected corresponds to a first intent, or the first information is used to indicate an intent expression that the consuming entity expects, and the intent expression that is expected corresponds to a first intent. One or more recommended solutions may also be described as: one or more recommended intent expressions. An intent expression corresponds to a solution, and an intent expression may be a specific expression form of the solution.

[0008] Based on the above method, the consumer entity can indicate the preference for the solution to the producer entity, so that when the goal of the first intention cannot be achieved, the producer entity can generate a solution that meets the preference without generating a solution that does not meet the preference. This helps to avoid the producer 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.

[0009] In conjunction with 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 consumer entity does not expect 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.

[0010] 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 guarantee, or the attribute that the consuming entity expects to maintain, etc. The one or more recommended solutions do not change the first attribute, which can also be described as: one or more recommended solutions guarantee or maintain the first attribute.

[0011] 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, etc. 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, etc.

[0012] 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 change 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.

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

[0014] In combination with the first aspect or any implementation manner thereof, in some other possible implementation manners, the first attribute also includes a context.

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

[0016] Combined with the first aspect or any implementation thereof, in some other possible implementations, the failure to achieve the goal of the first network management intention includes: after performing the action group for the first network management intention, it is determined that the goal of the first network management intention has not been achieved, where the action group includes one or more actions for managing the managed entities of the first network management intention.

[0017] 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 intentions that have been executed.

[0018] Combined with the first aspect or any implementation thereof, in some other possible implementations, the failure to achieve the goal of the first network management intention includes: performing a feasibility check for the first network management intention; when the result of the feasibility check is infeasible, it is determined that the goal of the first network management intention cannot be achieved.

[0019] 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 the intentions that fail the feasibility check.

[0020] Combined with the first aspect or any implementation thereof, in some other possible implementations, the sending of the second information to the consuming entity includes: sending an intention report to the consuming entity, where the intention report includes the second information.

[0021] Combined 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.

[0022] Combined with the first aspect or any implementation thereof, in some other possible implementations, the obtaining of the second information according to the first information 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.

[0023] In combination with the first aspect or any implementation thereof, in some other possible implementations, 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 on the first network management intention, and the first message includes the third information; 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.

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

[0025] A second aspect provides a method for managing network management intentions. The method can be executed by a consuming entity. Without special instructions, the "consuming entity" can refer to the consuming entity itself or a device capable of supporting the consuming entity to implement its functions.

[0026] Terms or features in the second aspect or its implementations that are the same as those in the first aspect or its implementations can refer to the first aspect or its implementations. The technical effects of the second aspect or its implementations can refer to the technical effects in the first aspect or its implementations and will not be elaborated in the second aspect.

[0027] The method includes: sending first information to a producing 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 intention; receiving second information from the producing entity, where the second information is used to indicate one or more recommended solutions that meet the preference; and managing the first network management intention according to the second information.

[0028] In combination with the second aspect, in some possible implementations, the first information includes a first attribute of the first network management intention. 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 a changeable attribute, and the one or more recommended solutions do not change attributes other than the first attribute.

[0029] 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.

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

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

[0032] 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.

[0033] In combination with the second aspect or any implementation thereof, in some other possible implementations, the sending the first information to the production entity includes: sending a third message to the production entity, where the third message is used to request the creation of the first network management intention; where 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.

[0034] In a third aspect, a method for managing a network management intention is provided. The method can be executed by a first network element. Without special instructions, the "first network element" can refer to the first network element itself or a device capable of supporting the first network element to implement its functions. Optionally, the first network element can be a network twin production entity or a knowledge base.

[0035] 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. 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 elaborated in the third aspect.

[0036] The method includes: receiving third information from a production entity, where the third information is used to indicate the preference of a consumption 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; determining second information according to the third information, where the second information is used to indicate one or more recommended solutions that meet the preference; and sending the second information to the production entity.

[0037] In combination with the third aspect, in some possible implementation manners, the receiving the third information from the production entity includes: receiving a first message from the production entity, where the first message is used to request a feasibility check for the first network management intention, and the first message includes the third information; the 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.

[0038] In a fourth aspect, a method for managing a network management intention is provided. The method can be executed by a production entity and a consumption entity. Without special instructions, the "production entity" or "consumption entity" may refer to the production entity or the consumption entity itself, or may refer to a device capable of supporting the production entity or the consumption entity to implement its functions.

[0039] The method includes: the consumption entity sending first information, and the production entity receiving the first information, where the first information is used to indicate the preference of the consumption entity for a solution, and the preference corresponds to a first network management intention; in a case where the objective of the first network management intention cannot be achieved, the production entity sending second information, and the consumption entity receiving the second information, where the second information is used to indicate one or more recommended solutions that meet the preference; the consumption entity managing the first network management intention according to the second information.

[0040] The steps executed by the production entity in the fourth aspect or its implementation manners may refer to the first aspect or its implementation manners. The steps executed by the consumption entity in the fourth aspect or its implementation manners may refer to the second aspect or its implementation manners. The same terms or features in the fourth aspect or its implementation manners as those in the first aspect or its implementation manners may refer to the first aspect or its implementation manners. The technical effects of the fourth aspect or its implementation manners may refer to the technical effects in the first aspect or its implementation manners, and will not be elaborated in the fourth aspect.

[0041] In a fifth aspect, a communication device is provided. The device is used to execute the method provided in any of the above aspects or its implementation manners. Specifically, the device may include units and / or modules for executing the method provided in any of the above aspects or its implementation manners, such as a processing unit and / or a transceiver unit. Among them, the processing unit is used to execute the processing steps in the method provided in any of the above aspects or its implementation manners. The transceiver unit is used to execute the transceiver steps in the method provided in any of the above aspects or its implementation manners.

[0042] 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; 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.

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

[0044] In a sixth aspect, a communication device is provided, which includes: a memory for storing programs; at least one processor for executing the computer programs or instructions stored in the memory to perform the methods provided in any of the above aspects or their implementations.

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

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

[0047] In a seventh aspect, a communication device is provided, which includes: at least one processor and a communication interface. The at least one processor is used to obtain the computer programs or instructions stored in the memory through the communication interface to perform the methods provided in any of the above aspects or their implementations. The communication interface may be implemented by hardware or software.

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

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

[0050] For operations such as sending and obtaining / receiving involved by the processor, if there is no special description, or if it does not conflict with its actual role or internal logic in the relevant description, then it can be understood as the operations of the processor for outputting, receiving, and inputting, and can also be understood as the sending and receiving operations performed by the radio frequency circuit and the antenna. This application does not make any limitations in this regard.

[0051] In a ninth aspect, a computer-readable storage medium is provided, which stores program code for a device to execute, and the program code includes methods provided by any of the above aspects or their implementation manners.

[0052] In a tenth aspect, a computer program product including instructions is provided. When the computer program product runs on a computer, the computer is caused to execute the methods provided by any of the above aspects or their implementation manners.

[0053] In an eleventh aspect, a chip is provided. The chip includes a processor and a communication interface. The processor reads instructions stored on a memory through the communication interface and executes the methods provided by any of the above aspects or their implementation manners. The communication interface can be implemented by hardware or software.

[0054] Optionally, as an implementation manner, the chip further includes a memory, and computer programs or instructions are stored in the memory. The processor is configured to execute the computer programs or instructions stored on the memory. When the computer programs or instructions are executed, the processor is configured to execute the methods provided by any of the above aspects or their implementation manners.

[0055] Wherein, when the method provided in this application is executed by a chip, this application does not limit the number of chips for specifically implementing the method of this application. For example, it can be executed by one chip, or can be executed by two or more chips. And when the number of chips for implementing the method of this application is two or more, the chip manufacturers are not limited, and they can be the same manufacturer or different manufacturers.

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

[0057] In a thirteenth aspect, a computer program is provided. When it runs on a computer, the methods provided by any of the above aspects or their implementation manners are caused to be executed. Description of the Drawings

[0058] Figure 1 is a schematic structural diagram of an information object class (IOC) of intention information.

[0059] Figure 2 is a schematic structural diagram of an IOC of intention report.

[0060] Figure 3 is a schematic structural diagram of a communication system applicable to an embodiment of this application.

[0061] Figure 4 is a schematic flowchart of a network management intention management method 300 provided by an embodiment of this application.

[0062] Figure 5 It is a schematic flowchart of a network management intention management method 400 provided by an embodiment of the present application.

[0063] Figure 6 It is a schematic flowchart of a network management intention management method 500 provided by an embodiment of the present application.

[0064] Figure 7 It is a schematic structural diagram of a device provided by an embodiment of the present application.

[0065] Figure 8 It is another schematic structural diagram of a device provided by an embodiment of the present application.

[0066] Figure 9 It is a schematic diagram of a chip system provided by an embodiment of the present application. Detailed implementation manners

[0067] Before introducing the embodiments of the present application, the following explanations are made first.

[0068] "For indicating" or "indicating" may include direct indication and indirect indication, or in other words, "for indicating" or "indicating" may explicitly and / or implicitly indicate. The various numerical numbers such as first, second, etc. are only for the convenience of description and are not used to limit the scope of the embodiments of this application. For example, they are used to distinguish different messages, different information, etc. "Pre-defined" can be achieved by pre-saving corresponding codes, tables or other means 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 standard protocols in the communication field. For example, it may include long term evolution (LTE) protocol, new radio (NR) protocol, and related protocols applied to future communication systems. This application does not limit this. Words such as "exemplary", "for example", "exemplarily", "as (another) example" are used to give examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" in this application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. The terms "include", "comprise", "have" and their variants all mean "including but not limited to", unless otherwise specifically emphasized in other ways. "Multiple" means two or more. "And / or" describes the association relationship of associated objects and indicates that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one (item)" or its similar expression refers to any combination of these items, including any combination of single item (item) or plural items (items). For example, at least one (item) of a, b, and c can represent: 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 respectively. The related descriptions regarding network element A sending a message, information or data to network element B, and network element B receiving the message, information or data from network element A are intended to illustrate which network element the message, information or data is to be sent to, rather than limiting whether they are directly sent or indirectly sent via other network elements. Descriptions such as "when...", "in the case of...", "if" and "if" all refer to the device making corresponding processing under a certain objective situation, not limiting the time, and do not require the device to have a judgment action when implementing, nor does it mean there are other limitations.

[0069] In addition, the network architecture and service scenarios described in the embodiments of this application are used to more clearly illustrate the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Those of ordinary skill in the art will know that with the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of this application are equally applicable to similar technical problems.

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

[0071] To facilitate the understanding of the embodiments of this application, some terms related to the embodiments of this application are first explained.

[0072] 1. Network management and network management services

[0073] 1.1 Network management

[0074] 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 conditions 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 that when a network failure occurs, it can report and handle it in a timely manner, and coordinate and maintain the efficient operation of the network system, etc. Among them, network resources are the objects of network management, and can also be called network objects or managed entities. Exemplarily, network resources can be base station devices, routers, switches, core network devices, etc. In this regard, the embodiments of this application do not make special limitations. For the convenience of narration, the embodiments of this application are described by taking the managed entity as an example, but they can all be replaced by other objects of network management.

[0075] 1.2 Network Management Service

[0076] The network management service refers to a service that provides network management functions. The production entity of this service usually provides network management functions to the consumption entity of this service through a network interface (for example, a service-based interface).

[0077] 2. Network Management Intent (referred to as Intent for short)

[0078] The network management intent refers to the demand of the consumption entity of the network management service for the network management service, and can also be called the network management service demand. The embodiments of this application do not limit this name. Exemplarily, the network management intent can be an intent such as an optical dedicated line service intent or an energy-saving intent, such as the intent defined in the 3rd generation partnership project (3GPP) standard specification 28.312.

[0079] The interaction scenario based on intent mainly includes two roles, namely the production entity of the network management service and the consumption entity of the network management service. Among them, the production entity of the network management service can also be called the network management service providing entity, the network management provider, or the intent provider, or the intent handler, etc. The consumption entity of the network management service can also be called the network management service consumer, or the intent consumer, or the intent owner, etc. Among them, the consumption entity of the network management service can be the invoker of the network management service and can perform operations such as creating, modifying, deleting, and querying the network management intent expression. The consumption entity of the network management service can be configured in a network management system (NMS), or an element management system (EMS), or a network equipment (NE). The consumption entity of the network management service can be a management function, or a management function entity, or a management entity, or a network equipment, or a network element, etc. This application does not make any limitations in this regard. For a more detailed description of the production entity and the consumption entity of the network management service, please refer to the following Figure 3 .

[0080] The intent can be applied to a network system so that the specified performance indicators of network devices within a specific range reach the expected goals. The intent can express the expectation for the network system through formal specifications and descriptive information. Among them, the formal specification can refer to the specific syntax or semantics of the intent, and the descriptive information can be used to describe at least one of the requirements, goals, or constraints of the intent.

[0081] An intent may include at least one intent expectation. Each intent expectation may represent the performance requirements of a network management service consuming entity for a specific network object. An intent expectation may be composed of at least one expectation target and at least one expectation object. Each expectation target may represent the performance requirements of a network management service consuming entity for a certain specific attribute of the expectation object. The expectation object may be the network object on which the intent acts, and the expectation object may also be referred to as the acting object. Exemplarily, an intent expectation may include two expectation targets. One expectation target is that the average downlink throughput rate is greater than 5 Mbps, and the other expectation target is that the end-to-end delay is less than 10 milliseconds. If the average downlink throughput rate of the expectation object is greater than 5 Mbps, then the expectation target regarding the downlink throughput rate is satisfied. If the end-to-end delay of the expectation object is less than 10 milliseconds, then the expectation target regarding the delay is satisfied. If both expectation targets of the intent expectation are satisfied, then the intent expectation is satisfied. If there is one or more intent expectations that are not satisfied, or there is one or more expectation targets that are not satisfied, then the intent is not satisfied.

[0082] In the embodiments of the present application, whether an intent, an intent expectation or an expectation target is satisfied or not satisfied may also be described as: whether an intent, an intent expectation or an expectation target is achieved or not achieved, whether an intent, an intent expectation or an expectation target is realized or not realized, or whether an intent, an intent expectation or an expectation target has been achieved or not achieved, etc.

[0083] An intent may further include an intent context. The intent context may represent the constraints or conditions of a network management service consuming entity for the intent. Exemplarily, a network management service consuming entity may constrain the acting duration of the intent through the intent context.

[0084] An intent may further include an expectation context. The expectation context may represent the constraints or conditions of a network management service consuming entity for an intent expectation. Exemplarily, a network management service consuming entity may constrain the acting duration of the intent expectation through the expectation context.

[0085] An intent may further include a target context. The target context may represent the constraints or conditions of a network management service consuming entity for an expectation target. Exemplarily, a network management service consuming entity may constrain the acting duration of the expectation target through the target context.

[0086] An intent may further include an object context. The object context may represent the constraints or conditions of a network management service consuming entity for the network object on which the intent acts. Exemplarily, a network management service consuming entity may indicate the location area of the network object on which the intent acts through the object context.

[0087] Exemplarily, an intent may be expressed as:

[0088]

[0089] For example, the intention can be expressed as: ensuring that the handover failure rate of a certain community is < 2% when the load > 80%. Among them, "a certain community" is the expected object or the object of action, and "a certain community" 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).

[0090] The intention expectation, expectation target, and intention context introduced above can be used as cells in the IOC of the intention creation request. The network management service consuming entity can express the demand for the network management service by sending the above cells to the network management service producing entity.

[0091] The cells in the intention IOC can use a specific structure to express the demand for the network management service.

[0092] Exemplarily, Figure 1 Fig. shows a schematic structural diagram of an intention IOC.

[0093] See Figure 1 , the intention IOC includes intention expectation and intention context. The intention expectation includes expectation object, expectation target, and expectation context. The expectation object includes expectation object context, and the expectation target includes target context. It can be understood that non-context type cells (such as intention IOC, intention expectation, expectation object, or expectation target) can include context type cells (such as intention context, expectation object context, target context, expectation context, etc.), and the context type cells can be used to constrain the non-context type cells.

[0094] It can be understood that Figure 1 is a schematic illustration of the relationship of the attributes in the intention IOC. Based on the network management service requirements, other attributes can also be included in the intention IOC, and this application does not make special limitations on this. It can also be understood that this application does not make special limitations on the number of attributes of the same type. For example, an intention IOC can include one or more parallel intention expectation attributes, and an intention expectation can also include one or more parallel expectation target attributes.

[0095] 3. Network Management Intention Template

[0096] A network management intent template refers to the templatized description information of network management intents, and can also be referred to as a network management service requirement template. The embodiments of this application do not limit this name. The intent template can be used to specify the syntax and semantics of various types of attribute expressions introduced above. For example, the intent template can specify the field types, value types, etc. that can be adopted by 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 types of expected target attributes that the intent expectation can include, such as delay, bandwidth, maximum number of users, etc. The intent expectation description information can also specify the field type of each expected target. For example, the field type of the expected target regarding delay is a string, the field type of the expected target regarding bandwidth is a string, and the field type of the expected target regarding the maximum number of users is an integer. As another example, the intent template can also include intent context description information for specifying 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 this application does not make special limitations on this.

[0097] 4. Intent Expression

[0098] In the embodiments of this application, an intent expression is the information form for expressing network management service intents and can be the instantiation result of a network management intent template. Consumers of network management intents can instantiate the intent IOC according to the intent template to generate an intent expression, and then the generated intent expression after instantiation can be used for specific network services. For example, the intent expression can be represented by a list of key-value pairs of a set of attributes and values of network management service intents (for example, a set of [attribute, value]).

[0099] Exemplarily, the intent expression includes an instance of performance metric information, an instance of network object information, and an instance of context information.

[0100] For example, the instance of performance metric information can include the value or value range of the target metric requirements corresponding to the performance metric information. For example, the target metric requirements corresponding to the performance metric information template include a bandwidth parameter, and the instance of performance metric information includes that the value of the bandwidth parameter is 20M, or the value range of the bandwidth parameter is from 10M to 15M. For example, the target metric requirements corresponding to the performance metric information template include a delay parameter, and the instance of the delay parameter includes that the value of the delay parameter is 2s, or the value range of the delay parameter is from 1s to 5s.

[0101] 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, that is, one of the physical entities or logical entities used to indicate the implementation of the network management service. At this time, the network object information instance indicates a specific network object. For example, the network object information template indicates a network service, and the network object information instance indicates an energy-saving service.

[0102] The context information instance is used to indicate the constraint conditions 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 destination information corresponding to the target network object indicated by the network object instance.

[0103] The intent expectation information instance includes the performance metric information instance and the network object information instance.

[0104] In the embodiments of the present application, the "intent" transmitted through the message refers to the intent expression.

[0105] 5. Network management intent instance

[0106] The network management intent instance refers to the network management intent processing process locally created by the network management service providing entity according to the received network management intent expression (for example, the performance metric information instance, the network object information instance, the context information instance).

[0107] The network management intent processing process is used to process the network management intent expression. Exemplarily, the network management intent processing process may include an identifier used to identify this process; the network management intent processing process may include computing resources used to perform operations such as network management intent translation and querying a database (such as a semantic knowledge base); it may include storage resources used to store the network management intent expression, the result of network management intent translation, etc.

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

[0109] 6. Network management action group (actions)

[0110] A network management action group is one or more network management actions generated by a network management service production entity based on an intent expression. The network management service production entity executes one or more network management actions to achieve the intent of the network management service consuming entity. 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 an operation instruction set for a desired object (such as a physical entity or a logical entity in a network system to which the intent applies), containing one or more instructions. For example, adjusting the antenna tilt angle of a certain base station, turning on the energy-saving switch of a certain cell, etc.

[0111] Based on the intent expression, the network management service production entity can generate multiple management action groups. During the execution process, the network management service production entity can select some of the management action groups for execution at a single time. That is to say, the management action groups generated by the network management service production entity through translation of the intent expression are alternative operations that can be used to achieve the intent. The network management service production entity may choose to execute one of the network management action groups to achieve the intent, or it may also choose to execute the network management action groups multiple times to achieve the intent.

[0112] 7. Intent Report

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

[0114] The intent report IOC can include one or more of an Intent Fulfilment Report, an Intent Conflict Report, or an Intent Feasibility Check Report.

[0115] An intent achievement report, which can also be referred to as an intent satisfaction report, an intent realization report, or intent realization information, etc., is used to evaluate the degree of achievement of specific aspects of the intent of a network management service production entity. The intent achievement report may include achievement information of specific aspects of the intent. The achievement information is used to describe the achievement status of the specific aspect, and the achievement status can be achieved or unachieved. The specific aspect may include one or more of an intent, an intent expectation, and an expected target. That is, the intent achievement report may include one or more of the achievement information (intentFulfilmentinfo) of the intent, the achievement information (expectationfulfilmentInfo) of the intent expectation of the intent, or the achievement information (targetfulfilmentInfo) of the expected target of the intent. For example, the intent achievement report only includes the achievement information of the intent, or the intent achievement report only includes the achievement information of the expected target of the intent, or the intent achievement report includes 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, the intent includes an intent expectation, which may include expected target A and expected target B. Expected target A has been achieved, and expected target B has not been achieved. In the intent achievement report, the achievement status of the intent is unachieved, the achievement status of the intent expectation is unachieved, the achievement status of expected target A is achieved, and the achievement status of expected target B is unachieved. The achievement information of the intent expectation can also be referred to as the intent expectation achievement result (ExpectationFulfilmentResult), and the achievement information of the expected target can also be referred to as the intent expectation achievement result (TargetFulfilmentResult). The intent achievement report may also include the realized value of the expected target and optionally the predicted value of the expected target. The realized 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 realized value of the expected target evaluated by the network management service production entity. Optionally, when the achievement status is unachieved, the intent achievement report may also include the specific status of the unachievement. The specific status of the unachievement may refer to the stage at which this achievement status appears, such as the stage when the intent is just created, the stage when the intent is suspended due to a conflict, or the stage when the action group corresponding to the intent has been executed, etc.

[0116] An intent conflict report, which can also be referred to as intent conflict information, is used to describe the detected intent conflict information. The intent conflict information includes the type of conflict and possible conflict resolution solutions. The types of conflict include, but are not limited to, the following types: conflict between different intents (i.e., intent conflict), conflict between different intent expectations of the same intent (i.e., expectation conflict), or conflict between different expected targets of the same intent (i.e., target conflict).

[0117] An intent feasibility check report, which can also be referred to as intent feasibility check information, is used to indicate whether an intent is feasible or not. After receiving an intent creation request or modification request from a network management service consuming entity, a network management service producing entity can automatically perform an intent feasibility check to obtain an intent feasibility check report.

[0118] A network management service consuming entity can obtain an intent report from a network management service producing entity by querying or subscribing. For example, a network management service consuming entity can use the "getMOIAttributeValue" operation to query the intent report to obtain the intent report. Another example is that a network management service consuming entity can obtain the intent report by subscribing to the "NotifyMOIAttributeValueChanges" notification.

[0119] Exemplarily, Figure 2 A schematic structural diagram of an intent report IOC is shown.

[0120] See Figure 2 , the intent report IOC includes an intent achievement report, an intent conflict report, and an intent feasibility check report. The intent achievement report includes the expected result of intent achievement. The expected result of intent achievement includes the target achievement result. It can be understood that Figure 2 is a schematic illustration of the relationship between the attributes in the intent report IOC. Based on the network management service requirements, the intent report IOC may also include other attributes, which are not particularly limited in this application.

[0121] 8. Intent Report Template

[0122] An intent report template refers to the templatized descriptive information of an intent report, which is used to specify the syntax and semantics of the expression of the intent report. For example, the intent report template can specify the field types or value types that can be adopted by each attribute in the intent report IOC. As an example, the intent report template can include one or more of the intent achievement description information for specifying how the intent achievement report is expressed, the intent conflict description information for specifying how the intent conflict report is expressed, and the 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, value types, etc. that can be adopted by each attribute included 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. Another example is that the type of the expected target attribute includes throughput, and the value type of the actual value of the throughput is an integer. The intent conflict description information is used to indicate how the intent conflict report is represented, such as the optional attributes and types of each field in the intent conflict, such as the optional attribute of the intent conflict report is the conflict type, and the types of the conflict include intent conflict, expectation conflict, and target conflict. The intent feasibility check description information is used to indicate how the intent feasibility check report is represented.

[0123] 9. Intent Report Expression

[0124] An intent report expression is an information form that expresses the intent report of the network management service and can be the instantiation result of the intent report template. The intent report expression contains the requirements of the network management service consumption entity for the monitoring intent and reports the information reflecting the current intent achievement situation. The network management service production entity can instantiate the intent report IOC according to the intent report template to generate the intent report expression. Exemplarily, the intent report expression includes the achievement information of the current intent and the actual value of the expected target. For example, if the expected target of the intent is throughput > 10 Mbps, according to the achievement situation of the current intent, the network management service production entity will report that the intent achievement information is: achieved, and the actual value of the expected target is 12 Mbps.

[0125] 10. Intent Report Instance

[0126] An intent report instance refers to the intent report processing process created locally by the network management service production entity according to the intent report expression. The intent report instance can be automatically created by the network management service production entity when creating the network management intent. When the network management service production entity deletes the network management intent based on the request of the network management service consumption entity, the corresponding intent report instance of the network management intent will also be deleted. The intent report instance is not created or deleted by the network management service consumption entity.

[0127] The relevant terms related to the embodiments of the present application are described above. The following is combined withFigure 3 Describe the application scenarios applicable to the embodiments of this application.

[0128] Figure 3 It is a schematic structural diagram of a communication system applicable to the embodiments of this application. First, describe the devices that may be involved in this communication system.

[0129] 1. Network management service consumption entity 210: The calling entity for network management is called the network management service consumption entity. The network management service consumption entity 210 can be used to call management services, or call intent services to manage the network system. Exemplarily, the network management service consumption entity 210 can instantiate an intent template, set intent IOCs to generate intent expressions, and send the intent expressions to the network management service production network element 220 to achieve the expectations for the network system.

[0130] The network management service consumption entity 210 can also be called 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, and this application does not make specific limitations on this.

[0131] The capabilities or functions of the network management service consumption entity can be deployed on a certain network element, and this network element is called the network management service consumption network element; the capabilities or functions of the network management service consumption entity can also be deployed on other devices. In this regard, the embodiments of this application do not make limitations; for the convenience of description, the embodiments of this application use the network management service consumption entity as an example for description, but it can be replaced by other devices on which the capabilities or functions of the network management service consumption entity are deployed.

[0132] 2. Network management service production entity 220: The providing entity for network management services is called the network management service production entity. The network management service production entity 220 can be used to provide network management services. Exemplarily, the network management service production entity 220 can receive intent expressions from the network management service consumption entity 210 and perform processes of intent translation, intent management, and intent execution and maintenance based on the intent expressions.

[0133] The network management service production entity 220 can 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, which are not specifically limited in this application.

[0134] 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. In this regard, the embodiments of this application do not make any limitations; for the convenience of description, the embodiments of this application take the network management service production entity as an example for illustration, but it can be replaced by other devices on which the capabilities or functions of the network management service production entity are deployed.

[0135] The above-mentioned entity can be either a network element in a hardware device, or a software function running on dedicated hardware, or a virtualized function instantiated on a platform (such as a cloud platform). It can be understood that the above-mentioned entity can be implemented by one device, or can also be jointly implemented by multiple devices. 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). The network equipment can be a base station or a core network element.

[0136] As an example, the network management service consumption entity 210 can be deployed within the NMS, and the network management service production entity 220 can be deployed within different EMSs. The interaction between the network management service consumption entity 210 and the network management service production entity 220 can perform information interaction through the interface between the NMS and the EMS.

[0137] As another example, the network management service consumption entity 210 can be deployed within the EMS, and the network management service production entity 220 can be deployed within different NEs. The interaction between the network management service consumption entity 210 and the network management service production entity 220 can perform information interaction through the interface between the NMS and the EMS.

[0138] Optionally, the above 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 deploying an NDT system, which can be used to provide network management services.

[0139] The solution of this application can also be applied to other systems containing corresponding entities, which are not limited in this application, and the embodiments of this application do not make specific limitations on this.

[0140] For the sake of simplicity of description hereinafter, the network management intent is abbreviated as intent, the network management service consumption entity is abbreviated as consumption entity, the network management service production entity is abbreviated as production entity, and the desired target is abbreviated as target.

[0141] Currently, when the intent fails to be achieved due to conflicts or other reasons, the production entity can generate possible solutions based on the current network state and recommend them to the consumption entity. There are three common types of solutions:

[0142] 1) Suspend the whole intent;

[0143] 2) Recommend a new intent, such as adding recommended expectations or targets, terminating part of the intent, etc.;

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

[0145] For example, the target of the intent is to ensure that the uplink throughput rate of a certain venue is greater than 20 Mbps. The production entity monitors the current network state and finds that the target of this intent cannot be achieved. Based on the current network state, the production entity calculates that the maximum achievable uplink throughput rate is 15 Mbps, and at the same time predicts the future network state, expecting that the target of the intent can be achieved after 5 hours (h). The production entity can generate and recommend the following possible solutions to the consumption entity: 1. Terminate this intent; 2. Recommend a new intent, and the target of the new intent is to ensure that the uplink throughput rate is greater than 15 Mbps; 3. Update the execution time of the intent to 5 h later.

[0146] However, the solutions generated by the production entity may include many useless solutions. Useless solutions can be understood as solutions that are difficult to meet the business requirements of the consumption entity, that is, solutions that cannot meet the specific needs of the consumption entity in a specific business scenario, that is, solutions that the consumption entity will not consider at all. Taking the intention of the drone natural gas pipeline inspection scenario as an example, when this intention cannot be achieved, the solution recommended by the production entity for a new object of action is a useless solution because the drone needs to conduct inspections along the pipeline, so the object of action cannot be changed. The generation of useless solutions will consume the computing power resources of the production entity, resulting in a waste of computing power resources. At the same time, useless solutions will also increase the difficulty of selection for the consumption entity and increase the burden on the consumption entity.

[0147] In view of the above problems, the present application provides a method, device, and system for managing network management intentions, in order to reduce the waste of computing power resources of the production entity and reduce the burden on the consumption entity.

[0148] The method embodiments of the present application will be described below.

[0149] Figure 4 It is a schematic flowchart of the network management intention management method 300 provided by the present application.

[0150] Figure 4 The method shown can be executed by the production entity and the consumption entity. Without special instructions, the "production entity" or "consumption entity" can refer to the production entity or consumption entity itself, or can refer to a device that can support the production entity or consumption entity to realize its functions. For the convenience of description, the production entity and the consumption entity are used for description below. The method 300 includes at least some of the following content.

[0151] Step 301, the consumption entity sends the first information to the production entity. Correspondingly, the production entity receives the first information from the consumption entity.

[0152] Among them, the first information is used to indicate the preference of the consumption entity for the solution, and the preference corresponds to the first intention.

[0153] The first intention can be various types of intentions. The type of the first intention can be related to the target included in the first intention. Exemplarily, the target of the intention includes that the performance index value reaches the corresponding performance index range. When the performance index is the throughput rate index, for example, the average downlink throughput rate is greater than or equal to 5 Mbps, this intention can be called the throughput rate intention; when the performance index is the energy saving index, for example, the energy saving is greater than or equal to 10 kilowatts, this intention can be called the energy saving intention.

[0154] This preference corresponds to the first intention, which can be understood as: this preference applies to the first intention, or this preference is used when the goal of the first intention cannot be achieved. The solution can be a solution for the situation where the goal of the first intention cannot be achieved. For example, as mentioned above, aborting the entire first intention, recommending a new intention, or recommending other feasible intention implementations, etc. The preference for the solution can be understood as: the preference of the consuming entity for the solution to the situation where the goal of the first intention cannot be achieved. The consuming entity can use this preference to restrict the producing entity from generating solutions that do not meet this preference.

[0155] The embodiments of the present application do not limit the implementation manner of the first information. In a possible implementation manner, the first information may include the first attribute of the first intention. Among them, the first attribute is an attribute that the consuming entity does not expect to change. In this case, the consuming entity prefers a solution that does not change the first attribute, that is, the consuming entity expects the producing entity to recommend a solution that conforms to the first attribute or a solution with the first attribute unchanged when the first intention cannot be achieved. Or, the first attribute is an attribute that can be changed. If the first intention further 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 where only the first attribute of the first intention can be changed, the consuming 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 consuming entity expects the producing entity to recommend a solution that conforms to the attributes other than the first attribute, a solution with the attributes other than the first attribute unchanged, or a solution that only changes the first attribute when the first intention cannot be achieved.

[0156] It should be noted that 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 guarantee, or the attribute that the consuming entity expects to maintain, etc. The first attribute being an attribute that can be changed can also be described as: the attribute that the consuming entity allows to change, the attribute that does not need to be guaranteed, or the attribute that does not need to be maintained, etc.

[0157] 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 of action, or a context. The target may also be referred to as an expected target, and the object of action may also be referred to as an expected object. The object of action can be used to determine the entity to be managed that the intention expects. The first attribute including at least one of a target, an object of action, or a context can also be described as: the value of the first attribute can be a target, an object of action, a context, or any combination of the three. Or, the value of the first attribute corresponds to a target, an object of action, a context, or any combination of the three.

[0158] Example 1. Taking the first attribute as an attribute that the consuming entity does not expect to change as an example, when the first attribute is the target, it indicates that when the first intention cannot be achieved, the consuming entity does not accept the downgrading of the intention target. Or rather, when the first intention cannot be achieved, the consuming entity expects the producing entity to recommend a solution that can meet the target, that is, the consuming entity expects the producing entity to recommend a solution with an unchanged target. For example, for the intention of drone material transportation, the intention target is to ensure that the uplink bandwidth of the drone is greater than 300 kbps, the object of action is the TAC area passed by the flight path, and the first attribute is the target. After this intention is issued, the producing entity monitors the network status of the TAC area passed by the flight path and finds that the target of this intention cannot be achieved. Since the preference of the consuming entity for the solution indicates that the target of the intention cannot be changed (that is, the target of ensuring that the uplink bandwidth of the drone is greater than 300 kbps cannot be changed), the producing entity can recommend other objects of action. For example, update the object of action of this intention to another TAC area (such as a feasible TAC area near the infeasible TAC area). When the first attribute is the object of action, it indicates that when the first intention cannot be achieved, the consuming entity expects the producing entity to recommend a solution that can meet the object of action, that is, the consuming entity expects the producing entity to recommend a solution with an unchanged object of action. For example, for the intention of drone natural gas pipeline inspection, the target of this intention is to ensure that the uplink throughput rate is greater than 25 Mbps, the object of action is the TAC area passed by the flight path, and the first attribute is the object of action. After this intention is issued, the producing entity monitors the network status of the TAC area passed by the flight path and finds that the target of this intention cannot be achieved. Since the preference of the consuming entity for the solution indicates that the object of action of the intention cannot be changed, the producing entity does not change the TAC area as the object of action, but changes the target of the intention. For example, it can recommend updating the target of this intention to ensure that the uplink throughput rate is greater than 20 Mbps.

[0159] Example 2. Taking the first attribute as the changeable attribute and the attributes other than the first attribute as the unchangeable attributes, when the first attribute is the target, it indicates that when the first intention cannot be achieved, the consuming entity expects the producing entity to recommend a solution that can meet the attributes other than the target, that is, the consuming entity expects the producing entity to recommend a solution with the attributes other than the target unchanged. For example, for the intention of an unmanned aerial vehicle (UAV) to inspect a natural gas pipeline, the target of this intention is to ensure that the uplink throughput rate is greater than 25 Mbps, the object of action is the TAC area passed by the flight path, and the first attribute is the target. After this intention is issued, the producing entity monitors the network status of the TAC area passed by the flight path and finds that the target of this intention cannot be achieved. Since the preference of the consuming entity for the solution indicates that the target of the intention is changeable (that is, the target of ensuring the uplink throughput rate is greater than 25 Mbps is changeable, and the object of action, the TAC area, is unchangeable), the producing entity can change the target of the intention and keep the area of action unchanged. For example, it is recommended to update the target of this intention to ensure that the uplink throughput rate is greater than 20 Mbps and keep the object of action, the TAC area, of the intention unchanged. When the first attribute is the object of action, it indicates that when the first intention cannot be achieved, the consuming entity expects the producing entity to recommend a solution that can meet the attributes other than the object of action, that is, the consuming entity expects the producing entity to recommend a solution with the attributes other than the object of action unchanged. For example, for the intention of an unmanned aerial vehicle to transport supplies, the target of this intention is to ensure that the uplink bandwidth of the UAV is greater than 300 kbps, the object of action is the TAC area passed by the flight path, and the first attribute is the object of action. After this intention is issued, the producing entity monitors the network status of the TAC area passed by the flight path and finds that the target of this intention cannot be achieved. Since the preference of the consuming entity for the solution indicates that the object of action of the intention is changeable (that is, the object of action, the TAC area, is changeable, and the target of ensuring the uplink bandwidth of the UAV is greater than 300 kbps is unchangeable), the producing entity can change the area of action and keep the target of the intention unchanged. For example, it is recommended to update the object of action of this intention to another TAC (such as a feasible TAC area near the infeasible TAC area) and keep the target of ensuring the uplink bandwidth of the UAV is greater than 300 kbps unchanged.

[0160] 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. Exemplarily, taking the first attribute as the object of action and the first attribute as the attribute that the consuming entity does not expect to change as an example, when the first attribute is for the entire intention, the first attribute represents the object of action of all intention expectations of the intention, that is, the consuming entity expects the producing entity to recommend a solution that does not change the object of action 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 object of action of this intention expectation, that is, the consuming entity expects the producing entity to recommend a solution that does not change the object of action of this intention expectation when the intention cannot be achieved. Exemplarily, taking the first attribute as the goal and the first attribute as the attribute that the consuming 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 consuming entity expects the producing entity to recommend a solution that does 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 of this intention expectation, that is, the consuming entity expects the producing entity to recommend a solution that does not change all expected goals of this intention expectation when the intention cannot be achieved; when the first attribute is for a certain expected goal, the first attribute represents this expected goal, that is, the consuming entity expects the producing entity to recommend a solution that does not change this expected goal when the intention cannot be achieved.

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

[0162] A possible implementation manner is that the consuming entity can send the first information to the producing entity as a separate information.

[0163] Another possible implementation manner is that the consuming entity can send a third message to the producing entity, and the third message includes the first information.

[0164] 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 intention management.

[0165] Exemplarily, the third message can be used to create or request to create an intention. For example, the third message is an intention creation request message. When the third message is used to create or request to create an intention, there are many ways for the third message to carry the first information, without limitation. A possible implementation manner is that the third message can include an intention and the first information, where the intention can be represented as an instantiated intention IOC (such as Figure 1 shown). Another possible implementation manner is that the third message can include an intention, and the intention includes the first information, where the intention can be represented as an instantiated intention IOC (such as Figure 1as shown). For example, the intent IOC corresponding to the intent includes an intent expectation and an intent context, and the intent context includes first information. Another example is that the intent IOC corresponding to the intent includes an intent expectation, the intent expectation includes an expectation context, and the expectation context includes first information. Still another example is that the intent IOC corresponding to the intent includes an intent expectation, the intent expectation includes an expectation target, the expectation target includes a target context, and the target context includes first information.

[0166] Exemplarily, the third message can be used to modify or request to modify an intent. For example, the third message is an intent modification request message. When the third message is used to modify or request to modify an intent, there are many ways for the third message to carry the first information, which is 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 intent expectation of the intent and the first information. In another possible implementation, the third message may include an identifier of the expectation target of the intent and the first information. In another possible implementation, if the third message realizes the modification function by carrying the modified intent IOC, then the first information may also be included in the intent IOC of the intent.

[0167] It should be noted that the first information can also be described as: the first information is used to indicate an intent expression that the consuming entity does not expect, and the unexpected intent expression corresponds to a first intent, or the first information is used to indicate an intent expression that the consuming entity expects, and the expected intent expression corresponds to a first intent. The intent expression corresponds to a solution, and the intent expression can be a specific expression form of the solution. In the embodiments of the present application, the solution includes a new intent expression used to replace the original intent. The new intent expression can be a complete structured intent expression, or can only include the intent expression that needs to be modified, added, or deleted.

[0168] Step 302, when the goal of the first intent cannot be achieved, the producing entity sends a second information to the consuming entity, and correspondingly, the consuming entity receives the second information from the producing entity.

[0169] Wherein, the second information is used to indicate one or more recommended solutions.

[0170] The solutions in the one or more recommended solutions are solutions for the situation where the goal of the first intent cannot be achieved, and may include, for example, aborting the entire first intent, recommending a new intent, or recommending other feasible intent implementations mentioned above.

[0171] One or more recommended solutions satisfy the consumption entity's preferences for the solution. Exemplarily, when the first information includes a first attribute that the consumption entity does not expect to change, the solution that satisfies the consumption entity's preferences for the solution does not change the first attribute. In this case, one or more recommended solutions do not change the first attribute. Combining with Example 1 in Step 301, when the first attribute is the target, for the intention of unmanned aerial vehicle (UAV) material transportation, one or more recommended solutions are: updating the object of the first intention to another TAC area, that is, the second information indicates updating the object of the first intention to another TAC area. When the first attribute is the object, for the intention of UAV natural gas pipeline inspection, one or more recommended solutions are: updating the target of the first intention to ensure that the uplink throughput rate is greater than 20 Mbps, that is, the second information indicates updating the target of the first intention to ensure that the uplink throughput rate is greater than 20 Mbps. Exemplarily, when the first information includes a changeable first attribute, the solution that satisfies the consumption entity's preferences for the solution does not change the attributes other than the first attribute. In this case, one or more recommended solutions do not change the attributes other than the first attribute. Combining with Example 2 in Step 301, when the first attribute is the target, for the intention of UAV natural gas pipeline inspection, one or more recommended solutions are: updating the target of the first intention to ensure that the uplink throughput rate is greater than 20 Mbps, that is, the second information indicates updating the target of the first intention to ensure that the uplink throughput rate is greater than 20 Mbps. When the first attribute is the object, for the intention of UAV material transportation, one or more recommended solutions are: updating the object of the first intention to another TAC, that is, the second information indicates updating the object of the first intention to another TAC. A more detailed description can refer to Example 1 and Example 2 in Step 301.

[0172] It should be noted that 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. One or more recommended solutions do not change the 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 the attributes other than the first attribute, or one or more recommended solutions maintain the attributes other than the first attribute, etc.

[0173] In some embodiments, the production entity may determine that the goal of the first intention cannot be achieved. Embodiments of the present application do not limit the implementation manner of determining that the goal of the first intention cannot be achieved. In one possible implementation manner, the production entity performs a feasibility check for 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 manner, 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, the production entity determines that the goal of the first intention has not been achieved according to the realization value of the goal of the intention after the first intention is executed.

[0174] Embodiments of the present application do not limit the implementation manner of the production entity performing a feasibility check for the first intention. In one possible implementation manner, the production entity itself performs a feasibility check for the first intention. In another possible implementation manner, the production entity requests the first network element to perform a feasibility check for the first intention, where the first network element may be a knowledge base or a network twin service production entity, etc.

[0175] In some embodiments, in the case where the goal of the first intention cannot be achieved, the production entity may obtain the second information according to the first information. Embodiments of the present application do not limit the implementation manner of the production entity obtaining the second information according to the first information.

[0176] In one possible implementation manner, the production entity may determine the second information according to the first information. For example, the production entity may generate a solution that meets the preferences of the consuming entity for the solution based on the current network state and the first information, and then determine the second information. The network state is the state of network performance metrics related to the goal of the intention. For example, for a throughput intention, the current network state may include the throughput of the current network. For another example, for an energy-saving intention, the current network state may include the energy consumption of the current network.

[0177] In another possible implementation manner, 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 the third information to the first network element according to the first information, where the third information is used to indicate the preference of the consuming entity for the solution or the third information is used to indicate the solution type corresponding to the preference; after receiving the third information, the first network element may generate a solution that meets the preference of the consuming entity for the solution according to the third information, and then determine the second information; the first network element sends the second information to the production entity, and correspondingly, the production entity receives the second information from the first network element.

[0178] When the third information is used to indicate the preference of the consuming entity for the solution, the form of the third information may be the same as or different from that of the first information. For example, when the producing entity forwards the first information to the first network element, the form of the third information may be the same as that of the first information. For another example, the producing entity may convert the first information into the third information that can be recognized and used by the first network element, and the third information may be used to instruct the first network element to perform a query or simulation operation that meets the preference of the consuming entity for the solution.

[0179] When the third information is used to indicate the type of solution corresponding to the preference, the producing entity also determines the type of solution corresponding to the preference according to the first information, where the type of solution corresponding to the preference may indicate the operations that the first network element needs to perform, such as detecting the feasible objects of the intention, detecting the feasible time of the intention, etc.

[0180] The embodiments of the present application do not limit the manner in which the producing 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 producing entity. The third information and the second information may be carried in any message that is exchanged between the producing entity and the first network element. For example, in the case where the first network element performs a feasibility check for the first intention, the producing entity may send a first message to the first network element, where the first message is used to request a feasibility check for the first intention and the first message includes the third information, and the first network element may send a second message to the producing entity, where the second message is used to indicate the result of the feasibility check and the second message includes the second information. In one manner, when the result of the feasibility check for the first intention is infeasible, the first network element sends the above second message to the producing entity.

[0181] It should be noted that one or more recommended solutions may also be described as: one or more recommended intention expressions. The relationship between the intention expression and the solution may refer to the description in step 301.

[0182] 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 that interacts between the production entity and the consumer entity. In a possible implementation, the production entity sends an intention report to the consumer entity, and the intention report includes the second information. Among them, 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. The description of the intention report, the intention satisfaction report, the intention conflict report, or the intention feasibility check report can refer to the term explanation section. Exemplarily, for the case where the production entity determines that the goal of the first intention cannot be achieved based on the result of the feasibility check, the production entity can send an intention feasibility check report to the consumer entity, wherein the intention feasibility check report is used to indicate the result of the feasibility check and the intention feasibility check report includes the second information. Exemplarily, for the case where the production entity determines that the goal of the first intention cannot be achieved based on the realization value of the goal of the first intention, the production entity can send an intention satisfaction report to the consumer entity, wherein the intention satisfaction report includes the second information. Exemplarily, when the production entity determines that there is a conflict in the first intention (such as a conflict between the first intention and other intentions, a conflict within the first intention, etc.), the production entity can send an intention conflict report to the consumer entity, wherein the intention conflict report includes the second information.

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

[0184] In an embodiment of the present application, the consumer entity manages the first intent according to 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 according to 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.

[0185] In method 300, the consumer entity can indicate a preference for a solution to the producer entity, and when the intended goal cannot be achieved, the producer entity can generate a solution that satisfies the preference without generating a solution that does not satisfy the preference. In this way, method 300 helps to prevent the producer entity from generating a solution that the consumer entity will not consider at all, thereby reducing the waste of computing resources and alleviating the burden on the consumer entity.

[0186] The following takes 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 to describe method 300 in detail.

[0187] Figure 5 It is a schematic flowchart of the network management intention management method 400 provided by this application. The intention service consumer, intention service producer, network twin service producer, solution preference attribute, intention creation request message, feasibility check request message, feasibility check response message, message #1, and information #1 in method 400 respectively correspond to the consumption entity, production entity, network twin production entity, first information, third message, first message, second message, intention feasibility check report, and third information above.

[0188] Step 401, the intention service consumer sends an intention creation request message to the intention service producer. Correspondingly, the intention service producer receives the intention creation request message from the intention service consumer.

[0189] Among them, the intention creation request message is used to request the creation of an intention. The intention creation request message includes the target of the intention, the object of action of the intention, and the solution preference attribute.

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

[0191] The optional values of the solution preference attribute can be [target, object], and the specific meanings are as follows:

[0192] 1) When the value of the solution preference attribute is the object, it indicates that when the intention cannot be achieved, a solution that conforms to the object is recommended, that is, a solution with the same object is recommended. This value can be the default value. When the value of the solution preference attribute is the object, compared with the original intention, the object of the new intention accepted by the intention service consumer is the same.

[0193] 2) When the value of the solution preference attribute is the target, it indicates that when the intention cannot be achieved, a solution that conforms to the target is recommended, that is, a solution with the same target is recommended. When the value of the solution preference attribute is the target, compared with the original intention, the target of the new intention accepted by the intention service consumer is the same.

[0194] The specific meanings of the optional values of the solution preference attribute can refer to step 301 and will not be elaborated here.

[0195] It should be noted that the solution preference attribute can also have other names, as long as its function is to describe the preference of the intended service consumer for the solution recommended by the intended service producer. For example, the recommendation preference attribute, etc. It should also be noted that the solution preference attribute can be for the entire intention or for a certain intention expectation or a certain expected goal of the intention, without limitation. For specific details, reference can be made to the description in the first attribute part.

[0196] Exemplarily, the intended service consumer can be an information technology (IT) system independently developed by the customer, etc., and the intended service producer can be the device network management of the manufacturer, such as the mobile broadband automation engine (MAE), etc.

[0197] There are many ways for the intention creation request message to carry the solution preference attribute, without limitation. For the specific implementation method, reference can be made to the sending method of the first piece of information.

[0198] Step 402: The intended service producer creates and configures an intended managed object instance (MOI) according to the intention creation request message.

[0199] Step 403: The intended service producer sends an intention creation response message to the intended service consumer. Correspondingly, the intended service consumer receives the intention creation response message from the intended service producer.

[0200] Among them, the intention creation response message includes the identifier of the intention and indication information #1. The indication information #1 is used to indicate whether the intention is successfully created. In method 400, the indication information indicates that the intention is successfully created.

[0201] Step 404: The intended 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 intended service producer to perform a feasibility check on the intention.

[0202] Among them, the feasibility check request message, in addition to requesting a feasibility check on the intent, may also include Information #1, which is used to indicate to the network twin service producer the preferences of the intent service consumer for the solution. Among them, the feasibility check may include: checking the satisfaction of intent fulfilment, or whether there are potential conflicts, etc., where the potential conflicts include at least one of the conflicts between different intents, the conflicts between different intent expectations of the same intent, or the conflicts between different expected goals of the same intent.

[0203] 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 detecting the feasible objects of the intent, detecting the feasible time of the intent, etc. This recommended solution type can be determined by the intent service producer based on the solution preference attributes from the intent service consumer.

[0204] Exemplarily, Information #1 may also include the solution preference attributes received in step 401.

[0205] Step 405, the network twin service producer performs a feasibility check on the intent.

[0206] When the result of the feasibility check of the intent is not passed (or infeasible), the network twin service producer may generate a recommended solution based on Information #1.

[0207] Step 406, the network twin service producer sends a feasibility check response message to the intent service producer. Correspondingly, the intent service producer receives the feasibility check response message from the network twin service producer.

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

[0209] 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.

[0210] Among them, Message #1 is a feedback message for intent feasibility check, which can carry an intent feasibility check report and can include an intent identifier, indication information #3, and an optional recommended solution. When the check result of the intent feasibility check is passed (or feasible), Message #1 may not include a recommended solution. When the check result of the intent feasibility check is not passed (or infeasible), Message #1 includes a recommended solution. When the indication information #3 indicates that the result of the intent feasibility check is not passed (or infeasible), Message #1 also includes a possible failure reason.

[0211] It should be noted that the embodiments of the present application do not limit the execution 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 creation response message and Message #1 can be the same message (that is, Step 403 and Step 407 are the same step), or the intent creation response message and Message #1 can be different messages, without limitation.

[0212] Optionally, in Step 408, the intent service consumer sends Message #2 to the intent service producer. Correspondingly, the intent service producer receives Message #2 from the intent service consumer.

[0213] Among them, Message #2 is used to indicate whether the intent service consumer accepts or rejects the recommended solution.

[0214] 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.

[0215] Specifically, the intent service producer can update the intent based on Message #2, generate a network deployment according to the updated intent, and configure and deploy the managed entity according to the generated network deployment. Then, the intent service consumer, the intent service producer, the network twin service producer, and the managed entity execute the updated intent.

[0216] After Step 407, the intent service consumer can indicate to the intent service producer whether to accept or reject the recommended solution as shown in Steps 408 and 409, or can also issue a new intent or modify the intent to the intent service producer based on the recommended solution.

[0217] In method 400, a solution preference attribute can be added to the intent model. Through this attribute, the intent service consumer can 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 consuming computing power resources in generating useless solutions, and also reducing the burden on the intent service consumer in making selections.

[0218] Taking the example of carrying the first information in the intent 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 intent report, method 300 will be described in detail below.

[0219] Figure 6 It is a schematic flowchart of the network management intent management method 500 provided by this application. The intent service consumer, intent service producer, network twin service producer, solution preference attribute, intent creation request message, message #3, message #4, and information #2 in method 500 respectively correspond to the consumption entity, production entity, network twin production entity, first information, third message, first message, second message, and third information above.

[0220] 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.

[0221] Among them, the intent creation request message is used to request the creation of an intent. The intent creation request message includes the target of the intent, the object of action of the intent, and the solution preference attribute.

[0222] Step 502, the intent service producer creates and configures the intent MOI according to the intent creation request message.

[0223] 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.

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

[0225] Steps 501 to 503 can refer to steps 401 to 403 and will not be elaborated further.

[0226] Step 504, the intent service producer conducts a feasibility check on the intent.

[0227] In method 500, the result of the feasibility check of the intent is passed.

[0228] It should be noted that the order of steps 503 and 504 in the embodiments of this application is not limited. Step 503 may be executed before step 503 as shown, or after step 504, without limitation. Figure 5

[0229] Step 505, the intent service producer executes the intent and monitors the achievement of the intent.

[0230] Step 506, when the intent service producer determines that the intent fails to be achieved, the intent service producer sends message #3 to the network twin service producer. Correspondingly, the network twin service producer receives message #3 from the intent service producer.

[0231] Among them, message #3 is used to obtain a recommended solution.

[0232] Message #3 may include information #2, and information #2 is used to indicate to the network twin service producer the preferences of the intent service consumer for the solution. Exemplarily, information #2 may include a recommended solution type, and the recommended solution type 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 detecting the feasible objects of the intent, detecting the feasible time of the intent, etc. The recommended solution type may 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.

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

[0234] Step 508, the network twin service producer sends message #4 to the intent service producer. Correspondingly, the intent service producer receives message #4 from the network twin service producer.

[0235] Among them, message #4 is the recommended solution.

[0236] 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.

[0237] Among them, the intent satisfaction report is used to indicate that the goal of the intent is not achieved and the recommended solution. Exemplarily, the intent satisfaction report includes the identifier of the intent, the achievement information, the reason for non - achievement, and the recommended solution, and the achievement information is used to indicate that the intent is not achieved.

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

[0239] Among them, message #5 is used to indicate that the intent service consumer accepts or rejects the recommended solution. When the intent service consumer accepts the recommended solution, message #5 may include the intent obtained based on the recommended solution, and the intent service producer may modify or configure the intent according to message #5.

[0240] 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.

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

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

[0243] In method 500, a solution preference attribute may be added to the intent model. The intent service consumer may use this attribute to restrict the intent service producer from generating certain solutions, thereby assisting the intent service producer to optimize the recommended solutions, helping to avoid the intent service producer consuming computing power resources in generating useless solutions, and at the same time reducing the burden on the intent service consumer in making choices.

[0244] As described above in conjunction with Figures 1 to 6 , the method embodiments provided in this application have been described in detail. Next, the device embodiments of this application will be described in conjunction with Figures 7 to 9 .

[0245] It can be understood that, in order to implement the functions in the above embodiments, Figures 7 to 9 the devices in

[0246] Figure 7 and Figure 8The structural schematic diagram of a possible device provided for the embodiments of the present application. These devices can be used to implement the functions of the production entity, the consumption entity, or the first network element in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments.

[0247] As Figure 7 shown, the device 10 includes a transceiver unit 11 and a processing unit 12.

[0248] When the device 10 is used to implement the function of the production entity in the above method embodiments, the transceiver unit 11 is used to execute the transceiver steps of the production entity, 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 processing steps of the production entity, such as steps 402, 409, 502, 504, 505, 511 or 511. When the device 10 is used to implement the function of the consumption entity in the above method embodiments, the transceiver unit 11 is used to execute the transceiver steps of the consumption entity, such as steps 301, 302, 401, 403, 407, 408, 501, 503, 509 or 510, and the processing unit 12 is used to execute the processing steps of the consumption entity, such as steps 303, 409 or 511. When the device 10 is used to implement the function of the first network element in the above 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.

[0249] For a more detailed description of the above transceiver unit 11 and processing unit 12, reference can be made to the relevant descriptions in the above method embodiments, which will not be elaborated here.

[0250] As Figure 8 shown, the device 20 includes a processor 21. The processor 21 is coupled to a memory 23, and the memory 23 is used to store instructions. When the device 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 function of the above processing unit 12.

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

[0252] Optionally, the device 20 further includes an interface circuit 22. The processor 21 and the interface circuit 22 are coupled to each other. It can be understood that the interface circuit 22 can be a transceiver or an input / output interface. When the device 20 is used to implement the method described above, the processor 21 is used to execute instructions to implement the function of the above processing unit 12, and the interface circuit 22 is used to implement the function of the above transceiver unit 11.

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

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

[0255] Among them, 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 embodiments of the present application. The input / output interface 32 may be an input / output circuit in the chip system 30, output the information processed by the chip system 30, or input the data or signaling information to be processed into the chip system 30 for processing.

[0256] 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 method embodiments.

[0257] 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 embodiments; 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 embodiments.

[0258] The present application also provides a communication device, including a processor, the processor is coupled to a memory, the memory is used to store computer programs or instructions and / or data, the processor is used to execute the computer programs or instructions stored in the memory, or read the data stored in the memory, so as to execute the methods in the above method embodiments. Optionally, the processor is one or more. Optionally, the communication device includes a memory. Optionally, the memory is one or more. Optionally, the memory is integrated with the processor or is separately provided.

[0259] The present application also provides a chip, including a processor, the processor being coupled to a memory, the memory being configured to store computer programs or instructions, and the processor being configured to execute the computer programs or instructions stored in the memory to implement the methods performed by the production entity, the consumption entity, or the first network element in the foregoing method embodiments.

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

[0261] The present application also provides a computer program product, including instructions that, when executed by a computer, implement the methods performed by the production entity, the consumption entity, or the first network element in the foregoing method embodiments.

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

[0263] For the explanations and beneficial effects of the relevant content in any of the foregoing devices, reference may be made to the corresponding method embodiments provided above, and details are not described herein again.

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

[0265] The method steps in the embodiments of the present application can be implemented in a hardware manner or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a removable hard disk, a 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, enabling the processor to read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in a production entity, a consumer 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 consumer entity, or a first network element.

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

[0267] In the various embodiments of the present application, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be cross-referenced, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0268] Unless otherwise specified, all technical and scientific terms used in the embodiments of this application have the same meanings as those commonly understood by those skilled in the technical field of this 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 this application. It should be understood that the above is for illustrative purposes, and the above examples are only to help those skilled in the art understand the embodiments of this application, rather than limiting the embodiments of the application to the specific numerical values or specific scenarios shown. Obviously, those skilled in the art can make 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 this application.

Claims

1. A management method for network management intents, characterized in that, The method includes: Receiving 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 intent; In the case where the objective 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 be changed, 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 objective of the first network management intent cannot be achieved.

6. The method according to claim 5, wherein The determining that the objective of the first network management intent cannot be achieved includes: After performing an action group for the first network management intent, determining that the objective 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, characterized in that The determining that the objective 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 objective 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 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 be changed, 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 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, 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; In a case where the objective of the first network management intention cannot be achieved, the production entity sends second information, and the consuming entity receives the second information, where the second information is used to indicate one or more recommended solutions that meet 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 send second information to the consuming entity in a case where the objective of the first network management intention cannot be achieved, where the second information is used to indicate one or more recommended solutions that meet 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 meet 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 meet 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, and when the computer program or instructions are executed by a communication device, the method according to any one of claims 1 to 22 is implemented.

29. A communication system, characterized in that, It includes 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.

Images