Network management intention management method, device and system

Abstract

The invention provides a network management intention management method, device and system, and the method comprises the steps: determining that execution of a first management action group cannot enable a target of a network management intention to be achieved in a range of a managed entity set of the network management intention, and the managed entity set comprises at least two managed entities, the first management action group comprises at least one action for managing the managed entity set; the first management action group or the second management action group is executed to enable the goal of the network management intent to be achieved within the scope of the managed entity subset, the managed entity subset is a subset of the managed entity set, and the second management action group comprises at least one action for managing the managed entity subset. Therefore, a flexible network management intention management mode is provided.

Description

Technical Field

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

[0002] With the development of network resource management, network management service consumption entities do not need to directly manage network resources. Network management service consumption entities can send network management intentions to network management service production entities. Network management service production entities execute network management intentions in order to achieve the expected goals for the specified performance indicators of network devices within a specific range. The current management method of network management intentions is not flexible enough. For example, when the network environment of network management intentions is complex and changeable, if the network management service production entity determines that the goal of the network management intention has not been achieved, it will delete or suspend the network management intention, and then issue a new network management intention. If the new network management intention cannot be achieved, it will delete or suspend the new network management intention again, and the cycle will repeat...

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

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

[0005] In a first 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 that execution of a first management action group fails to achieve a goal of the network management intent within 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 action group includes at least one action for managing the set of managed entities; executing the first management action group or the second management action group to achieve the goal of the network management intent within a subset of managed entities, wherein the subset of managed entities is a subset of the set of managed entities, and the second management action group includes at least one action for managing the subset of managed entities.

[0006] Based on the present 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 providing a flexible way to manage network management intentions.

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

[0008] 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 intent or request the modification of a network management intent, the request message includes the network management intent, the network management intent includes a subset of managed entities, or the request message includes the network management intent and a subset of managed entities.

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

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

[0011] 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 intent within the scope of the set of managed entities of the network management intent, the method also includes: sending a notification message indicating that the goal of the network management intent has not been achieved within the scope of the set of managed entities; and receiving a subset of managed entities in response to the notification message.

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

[0013] In combination with the first aspect, in certain implementation methods 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 managed entity subset 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 managed entity subset within the second time period, wherein the second time period is a subset of the first time period.

[0014] Based on this technical solution, the production entity can also consider the constraints on the time dimension when determining whether the goal of the network management intention has been 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.

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

[0016] 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 the network management intent; and executing the first management action group or the second management action group based on the network resources.

[0017] 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 the network management intention.

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

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

[0020] 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 the achievement of a target of the network management intent within the scope of the managed entity subset.

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

[0022] In combination with the first aspect, in some implementations of the first aspect, the intent report further 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.

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

[0024] 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 includes at least two managed entities, the managed entity subset is used to determine a second management action group when 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 includes at least one action for managing the set of managed entities, and the second management action group includes at least one action for managing the subset of managed entities; sending the subset of managed entities.

[0025] Regarding the beneficial technical effects of various implementation methods of the second aspect, reference may be made to the description of the relevant implementation methods of the first aspect and will not be elaborated herein.

[0026] 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 intent or request the modification of a network management intent, the request message includes the network management intent, the network management intent includes the subset of managed entities, or the request message includes the network management intent and the subset of managed entities.

[0027] In conjunction with the second aspect, in some 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.

[0028] In combination with the second aspect, in certain implementations of the second aspect, the method also includes: receiving notification information indicating that a 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.

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

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

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

[0032] In combination with the second aspect, in certain implementations of the second aspect, the intent report further 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.

[0033] According to a 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 execution of a first management action group fails to achieve a 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.

[0034] Regarding the beneficial technical effects of various implementation methods of the third aspect, reference may be made to the description of the relevant implementation methods of the first aspect and will not be elaborated herein.

[0035] 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 intent or the modification of a network management intent, the request message includes the network management intent, the network management intent includes a subset of managed entities, or the request message includes the network management intent and a subset of managed entities; and the request message is received.

[0036] In combination 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.

[0037] 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 intent within the scope of the set of managed entities of the network management intent, the method also includes: sending a notification message indicating that the goal of the network management intent has not been achieved within the scope of the set of managed entities; receiving the notification message; receiving a subset of managed entities in response to the notification message.

