A network management intention management method, device and system

By executing management action groups within a subset of managed entities, the problem of network management intents being difficult to achieve in complex environments is solved, enabling flexible and efficient network management intent management and improving the reliability and resource utilization efficiency of network management intents.

CN119449567BActive Publication Date: 2025-11-28HUAWEI TECH CO LTD

Patent Information

Application Number
CN202310991543.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-08-07
Publication Date
2025-11-28
Estimated Expiration
2043-08-07

AI Technical Summary

Technical Problem

Existing methods for managing network management intents are not flexible enough, especially in complex and ever-changing network environments, making it difficult to effectively achieve goals. This leads to repeated deletion or suspension of network management intents, failing to meet the needs of consumer entities.

Method used

If a network management intent goal within the scope of a set of managed entities fails to be achieved, the production entity can flexibly execute the first or second management action group to achieve the goal within the subset of managed entities, avoiding direct deletion or suspension of the entire intent, and utilizing the action group executed by the subset of managed entities to achieve the goal.

Benefits of technology

It improves the management flexibility and reliability of network management intentions, reduces signaling interactions, saves transmission resources, and optimizes the execution of network management intentions through time-dimensional constraints.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119449567B_ABST
    Figure CN119449567B_ABST
Patent Text Reader

Abstract

The application provides a network management intention management method, device and system, and the method comprises the following steps: determining that the execution of a first management action group fails to achieve a target of a network management intention in a range of a managed entity set of the network management intention, wherein the managed entity set comprises at least two managed entities, and the first management action group comprises at least one action for managing the managed entity set; and executing the first management action group or a second management action group to achieve the target of the network management intention in a range of a managed entity subset, wherein the managed entity subset is a subset of the managed entity set, and the second management action group comprises at least one action for managing the managed entity subset. Thus, a flexible network management intention management mode is provided.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication technology, and more particularly, to a network management intent management method, device and system. BACKGROUND

[0002] With the development of network resource management, a network management service consumer entity can not directly manage network resources. The network management service consumer entity can send a network management intent to a network management service producer entity, and the network management service producer entity executes the network management intent so that the specified performance indicators of the network devices in a specific range reach the expected target. The current network management intent management method is not flexible enough. For example, when the network environment of the network management intent is complex and changeable, if the network management service producer entity determines that the target of the network management intent is not achieved, the network management service producer entity will delete or suspend the network management intent, and then issue a new network management intent. If the new network management intent cannot be achieved, the network management service producer entity will delete or suspend the new network management intent again, and so on.

[0003] Therefore, how to improve the flexibility of managing the network management intent is a technical problem to be solved. SUMMARY

[0004] The present application provides a network management service intent management method, device and system, and provides a flexible network management intent management method.

[0005] In a first aspect, a network management intent management method is provided. The method can be executed by a network management service producer entity or a chip in the network management service producer entity. The method includes determining that execution of a first management action group fails to achieve a target of a network management intent in a managed entity set range of the network management intent, wherein the managed entity set includes at least two managed entities, and the first management action group includes at least one action for managing the managed entity set; and executing the first management action group or a second management action group to achieve the target of the network management intent in a managed entity subset range, wherein the managed entity subset is a subset of the managed entity set, and the second management action group includes at least one action for managing the managed entity subset.

[0006] Based on the technical solution, after the producer entity determines that the target of the network management intent in the managed entity set range cannot be achieved, the producer entity can flexibly execute the first management action or the second management action group based on the managed entity subset to achieve the target of the network management intent in the managed entity subset range, instead of directly deleting or suspending the entire network management intent. Therefore, a flexible network management intent management method is provided.

[0007] The executing the first management action group comprises: continuing to execute the first management action group, or re-executing the first management action group.

[0008] With reference to the first aspect, in some implementations of the first aspect, the method further includes: receiving a request message, the request message being used to request to create the network management intent or to modify the network management intent, the request message comprising the network management intent, or the request message comprising the network management intent and the subset of managed entities.

[0009] Based on the technical solution, the consumer entity can carry the subset of managed entities in the request message used to request the producer entity to create the network management intent, so that the signaling interaction between the consumer entity and the producer entity can be reduced, and transmission resources are saved.

[0010] With reference to the first aspect, in some implementations of the first aspect, the object context in the network management intent comprises information used to determine the set of managed entities and / or the subset of managed entities.

[0011] With reference to the first aspect, in some implementations of the first aspect, after determining that the execution of the first management action group fails to achieve the target of the network management intent within the set of managed entities of the network management intent, the method further includes: sending notification information, the notification information indicating that the target of the network management intent fails to be achieved within the set of managed entities; and receiving the subset of managed entities in response to the notification information.

[0012] Based on the technical solution, the consumer entity can send the subset of managed entities to the producer entity in response to the notification information, that is, the consumer entity can produce the subset of managed entities based on the notification information, so that the management manner of the network management intent is more flexible.

[0013] With reference to the first aspect, in some implementations of the first aspect, the execution of the first management action group fails to achieve the target of the network management intent within the set of managed entities of the network management intent, which means that the execution of the first management action group fails to achieve the target of the network management intent within a first time period within the set of managed entities of the network management intent; and the executing the first management action group or the second management action group to achieve the target of the network management intent within the subset of managed entities means that the first management action group or the second management action group is executed to achieve the target of the network management intent within a second time period within the subset of managed entities, wherein the second time period is a subset of the first time period.

[0014] Based on the technical solution, the production entity can consider the constraint condition in the time dimension when determining whether the target of the network management intention is achieved and when executing the first management action group or the second management action group, so that the management manner of the network management intention is more flexible.

[0015] Exemplarily, the target of the network management intention includes that an index value of a performance index reaches a corresponding performance index range, where the performance index is an energy saving index or a throughput rate index.

[0016] With reference to the first aspect, in some implementations of the first aspect, the executing the first management action group or the second management action group comprises: determining, based on the subset of managed entities, network resources in the subset of managed entities that can be used to achieve the target of the network management intention; and executing the first management action group or the second management action group based on the network resources.

[0017] Based on the technical solution, the production entity can determine the network resources that can be used, and then determine and execute the first management action group or the second management action group based on the network resources, so that the reliability of the management of the network management intention can be improved.

[0018] With reference to the first aspect, in some implementations of the first aspect, the method further comprises: determining that a reason why the executing the first management action group fails to achieve the target of the network management intention in the set of managed entities is that an intention conflict occurs.

[0019] Based on the technical solution, in the scenario where the intention conflict occurs, the production entity can not directly delete or suspend the entire network management intention, but can execute the first management action group or the second management action group to achieve the target of the network management intention in the subset of managed entities, so that the flexibility of the management of the network management intention is provided.

[0020] With reference to the first aspect, in some implementations of the first aspect, the method further comprises: sending an intention report, the intention report comprising an achievement situation of the target of the network management intention in the subset of managed entities.

[0021] Based on the technical solution, the consumption entity can know the execution situation of the network management intention, and can better manage the network management intention.

[0022] With reference to the first aspect, in some implementations of the first aspect, the intention report further comprises an achievement situation of the target of the network management intention in the set of managed entities other than the subset of managed entities.

[0023] Based on the technical solution, the consumption entity can improve the management manner of the network management intention based on the overall achievement situation of the set of managed entities.

[0024] In a second aspect, a method for managing a network management intent is provided, which can be performed by a network management service producer or a chip in the network management service producer. The method comprises: determining a subset of managed entities, the subset of managed entities being a subset of a set of managed entities of the network management intent, wherein the set of managed entities comprises at least two managed entities, and the subset of managed entities is used to determine a second set of management actions for achieving a target of the network management intent in the subset of managed entities when a first set of management actions fails to achieve the target of the network management intent in the set of managed entities, wherein the first set of management actions comprises at least one action for managing the set of managed entities, and the second set of management actions comprises at least one action for managing the subset of managed entities; and sending the subset of managed entities.

[0025] The beneficial technical effects of the various implementations of the second aspect can be referred to the descriptions of the related implementations of the first aspect, and will not be elaborated here.

[0026] In combination with the second aspect, in some implementations of the second aspect, the sending the subset of managed entities comprises: sending a request message, the request message being used to request to create the network management intent or to modify the network management intent, the request message comprising the network management intent, the network management intent comprising the subset of managed entities, or the request message comprising the network management intent and the subset of managed entities.

[0027] In combination with the second aspect, in some implementations of the second aspect, the object context in the network management intent comprises information used to determine the set of managed entities and / or the subset of managed entities.

[0028] In combination with the second aspect, in some implementations of the second aspect, the method further comprises: receiving notification information, the notification information indicating that the target of the network management intent fails to be achieved in the set of managed entities; and the sending the subset of managed entities comprises: sending the subset of managed entities in response to the notification information.

[0029] Exemplarily, the target of the network management intent comprises that an index value of a performance index reaches a corresponding performance index range, wherein the performance index is a power saving index or a throughput index.

[0030] In combination with the second aspect, in some implementations of the second aspect, the reason that the execution of the first set of management actions fails to achieve the target of the network management intent in the set of managed entities is that an intent conflict occurs.

[0031] In combination with the second aspect, in some implementations of the second aspect, the method further comprises: receiving an intent report, the intent report comprising an achievement of the target of the network management intent in the subset of managed entities.

[0032] With reference to the second aspect, in some implementations of the second aspect, the intent report further comprises a status of achievement of the target of the network management intent within the set of managed entities outside the subset of managed entities.

