Communication method and apparatus

Abstract

The present application relates to the technical field of communications, and provides a communication method and apparatus, which are used for avoiding intent conflicts and improving service stability. In the method, on the basis of a first resource estimated to be required to be occupied to complete each expected intent among at least one expected intent, a first device can send second information to a second device to indicate whether preoccupation of the first resource for a first service is successful within an active time period, so that, subsequently, the second device can determine whether the active time period needs to be modified. When preoccupation of the first resource for a first intent instance is successful within the active time period, the first device can occupy the first resource within the active time period. That is, when the active time period is reached, the first device can directly occupy or use the first resource to implement the first intent instance. In this way, preoccupation of resources can be achieved, thereby avoiding the occurrence of intent conflicts and improving the service stability.

Description

Communication method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on December 21, 2023, with application number 202311777232.3 and application name “Communication Method and Device,” the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to a communication method and device. Background Art

[0003] In the current 3rd Generation Partnership Project (3GPP), management service consumers (MnS Consumers) can express their requirements, goals, and constraints for services or networks by configuring intent models. When delivering service intents using the intent model, MnS Consumers can activate or deactivate the intent by configuring the intentAdminiState attribute. Management service producers (MnS Producers) can then synchronously execute the intent based on the received intent expression.

[0004] However, if the MnS Consumer sends a large number of service intents at the same time, intent conflicts may occur, resulting in low service stability.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a communication method and apparatus to avoid conflicts of intent and improve service stability.

[0007] To achieve the above objectives, this application adopts the following technical solutions:

[0008] In a first aspect, a communication method is provided, which can be executed by a first device, or by a chip or circuit configured in the first device, or by a logic module or software that can realize all or part of the functions of the first device. The method includes: the first device receives a first request message from the second device, sends second information to the second device based on the first information, and occupies the first resource during the activation time period if the first resource is successfully pre-occupied during the activation time period. The first request message is used to request the creation of a first intention instance corresponding to the first business, the first request message includes the activation time period of the first intention instance, and the first intention instance includes at least one intention expectation; the first information is used to indicate the first resource required to estimate the completion of each of the at least one intention expectation, and the second information is used to indicate whether the first resource is successfully pre-occupied during the activation time period.

[0009] Based on the method described in the first aspect, the first device can send second information to the second device based on the estimated first resource required to complete each of the at least one intention expectation to indicate whether the first service has successfully pre-occupied the first resource within the activation time period, so that the second device can subsequently determine whether the activation time period needs to be modified. The first request message may include the activation time period of the first intention instance. When the first intention instance successfully pre-occupies the first resource within the activation time period, the first device can occupy the first resource within the activation time period, that is, when the activation time period is reached, the first device can directly occupy or use the first resource to implement the first intention instance. In this way, the pre-occupation of resources can be achieved, the intention conflict can be avoided, and the stability of the service can be improved.

[0010] In one possible design, the activation time period includes a first activation time and a first deactivation time, so that the first device can determine the time to activate the first intent instance and the time to deactivate the first intent instance. It is understood that if the activation time period does not include the first deactivation time, the first device can continue to occupy the first resource after activating the first intent instance until the second device sends a deactivation time or reconfigures the activation time period, etc., without limitation.

[0011] Optionally, the first request message includes an identifier and cycle information of the first service. The identifier is used to identify the first service, and the cycle information is used to indicate that the first intent instance is to be executed according to the scheduled cycle. In this way, the first device can determine, based on the identifier, that the intent instance to be created is related to the first service; and the first device can occupy the first resource periodically within the activation time within the scheduled cycle based on the cycle information, so as to avoid the need for the first device to re-occupy resources each time, thereby saving overhead.

[0012] In a possible design scheme, the method described in the first aspect also includes: the first device generates a first intention scheme based on the first intention instance. The first intention scheme is used to realize each intention expectation of at least one intention expectation. That is, the first intention scheme can be one of the intention schemes that can meet all the expected goals of the first intention instance, without limitation. The first device can use the first resource to execute the first intention scheme within the activation time period to realize the first intention instance. In a possible design scheme, before the first device sends the second information to the second device based on the first information, the method described in the first aspect also includes: the first device obtains the first information according to the first intention scheme. That is, the first device can directly pre-execute the first intention scheme by calling internal services, such as perception, analysis, decision-making and other components to obtain the first information, so that signaling overhead can be saved.

[0013] In a possible design scheme, before the first device sends the second information to the second device based on the first information, the method described in the first aspect also includes: the first device sends a second request message to the third device, and receives the first information returned by the third device based on the second request message. The second request message is used to request the estimated resources required to complete each of at least one intention expectation. That is, the first device sends a second request message to a third device of a third party to request the third device to generate the first information, and receives the first information returned after the third device pre-executes the first intention scheme. The third device can be a digital twin system, a knowledge base or an artificial intelligence AI model with a pre-evaluation function. In this way, the accuracy of the first information can be improved.

[0014] Optionally, the second request message includes at least one of the following: a first intention scheme, an expectation list, and / or expectation object information. The expectation list is used to indicate at least one intention expectation; the expectation object information is used to indicate the object that executes the first intention instance. In this way, the third device can estimate the first resources required to complete each of the at least one intention expectation after the first intention scheme is executed based on the expectation object information, thereby obtaining the first information.

[0015] In a possible design scheme, before the first device sends the second information to the second device based on the first information, the method described in the first aspect also includes: the first device determines whether there is an intent conflict between the first intent instance and other intent instances based on the first information. For example, if there is a resource that is larger than the first resource and is not pre-occupied during the activation time period, then there is no intent conflict between the first intent instance and other intent instances; if there is no resource that is larger than the first resource and is not pre-occupied during the activation time period, then there is an intent conflict between the first intent instance and other intent instances. In this way, the first device can determine whether the first intent instance of the device has successfully reserved the first resource, so that the first device can subsequently reasonably allocate network resources according to the situation of the intent conflict, for example, give priority to resource allocation for high-priority services to ensure the stability of high-priority services.

[0016] In a possible design scheme, there is no intention conflict between the first intention instance and other intention instances, and the method described in the first aspect also includes: the first device saves the first intention scheme. Among them, the first intention scheme occupies the first resource during the activation time period. It can be understood that the first intention scheme can be some configuration commands, and the first device can pre-save this part of the configuration commands. When the first device activates the first intention instance, the first device can directly execute this part of the configuration commands to avoid intention conflicts when executing the first intention instance, and give priority to ensuring the stability of the first business.

[0017] Optionally, the second information is used to indicate that the first resource is successfully reserved within the activation time period. In this way, the second device can determine that the first intention instance or the first service has successfully reserved the resource, or the second device can determine that the first service can be executed normally within the activation time period.

[0018] Optionally, the method described in the first aspect further includes: when the first activation time is reached, the first device activates the first intent instance; the first device occupies the first resource to execute the first intent scheme, and sends third information to the second device. The third information is used to indicate that the first resource is being used. That is, when the first activation time is reached, the first device can activate the first intent instance, and directly use the pre-occupied first resource to execute the first intent scheme, and feedback to the second device that the first resource is being used, so that the second device can determine that the first intent instance has been activated.

[0019] Optionally, the method described in the first aspect also includes: when the first deactivation time is reached, the first device deactivates the first intention instance; the first device suspends the execution of the first intention scheme and releases the first resource; the first device sends a fourth message to the second device. The fourth information is used to indicate that the first resource is successfully pre-occupied within the activation time period. That is, when the first deactivation time is reached, the first device needs to release the first resource to ensure the resource requirements of other services. The first device feeds back to the second device that the first resource is successfully pre-occupied within the activation time period. In this way, the second device can determine that the first intention instance or the first service has periodically reserved the first resource to avoid the need for the first device to re-occupy the resource every time, saving overhead.

[0020] In one possible design scheme, the method described in the first aspect further includes: the first device receives instruction information from the second device, and deactivates or deletes the first intent instance based on the instruction information, the first device suspends execution of the first intent scheme, and releases the first resource. The instruction information is used to indicate the deactivation or deletion of the first intent instance. In this way, the second device can deactivate the first intent instance in advance or delay to meet different business needs.

[0021] Wherein, the indication information is specifically used to indicate the deletion of the first intent instance. That is, the second device can directly delete the first intent instance in advance by sending the third indication information. At this time, the first device can send the sixth information to the second device to indicate that the current intent resource management state is empty, that is, the first intent instance does not exist.

[0022] If the third indication information is specifically used to indicate that the first deactivation time is modified to the third deactivation time, the method described in the first aspect also includes: when the third deactivation time is reached, the first device deactivates the first intention scheme, suspends the execution of the first intention scheme, and releases the first resource being occupied. That is, the second device can achieve early or delayed deactivation of the first intention instance by modifying the first deactivation time. At this time, the first device can send the sixth information to the second device. If the first intention instance is a periodically executed intention instance, the sixth information can indicate that the current intention resource management state is a successfully reserved state; if the first intention instance is a non-periodically executed intention instance, the sixth information can indicate that the current intention resource management state is an unreserved state.

[0023] In one possible design, there is an intent conflict between the first intent instance and other intent instances, and the second information is used to indicate a failure to pre-occupy the first resource within the activation time period. In this way, the second device can determine that the first intent instance or the first service failed to reserve resources within the activation time period, so that the second device can subsequently determine to modify the activation time period to resolve the intent conflict between the first intent instance and other intent instances, thereby improving the stability of the first service.

[0024] Optionally, before the first device sends the second information to the second device based on the first information, the method described in the first aspect also includes: the first device determines the second activation time and / or the second deactivation time of the first intention instance based on the priority of the intention instance. Wherein, the intention instance includes the first intention instance. That is, the first device can modify the first activation time to the second activation time, and / or modify the first deactivation time to the second deactivation time based on the priority of other intention instances that conflict with the first intention instance, so that the second device can subsequently determine to modify the activation time period. For example, optionally, the method described in the first aspect also includes: the first device sends fifth information to the second device. Wherein, the fifth information is used to indicate that there is an intent conflict between the first intention instance and other intention instances, and the fifth information includes the second activation time, and / or the second deactivation time.

[0025] Optionally, the method described in the first aspect also includes: the first device receives a third request message from the second device, modifies the activation time period according to the second activation time and / or the second deactivation time, obtains the modified activation time period, and executes the first intention scheme within the modified activation time period. The third request message is used to request to modify the activation time period according to the second activation time and / or the second deactivation time. That is, the second device determines to modify the activation time period according to the second activation time and / or the second deactivation time based on the third request message, and instructs the first device to execute the first intention scheme within the modified activation time period to resolve the situation where there is an intent conflict between the first intent instance and other intent instances, which can improve the stability of the first business.

[0026] In one possible design, the first device is the intent producer and the second device is the intent consumer. That is, the first device and the second device can be adapted to the 3GPP architecture, thus meeting the needs of different scenarios.

[0027] In one possible design, a first device includes a first functional entity, a second functional entity, and a first application. Alternatively, the combination of the first functional entity, the second functional entity, and the first application can implement the same functions or roles as the first device. The second device is the intent owner. It is understood that the first functional entity can be a non-RT RIC, the second functional entity can be a near-RT RIC, and the first application can be an extended application such as XAPP1. In other words, the first and second devices can be adapted for use in an O-RAN architecture, thus meeting the needs of different scenarios.

[0028] In the second aspect, a communication method is provided, which can be executed by a second device, or by a chip or circuit configured in the second device, or by a logic module or software that can realize all or part of the functions of the second device. The method includes: the second device sends a first request message to the first device, and receives second information from the first device. The first request message is used to request the creation of a first intent instance corresponding to the first business, the first request message includes the activation time period of the first intent instance, and the first intent instance includes at least one intent expectation; the second information is determined by the first information, and the first information is used to indicate the estimated first resource required to complete each of the at least one intent expectation; the second information is used to indicate whether the first resource is pre-occupied successfully within the activation time period.

[0029] In one possible design, the activation time period includes a first activation time and a first deactivation time.

[0030] Optionally, the first request message includes an identifier and cycle information of the first service, wherein the identifier is used to identify the first service, and the cycle information is used to indicate that the first intent instance is to be executed according to a predetermined cycle.

[0031] In one possible design scheme, there is no intent conflict between the first intent instance and other intent instances, and the second information is used to indicate that the reservation of the first resource within the activation time period is successful.

[0032] Optionally, the method of the second aspect further includes: the second device receiving third information from the first device, wherein the third information is used to indicate that the first resource is being used.

[0033] Optionally, the method described in the second aspect further includes: the second device receiving fourth information from the first device, wherein the fourth information is used to indicate that the first resource is pre-occupied successfully within the activation time period.

[0034] In one possible design scheme, there is an intent conflict between the first intent instance and other intent instances, and the second information is used to indicate a failure to pre-occupy the first resource within the activation time period.

[0035] Optionally, the method described in the second aspect further includes: the second device receiving fifth information from the first device, and sending a third request message to the first device based on the fifth information. The fifth information is used to indicate that there is an intent conflict between the first intent instance and other intent instances, and the fifth information includes a second activation time and / or a second deactivation time; and the third request message is used to request modification of the activation time period based on the second activation time and / or the second deactivation time.

[0036] In one possible design, the first device is the intent producer and the second device is the intent consumer.

[0037] In one possible design scheme, the first device includes: a first functional entity, a second functional entity and a first application, or a combination of the first functional entity, the second functional entity and the first application, which can achieve the same function or role as the above-mentioned first device; the second device is the intended owner.

[0038] In addition, the relevant technical effects of the method described in the second aspect can also refer to the relevant introduction of the method described in the first aspect, and will not be repeated here.

[0039] In a third aspect, a communication method is provided, which can be executed by a third device, or by a chip or circuit configured in the third device, or by a logic module or software that can realize all or part of the functions of the third device. The method includes: the third device receives a second request message from the first device, generates first information based on the second request message, and sends the first information to the first device. The second request message is used to request the estimated resources required to complete each of the at least one intended expectation; the first information is used to indicate the estimated first resources required to complete each of the at least one intended expectation.

[0040] In one possible design, the second request message includes at least one of the following: a first intent solution, a desired list, or desired object information. The first intent solution is used to implement each of the at least one desired intent; the desired list is used to indicate the at least one desired intent; and the desired object information is used to indicate the object on which to execute the first intent instance.

[0041] The relevant technical effects of the method described in the third aspect can also be referred to the relevant introduction of the method described in the first aspect, and will not be repeated here.

[0042] In a fourth aspect, a communication method is provided, the method comprising: a first device executing the method described in the first aspect, and a second device executing the method described in the second aspect.

[0043] In addition, the technical effects of the method described in the fourth aspect can also refer to the technical effects of the methods described in the first to second aspects, and will not be repeated here.

[0044] In a fifth aspect, a communication method is provided, which includes: a first device executing the method described in the first aspect, a second device executing the method described in the second aspect, and a third device executing the method described in the third aspect.

[0045] In addition, the technical effects of the method described in the fifth aspect can also refer to the technical effects of the methods described in the first to third aspects, and will not be repeated here.

[0046] In a sixth aspect, a communication device is provided, which includes: a module for executing the method described in the first aspect, for example, a transceiver module and a processing module.