[0038] In combination with the third aspect, in certain implementation methods 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 managed entity subset 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 managed entity subset within the second time period, wherein the second time period is a subset of the first time period.

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

[0040] 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 the network management intent; and executing the first management action group or the second management action group based on the network resources.

[0041] 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 goal of the network management intention within the scope of the managed entity set is that an intention conflict occurs.

[0042] 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 a target of the network management intent within the scope of the managed entity subset; and receiving the intent report.

[0043] In combination with the third aspect, in certain implementations of the third aspect, the intent report further 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.

[0044] In a fourth aspect, a management device for network management intention is provided, the device comprising a determination unit and an execution unit, wherein the determination unit is used to determine 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; 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 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.

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

[0046] Regarding various implementation methods of the fourth aspect and the beneficial technical effects of various implementation methods, reference may be made to the description of the relevant implementation methods of the first aspect and no further elaboration will be given.

[0047] In a fifth aspect, a management device for network management intent is provided, the device comprising 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 a set of managed entities of the network management intent, wherein the set of managed entities 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 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 includes at least one action for managing the set of managed entities, and the second management action group includes at least one action for managing the subset of managed entities; the transceiver unit is used to send the subset of managed entities.

[0048] Regarding various implementation methods of the fifth aspect and the beneficial technical effects of various implementation methods, reference may be made to the description of the relevant implementation methods of the first and second aspects, and no further elaboration will be given.

[0049] In a sixth aspect, a communication device is provided, wherein the communication device has the function 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 function can be implemented by hardware, or the corresponding software can be implemented by hardware. The hardware or software includes one or more units corresponding to the above functions.

[0050] In a seventh aspect, a communication device is provided, comprising a processor and a memory. Optionally, a transceiver may also be included. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, and control the transceiver to send and receive signals, so that the communication device executes the method in any possible implementation of the first aspect or any aspect of the first aspect.

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

[0052] In an eighth aspect, a communication device is provided, comprising a processor and a memory. Optionally, a transceiver may also be included. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, and control the transceiver to send and receive signals, so that the communication device executes the method in any possible implementation of the second aspect or any aspect of the second aspect.

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

[0054] In a ninth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is used 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, and the communication interface is also used to output the data and / or information processed by the processor, so that the method in any possible implementation of the first aspect or any aspect of the first aspect is executed. The communication device may be a chip used for network management service production network elements.

[0055] In a tenth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is used 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, and the communication interface is also used to output the data and / or information processed by the processor, so that the method in any possible implementation of the second aspect or any aspect of the second aspect is executed. The communication device can be a chip applied to a network management service consumption network element.

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

[0057] In a 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.

[0058] In a thirteenth aspect, a computer program product is provided, the computer program product comprising a computer program code, and when the computer program code is run on a computer, the method in the first aspect, or any possible implementation of any aspect in the first aspect, is executed.

[0059] In a fourteenth aspect, a computer program product is provided, the computer program product comprising a computer program code, and when the computer program code is run 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 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.

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

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

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

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

[0065] Figure 4 It is a schematic flow chart of a method for implementing a network management intention provided in an embodiment of the present application;

[0066] Figure 5 It is a schematic flow chart of another method for implementing network management intention provided in an embodiment of the present application;

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

[0068] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0069] The technical solution of the present application can be applied to various network function virtualization (NFV) systems, which can use standard formal language to describe the current operator's business technology solutions, network construction solutions and network operation and maintenance methods as patterns and strategies, 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: wireless intent driven network (wIDN) system, experiential networked intelligence (ENI) system, intent driven management service (IDMS) system or open network automation platform (ONAP) system, etc.

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

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

[0072] 1.1 Network Management

[0073] Network management refers to the management of network resources, including but not limited to monitoring, controlling and recording the performance and usage of network resources, and issuing management action groups to network resources (such as devices in the network) based on the detected network conditions to enable the network to operate effectively. Exemplarily, network management can be monitoring, testing, configuring, analyzing, evaluating and controlling network resources. Network management can also be timely reporting and processing 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. Exemplarily, network resources can be base station equipment, routers, switches, core network equipment, etc. In this regard, the embodiments of the present application are not particularly limited. For the convenience of description, the embodiments of the present application are described by taking the managed entity as an example, but they can all be replaced by other objects of network management.