[0033] With reference to the third aspect, in some implementations of the third aspect, the method further comprises: sending a request message, the request message being used to request creation of the network management intent or to request modification of the network management intent, the request message comprising the network management intent, the network management intent comprising the subset of managed entities, or the request message comprising the network management intent and the subset of managed entities; and receiving the request message.

[0034] With reference to the third aspect, in some implementations of the third aspect, the object context in the network management intent comprises information used to determine the set of managed entities and / or the subset of managed entities.

[0035] With reference to the third aspect, in some implementations of the third aspect, the method further comprises: sending notification information, the notification information indicating that the target of the network management intent has failed to be achieved within the set of managed entities; receiving the notification information; and receiving the subset of managed entities in response to the notification information.

[0036] With reference to the third aspect, in some implementations of the third aspect, the object context in the network management intent comprises information used to determine the set of managed entities and / or the subset of managed entities.

[0037] With reference to the third aspect, in some implementations of the third aspect, the method further comprises: sending notification information, the notification information indicating that the target of the network management intent has failed to be achieved within the set of managed entities; receiving the notification information; and receiving the subset of managed entities in response to the notification information.

[0038] With reference to the third aspect, in some implementations of the third aspect, the failure of the execution of the first management action group to achieve the target of the network management intent in the scope of the set of managed entities of the network management intent is that the execution of the first management action group fails to achieve the target of the network management intent in the scope of the set of managed entities of the network management intent within a first time period; and the achieving the target of the network management intent in the scope of the subset of managed entities is that the achieving the target of the network management intent in the scope of the subset of managed entities within a second time period, wherein the second time period is a subset of the first time period.

[0039] For example, the target of the network management intent comprises that an index value of a performance index reaches a corresponding performance index range, wherein the performance index is a power saving index or a throughput rate index.

[0040] With reference to the third aspect, in some implementations of the third aspect, the executing the first management action group or the second management action group comprises: determining, based on the subset of managed entities, network resources available for achieving the target of the network management intent in the scope of the subset of managed entities; and executing the first management action group or the second management action group based on the network resources.

[0041] With reference to the third aspect, in some implementations of the third aspect, the determining that the execution of the first management action group fails to achieve the target of the network management intent in the scope of the set of managed entities is that an intent conflict occurs.

[0042] With reference to the third aspect, in some implementations of the third aspect, the method further comprises: sending an intent report, the intent report comprising an achievement of the target of the network management intent in the scope of the subset of managed entities; and receiving the intent report.

[0043] With reference to the third aspect, in some implementations of the third aspect, the intent report further comprises an achievement of the target of the network management intent in the scope of the set of managed entities other than the scope of the subset of managed entities.

[0044] In a fourth aspect, a network management intent management apparatus is provided, which comprises a determining unit and an executing unit. The determining unit is configured to determine that execution of a first management action group fails to achieve a target of a network management intent in a range of a set of managed entities of the network management intent, wherein the set of managed entities comprises at least two managed entities, and the first management action group comprises at least one action for managing the set of managed entities. The executing unit is configured to execute the first management action group or a second management action group to achieve the target of the network management intent in a range of a subset of managed entities, wherein the subset of managed entities is a subset of the set of managed entities, and the second management action group comprises at least one action for managing the subset of managed entities.

[0045] The determining unit and the executing unit can be units in the processing unit.

[0046] For the various implementations of the fourth aspect and the beneficial technical effects of the various implementations, reference can be made to the descriptions of the related implementations of the first aspect, and details are not repeated.

[0047] In a fifth aspect, a network management intent management apparatus is provided, which comprises a transceiving unit and a processing unit. The processing unit is configured to determine a subset of managed entities, wherein the subset of managed entities is a subset of a set of managed entities of a network management intent, and the set of managed entities comprises at least two managed entities. The subset of managed entities is used to determine a second management action group when execution of a first management action group fails to achieve a target of the network management intent in the range of the set of managed entities, so as to achieve the target of the network management intent in the range of the subset of managed entities. The first management action group comprises at least one action for managing the set of managed entities, and the second management action group comprises at least one action for managing the subset of managed entities. The transceiving unit is configured to send the subset of managed entities.

[0048] For the various implementations of the fifth aspect and the beneficial technical effects of the various implementations, reference can be made to the descriptions of the related implementations of the first aspect and the second aspect, and details are not repeated.

[0049] In a sixth aspect, a communication apparatus is provided, which implements the first aspect or any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect, or the third aspect or any possible implementation of the third aspect. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software comprises one or more units corresponding to the above functions.

[0050] In a seventh aspect, a communication apparatus is provided, which comprises a processor and a memory. Optionally, the communication apparatus can further comprise a transceiver. The memory is configured to store a computer program, and the processor is configured to invoke and run the computer program stored in the memory, and control the transceiver to transceive signals, so that the communication apparatus performs the method in the first aspect, or any possible implementation of any of the aspects in the first aspect.

[0051] Exemplarily, the communication apparatus is a network management service producer entity.

[0052] In an eighth aspect, a communication apparatus is provided, which comprises a processor and a memory. Optionally, the communication apparatus can further comprise a transceiver. The memory is configured to store a computer program, and the processor is configured to invoke and run the computer program stored in the memory, and control the transceiver to transceive signals, so that the communication apparatus performs the method in the second aspect, or any possible implementation of any of the aspects in the second aspect.

[0053] Exemplarily, the communication apparatus is a network management service consumer entity.

[0054] In a ninth aspect, a communication apparatus is provided, which comprises a processor and a communication interface. The communication interface is configured to receive data and / or information, and transmit the received data and / or information to the processor. The processor is configured to process the data and / or information. The communication interface is further configured to output the data and / or information processed by the processor, so that the method in the first aspect, or any possible implementation of any of the aspects in the first aspect is performed. The communication apparatus can be a chip applied to a network management service producer network element.

[0055] In a tenth aspect, a communication apparatus is provided, which comprises a processor and a communication interface. The communication interface is configured to receive data and / or information, and transmit the received data and / or information to the processor. The processor is configured to process the data and / or information. The communication interface is further configured to output the data and / or information processed by the processor, so that the method in the second aspect, or any possible implementation of any of the aspects in the second aspect is performed. The communication apparatus can be a chip applied to a network management service consumer network element.

[0056] In an eleventh aspect, a computer readable storage medium is provided, which stores computer instructions. When the computer instructions are run on a computer, the method in the first aspect, or any possible implementation of any of the aspects in the first aspect is performed.

[0057] In a twelfth aspect, a computer-readable storage medium is provided, the computer-readable storage medium having computer instructions stored therein, which when executed on a computer, cause the method as in the second aspect, or any possible implementation of any of the aspects of the second aspect, to be performed.

[0058] In a thirteenth aspect, a computer program product is provided, the computer program product comprising computer program code which, when executed on a computer, causes the method as in the first aspect, or any possible implementation of any of the aspects of the first aspect, to be performed.

[0059] In a fourteenth aspect, a computer program product is provided, the computer program product comprising computer program code which, when executed on a computer, causes the method as in the second aspect, or any possible implementation of any of the aspects of the second aspect, to be performed.

[0060] In a fifteenth aspect, a wireless communication system is provided, comprising a communication device as in the fourth aspect, and / or a communication device as in the fifth aspect.

[0061] In a sixteenth aspect, a wireless communication system is provided, comprising a communication device as in any one or more of the fourth to fifteenth aspects, or a communication device in any possible implementation of any of these aspects. BRIEF DESCRIPTION OF DRAWINGS

[0062] Figure 1 is a schematic diagram of a data structure of a network management intent;

[0063] Figure 2 is a schematic architecture diagram of a communication system provided by an embodiment of the present application;

[0064] Figure 3 is a schematic flow diagram of a management method of a network management intent provided by an embodiment of the present application;

[0065] Figure 4 is a schematic flow diagram of an implementation of a network management intent provided by an embodiment of the present application;

[0066] Figure 5 is a schematic flow diagram of another implementation of a network management intent provided by an embodiment of the present application;

[0067] Figures 6 to 8 is a schematic diagram of a possible communication device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0068] The technical solutions in the present application will be described below with reference to the drawings.

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

[0070] For the sake of clarity, some terms in the embodiments of the present application are explained below.

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

[0072] 1.1 Network management

[0073] Network management refers to managing network resources, including but not limited to monitoring, controlling and recording the performance and usage of network resources, and issuing a group of management actions to network resources (such as devices in the network) based on the detected network conditions to make the network run effectively. Exemplarily, network management can be monitoring, testing, configuring, analyzing, evaluating and controlling network resources, etc. Network management can also be able to report and handle in time when the network fails, and coordinate and maintain the efficient operation of the network system, etc. Among them, network resources are the objects of network management, which can also be called network objects or managed entities. Exemplarily, network resources can be base station devices, routers, switches, core network devices, etc. For this purpose, the embodiments of the present application do not make special limitations, and for the sake of convenience, the embodiments of the present application are described by way of example with managed entities, but other objects of network management can be used instead.

[0074] 1.2 Network management service

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

[0076] 1.3 Network management service producer entity

[0077] The network management service providing entity is referred to as a network management service producer entity. Exemplarily, the capability or function of the network management service producer entity can be deployed on a certain network element, which is referred to as a network management service producer network element; the capability or function of the network management service producer entity can also be deployed on other devices, for which the embodiments of the present application do not make any limitation; for the convenience of description, the embodiments of the present application are described by taking the network management service producer entity as an example, but all can be replaced by other devices on which the capability or function of the network management service producer entity is deployed.

