Communication method and device

Abstract

The invention provides a communication method and device, belongs to the technical field of communication, and is used for avoiding intention conflicts and improving service stability. In the method, a first device can send second information to a second device according to a pre-estimated first resource required to be occupied by each intention expectation in at least one intention expectation, so as to indicate whether a first service successfully pre-occupies the first resource within an activation time period; for a subsequent second device may determine whether the activation time period needs to be modified. When the first intention instance successfully pre-occupies the first resource in the activation time period, the first device can occupy the first resource in 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 realize the first intention instance, so that pre-occupation of the resource can be realized, and the resource utilization rate is improved. The situation of intention conflict is avoided, and the service stability can be improved.

Description

Technical Field

[0001] This application relates to the field of communications, and in particular, to a communication method and apparatus. Background Art

[0002] In the current 3rd generation partnership project (3GPP), a management service consumer (MnS Consumer) can express requirements, goals, and constraints for services or networks through a configuration intent model. When the MnS Consumer issues a service intent through the intent model, it can activate or deactivate the intent by configuring the intent administrative state (intentAdminiState). The management service producer (MnS producer) can synchronously execute the intent according to the received intent expression.

[0003] However, if the number of service intents simultaneously issued by the MnS Consumer is large, intent conflicts may occur, resulting in low service stability. Summary of the Invention

[0004] Embodiments of this application provide a communication method and apparatus to avoid intent conflicts and improve service stability.

[0005] To achieve the above objective, this application adopts the following technical solutions:

[0006] In a first aspect, a communication method is provided. This method can be executed by a first device, or by a chip or circuit configured in the first device, or by a logical module or software capable of implementing all or part of the functions of the first device. The method includes: The first device receives a first request message from a second device, sends second information to the second device according to first information, and occupies a first resource within an activation time period when the preoccupation of the first resource within the activation time period is successful. The first request message is used to request the creation of a first intent instance corresponding to a first service. The first request message includes the activation time period of the first intent instance. The first intent instance includes at least one intent expectation. The first information is used to indicate the first resource estimated to be occupied to complete each of the at least one intent expectation. The second information is used to indicate whether the preoccupation of the first resource within the activation time period is successful.

[0007] Based on the method described in the first aspect, the first device can send the second information to the second device according to the first resources estimated to be occupied for each intention expectation in at least one intention expectation, to indicate whether the first service successfully pre-occupies the first resources during the activation period, so that the second device can determine whether it is necessary to modify the activation period subsequently. The first request message may include the activation period of the first intention instance. When the first intention instance successfully pre-occupies the first resources during the activation period, the first device can occupy the first resources during the activation period. That is, when the activation period arrives, the first device can directly occupy or use the first resources to implement the first intention instance. In this way, pre-occupation of resources can be achieved, the situation of intention conflicts can be avoided, and the stability of the service can be improved.

[0008] In a possible design, the activation period includes a first activation time and a first deactivation time, so that the first device can determine the time to activate the first intention instance and the time to deactivate the first intention instance. It can be understood that if the activation period does not include the first deactivation time, the first device can occupy the first resources all the time after activating the first intention instance until the second device issues the deactivation time or reconfigures the activation period, etc., which is not limited.

[0009] Optionally, the first request message includes the 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 intention instance is executed according to the reserved cycle. In this way, the first device can determine the intention instance related to the first service that needs to be created according to the identifier; the first device can occupy the first resources within the activation time according to the cycle information during the reserved cycle, so as to avoid the first device needing to re-pre-occupy resources each time and save overhead.

[0010] In a possible design, the method described in the first aspect further includes: the first device generates a first intention plan according to the first intention instance. The first intention plan is used to implement each intention expectation in at least one intention expectation. That is, the first intention plan can be one of the intention plans that can meet all the expected goals of the first intention instance, which is not limited. The first device can use the first resources to execute the first intention plan during the activation period to implement the first intention instance. In a possible design, before the first device sends the second information to the second device according to the first information, the method described in the first aspect further includes: the first device obtains the first information according to the first intention plan. That is, the first device can directly obtain the first information by calling internal services, such as components for perception, analysis, decision-making, etc., to pre-execute the first intention plan, so as to save signaling overhead.

[0011] In a possible design solution, before the first device sends the second information to the second device according to the first information, the method described in the first aspect further includes: the first device sends a second request message to a third device and receives the first information returned by the third device according to the second request message. Wherein, the second request message is used to request to obtain the resources required to estimate the completion of each of at least one intention expectation. That is, the first device sends a second request message to the third device, a third party, to request the third device to generate the first information and receives the first information returned by the third device after pre-executing the first intention plan. The third device may 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.

[0012] Optionally, the second request message includes at least one of the following: the first intention plan, the expectation list, and / or the expected object information. Wherein, the expectation list is used to indicate at least one intention expectation; the expected object information is used to indicate the object for executing the first intention instance. In this way, the third device can estimate the first resources required to complete each of at least one intention expectation after the first intention plan is executed according to the expected object information, so as to obtain the first information.

[0013] In a possible design solution, before the first device sends the second information to the second device according to the first information, the method described in the first aspect further includes: the first device determines whether there is an intention conflict between the first intention instance and other intention instances according to the first information. For example, if there are resources greater than the first resources and not pre-occupied during the activation period, there is no intention conflict between the first intention instance and other intention instances; if there are no resources greater than the first resources and not pre-occupied during the activation period, there is an intention conflict between the first intention instance and other intention instances. In this way, the first device can determine whether the first intention instance of the device successfully reserves the first resources, so that the first device can reasonably allocate network resources according to the situation of intention conflicts in the subsequent process. For example, it preferentially guarantees the resource allocation of high-priority services to ensure the stability of high-priority services.

[0014] In a possible design solution, when there is no intention conflict between the first intention instance and other intention instances, the method described in the first aspect further includes: the first device saves the first intention plan. Wherein, the first intention plan occupies the first resources during the activation period. It can be understood that the first intention plan may be some configuration commands. The first device can first save this part of the configuration commands in advance. 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 preferentially guarantee the stability of the first service.

[0015] Optionally, the second information is used to indicate that the reservation of the first resource is successful during the activation period. In this way, the second device can determine that the first intent instance or the first service has successfully reserved the resource. Or rather, the second device can determine that the first service can be normally executed during the activation period.

[0016] Optionally, the method described in the first aspect further includes: when the first activation time arrives, the first device activates the first intent instance; the first device occupies the first resource to execute the first intent plan, and sends the 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 arrives, the first device can activate the first intent instance, directly use the pre-occupied first resource to execute the first intent plan, and feedback to the second device that the first resource is being used. In this way, the second device can determine that the first intent instance has been activated.

[0017] Optionally, the method described in the first aspect further includes: when the first deactivation time arrives, the first device deactivates the first intent instance; the first device pauses executing the first intent plan and releases the first resource; the first device sends the fourth information to the second device. The fourth information is used to indicate that the reservation of the first resource is successful during the activation period. That is, when the first deactivation time arrives, the first device needs to release the first resource to ensure the resource requirements of other services. The first device feedbacks to the second device that the reservation of the first resource is successful during the activation period. In this way, the second device can determine that the first intent instance or the first service has periodically reserved the first resource, so as to avoid the first device needing to re-reserve the resource each time and save the overhead.

[0018] In a possible design, the method described in the first aspect further includes: the first device receives the indication information from the second device, and deactivates or deletes the first intent instance according to the indication information. The first device pauses executing the first intent plan and releases the first resource. The indication information is used to indicate deactivating or deleting the first intent instance. In this way, the second device can deactivate the first intent instance in advance or delay it to meet different service requirements.

[0019] Wherein, the indication information is specifically used to indicate deleting 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.

[0020] 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 further includes: when the third deactivation time is reached, the first device deactivates the first intent scheme, suspends the execution of the first intent scheme, and releases the first resource being occupied. That is, the second device can advance or delay the deactivation of the first intent 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 intent instance is an intent instance that is executed periodically, the sixth information can indicate that the current intent resource management status is the successfully reserved status; if the first intent instance is an intent instance that is not executed periodically, the sixth information can indicate that the current intent resource management status is the unreserved status.

[0021] In a possible design solution, there is an intent conflict between the first intent instance and other intent instances, and the second information is used to indicate that the preoccupation of the first resource fails during the activation time period. In this way, the second device can determine that the first intent instance or the first service fails to reserve resources during the activation time period, which can be used for the second device to determine to modify the activation time period subsequently to resolve the situation where there is an intent conflict between the first intent instance and other intent instances, and the stability of the first service can be improved.

[0022] Optionally, before the first device sends the second information to the second device according to the first information, the method described in the first aspect further includes: the first device determines the second activation time and / or the second deactivation time of the first intent instance according to the priority of the intent instance. Among them, the intent instance includes the first intent 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 according to the priority of other intent instances conflicting with the first intent instance, for the second device to determine to modify the activation time period subsequently. For example, optionally, the method described in the first aspect further includes: the first device sends the fifth information to the second device. Among them, 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.

[0023] Optionally, the method described in the first aspect further 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 intent scenario 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 according to the third request message, and instructs the first device to execute the first intent scenario within the modified activation time period to solve the problem of intent conflict between the first intent instance and other intent instances, which can improve the stability of the first service.

[0024] In a possible design solution, the first device is an intent producer, and the second device is an intent consumer. That is, the above-mentioned first device and second device can be applied to the 3GPP architecture, so as to meet the requirements in different scenarios.

[0025] In a possible design solution, 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 can achieve the same function or role as the above-mentioned first device; the second device is an intent owner. It can be 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. That is, the above-mentioned first device and second device can be applied to the O-RAN architecture, so as to meet the requirements in different scenarios.

[0026] In the second aspect, a communication method is provided. This method can be executed by the second device, or, alternatively, by a chip or circuit configured in the second device, or, further, by a logic module or software that can implement 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 to create 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, and the first information is used to indicate the first resources required to estimate the completion of each of the at least one intent expectation; the second information is used to indicate whether the first resources are successfully preoccupied within the activation time period.

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

[0028] Optionally, the first request message includes an identifier of the first service and period information. The identifier is used to identify the first service, and the period information is used to indicate that the first intent instance is executed according to the reserved period.

[0029] In a possible design, 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 is successful within the activation time period.

[0030] Optionally, the method described in the second aspect further includes: the second device receives third information from the first device. The third information is used to indicate that the first resource is being used.

[0031] Optionally, the method described in the second aspect further includes: the second device receives fourth information from the first device. The fourth information is used to indicate that the pre - occupation of the first resource is successful within the activation time period.

[0032] In a possible design, there is an intent conflict between the first intent instance and other intent instances, and the second information is used to indicate that the pre - occupation of the first resource fails within the activation time period.

[0033] Optionally, the method described in the second aspect further includes: the second device receives fifth information from the first device, and according to the fifth information, sends a third request message to the first device. 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 a second activation time and / or a second de - activation time; the third request message is used to request to modify the activation time period according to the second activation time and / or the second de - activation time.

[0034] In a possible design, the first device is an intent producer, and the second device is an intent consumer.

[0035] In a possible design, 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 an intent owner.

[0036] In addition, for the related technical effects of the method described in the second aspect, reference can also be made to the relevant introduction of the method described in the first aspect, which will not be elaborated here.

[0037] In a third aspect, a communication method is provided. This method 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 implement 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 according to the second request message, and sends the first information to the first device. Among them, the second request message is used to request to obtain the resources required to estimate the completion of each of at least one intention expectation; the first information is used to indicate the first resources required to estimate the completion of each of at least one intention expectation.

[0038] In a possible design, the second request message includes at least one of the following: a first intention scheme, an expectation list, or expectation object information. Among them, the first intention scheme is used to implement each of at least one intention expectation; 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.

[0039] For the related technical effects of the method described in the third aspect, reference can also be made to the relevant introduction of the method described in the first aspect, which will not be elaborated here.

[0040] In a fourth aspect, a communication method is provided. The method includes: The first device executes the method described in the first aspect, and the second device executes the method described in the second aspect.

[0041] In addition, for the technical effects of the method described in the fourth aspect, reference can also be made to the technical effects of the methods described in the first aspect to the second aspect, which will not be elaborated here.

[0042] In a fifth aspect, a communication method is provided. The method includes: The first device executes the method described in the first aspect, the second device executes the method described in the second aspect, and the third device executes the method described in the third aspect.

[0043] In addition, for the technical effects of the method described in the fifth aspect, reference can also be made to the technical effects of the methods described in the first aspect to the third aspect, which will not be elaborated here.

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

[0045] Among them, the transceiver module is used to receive a first request message from a second device and send second information to the second device according to first information. In the case of successfully pre-occupying a first resource within an 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 intent instance corresponding to a 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 first information is used to indicate the first resources estimated to be occupied for completing each of the at least one intent expectations, and the second information is used to indicate whether the first resource is successfully pre-occupied within the activation time period.

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

