Network management intention configuration method and device

Abstract

The invention provides a configuration method and device for a network management intention. The method comprises the following steps: receiving an action airspace associated with the network management intention; and configuring at least one managed entity of the network management intention based on the acting airspace, so that the goal of the network management intention is achieved when the at least one managed entity provides service for the terminal equipment in the acting airspace. Therefore, the resources in the managed entity set can provide services for the terminal equipment in the acting airspace, and the rationality of network management intention configuration is improved.

Description

Technical Field

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

[0002] At present, with the enrichment of application scenarios of network management intent, some network management intent can be applied to specific airspaces. For example, in the drone scenario, drones can realize applications such as transportation logistics, agricultural plant protection, security inspection, and geographic prediction in specific airspaces. How to configure network management intent for this scenario has become an urgent problem to be solved. Summary of the invention

[0003] The present application provides a method and device for configuring network management intent, which can improve the rationality of network management intent configuration.

[0004] In a first aspect, a method for configuring a network management intent is provided, which can be executed by a network management service production entity or a chip in the network management service production entity, and the method includes: receiving a scope associated with the network management intent; configuring at least one managed entity of the network management intent based on the scope, so that the goal of the network management intent is achieved when at least one managed entity provides services for a terminal device in the scope.

[0005] Based on this technical solution, the consumer entity can provide an action airspace associated with the network management intent, so that when the production entity configures the managed entity, the managed entity can concentrate resources to provide services for the terminal devices in the action airspace, thereby avoiding the failure to achieve the goal of the network management intent due to unreasonable configuration or using too many resources to achieve the goal, thereby improving the rationality of the network management intent configuration.

[0006] In combination with the first aspect, in certain implementations of the first aspect, the effective airspace is represented by a longitude range, a latitude range, and an altitude range, or the effective airspace is represented by three-dimensional network coding, or the effective airspace is represented by a sphere center coordinate and a sphere radius, or the effective airspace is represented by a sector center coordinate, a vertical angle range, a horizontal angle range, and a sector side length.

[0007] Based on this technical solution, the consumer entity can use a variety of methods to express the various shapes of the action airspace, so that the production entity can provide services to the terminal devices within the action airspace by configuring the managed entity.

[0008] In combination with the first aspect, in certain implementations of the first aspect, the target of the network management intention includes at least one of the following: the communication bandwidth is within the bandwidth indicator range, the communication delay is within the delay indicator range, the number of communication users is within the user indicator range, the network-aware speed measurement accuracy is within the speed measurement accuracy range, or the network-aware positioning accuracy is within the positioning accuracy range, wherein the network-aware speed measurement accuracy is the accuracy of measuring the speed of a moving object through a network perception function, and the network-aware positioning accuracy is the accuracy of locating an object through a network perception function.

[0009] Based on this technical solution, the production entity can configure the managed entity based on the target of the network management intention to provide different services for the terminal devices in the effective airspace.

[0010] In combination with the first aspect, in certain implementations of the first aspect, at least one managed entity of the network management intent is configured based on the action airspace so that the goal of the network management intent is achieved when the at least one managed entity provides services to the terminal device in the action airspace during an action time period, including: at least one managed entity of the network management intent is configured based on the action airspace so that the goal of the network management intent is achieved when the at least one managed entity provides services to the terminal device in the action airspace during an action time period, wherein the action airspace contains information about the action time period.

[0011] Based on this technical solution, the consumer entity can also provide an action time period associated with the action area, so that the production entity can configure the managed entity based on the action time period, which can further improve the rationality of the network management intention configuration.

[0012] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: receiving a non-effective airspace associated with a network management intention, and at least one managed entity is capable of not providing services to terminal devices in the non-effective airspace.

[0013] Based on the present technical solution, the production entity is able to not provide services for terminal devices in non-functional airspace. For example, for drone application scenarios, non-functional airspace may refer to airspace where drones are prohibited from flying. Thus, the production entity does not need to configure transmission resources for drone communications in the non-functional airspace, thereby improving resource utilization.

[0014] In combination with the first aspect, in certain implementations of the first aspect, receiving a scope space associated with a network management intent includes: receiving a first request message, the first request message is used to request the creation of a network management intent, the first request message includes the network management intent and the scope space, or the first request message includes the network management intent, and the network management intent includes the scope space; or, receiving a second request message, the second request message is used to request the modification of the network management intent, the second request message includes an identifier of the network management intent and the scope space; or, receiving a third request message, the third request message is used to request the activation of the network management intent, the third request message includes an identifier of the network management intent and the scope space; or, receiving a fourth request message, the fourth request message is used to request the suspending of the network management intent, the fourth request message includes an identifier of the network management intent and the scope space.

[0015] In combination with the first aspect, in certain implementations of the first aspect, at least one managed entity of the network management intent is configured based on the action airspace so that the goal of the network management intent is achieved when the at least one managed entity provides services to a terminal device in the action airspace, including: obtaining information of multiple managed entities of the network management intent; determining at least one managed entity among the multiple managed entities based on the action airspace and the information of the multiple managed entities; configuring at least one managed entity so that the goal of the network management intent is achieved when the at least one managed entity provides services to a terminal device in the action airspace.

[0016] Based on this technical solution, the production entity can select a suitable managed entity based on the effective airspace to provide services to the terminal devices within the effective airspace, thereby further improving the rationality of the network management intention configuration.

[0017] In combination with the first aspect, in some implementations of the first aspect, the information of the managed entity includes at least one of the following: location information, frequency information, beam pointing information, or beam width information.

[0018] Based on this technical solution, the production entity can select a suitable managed entity to provide services to the terminal devices in the effective airspace based on the attributes or capabilities of the managed entities, thereby further improving the rationality of the network management intention configuration.

[0019] In combination with the first aspect, in some implementations of the first aspect, the service includes any one of a communication service and a perception service.

[0020] In combination with the first aspect, in certain implementations of the first aspect, before receiving the action airspace associated with the network management intent, the method also includes: receiving a target related to the network management intent; determining a recommended action airspace based on the target of the network management intent; and sending the recommended action airspace, wherein the recommended action airspace is used to determine the action airspace.

[0021] Based on this technical solution, the consumer entity can determine the action airspace based on the recommended action airspace fed back by the production entity, which can improve the rationality of the action airspace determination and further improve the rationality of the configuration of the network management intention.

[0022] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: sending intent report information, the intent report information indicating whether a goal of the network management intent is achieved when at least one managed entity provides services to a terminal device in an effective airspace.

