Management method, management device and system of network management intention

Abstract

A network management intent management method, management device and system, a consumer entity being able to subscribe to a production entity to send an intent report to the production entity when a stable implementation value of a target of a network management intent fails to reach the target of the network management intent, the implementation value of the target of the intent indicated by the intent report received by the consumer entity is always stable and reliable. Alternatively, the production entity may indicate to the consumer entity, via the intent report, whether the implementation value of the intent target is stable. A decision is made based on the two intention reports, and the consumer entity can select a proper opportunity to intervene or manage execution of the network management intention, so that the probability of misjudgment is reduced, and resource waste is reduced.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and more particularly, 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. The network management service consuming entity may send a message to the network management service producing entity, causing the network management service producing entity to execute the network management intent, with the expectation that the specified performance metrics of network devices within a specific range reach the expected goals. During this process, the network management service consuming entity may intervene in the execution of the network management intent by sending a message to the producing entity, including modifying or deleting the network management intent, etc.

[0003] However, such a management mechanism may result in the failure to achieve a network management intent that could have been achieved due to misjudgment, causing waste of resources.

[0004] For network management service consuming entities, how to select an appropriate timing to intervene in or manage the execution of network management intents is a technical problem that needs to be solved. Summary of the Invention

[0005] Embodiments of this application provide a method, apparatus, and system for managing network management intents, which helps consuming entities select an appropriate timing to intervene in or manage the execution of network management intents, thereby helping to reduce misjudgment and waste of resources.

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

[0007] The method includes: receiving an intent report from a producing entity, where the intent report indicates that the stable achievement value of the target of the network management intent fails to reach the target of the network management intent; and managing the network management intent according to the intent report.

[0008] Based on the above method, the producing entity may indicate to the consuming entity that the stable achievement value of the target of the intent fails to reach the target of the intent. The intent report indicates the stable achievement value of the target of the intent. Compared with the prior art where the intent report simply indicates the achievement value of the target of the intent, the consuming entity can learn that the achievement value of the target of the intent is stable and reliable. Furthermore, based on this stable and reliable achievement value, the consuming entity can select an appropriate timing to intervene in or manage the execution of the intent, which helps reduce the probability of misjudgment and thus reduces waste of resources.

[0009] In combination with the first aspect, in some possible implementation manners, the method further includes: sending request information to the production entity, where the request information is used to request the production entity to send the intention report.

[0010] Based on the above implementation manner, the consumption entity can request the intention report from the production entity. Correspondingly, the production entity can send the intention report based on the request of the consumption entity. Compared with the production entity reporting the intention report periodically, this manner helps to reduce the signaling overhead caused by reporting the intention report.

[0011] In combination with the first aspect or any of its implementation manners, in some other possible implementation manners, the sending the request information to the production entity includes: sending a subscription request message to the production entity, where the subscription request message includes the request information.

[0012] Based on the above implementation manner, the consumption entity can obtain the intention report from the production entity based on the subscription method.

[0013] In combination with the first aspect or any of its implementation manners, in some other possible implementation manners, the request information includes the network management intention or an identifier of the network management intention.

[0014] Exemplarily, the identifier of the intention is information that can uniquely determine the intention, such as the name or number of the intention, etc.

[0015] In combination with the first aspect or any of its implementation manners, in some other possible implementation manners, the request information includes indication information, where the indication information is used to indicate that an intention report is to be sent when the stable implementation value of the target of the network management intention fails to reach the target of the network management intention.

[0016] Based on the above implementation manner, the consumption entity can require the production entity to send an intention report to it when the target of the intention is not achieved and the implementation value of the target of the intention has stabilized. In this case, the implementation value of the target of the intention indicated by the intention report received by the intention service consumer is always stable and reliable. The consumption entity manages the intention based on the stable and reliable implementation value, which helps to select an appropriate time to intervene or manage the execution of the intention, thereby helping to reduce the probability of misjudgment and thus reducing resource waste.

[0017] In addition, the production entity only reports the intention report to the consumption entity when the target of the intention is not achieved and the implementation value of the target of the intention has stabilized, which helps to reduce the signaling overhead.

[0018] Combined with the first aspect or any implementation thereof, in some other possible implementations, the stable implementation value includes: the implementation value of the objective of the network management intention when all action groups for the network management intention have become effective, where the action group includes one or more actions for managing the managed entities of the network management intention; or, the implementation value of the objective of the network management intention when the performance metric value of the managed entity of the network management intention continuously remains within a first range within a first observation duration.

[0019] Combined with the first aspect or any implementation thereof, in some other possible implementations, the method further includes: sending first information to the production entity, where the first information is used to indicate the first observation duration and / or the first range; where the first observation duration is the observation duration required to determine that the implementation value of the objective of the network management intention is stable, and the first range is the fluctuation range that the implementation value of the objective of the network management intention needs to satisfy to be stable.

[0020] Based on the above implementation, the consumer entity can customize the metrics for measuring whether the implementation value of the objective of the intention is stable, so that the stability of the objective of the intention reported by the production entity better meets the expectations of the consumer entity, can better assist the consumer entity in making decisions, helps the consumer entity select an appropriate time to intervene or manage the execution of the intention, and thus helps reduce the probability of misjudgment and waste of resources.

[0021] Combined with the first aspect or any implementation thereof, in some other possible implementations, the sending the first information to the production entity includes: sending a creation message to the production entity, where the creation message is used to request the creation of the network management intention. Where the creation message includes the network management intention, the network management intention includes the first information, or the creation message includes the network management intention and the first information.

[0022] Combined with the first aspect or any implementation thereof, in some other possible implementations, the managing the network management intention according to the intention report includes: sending a first request message to the production entity, where the first request message is used to request the production entity to delete the network management intention; or, sending a second request message to the production entity, where the second request message is used to request the production entity to modify the network management intention, where the modifying the network management intention includes one or more of the following operations: reducing the expected value of the unachieved objective of the network management intention, replacing the action group for the network management intention, or increasing the priority of the network management intention.

[0023] Combined with the first aspect or any of its implementation manners, in some other possible implementation manners, sending the first request message to the production entity includes: when the difference between the achieved value of the target of the network management intention and the expected value of the target of the network management intention is greater than a first threshold, sending the first request message to the production entity; or, sending the second request message to the production entity includes: when the difference between the achieved value of the target of the network management intention and the expected value of the target of the network management intention is less than or equal to the first threshold, sending the second request message to the production entity.

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

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

[0026] The method includes: monitoring the achieved value of the target of the network management intention; sending an intention report to a consumer entity, where the intention report is used to indicate that the stable achieved value of the target of the network management intention fails to reach the target of the network management intention.

[0027] Combined with the second aspect, in some possible implementation manners, the method further includes: receiving request information from the consumer entity, where the request information is used to request the intention report.

[0028] Combined with the second aspect or any of its implementation manners, in some other possible implementation manners, receiving the request information from the consumer entity includes: receiving a subscription request message from the consumer entity, where the subscription request message includes the request information.

[0029] Combined with the second aspect or any of its implementation manners, in some other possible implementation manners, the request information includes the network management intention or an identifier of the network management intention.

[0030] Combined with the second aspect or any of its implementation manners, in some other possible implementation manners, the request information includes indication information, where the indication information is used to indicate that an intention report is to be sent when the stable achieved value of the target of the network management intention fails to reach the target of the network management intention.

[0031] Combined with the second aspect or any of its implementation manners, in some other possible implementation manners, the method further includes: determining that the implementation value of the target of the network management intention is stable.

[0032] Combined with the second aspect or any of its implementation manners, in some other possible implementation manners, determining that the implementation value of the target of the network management intention is stable includes: determining that all action groups for the network management intention have become effective, where the action group includes one or more actions for managing the managed entities of the network management intention; or determining that the performance metric values of the managed entities of the network management intention continuously fall within a first range within a first observation duration.

[0033] Combined with the second aspect or any of its implementation manners, in some other possible implementation manners, the method further includes: receiving first information from the consuming entity, where the first information is used to indicate the first observation duration and / or the first range; where the first observation duration is the observation duration required to determine that the implementation value of the target of the network management intention is stable, and the first range is the fluctuation range that the implementation value of the target of the network management intention needs to satisfy to be stable.

[0034] Combined with the second aspect or any of its implementation manners, in some other possible implementation manners, receiving the first information from the consuming entity includes: receiving a creation message from the consuming entity, where the creation message is used to request the creation of the network management intention. Where the creation message includes the network management intention, the network management intention includes the first information, or the creation message includes the network management intention and the first information.

[0035] Combined with the second aspect or any of its implementation manners, in some other possible implementation manners, the method further includes: receiving a first request message from the consuming entity, where the first request message is used to request the producing entity to delete the network management intention; deleting the network management intention according to the first request message; or receiving a second request message from the consuming entity, where the second request message is used to request the producing entity to modify the network management intention; modifying the network management intention according to the first request message; where modifying the network management intention includes one or more of the following operations: reducing the expected value of the unfulfilled target of the network management intention, replacing the action group for the network management intention, or increasing the priority of the network management intention.

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

[0037] The method includes: the production entity monitors the achieved value of the target of the network management intent; the production entity sends an intent report, and the consumption entity receives the intent report, where the intent report is used to indicate that the stable achieved value of the target of the network management intent fails to reach the target of the network management intent; the consumption entity manages the network management intent according to the intent report.

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

[0039] In a fourth aspect, a communication device is provided. The device is used to execute the method provided by any of the above aspects or its implementation manner. Specifically, the device may include units and / or modules for executing the method provided by any of the above aspects or its implementation manner, 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 by any of the above aspects or its implementation manner, such as managing network management intent. The transceiver unit is used to execute the transceiver steps in the method provided by any of the above aspects or its implementation manner, such as receiving or sending an intent report, a first piece of information, or a subscription message, etc.

[0040] In one implementation manner, the device is a production entity or a consumption entity. When the device is a production entity or a consumption entity, the transceiver unit can be a transceiver, or an input / output interface, or a communication interface; the processing unit can be at least one processor. Optionally, the transceiver is a transceiver circuit. Optionally, the input / output interface is an input / output circuit.