[0047] Optionally, the first request message includes an identifier of the first service and cycle information. Among them, the identifier is used to identify the first service, and the cycle information is used to indicate the execution of the first intent instance according to a reserved cycle.

[0048] In a possible design, the processing module is further used to generate a first intent plan according to the first intent instance. Among them, the first intent plan is used to implement each of the at least one intent expectations.

[0049] In a possible design, before the first device sends the second information to the second device according to the first information, the processing module is further used to obtain the first information according to the first intent plan.

[0050] In a possible design, before the first device sends the second information to the second device according to the first information, the transceiver module is further used to send a second request message to a third device and receive the first information returned by the third device according to the second request message. Among them, the second request message is used to request to obtain the resources estimated to be occupied for completing each of the at least one intent expectations.

[0051] Optionally, the second request message includes at least one of the following: a first intent plan, an expectation list, or expectation object information. Among them, the expectation list is used to indicate at least one intent expectation; the expectation object information is used to indicate the object for executing the first intent instance.

[0052] In a possible design, before the first device sends the second information to the second device according to the first information, the processing module is further used to determine whether there is an intent conflict between the first intent instance and other intent instances according to the first information.

[0053] In a possible design solution, there is no intention conflict between the first intention instance and other intention instances. The processing module is further configured to save the first intention solution. The first intention solution occupies the first resource during the activation time period.

[0054] Optionally, the second information is used to indicate that the pre - occupation of the first resource during the activation time period is successful.

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

[0056] Optionally, when the first de - activation time is reached, the processing module is further configured to de - activate the first intention instance. The processing module is further configured to pause the execution of the first intention solution and release the first resource. The transceiver module is further configured to send the fourth information to the second device. The fourth information is used to indicate that the pre - occupation of the first resource during the activation time period is successful.

[0057] In a possible design solution, there is an intention conflict between the first intention instance and other intention instances. The second information is used to indicate that the pre - occupation of the first resource during the activation time period fails.

[0058] Optionally, before the first device sends the second information to the second device according to the first information, the processing module is further configured to determine the second activation time and / or the second de - activation time of the first intention instance according to the priority of the intention instances. The intention instances include the first intention instance.

[0059] 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 according to the second activation time and / or the second de - activation time to obtain a modified activation time period, and execute the first intention solution 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 de - activation time.

[0060] Optionally, the transceiver module may include a sending module and a receiving module. 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.

[0061] Optionally, the communication device described in the sixth aspect may further include a storage module that stores programs or instructions. When the processing module executes the programs or instructions, the communication device can execute the communication method described in the first aspect.

[0062] It should be noted that the communication device described in the sixth aspect may be the first device, or a chip (system) or other component or assembly that can be disposed in the first device, or a device including the first device. The embodiments of the present application do not limit this.

[0063] In addition, the technical effects of the communication device described in the sixth aspect may refer to the technical effects of the communication method described in the first aspect, which will not be elaborated here.

[0064] In a seventh aspect, a communication device is provided. The device includes modules for performing the method described in the second aspect above. For example, a transceiver module and a processing module.

[0065] Among them, the transceiver module 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 a 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 information is determined by the first information, and the first information is used to indicate the first resources required to estimate the completion of each of the at least one intent expectation; the second information is used to indicate whether the first resources are successfully preoccupied within the activation time period.

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

[0067] Optionally, the first request message includes an identifier of the first service and cycle information. The identifier is used to identify the first service, and the cycle information is used to indicate the execution of the first intent instance according to a reserved cycle.

[0068] In a possible design, 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 resources are successfully preoccupied within the activation time period.

[0069] Optionally, the transceiver module is further used to receive third information from the first device. The third information is used to indicate that the first resources are being used.

[0070] Optionally, when the first deactivation time is reached, the transceiver module is further used to receive fourth information from the first device. The fourth information is used to indicate that the first resources are successfully preoccupied within the activation time period.

[0071] In a possible design, there is an intent conflict between the first intent instance and other intent instances, and the second information is used to indicate that the first resources are preoccupied unsuccessfully within the activation time period.

[0072] Optionally, a transceiver module is configured to receive fifth information from a first device. A processing module is configured to send a third request message to the first device according to the fifth information. The fifth information is used to indicate that there is an intention conflict between a first intention instance and other intention instances, and the fifth information includes a second activation time and / or a second deactivation time; the third request message is used to request to modify an activation time period according to the second activation time and / or the second deactivation time.

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

[0074] Optionally, the communication device described in the seventh aspect may further include a storage module that stores programs or instructions. When the processing module executes the programs or instructions, the communication device can execute the communication method described in the second aspect.

[0075] It should be noted that the communication device described in the seventh aspect may be a second device, or a chip (system) or other component or assembly that can be disposed in the second device, or a device including the second device. The embodiments of the present application do not make any limitations in this regard.

[0076] 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 elaborated here.

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

[0078] Among them, the transceiver module is configured to receive a second request message from a first device. The processing module is configured to generate first information according to the second request message. The transceiver module is further configured to send the first information to the first device. The second request message is used to request to obtain the resources required to estimate the completion of each intention expectation in at least one intention expectation, and the first information is used to indicate the first resources required to estimate the completion of each intention expectation in at least one intention expectation.

[0079] In a possible design, the second request message includes at least one of the following: a first intention plan, an expectation list, or expectation object information. The first intention plan is used to implement each intention expectation in at least one intention expectation; the expectation list is used to indicate at least one intention expectation; the expectation object information is used to indicate an object for executing a first intention instance.

[0080] Optionally, the transceiver module may include a transmitting module and a receiving module. Among them, the transmitting module is used to implement the transmitting 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.

[0081] Optionally, the communication device described in the eighth aspect may further include a storage module, which stores programs or instructions. When the processing module executes the programs or instructions, the communication device can execute the communication method described in the eighth aspect.

[0082] It should be noted that the communication device described in the eighth aspect may be a third device, or a chip (system) or other components or assemblies that can be set in the third device, or a device including the third device. The embodiments of the present application do not make any limitations in this regard.

[0083] 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 elaborated here.

[0084] In a ninth aspect, a communication device is provided. The communication device includes: a processor, which is used to execute the method described in any possible implementation manner of the first aspect to the third aspect.

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

[0086] In a possible implementation, the communication device described in the ninth aspect may further include a memory. The memory may be integrated with the processor or may be separately provided. The memory may be used to store the computer programs and / or data involved in the communication method described in any possible implementation manner of the first aspect to the third aspect.

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

[0088] 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 manner of the first aspect to the third aspect, and will not be elaborated here.

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

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

[0091] In this embodiment, the communication device described in the tenth aspect may be a device (such as a first device, a second device, or a third device), or a chip (system) or other component or assembly that can be disposed in the device, or a device including the device.

[0092] In addition, the technical effects of the communication device described in the tenth aspect may refer to the technical effects of the communication method described in any one of the possible implementations of the first aspect to the third aspect, which will not be elaborated here.

[0093] In an eleventh aspect, a communication device is provided, including: a processor and a memory; the memory is configured to store a computer program, and when the processor executes the computer program, the communication device is caused to perform the communication method described in any one of the possible implementations of the first aspect to the third aspect.

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

[0095] In this embodiment, the communication device described in the eleventh aspect may be a device (such as a first device, a second device, or a third device), or a chip (system) or other component or assembly that can be disposed in the device, or a device including the device.

[0096] In addition, the technical effects of the communication device described in the eleventh aspect may refer to the technical effects of the communication method described in any one of the possible implementations of the first aspect to the third aspect, which will not be elaborated here.

[0097] In a twelfth aspect, a communication device is provided, including: a processor; the processor is configured to be coupled to a memory, and after reading a computer program in the memory, execute the communication method described in any one of the possible implementations of the first aspect to the third aspect according to the computer program.

[0098] In a possible implementation, the communication device described in the twelfth 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 twelfth aspect to communicate with other communication devices.

[0099] In this embodiment, the communication device described in the twelfth aspect may be a device (such as a first device, a second device, or a third device), or a chip (system) or other component or assembly that can be disposed in the device, or a device including the device.

[0100] In addition, the technical effects of the communication device described in the twelfth aspect may refer to the technical effects of the communication method described in any one of the possible implementation manners of the first aspect to the third aspect, which will not be elaborated here.

[0101] 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 further includes the third device described in the third aspect.

[0102] In a fourteenth aspect, a computer-readable storage medium is provided, including: a computer program or instruction; when the computer program or instruction runs on a computer, the computer is caused to execute the communication method described in any one of the possible implementation manners of the first aspect to the third aspect.

[0103] In a fifteenth aspect, a computer program product is provided, including a computer program or instruction, and when the computer program or instruction runs on a computer, the computer is caused to execute the communication method described in any one of the possible implementation manners of the first aspect to the third aspect. Description of the Drawings

[0104] Figure 1 Schematic diagram for ensuring user services with different priorities;

[0105] Figure 2 Schematic diagram of the architecture of the communication system provided in the embodiment of the present application;

[0106] Figure 3 Schematic diagram of the 3GPP architecture provided in the embodiment of the present application;

[0107] Figure 4 Schematic diagram of the O-RAN architecture provided in the embodiment of the present application;

[0108] Figure 5 Schematic flow of the communication method provided in the embodiment of the present application Figure 1 ;

[0109] Figure 6 Schematic flow of the communication method provided in the embodiment of the present application Figure 2 ;

[0110] Figure 7 Schematic flow of the communication method provided by the embodiment of the present application Figure 3 ;

[0111] Figure 8 Schematic diagram of modifying activation time period #1 provided by the embodiment of the present application Figure 1 ;

[0112] Figure 9 Schematic diagram of modifying activation time period #1 provided by the embodiment of the present application Figure 2 ;

[0113] Figure 10 Schematic diagram of modifying activation time period #1 provided by the embodiment of the present application Figure 3 ;

[0114] Figure 11 Schematic diagram of modifying activation time period #1 provided by the embodiment of the present application Figure 4 ;

[0115] Figure 12 Schematic flow of the communication method provided by the embodiment of the present application Figure 4 ;

[0116] Figure 13 Schematic structure of the communication device provided by the embodiment of the present application Figure 1 ;

[0117] Figure 14 Schematic structure of the communication device provided by the embodiment of the present application Figure 2 。 Detailed implementation manners

[0118] For easy understanding, the technical terms involved in this embodiment are introduced first below.

[0119] 1. Intent

[0120] Currently, the 3rd generation partnership project (3GPP) Service and System Aspect Work Group 5 (SA5) adopts the method of full-scale modeling of network resources and full-scale management of network objects in the definition of the traditional northbound interface (itf-N) of the network management system (NMS). The NMS directly performs operations such as addition, deletion, modification, and query on all its southbound management objects through operations of types such as configuration management (CM), performance management (PM), and fault management (FM). This not only increases the management and operation and maintenance thresholds for operators but also exposes the differentiated implementations of equipment manufacturers, making it difficult to achieve interoperability between different manufacturers.

[0121] To reduce the management complexity of network infrastructure and improve the operation and maintenance efficiency in a multi-vendor scenario, 3GPP SA5 launched the research on intent-driven management service (IDMS). The main solution ideas can be summarized as follows: The NMS acts as an intent consumer, where only the intent model is retained, and only intent expressions are transmitted on the northbound interface, thus shielding the differentiated details in the implementations of equipment manufacturers. Among them, the intent is expressed declaratively. Operation and maintenance personnel only need to declare what effects to achieve (what) through the intent expression, without having to determine how to achieve it (how), which helps to reduce the operation and maintenance threshold. When the intent producer, that is, the equipment management system (EMS), receives the intent expression, it needs to create an intent instance according to the intent expression. Specifically, the EMS can translate the intent expression into requirements for the network and specific execution operations based on the network status and execute them to achieve the intent.

[0122] The following introduces the related concepts of intent.

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

[0124] Intent expression: An expression used to carry the intent. The expression includes intent expectations, expected goals, expected objects, and the context of the intent, intent expectations, and expected goals, and has specific syntax and semantics.

[0125] Intention instance: An object after instantiating an intention. For example, in the embodiments of the present application, the intention can be replaced by an intention instance, which will not be elaborated hereinafter.

[0126] Intention conflict: When two intentions cannot be satisfied simultaneously due to mutual exclusion, there is an intention conflict between these two intentions. An intention conflict can include one or more of a syntax conflict, an operation conflict, and an effect conflict.

[0127] Among them, the syntax conflict may refer to a conflict in the intention expressions of two intentions. For example, the intention expressions of two intentions describe the same object, such as a cell, a base station, etc., with mutually exclusive goals under the same effective conditions. Exemplarily, if the goal reflected by the intention expression of one intention is to increase the downlink rate of the cell, and the goal reflected by the intention expression of another intention is to decrease the downlink rate of the cell, then there is a syntax conflict between these two intentions.

