Intent processing method and related apparatus

Abstract

The present application provides an intent processing method and a related apparatus. In the method, a first device sends first indication information, the first indication information being used for indicating a lifecycle management phase of an intent instance, wherein the lifecycle management phase comprises at least one of a feasibility assessment phase, a resource reservation phase, an exploration phase or an implementation phase of the intent instance; and the first device receives an intent management result obtained by the intent instance in the lifecycle management phase. Hence, the method introduces an intent lifecycle management phase indicating at least one of the feasibility assessment phase, the resource reservation phase, the exploration phase or the implementation phase in which the intent instance can be applied, so that direct implementation of a created intent instance can be prevented, and when the first indication information indicates a corresponding lifecycle management phase, an intent execution system performs corresponding processing on the intent instance on the basis of a network deployment condition and a network state.

Description

Intent processing method and related device

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on January 15, 2024, with application number 202410057520.X and application name “Intent Processing Method and Related Devices”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to an intent processing method and related devices. Background Art

[0003] The increasing number of network access devices and the diversification of services have also led to greater operational complexity. Network automation and intelligence are key networking topics. Their goal is to reduce operating expenditure (OPEX), improve the service experience, and enable various vertical industries (such as autonomous driving and smart cities) through various intelligent and automated technologies. With the continuous advancement of technology and the growth of network complexity, the need for abstract expression of operational requirements, supported by intent, has become increasingly apparent.

[0004] An intent is a user's expression of a desired system state, describing the network or service they desire. An intent does not define specific network or service configuration parameters, nor does it specify the management tasks to be performed by the system. Intents allow users to request networks and services without detailed knowledge of how these networks and services are provided. The system is assumed to automatically learn network and service behavior and employ intelligent and automated mechanisms to meet the needs expressed by users through intents. The intent execution system interprets intents based on intent information, such as the intent object and intent target, to obtain network configuration parameters and distribute them to the corresponding network elements for configuration and execution.

[0005] However, the capability of the intent execution system is determined by the network deployment and network status, and changes in real time. In this case, how to process intent is an unresolved problem. Summary of the Invention

[0006] The present application provides an intent processing method and related devices, which are conducive to intent processing in combination with network deployment conditions and network status.

[0007] In the first aspect, the present application provides an intent processing method, which can be applied to an intent monitoring system, or a device or apparatus deployed with an intent monitoring system. For ease of explanation, the first device is used as an example. In this method, the first device sends a first indication message, which is used to indicate the lifecycle management stage of the intent instance; wherein the lifecycle management stage includes at least one of the feasibility assessment stage, resource reservation stage, exploration stage, or implementation stage of the intent instance; accordingly, the first device receives the intent management result obtained by the intent instance during the lifecycle management stage.

[0008] It can be seen that the method, by introducing the intention lifecycle management stage, refers to at least one of the feasibility assessment stage, resource reservation stage, exploration stage or implementation stage that the schematic instance can be used for. In this way, the present application can avoid the immediate implementation of the intent instance after it is created, which is beneficial for the intent execution system to combine the network deployment situation and network status to process the intent instance accordingly after the first indication information indicates the corresponding lifecycle management stage. Specifically, the present application can achieve at least one of the following beneficial effects: it can perform a feasibility assessment on the intent instance before the intention is implemented, and then implement it when the expectations of the intent instance are met; or it can reserve resources before the intention instance is implemented to ensure that there are sufficient resources to meet the expectations of the intent instance during the implementation of the intent; or it can be beneficial to obtain the capability value of the intent instance through the exploration stage before the intention instance is implemented, and then it can be beneficial to select the target value expected by the intent, avoiding the problem that the expectations of the intent instance cannot be met due to multiple blind settings or the target value is set too low, resulting in the inability to obtain better network performance; or it can be implemented when the first device indicates that the schematic instance is used for implementation, avoiding the problem that the created intent instance is directly implemented, resulting in the inability to perform the above-mentioned stages of intention negotiation.

[0009] In an optional implementation, the first device sends a first indication message, including: the first device sends a first request, the first request is used to request the creation of an intent instance, the first request includes intent information and first indication information, the intent information includes the intent object and intent target of the intent instance; and, receives a response message, the response information includes an identifier of the intent instance. Optionally, the first request is used to request the creation of an intent instance. The intent instance is used to describe the expected state of the managed object; the intent object is the information of the managed object; the intent target is the performance indicator of the managed object. It can be seen that this implementation is conducive to creating an intent instance based on the lifecycle management stage indicated by the first indication message, avoiding problems such as information inconsistency caused by the need to maintain multiple intent instances for the same intent information.

[0010] In an optional implementation, the lifecycle management stage indicated by the first indication information is the feasibility assessment stage; the intent management result obtained by the intent instance in the lifecycle management stage is the feasibility assessment result obtained by the intent instance in the feasibility assessment stage. It can be seen that this implementation receives the feasibility assessment result of the intent instance before the intent instance is implemented, and can determine whether the intent instance is feasible, that is, whether the intent goal of the intent instance is met.

[0011] Optionally, the first device receiving the feasibility assessment result includes: the first device receiving a feasibility assessment report, wherein the feasibility assessment report includes the feasibility assessment result. Optionally, when the feasibility assessment result is infeasible, the feasibility assessment report also includes a reason for infeasibility, such as conflicting intent, insufficient resources, etc. In addition, the feasibility assessment report also includes an identifier of the intent instance.

[0012] In an optional implementation, the lifecycle management stage indicated by the first indication information is the resource reservation stage; the intent management result obtained by the intent instance in the lifecycle management stage is the resource reservation result obtained by the intent instance in the resource reservation stage. It can be seen that this implementation method reserves resources before the intent instance is implemented, which can ensure sufficient resource guarantees during the implementation of the intent instance.

[0013] Optionally, the first device receiving the resource reservation result includes: the first device receiving a resource reservation report, wherein the resource reservation report includes the resource reservation result, such as reserved or reservation failed. Optionally, the resource reservation report also includes the network device and / or cell associated with the reserved resources, and the number or proportion of the reserved resources, wherein the proportion is the ratio of the number of reserved resources to the total number of resources of the network device and / or cell.

[0014] In one embodiment, the lifecycle management stage indicated by the first indication information sent by the first device includes a feasibility assessment stage and a resource reservation stage. Then, the intention management result received by the first device, such as the feasibility assessment result and the resource reservation result described above, can be received separately or in combination. In another embodiment, the lifecycle management stage indicated by the first indication information sent by the first device is the feasibility assessment stage. The first device also sends a second request, and the second request includes indication information of the resource reservation stage or the second request is used to request to modify the lifecycle management stage indicated by the first indication information to the resource reservation stage. Then, the first device can receive the feasibility assessment result and the resource reservation result described above, respectively. Optionally, the first device sends the second request when there is a resource reservation requirement.

[0015] In an optional implementation, the lifecycle management stage indicated by the first indication information is the exploration stage; the intent management result obtained by the intent instance in the lifecycle management stage is the intent exploration result obtained by the intent instance in the exploration stage, and each intent exploration result includes the capability value of the intent target of the intent instance. It can be seen that this implementation obtains the capability value of the intent target before the intent instance is implemented, which helps to avoid the intention target being unattainable due to blindly setting the target value, or the setting of the target value is too low, resulting in the inability to obtain better energy consumption and performance effects of the network.

[0016] Optionally, the first device receives the intent exploration result, including: the first device receives the intent exploration report, wherein the intent exploration report includes at least one intent exploration result. In addition, the intent exploration report also includes an identifier of the intent instance. Each intent exploration result includes the name of the intent target (such as energy consumption target and rate target), and the capability value of the corresponding intent target (such as the current capability value and the capability value within the predicted time or predicted duration).

[0017] Optionally, after receiving the intent exploration result, the first device further determines the target value of the intent goal (such as the target value of energy consumption and the target value of downlink rate) based on the intent exploration result obtained during the exploration phase of the intent instance, and sends the target value of the intent goal. This embodiment determines the target value based on the capability value of the currently explored intent goal, thereby avoiding the intent goal being unattainable due to blindly setting the target value, or the target value being set too low to fully stimulate network capabilities.

[0018] Optionally, if the intent exploration report includes at least two intent exploration results, the first device may select a capability value included in one of the intent exploration results as the target value of the intent target.

[0019] In one optional implementation, the first indication information indicates that the lifecycle management phase is the implementation phase. In this case, the intent management result received by the first device is the intent execution result obtained by the intent instance during the implementation phase. This indicates that in this implementation, the first device instructs the intent instance to implement the intent instance through the first indication information, avoiding immediate implementation of the intent instance after creation.

[0020] In another optional implementation, the lifecycle management stage indicated by the first indication information is at least one of the feasibility assessment stage, resource reservation stage or exploration stage mentioned above. After the first device sends the first indication information and receives the corresponding intent management result, it also sends the second indication information, and the second indication information is used to indicate that the lifecycle management stage of the modified intent instance is the implementation stage; and receive the intent execution result obtained by the intent instance in the implementation stage. It can be seen that this implementation is conducive to intention negotiation based on the various lifecycle management stages mentioned above, avoiding the problem of information inconsistency caused by repeatedly creating intent instances with the same intent information, and enabling the successful implementation of the intent instance.

[0021] In an optional embodiment, in addition to the lifecycle management stage indicated by the first indication information of the first device being or including the feasibility assessment stage, the first device also sends evaluation constraint information, wherein the evaluation constraint information includes indication information for indicating the simulation technology, and / or indication information for indicating whether to perform simulation online or offline. For example, if the simulation technology indicated by the evaluation constraint information is network digital twin (NDT), then the feasibility assessment result is obtained by simulation assessment using NDT technology. In addition, if the evaluation constraint information indicates online simulation, the feasibility assessment result is obtained by online simulation assessment; if the evaluation constraint information indicates offline simulation, the feasibility assessment result is obtained by offline simulation assessment.

[0022] In another optional embodiment, in addition to the lifecycle management stage indicated by the first indication information of the first device being or including the exploration stage, the first device also sends the evaluation constraint information described above. For example, if the simulation technology indicated by the evaluation constraint information is NDT, then the intention exploration result is obtained by simulation evaluation using the NDT technology. In addition, if the evaluation constraint information indicates that the simulation is to be performed online, the intention exploration result is obtained by online simulation evaluation; if the evaluation constraint information indicates that the simulation is to be performed offline, the intention exploration result is obtained by offline simulation evaluation.

[0023] In one optional implementation, the intent instance is a wireless service intent instance. The intent object of the wireless service intent instance includes geographical coverage information of a network device or cell, and the intent target of the wireless service intent instance includes a latency target and / or a rate target. Optionally, one or more of the above-described implementations may be employed for the wireless service intent instance and will not be described in detail here.

[0024] In one optional embodiment, the intent instance is a wireless energy-saving intent instance. The intent object of the wireless energy-saving intent instance includes geographical coverage information of a network device or cell, and the intent target of the wireless energy-saving intent instance includes an energy consumption target and / or a rate target. Optionally, one or more of the above-described embodiments may be employed for the wireless energy-saving intent instance and will not be described in detail here.

[0025] In a second aspect, the present application also provides an intent processing method, which can be applied to an intent execution system, or a device or apparatus deployed with an intent execution system. For ease of explanation, the second device is used as an example. In this method, the second device receives first indication information, which is used to indicate the lifecycle management stage of the intent instance; wherein the lifecycle management stage includes at least one of the feasibility assessment stage, resource reservation stage, exploration stage, or implementation stage of the intent instance; and the second device sends the intent management result obtained by the intent instance in the lifecycle management stage.

[0026] Optionally, the second device also manages the intent instance according to the lifecycle management stage indicated by the first indication information to obtain the intent management result.

[0027] It can be seen that the method, by introducing the intention lifecycle management stage, refers to at least one of the feasibility assessment stage, resource reservation stage, exploration stage or implementation stage in which the schematic instance can be used. In this way, the present application can avoid the immediate implementation of the intent instance after creation, and is conducive to processing the intent instance in the feasibility assessment stage, resource reservation stage, exploration stage or implementation stage in combination with the network deployment situation and network status. Specifically, the present application can achieve at least one of the following beneficial effects: it can perform a feasibility assessment on the intent instance before the intent is implemented, and then implement it when the expectations of the intent instance are met; or it can reserve resources before the intent instance is implemented to ensure that there are sufficient resources to meet the expectations of the intent instance during the implementation of the intent; or it can be conducive to obtaining the capability value of the intent instance through the exploration stage before the intent instance is implemented, and then it can be conducive to selecting the target value expected by the intent, avoiding the problem that the expectations of the intent instance cannot be met due to multiple blind settings or the target value is set too low, resulting in the inability to obtain better network performance; or it can be implemented in the implementation stage when the first indication information indicates that the schematic instance is used to avoid the problem that the created intent instance is directly implemented, resulting in the inability to perform the above-mentioned stages of intention negotiation.

[0028] In an optional embodiment, the second device receives the first indication information, including: the second device receives the first request, the first request includes intent information and first indication information, the intent information includes the intent object and intent target of the intent instance; accordingly, the method also includes: the second device creates an intent instance based on the intent information, the intent instance includes the desired intent object and intent target, and also includes information on the lifecycle management stage indicated by the first indication information; and, sends a response message, the response message includes an identifier of the intent instance.

[0029] In an optional implementation, the lifecycle management stage indicated by the first indication information is the feasibility assessment stage; the intent management result obtained by the intent instance during the lifecycle management stage includes the feasibility assessment result obtained by the intent instance during the feasibility assessment stage. Accordingly, the second device also manages the intent instance according to the lifecycle management stage indicated by the first indication information and obtains the intent management result, including: the second device performs a feasibility assessment on the intent instance and obtains the feasibility assessment result.

[0030] Optionally, the second device sending the feasibility assessment result includes: the second device sending a feasibility assessment report, wherein the feasibility assessment report includes the feasibility assessment result. Optionally, when the feasibility assessment result is infeasible, the feasibility assessment report also includes a reason for infeasibility, such as conflicting intent, insufficient resources, etc. In addition, the feasibility assessment report also includes an identifier of the intent instance.

[0031] In an optional implementation, the lifecycle management stage indicated by the first indication information is the resource reservation stage; the intent management result obtained by the intent instance in the lifecycle management stage includes the resource reservation result obtained by the intent instance in the resource reservation stage. It can be seen that in this implementation, the second device reserves resources for the intent instance before the intent instance is implemented, which can ensure sufficient resources during the implementation of the intent instance.