[0041] In another implementation manner, the device is a chip, a chip system, or a circuit for a production entity or a consumption entity. When the device is a chip, a chip system, or a circuit for a production entity or a consumption entity, the transceiver unit can 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 can be at least one processor, a processing circuit, or a logic circuit, etc.

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

[0043] In one implementation manner, the device is a production entity or a consumption entity.

[0044] In another implementation manner, the device is a chip, a chip system or a circuit used in a production entity or a consumption entity.

[0045] In a sixth aspect, a communication device is provided, which includes: at least one processor and a communication interface. The at least one processor is configured to obtain the computer programs or instructions stored in a memory through the communication interface to perform the method provided in any of the above aspects or its implementation manners. The communication interface can be implemented by hardware or software.

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

[0047] In a seventh aspect, a processor is provided for performing the methods provided in the above aspects.

[0048] 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 operations such as outputting, receiving, and inputting by the processor, and can also be understood as sending and receiving operations performed by the radio frequency circuit and the antenna. This application does not make any limitations in this regard.

[0049] In an eighth aspect, a computer-readable storage medium is provided, which stores program codes for a device to execute. The program codes include those for performing the method provided in any of the above aspects or its implementation manners.

[0050] In a ninth aspect, a computer program product including instructions is provided. When the computer program product runs on a computer, it causes the computer to perform the method provided in any of the above aspects or its implementation manners.

[0051] In a tenth aspect, a chip is provided. The chip includes a processor and a communication interface. The processor reads the instructions stored on a memory through the communication interface to perform the method provided in any of the above aspects or its implementation manners. The communication interface can be implemented by hardware or software.

[0052] Optionally, as an implementation, the chip further includes a memory, in which computer programs or instructions are stored, and 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 method provided by any of the above aspects or its implementation manners.

[0053] Wherein, when the method provided by this application is executed by a chip, this application does not limit the number of chips for implementing the method of this application. For example, it can be executed by one chip, or 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.

[0054] In an eleventh aspect, a communication system is provided, including at least one of the above-mentioned production entity or consumption entity.

[0055] In a twelfth aspect, a computer program is provided, which, when running on a computer, causes the method provided by any of the above aspects or its implementation manners to be executed. Description of the Drawings

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

[0057] Figure 2 It is a schematic structural diagram of a communication system applicable to an embodiment of this application.

[0058] Figure 3 It is an example of the influence of the intervention of the consumption entity on the realization of intention.

[0059] Figure 4 It is a schematic flowchart of the network management intention management method 400 provided by the embodiment of this application.

[0060] Figure 5 It is a schematic flowchart of the network management intention management method 500 provided by the embodiment of this application.

[0061] Figure 6 It is a schematic flowchart of the network management intention management method 600 provided by the embodiment of this application.

[0062] Figure 7 It is a schematic flowchart of the network management intention management method 700 provided by the embodiment of this application.

[0063] Figure 8 It is a schematic flowchart of the network management intention management method 800 provided by the embodiment of this application.

[0064] Figure 9 It is a schematic flowchart of a network management intention management method 900 provided by an embodiment of the present application.

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

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

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

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

[0069] "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 designations such as first, second, etc. are only for convenience of description and are not used to limit the scope of the embodiments of the present application. For example, they are used to distinguish different messages, different information, etc. "Pre-defined" can be implemented by pre-saving corresponding codes, tables or other means that can be used to indicate relevant information in the device. The present application does not limit its specific implementation manner. 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. The present 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 the present 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. "At least one" means one or more, and "a plurality" 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, and do not limit 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, which does not limit time, and does not require the device to have a judgment action when implementing, nor does it mean there are other limitations.

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

[0071] The technical solutions of the present application can be applied to various network function virtualization (NFV) systems. Such systems can describe the current service technical 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 the present 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.

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

[0073] 1. Network management, network management service, network management service production entity, and network management service consumption entity

[0074] 1.1 Network management

[0075] 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 to monitor, test, configure, analyze, evaluate, and control network resources, etc. Network management can also be to report and handle in a timely manner when a network failure occurs, 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 the present application do not make special limitations. For the convenience of narration, the embodiments of the present application are described by taking the managed entity as an example, but can be replaced by other objects of network management.

[0076] 1.2 Network management service

[0077] A 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).

[0078] 1.3 Network management service production entity

[0079] The entity that provides a network management service is called a network management service production entity. Exemplarily, the capabilities or functions of a network management service production entity can be deployed on a certain network element, and this network element is called a network management service production network element; the capabilities or functions of a network management service production entity can also be deployed on other devices, and in this regard, the embodiments of this application do not make any limitations; for the convenience of description, the embodiments of this application use 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.

[0080] 1.4 Network management service consumption entity

[0081] The entity that invokes network management is called a network management service consumption entity. Exemplarily, the capabilities or functions of a network management service consumption entity can be deployed on a certain network element, and this network element is called a network management service consumption network element; the capabilities or functions of a network management service consumption entity can also be deployed on other devices, and in this regard, the embodiments of this application do not make any limitations; for the convenience of description, the embodiments of this application use the network management service consumption 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 consumption entity are deployed.

[0082] 2. Network management intention (abbreviation: intention)

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

[0084] In the intended interaction scenario of this application, there are mainly two roles, namely the entity providing network management and the entity consuming network management services. Among them, the entity providing network management can also be called the network management provider, or the intent provider, or the intent handler, etc. The entity consuming network management services can also be called the network management service consumer, or the intent consumer, or the intent owner, etc.

[0085] Among them, the entity consuming network management services can be the invoker of network management services, and can perform operations such as creating, modifying, deleting, and querying network management intent expressions. It can be configured in a network management system (NMS), or an element management system (EMS), or a network equipment (NE), and 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 restrictions on this.

[0086] Intents can be applied to a network system to achieve the expected goals for the specified performance indicators of network equipment within a specific range. Intents can express the expectations 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 the requirements, goals, and constraints of the intent.

[0087] 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 an expected object. Each expectation target may represent the performance requirements of a network management service consuming entity for a specific attribute of the expected 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 latency is less than 10 milliseconds. If the average downlink throughput rate of the expected object is greater than 5 Mbps, then the expectation target regarding the downlink throughput rate is met. If the end-to-end latency of the expected object is less than 10 milliseconds, then the expectation target regarding the latency is met. If both expectation targets of the intent expectation are met, then the intent expectation is met. If one or more intent expectations are not met, or one or more expectation targets are not met, then the intent is not met. In the embodiments of this application, whether an intent, an intent expectation, or an expectation target is met or not may also be described as: whether an intent, an intent expectation, or an expectation target is achieved or not, whether an intent, an intent expectation, or an expectation target is realized or not, or whether an intent, an intent expectation, or an expectation target has been achieved or not, etc. The following will use the method of "whether an intent, an intent expectation, or an expectation target has been achieved or not" for description.

[0088] 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 duration of the action of the intent through the intent context.

[0089] 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 duration of the action of the intent expectation through the expectation context.

[0090] 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 duration of the action of the expectation target through the target context.

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

[0092] The intention expectations, expected goals, and intention contexts introduced above can be used as cells in the IOC of the intention creation request. The network management service consuming entity can send the above cells to the network management service producing entity to express its demand for the network management service.

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

[0094] Exemplarily, Figure 1 A schematic structural diagram of an intention IOC is shown.

[0095] See Figure 1 , the intention IOC includes intention expectations and intention contexts. Intention expectations include expected objects, expected goals, and expected contexts. Expected objects include expected object contexts, and expected goals include goal contexts. It can be understood that non-context type cells (such as intention IOC, intention expectations, expected objects, or expected goals) can include context type cells (such as intention contexts, expected object contexts, goal contexts, expected contexts, etc.), and context type cells can be used to constrain non-context type cells.

[0096] It can be understood that Figure 1 This is a schematic illustration of the relationship of the attributes in the intention IOC. Based on the network management service demand, the intention IOC can also include other attributes, 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 expected goal attributes.

[0097] 3. Network Management Intention Template

[0098] 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 to be expressed. The intent expectation description information can specify the types of expected target attributes that the intent expectation can include, such as latency, 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 latency 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 to be 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.

[0099] 4. Intent Expression

[0100] In the embodiments of this application, an intent expression is an 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, an 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]).

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

[0102] For example, an instance of performance metric information can include the value or value range of the target metric requirement corresponding to the performance metric information. For example, the target metric requirement corresponding to the performance metric information template includes 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 requirement corresponding to the performance metric information template includes a latency parameter, and the instance of the latency parameter includes that the value of the latency parameter is 2s, or the value range of the latency parameter is from 1s to 5s.

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

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

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

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

[0107] 5. Network management intent instance

[0108] 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).

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

[0110] Among them, network management intent translation is used to convert the network management intent expression into a corresponding management action group, and the management action group may 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.

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

[0112] 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. By executing one or more network management actions, the network management service production entity can 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.

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

[0114] 7. Intent Report

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

[0116] The intent report IOC can include one or more of an intent fulfilment report, an intent conflict report, or an intent feasibility check report.

[0117] 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 includes only the achievement information of the intent, or the intent achievement report includes only 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, an 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 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 occurs, 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.

[0118] 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).

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

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