[0047] Among them, the transceiver module is used to receive a first request message from the second device, and send the second information to the second device based on the first information. In the case that the first resource is pre-occupied successfully within the activation time period, the processing module is used to occupy the first resource within the activation time period. Among them, the first request message is used to request the creation of a first intention instance corresponding to the first business, the first request message includes the activation time period of the first intention instance, and the first intention instance includes at least one intention expectation; the first information is used to indicate the first resource required to estimate the completion of each of the at least one intention expectation, and the second information is used to indicate whether the first resource is pre-occupied successfully within the activation time period.

[0048] In one possible design, the activation time period includes a first activation time and a first deactivation time.

[0049] Optionally, the first request message includes an identifier and cycle information of the first service, wherein the identifier is used to identify the first service, and the cycle information is used to indicate that the first intent instance is to be executed according to a predetermined cycle.

[0050] In one possible design solution, the processing module is further configured to generate a first intention solution based on the first intention instance, wherein the first intention solution is configured to implement each of the at least one intention expectation.

[0051] In one possible design scheme, before the first device sends the second information to the second device based on the first information, the processing module is further used to obtain the first information according to the first intention scheme.

[0052] In one possible design, before the first device sends the second information to the second device based on the first information, the transceiver module is further configured to send a second request message to the third device and receive the first information returned by the third device based on the second request message. The second request message is used to request an estimated resource required to complete each of the at least one intended expectation.

[0053] Optionally, the second request message includes at least one of the following: a first intent scheme, a desired list, or desired object information, wherein the desired list is used to indicate at least one intent expectation; and the desired object information is used to indicate an object to execute the first intent instance.

[0054] In one possible design scheme, before the first device sends the second information to the second device based on the first information, the processing module is also used to determine whether there is an intent conflict between the first intent instance and other intent instances based on the first information.

[0055] In a possible design solution, the first intent instance does not conflict with other intent instances, and the processing module is further configured to save the first intent solution, wherein the first intent solution occupies the first resource during the activation time period.

[0056] Optionally, the second information is used to indicate that the first resource is successfully pre-occupied within the activation time period.

[0057] Optionally, when the first activation time is reached, the processing module is further configured to activate the first intent instance. The processing module is further configured to occupy the first resource to execute the first intent solution and send third information to the second device. The third information is configured to indicate that the first resource is being used.

[0058] Optionally, when the first deactivation time is reached, the processing module is further configured to deactivate the first intent instance. The processing module is further configured to suspend execution of the first intent solution and release the first resource. The transceiver module is further configured to send fourth information to the second device. The fourth information is configured to indicate that the first resource was successfully pre-occupied within the activation time period.

[0059] In one possible design scheme, there is an intent conflict between the first intent instance and other intent instances, and the second information is used to indicate a failure to pre-occupy the first resource within the activation time period.

[0060] Optionally, before the first device sends the second information to the second device based on the first information, the processing module is further used to determine the second activation time and / or second deactivation time of the first intent instance based on the priority of the intent instance, wherein the intent instance includes the first intent instance.

[0061] Optionally, the transceiver module is further configured to receive a third request message from the second device. The processing module is further configured to modify the activation time period based on the second activation time and / or the second deactivation time, obtain the modified activation time period, and execute the first intention solution within the modified activation time period. The third request message is used to request modification of the activation time period based on the second activation time and / or the second deactivation time.

[0062] Optionally, the transceiver module may include a sending module and a receiving module, wherein the sending module is used to implement the sending function of the communication device described in the sixth aspect, and the receiving module is used to implement the receiving function of the communication device described in the sixth aspect.

[0063] Optionally, the communication device described in the sixth aspect may further include a storage module, wherein the storage module stores a program or instruction. When the processing module executes the program or instruction, the communication device may execute the communication method described in the first aspect.

[0064] It should be noted that the communication device described in the sixth aspect can be a first device, or a chip (system) or other parts or components that can be set in the first device, or a device that includes the first device. The embodiments of the present application do not limit this.

[0065] In addition, the technical effects of the communication device described in the sixth aspect can refer to the technical effects of the communication method described in the first aspect, and will not be repeated here.

[0066] In a seventh aspect, a communication device is provided, which includes modules for executing the method described in the second aspect, for example, a transceiver module and a processing module.

[0067] The transceiver module is configured to send a first request message to the first device and receive second information from the first device. The first request message is configured to request the creation of a first intent instance corresponding to the first service, the first request message includes an activation time period for the first intent instance, and the first intent instance includes at least one intent expectation. The second information is determined based on the first information, the first information is configured to indicate the first resource required to complete each of the at least one intent expectation. The second information is configured to indicate whether the first resource is successfully pre-occupied within the activation time period.

[0068] In one possible design, the activation time period includes a first activation time and a first deactivation time.

[0069] Optionally, the first request message includes an identifier and cycle information of the first service, wherein the identifier is used to identify the first service, and the cycle information is used to indicate that the first intent instance is to be executed according to a predetermined cycle.

[0070] In one possible design scheme, there is no intent conflict between the first intent instance and other intent instances, and the second information is used to indicate that the first resource is pre-occupied successfully within the activation time period.

[0071] Optionally, the transceiver module is further configured to receive third information from the first device, wherein the third information is used to indicate that the first resource is being used.

[0072] Optionally, when the first deactivation time arrives, the transceiver module is further configured to receive fourth information from the first device, wherein the fourth information is configured to indicate that the first resource is successfully pre-occupied within the activation time period.

[0073] In one possible design scheme, there is an intent conflict between the first intent instance and other intent instances, and the second information is used to indicate a failure to pre-occupy the first resource within the activation time period.

[0074] Optionally, the transceiver module is configured to receive fifth information from the first device. The processing module is configured to send a third request message to the first device based on the fifth information. The fifth information is configured to indicate that there is an intent conflict between the first intent instance and other intent instances, and the fifth information includes a second activation time and / or a second deactivation time; and the third request message is configured to request modification of the activation time period based on the second activation time and / or the second deactivation time.

[0075] Optionally, the transceiver module may include a sending module and a receiving module, wherein the sending module is used to implement the sending function of the communication device described in the seventh aspect, and the receiving module is used to implement the receiving function of the communication device described in the seventh aspect.

[0076] Optionally, the communication device described in the seventh aspect may further include a storage module, wherein the storage module stores a program or instruction. When the processing module executes the program or instruction, the communication device may execute the communication method described in the second aspect.

[0077] It should be noted that the communication device described in the seventh aspect can be a second device, or a chip (system) or other parts or components that can be set in the second device, or a device that includes a second device. The embodiments of the present application do not limit this.

[0078] In addition, the technical effects of the communication device described in the seventh aspect can refer to the technical effects of the communication method described in the second aspect, and will not be repeated here.

[0079] In an eighth aspect, a communication device is provided, which includes modules for executing the method described in the third aspect, for example, a transceiver module and a processing module.

[0080] The transceiver module is configured to receive a second request message from the first device. The processing module is configured to generate first information based on the second request message. The transceiver module is further configured to send the first information to the first device. The second request message is configured to request the estimated resources required to complete each of the at least one expected intent. The first information is configured to indicate the estimated first resources required to complete each of the at least one expected intent.

[0081] In one possible design, the second request message includes at least one of the following: a first intent solution, a desired list, or desired object information. The first intent solution is used to implement each of the at least one desired intent; the desired list is used to indicate the at least one desired intent; and the desired object information is used to indicate the object on which to execute the first intent instance.

[0082] Optionally, the transceiver module may include a sending module and a receiving module, wherein the sending module is used to implement the sending function of the communication device described in the eighth aspect, and the receiving module is used to implement the receiving function of the communication device described in the eighth aspect.

[0083] Optionally, the communication device described in the eighth aspect may further include a storage module, wherein the storage module stores a program or instruction. When the processing module executes the program or instruction, the communication device may execute the communication method described in the eighth aspect.

[0084] It should be noted that the communication device described in the eighth aspect can be a third device, or a chip (system) or other parts or components that can be set in a third device, or a device that includes a third device. The embodiments of the present application do not limit this.

[0085] In addition, the technical effects of the communication device described in the eighth aspect can refer to the technical effects of the communication method described in the third aspect, and will not be repeated here.

[0086] In a ninth aspect, a communication device is provided, comprising: a processor configured to execute the method described in any possible implementation of the first to third aspects.

[0087] In one possible implementation, the communication device described in the ninth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be used for the communication device described in the ninth aspect to communicate with other communication devices.

[0088] In one possible implementation, the communication device described in aspect 9 may further include a memory. The memory may be integrated with the processor or provided separately. The memory may be used to store the computer program and / or data involved in the communication method described in any possible implementation of aspects 1 to 3.

[0089] In this embodiment, the communication device described in the ninth aspect can be a first device, a second device, or a third device, or a chip (system) or other parts or components that can be set in the first device, the second device, or the third device, or a device that includes the first device, the second device, or the third device.

[0090] In addition, the technical effects of the communication device described in the ninth aspect can refer to the technical effects of the communication method described in any possible implementation method in the first to third aspects, and will not be repeated here.

[0091] In a tenth aspect, a communication device is provided. The communication device includes: a processor coupled to a memory, the processor being configured to execute a computer program stored in the memory, so that the communication device performs the communication method described in any possible implementation of the first to third aspects.

[0092] In one possible implementation, the communication device described in the tenth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be used for the communication device described in the tenth aspect to communicate with other communication devices.

[0093] In this embodiment, the communication device described in the tenth aspect can be a device (such as a first device, a second device, or a third device), or a chip (system) or other parts or components that can be set in the device, or a device that includes the device.

[0094] In addition, the technical effects of the communication device described in the tenth aspect can refer to the technical effects of the communication method described in any possible implementation method from the first aspect to the third aspect, and will not be repeated here.

[0095] In the eleventh aspect, a communication device is provided, comprising: a processor and a memory; the memory is used to store a computer program, and when the processor executes the computer program, the communication device executes the communication method described in any possible implementation method of the first to third aspects.

[0096] In one possible implementation, the communication device described in the eleventh aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be used for the communication device described in the eleventh aspect to communicate with other communication devices.

[0097] In this embodiment, the communication device described in the eleventh aspect can be a device (such as a first device, a second device, or a third device), or a chip (system) or other parts or components that can be set in the device, or a device that includes the device.

[0098] In addition, the technical effects of the communication device described in the eleventh aspect can refer to the technical effects of the communication method described in any possible implementation method of the first to third aspects, and will not be repeated here.

[0099] In the twelfth aspect, a communication device is provided, comprising: a processor; the processor is used to couple with a memory, and after reading a computer program in the memory, execute the communication method as described in any possible implementation method of the first to third aspects according to the computer program.

[0100] In one possible implementation, the communication device described in aspect 12 may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be used for the communication device described in aspect 12 to communicate with other communication devices.

[0101] In this embodiment, the communication device described in aspect 12 may be a device (such as a first device, a second device, or a third device), or a chip (system) or other parts or components that can be set in the device, or a device that includes the device.

[0102] In addition, the technical effects of the communication device described in the twelfth aspect can refer to the technical effects of the communication method described in any possible implementation method from the first aspect to the third aspect, and will not be repeated here.

[0103] In a thirteenth aspect, a communication system is provided. The communication system includes the first device described in the first aspect and / or the second device described in the second aspect. Optionally, the communication system also includes the third device described in the third aspect.

[0104] In a fourteenth aspect, a computer-readable storage medium is provided, comprising: a computer program or instructions; when the computer program or instructions are run on a computer, the computer is caused to execute the communication method described in any possible implementation method of the first to third aspects.

[0105] In a fifteenth aspect, a computer program product is provided, comprising a computer program or instructions, which, when executed on a computer, enables the computer to execute the communication method described in any one of the possible implementations of the first to third aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0106] Figure 1 is a schematic diagram of protecting services for users of different priorities;

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

[0108] FIG3 is a schematic diagram of a 3GPP architecture provided in an embodiment of the present application;

[0109] FIG4 is a schematic diagram of an O-RAN architecture provided in an embodiment of the present application;

[0110] FIG5 is a flow chart of a communication method according to an embodiment of the present application;

[0111] FIG6 is a second flow chart of the communication method provided in an embodiment of the present application;

[0112] FIG7 is a third flow chart of the communication method provided in an embodiment of the present application;

[0113] FIG8 is a first schematic diagram of modifying activation time period #1 according to an embodiment of the present application;

[0114] FIG9 is a second schematic diagram of modifying activation time period #1 according to an embodiment of the present application;

[0115] FIG10 is a third schematic diagram of modifying activation time period #1 according to an embodiment of the present application;

[0116] FIG11 is a fourth schematic diagram of modifying activation time period #1 according to an embodiment of the present application;

[0117] FIG12 is a fourth flow chart of a communication method according to an embodiment of the present application;

[0118] FIG13 is a first structural diagram of a communication device provided in an embodiment of the present application;

[0119] FIG14 is a second structural diagram of the communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0120] For ease of understanding, the technical terms involved in this embodiment are first introduced below.

[0121] 1. Intent

[0122] The current 3rd Generation Partnership Project (3GPP) Service and System Aspect Work Group 5 (SA5) defines the traditional northbound interface (itf-N) of the network management system (NMS) using a comprehensive approach to modeling network resources and managing network objects. The NMS directly adds, deletes, modifies, and queries all southbound management objects through operations such as configuration management (CM), performance management (PM), and fault management (FM). This not only raises the management and maintenance threshold for operators but also exposes the differentiated implementations of equipment vendors, making interoperability difficult.

[0123] To reduce the management complexity of network infrastructure and improve O&M efficiency in multi-vendor scenarios, 3GPP SA5 initiated research on intent-driven management services (IDMS). The key approach can be summarized as follows: the NMS, acting as an intent consumer, retains only the intent model and transmits only intent expressions on the northbound interface, thus shielding the implementation details that differ among device vendors. Intents are expressed declaratively, allowing operators to simply declare the desired effect (what) through intent expressions without having to determine how to achieve it (how), thus lowering the operational barrier to entry. Upon receiving the intent expression, the equipment management system (EMS), the intent producer, must create an intent instance based on the intent expression. Specifically, the EMS translates the intent expression into network requirements and specific actions based on the network status, and then executes them to fulfill the intent.

[0124] The following is an introduction to the concepts related to intent.

[0125] Among them, intent: expectations for the system, including requirements, goals and constraints, only describes what needs to be achieved without explaining how to achieve it.

[0126] Intent expression: An expression used to carry intent. The expression includes the intent expectation, the expected target, the expected object, and the context of the intent, intent expectation, and expected target, and has specific syntax and semantics.

[0127] Intent instance: An object that instantiates an intent. For example, in the embodiments of this application, intent can be replaced by an intent instance, which will not be described in detail later.

[0128] Intent conflict: When two intents cannot be satisfied simultaneously due to mutual exclusion, there is an intent conflict between the two intents. Intent conflicts can include one or more of syntax conflicts, operation conflicts, and effect conflicts.

[0129] A grammatical conflict may refer to a conflict between the intent expressions of two intents. For example, the intent expressions of two intents describe the same object, such as a cell or base station, and are mutually exclusive targets under the same effective conditions. For example, if the intent expression of one intent reflects the goal of increasing the cell downlink rate, and the intent expression of another intent reflects the goal of reducing the cell downlink rate, then there is a grammatical conflict between the two intents.