[0078] 1.4 Network management service consumer entity

[0079] The network management invoking entity is referred to as a network management service consumer entity. Exemplarily, the capability or function of the network management service consumer entity can be deployed on a certain network element, which is referred to as a network management service consumer network element; the capability or function of the network management service consumer entity can also be deployed on other devices, for which the embodiments of the present application do not make any limitation; for the convenience of description, the embodiments of the present application are described by taking the network management service consumer entity as an example, but all can be replaced by other devices on which the capability or function of the network management service consumer entity is deployed.

[0080] 2. Network management intent (referred to as intent)

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

[0082] In the intent-based interaction scenario of the present application, two roles are mainly included, which are a network management providing entity and a network management service consumer entity. The network management providing entity can also be referred to as a network management provider, or an intent provider, or an intent handler, etc. The network management service consumer entity can also be referred to as a network management service consumer, or an intent consumer, or an intent owner, etc.

[0083] The network management service consumer entity can be a caller of a network management service, can perform network management intent expression creation, modification, deletion, query, and the like, can be configured in a network management system (NMS), or an element management system (EMS), or network equipment (NE), can be a management function, or a management function entity, or a management entity, or network equipment, or a network element, and the like, and the present application does not limit the same.

[0084] The intent can be applied to a network system, so that a specified performance indicator of a network device in a specific range reaches an expected target. The intent can express a desire for the network system through formal specification and description information. The formal specification can refer to a syntax or semantics specific to the intent, and the description information can be used to describe the requirements, targets, and constraints of the intent.

[0085] The intent can include at least one intent desire. Each intent desire can represent a performance requirement of a network management service consumer entity for a specific network object. One intent desire can be composed of at least one desire target and a desire object, and each desire target can represent a performance requirement of the network management service consumer entity for a certain specific attribute of the desire object. Exemplarily, the intent desire can include two desire targets, one of which is that the average downlink throughput is greater than 5 Mbps, and the other of which is that the end-to-end latency is less than 10 milliseconds. If the average downlink throughput of the desire object is greater than 5 Mbps, the desire target about the downlink throughput is satisfied. If the end-to-end latency of the desire object is less than 10 milliseconds, the desire target about the latency is satisfied. If both of the two desire targets of the intent desire are satisfied, the intent desire is fulfilled. If one or more intent desires are not satisfied, or one or more desire targets are not satisfied, the intent is not satisfied, or described as the intent is not fulfilled, or the intent is not implemented.

[0086] The intent can also include an intent context. The intent context can represent a constraint or condition of the network management service consumer entity for the intent. Exemplarily, the network management service consumer entity can constrain the action duration of the intent through the intent context.

[0087] The intent can also include a desire context. The desire context can represent a constraint or condition of the network management service consumer entity for an intent desire. Exemplarily, the network management service consumer entity can constrain the action duration of the intent desire through the desire context.

[0088] The intent can also include a target context, which can represent a constraint or condition of the network management service consuming entity on a desired target. Illustratively, the network management service consuming entity can constrain the duration of the desired target through the target context.

[0089] The intent can also include an object context, which can represent a constraint or condition of the network management service consuming entity on a network object acted on by the intent. Illustratively, the network management service consuming entity can indicate the region of the network object acted on by the intent through the object context.

[0090] The intent expectation, the desired target, and the intent context described above can be used as information elements in an information object class (IOC) in an intent creation request, and the network management service consuming entity can express the demand for the network management service by sending the information elements to the network management service producing entity.

[0091] The information elements in the intent IOC can express the demand for the network management service in a specific structure. Illustratively, Figure 1 An illustrative structure diagram of an intent IOC is shown.

[0092] Referring to Figure 1 , the intent IOC includes an intent expectation and an intent context. The intent expectation includes a desired object, a desired target, and a desired context. The desired object includes a desired object context (or also referred to as an object context), and the desired target includes a target context. It can be understood that a non-context type information element (such as the intent IOC, the intent expectation, the desired object, or the desired target) can include a context type information element (such as the intent context, the desired object context, the target context, the desired context, etc.), and the context type information element can be used to constrain the non-context type information element.

[0093] It can be understood that Figure 1 The relationship of the attributes in the intent IOC is illustratively described, and other attributes can be included in the intent IOC based on the demand for the network management service, which is not particularly limited in the present application. It can also be understood that the number of attributes of the same type is not particularly limited in the present application, for example, one or more parallel intent expectation attributes can be included in one intent IOC, and one or more parallel desired target attributes can be included in one intent expectation.

[0094] 3. Network management intent template

[0095] The network management intent template refers to a stylized description of a network management intent, which can also be referred to as a network management service requirement template. The embodiments of the present application do not limit the name. The intent template can be used to specify the syntax and semantics of the expressions of various attributes described above. For example, the intent template can specify the field types and value types that can be used by each attribute in the IOC. For example, the intent template can include intent expectation description information used to specify how the intent expectation is expressed. The intent expectation description information can specify the types of expected target attributes that can be included in the intent expectation, such as latency, bandwidth, maximum number of users, etc. The intent expectation description information can also specify the field types of each expected target, such as the field type of the expected target for latency is a string, the field type of the expected target for bandwidth is a string, and the field type of the expected target for the maximum number of users is an integer. For another example, the intent template can also include intent context description information used to specify how the intent context and the expectation context are expressed. The intent context description information can be used to specify the field types of the intent context, which is not particularly limited in the present application.

[0096] 4. Intent expression

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

[0098] For example, the intent expression includes a performance indicator information instance, a network object information instance, and a context information instance.

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

[0100] The target network object indicated by the network object information instance is an 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.

[0101] The context information instance is used to indicate a constraint condition of the network management intention expression. Exemplarily, the context information instance includes a constraint parameter of the network management intention expression, for example, the context information instance can include source and sink information corresponding to the target network object indicated by the network object instance.

[0102] The intention expectation information instance includes the performance indicator information instance and the network object information instance.

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

[0104] 5. Intention instance

[0105] The network management intention instance refers to a network management intention processing process created locally by a network management service providing entity according to the received network management intention expression (for example, the performance indicator information instance, the network object information instance, and the context information instance).

[0106] The network management intention processing process is used to process the network management intention expression. Exemplarily, the network management intention processing process can include an identifier used to identify the process; the network management intention processing process can include a computing resource used to perform network management intention translation, query a database (for example, a semantic knowledge base), and the like; and the network management intention processing process can include a storage resource used to store the network management intention expression, a result of network management intention translation, and the like.

[0107] The network management intention translation is used to convert the network management intention expression into a corresponding management action group. The management action group can be an instruction acting on a physical entity or a logical entity, for example, adjusting the antenna inclination of a certain base station or turning on the energy saving switch of a certain cell.

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

[0109] The network management action group is one or more network management actions generated by the network management service producer entity based on the intent expression. The network management service producer entity performs one or more network management actions to meet the intent of the network management service consumer entity. The network management action group can also be referred to as a management operation, an intent operation, or a network management task. The network management action group can be a set of operation instructions for a desired object (for example, a physical entity or a logical entity in the network system on which the intent acts), containing one or more instructions. For example, adjusting the antenna tilt angle of a base station, turning on the energy-saving switch of a cell, etc.

[0110] The network management service producer entity can generate multiple management action groups based on the intent expression. In the process of execution, the network management service producer entity can select some management action groups from the multiple management action groups for execution at a time. That is, the management action group generated by the network management service producer entity based on the intent expression is a selectable operation that can be used to meet the intent. The network management service producer entity can select one network management action group for execution to meet the intent, or can select multiple network management action groups for execution to meet the intent.

[0111] The related terms involved in the embodiments of the present application are described above, and the following describes the application scenarios to which the embodiments of the present application are applicable. Figure 1 The application scenarios to which the embodiments of the present application are applicable are described.

[0112] The related terms involved in the embodiments of the present application are described above, and the following describes the application scenarios to which the embodiments of the present application are applicable. Figure 1 The application scenarios to which the embodiments of the present application are applicable are described.

[0113] Figure 2 FIG. 1 is a schematic structural diagram of a communication system to which the embodiments of the present application are applicable. First, the devices possibly involved in the communication system are described.

[0114] 1. The network management service consumer entity 210 can be used to invoke a management service, or in other words, an intent service to manage a network system. For example, the network management service consumer entity 210 can instantiate an intent template, set an intent IOC, generate an intent expression, and send the intent expression to the network management service producer network element 220 to achieve the desired network system.

[0115] The network management service consuming entity 210 can also be referred to as a network management service consuming network element, a network management service consumer, an intent management service consumer, an intent consumer, an intent owner, etc. In future communication systems, the network management service consuming entity can also have other names, which are not particularly limited in the present application.

[0116] 2. The network management service producing entity 220 can be configured to provide management services. For example, the network management service producing entity 220 can receive an intent expression from the network management service consuming entity 210, perform intent translation, intent management, and intent execution and maintenance based on the intent expression.

[0117] The network management service producing entity 220 can also be referred to as a network management service producing network element, an intent management service provider, a network management service producer, an intent provider, an intent handler, etc. In future communication systems, the network management service producing entity can also have other names, which are not particularly limited in the present application.