[0128] The operation conflict may refer to a conflict in the executed operations (intent operations) after translation of two intentions, that is, the operations of the two intentions cannot be executed simultaneously. For example, the solutions corresponding to the two intentions respectively include mutually exclusive operations on the same parameter and / or attribute of the same network element. Exemplarily, when the solution of intention #1 requires increasing the network configuration parameter A, and the solution of intention #2 requires decreasing the network configuration parameter A, there is an operation conflict between them. Figure 1 And Figure 2 between them.

[0129] The effect conflict may refer to the mutual exclusion of the effects of the executed operations after translation of two intentions.

[0130] Intention creation: Create a new intention instance in the intention system and create a corresponding intention context.

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

[0132] 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, and the RAN functional network element can report performance data through the E2 interface, such as per-user equipment (Per-UE), per-cell, etc.

[0133] E2 node: A logical node connected to the E2 interface. For new radio (NR) access, it is the Open RAN Central Unit Control Plane (O-CU-CP), Open RAN Central Unit User Plane (O-CU-UP), and Open RAN Distributed Unit (O-DU), etc. For E-UTRA access, it is the Open RAN Evolved NodeB (O-eNB).

[0134] A1 policy: Using a declarative policy expression form, enabling the Non-RT RIC in the service management and orchestration (SMO) framework to guide the functions in the Near-RT RIC to better achieve RAN intentions. The A1 policy can include a policy type identifier (policyTypeId), a policy identifier (policyId), and a policy object (policyObject).

[0135] Among them, the RAN intention can be a higher-level operation or service objective to be achieved by the radio access network, allowing the operator to specify the service level agreement (SLA) that the RAN should achieve for all or a category of users in a given area within a period of time. The policyTypeId can be a policy type identifier assigned by the owner who defines the policyType, including two parts: the type name (TypeName) and the version. For example, ORAN_QoSTarget_2.0.0. The policyId can be an identifier assigned by the Non-RT RIC when creating the A1 policy. The policyObject can be a lightweight data exchange (JavaScript object notation, JSON) format representation of the A1 policy used as the payload in the policy process based on the hyperText transfer protocol (HTTP), mainly including the scope to which the A1 policy is applied, the objective of the A1 policy, and the resources of the A1 policy.

[0136] 2. Intention consumers and intention producers.

[0137] Among them, the intention consumer is a device that manages intentions. Specifically, the intention consumer can generate an intention and send an intention expression used to carry the intention to the intention producer. Among them, the intention can be the requirement of the intention consumer for the network where the device executing the intention solution is located. For example, the intention can reflect the requirement of the intention consumer for at least one key performance indicator (KPI) in the network where the device executing the intention solution is located.

[0138] The intention producer is a device that processes intentions. Specifically, after receiving the intention expression from the intention consumer, the intention producer can generate multiple solutions that can meet the intention and select one solution for execution. Then, the intention producer can send the selected solution to the device that executes the intention so that the device that executes the intention can execute the selected solution.

[0139] The intention consumer and / or the intention producer can be, but are not limited to, computing devices, servers, or network devices, etc. For example, the intention consumer can be a business support system (BSS), an operations support system (OSS), an NMS, an IDMS Consumer, or an MnS Consumer, etc., without limitation.

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

[0141] It should be understood that the intent consumer and the intent producer can also adopt other names as long as they have the same functions. The embodiments of the present application do not limit this.

[0142] 3. Service guarantee

[0143] For services or users with different priorities, network devices need to provide differentiated services to preferentially meet the needs of high-priority services or users. For example, with the continuous development of mobile network technology, the quality of live broadcast services has also been continuously improved, gradually becoming an important way for people to obtain information, entertainment, social interaction, etc. For operators, live broadcast services have also become one of their important sources of income. Therefore, network devices need to preferentially guarantee the live broadcast service requirements of high-priority services or users.

[0144] As Figure 1 shown, the network can provide differentiated quality of service (QoS) priority guarantees for users or services with different priorities to ensure user services. Exemplarily, for very very important persons (VVIPs), a higher QoS priority can be set than that of ordinary users. For example, VVIP users can be set with a quality of service class identifier (QCI) = 6, and ordinary users can be set with QCI = 9 to achieve preferentially providing a good experience for VVIP users in a congested network, especially to meet experiences such as uplink rate, and at the same time can enjoy the priority access to the fifth generation mobile communication technology (5G) extreme speed service during peak hours, thereby providing better network guarantee for VVIP users.

[0145] Currently, in the current 3rd generation partnership project (3GPP), a management service consumer (MnS Consumer) can express requirements, goals, and constraints for services or the network by configuring an intent model. When the MnS Consumer issues a service intent through the intent model, it can activate or deactivate the intent by configuring the attribute intentAdminiState, and the management service producer (MnS producer) can synchronously execute the intent according to the received intent expression.

[0146] However, when the number of service intents simultaneously sent by the MnS Consumer is large, intent conflicts may occur, resulting in low service stability.

[0147] For example, the network guarantees user services by providing differentiated QoS priorities. When there are many users to be guaranteed, for example, when the number of VVIP users is large, the MnS Consumer may need to simultaneously send a large number of service intents to guarantee the needs of VVIP users. The MnS Producer synchronously executes the intents according to the received intent expressions, which may lead to too many intents being executed simultaneously in the system, resulting in intent conflicts and having a great impact on the service stability of the users being guaranteed, thus leading to low service stability.

[0148] In view of the above technical problems, the embodiments of the present application propose the following technical solutions to avoid intent conflicts and improve service stability.

[0149] Next, the technical solutions in the embodiments of the present application will be described with reference to the accompanying drawings.

[0150] 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, worldwide interoperability for microwave access (WiMAX) communication systems, 5G, such as new radio (NR) systems, and future communication systems, etc.

[0151] The present application will present various aspects, embodiments or features around a system 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 the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. In addition, combinations of these solutions can also be used.

[0152] In addition, in the embodiments of the present application, words such as "exemplary" and "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of the word "exemplary" is intended to present concepts in a specific manner.

[0153] In the embodiments of the present application, the terms "information", "signal", "message", "channel", and "signaling" may sometimes be used interchangeably. It should be noted that when the differences are not emphasized, their intended meanings are consistent. The terms "of", "corresponding", and "corresponding to" may sometimes be used interchangeably. It should be noted that when the differences are not emphasized, their intended meanings are consistent. In addition, the " / " mentioned in the present application may be used to represent an "or" relationship. It can be understood that in the present application, "indication" may include direct indication, indirect indication, display indication, and implicit indication. When it is described that a certain indication information is used to indicate A, it can be understood that the indication information carries A, directly indicates A, or indirectly indicates A.

[0154] In the present 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. For example, 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, where there is an association relationship between the other information and the information to be indicated. It is also possible to only indicate a part of the information to be indicated, while the other parts of the information to be indicated are known or pre-agreed. For example, the arrangement order of each piece of information pre-agreed (such as stipulated by a protocol) can also be used to indicate specific information, thereby reducing the indication overhead to a certain extent.

[0155] The information to be indicated can be sent as a whole, or can be divided into multiple sub-information and sent separately, and the sending periods and / or sending opportunities of these sub-information can be the same or different. The specific sending method is not limited in the present application. Among them, the sending periods and / or sending opportunities of these sub-information can be pre-defined, such as pre-defined according to a protocol, or can be configured by the transmitting device by sending configuration information to the receiving device.

[0156] The network architecture and service scenarios described in the embodiments of the present application are for more clearly explaining the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those of ordinary skill in the art know that with the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0157] To facilitate the understanding of the embodiments of the present application, first, Figure 2 the communication system shown in Figure 2Schematic diagram of the architecture of a communication system applicable to the communication method provided in the embodiments of the present application Figure 1 。

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

[0159] The communication system can be used for the architectures of different communication systems, such as the 3GPP architecture or the 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 will be introduced separately below.

[0160] The above communication system can be applied to the 3GPP architecture, Figure 3 Schematic diagram of the 3GPP architecture provided in the embodiments of the present application. As Figure 3 shown, the above-mentioned first device can be an intent producer, and the second device can be an intent consumer. Among them, the first device can be an MnS producer, and the second device can be an MnS consumer. The MnS Consumer can send the intent to the MnS Producer by calling the intent-driven Mns interface. The MnS Producer can translate the intent into a specific execution policy and send it to the network infrastructure, and continuously monitor the network status during the intent execution process to ensure the achievement of the intent.

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

[0162] The above communication system can also be applied to the O-RAN architecture, Figure 4 Schematic diagram of the O-RAN architecture provided in the embodiments of the present application. As Figure 4As shown, the above-mentioned second device can be the intent owner, and the intent owner can be equivalent to the above-mentioned intent consumer, with the same functions or roles as the intent consumer, without limitation. The above-mentioned first device can include a first functional entity, a second functional entity, and a first application; or rather, the combination of the first functional entity, the second functional entity, and the first application can achieve the same functions or roles 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.

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

[0164] The Near-RT RIC is a component in the O-RAN architecture. Its main function is to provide near-real-time (the latency of the control loop >= 10ms and < 1s) intelligent control and coordination in the RAN to support network automation and optimization. The Near-RT RIC can be deployed independently on the cloud platform, or the Near-RT RIC and the SMO can be deployed in the same device, without limitation.

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

[0166] 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 through the A1 interface to the Near-RT RIC to select a suitable XAPP for execution. For example, XAPP1 can convert it into an execution plan and send it down to the E2 node for execution ( Figure 4 not drawn in the figure). The Near-RT RIC can feedback the execution result of the A1 policy (A1 policy feedback) to the Non-RT RIC, and the Non-RT RIC can feedback the intent execution result (intent feedback) to the intent owner.

[0167] 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 a pre-evaluation function, such as services with functions related to network digital twins, etc., without limitation.

[0168] It should be understood that in the embodiments of the present application, the names of nodes, modules, devices, or network elements in different scenarios, architectures, or systems are exemplarily given, as well as the names of the communication interfaces between two of the nodes, modules, devices, or network elements. It does not exclude the possibility of name changes in future communication systems, scenarios, or architectures.

[0169] In this communication system, the first device can send second information to the second device according to the first resources required for each intention expectation in at least one intention expectation estimated to be completed, to indicate whether the first service successfully pre-occupies the first resources during the activation period, so that the second device can determine whether it needs to modify the activation period subsequently. The first request message can include the activation period of the first intention instance. When the first intention instance successfully pre-occupies the first resources during the activation period, the first device can occupy the first resources during the activation period. That is, when the activation period arrives, the first device can directly occupy or use the first resources to implement the first intention instance. In this way, pre-occupation of resources can be achieved, the situation of intention conflicts can be avoided, and the stability of the service can be improved.

[0170] It can be understood that the above Figures 2 - 4 For the sake of easy understanding, a simplified schematic diagram is exemplified. In this communication system, there can also be other devices, network elements, or functional entities, Figures 2 - 4 which are not drawn.

[0171] For easy understanding, the following will combine Figures 5 - 12 to specifically elaborate on the communication method provided in the embodiments of the present application.

[0172] Exemplarily, Figure 5 is a flowchart illustration of the communication method provided in the embodiments of the present application Figure 1 . This method can be applied to the above communication system and involves the interaction between the first device, the second device, and the third device.

[0173] Specifically, as Figure 5 shown, the process of this communication method is as follows:

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

[0175] It can be understood that the above first device and second device can be applicable to the Figure 3 shown 3GPP architecture, or the aboveFigure 4 The O-RAN architecture shown below. Taking the following two cases as examples, the process of the second device sending a first request message to the first device will be introduced.

[0176] Case a:

[0177] The above first device and second device can be applicable to the above Figure 3 shown 3GPP architecture. That is, the first device can be an intent producer, and the second device can be an intent consumer.

[0178] The intent consumer sends a first request message to the intent producer. Correspondingly, the intent producer receives the first request message from the intent consumer. It can be understood that in this case, the intent producer can create a first intent instance according to the first request message and create a corresponding intent context.

[0179] Case b:

[0180] The above first device and second device can be applicable to the above Figure 4 shown O-RAN architecture. 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 an intent owner.

[0181] That is, the intent owner can send a first request message to the first functional entity. Correspondingly, the first functional entity receives the first request message from the intent owner. It can be understood that in this case, the first functional entity can create a first intent instance according to the first request message and create a corresponding intent context. Combining the above two cases, the first request message will be introduced below.

[0182] Among them, the first request message can be used to request the creation of a first intent instance corresponding to a first service. The first intent instance includes at least one intent expectation.