[0023] In combination with the first aspect, in certain implementations of the first aspect, at least one managed entity of the network management intent is configured based on the action airspace so that the goal of the network management intent is achieved when the at least one managed entity provides services to a terminal device in the action airspace, including: obtaining information of at least one managed entity; determining a management action group for each managed entity to achieve the goal of the network management intent based on the action airspace and the information of the at least one managed entity; configuring at least one managed entity so that the goal of the network management intent is achieved when the at least one managed entity provides services to a terminal device in the action airspace.

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

[0025] In a second aspect, a method for configuring a network management intent is provided, which can be executed by a network management service consumer entity or a chip in the network management service consumer entity, and the method includes: determining a scope associated with the network management intent, the scope being used to configure at least one managed entity of the network management intent so that the goal of the network management intent is achieved when at least one managed entity provides services to a terminal device in the scope; and sending the scope.

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

[0027] In combination with the second aspect, in certain implementations of the second aspect, the effective airspace is represented by a longitude range, a latitude range, and an altitude range, or the effective airspace is represented by three-dimensional network coding, or the effective airspace is represented by a sphere center coordinate and a sphere radius, or the effective airspace is represented by a sector center coordinate, a vertical angle range, a horizontal angle range, and a sector side length.

[0028] In combination with the second aspect, in certain implementations of the second aspect, the goals of the network management intent include at least one of the following: the communication bandwidth is within the bandwidth indicator range, the communication delay is within the delay indicator range, the number of communication users is within the user indicator range, the network-aware speed measurement accuracy is within the speed measurement accuracy range, or the network-aware positioning accuracy is within the positioning accuracy range, wherein the network-aware speed measurement accuracy is the accuracy of measuring the speed of a moving object through a network perception function, and the network-aware positioning accuracy is the accuracy of locating an object through a network perception function.

[0029] In combination with the second aspect, in certain implementations of the second aspect, the action airspace includes information indicating an action time period associated with the action airspace, and the action time period is used to configure at least one managed entity of the network management intent so that the goal of the network management intent is achieved when the at least one managed entity provides services to a terminal device in the action airspace during the action time period.

[0030] In combination with the second aspect, in certain implementations of the second aspect, the method further includes: sending a non-effective airspace associated with a network management intention, and at least one managed entity is able to not provide services to a terminal device in the non-effective airspace.

[0031] In combination with the second aspect, in certain implementations of the second aspect, sending a scope space includes: sending a first request message, the first request message is used to request the creation of a network management intent, the first request message includes the network management intent and the scope space, or the first request message includes the network management intent, and the network management intent includes the scope space; or, sending a second request message, the second request message is used to request the modification of the network management intent, the second request message includes the identifier of the network management intent and the scope space; or, sending a third request message, the third request message is used to request the activation of the network management intent, the third request message includes the identifier of the network management intent and the scope space; or, sending a fourth request message, the fourth request message is used to request the suspending of the network management intent, the fourth request message includes the identifier of the network management intent and the scope space.

[0032] In combination with the second aspect, in certain implementations of the second aspect, determining the effective airspace includes: sending an expected effective airspace associated with a network management intent; receiving a recommended airspace, the recommended airspace including at least one of a recommended effective airspace and a recommended ineffective airspace, the recommended airspace being determined based on the expected effective airspace; and determining the effective airspace based on the recommended airspace.

[0033] In combination with the second aspect, in certain implementations of the second aspect, the method includes: receiving intent report information, the intent report information indicating whether a goal of the network management intent is achieved when at least one managed entity is in an effective airspace.

[0034] In combination with the second aspect, in certain implementations of the second aspect, the method includes: sending a target of network management intent; receiving a recommended action airspace, the recommended action airspace is determined based on the target of the network management intent, and the recommended action airspace is used to determine the action airspace.

[0035] In combination with the second aspect, in some implementations of the second aspect, the service includes any one of a communication service and a perception service.

[0036] In combination with the second aspect, in certain implementations of the second aspect, the method includes: receiving intent reporting information, the intent reporting information indicating whether a goal of network management intent is achieved when at least one managed entity provides services to a terminal device in an effective airspace.

[0037] According to a third aspect, a method for configuring a network management intent is provided, the method comprising: determining a scope associated with the network management intent; sending the scope, receiving the scope; and configuring at least one managed entity of the network management intent based on the scope, so that the goal of the network management intent is achieved when the at least one managed entity provides services for a terminal device in the scope.

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

[0039] In combination with the third aspect, in certain implementations of the third aspect, the effective airspace is represented by a longitude range, a latitude range, and an altitude range, or the effective airspace is represented by three-dimensional network coding, or the effective airspace is represented by spherical center coordinates and spherical radius, or the effective airspace is represented by sector center coordinates, vertical angle range, horizontal angle range, and sector side length.

[0040] In combination with the third aspect, in certain implementations of the third aspect, the target of the network management intention includes at least one of the following: the communication bandwidth is within the bandwidth indicator range, the communication delay is within the delay indicator range, the number of communication users is within the user indicator range, the network-aware speed measurement accuracy is within the speed measurement accuracy range, or the network-aware positioning accuracy is within the positioning accuracy range, wherein the network-aware speed measurement accuracy is the accuracy of measuring the speed of a moving object through a network perception function, and the network-aware positioning accuracy is the accuracy of positioning an object through a network perception function.

[0041] In combination with the third aspect, in certain implementations of the third aspect, the at least one managed entity of the network management intent is configured based on the action airspace so that the goal of the network management intent is achieved when the at least one managed entity provides services to the terminal device in the action airspace during an action time period, including: configuring at least one managed entity of the network management intent based on the action airspace so that the goal of the network management intent is achieved when the at least one managed entity provides services to the terminal device in the action airspace during an action time period, wherein the action airspace contains information about the action time period.

[0042] In combination with the third aspect, in certain implementations of the third aspect, the method also includes: sending a non-effective airspace associated with the network management intention, receiving a non-effective airspace associated with the network management intention, and the at least one managed entity is able to not provide services to terminal devices in the non-effective airspace.

[0043] In combination with the third aspect, in certain implementations of the third aspect, the sending of the scope airspace and the receiving of the scope airspace include: sending a first request message and receiving the first request message, the first request message being used to request the creation of the network management intention, the first request message comprising the network management intention and the scope airspace, or the first request message comprising the network management intention, the network management intention comprising the scope airspace; or, sending a second request message and receiving the second request message, the second request message being used to request the modification of the network management intention, the second request message comprising an identifier of the network management intention and the scope airspace; or, sending a third request message and receiving the third request message, the third request message being used to request the activation of the network management intention, the third request message comprising an identifier of the network management intention and the scope airspace; or, sending a fourth request message and receiving the fourth request message, the fourth request message being used to request the suspending of the network management intention, the fourth request message comprising an identifier of the network management intention and the scope airspace.