[0130] An operation conflict may refer to a conflict between two intents in the translated execution operation (intent operation), that is, the operations of the two intents cannot be executed at the same time. For example, the solutions corresponding to the two intents contain mutually exclusive operations on the same parameter and / or attribute of the same network element. For example, when the solution of intent #1 requires that the network configuration parameter A be increased, and the solution of intent #2 requires that the network configuration parameter A be decreased, there is an operation conflict between intent 1 and intent 2.

[0131] An effect conflict may refer to two intended operations being mutually exclusive in effect after translation.

[0132] Intent creation: Create a new intent instance in the intent system and create a corresponding intent context.

[0133] A1 interface: The interface between the non-real-time radio access network (RAN) intelligent controller (Non-RT RIC) and the near-real-time RAN intelligent controller (Near-RT RIC). It enables machine learning (ML) model management (such as ML model deployment and update), policy management, and rich information transmission.

[0134] E2 interface: The interface between the Near-RT RIC and the RAN functional network element, which enables the Near-RT RIC to control the RAN functional network element. The RAN functional network element can report performance data such as per-user equipment (Per-UE) and per-cell through the E2 interface.

[0135] E2 node: A logical node connected to the E2 interface. For new radio (NR) access, it includes the O-RAN central unit–control plane (O-CU-CP), O-RAN central unit–user plane (O-CU-UP), and O-RAN distributed unit (O-DU). For E-UTRA access, it includes the O-RAN evolved NodeB (O-eNB).

[0136] A1 policy: uses a declarative policy expression format to enable the Non-RT RIC in the service management and orchestration (SMO) framework to guide the functions in the Near-RT RIC to better implement RAN intent. The A1 policy can contain a policy type identifier (policyTypeId), a policy identifier (policyId), and a policy object (policyObject).

[0137] Among them, RAN intent can be a higher-level operational or business goal to be achieved by the radio access network, allowing operators to specify the service level agreement (SLA) that the RAN will achieve for all or a class of users in a given area over a period of time. policyTypeId can be a policy type identifier assigned by the owner of the policyType definition, consisting of a type name (TypeName) and a version (version), for example, ORAN_QoSTarget_2.0.0. policyId can be an identifier assigned by the Non-RT RIC when creating an A1 policy. policyObject can be an A1 policy representation in a lightweight data exchange (javascript object notation, JSON) format used as a payload in a policy process based on the hypertext transfer protocol (HTTP), mainly including the scope of application of the A1 policy, the target of the A1 policy, and the resources of the A1 policy.

[0138] 2. Intent consumers and intention producers.

[0139] The intent consumer is the device that manages intents. Specifically, the intent consumer can generate an intent and send an intent expression to the intent generator to carry the intent. The intent can be the intent consumer's requirement for the network where the device executing the intent solution is located. For example, the intent can reflect the intent consumer's requirement for at least one key performance indicator (KPI) in the network where the device executing the intent solution is located.

[0140] An intent producer is a device that processes intents. Specifically, after receiving an intent expression from an intent consumer, the intent producer generates multiple solutions that can satisfy the intent and selects one solution for execution. The intent producer then sends the selected solution to the device that executes the intent, which then executes it.

[0141] Intent consumers and / or intent producers may be, but are not limited to, computing devices, servers, or network devices. For example, intent consumers may be business support systems (BSS), operations support systems (OSS), NMSs, IDMS Consumers, or MnS Consumers, without limitation.

[0142] The intent producer can be NMS, EMS, IDMS Producer or MnS Producer, etc., without limitation.

[0143] It should be understood that the intended consumer and the intended producer may also adopt other names as long as they have the same function, and the embodiments of the present application do not limit this.

[0144] 3. Business assurance

[0145] Network equipment must provide differentiated services for services or users of different priorities, prioritizing the needs of high-priority services or users. For example, with the continuous advancement of mobile network technology, the quality of live streaming services has continued to improve, gradually becoming a vital way for people to obtain information, entertainment, and socialize. For operators, live streaming has also become a key source of revenue. Therefore, network equipment must prioritize the live streaming needs of high-priority services or users.

[0146] As shown in Figure 1, the network can provide differentiated quality of service (QoS) priority protection for users or services of different priorities. For example, for very very important people (VVIP), a higher QoS priority can be set than that for ordinary users. For example, VVIP users can be set to a quality of service class identifier (QCI) = 6, and ordinary users can be set to QCI = 9, so as to provide VVIP users with a good experience in a congested network, especially to meet the uplink rate and other experiences. At the same time, they can enjoy priority access to the fifth generation mobile communication technology (5G) high-speed service during busy hours, thereby providing VVIP users with better network protection.

[0147] Currently, in the 3rd Generation Partnership Project (3GPP), management service consumers (MnS Consumers) can express their requirements, goals, and constraints for services or networks by configuring intent models. When delivering service intents using the intent model, MnS Consumers can activate or deactivate the intent by configuring the intentAdminiState property. Management service producers (MnS Producers) can then synchronously execute the intent based on the received intent expression.

[0148] However, if the MnS Consumer sends a large number of service intents at the same time, intent conflicts may occur, resulting in low service stability.

[0149] For example, the network provides differentiated QoS priorities to protect user services. When there are many users to be protected, such as a large number of VVIP users, the MnS Consumer may need to simultaneously issue a large number of service intents to meet the needs of VVIP users. The MnS Producer synchronously executes the intents based on the received intent expressions. This may cause too many intents to be executed simultaneously in the system, resulting in intent conflicts. This has a significant impact on the stability of the services being protected for users, resulting in lower service stability.

[0150] In response to the above technical problems, the embodiments of the present application propose the following technical solutions to avoid conflicts of intent and improve business stability.

[0151] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0152] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as wireless fidelity (WiFi) systems, vehicle to everything (V2X) communication systems, device-to-device (D2D) communication systems, 4G, such as long-term evolution (LTE) systems, world-wide interoperability for microwave access (WiMAX) communication systems, 5G, such as new radio (NR) systems, and future communication systems.

[0153] This application will present various aspects, embodiments, or features in the context of systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Furthermore, combinations of these aspects may also be used.

[0154] Additionally, in the embodiments of this application, words such as "exemplary" and "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of the word "exemplary" is intended to present concepts in a concrete manner.

[0155] In the embodiments of the present application, "information", "signal", "message", "channel" and "signaling" can sometimes be used interchangeably. It should be noted that when the distinction between them is not emphasized, the meanings they intend to express are matched. "of", "corresponding, relevant" and "corresponding" can sometimes be used interchangeably. It should be noted that when the distinction between them is not emphasized, the meanings they intend to express are matched. In addition, the " / " mentioned in the present application can be used to represent an "or" relationship. It can be understood that in the present application, "indication" can include direct indication, indirect indication, explicit indication and implicit indication. When describing a certain indication information as being used to indicate A, it can be understood that the indication information carries A, directly indicates A, or indirectly indicates A.

[0156] In this application, the information indicated by the indication information is referred to as the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or the index of the information to be indicated, etc., or the information to be indicated can be indirectly indicated by indicating other information, wherein there is an association between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance. For example, the indication of specific information can also be achieved with the help of the arrangement order of each information agreed in advance (such as specified in the protocol), thereby reducing the indication overhead to a certain extent.

[0157] The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. The transmission period and / or transmission timing of these sub-information can be the same or different. The specific transmission method is not limited in this application. The transmission period and / or transmission timing of these sub-information can be predefined, for example, according to a protocol, or can be configured by the transmitting device through sending configuration information to the receiving device.

[0158] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0159] To facilitate understanding of the embodiments of the present application, a communication system applicable to the embodiments of the present application is first described in detail using the communication system shown in Figure 2 as an example. For example, Figure 2 is a schematic diagram of the architecture of a communication system applicable to the communication method provided in the embodiments of the present application.

[0160] As shown in Figure 2, the communication system mainly includes: a first device and a second device. Optionally, the communication system also includes a third device. It is understood that the "device" mentioned in the embodiments of the present application is only an exemplary expression, and "device" can also be replaced by any possible expression, such as "device", "module", etc., without limitation.

[0161] The communication system can be used in different communication system architectures, such as a 3GPP architecture or an open radio access network (open-RAN, O-RAN) architecture. Under different architectures, the above-mentioned first device and second device can be different devices, which are introduced below.

[0162] The above-mentioned communication system can be applied to the 3GPP architecture. FIG3 is a schematic diagram of the 3GPP architecture provided in an embodiment of the present application. As shown in FIG3 , the above-mentioned first device can be an intent producer, and the second device can be an intent consumer. The first device can be an MnS producer (Producer), and the second device can be an MnS consumer (Consumer). The MnS Consumer can send the intent to the MnS Producer by calling the intent-driven management service (intent-driven Mns) interface. The MnS Producer can translate the intent into a specific execution strategy and send it to the network infrastructure. During the execution of the intent, it continuously monitors the network status to ensure that the intent is achieved.

[0163] In this architecture, the third device can be a third-party pre-assessment system or intention pre-assessment system (not shown in Figure 3), such as a digital twin system with pre-assessment capabilities, a knowledge base, or an artificial intelligence (AI) model, without limitation. It should be understood that the third device can also call on the perception, analysis, and decision-making modules within the second device to obtain relevant data, without limitation.

[0164] The above-mentioned communication system can also be applied to the O-RAN architecture. FIG4 is a schematic diagram of the O-RAN architecture provided in an embodiment of the present application. As shown in FIG4 , the above-mentioned second device can be the intention owner, and the intention owner can be equivalent to the above-mentioned intention consumer, and has the same functions or roles as the intention consumer, without limitation. The above-mentioned first device can include a first functional entity, a second functional entity and a first application; or in other words, the combination of the first functional entity, the second functional entity and the first application can achieve the same function or role as the above-mentioned first device. Among them, the first functional entity can be a Non-RT RIC, the second functional entity can be a Near-RT RIC, and the first application can be an extended application (XAPP), such as XAPP1.

[0165] Among them, Non-RT RIC is a functional module of the operator's centralized SMO framework. Its main functions are non-real-time (control loop latency > 1s) control and optimization of RAN elements and resources, AI / ML workflows (including model training and updates), and policy-based applications / functions.

[0166] The Near-RT RIC is a component in the O-RAN architecture. Its primary function is to provide near-real-time (control loop latency >= 10ms, but < 1s) intelligent control and coordination within the RAN to support network automation and optimization. The Near-RT RIC can be deployed independently on a cloud platform or co-located with the SMO.

[0167] An XAPP is an application designed to run on a near-real-time RAN intelligent controller. It may consist of one or more microservices and is independent of the near-real-time RAN intelligent controller and can be provided by any third party. The E2 interface can support direct association between the XAP and RAN functions.

[0168] The intent owner can send an intent to the Non-RT RIC. The Non-RT RIC translates the received intent into an A1 policy and sends it to the Near-RT RIC via the A1 interface. The Near-RT RIC selects an appropriate XAPP for execution. For example, XAPP1 can convert the intent into an execution plan and send it to the E2 node via the E2 interface for execution (not shown in Figure 4). The Near-RT RIC can provide feedback on the execution results of the A1 policy to the Non-RT RIC (A1 policy feedback), and the Non-RT RIC can provide feedback on the execution results of the intent to the intent owner (intent feedback).

[0169] In this architecture, the third device can be another XAPP running on the Near-RT RIC that is different from XAPP1, such as XAPP2. XAPP2 can have pre-evaluation functions, such as services with network digital twin related functions, etc., without limitation.

[0170] It should be understood that the names of nodes, modules, devices or network elements in different scenarios or architectures or systems, as well as the names of communication interfaces between nodes, modules, devices or network elements are given as examples in the embodiments of the present application, and the possibility of name changes in future communication systems, scenarios or architectures is not excluded.

[0171] In this communication system, the first device can send second information to the second device based on the estimated first resource required to complete each of the at least one intention expectation to indicate whether the first service successfully pre-occupies the first resource within the activation time period, so that the second device can subsequently determine whether the activation time period needs to be modified. The first request message may include the activation time period of the first intention instance. When the first intention instance successfully pre-occupies the first resource within the activation time period, the first device can occupy the first resource within the activation time period, that is, when the activation time period is reached, the first device can directly occupy or use the first resource to implement the first intention instance. In this way, the pre-occupation of resources can be achieved, the intention conflict can be avoided, and the stability of the service can be improved.

[0172] It can be understood that the above Figures 2 to 4 are simplified schematic diagrams for ease of understanding, and the communication system may also include other devices, network elements, or functional entities, which are not drawn in Figures 2 to 4.

[0173] For ease of understanding, the communication method provided in the embodiment of the present application will be specifically described below with reference to Figures 5 to 12.

[0174] 5 is a flow chart of a communication method according to an embodiment of the present application. The method can be applied to the above-mentioned communication system and involves interaction between a first device, a second device, and a third device.

[0175] Specifically, as shown in FIG5 , the process of the communication method is as follows:

[0176] S501: A second device sends a first request message to a first device. Correspondingly, the first device receives the first request message from the second device.

[0177] It is understood that the first device and the second device can be applicable to the 3GPP architecture shown in Figure 3 or the O-RAN architecture shown in Figure 4. The following describes the process of the second device sending the first request message to the first device using the following two cases as examples.

[0178] Case a:

[0179] The first device and the second device may be applicable to the 3GPP architecture shown in FIG. 3 , that is, the first device may be an intent producer, and the second device may be an intent consumer.

[0180] The intent consumer sends a first request message to the intent producer. Accordingly, the intent producer receives the first request message from the intent consumer. It is understood that in this case, the intent producer can create a first intent instance and a corresponding intent context based on the first request message.

[0181] Case b:

[0182] The above-mentioned first device and second device can be applicable to the O-RAN architecture shown in Figure 4 above, that is, the first device can include a first functional entity, a second functional entity and a first application, and the second device can be the intent owner.

[0183] That is, the intent owner can send a first request message to the first functional entity. Accordingly, the first functional entity receives the first request message from the intent owner. It is understood that in this case, the first functional entity can create a first intent instance and a corresponding intent context based on the first request message. Combining the above two scenarios, the first request message is introduced below.

[0184] The first request message may be used to request creation of a first intent instance corresponding to the first service. The first intent instance includes at least one intent expectation.

[0185] The first intent instance may be an intent instance related to the first business, that is, the first business may be a business or user guaranteed by the first intent instance. Exemplarily, the first business may be a live broadcast business, a video business, etc. of user #1, without limitation. For ease of understanding, the embodiment of the present application will be described in detail using the example of the first business being the live broadcast business of user #1. It can be understood that the live broadcast business of user #1 may be a contracted business of the second device, the second device may undertake the business needs of the live broadcast business of user #1, and the first device may provide business guarantees for the live broadcast business of user #1.

[0186] In one possible design scheme, the first request message includes a first intent expression, and the first intent expression is used to request the creation of a first intent instance.

[0187] The first intention expression may include at least one intention expectation, at least one expected target, an expected object, and the context of the intention, intention expectation, and expected target, with specific syntax and semantics. The at least one intention expectation included in the first intention expression is the at least one intention expectation included in the first intention instance. It can be understood that an expression can include at least one intention expectation, and each intention expectation corresponds to at least one expected target.