[0183] The first intent instance can be an intent instance related to the first service. That is, the first service can be the service or user guaranteed by the first intent instance. Exemplarily, the first service can be the live broadcast service, video service, etc. of user #1, without limitation. For ease of understanding, the embodiments of the present application will take the first service as the live broadcast service of user #1 as an example for subsequent introduction. It can be understood that the live broadcast service of user #1 can be a subscribed service of the second device. The second device can undertake the service requirements of the live broadcast service of user #1, and the first device can provide service guarantee for the live broadcast service of user #1.

[0184] In a possible design, 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.

[0185] Among them, 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 may include at least one intention expectation, and each intention expectation corresponds to at least one expected target.

[0186] The at least one expected target corresponding to each intention expectation is the same as the service guarantee target of the first service. Or rather, all the expected targets of the first intention expression are the same as the service guarantee target of the first service. For example, if the service guarantee target of the first service is: the uplink throughput is greater than or equal to 5 million bits per second (Mb / s), and the uplink latency is less than or equal to 10 milliseconds (ms), then the at least one expected target corresponding to each intention expectation may include: the uplink throughput rate is greater than or equal to 5 Mb / s and the uplink latency is less than or equal to 10 ms. Suppose the cell to which user #1 belongs is cell #1, or rather, cell #1 can provide services for user #1, then the expected object may be cell #1.

[0187] It should be understood that the service guarantee target of the above-mentioned first service, or the expected target corresponding to the at least one expected target, can be at the granularity of the service on the user, that is, at the per-user-per-service level. For example, for the live broadcast service of the above-mentioned user #1, at this time, the service guarantee target of the first service is for the live broadcast service of user #1; the service guarantee target of the above-mentioned first service, or the expected target corresponding to the at least one expected target, can also be at the granularity of the user, that is, at the per-user level. For example, for the above-mentioned user #1, at this time, the service guarantee target of the first service is for any service on user #1, without limitation.

[0188] The first request message may include the activation time period of the first intention instance, and the activation time may be determined by the second device according to the execution time period of the reservation guarantee for the subscribed user, that is, the live broadcast service of the above-mentioned user #1. It can be understood that the execution time period of the reservation guarantee for the subscribed user may be included in this activation time period, without limitation. The activation time period may be the time interval during which the first intention instance is activated. During this activation time period, the first intention instance may be activated, or rather, the first service may be executed.

[0189] 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 execution of the first service may be paused. It can be understood that the time interval between the first activation time and the first deactivation time is the activation time period.

[0190] It can be understood that the above is the case where the second device directly sets the activation time and the deactivation time of the first intent instance. The second device may also not directly set the activation time and the deactivation time of the first intent instance, that is, the second device may set different intent activation policies, and the following will take the following cases as examples for specific introduction.

[0191] Case 1:

[0192] Activate when the intent (or intent instance) is sent, and deactivate manually.

[0193] 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 it is necessary to deactivate the intent, the second device may send a delete intent request message to request the deletion of the intent. At this time, the first device may 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 may execute the intent scheme corresponding to the intent all the time after activating the intent.

[0194] 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 is empty.

[0195] Case 2:

[0196] Activate when the intent is sent, and set the deactivation time.

[0197] 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. The second device may set the deactivation time, and when the deactivation time is reached, the first device may deactivate the intent.

[0198] It can be understood that in Case 2, the second device may configure an intent activation policy, and the intent activation policy includes the deactivation time.

[0199] Case 3:

[0200] Set the activation time, and deactivate manually.

[0201] The second device can set an activation time, and when this activation time is reached, the first device can activate the intent. When it is necessary to deactivate the intent, 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 according to this delete intent request message. That is, the time when the second device sends this delete intent request message is the deactivation time of this intent. It should be understood that before the second device sends the delete intent request message, the first device can keep executing the intent scheme corresponding to this intent after activating the intent.

[0202] It can be understood that in case 3, the second device can configure an intent activation policy, and this intent activation policy includes the activation time.

[0203] Case 4:

[0204] Set the activation time and the deactivation time.

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

[0206] It can be understood that in case 4, the second device can configure an intent activation policy, and this intent activation policy includes the activation time and the deactivation time.

[0207] The above activation time period includes a first activation time and a first deactivation time, that is, corresponding to this case 4. For easy understanding, the embodiments of the present application take case 4 as an example for introduction, and will not be elaborated later.

[0208] It can be understood that the intents in the above cases 1 - 4 can include a first intent instance, which is not limited.

[0209] Optionally, the first request message can also include an identifier of the first service and cycle information.

[0210] Among them, the identifier can be used to identify the first service. That is, this 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 guarantee the first service. For example, this identifier can be identifier #1, and identifier #1 can be used to identify the live broadcast service of user #1, etc., which is not limited.

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

[0212] It can be understood that the period of the above reservation can be set according to actual needs without limitation. Optionally, the first request message may further include resource reservation indication information (field) and / or pre-evaluation system selection indication information (field).

[0213] Among them, the resource reservation indication information can indicate whether exclusive use of resources is allowed when executing the first intent instance. When the resource reservation indication information takes a first value, it can indicate that exclusive use of resources is required when executing the first intent instance. That is, the first intent instance can execute a resource pre-occupation process (such as step S502 below) during the activation time period; when the resource reservation indication information takes a second value, it can indicate that exclusive use of resources is not required when executing the first intent instance. That is, the first intent instance does not execute the resource pre-occupation process during 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, and the second value can be false without limitation.

[0214] It can be understood that the embodiments of the present application are introduced under the condition that the resource reservation indication information takes the first value, and will not be elaborated hereinafter.

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

[0216] If the pre-evaluation system selection indication information is empty, or the first request message does not include the pre-evaluation system selection indication information, the first device can default to invoking internal components, such as perception, analysis, decision-making, etc. for pre-evaluation to generate the above first information without limitation. Optionally, the first request message may further include at least one of the following: the service guarantee target of the first service, the application scope, or the terminal / terminal group identifier.

[0217] Among them, the introduction of the service guarantee target of the first service can refer to the introduction of the above relevant content and will not be elaborated. The application scope can correspond one-to-one with the above expected object. For example, the application scope can be cell #1. The terminal / terminal group identifier can be used to identify the terminal (i.e., the above user) to which the first service belongs, or the terminal to which it belongs without limitation. For example, terminal #1 can indicate the above user #1.

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

[0219] S502, the first device sends the second information to the second device according to the first information. Correspondingly, the second device receives the second information from the first device.

[0220] It can be understood that before introducing the first information and the second information, the above method further includes:

[0221] The first device generates a first intent solution according to the first intent instance.

[0222] Among them, the first intent solution can be used to implement each intent expectation in at least one intent expectation. That is, the first intent solution can be one of at least one intent solution that is the expected target for completing all intent expectations of the first intent instance. That is, when the first intent solution is executed, it can achieve the expected target of the uplink throughput rate being greater than or equal to 5 Mb / s and the uplink delay being less than or equal to 10 ms. It can be understood that the achievement effect of the first intent solution can also meet the expected achievement effect.

[0223] The following specifically introduces the process of generating the first intent solution.

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

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

[0226] Exemplarily, the first functional entity can generate an A1 policy according to the first intent instance. The A1 policy is a declarative policy expression form, and the A1 policy can include policyTypeId, policyId, and policyObject. 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 E2 node information to be executed, and 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 service guarantee target of the first service, which will not be elaborated. It can be understood that the specific introduction of the A1 policy can refer to the introduction in the above technical terms section and will not be elaborated.

[0227] The first functional entity can send the A1 policy to the second functional entity, and the second functional entity can send the A1 policy to a suitable application, such as the first application, according to the content of the A1 policy. The first application can translate the A1 policy to generate the first intent solution, and the first intent solution can be a control message for the E2 node.

[0228] It can be understood that the first functional entity can also send at least one of the following to the second functional entity together with the A1 policy: activation time period, identifier of the first service, resource reservation indication information, cycle information, pre-evaluation system selection indication information, service guarantee target of the first service, application scope, or terminal / terminal group identifier, etc. The second functional entity can store this part of information for subsequent pre-occupation of resources for the first intention instance.

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

[0230] Among them, the first information can be used to indicate the first resources required to estimate the completion of each intention expectation in at least one intention expectation; or, the first information can be used to indicate the first resources 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 resources required to estimate the completion of all service guarantee goals of the first service.

[0231] The first device can call an internal service or an external service to obtain the first information. Taking the following two ways as examples, the implementation process of the first device obtaining the first information will be specifically introduced below.

[0232] Method 1:

[0233] The first device generates the first information according to the first intention plan.

[0234] (1) Based on the above situation a, the intention producer can generate the first information according to the first intention plan. Exemplarily, the intention producer can call an internal service, such as components for perception, analysis, decision-making, etc., to perform a pre-evaluation of resources for the first intention plan, so as to evaluate the first (network) resources required to implement the first intention instance when the first intention plan is executed, that is, to evaluate the first resources required to complete all intention expectations of the first intention instance when the first intention plan is executed, so as to obtain the first information. It can be understood that the resources described in the embodiments of the present application may include: resource blocks (RBs), transmission bandwidth, frequency bands, central processing units (CPUs), graphics processing units (GPUs), slice resources, or memory, etc., which will not be elaborated hereinafter. The resources may include the above first resources.

[0235] For example, taking the case where the intention producer executes intention scenario #1 as an example, the intention producer can estimate the resources required (denoted as resource #1) to achieve an uplink throughput rate equal to 5 Mb / s and an uplink latency equal to 10 ms when executing intention scenario #1 by invoking internal services, such as components for perception, analysis, decision-making, etc., so as to generate the first piece of information.

[0236] Method 2:

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

[0238] The third device generates the first piece of information according to the second request message.

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

[0240] The following is a specific introduction.

[0241] Based on the above situation a, the third device can be a third-party pre-evaluation system or an intention pre-evaluation system, such as a digital twin system with pre-evaluation function, a knowledge base, or an AI model, etc., without limitation. For ease of understanding, the following takes the third device as an intention pre-evaluation system as an example for subsequent introduction.

[0242] Among them, the second request message may include at least one of the following: the first intention scenario, the expectation list, or the expected object information.

[0243] The first intention scenario can be used to implement each intention period in the at least one intention expectation.

[0244] The expectation list can be used to indicate at least one intention expectation, or rather, the expectation list can indicate all expectations of the first intention instance, or rather, the expectation list can indicate all expected goals of the first intention instance. For example, the expectation list may include: the uplink throughput rate is greater than or equal to 5 Mb / s, and the uplink latency is less than or equal to 10 ms. It can be understood that this expectation list can be the same as the service guarantee target of the above first service, and will not be elaborated.

[0245] The expected object information can be used to indicate the object for executing the first intention instance, which is the same as the above application scope, such as the above cell #1, and will not be elaborated.

[0246] The second request message can be used to request to obtain the resources required to estimate the completion of each intention expectation in the at least one intention expectation, that is, the second request message can be used to request to obtain the first resources required to estimate the completion of all expected goals of the first intention instance.

[0247] In this case, the intention pre-evaluation system can obtain relevant network configuration information and network and service metric statistical values based on the expected object information and the expected list, and perform resource pre-evaluation on the first intention plan to evaluate the first resources required to implement the first intention instance when the first intention plan is executed, that is, to evaluate the first resources required to complete all the expected goals of the first intention instance when the first intention plan is executed, so as to obtain the first information and feedback the first information to the intention producer.

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

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

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

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

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

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

[0254] The second request message may request to obtain the resources required to estimate the completion of each intention expectation in at least one intention expectation, that is, the second request message may be used to request to obtain the first resources required to estimate the completion of all the expected goals of the first intention instance. In this case, the second application can obtain the first resources required when the first intention plan is executed to complete the uplink throughput rate equal to 5 Mb / s and the uplink delay equal to 10 ms according to the A1 policy and the application scope, so as to generate the first information, and the second application can send the first information to the second functional entity.

[0255] 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 naming, such as the second request, the resource pre-evaluation request, etc., without limitation.

[0256] Combined with the above introduction, in a possible design solution, before the first device sends the second information to the second device according to the first information, the above method may further include:

[0257] The first device determines whether there is an intention conflict between the first intention instance and other intention instances according to the first information.

[0258] Exemplarily, if there is a resource greater than the first resource and not preoccupied within the activation time period, there is no intention conflict between the first intention instance and other intention instances; if there is no resource greater than the first resource and not preoccupied within the activation time period, there is an intention conflict between the first intention instance and other intention instances.

[0259] The following is a specific introduction.

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

[0261] Exemplarily, the intention producer can determine whether there is a resource greater than the first resource and not preoccupied within the activation time period. If the intention producer determines that there is a resource greater than the first resource and not preoccupied within the activation time period, it can indicate that there is no intention conflict between the first intention instance and other intention instances. That is, within this activation time period, there is still free resource in the system that is greater than the first resource and not preoccupied by other intention instances.