[0074] 1.2 Network Management Services

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

[0076] 1.3 Network management service production entity

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

[0078] 1.4 Network Management Service Consumption Entity

[0079] The calling entity of network management is called a network management service consumption entity. Exemplarily, the capability or function of the network management service consumption entity can be deployed on a certain network element, which is called a network management service consumption network element; the capability or function of the network management service consumption entity can also be deployed on other devices, which is not limited in the embodiments of the present application; for the convenience of description, the embodiments of the present application take the network management service consumption entity as an example for explanation, but they can all be replaced by other devices that deploy the capability or function of the network management service consumption entity.

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

[0081] The network management intent refers to the demand of the network management service consumer entity for the network management service, which may also be referred to as the network management service demand. The embodiment of the present application does not limit this name. 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 the third generation partnership project (3GPP) standard specification 28.312.

[0082] In the intentional interaction scenario of this application, there are mainly two roles, namely the network management provider entity and the network management service consumer entity. Among them, the network management provider entity can also be called a network management provider, or an intent provider (intent provider), or an intent handler (intent handler), etc. The network management service consumer entity can also be called a network management service consumer, or an intent consumer (intent consumer), or an intent owner (intent owner), etc.

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

[0084] Intent can be applied to network systems to achieve the expected goals for the specified performance indicators of network devices within a specific range. Intent can express expectations for network systems through formal specifications and description information. Among them, formal specifications can refer to the specific syntax or semantics of intent, and description information can be used to describe the requirements, goals, and constraints of intent.

[0085] An intent may include at least one intent expectation. Each intent expectation may represent the performance requirements of a network management service consumer entity for a specific network object. An intent expectation may consist of at least one expected target and an expected object, and each expected target may represent the performance requirements of a network management service consumer entity for a specific attribute of an expected object. Exemplarily, an intent expectation may include two expected targets, one of which is an average downlink throughput greater than 5Mbps, 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 5Mbps, 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 the 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 is described as the intent not being fulfilled or the intent not being realized.

[0086] The intent may also include an intent context. The intent context may represent the 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.

[0087] The intent may also include an expected context. The expected context may represent the constraints or conditions that the network management service consuming entity expects for an intent. For example, the network management service consuming entity may constrain the expected duration of the intent through the expected context.

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

[0089] The intent may also include an object context, which may indicate constraints or conditions of the network management service consuming entity on the network object to be acted upon. Exemplarily, the network management service consuming entity may indicate the region where the network object to be acted upon is located through the object context.

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

[0091] The information element in the IOC may adopt a specific structure to express the demand for network management services. For example, Figure 1 A schematic structural diagram of an intended IOC is shown.

[0092] See also 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.

[0093] Understandably, Figure 1 This is a schematic illustration of the relationship between the attributes in the intent IOC. Based on the network management service requirements, the intent IOC may also contain other attributes, which are not specifically limited in this application. It can also be understood that this application does not specifically limit the number of attributes of the same type. For example, an intent IOC may contain one or more parallel intent expectation attributes, and an intent expectation may also contain one or more parallel expected target attributes.

[0094] 3. Network Management Intent Template

[0095] The network management intent template refers to the template description information of the network management intent, which can also be called the network management service requirement template. The embodiment of the present application does not limit this name. The intent template can be used to specify the syntax and semantics of the various attribute expressions introduced above. For example, the intent template can specify the field type, value type, etc. that can be used for each attribute in the IOC. 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, such as the field type of the expected target for latency is a string, the field type of the expected target for bandwidth is a string, and the field type of the expected target for the maximum number of users is an integer. Again exemplarily, the intent template can also include intent context description information that specifies how the intent context and the expected context are expressed. The intent context description information can be used to specify the field type of the intent context, etc., and the present application does not specifically limit this.

[0096] 4. Intent Expression

[0097] 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 then the intent expression generated after instantiation 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.

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

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

[0100] The target network object indicated by the network object information instance is the instantiation result of the target network object indicated by the network object information template. Exemplarily, the target network object indicated by the network object information instance is one of the target network objects indicated by the network object information template, that is, one of the physical entities or logical entities used to indicate the network management service. At this time, the network object information instance indicates a specific network object. For example, the network object information template indicates a network service, and the network object information instance indicates an energy-saving service.

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

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

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