[0118] The above entities can be network elements in hardware devices, or software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). It can be understood that the above entities can be implemented by one device, or can also be implemented by multiple devices together. In addition, the above entities can also be functional modules in a system, such as a network management system (NMS), an equipment management system (EMS), or functional modules in a device, such as one or more functional modules in a network equipment (NE), which can be a base station or a core network element.

[0119] For example, the network management service consuming entity 210 can be deployed in an NMS, and the network management service producing entity 220 can be deployed in different EMSs. The interaction between the network management service consuming entity 210 and the network management service producing entity 220 can be information interaction through an interface between the NMS and the EMS.

[0120] Exemplarily, the network management service consumer entity 210 can be deployed in an EMS, the network management service producer entity 220 can be deployed in a different NE, and the interaction between the network management service consumer entity 210 and the network management service producer entity 220 can be information interaction through an interface between the NMS and the EMS.

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

[0122] With the development of network resource management, the network management service consumer entity can not directly manage the network resources. The network management service consumer entity can send a message to the network management service producer entity, so that the network management service producer entity executes a network management intent, so as to make the specified performance indicators of the network devices in a specific range reach the expected target. At present, the application environment of the network management intent is usually complex and changeable, and therefore how to manage the network management intent in a complex and changeable environment is a technical problem to be solved.

[0123] Figure 3 is a schematic flowchart of the management method of the network management intent provided by the embodiments of the present application. For ease of description, the network management service producer entity is referred to as a producer entity, the network management service consumer entity is referred to as a consumer entity, and the network management intent is referred to as an intent.

[0124] S310, the producer entity determines that the execution of the first management action group fails to make the target of the network management intent be achieved in the range of the set of managed entities of the network management intent.

[0125] The set of managed entities contains at least two managed entities. The first management action group contains at least one action for managing the set of managed entities.

[0126] S320, the producer entity executes the first management action group or the second management action group to make the target of the network management intent be achieved in the range of the subset of managed entities.

[0127] The subset of managed entities is a subset of the set of managed entities. The second management action group contains at least one action for managing the subset of managed entities. That is, after the producer entity determines that the target of the network management intent in the range of the set of managed entities cannot be achieved, the producer entity can flexibly execute the first management action group or the second management action group based on the subset of managed entities, so as to make the target of the network management intent be achieved in the range of the subset of managed entities, instead of directly deleting or suspending the entire network management intent, thereby providing a flexible management manner of the network management intent.

[0128] It can be understood that the target of fulfilling the network management intention can also be described as satisfying the target of the network management intention, achieving the target of the network management intention, and the like.

[0129] In the embodiments of the present application, the network management intention can be various types of network management intentions. The type of the network management intention can be related to the target contained in the network management intention. Exemplarily, when the target contained in the network management intention is that the index value of the performance index reaches the corresponding index range, and the performance index is the throughput rate index, for example, the average downlink throughput rate is greater than or equal to 5 Mbps, the network management intention can be referred to as 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, the network management intention can be referred to as an energy saving intention. The type of the performance index is not particularly limited in the present application, for example, there can also be a coverage rate index, a time delay index, and the like.

[0130] The set of managed entities contains a plurality of managed entities. The types of at least two managed entities in the plurality of managed entities can be the same or different. Exemplarily, the plurality of managed entities can contain any one or more of a base station device, a router, a switch or a core network device. The subset of managed entities is a subset of the set of managed entities, that is, the subset of managed entities is part of the set of managed entities, and the subset of managed entities contains part of the plurality of managed entities contained in the set of managed entities. For example, the set of managed entities contains 10 base station devices, and the subset of managed entities contains 5 of the 10 base station devices. For another example, the set of managed entities contains 5 base station devices and 5 routers, and the subset of managed entities contains 5 routers. For yet another example, the set of managed entities contains 100 cells, and the subset of managed entities contains 50 cells. The present application does not particularly limit this.

[0131] The set of managed entities can be indicated by the object context. The description of the object context can be referred to the above introduction, which is not described herein. Exemplarily, the object context represents the area where the set of managed entities is located, for example, the object context contains the coverage area polygon or the tracking area code (TAC) corresponding to the coverage area of the area. Thus, the production entity can determine the set of managed entities based on the object context, for example, the production entity can determine that all base station devices in the area form the set of managed entities based on the object context. The type of the managed entity in the area (for example, a base station device) can be pre-configured or indicated by other information, which is not particularly limited in the present application.

[0132] The subset of managed entities can be determined in various ways. Illustratively, the consumer entity can determine the subset of managed entities based on historical data, which can include intent reports of historical runs of the network management intent. For example, the consumer entity can determine the subset of network management intents based on historical achievement of the goals of the network management intents, such as the consumer entity can determine the managed entities in the area with the lowest historical achievement rate of the goals as the subset of managed entities. Further illustratively, the consumer entity can also determine the subset of managed entities based on other information, such as user feedback information. For example, the consumer entity can obtain the user tolerance of unachieved goals, such as the consumer entity can determine the managed entities in the area with lower user tolerance of unachieved goals as the subset of managed entities, so as to improve the satisfaction of the network management intent service. The application does not particularly limit the way of determining the subset of managed entities, such as the subset of managed entities can also be determined based on the settings of the operator. Thus, the network management intent can be differentiated within the range of the set of managed entities, so as to improve the utilization of network resources.

[0133] It can be understood that the way of determining the subset of managed entities can be related to the type of network management intent, such as for the throughput intent, the consumer entity can determine the subset of managed entities of the throughput intent based on the user tolerance of unachieved goals; for the energy saving intent, the consumer entity can determine the subset of managed entities of the energy saving intent based on the historical intent report, which is not particularly limited by the application.