[0262] For example, if the intention producer determines that the free resource not occupied by other intention instances within the activation time period is Resource #2, and this Resource #2 is greater than the above-estimated Resource #1, it can indicate that there is no intention conflict between the first intention instance and other intention instances.

[0263] If the intention producer determines that there is no resource greater than the first resource and not preoccupied within the activation time period, it can indicate that there is an intention conflict between the first intention instance and other intention instances. That is, within this activation time period, the free resource in the system that is not preoccupied by other intention instances is less than the first resource, or there is no free resource in the system that is not preoccupied by other intention instances, such as the free resource being 0. For example, if the intention producer determines that the free resource not occupied by other intention instances within the activation time period is Resource #3, and this Resource #3 is less than the above-estimated Resource #1, it can indicate that there is an intention conflict between the first intention instance and other intention instances.

[0264] For example, within a time period that completely coincides with or partially coincides with this activation time period, if the second intention instance preoccupies the fourth resource, it can indicate that there is an intention conflict between the first intention instance and this second intention instance.

[0265] (2) Based on the above situation b, the second functional entity can, according to the first information, determine whether there is a resource that is greater than the first resource and not pre-occupied during the activation period. If the second functional entity determines that there is a resource that is greater than the first resource and not pre-occupied during the activation period, it can indicate that there is no intention conflict between the first intention instance and other intention instances. That is, during this activation period, there is still a free resource in the system that is greater than the first resource and not pre-occupied by other intention instances.

[0266] For example, if the second functional entity determines that the free resource not occupied by other intention instances during the activation period is Resource #2, and this Resource #2 is greater than the above-estimated Resource #1, it can indicate that there is no intention conflict between the first intention instance and other intention instances.

[0267] If the second functional entity determines that there is no resource that is greater than the first resource and not pre-occupied during the activation period, it can indicate that there is an intention conflict between the first intention instance and other intention instances. That is, during this activation period, the free resource in the system that is not pre-occupied by other intention instances is less than the first resource, or there is no free resource in the system that is not pre-occupied by other intention instances, such as the free resource being 0. For example, if the second functional entity determines that the free resource not occupied by other intention instances during the activation period is Resource #3, and this Resource #3 is less than the above-estimated Resource #1, it can indicate that there is an intention conflict between the first intention instance and other intention instances.

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

[0269] Combined with the above introduction, in a possible design solution, the above method may further include:

[0270] The first device saves the first intention plan.

[0271] Among them, the first intention plan can be some configuration commands, such as internal logic or command sequences that need to be executed, etc.

[0272] It can be understood that in the case where there is no intention conflict between the first intention instance and other intention instances, the first device can save the first intention plan, and the first intention plan can occupy the first resource during the activation period. In the case where there is an intention conflict between the first intention instance and other intention instances, the first device can also save the first intention plan for subsequent use during a new activation period. The first device can directly occupy the first resource to execute this first intention plan without limitation.

[0273] The following is a specific introduction.

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

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

[0276] Combined with the above introduction, the second information can be used to indicate whether the pre - occupation of the first resource is successful during the activation time period, and the second information is determined by the first information. Next, in two cases where there is an intention conflict between the first intention instance and other intention instances, and where there is no intention conflict between the first intention instance and other intention instances during the activation time period, the second information will be specifically introduced.

[0277] Case 5:

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

[0279] The second information can be used to indicate that the pre - occupation of the first resource is successful during the activation time period.

[0280] That is, the second information can be used to characterize the intention resource management status of the first intention instance as the reserved status, to indicate that the first intention instance pre - occupies the first resource successfully during the activation time period. For easy understanding, in the embodiments of the present application, the second information indicating that the pre - occupation of the first resource is successful during the activation time period can be denoted as management status #2, and will not be elaborated hereinafter.

[0281] It can be understood that after the first device creates the first intention instance according to 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 intention conflict between the first intention instance and other intention instances, the intention resource management status of the first intention instance is the in - reservation status, to indicate that the first intention instance is executing the resource pre - occupation process during the activation time period, and this intention resource management status can be denoted as management status #1.

[0282] At this time, when the first intent instance successfully pre-occupies the first resource within the activation time period, the intent resource management state can change from the reserved state to the reserved state, that is, the intent resource management state can change from management state #1 to management state #2.

[0283] Case 6:

[0284] Within the activation time period, there is an intent conflict between the first intent instance and other intent instances.

[0285] The second information can be used to indicate that the pre-occupation of the first resource fails 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 the unreserved state, so as to indicate that the first intent instance fails to pre-occupy the first resource within the activation time period. For ease of understanding, in the embodiments of the present application, the second information indicating that the pre-occupation of the first resource fails within the activation time period can be denoted as management state #3, which will not be elaborated hereinafter.

[0286] At this time, when the first intent instance fails to pre-occupy the first resource within the activation time period, the intent resource management state can change from the reserved state to the unreserved state, that is, the intent resource management state can change from management state #1 to management state #3.

[0287] It can be understood that the naming of the above first information is only an example, and the first information can also be replaced with any other possible naming, such as resource evaluation information, etc., without limitation. The naming of the above second information is only an example, and the second information can also be replaced with any other possible naming, such as intent report, etc., without limitation.

[0288] S503. In the case where the first resource is successfully pre-occupied within the activation time period, the first device occupies the first resource within the activation time period.

[0289] It can be understood that this step S503 is a step executed based on the above case 5, that is, within the activation time period, when there is no intent conflict between the first intent instance and other intent instances, the first device can occupy the first resource within the activation time period. In this way, resource pre-occupation can be performed before executing the intent to reasonably allocate network resources, so that limited network resources can be accurately invested in the services that need to be guaranteed, ensuring the service stability of the users who need to be guaranteed, and avoiding conflicts when executing the intent.

[0290] Exemplarily, in one possible design solution, the above method may further include:

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

[0292] The first device occupies the first resource to execute the first intent scheme.

[0293] The first device sends the third information to the second device. Correspondingly, the second device receives the third information from the first device.

[0294] Among them, the third information can be used to indicate that the first resource is being occupied. That is to say, the third information can be used to characterize that the intention resource management state of the first intention instance is in the using state, so as to indicate that the first intention instance has been activated. For ease of understanding, in the embodiments of the present application, the third information can be denoted as management state #4, and will not be elaborated hereinafter.

[0295] At this time, the intention resource management state can change from the reserved state to the using state, that is, the intention resource management state can change from management state #2 to management state #4.

[0296] The following is a specific introduction.

[0297] (1) Based on the above situation a, the intention producer can activate the created first intention instance when reaching the first activation time, and occupy the pre-reserved first resource to execute the first intention plan. For example, the intention producer can send a corresponding control message to the desired 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 elaborated.

[0298] The intention producer can also report the current intention resource management state, that is, management state #4, to the intention consumer, so that the intention consumer can obtain the intention resource management state of the first intention instance in real time.

[0299] (2) Based on the above situation b, the first application can activate the created first intention instance when reaching the first activation time, and occupy the pre-reserved first resource 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 according to the control message for the E2 node in the first intention plan. The implementation process of this process can refer to the implementation process of the extended application executing the intention plan in the prior art and will not be elaborated.

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

[0301] In a possible design solution, the above method may further include:

[0302] When reaching the first deactivation time, the first device deactivates the first intention instance.

[0303] The first device suspends the execution of the first intent plan and releases the first resource.

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

[0305] It can be understood that if the above first intent instance is an intent instance that is executed periodically, the fourth information can be used to indicate that the preoccupation of the first resource is successful within the activation time period. That is to say, the fourth information can be used to characterize that the intent resource management state of the first intent instance is in a reserved state, so as to indicate that the first intent instance successfully preoccupies the first resource within the activation time period, so that the first intent instance can continue to use the first resource within the activation time period at other moments within the reserved period.

[0306] For ease of understanding, in the embodiments of the present application, the fourth information when the first intent instance is an intent instance that is executed periodically can be denoted as management state #5, which will not be elaborated hereinafter. This management state #5 is the same as the above management state #2. In this case, the intent resource management state can change from the in-use state to the reserved state. That is to say, the intent resource management state can change from management state #4 to management state #2 or management state #5, without limitation.

[0307] If the above first intent instance is a non-periodic execution intent instance, the fourth information can be used to indicate that the preoccupation of the first resource fails within the activation time period. That is to say, the fourth information can be used to characterize that the intent resource management state of the first intent instance is in an unreserved state, so as to indicate that the first intent instance fails to preoccupy the first resource within the activation time period. For ease of understanding, in the embodiments of the present application, the fourth information when the first intent instance is a non-periodic execution intent instance can be denoted as management state #6, which will not be elaborated hereinafter. This management state #6 is the same as the above management state #3.

[0308] In this case, the intent resource management state can change from the in-use state to the unreserved state. That is to say, the intent resource management state can change from management state #4 to management state #3 or management state #6, without limitation.

[0309] The following is a specific introduction.

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

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

[0312] In summary, the first device can send a second message to the second device according to the first resources estimated to be occupied for each intent expectation in at least one intent expectation, to indicate whether the first service successfully pre-occupies the first resources during the activation period, so that the second device can determine whether it needs to modify the activation period subsequently. The first request message can include the activation period of the first intent instance. When the first intent instance successfully pre-occupies the first resources during the activation period, the first device can occupy the first resources during the activation period, that is, when the activation period is reached, the first device can directly occupy or use the first resources to implement the first intent instance. In this way, pre-occupation of resources can be achieved, the situation of intent conflicts can be avoided, and the stability of the service can be improved.

[0313] Combined with the above embodiments, 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:

[0314] The second device sends an indication message to the first device. Correspondingly, the first device receives the indication message from the second device.

[0315] The first device deactivates or deletes the first intent instance according to the indication message.

[0316] The first device suspends the execution of the first intent plan and releases the first resources.

[0317] Among them, (1) if the indication message is specifically used to indicate deleting the first intent instance, the first device can directly delete the first intent instance according to the indication message. The following is a specific introduction.

[0318] Based on the above situation a, the intent consumer can send an indication message to the intent producer to indicate deleting the first intent instance. The intent producer can delete the first intent instance according to the indication message, and the intent producer can suspend the execution of the first intent plan and release the first resources.

[0319] In this case, the intention producer may also send a sixth piece of information to the intention consumer. The sixth piece of information may be used to indicate that the intention resource management status of the first intention instance is empty, so as to indicate that the first intention instance has been deleted. The sixth piece of information may be denoted as management status #7, which will not be elaborated hereinafter.

[0320] In this case, the intention resource management status may change from the in-use state to the empty state. That is to say, the intention resource management status may change from management status #4 to management status #7, without limitation.

[0321] It can be understood that the implementation of this process in the above case b is similar to the implementation process of case a, which can be referred to for understanding and will not be elaborated herein.

[0322] (2) If the indication information is specifically used to indicate that the first deactivation time is modified to a third deactivation time, then when the third deactivation time arrives, the first device deactivates the first intention plan, pauses the execution of the first intention plan, and releases the first resource being occupied. The third indication information may include the third deactivation time, and the third activation time may be greater than the first deactivation time or less than the first deactivation time, so as to achieve early or delayed deactivation of the first intention instance to meet different service requirements.

[0323] Based on the above case a, the intention consumer may send indication information to the intention producer to indicate that the first deactivation time is modified to a third deactivation time. The intention producer may modify the first deactivation time to the third deactivation time according to the indication information. When the third deactivation time arrives, the intention producer may deactivate the first intention instance, pause the execution of the first intention plan, and release the occupied first resource.

[0324] In this case, the intention producer may also send a seventh piece of information to the intention consumer.

[0325] If the above first intention instance is an intention instance that is executed periodically, the seventh piece of information may be used to represent that the intention resource management status of the first intention instance is the reserved state, so as to indicate that the first intention instance has successfully pre-occupied the first resource during the activation time period, so that the first intention instance can continue to use the first resource during the activation time periods at other moments within the reserved period. For ease of understanding, in the embodiments of the present application, when the first intention instance is an intention instance that is executed periodically, the seventh piece of information may be denoted as management status #8, which will not be elaborated hereinafter. This management status #8 is the same as the above management status #2 or management status #5.

[0326] At this time, the intention resource management status may change from the in-use state to the reserved state. That is to say, the intention resource management status may change from management status #4 to management status #2, management status #5 or management status #8, without limitation.

[0327] If the above-mentioned first intention instance is a non-periodic execution intention instance, the seventh piece of information can be used to characterize that the intention resource management state of the first intention instance is an unreserved state, indicating that the first intention instance fails to pre-occupy the first resource during the activation period. For ease of understanding, in the embodiments of the present application, the seventh piece of information when the first intention instance is a non-periodic execution intention instance can be denoted as management state #9, which will not be elaborated hereinafter. This management state #9 is the same as the above-mentioned management state #6.

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