[0032] Correspondingly, the second device also manages the intent instance according to the lifecycle management stage indicated by the first indication information and obtains the intent management result, including: the second device reserves corresponding resources for the intent instance and obtains the resource reservation result.

[0033] Optionally, the second device sending the resource reservation result includes: the second device sending a resource reservation report, wherein the resource reservation report includes the resource reservation result, such as reserved or reservation failed. Optionally, the resource reservation report also includes the network device and / or cell associated with the reserved resources, and the number or proportion of the reserved resources, wherein the proportion is the ratio of the number of reserved resources to the total number of resources of the network device and / or cell.

[0034] In one embodiment, the lifecycle management stage indicated by the first indication information received by the second device includes a feasibility assessment stage and a resource reservation stage. Then, the intention management results sent by the second device, such as the feasibility assessment results and resource reservation results described above, can be sent separately or combined.

[0035] In another embodiment, the lifecycle management stage indicated by the first indication information received by the second device is the feasibility assessment stage. The second device may also receive a second request, which includes indication information of the resource reservation stage or the second request is used to request that the lifecycle management stage indicated by the first indication information be modified to the resource reservation stage. In this way, the second device can modify the previous value of the lifecycle management stage to the value of the resource reservation stage, for example, if the previous value was the feasibility assessment stage, the modified value is the resource reservation stage. In this embodiment, the second device sends the feasibility assessment result and resource reservation result described above respectively.

[0036] In one embodiment, the lifecycle management phase indicated by the first indication information is the exploration phase; the intent management result obtained by the intent instance during the lifecycle management phase includes the intent exploration result obtained by the intent instance during the exploration phase; wherein each intent exploration result includes the capability value of the intent target of the intent instance. It can be seen that this embodiment can explore the capability value of the intent target before the intent instance is implemented, thereby helping to avoid the intent target being unattainable due to blindly setting the target value, or the target value being set too low, resulting in the inability to obtain better energy consumption and performance effects of the network.

[0037] Optionally, the second device sending the intent exploration result includes: the second device sending an intent exploration report, wherein the intent exploration report includes at least one intent exploration result. In addition, the intent exploration report also includes an identifier of the intent instance. Each intent exploration result includes the name of the intent target (such as energy consumption target and rate target), and the capability value of the corresponding intent target (such as the current capability value and the capability value within the predicted time or predicted duration). Accordingly, the second device explores and evaluates the intent instance to obtain an intent exploration result or an intent exploration report.

[0038] In an optional implementation, after the second device sends the intent exploration report or intent exploration result to the first device, it also receives the target value of the intent target from the first device, where the target value of the intent target is determined by the first device based on the capability value of the intent target. It can be seen that in this implementation, the target value is determined by the first device based on the capability value of the currently explored intent target, thereby avoiding the intent target being unattainable due to blindly setting the target value, or the target value being set too low to fully stimulate the network capability.

[0039] In an optional implementation, the lifecycle management phase indicated by the first indication information is the implementation phase. In this case, the intent management result sent by the second device is the intent execution result obtained by the intent instance during the implementation phase. Optionally, the second device implements the intent instance to obtain the intent execution result. This shows that this implementation avoids immediate implementation of the intent instance after it is created by indicating the implementation of the intent instance through the first indication information.

[0040] In another optional implementation, the lifecycle management stage indicated by the first indication information is at least one of the feasibility assessment stage, resource reservation stage or exploration stage described above. After the second device receives the first indication information and sends the corresponding intent management result, it also receives the second indication information, and the second indication information is used to indicate that the lifecycle management stage of the modified intent instance is the implementation stage. Optionally, the second device modifies the lifecycle management stage of the intent instance to the implementation stage, and implements the intent instance to obtain the intent execution result. The second device sends the intent execution result. It can be seen that this implementation is conducive to intention negotiation based on the various lifecycle management stages described above, avoiding the problem of information inconsistency caused by repeated creation of intent instances with the same intent information, so that the intent instance can be successfully implemented.

[0041] In one optional embodiment, in addition to receiving the first indication information indicating that the lifecycle management stage is or includes the feasibility assessment stage, the second device also receives evaluation constraint information, where the evaluation constraint information includes information indicating a simulation technology and / or information indicating whether to perform online or offline simulation. For example, if the simulation technology indicated by the evaluation constraint information is NDT, then the feasibility assessment result is obtained through simulation evaluation using the NDT technology. Furthermore, if the evaluation constraint information indicates online simulation, then the feasibility assessment result is obtained through online simulation evaluation; if the evaluation constraint information indicates offline simulation, then the feasibility assessment result is obtained through offline simulation evaluation. In another optional embodiment, in addition to receiving the first indication information indicating that the lifecycle management stage is or includes the exploration stage, the second device also receives the aforementioned evaluation constraint information. For example, if the simulation technology indicated by the evaluation constraint information is NDT, then the intended exploration result is obtained through simulation evaluation using the NDT technology. Furthermore, if the evaluation constraint information indicates online simulation, then the intended exploration result is obtained through online simulation evaluation; if the evaluation constraint information indicates offline simulation, then the intended exploration result is obtained through offline simulation evaluation.

[0042] Optionally, the evaluation constraint information may be included in the first request carrying the first indication information.

[0043] In one optional implementation, the intent instance is a wireless service intent instance. The intent object of the wireless service intent instance includes geographical coverage information of a network device or cell, and the intent target of the wireless service intent instance includes a latency target and / or a rate target. Optionally, one or more of the above-described implementations may be employed for the wireless service intent instance and will not be described in detail here.

[0044] In one optional embodiment, the intent instance is a wireless energy-saving intent instance. The intent object of the wireless energy-saving intent instance includes geographical coverage information of a network device or cell, and the intent target of the wireless energy-saving intent instance includes an energy consumption target and / or a rate target. Optionally, one or more of the above-described embodiments may be employed for the wireless energy-saving intent instance and will not be described in detail here.

[0045] On the third aspect, the present application provides an intent processing method for a wireless service intent instance, which can be applied to an intent monitoring system, or a device or apparatus deployed with an intent monitoring system. For ease of explanation, the first device is used as an example. In this method, the first device sends a first indication message, which is used to indicate the lifecycle management stage of the wireless service intent instance; wherein the lifecycle management stage includes at least one of the feasibility assessment stage, resource reservation stage, or implementation stage of the wireless service intent instance; accordingly, the first device receives the intent management result obtained by the wireless service intent instance in the lifecycle management stage.

[0046] It can be seen that the method introduces the intention lifecycle management stage to indicate at least one of the feasibility assessment stage, resource reservation stage or implementation stage that the wireless service intention instance can be used for. In this way, the present application can avoid the immediate implementation of the intention instance after it is created, which is beneficial for the intention execution system to process the intention instance accordingly in combination with the network deployment situation and network status after the first indication information indicates the lifecycle management stage that the intention instance is used for. Specifically, the present application can achieve at least one of the following beneficial effects: it can perform a feasibility assessment on the wireless service intention instance before the wireless service intention is implemented, and implement it when the expectations of the wireless service intention instance are met; or it can reserve resources before the wireless service intention instance is implemented to ensure that there are sufficient resources to meet the expectations of the wireless service intention instance during the intention implementation process; or it can be implemented after the first device indicates that the wireless service intention instance is used for the implementation stage, avoiding the problem that the created wireless service intention instance is directly implemented and cannot perform the above-mentioned stages of intention negotiation.

[0047] In an optional implementation, the first device sends a first indication message, including: the first device sends a first request, the first request is used to request the creation of a wireless service intention instance, the first request includes intention information and first indication information, the intention information includes the intention object and intention target of the wireless service intention instance, wherein the intention object includes the coverage geographical area information of the network device or cell, and the intention target includes the delay target and the rate target. Optionally, the first request is used to request the creation of an intention instance. The intention instance is used to describe the expected state of the managed object; the intention object is the information of the managed object; the intention target is the performance indicator of the managed object. It can be seen that this implementation is conducive to creating a wireless service intention instance based on the lifecycle management stage indicated by the first indication message, avoiding problems such as information inconsistency caused by the need to maintain multiple wireless service intention instances for the same intention information.

[0048] In one optional implementation, the lifecycle management stage indicated by the first indication information is the feasibility assessment stage; the intent management result obtained by the wireless service intent instance in the lifecycle management stage is the feasibility assessment result obtained by the wireless service intent instance in the feasibility assessment stage. This shows that this implementation receives the feasibility assessment result of the wireless service intent instance before the wireless service intent instance is implemented, and is able to determine whether the wireless service intent instance is feasible, that is, whether the intent goal of the wireless service intent instance is met.

[0049] Optionally, the first device receiving the feasibility assessment result includes: the first device receiving a feasibility assessment report, wherein the feasibility assessment report includes the feasibility assessment result. Optionally, when the feasibility assessment result is infeasible, the feasibility assessment report also includes a reason for infeasibility, such as conflicting intent, insufficient resources, etc. In addition, the feasibility assessment report also includes an identifier of the intent instance.

[0050] In one optional implementation, the lifecycle management phase indicated by the first indication information is the resource reservation phase; and the intent management result obtained by the wireless service intent instance during the lifecycle management phase is the resource reservation result obtained by the wireless service intent instance during the resource reservation phase. This shows that this implementation, by reserving resources before implementing the wireless service intent instance, can ensure sufficient resources during the implementation of the wireless service intent instance.

[0051] Optionally, the first device receives a resource reservation result, including: the first device receives a resource reservation report, wherein the resource reservation report includes a resource reservation result, such as reserved or reservation failed. Optionally, the resource reservation report also includes the network device and / or cell associated with the reserved resources, and the number or proportion of reserved resources, wherein the proportion is the ratio of the number of reserved resources to the total number of resources of the network device and / or cell. Optionally, the reserved resources include at least one of wireless physical resource block (PRB) resources, the number of connections of the radio resource controller (RRC), or data radio bearer (DRB) resources.

[0052] In one embodiment, the lifecycle management stage indicated by the first indication information sent by the first device includes a feasibility assessment stage and a resource reservation stage. Then, the intention management result received by the first device, such as the feasibility assessment result and the resource reservation result described above, can be received separately or in combination. In another embodiment, the lifecycle management stage indicated by the first indication information sent by the first device is the feasibility assessment stage. The first device also sends a second request, and the second request includes indication information of the resource reservation stage or the second request is used to request to modify the lifecycle management stage indicated by the first indication information to the resource reservation stage. Then, the first device can receive the feasibility assessment result and the resource reservation result described above, respectively. Optionally, the first device sends the second request when there is a resource reservation requirement.

[0053] In one optional embodiment, the lifecycle management phase indicated by the first indication information is the implementation phase. In this case, the intent management result received by the first device is the intent execution result obtained by the wireless service intent instance during the implementation phase. Therefore, in this embodiment, the first device instructs the wireless service intent instance to implement via the first indication information, thus avoiding immediate implementation of the wireless service intent instance after creation.

[0054] In another optional implementation, the lifecycle management stage indicated by the first indication information is at least one of the feasibility assessment stage or the resource reservation stage described above. After the first device sends the first indication information and receives the corresponding intent management result, it also sends the second indication information, and the second indication information is used to indicate that the lifecycle management stage of the wireless service intent instance is modified to the implementation stage; and receive the intent execution result obtained by the wireless service intent instance in the implementation stage. It can be seen that this implementation is conducive to intent negotiation based on the various lifecycle management stages described above, avoiding the problem of information inconsistency caused by repeatedly creating wireless service intent instances with the same intent information, and enabling the successful implementation of wireless service intent instances.

[0055] In an optional embodiment, in addition to the lifecycle management stage indicated by the first indication information of the first device being or including the feasibility assessment stage, the first device also sends evaluation constraint information, wherein the evaluation constraint information includes indication information for indicating the simulation technology, and / or indication information for indicating whether to perform simulation online or offline. For example, if the simulation technology indicated by the evaluation constraint information is network digital twin (NDT), then the feasibility assessment result is obtained by simulation assessment using NDT technology. In addition, if the evaluation constraint information indicates online simulation, the feasibility assessment result is obtained by online simulation assessment; if the evaluation constraint information indicates offline simulation, the feasibility assessment result is obtained by offline simulation assessment.

[0056] Optionally, the evaluation constraint information may be included in the first request carrying the first indication information.

[0057] In a fourth aspect, the present application also provides an intent processing method for a wireless service intent instance, which corresponds to the intent processing method described in the third aspect and is explained from the perspective of a second device. In the intent processing method, the second device receives first indication information, which is used to indicate the lifecycle management stage of the wireless service intent instance; wherein the lifecycle management stage includes at least one of the feasibility assessment stage, resource reservation stage, or implementation stage of the wireless service intent instance; and the second device sends the intent management result obtained by the wireless service intent instance in the lifecycle management stage.

[0058] Optionally, the second device also manages the wireless service intent instance according to the lifecycle management stage indicated by the first indication information to obtain an intent management result.

[0059] It can be seen that the method, by introducing the intent lifecycle management stage, indicates at least one of the feasibility assessment stage, resource reservation stage or implementation stage that the wireless service intent instance can be used for. In this way, the present application can avoid the immediate implementation of the intent instance after creation, which is conducive to processing the intent instance in the feasibility assessment stage, resource reservation stage or implementation stage in combination with the network deployment situation and network status. Specifically, the present application can achieve at least one of the following beneficial effects: it can perform a feasibility assessment on the wireless service intent instance before the wireless service intent instance is implemented, and implement it when the expectations of the wireless service intent instance are met; or it can reserve resources before the wireless service intent instance is implemented to ensure that there are sufficient resources to meet the expectations of the wireless service intent instance during the implementation of the wireless service intent; or it can be implemented after the first indication information indicates that the wireless service intent instance is used for the implementation stage, thereby avoiding the problem that the created wireless service intent instance is directly implemented and cannot perform the above-mentioned stages of intent negotiation.

[0060] In an optional implementation, the second device receives the first indication information, including: the second device receives a first request, the first request includes intent information and first indication information, and the intent information includes the intent object and intent target of the wireless service intent instance. The intent object includes the coverage geographical area information of the network device or cell, and the intent target includes the latency target and the rate target. Accordingly, the method also includes: the second device creates a wireless service intent instance based on the intent information, the wireless service intent instance includes the desired intent object and intent target, and also includes information on the lifecycle management stage indicated by the first indication information.

