Management method and management apparatus for network management intent, and system
By automatically executing or pausing action groups in the network management service production entity and responding to trigger and pause conditions, the problems of low network management intention management performance and high transmission resource consumption in the prior art are solved, and flexible and efficient networks are realized manage.
Patent Information
- Application Number
- PCT/CN2024/072016
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-11
- Filing Date
- 2024-01-12
- Publication Date
- 2024-11-14
AI Technical Summary
In the prior art, the management performance of network management intentions is low, frequent signaling interactions are required, resulting in large consumption of transmission resources, and it is difficult to achieve flexible management.
By receiving trigger conditions and pause conditions associated with network management intent in the network management service production entity, automatically execute or pause action groups, reduce signaling dependence between consumer entities and production entities, and realize flexible management of action groups and Multiple executions and pauses.
It improves the management performance of network management intentions, reduces the consumption of transmission resources, enhances the flexibility and efficiency of management, especially in frequent demand scenarios.
Smart Images

Figure CN2024072016_14112024_PF_FP_ABST
Abstract
Description
A management method, management device and system for network management intention
[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on May 11, 2023, with application number 202310532312.6 and application name “A management method, management device and system for network management intentions”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communication technology, and more particularly, to a method, device, and system for managing network management intent. Background Art
[0003] With the advancement of network resource management, network management service consumers no longer need to directly manage network resources. Instead, they can send messages to network management service producers, enabling them to execute network management intent, aiming to achieve the desired performance targets for network devices within a specific scope. This approach to managing network management intent typically requires frequent signaling between consumers and producers.
[0004] Therefore, how to improve the management performance of network management intentions is a technical problem that needs to be solved urgently.
[0005] Summary of the Invention
[0006] The present application provides a network management intent management method, management device and system, which can improve the management performance of network management intent.
[0007] In a first aspect, a method for managing network management intent is provided. The method can be executed by a network management service production entity or a chip within the network management service production entity. The method includes: receiving a trigger condition associated with the network management intent, the trigger condition being a condition for triggering execution of an action group, the action group including at least one network management action for achieving at least one goal in the network management intent; and initiating execution of the action group in response to determining that the trigger condition is satisfied.
[0008] Based on this technical solution, the production entity can start executing the action group in response to determining that the trigger condition is met, rather than relying on signaling between the consumer entity and the production entity to trigger the execution of the action group, which can improve the management performance of the network management intention.
[0009] In combination with the first aspect, in some implementations of the first aspect, the trigger condition is a constraint condition on a performance indicator of a managed entity with respect to network management intent.
[0010] Based on this technical solution, network management intent can be configured with multiple types of trigger conditions to achieve flexible management of network management intent.
[0011] In combination with the first aspect, in certain implementations of the first aspect, receiving a trigger condition associated with a network management intention includes: receiving a first request message, the first request message is used to request creation of a network management intention, the first request message includes the network management intention and the trigger condition, or the first request message includes the network management intention, the network management intention includes the trigger condition; or, receiving a second request message, the second request message is used to request modification of the network management intention, the second request message includes an identifier of the network management intention and the trigger condition.
[0012] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: receiving a pause condition associated with the network management intention, the pause condition being a condition for pausing the action group; and suspending execution of the action group in response to determining that the pause condition is met.
[0013] Based on this technical solution, the production entity can suspend the execution of the action group in response to determining that the suspension condition is met, rather than relying on signaling between the consumption entity and the production entity to suspend the execution of the action group, which can reduce the consumption of transmission resources.
[0014] In combination with the first aspect, in certain implementations of the first aspect, the suspension condition is a constraint condition on a performance indicator of a managed entity with respect to network management intent.
[0015] Based on this technical solution, network management intent can be configured with various types of pause conditions to achieve flexible management of network management intent.
[0016] In combination with the first aspect, in certain implementations of the first aspect, receiving a pause condition associated with a network management intent includes: receiving a third request message, the third request message is used to request creation of a network management intent, the third request message includes the network management intent and the pause condition; or receiving a fourth request message, the fourth request message is used to request modification of the network management intent, the fourth request message includes an identifier of the network management intent and the pause condition.
[0017] In combination with the first aspect, in certain implementations of the first aspect, after pausing execution of the action group, the method further includes: in response to determining that the trigger condition is satisfied, resuming execution of the action group.
[0018] Based on this technical solution, the production entity can execute and pause the execution of the action group multiple times. This process does not rely on signaling between the consumer entity and the production entity. Especially in scenarios where there is frequent demand for network management intentions, the consumption of transmission resources can be reduced.
[0019] In combination with the first aspect, in certain implementations of the first aspect, in response to determining that the trigger condition is met and after starting to execute the action group, the method further includes: sending first report information, the first report information indicating that the action group enters a state of being executed.
[0020] Based on this technical solution, the production entity can report to the consumption entity that the action group has entered the executed state, so that the consumption entity can know the running status of the current network management intention.
[0021] In combination with the first aspect, in certain implementations of the first aspect, in response to determining that the pause condition is met, after suspending execution of the action group, the method further includes: sending second report information, the second report information indicating that the action group enters a suspended state.
[0022] Based on this technical solution, the production entity can report to the consumption entity that the action group has entered a suspended state, so that the consumption entity can be aware of the running status of the current network management intention.
[0023] In combination with the first aspect, in certain implementations of the first aspect, at least one target is all targets in all expectations in the network management intent; or, at least one target is all targets in one expectation in the network management intent; or, at least one target is one target in one expectation in the network management intent.
[0024] Based on this technical solution, when the network management intention includes at least one intention expectation and an intention expectation includes at least one expected target, the trigger condition can be associated with the network management intention, the intention expectation or the expected target, so that different intention expectations or expected targets support the configuration of different trigger conditions, thereby enabling flexible management of network management intentions.
[0025] In a second aspect, a method for managing network management intent is provided. The method can be executed by a network management service consuming entity or a chip within the network management service consuming entity. The method includes: generating a trigger condition associated with the network management intent, the trigger condition being a condition for triggering execution of an action group, the action group including at least one network management action for achieving at least one goal in the network management intent; and sending the trigger condition.
[0026] Regarding the beneficial technical effects of various implementation methods of the second aspect, please refer to the description of the relevant implementation methods of the first aspect and will not be repeated here.
[0027] In combination with the second aspect, in some implementations of the second aspect, the trigger condition is a constraint condition on a performance indicator of a managed entity with respect to network management intent, or the trigger condition is a periodic constraint condition.
[0028] In combination with the second aspect, in certain implementations of the second aspect, sending a trigger condition includes: sending a first request message, the first request message is used to request the creation of a network management intention, the first request message includes the network management intention and the trigger condition, or the first request message includes the network management intention, and the network management intention includes the trigger condition; or, sending a second request message, the second request message is used to request the modification of the network management intention, and the second request message includes an identifier of the network management intention and the trigger condition.
[0029] In combination with the second aspect, in certain implementations of the second aspect, the method further includes: sending a pause condition of the network management intention, where the pause condition is a condition for pausing the action group.
[0030] In combination with the second aspect, in certain implementations of the second aspect, the suspension condition is a constraint condition on a performance indicator of a managed entity with respect to network management intent.
[0031] In combination with the second aspect, in certain implementations of the second aspect, sending a pause condition includes: sending a third request message, the third request message is used to request creation of a network management intention, the third request message includes the network management intention and the pause condition; or sending a fourth request message, the fourth request message is used to request modification of the network management intention, the fourth request message includes an identifier of the network management intention and the pause condition.
[0032] In combination with the second aspect, in some implementations of the second aspect, the method further includes: receiving first report information, where the first report information indicates that the action group enters an executed state.
[0033] In combination with the second aspect, in some implementations of the second aspect, the method further includes: receiving second report information, where the second report information indicates that the action group enters a paused state.
[0034] In combination with the second aspect, in certain implementations of the second aspect, at least one target is all targets in all expectations in the network management intent; or, at least one target is all targets in one expectation in the network management intent; or, at least one target is one target in one expectation in the network management intent.
[0035] In a third aspect, the method can be performed by a network management service consuming entity or a chip within the network management service consuming entity, or a network management service producing entity or a chip within the network management service producing entity. The method includes: sending a trigger condition associated with a network management intent; receiving a trigger condition associated with the network management intent, where the trigger condition is a condition for triggering execution of an action group, where the action group includes at least one network management action for achieving at least one goal in the network management intent; and initiating execution of the action group in response to determining that the trigger condition is satisfied.
[0036] Regarding the beneficial technical effects of various implementation methods of the third aspect, please refer to the description of the relevant implementation methods of the first aspect and will not be repeated here.
[0037] In combination with the third aspect, in certain implementations of the third aspect, the triggering condition is a constraint condition on a performance indicator of a managed entity with respect to network management intent.
[0038] In combination with the third aspect, in certain implementations of the third aspect, sending and receiving trigger conditions associated with network management intentions includes: sending and receiving a first request message, the first request message is used to request the creation of a network management intention, the first request message includes the network management intention and the trigger conditions, or the first request message includes the network management intention, and the network management intention includes the trigger conditions; or, sending and receiving a second request message, the second request message is used to request the modification of the network management intention, the second request message includes the identifier of the network management intention and the trigger conditions.
[0039] In combination with the third aspect, in certain implementations of the third aspect, the method further includes: sending and receiving a pause condition of the network management intention, the pause condition being a condition for suspending the action group; and suspending execution of the action group in response to determining that the pause condition is met.
[0040] In combination with the third aspect, in certain implementations of the third aspect, after pausing execution of the action group, the method further includes: in response to determining that the trigger condition is satisfied, resuming execution of the action group.
[0041] In combination with the third aspect, in certain implementations of the third aspect, in response to determining that the trigger condition is met and after starting to execute the action group, the method further includes: sending and receiving first report information, the first report information indicating that the action group starts to be executed.
[0042] In combination with the third aspect, in certain implementations of the third aspect, in response to determining that the suspension condition is met, after suspending execution of the action group, the method further includes: sending and receiving second report information, the second report information indicating that the action group is suspended.
[0043] In combination with the third aspect, in certain implementations of the third aspect, at least one target is all targets in all expectations in the network management intent; or, at least one target is all targets in one expectation in the network management intent; or, at least one target is one target in one expectation in the network management intent.
[0044] In a fourth aspect, a management device for network management intentions is provided, which includes a transceiver unit and a processing unit. The transceiver unit is used to receive a trigger condition associated with the network management intention, where the trigger condition is a condition for triggering the execution of an action group, and the action group includes at least one network management action for achieving at least one goal in the network management intention; the processing unit is used to start executing the action group in response to determining that the trigger condition is met.
[0045] Regarding the various implementation methods of the fourth aspect and the beneficial technical effects of various implementation methods, please refer to the description of the relevant implementation methods of the first aspect and will not be repeated here.
[0046] In the fifth aspect, a management device for network management intentions is provided, which includes a transceiver unit and a processing unit. The processing unit is used to generate a trigger condition associated with the network management intention, where the trigger condition is a condition for triggering the execution of an action group, and the action group includes at least one network management action for achieving at least one goal in the network management intention; the transceiver unit is used to send the trigger condition.
[0047] Regarding the various implementation methods of the fifth aspect and the beneficial technical effects of various implementation methods, please refer to the description of the relevant implementation methods of the first aspect and will not be repeated here.
[0048] In a sixth aspect, a communication device is provided, wherein the communication device is capable of implementing the first aspect or any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect, or the third aspect or any possible implementation of the third aspect. The functions can be implemented by hardware or by hardware executing corresponding software implementations. The hardware or software includes one or more units corresponding to the above functions.
[0049] In a seventh aspect, a communication device is provided, comprising a processor and a memory. Optionally, the device may further comprise a transceiver. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory, and control the transceiver to transmit and receive signals, so that the communication device performs the method according to the first aspect, or any possible implementation of any aspect of the first aspect.
[0050] Exemplarily, the communication device is a network management service production entity.
[0051] In an eighth aspect, a communication device is provided, comprising a processor and a memory. Optionally, the device may further comprise a transceiver. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory and control the transceiver to transmit and receive signals, so that the communication device performs the method according to the second aspect, or any possible implementation of any aspect of the second aspect.
[0052] Exemplarily, the communication device is a network management service consumption entity.
[0053] In a ninth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is configured to receive data and / or information and transmit the received data and / or information to the processor, and the processor processes the data and / or information. The communication interface is further configured to output the processed data and / or information, so that the method according to the first aspect, or any possible implementation of any aspect of the first aspect, is executed. The communication device may be a chip used in a network management service production network element.
[0054] In a tenth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is configured to receive data and / or information and transmit the received data and / or information to the processor, and the processor processes the data and / or information. The communication interface is further configured to output the processed data and / or information, so that the method according to the second aspect, or any possible implementation of any aspect of the second aspect, is executed. The communication device may be a chip used in a network management service consumption network element.
[0055] In the eleventh aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions. When the computer instructions are executed on a computer, the method in the first aspect, or any possible implementation of any aspect in the first aspect, is executed.
[0056] In the twelfth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions. When the computer instructions are executed on a computer, the method in the second aspect, or any possible implementation of any aspect in the second aspect, is executed.
[0057] In a thirteenth aspect, a computer program product is provided, comprising a computer program code, which, when run on a computer, enables the method according to the first aspect, or any possible implementation of any aspect in the first aspect, to be executed.
[0058] In a fourteenth aspect, a computer program product is provided, comprising a computer program code, which, when run on a computer, enables the method according to the second aspect, or any possible implementation of any aspect in the second aspect, to be executed.
[0059] In the fifteenth aspect, a wireless communication system is provided, comprising the communication device as described in the fourth aspect, and / or the communication device as described in the fifth aspect.
[0060] In the sixteenth aspect, a wireless communication system is provided, comprising a communication device as described in any one or more aspects from the fourth to the fifteenth aspect, or a communication device in any possible implementation of any of these aspects. BRIEF DESCRIPTION OF THE DRAWINGS
[0061] FIG1 shows a schematic structural diagram of an intention IOC;
[0062] FIG2 is a schematic structural diagram of a communication system applicable to an embodiment of the present application;
[0063] FIG3 is a schematic flowchart of a method for managing network management intent provided in an embodiment of the present application;
[0064] FIG4 is another schematic flow chart of a method for managing network management intent provided in an embodiment of the present application;
[0065] 5 to 7 are schematic diagrams of possible communication devices provided in embodiments of the present application. DETAILED DESCRIPTION
[0066] The technical solution in this application will be described below with reference to the accompanying drawings.
[0067] The technical solution of the present application can be applied to various network function virtualization (NFV) systems. The system can describe the current operator's business technology solutions, network construction solutions, and network operation and maintenance methods as patterns and strategies in a standard formal language, and implement the technical solutions and construction solutions based on these patterns and strategies. For example, the technical solution of the present application can be applied to one or more of the following systems: a wireless intent driven network (wIDN) system, an experiential networked intelligence (ENI) system, an intent driven management service (IDMS) system, or an open network automation platform (ONAP) system.
[0068] For the sake of clarity, some terms in the embodiments of this application are explained below.
[0069] 1. Network management, network management services, network management service production entities, and network management service consumption entities
[0070] 1.1 Network Management
[0071] Network management refers to the management of network resources, including but not limited to monitoring, controlling and recording the performance and usage of network resources, and issuing management action groups to network resources (such as devices in the network) based on the detected network conditions to enable the network to operate effectively. For example, network management can be monitoring, testing, configuring, analyzing, evaluating and controlling network resources. Network management can also be timely reporting and handling when a network failure occurs, and coordinating and maintaining the efficient operation of the network system. Among them, network resources are the objects of network management, which can also be called network objects or managed entities. For example, network resources can be base station equipment, routers, switches, core network equipment, etc. In this regard, the embodiments of the present application do not make special limitations. For the convenience of description, the embodiments of the present application are explained using managed entities as an example, but they can be replaced with other objects of network management.
[0072] 1.2 Network Management Services
[0073] A network management service refers to a service that provides network management functions. The service producing entity usually provides the network management functions to the service consuming entity through a network interface (eg, a service-based interface).
[0074] 1.3 Network Management Service Production Entity
[0075] The entity providing the network management service is referred to as the network management service production entity. For example, the capabilities or functions of the network management service production entity may be deployed on a network element, referred to as the network management service production network element. The capabilities or functions of the network management service production entity may also be deployed on other devices, which is not limited in the embodiments of this application. For ease of description, the embodiments of this application use the network management service production entity as an example, but any other device that deploys the capabilities or functions of the network management service production entity may be substituted.
[0076] 1.4 Network Management Service Consumption Entities
[0077] The entity that calls network management is called a network management service consuming entity. For example, the capabilities or functions of the network management service consuming entity can be deployed on a certain network element, which is called a network management service consuming network element. The capabilities or functions of the network management service consuming entity can also be deployed on other devices, which is not limited in this embodiment of the present application. For ease of description, this embodiment of the present application uses the network management service consuming entity as an example, but any other device that deploys the capabilities or functions of the network management service consuming entity can be replaced.
[0078] 2. Network Management Intent (abbreviated as Intent)
[0079] A network management intent refers to a demand for network management services by a network management service consuming entity, and may also be referred to as a network management service demand. This term is not limited in the embodiments of the present application. For example, the network management intent may be an optical dedicated line service intent or an energy-saving intent, such as the intent defined in 3rd Generation Partnership Project (3GPP) standard specification 28.312.
[0080] In the intent-based interaction scenario of this application, there are two main roles: the network management provider entity and the network management service consumer entity. Among them, the network management provider entity can also be called the network management provider, or the intent provider (intent provider), or the intent handler (intent handler), etc. The network management service consumer entity can also be called the network management service consumer, or the intent consumer (intent consumer), or the intent owner (intent owner), etc.
[0081] Among them, the network management service consumption entity can be the caller of the network management service, and can perform operations such as creating, modifying, deleting, and querying network management intent expressions. It can be configured in a network management system (NMS), an element management system (EMS), or network equipment (NE). It can be a management function, a management function entity, a management entity, a network equipment, a network element, etc. This application does not limit this.
[0082] Intents can be applied to network systems to achieve desired performance targets for specific network devices within a specific scope. Intents can express expectations for network systems through formal specifications and descriptive information. Formal specifications can refer to the intent's specific syntax or semantics, while descriptive information can describe the intent's requirements, goals, and constraints.
[0083] An intent may include at least one intent expectation. Each intent expectation may represent the performance requirement of a network management service consuming entity for a specific network object. An intent expectation may consist of at least one expected target and an expected object, and each expected target may represent the performance requirement of a network management service consuming entity for a specific attribute of an expected object. For example, 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 an intent expectation are met, then the intent expectation is achieved.
[0084] An intent may also include an intent context. The intent context may represent constraints or conditions imposed by the network management service consumer on the intent. For example, the network management service consumer may constrain the duration of the intent through the intent context.
[0085] Intents may also include an expected context. The expected context may represent the constraints or conditions that a network management service consumer expects for an intent. For example, the network management service consumer may use the expected context to constrain the expected duration of the intent.
[0086] The intent may also include a target context, which may represent the constraints or conditions imposed by the network management service consumer on a desired target. For example, the network management service consumer may constrain the duration of the desired target through the target context.
[0087] The intent may also include an object context, which may indicate constraints or conditions on the network object to be acted upon by the network management service consumer. For example, the network management service consumer may use the object context to indicate the area where the intended network object is located.
[0088] 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.
[0089] The information element in the intent IOC can use a specific structure to express the demand for network management services. For example, Figure 1 shows a schematic structural diagram of an intent IOC.
[0090] Referring to Figure 1 , the intent IOC includes an intent expectation and an intent context. The intent expectation includes an expected object, an expected target, and an expected context. The expected object includes an expected object context, and the expected target includes a target context. It is understood that non-contextual information elements (such as intent IOC, intent expectation, expected object, or expected target) can include contextual information elements (such as intent context, expected object context, target context, expected context, etc.), and contextual information elements can be used to constrain non-contextual information elements.
[0091] It is understood that Figure 1 is a schematic illustration of the relationship between attributes in an intent IOC. Based on network management service requirements, the intent IOC may also include other attributes, and this application does not specifically limit this. It is also understood that this application does not specifically limit the number of attributes of the same type. For example, an intent IOC may include one or more parallel intent expectation attributes, and an intent expectation may also include one or more parallel desired target attributes.
[0092] 3. Network Management Intent Template
[0093] The network management intent template refers to the templated description information of the network management intent, which can also be called the network management service requirement template. The embodiment of this application does not limit this name. The intent template can be used to specify the syntax and semantics of the various attribute expressions introduced above. For example, the intent template can specify the field type, value type, etc. that can be used for each attribute in the IOC. Exemplarily, the intent template can include intent expectation description information for specifying how the intent expectation is expressed. The intent expectation description information can specify the type of expected target attributes that the intent expectation can contain, such as latency, bandwidth, maximum number of users, etc. The intent expectation description information can also specify the field type of each expected target. For example, the field type of the expected target for latency is a string, the field type of the expected target for bandwidth is a string, and the field type of the expected target for the maximum number of users is an integer. As another example, the intent template can also include intent context description information that specifies how the intent context and the expected context are expressed. The intent context description information can be used to specify the field type of the intent context, etc., and this application does not specifically limit this.
[0094] 4. Intent Expression
[0095] In the embodiment of the present application, the intent expression is an information formula that expresses the network management service intent, and can be the instantiation result of the network management intent template. Consumers of network management intent can instantiate the intent IOC according to the intent template to generate an intent expression, and the instantiated intent expression can be used for specific network services. For example, the intent expression can be represented by a list of a set of attribute and value key-value pairs (for example, a set of [attribute, value]) of the network management service intent.
[0096] Exemplarily, the intent expression includes a performance indicator information instance, a network object information instance, and a context information instance.
[0097] For example, a performance indicator information instance may include the value or value range of the target indicator requirement corresponding to the performance indicator information. For example, if the target indicator requirement corresponding to a performance indicator information template includes a bandwidth parameter, a performance indicator information instance may include a bandwidth parameter value of 20 Mbps, or a bandwidth parameter value range of 10 Mbps to 15 Mbps. For example, if the target indicator requirement corresponding to a performance indicator information template includes a latency parameter, a latency parameter instance may include a latency parameter value of 2 s, or a latency parameter value range of 1 s to 5 s.
[0098] The target network object indicated by the network object information instance is the instantiation result of the target network object indicated by the network object information template. Exemplarily, the target network object indicated by the network object information instance is one of the target network objects indicated by the network object information template, i.e., one of the physical or logical entities that implement the network management service. In this case, the network object information instance indicates a specific network object. For example, the network object information template indicates a network service, while the network object information instance indicates an energy-saving service.
[0099] The context information instance is used to indicate the constraints of the network management intent expression. Exemplarily, the context information instance includes the constraint parameters of the network management intent expression. For example, the context information instance may include the source and sink information corresponding to the target network object indicated by the network object instance.
[0100] Intent expectation information instances include performance indicator information instances and network object information instances.
[0101] In the embodiment of the present application, the "intention" transmitted through the message refers to the intention expression.
[0102] 5. Intent Examples
[0103] 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).
[0104] The network management intent processing process is used to process network management intent expressions. For example, the network management intent processing process may include an identifier that identifies the process; computing resources that are used to perform operations such as network management intent translation and database query (e.g., a semantic knowledge base); and storage resources that are used to store network management intent expressions and network management intent translation results.
[0105] 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.
[0106] 6. Network Management Action Group (actions)
[0107] A network management action group is one or more network management actions generated by a network management service producer based on an intent expression. The network management service producer executes one or more network management actions to satisfy the intent of a network management service consumer. A network management action group can also be referred to as a management operation or an intent operation. A network management action group can be a set of operational instructions for a desired object (e.g., a physical or logical entity in the network system intended to act on), containing one or more instructions. For example, adjusting the antenna tilt of a base station or turning on the energy-saving switch of a cell can be performed.
[0108] A network management service production entity can generate multiple management action groups based on intent expressions. During execution, the network management service production entity can select some of these management action groups to execute at a time. In other words, the management action groups generated by the network management service production entity based on the intent expression are selectable operations that can be used to satisfy the intent. The network management service production entity may select one of these network management action groups to execute to satisfy the intent, or it may select multiple network management action groups to execute to satisfy the intent.
[0109] The above describes the relevant terms involved in the embodiments of the present application. The following describes the application scenarios applicable to the embodiments of the present application in conjunction with Figure 1.
[0110] Figure 2 is a schematic structural diagram of a communication system applicable to an embodiment of the present application. First, the devices that may be involved in the communication system are described.
[0111] 1. Network Management Service Consuming Entity 210: This entity can be used to invoke management services, or intent services, to manage the network system. For example, the network management service consuming entity 210 can instantiate an intent template, set intent IOCs, generate an intent expression, and send the intent expression to the network management service producing network element 220 to implement expectations for the network system.
[0112] 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.
[0113] 2. Network management service production entity 220: can be used to provide management services. For example, the network management service production entity 220 can receive intent expressions from the network management service consumption entity 210 and perform intent translation, intent management, and intent execution and maintenance processes based on the intent expressions.
[0114] 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.
[0115] The above-mentioned entity can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (for example, a cloud platform). It is understandable that the above-mentioned entity can be implemented by one device, or it can be implemented by multiple devices together. In addition, the above-mentioned entity can also be a functional module within a system, such as a network management system (NMS), an equipment management system (EMS), or a functional module within a device, such as one or more functional modules within a network equipment (NE), and the network equipment can be a base station or a core network element.
[0116] 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.
[0117] As another example, the network management service consumption entity 210 can be deployed in the EMS, and the network management service production entity 220 can be deployed in different NEs. The interaction between the network management service consumption entity 210 and the network management service production entity 220 can be carried out through information exchange through the interface between the NMS and the EMS.
[0118] 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.
[0119] For the sake of simplicity, the network management service consumption entity is referred to as the consumption entity, and the network management service production entity is referred to as the production entity.
[0120] FIG3 is a schematic flowchart of a method for managing network management intent provided in an embodiment of the present application.
[0121] S310: The consumer entity sends a trigger condition associated with the network management intention to the producer entity.
[0122] Correspondingly, the production entity receives the trigger condition from the consumption entity.
[0123] The trigger condition is a condition for triggering the execution of an action group, which includes at least one network management action for achieving at least one goal in a network management intent. Thus, the production entity can initiate (or resume) execution of the action group in response to determining that the trigger condition is satisfied, rather than relying on signaling between the consumer and production entities to trigger the execution of the action group. This can reduce transmission resource consumption, particularly in scenarios where the network management intent is frequently required.
[0124] The trigger condition may include various types of constraints for triggering the execution of an action group. Exemplarily, the trigger condition may be a constraint on the performance indicator of the managed entity regarding the network management intention, such as an energy-saving type of network management intention, and the constrained performance indicator may be an energy-saving related performance indicator (such as physical resource block utilization, activity factor, and other network capacity indicators). When the performance indicator is greater than or equal to a certain threshold, the production entity determines that the trigger condition is met, and in response to the trigger condition, executes an energy-saving related action group (such as shutting down the power amplifier of the RF module, shutting down the carrier, and other management actions). As another example, the trigger condition is a periodic constraint. For example, the trigger condition indicates the period of the production entity executing the action group, such as the trigger condition instructs the production entity to execute the energy-saving related action group at 10 o'clock every night. As another example, the trigger condition may include constraints on the performance indicators of the managed entity with respect to the network management intention and periodic constraints. When both the constraints on the performance indicators and the periodic constraints are met, the production entity executes the action group. For example, if the performance indicator of the production entity is greater than or equal to a specific threshold between 10 pm and 9 am the next day, the production entity determines that the trigger condition is met and executes the action group in response to the satisfaction of the trigger condition. This application does not specifically limit this.
[0125] It is understandable that the name “trigger condition” is merely exemplary and not limiting. For example, it is also called “activation condition”, “start condition”, “start condition”, etc.
[0126] The consuming entity can use a variety of methods to send trigger conditions to the producing entity. For example, the consuming entity can carry the trigger condition in a first request message or a second request message, wherein the first request message is used to request the creation of the network management intent, and the second request message is used to modify the network management intent. Alternatively, the consuming entity can also carry the trigger condition in other messages used for intent management. Alternatively, the consuming entity can send the trigger condition as a separate message to the producing entity. The consuming entity can express its requirements for the managed entity through the trigger condition. For example, when the network management intent in the managed entity is suspended, an intent conflict occurs, or the expected goal cannot be achieved for a long time, the consuming entity can send the trigger condition so that the producing entity can respond to the determination that the trigger condition is met and execute the action group (such as starting to execute or resume executing the action group).
[0127] Optionally, the first request message is a create request message, and the second request message is a modify request message.
[0128] When the consumer entity carries the trigger condition in the first request message (such as the intent creation request message), the first request message may include the network management intent, and the network management intent may be expressed as an instantiated intent IOC (as shown in Figure 1). In this case, in one possible implementation, the first request message includes the intent IOC and the trigger condition. At this time, the trigger condition may be associated with the network management intent, and the action group triggered by the trigger condition is used to achieve all desired goals in the network management intent. In another possible implementation, the first request message includes the intent IOC, and the intent IOC includes the trigger condition.
[0129] For example, the intent IOC includes intent expectations and intent context, and the intent context includes trigger conditions. At this time, the action group triggered by the trigger conditions can be used to achieve all the expected goals in the network management intent.
[0130] For another example, the intent IOC includes the intent expectation, the intent expectation includes the expectation context, and the expectation context includes the trigger condition. At this time, the action group triggered by the trigger condition can be used to achieve all the goals of the intent expectation.
[0131] For another example, the intent IOC includes the intent expectation, the intent expectation includes the expected target, the expected target includes the target context, and the target context includes the trigger condition. At this time, the action group triggered by the trigger condition can be used to achieve the expected target.
[0132] When the consumer entity carries the trigger condition in the second request message (such as the intent modification request message), the second request message may include the identifier of the network management intent and the trigger condition, and the action group triggered by the trigger condition is used to achieve all the desired goals in the network management intent. Alternatively, the second request message may include the intended expectation or the desired goal (or the identifier of the intended expectation or the desired goal) and the trigger condition, and the action group triggered by the trigger condition is used to achieve the intended expectation or the desired goal. It is understandable that if the modification function is implemented by carrying the modified intent IOC in the second request message, then the trigger condition may also be included in the intent IOC, which will not be elaborated here.
[0133] It is understandable that the intent IOC may include multiple trigger conditions, and multiple trigger conditions may be associated with different intent expectations or expected targets. The trigger conditions associated with different intent expectations or expected targets may be the same or different, and this application does not specifically limit this.
[0134] It is also understood that the trigger condition can be expressed based on the context template of the network management intent. For example, when the trigger condition is a constraint condition on a performance indicator of a managed entity in the network management intent, the trigger condition can include information such as the type of the performance indicator and the performance indicator range. Thus, the production entity can obtain the performance indicator value of the managed entity based on the performance indicator type and determine whether at least one objective of the network management intent has been achieved based on whether the performance indicator value is within the performance indicator range.
[0135] In response to determining that the trigger condition is met, the production entity starts to execute or resumes the execution of the action group. At this time, the action group enters the state of being executed, and the network management intention is in an activated state. The intention being in an activated state can mean that the production entity configures the managed entity based on the purpose of meeting the intention expectation or expected target. Exemplarily, the production entity can determine the management action group based on the intention expectation or expected target, and send the management action group to the managed entity. The managed entity meets the intention expectation or expected target by executing the management action group. For example, the production entity receives an energy-saving intention, and the intended expected target is to reduce the average energy consumption by 30%. When the energy-saving intention is activated, the production entity determines that the managed entity turns off the power amplifier of the RF module based on the intended expected target, and sends the instruction "turn off the power amplifier of the RF module" to the managed entity. The managed entity turns off the power amplifier of the RF module based on the instruction to meet the intended expected target of reducing the average energy consumption by 30%.
[0136] The trigger conditions provided in the embodiment of the present application are described above. Optionally, in the present application, the consumer entity may also send a pause condition to the producer entity by executing the following step S320:
[0137] Optionally, S320, the consuming entity sends a pause condition associated with the network management intention to the producing entity.
[0138] Accordingly, the producing entity receives the pause condition from the consuming entity.
[0139] The pause condition is a condition of the pause action group. Thus, the production entity can respond to determining that the pause condition satisfies the pause action group without relying on signaling between the consumer entity and the production entity to trigger the pause action group, thereby reducing transmission resource consumption.
[0140] The pause condition may include various types of constraints for triggering the pause action group. The pause condition may be similar to the trigger condition. For example, the pause condition may be a constraint on the performance indicator of the managed entity with respect to the network management intention, such as an energy-saving type of network management intention. The constrained performance indicator may be an energy-saving related performance indicator (such as physical resource block utilization, activity factor, and other network capacity indicators). When the performance indicator is less than or equal to a certain threshold, the production entity determines that the pause condition is satisfied, and suspends the energy-saving related action group in response to the suspension condition. As another example, the pause condition is a periodic constraint. For example, the pause condition indicates the period of the production entity executing the action group. For example, the pause condition indicates that the production entity suspends the energy-saving related action group at 9 a.m. every day. As another example, the pause condition may include constraints on the performance indicators of the managed entity with respect to the network management intention and periodic constraints. When both the constraints on the performance indicators and the periodic constraints are met, the production entity suspends the action group. For example, if the performance indicator of the production entity is less than or equal to a certain threshold between 9 a.m. and 10 p.m. every day, the production entity determines that the pause condition is met, and suspends the action group in response to determining that the pause condition is met. This application does not specifically limit this.
[0141] It is understandable that the name "pause condition" is only exemplary and not limiting. For example, it can also be called "deactivation condition", "end condition", "suspend condition" and so on.
[0142] The consuming entity may also use a variety of methods to send a pause condition to the producing entity. It is understandable that the way in which the consuming entity sends the pause condition may be similar to the way in which the trigger condition is sent. For example, the consuming entity may carry the pause condition in a third request message (such as an intent to create a request message) or a fourth request message (an intent to modify a request message). Alternatively, the consuming entity may also carry the pause condition in other messages used for intent management. Alternatively, the consuming entity may send the pause condition as a separate message to the producing entity. It is understandable that the pause condition may also be included in the intent IOC, and the way in which the pause condition is associated with the network management intent, intent expectation or expected target is similar to the description above for the trigger condition. Please refer to the relevant description in S310 above, which will not be repeated here.
[0143] When the production entity suspends the action group in response to determining that the suspension condition is met, the action group enters a suspended state, and the network management intention is in a deactivated state. The deactivated state of the intention means that the production network element retains the context information of the intention and suspends maintaining the intention expectation or the intention expectation target to be met. For example, when the intention is in an inactive state, even if the intention expectation target is not met, the production network element will not determine the management action group based on the intention expectation target. For example, when the energy-saving intention is converted from an active state to an inactive state, the production network element does not need to maintain the intention expectation target of reducing the average energy consumption by 30%. The production network element can instruct the managed entity to turn on the power amplifier of the RF module, or it can keep the configuration before the inactive state unchanged (no additional instructions are issued based on the intention).
[0144] S330 : In response to determining that the trigger condition is met, the production entity executes the action group.
[0145] In response to determining that the trigger condition is met, the production entity may start executing the action group or resume executing the action group (for example, the action group was previously in a suspended state). The production entity may configure the managed entity to activate the network management intent and set the intent state of the network management intent to an activated state. For example, the production entity may determine a management action group for achieving the intended expectation or expected goal of the network management intent, and send the management action group to the managed entity, which then executes the management action group to meet the intended expectation or expected goal.
[0146] The way in which the production entity executes the action group can be related to the trigger condition. For example, if the trigger condition is associated with a network management intent, the production entity selects a management action group that can meet all the goals of all expectations. If the trigger condition is associated with a specific expectation of the network management intent, the production entity can select a management action group that can meet all the goals of the expectation. If the activation trigger condition is associated with a specific goal of a specific expectation of the network management intent, the production entity can select a management action group that can meet the specific goal.
[0147] Optionally, S340, the production entity sends first report information to the consumption entity.
[0148] Correspondingly, the consuming entity receives the first report information from the producing entity.
[0149] The production entity may send a first intention report to the consumption entity after each execution of the action group in response to the trigger condition. The first intention report indicates that the network management intention enters an activated state, or indicates that the action group for achieving at least one goal enters an executed state (or a running state). For example, the first intention report may include indication information, which indicates that the network management intention enters an activated state, or indicates that the action group for achieving at least one goal enters an executed state (or a running state).
[0150] Optionally, the first intent report also includes an identifier for determining the satisfied trigger condition. For example, if the network management intent is configured with at least one trigger condition, the producing entity can report to the consuming entity which trigger condition caused the currently executed action group to be executed. This allows the consuming entity to understand the current operational status of the network management intent.
[0151] Optionally, in S350 , the production entity suspends execution of the action group in response to determining that the suspension condition is met.
[0152] In response to determining that the suspension condition is met, the production entity may suspend execution of the action group, causing the action group to enter a suspended state and the network management intent to be deactivated. The production entity may retain contextual information of the network management intent and suspend execution of the action group to maintain the intent expectation or to ensure that the intent expectation target is met. For details on how the production entity suspends execution of the action group, refer to the description of the deactivated state in step S320. This description is not repeated here.
[0153] Optionally, in S360, the production entity sends second report information to the consumption entity.
[0154] Correspondingly, the consuming entity receives the second report information from the producing entity.
[0155] The production entity may send a second intention report to the consumption entity after each suspension of the action group. The second intention report indicates that the network management intention is in a deactivated state, or indicates that the action group for achieving at least one goal has entered a state where execution is suspended. For example, the second report information may include indication information, which indicates that the network management intention is in a deactivated state, or indicates that the action group for achieving at least one goal has entered a state where execution is suspended.
[0156] Optionally, the second report information also includes an identifier for determining the suspension condition that is satisfied. For example, if the network management intent includes at least one suspension condition, the production entity can report to the consumption entity which suspension condition the current action group is suspended in response to. In addition, the second report information can also include a trigger condition identifier, which indicates the previous execution state of the action group based on which trigger condition is satisfied and executed. In other words, the second report information can include a set of trigger conditions and a suspension condition identifier.
[0157] Optionally, after the production network element suspends execution of the action group, the production entity resumes execution of the action group in response to determining that the trigger condition has been met. It is understood that after suspending execution of the action, the production entity may continue to check whether the trigger condition has been met. In other words, the production entity may return to step S330 to resume execution. The production entity may execute and resume the action group multiple times within the duration of the network management intent.
[0158] Based on this technical solution, the production entity can start executing the action group in response to determining that the trigger condition is met. In a scenario where there is frequent demand for the network management intent, the production entity can start or resume executing the action group multiple times based on the trigger condition, rather than relying on the consumer entity to send network management intent creation requests to the production entity multiple times to implement multiple executions of the action group, thereby reducing the consumption of transmission resources.
[0159] The above describes the manner in which an action group is executed in response to a trigger condition in an embodiment of the present application. To facilitate understanding of the embodiment of the present application, the following description is made by taking an example in which a consumer entity sends a create intent request message carrying a trigger condition.
[0160] FIG4 is a schematic flowchart of a method for managing network management intent provided in an embodiment of the present application.
[0161] S401: The consumer entity sends a create intent request message to the producer entity. Correspondingly, the producer entity receives the create intent request message from the consumer entity.
[0162] The intent creation request message may request the production entity to create a network management intent. Exemplarily, the intent creation request message may include an intent IOC of the network management intent, and the intent IOC may include a trigger condition. The IOC may also include a pause condition.
[0163] For the description of the triggering conditions and the pause conditions, please refer to the relevant description in FIG2 , which will not be repeated here.
[0164] Optionally, the intent creation request message may also include conflict management indication information, which indicates that if the network management intent conflicts with other currently executed network management intents, a network management action for achieving at least one goal of the network management intent will not be performed. The conflict between the network management intent and other currently executed network management intents means that the intended expected goal of the network management intent and the intended expected goals of other currently executed network management intents cannot be met at the same time. To facilitate understanding of the embodiments of the present application, several possible conflict scenarios between the network management intent and other currently executed network management intents are exemplified below.
[0165] In the first possible scenario, the intent expectation or target associated with the activation trigger condition semantically conflicts with other currently executed network management intents. For example, the trigger condition for an energy-saving network management intent is that the physical resource block utilization is less than or equal to 20%. However, the intent expectation target of the network management intent currently executed by the production entity to ensure user experience is that the physical resource block utilization is greater than 40%. In this case, the production entity can semantically determine that this network management intent conflicts with other network management intents. Upon determining that the trigger condition is met, the production entity can determine not to execute the action group based on the conflict indication information and can send a conflict information to the consumer entity.
[0166] In the second possible scenario, the action group that the production entity starts or resumes based on the trigger condition conflicts with the management action group currently being executed for another network management intent. For example, the production entity determines that the trigger condition is met and, based on the target associated with the trigger condition, determines the management action group to achieve the target, such as shutting down the power amplifier of the RF module. However, the management action group currently being executed for another network management intent is to shut down the power amplifier of the RF module. The production entity can then determine to exit the process of executing the management action group based on the conflict management indication information and send a conflict notification to the consumer entity.
[0167] It is understood that the above is merely an example of a possible conflict situation, and this application does not specifically limit this. It is also understood that the conflict management indication information can be a separate information element sent by the consumer entity to the producer entity, or included in the intent IOC, and this application does not specifically limit this.
[0168] Optionally, in S402 , the production entity performs a validity check based on the intention to create the request message.
[0169] The production entity can check whether the intent to create a request message conforms to the predefined syntax and semantics based on the network management intent template. For example, the consumer entity and the production entity can specify the description information of the trigger conditions and the pause conditions, such as adding a template that specifies how to express the trigger conditions and the pause conditions in the intent template. If the production entity determines that the intent to create a request message does not conform to the provisions of the template, the production entity can inform the consumer entity that the intent to create a request message is invalid, so that the consumer entity resends a valid intent to create a request message; if the production entity determines that the intent to create a request message is valid, the production entity can perform subsequent actions.
[0170] Optionally, in S403, the consumer entity sends a create intent request response message to the producer entity. Correspondingly, the producer entity receives the create intent request response message from the consumer entity.
[0171] The intent creation request response message may indicate whether the network management intent is created successfully. Exemplarily, the intent creation request response message may include an intent identifier of the network management intent, which may be used to mark the network management intent. The intent creation request response message may also indicate information including whether the intent creation is successful. For example, if the production entity determines in step S402 that the intent creation request message is valid, then the information indicates that the creation is successful. If the intent creation request message is determined to be invalid, then the information indicates that the creation is unsuccessful. In this case, the intent creation request response message may also include the reason for the unsuccessful creation, such as which information in the intent creation request response message does not conform to the expression specified in the template. Optionally, the intent creation request response message may also include a template for recommended expression, so that the consumer entity may resend a valid intent creation request message based on the template for recommended expression.
[0172] S404: The production entity determines that the triggering condition is met.
[0173] When it is determined that the event indicated by the trigger condition has occurred or the period has arrived, the production entity determines that the activation trigger condition has been met. For example, if the activation trigger condition is related to a performance indicator of the managed entity, the production entity may obtain the performance indicator value from the managed entity. For example, before step S405, the production entity may send an indicator data subscription request message to the managed entity. This data subscription request message may subscribe to the performance indicator value used to determine whether the activation trigger condition has been met. Thus, the managed entity may return the performance indicator value to the production entity based on the data subscription request message. The production entity may determine that the activation trigger condition has been met based on the performance indicator value and perform the following action S405.
[0174] S405, the production entity executes the action group.
[0175] The production entity can configure the managed entity to start executing the action group or resume executing the action group, so that the action group enters the executed state and the intended state of the network management intent enters the activated state. For example, the production entity can determine a management action group for achieving the intended expectation or expected goal of the network management intent, and send the management action group to the managed entity. The managed entity executes the management action group to meet the intended expectation or expected goal.
[0176] For a more detailed description of how the production entity executes the action group, please refer to the description of step S330 in Figure 3, which will not be repeated here.
[0177] Optionally, in S406, the production entity sends first report information to the consumption entity. Correspondingly, the consumption entity receives the first report information from the consumption entity.
[0178] For the relevant content of the first report information, please refer to the description of step S340 above and will not be repeated here.
[0179] S407: The production entity determines that the suspension condition is met.
[0180] For details on how the production entity determines that the suspension conditions are met, please refer to the description of step S350 above and will not be repeated here.
[0181] S408, the production entity suspends execution of the action group.
[0182] The production entity can retain the contextual information of the network management intent and suspend the maintenance of the intent expectation or the intent expectation target is met. At this time, the action group is in a suspended state and the network management intent enters a deactivated state. For details on how the production entity suspends the execution of the action group, please refer to the relevant description in step S350 above. It will not be repeated here.
[0183] Optionally, in S409, the production entity sends second report information to the consumption entity. Correspondingly, the consumption entity receives the second report information from the production entity.
[0184] For the relevant content of the second report information, please refer to the description of step S360 above and will not be repeated here.
[0185] It is understandable that after suspending the execution of the management action group, the production entity can continue to detect whether the trigger condition is met. In other words, the production entity can return to step S404 to continue execution. The production entity can execute and suspend the network management intent multiple times within the duration of the network management intent.
[0186] Based on this technical solution, the production entity can start executing the action group in response to determining that the trigger condition is met, rather than relying on signaling between the consumer entity and the production entity to trigger the execution of the action group. Especially in scenarios where there is frequent demand for the network management intention, the consumption of transmission resources can be reduced.
[0187] 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.
[0188] Corresponding to the methods provided in the above method embodiments, embodiments of the present application also provide corresponding apparatuses, which include modules for executing the corresponding methods in the above method embodiments. The modules may be software, hardware, or a combination of software and hardware. It is understood that the technical features described in the above method embodiments are also applicable to the following apparatus embodiments.
[0189] Referring to Figure 5 , as an example, Figure 5 is a schematic diagram of a communication device 10 provided in an embodiment of the present application. Device 10 includes a transceiver unit 11 and a processing unit 12. Transceiver unit 11 can be used to implement corresponding communication functions. Transceiver unit 11 can also be referred to as a communication interface or communication unit. Processing unit 12 can be used to process data or information.
[0190] Optionally, the device 10 further includes a storage unit, which can be used to store instructions and / or data. The processing unit 12 can read the instructions and / or data in the storage unit so that the device implements the aforementioned various method embodiments.
[0191] In one possible design, the device 10 can be used to execute the actions performed by the production entity in the above method embodiments. In this case, the device 10 can be a production entity or a component of a production entity. The transceiver unit 11 is used to execute the transceiver-related operations on the production entity side in the above method embodiments, and the processing unit 12 is used to execute the processing-related operations on the production entity side in the above method embodiments.
[0192] In a first possible implementation method, the transceiver unit 11 is used to receive a trigger condition associated with a network management intention, where the trigger condition is a condition for triggering the execution of an action group, and the action group includes at least one network management action for achieving at least one goal in the network management intention; the transceiver unit 11 is used to start executing the action group in response to determining that the trigger condition is met.
[0193] The apparatus 10 can implement the steps or processes performed by the production entity in the method embodiments according to the embodiments of the present application. The apparatus 10 may include units for executing the methods performed by the production entity in the method embodiments according to the embodiments of the present application. The specific processes for each unit to perform the above-mentioned corresponding steps have been described in detail in the above-mentioned method embodiments and will not be repeated here for the sake of brevity.
[0194] 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.
[0195] The first possible implementation method is that the processing unit 12 is used to generate a trigger condition associated with the network management intention, where the trigger condition is a condition for triggering the execution of an action group, and the action group includes at least one network management action for achieving at least one goal in the network management intention; the transceiver unit 11 is used to send the trigger condition.
[0196] The apparatus 10 can implement the steps or processes corresponding to those performed by the consumer entity in the method embodiment according to the embodiment of the present application. The apparatus 10 may include units for executing the method performed by the consumer entity in the method embodiment according to the embodiment of the present application. The specific process of each unit executing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiments and will not be repeated here for the sake of brevity.
[0197] It is understandable that the device 10 here is embodied in the form of a functional unit. The term "unit" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing at least one software or firmware program, a merged logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art will understand that the device 10 may be specifically a production entity in the above-mentioned embodiment, and may be used to execute the various processes and / or steps corresponding to the production entity in the above-mentioned method embodiments; or, the device 10 may be specifically a consumer entity in the above-mentioned embodiment, and may be used to execute the various processes and / or steps corresponding to the consumer entity in the above-mentioned method embodiments. To avoid repetition, it will not be described here.
[0198] The apparatus 10 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the communication equipment (such as a production entity or a consumption entity) in the above-mentioned method. The functions can be implemented by hardware, or the corresponding software can be implemented by hardware. The hardware or software includes at least one module corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.
[0199] 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.
[0200] It should be noted that the apparatus in FIG5 may be the device in the aforementioned embodiment, or may be a chip or chip system, such as a system on chip (SoC). The transceiver unit may be an input / output circuit or a communication interface; the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip. This is not limited here.
[0201] Referring to Figure 6 , as an example, Figure 6 is a schematic diagram of another communication device 20 provided in an embodiment of the present application. The device 20 includes a processor 21, which is coupled to a memory 22. Optionally, the device 20 also includes the memory 22. The memory 22 is used to store computer programs or instructions and / or data. The processor 21 is used to execute the computer programs or instructions stored in the memory 22, or read the data stored in the memory 22, to perform the methods described in the above method embodiments.
[0202] Optionally, there is at least one processor 21.
[0203] Optionally, there is at least one memory 22.
[0204] Optionally, the memory 22 is integrated with the processor 21 or provided separately.
[0205] Optionally, as shown in Figure 6, the device 20 further includes a transceiver 23, which is used to receive and / or send signals. For example, the processor 21 is used to control the transceiver 23 to receive and / or send signals.
[0206] As a solution, the device 20 is used to implement the operations performed by the production entity in the above various method embodiments.
[0207] For example, the processor 21 is configured to execute computer programs or instructions stored in the memory 22 to implement the relevant operations of the production entity in the above various method embodiments. For example, the method executed by the production entity in the embodiment shown in FIG3 .
[0208] As another solution, the device 20 is used to implement the operations performed by the consumer entity in the above various method embodiments.
[0209] For example, the processor 21 is configured to execute computer programs or instructions stored in the memory 22 to implement the relevant operations of the consumer entity in the above various method embodiments. For example, the method executed by the consumer entity in the embodiment shown in FIG3 .
[0210] It is understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.
[0211] It is also understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. As an example and not a limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).
[0212] 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.
[0213] Memory described herein is intended to comprise, but not be limited to, these and any other suitable types of memory.
[0214] 7 , as an example, is a schematic diagram of a chip system 30 provided in accordance with an embodiment of the present application. The chip system 30 (or processing system) includes a logic circuit 31 and an input / output interface 32 .
[0215] The logic circuit 31 may be a processing circuit in the chip system 30. The logic circuit 31 may be coupled to a storage unit and call instructions in the storage unit so that the chip system 30 can implement the methods and functions of the various embodiments of the present application. The input / output interface 32 may be an input / output circuit in the chip system 30, outputting information processed by the chip system 30 or inputting data or signaling information to be processed into the chip system 30 for processing.
[0216] Specifically, for example, if a production entity installs the chip system 30 , the logic circuit 31 is coupled to the input / output interface 32 , and the input / output interface 32 can input the wake-up signal to the logic circuit 31 for processing.
[0217] As a solution, the chip system 30 is used to implement the operations performed by the production entity in the above various method embodiments.
[0218] For example, the logic circuit 31 is used to implement the processing-related operations performed by the production entity in the above method embodiments, such as the processing-related operations performed by the production entity in the embodiment shown in Figure 3; the input / output interface 32 is used to implement the sending and / or receiving-related operations performed by the production entity in the above method embodiments, such as the sending and / or receiving-related operations performed by the production entity in the embodiment shown in Figure 3.
[0219] As another solution, the chip system 30 is used to implement the operations performed by the consumer entity in the above various method embodiments.
[0220] For example, the logic circuit 31 is used to implement the processing-related operations performed by the consumer entity in the above method embodiments, such as the processing-related operations performed by the consumer entity in the embodiment shown in Figure 3; the input / output interface 32 is used to implement the sending and / or receiving-related operations performed by the consumer entity in the above method embodiments, such as the sending and / or receiving-related operations performed by the consumer entity in the embodiment shown in Figure 3.
[0221] An embodiment of the present application further provides a computer-readable storage medium on which computer instructions for implementing the methods executed by the device in the above-mentioned method embodiments are stored.
[0222] 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.
[0223] 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.
[0224] 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.
[0225] An embodiment of the present application further provides a communication system, which includes the production entity and the consumption entity in the above embodiments.
[0226] 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.
[0227] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as at least two units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0228] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes at least one computer instruction. When the computer program instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instruction can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instruction can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes at least one available medium integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)). For example, the aforementioned available medium includes, but is not limited to, various media that can store program code, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
[0229] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.
Claims
1. A method for managing network management intentions, characterized in that: The method comprises: Receiving a trigger condition associated with a network management intention, the trigger condition being a condition for triggering execution of an action group, the action group comprising at least one network management action for achieving at least one goal in the network management intention; In response to determining that the trigger condition is satisfied, the action group begins to be executed.
2. The method according to claim 1, characterized in that The trigger condition is a constraint condition on a performance indicator of a managed entity of the network management intention.
3. The method according to claim 1 or 2, characterized in that The receiving a trigger condition associated with the network management intention includes: receiving a first request message, where the first request message is used to request the creation of the network management intent, the first request message includes the network management intent and the trigger condition, or the first request message includes the network management intent, and the network management intent includes the trigger condition; or, A second request message is received, where the second request message is used to request modification of the network management intention, and the intention modification request message (the second request message) includes an identifier of the network management intention and the trigger condition.
4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: receiving a pause condition associated with the network management intention, the pause condition being a condition for pausing the action group; In response to determining that the suspension condition is satisfied, execution of the action group is suspended.
5. The method according to claim 4, characterized in that: The suspension condition is a constraint condition on a performance indicator of a managed entity of the network management intention.
6. The method according to claim 4 or 5, characterized in that The receiving a pause condition associated with a network management intention comprises: receiving a third request message, where the third request message is used to request the creation of the network management intention, and the third request message includes the network management intention and the pause condition; or A fourth request message is received, where the fourth request message is used to request modification of the network management intention, and the fourth request message includes an identifier of the network management intention and the pause condition.
7. The method according to any one of claims 4 to 6, characterized in that After pausing the execution of the action group, the method further includes: In response to determining that the trigger condition is satisfied, resuming execution of the action group.
8. The method according to any one of claims 1 to 7, characterized in that After the trigger condition is determined to be satisfied and the action group is started to be executed, the method further includes: A first report information is sent, where the first report information indicates that the action group enters an executed state.
9. The method according to any one of claims 4 to 8, characterized in that After pausing the execution of the action group in response to determining that the suspension condition is satisfied, the method further includes: Sending second report information, wherein the second report information indicates that the action group enters a paused state.
10. The method according to any one of claims 1 to 9, characterized in that: The at least one target is all targets in all expectations in the network management intention; or, The at least one target is all targets in a desired state in the network management intention; or, The at least one target is a desired target in the network management intention.
11. A method for managing network management intentions, characterized in that: The method comprises: generating a trigger condition associated with a network management intention, the trigger condition being a condition for triggering execution of an action group, the action group comprising at least one network management action for achieving at least one goal in the network management intention; The trigger condition is sent.
12. The method according to claim 11, characterized in that The trigger condition is a constraint condition on a performance indicator of a managed entity of the network management intention.
13. The method according to claim 11 or 12, characterized in that: The sending trigger condition includes: sending a first request message, where the first request message is used to request the creation of the network management intention, the first request message includes the network management intention and the trigger condition, or the first request message includes the network management intention, and the network management intention includes the trigger condition; or, Send a second request message, the second request message is used to request to modify the network management intention, the second request message includes The identifier of the network management intention and the trigger condition.
14. The method according to any one of claims 11 to 13, characterized in that The method further comprises: A pause condition associated with the network management intention is sent, where the pause condition is a condition for pausing the action group.
15. The method according to claim 14, characterized in that The suspension condition is a constraint condition on a performance indicator of a managed entity of the network management intention.
16. The method according to claim 14 or 15, characterized in that The sending of a pause condition associated with the network management intention comprises: Sending a third request message, where the third request message is used to request the creation of the network management intention, and the third request message includes the network management intention and the pause condition; or A fourth request message is sent, where the fourth request message is used to request modification of the network management intention, and the third request message includes an identifier of the network management intention and the pause condition.
17. The method according to any one of claims 11 to 16, characterized in that The method further comprises: First report information is received, where the first report information indicates that the action group enters a state of being executed.
18. The method according to any one of claims 14 to 17, characterized in that The method further comprises: Second report information is received, where the second report information indicates that the action group enters a paused state.
19. The method according to any one of claims 11 to 18, characterized in that: The at least one target is all targets in all expectations in the network management intention; or, The at least one target is all targets in a desired state in the network management intention; or, The at least one target is a desired target in the network management intention.
20. A method for managing network management intentions, characterized in that: The method comprises: Sending a trigger condition associated with a network management intention, receiving a trigger condition associated with the network management intention, the trigger condition being a condition for triggering execution of an action group, the action group comprising at least one network management action for achieving at least one goal in the network management intention; In response to determining that the trigger condition is satisfied, the action group begins to be executed.
21. The method of claim 20, wherein: The trigger condition is a constraint condition on a performance indicator of a managed entity of the network management intention.
22. A management device for network management intention, characterized in that: The device comprises a transceiver unit and a processing unit. The transceiver unit is used to receive a trigger condition associated with a network management intention, wherein the trigger condition is a condition for triggering the execution of an action group, and the action group includes at least one network management action for achieving at least one goal in the network management intention; The processing unit is configured to start executing the action group in response to determining that the trigger condition is satisfied.
23. The device according to claim 22, characterized in that The trigger condition is a constraint condition on a performance indicator of a managed entity of the network management intention.
24. A management device for network management intention, characterized in that: The device comprises a transceiver unit and a processing unit. The processing unit is used to generate a trigger condition associated with a network management intention, wherein the trigger condition is a condition for triggering the execution of an action group, and the action group includes at least one network management action for achieving at least one goal in the network management intention; The transceiver unit is used to send the trigger condition.
25. The management device according to claim 24, characterized in that: The trigger condition is a constraint condition on a performance indicator of a managed entity of the network management intention.
26. A communication device, characterized in that: The method comprises a unit for executing the method according to any one of claims 1 to 10, or comprises a unit for executing the method according to any one of claims 11 to 19.
27. A communication system, characterized in that: The invention comprises an apparatus for executing the method according to any one of claims 1 to 10 and an apparatus for executing the method according to any one of claims 11 to 19.
28. The system of claim 27, wherein: It also includes managed entities for network management purposes.
29. 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 10, or the computer is caused to execute the method according to any one of claims 11 to 19.
30. A computer program product, characterized in that The method comprises a computer program code, which, when executed on a computer, causes the computer to implement the method according to any one of claims 1 to 10 or causes the computer to implement the method according to any one of claims 11 to 19.
31. 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 10, 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 11 to 19.
32. The device according to claim 31, characterized in that The apparatus also includes the memory.
Citation Information
Patent Citations
Management method, management device and system of network management intention
CN118945032A
Method and device for executing intention
CN112822030A
Intention state management method, network element and system
CN113329480A
Intention processing method, device and system
CN115051903A
Request processing method, device and equipment and readable storage medium
CN115706740A
Cited By
Method, apparatus and computer program
WO2026114807A1