[0104] 5. Intent Examples

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

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

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

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

[0109] A network management action group is one or more network management actions generated by a network management service production entity based on an intent expression. The network management service production entity satisfies the intent of a network management service consumption entity by executing one or more network management actions. A network management action group can also be called a management operation, an intent operation, or a network management task. A network management action group can be a set of operation instructions for a desired object (e.g., a physical entity or a logical entity in a network system that is intended to act on), containing one or more instructions. For example, adjusting the antenna tilt angle of a base station, turning on the energy-saving switch of a cell, etc.

[0110] The network management service production entity can generate multiple management action groups based on the intent expression. During the execution process, the network management service production entity can select some management action groups from multiple 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 translation of the intent expression are optional operations that can be used to meet the intent. The network management service production entity may select one of the network management action groups to execute to meet the intent, or it may select multiple network management action groups to execute to meet the intent.

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

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

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

[0114] 1. Network management service consumption entity 210: can be used to call management services, or call intent services to manage the network system. Exemplarily, the network management service consumption entity 210 can instantiate the intent template, set the intent IOC to generate an intent expression, and send the intent expression to the network management service production network element 220 to realize the expectations of the network system.

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

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

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

[0118] 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 (e.g., a cloud platform). It is understandable that the above-mentioned entity can be implemented by one device, or can also 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 (network management system, NMS), an equipment management system (equipment management system, EMS) or a functional module within a device, such as one or more functional modules within a network equipment (network equipment, NE), and the network equipment can be a base station or a core network element.

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

[0120] As another example, the network management service consumption entity 210 can be deployed in the EMS, the network management service production entity 220 can be deployed in different NEs, and 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.

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

[0122] With the development of network resource management, network management service consumption entities do not need to directly manage network resources. Network management service consumption entities can send messages to network management service production entities to enable network management service production entities to execute network management intentions, so that the specified performance indicators of network devices within a specific range can reach the expected goals. At present, the application environment of network management intentions is usually complex and changeable. Therefore, how to manage network management intentions in a complex and changeable environment is a technical problem that needs to be solved urgently.

[0123] Figure 3 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 intention is referred to as the intention.

[0124] S310: 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.

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

[0126] S320, the production entity executes the first management action group or the second management action group to achieve the goal of network management intention within the managed entity subset.

[0127] 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. That is, after the production entity determines that the goal 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 so that the goal of the network management intent within the managed entity subset is achieved, instead of directly deleting or suspending the entire network management intent, providing a flexible way to manage network management intent.

[0128] It can be understood that the goal of fulfilling the network management intent can also be described as the goal of satisfying the network management intent, the goal of achieving the network management intent, etc.

[0129] In an embodiment 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 contained in the network management intent. Exemplarily, the target of the network management intent includes that the indicator value of the performance indicator reaches 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 may be referred to as 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 may be referred to as an energy-saving intention. The present application specifically limits the types of performance indicators, such as coverage indicators, latency indicators, etc.

[0130] 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. A managed entity subset is a subset of a managed entity set, that is, a managed entity subset is a partial managed entity, and the managed entity subset includes some 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.

[0131] The set of managed entities may be indicated by an object context. Among them, the description of the object context can refer to the introduction above 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. Among them, the type of managed entity in the area (such as base station equipment) can be pre-configured or indicated by other information, and this application does not specifically limit this.

[0132] The managed entity subset can be determined in a variety of ways. Exemplarily, the consumer entity can determine the managed entity subset based on historical data, where the historical data can include the intention report of the historical operation of the network management intention. For example, the consumer entity can determine the network management intention subset based on the historical achievement of the target of the network management intention, such as the consumer entity can determine the managed entities in the area with the lowest historical achievement rate of the target as the managed entity subset. In another exemplary embodiment, the consumer entity can also determine the managed entity subset based on other information, such as user feedback information. For example, the consumer entity can obtain the user's tolerance for non-achievement of the target, such as the consumer entity can determine the managed entities in the area with a low user tolerance for non-achievement of the target as the managed entity subset, thereby improving the satisfaction of the network management intention service. The present application does not specifically limit the method for determining the managed entity subset, such as the managed entity subset can also be determined based on the operator's settings. Thus, differentiated guarantees can be obtained within the range of the managed entity set of the network management intention, and the utilization rate of network resources can be improved.

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