[0061] In an optional implementation, the lifecycle management stage indicated by the first indication information is the feasibility assessment stage; the intent management result obtained by the wireless service intent instance during the lifecycle management stage includes the feasibility assessment result obtained by the wireless service intent instance during the feasibility assessment stage. Accordingly, the second device also manages the wireless service intent instance according to the lifecycle management stage indicated by the first indication information and obtains the intent management result, including: the second device performs a feasibility assessment on the wireless service intent instance and obtains the feasibility assessment result.

[0062] Optionally, the second device transmitting the feasibility assessment result includes: the second device transmitting a feasibility assessment report, wherein the feasibility assessment report includes the feasibility assessment result. Optionally, when the feasibility assessment result is infeasible, the feasibility assessment report also includes a reason for infeasibility, such as an intent conflict, insufficient resources, etc. In addition, the feasibility assessment report also includes an identifier of the wireless service intent instance.

[0063] In an optional implementation, the lifecycle management phase indicated by the first indication information is the resource reservation phase; the intent management result obtained by the wireless service intent instance during the lifecycle management phase includes the resource reservation result obtained by the wireless service intent instance during the resource reservation phase. This indicates that in this implementation, the second device reserves resources for the wireless service intent instance before the wireless service intent instance is implemented, thereby ensuring sufficient resources during the implementation of the wireless service intent instance.

[0064] Correspondingly, the second device also manages the wireless service intention instance according to the lifecycle management stage indicated by the first indication information and obtains the intention management result, including: the second device reserves corresponding resources for the wireless service intention instance and obtains the resource reservation result.

[0065] Optionally, the second device sending the resource reservation result includes: the second device sending a resource reservation report, wherein the resource reservation report includes the resource reservation result, such as reserved or reservation failed. Optionally, the resource reservation report also includes the network device and / or cell associated with the reserved resources, and the number or proportion of the reserved resources, wherein the proportion is the ratio of the number of reserved resources to the total number of resources of the network device and / or cell.

[0066] In one embodiment, the lifecycle management stage indicated by the first indication information received by the second device includes a feasibility assessment stage and a resource reservation stage. Then, the intention management results sent by the second device, such as the feasibility assessment results and resource reservation results described above, can be sent separately or combined.

[0067] In another embodiment, the lifecycle management stage indicated by the first indication information received by the second device is the feasibility assessment stage. The second device may also receive a second request, which includes indication information of the resource reservation stage or the second request is used to request that the lifecycle management stage indicated by the first indication information be modified to the resource reservation stage. In this way, the second device can modify the previous value of the lifecycle management stage to the value of the resource reservation stage, for example, if the previous value was the feasibility assessment stage, the modified value is the resource reservation stage. In this embodiment, the second device sends the feasibility assessment result and resource reservation result described above respectively.

[0068] In one optional implementation, the lifecycle management phase indicated by the first indication information is the implementation phase. The intent management result sent by the second device is the intent execution result obtained by the wireless service intent instance during the implementation phase. Optionally, the second device implements the wireless service intent instance to obtain the intent execution result. This embodiment avoids immediate implementation of the wireless service intent instance after creation by indicating the implementation of the wireless service intent instance through the first indication information.

[0069] In another optional implementation, the lifecycle management stage indicated by the first indication information is at least one of the feasibility assessment stage or the resource reservation stage described above. After the second device receives the first indication information and sends the corresponding intent management result, it also receives the second indication information, and the second indication information is used to indicate that the lifecycle management stage of the wireless service intent instance is modified to the implementation stage. Optionally, the second device modifies the lifecycle management stage of the wireless service intent instance to the implementation stage, and implements the wireless service intent instance to obtain the intent execution result. The second device sends the intent execution result. It can be seen that this implementation is conducive to intent negotiation based on the various lifecycle management stages described above, avoiding the problem of information inconsistency caused by repeated creation of wireless service intent instances with the same intent information, so that the wireless service intent instance can be successfully implemented.

[0070] In an optional embodiment, in addition to receiving the first indication information indicating that the lifecycle management stage is or includes a feasibility assessment stage, the second device also receives evaluation constraint information, wherein the evaluation constraint information includes indication information for indicating a simulation technology, and / or indication information for indicating whether to perform simulation online or offline. For example, if the simulation technology indicated by the evaluation constraint information is NDT, then the feasibility assessment result is obtained by performing simulation assessment using the NDT technology. In addition, if the evaluation constraint information indicates that the simulation is to be performed online, then the feasibility assessment result is obtained by using an online simulation assessment; if the evaluation constraint information indicates that the simulation is to be performed offline, then the feasibility assessment result is obtained by using an offline simulation assessment.

[0071] Optionally, the evaluation constraint information may be included in the first request carrying the first indication information.

[0072] In a fifth aspect, the present application also provides an intent processing method for a wireless energy-saving intention instance. The method can be applied to an intent monitoring system, or a device or apparatus deployed with an intent monitoring system. For ease of explanation, the first device is used as an example. In the method, the first device sends a first indication message, which is used to indicate the lifecycle management stage of the wireless energy-saving intention instance; wherein the lifecycle management stage includes at least one of the exploration stage or the implementation stage of the wireless energy-saving intention instance; accordingly, the first device receives the intent management result obtained by the wireless energy-saving intention instance in the lifecycle management stage.

[0073] It can be seen that the method indicates at least one of the exploration phase or implementation phase that the wireless energy-saving intention instance can be used for by introducing the intention lifecycle management phase. In this way, the present application can avoid the immediate implementation of the intention instance after it is created, which is beneficial for the intention execution system to process the intention instance in combination with the network deployment situation and network status after the first indication information indicates the corresponding lifecycle management phase. Specifically, the present application can achieve at least one of the following beneficial effects: it is beneficial to obtain the capability value of the wireless energy-saving intention instance through the exploration phase before the wireless energy-saving intention instance is implemented, and then it is beneficial to select the target value expected by the intention, avoiding the problem that the expectations of the wireless energy-saving intention instance cannot be met due to multiple blind settings or the target value is set too low, resulting in the inability to obtain better network performance; or, after the first device indicates that the wireless energy-saving intention instance is used for the implementation phase, it is implemented to avoid the problem that the created wireless energy-saving intention instance is directly implemented, resulting in the inability to perform the above-mentioned stages of intention negotiation.

[0074] In an optional implementation, the first device sends a first indication message, including: the first device sends a first request, the first request is used to request the creation of a wireless energy-saving intention instance, the first request includes intent information and first indication information, and the intent information includes the intent object and intent target of the wireless energy-saving intention instance. Among them, the intent object includes the coverage geographical area information of the network device or cell, and the intent target includes the energy consumption target and the rate target. Optionally, the first request is used to request the creation of an intent instance. The wireless energy-saving intention instance is used to describe the expected state of the managed object; the intent object is the information of the managed object; the intent target is the performance indicator of the managed object. It can be seen that this implementation is conducive to creating a wireless energy-saving intention instance based on the lifecycle management stage indicated by the first indication message, avoiding problems such as information inconsistency caused by the need to maintain multiple wireless energy-saving intention instances for the same intent information.

[0075] In one optional implementation, the lifecycle management phase indicated by the first indication information is the exploration phase; the intent management result obtained by the wireless energy-saving intent instance during the lifecycle management phase is the intent exploration result obtained by the wireless energy-saving intent instance during the exploration phase, and each intent exploration result includes the capability value of the intent target of the wireless energy-saving intent instance. This embodiment obtains the capability value of the intent target before implementing the wireless energy-saving intent instance, thereby preventing the intent target from being unattainable due to blindly setting the target value, or preventing the target value from being set too low, resulting in the inability to achieve better energy consumption and performance results for the network.

[0076] Optionally, the first device receiving the intent exploration result includes: the first device receiving the intent exploration report, wherein the intent exploration report includes at least one intent exploration result. In addition, the intent exploration report also includes an identifier of the wireless energy-saving intention instance. Each intent exploration result includes the name of the intent target (such as an energy consumption target and a rate target), and the capability value of the corresponding intent target (such as the current capability value and the capability value within the predicted time or predicted duration).

[0077] Optionally, after receiving the intent exploration result, the first device further determines the target value of the intent goal (such as the target value of energy consumption and the target value of downlink rate) based on the intent exploration result obtained during the exploration phase of the wireless energy-saving intent instance, and sends the target value of the intent goal. This embodiment determines the target value based on the capability value of the currently explored intent goal, thereby avoiding the intent goal being unattainable due to blindly setting the target value, or the target value being set too low to fully stimulate network capabilities.

[0078] Optionally, if the intent exploration report includes at least two intent exploration results, the first device may select a capability value included in one of the intent exploration results as the target value of the intent target.

[0079] In one optional embodiment, the first indication information indicates that the lifecycle management phase is the implementation phase. In this case, the intent management result received by the first device is the intent execution result obtained by the wireless power saving intent instance during the implementation phase. Thus, in this embodiment, the first device instructs the wireless power saving intent instance to be implemented via the first indication information, avoiding immediate implementation of the wireless power saving intent instance after creation.

[0080] In another optional implementation, the lifecycle management stage indicated by the first indication information is the exploration stage described above. After the first device sends the first indication information and receives the corresponding intent management result, it also sends a second indication information, the second indication information being used to indicate that the lifecycle management stage of the modified intent instance is the implementation stage; and receives the intent execution result obtained by the intent instance in the implementation stage. It can be seen that this implementation is conducive to intent negotiation based on the exploration stage described above, avoiding the problem of information inconsistency caused by repeatedly creating wireless energy-saving intent instances with the same intent information, and enabling the successful implementation of wireless energy-saving intent instances.

[0081] In another optional embodiment, in addition to the lifecycle management stage indicated by the first indication information of the first device being or including the exploration stage, the first device also sends the evaluation constraint information described above. For example, if the simulation technology indicated by the evaluation constraint information is NDT, then the intention exploration result is obtained by simulation evaluation using the NDT technology. In addition, if the evaluation constraint information indicates that the simulation is to be performed online, the intention exploration result is obtained by online simulation evaluation; if the evaluation constraint information indicates that the simulation is to be performed offline, the intention exploration result is obtained by offline simulation evaluation.

[0082] In a sixth aspect, the present application also provides an intent processing method for a wireless energy-saving intention instance. The method can be applied to an intent execution system, or a device or apparatus deployed with an intent execution system. For ease of explanation, the second device is used as an example. In the method, the second device receives first indication information, which is used to indicate the lifecycle management stage of the wireless energy-saving intention instance; wherein the lifecycle management stage includes at least one of the exploration stage or the implementation stage of the wireless energy-saving intention instance; and the second device sends the intent management result obtained by the wireless energy-saving intention instance in the lifecycle management stage.

[0083] Optionally, the second device further manages the wireless energy saving intention instance according to the lifecycle management stage indicated by the first indication information to obtain an intention management result.

[0084] It can be seen that the method indicates at least one of the exploration phase or implementation phase that the wireless energy-saving intention instance can be used for by introducing the intention lifecycle management phase. In this way, the present application can avoid the immediate implementation of the intention instance after creation, which is beneficial for processing the intention instance in the exploration phase or implementation phase in combination with the network deployment situation and network status. Specifically, the present application can achieve at least one of the following beneficial effects: it is beneficial for obtaining the capability value of the intention instance through the exploration phase before the implementation of the intention instance, and then it is beneficial for selecting the target value expected by the intention, avoiding the problem that the expectations of the intention instance cannot be met due to multiple blind settings or the target value is set too low, resulting in the inability to obtain better network performance; or, the first indication information indicates that the intention instance is used for implementation phase and then implemented to avoid the problem that the created intention instance is directly implemented, resulting in the inability to perform the above-mentioned stages of intention negotiation.

[0085] In an optional embodiment, the second device receives the first indication information, including: the second device receives a first request, the first request includes intent information and first indication information, and the intent information includes the intent object and intent target of the wireless energy-saving intention instance. The intent object includes the coverage geographical area information of the network device or cell, and the intent target includes the energy consumption target and the rate target. Accordingly, the method also includes: the second device creates a wireless energy-saving intention instance based on the intent information, the wireless energy-saving intention instance includes the desired intent object and intent target, and also includes information on the lifecycle management stage indicated by the first indication information.

[0086] In one embodiment, the lifecycle management phase indicated by the first indication information is the exploration phase; the intent management results obtained by the wireless energy-saving intent instance during the lifecycle management phase include the intent exploration results obtained by the wireless energy-saving intent instance during the exploration phase; wherein each intent exploration result includes the capability value of the intent target of the wireless energy-saving intent instance. This embodiment allows exploration of the capability value of the intent target before implementing the wireless energy-saving intent instance, thereby preventing the intent target from being unattainable due to blindly setting the target value, or preventing the target value from being set too low, resulting in the inability to achieve optimal energy consumption and performance results for the network.

[0087] Optionally, the second device sending the intention exploration result includes: the second device sending an intention exploration report, wherein the intention exploration report includes at least one intention exploration result. In addition, the intention exploration report also includes an identifier of the wireless energy-saving intention instance. Each intention exploration result includes the name of the intention target (such as energy consumption target and rate target), and the capability value of the corresponding intention target (such as the current capability value and the capability value within the predicted time or predicted duration). Accordingly, the second device performs an exploration and evaluation of the intention target on the wireless energy-saving intention instance to obtain an intention exploration result or an intention exploration report.

[0088] In an optional implementation, after the second device sends the intent exploration report or intent exploration result to the first device, it also receives the target value of the intent target from the first device, where the target value of the intent target is determined by the first device based on the capability value of the intent target. It can be seen that in this implementation, the target value is determined by the first device based on the capability value of the currently explored intent target, thereby avoiding the intent target being unattainable due to blindly setting the target value, or the target value being set too low to fully stimulate the network capability.

[0089] In one optional implementation, if the lifecycle management phase indicated by the first indication information is the implementation phase, the intent management result sent by the second device is the intent execution result obtained by the wireless power-saving intent instance during the implementation phase. Alternatively, the second device implements the wireless power-saving intent instance to obtain the intent execution result. This embodiment, by indicating the implementation of the wireless power-saving intent instance through the first indication information, avoids immediate implementation of the wireless power-saving intent instance after creation.

[0090] In another optional implementation, the lifecycle management stage indicated by the first indication information is the exploration stage described above. After the second device receives the first indication information and sends the corresponding intent management result, it also receives the second indication information. The second indication information is used to indicate that the lifecycle management stage of the wireless energy-saving intention instance is modified to the implementation stage. Optionally, the second device modifies the lifecycle management stage of the wireless energy-saving intention instance to the implementation stage, and implements the wireless energy-saving intention instance to obtain the intention execution result. The second device sends the intention execution result. It can be seen that this implementation is conducive to intention negotiation based on the exploration stage described above, avoiding the problem of information inconsistency caused by repeated creation of wireless energy-saving intention instances with the same intent information, so that the wireless energy-saving intention instance can be successfully implemented.