[0329] It can be understood that the implementation of this process in the above-mentioned situation b is similar to the implementation process of situation a and can be understood by reference without further elaboration.

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

[0331] The first device determines the second activation time and / or the second deactivation time of the first intention instance according to the priority of the intention instance.

[0332] Wherein, the intention instance includes the first intention instance.

[0333] It can be understood that each intention instance can correspond to a priority. The higher the priority of the intention instance, the higher the priority of the corresponding service, which needs to be guaranteed first. The first device can determine the second activation time and / or the second deactivation time of the first intention instance according to the priorities of other intention instances that have an intention conflict with the first intention instance during the activation period.

[0334] It can be understood that the specific implementation of this process can refer to the implementation process of step S708 below and will not be elaborated herein.

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

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

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

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

[0339] The first device executes the first intent scenario during the modified activation time period.

[0340] 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 reason for the intent conflict to the second device. For example, during the activated time period, if there is an intent conflict between the first intent instance and the second intent instance, the fifth information can be used to indicate that there is an intent conflict between the first intent instance and other intent instances. The fifth information can include the second activation time and / or the second deactivation time.

[0341] 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 second device can send the third request message to the first device according to the fifth information, so as 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. In this way, the situation where there is an intent conflict between the first intent instance and other intent instances can be avoided.

[0342] The first device can execute the pre-saved first intent scenario during the modified activation time period to resolve the conflict between the first intent instance and other intent instances.

[0343] It can be understood that for the specific implementation of this process, reference can be made to the implementation process of the following steps S709 - S712, which will not be elaborated here.

[0344] It can be understood that the first device can also determine the second activation time and / or the second deactivation time of the first intent instance according to the preemption ability of the intent instance; or, the first device can also jointly determine the second activation time and / or the second deactivation time of the first intent instance according to the priority and preemption ability of the intent instance, which is not limited.

[0345] It can be understood that in the embodiments of the present application, "occupation" and "use" can be replaced with each other, and "reservation" and "pre - occupation" can be replaced with each other, which is not limited. The above combines the method embodiments to introduce the overall process of the communication method provided by the embodiments of the present application. For the convenience of understanding, the above - mentioned method will be introduced by taking the following 3 scenarios as examples.

[0346] Scenario 1:

[0347] Figure 6 is a schematic diagram of the process of the communication method provided by the embodiments of the present application Figure 2 . It mainly involves the interaction between the MnS Consumer (such as the second device above), the MnS Producer (such as the first device above), and the intent pre - evaluation system #1 (such as the third device above).

[0348] As Figure 6 shown, the method may include:

[0349] S601, the MnS Consumer obtains the subscription information.

[0350] Among them, the subscription information may include: the subscribed services or applications (APPs) of the user, the service guarantee objectives, and the reserved service guarantee time periods corresponding to each subscribed service or application, etc.

[0351] For example, the user may be User #1, and the subscribed services or applications of the user may include: the live broadcast service, video service, or voice service of User #1, etc.

[0352] The service guarantee objectives may include the service guarantee objectives corresponding to each subscribed service or application. For example, taking the live broadcast service of User #1 as an example, the service guarantee objective #1 of the live broadcast service may include: the uplink throughput rate is greater than or equal to 5 Mb / s, and the uplink delay is less than or equal to 10 ms.

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

[0354] S602, the MnS Consumer sends the intention creation request message #1 to the MnS Producer.

[0355] When User #1 has a service requirement for the live broadcast service, the MnS Consumer may, according to the subscription information, determine whether the live broadcast service of User #1 is a subscribed service of the network, that is, whether it is a service that the network needs to guarantee. If the MnS Consumer determines that the subscription information includes the live broadcast service of User #1, the MnS Consumer may determine that the live broadcast service of User #1 is a service that the network needs to guarantee.

[0356] At this time, the MnS Consumer may send the intention creation request message #1 to the MnS Producer. The intention creation request message #1 is used to request the creation of an intention instance #1 related to the live broadcast service. The intention instance #1 may include at least one intention expectation, and all the expected objectives included in the at least one intention expectation are the same as the service guarantee objective #1. That is, the intention instance #1 may include: the uplink throughput rate is greater than or equal to 5 Mb / s, and the uplink delay is less than or equal to 10 ms.

[0357] The intention creation request message #1 may further include: service guarantee objective #1, application scope #1, the identifier of user #1 (denoted as identifier #a), the identifier of the live broadcast service (denoted as identifier #b), intention activation policy #1, and reservation indication information #1.

[0358] Among them, the application scope #1 can be used to indicate the cell to which user #1 belongs. For example, cell #1 can provide services for user #1. The intention activation policy #1 can be used to indicate the activation time period #1 of intention instance #1. The activation time period may include activation time #1 and deactivation time #1. It can be understood that this activation time period #1 is the same as the above-mentioned service guarantee time period #1.

[0359] The reservation indication information #1 can be used to indicate whether exclusive resources are allowed when executing intention instance #1. If the reservation indication information #1 is true, it can indicate that exclusive resources are 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 the resource reservation indication information #1 is false, it can indicate that exclusive resources are 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 embodiments of this application are introduced under the condition that the reservation indication information #1 is true.

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

[0361] Among them, the pre-evaluation system selection indication information #1 can be used to specify the pre-evaluation system to be used. For example, the pre-evaluation system selection indication information #1 can specify that the pre-evaluation system to be used is pre-evaluation system #1, etc., without limitation. It can be understood that if the pre-evaluation system selection indication information #1 is empty, or the intention creation request message #1 does not include the pre-evaluation system selection indication information #1, then the MnS Producer can default to calling internal components, such as perception, analysis, decision-making, etc. for pre-evaluation. For easy understanding, in scenario 1, the pre-evaluation system selection indication information #1 specifies that the pre-evaluation system to be used is pre-evaluation system #1 as an example for subsequent introduction.

[0362] The period information #1 can be used to indicate the execution of the first intention instance according to the reserved period. For example, if the reserved period is from Monday to Friday and the activation time period is from 19:00 to 22:00, then the MnS Producer can execute the first intention instance periodically at 19:00 - 22:00 from Monday to Friday, or guarantee the live broadcast service.

[0363] S603, the MnS Producer creates intention instance #1 and generates intention plan #1.

[0364] The MnS Producer can create a request message #1 according to the intention, create an intention instance #1, and generate an intention plan #1 based on the intention instance #1.

[0365] Among them, the intention plan #1 is one of at least one intention plan that can achieve all the expected goals of the intention instance #1, without limitation. The MnS Producer can save the intention plan #1, that is, the MnS Producer can save some configuration commands corresponding to the intention plan #1. The MnS Producer can also perform an intention feasibility check. If the intention instance #1 passes the intention feasibility check and the resource reservation indication #1 is True, then the MnS Producer proceeds with the resource preoccupation process, that is, executes the following step S604.

[0366] S604. The MnS Producer sends a resource evaluation request #1 to the pre-evaluation system #1.

[0367] Among them, the resource evaluation request #1 may include the intention plan #1, the expectation list #1, and the expected object information #1. The expectation list #1 can be used to indicate at least one intention expectation. Or rather, the expectation list #1 can indicate all the expectations of the intention instance #1. Or rather, the expectation list #1 can indicate all the expected goals of the intention instance #1. This expectation list #1 is the same as the above-mentioned service guarantee goal #1. That is, the expectation list #1 may include: the uplink throughput rate is greater than or equal to 5 Mb / s, and the uplink delay is less than or equal to 10 ms.

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

[0369] When the pre-evaluation system selection indication information #1 designates the pre-evaluation system to be used as the intention pre-evaluation system #1, the MnS Producer can send a resource evaluation request #1 to the pre-evaluation system #1 to request a resource pre-evaluation of the intention instance #1. Or rather, to request to obtain the resources required when the estimated intention plan #1 is executed to achieve: the uplink throughput rate is equal to 5 Mb / s, and the uplink delay is equal to 10 ms.

[0370] S605. The pre-evaluation system #1 obtains the resources #1.

[0371] The pre-evaluation system #1 can obtain the resources #1 required to achieve the uplink throughput rate equal to 5 Mb / s and the uplink delay equal to 10 ms by pre-executing the intention plan #1 according to the expectation list #1 and the expected object information #1.

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

[0373] S606. The pre - evaluation system #1 sends resource evaluation information #1 to the MnS Producer.

[0374] Among them, the resource evaluation information #1 may include Resource #1.

[0375] S607. The MnS Producer determines whether there is an intention conflict in the intention instance #1.

[0376] The MnS Producer can count the percentage of Resource #1 in the entire network resources during the activation time period #1.

[0377] If there is no resource greater than Resource #1 and not pre - occupied during the activation time period #1, then the intention instance #1 has an intention conflict with other intention instances. For example, during the activation time period #1, the intention instance #1 conflicts with the intention instance #2. That is, during the activation time period #1, the intention instance #1 fails to pre - occupy Resource #1, triggering the MnS Producer to execute the following step S609.

[0378] If there is a resource greater than Resource #1 and not pre - occupied during the activation time period #1, then the intention instance #1 has no intention conflict with other intention instances. That is, during the activation time period #1, the intention instance #1 successfully pre - occupies Resource #1, triggering the MnS Producer to execute the following step S609a1.

[0379] S608. The MnS Producer sends the intention report #1 to the MnS Consumer.

[0380] Among them, the intention report #1 may include the intention resource management status #1 and the failure reason #1.

[0381] The intention resource management status #1 may be an unreserved status to indicate that during the activation time period #1, the intention instance #1 fails to pre - occupy Resource #1.

[0382] The failure reason #1 may indicate the reason for the failure of the intention instance #1 to pre - occupy Resource #1. For example, during the activation time period #1, reasons such as insufficient resources or the resources have been pre - occupied during the activation time period, etc., so that the subsequent MnS Consumer can modify the intention according to the failure reason #1. For example, adjust the activation time period of the intention instance #1, etc., without limitation.

[0383] The MnS Producer can feedback the intention report #1 to the MnS Consumer through the intention report interface.

[0384] S609a1, MnS Producer pre-occupies Resource #1.

[0385] MnS Producer can pre-occupy Resource #1. For example, MnS Producer can mark that during Activation Period #1, Intention Instance #1 needs to occupy Resource #1.

[0386] S09a2, MnS Producer sends Intention Report #2 to MnS Consumer.

[0387] Among them, Intention Report #2 can include Intention Resource Management Status #2. Intention Resource Management Status #2 can be the reserved status to indicate that during Activation Period #1, Intention Instance #1 successfully pre-occupies Resource #1. MnS Producer can feedback Intention Report #2 to MnS Consumer through the intention report interface.

[0388] S610a1, when Activation Time #1 is reached, MnS Producer activates Intention Instance #1.

[0389] Exemplarily, when Activation Time #1 is reached, MnS Producer can activate Intention Instance #1 and occupy Resource #1 to execute Intention Plan #1, or in other words, occupy Resource #1 to send some configuration commands corresponding to Intention Plan #1 to Cell #1.

[0390] S610a2, MnS Producer sends Intention Report #3 to MnS Consumer.

[0391] Among them, Intention Report #3 can include Intention Resource Management Status #3. Intention Resource Management Status #3 can be the in-use status to indicate that Intention Instance #1 has been activated. MnS Producer can feedback Intention Report #3 to MnS Consumer through the intention report interface.

[0392] S611a1, MnS Consumer sends Indication Information #1 to MnS Producer.

[0393] The following takes the following two situations as examples to specifically introduce Indication Information #1.

[0394] Scenario a: The indication information #1 can be a modification request message #1 to request modification of the deactivation time of the intention instance #1. For example, it requests to modify the deactivation time #1 to the deactivation time #2 to achieve early or delayed deactivation of the intention instance #1. It can be understood that the deactivation time #2 is greater than or equal to the activation time #1. In the embodiments of the present application, the size relationship between the deactivation time #1 and the deactivation time #2 is not limited. For the convenience of understanding, the following takes the deactivation time #2 being less than the deactivation time #1 as an example for subsequent introduction.

[0395] Scenario b: The indication information #1 can be a deletion intention request message #1 to request deletion of the intention instance #1.

[0396] S611a2, the MnS Producer deactivates / deletes the intention instance #1.

[0397] Based on the above Scenario a, the MnS Producer can, according to the intention request message #1, deactivate the intention instance #1 after reaching the deactivation time #2. The MnS Producer can pause the execution of the intention plan #1 and release the resource #1.

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

[0399] S611a3, the MnS Producer sends an intention report #4 to the MnS Consumer.

