Method and apparatus for managing network management intent, and system

Abstract

Provided in the present application are a method and apparatus for managing a network management intent, and a system. The method comprises: determining that the execution of first management actions fail to make the goal of a network management intent be fulfilled within the range of a set of managed entities of the network management intent, wherein the set of managed entities includes at least two managed entities, and the first management actions include at least one action used for managing the set of managed entities; and executing the first management actions or second management actions, so as to make the goal of the network management intent be fulfilled within the 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 actions include at least one action used for managing the subset of managed entities. Therefore, a flexible way of managing a network management intent is provided.

Description

A method, device and system for managing network management intention

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

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

[0003] With the advancement of network resource management, network management service consumers no longer need to directly manage network resources. Instead, they can send network management intents to network management service producers. These producers then execute the intents, aiming to achieve the desired performance targets for network devices within a specific scope. Current approaches to managing network management intents are inflexible. For example, if the network environment for a network management intent is complex and volatile, and the network management service producer determines that the intent's goals have not been achieved, it will delete or suspend the intent and then issue a new one. If the new intent again fails to be achieved, it will delete or suspend the new one again, and this cycle will repeat.

[0004] Therefore, how to improve the flexibility of network management intentions is a technical problem that needs to be solved urgently.

[0005] Summary of the Invention

[0006] The present application provides a method, device and system for managing network management service intentions, providing a flexible way to manage network management intentions.

[0007] In a first aspect, a method for managing network management intentions is provided, which can be executed by a network management service production entity or a chip in a network management service production entity, the method comprising: determining that the execution of a first management action group fails to achieve the goal of the network management intention within the scope of a 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; executing the first management action group or the second management action group to achieve the goal of the network management intention within the scope of a managed entity subset, 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.

[0008] Based on this technical solution, after the production entity determines that the goal of the network management intention within the scope of the managed entity set cannot be achieved, it can flexibly execute the first management action or the second management action group based on the managed entity subset to achieve the goal of the network management intention within the scope of the managed entity subset, instead of directly deleting or suspending the entire network management intention, providing a flexible way to manage network management intentions.

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

[0010] In combination with the first aspect, in certain implementations of the first aspect, the method also includes: receiving a request message, the request message is used to request the creation of a network management intention or the modification of a network management intention, the request message includes the network management intention, the network management intention includes a subset of managed entities, or the request message includes the network management intention and a subset of managed entities.

[0011] Based on this technical solution, the consumer entity can carry the managed entity subset in the request message used to request the producer entity to create a network management intention, thereby reducing the signaling interaction between the consumer entity and the producer entity and saving transmission resources.

[0012] In combination with the first aspect, in some implementations of the first aspect, the object context in the network management intent includes information for determining a managed entity set and / or a managed entity subset.

[0013] In combination with the first aspect, in certain implementations of the first aspect, after determining that the execution of the first management action group fails to achieve the goal of the network management intention within the scope of the set of managed entities of the network management intention, the method also includes: sending a notification message indicating that the goal of the network management intention has failed to be achieved within the scope of the set of managed entities; and receiving a subset of managed entities in response to the notification message.

[0014] Based on this technical solution, the consuming entity can send a subset of managed entities to the producing entity in response to the notification information. That is, the consuming entity can produce a subset of managed entities based on the notification information, making the management method of network management intention more flexible.

[0015] In combination with the first aspect, in certain implementations of the first aspect, the execution of the first management action group fails to achieve the goal of the network management intention within the scope of the set of managed entities of the network management intention, which means: the execution of the first management action group fails to achieve the goal of the network management intention within the scope of the set of managed entities of the network management intention within the first time period; then executing the first management action group or the second management action group to achieve the goal of the network management intention within the scope of 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 the scope of the subset of managed entities within the second time period, wherein the second time period is a subset of the first time period.

[0016] Based on this technical solution, the production entity can also consider the constraints in the time dimension when determining whether the goals of the network management intention are achieved and executing the first management action group or the second management action group, making the management method of the network management intention more flexible.

[0017] Exemplarily, the goal of the network management intention includes that the indicator value of the performance indicator reaches a corresponding performance indicator range, wherein the performance indicator is an energy saving indicator or a throughput indicator.

[0018] In combination with the first aspect, in certain implementations of the first aspect, executing the first management action group or the second management action group includes: determining, based on the managed entity subset, network resources within the managed entity subset that can be used to achieve the goals of network management intentions; and executing the first management action group or the second management action group based on the network resources.

[0019] Based on this 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, which can improve the reliability of the management of network management intentions.

[0020] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: determining that the reason why the execution of the first management action group fails to achieve the goal of the network management intention within the scope of the managed entity set is that an intention conflict occurs.

[0021] Based on this technical solution, in the scenario of an intent conflict, the production entity may not directly delete or suspend the entire network management intent, but may execute the first management action group or the second management action group to achieve the goal of the network management intent within the scope of the managed entity subset, providing flexibility in network management intent management.

[0022] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: sending an intent report, where the intent report includes a status of achievement of a target of the network management intent within the scope of the managed entity subset.

[0023] Based on this technical solution, the consumer entity can learn about the execution status of the network management intention and can better manage the network management intention.

[0024] In combination with the first aspect, in some implementations of the first aspect, the intent report further includes a status of achievement of a target of the network management intent within the scope of the managed entity set excluding the scope of the managed entity subset.

[0025] Based on this technical solution, the consuming entity can improve the management method of the network management intention based on the overall achievement of the managed entity set.

[0026] In a second aspect, a method for managing network management intent is provided, which can be executed by a network management service production entity or a chip in the network management service production entity, the method comprising: determining a subset of managed entities, the managed subset being a subset of a set of managed entities of the network management intent, wherein the set of managed entities contains at least two managed entities, the managed entity subset is used to determine a second management action group when the execution of a first management action group fails to achieve the goal of the network management intent within the set of managed entities, so as to achieve the goal of the network management intent within the scope of the managed entity subset, wherein the first management action group contains at least one action for managing the set of managed entities, and the second management action group contains at least one action for managing the subset of managed entities; sending the subset of managed entities.

[0027] Regarding the beneficial technical effects of various implementation methods of the second aspect, please refer to the description of the relevant implementation methods of the first aspect and will not be repeated here.

[0028] In combination with the second aspect, in certain implementations of the second aspect, sending a subset of managed entities includes: sending a request message, the request message is used to request the creation of a network management intention or request the modification of a network management intention, the request message includes the network management intention, the network management intention includes the subset of managed entities, or the request message includes the network management intention and the subset of managed entities.

[0029] In conjunction with the second aspect, in certain implementations of the second aspect, the object context in the network management intent includes information for determining a managed entity set and / or a managed entity subset.

[0030] In combination with the second aspect, in certain implementations of the second aspect, the method also includes: receiving notification information, the notification information indicating that the goal of the network management intention within the scope of the managed entity set has not been achieved; sending a subset of managed entities, including: sending a subset of managed entities in response to the notification information.

[0031] Exemplarily, the goal of the network management intention includes that the indicator value of the performance indicator reaches a corresponding performance indicator range, wherein the performance indicator is an energy saving indicator or a throughput indicator.

[0032] In combination with the second aspect, in certain implementations of the second aspect, the reason why the execution of the first management action group fails to achieve the target of the network management intention within the scope of the managed entity set is that an intention conflict occurs.