[0091] In an optional embodiment, in addition to receiving the first indication information indicating that the lifecycle management stage is or includes the exploration stage, the second device also receives the evaluation constraint information described above. For example, if the simulation technology indicated by the evaluation constraint information is NDT, then the intention exploration result is obtained by simulation evaluation using the NDT technology. In addition, if the evaluation constraint information indicates that the simulation is to be performed online, the intention exploration result is obtained by online simulation evaluation; if the evaluation constraint information indicates that the simulation is to be performed offline, the intention exploration result is obtained by offline simulation evaluation.

[0092] Optionally, the evaluation constraint information may be included in the first request carrying the first indication information.

[0093] In a seventh aspect, embodiments of the present application further provide a communication device. The communication device is a first device, or a device of the first device, or a device capable of being used in conjunction with the first device. In one possible implementation, the communication device includes a functional module, which is implemented as a hardware circuit, or software, or a combination of a hardware circuit and software.

[0094] In one possible implementation, the communication device includes one or more functional units, such as a communication unit, wherein the communication unit is used to send a first indication message, and the first indication message is used to indicate the lifecycle management stage of the intent instance; wherein the lifecycle management stage includes at least one of the feasibility assessment stage, resource reservation stage, exploration stage or implementation stage of the intent instance; accordingly, the communication unit is also used to receive the intent management result obtained by the intent instance in the lifecycle management stage. Optionally, the communication device may further include a processing unit for determining the first indication message. Optionally, the optional implementation methods that may be performed by the communication device may refer to the above-mentioned first aspect and one or more possible implementation methods therein, which will not be described in detail here.

[0095] In another possible implementation, the communication device includes one or more functional units, such as a communication unit, wherein the communication unit is used to send first indication information, and the first indication information is used to indicate the lifecycle management stage of the wireless service intention instance; wherein the lifecycle management stage includes at least one of the feasibility assessment stage, resource reservation stage, or implementation stage of the wireless service intention instance; accordingly, the communication unit is also used to receive the intent management result obtained by the wireless service intention instance in the lifecycle management stage. Optionally, the communication device may further include a processing unit for determining the first indication information. Optionally, the optional implementation methods that may be performed by the communication device can be found in the third aspect above and one or more possible implementation methods therein, which will not be described in detail here.

[0096] In another possible implementation, the communication device includes one or more functional units, such as a communication unit, wherein the communication unit is used to send first indication information, and the first indication information is used to indicate the lifecycle management stage of the wireless energy-saving intention instance; wherein the lifecycle management stage includes at least one of the exploration stage or the implementation stage of the wireless energy-saving intention instance; accordingly, the communication unit is also used to receive the intent management result obtained by the wireless energy-saving intention instance in the lifecycle management stage. Optionally, the communication device may further include a processing unit for determining the first indication information. Optionally, the optional implementation methods that may be performed by the communication device can be referred to the fifth aspect and one or more possible implementation methods thereof, which will not be described in detail here.

[0097] In an eighth aspect, embodiments of the present application further provide a communication device. The communication device is a second device, or a device of the second device, or a device capable of being used in conjunction with the second device. In one possible implementation, the communication device includes a functional module, which is implemented as a hardware circuit, or software, or a combination of a hardware circuit and software.

[0098] In one possible implementation, the communication device includes one or more functional units, such as a communication unit, wherein the communication unit is used to receive first indication information, and the first indication information is used to indicate the lifecycle management stage of the intent instance; wherein the lifecycle management stage includes at least one of the feasibility assessment stage, resource reservation stage, exploration stage or implementation stage of the intent instance; the communication unit is also used to send the intent management result obtained by the intent instance in the lifecycle management stage. Optionally, the communication device may further include a processing unit, which is used to manage the intent instance according to the lifecycle management stage indicated by the first indication information and obtain the intent management result. Optionally, the optional implementation method that the communication device may also perform can be found in the above-mentioned second aspect and one or more possible implementation methods therein, which will not be described in detail here.

[0099] In another possible implementation, the communication device includes one or more functional units, such as a communication unit, wherein the communication unit is used to receive first indication information, and the first indication information is used to indicate the lifecycle management stage of the wireless service intention instance; wherein the lifecycle management stage includes at least one of the feasibility assessment stage, resource reservation stage or implementation stage of the wireless service intention instance; the communication unit is also used to send the intention management result obtained by the wireless service intention instance in the lifecycle management stage. Optionally, the communication device may further include a processing unit, which is used to manage the wireless service intention instance according to the lifecycle management stage indicated by the first indication information and obtain the intention management result. Optionally, the optional implementation method that the communication device may also perform can refer to the fourth aspect above and one or more possible implementation methods therein, which will not be described in detail here.

[0100] In one possible implementation, the communication device includes one or more functional units, such as a communication unit, wherein the communication unit is configured to receive first indication information, the first indication information being configured to indicate a lifecycle management phase of a wireless energy-saving intention instance; wherein the lifecycle management phase includes at least one of an exploration phase or an implementation phase of the wireless energy-saving intention instance; and the communication unit is further configured to send an intent management result obtained by the wireless energy-saving intention instance during the lifecycle management phase. Optionally, the communication device may further include a processing unit configured to manage the wireless energy-saving intention instance according to the lifecycle management phase indicated by the first indication information and obtain an intent management result. Optionally, the optional implementations that may be performed by the communication device may refer to the sixth aspect and one or more possible implementations thereof, which will not be described in detail here.

[0101] For the seventh and eighth aspects, as an example, the processing unit can be the processing unit or can be embodied as a processing circuit or a logic circuit; the transceiver unit can be an input / output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or chip system.

[0102] During implementation, the processor can be used to perform, for example, but not limited to, baseband-related processing, and the transceiver or communication interface can be used to perform, for example, but not limited to, radio frequency transceiver. The above-mentioned devices can be provided on separate chips, or at least partially or entirely on the same chip. For example, the processor can be further divided into an analog baseband processor and a digital baseband processor. The analog baseband processor can be integrated with the transceiver (or communication interface) on the same chip, while the digital baseband processor can be provided on a separate chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip. For example, a digital baseband processor can be integrated with multiple application processors (such as, but not limited to, a graphics processor, a multimedia processor, etc.) on the same chip. Such a chip can be called a system on a chip (SoC). Whether each device is provided independently on different chips or integrated on one or more chips often depends on the needs of the product design. The embodiments of the present application do not limit the implementation form of the above-mentioned devices.

[0103] Ninth aspect, the embodiment of the present application also provides a processor for executing the method described in any one of the first aspect, the third aspect or the fifth aspect or any one of the possible implementation methods of any one of the aspects, or for executing the method described in any one of the second aspect, the fourth aspect or the sixth aspect or any one of the possible implementation methods of any one of the aspects. In the process of executing these methods, the process of sending the above-mentioned signal and receiving the above-mentioned signal in the above-mentioned method can be understood as the process of outputting the above-mentioned signal by the processor, and the process of the above-mentioned signal input by the processor. When outputting the above-mentioned signal, the processor outputs the above-mentioned signal to the transceiver so that it is transmitted by the transceiver (or communication interface). After being output by the processor, the above-mentioned signal may also need to undergo other processing before arriving at the transceiver (or communication interface). Similarly, when the processor receives the above-mentioned signal input, the transceiver (or communication interface) receives the above-mentioned signal and inputs it into the processor. Furthermore, after the transceiver (or communication interface) receives the above-mentioned signal, the above-mentioned signal may need to undergo other processing before being input into the processor.

[0104] For the sending and receiving operations involved in the processor, unless otherwise specified, or unless they conflict with their actual functions or internal logic in the relevant descriptions, they can be more generally understood as processor output, reception, input and other operations, rather than sending and receiving operations directly performed by the RF circuit and antenna.

[0105] During implementation, the processor may be a processor specifically configured to execute these methods, or may be a processor that executes computer instructions in a memory to execute these methods, such as a general-purpose processor. The memory may be a non-transitory memory, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or disposed on separate chips. The embodiments of the present application do not limit the type of memory or the configuration of the memory and the processor.

[0106] In a tenth aspect, an embodiment of the present application further provides a communication device, comprising: a processor configured to invoke a computer program stored in a memory to cause the communication device to implement the method described in any one of aspects 1 to 6 or any possible implementation of any one of aspects 1 to 6. Optionally, the communication device further comprises a memory, and the processor and the memory are coupled. Optionally, the communication device may be a chip or a chip system.

[0107] In the eleventh aspect, the present application also provides a chip, which includes a processor, and the processor is used to determine first indication information, wherein the first indication information is used to indicate the lifecycle management stage of the intent instance; wherein the lifecycle management stage includes at least one of the feasibility assessment stage, resource reservation stage, exploration stage or implementation stage of the intent instance. Optionally, the chip also includes a transceiver interface, which is coupled to the processor, and the transceiver interface is used to send the first indication information. Optionally, the chip is also used by the processor or by the processor and the transceiver interface to implement the method described in any one of the first, third or fifth aspects or any possible implementation method of any one of the aspects, which will not be described in detail here.

[0108] In the twelfth aspect, the present application also provides a chip, which includes a processor, and the processor is used to manage the intent instance according to the lifecycle management stage indicated by the first indication information, and obtain the intent management results of the intent instance in each lifecycle management stage. Optionally, the chip also includes a transceiver interface, which is used to receive the first indication information and send the obtained intent management results. Optionally, the chip is also used by the processor or by the processor and the transceiver interface to implement the method described in any one of the second, fourth or sixth aspects or any possible implementation methods of any one of the aspects, which will not be described in detail here.

[0109] In the thirteenth aspect, the present application also provides a communication system, which includes at least one first device that executes the method described in the first aspect or any optional embodiment of the first aspect and at least one second device that executes the method described in the second aspect or any possible embodiment of the second aspect; or, the system includes at least one first device that executes the method described in the third aspect or any optional embodiment of the third aspect and at least one second device that executes the method described in the fourth aspect or any possible embodiment of the fourth aspect; or, the system includes at least one first device that executes the method described in the fifth aspect or any optional embodiment of the fifth aspect and at least one second device that executes the method described in the sixth aspect or any possible embodiment of the sixth aspect. In another possible design, the system may also include other devices that interact with the first device and / or the second device.

[0110] In the fourteenth aspect, the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is run, the method described in any one of the above-mentioned aspects from the first to the sixth aspect or any possible implementation method of any one of the aspects is executed.

[0111] In the fifteenth aspect, the present application also provides a computer program product comprising instructions, the computer program product comprising: computer program code, when the computer program code is run, the method described in any one of the above-mentioned aspects from the first to the sixth aspect or any possible implementation method of any one of the aspects is executed.

[0112] In the sixteenth aspect, the present application provides a chip system, which includes a processor and an interface, wherein the interface is used to obtain a program or instruction, and the processor is used to call the program or instruction to implement the method described in any one of the first to sixth aspects or any possible implementation method of any one of the aspects. In one possible design, the chip system also includes a memory, which is used to store program instructions and data necessary for the terminal. The chip system can be composed of a chip, or it can include a chip and other discrete devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0113] Figure 1 is a schematic diagram of an intent management logic framework;

[0114] FIG2 is a schematic diagram of the structure of an autonomous network system used in this application;

[0115] FIG3 is a flow chart of an intention processing method;

[0116] FIG4 is a flow chart of an intent processing method provided in an embodiment of the present application;

[0117] FIG5 is a flow chart of another method for processing intent provided in an embodiment of the present application;

[0118] FIG6 is a flow chart of another method for processing intent provided in an embodiment of the present application;

[0119] FIG7 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0120] FIG8 is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0121] An intent-driven management system (IDM) is a system that uses intent for closed-loop automation management and control. The IDM can translate intents into policies and management tasks, which can then be executed by the IDM to achieve closed-loop automation. In an IDM approach, the IDM uses various closed-loop automation mechanisms to fulfill intents. The IDM is also called an intent handling function. Please refer to Figure 1, which illustrates a logical framework for intent management. As shown in Figure 1, the intent management logical framework primarily includes an intent monitoring module (or intent monitoring system), an intent execution module (or intent execution system), and the logical interface between the intent monitoring and intent execution modules. The intent monitoring system is used to determine the intent information and intent target of an intent instance and monitor the execution of the intent instance. The intent execution system is used to translate, implement, and evaluate received intent instances. Intent information includes the intent object and intent target of an intent instance.

[0122] Among them, intent is a set of expectations, including requirements, goals, conditions and constraints for mobile communication networks, but does not specify how to achieve these expectations. Intent is equal to intent object (or management object of intent), for example, capacity intent (for example, the proportion of high load in area 1 is 10%), coverage intent (for example, the proportion of weak coverage in area 1 is 20%), rate intent (for example, the proportion of low-speed users in area 1 is 5%). Management objects are used to describe information about a managed object or management task in the intent-driven management system. The information model of the management object can be used as an interaction parameter in the management interface. Creating a management object means creating management information in the management system, enabling the management system to manage the managed object or perform management tasks based on the management information. Intent can be considered as a management object in the management system. Intent instance is used to describe the expected state of the managed object. Intent object is the information of the managed object; intent target is the performance indicator of the managed object.

[0123] For example, the intent instance is a wireless service intent instance, the intent object of the wireless service intent instance includes the coverage geographic area information of the network device or cell, and the intent target of the wireless service intent instance includes the latency target and / or the rate target. For another example, the intent instance is a wireless energy conservation intent instance, the intent object of the wireless energy conservation intent instance includes the coverage geographic area information of the network device or cell, and the intent target of the wireless energy conservation intent instance includes the energy consumption target and / or the rate target.

[0124] Optionally, the system architecture or scenario in which the intent processing method provided in the present application is applied is an autonomous network system. Please refer to Figure 2. Figure 2 is a structural diagram of an autonomous network system applied in the present application. As shown in Figure 2, the autonomous network system includes the following three situations: (1) a single-domain autonomous network, wherein the single-domain autonomous network includes a network element and a domain management functional unit; (2) a cross-domain autonomous network, wherein the cross-domain autonomous network includes a network element, a domain management functional unit and a cross-domain management functional unit; (3) a business autonomous network, wherein the business autonomous network includes a network element, a domain management functional unit, a cross-domain management functional unit and a business operation unit.