[0188] At least one expected target corresponding to each intent expectation is the same as the service assurance target of the first service, or in other words, all expected targets of the first intent expression are the same as the service assurance target of the first service. For example, if the service assurance target of the first service is: uplink throughput greater than or equal to 5 megabits per second (Mb / s), uplink delay less than or equal to 10 milliseconds (ms), then at least one expected target corresponding to each intent expectation may include: uplink throughput greater than or equal to 5 Mb / s and uplink delay less than or equal to 10ms. Assume that the cell to which user #1 belongs is cell #1, or that cell #1 can provide services for user #1, then the expected object may be cell #1.

[0189] It should be understood that the business assurance target of the above-mentioned first business, or the expected target corresponding to at least one expected target, can be based on the granularity of the business on the user, that is, at the level of per user per business (per user Per business), for example, the live broadcast business of the above-mentioned user #1, at this time, the business assurance target of the first business is for the live broadcast business of user #1; the business assurance target of the above-mentioned first business, or the expected target corresponding to at least one expected target, can also be based on the granularity of the user, that is, at the level of per user (per user), for example, the above-mentioned user #1, at this time, the business assurance target of the first business is for any business on user #1, without limitation.

[0190] The first request message may include an activation time period for the first intent instance. The activation time may be determined by the second device based on the execution time period of the reservation guarantee for the live broadcast service of the contracted user, i.e., the above-mentioned user #1. It is understood that the execution time period of the reservation guarantee for the contracted user may be included in the activation time period without limitation. The activation time period may be the time interval for the activation of the first intent instance. During the activation time period, the first intent instance may be activated, or in other words, the first service may be executed.

[0191] Optionally, the activation time period may include a first activation time and a first deactivation time. When the first activation time is reached, the first intent instance may be activated, or in other words, the first service may be executed; when the first deactivation time is reached, the first intent instance may be deactivated, or in other words, the first service may be suspended. It is understood that the time interval between the first activation time and the first deactivation time is the activation time period.

[0192] It is understood that the above is a case where the second device directly sets the activation time and deactivation time of the first intent instance. The second device can also not directly set the activation time and deactivation time of the first intent instance. That is, the second device can set different intent activation policies. The following example is used to describe the specific situation.

[0193] Case 1:

[0194] Activated when an intent (or intent instance) is delivered, and deactivated manually.

[0195] The second device directly activates the intent when sending the intent, that is, the time when the second device sends the intent is the activation time of the intent. When the intent needs to be deactivated, the second device can send a delete intent request message to request deletion of the intent. At this time, the first device can deactivate the intent according to the delete intent request message, that is, the time when the second device sends the delete intent request message is the deactivation time of the intent. It should be understood that before the second device sends the delete intent request message, the first device can continue to execute the intent scheme corresponding to the intent after activating the intent.

[0196] It can be understood that in case 1, the second device may not need to configure an intent activation policy, or the intent policy configuration may be empty.

[0197] Case 2:

[0198] Activate when sending intent and set deactivation time.

[0199] The second device directly activates the intent when it sends it. That is, the time when the second device sends the intent is the activation time of the intent. The second device can set a deactivation time, and when the deactivation time is reached, the first device can deactivate the intent.

[0200] It can be understood that in case 2, the second device can configure an activation intention policy, which includes a deactivation time.

[0201] Case 3:

[0202] Set the activation time and deactivate manually.

[0203] The second device can set an activation time, and when the activation time is reached, the first device can activate the intent. When the intent needs to be deactivated, the second device can send a delete intent request message to request the deletion of the intent. At this time, the first device can deactivate the intent based on the delete intent request message. That is, the time when the second device sends the delete intent request message is the deactivation time of the intent. It should be understood that before the second device sends the delete intent request message, the first device can continue to execute the intent solution corresponding to the intent after activating the intent.

[0204] It can be understood that in case 3, the second device can configure an activation intention policy, which includes an activation time.

[0205] Case 4:

[0206] Set the activation time and deactivation time.

[0207] The second device can set an activation time, when the activation time is reached, the first device can activate the intent. The second device can set a deactivation time, when the deactivation time is reached, the first device can deactivate the intent.

[0208] It can be understood that in case 4, the second device can configure an activation intention policy, which includes an activation time and a deactivation time.

[0209] The activation time period includes a first activation time and a first deactivation time, which corresponds to situation 4. For ease of understanding, the present embodiment is described using situation 4 as an example and will not be described in detail later.

[0210] It is understood that the intentions of the above cases 1 to 4 may include the first intention instance, without limitation.

[0211] Optionally, the first request message may further include an identifier and cycle information of the first service.

[0212] The identifier can be used to identify the first service, that is, the identifier can be used to indicate that the first intent instance is an intent instance related to the first service, and the first intent instance is used to ensure the first service. For example, the identifier can be identifier #1, and identifier #1 can be used to identify the live broadcast service of user #1, etc., without limitation.

[0213] The period information can be used to indicate that the first intent instance is executed according to the scheduled period. That is, within the scheduled period, the first device can periodically execute the first intent instance during the activation time period. For example, if the scheduled period is Monday to Friday and the activation time period is 19:00-22:00, the first device can execute the first intent instance from 19:00 to 22:00 from Monday to Friday.

[0214] It is understandable that the above reservation period can be set according to actual needs and is not limited. Optionally, the first request message may further include resource reservation indication information (field) and / or pre-assessment system selection indication information (field).

[0215] Among them, the resource reservation indication information can indicate whether it is allowed to monopolize resources when executing the first intention instance. If the resource reservation indication information is the first value, it can indicate that resources need to be monopolized when executing the first intention instance, that is, the first intention instance can execute the resource pre-occupancy process (such as step S502 below) within the activation time period; if the resource reservation indication information is the second value, it can indicate that resources do not need to be monopolized when executing the first intention instance, that is, the first intention instance does not execute the resource pre-occupancy process within the activation time period. In this case, the first service can be guaranteed by a method based on QoS priority without limitation. Among them, the first value can be true (true), and the second value can be false (false), without limitation.

[0216] It can be understood that the embodiment of the present application is introduced under the condition that the resource reservation indication information has the first value, and will not be described in detail later.

[0217] The pre-assessment system selection indication information can be used to indicate the pre-assessment system to be used. It is understood that if the pre-assessment system selection indication information indicates that the pre-assessment system to be used is a third device, the first device needs to obtain the first information through the third device.

[0218] If the pre-assessment system selection indication information is empty, or the first request message does not include the pre-assessment system selection indication information, the first device may, by default, invoke internal components, such as perception, analysis, and decision-making, to perform pre-assessment to generate the aforementioned first information, without limitation. Optionally, the first request message may further include at least one of the following: a service assurance objective, application scope, or terminal / terminal group identifier of the first service.

[0219] The service assurance objectives for the first service can be described in the same manner as described above and are omitted for clarity. The application scope can correspond to the desired target, e.g., the application scope can be Cell #1. The terminal / terminal group identifier can be used to identify the terminal (i.e., the user) to which the first service belongs, or the terminals to which it belongs, without limitation. For example, Terminal #1 can indicate User #1.

[0220] It can be understood that the naming of the above-mentioned first request message is only an example, and the first request message can also be replaced with any other possible names, such as first request, request message #1, etc., without limitation.

[0221] S502: The first device sends second information to the second device based on the first information. Correspondingly, the second device receives the second information from the first device.

[0222] It is understood that before introducing the first information and the second information, the above method further includes:

[0223] The first device generates a first intent solution based on the first intent instance.

[0224] The first intention solution can be used to achieve each of the at least one intention expectation. That is, the first intention solution can be one of at least one intention solution that can achieve the expected goals of all the intention expectations of the first intention instance. That is, when the first intention solution is executed, it can achieve the expected goals of an uplink throughput greater than or equal to 5 Mb / s and an uplink latency less than or equal to 10 ms. It can be understood that the effect achieved by the first intention solution can also meet the expected effect.

[0225] The following is a detailed introduction to the process of generating the first intention solution.

[0226] Based on the above situation a, the intent producer can translate the first intent instance to obtain a first intent solution, which can represent the internal logic or command sequence that needs to be executed.

[0227] Based on the above situation b, the first application can generate multiple intent solutions based on the first intent instance forwarded by the first functional entity through the second functional entity.

[0228] Exemplarily, the first functional entity can generate an A1 policy based on the first intent instance. The A1 policy is a declarative policy expression. The A1 policy can include policyTypeId, policyId, and policyObject. The policyObject can include the scope of application of the A1 policy, the target of the A1 policy, and the resources of the A1 policy. The scope of application of the A1 policy can be the executed E2 node information. The scope of application of the A1 policy can correspond to the above-mentioned expected object information or application scope; the target of the A1 policy can correspond to the above-mentioned expected list or the business assurance target of the first business, which will not be elaborated. It can be understood that the specific introduction of the A1 policy can refer to the introduction of the above-mentioned technical terminology part, and will not be elaborated.

[0229] The first functional entity may send the A1 policy to the second functional entity, and the second functional entity may send the A1 policy to an appropriate application, such as the first application, based on the content of the A1 policy. The first application may translate the A1 policy to generate the first intent solution, which may be a control message to the E2 node.

[0230] It is understood that the first functional entity may further send at least one of the following items to the second functional entity along with the A1 policy: the activation time period, the identifier of the first service, resource reservation indication information, cycle information, pre-assessment system selection indication information, the service assurance target of the first service, the application scope, or the terminal / terminal group identifier. The second functional entity may store this information for subsequent resource pre-occupancy for the first intent instance.

[0231] In combination with the above introduction, before the first device sends the second information to the second device according to the first information, the above method may further include: the first device obtains the first information.

[0232] In which, the first information can be used to indicate the first resource required to estimate the completion of each of at least one intention expectation; or, the first information can be used to indicate the first resource required to estimate the completion of all expected goals of the first intention instance; or, the first information can be used to indicate the first resource required to estimate the completion of all business assurance goals of the first business.

[0233] The first device may call an internal service or an external service to obtain the first information. The following takes the following two methods as examples to specifically introduce the implementation process of the first device obtaining the first information.

[0234] Method 1:

[0235] The first device generates first information according to the first intention scheme.

[0236] (1) Based on the above situation a, the intent producer can generate the first information according to the first intent scheme. Exemplarily, the intent producer can perform a resource pre-assessment on the first intent scheme by calling internal services, such as perception, analysis, decision-making and other components, to evaluate the first (network) resources required to realize the first intent instance when the first intent scheme is executed, that is, to evaluate the first resources required to complete all the intended goals of the first intent instance when the first intent scheme is executed, so as to obtain the first information. It can be understood that the resources described in the embodiment of the present application may include: resource blocks (RB), transmission bandwidth, frequency band, central processing unit (CPU), image processing unit (GPU), slice resources, or memory, etc., which will not be elaborated later. The resource may include the above-mentioned first resource.

[0237] For example, taking the intention producer executing intention plan #1 as an example, the intention producer can call internal services, such as perception, analysis, decision-making and other components, to estimate the resources (recorded as resource #1) required to achieve an uplink throughput equal to 5Mb / s and an uplink delay equal to 10ms when executing intention plan #1 to generate the first information.

[0238] Method 2:

[0239] The first device sends a second request message to the third device. Correspondingly, the third device receives the second request message from the first device.

[0240] The third device generates first information according to the second request message.

[0241] The third device sends the first information to the first device. Correspondingly, the first device receives the first information returned by the third device according to the second request message.

[0242] The following is a detailed introduction.

[0243] Based on scenario a above, the third device can be a third-party pre-assessment system or intent pre-assessment system, such as a digital twin system, knowledge base, or AI model with pre-assessment capabilities, without limitation. For ease of understanding, the following description uses the intent pre-assessment system as an example of the third device.

[0244] The second request message may include at least one of the following: a first intention scheme, a desired list, or desired object information.

[0245] The first intention solution may be used to implement each intention period of the at least one intention expectation.

[0246] The expectation list can be used to indicate at least one intent expectation, or in other words, the expectation list can indicate all expectations of the first intent instance, or in other words, the expectation list can indicate all expected targets of the first intent instance. For example, the expectation list can include: uplink throughput greater than or equal to 5Mb / s, uplink delay less than or equal to 10ms. It can be understood that the expectation list can be the same as the service guarantee target of the first service mentioned above, and will not be repeated here.

[0247] The expected object information can be used to indicate the object that executes the first intention instance, which is the same as the above-mentioned application scope, such as the above-mentioned cell #1, and will not be repeated.

[0248] The second request message can be used to request the estimated resources required to complete each of at least one intention expectation, that is, the second request message can be used to request the estimated first resources required to complete all expected goals of the first intention instance.

[0249] In this case, the intention pre-assessment system can obtain relevant network configuration information and network and business indicator statistics based on the expected object information and the expected list, and perform resource pre-assessment on the first intention plan to evaluate the first resources required to realize the first intention instance when the first intention plan is executed, that is, evaluate the first resources required to complete the expected goals of all intention expectations of the first intention instance when the first intention plan is executed, so as to obtain first information and feed the first information back to the intention producer.

[0250] (2) Based on the above situation b, the first device sends a second request message to the third device, including:

[0251] The first application sends a second request message to the third device; correspondingly, the third device receives the second request message from the first application.

[0252] The first device receives the first information returned by the third device according to the second request message, including:

[0253] The second functional entity receives first information forwarded by the third device through the second functional entity.

[0254] Among them, the third device can be other applications different from the first application running on the second functional entity, such as the second application. The second application can have a pre-evaluation function or a service with network digital twin related functions.

[0255] The second request message may include at least one of the following: a first intention scheme, an A1 policy, or an application scope.

[0256] The second request message can request the estimated resources required to complete each of at least one intended expectation, that is, the second request message can be used to request the estimated first resources required to complete all expected targets of the first intention instance. In this case, the second application can obtain the first resources required to complete the uplink throughput equal to 5Mb / s and the uplink delay equal to 10ms when the first intention solution is executed based on the A1 policy and application scope to generate the first information. The second application can send the first information to the second functional entity.

[0257] It can be understood that the naming of the above second request message is only an example, and the second request message can also be replaced with any other possible names, such as second request, resource pre-assessment request, etc., without limitation.

[0258] In combination with the above introduction, in one possible design solution, before the first device sends the second information to the second device based on the first information, the method may further include:

[0259] The first device determines, based on the first information, whether there is an intent conflict between the first intent instance and other intent instances.

[0260] For example, if there is a resource that is larger than the first resource and is not pre-occupied within the activation time period, there is no intention conflict between the first intention instance and other intention instances; if there is no resource that is larger than the first resource and is not pre-occupied within the activation time period, there is an intention conflict between the first intention instance and other intention instances.

[0261] The following is a detailed introduction.

[0262] (1) Based on the above situation a, the intent producer can determine whether there is an intent conflict between the first intent instance and other intent instances within the activation time period based on the first information.