[0033] In combination with the second aspect, in some implementations of the second aspect, the method further includes: receiving an intent report, where the intent report includes a status of achievement of a target of the network management intent within the scope of the managed entity subset.

[0034] In conjunction with the second aspect, in certain implementations of the second aspect, the intent report further includes a status of achievement of a target of the network management intent within the scope of the managed entity set excluding the scope of the managed entity subset.

[0035] On the third aspect, a method for configuring a network management intention is provided, the method comprising: sending a subset of managed entities; receiving a subset of managed entities; determining that the execution of a first management action group fails 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; executing the first management action group or the second management action group to achieve the goal of the network management intention within the scope of the managed entity subset, 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.

[0036] Regarding the beneficial technical effects of various implementation methods of the third aspect, please refer to the description of the relevant implementation methods of the first aspect and will not be repeated here.

[0037] In combination with the third aspect, in certain implementations of the third aspect, a request message is sent, the request message is used to request the creation of a network management intention or the modification of a network management intention, the request message includes the network management intention, the network management intention includes a subset of managed entities, or the request message includes the network management intention and a subset of managed entities; and the request message is received.

[0038] In conjunction with the third aspect, in certain implementations of the third aspect, the object context in the network management intent includes information for determining a managed entity set and / or a managed entity subset.

[0039] In combination with the third aspect, in certain implementations of the third aspect, after determining that the execution of the first management action group fails to achieve the goal of the network management intention within the scope of the set of managed entities of the network management intention, the method also includes: sending a notification message indicating that the goal of the network management intention has failed to be achieved within the scope of the set of managed entities; receiving the notification message; and receiving a subset of managed entities in response to the notification message.

[0040] In combination with the third aspect, in certain implementations of the third aspect, the execution of the first management action group fails to achieve the goal of the network management intention within the scope of the set of managed entities of the network management intention, which means: the execution of the first management action group fails to achieve the goal of the network management intention within the scope of the set of managed entities of the network management intention within the first time period; then executing the first management action group or the second management action group to achieve the goal of the network management intention within the scope of 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 the scope of the subset of managed entities within the second time period, wherein the second time period is a subset of the first time period.

[0041] Exemplarily, the goal of the network management intention includes that the indicator value of the performance indicator reaches a corresponding performance indicator range, wherein the performance indicator is an energy saving indicator or a throughput indicator.

[0042] In combination with the third aspect, in certain implementations of the third aspect, executing the first management action group or the second management action group includes: determining, based on the managed entity subset, network resources within the managed entity subset that can be used to achieve the goals of network management intentions; and executing the first management action group or the second management action group based on the network resources.

[0043] In combination with the third aspect, in certain implementations of the third aspect, it is determined that the reason why the execution of the first management action group fails to achieve the target of the network management intention within the scope of the managed entity set is that an intention conflict occurs.

[0044] In combination with the third aspect, in certain implementations of the third aspect, the method further includes: sending an intent report, the intent report including the achievement of the target of the network management intent within the scope of the managed entity subset; and receiving the intent report.

[0045] In combination with the third aspect, in certain implementations of the third aspect, the intent report further includes a status of achievement of a target of the network management intent within the scope of the managed entity set excluding the scope of the managed entity subset.

[0046] In a fourth aspect, a management device for network management intention is provided, which includes a determination unit and an execution unit, wherein the determination unit is used to determine that the execution of the first management action group fails 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 used to execute the first management action group or the second management action group to achieve the goal of the network management intention within the scope of the managed entity subset, 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.

[0047] The determining unit and the executing unit may be units in the processing unit.

[0048] Regarding the various implementation methods of the fourth aspect and the beneficial technical effects of various implementation methods, please refer to the description of the relevant implementation methods of the first aspect and will not be repeated here.

[0049] In a fifth aspect, a management device for network management intention is provided, which includes a transceiver unit and a processing unit, wherein the processing unit is used to determine a subset of managed entities, the managed subset being a subset of the managed entity set of the network management intention, wherein the managed entity set contains at least two managed entities, and the managed entity subset is used to determine a second management action group when the execution of the first management action group fails to achieve the goal of the network management intention within the managed entity set, so as to achieve the goal of the network management intention within the scope of the managed entity subset, wherein the first management action group contains at least one action for managing the managed entity set, and the second management action group contains at least one action for managing the managed entity subset; the transceiver unit is used to send the managed entity subset.

[0050] Regarding the various implementation methods of the fifth aspect and the beneficial technical effects of the various implementation methods, please refer to the description of the relevant implementation methods of the first and second aspects and will not be repeated here.

[0051] In a sixth aspect, a communication device is provided, wherein the communication device is capable of implementing 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 includes one or more units corresponding to the above functions.

[0052] In a seventh aspect, a communication device is provided, comprising a processor and a memory. Optionally, the device may further comprise a transceiver. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory, and control the transceiver to transmit and receive signals, so that the communication device performs the method according to the first aspect, or any possible implementation of any aspect of the first aspect.

[0053] Exemplarily, the communication device is a network management service production entity.

[0054] In an eighth aspect, a communication device is provided, comprising a processor and a memory. Optionally, the device may further comprise a transceiver. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory and control the transceiver to transmit and receive signals, so that the communication device performs the method according to the second aspect, or any possible implementation of any aspect of the second aspect.

[0055] Exemplarily, the communication device is a network management service consumption entity.

[0056] In a ninth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is configured to receive data and / or information and transmit the received data and / or information to the processor, and the processor processes the data and / or information. The communication interface is further configured to output the processed data and / or information, so that the method according to the first aspect, or any possible implementation of any aspect of the first aspect, is executed. The communication device may be a chip used in a network management service production network element.

[0057] In a tenth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is configured to receive data and / or information and transmit the received data and / or information to the processor, and the processor processes the data and / or information. The communication interface is further configured to output the processed data and / or information, so that the method according to the second aspect, or any possible implementation of any aspect of the second aspect, is executed. The communication device may be a chip used in a network management service consumption network element.

[0058] In the eleventh aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions. When the computer instructions are executed on a computer, the method in the first aspect, or any possible implementation of any aspect in the first aspect, is executed.

[0059] In the twelfth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions. When the computer instructions are executed on a computer, the method in the second aspect, or any possible implementation of any aspect in the second aspect, is executed.

[0060] In a thirteenth aspect, a computer program product is provided, comprising a computer program code, which, when run on a computer, enables the method according to the first aspect, or any possible implementation of any aspect in the first aspect, to be executed.

[0061] In a fourteenth aspect, a computer program product is provided, comprising a computer program code, which, when run on a computer, enables the method according to the second aspect, or any possible implementation of any aspect in the second aspect, to be executed.

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

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

[0064] FIG1 is a schematic diagram of a data structure of a network management intention;

[0065] FIG2 is a schematic architecture diagram of a communication system provided in an embodiment of the present application;

[0066] FIG3 is a schematic flow chart of a method for managing network management intent provided in an embodiment of the present application;

[0067] FIG4 is a schematic flow chart of a method for implementing a network management intention provided in an embodiment of the present application;

[0068] FIG5 is a schematic flow chart of another implementation method of network management intention provided in an embodiment of the present application;

[0069] 6 to 8 are schematic diagrams of possible communication devices provided in embodiments of the present application. DETAILED DESCRIPTION

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

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

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

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

[0074] 1.1 Network Management