[0134] The producer entity can obtain the subset of managed entities in various ways. In some possible implementation manners, the producer entity can determine the subset of managed entities through the data structure of the network management intent (for example Figure 1The subset of managed entities is a constraint in the spatial dimension. That is, the subset of managed entities can be indicated by the object context. The object context can further contain constraints or conditions for determining the subset of managed entities (e.g., assuranceSubsetAttri can be defined), the network management intent contains the desired object, the desired object contains the object context, and the object context contains the spatial constraint. Exemplarily, the spatial constraint in the object context is: the TAC corresponding to region #1 and the TAC corresponding to region #2, region #1 is the region where the set of managed entities is located, region #2 is the region where the subset of managed entities is located, and region #1 contains region #2. Thus, the production entity can perform the first management action group or the second management action group based on the region where the subset of managed entities is located. In other possible implementation manners, the subset of managed entities can also be indicated by other information. For example, when the production entity determines that the execution of the first management action group fails to achieve the target of the network management intent within the set of managed entities of the network management intent, the production entity can send notification information to the consumer entity, so that the consumer entity can indicate the subset of managed entities to the production entity. For more details about how the production entity obtains the subset of managed entities, refer to the description of the first management action group and the second management action group below. Figure 4 and Figure 5 The above description is not repeated here.

[0135] In some embodiments, the production entity can further obtain information of a time period. For example, the production entity can obtain information indicative of a first time period and information indicative of a second time period, the first time period can be used to determine whether the execution of the first management action set fails to achieve the target of the network management intent in the scope of the set of managed entities, and the second time period can be used to execute the first management action set in combination with a second management action set to achieve the target of the network management intent in the scope of the subset of managed entities within the second time period. The second time period can be a subset of the first time period, for example, the first time period can be 24 hours of a day, and the second time period can be from 9 am to 6 pm of a day. In this case, the meaning that the execution of the first management action set fails to achieve the target of the network management intent in the scope of the set of managed entities of the network management intent can mean that the execution of the first management action set fails to achieve the target of the network management intent in the scope of the set of managed entities of the network management intent within the first time period. The meaning that the execution of the first management action set or the second management action set achieves the target of the network management intent in the scope of the subset of managed entities can mean that the execution of the first management action set or the second management action set achieves the target of the network management intent in the scope of the subset of managed entities within the second time period. For example, the set of managed entities of the throughput rate intent corresponds to region A, the first time period can be 24 hours of a day, the subset of managed entities corresponds to region B, and the second time period can be from 9 am to 6 pm of a day. If the production entity determines that the execution of the first management action set fails to achieve the throughput rate greater than or equal to 5 Mbps in the scope of region A within 24 hours of a day, the production entity can achieve the throughput rate greater than or equal to 5 Mbps in the scope of region B within from 9 am to 6 pm of a day by executing the first management action set or the second management action set. Thus, the production entity can consider the constraint in the time dimension when determining whether the target of the network management intent is achieved and executing the first management action set or the second management action set, so that the management of the network management intent is more flexible.

[0136] It can be understood that the production entity can obtain the information indicative of the first time period and the second time period in various manners. In some embodiments, the production entity can obtain the first time period and the second time period based on the network management intent, for example, the first time period and the second time period can be time constraints in the object context. For example, the subset of managed entities can be an object context, and the time constraint can be a constraint in the time dimension of the object context. Alternatively, the consumption entity can send the information indicative of the first time period and the second time period to the production entity through separate information. The present application does not particularly limit this.

[0137] The production entity can execute a first management action group based on the set of managed entities, the first management action group comprising at least one action for managing the set of managed entities. For example, the production entity can send instructions of the action group to a plurality of managed entities in the set of managed entities, and the managed entities execute the action group based on the instructions so that the network management intent is achieved in the set of managed entities. For example, the throughput rate intent comprises a target of an average downlink throughput rate greater than 5 Mbps, and the production entity sends instructions for adjusting the antenna tilt angle and reducing the number of symbols corresponding to the physical downlink control channel to a plurality of managed entities in the set of managed entities, and the plurality of managed entities execute the action group (such as the base station modifying the associated communication parameters) based on the instructions to achieve the target of the average downlink throughput rate greater than or equal to 5 Mbps. For another example, the energy saving intent comprises a target of energy saving greater than or equal to 10 kW, and the production entity can send instructions for turning on the energy saving switch to a plurality of managed entities in the set of managed entities, and the plurality of managed entities turn on the energy saving switch to achieve the target of energy saving greater than or equal to 10 kW. Wherein, turning on the energy saving switch can refer to turning on the carrier shutdown, symbol shutdown or radio frequency module hibernation, etc. The present application does not make special limitations thereto.

[0138] The production entity can determine that the execution of the first management action group fails to achieve the target of the network management intent in the set of managed entities in various ways. For example, the production entity can obtain a performance index value of the target of the network management intent, such as the throughput rate intent, and then obtain a throughput rate index value in the set of managed entities to determine whether the network management intent is achieved in the set of managed entities.

[0139] In some embodiments, the production entity can also determine the reason why the target of the network management intent is not achieved, such as the reason is that a conflict occurs. For example, the network management intent conflicts with other network management intents in the set of managed entities of the network management intent. The network management intent conflicts with other network management intents currently being executed means that the intent expectation target of the network management intent and the intent expectation target of other network management intents currently being executed cannot be satisfied simultaneously in the set of managed entities. In order to facilitate the understanding of the embodiments of the present application, the following exemplary describes several possible conflict situations of the network management intent and other network management intents currently being executed. In the first possible situation, the network management intent conflicts with other network management intents currently being executed in semantics. Exemplarily, the target of the energy saving intent includes that the physical resource block utilization is less than or equal to 20%, however, the target of the throughput rate intent currently being executed by the production entity includes that the physical resource block utilization is greater than 40%, then the production entity can determine that the network management intent conflicts with other network management intents in semantics. In the second possible situation, the production entity determines that the first set of management actions conflicts with the set of management actions of other network management intents currently being executed. For example, the production entity executes the energy saving intent and the throughput rate intent, since the production entity executes the management action (such as symbol off) for making the energy saving intent be achieved, the throughput rate is reduced, the target of the throughput rate intent cannot be achieved, at this time, the production entity can consider that the reason why the target of the throughput rate intent is not achieved is that the throughput rate intent conflicts with the energy saving intent. Thus, the production entity can also feed back the reason why the target of the network management intent is not achieved to the consumer entity, so as to improve the management manner of the network management intent.

[0140] In some embodiments, after the production entity determines that the execution of the first set of management actions fails to achieve the target of the network management intent in the set of managed entities, the production entity can determine whether to continue to execute or re-execute the first set of management actions to achieve the target of the network management intent in the subset of managed entities. For example, if the production entity determines that the execution of the first set of management actions achieves the target of the network management intent in the set of managed entities, the production entity can continue to execute the first set of management actions to maintain the execution of the network management intent based on the subset of managed entities, instead of suspending the execution of the network management intent. For another example, the production entity can acquire the relevant parameters of the network environment, such as the energy saving capability of the subset of managed entities, etc., the production entity can determine whether the execution of the first set of management actions can achieve the target of the network management intent in the subset of managed entities, if the production entity determines that it can be achieved, the production entity can re-execute the first set of management actions to achieve the target of the network management intent in the subset of managed entities.

[0141] In some other embodiments, the production entity can execute a second management action group to achieve the target of the network management intent in the subset of the set of managed entities after determining that the execution of the first management action group fails to achieve the target of the network management intent in the set of managed entities. That is, the production entity can determine and execute the second management action group, and the first management action group and the second management action group can contain one or more same actions, which are not particularly limited in the present application. For the convenience of understanding the embodiments of the present application, the following examples are mainly illustrated in the way that the production entity executes the second management action group.

[0142] The production entity can determine the second management action group in various ways. For example, the production entity can determine the network resources in the subset of the set of managed entities for achieving the target of the network management intent based on the subset of the set of managed entities, and execute the second management action group based on the network resources. For example, the production entity can obtain the communication resources available to the managed entities in the subset of the set of managed entities, and determine the second management action group based on the communication resources, and send the instructions of the action group to the managed entities in the subset of the set of managed entities based on the second management action group. For example, the production entity can send the instructions of closing the carrier shutdown, closing the symbol shutdown, closing the radio module sleep, or closing the radio channel shutdown to the managed entities in the subset of the set of managed entities. The action of closing the carrier shutdown can make more frequency domain resources available in the subset of the set of managed entities, the action of closing the symbol shutdown can make more time domain resources available in the subset of the set of managed entities, the action of closing the radio module sleep can make more frequency domain resources available in the subset of the set of managed entities, and the action of closing the radio channel shutdown can make more space domain resources available in the subset of the set of managed entities, thereby improving the throughput in the subset of the set of managed entities to make the throughput index value in the subset of the set of managed entities reach the corresponding throughput index range. When the subset of the set of managed entities also has an associated action time period, the production entity can determine the network resources available in the subset of the set of managed entities for achieving the target of the network management intent in the action time period, and determine and execute the second management action group based on the network resources. Thus, the present application provides a more flexible network management intent management method.

[0143] In some embodiments, the production entity can also obtain assurance strength information, and the production entity can determine the network resources in the subset of the managed entities that can be used to achieve the target of the network management intent based on the assurance strength information. For example, the assurance strength information can be information corresponding to other network management intents that the production entity is currently executing. For example, the production entity can maintain the execution of a throughput rate intent and a power saving intent at the same time, a first management action group is used to cause the target of the throughput rate intent to be achieved in the set of managed entities, and when the production entity determines that the execution of the first management action group fails to cause the target of the throughput rate intent to be achieved in the set of managed entities, the production entity can determine the network resources based on the subset of the managed entities of the throughput rate intent and the assurance strength information of the power saving intent. For example, when the assurance strength information indicates that the assurance strength of the power saving intent is high (or the assurance strength of the power saving intent is higher than the assurance strength of the throughput rate intent), the production entity cannot encroach on the network resources used to achieve the target of the power saving intent to cause the target of the throughput rate to be achieved. When the assurance strength information indicates that the assurance strength of the power saving intent is low (or the assurance strength of the power saving intent is lower than the assurance strength of the throughput rate intent), the production entity can encroach on the network resources used to achieve the target of the power saving intent to cause the target of the throughput rate to be achieved. For another example, the assurance strength information can be information of the network management intent in step S310, for example, the network management intent is a throughput rate intent, and when the assurance strength information indicates that the assurance strength of the throughput rate intent is high, the production entity can encroach on the network resources used to achieve other network management intents to guarantee the target of the throughput rate intent to be achieved. When the assurance strength information indicates that the assurance strength of the throughput rate intent is low, the production entity cannot encroach on the network resources used to achieve other network management intents. In the embodiments of the present application, the production entity executing a management action group that is not conducive to achieving the target of the network management intent can be considered as encroaching on the network resources of the network management intent. For example, the production entity executes carrier shutdown, which is not conducive to achieving the target of the throughput rate intent, and can be considered as encroaching on the network resources of the throughput rate intent. Thus, the production entity determines the second management action group based on the assurance strength information, which can improve the flexibility of network management intent management, and is conducive to improving the utilization efficiency of network resources and improving user satisfaction.

[0144] Thus, based on the technical solution, after the production entity determines that the target of the network management intent in the set of managed entities cannot be achieved, the production entity can flexibly execute the first management action or the second management action group based on the subset of the managed entities to cause the target of the network management intent to be achieved in the subset of the managed entities, instead of directly deleting or suspending the entire network management intent, thereby providing a flexible network management intent management manner.

[0145] The above describes the method that the production entity determines the execution of the first management action group fails to achieve the target of the network management intention in the range of the set of managed entities, and then executes the second management action group to achieve the target of the network management intention in the range of the subset of managed entities. In order to facilitate the understanding of the embodiments of the present application, the following describes the method in combination with Figure 4 and Figure 5 Two possible interaction modes of the consumption entity and the production entity are described.

[0146] Figure 4 is a schematic flowchart of an implementation mode of the network management intention provided by the embodiments of the present application.

[0147] S401, the consumption entity sends a request message to the production entity. Correspondingly, the production entity receives the request message from the consumption entity.

[0148] The request message contains the subset of managed entities. The description of the subset of managed entities can refer to the description in the above Figure 3 , which is not repeated here.

[0149] Exemplarily, the request message is used to request the production entity to create the network management intention, in other words, the request message can be an intention creation request message. The request message contains the network management intention, and the network management intention contains the set of managed entities, and the set of managed entities contains the subset of managed entities. For example, the intention creation request message can contain the data structure as shown in the above Figure 1 , and the network management intention can contain the set of managed objects. For example, the constraint or condition represented by the object context in the network management intention can be used to determine the set of managed objects and the subset of managed objects. Alternatively, the request message contains the network management intention and the subset of managed objects, in other words, the subset of managed objects can be indicated or determined by the information outside the data structure of the network management intention, which is not particularly limited by the present application. The more detailed description of the set of managed objects and the subset of managed objects can refer to the description in the above Figure 3 , which is not repeated here.

[0150] It can be understood that in some implementation modes, the request message is used to request the production entity to modify the network management intention, in other words, the request message can be an intention modification request message. The type of the request message is not particularly limited by the present application, for example, the request message can also be a network management intention activation request message, etc. In order to facilitate the understanding, the request message is exemplarily taken as the intention creation request message in the present text.

[0151] Optionally, S402, the production entity performs a feasibility check.

[0152] The production entity obtains the subset of managed entities in the request message, and determines whether the subset of managed entities exceeds the range of the set of managed entities. If the production entity determines that the subset of managed entities exceeds the range of the set of managed entities, for example, the geographic area corresponding to the subset of managed entities exceeds the geographic area corresponding to the set of managed entities, the production entity can feed back a message indicating that the subset of managed entities is incorrect to the consumer entity. If the production entity determines that the subset of managed entities does not exceed the range of the set of managed entities, the production entity can perform subsequent processes.

[0153] It can be understood that the production entity can also perform a feasibility check on the request message. For example, the production entity can detect whether the request message can be successfully interpreted, for example, whether the request message conforms to the syntax semantics of the network management intent. If the production entity detects that the request message can be successfully interpreted, the production entity can perform the first management action group based on the method described above. If the production entity detects that the request message cannot be successfully interpreted, for example, a syntax error, the production entity can send a feedback indicating the syntax error to the consumer entity.

[0154] Optionally, the production entity sends a response message to the consumer entity at S403. Accordingly, the consumer entity receives the response message from the production entity.

[0155] The production entity can send a response message to the consumer entity in response to the request message at S401. For example, when the request message is an intent creation request message, the response message can be an intent creation request response message.

[0156] If the production entity determines that the intent creation is not feasible at S402, for example, the subset of managed entities exceeds the range of the set of managed entities, or the request message does not conform to the syntax or semantics of the network management intent, the response message can be used to feed back that the intent creation is not feasible, or the response message can contain information indicating that the intent creation is not feasible. In some implementations, the response message can also contain failure reason information, which can indicate the reason for the failure of the intent creation (such as the subset of managed objects exceeding the range or the information expression error, etc.), which is not particularly limited in the present application.

[0157] It can be understood that if the production entity detects that the intent creation is feasible at S402, in other words, the production entity determines that the subset of managed entities is within the range of the set of managed entities, the response message can be used to feed back that the intent creation is feasible, or the response message contains information indicating that the intent creation is feasible. Alternatively, the production entity can not perform S403. The present application is not particularly limited in this regard.

[0158] It can also be understood that if the production entity determines that the creation of the intent is not feasible based on the request message and sends a response message to the consumption entity that the creation of the intent is not feasible, the consumption entity can adjust or regenerate the request message based on the response message. For example, if the consumption entity determines that the subset of managed entities exceeds the range of the set of managed entities based on the response message, the consumption entity can adjust the range of the subset of managed entities and resend the request message to the production entity that requests the creation of the network management intent or requests the modification of the network management intent. This process of the production entity feeding back the corresponding message and the consumption entity resending the request message can be repeated at least once until the production entity determines that the creation of the intent is feasible. For the sake of simplicity, the details are not described herein.

[0159] S404, the production entity executes the first management action group.

[0160] The production entity can execute the first management action group based on the set of managed entities, and the first management action group contains at least one action for managing the set of managed entities. For more detailed description of the production entity executing the first management action group, please refer to the description in the above Figure 3 , which will not be repeated here.

[0161] S405, the production entity determines that the execution of the first management action group fails to achieve the goal of the network management intent within the range of the set of managed entities.

[0162] For more detailed description of the production entity determining that the goal of the network management intent is not achieved within the range of the set of managed entities, please refer to the description in the above Figure 3 , which will not be repeated here.

[0163] S406, the production entity executes the second management action group to achieve the goal of the network management intent within the range of the subset of managed entities.

[0164] For more detailed description of the production entity executing the second management action group, please refer to the description in the above Figure 3 , which will not be repeated here. It can be understood that this step can also be the production entity executing the first management action group, and for more detailed description, please refer to the description in the above Figure 3 , which will not be repeated here.

[0165] Optionally, S407, the production entity sends an intent report to the consumption entity. Correspondingly, the consumption entity receives the intent report from the production entity.

[0166] The intention report can be used to indicate whether the target of the network management intention is achieved within the scope of the subset of managed entities. Illustratively, the intention report can contain an identifier indicating whether the target of the network management intention is achieved within the scope of the subset of managed entities. The intention report can also contain the indicator value of the performance indicator within the scope of the subset of managed entities. For example, the target of the network management intention contains the performance indicator of the throughput rate indicator, such as the target of the network management intention is that the average downlink throughput rate is greater than or equal to 5 Mbps, then the intention report can contain the throughput rate value within the scope of the subset of managed entities.

[0167] In some embodiments, the intention report can also contain the performance indicator within the scope of the set of managed entities except the indicator value of the performance indicator within the scope of the subset of managed entities. For example, the intention report can contain the throughput rate value within the scope of the set of managed entities except the scope of the subset of managed entities. Thus, the consuming entity can improve the management of the network management intention based on the overall achievement of the set of managed entities.

[0168] In some embodiments, the producing entity can periodically feed back the intention report to the consuming entity, or feed back the intention report based on the query of the consuming entity, which is not particularly limited in the present application.

[0169] Thus, based on the technical solution, after the producing entity determines that the target of the network management intention within the scope of the set of managed entities cannot be achieved, the producing entity can flexibly perform the first management action or the second management action group based on the subset of managed entities, so that the target of the network management intention is achieved within the scope of the subset of managed entities, instead of directly deleting or suspending the entire network management intention, thereby improving a flexible management manner of the network management intention.

[0170] The above Figure 4 A method of carrying the subset of managed entities in a request message is introduced. In the embodiments of the present application, the consuming entity can also occur the subset of managed entities to the producing entity after the producing entity determines that the target of the network management intention within the scope of the set of managed entities cannot be achieved. In order to facilitate the understanding of the embodiments of the present application, the following will be combined with the above Figure 5 The above

[0171] Figure 5 is a schematic flow chart of another implementation manner of the network management intention provided by the embodiments of the present application.

[0172] Optionally, S501, the consuming entity sends a request message to the producing entity. Correspondingly, the producing entity receives the request message from the consuming entity.

[0173] The request message can be used to request the producer entity to create a network management intent, in other words, the request message can be an intent creation request message. The request message contains the network management intent, which contains a set of managed entities. For example, the intent creation request message can contain a network management intent (e.g. the data structure shown in Figure 1 The network management intent can contain a set of managed objects, such as the constraints or conditions represented in the object context of the network management intent can be used to determine the set of managed objects.

[0174] Optionally, S502, the producer entity performs a feasibility check.

[0175] The producer entity can perform a feasibility check on the request message. Illustratively, the producer entity can detect whether the request message can be successfully interpreted, such as detecting whether the request message complies with the syntax semantics of the network management intent. If the producer entity detects that the request message can be successfully interpreted, the producer entity can perform the first set of management actions based on the methods described above. If the producer entity detects that the request message cannot be successfully interpreted, such as syntax error, the producer entity can send a feedback to the consumer entity indicating the syntax error.

[0176] Optionally, S503, the producer entity sends a response message to the consumer entity. Correspondingly, the consumer entity receives the response message from the producer entity.

[0177] The producer entity can send a response message to the consumer entity in response to the request message of S502. Illustratively, when the request message is an intent creation request message, the response message can be an intent creation request response message. The description of S503 can be referred to the description of S403 in Figure 4 , which is not repeated here.

[0178] S504, the producer entity performs the first set of management actions.

[0179] The producer entity can perform the first set of management actions based on the set of managed entities, which contains at least one action for managing the set of managed entities. The description of the producer entity performing the first set of management actions can be referred to the description in Figure 3 , which is not repeated here.

[0180] S505, the producer entity determines that the performance of the first set of management actions fails to achieve the goal of the network management intent within the set of managed entities.

[0181] The description of the producer entity determining that the goal of the network management intent is not achieved within the set of managed entities can be referred to the description in Figure 3The details are described in the foregoing description of the method, and are not repeated here.

[0182] S506, the production entity sends the notification information to the consumption entity. Correspondingly, the consumption entity receives the notification information from the production entity.

[0183] The notification information is used to indicate that the target of the network management intent fails to be achieved within the range of the set of managed entities. Illustratively, the notification information can indicate the achievement of the first management action group of the consumption entity on the target of the network management intent, for example, the notification information can contain the index value of the performance index within the range of the set of managed entities. For example, the target of the network management intent contains the performance index as the throughput index, such as the target of the network management intent is that the average downlink throughput rate is greater than or equal to 5Mbps, and then the notification information can contain the throughput value within the range of the set of managed entities.

[0184] S507, the consumption entity sends the subset of managed entities to the production entity. Correspondingly, the consumption entity receives the subset of managed entities from the consumption entity.

[0185] The consumption entity can determine the subset of managed entities based on the notification information. For example, the consumption entity can determine the subset of managed entities based on the achievement of the network management intent contained in the notification information. For another example, the consumption entity can determine the subset of managed entities based on the use scenario of the network management intent. The determination method of the subset of managed entities can refer to the description in the foregoing Figure 3

[0186] It can be understood that the consumption entity can directly send the subset of managed entities to the production entity, or the consumption entity can also regenerate the request message (such as the intent creation request message) and send the subset of managed entities in the request message to the production entity. That is, the consumption entity can update the expected object of the network management intent, and the object context contains the subset of managed entities. The consumption entity can send the updated network management intent (or the object context of the network management intent) to the production entity. The present application does not make special limitation thereto.

[0187] S508, the production entity executes the second management action group to achieve the target of the network management intent within the range of the subset of managed entities.

[0188] For more detailed description of the production entity executing the second management action group, refer to the description in the foregoing Figure 3 Figure 3

[0189] ​​​Optionally, S509, the production entity sends an intent report to the consumption entity. Correspondingly, the consumption entity receives the intent report from the production entity.

[0190] For more details about the intent report, refer to the description of step S407 in the above Figure 4 For more details about the intent report, refer to the description of step S407 in the above

[0191] Therefore, based on the technical solution, after the production entity determines that the target of the network management intent within the set of managed entities cannot be achieved, the production entity can flexibly perform the first management action or the second management action group based on the subset of managed entities, so that the target of the network management intent within the subset of managed entities is achieved, instead of directly deleting or suspending the entire network management intent, thereby improving a flexible network management intent management manner.

[0192] It can also be understood that the methods and operations implemented by the production entity in the above various method embodiments can also be implemented by components (such as chips or circuits) of the production entity, and in addition, the methods and operations implemented by the consumption entity can also be implemented by components (such as chips or circuits) of the consumption entity, without limitation.

[0193] Corresponding to the methods given in the above various method embodiments, the embodiments of the present application also provide corresponding devices, and the devices include modules for performing the corresponding modules of the above various method embodiments. The modules can be software, hardware, or a combination of software and hardware. It can be understood that the technical features described in the above various method embodiments are also applicable to the following device embodiments.

[0194] Referring to Figure 6 , as an example, Figure 6 is a schematic diagram of a communication device 10 provided by an embodiment of the present application. The device 10 includes a transceiver unit 11 and a processing unit 12. The transceiver unit 11 can be used to implement corresponding communication functions. The transceiver unit 11 can also be referred to as a communication interface or a communication unit. The processing unit 12 can be used for processing data or information.

[0195] Optionally, the device 10 further includes a storage unit, which can be used to store instructions and / or data. The processing unit 12 can read the instructions and / or data in the storage unit, so that the device implements the above various method embodiments.

[0196] In a possible design, the apparatus 10 can be configured to perform actions performed by the production entity in the method embodiments, and the apparatus 10 can be the production entity or a component of the production entity, the transceiver unit 11 can be configured to perform operations related to receiving and sending performed by the production entity in the method embodiments, and the processing unit 12 can be configured to perform operations related to processing performed by the production entity in the method embodiments.

[0197] In a first possible implementation, the processing unit 12 is configured to determine that execution of the first management action group fails to achieve the target of the network management intent in the range of the set of managed entities, the set of managed entities includes at least two managed entities, and the first management action group includes at least one action for managing the set of managed entities; and perform the first management action or a second management action group to achieve the target of the network management intent in the range of a subset of managed entities, the subset of managed entities is a subset of the set of managed entities, and the second management action group includes at least one action for managing the subset of managed entities. Optionally, the transceiver unit 11 is configured to receive the subset of managed entities.

[0198] The apparatus 10 can implement steps or procedures performed by the production entity in the method embodiments according to the embodiments of the present application, and the apparatus 10 can include units for performing the methods performed by the production entity in the method embodiments of the embodiments of the present application. The specific processes in which the units perform the corresponding steps are described in detail in the method embodiments, and are not described here for brevity.

[0199] In another possible design, the apparatus 10 can be configured to perform actions performed by the consumption entity in the method embodiments, and the apparatus 10 can be the consumption entity or a component of the consumption entity, the transceiver unit 11 can be configured to perform operations related to receiving and sending performed by the consumption entity in the method embodiments, and the processing unit 12 can be configured to perform operations related to processing performed by the consumption entity in the method embodiments.

[0200] In a first possible implementation, the processing unit 12 is configured to determine the subset of managed entities, the subset of managed entities is a subset of a set of managed entities of a network management intent, the set of managed entities includes at least two managed entities, and the subset of managed entities is used to perform a first management action or a second management action group to achieve the target of the network management intent in the range of the subset of managed entities when execution of the first management action group fails to achieve the target of the network management intent in the range of the set of managed entities, the first management action group includes at least one action for managing the set of managed entities, and the second management action group includes at least one action for managing the subset of managed entities; and the transceiver unit 11 is configured to receive the subset of managed entities.

[0201] The apparatus 10 can implement the steps or procedures performed by the consuming entity in the method embodiments according to the embodiments of the present application, and can include units for performing the methods implemented by the consuming entity in the method embodiments of the embodiments of the present application. The specific process of each unit performing the corresponding steps has been described in the above method embodiments, and will not be repeated here.

[0202] It can be understood that the apparatus 10 herein is embodied in the form of functional units. The term "unit" herein can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (for example, a shared processor, a dedicated processor, or a group processor, etc.) and a memory for executing at least one software or firmware program, a combination of logic circuitry and / or other suitable components that support the described functions. In an optional example, those skilled in the art can understand that the apparatus 10 can be embodied as the production entity in the above embodiments, and can be used to perform the procedures and / or steps corresponding to the production entity in the above method embodiments; or the apparatus 10 can be embodied as the consuming entity in the above embodiments, and can be used to perform the procedures and / or steps corresponding to the consuming entity in the above method embodiments. To avoid repetition, details are not repeated here.

[0203] The apparatus 10 of each of the above schemes has the function of implementing the corresponding steps performed by the communication device (for example, the production entity, or the consuming entity) in the above method. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes at least one module corresponding to the above function; for example, the transceiver unit can be replaced by a transceiver (for example, the transmitting unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor, which respectively performs the transceiving operation and the related processing operation in each method embodiment.

[0204] In addition, the transceiver unit 11 can also be a transceiver circuit (for example, which can include a receiving circuit and a transmitting circuit), and the processing unit can be a processing circuit.

[0205] It should be noted that, Figure 6 The apparatus in the above embodiments can be a device, or a chip or a chip system, for example, a system on chip (SoC). The transceiver unit can be an input / output circuit, a communication interface; and the processing unit can be a processor or a microprocessor integrated on the chip or an integrated circuit. Herein, no limitation is made.

[0206] Referring to Figure 7 , as an example, Figure 7is a schematic diagram of another communication apparatus 20 provided by an embodiment of the present application. The apparatus 20 comprises a processor 21 coupled with a memory 22. Optionally, the apparatus 20 further comprises the memory 22. The memory 22 is configured to store computer programs or instructions and / or data, and the processor 21 is configured to execute the computer programs or instructions stored in the memory 22, or read the data stored in the memory 22, to perform the methods in the above method embodiments.

[0207] Optionally, the processor 21 is at least one.

[0208] Optionally, the memory 22 is at least one.

[0209] Optionally, the memory 22 is integrated with the processor 21, or is separately arranged.

[0210] Optionally, as shown in the embodiment of Figure 7 the apparatus 20 further comprises a transceiver 23 configured to receive and / or send signals. For example, the processor 21 is configured to control the transceiver 23 to receive and / or send signals.

[0211] As a solution, the apparatus 20 is configured to implement the operations performed by the production entity in the above method embodiments.

[0212] For example, the processor 21 is configured to execute the computer programs or instructions stored in the memory 22, to implement the related operations of the production entity in the above method embodiments. For example, Figure 3 the method performed by the production entity in the embodiment of

[0213] As another solution, the apparatus 20 is configured to implement the operations performed by the consumption entity in the above method embodiments.

[0214] For example, the processor 21 is configured to execute the computer programs or instructions stored in the memory 22, to implement the related operations of the consumption entity in the above method embodiments. For example, Figure 3 the method performed by the consumption entity in the embodiment of

[0215] It can be appreciated that the processor mentioned in the embodiments of the present application can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0216] It can also be appreciated that the memory mentioned in the embodiments of the present application can be a volatile memory and / or a non-volatile memory. The non-volatile memory can be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically EPROM (EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM). For example, the RAM can be used as an external cache. By way of example and not limitation, the RAM includes the following forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synclink DRAM (SLDRAM) and direct rambus RAM (DR RAM).

[0217] When the processor is a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, the memory (storage module) can be integrated in the processor.

[0218] The memory described herein is intended to include, but not limited to, these and any other suitable types of memory.

[0219] Referring to Figure 8 , as an example, Figure 8 is a schematic diagram of a chip system 30. The chip system 30 (or also can be referred to as a processing system) includes a logic circuit 31 and an input / output interface 32.

[0220] 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 invoke 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, and output information processed by the chip system 30, or input data or signaling information to be processed by the chip system 30.

[0221] Specifically, for example, if the production entity installs the chip system 30, the logic circuit 31 is coupled to the input / output interface 32, and the input / output interface 32 can input a wake-up signal to the logic circuit 31 for processing.

[0222] As one solution, the chip system 30 is used to implement the operations performed by the production entity in the above various method embodiments.

[0223] For example, the logic circuit 31 is used to implement the processing-related operations performed by the production entity in the above method embodiments, such as, Figure 3 the processing-related operations performed by the production entity in the embodiments shown in the above method embodiments; and the input / output interface 32 is used to implement the sending and / or receiving-related operations performed by the production entity in the above method embodiments, such as, Figure 3 the sending and / or receiving-related operations performed by the production entity in the embodiments shown in the above method embodiments.

[0224] As another solution, the chip system 30 is used to implement the operations performed by the consumption entity in the above various method embodiments.

[0225] For example, the logic circuit 31 is used to implement the processing-related operations performed by the consumption entity in the above method embodiments, such as, Figure 3 the processing-related operations performed by the consumption entity in the embodiments shown in the above method embodiments; and the input / output interface 32 is used to implement the sending and / or receiving-related operations performed by the consumption entity in the above method embodiments, such as, Figure 3 the sending and / or receiving-related operations performed by the consumption entity in the embodiments shown in the above method embodiments.

[0226] The embodiments of the present application also provide a computer readable storage medium, which stores computer instructions for implementing the methods performed by the devices in the above various method embodiments.

[0227] For example, the computer program, when executed by a computer, enables the computer to implement the method performed by the production entity in each of the above-mentioned method embodiments.

[0228] For another example, the computer program, when executed by a computer, enables the computer to implement the method performed by the consumption entity in each of the above-mentioned method embodiments.

[0229] The embodiments of the present application further provide a computer program product comprising instructions which, when executed by a computer, implement the method performed by the production entity or the consumption entity in each of the above-mentioned method embodiments.

[0230] The embodiments of the present application further provide a communication system comprising the production entity and the consumption entity in each of the above-mentioned embodiments.

[0231] The explanations and beneficial effects of the related contents in any of the above-mentioned apparatuses can refer to the corresponding method embodiments provided above, and will not be repeated here.

[0232] In several embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented by other manners. For example, the apparatus embodiments described above are only illustrative, for example, the division of the units is only a logical function division, and in actual implementation, there can be another division manner, for example, at least two units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units or components shown or discussed can be indirect coupling or communication connection through some interfaces, apparatuses or units, and can be electrical, mechanical or other forms.

[0233] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes at least one computer instruction. When the computer program instruction is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable apparatus. For example, the computer can be a personal computer, a server, a network device or the like. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) manner. The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. integrated with at least one available medium. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD) and the like. For example, the foregoing available medium includes but is not limited to: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and various media that can store program codes.