[0134] The production entity may obtain the managed entity subset in a variety of ways. In some possible implementations, the production entity may determine the managed entity subset through a data structure of a network management intent (e.g. Figure 1The data structure of the network management intent shown in the figure), the managed entity subset is a constraint condition in the spatial dimension. That is, 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 the spatial constraint condition. Exemplarily, the object context includes the spatial constraint condition: 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 perform the first management action group or the second management action group based on the area where the managed entity subset is located. In some 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 intent within the managed entity set of the network management intent, a notification message may be sent 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 the production entity obtaining the managed entity subset, see below. Figure 4 and Figure 5 The description is not repeated here.

[0135] In some implementations, the production entity may also obtain information about the time period. Exemplarily, 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 the execution of the first management action group enables the target of the network management intention to be achieved within the scope of the managed entity set, and the second time period may be used to execute the first management action group combined with the second management action group to enable the target of the network management intention to be achieved within the scope of the managed entity subset within the second time period. The second time period is a subset of the first time period, such as the first time period is 24 hours in a day, and the second time period is from 9 am to 6 pm in a day. In this case, the meaning that the execution of the first management action group fails to enable the target of the network management intention to be achieved within the scope of the managed entity set of the network management intention is: the execution of the first management action group fails to enable the target of the network management intention to be achieved within the scope of the managed entity set of the network management intention within the first time period. Executing the first management action group or the second management action group to enable the target of the network management intention to be achieved within the scope of the managed entity subset means: executing the first management action group or the second management action group to enable the target of the network management intention to be achieved within the scope of the managed entity subset within the second time period. For example, the managed entity set of the throughput intent corresponds to region A, the first time period is 24 hours in a day, the managed entity subset corresponds to region B, and the second time period is from 9 am to 6 pm in a day. 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 the scope of region A within 24 hours in a day, then the production entity can make the throughput index greater than or equal to 5 Mbps within the scope of region B from 9 am to 6 pm by executing the first management action group or the second management action group. Therefore, the production entity can also consider the constraints in the time dimension when determining whether the goal of the network management intent is achieved and executing the first management action group or the second management action group, making the management method of the network management intent more flexible.

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

[0137] The production entity may execute a first management action group based on a managed entity set, and the first management action group includes at least one action for managing the managed entity set. Exemplarily, the production entity may 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 goal 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, and multiple managed entities execute the action group based on the instruction (for example, the base station modifies the associated communication parameters) to achieve the goal 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 may send an instruction to instruct 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. Among them, turning on the energy-saving switch may refer to turning on carrier shutdown, symbol shutdown, or radio frequency module sleep, etc. This application does not impose any particular limitation on this.

[0138] The production entity may determine in a variety of ways that the execution of the first management action group fails to achieve the target of the network management intent within the scope of the managed entity set. For example, the production entity may obtain a performance indicator value related to the target of the network management intent. For example, if the network management intent is a throughput intent, the production entity may obtain a throughput indicator value within the scope of the managed entity set to determine whether the network management intent is achieved within the scope of the managed entity set.

[0139] In some implementations, the production entity may also determine the reason why the target of the network management intention cannot be achieved, such as the reason being a conflict. For example, the network management intention conflicts with other network management intentions within the scope of the managed entity set of the network management intention. The conflict between the network management intention and other currently executed network management intentions means that the intended expected target of the network management intention and the intended expected target of other currently executed network management intentions cannot be satisfied at the same time within the scope of the managed entity set. In order to facilitate the understanding of the embodiments of the present application, the following exemplary descriptions of several possible conflict situations between the network management intention and other currently executed network management intentions are given. In the first possible scenario, the intended expectation or target of the network management intention semantically conflicts with other currently executed network management intentions. For example, the energy-saving intention includes a target of physical resource block utilization less than or equal to 20%, but the throughput intention currently executed by the production entity includes a target of physical resource block utilization greater than 40%, then the production entity can semantically determine that the network management intention conflicts with other network management intentions. In the second possible scenario, the production entity determines that the first management action group conflicts with the management action group of other currently executed network management intentions. For example, the production entity executes energy-saving intent and throughput intent. Since the production entity performs management actions (such as symbol shutdown) to achieve the energy-saving intent, the throughput decreases and the throughput intent target cannot be achieved. At this time, the production entity can believe that the reason why the throughput intent target is not achieved is that the throughput intent conflicts with the energy-saving intent. Therefore, the production entity can also feed back the reason for failing to achieve the network management intent target to the consumer entity to improve the management method of the network management intent.

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