[0125] A business operations unit, also known as a communication service management function unit, provides functions and management services such as billing, settlement, accounting, customer service, sales, network monitoring, communication service lifecycle management, and business intent translation. This unit encompasses a carrier's operational system or a vertical operational technology system.

[0126] The cross-domain management function unit may also be referred to as a network management function unit (network management function, NMF). The cross-domain management function unit provides one or more of the following functions or management services: network lifecycle management, network deployment, network fault management, network performance management, network configuration management, network assurance, network optimization functions, translation of the network intent of the communication service provider (intent from communication service provider, intent-CSP), translation of the network intent of the communication service user (intent from communication service consumer, intent-CSC), etc. The network here may include one or more network elements, subnetworks or network slices. For example, the cross-domain management function unit may be a network slice management function (NSMF) unit, a management data analytical function (MDAF) unit, a cross-domain self-organization network function (SON-function) unit, or a cross-domain intent management function unit.

[0127] In some deployment scenarios, the cross-domain management functional unit may also provide one or more of the following management functions or management services: sub-network lifecycle management, sub-network deployment, sub-network fault management, sub-network performance management, sub-network configuration management, sub-network assurance, sub-network optimization, sub-network intent translation for communication service providers, sub-network intent translation for communication service users, etc. A sub-network may be composed of multiple small sub-networks or multiple network slice sub-networks.

[0128] In terms of implementation, the cross-domain management functional unit can be implemented in the form of a management platform + multiple management applications, wherein the management application implements the management function of one or more networks or sub-networks above.

[0129] The domain management function unit can also be called a subnetwork management function (NMF) or a network element / function management function unit. The domain management function unit provides one or more of the following functions or management services: lifecycle management of subnetworks or network elements, deployment of subnetworks or network elements, fault management of subnetworks or network elements, performance management of subnetworks or network elements, assurance of subnetworks or network elements, optimization management of subnetworks or network elements, and intent translation of subnetworks or network elements. The subnetwork here includes one or more network elements. Alternatively, the subnetwork here may also include one or more subnetworks, that is, one or more subnetworks form a subnetwork with a larger coverage area. Alternatively, the subnetwork here may also include one or more network slice subnetworks.

[0130] Subnetworks can be described in one of the following ways: (1) a network in a certain technical domain, such as a wireless access network, core network, or transmission network; (2) a network of a certain standard, such as a global system for mobile communications (GSM) network, a long-term evolution (LTE) network, or a fifth-generation mobile communication technology (5G) network; (3) a network provided by a certain equipment vendor, such as a network provided by equipment vendor X; (4) a network in a certain geographical area, such as a network in factory A or a network in prefecture-level city B. In terms of implementation, the domain management functional unit can be implemented as a management platform + multiple management applications, where the management application implements the management function of one or more subnetworks or network elements mentioned above.