[0234] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for managing network management intent, characterized in that, The method includes: It is determined that the execution of the first management action group failed to achieve the objective of the network management intent within the scope of the set of managed entities of the network management intent, wherein the set of managed entities contains at least two managed entities, and the first management action group contains at least one action for managing the set of managed entities. The first management action group or the second management action group is executed to achieve the objective of the network management intent within a subset of managed entities, wherein the subset of managed entities is a subset of the set of managed entities, and the second management action group includes at least one action for managing the subset of managed entities.

2. The method as described in claim 1, characterized in that, The method further includes: A request message is received, which is used to request the creation of the network management intent or to request the modification of the network management intent. The request message includes the network management intent, which includes the subset of managed entities, or the request message includes both the network management intent and the subset of managed entities.

3. The method as described in claim 1 or 2, characterized in that, The object context in the network management intent contains information for identifying the set of managed entities and / or the subset of managed entities.

4. The method as described in claim 1, characterized in that, After determining that the execution of the first management action group failed to achieve the objective of the network management intent within the set of managed entities of the network management intent, the method further includes: Send a notification message indicating that the objective of the network management intent within the set of managed entities has not been achieved; The managed subset of entities that receive the notification information.

5. The method as described in claim 1 or 2, characterized in that: The failure of the execution of the first management action group to achieve the goal of the network management intention within the scope of the set of managed entities of the network management intention means that the execution of the first management action group failed to achieve the goal of the network management intention within the first time period within the scope of the set of managed entities of the network management intention. The execution of the first management action group or the second management action group to achieve the goal of the network management intention within the subset of managed entities means: executing the first management action group or the second management action group to achieve the goal of the network management intention within a second time period within the subset of managed entities, wherein the second time period is a subset of the first time period.