[0263] For example, the intent producer can determine whether there are resources that are larger than the first resource and not pre-occupied within the activation time period. If the intent producer determines that there are resources that are larger than the first resource and not pre-occupied within the activation time period, it can be indicated that there is no intent conflict between the first intent instance and other intent instances. That is, within the activation time period, there are still idle resources in the system that are larger than the first resource and not pre-occupied by other intent instances.

[0264] For example, if the intent producer determines that there is an idle resource not occupied by other intent instances during the activation time period, which is resource #2, and that resource #2 is greater than the above-estimated resource #1, it can be indicated that there is no intent conflict between the first intent instance and other intent instances.

[0265] If the intent producer determines that there is no resource that is larger than the first resource and has not been pre-occupied during the activation time period, it can be characterized as an intent conflict between the first intent instance and other intent instances. That is, during the activation time period, the idle resources in the system that are not pre-occupied by other intent instances are smaller than the first resource, or there are no idle resources in the system that are not pre-occupied by other intent instances, such as the idle resource is 0. For example, if the intent producer determines that the idle resource that is not occupied by other intent instances during the activation time period is resource #3, and resource #3 is smaller than the above-estimated resource #1, it can be characterized as an intent conflict between the first intent instance and other intent instances.

[0266] For example, if the second intention instance pre-occupies the fourth resource during a time period that completely overlaps with or partially overlaps with the activation time period, it can be indicated that there is an intention conflict between the first intention instance and the second intention instance.

[0267] (2) Based on the above situation b, the second functional entity can determine whether there are resources that are larger than the first resource and are not pre-occupied during the activation time period based on the first information. If the second functional entity determines that there are resources that are larger than the first resource and are not pre-occupied during the activation time period, it can be indicated that there is no intention conflict between the first intent instance and other intent instances. That is, during the activation time period, there are still idle resources in the system that are larger than the first resource and are not pre-occupied by other intent instances.

[0268] For example, the second functional entity determines that there is an idle resource not occupied by other intention instances during the activation time period, which is resource #2, and the resource #2 is greater than the above-mentioned estimated resource #1, then it can be indicated that there is no intention conflict between the first intention instance and other intention instances.

[0269] If the second functional entity determines that there is no resource that is larger than the first resource and has not been pre-occupied during the activation time period, it can be characterized as an intention conflict between the first intent instance and other intent instances. That is, during the activation time period, the idle resources in the system that are not pre-occupied by other intent instances are smaller than the first resource, or there are no idle resources in the system that are not pre-occupied by other intent instances, such as the idle resource is 0. For example, if the second functional entity determines that the idle resource that is not occupied by other intent instances during the activation time period is resource #3, and resource #3 is smaller than the above-estimated resource #1, it can be characterized as an intention conflict between the first intent instance and other intent instances.

[0270] For example, if the second intention instance pre-occupies the fourth resource in a time period that completely overlaps with or partially overlaps with the activation time period, it can be indicated that there is an intention conflict between the first intention instance and the second intention instance.

[0271] In combination with the above introduction, in a possible design solution, the above method may further include:

[0272] The first device saves the first intent scheme.

[0273] The first intention scheme may be some configuration commands, such as internal logic or command sequences that need to be executed.

[0274] It can be understood that when there is no conflict of intent between the first intent instance and other intent instances, the first device can save the first intent solution, and the first intent solution can occupy the first resource during the activation time period. When there is a conflict of intent between the first intent instance and other intent instances, the first device can also save the first intent solution so that the first device can directly occupy the first resource to execute the first intent solution during the new activation time period, without limitation.

[0275] The following is a detailed introduction.

[0276] (1) Based on the above situation a, the intention producer can save the first intention solution, and the first intention solution can occupy the first resource during the activation time period. That is, the intention producer can save the configuration command related to the first intention solution, so that after the first intention instance is activated, the intention producer can directly occupy the first resource to execute the first intention solution, such as occupying resource #1 to send the relevant configuration command to cell #1, etc., without limitation.

[0277] (2) Based on the above situation b, the first application can save the first intention solution, and the first intention solution can occupy the first resource during the activation time period. That is, the first application can save the control message to the E2 node related to the first intention solution, so that after the first intention instance is activated, the first application can directly occupy the first resource to execute the first intention solution, such as occupying resource #1 to send the control message to the E2 node to cell #1, etc., without limitation.

[0278] In combination with the above introduction, the second information can be used to indicate whether the first resource is pre-occupied successfully within the activation time period, and the second information is determined by the first information. The second information is specifically introduced below for two situations: one in which there is an intent conflict between the first intent instance and other intent instances within the activation time period, and the other in which there is no intent conflict between the first intent instance and other intent instances.

[0279] Case 5:

[0280] During the activation time period, there is no intent conflict between the first intent instance and other intent instances.

[0281] The second information may be used to indicate that the first resource is successfully pre-occupied within the activation time period.

[0282] That is, the second information can be used to characterize the intent resource management state of the first intent instance as a reserved state, to indicate that the first intent instance successfully pre-occupies the first resource within the activation time period. For ease of understanding, the embodiment of the present application can record the second information indicating the successful pre-occupancy of the first resource within the activation time period as management state #2, and will not be repeated later.

[0283] It can be understood that after the first device creates the first intent instance based on the first request message, during the process of the first device obtaining the first information and the process of the first device determining whether there is an intent conflict between the first intent instance and other intent instances, the intent resource management status of the first intent instance is in the reservation state, indicating that the first intent instance is executing the resource pre-occupation process within the activation time period. The intent resource management status can be recorded as management status #1.

[0284] At this time, when the first intention instance successfully pre-occupies the first resource within the activation time period, the intention resource management state can be changed from the booking state to the reserved state, that is, the intention resource management state can be changed from management state #1 to management state #2.

[0285] Case 6:

[0286] During the activation period, the first intent instance has an intent conflict with other intent instances.

[0287] The second information can be used to indicate a failure to pre-occupy the first resource within the activation time period. That is, the second information can be used to characterize the intent resource management state of the first intent instance as an unreserved state, to indicate that the first intent instance failed to pre-occupy the first resource within the activation time period. For ease of understanding, the embodiment of the present application can record the second information indicating a failure to pre-occupy the first resource within the activation time period as management state #3, which will not be repeated later.

[0288] At this time, when the first intention instance fails to pre-occupy the first resource within the activation time period, the intention resource management state can be changed from the booking state to the unbooked state, that is, the intention resource management state can be changed from management state #1 to management state #3.

[0289] It is understood that the naming of the first information described above is merely an example and can be replaced with any other possible name, such as resource assessment information, without limitation. The naming of the second information described above is merely an example and can be replaced with any other possible name, such as intent report, without limitation.

[0290] S503: If the first resource is pre-occupied successfully within the activation time period, the first device occupies the first resource within the activation time period.

[0291] It can be understood that step S503 is a step performed based on the above-mentioned situation 5, that is, during the activation time period, when there is no intention conflict between the first intent instance and other intent instances, the first device can occupy the first resource during the activation time period. In this way, resource pre-occupancy can be achieved before executing the intention, so as to reasonably allocate network resources and accurately deliver limited network resources to the services that need to be protected, thereby ensuring the business stability of users who need to be protected and avoiding conflicts when executing intentions.

[0292] For example, in a possible design solution, the above method may further include:

[0293] When the first activation time is reached, the first device activates the first intent instance.

[0294] The first device occupies the first resource to execute the first intention scheme.

[0295] The first device sends third information to the second device, and correspondingly, the second device receives the third information from the first device.

[0296] Among them, the third information can be used to indicate that the first resource is being occupied. That is, the third information can be used to characterize the intent resource management state of the first intent instance as being in use, to indicate that the first intent instance has been activated. For ease of understanding, the embodiment of the present application can record the third information as management state #4, and will not be repeated later.

[0297] At this time, the intended resource management state can be changed from the reserved state to the in-use state, that is, the intended resource management state can be changed from management state #2 to management state #4.

[0298] The following is a detailed introduction.

[0299] (1) Based on the above situation a, the intention producer can activate the created first intention instance when the first activation time is reached, and occupy the first resource pre-occupied in advance to execute the first intention plan. For example, the intention producer can send a corresponding control message to the expected object according to the internal logic or command sequence corresponding to the first intention production plan. The implementation process of this process can refer to the implementation process of the intention producer executing the intention plan in the prior art, and will not be repeated here.

[0300] The intent producer can also report the current intent resource management status, i.e., management status #4, to the intent consumer so that the intent consumer can obtain the intent resource management status of the first intent instance in real time.

[0301] (2) Based on the above situation b, the first application can activate the created first intention instance when the first activation time is reached, and occupy the first resource pre-occupied in advance to execute the first intention plan. The first application can execute the first intention plan. For example, the first application can send a corresponding control message to the corresponding E2 node based on the control message to the E2 node in the first intention plan. The implementation process of this process can refer to the implementation process of the extended application execution intention plan in the prior art, and will not be repeated here.

[0302] It can be understood that the second functional entity can send the current intent resource management status, i.e., management status #4 (related to A1 policy) to the first functional entity, and the first functional entity can forward the management status #4 (related to intent) to the intent owner so that the intent owner can obtain the intent resource management status of the first intent instance in real time.

[0303] In one possible design solution, the above method may further include:

[0304] When the first deactivation time is reached, the first device deactivates the first intent instance.

[0305] The first device suspends execution of the first intention scheme and releases the first resource.

[0306] The first device sends fourth information to the second device. Correspondingly, the second device receives the fourth information from the first device.

[0307] It can be understood that if the above-mentioned first intention instance is an intention instance that is executed periodically, the fourth information can be used to indicate that the first resource is successfully pre-occupied within the activation time period. That is, the fourth information can be used to characterize the intention resource management state of the first intention instance as a reserved state, to indicate that the first intention instance successfully pre-occupies the first resource within the activation time period, so that the first intention instance can continue to use the first resource within the activation time period at other times within the reserved cycle.

[0308] For ease of understanding, the embodiment of the present application can record the fourth information when the first intent instance is an intent instance during periodic execution as management state #5, which will not be repeated later. This management state #5 is the same as the above-mentioned management state #2. In this case, the intent resource management state can be changed from the in-use state to the reserved state, that is, the intent resource management state can be changed from management state #4 to management state #2 or management state #5, without limitation.

[0309] If the above-mentioned first intention instance is an intention instance of non-periodic execution, the fourth information can be used to indicate that the pre-occupancy of the first resource within the activation time period failed. That is, the fourth information can be used to characterize the intention resource management state of the first intention instance as an unreserved state, to indicate that the first intention instance failed to pre-occupy the first resource within the activation time period. For ease of understanding, the embodiment of the present application can record the fourth information when the first intention instance is an intention instance of non-periodic execution as management state #6, and will not be repeated later. The management state #6 is the same as the above-mentioned management state #3.

[0310] In this case, the intended resource management state can change from the in-use state to the unreserved state, that is, the intended resource management state can change from management state #4 to management state #3 or management state #6, without limitation.

[0311] The following is a detailed introduction.

[0312] (1) Based on the above situation a, the intent producer can deactivate the first intent instance, suspend the execution of the first intent solution, and release the occupied first resource when the first deactivation time is reached. The intent producer can also report the current intent resource management status, i.e., the above management status #5 or management status #6, to the intent consumer so that the intent consumer can obtain the intent resource management status of the first intent instance in real time.

[0313] (2) Based on the above situation b, the first application can deactivate the first intent instance, suspend the execution of the first intent solution, and release the occupied first resource when the first deactivation time is reached. The second functional entity can also send the current intent resource management state, i.e., management state #5 or management state #6 (related to the A1 policy), to the first functional entity. The first functional entity can forward the management state #5 or management state #6 (related to the intent) to the intent owner so that the intent owner can obtain the intent resource management state of the first intent instance in real time.

[0314] In summary, the first device can send second information to the second device based on the estimated first resource required to complete each of the at least one intention expectation to indicate whether the first service has successfully pre-occupied the first resource within the activation time period, so that the second device can subsequently determine whether the activation time period needs to be modified. The first request message may include the activation time period of the first intention instance. When the first intention instance successfully pre-occupies the first resource within the activation time period, the first device can occupy the first resource within the activation time period, that is, when the activation time period is reached, the first device can directly occupy or use the first resource to implement the first intention instance. In this way, the pre-occupation of resources can be achieved, the intention conflict can be avoided, and the stability of the service can be improved.

[0315] In combination with the above embodiment, in a possible design solution, when there is no intent conflict between the first intent instance and other intent instances, the above method may further include:

[0316] The second device sends the indication information to the first device. Correspondingly, the first device receives the indication information from the second device.

[0317] The first device deactivates or deletes the first intent instance according to the indication information.

[0318] The first device suspends execution of the first intention scheme and releases the first resource.

[0319] Among them, (1) if the instruction information is specifically used to instruct to delete the first intent instance, the first device can directly delete the first intent instance according to the instruction information. The details are described below.

[0320] Based on the above situation a, the intent consumer can send an instruction to the intent producer to instruct it to delete the first intent instance. The intent producer can delete the first intent instance according to the instruction, suspend the execution of the first intent solution, and release the first resource.

[0321] In this case, the intent producer can also send the sixth information to the intent consumer. The sixth information can be used to indicate that the intent resource management status of the first intent instance is empty, to indicate that the first intent instance is deleted. The sixth information can be recorded as management status #7 and will not be repeated later.

[0322] In this case, the intent resource management state can change from the in-use state to the empty state, that is, the intent resource management state can change from management state #4 to management state #7, without limitation.

[0323] It can be understood that the implementation of this process in the above-mentioned case b is similar to the implementation process of case a, which can be used as a reference for understanding and will not be elaborated on.

[0324] (2) If the indication information is specifically used to indicate that the first deactivation time is to be changed to a third deactivation time, then when the third deactivation time is reached, the first device deactivates the first intent solution, suspends execution of the first intent solution, and releases the first resource currently occupied. The third indication information may include a third deactivation time, which may be greater than or less than the first deactivation time, to achieve early or delayed deactivation of the first intent instance to meet different service requirements.

[0325] Based on the above scenario (a), the intent consumer can send an instruction to the intent producer to change the first deactivation time to the third deactivation time. The intent producer can modify the first deactivation time to the third deactivation time based on the instruction. When the third deactivation time is reached, the intent producer can deactivate the first intent instance, suspend the execution of the first intent solution, and release the occupied first resources.

[0326] In this case, the intent producer may also send a seventh message to the intent consumer.

[0327] If the above-mentioned first intention instance is an intention instance for periodic execution, the seventh information can be used to characterize the intention resource management state of the first intention instance as a reserved state, to indicate that the first intention instance successfully pre-occupies the first resource within the activation time period, so that the first intention instance can continue to use the first resource within the activation time period at other moments within the reserved cycle. For ease of understanding, the embodiment of the present application can record the seventh information when the first intention instance is an intention instance for periodic execution as management state #8, and will not be repeated later. The management state #8 is the same as the above-mentioned management state #2 or management state #5.

[0328] At this time, the intended resource management status can be changed from the in-use status to the reserved status, that is, the intended resource management status can be changed from management status #4 to management status #2, management status #5 or management status #8, without limitation.