[0141] 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 managed entity set, the second management action group can be executed to achieve the goal of the network management intention within the scope of the managed entity subset. In other words, the production entity can determine and execute the second management action group, and the first management action group and the second management action group may contain one or more identical actions, which is not particularly limited in this application. In order to facilitate understanding of the embodiments of the present application, the following mainly uses the way in which the production entity executes the second management action group as an example.

[0142] The production entity may determine the second management action group in a variety of ways. Exemplarily, the production entity may determine the network resources within the managed entity subset for achieving the goal of the network management intent based on the managed entity subset, and execute the second management action group based on the network resources. Taking the throughput intent as an example, the production entity may 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 instructions of the action group to the managed entities in the managed entity subset based on the second management action group. For example, the production entity may 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 action time period, the production entity can determine the network resources within the managed entity subset within the action time period that can be used to achieve the goal of network management intent, and determine and execute the second management action group based on the network resources. Therefore, the present application provides a more flexible way to manage network management intent.

[0143] In some implementations, the production entity may also obtain guarantee strength information, and the production entity may determine the network resources within the managed entity subset that can be used to achieve the goal 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 currently being executed by the production entity. For example, the production entity simultaneously maintains the execution of the throughput intention and the energy-saving intention, and the first management action group is used to achieve the goal of the throughput intention within the managed entity set. When the production entity determines that the execution of the first management action group fails to achieve the goal of the throughput intention within 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 occupy the network resources used to achieve the goal 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. Among them, in an embodiment of the present application, the production entity executes 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, the production entity executes carrier shutdown, which is not conducive to achieving the goal of the throughput intention. 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.

[0144] Therefore, based on the present 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 so that the goal of the network management intention within the scope of the managed entity subset is achieved, instead of directly deleting or suspending the entire network management intention, thereby providing a flexible way to manage network management intentions.

[0145] The above describes a method in which, after determining that the execution of the first management action group fails to achieve the goal of network management intent within the scope of the managed entity set, the production entity executes the second management action group to achieve the goal of network management intent within the scope of the managed entity subset. Figure 4 and Figure 5 Two possible ways of interaction between consumer and producer entities are described.

[0146] Figure 4 It is a schematic flowchart of a method for implementing a network management intention provided in an embodiment of the present application.

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

[0148] This request message contains a managed entity subset. For a description of the managed entity subset, see the above Figure 3 The description is not repeated here.