[0075] Network management refers to the management of network resources, including but not limited to monitoring, controlling and recording the performance and usage of network resources, and issuing management action groups to network resources (such as devices in the network) based on the detected network conditions to enable the network to operate effectively. For example, network management can be monitoring, testing, configuring, analyzing, evaluating and controlling network resources. Network management can also be timely reporting and handling when a network failure occurs, and coordinating and maintaining the efficient operation of the network system. Among them, network resources are the objects of network management, which can also be called network objects or managed entities. For example, network resources can be base station equipment, routers, switches, core network equipment, etc. In this regard, the embodiments of the present application do not make special limitations. For the convenience of description, the embodiments of the present application are explained using managed entities as an example, but they can be replaced with other objects of network management.

[0076] 1.2 Network Management Services

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

[0078] 1.3 Network Management Service Production Entity

[0079] The entity providing the network management service is referred to as the network management service production entity. For example, the capabilities or functions of the network management service production entity may be deployed on a network element, referred to as the network management service production network element. The capabilities or functions of the network management service production entity may also be deployed on other devices, which is not limited in the embodiments of this application. For ease of description, the embodiments of this application use the network management service production entity as an example, but any other device that deploys the capabilities or functions of the network management service production entity may be substituted.

[0080] 1.4 Network Management Service Consumption Entities

[0081] The entity that calls network management is called a network management service consuming entity. For example, the capabilities or functions of the network management service consuming entity can be deployed on a certain network element, which is called a network management service consuming network element. The capabilities or functions of the network management service consuming entity can also be deployed on other devices, which is not limited in this embodiment of the present application. For ease of description, this embodiment of the present application uses the network management service consuming entity as an example, but any other device that deploys the capabilities or functions of the network management service consuming entity can be replaced.

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

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

[0084] In the intent-based interaction scenario of this application, there are two main roles: the network management provider entity and the network management service consumer entity. Among them, the network management provider entity can also be called the network management provider, or the intent provider (intent provider), or the intent handler (intent handler), etc. The network management service consumer entity can also be called the network management service consumer, or the intent consumer (intent consumer), or the intent owner (intent owner), etc.

[0085] Among them, the network management service consumption entity can be the caller of the network management service, and can perform operations such as creating, modifying, deleting, and querying network management intent expressions. It can be configured in a network management system (NMS), an element management system (EMS), or network equipment (NE). It can be a management function, a management function entity, a management entity, a network equipment, a network element, etc. This application does not limit this.

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

[0087] An intent may include at least one intent expectation. Each intent expectation may represent the performance requirements of a network management service consuming entity for a specific network object. An intent expectation may consist of at least one expected target and an expected object, each expected target representing the performance requirements of the network management service consuming entity for a specific attribute of the expected object. For example, an intent expectation may include two expected targets, one of which is an average downlink throughput greater than 5 Mbps and the other is an end-to-end delay less than 10 milliseconds. If the average downlink throughput of the expected object is greater than 5 Mbps, then the expected target for downlink throughput is met. If the end-to-end delay of the expected object is less than 10 milliseconds, then the expected target for delay is met. If both expected targets of an intent expectation are met, then the intent expectation is achieved. If one or more intent expectations are not met, or one or more expected targets are not met, then the intent is not met, or described as not being fulfilled or not being realized.

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

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

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

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

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

[0093] The information element in the intent IOC can use a specific structure to express the demand for network management services. For example, Figure 1 shows a schematic structural diagram of an intent IOC.

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

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

[0096] 3. Network Management Intent Template

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

[0098] 4. Intent Expression

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

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

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

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

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

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

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

[0106] 5. Intent Examples

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

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

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

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

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

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

[0113] The above describes the relevant terms involved in the embodiments of the present application. The following describes the application scenarios applicable to the embodiments of the present application in conjunction with Figure 1.

[0114] The above describes the relevant terms involved in the embodiments of the present application. The following describes the application scenarios applicable to the embodiments of the present application in conjunction with Figure 1.

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

[0116] 1. Network Management Service Consuming Entity 210: This entity can be used to invoke management services, or intent services, to manage the network system. For example, the network management service consuming entity 210 can instantiate an intent template, set intent IOCs, generate an intent expression, and send the intent expression to the network management service producing network element 220 to implement expectations for the network system.

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

[0118] 2. Network management service production entity 220: can be used to provide management services. For example, the network management service production entity 220 can receive intent expressions from the network management service consumption entity 210 and perform intent translation, intent management, and intent execution and maintenance processes based on the intent expressions.

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

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

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

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

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

[0124] With the advancement of network resource management, network management service consumers no longer need to directly manage network resources. Instead, they can send messages to network management service producers, enabling them to execute network management intents, aiming to achieve the desired performance targets for specific network devices within a specific scope. Currently, the application environments for network management intents are often complex and ever-changing. Therefore, managing network management intents within these complex and ever-changing environments is a pressing technical challenge.

[0125] Figure 3 is a schematic flow chart of a method for managing network management intent provided by an embodiment of the present application. For ease of description, the network management service production entity is referred to as the production entity, the network management service consumption entity is referred to as the consumption entity, and the network management intent is referred to as the intent.

[0126] S310: The production entity determines that execution of the first management action group fails to achieve the target of the network management intention within the scope of the managed entity set of the network management intention.

[0127] The managed entity set includes at least two managed entities. The first management action group includes at least one action for managing the managed entity set.

[0128] S320: The production entity executes the first management action group or the second management action group to achieve the target of network management intention within the scope of the managed entity subset.

[0129] The managed entity subset is a subset of the managed entity set. The second management action group includes at least one action for managing the managed entity subset. In other words, after the production entity determines that the target of the network management intent within the managed entity set cannot be achieved, it can flexibly execute the first management action group or the second management action group based on the managed entity subset to achieve the target of the network management intent within the managed entity subset, rather than directly deleting or suspending the entire network management intent, providing a flexible way to manage network management intent.

[0130] It is understandable that the goal of fulfilling the network management intention can also be described as the goal of satisfying the network management intention, the goal of realizing the network management intention, etc.

[0131] In the embodiments of the present application, the network management intent may be various types of network management intent. The type of network management intent may be related to the target included in the network management intent. For example, the target of the network management intent includes the indicator value of the performance indicator reaching the corresponding energy indicator range. When the performance indicator is a throughput indicator, such as the average downlink throughput is greater than or equal to 5Mbps, the network management intent can be called a throughput intention; when the performance indicator is an energy-saving indicator, such as energy saving is greater than or equal to 10 kilowatts, the network management intention can be called an energy-saving intention. The present application specifically limits the types of performance indicators, for example, there may also be coverage indicators, latency indicators, etc.

[0132] The managed entity set includes multiple managed entities. The types of at least two managed entities among the multiple managed entities may be the same, or may be different. Exemplarily, the multiple managed entities may include any one or more of base station devices, routers, switches, or core network devices. The managed entity subset is a subset of the managed entity set, that is, the managed entity subset is part of the managed entities, and the managed entity subset includes part of the managed entities among the multiple managed entities included in the managed entity set. For example, the managed entity set includes 10 base station devices, and the managed entity subset includes 5 base station devices among the 10 base station devices. For another example, the managed entity set includes 5 base station devices and 5 routers, and the managed entity subset includes 5 routers. For another example, the managed entity set includes 100 cells, and the managed entity subset includes 50 cells. This application does not specifically limit this.