[0400] Among them, the intention report #4 can include an intention resource management status #4 and a user service usage time #1. The user service usage time #1 can be the time interval between the start time and the end time when the user #1 uses the live service, so that the MnS Consumer can better learn the behavior of the user #1 and continuously improve the activation time period of the intention instance #1, and further accurately allocate network resources.

[0401] Exemplarily, based on the above Scenario a, the intention resource management status #4 can be a reserved status to indicate that within the activation time period #1, the intention instance #1 has successfully preoccupied the resource #1. It should be noted that the intention instance #1 executes periodically within the reserved period. In this case, the user service usage time #1 can be the time interval between the activation time #1 and the deactivation time #2.

[0402] Based on the above Scenario b, the intention resource management status #3 can be empty to indicate that the intention instance #1 has been deleted. In this case, the user service usage time #1 can be the time interval between the activation time #1 and the time when the deletion intention request message #1 is sent.

[0403] The MnS Producer can feedback Intent Report #4 to the MnS Consumer through the intent report interface.

[0404] S612a1, when the deactivation time #1 is reached, the MnS Producer deactivates Intent Instance #1.

[0405] Exemplarily, when the activation time #1 is reached, the MnS Producer can deactivate Intent Instance #1, the MnS Producer can pause the execution of Intent Scheme #1, and release Resource #1.

[0406] S612a2, the MnS Producer sends Intent Report #5 to the MnS Consumer.

[0407] Among them, Intent Report #5 can include Intent Resource Management Status #5 and User Service Usage Time #2.

[0408] Intent Resource Management Status #5 can be the reserved status.

[0409] User Service Usage Time #2 can be the time interval between the activation time #1 and the deactivation time #1.

[0410] In this way, in this 3GPP architecture, the MnS Consumer can make the intent instance execute asynchronously by configuring the intent activation policy (i.e., the activation time period). By specifying the activation time period of each intent instance, it is possible to avoid having too many concurrently executing intent instances. The MnS Consumer pre-occupies resources before executing the intent instance by configuring the resource reservation indication, which can perform resource evaluation and pre-occupation in advance, allocate network resources reasonably, accurately allocate limited network resources to the services that need to be guaranteed, ensure the service stability of the users that need to be guaranteed, and avoid conflicts when executing the intent instance.

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

[0412] Scenario 2:

[0413] Figure 7 This is the process schematic of the communication method provided by the embodiment of the present application. Figure 3 It mainly involves the interaction among the MnS Consumer (such as the second device above), the MnS Producer (such as the first device above), and the Intent Pre-evaluation System #1 (such as the third device above).

[0414] As shown in Figure 7 the method may include:

[0415] S701, the MnS Consumer obtains the subscription information.

[0416] S702, the MnS Consumer sends an intent creation request message #1 to the MnS Producer.

[0417] S703, the MnS Producer creates intent instance #1 and generates intent scheme #1.

[0418] S704, the MnS Producer sends a resource evaluation request #1 to the pre-evaluation system #1.

[0419] S705, the pre-evaluation system #1 obtains resource #1.

[0420] S706, the pre-evaluation system #1 sends resource evaluation information #1 to the MnS Producer.

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

[0422] If there are resources greater than resource #1 and not preoccupied during activation period #1, then there is no intent conflict between intent instance #1 and other intent instances. That is, within activation period #1, if intent instance #1 successfully preoccupies resource #1, then the above steps S609a1 - S612a2 can be executed. For reference and understanding, it will not be elaborated here.

[0423] If there are no resources greater than resource #1 and not preoccupied during activation period #1, then there is an intent conflict between intent instance #1 and other intent instances. For example, within activation period #1, there is an intent conflict between intent instance #1 and intent instance #2. That is, within activation period #1, if intent instance #1 fails to preoccupy resource #1, it triggers the MnS Producer to execute the following step S708.

[0424] S708, the MnS Producer processes the intent conflict.

[0425] The MnS Producer can process the conflict according to the priority of the intent instance. For example, there is an intent conflict between intent instance #1 and intent instance #2.

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

[0427] The following is a specific introduction by taking the following situation as an example.

[0428] Situation c1: As shown in (a) of Figure 8 , C < A < B < D.

[0429] That is to say, the activation time period #a includes the activation time period #1. In this case, as shown in (b) of Figure 8 , MnSProducer can recommend deactivating the intent instance #1, that is to say, MnS Producer can set A and B to 0 or non-existent.

[0430] Situation c2: As shown in (a) of Figure 9 , A < C < D < B.

[0431] That is to say, the activation time period #1 includes the activation time period #a. In this case, as shown in (b) of Figure 9 , MnSProducer can recommend executing the intent instance #1 in two segments, or rather, MnS Producer can configure two activation time periods for the intent instance #1, including the activation time period #b1 and the activation time period #b2. Among them, the activation time of the activation time period #b1 is A, the deactivation time is E, E is greater than A and less than or equal to C; the activation time of the activation time period #b2 is F, the deactivation time is B, F is greater than or equal to D and less than B.

[0432] Situation c3: As shown in (a) of Figure 10 , C < A < D < B.

[0433] That is to say, the activation time period #a and the activation time period #1 have an overlapping time period. In this case, as shown in (b) of Figure 10 , MnS Producer can recommend modifying the activation time #1 of the intent instance #1 to G, G is greater than or equal to D and less than B.

[0434] Situation 4: As shown in (a) of Figure 11 , A < C < B < D.

[0435] That is to say, the activation time period #a and the activation time period #1 have an overlapping time period. In this case, as shown in (b) of Figure 11 , MnS Producer can recommend modifying the deactivation time #1 of the intent instance #1 to H, H is greater than A and less than or equal to C.

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

[0437] S709, the MnS Producer sends Conflict Report #1 of Intentions to the MnS Consumer.

[0438] Among them, the Conflict Report #1 of Intentions may include conflict information of intentions to indicate that there is an intention conflict between Intention Instance #1 and Intention Instance #2.

[0439] The Conflict Report #1 of Intentions may also include the activation time period recommended by the MnS Producer for Intention Instance #1. The following is a specific introduction.

[0440] Based on the above situation c1, the activation time period recommended for Intention Instance #1 may be empty, that is, Intention Instance #1 is deactivated.

[0441] Based on the above situation c2, the activation time period recommended for Intention Instance #1 includes 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; the activation time of Activation Time Period #b2 is F, and the deactivation time is B.

[0442] Based on the above situation c3, the activation time period recommended for 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 B unchanged.

[0443] Based on the above situation c4, the activation time period recommended for 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 A unchanged.

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

[0445] The MnS Consumer may evaluate the intention conflict between Intention Instance #1 and Intention Instance #2 according to the Conflict Report #1 of Intentions and select a conflict resolution plan. Exemplarily, the MnS Consumer may determine to modify the activation time #1 and / or deactivation time #1 of Intention Instance #1 according to the recommended activation time period in the Conflict Report #1 of Intentions.

[0446] For easy understanding, taking the above situation c3 as an example, the MnS Consumer may determine to modify the activation time #1 of Intention Instance #1 from A to G to resolve the situation where there is an intention conflict between Intention Instance #1 and Intention Instance #2 within the activation time period #1.

[0447] S711, the MnS Consumer sends Modification Request Message #2 to the MnS Producer.

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

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

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

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

[0452] It can be understood that the specific implementation of this process is similar to the above steps S611a2 - S611a3, and can be referred to for understanding without further elaboration.

[0453] When the deactivation time B is reached, the MnS Producer may deactivate the intent instance #1, pause the execution of the intent scenario #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, and can be referred to for understanding without further elaboration.

[0454] In this way, in this 3GPP architecture, in the case of intent conflicts during the synchronous execution of intent instances, the MnS Producer may modify the activation time period of the intent instance where the intent conflict occurs according to the priority of the intent instance, so as to perform conflict handling in advance and avoid conflicts when executing the intent example.

[0455] Scenario 3:

[0456] Figure 12 The flowchart of the communication method provided by the embodiment of the present application Figure 4 It mainly involves the interaction between the intent owner (such as the above-mentioned second device), Non-RT RIC (such as the above-mentioned first functional entity), 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, Near-RT RIC, and XAPP1 together constitute the above-mentioned first device, and XAPP1 and XAPP2 are applications running on the Near-RT RIC.

[0457] As Figure 12 shown, the method may include:

[0458] S1201, the intent owner obtains the signing information.

[0459] S1202, the intent owner sends an intent creation request message #1 to the Non-RT RIC.

[0460] Among them, the intent creation request message #1 is the same as the intent creation request message #1 in step S602 above, which can be understood by reference and will not be elaborated.

[0461] S1203, the Non-RT RIC generates an A1 policy.

[0462] The Non-RT RIC can generate an A1 policy according to the received creation request message #1. Among them, the A1 policy is a declarative policy expression form, and the A1 policy can include policyTypeId, policyId, and policyObject. For specific introductions, reference can be made to the introduction in the above technical terms section and will not be elaborated.

[0463] It can be understood that the A1 policy and the above intent instance #1 can be mutually transformed without limitation.

[0464] S1204, the Non-RT RIC sends the A1 policy and reservation resource information to the Near-RT RIC.

[0465] Among them, the reservation resource information can include: service guarantee target #1, application scope #1, the identifier of user #1, the identifier of the live broadcast service, intent activation policy #1, and reservation indication information #1.

[0466] Optionally, the reservation resource information can also include: pre-evaluation system selection indication information #1 and / or cycle information #1. Suppose the pre-evaluation system selection indication information #1 specifies that the pre-evaluation system to be used is XAPP #2.

[0467] S1205, the Near-RT RIC sends the A1 policy to XAPP1.

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

[0469] S1206, XAPP1 generates an intent solution #1.

[0470] XAPP1 can translate the received A1 policy to generate Intent Scheme #1, and Intent Scheme #1 can be a control message for the E2 node. It can be understood that Intent Scheme #1 is one of at least one intent scheme that can achieve all the intent expectations of Intent Instance #1, without limitation. XAPP1 can save Intent Scheme #1, that is, the MnS Producer can save the control message for the E2 node corresponding to Intent Scheme #1.

[0471] At S1207, XAPP1 sends Resource Evaluation Request #1 to XAPP2.

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

[0473] Resource Evaluation Request #1 can include: Intent Scheme #1, the A1 policy target list, and A1 policy object information.

[0474] It can be understood that the above policyObject can include the scope of A1 policy application, the target of the A1 policy, and the resources of the A1 policy. The A1 policy target list is determined according to the target of the A1 policy and can include all the policy targets of the A1 policy; the A1 policy object information includes the scope of A1 policy application. For example, the A1 policy object information can be the information of the executed E2 node.

[0475] The A1 policy target list and the above Expectation List #1 can be converted to each other, and the scope of A1 policy application and the above Expectation Object Information #1 can be converted to each other, which will not be elaborated.

[0476] When the above Pre-evaluation System Selection Indication Information #1 specifies that the pre-evaluation system to be used is XAPP2, the MnS Producer can send Resource Evaluation Request #1 to XAPP2 to request the pre-execution of Intent Scheme #1 to obtain the resources required to achieve an uplink throughput of 5 Mb / s and an uplink latency of 10 ms.

[0477] At S1208, XAPP2 obtains Resource #1.

[0478] The pre-evaluation system #1 can, according to the Expectation List #1 and the Expectation Object Information #1, obtain the resources #1 required to achieve an uplink throughput of 5 Mb / s and an uplink latency of 10 ms by pre-executing Intent Scheme #1.

[0479] At S1209, XAPP2 sends Resource Evaluation Information #1 to the Near-RT RIC.

[0480] Among them, Resource Evaluation Information #1 can include Resource #1.

[0481] S1210, the Near-RT RIC determines whether there is an intention conflict in intention instance #1.

[0482] The Near-RT RIC can count the percentage of resource #1 in the entire network resources during activation period #1.

[0483] If there is no resource greater than resource #1 and not pre-occupied during activation period #1, then there is an intention conflict between intention instance #1 and other intention instances. For example, during activation period #1, there is an intention conflict between intention instance #1 and intention instance #2. That is, during activation period #1, the pre-occupation of resource #1 by intention instance #1 fails, triggering the MnS Producer to execute the following step S1211a1.

[0484] If there is a resource greater than resource #1 and not pre-occupied during activation period #1, then there is no intention conflict between intention instance #1 and other intention instances. That is, during activation period #1, the pre-occupation of resource #1 by intention instance #1 is successful, triggering the MnS Producer to execute the following step S1212a1.

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

[0486] Among them, the A1 policy feedback information #1 can include the A1 policy resource management status #1 and the failure reason #1.

[0487] It can be understood that the A1 policy resource management status #1 is the same or similar to the intention report #1 in step S609 above. That is, the A1 policy resource management status #1 is the same 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. For reference and understanding, it will not be elaborated.

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

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