[0044] In combination with the third aspect, in certain implementations of the third aspect, the at least one managed entity of the network management intention is configured based on the effective airspace so that the goal of the network management intention is achieved when the at least one managed entity provides services to the terminal device in the effective airspace, including: obtaining information of multiple managed entities of the network management intention; determining the at least one managed entity among the multiple managed entities based on the effective airspace and the information of the multiple managed entities; configuring the at least one managed entity so that the goal of the network management intention is achieved when the at least one managed entity provides services to the terminal device in the effective airspace.

[0045] In combination with the third aspect, in certain implementations of the third aspect, the information of the managed entity includes at least one of the following: location information, frequency information, beam pointing information, or beam width information.

[0046] In combination with the third aspect, in some implementations of the third aspect, the service includes any one of a communication service and a perception service.

[0047] In combination with the third aspect, in certain implementations of the third aspect, before sending the action airspace and receiving the action airspace, the method also includes: sending a target consistent with the network management intention, receiving a target consistent with the network management intention; determining a recommended action airspace based on the target of the network management intention; receiving the recommended action airspace, sending the recommended action airspace, and the recommended action airspace is used to determine the action airspace.

[0048] In combination with the third aspect, in certain implementations of the third aspect, the method further includes: sending intent report information, receiving intent report information, wherein the intent report information indicates whether the goal of the network management intent is achieved when the at least one managed entity provides services to the terminal device in the action airspace.

[0049] In combination with the third aspect, in certain implementations of the third aspect, the at least one managed entity of the network management intent is configured based on the action airspace so that the goal of the network management intent is achieved when the at least one managed entity provides services to the terminal device in the action airspace, including: obtaining information of the at least one managed entity; determining a management action group for each of the managed entities to achieve the goal of the network management intent based on the action airspace and the information of the at least one managed entity; configuring the at least one managed entity so that the goal of the network management intent is achieved when the at least one managed entity provides services to the terminal device in the action airspace.

[0050] In a fourth aspect, a device for configuring a network management intent is provided, the device comprising a transceiver unit and a processing unit, wherein the transceiver unit is used to receive an action space associated with the network management intent; the processing unit is used to configure at least one managed entity of the network management intent based on the action space, so that the goal of the network management intent is achieved when at least one managed entity provides services for a terminal device in the action space.

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

[0052] In a fifth aspect, a device for configuring a network management intent is provided, the device comprising a transceiver unit and a processing unit, wherein the processing unit determines an action airspace associated with the network management intent, the action airspace being used to configure at least one managed entity of the network management intent so that the goal of the network management intent is achieved when at least one managed entity provides services to a terminal device in the action airspace; and the transceiver unit is used to send the action airspace.

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

[0054] In a sixth aspect, a communication device is provided, wherein the communication device has the function of implementing the first aspect or any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect, or the third aspect or any possible implementation of the third aspect. The function can be implemented by hardware, or the corresponding software can be implemented by hardware. The hardware or software includes one or more units corresponding to the above functions.

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

[0056] Exemplarily, the communication device produces network elements for network management services.

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

[0058] Exemplarily, the communication device is a network management service consuming network element.

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

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

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

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

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

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

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

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

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

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

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

[0070] Figure 4 This is a schematic diagram of a possible action space;

[0071] Figure 5 is a schematic flow chart of a possible method for determining an action area provided in an embodiment of the present application;

[0072] Figure 6 is a schematic flow chart of a possible method for configuring network management intent provided in an embodiment of the present application;

[0073] Figures 7 to 9 It is a schematic diagram of a possible communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

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

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

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

[0078] 1.1 Network Management

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

[0080] 1.2 Network Management Services

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

[0082] 1.3 Network management service production entity

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

[0084] 1.4 Network Management Service Consumption Entity

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

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

[0087] The network management intent refers to the demand of the network management service consumer entity for the network management service, which may also be referred to as the network management service demand. The embodiment of the present application does not limit this name. For example, the network management intent may be an optical dedicated line service intent or an energy-saving intent, such as the intent defined in the third generation partnership project (3GPP) standard specification 28.312.

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

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

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

[0091] 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. Exemplarily, an intent expectation may include two expected targets, one of which is an average downlink throughput greater than 5 Mbps, and the other is an end-to-end delay less than 10 milliseconds. If the average downlink throughput of the expected object is greater than 5 Mbps, then the expected target for downlink throughput is met. If the end-to-end delay of the expected object is less than 10 milliseconds, then the expected target for delay is met. If both expected targets of an intent expectation are met, then the intent expectation is achieved.

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

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

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

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

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

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

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

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

[0100] 3. Network Management Intent Template

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

[0102] 4. Intent Expression

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

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

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

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

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

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

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

[0110] 5. Intent Examples

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

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

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

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

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

[0116] The network management service production entity can generate multiple management action groups based on the intent expression. During the execution process, the network management service production entity can select some management action groups from multiple management action groups to execute at a time. In other words, the management action groups generated by the network management service production entity based on the translation of the intent expression are optional operations that can be used to meet the intent. The network management service production entity may select one of the network management action groups to execute to meet the intent, or it may select multiple network management action groups to execute to meet the intent.

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

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

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

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

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

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

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

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

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

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

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

[0128] As the application scenarios of network management intents become richer, some network management intents can be applied to specific airspaces. For example, in the drone scenario, drones can be used for transportation and logistics, agricultural plant protection, security inspections, geographic prediction, and other applications in specific airspaces. The performance of network management intent in this scenario is strongly related to the airspace in which it is used. How to provide network management intent services for this scenario has become an urgent problem to be solved.

[0129] The present application provides a method and device for configuring network management intent, which can improve the rationality of the configuration of network management intent in airspace-related scenarios. Figure 3 The configuration method of the network management intention provided in the embodiment of the present application is explained.

[0130] Figure 3For ease of description, the network management service production entity is referred to as the production entity, the network management service consumption entity is referred to as the consumption entity, and the network management intent is referred to as the intent.

[0131] S310, the consumer entity sends the role airspace associated with the network management intention to the producer entity. Correspondingly, the producer entity receives the role airspace associated with the network management intention from the consumer entity.

[0132] The action airspace can be used to configure at least one managed entity of the network management intent, so that the goal of the network management intent is achieved when the at least one managed entity provides services to the terminal devices in the action airspace. In other words, the consumer entity can provide an action airspace associated with the network management intent, so that when the production entity configures the managed entity, the managed entity can concentrate resources to provide services to the terminal devices in the action airspace, avoiding the failure to achieve the goal of the network management intent or using too many resources to achieve the goal due to unreasonable configuration, thereby improving the rationality of the configuration of the network management intent.