[0133] The set of managed entities may be indicated by an object context. For the description of the object context, please refer to the above introduction and will not be repeated here. Exemplarily, the object context represents the area where the set of managed entities is located, such as the object context contains the coverage area polygon (polygon) or the coverage area tracking area code (TAC) corresponding to 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 constitute the set of managed entities based on the object context. The type of managed entity in the area (such as base station device) may be pre-configured or indicated by other information, and this application does not specifically limit this.

[0134] The managed entity subset can be determined in a variety of ways. For example, the consuming entity can determine the managed entity subset based on historical data, where the historical data can include intent reports on the historical operation of the network management intent. For example, the consuming entity can determine the network management intent subset based on the historical achievement of the network management intent's goals. For example, the consuming entity can determine the managed entities in the area with the lowest historical goal achievement rate as the managed entity subset. As another example, the consuming entity can also determine the managed entity subset based on other information, such as user feedback information. For example, the consuming entity can obtain the user's tolerance for goal failure. For example, the consuming entity can determine the managed entities in the area with the lowest user tolerance for goal failure as the managed entity subset, thereby improving the satisfaction of the network management intent service. This application does not specifically limit the method for determining the managed entity subset. For example, the managed entity subset can also be determined based on the operator's settings. As a result, differentiated protection can be obtained within the set of managed entities of the network management intent, which can improve the utilization of network resources.

[0135] It can be understood that the method of determining the subset of managed entities may be related to the type of network management intent. For example, for throughput intent, the consumer entity may determine the subset of managed entities with throughput intent based on the user's tolerance for non-achievement of the target; for energy-saving intent, the consumer entity may determine the subset of managed entities with energy-saving intent based on historical intent reports. This application does not specifically limit this.

[0136] The production entity can obtain the managed entity subset in a variety of ways. In some possible implementations, the production entity can determine the managed entity subset through the data structure of the network management intent (such as the data structure of the network management intent shown in Figure 1), and the managed entity subset is a constraint condition in the spatial dimension. In other words, the managed entity subset can be indicated by the object context. The object context can also include constraints or conditions for determining the managed entity subset (for example, it can be defined as assuranceSubsetAttri), the network management intent includes the expected object, the expected object includes the object context, and the object context includes spatial constraints. Exemplarily, the object context includes spatial constraints: the TAC corresponding to area #1 and the TAC corresponding to area #2, area #1 is the area where the managed entity set is located, area #2 is the area where the managed entity subset is located, and area #1 includes area #2. Thus, the production entity can execute the first management action group or the second management action group based on the area where the managed entity subset is located. In other possible implementations, the managed entity subset may 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 goal of the network management intention within the scope of the managed entity set of the network management intention, it may send a notification message to the consumer entity, so that the consumer entity can indicate the managed entity subset to the production entity. For a more detailed description of how the production entity obtains the managed entity subset, please refer to the description of Figures 4 and 5 below, which will not be repeated here.

[0137] In some implementations, the production entity may also obtain time period information. For example, the production entity may obtain information indicating a first time period and information indicating a second time period. The first time period may be used to determine whether execution of the first management action group achieves the network management intent goal within the set of managed entities. The second time period may be used to execute the first management action group combined with the second management action group to achieve the network management intent goal within the subset of managed entities within the second time period. The second time period is a subset of the first time period, for example, the first time period is 24 hours a day, and the second time period is 9:00 AM to 6:00 PM a day. In this case, failure to achieve the network management intent goal within the set of managed entities for the network management intent means that execution of the first management action group fails to achieve the network management intent goal within the set of managed entities for the network management intent within the first time period. Execution of the first or second management action group to achieve the network management intent goal within the subset of managed entities means that execution of the first or second management action group to achieve the network management intent goal within the subset of managed entities within the second time period. For example, the set of managed entities for throughput intent corresponds to region A, with the first time period being 24 hours a day; the subset of managed entities corresponds to region B, with the second time period being 9:00 AM to 6:00 PM. If the production entity determines that the execution of the first management action group fails to make the throughput index greater than or equal to 5 Mbps within region A within 24 hours, then the production entity can execute the first or second management action group to make the throughput index greater than or equal to 5 Mbps within region B between 9:00 AM and 6:00 PM. Thus, the production entity can consider time constraints when determining whether the goals of the network management intent have been achieved and when executing the first or second management action group, making the management of network management intent more flexible.

[0138] It is understandable that the production entity can obtain information indicating the first time period and the second time period in a variety of ways. In some implementations, 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. Exemplarily, the managed entity subset is the object context, and the time constraint is the constraint on the time dimension of the object context. Alternatively, the consumer entity can also send information indicating the first time period and the second time period to the production entity through separate information. This application does not specifically limit this.

[0139] The production entity can execute a first management action group based on the managed entity set, and the first management action group includes at least one action for managing the managed entity set. Exemplarily, the production entity can send an action group instruction to multiple managed entities in the managed entity set, and the managed entities execute the action group based on the instruction so that the network management intention is achieved within the managed entity set. Taking the throughput intention as an example, for example, the throughput intention includes the target of an average downlink throughput greater than 5Mbps, 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 multiple managed entities in the managed entity set. Multiple managed entities execute the action group based on the instruction (for example, the base station modifies the associated communication parameters) to achieve the target of an average downlink throughput greater than or equal to 5Mbps. Taking the energy saving intention as an example, for example, the energy saving intention includes energy saving greater than or equal to 10kW, the production entity can send an instruction to turn on the energy saving switch to multiple managed entities in the managed entity set, and multiple managed entities achieve energy saving greater than or equal to 10kW by turning on the energy saving switch. Here, turning on the energy saving switch can refer to turning on carrier shutdown, symbol shutdown, or radio frequency module sleep, etc. This application does not impose any particular limitation on this.

[0140] The production entity can use various methods to determine whether execution of the first management action group fails to achieve the network management intent within the scope of the set of managed entities. For example, the production entity can obtain performance indicator values ​​consistent with the network management intent. For example, if the network management intent is a throughput intent, the production entity can obtain throughput indicator values ​​within the scope of the set of managed entities to determine whether the network management intent has been achieved within the scope of the set of managed entities.

[0141] In some implementations, the production entity may also determine the reason for failure to achieve the network management intent's objectives, such as a conflict. For example, a network management intent conflicts with other network management intents within the scope of the network management intent's managed entity set. A conflict between a network management intent and another currently executing network management intent means that the desired objectives of the network management intent and the desired objectives of another currently executing network management intent cannot be simultaneously met within the scope of the managed entity set. To facilitate understanding of the embodiments of the present application, the following examples illustrate several possible conflict scenarios between the network management intent and other currently executing network management intents. In the first possible scenario, the desired objectives or goals of the network management intent semantically conflict with those of other currently executing network management intents. For example, if the energy-saving intent includes a target of physical resource block utilization less than or equal to 20%, while the throughput intent currently executed by the production entity includes a target of physical resource block utilization greater than 40%, the production entity may semantically determine that the network management intent conflicts with the other network management intents. In the second possible scenario, the production entity determines that the first management action group conflicts with the management action group of another currently executing network management intent. For example, a production entity implements both energy-saving and throughput intents. However, due to a management action (such as symbolic shutdown) performed by the production entity to achieve the energy-saving intent, the throughput decreases and the throughput intent cannot be achieved. In this case, the production entity can conclude that the failure to achieve the throughput intent is due to a conflict between the throughput intent and the energy-saving intent. Consequently, the production entity can also provide feedback to the consumer entity regarding the reasons for the failure to achieve the network management intent, thereby improving the management of network management intent.