[0329] If the above-mentioned first intention instance is an intention instance of non-periodic execution, the seventh information can be used to characterize the intention resource management state of the first intention instance as an unreserved state, to indicate that the first intention instance failed to pre-occupy the first resource within the activation time period. For ease of understanding, the embodiment of the present application can record the seventh information when the first intention instance is an intention instance of non-periodic execution as management state #9, and will not be repeated later. The management state #9 is the same as the above-mentioned management state #6.

[0330] At this time, the intended resource management state can change from the in-use state to the unreserved state, that is, the intended resource management state can change from management state #4 to management state #6 or management state #9, without limitation.

[0331] It can be understood that the implementation of this process in the above-mentioned case b is similar to the implementation process of case a, which can be used as a reference for understanding and will not be elaborated on.

[0332] In a possible design solution, when there is an intent conflict between the first intent instance and other intent instances, the above method may further include:

[0333] The first device determines a second activation time and / or a second deactivation time of the first intent instance based on the priority of the intent instance.

[0334] The intent instance includes a first intent instance.

[0335] It can be understood that each intent instance can correspond to a priority, and the business corresponding to the intent instance with a high priority has a high priority and needs to be prioritized. The first device can determine the second activation time and / or the second deactivation time of the first intent instance based on the priority of other intent instances that conflict with the first intent instance within the activation time period.

[0336] It can be understood that the specific implementation of this process can refer to the implementation process of step S708 below, and no further details are given.

[0337] Optionally, the above method may further include:

[0338] The first device sends the fifth information to the second device. Correspondingly, the second device receives the fifth information from the second device.

[0339] The second device sends a third request message to the first device according to the fifth information. Correspondingly, the first device receives the third request message from the second device.

[0340] The first device modifies the activation time period according to the second activation time and / or the second deactivation time to obtain a modified activation time period.

[0341] The first device executes the first intent scheme within the modified activation time period.

[0342] Among them, the fifth information can be used to indicate that there is an intent conflict between the first intent instance and other intent instances, that is, the first device can report the cause of the intent conflict to the second device. For example, if there is an intent conflict between the first intent instance and the second intent instance during the activation time period, the fifth information can be used to indicate that there is an intent conflict between the first intent instance and the other intent instances. The fifth information may include the second activation time and / or the second deactivation time.

[0343] The third request message is used to request modification of the activation time period according to the second activation time and / or the second deactivation time. The second device can send the third request message to the first device based on the fifth information to request the first device to modify the activation time period according to the second activation time and / or the second deactivation time. The first device can modify the activation time period according to the second activation time and / or the second deactivation time, thereby avoiding the situation where there is an intent conflict between the first intent instance and other intent instances.

[0344] The first device can execute the pre-saved first intent solution within the modified activation time period to resolve the situation where the first intent instance conflicts with other intent instances.

[0345] It can be understood that the specific implementation of this process can refer to the implementation process of the following steps S709-S712, and no further details are given.

[0346] It can be understood that the first device can also determine the second activation time and / or second deactivation time of the first intent instance based on the preemption capability of the intent instance; or, the first device can also jointly determine the second activation time and / or second deactivation time of the first intent instance based on the priority and preemption capability of the intent instance, without limitation.

[0347] It is understood that in the embodiments of the present application, "occupy" and "use" can be interchangeable, and "reservation" and "pre-occupy" can be interchangeable, without limitation. The above is a comprehensive introduction to the process of the communication method provided in the embodiments of the present application in combination with the method embodiments. For ease of understanding, the above method is described below using the following three scenarios as examples.

[0348] Scenario 1:

[0349] FIG6 is a second flow chart of the communication method provided in an embodiment of the present application, which mainly involves the interaction between the MnS Consumer (such as the second device mentioned above), the MnS Producer (such as the first device mentioned above), and the intention pre-assessment system #1 (such as the third device mentioned above).

[0350] As shown in FIG6 , the method may include:

[0351] S601, the MnS consumer obtains the contract information.

[0352] The contract information may include: the user's contracted services or contracted applications (APPs), service assurance targets, and the reserved service assurance time period corresponding to each contracted service or contracted application.

[0353] For example, the user may be user #1, and the user's contracted services or contracted applications may include: user #1's live broadcast service, video service, or voice service, etc.

[0354] The service assurance target may include the service assurance target corresponding to each contracted service or contracted application. For example, taking the live broadcast service of user #1 as an example, the service assurance target #1 of the live broadcast service may include: the uplink throughput is greater than or equal to 5Mb / s, and the uplink delay is less than or equal to 10ms.

[0355] The service guarantee period may include the service guarantee period corresponding to each contracted service or contracted application. For example, taking the live broadcast service of user #1 as an example, it is necessary to ensure that the uplink throughput of the live broadcast service is greater than or equal to 5Mb / s and the uplink delay is less than or equal to 10ms within the service guarantee period #1.

[0356] S602: MnS Consumer sends a create intent request message #1 to MnS Producer.

[0357] When user #1 has a live streaming service requirement, the MnS Consumer can determine, based on the contract information, whether user #1's live streaming service is a contracted service of the network, that is, whether it is a service that the network needs to guarantee. If the MnS Consumer determines that the contract information includes user #1's live streaming service, the MnS Consumer can determine that user #1's live streaming service is a service that the network needs to guarantee.

[0358] At this point, the MnS Consumer can send an intent creation request message #1 to the MnS Producer. This intent creation request message #1 is used to request the creation of intent instance #1 related to the live broadcast service. Intent instance #1 can include at least one intent expectation. All expected targets contained in this at least one intent expectation are the same as service assurance target #1. In other words, intent instance #1 can include: uplink throughput greater than or equal to 5 Mb / s, and uplink latency less than or equal to 10 ms.

[0359] The intent creation request message #1 may also include: service assurance target #1, application scope #1, identification of user #1 (denoted as identification #a), identification of the live broadcast service (denoted as identification #b), intent activation strategy #1 and reservation indication information #1.

[0360] Application scope #1 can be used to indicate the cell to which user #1 belongs, such as cell #1, which can provide services to user #1. Intended activation policy #1 can be used to indicate activation time period #1 of instance #1. The activation time period can include activation time #1 and deactivation time #1. It is understood that activation time period #1 is the same as the aforementioned service guarantee time period #1.

[0361] Reservation indication information #1 can be used to indicate whether exclusive use of resources is allowed when executing intention instance #1. If reservation indication information #1 is true, it can be indicated that exclusive use of resources is required when executing intention instance #1, that is, intention instance #1 can execute the resource pre-occupation process within the activation time period #1; if resource reservation indication information #1 is false, it can be indicated that exclusive use of resources is not required when executing intention instance #1, that is, intention instance #1 does not execute the resource pre-occupation process within the activation time period #1. It can be understood that the embodiment of the present application is introduced when reservation indication information #1 is true.

[0362] Optionally, the intention creation request message #1 may further include: pre-assessment system selection indication information #1 and / or period information #1.

[0363] Pre-assessment system selection indication information #1 can be used to specify the pre-assessment system to be used. For example, pre-assessment system selection indication information #1 can specify that the pre-assessment system to be used is pre-assessment system #1, etc., without limitation. It is understood that if pre-assessment system selection indication information #1 is empty, or if pre-assessment system selection indication information #1 is not included in the creation intent request message #1, the MnS Producer can default to calling internal components such as perception, analysis, and decision-making to perform pre-assessment. For ease of understanding, the subsequent description in Scenario 1 uses the example of pre-assessment system selection indication information #1 specifying that the pre-assessment system to be used is pre-assessment system #1.

[0364] Cycle information #1 can be used to indicate that the first intent instance is executed according to the scheduled cycle. For example, if the scheduled cycle is Monday to Friday and the activation time period is 19:00-22:00, then the MnS Producer can execute the first intent instance periodically from 19:00 to 22:00 from Monday to Friday, or ensure the live broadcast service.

[0365] S603, MnS Producer creates intent instance #1 and generates intent solution #1.

[0366] The MnS Producer may create an intent instance #1 according to the intent creation request message #1, and generate an intent solution #1 according to the intent instance #1.

[0367] Intent Solution #1 is one of at least one intent solution that can achieve all the desired goals of Intent Instance #1, without limitation. The MnS Producer can save Intent Solution #1, that is, the MnS Producer can save the configuration commands corresponding to Intent Solution #1. The MnS Producer can also perform an intent feasibility check. If Intent Instance #1 passes the intent feasibility check and Resource Reservation Indication #1 is True, the MnS Producer performs the resource pre-occupation process, namely, executing the following step S604.

[0368] S604: MnS Producer sends resource evaluation request #1 to pre-evaluation system #1.

[0369] Resource Assessment Request #1 may include Intent Scheme #1, Expectation List #1, and Expectation Object Information #1. Expectation List #1 may be used to indicate at least one intended expectation, or in other words, Expectation List #1 may refer to all expectations of Schematic Instance #1, or in other words, Expectation List #1 may refer to all expected targets of Schematic Instance #1. Expectation List #1 is the same as Service Assurance Target #1 described above, that is, Expectation List #1 may include: uplink throughput greater than or equal to 5 Mb / s, and uplink latency less than or equal to 10 ms.

[0370] The expected object information #1 can be used to indicate the object for executing the intention instance #1, which is the same as the application scope #1 described above. That is, the expected object information #1 can be the cell #1.

[0371] When the above-mentioned pre-assessment system selection indication information #1 specifies that the pre-assessment system to be used is the intention pre-assessment system #1, the MnS Producer can send a resource assessment request #1 to the pre-assessment system #1 to request resource pre-assessment of the intention instance #1, or in other words, to request to obtain the resources required when the estimated intention solution #1 is executed: the uplink throughput is equal to 5Mb / s and the uplink delay is equal to 10ms.

[0372] S605: Pre-assessment system #1 obtains resource #1.

[0373] Pre-assessment system #1 can obtain resources #1 required to achieve an uplink throughput of 5 Mb / s and an uplink delay of 10 ms based on expectation list #1 and expectation object information #1 through pre-execution intention solution #1.

[0374] Resource #1 may include: RB, transmission bandwidth, frequency band, CPU, GPU, slice resources, or memory, etc., without limitation.

[0375] S606: Pre-assessment system #1 sends resource assessment information #1 to MnS Producer.

[0376] Among them, resource evaluation information #1 may include resource #1.

[0377] S607, MnS Producer determines whether there is an intent conflict in intent instance #1.

[0378] The MnS Producer can calculate the percentage of resource #1 in the total network resources during activation time period #1.

[0379] If there is no resource larger than resource #1 and not pre-occupied in activation time period #1, then there is an intent conflict between intent instance #1 and other intent instances. For example, in activation time period #1, there is an intent conflict between intent instance #1 and intent instance #2. That is, in activation time period #1, intent instance #1 fails to pre-occupy resource #1, triggering MnS Producer to execute the following step S609.

[0380] If there is a resource that is larger than resource #1 and has not been pre-occupied in activation time period #1, then there is no intention conflict between intention instance #1 and other intention instances. That is, in activation time period #1, intention instance #1 successfully pre-occupies resource #1, triggering MnS Producer to execute the following step S609a1.

[0381] S608: MnS Producer sends intent report #1 to MnS Consumer.

[0382] Among them, intent report #1 can include intent resource management status #1 and failure reason #1.

[0383] Intent resource management state #1 can be an unreserved state to indicate that intent instance #1 failed to pre-occupy resource #1 within activation time period #1.

[0384] Failure reason #1 may refer to the reason why pre-occupancy of resource #1 for schematic instance #1 failed, such as insufficient resources or resources already pre-occupied within activation time period #1. This allows the MnS Consumer to subsequently modify its intent based on failure reason #1, for example, by adjusting the activation time period of intent instance #1. This is not limited to any specific reason.

[0385] MnS Producer can feedback intent report #1 to MnS Consumer through the intent report interface.

[0386] S609a1, MnS Producer pre-occupies resource #1.

[0387] The MnS Producer may pre-occupy resource #1. For example, the MnS Producer may mark that within activation time period #1, intent instance #1 needs to occupy resource #1.

[0388] S609a2, MnS Producer sends intent report #2 to MnS Consumer.

[0389] Intent Report #2 may include Intent Resource Management Status #2, which may be in the Reserved state, indicating that Intent Instance #1 successfully pre-occupies Resource #1 within Activation Time Period #1. The MnS Producer may feed back Intent Report #2 to the MnS Consumer via the Intent Reporting Interface.

[0390] S610a1, when activation time #1 is reached, the MnS Producer activates intent instance #1.

[0391] For example, when activation time #1 is reached, MnS Producer may activate intent instance #1 and occupy resource #1 to execute intent solution #1, or in other words, occupy resource #1 to send some configuration commands corresponding to intent solution #1 to cell #1.

[0392] S610a2 , the MnS Producer sends an intent report #3 to the MnS Consumer.

[0393] Intent report #3 may include intent resource management status #3. Intent resource management status #3 may be in use, indicating that instance #1 is activated. The MnS Producer may feed back intent report #3 to the MnS Consumer via the intent report interface.

[0394] S611a1 , MnS Consumer sends instruction information #1 to MnS Producer.

[0395] The following two cases are used as examples to describe the indication information #1 in detail.

[0396] Case a: Indication #1 can be a modification request message #1, requesting a modification of the deactivation time of intent instance #1. For example, it requests that deactivation time #1 be modified to deactivation time #2 to achieve earlier or later deactivation of intent instance #1. It is understood that deactivation time #2 is greater than or equal to activation time #1. This embodiment of the application does not impose any restrictions on the relationship between deactivation time #1 and deactivation time #2. For ease of understanding, the following description uses the example of deactivation time #2 being less than deactivation time #1.

[0397] Case b: Indication information #1 may be a delete intent request message #1 to request the deletion of intent instance #1.

[0398] S611a2, MnS Producer deactivates / deletes intent instance #1.

[0399] Based on the above situation a, MnS Producer can deactivate intent instance #1 after reaching deactivation time #2 according to intent request message #1. MnS Producer can suspend execution of intent solution #1 and release resource #1.

[0400] Based on the above situation b, the MnS Producer can delete the intent instance #1 and release the first resource #1 after receiving the deletion intent request message #1.

[0401] S611a3, MnS Producer sends intent report #4 to MnS Consumer.

[0402] Intent report #4 may include intent resource management status #4 and user service usage time #1. User service usage time #1 can be the time interval between the start and end times of user #1's live broadcast service. This allows MnS Consumer to better learn user #1's behavior, continuously improve the activation time period of intent instance #1, and further accurately allocate network resources.

[0403] For example, based on the above scenario a, intent resource management state #4 can be a reserved state, indicating that intent instance #1 successfully pre-occupies resource #1 within activation time period #1. It should be noted that intent instance #1 is executed periodically within the reserved period. In this case, user service usage time #1 can be the time interval between activation time #1 and deactivation time #2.

[0404] Based on the above situation b, the intention resource management state #3 can be empty to indicate that the schematic instance #1 is deleted. In this case, the user service time #1 can be the time interval between the activation time #1 and the time when the deletion intention request message #1 is issued.

[0405] MnS Producer can feed back intent report #4 to MnS Consumer through the intent report interface.

[0406] S612a1, when the deactivation time #1 is reached, the MnS Producer deactivates the intent instance #1.