[0133] Among them, the goal of fulfilling the network management intention can also be described as the goal of satisfying the network management intention, the goal of realizing the network management intention, etc.

[0134] It is understandable that the scope of the three-dimensional space can be a three-dimensional space where the consumer entity calls the service. The scope of the three-dimensional space can be configured based on the specific application scenario, and this application does not specifically limit this. For example, the scope of the three-dimensional space can include one or more three-dimensional spaces in the shape of a cube, a sphere, etc. Figure 4 A schematic diagram of a possible action space is shown in FIG.

[0135] For example Figure 4 , the action space contains three cubic three-dimensional spaces. Among them, Figure 4The plane formed by the x-axis and the y-axis can represent the ground plane, and the z-axis represents the direction perpendicular to the ground plane. The three three-dimensional spaces can be: the airspace of 50 meters to 100 meters above area #1, the airspace of 80 meters to 130 meters above area #2, and the airspace of 120 meters to 170 meters above area #3. Among them, area #1, area #2 and area #3 are three specific two-dimensional areas on the ground. Thus, the production entity can configure the managed entity so that the goal of the network management intent is achieved within the effective airspace. For example, in the scenario of drone management, the network management intent is a communication service assurance intent, and the effective airspace represents the flight range of the drone. The production entity can configure the managed entity (such as a base station) so that the managed entity provides transmission resources for communication for the drone in the effective airspace.

[0136] The action airspace can be expressed in various ways that can be used to describe three-dimensional space. Exemplarily, the action airspace can be represented by a longitude range, a latitude range, and an altitude range. For example, a consumer entity can describe the range of the action area projected to the ground through a set of longitude ranges and latitude ranges (for example, the longitude range is 120 degrees 53 minutes east longitude to 120 degrees 55 minutes east longitude, and the latitude range is 30 degrees 41 minutes to 43 minutes north latitude), and then describe the height of the action airspace through a set of altitude ranges (for example, the altitude range is 50 meters to 100 meters from the ground). Exemplarily, the action airspace can be represented by a three-dimensional network coding table, such as a geographic coordinate subdividing grid with one dimension integral coding on 2n-tree (GeoSoT) based on a 2n one-dimensional integer array. Exemplarily, the action airspace is represented by the spherical center coordinates and the spherical radius. For example, the spherical center coordinates can be located by longitude, latitude, and altitude, and a spherical area is limited by the spherical radius. In another exemplary embodiment, the action airspace is represented by the sector center coordinates, vertical angle range, horizontal angle range and sector side length, for example, the sector center coordinates are located by longitude, latitude and altitude, and then a sector area is limited by the vertical angle range, horizontal angle range and sector side length. This application does not specifically limit the expression of three-dimensional space. The expression of three-dimensional space adopted by the consumer entity may be related to the shape of the action space, or may be related to the ability of the consumer entity and the production entity to interpret, and this application does not specifically limit this.

[0137] The determination of the action airspace may be determined by the consumer entity based on the scenario, or may be determined by negotiation between the consumer entity and the production entity. When the consumer entity and the production entity determine the action airspace through negotiation, optionally, before step S310, the consumer entity may first send a goal consistent with the network management intent to the production entity, and the production entity may determine whether it is feasible to achieve the goal of the network management intent within the expected action airspace based on its capabilities. If the production entity confirms that it is feasible, the production entity may return information confirming the feasibility to the consumer entity. If the production entity confirms that it is not feasible, the production entity may determine a recommended action airspace and return the recommended action airspace to the consumer entity. After receiving the recommended action airspace, the consumer entity may determine the recommended action airspace as the action airspace in step S310, or may adjust the recommended action airspace and use it as the action airspace in step S310. For more detailed information on how to determine the action airspace, please refer to the following text Figure 5 and Figure 6 The introduction of will not be elaborated here.

[0138] The consumer entity may send the scope airspace to the producer entity in a variety of ways. For example, the consumer entity may send a first request message carrying the scope airspace to the producer entity, wherein the first request message may be used to request the creation of a network management intent. For example, the first request message includes a network management intent (such as Figure 1 The data structure shown in FIG. 10A ) and the scope space, or the first request message includes a network management intention, and the network management intention includes a scope space (for example, the scope space can be as follows Figure 1 Expected object of the data structure shown). In another exemplary manner, the consumer entity may send a second request message carrying a scope airspace to the production entity, wherein the second request message is used to modify the network management intent. For example, the second request message may include an identifier and a scope airspace of the network management intent. In another exemplary manner, the consumer entity may send a third request message carrying a scope airspace to the production entity, wherein the third request message is used to activate the network management intent. For example, the third request message may include an identifier and a scope airspace of the network management intent. In another exemplary manner, the consumer entity may send a fourth request message carrying a scope airspace to the production entity, wherein the fourth request message is used to suspend the network management intent. For example, the fourth request message may include an identifier and a scope airspace of the network management intent. It can be understood that the above is only an exemplary description, and the consumer entity may also use a separate message or other message to send the scope airspace to the production entity, and the present application does not specifically limit this.

[0139] In one possible implementation, the network management intent is associated with multiple scopes. In this case, the network management intent may contain multiple goals, and multiple scopes may be associated with different goals. Exemplarily, the network management intent is associated with a first scope and a second scope, the first scope is associated with goal #1 of the network management intent (such as the communication bandwidth is greater than the first threshold), and the second scope is associated with goal #2 of the network management intent (such as the number of users is greater than the second threshold). Thus, consumer entities can associate different goals based on the characteristics of different scopes, and production entities will not indiscriminately achieve all goals of the network management intent in all scopes, which can improve the performance of the network management intent.

[0140] After receiving the effective airspace, the production entity may regard the airspace outside the effective airspace as the non-effective airspace by default. Alternatively, the consumer entity may send the non-effective airspace associated with the network management intent to the production entity. The goal of the network management intent may not be achieved in the non-effective airspace. For example, for drone application scenarios, the non-effective airspace may refer to the airspace where drones are prohibited from flying, so that the production entity does not need to configure transmission resources for drone communications in the non-effective airspace, which can improve the efficiency of transmission resources.

[0141] It is understandable that the expression of the non-effective airspace is similar to that of the effective airspace, for example, the non-effective airspace can be represented by a longitude range, a latitude range, and an altitude range, or by GeoSOT, or by spherical center coordinates or spherical radius, or other expressions that can represent airspace defined in the future. The sending method of the non-effective airspace can also be similar to that of the effective airspace, for example, the non-effective airspace can be carried in the first request message, the second request message, the third request message, or the fourth request message described above, which will not be described in detail here.