[0142] In some implementations, after the production entity determines that the execution of the first management action group fails to achieve the goal of the network management intention within the scope of the managed entity set, it can determine whether to continue to execute or re-execute the first management action group so that the goal of the network management intention is achieved within the scope of the managed entity subset. For example, if the production entity determines that the execution of the first management action group achieves the goal of the network management intention within the scope of the managed entity set, then the production entity can continue to execute the first management action group and maintain the execution of the network management intention based on the managed entity subset, rather than suspending the execution of the network management intention. For another example, the production entity can obtain relevant parameters of the network environment, such as the energy-saving capability of the managed entity subset, etc. The production entity can determine whether the execution of the first management action group can achieve the goal of the network management intention within the scope of the managed entity subset. If the production entity determines that it can be achieved, then the production entity can re-execute the first management action group to achieve the goal of the network management intention within the scope of the managed entity subset.

[0143] In other implementations, after the production entity determines that the execution of the first management action group fails to achieve the goal of the network management intention within the scope of the set of managed entities, it can execute the second management action group to achieve the goal of the network management intention within the scope of the subset of managed entities. In other words, the production entity can determine and execute the second management action group. The first management action group and the second management action group may contain one or more identical actions, and this application does not specifically limit this. To facilitate understanding of the embodiments of the present application, the following mainly uses the example of the production entity executing the second management action group.

[0144] The production entity can determine the second management action group in a variety of ways. For example, the production entity can determine the network resources within the managed entity subset for achieving the goal of the network management intention based on the managed entity subset, and execute the second management action group based on the network resources. Taking the throughput intention as an example, the production entity can obtain the communication resources that the managed entities in the managed entity subset can use, and determine the second management action group based on the communication resources, and send action group instructions to the managed entities in the managed entity subset based on the second management action group. For example, the production entity can send instructions to the managed entities in the managed entity subset to turn off carrier shutdown, turn off symbol shutdown, turn off RF module sleep, or turn off RF channel shutdown. Among them, the action of turning off the carrier shutdown can enable more frequency domain resources to be used within the managed entity subset, the action of turning off the symbol shutdown can enable more time domain resources to be used within the managed entity subset, the action of turning off the RF module sleep can enable more frequency domain resources to be used within the managed entity subset, and the action of turning off the RF channel shutdown can enable more airspace resources to be used within the managed entity subset, thereby improving the throughput within the managed entity subset, so that the throughput index value within the managed entity subset reaches the corresponding throughput index range. When the managed entity subset also has an associated effective time period, the production entity can determine the network resources within the managed entity subset within the effective time period that can be used to achieve the goal of network management intentions, and determine and execute the second management action group based on the network resources. Therefore, the present application provides a more flexible management method for network management intentions.

[0145] In some implementations, the production entity may also obtain guarantee strength information, and the production entity may determine the network resources within the scope of the managed entity subset that can be used to achieve the target of the network management intention based on the guarantee strength information. Exemplarily, the guarantee strength information may be information corresponding to other network management intentions that the current production entity is executing. For example, the production entity maintains the execution of throughput intention and energy-saving intention at the same time, and the first management action group is used to achieve the target of the throughput intention within the scope of the managed entity set. When the production entity determines that the execution of the first management action group fails to achieve the target of the throughput intention within the scope of the managed entity set, the production entity may determine the network resources based on the managed entity subset of the throughput intention and the guarantee strength information of the energy-saving intention. For example, when the guarantee strength information indicates that the guarantee strength of the energy-saving intention is high (or the guarantee strength of the energy-saving intention is higher than the guarantee strength of the throughput intention), the production entity cannot encroach on the network resources used to achieve the target of the energy-saving intention so that the throughput target is achieved. When the guarantee strength information indicates that the guarantee strength of the energy-saving intention is low (or the guarantee strength of the energy-saving intention is lower than the guarantee strength of the throughput intention), the production entity can occupy the network resources used to achieve the goal of the energy-saving intention so that the throughput target is achieved. As another example, the guarantee strength information can be the information of the network management intention in step S310. For example, the network management intention is the throughput intention. When the guarantee strength information indicates that the guarantee strength of the throughput intention is high, the production entity can occupy the network resources used to achieve other network management intentions to ensure that the goal of the throughput intention is achieved. When the guarantee strength information indicates that the guarantee strength of the throughput intention is low, the production entity cannot occupy the network resources used to achieve other network management intentions. In this embodiment of the present application, the production entity performs a management action group that is not conducive to achieving the goal of the network management intention, which can be considered as occupying the network resources of the network management intention. For example, if the production entity performs carrier shutdown, this action is not conducive to achieving the goal of the throughput intention, and it can be considered that this action is occupying the network resources of the throughput intention. Therefore, the production entity determines the second management action group based on the assurance strength information, which can improve the flexibility of network management intention management, and is conducive to improving the utilization efficiency of network resources and improving user satisfaction.

[0146] Therefore, based on this technical solution, after the production entity determines that the goal of the network management intention within the scope of the managed entity set cannot be achieved, it can flexibly execute the first management action or the second management action group based on the managed entity subset to achieve the goal of the network management intention within the scope of the managed entity subset, instead of directly deleting or suspending the entire network management intention, providing a flexible way to manage network management intentions.

[0147] The above describes a method in which, after determining that the execution of a first management action group fails to achieve the network management intent within the scope of a set of managed entities, a production entity executes a second management action group to achieve the network management intent within the scope of a subset of managed entities. To facilitate understanding of the embodiments of the present application, two possible interaction modes between a consumer entity and a production entity are described below in conjunction with Figures 4 and 5.

[0148] FIG4 is a schematic flowchart of a method for implementing network management intention provided in an embodiment of the present application.

[0149] S401: A consumer entity sends a request message to a producer entity. Correspondingly, the producer entity receives the request message from the consumer entity.

[0150] The request message includes a managed entity subset. For an explanation of the managed entity subset, please refer to the description of FIG3 above, which will not be repeated here.

[0151] Exemplarily, the request message is used to request the production entity to create a network management intention. In other words, the request message may be an intention creation request message. The request message includes the network management intention, the network management intention includes a set of managed entities, and the managed entity set includes a subset of managed entities. For example, the intention creation request message may include a network management intention (such as the data structure shown in FIG1 ), and the network management intention may include a set of managed objects. For example, the constraints or conditions represented by the object context in the network management intention may be used to determine the set of managed objects and the subset of managed objects. Alternatively, the request message includes the network management intention and the subset of managed objects. In other words, the subset of managed objects may be indicated or determined by information other than the data structure of the network management intention, and this application does not specifically limit this. For a more detailed description of the set of managed objects and the subset of managed objects, please refer to the description in FIG3 above, which will not be repeated here.

[0152] It is understood that in some implementations, the request message is used to request the production entity to modify a network management intent. In other words, the request message may be an intent modification request message. This application does not specifically limit the type of request message. For example, the request message may also be a network management intent activation request message. For ease of understanding, this document uses the request message as an intent creation request message for example.

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

[0154] The producing entity obtains the managed entity subset in the request message and can determine whether the managed entity subset exceeds the scope of the managed entity set. If the producing entity determines that the managed entity subset exceeds the scope of the managed entity set, for example, the geographical area corresponding to the managed entity subset exceeds the geographical area corresponding to the managed entity set, the producing entity can provide feedback to the consuming entity indicating that the managed entity subset is incorrect. If the producing entity determines that the managed entity subset does not exceed the scope of the managed entity set, the producing entity can proceed with the subsequent process.