[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 intent report expression. For example, an 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, an intent report template can include one or more of the intent achievement description information for specifying how an intent achievement report is expressed, the intent conflict description information for specifying how an intent conflict report is expressed, and the intent feasibility check description information for specifying how an 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 achievement information attributes 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 achieved value of the throughput is an integer. The intent conflict description information is used to indicate how an 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 conflicts include intent conflict, expectation conflict, and target conflict. The intent feasibility check description information is used to indicate how an intent feasibility check report is represented.

[0123] 9. Intent Report Expression

[0124] An intent report expression is an information form for expressing the intent report of a network management service, and can be the instantiation result of an intent report template. The intent report expression contains the requirements of the network management service consumption entity for monitoring intents and the report information reflecting the current intent achievement status. The network management service production entity can instantiate the intent report IOC according to the intent report template to generate an intent report expression. Exemplarily, the intent report expression includes the achievement information of the current intent and the implementation value of the expected target. For example, if the expected target of the intent is throughput > 10 Mbps, according to the achievement status of the current intent, the network management service production entity will report the intent achievement information as: achieved, and the implementation 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 locally created 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 a 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 with Figure 2 to describe the application scenarios applicable to the embodiments of the present application.

[0128] Figure 2 is a schematic structural diagram of a communication system applicable to the embodiments of the present application. First, the devices that may be involved in the communication system are described.

[0129] 1. Network management service consumption entity 210: It can be used to call the management service, or call the intent service to manage the network system. Exemplarily, the network management service consumption entity 210 can instantiate the intent template, set the intent IOC, generate an intent expression, and send the intent expression to the network management service production network element 220 to achieve the expectation for the network system.

[0130] The network management service consumption entity 210 can also be referred to as a network management service consumption network element, a network management service consumer, an intent management service consumer, an intent service consumer, an intent consumer, or an intent owner, etc. In future communication systems, the network management service consumption entity may also have other names, and the present application does not make special limitations on this.

[0131] 2. Network Management Service Production Entity 220: It can be used to provide management services. Exemplarily, the network management service production entity 220 can receive an intent expression 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 expression.

[0132] 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 particularly limited in this application.

[0133] The above 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 (e.g., a cloud platform). It can be understood that the above entity can be implemented by one device, or jointly implemented by multiple devices. Additionally, the above 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.

[0134] 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 in 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.

[0135] 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 in 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.

[0136] Optionally, the above communication system may further include other devices or network elements, such as a knowledge base or a digital twin system, etc.

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

[0138] For the sake of simplicity in description below, the network management intention is simply referred to as intention, the network management service consumption entity is simply referred to as consumption entity, the network management service production entity is simply referred to as production entity, and the expected target is simply referred to as target.

[0139] Currently, the consumption entity can send messages to the production entity to implement management operations during the intention life cycle, such as creation, deletion, modification, or query of intentions. When the consumption entity receives an intention report from the production entity indicating that the intention has not been achieved, the consumption entity can intervene in the execution of the intention according to the achieved value of the target in the intention report. For example, the following operations can be performed:

[0140] 1. When the achieved value of the target of the intention is close to the expected value of the target, request the production entity to modify the intention, such as reducing the target of the intention or modifying the priority of the intention, etc.;

[0141] 2. When the achieved value of the target of the intention is far from the expected value of the target, request the production entity to delete the intention.

[0142] Among them, the expected value of the target, that is, the target value, is the value that the consumption entity expects the performance indicators related to the target to reach.

[0143] For example, the target of the intention is to ensure that the average downlink throughput rate > 25 Mbps, and the reporting period of the intention report is 15 minutes (min). During the execution of this intention, an intention conflict is encountered. At the end of the reporting period, the consumption entity receives the intention report. The achievement information of the intention in the intention report is not achieved, and the specific achieved value of the target of the intention is 23 Mbps. Because the achieved value of the target of the intention is close to the expected value of the target of the intention, the consumption entity can request to modify the priority of the intention.

[0144] However, the intervention of the consumption entity may cause the intention that could have been achieved to ultimately not be achieved, resulting in waste of resources. The reasons are as follows:

[0145] 1. The consumption entity has a low tolerance for the intention not being achieved. After receiving the intention report indicating that the intention has not been achieved, it is easy to intervene in the execution of the intention prematurely, resulting in the deletion or modification of the intention that could have been achieved;

[0146] 2. The achieved value of the target of the intention is changing, and the achieved value of the target in the intention report does not necessarily reflect the true situation of the intention. The operations taken by the consumption entity based on the achieved value of the target may cause the intention that could have been achieved to be deleted or modified.

[0147] Figure 3It is an example of the influence of the intervention of a consuming entity on the realization of an intention.

[0148] In Figure 3 In the example shown, the goal of the intention is to ensure an average downlink throughput rate > 25 Mbps, and the reporting period of the intention report is 15 minutes. During the execution of this intention, an intention conflict is encountered. At 15 minutes, the production entity reports the intention report for the first time. The result reported in the intention report is that the intention is not achieved, and the realized value of the intention goal is 18 Mbps, which has a large difference from the expected value of the goal. At 30 minutes, the production entity reports the intention report for the second time. The result reported in the intention report is that the intention is not achieved, and the realized value of the intention goal is 22 Mbps, which is close to the expected value of the goal.

[0149] If the consuming entity intervenes when it receives the intention report for the first time and the realized value of the goal has a large difference from the expected value of the goal, the consuming entity may choose to delete the intention. If the consuming entity intervenes when it receives the intention report for the second time and the realized value of the goal is close to the expected value of the goal, the consuming entity may choose to modify the intention, such as modifying the expected value of the intention goal.

[0150] In Figure 3 Case 1 and Case 2 of the intention realization are shown, and Case 1 and Case 2 start to be different after 23 minutes.

[0151] Case 1 is shown by the solid line part after 23 minutes and represents the realization of the intention without the intervention of the consuming entity. It can be seen that if the consuming entity does not intervene, the intention can be realized under natural execution. In this way, whether the consuming entity intervenes after receiving the report for the first time or after receiving the intention report for the second time, it will cause the intention that could have been realized to not be realized, resulting in a waste of resources.

[0152] Case 2 is shown by the dotted line part after 23 minutes and indicates that the intention cannot be achieved under natural execution. However, according to the realized value of the dotted line part, by modifying the expected value of the intention goal, the intention can be achieved. But if the consuming entity intervenes when it receives the intention report for the first time and the consuming entity chooses to delete the intention, then it will cause the intention that could have been realized after the intervention of the consuming entity to not be achieved, resulting in a waste of resources.

[0153] Combining the above Case 1 and Case 2, it can be seen that the current intention management mechanism may lead to the ultimate non - realization of an intention that could have been realized due to misjudgment, resulting in a waste of resources. For the consuming entity, how to choose the appropriate timing to intervene or manage the execution of the intention is a technical problem that needs to be solved.

[0154] In view of the above problems, the present application provides a method, a management method and a system for managing network management intentions, in order to reduce the probability of misjudgment by consumer entities, enable consumer entities to select appropriate timing to intervene or manage the execution of intentions, and thus reduce resource waste.

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

[0156] Figure 4 It is a schematic flowchart of a management method 400 for network management intentions provided by the present application.

[0157] Figure 4 The method shown can be executed by a production entity and a consumer entity. Without special instructions, the "production entity" or "consumer entity" can refer to the production entity or consumer entity itself, or can refer to a device capable of supporting the production entity or consumer entity to achieve its functions. For the sake of convenient description, the production entity and the consumer entity are used for description below. The method 400 includes at least part of the following content.

[0158] Step 401, the production entity monitors the achieved value of the target of the intention.

[0159] The intention can be various types of intentions. The type of intention can be related to the target included in the 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 a 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 an energy saving intention.

[0160] The achieved value of the target of the intention, which can also be called the achieved value or the current value, etc., is corresponding to the intention report. The achieved value of the target carried in a certain intention report is the already achieved value of the target when generating this intention report. The achieved value of the target of the intention is related to the performance index value of the entity to be managed of the intention. One relationship between the achieved value of the target of the intention and the performance index value of the entity to be managed of the intention can be: the production entity can continuously collect the performance index values related to the target at the entity to be managed, but only the performance index value at the time of about to send the intention report is the achieved value of the target, and the intention report carries this performance index value (that is, the achieved value of the target). Another relationship between the achieved value of the target of the intention and the performance index value of the entity to be managed of the intention can be: the achieved value of the target is obtained by observing and calculating the performance index values related to this target of the entity to be managed over a period of time.

[0161] The achieved value of the target of the production entity monitoring intent can also be described as: the achieved value of the target of the production entity monitoring, evaluation, or detection intent, etc. The achieved value of the target of the production entity monitoring intent can be understood as: the production entity continuously collects or samples the performance index values related to the target at the managed entity of the intent, and obtains the achieved value of the target based on the collected or sampled performance index values.

[0162] Step 402, the production entity sends an intent report to the consumption entity. Correspondingly, the consumption entity receives the intent report from the production entity.

[0163] Among them, the intent report is used to indicate that the stable achieved value of the target of the intent fails to achieve the target of the intent.

[0164] The stable achieved value of the target of the intent can mean that the achieved value of the target of the intent is stable. If the performance index values related to the target of the intent continuously fall within the preset range within the preset time, then the achieved value of the target of the intent is stable; otherwise, the achieved value of the target of the intent is not stable. The stable achieved value of the target of the intent can be considered reliable, trustworthy, or available.

[0165] The stable achieved value of the target of the intent can include: the achieved value of the target when all action groups for the intent have taken effect, and / or the achieved value of the target when the performance index values of the managed entity of the intent continuously fall within the first range within the first observation duration. Among them, the description of the action group can refer to the term explanation part. The first observation duration is the observation duration required to determine that the achieved value of the target of the intent is stable, and the first range is the fluctuation range required for the achieved value of the target of the intent to be stable, or the fluctuation range required to determine that the achieved value of the target of the intent is stable. That all action groups for the intent have taken effect can also be replaced with: the last action group for the intent has taken effect.

[0166] The production entity can also determine whether the achieved value of the target of the intent is stable. The embodiments of the present application do not limit the specific implementation manner.

[0167] In a possible implementation, the production entity can determine whether all action groups for an intent have taken effect. When all action groups for the intent have taken effect, the realization value of the intent's target is stable; otherwise, the realization value of the intent's target is unstable. That is to say, the production entity can judge whether the realization value of the intent's target is stable based on whether all action groups for the intent have been executed and have taken effect. For example, to ensure the smooth progress of an important video conference, it is necessary to ensure high-definition and smoothness of the video conference. The target 1 of the performance guarantee intent is to ensure that the throughput rate is greater than 25 Mbps. There are 2 action groups for this performance guarantee intent. Before the 2 action groups are executed and take effect, the relevant performance index values of target 1 are constantly changing. Therefore, the realization value of target 1 is in an unstable state. After the 2 action groups are executed, since no new action groups will be executed, the relevant performance index values of target 1 gradually tend to be stable. After a period of time (i.e., after the action groups take effect), the relevant performance index values of target 1 reach stability, that is, the realization value of target 1 is stable.

[0168] There are many ways to judge whether the action groups of an intent have taken effect. Exemplarily, the production entity can judge whether the action groups of an intent have taken effect by judging whether the performance index values of the managed entity of the intent are continuously within the first range within the first observation duration. For example, if the relevant performance index values of the intent are continuously within the first range within the first observation duration, the production entity judges that the action groups of the intent have taken effect; otherwise, the production entity judges that the action groups of the intent have not taken effect.

[0169] In another possible implementation, the production entity can determine whether the performance index values of the managed entity of the intent are continuously within the first range within the first observation duration. When the performance index values of the managed entity of the intent are continuously within the first range within the first observation duration, the realization value of the intent's target is stable; otherwise, the realization value of the intent's target is unstable. For example, to ensure the smooth progress of an important video conference, it is necessary to ensure high-definition and smoothness of the video conference. The target 1 of the performance guarantee intent is to ensure that the throughput rate is greater than 25 Mbps. The first observation duration is 3 minutes, and the first range is 10%. If the fluctuation of the performance index related to target 1 is within 10% within the first observation duration, then the realization value of target 1 is stable. Another example, the energy-saving intent includes target 2, and target 2 is to ensure that the energy consumption is less than 1000 kw. The first observation duration is 10 minutes, and the first range is 5%. If the fluctuation of the performance index values related to target 2 is within 5% within the first observation duration, then the realization value of target 2 is stable.

[0170] It should be noted that when an intention includes multiple targets, each target can correspond to a first observation duration and a first range. The first observation durations and / or first ranges corresponding to different targets can be the same or different. For example, the performance guarantee intention includes Target 1 and Target 2. Target 1 is to guarantee that the throughput rate is greater than 25 Mbps, and Target 2 is to guarantee that the latency is less than 10 ms. The first observation duration corresponding to Target 1 is 3 min and the first range is 10%, and the first observation duration corresponding to Target 2 is 5 min and the first range is 8%. Another example, the performance guarantee intention includes Target 1 and Target 2. Target 1 is to guarantee that the throughput rate is greater than 25 Mbps, and Target 2 is to guarantee that the latency is less than 10 ms. The first observation durations corresponding to Target 1 and Target 2 are 3 min and the first range is 10%.

[0171] The above first observation duration and / or first range can be defined by the consuming entity or determined by the producer based on historical experience, without limitation.

[0172] The above method of defining "the realization value of the intention target is stable" is only an example, and there can be other definition methods. As long as the meaning of "the realization value of the intention target is stable" is that the realization value of the intention target will not change significantly within a period of time, and this realization value is reliable, credible or available.

[0173] If the realization value of the intention target is stable, it means the intention is stable; if the realization value of the intention target is unstable, it means the intention is unstable. Therefore, "the realization value of the intention target is stable" can also be described as "the intention is stable".

[0174] For the case where the first observation duration and / or first range can be defined by the consuming entity, method 400 may further include step 403, and step 403 is as follows.

[0175] Optionally, in step 403, the consuming entity sends first information to the producing entity. Correspondingly, the producing entity receives the first information from the consuming entity. The first information is used to indicate the first observation duration and / or the first range. It should be noted that the first information can also indicate other information for determining whether the realization value of the intention target is stable, without limitation.

[0176] The embodiments of the present application do not limit the way for the consuming entity to send the first information to the producing entity.

[0177] One possible implementation, the consuming entity can send the first information to the producing entity as a separate information.

[0178] Another possible implementation, the consuming entity can send a first message to the producing entity, and the first message includes the first information.

[0179] Embodiments of the present application do not limit the message type of the first message, and the first message can be any message related to intent management.

[0180] Exemplarily, the first message can be used to create or request to create an intent. For example, the first message is an intent creation request message. When the first message is used to create or request to create an intent, there are many ways for the first message to carry the first information, which are not limited. In one possible implementation, the first message can include an intent and the first information, where the intent can be represented as an instantiated intent IOC (as Figure 1 shown). In another possible implementation, the first message can include an intent, and the intent includes the first information, where the intent can be represented as an instantiated intent IOC (as Figure 1 shown). For example, the intent IOC corresponding to the intent includes an intent expectation and an intent context, and the intent context includes the first information. 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 the first information. 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 the first information. For the case where the first message is used to create or request to create an intent, after receiving the first message, the production entity can create an intent according to the first message, and subsequently, the production entity can determine whether the implementation value of the target of the intent is stable according to the first information.

[0181] Exemplarily, the first message can be used to modify or request to modify an intent. For example, the first message is an intent modification request message. When the first message is used to modify or request to modify an intent, there are many ways for the first message to carry the first information, which are not limited. In one possible implementation, the first message can include an identifier of the intent and the first information. In another possible implementation, the first message can include an identifier of the intent expectation of the intent and the first information. In another possible implementation, the first message can include an identifier of the expectation target of the intent and the first information. In another possible implementation, if the first message implements the modification function by carrying a modified intent IOC, then the first information can also be included in the intent IOC of the intent. For the case where the first message is used to modify or request to modify an intent, the production entity can modify the already created intent according to the first message, and subsequently, the production entity can determine whether the implementation value of the target of the modified intent is stable according to the first information.

[0182] Exemplarily, the first message can be a subscription request message. The subscription request message can be sent along with the intent creation request message or the intent modification request message, that is, the subscription request message is included in the intent creation request message or the intent modification request message. The subscription request message can also be sent separately after the intent creation request message or the intent modification request message.

[0183] Exemplarily, the first message may be a query request message.

[0184] There are many ways in which the intent report indicates that the stable implementation value of the target of the intent fails to achieve the target of the intent. It can be directly indicated by carrying the corresponding cell, or indirectly indicated.

[0185] For the direct indication method, exemplarily, the intent report may include the achievement information of the target of the intent, the implementation value of the target of the intent, and the stability information of the implementation value of the target of the intent. Among them, the achievement information of the target of the intent is used to indicate that the target of the intent is not achieved, and the stability information of the implementation value of the target of the intent is used to indicate whether the implementation value of the target of the intent is stable. That is to say, compared with the existing intent report, the intent report of the embodiments of the present application can additionally carry the stability information of the implementation value of the target of the intent. In method 400, the stability information of the implementation value of the target of the intent is used to indicate that the implementation value of the target of the intent is stable. The implementation manner of the intent report additionally carrying the stability information of the implementation value of the target of the intent will be described in detail below in conjunction with Figure 5 is described in detail.

[0186] For the indirect indication method, exemplarily, when the production entity sends an intent report only when the stable implementation value of the target of the intent fails to achieve the target of the intent, the intent report may include the achievement information of the target of the intent and the implementation value of the target of the intent. The intent report itself may indicate that the implementation value of the target of the intent is stable, or rather, sending or receiving the intent report means that the implementation value of the target of the intent is stable.

[0187] There are many ways to trigger the production entity to send an intent report.

[0188] One possible implementation is that the production entity can periodically send an intent report to the consumption entity, that is, the arrival of the reporting period will trigger the production entity to send an intent report. Among them, the reporting period for the production entity to report the intent report can be pre-configured or predefined, or can be judged by the producer based on historical experience, or can be provided by the consumption entity, without limitation. For the case where the consumption entity provides the reporting period to the production entity, one possible implementation is that the consumption entity sends a subscription message to the production entity, and the subscription message includes period information, and the period information is used to indicate the period for reporting the intent report.

[0189] Another possible implementation is that the production entity can send an intent report based on the request of the consumption entity. Compared with periodically reporting the intent report, this method helps to reduce the signaling overhead caused by reporting the intent report. In this case, method 400 may further include step 404, and step 404 is as follows.

[0190] Optionally, in step 404, the consuming entity sends request information to the producing entity. Correspondingly, the producing entity receives the request information from the consuming entity.

[0191] Among them, the request information is used to request the producing entity to send an intent report. Exemplarily, the request information may include an intent or an identifier of the intent. Among them, the identifier of the intent is information that can uniquely determine the intent, such as the name or number of the intent (identifier (ID) or distinguished name (DN)), etc.

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

[0193] In a possible implementation, the consuming entity may send the request information to the producing entity as a separate piece of information.

[0194] In another possible implementation, the consuming entity may send a second message to the producing entity, and the second message includes the request information. The embodiments of the present application do not limit the message type of the second message. The second message may be any message related to intent management. For example, the second message may be a message for creating or requesting to create an intent (such as an intent creation request message), a message for modifying or requesting to modify an intent (such as an intent modification request message), a subscription request message, or a query request message, etc. For specific descriptions, reference may be made to the first message.

[0195] Optionally, the request information may further include indication information, and the indication information is used to indicate that an intent report is to be sent when the stable implementation value of the target of the intent fails to achieve the target of the intent. In other words, the consuming entity may require the producing entity to send an intent report to it when the stable implementation value of the target of the intent fails to achieve the target of the intent. When the stable implementation value of the target of the intent achieves the target of the intent, and / or when the implementation value of the target of the intent is not stable and fails to achieve the target of the intent, an intent report may not be sent to it. In this case, the producing entity may send an intent report to the consuming entity according to the received indication information. For the case where the request information includes indication information, the intent report itself may indicate that the implementation value of the target of the intent is stable. Or, sending or receiving an intent report means that the implementation value of the target of the intent is stable. Or, the stability of the implementation value of the target of the intent is indirectly indicated by the request information sent by the consuming entity to request the intent report. And if the intent report includes the implementation value of the target of the intent, then the implementation value is always stable.

[0196] In the embodiments of the present application, the consuming entity may obtain the intent report from the producing entity in a subscription-based manner.

[0197] The subscription can be an explicit subscription. Exemplarily, the consuming entity subscribes to the intent report through a separate subscription request message, and the subscription request message includes the above-mentioned indication information. Embodiments of the present application do not limit the manner in which the subscription request message carries the indication information. For example, the subscription request message can include a subscription IOC (such as NtfSubscriptionControl IOC), and the subscription IOC includes the above-mentioned indication information. Another example is that the subscription request message directly includes the indication information.

[0198] The subscription can also be an implicit subscription. Exemplarily, the indication information can be sent along with other messages related to intent management. For example, the indication information can be included in an intent creation request message or an intent modification request message. Taking the indication information included in the intent creation request message as an example, the intent creation request message can include an intent IOC and the indication information; or, the intent creation request message can include an intent, and the intent includes the indication information. For example, the indication information can be included in the intent context, the expected context, or the target context. Taking the indication information included in the intent modification request message as an example, the intent modification request message can include: the identifier of the intent and the indication information, the identifier of the intent expectation of the intent and the indication information, or the identifier of the expected target of the intent and the indication information; or, the intent modification request message can include the modified intent, and the modified intent includes the indication information.

[0199] It should be noted that the request information and the first information can be sent through the same message or through different messages. When the request information and the first information are sent through the same message, the first message and the second message are the same message, and step 403 and step 404 are the same step.

[0200] Step 405, the consuming entity manages the intent according to the received intent report.

[0201] A possible implementation manner is that the producing entity can modify or delete the intent according to the received intent report.

[0202] Exemplarily, the producing entity can send a first request message to the producing entity according to the received intent report, and the first request message is used to request the producing entity to delete the intent.

[0203] Exemplarily, the producing entity can send a second request message to the producing entity according to the received intent report, and the second request message is used to request the producing entity to modify the intent.

[0204] A possible implementation, the intent report is used to indicate that the target of the intent has not been achieved and the stable implementation value of the target of the intent. The production entity can determine whether to modify the intent or delete the intent according to the stable implementation value of the target of the intent and the expected value of the target. Among them, the expected value of the target, that is, the target value, is the value that the consumer entity expects the performance indicators related to the target to reach. For example, the performance guarantee type intent includes target 1, and target 1 is to ensure that the throughput rate is greater than 25 Mbps. The expected value of the throughput rate related to target 1 is 25 Mbps. At 30 minutes, the throughput rate of target 1 is 24.8 Mbps. Then, at 30 minutes, the implementation value of target 1 is 24.8 Mbps.

[0205] Exemplarily, when the difference between the stable implementation value of the target of the intent and the expected value of the target of the intent is greater than the first threshold, the consumer entity sends a first request message to the production entity.

[0206] For example, the target 1 of the performance guarantee type intent is to ensure that the throughput rate is greater than 25 Mbps. During the execution of this intent, this intent conflicts with other intents. The production entity immediately reports the occurrence of the conflict and tries to resolve the conflict by switching the action group. After trying all the action groups for this intent, the implementation value of target 1 is 5 Mbps. The target 1 of this intent has not been achieved and the implementation value of the target 1 of this intent has stabilized. The production entity can send an intent report to the consumer entity to report to the consumer entity that the target 1 of this intent has not been achieved and the implementation value of target 1 is 5 Mbps. Since the gap between 5 Mbps and the expected value of the target, 25 Mbps, is too large, the consumer entity believes that this intent cannot be realized. Therefore, this intent can be deleted.

[0207] Exemplarily, when the difference between the stable implementation value of the target of the intent and the expected value of the target of the intent is less than or equal to the first threshold, the consumer entity sends a second request message to the production entity.

[0208] Modifying the intent includes one or more of the following operations: reducing the expected value of the unachieved target of the intent, replacing the action group for the intent, or increasing the priority of the intent. Exemplarily, when the stable implementation value of the target of the intent is close to the expected value of the target, the consumer entity can request to reduce the expected value of the target of the intent. Exemplarily, when there is a certain gap between the stable implementation value of the target of the intent and the expected value of the target, the consumer entity can request to replace the action group for the intent or increase the priority of the intent.

[0209] For example, the intent report received by the production entity indicates that the target 1 of the intent has not been achieved and the implementation value of the target 1 of the intent is 24.8 Mbps. Since 24.8 Mbps is close to 25 Mbps, the consumer entity can accept this implementation value. Therefore, the consumer entity can reduce target 1 to 24.8 Mbps.

[0210] For another example, the intention report received by the production entity indicates that the target 1 of the intention is not achieved, and the achieved value of the target 1 of the intention is 22 Mbps. Since there is a certain gap between 22 Mbps and 25 Mbps, the consumption entity may request to replace the action group for this intention or increase the priority of this intention.

[0211] In method 400, the production entity may indicate to the consumption entity that the stable achieved value of the target of the intention fails to achieve the target of the intention. The intention report indicates the stable achieved value of the target of the intention. Compared with the prior art where the intention report simply indicates the achieved value of the target of the intention, the consumption entity can learn that the achieved value of the target of the intention is stable and reliable. Furthermore, based on this stable and reliable achieved value, the consumption entity can choose an appropriate time to intervene or manage the execution of the intention, which helps to reduce the probability of misjudgment and thus reduce resource waste.

[0212] The following combines Figure 5 to describe the implementation manner of the intention report additionally carrying the stable information of the achieved value of the target of the intention.

[0213] Figure 5 is a schematic flowchart of the management method 500 for network management intentions provided by this application.

[0214] Figure 5 The method shown can be executed by the production entity and the 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. For the convenience of description, the production entity and the consumption entity are used for description below. Method 500 includes at least part of the following content.

[0215] Step 501, the production entity monitors the achieved value of the target of the intention. Step 501 can refer to step 401.

[0216] Step 502, the production entity sends an intention report to the consumption entity. Correspondingly, the consumption entity receives the intention report from the production entity.

[0217] Among them, the intention report is used to indicate that the achieved value of the target of the intention fails to achieve the target of the intention, as well as stability information, and the stability information is used to indicate whether the achieved value of the target of the intention is stable. Exemplarily, the intention report may include achievement information, the achieved value of the target of the intention, and stability information. Among them, the achievement information is used to indicate whether the target of the intention is achieved, and the achievement information may include one or more of the achievement information of the intention, the expected achievement information of the intention, or the achievement information of the target of the intention. For example, the intention achievement report only includes the achievement information of the intention, or the intention achievement report only includes the achievement information of the target of the intention, or the intention achievement report includes the achievement information of the intention, the expected achievement information of the intention, and the achievement information of the target of the intention.

[0218] In an embodiment of the present application, the consuming entity may add a stability attribute to the intention report IOC. Specifically, the intention report template configured by the consuming entity for the producing entity may stipulate that the stability attribute is included in the intention report IOC. The stability attribute is used to describe whether the achieved value of the target of the intention is stable. In this way, when the producing entity determines the intention report based on the intention report IOC, in addition to indicating that the achieved value of the target of the intention fails to achieve the target of the intention, the intention report can also indicate whether the achieved value of the target of the intention is stable.

[0219] The embodiment of the present application does not limit the implementation manner for the producing entity to determine whether the achieved value of the target of the intention is stable. For a detailed description, reference can be made to step 402. It should be noted that when the consuming entity defines the first observation duration and / or the first range for the producing entity to determine whether the action group of the intention has taken effect or to determine whether the achieved value of the target of the intention is stable, method 500 may further include step 503, and step 503 is as follows.

[0220] Optionally, in step 503, the consuming entity sends the first information to the producing entity, and correspondingly, the producing entity receives the first information from the consuming entity. Among them, the first information is used to indicate the first observation duration and / or the first range. It should be noted that the first information may also indicate other information for determining whether the achieved value of the target of the intention is stable, without limitation. Step 503 may refer to step 403.

[0221] There are many ways to trigger the producing entity to send an intention report. For a detailed description, reference can be made to step 403. It should be noted that when the producing entity sends an intention report based on the request of the consuming entity, method 500 may further include step 504, and step 504 is as follows.

[0222] Optionally, in step 504, the consuming entity sends request information to the producing entity. Correspondingly, the producing entity receives the request information from the consuming entity. Step 504 can refer to step 404, except that the request information in step 504 does not include the indication information used to indicate that an intention report is to be sent when the stable realization value of the intended target fails to achieve the intended target. In this way, when the intention report is sent, the realization value of the intended target may or may not be stable, and this situation can be indicated to the consuming entity through the stability information in the intention report.

[0223] Step 505, the consuming entity manages the intention according to the received intention report.

[0224] A possible implementation manner is that the consuming entity manages the intention according to the received intention report, including: when the intention report indicates that the realization value of the intended target fails to achieve the intended target and the realization value of the intended target is stable, the consuming entity performs a first management on the intention, where the first management includes intervening in the execution of the intention; and / or when the intention report indicates that the realization value of the intended target fails to achieve the intended target and the realization value of the intended target is not stable, the consuming entity does not intervene in the execution of the intention. That is to say, when the realization value of the intended target is stable, that is, the realization value indicated by the intention report is stable and reliable, the consuming entity can intervene in the execution of the intention; when the realization value of the intended target is not stable, that is, the realization value indicated by the intention report is unreliable, in order to avoid misjudgment, the consuming entity will not intervene in the execution of the intention at this time.

[0225] When the intention report indicates that the realization value of the intended target fails to achieve the intended target and the realization value of the intended target is stable, the consuming entity intervenes in the execution of the intention. Specifically, reference can be made to the implementation manner in which the consuming entity manages the intention according to the received intention report in step 405, and details will not be elaborated.

[0226] In method 500, the producing entity can inform the consuming entity whether the realization value of the intended target is stable and reliable by indicating the stability information of the realization value of the intended target in the intention report, thereby assisting the consuming entity in making decisions, helping the consuming entity select an appropriate timing to intervene or manage the execution of the intention, and thus reducing the probability of misjudgment of the consuming entity and reducing resource waste.

[0227] In some other embodiments of the present application, in the case where the intention report indicates that the realization value of the intended target fails to achieve the intended target and the realization value of the intended target is not stable, the intention report can also be used to indicate the estimated duration for the realization value of the intended target to reach stability. In this case, method 500 can also include step 505, and step 505 is as follows.

[0228] Optionally, in step 505, the producing entity obtains the estimated duration for the realization value of the intended target to reach stability.

[0229] Embodiments of the present application do not limit the implementation manner for the production entity to achieve a stable estimated duration for the target of obtaining the intention.

[0230] In a possible implementation manner, the production entity may obtain the estimated duration from the first network element. The first network element may estimate the estimated duration for the value of the target that is not yet stable to reach stability based on at least one of the following information: the latest statistical data of network or service performance metrics, historical experience (such as the estimated time based on experience), the current state of network resource utilization and availability, or the prediction result based on a network simulation system. Exemplarily, the first network element is a knowledge base or a digital twin system, or a network element deployed with a knowledge base and / or a digital twin system.

[0231] Optionally, method 500 may further include: after the value of the target of the intention reaches stability, the production entity updates the duration for the value of the target to reach stability to the first network element for reference when estimating the estimated duration for the value of the target to reach stability in the future.

[0232] In the case where the intention report is also used to indicate the above-mentioned estimated duration, the consuming entity may refer to the estimated duration for the value of the target of the intention to reach stability when managing the intention, that is, the consuming entity may manage the intention according to the estimated duration for the value of the target of the intention to reach stability.

[0233] Embodiments of the present application relate to the implementation manner for the consuming entity to manage the intention according to the estimated duration for the value of the target of the intention to reach stability. In a possible implementation manner, when the estimated duration is less than or equal to the duration threshold, the consuming entity does not intervene in the execution of the intention; and / or, when the estimated duration is greater than the duration threshold, the consuming entity may perform a first management on the intention. The first management includes intervening in the execution of the intention. Specifically, reference may be made to the implementation manner in which the consuming entity manages the intention according to the received intention report in step 405, which will not be elaborated herein.

[0234] It should be noted that in the case where the intention report indicates the estimated duration for the value of the target of the intention to reach stability, the intention report may explicitly indicate whether the value of the target of the intention is stable through the stability information, or may indirectly indicate whether the value of the target of the intention is stable by indicating whether the estimated time is indicated. For example, if the intention report indicates the estimated time, it means that the value of the target of the intention is not stable, and if the intention report does not indicate the estimated time, it means that the value of the target of the intention is stable.

[0235] Based on the above-mentioned estimated time, it can assist the consuming entity to further determine whether to wait, which helps to reduce the probability of misjudgment of the consuming entity, thereby reducing resource waste.

[0236] Taking the example where the request information is carried in the subscription message and the subscription request message is sent separately after the intent creation request message, the solution in method 400 where the consuming entity requests the producing entity to send an intent report when the stable implementation value of the target of the intent fails to reach the target of the intent will be described in detail below.

[0237] Figure 6 It is a schematic flowchart of the network management intent management method 600 provided by this application. The solution of method 600 enables the consuming entity to obtain the information that the target of the intent has not been achieved and the implementation value of the target of the intent has been stabilized in the first place. The "intent service consumer" in method 600 can correspond to the consuming entity above, and the "intent service producer" can correspond to the producing entity above.

[0238] Step 601, the intent service consumer configures an intent report template for the intent service producer.

[0239] Optionally, the intent report template can stipulate that the intent report IOC includes a stability attribute.

[0240] The stability attribute is used to describe whether the intent is stable and can include two states:

[0241] 1) Not Stable: Before the intent service producer determines that the implementation value of the relevant target tends to be stable, the stability attribute remains "Not Stable". For example, it will remain "Not Stable" before the intent is not implemented and all action groups of the intent are not executed.