[0490] Among them, the intention report #1 can include the intention resource management status #1 and the failure reason #1.

[0491] The intention resource management status #1 can be the unreserved state to indicate that during activation period #1, the pre-occupation of resource #1 by intention instance #1 fails.

[0492] The failure reason #1 can indicate the reason for the preoccupation failure of the intent instance #1 with the resource #1. For example, within the activation time period #1, the resource is insufficient or has been preoccupied during the activation time period, etc. This is used for the MnS Consumer to modify the intent based on this failure reason #1. For example, adjusting the activation time period of the intent instance #1, etc., without limitation.

[0493] The Non-RT RIC can convert the A1 policy feedback information #1 to obtain the intent report #1 and send this intent report to the intent owner.

[0494] S1212a1, the Near-RT RIC preoccupies the resource #1.

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

[0496] S1212a2, the Near-RT RIC sends the A1 policy feedback information #2 to the Non-RT RIC.

[0497] Among them, the A1 policy feedback information #2 can include the intent resource management status #2. It can be understood that the A1 policy feedback information #2 is the same as or similar to the above-mentioned intent report #2. That is, the 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, and can be understood by reference without further elaboration.

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

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

[0500] Among them, the intent report #2 can include the intent resource management status #2, and the intent resource management status #2 can be the reserved status to indicate that within the activation time period #1, the intent instance #1 has successfully preoccupied the resource #1.

[0501] The Non-RT RIC can convert the A1 policy feedback information #2 to obtain the intent report #2 and send this intent report to the intent owner.

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

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

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

[0505] When the activation time #1 is reached, XAPP1 can activate intent instance #1, occupy resource #1 to execute intent plan #1, or in other words, occupy resource #1 to send the control message corresponding to intent plan #1 to cell #1 for the E2 node.

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

[0507] It can be understood that when the activation time #1 is reached, XAPP1 can also deactivate intent instance #1, pause the execution of intent plan #1, and release resource #1. In this case, XAPP1 can also feedback a new intent report to the intent owner, such as the above-mentioned intent report #5. The implementation process of this process is similar to the above step S612a2, and can be understood by reference, without limitation.

[0508] The above combines Figures 4 - 12 has described in detail the communication method provided in this embodiment. The following combines Figures 13 - 14 to describe in detail the communication device for executing the communication method provided in this embodiment.

[0509] Figure 13 is a schematic structural diagram of the communication device provided in this embodiment Figure 1 . Exemplarily, as Figure 13 shown, the communication device 1300 includes: a transceiver module 1301 and a processing module 1302. For the sake of convenience of description, Figure 13 only the main components of this communication device are shown.

[0510] Among them, the transceiver module 1301 is used to execute the transceiver function of the method shown above Figure 5 , and the processing module 1302 is used to execute other functions of the method shown above Figure 5 except for the transceiver function.

[0511] For example, the transceiver module 1301 is configured to receive a first request message from a second device and send second information to the second device according to the first information. When the pre - occupation of the first resource is successful within the activation time period, the processing module 1302 is configured to occupy the first resource within the activation time period. The first request message is used to request the creation of a first intent instance corresponding to a 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 first information is used to indicate the first resources estimated to be occupied for completing each of the at least one intent expectations, and the second information is used to indicate whether the pre - occupation of the first resource is successful within the activation time period.

[0512] The transceiver module 1301 is configured to send a first request message to a 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 a 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 based on the first information, and the first information is used to indicate the first resources estimated to be occupied for completing each of the at least one intent expectations. The second information is used to indicate whether the pre - occupation of the first resource is successful within the activation time period. The transceiver module 1301 is configured to receive fifth information from the first device. The processing module 1302 is configured to send a third request message to the first device according to 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 a second activation time and / or a second de - activation time. The third request message is used to request to modify the activation time period according to the second activation time and / or the second de - activation time.

[0513] Optionally, the transceiver module 1301 may include a sending module ( Figure 13 not shown in the figure) and a receiving module ( Figure 13 not shown in the figure). 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.

[0514] Optionally, the communication device 1300 may further include a storage module ( Figure 13 not shown in the figure), and the storage module stores programs or instructions. When the processing module 1302 executes the programs or instructions, the communication device 1300 can perform the functions of the first device, the second device, or the third device in the above - mentioned method.

[0515] It can be understood that the communication device 1300 may be a device (such as the first device, the second device, or the third device), or a chip (system) or other components or assemblies that can be set in a device, or a device containing a device. The embodiments of the present application do not make any limitations in this regard.

[0516] In addition, for the technical effects of the communication device 1300, reference may be made to the technical effects of the communication method shown above, which will not be elaborated here.

[0517] Figure 14 Structural schematic of the communication device provided in this embodiment Figure 2 . Exemplarily, the communication device may be a terminal or a network device, or may also be a chip (system) or other components or assemblies that can be set in a terminal or a network device. As Figure 14 shown, 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. Among them, the processor 1401 is coupled to the memory 1402 and the transceiver 1403, and may be connected through a communication bus, for example.

[0518] The following Figure 14 will specifically introduce each component of the communication device 1400:

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

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

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

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

[0523] Among them, the storage 1402 is used to store the software program for implementing the solution of this embodiment and is controlled by the processor 1401 for execution. The specific implementation manner can refer to the above method embodiment and will not be elaborated here.

[0524] Optionally, the memory 1402 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 1402 can be integrated with the processor 1401 or exist independently and is coupled to the processor 1401 through the interface circuit of the communication device 1400 ( Figure 14 not shown in []). This embodiment does not make specific limitations on this.

[0525] The transceiver 1403 is used for communication with other communication devices. For example, when the communication device 1400 is a terminal, the transceiver 1403 can be used for communication with a network device or with another terminal device. Another example is that when the communication device 1400 is a network device, the transceiver 1403 can be used for communication with a terminal or with another network device.

[0526] Optionally, the transceiver 1403 can include a receiver and a transmitter ( Figure 14 not shown separately in []). Among them, the receiver is used to implement the receiving function, and the transmitter is used to implement the sending function.

[0527] Optionally, the transceiver 1403 can be integrated with the processor 1401 or exist independently and is coupled to the processor 1401 through the interface circuit of the communication device 1400 (Figure 14 is not shown) is coupled to the processor 1401, and this embodiment does not make specific limitations thereon.

[0528] It can be understood that Figure 14 the structure of the communication device 1400 shown in does not constitute a limitation on the communication device. The actual communication device may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0529] In addition, for the technical effects of the communication device 1400, reference may be made to the technical effects of the method described in the above method embodiments, and details are not described herein again.

[0530] 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 (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

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

[0532] The above embodiments can be implemented in whole or in part by software, hardware (such as circuits), firmware, or any combination thereof. 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 programs are loaded or executed on a computer, the processes or functions described in accordance with the embodiments 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 devices. 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 wired (such as infrared, wireless, microwave, etc.) means. 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 one or more collections of available media. The available media can be magnetic media (such as floppy disks, hard disks, magnetic tapes), optical media (such as DVDs), or semiconductor media. The semiconductor media can be a solid-state drive.

[0533] It should be understood that the term "and / or" in this document is merely a description of the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. Here, A and B can be singular or plural. Additionally, the character " / " in this document generally represents an "or" relationship between the associated objects before and after, but it may also represent an "and / or" relationship, which can be specifically understood by referring to the context.

[0534] In this embodiment, "at least one" means one or more, and "a plurality" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, and c can be single or multiple.

[0535] It should be understood that in various embodiments, the magnitudes of the sequence numbers of the above processes do not imply the order of execution. The order of execution of each process should be determined by its function and internal logic, and should not impose any limitation on the implementation process of this embodiment.

[0536] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this embodiment.

[0537] Those skilled in the art can 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 foregoing method embodiments, and will not be elaborated herein.

[0538] 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 only a logical function division, and there can be other division methods in actual implementation. For example, 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 displayed or discussed coupling or direct coupling or communication connection to each other can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be in an electrical, mechanical, or other form.

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

[0540] In addition, the functional units in each embodiment can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0541] When the above-mentioned 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, in essence, or the part that contributes to the prior art or a part of this technical solution can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in each embodiment. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0542] As described above, the above is only the specific implementation manner of this embodiment, but the protection scope of this embodiment is not limited thereto. Any person skilled in the art within the technical scope disclosed in this embodiment can easily think of changes or substitutions, which should all be covered by the protection scope of this embodiment. Therefore, the protection scope of this embodiment shall be subject to the protection scope of the claims.

Claims

1. A communication method, characterized in that, Including: A first device receives a first request message from a second device; wherein, the first request message is used to request the creation of a first intent instance corresponding to a 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 first information; wherein, the first information is used to indicate a first resource required to estimate the completion of each of the at least one intent expectation, and the second information is used to indicate whether the first resource is successfully preoccupied within the activation time period; When the first resource is successfully preoccupied within the activation time period, the first device occupies the first resource within the activation time period.

2. The method according to claim 1, wherein 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 of the first service and cycle information; wherein, the identifier is used to identify the first service, and the cycle information is used to indicate the execution of the first intent instance according to a reserved cycle.

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

5. The method according to claim 4, wherein 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 the first information according to the first intent plan.

6. The method according to claim 4, wherein 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 a third device; wherein, the second request message is used to request to obtain a resource required to estimate the completion of each of the at least one intent 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, wherein The second request message includes at least one of the following: the first intent plan, an expectation list, or expectation object information; Wherein, the expectation list is used to indicate the at least one intent expectation; the expectation object information is used to indicate an object for executing the first intent instance.

8. The method according to any one of claims 5-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 according to the first information.

9. The method according to claim 8, wherein When there is no intent conflict between the first intent instance and other intent instances, the method further includes: The first device saves the first intent plan; wherein, the first intent plan occupies the first resource within the activation time period.

10. The method according to claim 9, wherein The second information is used to indicate that the first resource is successfully preoccupied within the activation time period.

11. The method according to claim 9 or 10, characterized in that, The method further includes: When reaching the first activation time, the first device activates the first intent instance; The first device occupies the first resource to execute the first intent plan; 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-11, characterized in that, The method further includes: When the first deactivation time is reached, the first device deactivates the first intent instance; The first device suspends the execution of the first intent scenario and releases the first resource; The first device sends fourth information to the second device; wherein, the fourth information is used to indicate that the preoccupation of the first resource within the activation period is successful.

13. The method according to claim 8, wherein There is an intent conflict between the first intent instance and other intent instances, and the second information is used to indicate that the preoccupation of the first resource within the activation period fails.

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

15. The method according to claim 14, characterized in that, The method further 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 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 includes: 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 period according to the second activation time and / or the second deactivation time; The first device modifies the activation period according to the second activation time and / or the second deactivation time to obtain a modified activation period; The first device executes the first intent scenario within the modified activation period.

17. A communication method, characterized in that, Includes: The second device sends a first request message to the first device; wherein, the first request message is used to request to create a first intent instance corresponding to a first service, the first request message includes the activation 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 first information, and the first information is used to indicate the first resources required to estimate the completion of each of the at least one intent expectation; the second information is used to indicate whether the preoccupation of the first resource within the activation period is successful.

18. The method according to claim 17, wherein The activation 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 of the first service and cycle information; wherein, the identifier is used to identify the first service, and the cycle information is used to indicate the execution of the first intent instance 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 preoccupation of the first resource within the activation period is successful.

21. The method according to claim 20, wherein The method further includes: 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 includes: The second device receives fourth information from the first device; wherein, the fourth information is used to indicate that the pre - occupation of the first resource during the activation period is successful.

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

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

25. A communication method, characterized in that, It includes: A third device receives a second request message from a first device; wherein, the second request message is used to request to obtain the resources required to estimate the completion of each intention expectation in at least one intention expectation; The third device generates first information according to the second request message; the first information is used to indicate the first resources required to estimate the completion of each intention expectation in the at least one intention expectation; The third device sends the first information to the first device.

26. The method according to claim 25, wherein The second request message includes at least one of the following: a first intention scheme, an expectation list, or expectation object information; Wherein, the first intention scheme is used to implement each intention expectation in the at least one intention expectation; the expectation list is used to indicate the at least one intention expectation; the expectation object information is used to indicate the object executing the first intention instance.

27. A communication device, characterized in that, The device includes: a module for executing the method according to any one of claims 1 - 26.

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

29. A computer-readable storage medium, characterized in that, The computer - readable storage medium includes a computer program or instruction, and when the computer program or instruction runs on a computer, the computer is caused to execute the method according to any one of claims 1 - 26.

30. A computer program product, characterized in that, The computer program product includes a computer program or instruction, and when the computer program or instruction is run by a communication device, the method according to any one of claims 1 - 26 is caused to be executed.

Images