[0155] It is understood that the production entity may also perform a feasibility check on the request message. For example, the production entity may detect whether the request message can be successfully interpreted, such as detecting whether the request message conforms to the grammatical semantics of the network management intent. If the request message is detected to be successfully interpreted, the production entity may execute the first management action group based on the method described above. If the production entity detects that the request message cannot be successfully interpreted, such as due to a grammatical error, the production entity may send feedback indicating the grammatical error to the consumer entity.

[0156] Optionally, in S403, the production entity sends a response message to the consumption entity. Correspondingly, the consumption entity receives the response message from the production entity.

[0157] The production entity may send a response message to the consumption entity in response to the request message of S401. For example, when the request message is an intent-to-create request message, the response message may be an intent-to-create request response message.

[0158] If the production entity determines in step S402 that the creation intention is not feasible, such as because the managed entity subset exceeds the range of the managed entity set, or the request message does not conform to the syntax or semantics of the network management intention, the response message can be used to provide feedback that the creation intention is not feasible, or the response message can include information indicating that the creation intention is not feasible. In some implementations, the response message can also include failure reason information, which can indicate the reason for the schematic creation failure (such as the managed object subset exceeding the range or the information expression error, etc.), which is not particularly limited in this application.

[0159] It is understood that if the production entity detects that the creation intention is feasible in step S402, in other words, if the production entity determines that the managed entity subset is within the scope of the managed entity set, then the response message can be used to provide feedback that the creation intention is feasible, or the response message can include information indicating that the creation intention is feasible. Alternatively, the production entity may not perform step S403. This application does not specifically limit this.

[0160] It can also be understood that if the production entity determines that the creation intention is not feasible based on the request message, and sends a response message to the consumer entity to feedback that the creation intention is not feasible, then the consumer entity can adjust or regenerate the request message based on the response message. For example, the consumer entity determines that the subset of managed entities exceeds the scope of the set of managed entities based on the response message, then the consumer entity can adjust the scope of the subset of managed entities and resend a request message to the production entity requesting the creation of a network management intention or requesting the modification of a network management intention. This process of the production entity feeding back the corresponding message and the consumer entity resending the request message can be repeated at least once until the production entity determines that the creation intention is feasible. For the sake of simplicity, it will not be elaborated here.

[0161] S404: The production entity executes a first management action group.

[0162] The production entity can execute a first management action group based on the managed entity set, wherein the first management action group includes at least one action for managing the managed entity set. For a more detailed description of the production entity executing the first management action group, please refer to the description in Figure 3 above, which is not repeated here.

[0163] S405: The production entity determines that the execution of the first management action group fails to achieve the goal of the network management intention within the scope of the managed entity set.

[0164] For a more detailed explanation of the production entity determining that the goal of network management intention within the scope of the managed entity set has not been achieved, please refer to the description in Figure 3 above, which will not be repeated here.

[0165] S406: The production entity executes a second management action group to achieve the goal of network management intention within the scope of the managed entity subset.

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

[0167] Optionally, in S407, the production entity sends an intention report to the consumption entity. Correspondingly, the consumption entity receives the intention report from the production entity.

[0168] The intent report can be used to indicate whether the network management intent target has been achieved within the scope of the managed entity subset. For example, the intent report can include an identifier that indicates whether the network management intent target has been achieved within the scope of the managed entity subset. The intent report can also include the indicator value of a performance indicator within the scope of the managed entity subset. For example, if the network management intent target includes a throughput indicator, such as an average downlink throughput greater than or equal to 5 Mbps, then the intent report can include the throughput value within the scope of the managed entity subset.

[0169] In some embodiments, the intent report may also include performance indicator values ​​for the managed entity set excluding the managed entity subset. For example, the intent report may include throughput values ​​for the managed entity set excluding the managed entity subset. This allows consuming entities to improve their approach to network management intent based on the overall achievement of the managed entity set.

[0170] In some embodiments, the production entity may periodically report feedback intentions to the consumption entity, or report feedback intentions based on inquiries from the consumption entity, which is not particularly limited in this application.

[0171] Therefore, based on this technical solution, after the production entity determines that the goal of the network management intention within the scope of the managed entity set cannot be achieved, it can flexibly execute the first management action or the second management action group based on the managed entity subset to achieve the goal of the network management intention within the scope of the managed entity subset, instead of directly deleting or suspending the entire network management intention, thereby improving a flexible management method of network management intention.

[0172] Figure 4 above describes a method for carrying a subset of managed entities in a request message. In an embodiment of the present application, a consuming entity may also send a subset of managed entities to a producing entity after the producing entity determines that the network management objectives within the set of managed entities cannot be achieved. To facilitate understanding of this embodiment of the present application, this method is described and introduced below in conjunction with Figure 5.

[0173] FIG5 is a schematic flowchart of another method for implementing network management intent provided in an embodiment of the present application.

[0174] Optionally, in S501, the consumer entity sends a request message to the producer entity. Correspondingly, the producer entity receives the request message from the consumer entity.

[0175] This request message may be used to request a production entity to create a network management intent. In other words, the request message may be an intent creation request message. The request message includes the network management intent, which includes a set of managed entities. For example, the intent creation request message may include a network management intent (e.g., the data structure shown in FIG1 ), which may include a set of managed objects. For example, the constraints or conditions represented by the object context in the network management intent may be used to determine the set of managed objects.

[0176] Optionally, S502, the production entity performs a feasibility check.

[0177] The production entity may perform a feasibility check on the request message. For example, the production entity may detect whether the request message can be successfully interpreted, such as detecting whether the request message conforms to the grammatical semantics of the network management intent. If the request message is detected to be successfully interpreted, the production entity may execute the first management action group based on the method described above. If the production entity detects that the request message cannot be successfully interpreted, such as a grammatical error, the production entity may send feedback indicating the grammatical error to the consumer entity.

[0178] Optionally, in S503, the production entity sends a response message to the consumption entity. Correspondingly, the consumption entity receives the response message from the production entity.

[0179] The production entity may send a response message to the consumption entity in response to the request message of S502. For example, when the request message is an intent-to-create request message, the response message may be an intent-to-create request response message. For a more detailed description of step S503, please refer to the description of S403 in Figure 4 above, which will not be repeated here.

[0180] S504: The production entity executes a first management action group.

[0181] The production entity can execute a first management action group based on the managed entity set, wherein the first management action group includes at least one action for managing the managed entity set. For a more detailed description of the production entity executing the first management action group, please refer to the description in Figure 3 above, which is not repeated here.

[0182] S505: The production entity determines that the execution of the first management action group fails to achieve the goal of the network management intention within the scope of the managed entity set.

[0183] For a more detailed explanation of the production entity determining that the goal of network management intention within the scope of the managed entity set has not been achieved, please refer to the description in Figure 3 above, which will not be repeated here.

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

[0185] This notification information is used to indicate that the target of the network management intent has not been achieved within the scope of the set of managed entities. Exemplarily, the notification information may indicate whether the first management action group of the consuming entity has achieved the network management intent. For example, the notification information may include the indicator value of a performance indicator within the scope of the set of managed entities. For example, if the target of the network management intent includes a throughput indicator, such as the target of the network management intent is an average downlink throughput greater than or equal to 5 Mbps, then the notification information may include the throughput value within the scope of the set of managed entities.