6. The method as described in claim 1 or 2, characterized in that, The execution of the first management action group or the second management action group includes: Based on the subset of managed entities, determine the network resources within the scope of the managed entity subset that can be used to achieve the network management intent; Execute the first management action group or the second management action group based on the network resources.

7. The method as described in claim 1 or 2, characterized in that, The method further includes: The reason why the execution of the first management action group failed to achieve the goal of the network management intent within the scope of the managed entity set was determined to be due to an intent conflict.

8. The method as described in claim 1 or 2, characterized in that, The method further includes: Send an intent report, which includes the achievement status of the network management intent objectives within the subset of managed entities.

9. The method as described in claim 8, characterized in that, The intent report also includes the achievement of the network management intent's objectives within the set of managed entities, excluding the subset of managed entities.

10. A method for managing network management intent, characterized in that, The method includes: A subset of managed entities is determined, wherein the subset of managed entities is a subset of the set of managed entities for a network management intent, wherein the set of managed entities contains at least two managed entities, and the subset of managed entities is used to execute either the first management action group or the second management action group when the execution of the first management action group fails to achieve the goal of the network management intent within the set of managed entities, so that the goal of the network management intent is achieved within the scope of the subset of managed entities, wherein the first management action group contains at least one action for managing the set of managed entities, and the second action group contains at least one action for managing the subset of managed entities; Send the managed subset of entities.