[0142] Optionally, the consuming entity may also indicate an effective time period, so that the producing entity may configure the managed entity so that the goal of the network management intention is achieved within the effective area and within the effective time period.

[0143] The consumer entity may send the action time period associated with the action airspace to the producer entity. For example, the consumer entity sends the network management intent to the producer entity, and the network management intent includes the action airspace (e.g. Figure 1 The desired object shown in FIG. 1 ), the action object may include information indicating the action time period (such as Figure 1The desired object context shown in the figure). At this time, the action time period can be regarded as a constraint condition of the action airspace. The production entity can determine the managed object based on the action airspace, and then configure the managed object with the action time period as a constraint condition. As another example, the action time period can also be carried in the first request message, the second request message, the third request message or the fourth request message described above, or the consumer entity can also send the action time period to the production entity through a separate message, and the present application does not specifically limit this.

[0144] S320, the production entity configures at least one managed entity of the network management intent based on the action airspace, so that the goal of the network management intent is achieved when the at least one managed entity provides services for the terminal device in the action airspace.

[0145] The terminal device in the embodiments of the present application may refer to user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent or user device. For example, the terminal in the embodiments of the present application can be a drone, a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5G network or a terminal in a future evolution network, etc. Among them, wearable devices can also be called wearable smart devices, which are a general term for the intelligent design of daily wearables and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and only focus on a certain type of application functions, and need to be used with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring. In addition, the terminal device can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. This application does not limit the specific form of the terminal device.

[0146] It is understandable that the terminal device being in the effective airspace may include a variety of situations, such as a drone flying into the effective airspace, or a wearable device being carried into the effective airspace, etc. This application does not specifically limit this.

[0147] The service provided by the managed entity to the terminal device in the effective airspace may be related to the goal of the network management intent, for example, the service includes any one of the communication service and the perception service. Exemplarily, the network management intent is the communication service guarantee intent, and the production entity may configure the managed entity so that the managed entity provides communication services to the terminal devices in the effective airspace, such as the production entity configuring the base station so that the base station provides transmission resources for communication to the terminal devices (such as drones) in the effective airspace. Another exemplary example is that the network management intent is the speed measurement service intent, and the production entity may configure the base station so that the base station uses the perception function to measure the moving speed of the drone in the effective airspace. Among them, the perception function may refer to the base station using various propagation characteristics of radio waves, such as reflection, scattering, refraction and other characteristics to reconstruct and depict the physical world.

[0148] Exemplarily, the target of network management intent may include any of the following: communication bandwidth is within the bandwidth indicator range, communication delay is within the delay indicator range, number of users is within the user indicator range, network-aware speed measurement accuracy is within the speed measurement accuracy range, or network-aware positioning accuracy is within the positioning accuracy range, wherein network-aware speed measurement accuracy is the accuracy of measuring the speed of a moving object through a network-aware function, and network-aware positioning accuracy is the accuracy of locating an object through a network-aware function. If the target of network management intent includes the above-mentioned targets of communication bandwidth, communication delay or number of users, the managed entity may provide communication services for terminal devices within the effective airspace so that the corresponding target is achieved. If the target of network management intent includes the above-mentioned targets of network-aware speed measurement accuracy or network-aware positioning accuracy, the managed entity may provide perception services for terminal devices within the effective airspace.

[0149] The production entity configures at least one managed entity based on the functional airspace, which may include the following actions: the production entity selects at least one managed entity for providing services for the functional airspace based on the functional airspace.

[0150] Exemplarily, the production entity may obtain information of multiple managed entities of the network management intention, and select at least one managed entity from the multiple managed entities to provide services for the action airspace based on the information of the action airspace and multiple managed entities. Among them, the information of the managed entity obtained by the production entity may be related to the target of the network management intention. For example, the information of the managed entity may include at least one of the following: location information, frequency information, beam pointing information or beam width information, etc. For example, the production entity may select at least one managed entity whose service range covers the action area based on the information of the managed entity. For example, the location information contains the height information of the managed entity, the production entity obtains the height information of multiple managed entities, determines the height difference between each managed object and the action airspace, and selects the managed object whose height difference is less than or equal to the specific height difference threshold to provide services for the terminal equipment in the action airspace. For another example, the production entity may select a broadband managed entity that can provide the target of the network management intention based on the frequency, beam pointing or beam width supported by the action management entity. This application is not particularly limited to this.

[0151] It can be understood that the production entity selects at least one managed entity for providing services to the action airspace as an optional action. That is, the production entity can directly configure the managed entity so that the goal of network management intent is achieved when the managed entity provides services to the terminal device in the action airspace. The production entity configures the managed entity, which can refer to sending an instruction of the management action group to the managed entity, and the managed entity provides services to the terminal device by executing the management action group.

[0152] The production entity can determine a network management action group for achieving the goal of the network management intention based on the effective airspace. Exemplarily, the production entity configures the frequency of the managed entity based on the goal of the network management intention and the height of the effective airspace. For example, when the height of the effective airspace is less than or equal to 200 meters, the frequency of the managed entity serving the terminal devices in the effective airspace is configured to be 2.6G; when the height of the effective airspace is greater than or equal to 200 meters, the frequency of the managed entity serving the terminal devices in the effective airspace is configured to be 4.9F; when the height of the effective airspace is greater than or equal to 150 meters and less than or equal to 200 meters, the managed entity can also configure the 4.9G frequency as the switching bandwidth. As another example, the production entity can also configure the beam pointing and width of the managed entity based on the height of the effective airspace, so that the managed entity can provide services for the effective airspace.

[0153] After the production entity sends the network management action group used to achieve the target of the network management intention to the managed entity, it can also obtain the performance indicator value related to the target of the network management intention. For example, if the target of the network management intention is that the communication delay is within the delay indicator range, the production entity can obtain the communication delay of the terminal device in the effective airspace to determine whether the target of the network management intention is achieved. At this time, the production entity can also feedback the execution status of the network management intention to the consumer entity, that is, the production entity can also perform the following step S330.

[0154] Optionally, S330, the production entity sends intention report information to the consumption entity. Correspondingly, the consumption entity receives the intention report information sent by the production entity.

[0155] The intent report information may indicate whether the target of the network management intent is achieved when at least one managed entity provides services to terminal devices in the effective airspace. Exemplarily, the production entity may determine whether the network management intent is achieved based on the performance indicator value of the managed entity, and feedback the achievement result of the target of the network management intent to the consumer entity. Optionally, the production entity may also feedback the current performance indicator value to the consumer entity, such as feedback on the communication delay of the terminal device in the current effective airspace. Thus, the consumer entity can be informed of the execution status of the network management intent in a timely manner.