[0186] S507: The consuming entity sends the managed entity subset to the producing entity. Correspondingly, the consuming entity receives the managed entity subset from the consuming entity.

[0187] The consuming entity may determine the managed entity subset based on the notification information. For example, the consuming entity may determine the managed entity subset based on the achievement of the network management intent contained in the notification information. Another example is that the consuming entity may determine the managed entity subset based on the usage scenario of the network management intent. The method for determining the managed entity subset can be found in the description of Figure 3 above and is not further elaborated here.

[0188] It is understandable that the consuming entity can directly send the managed entity subset to the producing entity, or the consuming entity can also regenerate a request message (such as an intent to create a request message), carry the managed entity subset in the request message and send it to the producing entity. In other words, the consuming entity can update the desired object of the network management intent, and the object context includes the managed entity subset. The consuming entity can send the updated network management intent (or the object context of the network management intent) to the producing entity. This application does not specifically limit this.

[0189] S508: The production entity executes a second management action group to achieve the goal of network management intention within the scope of the managed entity subset.

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

[0191] Optionally, in S509, the production entity sends an intention report to the consumption entity. Correspondingly, the consumption entity receives the intention report from the production entity.

[0192] For a more detailed description of the intention report, please refer to the description of step S407 in Figure 4 above, which will not be repeated here.

[0193] Therefore, based on this technical solution, after the production entity determines that the goal of the network management intention within the scope of the managed entity set cannot be achieved, it can flexibly execute the first management action or the second management action group based on the managed entity subset to achieve the goal of the network management intention within the scope of the managed entity subset, instead of directly deleting or suspending the entire network management intention, thereby improving a flexible management method of network management intention.

[0194] It can also be understood that in the above-mentioned method embodiments, the methods and operations implemented by the production entity can also be implemented by components that can be produced by the production entity (such as chips or circuits); in addition, the methods and operations implemented by the consumer entity can also be implemented by components that can be consumed by the consumer entity (such as chips or circuits), without limitation.

[0195] Corresponding to the methods provided in the above-mentioned method embodiments, embodiments of the present application also provide corresponding apparatuses, which include modules for executing the corresponding methods in the above-mentioned method embodiments. The modules may be software, hardware, or a combination of software and hardware. It is understood that the technical features described in the above-mentioned method embodiments are also applicable to the following apparatus embodiments.

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

[0197] 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 aforementioned various method embodiments.

[0198] In one possible design, the device 10 can be used to execute the actions performed by the production entity in the above method embodiments. In this case, the device 10 can be a production entity or a component of a production entity. The transceiver unit 11 is used to execute the transceiver-related operations on the production entity side in the above method embodiments, and the processing unit 12 is used to execute the processing-related operations on the production entity side in the above method embodiments.

[0199] In a first possible implementation, processing unit 12 is configured to determine that execution of a first management action group fails to achieve a target of the network management intent within a managed entity set 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 execute the first management action or the second management action group to achieve the target of the network management intent within a managed entity subset, 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. Optionally, transceiver unit 11 is configured to receive the managed entity subset.

[0200] The apparatus 10 can implement the steps or processes performed by the production entity in the method embodiments according to the embodiments of the present application. The apparatus 10 may include units for executing the methods performed by the production entity in the method embodiments according to the embodiments of the present application. The specific processes for each unit to perform the above-mentioned corresponding steps have been described in detail in the above-mentioned method embodiments and will not be repeated here for the sake of brevity.

[0201] Another possible design is that the device 10 can be used to execute the actions performed by the consumer entity in the above method embodiments. In this case, the device 10 can be a consumer entity or a component of a consumer entity, the transceiver unit 11 is used to execute the transceiver-related operations on the consumer entity side in the above method embodiments, and the processing unit 12 is used to execute the processing-related operations on the consumer entity side in the above method embodiments.

[0202] The first possible implementation method is that the processing unit 12 determines a managed entity subset, and the managed subset is a subset of the managed entity set of the network management intention, wherein the managed entity set contains at least two managed entities, and the managed entity subset is used to execute the first management action or the second management action group when the execution of the first management action group fails to achieve the goal of the network management intention within the managed entity set, so as to achieve the goal of the network management intention within the scope of the managed entity subset, wherein the first management action group contains at least one action for managing the managed entity set, and the second management action group contains at least one action for managing the managed entity subset; the transceiver unit 11 is used for the managed entity subset.

[0203] The apparatus 10 can implement the steps or processes corresponding to those performed by the consumer entity in the method embodiment according to the embodiment of the present application. The apparatus 10 may include units for executing the method performed by the consumer entity in the method embodiment according to the embodiment of the present application. The specific process of each unit executing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiments and will not be repeated here for the sake of brevity.

[0204] It is understandable that the device 10 here is embodied in the form of a functional unit. The term "unit" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing at least one software or firmware program, a merged logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art will understand that the device 10 may be specifically a production entity in the above-mentioned embodiment, and may be used to execute the various processes and / or steps corresponding to the production entity in the above-mentioned method embodiments; or, the device 10 may be specifically a consumer entity in the above-mentioned embodiment, and may be used to execute the various processes and / or steps corresponding to the consumer entity in the above-mentioned method embodiments. To avoid repetition, it will not be described here.

[0205] The apparatus 10 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the communication equipment (such as a production entity or a consumption entity) in the above-mentioned method. The functions can be implemented by hardware, or the corresponding software can be implemented by hardware. The hardware or software includes at least one module corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending 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 to respectively perform the sending and receiving operations and related processing operations in each method embodiment.

[0206] In addition, the transceiver unit 11 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing unit may be a processing circuit.

[0207] It should be noted that the apparatus in FIG6 may be the device in the aforementioned embodiment, or may be a chip or chip system, such as a system on chip (SoC). The transceiver unit may be an input / output circuit or a communication interface; the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip. This is not limited here.

[0208] Referring to Figure 7 , as an example, Figure 7 is a schematic diagram of another communication device 20 provided in an embodiment of the present application. The device 20 includes a processor 21, which is coupled to a memory 22. Optionally, the device 20 also includes the memory 22. The memory 22 is used to store computer programs or instructions and / or data. The processor 21 is used 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 described in the above method embodiments.

[0209] Optionally, there is at least one processor 21.

[0210] Optionally, there is at least one memory 22.

[0211] Optionally, the memory 22 is integrated with the processor 21 or provided separately.

[0212] Optionally, as shown in Figure 7, the device 20 further includes a transceiver 23, which is used to receive and / or send signals. For example, the processor 21 is used to control the transceiver 23 to receive and / or send signals.

[0213] As a solution, the device 20 is used to implement the operations performed by the production entity in the above various method embodiments.

[0214] For example, the processor 21 is configured to execute computer programs or instructions stored in the memory 22 to implement the relevant operations of the production entity in the above various method embodiments. For example, the method executed by the production entity in the embodiment shown in FIG3 .

[0215] As another solution, the device 20 is used to implement the operations performed by the consumer entity in the above various method embodiments.

[0216] For example, the processor 21 is configured to execute computer programs or instructions stored in the memory 22 to implement the relevant operations of the consumer entity in the above various method embodiments. For example, the method executed by the consumer entity in the embodiment shown in FIG3 .

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

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

[0219] 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, or a discrete hardware component, the memory (storage module) may be integrated into the processor.

[0220] Memory described herein is intended to comprise, but not be limited to, these and any other suitable types of memory.