[0149] Exemplarily, the request message is used to request the 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, the network management intent includes a managed entity set, and the managed entity set includes a managed entity subset. For example, the intent creation request message may include a network management intent (e.g. Figure 1 The network management intent 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 and the subset of managed objects. Alternatively, the request message includes the network management intent 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 intent. This is not particularly limited in the present application. For a more detailed description of the set of managed objects and the subset of managed objects, please refer to the above. Figure 3 The description in will not be repeated here.

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

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

[0152] The production 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 production 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, then the production entity can feedback a message of the managed entity subset error to the consumer entity. If the production entity determines that the managed entity subset does not exceed the scope of the managed entity set, then the production entity can proceed with the subsequent process.

[0153] It is understandable that the production entity may also perform a feasibility check on the request message. Exemplarily, 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 perform the first management action group based on the method described above. If the production entity detects that the request message cannot be successfully interpreted, such as a grammatical error, the production entity may send feedback indicating the grammatical error to the consumer entity.

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

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

[0156] If the production entity determines in step S402 that the creation intention is not feasible, such as the managed entity subset exceeds the scope 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 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 refer to the reason for the failure of the schematic diagram creation (such as the managed object subset exceeds the scope or the information expression error, etc.), which is not particularly limited in this application.

[0157] It is understandable that if the production entity detects that the creation intention is feasible in step S402, in other words, 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 feedback that the creation intention is feasible, or the response message contains information indicating that the creation intention is feasible. Or the production entity may not perform step S403. This application does not specifically limit this.

[0158] 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 managed entity subset exceeds the scope of the managed entity set based on the response message, then the consumer entity can adjust the scope of the managed entity subset and resend a request message to the production entity requesting to create a network management intention or requesting to modify the 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 repeated here.

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

[0160] The production entity may execute a first management action group based on the managed entity set, where 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 above Figure 3 The description in will not be repeated here.

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

[0162] For a more detailed explanation of the failure of the production entity to determine the network management intent within the scope of the managed entity set, see above. Figure 3 The description in will not be repeated here.

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

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

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

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

[0167] In some embodiments, the intent report may also include the indicator values ​​of the performance indicators within the managed entity set excluding the managed entity subset. For example, the intent report may include the throughput value within the managed entity set excluding the managed entity subset. Thus, the consumer entity can improve the management method of the network management intent based on the overall achievement of the managed entity set.

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

[0169] Therefore, based on the present 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 providing a flexible management method for network management intentions.

[0170] above Figure 4 A method for carrying a managed entity subset in a request message is introduced. In an embodiment of the present application, the consuming entity may also send a managed entity subset to the producing entity after the producing entity determines that the target of the network management intention within the managed entity set cannot be achieved. Figure 5 This method is described and introduced.

[0171] Figure 5 It is a schematic flowchart of another method for implementing network management intention provided in an embodiment of the present application.

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

[0173] The 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, and the network management intent includes a set of managed entities. For example, the intent creation request message may include a network management intent (e.g. Figure 1 The data structure shown), the network management intent may include a set of managed objects, such as the constraints or conditions represented by the object context in the network management intent may be used to determine the set of managed objects.

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

[0175] The production entity may perform a feasibility check on the request message. Exemplarily, 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 it is detected that the request message can be successfully interpreted, the production entity may perform the first management action group based on the method described above. If the production entity detects that the request message cannot be successfully interpreted, such as a grammatical error, the production entity may send feedback indicating the grammatical error to the consumer entity.

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

[0177] 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 above Figure 4 The description in S403 is not repeated here.

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

[0179] The production entity may execute a first management action group based on the managed entity set, where 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 above Figure 3 The description in will not be repeated here.

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

[0181] For a more detailed explanation of the failure of the production entity to determine the network management intent within the scope of the managed entity set, see above. Figure 3The description in will not be repeated here.

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

[0183] The notification information is used to indicate that the target of the network management intention has not been achieved within the scope of the managed entity set. Exemplarily, the notification information may indicate the achievement of the network management intention by the first management action group of the consumer entity. For example, the notification information may include the indicator value of the performance indicator within the scope of the managed entity set. For example, the target of the network management intention includes a performance indicator as a throughput indicator. For example, if the target of the network management intention is that the average downlink throughput is greater than or equal to 5Mbps, then the notification information may include the throughput value within the scope of the managed entity set.

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

[0185] 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. For another example, the consuming entity may determine the managed entity subset based on the usage scenario of the network management intent. For more information on how to determine the managed entity subset, please refer to the above. Figure 3 The description in will not be repeated here.

[0186] 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, the object context includes the managed entity subset, and 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.

[0187] S508, the production entity executes a second management action group to achieve the goal of network management intention within the managed entity subset.

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

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

[0190] For a more detailed description of intent reporting, please refer to the above Figure 4 The description of step S407 is omitted here.

[0191] Therefore, based on the present 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 providing a flexible management method for network management intentions.

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

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

[0194] See also Figure 6 , as an example, Figure 6 1 is a schematic diagram of a communication device 10 provided in an embodiment of the present application. The device 10 includes a transceiver unit 11 and a processing unit 12. The transceiver unit 11 can be used to implement a corresponding communication function. The transceiver unit 11 can also be called a communication interface or a communication unit. The processing unit 12 can be used to process data or information.

[0195] Optionally, the device 10 further includes a storage unit, which can be used to store instructions and / or data, and 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.

[0196] In a 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.

[0197] In a first possible implementation, the processing unit 12 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; execute the first management action 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. Optionally, the transceiver unit 11 is used to receive the managed entity subset.

[0198] The device 10 can implement the steps or processes performed by the production entity in the method embodiment according to the embodiment of the present application, and the device 10 may include a unit for executing the method performed by the production entity in the method embodiment of the present application. The specific process of each unit performing the above corresponding steps has been described in detail in the above method embodiments, and for the sake of brevity, it will not be repeated here.

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

[0200] The first possible implementation method is that the processing unit 12 determines a managed entity subset, the managed subset is a subset of the managed entity set of the network management intention, wherein the managed entity set includes 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 that the goal of the network management intention is achieved 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 11 is used for the managed entity subset.

[0201] The device 10 can implement the steps or processes performed by the consumer entity in the method embodiment according to the embodiment of the present application, and the device 10 may include a unit for executing the method performed by the consumer entity in the method embodiment of the present application. The specific process of each unit performing the above corresponding steps has been described in detail in the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0202] 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 may 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 repeated here.