[0407] For example, when activation time #1 is reached, the MnS Producer may deactivate the intent instance #1, suspend the execution of the intent solution #1, and release the resource #1.

[0408] S612a2, MnS Producer sends intent report #5 to MnS Consumer.

[0409] Among them, the intention report #5 may include the intention resource management status #5 and the user service usage time #2.

[0410] Intent resource management state #5 can be a reserved state.

[0411] The user service usage time #2 may be the time interval between the activation time #1 and the deactivation time #1.

[0412] In this way, within this 3GPP architecture, the MnS Consumer can asynchronously execute intent instances by configuring intent activation policies (i.e., activation time periods). By specifying the activation time period for each intent instance, it can prevent too many intent instances from being executed simultaneously. By configuring resource reservation instructions, the MnS Consumer can pre-occupy resources before executing an intent instance. This allows for early resource evaluation and pre-occupation, rationally allocating network resources and precisely targeting the services that require support, ensuring service stability for users and avoiding conflicts when executing intent instances.

[0413] At the same time, MnS Producer can return resource management status and user service usage time, enabling MnS Consumer to better learn user behavior and continuously improve the activation strategy of intent instances, thereby further accurately allocating network resources.

[0414] Scenario 2:

[0415] FIG7 is a flow chart of the communication method provided in an embodiment of the present application, which mainly involves the interaction between the MnS Consumer (such as the second device), the MnS Producer (such as the first device), and the intention pre-assessment system #1 (such as the third device).

[0416] As shown in FIG7 , the method may include:

[0417] S701, the MnS consumer obtains the contract information.

[0418] S702: MnS Consumer sends a create intent request message #1 to MnS Producer.

[0419] S703, MnS Producer creates intent instance #1 and generates intent solution #1.

[0420] S704: MnS Producer sends resource evaluation request #1 to pre-evaluation system #1.

[0421] S705: Pre-assessment system #1 obtains resource #1.

[0422] S706: Pre-assessment system #1 sends resource assessment information #1 to MnS Producer.

[0423] S707, MnS Producer determines whether there is an intent conflict in intent instance #1.

[0424] If there is a resource that is larger than resource #1 and has not been pre-occupied in the activation time period #1, then there is no intention conflict between intention instance #1 and other intention instances. That is, in the activation time period #1, intention instance #1 successfully pre-occupies resource #1, then the above steps S609a1-S612a2 can be executed. You can refer to it for understanding and will not elaborate on it.

[0425] If there is no resource larger than resource #1 and not pre-occupied in activation time period #1, then there is an intent conflict between intent instance #1 and other intent instances. For example, in activation time period #1, there is an intent conflict between intent instance #1 and intent instance #2. That is, in activation time period #1, intent instance #1 fails to pre-occupy resource #1, triggering MnS Producer to execute the following step S708.

[0426] S708, the MnS Producer handles the intent conflict.

[0427] MnS Producer can handle conflicts based on the priority of intent instances. For example, intent instance #1 conflicts with intent instance #2.

[0428] Assume that the activation time #1 of intent instance #1 is A and the deactivation time #1 is B; the activation time #a of intent instance #2 (corresponding to activation time period #a) is C and the deactivation time #a is D. The priority of intent instance #2 is greater than that of intent instance #1.

[0429] The following is a detailed introduction using the following situation as an example.

[0430] Case c1: As shown in (a) of Figure 8, C <A<B<D。

[0431] That is, activation period #a includes activation period #1. In this case, as shown in FIG8(b), MnS Producer may recommend deactivating intent instance #1, that is, MnS Producer may set A and B to 0 or not exist.

[0432] Case c2: As shown in (a) of Figure 9, A <C<D<B。

[0433] That is, activation time period #1 includes activation time period #a. In this case, as shown in (b) of Figure 9, MnS Producer can recommend that intent instance #1 be executed in two segments. In other words, MnS Producer can configure two activation time periods for intent instance #1, including activation time period #b1 and activation time period #b2. The activation time of activation time period #b1 is A, and the deactivation time is E, where E is greater than A and less than or equal to C; the activation time of activation time period #b2 is F, and the deactivation time is B, where F is greater than or equal to D and less than B.

[0434] Case c3: As shown in (a) of Figure 10, C <A<D<B。

[0435] That is, the activation time period #a overlaps with the activation time period #1. In this case, as shown in (b) of Figure 10, the MnS Producer can recommend changing the activation time #1 of intent instance #1 from A to G, where G is greater than or equal to D and less than B.

[0436] Case 4: As shown in Figure 11 (a), A <C<B<D。

[0437] That is, the activation time period #a overlaps with the activation time period #1. In this case, as shown in (b) of Figure 11, the MnS Producer can recommend changing the deactivation time #1 of intent instance #1 from B to H, where H is greater than A and less than or equal to C.

[0438] Based on the above four different situations, MnS Producer can recommend modifying the activation time period of intent instance #1 to prioritize the resource requirements of the high-priority intent instance #2.

[0439] S709: MnS Producer sends intent conflict report #1 to MnS Consumer.

[0440] Among them, intention conflict report #1 may include intention conflict information to indicate that there is an intention conflict between intent instance #1 and intent instance #2.

[0441] Intent conflict report #1 may also include the activation time period of intent instance #1 recommended by the MnS Producer, which will be described in detail below.

[0442] Based on the above situation c1, the activation time period of the recommended intent instance #1 can be empty, that is, the intent instance #1 is deactivated.

[0443] Based on the above situation c2, the recommended activation time periods for intent instance #1 include activation time period #b1 and activation time period #b2. Activation time period #b1 has an activation time of A and a deactivation time of E; activation time period #b2 has an activation time of F and a deactivation time of B.

[0444] Based on the above situation c3, the recommended activation time period of intention instance #1 is the time interval between D and B, that is, the recommended activation time is G, and the deactivation time #1 of intention instance #1 remains unchanged at B.

[0445] Based on the above situation c4, the recommended activation time period of intention instance #1 is the time interval between A and H, that is, the recommended deactivation time is H, and the activation time #1 of intention instance #1 remains unchanged at A.

[0446] S710, MnS Consumer evaluates the intention conflict.

[0447] The MnS Consumer can evaluate the intent conflict between Intent Instance #1 and Intent Instance #2 based on Intent Conflict Report #1 and select a conflict resolution. For example, the MnS Consumer can modify the activation time #1 and / or deactivation time #1 of Intent Instance #1 based on the activation time period recommended in Intent Conflict Report #1.

[0448] For ease of understanding, taking the above situation c3 as an example, the MnS Consumer can determine to change the activation time #1 of the intent instance #1 from A to G to resolve the situation where there is an intent conflict between the intent instance #1 and the intent instance #2 within the activation time period #1.

[0449] S711 , MnS Consumer sends a modification request message #2 to MnS Producer.

[0450] Taking the above case c3 as an example, the MnS Consumer may send a modification request message #2 to the MnS Producer to request that the activation time #1 be modified from A to G. That is, the modified activation time period #1 may be the time interval between G and B.

[0451] S712: The MnS Producer modifies the activation time period #1 according to the modification request message #2.

[0452] The MnS Producer may modify the activation time #1 from A to G according to the modification request message #1.

[0453] When activation time G is reached, MnS Producer can activate intent instance #1 and occupy resource #1 to execute intent solution #1, or in other words, occupy resource #1 to send some configuration commands corresponding to intent solution #1 to cell #1.

[0454] It can be understood that the specific implementation of this process is similar to the above steps S611a2-S611a3, which can be used as a reference for understanding and will not be described in detail.

[0455] When the deactivation time B is reached, the MnS Producer can deactivate the intent instance #1, suspend the execution of the intent solution #1, and release the resource #1. It can be understood that the specific implementation of this process is similar to the above steps S612a1-S612a2, which can be referred to for understanding and will not be repeated here.

[0456] In this way, under the 3GPP architecture, when there is an intent conflict during the synchronous execution of intent instances, the MnS Producer can modify the activation time period of the intent instance where the intent conflict occurs according to the priority of the intent instance, so that the conflict can be handled in advance to avoid conflicts when executing the intent instance.

[0457] Scenario 3:

[0458] Figure 12 is a fourth flow chart of the communication method provided in an embodiment of the present application. It mainly involves the interaction between the intention owner (such as the above-mentioned second device), the Non-RT RIC (such as the above-mentioned first functional entity), the Near-RT RIC (such as the above-mentioned second functional entity), XAPP1 (such as the above-mentioned first application) and XAPP2 (such as the above-mentioned third device). It can be understood that the Non-RT RIC, the Near-RT RIC and XAPP1 together constitute the above-mentioned first device, and XAPP1 and XAPP2 are applications running on the Near-RT RIC.

[0459] As shown in FIG12 , the method may include:

[0460] S1201, the intention owner obtains the contract information.

[0461] S1202: The intent owner sends an intent creation request message #1 to the NonRT RIC.

[0462] Among them, the intention to create request message #1 is the same as the intention to create request message #1 in the above step S602, which can be used as a reference for understanding and will not be repeated.

[0463] S1203, Non-RT RIC generates A1 strategy.

[0464] The Non-RT RIC can generate an A1 policy based on the received Create Request Message #1. The A1 policy is a declarative policy expression that can include policyTypeId, policyId, and policyObject. For details, refer to the technical terminology section above and will not be repeated here.

[0465] It is understandable that the A1 strategy and the above-mentioned intent instance #1 can be converted into each other without limitation.

[0466] S1204: The Non-RT RIC sends the A1 policy and reserved resource information to the Near-RT RIC.

[0467] The reservation resource information may include: service assurance target #1, application scope #1, identifier of user #1, identifier of live broadcast service, intention activation strategy #1 and reservation indication information #1.

[0468] Optionally, the resource reservation information may further include: pre-assessment system selection indication information #1 and / or cycle information #1. Assume that the pre-assessment system selection indication information #1 specifies that the pre-assessment system to be used is XAPP #2.

[0469] S1205: Near-RT RIC sends the A1 policy to XAPP1.

[0470] The Near-RT RIC may store the above-mentioned reserved resource information for subsequent pre-occupancy of resources required by intent instance #1. The Near-RT RIC may select a suitable XAPP, such as XAPP1, according to the content of the A1 policy and send the A1 policy to the XAPP1.

[0471] S1206, XAPP1 generates intention plan #1.

[0472] XAPP1 can translate the received A1 policy into Business Graph Solution #1. Intent Solution #1 can be a control message to node E2. It should be understood that Intent Solution #1 is one of at least one intent solution that can accomplish all the desired goals of Intent Instance #1, without limitation. XAPP1 can save Intent Solution #1. That is, the MnS Producer can save the control message to node E2 corresponding to Intent Solution #1.

[0473] S1207 , XAPP1 sends a resource evaluation request #1 to XAPP2 .

[0474] Among them, XAPP2 can be an application of a digital twin system, knowledge base or AI model with pre-evaluation function.

[0475] Resource evaluation request #1 may include: intent scenario #1, A1 policy target list, and A1 policy object information.

[0476] It can be understood that the above-mentioned policyObject can include the scope of application of the A1 policy, the target of the A1 policy and the resources of the A1 policy. The A1 policy target list is determined based on the target of the A1 policy and can include all policy targets of the A1 policy; the A1 policy object information includes the scope of application of the A1 policy, such as the A1 policy object information can be the executed E2 node information.

[0477] The A1 policy target list and the above-mentioned expectation list #1 can be converted into each other, and the scope of application of the A1 policy and the above-mentioned expected object information #1 can be converted into each other, which will not be elaborated on.

[0478] When the pre-assessment system selection indication information #1 specifies that the pre-assessment system to be used is XAPP2, the MnS Producer can send a resource assessment request #1 to XAPP2 to request pre-execution intention solution #1 to obtain the resources required to complete the uplink throughput equal to 5 Mb / s and the uplink delay equal to 10 ms.

[0479] S1208, XAPP2 obtains resource #1.

[0480] Pre-assessment system #1 can obtain resources #1 required to achieve an uplink throughput of 5 Mb / s and an uplink delay of 10 ms through pre-execution intention solution #1 based on expectation list #1 and expectation object information #1.

[0481] S1209, XAPP2 sends resource evaluation information #1 to the Near-RT RIC.

[0482] Among them, resource evaluation information #1 may include resource #1.

[0483] S1210, Near-RT RIC determines whether there is an intent conflict in intent instance #1.

[0484] Near-RT RIC can count the percentage of resource #1 in the total network resources during activation time period #1.

[0485] If there is no resource larger than resource #1 and not pre-occupied in activation time period #1, then there is an intent conflict between intent instance #1 and other intent instances. For example, in activation time period #1, there is an intent conflict between intent instance #1 and intent instance #2. That is, in activation time period #1, intent instance #1 fails to pre-occupy resource #1, triggering MnS Producer to execute the following step S1211a1.

[0486] If there is a resource that is larger than resource #1 and has not been pre-occupied in activation time period #1, then there is no intention conflict between intention instance #1 and other intention instances. That is, in activation time period #1, intention instance #1 successfully pre-occupies resource #1, triggering MnS Producer to execute the following step S1212a1.

[0487] S1211a1, the Near-RT RIC sends A1 strategy feedback information #1 to the Non-RT RIC.

[0488] The A1 policy feedback information #1 may include the A1 policy resource management status #1 and the failure reason #1.

[0489] It can be understood that the A1 policy resource management status #1 is the same as or similar to the intention report #1 in the above step S609, that is, the A1 policy resource management status #1 is the same as or similar to the intention resource management status #1 in the above intention report #1, and the failure reason #1 is the same as the failure reason #1 in the above intention report #1. You can refer to it for understanding and will not elaborate on it.

[0490] The Near-RT RIC may send A1 policy feedback information #1 to the Non-RT RIC through an A1 policy feedback interface.

[0491] S1211a2, Non-RT RIC sends intent report #1 to the intent owner.

[0492] Among them, intent report #1 can include intent resource management status #1 and failure reason #1.

[0493] Intent resource management state #1 can be an unreserved state to indicate that intent instance #1 failed to pre-occupy resource #1 within activation time period #1.

[0494] Failure reason #1 may refer to the reason why schematic instance #1 failed to pre-occupy resource #1, such as insufficient resources or resources already pre-occupied within activation time period #1. This allows the MnS Consumer to modify its intent based on failure reason #1, for example, by adjusting the activation time period of intent instance #1. This is not limited to any specific reason.

[0495] The non-RT RIC may transform the A1 policy feedback information #1 to obtain an intention report #1, and send the intention report to the intention owner.

[0496] S1212a1, Near-RT RIC pre-occupies resource #1.

[0497] Near-RT RIC can pre-occupy resource #1. For example, Near-RT RIC can mark that within activation time period #1, intent instance #1 needs to occupy resource #1.

[0498] S1212a2: The Near-RT RIC sends A1 strategy feedback information #2 to the Non-RT RIC.

[0499] Among them, A1 policy feedback information #2 may include intent resource management status #2. It is understood that A1 policy feedback information #2 is the same as or similar to the above-mentioned intent report #2. That is, A1 policy resource management status #2 is the same as or similar to the intent resource management status #2 in the above-mentioned intent report #2. You can refer to it for understanding and will not repeat it here.