[0131] A network element is an entity that provides network services, including core network elements, access network elements, etc. For example, core network elements may include but are not limited to access and mobility management function (AMF) entity, session management function (SMF) entity, policy control function (PCF) entity, network data analysis function (NWDAF) entity, network repository function (NRF), gateway, etc. Access network elements may include but are not limited to: various types of base stations (such as next generation node B (gNB), evolved Node B (eNB), centralized control unit (CUCP), centralized unit (CU), distributed unit (DU), centralized user plane unit (CUUP), etc.

[0132] Under the service-oriented management architecture, focusing on the management service provider (Management Service Producer, MnS Producer) and the management service consumer (Management Service Consumer, MnS Consumer), it should be understood that: when the management service is the management service provided by the above-mentioned business operation unit, the business operation unit is the management service provider, and other business operator units can be management service consumers; when the management service is the management service provided by the above-mentioned cross-domain management function unit, the cross-domain management function unit is the management service provider, and the business operation unit is the management service consumer; when the management service is the management service provided by the above-mentioned domain management function unit, the domain management function unit is the management service provider, and the cross-domain management function unit or the business operation unit is the management service consumer; when the management service is the management service provided by the above-mentioned network element, the network element is the management service provider, and the domain management function unit or the cross-domain management function unit or the business operation unit is the management service consumer.

[0133] Optionally, the intent management system is applied to the aforementioned autonomous network system, including but not limited to the following deployment scenarios: Deployment Scenario #1: For intent management capabilities in a single-domain autonomous network, the intent execution module is deployed in the domain management functional unit, and the intent monitoring module is deployed in the cross-domain management functional unit; Deployment Scenario #2: For intent management capabilities in a cross-domain autonomous network, the intent execution module is deployed in the cross-domain management functional unit, and the intent monitoring module is deployed in the business operation unit; Deployment Scenario #3: For intent management capabilities in a business autonomous network, the intent execution module is deployed in the business operation unit, and the intent monitoring module is deployed in a third-party system outside the autonomous network, such as an enterprise system. In a service-based management architecture, the intent monitoring module is the management service consumer, the intent execution module is the management service provider, the logical interface is the intent service interface, and the logical interface is the intent management service.

[0134] Please refer to Figure 3, which is a flowchart of an intent processing method. As shown in Figure 3, the intent processing method includes but is not limited to the following steps:

[0135] S101. The intention execution system sends management capability information to the intention monitoring system, and correspondingly, the intention monitoring system receives the management capability information.

[0136] Among them, the management capability information includes the intent objects supported by the intent execution system (such as wireless subnetworks and wireless slicing services, etc.) and the target names of the supported intent targets (such as weak coverage ratio, high load ratio, uplink rate, downlink rate, uplink or downlink average rate and energy consumption target, etc.).

[0137] S102. The intent monitoring system sends an intent instance creation request to the intent execution system based on the management capability information of the intent execution system. Correspondingly, the intent execution system receives the intent instance creation request.

[0138] The intent instance creation request includes intent information, which includes the desired intent object and the target value of the intent target.

[0139] S103. The intent execution system creates an intent instance according to the intent instance creation request, and performs intent translation on the intent instance to obtain network configuration parameters.

[0140] S104. The intention execution system sends the network configuration parameters to the corresponding network element.

[0141] The network element is configured according to the network configuration parameters, thereby executing the intent instance. Optionally, the intent processing method may further include steps S105 and S106.

[0142] S105. The intention execution system obtains network performance indicators, and evaluates the network performance indicators to obtain intention execution information.

[0143] S106. The intention execution system sends intention execution information to the intention monitoring system.

[0144] In this application, the intention execution information may also be referred to as the intention execution result.

[0145] It can be seen that in the intent processing method described in Figure 3, the intent monitoring system can only obtain the target name of the intent object and intent target supported by the intent execution system. The target value of the intent target is carried by the intent monitoring system through the intent instance creation request. However, the capability of the intent execution system is determined by the network deployment and network status, and changes in real time. Therefore, in this case, how to perform intent processing is a problem to be solved.

[0146] In the present application, the intention execution system receives first indication information from the intention monitoring system, and the first indication information is used to indicate the lifecycle management stage of the intent instance, wherein the lifecycle management stage includes at least one of the feasibility assessment stage, resource reservation stage, exploration stage, or implementation stage of the intent instance; furthermore, the intention execution system sends the intention management result obtained by the intent instance in the lifecycle management stage to the intent monitoring system. For example, the sent intention management result includes at least one of the following: the feasibility assessment result obtained by the intent instance in the feasibility assessment stage, the resource reservation result obtained in the resource reservation stage, the intention exploration result obtained in the exploration stage, or the intention execution result obtained in the implementation stage.

[0147] It can be seen that the present application, by introducing the intent lifecycle management stage, refers to at least one of the feasibility assessment stage, resource reservation stage, exploration stage or implementation stage that the schematic instance can be used for. In this way, the present application can avoid immediate implementation after the intent instance is created, which is conducive to the intent execution system to perform corresponding processing on the intent instance in combination with the network deployment situation and network status after the first indication information indicates the corresponding lifecycle management stage. In other words, the intent processing method (or intention management method) provided by the present application supports intent negotiation capabilities, such as feasibility assessment, resource reservation, capability value exploration or implementation, etc., through the intent lifecycle management stage, and supports lifecycle management at different stages through the first indication information to support intent negotiation between the intent monitoring system and the intent execution system.

[0148] Please refer to Figure 4, which is a flow chart of an intent processing method provided by an embodiment of the present application. The intent processing method shown in Figure 4 is described in terms of the interaction between a first device having an intent monitoring system and a second device having an intent execution system. As shown in Figure 4, the intent processing method includes but is not limited to the following steps:

[0149] S201. The first device sends a first indication message, and accordingly, the second device receives the first indication message, where the first indication message is used to indicate the lifecycle management phase of the schematic instance;

[0150] The lifecycle management stage includes at least one of the feasibility assessment stage, resource reservation stage, exploration stage or implementation stage of the intent instance.

[0151] Optionally, step S201 is: the first device sends a first request, and correspondingly, the second device receives the first request, the first request includes intent information and first indication information, the intent information includes the intent object and intent target of the intent instance; the second device creates an intent instance according to the intent information. The intent instance includes the desired intent object and the lifecycle management stage indicated by the first indication information. Optionally, the second device also sends a first response to the first device, and the first response includes an identifier of the intent instance. It can be seen that this embodiment is conducive to creating an intent instance based on the lifecycle management stage indicated by the first indication information, avoiding the problem that the same intent information needs to maintain multiple intent instances, such as the value of the intent object or the intent target, is inconsistent. For example, the intent object in the intent information is the coverage geographical area information, and the intent target is the uplink delay and uplink rate. Then, in the multiple intent instances maintained by the same intent information, the values ​​of the coverage geographical area may be inconsistent.

[0152] The identifier of the intent instance may be the distinguished name (DN) of the managed object instance. Optionally, the identifier of the intent instance may be carried in the first request, or may be allocated to the managed object instance by the second device when creating the intent instance.

[0153] S202. The second device manages the intent instance according to the lifecycle management stage indicated by the first indication information, and obtains the intent management result of the intent instance in the lifecycle management stage.

[0154] The intent management result is also called the intent report. The intent report is the intent result information fed back to the user by the intent-driven management system. For example, this application may include at least one item such as the intent execution result, the intent feasibility assessment report, the intent exploration report or the resource reservation report.

[0155] S203. The second device sends the intent management result obtained by the intent instance in the lifecycle management stage, and correspondingly, the first device receives the intent management result of the intent instance.

[0156] In an optional embodiment, the lifecycle management stage indicated by the first indication information is the feasibility assessment stage, and the second device sends the feasibility assessment result obtained by the intent instance during the feasibility assessment stage to the first device. Optionally, step S202 may specifically include: the second device performs a feasibility assessment on the intent instance to obtain a feasibility assessment result.

[0157] Optionally, the second device sends the feasibility assessment result to the first device in the form of a feasibility assessment report. Optionally, the feasibility assessment report includes not only the feasibility assessment result (such as whether the implementation of the intent instance is feasible or not), but also the identifier of the intent instance and the reason for infeasibility (if it is infeasible, it also includes the reason for infeasibility, such as intent conflict, insufficient resources, etc.).

[0158] Optionally, the second device also receives evaluation constraint information from the first device, wherein the evaluation constraint information includes indication information for indicating the simulation technology, and / or indication information for indicating whether to perform simulation online or offline. In this way, the second device determines the specific simulation technology based on the evaluation constraint information. For example, if the simulation technology indicated by the evaluation constraint information is network digital twin (NDT), then the second device uses NDT technology to perform simulation evaluation and obtain a feasibility evaluation result. In addition, if the evaluation constraint information indicates that the simulation is to be performed online, the simulation evaluation is performed online; if the evaluation constraint information indicates that the simulation is to be performed offline, the simulation evaluation is performed offline. Optionally, the first request may include the evaluation constraint information.

[0159] Optionally, the intent instance created by the second device includes intent information of the intent instance, first indication information, and evaluation constraint information.

[0160] In another optional implementation, the lifecycle management stage indicated by the first indication information is the resource reservation stage, and in step S203, the second device sends the resource reservation result obtained by the intent instance in the resource reservation stage to the first device. Optionally, step S202 may be specifically as follows: the second device reserves corresponding resources for the intent instance and obtains the resource reservation result. Optionally, the second device sends the resource reservation result to the first device in the form of a resource reservation report. Optionally, the corresponding resources reserved by the second device for the intent instance are wireless PRB resources, the number of RRC connections or at least one of DRB resources. The resource reservation result may also be referred to as the resource reservation status (such as reserved or reservation failed), and the resource reservation report may also include the network devices and / or cells associated with the reserved resources, and the number or proportion of reserved resources. The ratio is the ratio of the number of reserved resources to the total number of resources of the network devices and / or cells.

[0161] In an optional implementation, the lifecycle management stage indicated by the first indication information includes the feasibility assessment stage and the resource reservation stage described above. Then, the second device not only sends the feasibility assessment result obtained by the intent instance in the feasibility assessment stage to the second device, but also sends the resource reservation result obtained by the intent instance in the resource reservation stage to the second device. Accordingly, step S202 is specifically as follows: the second device performs a feasibility assessment on the intent instance to obtain a feasibility assessment result, and the second device reserves corresponding resources for the intent instance to obtain a resource reservation result. Optionally, in step S203, the feasibility assessment result and the resource reservation result can be sent to the first device separately, or they can be sent to the first device together, which is not limited in this application.

[0162] In another optional implementation, the lifecycle management stage indicated by the first indication information in step S201 is the feasibility assessment stage. After step S201, the first device may also send a second request to the second device, and the second request includes indication information of the resource reservation stage, or the second request is used to request to modify the lifecycle management stage indicated by the first indication information to the resource reservation stage. For example, the value of the first indication information before the modification is the value of the feasibility assessment stage, and after the modification, it is the value of the resource reservation stage. In this way, the second device can determine and send the feasibility assessment result through steps S202 and S203, and can also determine and send the resource reservation result through steps S202 and S203. Optionally, the feasibility assessment result and the resource reservation result can be sent to the first device separately, or they can be sent to the first device together. Optionally, the second request is called an intent instance modification request to modify the value of the lifecycle stage of the intent instance.

[0163] In an optional implementation, the lifecycle management stage indicated by the first indication information is the exploration stage; step S202 is specifically: the second device explores the intent instance and obtains the intent exploration result. Correspondingly, step S203 is specifically: the second device sends the intent exploration result to the first device. Each intent exploration result includes the capability value of the intent target of the intent instance. It can be seen that this implementation method obtains the capability value of the intent target before the intent instance is implemented, which is conducive to avoiding the intention target from being unable to be achieved due to blindly setting the target value, or the setting of the target value is too low, resulting in the inability to obtain better energy consumption and performance effects of the network.

[0164] Optionally, the second device determines the intention exploration result, including: the second device determines an intention exploration report, wherein the intention exploration report includes at least one intention exploration result. In addition, the intention exploration report also includes an identifier of the intent instance. Each intention exploration result includes the name of the intent target (such as energy consumption target and rate target), and the capability value of the corresponding intent target (such as the current capability value and the capability value within the predicted time or predicted duration).

[0165] Optionally, the method also includes: after the first device receives the intention exploration result, it determines the target value of the intention target (such as the target value of energy consumption and the target value of downlink rate) according to the intention exploration result obtained in the exploration phase of the intention instance; and sends the target value of the intention target to the second device. It can be seen that this implementation method determines the target value based on the capability value of the intention target currently explored, thereby avoiding the intention target being unable to be achieved due to blindly setting the target value, or the target value set is too low to fully stimulate the network capability. Among them, the intention target in the intention instance previously created by the second device has no set value, only the name of the intention target, or the capability value of the intention target in the created intention instance is 0, until the first device determines and sends the target value of the intention target to the second device according to the intention exploration result, the capability value of the intention target in the intention instance is the target value.

[0166] Optionally, if the intent exploration report includes at least two intent exploration results, the first device may select a capability value included in one of the intent exploration results as the target value of the intent target.

[0167] In an optional embodiment, the lifecycle management stage indicated by the first indication information of the first device is the exploration stage, and the first device also sends the evaluation constraint information described above. For example, if the simulation technology indicated by the evaluation constraint information is NDT, then the intention exploration result is obtained by simulation evaluation using the NDT technology. In addition, if the evaluation constraint information indicates that the simulation is to be performed online, the intention exploration result is obtained by using online simulation evaluation; if the evaluation constraint information indicates that the simulation is to be performed offline, the intention exploration result is obtained by using offline simulation evaluation.

[0168] In an optional implementation, the lifecycle management stage indicated by the first indication information is the implementation stage, and step S202 is specifically: the second device implements the intention instance and obtains the intention execution result. Correspondingly, step S203 is specifically: the second device sends the intention execution result to the first device. Optionally, the second device sends the intention execution result to the first device in the form of an intention execution report. The intention execution result includes whether the intention target of the intention instance is met, such as whether each intention target is met. Optionally, in addition to the intention execution result, the intention execution report may also include the current measurement value of the intention target.

[0169] Optionally, the second device implements the intention instance and obtains the intention execution result, including: the second device translates the intention of the intention instance to obtain network configuration parameters; the second device configures and activates the network configuration parameters, and obtains network performance indicators after the implementation of the intention instance; the second device generates an intention execution report based on the network performance indicators, and the intention execution report includes whether the intention target of the intention instance is met and the current measurement value of the intention target.

[0170] It can be seen that in this implementation, the first device instructs the implementation of the intent instance through the first indication information, avoiding the immediate implementation of the intent instance after it is created.

[0171] In another optional implementation, the lifecycle management stage indicated by the first indication information is at least one of the feasibility assessment stage, resource reservation stage or exploration stage mentioned above. After sending the first indication information and receiving the corresponding intent management result, the first device also sends the second indication information. The second indication information is used to indicate that the lifecycle management stage of the modified intent instance is the implementation stage; further, the method also includes: the second device modifies the lifecycle management stage of the intent instance to the implementation stage. Correspondingly, step S202 also includes: the second device implements the intent instance and obtains the intent execution result. Step S203 also includes: the second device sends the intent execution result to the first device. It can be seen that this implementation method is conducive to intention negotiation based on the various lifecycle management stages mentioned above, avoiding the problem of information inconsistency caused by repeatedly creating intent instances with the same intent information, and enabling the successful implementation of the intent instance.

[0172] As described above, the lifecycle stage indicated by the first indication information in step S201 includes at least one of the feasibility assessment stage, resource reservation stage, exploration results, or implementation stage described above. In step S202, the second device manages the intent instance according to the corresponding lifecycle management stage to obtain the corresponding intent management stage; then, in step S203, the second device sends the corresponding intent management stage. As described above, each intent management result can be sent separately or in combination. In addition, the first device can also modify the lifecycle management stage of the intent instance through a request message.

[0173] It can be seen that the intent processing method described in Figure 4, by introducing the intent lifecycle management stage, refers to at least one of the feasibility assessment stage, resource reservation stage, exploration stage or implementation stage in which the schematic instance can be used. In this way, the present application can achieve at least one of the following beneficial effects: it can perform a feasibility assessment on the intent instance before the intent is implemented, and implement it when the expectations of the intent instance are met; or reserve resources before the intent instance is implemented to ensure that there are sufficient resources to meet the expectations of the intent instance during the intent implementation process; or it is beneficial to obtain the capability value of the intent instance through the exploration stage before the intent instance is implemented, and then it is beneficial to select the target value expected by the intent, avoiding the problem of multiple blind settings resulting in the failure to meet the expectations of the intent instance or setting the target value too low, resulting in the inability to obtain better network performance; or, the first device indicates that the schematic instance is used for implementation and then implements it to avoid the problem that the created intent instance is directly implemented and the above-mentioned stages of intention negotiation cannot be carried out.

[0174] Please refer to Figure 5, which is a flow chart of another intent processing method provided by an embodiment of the present application. The intent processing method described in Figure 5 takes the wireless service intent instance as an example to illustrate the feasibility assessment stage, the resource reservation stage and the implementation (also called fulfillment) stage, the three lifecycle management stages. In addition, in the intent processing method, the intent monitoring system or the intent monitoring module is illustrated by the cross-domain management functional unit in Figure 2, and the intent execution system or the intent execution module is illustrated by the domain management functional unit in Figure 2 as an example. In addition, the first request is a wireless service intent instance creation request, the first indication information is the intent lifecycle indication information, and the second request is an example of a wireless service intent instance modification request. As shown in Figure 5, the intent processing method includes but is not limited to the following steps:

[0175] S301. The cross-domain management function unit sends a radio service intent instance creation request to the domain management function unit. Correspondingly, the domain management function unit receives the radio service intent instance creation request.

[0176] The wireless service intent instance creation request carries the intent information of the wireless service intent instance (also called wireless service expectation information) and the intent lifecycle indication information. The intent information includes the information of the expected intent object (for example, object type: wireless service (radio service), object name: coverage geographical area information), and the information of the expected intent target (for example, the intent target includes the delay target and the rate target. Taking the above behavior as an example, the information of the expected intent target is: uplink delay target: <10ms; uplink rate target: >500Mbps). The intent lifecycle indication information is a feasibility check. That is, the value of the intent lifecycle indication information (also called intent execution purpose (intent execution purpose)) is a feasibility check (intent execution purpose = feasibility check), indicating that the execution system (that is, the domain management function unit) performs a feasibility assessment on the wireless service intent instance. The domain management function unit can be a feasibility assessment of the intent information of the wireless service intent instance.

[0177] Optionally, the radio service intent instance creation request is also called a radio service intent creation request (request to create radio service intent), which carries intent execution purpose=feasibility check.

[0178] Optionally, the wireless service intent instance creation request also carries simulation constraint information, which includes at least one of the following: online or offline indication information, indicating whether to simulate and evaluate the wireless service intent instance online or offline; or indication information indicating possible simulation techniques (also known as simulation technologies). For example, possible simulation techniques include NDT. Optionally, as shown in Figure 5, the NDT is integrated as a simulation module within the domain management functional unit.

[0179] S302. The domain management function unit creates a wireless service intent instance (ie, a wireless service intent management object instance) according to the wireless service intent instance creation request.

[0180] The wireless service intention instance includes the intention information of the wireless service intention instance, the intention lifecycle indication information and the evaluation constraint information.

[0181] S303. The domain management function unit sends wireless service intent instance creation response information to the cross-domain management function unit. Correspondingly, the cross-domain management function unit receives the wireless service intent instance creation response information.

[0182] The radio service intent instance creation response message is also referred to as a response for creating a radio service intent. The radio service intent instance creation response message carries an identifier of the radio service intent instance. The radio service intent instance identifier may be a distinguished name (DN) of a radio service intent management object instance. Optionally, the radio service intent instance identifier may be carried in the radio service intent instance creation request in step S301, or may be assigned by the domain management function unit when creating the radio service intent instance in step S302.

[0183] S304. The domain management function unit performs a feasibility assessment on the wireless service intent instance according to the value of the intent lifecycle indication information in the wireless service intent instance (ie, feasibility assessment), and generates an intent feasibility assessment report (ie, the feasibility assessment report described above).

[0184] Optionally, the domain management functional unit also determines the specific simulation method and means based on the simulation evaluation constraint information. For example, when the online or offline indication information indicates online, the simulation is performed online; when the simulation technology is NDT, the network digital twin is used for simulation evaluation. After the domain management functional unit completes the simulation evaluation, it generates an intention feasibility evaluation report. Optionally, the intention feasibility evaluation report includes the intention feasibility evaluation results (feasible or infeasible), and when it is infeasible, it also includes the reasons for infeasibility (for example, intention conflict, insufficient resources, etc.).

[0185] S305. The domain management functional unit sends an intention feasibility assessment report to the cross-domain management functional unit. The intention feasibility assessment report includes the intention instance identifier and the intention feasibility assessment result (and the reason for infeasibility if infeasible).

[0186] Optionally, an intent feasibility check report may be carried in the intent report and sent.

[0187] Optionally, when the cross-domain management function unit has a resource reservation requirement, and / or when the cross-domain management function unit receives an intention feasibility assessment report and learns that the wireless service intention instance is feasible, step S306 may also be executed.

[0188] S306. The cross-domain management function unit sends a wireless service intention instance modification request to the domain management function unit. Correspondingly, the domain management function unit receives the wireless service intention instance modification request, wherein the wireless service intention instance modification request carries the identifier of the wireless service intention instance and the intention life cycle indication information: resource reservation.

[0189] Optionally, the radio service intent instance modification request is also called a radio service intent modification request (request to modify radio service intent), which carries intent execution purpose=resource reservation.

[0190] S307. The domain management function unit modifies the value of the intent lifecycle indication information in the wireless service intent instance to resource reservation (feasibility check before modification); reserves corresponding resources for the wireless service intent instance, and generates a resource reservation report.

[0191] As shown in FIG5 , the domain management function unit reserves corresponding resources for the wireless service intention instance in combination with the resources of the network element (such as a base station), and generates a resource reservation report.

[0192] Optionally, the resources reserved for the wireless service intent instance are at least one of wireless PRB resources, RRC connection number or DRB resources. The resource reservation report includes the resource reservation status (such as reserved or reservation failed), the network device and / or cell associated with the reserved resources, and the number or proportion of reserved resources, wherein the proportion is the ratio of the number of reserved resources to the total number of resources of the network device and / or cell.

[0193] S308. The domain management function unit sends a resource reservation report to the inter-domain management function unit. Correspondingly, the inter-domain management function unit receives the resource reservation report.

[0194] Optionally, the intended lifecycle indication information in step S301 may also be a feasibility check and resource reservation. In this case, step S306 is not required, and steps S305 and S308 may be sent separately or in combination.

[0195] S309. The cross-domain management function unit sends a wireless service intent instance modification request to the domain management function unit. Correspondingly, the domain management function unit receives the wireless service intent instance modification request, wherein the wireless service intent instance modification request carries the identifier of the wireless service intent instance and the intent lifecycle indication information: implementation or execution (Fulfill).

[0196] Optionally, the radio service intent instance modification request is also called a request to configure radio service intent for fulfillment, which carries intent execution purpose=fulfill.

[0197] S310. The domain management functional unit modifies the value of the intent lifecycle indication information in the wireless service intent instance to fulfill (before modification, it was feasibility check or resource reservation or feasibility check and resource reservation), executes or implements the wireless service intent instance, and generates an intent execution report.

[0198] As shown in Figure 5, the domain management functional unit implements the wireless service intent instance in conjunction with the resources of network elements (such as base stations). Optionally, an intent fulfillment report may be included in the intent report and sent. In one optional implementation, the domain management functional unit executes or implements the wireless service intent instance and generates the intent fulfillment report, including: translating the wireless service intent instance into wireless service configuration parameters, configuring and activating the wireless service configuration parameters on network elements; after executing the wireless service intent instance, the domain management functional unit obtains network performance indicators; and evaluating whether the intent objectives of the wireless service intent instance are met based on the obtained network performance indicators, thereby obtaining a wireless service intent fulfillment report. The wireless service intent fulfillment report includes the intent execution results and the current performance measurement value of each intent objective. The intent execution results include whether the intent is met and / or whether each intent objective is met. Here, whether the intent is met refers to evaluating whether all intent objectives of the wireless service intent instance are met based on the obtained network performance indicators. If all intent objectives are met, the intent is fulfilled; otherwise, the intent is not met. For example, the intent targets are an uplink delay target of <10ms and an uplink rate target of >500Mbps. If both the uplink delay target and the uplink rate target are met based on network performance indicators, then the wireless service intent instance is met.

[0199] In another optional implementation, if the domain management function unit has reserved resources for the wireless service intent instance in step S307, then in step S310, the domain management function unit needs to allocate the reserved resources to the wireless service intent instance.

[0200] S311. The domain management function unit sends an intention execution report to the cross-domain management function unit. Correspondingly, the cross-domain management function unit receives the intention execution report.

[0201] As can be seen, in the intent processing method described in Figure 5, the cross-domain management system can perform at least one of the following management actions on the wireless service intent instance before implementation: a. Feasibility assessment, determining whether the intent information of the corresponding wireless service intent instance can be satisfied; b. Resource reservation, performing resource reservation before implementation to ensure sufficient resources to guarantee the provisioning of the corresponding wireless service during the implementation of the wireless service intent. This method can support different lifecycle management stages of the wireless service intent instance for the same wireless service intent instance, avoiding issues such as duplicate creation of wireless service intent instances that may lead to inconsistent information. It also ensures that the domain management system is aware of the management of the wireless service intent instance throughout its lifecycle. By introducing intent lifecycle indication information into the wireless service intent instance, it indicates that the created wireless service intent instance is eligible for feasibility assessment, resource reservation, and / or implementation, avoiding the immediate implementation of the created wireless service intent instance. Furthermore, by using the feasibility assessment and resource reservation stages for the wireless service intent instance, the desired wireless service instance can be successfully provisioned during implementation. This allows for obtaining wireless service provisioning capabilities between wireless service intent instance implementations, thereby guiding the sales of the corresponding wireless service.

[0202] Please refer to Figure 6, which is a flow chart of another intent processing method provided by an embodiment of the present application. The intent processing method described in Figure 6 takes the wireless energy saving intent of the radio access network (RAN) as an embodiment, and the target name of the intent target of the created wireless energy saving intent instance includes energy consumption, uplink rate and / or downlink rate, etc. The life cycle management phases described include: a probe phase and a fulfillment phase (also referred to as an implementation phase). Optionally, the intent target may also include other targets, such as energy efficiency, etc. The embodiment of the present application takes energy consumption and downlink rate as examples. In addition, in the intent processing method, the intent monitoring system or intent monitoring module is described by taking the cross-domain management functional unit in Figure 2, and the intent execution system or intent execution module is described by taking the domain management functional unit in Figure 2 as an example. In addition, the first request is a wireless energy saving intent instance creation request, the first indication information is the intent life cycle indication information, and the second request is an example of a wireless energy saving intent instance modification request. As shown in Figure 6, the intent processing method includes but is not limited to the following steps:

[0203] S401. The cross-domain management function unit sends a wireless energy-saving intention instance creation request to the domain management function unit. Correspondingly, the domain management function unit receives the wireless energy-saving intention instance creation request, which carries the intention information of the wireless energy-saving intention instance and the intention lifecycle indication information: probe.

[0204] The intent information of a wireless energy-saving intent instance includes information about the desired intent object (e.g., object type: radio access network subnet (RAN sub network), object name: coverage geographic area information) and information about the desired intent target (including energy consumption and downlink rate). The value of the intent lifecycle indicator (intent execution purpose) is probe, which instructs the intent execution system (i.e., the domain management functional unit) to perform an exploration and evaluation of the intent target for the wireless energy-saving intent instance.

[0205] Among them, the main difference between the intention target of the intention instance in the intention processing method described in Figure 6 and the intention target of the intention instance in the intention processing method described in Figure 5 is that the intention target of the intention instance in the intention processing method described in Figure 6 only has a name and no target value, or it can also be considered that the target value of the intention target of the intention instance in the intention processing method described in Figure 6 is set to 0.

[0206] Optionally, the wireless energy saving intent instance creation request is also called a radio access network energy saving intent creation request (request to create RAN energy saving intent), which carries an intent target name (intent target name) and intent execution purpose=probe.

[0207] Optionally, the wireless energy-saving intention instance creation request also carries simulation constraint information, and the simulation constraint information includes at least one of the following: online (online) or offline (offline) indication information, used to indicate the capability value of exploring the intention target of the wireless energy-saving intention instance in an online or offline manner; or indication information for indicating the technology that can be adopted for simulation (also called simulation technology). For example, the technology that can be explored includes NDT. Optionally, as shown in Figure 6, the NDT is integrated into the domain management function unit as a simulation module. Among them, this application does not limit the name of the simulation constraint information, and it can also be evaluation constraint information, verification constraint information or simulation evaluation constraint information, etc.

[0208] S402. The domain management function unit creates a wireless energy saving intention instance (or called a wireless energy saving intention management object instance) according to the wireless energy saving intention instance creation request.

[0209] Optionally, the created wireless energy-saving intent instance includes the intent information of the wireless energy-saving intent instance, the intent lifecycle indication information, or includes the intent information of the wireless energy-saving intent instance, the intent lifecycle indication information, and the simulation constraint information. As described above, the intent target in the intent information only includes the name of the wireless energy-saving target (including the energy consumption target and the downlink rate target), without a target value or with the target value set to 0.

[0210] S403. The domain management function unit sends wireless energy saving intention instance creation response information to the cross-domain management function unit. Correspondingly, the cross-domain management function unit receives the wireless energy saving intention instance creation response information.

[0211] The wireless energy-saving intention instance creation response message carries the identifier of the wireless energy-saving intention instance. Optionally, the identifier of the wireless energy-saving intention instance may be the DN of the management object instance. Optionally, the identifier of the wireless energy-saving intention instance may be carried in the wireless energy-saving intention instance creation request in step S401, or may be assigned to the wireless energy-saving intention instance by the domain management function unit when creating the wireless energy-saving intention instance in step S402.

[0212] Optionally, the wireless energy saving intent instance creation response information is also called a radio access network energy saving intent creation response (response for creating RAN energy saving intent), which carries the identifier of the intent instance.

[0213] S404. The domain management function unit explores (simulates and predicts) the wireless energy-saving intent instance based on the value of the intent lifecycle indication information (probe) in the wireless energy-saving intent instance, explores the capability values ​​of the supported energy consumption target and downlink rate target, and obtains a wireless energy-saving intent exploration report (intent probe report).

[0214] Optionally, the domain management functional unit simulates the wireless energy saving intention instance to explore the capability values ​​of the supported energy consumption targets and rate targets, which may include: the domain management functional unit gradually increases the increment according to the current measurement value to achieve the capability value with better energy consumption targets and rate targets.

[0215] The preferred capability value is a suitable, recommended, or better-performing value selected from multiple sets of intent target values ​​based on simulation results. The multiple sets of intent target values ​​include, but are not limited to, current measured values ​​and values ​​determined in incremental increments based on the current measured values. For example, if the intent targets include energy consumption targets and rate targets, the preferred capability value, i.e., the better-performing value, is a set of values ​​selected from multiple sets of energy consumption targets and downlink rate target values ​​based on simulation results, where the maximum energy consumption is lower and the minimum rate is larger.

[0216] For example, assuming the intended target includes an energy consumption target and a downlink rate target, the current measured values ​​are that the maximum energy consumption is 40 kWh (i.e., the energy consumption value is less than 40 kWh) and the minimum downlink rate is 400 Mbps (i.e., the downlink rate value is greater than 400 Mbps). If the maximum energy consumption is increased to 50 kWh (i.e., the energy consumption value is less than 50 kWh), the minimum downlink rate obtained by simulation is 500 Mbps (i.e., the downlink rate value is greater than 500 Mbps); if the energy consumption capacity value is further increased, if the maximum energy consumption is increased to less than 60 kWh (i.e., the energy consumption value is less than 60 kWh), the maximum downlink rate obtained by simulation is 500 Mbps (i.e., the downlink rate value is greater than 500 Mbps). Then, the values ​​of multiple sets of energy consumption targets and downlink rate targets are: (1) Current measured values: Energy consumption value is less than 40 kWh, downlink rate value is greater than 400 Mbps; Two sets of values ​​determined by simulation in a step-by-step increment manner: (2) Energy consumption capacity value is less than 50 kWh, downlink rate capacity value is greater than 500 Mbps; (3) Energy consumption capacity value is less than 60 kWh, downlink rate capacity value is greater than 500 Mbps. Then, according to the simulation results, the better capacity value selected from the above three sets of energy consumption targets and downlink rate targets is: Energy consumption capacity value is less than 50 kWh, downlink rate capacity value is greater than 500 Mbps. Compared with other sets of values, the minimum rate value of this set is the largest, but the maximum energy consumption value is the lowest.

[0217] Among them, this application does not limit how the cross-domain management function unit simulates the wireless energy-saving intention instance to obtain a capability value with better energy consumption target and downlink rate target.

[0218] Optionally, the domain management functional unit also determines the specific simulation method and means based on the simulation evaluation constraint information. For example, if the online or offline indication information indicates online, the simulation is performed online; if the simulation technology is NDT, the network digital twin is used for simulation to obtain a wireless energy-saving intention exploration report.

[0219] The wireless energy-saving intention exploration report contains at least one intention exploration result, each of which contains the capability values ​​of the intended target (i.e., energy consumption target and downlink rate target). For example, in intention exploration result 1, the energy consumption capability value is less than 50 kWh, and the downlink rate capability value is greater than 500 Mbps; in intention exploration result 2, the energy consumption capability value is less than 100 kWh, and the downlink rate capability value is greater than 300 Mbps.

[0220] Optionally, the capability value of the intended target may also include the current capability value and the capability value within the predicted time or predicted duration. For example, in the intent exploration result 3: the current capability value of energy consumption is less than 100 kWh, and the capability value of energy consumption within a predicted time or duration is less than 50 kWh; the current capability value of the downlink rate is greater than 600Mbps, and the capability value of the downlink rate within a predicted time or duration is greater than 500Mbs.

[0221] S405. The domain management function unit sends a wireless energy-saving intention exploration report to the cross-domain management function unit. Correspondingly, the cross-domain management function unit receives the wireless energy-saving intention exploration report, wherein the wireless energy-saving intention exploration report includes an identifier of a wireless energy-saving intention instance and at least one intention exploration result.

[0222] Among them, each intention exploration result includes: the name of the intention target (ie, energy consumption target and downlink rate target) and the corresponding capability value (which may include the current capability value and the capability value within the predicted time or predicted duration).

[0223] Optionally, the wireless energy saving intention probe report may be referred to as an intent probe report, and may be carried in an intent report and sent.

[0224] S406. The cross-domain management function unit determines a target value of the intent target in the wireless energy-saving intent instance according to the acquired wireless energy-saving intent exploration report.

[0225] For example, when the wireless energy-saving intention exploration report includes the two intention exploration results, intention exploration result 1 and intention exploration result 2, as mentioned above, the cross-domain management function unit selects intention exploration result 1 to determine the target value in the wireless energy-saving intention instance, such as the target value of energy consumption is less than 50 kilowatts, and the target value of the downlink rate is greater than 500Mbps.

[0226] S407. The cross-domain management function unit sends a wireless energy-saving intention instance modification request to the domain management function unit. Correspondingly, the domain management function unit receives the wireless energy-saving intention instance modification request, wherein the wireless energy-saving intention instance modification request carries the identifier of the wireless energy-saving intention instance, the target value of the wireless energy-saving intention instance (i.e., the target value of energy consumption and the target value of downlink rate) and the intention life cycle indication information: fulfill.

[0227] Optionally, the wireless energy saving intent instance modification request may also be referred to as a request to configure RAN energy saving intent for fulfillment, which carries an intent target value and intent execution purpose = fulfill. The intent target value is the target value of the intent target determined in step S406.

[0228] S408. The domain management functional unit modifies the value of the intent lifecycle indication information in the wireless energy-saving intention instance to fulfill (probe before modification), and configures the target value of the wireless energy-saving intention instance (that is, the target value of energy consumption in the wireless energy-saving intention instance is configured to be less than 50 kWh, and the target value of the downlink rate is configured to be greater than 500 Mbps), and executes / implements the wireless energy-saving intention instance, and generates a wireless energy-saving intention execution report.

[0229] As shown in Figure 6, the domain management functional unit implements the wireless energy saving intent instance in conjunction with the resources of the network element (such as the base station). Optionally, an intent fulfillment report can be sent with the intent report.

[0230] Optionally, the domain management functional unit executes or implements the wireless service intent instance and generates an intent execution report, including: the domain management functional unit translates the wireless energy-saving intent instance into wireless energy-saving configuration parameters, configures and activates the wireless energy-saving configuration parameters on the network element; after the domain management functional unit executes the wireless energy-saving intent instance, it obtains network performance indicators; and evaluates whether the intent target of the wireless energy-saving intent instance is met based on the obtained network performance indicators to obtain a wireless energy-saving intent execution report. The wireless energy-saving intent execution report includes the intent execution results (including whether the intent is met, whether each intent target is met), and the current performance measurement value of each intent target.

[0231] S409. The domain management function unit sends the wireless energy-saving intention execution report to the cross-domain management function unit. Correspondingly, the cross-domain management function unit receives the wireless energy-saving intention execution report.

[0232] It can be seen that in the intent processing method described in Figure 6, before the cross-domain management function unit sends the target value of the intent target of the wireless energy-saving intention instance to the domain management function unit, it can first obtain the capability value supported by the deployed network, and then select a better capability value as the target value of the wireless energy-saving intention instance, so as to avoid multiple blind settings that lead to the target value not being achieved, or setting the target value too low, resulting in the failure to obtain the network's better energy consumption effect and performance effect. In other words, the embodiment of the present application introduces the capability value exploration of the wireless energy-saving intention target before the execution of the wireless energy-saving intention instance, so as to enable the operator to obtain the capability value of the current network for the wireless energy-saving target, and then determine the target value of the better wireless intention instance, so as to avoid setting it too high and not being able to meet the requirements, and also avoid setting it too low and not being able to fully stimulate the network capabilities.

[0233] In the embodiments provided in the present application above, the solutions of the various methods provided in the embodiments of the present application are introduced from the perspective of each device itself and from the perspective of the interaction between each device. It is understandable that each device, such as the above-mentioned first device, second device, cross-domain management functional unit or domain management functional unit, etc., in order to implement the above-mentioned functions, includes a hardware structure and / or software unit corresponding to the execution of each function. Those skilled in the art should easily appreciate that, in combination with the units and algorithm steps of each example described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0234] Please refer to Figure 7, which is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device shown in Figure 7 includes a transceiver module 701.