[0203] The device 10 of each of the above schemes has the function of implementing the corresponding steps performed by the communication equipment (such as a production entity, and also such as a consumption entity) in the above method. The function can be implemented by hardware, or by hardware executing the corresponding software implementation. The hardware or software includes at least one module corresponding to the above function; for example, the transceiver unit can be replaced by a transceiver (for example, the 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.

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

[0205] It should be pointed out that Figure 6 The device in the above-mentioned embodiment may be a device, or a chip or a 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 or a microprocessor or an integrated circuit integrated on the chip. This is not limited here.

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

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

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

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

[0210] Alternatively, if Figure 7 As shown, the device 20 further includes a transceiver 23, and the transceiver 23 is used for receiving and / or sending signals. For example, the processor 21 is used to control the transceiver 23 to receive and / or send signals.

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

[0212] For example, the processor 21 is used to execute the computer program or instructions stored in the memory 22 to implement the relevant operations of the production entity in the above various method embodiments. Figure 3 The method performed by the production entity in the illustrated embodiment.

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

[0214] For example, the processor 21 is used to execute the computer program or instructions stored in the memory 22 to implement the relevant operations of the consumer entity in each of the above method embodiments. Figure 3 The method performed by the consuming entity in the illustrated embodiment.

[0215] It is understandable that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or 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 the processor may also be any conventional processor, etc.

[0216] It can also be understood that the memory mentioned in the embodiments of the present application can be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory can 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 can 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 connection dynamic random access memory (SLDRAM) and direct rambus RAM (DR RAM).

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

[0218] Memory described herein is intended to include, without being limited to, these and any other suitable types of memory.

[0219] See also Figure 8 , as an example, Figure 8 Schematic diagram of a chip system 30 provided in an embodiment of the present application. The chip system 30 (or also referred to as a processing system) includes a logic circuit 31 and an input / output interface 32 .

[0220] Among them, the logic circuit 31 can be a processing circuit in the chip system 30. The logic circuit 31 can be coupled to the storage unit and call the instructions in the storage unit so that the chip system 30 can implement the methods and functions of each embodiment of the present application. The input / output interface 32 can 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.

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

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

[0223] For example, the logic circuit 31 is used to implement the processing-related operations performed by the production entity in the above method embodiment, such as: Figure 3 The processing-related operations performed by the production entity in the embodiment shown; 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 embodiment, such as, Figure 3 The production entity in the illustrated embodiment performs sending and / or receiving related operations.

[0224] As another solution, the chip system 30 is used to implement the operations performed by the consumer 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 consumer entity in the above method embodiment, such as: Figure 3 The processing-related operations performed by the consuming entity in the illustrated embodiment; the input / output interface 32 is used to implement the sending and / or receiving-related operations performed by the consuming entity in the above method embodiment, such as, Figure 3 The consuming entity in the illustrated embodiment performs sending and / or receiving related operations.

[0226] An embodiment of the present application also 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.

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

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

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

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

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

[0232] In the several embodiments provided in the present 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. There may be other division methods in actual implementation, 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.

[0233] 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 devices. 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 a website site, 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 to another website site, computer, server or data center. 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 contains 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), etc. For example, the aforementioned available medium includes, but is not limited to, various media that can store program codes, 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.

[0234] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope 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