[0156] Optionally, if the target of the network management intention is not achieved, the production entity may also determine in which area of ​​the effective area the target of the network management intention is not achieved, and carry the unachieved area where the target of the network management intention is not achieved in the intention report information. Figure 4 As shown in the action area composed of three three-dimensional spaces, the production entity determines the communication delay when the managed entity provides communication services to the terminal devices in the three three-dimensional spaces, and determines that the communication delay in one of the three-dimensional spaces fails to achieve the corresponding network management intention target. Then, the production entity can feedback the coordinates of the three-dimensional space to the consumer entity, so that the consumer entity can know which airspace has failed to achieve the target and can perform more refined management of the network management intention.

[0157] Based on this technical solution, the consumer entity can provide an action airspace associated with the network management intent, so that when the production entity configures the managed entity, the managed entity can concentrate resources to provide services for the terminal devices in the action airspace, thereby avoiding the failure to achieve the goal of the network management intent due to unreasonable configuration or using too many resources to achieve the goal, thereby improving the rationality of the network management intent configuration.

[0158] Combination of the above Figure 3 and Figure 4The consumer entity sends the action airspace to the production entity, and the production entity configures at least one managed entity based on the action airspace. Before step S310, that is, before the consumer entity sends the action airspace to the production entity, the consumer entity can also use a variety of methods to determine the action airspace. In one possible implementation, the consumer entity can directly determine the action airspace based on the scenario. In another possible implementation, the consumer entity can determine the action airspace through negotiation with the production entity. In order to facilitate the understanding of the embodiments of the present application, the following is combined with Figure 5 A possible method for consumer entities and producer entities to determine the effective airspace through negotiation is introduced.

[0159] Figure 5 It is a schematic flowchart of a possible method for determining an effective airspace provided in an embodiment of the present application.

[0160] S510, the consumer entity sends a target of network management intent to the producer entity. Correspondingly, the producer entity receives the target of network management intent from the consumer entity.

[0161] Before determining the role, the consumer entity can send the target of the network management intention to the production entity, so that the production entity can determine the area where it can provide services based on the target of the network management intention and the capabilities of the managed entities so that the target of the network management intention is achieved, and feedback the area to the consumer entity.

[0162] Exemplarily, the consumer entity sends an intent detection request message to the producer entity, and the intent detection request message carries the target of the network management intent. The intent detection request message can be used to request the producer entity to return the recommended action airspace. Or the intent detection request message contains detection object indication information, and the detection object indication information instructs the producer entity to return the recommended action airspace. For example, in the drone scenario, the description of the detection object indication information can be "recommended flyer airspace", which is used to instruct the producer entity to return the recommended action airspace that can provide services for the drone.

[0163] S520, the production entity determines the recommended action airspace based on the goal of the network management intent.

[0164] The production entity can obtain the capabilities of the managed entities it manages based on the goals of the network management intent. For example, if the goal of the network management intent is that the communication bandwidth is greater than or equal to a specific bandwidth threshold, the production entity can obtain the bandwidth capabilities of the managed base stations and determine the areas that can achieve the goals of the network management intent based on the bandwidth capabilities. For another example, if the goal of the network management intent is that the network-aware positioning accuracy is greater than or equal to a specific positioning accuracy threshold, the production entity can obtain the perception capabilities of the managed base stations and determine the areas that can achieve the goals of the network management intent based on the perception capabilities. In other words, the production entity can estimate the recommended action area that can achieve the goals based on the goals of the network management intent and the managed capabilities.

[0165] It is understandable that the production entity can also determine the recommended non-effective airspace based on the goal of network management intent, and the recommended non-effective airspace can also be used to determine the effective airspace. In the embodiments of the present application, the recommended effective airspace is taken as an example.

[0166] S530, the production entity sends the recommended action space to the consumption entity. Correspondingly, the consumption entity receives the recommended action space from the production entity.

[0167] In an illustrative manner, the production entity may send an intent detection response message to the consumption entity, and the intent detection response message includes a recommended role space. The expression form of the recommended role space may be the same as that in the above text. Figure 3 The expression form of the action space introduced in step S310 is similar and will not be repeated here.

[0168] S540, the consumer entity determines the action space based on the recommended action space.

[0169] The consumer entity can directly regard the recommended action space as the action space, or adjust the recommended action space according to the scenario to determine the action space, thereby executing the above Figure 3 Step S310 in the above method sends the action space to the consumer entity, which is not specifically limited in this application. In this embodiment, the consumer entity determines the action space based on the recommended action space fed back by the production entity, which can improve the rationality of the action space determination and further improve the rationality of the configuration of the network management intention.

[0170] It is understandable that the optional steps S510 to S540 described above occur before step S310. In this case, the consumer entity may determine the scope of the action before sending the intent to create a request message to the producer entity. In another possible implementation, the consumer entity and the producer entity may exchange intent to create a request message multiple times and determine the scope of the action through negotiation. Figure 6 A possible implementation method is described as an example.

[0171] Figure 6 It is a schematic flowchart of a possible implementation method provided by an embodiment of the present application.

[0172] S601, the consumer entity sends a create request message #1 to the producer entity.

[0173] Intent creation request message #1 may contain a network management intent (e.g. Figure 1 The network management intent may include the target and scope of the network management intent #1 (e.g. Figure 1 Alternatively, the intent construction request message includes the network management intent and scope #1. For a more detailed description of scope #1, see the above Figure 3 The description of step S310 is not repeated here.

[0174] Optionally, S602, the production entity performs a feasibility check based on the action space #1.

[0175] The production entity can determine whether the goal of the network management intent can be achieved when the managed entity it manages provides services to the terminal devices in the scope airspace #1 based on the goal of the network management intent. If the production entity determines that it can be achieved, the production entity can subsequently configure the managed entity based on the scope airspace #1. If the production entity determines that it cannot be achieved, the production entity can determine the recommended scope airspace based on the goal of the network management intent and the scope airspace #1. In one possible implementation, the production entity can also call the network twin production entity to estimate whether the goal of the network management intent can be achieved in the scope airspace #1 with the current network resources (such as the communication resources that the managed entity can schedule). The method for the production entity to determine the recommended scope airspace is similar to Figure 5 The description of step S520 is similar and will not be repeated here.