[0235] In one design of this embodiment, the communication device is a device such as an intention monitoring system, a first device, or a cross-domain management function unit, or a related device among these devices:

[0236] In one example, the transceiver module 701 is used to send a first indication message, and the first indication message is used to indicate the lifecycle management stage of the intent instance; wherein the lifecycle management stage includes at least one of the feasibility assessment stage, resource reservation stage, exploration stage or implementation stage of the intent instance; accordingly, the transceiver module 701 is also used to receive the intent management results obtained by the intent instance in the lifecycle management stage.

[0237] In another example, the transceiver module 701 is used to send a first indication message, and the first indication message is used to indicate the lifecycle management stage of the wireless service intention instance; wherein the lifecycle management stage includes at least one of the feasibility assessment stage, resource reservation stage or implementation stage of the wireless service intention instance; accordingly, the transceiver module 701 is also used to receive the intent management result obtained by the wireless service intention instance in the lifecycle management stage.

[0238] In another example, the transceiver module 701 is used to send a first indication message, and the first indication message is used to indicate the lifecycle management stage of the wireless energy-saving intention instance; wherein the lifecycle management stage includes at least one of the exploration stage or the implementation stage of the wireless energy-saving intention instance; accordingly, the transceiver module 701 is also used to receive the intent management result obtained by the wireless energy-saving intention instance in the lifecycle management stage.