[0242] 2) Stable: When the intent service producer determines that the implementation value of the relevant target tends to be stable, the stability attribute becomes "Stable". For example, when the intent is not implemented, all action groups of the intent are not executed and take effect, the stability attribute becomes "Stable".

[0243] Whether the intent is not stable or the intent is stable can refer to the relevant description of whether the implementation value of the target of the intent is stable in step 401, which will not be elaborated here.

[0244] It should be noted that step 601 is executed during the first configuration.

[0245] Step 602, the intent service consumer requests the intent service producer to create an intent, and the intent service producer creates and executes the intent.

[0246] Specifically, an intent service consumer may send an intent creation request message to an intent service producer. The intent service producer may create an intent (i.e., an intent instance) based on the request of the intent service consumer, and send an intent creation response message to the intent service consumer after creating the intent. Subsequently, the intent service producer may perform a feasibility check on the intent, and start to execute the intent after the feasibility check passes. The execution of the intent by the intent service producer may refer to performing network management tasks, service management tasks, or a network management action group, such as deploying or configuring parameters. Taking the intent of performance guarantee as an example, to ensure the smooth progress of an important video conference, it is necessary to ensure the high-definition and smoothness of the video conference. The first goal of the intent of performance guarantee is to ensure that the throughput rate is greater than 25 Mbps, and the evaluation period of the intent implementation status is 15 minutes. The network management tasks, service management tasks, or network management action group of this performance guarantee intent may include changing the parameters of the base station, such as reducing the number of physical downlink control channel (PDCCH) symbols, etc.

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