[0221] 8 , as an example, is a schematic diagram of a chip system 30 provided in accordance with an embodiment of the present application. The chip system 30 (or processing system) includes a logic circuit 31 and an input / output interface 32 .

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

[0223] Specifically, for example, if a 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 the wake-up signal to the logic circuit 31 for processing.

[0224] As a solution, the chip system 30 is used to implement the operations performed by the production 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 production entity in the above method embodiments, such as the processing-related operations performed by the production entity in the embodiment shown in Figure 3; 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 the sending and / or receiving-related operations performed by the production entity in the embodiment shown in Figure 3.

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

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

[0228] An embodiment of the present application further provides a computer-readable storage medium on which computer instructions for implementing the methods executed by the device in the above-mentioned method embodiments are stored.

[0229] For example, when the computer program is executed by a computer, the computer can implement the methods performed by the production entity in each embodiment of the above method.

[0230] For another example, when the computer program is executed by a computer, the computer can implement the methods performed by the consumer entity in each embodiment of the above method.

[0231] An embodiment of the present application also provides a computer program product, comprising instructions, which, when executed by a computer, implement the methods performed by a production entity or a consumption entity in the above-mentioned method embodiments.

[0232] An embodiment of the present application further provides a communication system, which includes the production entity and the consumption entity in the above embodiments.

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

[0234] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as 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 mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0235] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes at least one computer instruction. When the computer program instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instruction 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 instruction can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes at least one available medium integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)). For example, the aforementioned available medium includes, but is not limited to, various media that can store program code, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0236] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for managing network management intentions, characterized in that: The method comprises: Determining that execution of a first management action group fails to achieve a target of the network management intention within a 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; Execute the first management action group or the second management action group to achieve the goal of the network management intention within the scope of the managed entity subset, 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.

2. The method according to claim 1, characterized in that The method further comprises: Receive a request message, wherein the request message is used to request the creation of the network management intention or the modification of the network management intention, the request message includes the network management intention, the network management intention includes the managed entity subset, or the request message includes the network management intention and the managed entity subset.

3. The method according to claim 1 or 2, characterized in that The object context in the network management intent includes information for determining the managed entity set and / or the managed entity subset.

4. The method according to claim 1, characterized in that After determining that the execution of the first management action group fails to achieve the target of the network management intention within the scope of the managed entity set of the network management intention, the method further includes: Sending notification information, wherein the notification information indicates that a target of the network management intention has not been achieved within the scope of the managed entity set; The subset of managed entities is received in response to the notification information.

5. The method according to any one of claims 1 to 4, characterized in that: The execution of the first management action group fails to achieve the target of the network management intention within the managed entity set of the network management intention, which means that the execution of the first management action group fails to achieve the target of the network management intention within the managed entity set of the network management intention within a first time period; Then the execution of the first management action group or the second management action group so as to achieve the goal of the network management intention within the scope of the managed entity subset means: executing the first management action group or the second management action group so as to achieve the goal of the network management intention within the scope of the managed entity subset within the second time period, wherein the second time period is a subset of the first time period.

6. The method according to any one of claims 1 to 5, characterized in that The executing the first management action group or the second management action group includes: Determining, based on the managed entity subset, network resources within the managed entity subset that can be used to achieve the goal of the network management intention; The first management action group or the second management action group is performed based on the network resources.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: The reason why it is determined that the execution of the first management action group fails to achieve the target of the network management intention within the scope of the managed entity set is that an intention conflict occurs.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: Sending an intent report, wherein the intent report includes the achievement of the target of the network management intent within the managed entity subset.

9. The method according to claim 8, characterized in that The intent report also includes the achievement of the target of the network management intent within the scope of the managed entity set excluding the scope of the managed entity subset.

10. A method for managing network management intentions, characterized in that: The method comprises: Determine a managed entity subset, the managed subset being a subset of a managed entity set of network management intent, wherein the managed entity set includes at least two managed entities, and the managed entity subset is used to execute the first management action group or the second management action group when the execution of the first management action group fails to achieve the target of the network management intent within the managed entity set, so that the target of the network management intent is achieved within the scope of the managed entity subset, wherein the first management action group includes at least one action for managing the managed entity set, and the second management action group includes at least one action for managing the managed entity subset; The managed entity subset is sent.

11. The method according to claim 10, characterized in that The sending of the managed entity subset includes: Send a request message, wherein the request message is used to request the creation of the network management intention or the modification of the network management intention, the request message includes the network management intention, the network management intention includes the managed entity subset, or the request message includes the network management intention and the managed entity subset.

12. The method according to claim 10 or 11, characterized in that The object context in the network management intent includes information for determining the managed entity set and / or the managed entity subset.

13. The method according to claim 12, characterized in that The method further comprises: receiving notification information, the notification information indicating that a target of the network management intention within the managed entity set has not been achieved; The sending of the managed entity subset includes: The subset of managed entities sending responses to the notification information.

14. The method according to any one of claims 10 to 13, characterized in that The reason why the execution of the first management action group fails to achieve the target of the network management intention within the scope of the managed entity set is that an intention conflict occurs.

15. The method according to any one of claims 10 to 14, characterized in that The method further comprises: An intent report is received, wherein the intent report includes a status of achievement of a target of the network management intent within the managed entity subset.

16. The method according to claim 15, characterized in that The intent report also includes the achievement of the target of the network management intent within the scope of the managed entity set excluding the scope of the managed entity subset.

17. A method for managing network management intentions, characterized in that: The method comprises: Sending a subset of managed entities; Receiving the managed entity subset; Determining that execution of a first management action group fails to achieve a target of the network management intention within a 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; Execute the first management action group or the second management action group to achieve the goal of the network management intention within the scope of the managed entity subset, 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.

18. A management device for network management intention, characterized in that: The device comprises a determining unit and an executing unit, wherein: The determining unit is configured to determine that the execution of the first management action group fails to achieve the target 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 used to execute the first management action group or the second management action group to achieve the goal of the network management intention within the scope of the managed entity subset, 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.

19. A method for managing network management intentions, characterized in that: The device comprises a transceiver unit and a processing unit, wherein: The processing unit is used to determine a managed entity subset, the managed subset is a subset of a managed entity set of a network management intention, wherein the managed entity set includes at least two managed entities, and the managed entity subset is used to determine a second management action group when the execution of a first management action group fails to achieve a target of the network management intention within the managed entity set, so as to achieve the target of the network management intention within the managed entity subset, wherein the first management action group includes at least one action for managing the managed entity set, and the second management action group includes at least one action for managing the managed entity subset; The transceiver unit is used to send the managed entity subset.

20. A communication device, characterized in that: The method comprises a unit for executing the method according to any one of claims 1 to 9, or comprises a unit for executing the method according to any one of claims 10 to 16.

21. A communication system, characterized in that: The invention comprises an apparatus for executing the method according to any one of claims 1 to 9 and an apparatus for executing the method according to any one of claims 10 to 16.

22. The system of claim 21, wherein: Also included are managed entities for network management purposes.

23. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 9, or the computer is caused to execute the method according to any one of claims 10 to 16.

24. A computer program product, characterized in that The method comprises a computer program code, which, when executed on a computer, enables the computer to implement the method according to any one of claims 1 to 9 or enables the computer to implement the method according to any one of claims 10 to 16.

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

26. The device according to claim 25, characterized in that The apparatus also includes the memory.

Images