[0176] It is understandable that the production entity can also perform a feasibility check on the intent to create request message #1. Exemplarily, the production entity can detect whether the intent to create request message #1 can be successfully interpreted, such as detecting whether the intent to create request message #1 conforms to the grammatical semantics of the network management intent. If it is detected that the intent to create request message #1 can be successfully interpreted, the production entity can configure the managed object based on the method described above. If it is detected that the intent to create request message #1 cannot be successfully interpreted, such as a grammatical error, the production entity can send feedback indicating the grammatical error to the consumer entity.

[0177] Optionally, S603, the production entity sends a create request response message to the consumption entity.

[0178] If the production entity determines in step S602 that the managed entity can achieve the goal of the network management intention when providing services to the terminal device in the action airspace #1, then the production entity can carry information indicating that the action airspace #1 is feasible in the intention creation request response message. It is understandable that the production entity can also carry the identification of the network management intention and the information on whether the network management intention is successfully created in the intention creation request message #1.

[0179] If the production entity determines in step S602 that the managed entity cannot achieve the goal of the network management intent when providing services to the terminal device in the action airspace #1, then the production entity can carry information indicating that the action airspace #1 is not feasible in the intention creation request response message. Exemplarily, the intention creation request response message may include failure cause information, which indicates that the goal of the network management intent cannot be achieved in the action airspace #1. It can be understood that if the creation of the network management intent fails due to other reasons (such as information expression errors, etc.), the failure cause information can also indicate other reasons that caused the creation failure.

[0180] It is understandable that if the production entity determines in step S602 that the managed entity can achieve the goal of network management intent when providing services to the terminal device in the action airspace #1, then the production entity may not perform step S603. If the production entity determines in step S602 that the goal of network management intent cannot be achieved, the intent creation request response message in step S603 may also be replaced by other information, such as intent feasibility detection feedback information, etc., which is not particularly limited in this application.

[0181] If the production entity also determines the recommended role space, then the intention to create the request response message may also include the recommended role space. Then the consumption entity may also perform the following step S604.

[0182] Optionally, at S604, the consumer entity determines the role space #2 based on the recommended role space.

[0183] The consumer entity may directly regard the recommended scope space as scope space #2, or may adjust the recommended scope space in combination with the scenario to determine scope space #2, and send scope space #2 to the producer entity. Exemplarily, the consumer entity may regenerate the data structure of the network management intent based on scope space #2, and send an intent creation request message #2 to the producer entity, the intent creation request message #2 including the network management intent, the network management intent including scope space #2, or the intent creation request message #2 including scope space #2.

[0184] It can be understood that the above steps S601 to S604 can be looped N times (it can be understood that in the last loop, there is no recommended scope in the intent creation response message in S603, and step S604 is not executed) until the consumer entity sends scope #N to the producer entity, and the producer entity determines that the managed entity provides services for the terminal device in scope #N, so as to achieve the goal of network management intent and configure the managed entity based on scope #N.

[0185] S605, the production entity configures at least one managed entity of the network management intent based on the action airspace #N, so that the goal of the network management intent is achieved when the at least one managed entity provides services for the terminal device in the action airspace #N.

[0186] The content of step S605 is the same as above Figure 3 The process is similar to that described in step S320 and will not be described in detail here.

[0187] Optionally, S606, the production entity sends intention report information to the consumption entity.

[0188] The content of step S606 is the same as above. Figure 3 The process is similar to that described in step S330 and will not be described in detail here.

[0189] Based on this technical solution, the consumer entity can provide an action airspace associated with the network management intent, so that when the production entity configures the managed entity, the managed entity can concentrate resources to provide services for the terminal devices in the action airspace, avoiding the failure to achieve the goal of the network management intent due to unreasonable configuration, thereby improving the rationality of the network management intent configuration.

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

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

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

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

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

[0195] In a first possible implementation, the transceiver unit 11 is used to receive an action airspace associated with a network management intent; the processing unit 12 is used to configure at least one managed entity of the network management intent based on the action airspace, so that the goal of the network management intent is achieved when at least one managed entity provides services to a terminal device in the action airspace.

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

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

[0198] In a first possible implementation, a processing unit 12 determines an action airspace associated with a network management intent, where the action airspace is used to configure at least one managed entity of the network management intent so that a goal of the network management intent is achieved when at least one managed entity provides services to a terminal device in the action airspace; and a transceiver unit 11 is used to send the action airspace.

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

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

[0201] The device 10 of each of the above schemes has the function of implementing the corresponding steps performed by the communication equipment (such as a production entity, and also such as a consumption entity) in the above method. The function can be implemented by hardware, or by hardware executing the corresponding software implementation. The hardware or software includes at least one module corresponding to the above function; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.

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

[0203] It should be pointed out that Figure 7 The device in the above-mentioned embodiment may be a device, or a chip or a chip system, such as a system on chip (SoC). The transceiver unit may be an input / output circuit or a communication interface; the processing unit may be a processor or a microprocessor or an integrated circuit integrated on the chip. This is not limited here.

[0204] See also Figure 8 , as an example, Figure 82 is a schematic diagram of another communication device 20 provided in an embodiment of the present application. The device 20 includes a processor 21, and the processor 21 is coupled to a memory 22. Optionally, the device 20 also includes a memory 22. The memory 22 is used to store computer programs or instructions and / or data, and the processor 21 is used to execute the computer programs or instructions stored in the memory 22, or read the data stored in the memory 22, so as to execute the methods in the above method embodiments.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0230] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as at least two units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

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

Claims

1. A method for configuring network management intention, characterized in that: The method comprises: receiving a scope associated with a network management intent; At least one managed entity of the network management intent is configured based on the action airspace, so that the goal of the network management intent is achieved when the at least one managed entity provides services for terminal devices in the action airspace.

2. The method according to claim 1, characterized in that The action airspace is represented by a longitude range, a latitude range and an altitude range, or the action airspace is represented by a three-dimensional network coding, or the action airspace is represented by a sphere center coordinate and a sphere radius, or the action airspace is represented by a sector center coordinate, a vertical angle range, a horizontal angle range and a sector side length.

3. The method according to claim 1 or 2, characterized in that The objectives of the network management intention include at least one of the following: the communication bandwidth is within the bandwidth indicator range, the communication delay is within the delay indicator range, the number of communication users is within the user indicator range, the network-aware speed measurement accuracy is within the speed measurement accuracy range, or the network-aware positioning accuracy is within the positioning accuracy range, wherein the network-aware speed measurement accuracy is the accuracy of measuring the speed of a moving object through a network-aware function, and the network-aware positioning accuracy is the accuracy of positioning an object through a network-aware function.