[0248] Step 603, the intent service consumer sends a subscription request message to the intent service producer. Correspondingly, the intent service producer receives the subscription request message from the intent service consumer.

[0249] Among them, the subscription request message is used to subscribe to an intent report. The subscription request message includes indication information for instructing the production entity to send an intent report when the stable implementation value of the target of the intent fails to reach the target of the intent, that is, the intent service consumer subscribes to the intent service producer to send an intent report when the stable implementation value of the target of the intent fails to reach the target of the intent.

[0250] Step 604, the intent service producer evaluates the intent.

[0251] Specifically, the intent service producer continuously evaluates the achievement of the target of the intent and the stability of the implementation value of the target of the intent. The method for the intent service producer to evaluate the stability of the implementation value of the target of the intent may refer to the method for the intent service producer to determine whether the implementation value of the target of the intent is stable in step 402.

[0252] Step 605, if it is determined that the target of the intention has not been achieved and the achieved value of the target of the intention has stabilized, the intention service producer sends an intention report to the intention service consumer. Correspondingly, the intention service consumer receives the intention report from the intention service producer.

[0253] Among them, the intention report is used to indicate that the stable achieved value of the target of the intention fails to achieve the target of the intention.

[0254] Optionally, the intention report is also used to indicate the stable information of the achieved value of the target of the intention. At this time, the stable information is used to indicate that the achieved value of the target of the intention is stable. For example, when the intention report IOC includes a stability attribute, the intention report also includes the stable information of the achieved value of the target of the intention.