[0500] The Near-RT RIC may send the A1 policy feedback information #2 to the Non-RT RIC through the A1 policy feedback interface.

[0501] S1212a3, the Non-RT RIC sends intent report #2 to the intent owner.

[0502] Among them, intent report #2 may include intent resource management status #2, and intent resource management status #2 may be a reserved state to indicate that intent instance #1 successfully pre-occupies resource #1 within activation time period #1.

[0503] The non-RT RIC may transform the A1 policy feedback information #2 to obtain an intent report #2, and send the intent report to the intent owner.

[0504] S1212a4, Near-RT RIC sends intent solution #1 and activation time period #1 to XAPP1.

[0505] It should be noted that this scenario does not limit the order of step S1212a2 and step S1212a4. For example, step S1212a2 can be executed before step S1212a4, or step S1212a2 can also be executed after step S1212a4, without limitation.

[0506] S1212a5, when activation time #1 is reached, XAPP1 activates the intent instance.

[0507] When activation time #1 is reached, XAPP1 may activate intent instance #1 and occupy resource #1 to execute intent solution #1, or in other words, occupy resource #1 to send a control message to the E2 node corresponding to intent solution #1 to cell #1.

[0508] It can be understood that after activating intent instance #1, XAPP1 can also feedback a new intent report to the intent owner, such as the above-mentioned intent report #3. Intent report #3 may include intent resource management status #3. Intent resource management status #3 may be in use to indicate that intent instance #1 has been activated. The implementation process of this process is similar to the above-mentioned step S610a2, which can be used as a reference for understanding without limitation.

[0509] It is understood that when activation time #1 is reached, XAPP1 can also deactivate intent instance #1, suspend execution of intent solution #1, and release resource #1. In this case, XAPP1 can also provide a new intent report to the intent owner, such as intent report #5. The implementation of this process is similar to step S612a2 above and can be used as a reference for understanding without limitation.

[0510] The communication method provided by this embodiment is described in detail above with reference to Figures 4 to 12. The communication device for executing the communication method provided by this embodiment is described in detail below with reference to Figures 13 and 14.

[0511] Figure 13 is a structural diagram of a communication device provided in this embodiment. As shown in Figure 13, the communication device 1300 includes a transceiver module 1301 and a processing module 1302. For ease of description, Figure 13 only shows the main components of the communication device.

[0512] The transceiver module 1301 is used to perform the transceiver function of the method shown in FIG. 5 , and the processing module 1302 is used to perform other functions of the method shown in FIG. 5 except the transceiver function.

[0513] For example, the transceiver module 1301 is used to receive a first request message from the second device, and send second information to the second device based on the first information. In the case where the first resource is successfully pre-occupied within the activation time period, the processing module 1302 is used to occupy the first resource within the activation time period. The first request message is used to request the creation of a first intention instance corresponding to the first business, the first request message includes the activation time period of the first intention instance, and the first intention instance includes at least one intention expectation; the first information is used to indicate the first resource required to estimate the completion of each of the at least one intention expectation, and the second information is used to indicate whether the first resource is successfully pre-occupied within the activation time period.

[0514] The transceiver module 1301 is used to send a first request message to the first device and receive second information from the first device. The first request message is used to request the creation of a first intent instance corresponding to the first service, the first request message includes the activation time period of the first intent instance, and the first intent instance includes at least one intent expectation; the second information is determined by the first information, the first information is used to indicate the first resource required to estimate the completion of each of the at least one intent expectation; the second information is used to indicate whether the first resource is successfully pre-occupied within the activation time period. The transceiver module 1301 is used to receive the fifth information from the first device. The processing module 1302 is used to send a third request message to the first device based on the fifth information. The fifth information is used to indicate that there is an intent conflict between the first intent instance and other intent instances, the fifth information includes the second activation time and / or the second deactivation time; the third request message is used to request to modify the activation time period based on the second activation time and / or the second deactivation time.

[0515] Optionally, the transceiver module 1301 may include a sending module (not shown in FIG13 ) and a receiving module (not shown in FIG13 ). The sending module is used to implement the sending function of the communication device 1300 , and the receiving module is used to implement the receiving function of the communication device 1300 .

[0516] Optionally, the communication device 1300 may further include a storage module (not shown in FIG13 ) storing a program or instruction. When the processing module 1302 executes the program or instruction, the communication device 1300 may perform the functions of the first device, the second device, or the third device in the above method.

[0517] It can be understood that the communication device 1300 can be a device (such as a first device, a second device, or a third device), or a chip (system) or other parts or components that can be set in the device, or a device that includes a device. The embodiments of the present application do not limit this.

[0518] In addition, the technical effects of the communication device 1300 can refer to the technical effects of the communication method shown above, and will not be repeated here.

[0519] Figure 14 is a second structural diagram of a communication device provided in this embodiment. Exemplarily, the communication device may be a terminal or a network device, or a chip (system) or other component or assembly that can be provided in a terminal or a network device. As shown in Figure 14, the communication device 1400 may include a processor 1401. Optionally, the communication device 1400 may further include a memory 1402 and / or a transceiver 1403. The processor 1401 is coupled to the memory 1402 and the transceiver 1403, for example, by a communication bus.

[0520] The following is a detailed introduction to the various components of the communication device 1400 with reference to FIG14 :

[0521] The processor 1401 is the control center of the communication device 1400 and can be a single processor or a collective term for multiple processing elements. For example, the processor 1401 can be one or more central processing units (CPUs), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the present embodiment, such as one or more digital signal processors (DSPs) or one or more field programmable gate arrays (FPGAs).

[0522] Optionally, the processor 1401 may execute various functions of the communication device 1400 , such as executing the communication method shown in FIG. 5 , by running or executing a software program stored in the memory 1402 and calling data stored in the memory 1402 .

[0523] In a specific implementation, as an embodiment, the processor 1401 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG14 .

[0524] In a specific implementation, as an embodiment, the communication device 1400 may also include multiple processors, such as the processor 1401 and the processor 1404 shown in FIG14 . Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0525] The storage 1402 is used to store the software program for executing the solution of this embodiment, and the execution is controlled by the processor 1401. The specific implementation method can refer to the above method embodiment and will not be repeated here.

[0526] Alternatively, the memory 1402 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, a random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and capable of being accessed by a computer, but not limited thereto. The memory 1402 may be integrated with the processor 1401 or may exist independently and be coupled to the processor 1401 via an interface circuit (not shown in FIG. 14 ) of the communication device 1400, which is not specifically limited in this embodiment.

[0527] Transceiver 1403 is used for communication with other communication devices. For example, if communication device 1400 is a terminal, transceiver 1403 can be used to communicate with a network device or another terminal device. For another example, if communication device 1400 is a network device, transceiver 1403 can be used to communicate with a terminal or another network device.

[0528] Optionally, the transceiver 1403 may include a receiver and a transmitter (not shown separately in FIG14 ), wherein the receiver is used to implement a receiving function, and the transmitter is used to implement a sending function.

[0529] Optionally, the transceiver 1403 may be integrated with the processor 1401 or exist independently and be coupled to the processor 1401 via an interface circuit (not shown in FIG. 14 ) of the communication device 1400 , which is not specifically limited in this embodiment.

[0530] It is understandable that the structure of the communication device 1400 shown in FIG14 does not constitute a limitation on the communication device, and an actual communication device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0531] In addition, the technical effects of the communication device 1400 can refer to the technical effects of the methods described in the above method embodiments, and will not be repeated here.

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

[0533] It should also be understood that the memory in this embodiment can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0534] The above embodiments can be implemented in whole or in part through software, hardware (such as circuits), firmware, or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the processes or functions described in this embodiment are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired method (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains a collection of one or more available media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, or tape), an optical medium (such as a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state drive.

[0535] It should be understood that the term "and / or" as used herein simply describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A alone, A and B together, or B alone. A and B can be singular or plural. Furthermore, the character " / " as used herein generally indicates an "or" relationship between the associated objects, but it may also indicate an "and / or" relationship. For specific understanding, please refer to the context.

[0536] In this embodiment, "at least one" means one or more, and "plurality" means two or more. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural.

[0537] It should be understood that in various embodiments, the size of the sequence numbers of the above 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 this embodiment.

[0538] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software 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 beyond the scope of this embodiment.

[0539] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0540] In the several embodiments provided above, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0541] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0542] In addition, each functional unit in each embodiment may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0543] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this embodiment, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method described in each embodiment. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

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

Claims

1. A communication method, characterized in that: include: The first device receives a first request message from the second device; wherein the first request message is used to request the creation of a first intent instance corresponding to the first service, the first request message includes an activation time period of the first intent instance, and the first intent instance includes at least one intent expectation; The first device sends second information to the second device according to the first information; wherein the first information is used to indicate the first resource required to be occupied for each of the at least one intended expectation, and the second information is used to indicate whether the first resource is pre-occupied successfully within the activation time period; In a case where the first resource is pre-occupied successfully within the activation time period, the first device occupies the first resource within the activation time period.

2. The method according to claim 1, characterized in that The activation time period includes a first activation time and a first deactivation time.

3. The method according to claim 1 or 2, characterized in that: The first request message includes an identifier and cycle information of the first service, wherein the identifier is used to identify the first service, and the cycle information is used to indicate that the first intent instance is to be executed according to a reserved cycle.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: The first device generates a first intention scheme according to the first intention instance; wherein the first intention scheme is used to implement each of the at least one intention expectation.

5. The method according to claim 4, characterized in that Before the first device sends the second information to the second device according to the first information, the method further includes: The first device obtains first information according to the first intention scheme.

6. The method according to claim 4, characterized in that Before the first device sends the second information to the second device according to the first information, the method further includes: The first device sends a second request message to the third device; wherein the second request message is used to request to obtain the estimated resources required to complete each of the at least one intended expectation; The first device receives the first information returned by the third device according to the second request message.

7. The method according to claim 6, characterized in that The second request message includes at least one of the following: the first intention scheme, the desired list, or the desired object information; Among them, the expectation list is used to indicate the at least one intention expectation; the expected object information is used to indicate the object that executes the first intention instance.

8. The method according to any one of claims 5 to 7, characterized in that: Before the first device sends the second information to the second device according to the first information, the method further includes: The first device determines whether there is an intent conflict between the first intent instance and other intent instances based on the first information.

9. The method according to claim 8, characterized in that The first intent instance does not have an intent conflict with other intent instances, and the method further includes: The first device saves the first intention scheme; wherein the first intention scheme occupies the first resource during the activation time period.

10. The method according to claim 9, characterized in that The second information is used to indicate that the first resource is pre-occupied successfully within the activation time period.

11. The method according to claim 9 or 10, characterized in that: The method further comprises: When the first activation time is reached, the first device activates the first intent instance; The first device occupies the first resource to execute the first intention scheme; The first device sends third information to the second device, wherein the third information is used to indicate that the first resource is being used.

12. The method according to any one of claims 9 to 11, characterized in that: The method further comprises: When the first deactivation time is reached, the first device deactivates the first intent instance; The first device suspends execution of the first intention scheme and releases the first resource; The first device sends fourth information to the second device, wherein the fourth information is used to indicate that pre-occupancy of the first resource within the activation time period is successful.

13. The method according to claim 8, characterized in that There is an intent conflict between the first intent instance and other intent instances, and the second information is used to indicate that pre-occupancy of the first resource within the activation time period failed.

14. The method according to claim 13, characterized in that The method further comprises: The first device determines a second activation time and / or a second deactivation time of the first intent instance according to a priority of the intent instance; wherein the intent instance includes the first intent instance.

15. The method according to claim 14, characterized in that The method further comprises: The first device sends fifth information to the second device; wherein the fifth information is used to indicate that there is an intent conflict between the first intent instance and other intent instances, and the fifth information includes the second activation time, and / or the second deactivation time.

16. The method according to claim 15, characterized in that The method further comprises: The first device receives a third request message from the second device; wherein the third request message is used to request to modify the activation time period according to the second activation time and / or the second deactivation time; The first device modifies the activation time period according to the second activation time and / or the second deactivation time to obtain a modified activation time period; The first device executes the first intent scheme during the modified activation time period.

17. A communication method, characterized in that: include: The second device sends a first request message to the first device; wherein the first request message is used to request the creation of a first intent instance corresponding to the first service, the first request message includes an activation time period of the first intent instance, and the first intent instance includes at least one intent expectation; The second device receives second information from the first device; wherein the second information is determined by the first information, and the first information is used to indicate the first resource required to occupy the estimated completion of each of the at least one intended expectation; the second information is used to indicate whether the first resource is pre-occupied successfully within the activation time period.

18. The method according to claim 17, characterized in that The activation time period includes a first activation time and a first deactivation time.

19. The method according to claim 17 or 18, characterized in that The first request message includes an identifier and cycle information of the first service, wherein the identifier is used to identify the first service, and the cycle information is used to indicate that the first intent instance is to be executed according to a reserved cycle.

20. The method according to any one of claims 17 to 19, characterized in that There is no intent conflict between the first intent instance and other intent instances, and the second information is used to indicate that the first resource is successfully pre-occupied within the activation time period.

21. The method according to claim 20, characterized in that The method further comprises: The second device receives third information from the first device, wherein the third information is used to indicate that the first resource is being used.

22. The method according to claim 20 or 21, characterized in that The method further comprises: The second device receives fourth information from the first device, wherein the fourth information is used to indicate that pre-occupancy of the first resource within the activation time period is successful.

23. The method according to any one of claims 17 to 19, characterized in that There is an intent conflict between the first intent instance and other intent instances, and the second information is used to indicate that pre-occupancy of the first resource within the activation time period failed.

24. The method according to claim 23, characterized in that The method further comprises: The second device receives fifth information from the first device; wherein the fifth information is used to indicate that there is an intent conflict between the first intent instance and other intent instances, and the fifth information includes the second activation time and / or the second deactivation time; The second device sends a third request message to the first device based on the fifth information; wherein the third request message is used to request to modify the activation time period based on the second activation time and / or the second deactivation time.

25. A communication method, characterized in that: include: The third device receives a second request message from the first device; wherein the second request message is used to request to obtain the estimated resources required to complete each of the at least one intended expectation; The third device generates first information according to the second request message; the first information is used to indicate a first resource estimated to be required to complete each of the at least one intended expectation; The third device sends the first information to the first device.

26. The method according to claim 25, characterized in that The second request message includes at least one of the following: a first intention scheme, a desired list, or desired object information; Among them, the first intention scheme is used to implement each of the at least one intention expectation; the expectation list is used to indicate the at least one intention expectation; and the expectation object information is used to indicate the object that executes the first intention instance.

27. A communication device, characterized in that: The apparatus comprises: a module for executing the method as claimed in any one of claims 1-26.

28. A communication device, characterized in that: The communication device comprises: a processor; when the processor executes computer instructions, the communication device executes the method according to any one of claims 1-26.

29. A computer-readable storage medium, characterized in that: The computer-readable storage medium comprises a computer program or instructions, and when the computer program or instructions are executed on a computer, the computer is caused to perform the method according to any one of claims 1 to 26.

30. A computer program product, characterized in that The computer program product comprises a computer program or instructions, and when the computer program or instructions are executed by a communication device, the method according to any one of claims 1 to 26 is executed.

Images