4. The method according to any one of claims 1 to 3, characterized in that The configuring at least one managed entity of the network management intention based on the action airspace so that the goal of the network management intention is achieved when the at least one managed entity provides services for the terminal device in the action airspace includes: At least one managed entity of the network management intention is configured based on the effective airspace, so that the goal of the network management intention is achieved when the at least one managed entity provides services to the terminal device in the effective airspace during the effective time period, wherein the effective airspace contains information about the effective time period.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: A non-effective airspace associated with the network management intention is received, and the at least one managed entity is capable of not providing services to terminal devices in the non-effective airspace.

6. The method according to any one of claims 1 to 5, characterized in that The receiving a scope associated with a network management intent includes: receiving a first request message, wherein 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 scope space, or the first request message includes the network management intent, and the network management intent includes the scope space; or, receiving a second request message, where the second request message is used to request modification of the network management intention, and the second request message includes an identifier of the network management intention and the scope; or, receiving a third request message, the third request message being used to request activation of the network management intent, the third request message comprising an identifier of the network management intent and the scope of action; or, A fourth request message is received, where the fourth request message is used to request to suspend the network management intention, and the fourth request message includes an identifier of the network management intention and the scope space.

7. The method according to any one of claims 1 to 6, characterized in that The configuring at least one managed entity of the network management intention based on the action airspace so that the goal of the network management intention is achieved when the at least one managed entity provides services for the terminal device in the action airspace includes: Acquire information of multiple managed entities of the network management intention; Determine the at least one managed entity from among the multiple managed entities based on the action airspace and information of the multiple managed entities; The at least one managed entity is configured so that the goal of network management intent is achieved when the at least one managed entity provides services to terminal devices in the effective airspace.

8. The method according to claim 7, characterized in that The information of the managed entity includes at least one of the following: location information, frequency information, beam pointing information or beam width information.

9. The method according to any one of claims 1 to 8, characterized in that The service includes any one of a communication service and a perception service.

10. The method according to any one of claims 1 to 9, characterized in that Prior to receiving the action airspace associated with the network management intention, the method further includes: Receiving a target related to the network management intent; Determine a recommended action airspace based on the objectives of the network management intent; The recommended action space is sent, and the recommended action space is used to determine the action space.

11. The method according to any one of claims 1 to 10, characterized in that The method further comprises: Sending intention report information, wherein the intention report information indicates whether the target of the network management intention is achieved when the at least one managed entity provides services for the terminal device in the action airspace.

12. A method for configuring network management intention, characterized in that: The method comprises: Determine a role airspace associated with a network management intent, the role airspace being used to configure at least one managed entity of the network management intent so that a goal of the network management intent is achieved when the at least one managed entity provides services for a terminal device in the role airspace; Send the action space.

13. The method according to claim 12, characterized in that The action airspace is represented by a longitude range, a latitude range and an altitude range, or the action airspace is represented by a three-dimensional network coding, or the action airspace is represented by a sphere center coordinate and a sphere radius, or the action airspace is represented by a sector center coordinate, a vertical angle range, a horizontal angle range and a sector side length.

14. The method according to claim 12 or 13, characterized in that The objectives of the network management intention include at least one of the following: the communication bandwidth is within the bandwidth indicator range, the communication delay is within the delay indicator range, the number of communication users is within the user indicator range, the network-aware speed measurement accuracy is within the speed measurement accuracy range, or the network-aware positioning accuracy is within the positioning accuracy range, wherein the network-aware speed measurement accuracy is the accuracy of measuring the speed of a moving object through a network-aware function, and the network-aware positioning accuracy is the accuracy of positioning an object through a network-aware function.

15. The method according to any one of claims 12 to 14, characterized in that The action airspace contains information indicating an action time period associated with the action airspace, and the action time period is used to configure at least one managed entity of the network management intention so that the goal of the network management intention is achieved when the at least one managed entity provides services to a terminal device in the action airspace during the action time period.

16. The method according to any one of claims 12 to 15, characterized in that The method further comprises: A non-effective airspace associated with the network management intention is sent, and the at least one managed entity is capable of not providing services to terminal devices in the non-effective airspace.

17. The method according to any one of claims 12 to 16, characterized in that The sending of the action airspace includes: Sending 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 scope space, or the first request message includes the network management intent, and the network management intent includes the scope space; or, Sending a second request message, where the second request message is used to request modification of the network management intention, and the second request message includes an identifier of the network management intention and the scope; or, Sending a third request message, where the third request message is used to request activation of the network management intent, and the third request message includes an identifier of the network management intent and the scope; or, A fourth request message is sent, where the fourth request message is used to request to suspend the network management intention, and the fourth request message includes an identifier of the network management intention and the scope.

18. The method according to any one of claims 12 to 17, characterized in that The method comprises: a target for sending said network management intention; A recommended scope is received, where the recommended scope is determined based on a target of the network management intent, and the recommended scope is used to determine the scope.

19. The method according to any one of claims 12 to 18, characterized in that The service includes any one of a communication service and a perception service.

20. The method according to any one of claims 12 to 19, characterized in that The method comprises: Receive intent report information, where the intent report information indicates whether a target of the network management intent is achieved when the at least one managed entity provides services to a terminal device in the action airspace.

21. A method for configuring network management intention, characterized in that: The method comprises: Sending the scope associated with the network management intent; Receiving the action airspace; At least one managed entity of the network management intent is configured based on the action airspace, so that the goal of the network management intent is achieved when the at least one managed entity provides services for terminal devices in the action airspace.

22. A device for configuring network management intention, characterized in that: The device comprises a transceiver unit and a processing unit, wherein: The transceiver unit is used to receive the action airspace associated with the network management intention; The processing unit is used to configure at least one managed entity of the network management intention based on the action airspace, so that the goal of the network management intention is achieved when the at least one managed entity provides services for the terminal device in the action airspace.

23. A device for configuring network management intention, characterized in that: The device comprises a transceiver unit and a processing unit, wherein: The processing unit determines a role airspace associated with a network management intent, the role airspace being used to configure at least one managed entity of the network management intent so that a goal of the network management intent is achieved when the at least one managed entity provides services for a terminal device in the role airspace; The transceiver unit is used to send the effective airspace.

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

25. A communication system, characterized in that: The invention comprises an apparatus for executing the method according to any one of claims 1 to 11 and an apparatus for executing the method according to any one of claims 12 to 20.

26. The system of claim 25, wherein: It also includes managed entities for network management purposes.

27. 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 11, or the computer is caused to execute the method according to any one of claims 12 to 20.

28. 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 11 or causes the computer to implement the method according to any one of claims 12 to 20.

29. 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 11, 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 12 to 20.

30. The device according to claim 29, characterized in that The apparatus also includes the memory.

Images