[0255] For example, to ensure the smooth progress of an important video conference, it is necessary to ensure high-definition and smoothness of the video conference. The target 1 of the performance guarantee type intention is to ensure that the throughput rate is greater than 25 Mbps. During the execution of this intention, this intention conflicts with other intentions. The intention service producer immediately reports the occurrence of the conflict and tries to resolve the conflict by switching the action group. After trying all the action groups for this intention, the achieved value of target 1 is 24.8 Mbps. The target 1 of this intention has not been achieved and the achieved value of target 1 is stable. The intention service producer can send an intention report to the intention service consumer to report to the intention service consumer that the target 1 of this intention has not been achieved, the achieved value of target 1 is 24.8 Mbps, and optionally the achieved value of target 1 is stable.

[0256] Step 606, the intention service consumer manages the intention according to the received intention report.

[0257] Step 606 can refer to Step 405 and will not be elaborated here.

[0258] In Method 600, the intention service consumer can request the intention service producer to send an intention report to it when the target of the intention has not been achieved and the achieved value of the target of the intention has stabilized. In this case, the achieved value of the target of the intention indicated by the intention report received by the intention service consumer is always stable and reliable. The intention service consumer manages the intention based on the stable and reliable achieved value, which helps to select an appropriate timing to intervene or manage the execution of the intention, thereby helping to reduce the probability of misjudgment and thus reducing resource waste.

[0259] Next, taking the production entity reporting the intention report periodically as an example, the solution in Methods 400 and 500 where the intention report additionally carries the stable information of the achieved value of the target of the intention will be described in detail.

[0260] Figure 7 It is a schematic flowchart of the management method 700 for network management intentions provided by this application. Figure 7In this, the "intended service consumer" can correspond to the consumption entity above, and the "intended service producer" can correspond to the production entity above. The relevant descriptions can refer to each other or be referenced.

[0261] Step 701: The intended service consumer configures an intention report template for the intended service producer.

[0262] Among them, the intention report template can stipulate that the intention report IOC includes a stability attribute. Step 701 can refer to Step 601.

[0263] Step 702: The intended service consumer requests the intended service producer to create an intention, and the intended service producer creates and executes the intention.

[0264] Step 702 can refer to Step 602. The difference is that the intention creation request message sent by the intended service producer can carry the period for reporting the intention report. Of course, the period for reporting the intention report can also not be carried in the intention creation request message, but provided to the intended service producer through other messages, such as a subscription request message.

[0265] Step 703: The intended service producer evaluates the intention. Step 703 can refer to Step 604, which will not be elaborated here.

[0266] According to the evaluation result of the intention by the intended service producer, the following two situations may occur subsequently.

[0267] Situation 1: The goal of the intention has been achieved, that is, the intention has been achieved.

[0268] In this case, Step 704 can be executed. Step 704 is as follows.

[0269] Step 704: If the intended service producer determines that all goals of the intention have been achieved, the intended service producer sends an intention report to the intended service consumer. Correspondingly, the intended service consumer receives the intention report from the intended service producer. Among them, the intention report is used to indicate that the realized value of the goal of the intention achieves the goal of the intention. Exemplarily, the intention report includes achievement information and the realized value of the goal of the intention, and the achievement information is used to indicate that the goal of the intention has been achieved or the intention has been achieved.

[0270] Situation 2: The goal of the intention has not been achieved, that is, the intention has not been achieved.

[0271] In this case, Step 705 and Step 706 can be executed. Step 705 and Step 706 are as follows.

[0272] Step 705, if the intent service producer determines that the goal of the intent is not achieved, the intent service producer sends an intent report to the intent service consumer. Correspondingly, the intent service consumer receives the intent report from the intent service producer.

[0273] Among them, the intent report is used not only to indicate that the achieved value of the goal of the intent does not meet the goal of the intent, but also to indicate the stability information of the achieved value of the goal of the intent. The stability information is used to indicate whether the achieved value of the goal of the intent is stable.

[0274] For example, to ensure the smooth progress of an important video conference, it is necessary to ensure high-definition and smoothness of the video conference. The goal 1 of the performance guarantee type intent is to ensure that the throughput rate is greater than 25 Mbps. The intent service producer periodically (such as every 15 minutes) reports an intent report to the intent service consumer. Before the execution of the action group for the intent is completed, the evaluation result of the intent is that the goal 1 of the intent is not achieved and the achieved value of the goal 1 of the intent is stable. The intent report reported by the intent service producer is used to indicate that the goal 1 of the intent is not achieved, the achieved value of the goal 1, and the achieved value of the goal 1 is not stable; when the reporting cycle arrives after the execution and effectiveness of the action group for the intent, the evaluation result of the intent is that the goal 1 of the intent is not achieved, the achieved value of the goal 1 is 24.8 Mbps, and the achieved value of the goal 1 is stable. The intent report reported by the intent service producer to the intent service consumer is used to indicate that the goal 1 of the intent is not achieved, the achieved value of the goal 1 is 24.8 Mbps, and the achieved value of the goal 1 is stable.