11. The method as described in claim 10, characterized in that, The sending of the managed entity subset includes: Send a request message, the request message being used to request the creation of the network management intent or to request the modification of the network management intent, the request message including the network management intent, the network management intent including the subset of managed entities, or the request message including the network management intent and the subset of managed entities.

12. The method as described in claim 10 or 11, characterized in that, The object context in the network management intent contains information for identifying the set of managed entities and / or the subset of managed entities.

13. The method as described in claim 12, characterized in that, The method further includes: Receive a notification message indicating that the objective of the network management intent within the set of managed entities has not been achieved; The sending of the managed entity subset includes: The managed subset of entities that send a response to the notification information.

14. The method as described in claim 10 or 11, characterized in that, The reason why the execution of the first management action group failed to achieve the goal of the network management intent within the set of managed entities is that an intent conflict occurred.

15. The method as described in claim 10 or 11, characterized in that, The method further includes: Receive an intent report, which includes the achievement status of the network management intent objectives within the subset of the managed entities.

16. The method as described in claim 15, characterized in that, The intent report also includes the achievement of the network management intent's objectives within the set of managed entities, excluding the subset of managed entities.

17. A method for managing network management intent, characterized in that, The method includes: Send a subset of the managed entities; Receive the managed entity subset; It is determined that the execution of the first management action group failed to achieve the objective of the network management intent within the scope of the set of managed entities of the network management intent, wherein the set of managed entities contains at least two managed entities, and the first management action group contains at least one action for managing the set of managed entities. The first management action group or the second management action group is executed to achieve the objective of the network management intent within a subset of managed entities, wherein the subset of managed entities is a subset of the set of managed entities, and the second management action group includes at least one action for managing the subset of managed entities.

18. A management device for network management intent, characterized in that, The device includes a determining unit and an executing unit, wherein... The determining unit is configured to determine that the execution of the first management action group failed to achieve the goal of the network management intention within the scope of the managed entity set of the network management intention, wherein the managed entity set includes at least two managed entities, and the first management action group includes at least one action for managing the managed entity set. The execution unit is configured to execute the first management action group or the second management action group to achieve the goal of the network management intent within a subset of managed entities, wherein the subset of managed entities is a subset of the set of managed entities, and the second management action group includes at least one action for managing the subset of managed entities.

19. A management device for network management intent, characterized in that, The device includes a transceiver unit and a processing unit, wherein... The processing unit is configured to determine a subset of managed entities, wherein the subset of managed entities is a subset of the set of managed entities for a network management intent, wherein the set of managed entities contains at least two managed entities, and the subset of managed entities is configured to determine a second set of management actions when the execution of a first set of management actions fails to achieve the goal of the network management intent within the set of managed entities, so that the goal of the network management intent is achieved within the subset of managed entities, wherein the first set of management actions contains at least one action for managing the set of managed entities, and the second set of management actions contains at least one action for managing the subset of managed entities; The transceiver unit is used to send the managed entity subset.

20. A communication device, characterized in that, It includes a unit for performing the method as described in any one of claims 1 to 9, or includes a unit for performing the method as described in any one of claims 10 to 16.

21. A communication system, characterized in that, It includes means for performing the method as described in any one of claims 1 to 9 and means for performing the method as described in any one of claims 10 to 16.

22. The system as claimed in claim 21, characterized in that, It also includes the managed entities with network management intent.

23. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1 to 9, or causes the computer to perform the method as described in any one of claims 10 to 16.

24. A computer program product, characterized in that, It includes computer program code that, when run on a computer, causes the computer to implement the method as described in any one of claims 1 to 9 or causes the computer to implement the method as described in any one of claims 10 to 16.

25. A communication device, characterized in that, include: A processor is configured to execute a computer program stored in a memory to cause the apparatus to perform the method as claimed in any one of claims 1 to 9, or to execute a computer program stored in a memory to cause the apparatus to perform the method as claimed in any one of claims 10 to 16.

26. The apparatus as claimed in claim 25, characterized in that, The device also includes the memory.

Citation Information

Patent Citations

  • Intent processing method, apparatus and system

    WO2020164490A1

  • Method and apparatus for executing intent

    WO2021093782A1

Cited By

  • Method and apparatus for managing network management intent, and system

    EP4730731A1

  • Method and apparatus for managing network management intent, and system

    WO2025030789A1