[0239] Optionally, the communication device may further include a processing module 702 for determining the first indication information. Optionally, the communication device may also be used to implement the functions of the intention monitoring system, the first device or the cross-domain management functional unit in the embodiments shown in Figures 1 to 6 and the optional implementation methods.

[0240] In another design of this embodiment, the communication device is a device such as an intention execution system, a second device, or a domain management function unit, or a related device among these devices:

[0241] In one example, the transceiver module 701 is used to receive first indication information, where the first indication information is used to indicate the lifecycle management stage of the intent instance; wherein the lifecycle management stage includes at least one of the feasibility assessment stage, resource reservation stage, exploration stage, or implementation stage of the intent instance; the transceiver module 701 is also used to send the intent management result obtained by the intent instance during the lifecycle management stage. Optionally, the communication device may further include a processing module 702, which is used to manage the intent instance according to the lifecycle management stage indicated by the first indication information and obtain the intent management result.

[0242] In another example, the transceiver module 701 is configured to receive first indication information, where the first indication information is configured to indicate a lifecycle management stage of a wireless service intent instance; wherein the lifecycle management stage includes at least one of a feasibility assessment stage, a resource reservation stage, or an implementation stage of the wireless service intent instance; and the transceiver module 701 is further configured to transmit an intent management result obtained during the lifecycle management stage of the wireless service intent instance. Optionally, the communication device may further include a processing module 702 configured to manage the wireless service intent instance according to the lifecycle management stage indicated by the first indication information and obtain an intent management result.

[0243] In another example, the transceiver module 701 is configured to receive first indication information indicating a lifecycle management phase of a wireless energy-saving intent instance; wherein the lifecycle management phase includes at least one of an exploration phase or an implementation phase of the wireless energy-saving intent instance; and the transceiver module 701 is further configured to transmit an intent management result obtained during the lifecycle management phase of the wireless energy-saving intent instance. Optionally, the communication device may further include a processing module 702 configured to manage the wireless energy-saving intent instance according to the lifecycle management phase indicated by the first indication information and obtain an intent management result.

[0244] Optionally, when the communication device is an intention execution system, a second device or a domain management functional unit or other devices or related devices in these devices, it is also used to implement the functions of these devices in the embodiments shown in Figures 1 to 6 and optional implementation methods.

[0245] Please refer to Figure 8, which is a schematic diagram of the structure of another communication device provided in an embodiment of the present application. The communication device shown in Figure 8 includes at least one processor 801. Optionally, it also includes a memory 802 and / or a transceiver 803. The specific connection medium between the above-mentioned processor 801 and the memory 802 is not limited in the embodiment of the present application. In Figure 8, the connection between the memory 802 and the processor 801 via the bus 804 is taken as an example. The bus 804 is represented by a bold line in the figure. The connection method between other components is only for schematic illustration and is not limited. The bus 804 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one bold line is used in Figure 8, but it does not mean that there is only one bus or one type of bus.

[0246] The processor 801 may have a data transceiver function and may communicate with other devices. In the apparatus shown in FIG8 , an independent data transceiver module, such as a transceiver 803, may also be provided for transmitting and receiving data. When the processor 801 communicates with other devices, data may be transmitted through the transceiver 803.

[0247] In one example, when the intent monitoring system, the first device or the cross-domain management functional unit adopts the form shown in Figure 8, the processor 801 in Figure 8 can call the computer execution instructions stored in the memory 802 to enable the intent monitoring system, the first device or the cross-domain management functional unit to execute the method corresponding to the intent monitoring system, the first device and the cross-domain management functional unit in any embodiment of Figures 1 to 6.

[0248] In one example, when the intention execution system, the second device or the domain management functional unit adopts the form shown in Figure 8, the processor 801 in Figure 8 can call the computer execution instructions stored in the memory 802 to enable the intention execution system, the second device or the domain management functional unit to execute the method executed by the intention execution system, the second device and the domain management functional unit in any embodiment of Figures 1 to 6.

[0249] An embodiment of the present application also provides a communication system, which may include the intent monitoring system, the first device or the cross-domain management functional unit in Figures 1 to 6, and also includes the intent execution system, the second device or the domain management functional unit in Figures 1 to 6. For details, please refer to the method embodiments described above.

[0250] The solutions described in this application can be implemented in various ways. For example, these techniques can be implemented in hardware, software, or a combination of hardware. For hardware implementation, the processing module used to execute these techniques at a communication device (e.g., a base station, a terminal, a network entity, or a chip) can be implemented in one or more general-purpose processors, digital signal processors (DSPs), digital signal processing devices, application-specific integrated circuits (ASICs), programmable logic devices, field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor can be a microprocessor, and optionally, the general-purpose processor can also be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration.

[0251] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0252] The present application also provides a computer-readable medium having instructions stored thereon, which, when executed by a computer, enables the computer device to implement the functions of any of the above method embodiments through a transceiver and a processor.

[0253] The present application also provides a computer program product, which, when executed by a computer, enables the computer device to implement the functions of any of the above method embodiments through a transceiver and a processor.

[0254] The present application also provides a processing device, which may be a product such as a chip device, and the processing device is used to determine the relevant information required in the embodiments described in any of the diagrams in Figures 1 to 6. For example, the processing device is used to determine a model acquisition response. For another example, the processing device is used to use the model to be migrated, fine-tune it through transfer learning, and obtain the required model. Optionally, the processing device may be a baseband processing module, and the information determined by the processing device may be sent out through the radio frequency processing module, such as the migrated model or the model to be migrated. Alternatively, information sent by other devices is received through the radio frequency processing module, and the processing device determines other information based on the information.

[0255] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0256] It is understandable that some optional features in the embodiments of the present application may, in certain scenarios, be implemented independently of other features, such as the solution on which they are currently based, to solve corresponding technical problems and achieve corresponding effects. They may also be combined with other features in certain scenarios as needed. Accordingly, the devices provided in the embodiments of the present application may also implement these features or functions accordingly, which will not be described in detail here.

[0257] Those skilled in the art will also appreciate that the various illustrative logical blocks and steps listed in the embodiments of the present application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the described functions for corresponding applications, but such implementation should not be construed as exceeding the scope of protection of the embodiments of the present application.

[0258] It will be understood that the “embodiment” mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, the various embodiments in the entire specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It will be understood that in the various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0259] It can be understood that in this application, "when", "if" and "if" all mean that the device will perform corresponding processing under certain objective circumstances, and do not limit the time, nor do they require the device to make judgments when it is implemented, nor do they mean that there are other limitations.

[0260] In this application, elements expressed in the singular are intended to mean "one or more" rather than "one and only one", unless otherwise specified. In this application, unless otherwise specified, "at least one" is intended to mean "one or more", and "more than one" is intended to mean "two or more". In the text description of this application, "including at least one of A, B and C" may mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B and C. In the text description of this application, "and / or" is merely a description of the association relationship of associated objects, indicating that there may be three relationships. For example, A and / or B may mean: A exists alone, A and B exist at the same time, and B exists alone, where A may be singular or plural, and B may be singular or plural.

[0261] It is understood that the various numbers involved in the embodiments of the present application are only for the convenience of description and are not intended to limit the scope of the embodiments of the present application. The size of the sequence number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic. In addition, the terms "system" and "network" are often used interchangeably in this article.

[0262] The predefined in this application may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0263] Those skilled in the art will appreciate that, for the sake of convenience and brevity of description, the specific working processes of the above-described systems, devices, and units may refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0264] The same or similar parts between the various embodiments in this application can refer to each other. In the various embodiments in this application, and the various implementation methods / implementation methods / implementation methods in each embodiment, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment are consistent and can be referenced to each other. The technical features in different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment can be combined to form new embodiments, implementation methods, implementation methods, or implementation methods according to their inherent logical relationships. The above-described implementation methods of this application do not constitute a limitation on the scope of protection of this application.

[0265] The above is only a specific implementation method of the present application, but the scope of protection of the present application is not limited thereto. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in this application, which should be covered by the scope of protection of the present application.

Claims

1. An intention processing method, characterized in that, The method further includes: Sending first indication information for indicating a lifecycle management phase of an intent instance; Wherein the lifecycle management phase includes at least one of a feasibility assessment phase, a resource reservation phase, an exploration phase, or an implementation phase of the intent instance; Receiving an intent management result obtained by the intent instance in the lifecycle management phase.

2. The method according to claim 1, characterized in that, The sending of the first indication information includes: Sending a first request for requesting creation of the intent instance, the first request including intent information and the first indication information, and the intent information including an intent object and an intent target of the intent instance.

3. The method according to claim 1 or 2, characterized in that The lifecycle management phase indicated by the first indication information includes a feasibility assessment phase; The intent management result obtained by the intent instance in the lifecycle management phase includes a feasibility assessment result obtained by the intent instance in the feasibility assessment phase.

4. The method according to any one of claims 1 to 3, characterized in that The lifecycle management phase indicated by the first indication information includes a resource reservation phase; The intent management result obtained by the intent instance in the lifecycle management phase includes a resource reservation result obtained by the intent instance in the resource reservation phase.

5. The method according to any one of claims 1 to 4, characterized in that The lifecycle management phase indicated by the first indication information includes an exploration phase; The intent management result obtained by the intent instance in the lifecycle management phase includes an intent exploration result obtained by the intent instance in the exploration phase, and each intent exploration result includes a capability value of the intent target of the intent instance.

6. The method according to claim 5, characterized in that, The method further includes: Determining a target value of the intent target according to the intent exploration result obtained by the intent instance in the exploration phase; Sending the target value of the intent target.

7. The method according to any one of claims 3 to 6, characterized in that The method further includes: Sending second indication information for indicating modification of the lifecycle management phase of the intent instance to an implementation phase; Receiving an intent execution result obtained by the intent instance in the implementation phase.

8. The method according to claim 3, 5 or 6, characterized in that, The method further includes: Sending first evaluation constraint information, wherein the first evaluation constraint information includes indication information for indicating a simulation technique, and / or indication information for indicating online simulation or offline simulation.

9. The method according to any one of claims 1 to 8, characterized in that, The intent instance is a wireless service intent instance, the intent object of the wireless service intent instance includes coverage geographical area information of a network device or a cell, and the intent target of the wireless service intent instance includes a latency target and / or a rate target.

10. The method according to any one of claims 1 to 8, characterized in that, The intent instance is a wireless energy saving intent instance, the intent object of the wireless energy saving intent instance includes coverage geographical area information of a network device or a cell, and the intent target of the wireless energy saving intent instance includes an energy consumption target and / or a rate target.

11. A method for intention processing, characterized in that, The method includes: Receiving first indication information for indicating a lifecycle management phase of an intent instance; Wherein, the lifecycle management stage includes at least one of a feasibility evaluation stage, a resource reservation stage, an exploration stage, or an implementation stage of the intent instance; Send the intent management result obtained by the intent instance in the lifecycle management stage.

12. The method according to claim 11, wherein The receiving the first indication information includes: Receive a first request, where the first request includes intent information and first indication information, and the intent information includes an intent object and an intent target of the intent instance; The method further includes: Create the intent instance according to the intent information.

13. The method according to claim 11 or 12, wherein The lifecycle management stage indicated by the first indication information includes a feasibility evaluation stage; The intent management result obtained by the intent instance in the lifecycle management stage includes a feasibility evaluation result obtained by the intent instance in the feasibility evaluation stage.

14. The method according to claim 13, wherein The method further includes: Perform a feasibility evaluation on the intent instance to obtain the feasibility evaluation result.

15. The method according to any one of claims 11 to 14, wherein The lifecycle management stage indicated by the first indication information includes a resource reservation stage; The intent management result obtained by the intent instance in the lifecycle management stage includes a resource reservation result obtained by the intent instance in the resource reservation stage.

16. The method according to claim 15, wherein The method further includes: Reserve corresponding resources for the intent instance to obtain a resource reservation result.

17. The method according to any one of claims 11 to 14, wherein The lifecycle management stage indicated by the first indication information includes an exploration stage; The intent management result obtained by the intent instance in the lifecycle management stage includes an intent exploration result obtained by the intent instance in the exploration stage; wherein, each intent exploration result includes a capability value of the intent target of the intent instance.

18. The method according to claim 17, characterized in that, The method further includes: Perform an exploration evaluation of the intent target of the intent instance to obtain the intent exploration result.

19. The method according to claim 17 or 18, characterized in that, The method further includes: Receive a target value of the intent target, and the target value of the intent target is determined by the capability value of the intent target.

20. The method according to any one of claims 13 to 19, characterized in that, The method further includes: Receive second indication information for indicating to modify the lifecycle management stage of the intent instance to an implementation stage; Send the intent execution result obtained by the intent instance in the implementation stage.

21. The method according to any one of claims 13, 14, or 17 to 19, characterized in that, The method further includes: Receive evaluation constraint information, wherein the evaluation constraint information includes indication information for indicating a simulation technology, and / or indication information for indicating online simulation or offline simulation.

22. The method according to any one of claims 11 to 21, characterized in that, The intent instance is a wireless service intent instance, the intent object of the wireless service intent instance includes coverage geographical area information of a network device or a cell, and the intent target of the wireless service intent instance includes a latency target and / or a rate target.

23. The method according to any one of claims 11 to 21, characterized in that, The intent instance is a wireless energy saving intent instance, the intent object of the wireless energy saving intent instance includes coverage geographical area information of a network device or a cell, and the intent target of the wireless energy saving intent instance includes an energy consumption target and / or a rate target.

24. A communication device, characterized in that, comprises one or more functional units, which are configured to execute the method according to any one of claims 1 to 10, or to execute the method according to any one of claims 11 to 23.

25. A communication device, characterized in that, comprises a processor, which calls a computer program stored in a memory to cause the communication device to implement the method according to any one of claims 1 to 10, or to implement the method according to any one of claims 11 to 23.

26. A communication device, characterized in that, comprises a processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, the processor being configured to implement the method according to any one of claims 1 to 10 by means of logic circuits or by executing code instructions, or being configured to implement the method according to any one of claims 11 to 23.

27. A communication system, characterized in that, comprises at least one of the following devices: a device for executing the method according to any one of claims 1 to 10, or a device for executing the method according to any one of claims 11 to 23.

28. A computer-readable storage medium, characterized in that, a computer program is stored in the computer-readable storage medium, and when the computer program is run, it implements the method according to any one of claims 1 to 10, or implements the method according to any one of claims 11 to 23.

29. A computer program product comprising instructions, which when run on a computer cause the computer to execute the method according to any one of claims 1 to 10, or to execute the method according to any one of claims 11 to 23.

Images