[0275] Step 706, the intent service consumer manages the intent according to the intent report.

[0276] Step 706 can refer to Step 505 and will not be elaborated here.

[0277] In Method 700, a stability attribute can be added to the intent report template to describe whether the achieved value of the goal of the intent is stable. When the goal of the intent is not achieved, the reported intent report can indicate the stability information of the achieved value of the goal of the intent, enabling the intent service consumer to know whether the achieved value indicated by the intent report is stable and reliable. Based on this, the consumer entity can make a decision, which helps the consumer entity choose an appropriate time to intervene or manage the execution of the intent, thereby helping to reduce the probability of misjudgment and also reducing resource waste while increasing the probability of intent achievement.

[0278] Next, taking the periodic reporting of intent reports by the production entity as an example, the solution in Method 500 where the intent report additionally carries the stability information of the achieved value of the goal of the intent and the estimated duration for the achieved value of the goal of the intent to reach stability will be described in detail.

[0279] Figure 8 It is a schematic flowchart of the network management intent management method 800 provided by the present application.Figure 8 The "predicted stable time" in Figure 8 can correspond to the "estimated time" in method 500, the "intended service consumer" can correspond to the consumption entity above, the "intended service producer" can correspond to the production entity above, and the relevant descriptions can refer to or reference each other. Figure 8 Take the case where the intended service producer obtains the estimated time from the knowledge base as an example.

[0280] Step 801, the intended service consumer configures an intent report template for the intended service producer.

[0281] Among them, the intent report template can stipulate that the intent report IOC includes a stability attribute and a predicted stable time (predictStableTime). The stability attribute is used to describe whether the achieved value of the intent's target is stable, and the description of the stability attribute can refer to step 601. The predicted stable time is used to describe the predicted time when the stability attribute of the achieved value of the intent's target becomes stable.

[0282] It should be noted that step 801 is executed during the first configuration.

[0283] Step 802, the intended service consumer requests the intended service producer to create an intent, and the intended service producer creates and executes the intent.

[0284] Step 802 can refer to step 602. The difference is that the intent creation request message sent by the intended service producer can carry the period for reporting the intent report. Of course, the period for reporting the intent report can also not be carried in the intent creation request message, but provided to the intended service producer through other messages, such as a subscription request message.

[0285] Step 803, the intended service producer evaluates the intent. Step 803 can refer to step 604.

[0286] According to the evaluation result of the intent by the intended service producer, the following two situations may occur subsequently.

[0287] Situation 1: The goal of the intent has been achieved

[0288] In this case, step 804 can be executed, and step 804 is as follows.

[0289] Step 804, if the intended service producer determines that all goals of the intent have been achieved, then the intended service producer sends an intent report to the intended service consumer. Correspondingly, the intended service consumer receives the intent report from the intended service producer. Among them, the intent report is used to indicate that the achieved value of the intent's target has achieved the goal of the intent. Exemplarily, the intent report includes achievement information and the achieved value of the intent's target, and the achievement information is used to indicate that the goal of the intent has been achieved or the intent has been achieved.

[0290] Situation 2: The target of the intention is not achieved

[0291] In Situation 2, according to whether the achieved value of the target of the intention is stable, it can be further divided into Situation A and Situation B.

[0292] Situation A: The achieved value of the target of the intention is not stable

[0293] In Situation A, steps 805 to 809 can be executed. Steps 805 to 809 are as follows.

[0294] Step 805, the intention service producer queries the knowledge base for the estimated stabilization time.

[0295] Exemplarily, the intention service producer can query the knowledge base for the estimated time when the current action group for the intention is completed and takes effect.

[0296] Step 806, the knowledge base sends the estimated stabilization time to the intention service producer.

[0297] The way for the knowledge base to estimate the estimated stabilization time can refer to the description in Step 505 and will not be elaborated here.

[0298] Step 807, the intention service producer sends an intention report to the intention service consumer. Correspondingly, the intention service consumer receives the intention report from the intention service producer.

[0299] Among them, in addition to indicating that the achieved value of the target of the intention does not achieve the target of the intention, the intention report is also used to indicate the stability information of the achieved value of the target of the intention and the estimated stabilization time. The stability information is used to indicate that the achieved value of the target of the intention is not stable.

[0300] For example, combined with Figure 3 , in Figure 3In the example shown, the target of the intent is to ensure that the average downlink throughput rate > 25 Mbps, and the reporting period of the intent report is 15 minutes. An intent conflict is encountered during the execution of this intent. At the 7th minute, the intent service producer determines that the target of the intent has not been achieved and switches the network management task, service management task, or action group for the first time. When the first reporting period (i.e., the 15th minute) arrives, the intent is still in the new intent effective period after the first switch of the network management task, service management task, or action group. Therefore, at 15 minutes, the intent report reported by the intent service producer indicates that the target of the intent has not been achieved, the achieved value of the target of the intent is 23 Mbps, the achieved value of the target of the intent is not stable, and the estimated stabilization time is 37 minutes. At the 23rd minute, the intent service producer determines that the target of the intent has not been achieved and switches the network management task, service management task, or action group for the second time. When the second reporting period (i.e., the 30th minute) arrives, the intent is still in the new intent effective period after the second switch of the network management task, service management task, or action group. Therefore, at 30 minutes, the intent report reported by the intent service producer indicates that the target of the intent has not been achieved, the achieved value of the target of the intent is 24 Mbps, the achieved value of the target of the intent is not stable, and the estimated stabilization time is 7 minutes.

[0301] Optionally, in step 808, after the subsequent intent service producer detects that the achieved value of the target of the intent has stabilized, it updates the stabilization time to the knowledge base. The stabilization time is the time when the achieved value of the target of the intent reaches stability.

[0302] Exemplarily, the intent service producer can update to the knowledge base the time when the current action group for the intent is completed and becomes effective.

[0303] In step 809, the intent service consumer manages the intent according to the intent report.

[0304] Step 809 can refer to the relevant description at step 505 in method 500, and will not be elaborated here.

[0305] Situation B: The achieved value of the target of the intent has stabilized

[0306] In situation B, steps 810 and 811 can be executed. Steps 810 and 811 are as follows.

[0307] In step 810, the intent service producer sends an intent report to the intent service consumer. Correspondingly, the intent service consumer receives the intent report from the intent service producer. The intent report is used not only to indicate that the achieved value of the target of the intent has not achieved the target of the intent, but also to indicate the stability information of the achieved value of the target of the intent. The stability information is used to indicate that the achieved value of the target of the intent has stabilized.

[0308] For example, in combination with the example in step 807, when the third reporting period (i.e., the 45th minute) arrives, the network management tasks, service management tasks, or action groups of the second handover have been executed and become effective. Therefore, at the 45th minute, the intent report reported by the intent service producer indicates that the target of the intent is not achieved, the achieved value of the target of the intent is 24.8 Mbps, and the achieved value of the target of the intent has stabilized.

[0309] Step 811, the intent service consumer manages the intent according to the intent report.

[0310] Step 811 can refer to the relevant description of step 505 and will not be elaborated here.

[0311] In method 800, a stability attribute and an expected stabilization time can be added to the report template. The stability attribute is used to describe whether the achieved value of the target of the intent is stable, and the expected stabilization time is used to describe the expected time when the stability attribute of the achieved value of the target of the intent becomes stable. When the target of the intent is not achieved, the reported intent report can indicate the stability of the target of the intent and the expected stabilization time. The stability can enable the intent service consumer to know whether the achieved value of the target indicated by the intent report is stable and reliable, and the expected stabilization time can allow the intent service consumer to further judge whether to wait. These two attributes can assist the intent service consumer in making decisions, help select an appropriate time to intervene or manage the execution of the intent, thereby helping to reduce the probability of misjudgment by the intent service consumer and reducing resource waste.

[0312] Taking the example of the production entity periodically reporting the intent report, the solutions in methods 400 and 500 where the intent report additionally carries the stability information of the achieved value of the target of the intent, and the intent creation request message carries the first observation duration and / or the first range will be described in detail below.

[0313] Figure 9 is a schematic flowchart of the management method 900 for network management intent provided by this application. In Figure 9 the stable observation duration can correspond to the first observation duration in methods 400 and 500, and the degree of stability can correspond to the first range in methods 400 and 500.

[0314] Step 901, the intent service consumer configures an intent report template for the intent service producer.

[0315] Among them, the intent report template can stipulate that the stability attribute is included in the intent report IOC.

[0316] Step 901 can refer to step 601.

[0317] Step 902, the intent service consumer requests the intent service producer to create an intent, and the intent service producer creates and executes the intent.

[0318] Step 902 can refer to Step 602. The difference is that the intention creation request message sent by the intention service consumer includes the period for reporting the intention report, the stable observation duration (stableObservationDuration), and the stable degree (stableDegree). Among them, the stable observation duration is the observation duration required to determine whether the implementation value of the intention target is stable. The stable degree is the fluctuation range required for the implementation value of the intention target to be stable, and can also be described as the fluctuation range required for the relevant performance indicators of the intention target to be stable. Of course, the period for reporting the intention report may not be carried in the intention creation request message, but provided to the intention service producer through other messages, such as the subscription request message.

[0319] Taking the performance guarantee type intention as an example, to ensure the smooth progress of an important video conference, it is necessary to ensure high-definition and smoothness of the video conference. The target 1 of the performance guarantee type intention is to ensure that the throughput rate is greater than 25 Mbps, the reporting period of the intention report is 15 minutes, the stable observation duration is 3 minutes, and the stable degree is 10%.

[0320] When the stable observation duration and the stable degree are carried in the intention creation request message, the fluctuation range of the implementation value of the intention target needs to be within the stable degree within the stable observation duration to be judged as stable.

[0321] Step 903, the intention service producer evaluates the intention.

[0322] Specifically, the intention service producer continuously evaluates the achievement of the intention target and the stability of the implementation value of the intention target. The method for the intention service producer to evaluate the stability of the implementation value of the intention target can refer to the method in Step 402 for the intention service producer to judge whether the implementation value of the intention target is stable. The stable observation duration and / or the stable degree relied on during the evaluation are obtained from Step 902.

[0323] For example, combining the example in Step 902, the intention service producer continuously judges whether the fluctuation range of the throughput rate within the past 3 minutes is within 10%. If the fluctuation range of the throughput rate is within 10%, it is judged that the implementation value of Target 1 is stable; if the fluctuation range of the throughput rate is outside 10%, it is judged that the implementation value of Target 1 is not stable.

[0324] Steps 904 to 906 can refer to Steps 704 to 706 and will not be elaborated here.

[0325] In method 900, the stable observation duration and stability degree can be increased in the intent IOC, enabling the intent service consumer to customize the metrics for measuring whether the implementation value of the intent target is stable. As a result, the stable information reported by the intent service producer is more in line with the expectations of the intent service consumer, which can better assist the intent service consumer in making decisions, help select the appropriate timing to intervene or manage the execution of the intent, thereby reducing the probability of misjudgment by the intent service consumer and reducing resource waste.

[0326] As described above in conjunction with Figures 4 to 9 , the method embodiments provided in this application have been described in detail. Next, the apparatus embodiments of this application will be described in conjunction with Figures 10 to 12 .

[0327] It can be understood that, in order to implement the functions in the above embodiments, Figures 10 to 12 the apparatuses in include the corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should easily realize that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, this application can be implemented in the form of hardware or a combination of hardware and computer software.

[0328] Figure 10 Figure 11 FIG. [FIG. number not provided in the original] is a schematic structural diagram of a possible apparatus provided for the embodiments of this application. These apparatuses can be used to implement the functions of the production entity or consumption entity in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments.

[0329] As Figure 10 shown, apparatus 10 includes a transceiver unit 11 and a processing unit 12.

[0330] When the device 10 is used to implement the functions 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 402, 403, 404, 502, 503, 504, 603, 605, 607, 704, 705, 804, 805, 806, 807, 808, 810, 904 or 905, and the processing unit 12 is used to execute the processing steps of the production entity, such as steps 401, 501, 505, 601, 602, 604, 701, 702, 703, 801, 802, 803, 901, 902 or 903. When the device 10 is used to implement the functions of the consumer entity in the above method embodiments, the transceiver unit 11 is used to execute the transceiver steps of the consumer entity, such as steps 402, 403, 404, 502, 503, 504, 603, 605, 704, 705, 804, 807, 810, 904 or 905, and the processing unit 12 is used to execute the processing steps of the consumer entity, such as steps 405, 505, 601, 602, 606, 701, 702, 706, 801, 802, 809, 811, 901, 902 or 906.

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

[0332] As Figure 11 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 functions of the above processing unit 12.

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

[0334] 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 functions of the above processing unit 12, and the interface circuit 22 is used to implement the functions of the above transceiver unit 11.

[0335] Exemplarily, when the device 20 is a chip applied to a production entity or a consumption entity, the chip implements the functions of the production entity or the consumption entity 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 or the consumption entity, and this information is sent by other devices to the production entity or the consumption entity; or, the chip sends information to other modules (such as a radio frequency module or an antenna) in the production entity or the consumption entity, and this information is sent by the production entity or the consumption entity to other devices.

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

[0337] Among them, the logic circuit 31 can be a processing circuit in the chip system 30. The logic circuit 31 can 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 can 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.

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

[0339] For example, the logic circuit 31 is used to implement the processing-related operations performed by the production entity or the consumption entity 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 or the consumption entity in the above method embodiments.

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

[0341] The present application also provides a chip, including a processor, the processor is coupled to a memory, the memory is used to store computer programs or instructions, and the processor is used to execute the computer programs or instructions stored in the memory to implement the methods performed by the production entity or the consumption entity in the above method embodiments.

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

[0343] The present application also provides a computer program product, including instructions, which when executed by a computer, implement the methods executed by the production entity or the consumption entity in the above method embodiments.

[0344] The present application also provides a communication system, which includes at least one of the production entity, the consumption entity, the knowledge base, or the digital twin system in the above embodiments.

[0345] For the explanations and beneficial effects of the relevant content in any of the above provided devices, reference can be made to the corresponding method embodiments provided above, and details are not elaborated here.

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

[0347] 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 may be composed of corresponding software modules, and the software modules may 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, so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and the storage medium may be located in the ASIC. Additionally, the ASIC may be located in the production entity or the consumption entity. Of course, the processor and the storage medium may also exist as discrete components in the production entity or the consumption entity.

[0348] In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are executed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable devices. The computer program or instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer program or instructions may 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 may 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 may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disc; or it may be a semiconductor medium, such as a solid-state drive.

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

[0350] Unless otherwise specified, all technical and scientific terms used in the embodiments of the present application have the same meaning as commonly understood by those skilled in the technical field of the present application. The terms used in the present application are only for the purpose of describing specific embodiments and are not intended to limit the scope of the present application. It should be understood that the above is for illustrative purposes only. The above examples are only to help those skilled in the art understand the embodiments of the present application, rather than to limit the embodiments of the application to the specific 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 the present application.

Claims

1. A method for managing network management intents, characterized in that, the method comprises: receiving an intent report from a production entity, the intent report indicating that a stable achievement value of a target of a network management intent fails to achieve the target of the network management intent; managing the network management intent according to the intent report.

2. The method according to claim 1, characterized in that, the method further comprises: sending request information to the production entity, the request information being used to request the production entity to send the intent report.

3. The method according to claim 2, characterized in that, sending the request information to the production entity includes: sending a subscription request message to the production entity, the subscription request message containing the request information.

4. The method according to claim 2 or 3, characterized in that, the request information includes the network management intent or an identifier of the network management intent.

5. The method according to any one of claims 2 to 4, characterized in that, the request information includes indication information, the indication information being used to indicate to send an intent report when a stable achievement value of a target of the network management intent fails to achieve the target of the network management intent.

6. The method according to any one of claims 1 to 5, characterized in that, the stable achievement value includes: an achievement value of the target of the network management intent when all action groups for the network management intent have become effective, wherein the action group includes one or more actions for managing managed entities of the network management intent; or, an achievement value of the target of the network management intent when a performance metric value of a managed entity of the network management intent continuously remains within a first range within a first observation duration.

7. The method according to any one of claims 1 to 6, characterized in that, the method further comprises: sending first information to the production entity, the first information being used to indicate the first observation duration and / or the first range; wherein, the first observation duration is an observation duration required to determine that an achievement value of the target of the network management intent is stable, and the first range is a fluctuation range required to be satisfied for the achievement value of the target of the network management intent to be stable.

8. The method according to any one of claims 1 to 7, characterized in that, managing the network management intent according to the intent report includes: sending a first request message to the production entity, the first request message being used to request the production entity to delete the network management intent; or, sending a second request message to the production entity, the second request message being used to request the production entity to modify the network management intent, wherein modifying the network management intent includes one or more of the following operations: reducing an expected value of a target that the network management intent fails to achieve, replacing an action group for the network management intent, or increasing a priority of the network management intent.

9. A method for managing network management intents, characterized in that, the method comprises: monitoring an achievement value of a target of a network management intent; Send an intent report to a consuming entity, where the intent report is used to indicate that the stable achievement value of the target of the network management intent fails to reach the target of the network management intent.

10. The method according to claim 9, wherein, the method further includes: receiving request information from the consuming entity, where the request information is used to request the intent report.

11. The method according to claim 10, wherein, the receiving the request information from the consuming entity includes: receiving a subscription request message from the consuming entity, where the subscription request message includes the request information.

12. The method according to claim 10 or 11, wherein, the request information includes the network management intent or an identifier of the network management intent.

13. The method according to any one of claims 10 to 12, wherein, the request information includes indication information, where the indication information is used to indicate that an intent report is to be sent when the stable achievement value of the target of the network management intent fails to reach the target of the network management intent.

14. The method according to any one of claims 9 to 13, wherein, the method further includes: determining that the achievement value of the target of the network management intent is stable.

15. The method according to claim 14, wherein, the determining that the achievement value of the target of the network management intent is stable includes: determining that all action groups for the network management intent have become effective, where an action group includes one or more actions for managing the managed entities of the network management intent; or, determining that the performance metric values of the managed entities of the network management intent continuously fall within a first range within a first observation duration.

16. The method according to any one of claims 9 to 15, wherein, the method further includes: receiving first information from the consuming entity, where the first information is used to indicate a first observation duration and / or a first range; wherein, the first observation duration is the observation duration required to determine that the achievement value of the target of the network management intent is stable, and the first range is the fluctuation range that the achievement value of the target of the network management intent needs to satisfy to be stable.

17. A method for managing a network management intent, wherein, the method includes: a production entity monitors the achievement value of the target of the network management intent; the production entity sends an intent report, and the consuming entity receives the intent report, where the intent report is used to indicate that the stable achievement value of the target of the network management intent fails to reach the target of the network management intent; the consuming entity manages the network management intent according to the intent report.

18. The method according to claim 17, wherein, the method further includes: the consuming entity sends request information, and the production entity receives the request information, where the request information is used to request the intent report.

19. A management device for a network management intent, wherein, the device includes a transceiver unit and a processing unit; The transceiver unit is configured to receive an intention report, where the intention report is used to indicate that the stable achievement value of the target of the network management intention fails to reach the target of the network management intention. The processing unit is configured to manage the network management intention according to the intention report.

20. A management device for network management intention Characterized in that The device includes a transceiver unit and a processing unit; The processing unit is configured to monitor the achievement value of the target of the network management intention; The transceiver unit is configured to send an intention report, where the intention report is used to indicate that the stable achievement value of the target of the network management intention fails to reach the target of the network management intention.

21. A communication device Characterized in that It includes a processor and an interface circuit. The interface circuit is configured to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device. The processor is configured to implement the method according to any one of claims 1 to 18 through logic circuits or by executing code instructions.

22. The communication device according to claim 21 Characterized in that The communication device is a chip or a chip system.

23. A computer-readable storage medium Characterized in that The storage medium stores a computer program or instructions. When the computer program or instructions are executed by a communication device, the method according to any one of claims 1 to 18 is implemented.

24. A communication system Characterized in that It includes a communication device for executing the method according to any one of claims 1 to 8 and a communication device for executing the method according to any one of claims 9 to 16.

Images