Resource release method, device, system, and storage medium

Abstract

The present disclosure relates to a resource release method, a device, a system, and a storage medium. The method may be executed by a first device. The method comprises: determining that there is a resource release requirement, and executing one or more resource release tasks. The first device is used to provide one or more computing power services for a second device, one of the resource release tasks is used for releasing a resource corresponding to one or more computing power services, and different resource release tasks correspond to different computing power services. The flexibility of resource release can be effectively improved, and the resource utilization efficiency can be improved.

Description

Resource release methods, devices, systems and storage media Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to resource release methods, devices, systems and storage media. Background Technology

[0002] With the rapid development of Artificial Intelligence (AI) and Machine Learning (ML) technologies, more and more organizations and individuals are using AI / ML models for various tasks, such as image recognition, speech recognition, natural language processing, and replacing traditional wireless communication algorithms. However, training and inferring these AI / ML models typically requires significant storage and computing resources.

[0003] Summary of the Invention

[0004] This disclosure presents resource release methods, devices, systems, and storage media.

[0005] According to a first aspect of the present disclosure, a resource release method is provided, executed by a first device, the method comprising:

[0006] If a resource release requirement is identified, execute one or more resource release tasks;

[0007] The first device is used to provide one or more computing power services to the second device, and a resource release task is used to release resources corresponding to one or more computing power services. Different resource release tasks correspond to different computing power services.

[0008] According to a second aspect of the embodiments of this disclosure, a resource release method is provided, executed by a second device, the method comprising:

[0009] Send first information to the first device, the first information being used to instruct the first device to perform one or more resource release tasks;

[0010] The first device is used to provide one or more computing power services to the second device, and a resource release task is used to release resources corresponding to one or more computing power services. Different resource release tasks correspond to different computing power services.

[0011] According to a third aspect of the present disclosure, a communication device is provided, comprising:

[0012] The processing module is configured to determine if there is a resource release requirement and execute one or more resource release tasks.

[0013] The first device is used to provide one or more computing power services to the second device, and a resource release task is used to release resources corresponding to one or more computing power services. Different resource release tasks correspond to different computing power services.

[0014] According to a fourth aspect of the embodiments of this disclosure, a communication device is provided, comprising:

[0015] The processing module is configured to send first information to the first device, the first information being used to instruct the first device to perform one or more resource release tasks;

[0016] The first device is used to provide one or more computing power services to the second device, and a resource release task is used to release resources corresponding to one or more computing power services. Different resource release tasks correspond to different computing power services.

[0017] According to a fifth aspect of the embodiments of this disclosure, a communication device is provided, comprising:

[0018] One or more processors;

[0019] The communication device is used to execute the resource release method described in the first or second aspect.

[0020] According to a sixth aspect of the present disclosure, a communication system is provided, including a first device and a second device, wherein the first device is configured to implement the resource release method described in the first aspect, and the second device is configured to implement the resource release method described in the second aspect.

[0021] According to a seventh aspect of the present disclosure, a storage medium is provided that stores instructions that, when executed on a communication device, cause the communication device to perform a resource release method as described in the first or second aspect.

[0022] According to an eighth aspect of the present disclosure, a computer program product is provided, including a computer program and / or instructions, which, when executed by a communication device, implement the resource release method as described in the first or second aspect.

[0023] In this embodiment of the disclosure, the first device can provide computing power services and resources to the second device, and can also release different resources by configuring one or more resource release tasks. When it is determined that there is a resource release requirement, the corresponding resource release task is executed to release the resources, which can effectively improve the flexibility of resource release and improve resource utilization efficiency. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0025] Figure 1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0026] Figure 2 is an exemplary interactive diagram of a resource release method provided according to an embodiment of the present disclosure.

[0027] Figure 3A is an exemplary flowchart of a resource release method provided according to an embodiment of the present disclosure.

[0028] Figure 3B is an exemplary flowchart of a resource release method provided according to an embodiment of the present disclosure.

[0029] Figure 3C is an exemplary flowchart of a resource release method provided according to an embodiment of the present disclosure.

[0030] Figure 3D is an exemplary flowchart of a resource release method provided according to an embodiment of the present disclosure.

[0031] Figure 3E is an exemplary flowchart of a resource release method provided according to an embodiment of the present disclosure.

[0032] Figure 4A is an exemplary flowchart of a resource release method provided according to an embodiment of the present disclosure.

[0033] Figure 4B is an exemplary flowchart of a resource release method provided according to an embodiment of the present disclosure.

[0034] Figure 4C is an exemplary flowchart of a resource release method provided according to an embodiment of the present disclosure.

[0035] Figure 4D is an exemplary flowchart of a resource release method provided according to an embodiment of the present disclosure.

[0036] Figure 5 is an exemplary flowchart of a resource release method provided according to an embodiment of the present disclosure.

[0037] Figure 6A is an exemplary structural diagram of a first device provided according to an embodiment of the present disclosure.

[0038] Figure 6B is an exemplary structural diagram of a second device provided according to an embodiment of the present disclosure.

[0039] Figure 7A is an exemplary structural diagram of a communication device provided according to an embodiment of the present disclosure.

[0040] Figure 7B is an exemplary structural diagram of a communication device provided according to an embodiment of the present disclosure. Detailed Implementation

[0041] This disclosure presents resource release methods, devices, systems, and storage media.

[0042] In a first aspect, embodiments of this disclosure propose a resource release method, executed by a first device, the method comprising:

[0043] If a resource release requirement is identified, execute one or more resource release tasks;

[0044] The first device is used to provide one or more computing power services to the second device, and a resource release task is used to release resources corresponding to one or more computing power services. Different resource release tasks correspond to different computing power services.

[0045] In the above embodiments, the first device can provide computing power services and resources to the second device, and can also release different resources by configuring one or more resource release tasks. When it is determined that there is a resource release requirement, the corresponding resource release task is executed to release the resources, which can effectively improve the flexibility of resource release and improve resource utilization efficiency.

[0046] In conjunction with some embodiments of the first aspect, in some embodiments, the first device and the second device share computing power, and the second device is used to provide one or more of the computing power services to the first device.

[0047] In the above embodiments, not only can the first device provide computing power services to the second device, but the second device can also provide computing power services to the first device, effectively improving the utilization efficiency of resources.

[0048] In conjunction with some embodiments of the first aspect, in some embodiments, the first device is a network device and the second device is a terminal device; or,

[0049] The first device is a terminal device, and the second device is a network device;

[0050] The number of terminal devices is one or more.

[0051] In conjunction with some embodiments of the first aspect, in some embodiments, the resources corresponding to the computing power service include at least one of storage resources, communication transmission resources, and computing power resources;

[0052] The resource release task includes at least one of the following:

[0053] Storage resource release task;

[0054] Communication transmission resource release task;

[0055] Task to release computing resources.

[0056] In the above embodiments, the first device can provide various resources to other devices, and the first device can also release various resources by configuring corresponding resource release tasks, thus ensuring the flexibility of resource release.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, the resource corresponding to each computing power service includes at least one sub-resource, and each resource release task includes at least one sub-release task.

[0058] One sub-release task is used to release one or more sub-resources, and different sub-release tasks correspond to different sub-resources.

[0059] In the above embodiments, resources can be further divided, and corresponding sub-release tasks can be configured to release different sub-resources, thereby further improving the flexibility of resource release.

[0060] In conjunction with some embodiments of the first aspect, in some embodiments, different resource release tasks have different task identifiers, and / or, different sub-release tasks have different sub-task identifiers.

[0061] In the above embodiments, corresponding task identifiers and sub-task identifiers can be configured for each resource release task and sub-release task, which can effectively reduce the communication overhead between the first device and the second device while ensuring the reliability of information interaction.

[0062] In conjunction with some embodiments of the first aspect, in some embodiments, determining that a resource release requirement exists and executing one or more resource release tasks includes:

[0063] Receive first information sent by the second device, the first information including at least one task identifier and / or at least one subtask identifier;

[0064] Execute the resource release task corresponding to each task identifier included in the first information, and / or execute the sub-release task corresponding to each sub-task identifier included in the first information.

[0065] In the above embodiments, the first device can release resources by receiving a release request or instruction sent by the second device, which can effectively ensure the reliability of resource release.

[0066] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is sent when the second device determines that the first resource is no longer needed, and the first information includes a task identifier and / or a sub-task identifier corresponding to the first resource, and the first resource includes at least one sub-resource corresponding to at least one computing power service provided by the first device.

[0067] In conjunction with some embodiments of the first aspect, in some embodiments, the second device further provides one or more of the computing power services to the first device, the method comprising:

[0068] If it is determined that the second resource provided by the second device is no longer needed, second information is sent to the second device. The second information includes the task identifier and / or subtask identifier corresponding to the second resource. The second resource includes at least one sub-resource corresponding to at least one computing power service provided by the second device.

[0069] In conjunction with some embodiments of the first aspect, in some embodiments, determining that a resource release requirement exists and executing one or more resource release tasks includes:

[0070] If resources are insufficient, execute the resource release task corresponding to each computing power service provided by the first device, and / or the sub-release task corresponding to each sub-resource provided by the first device; or...

[0071] If resources are insufficient, execute the N lowest priority resource release tasks and / or the M lowest priority sub-release tasks, where N is less than or equal to the total number of resource release tasks and M is less than or equal to the total number of sub-release tasks.

[0072] In the above embodiments, the first device can also execute resource release tasks that need to be performed when resources are insufficient, effectively ensuring the flexibility of resource release.

[0073] In conjunction with some embodiments of the first aspect, in some embodiments, determining that a resource release requirement exists and executing one or more resource release tasks includes:

[0074] Receive third information sent by the second device, the third information including at least one task identifier and / or at least one subtask identifier;

[0075] If resources are determined to be insufficient, resource release tasks and / or sub-resource release tasks are executed sequentially according to the priority corresponding to each task identifier included in the third information, and / or the priority corresponding to each sub-task identifier included in the third information, until the resources meet the demand.

[0076] In conjunction with some embodiments of the first aspect, in some embodiments, the third information is further used to indicate the priority corresponding to each task identifier and / or each subtask identifier in the third information.

[0077] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0078] If resources are insufficient, a fourth message is sent to the second device, which instructs the first device to perform one or more resource release tasks.

[0079] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes:

[0080] Send a fifth message to the second device, the fifth message including at least one of the following:

[0081] The response information is used to indicate that the first device has executed one or more resource release tasks based on the first information sent by the second device;

[0082] The first identification information includes the task identifier corresponding to the resource release task that the first device has completed and / or the sub-task identifier corresponding to the sub-release task that has been completed.

[0083] The second identification information includes the task identifier corresponding to the resource release task that the first device did not execute and / or the sub-task identifier corresponding to the sub-release task that was not executed.

[0084] In conjunction with some embodiments of the first aspect, in some embodiments, the first device and the second device share computing power;

[0085] The fifth information is also used to instruct the second device to execute the resource release task corresponding to the task identifier included in the first identification information, and / or the sub-release task corresponding to the sub-task identifier included in the first identification information.

[0086] In the above embodiments, when the first device and the second device share resources, they can release the resources corresponding to the same resource release task and / or sub-release task on both sides based on the fifth information mentioned above.

[0087] Secondly, embodiments of this disclosure propose a resource release method, executed by a second device, the method comprising:

[0088] Send first information to the first device, the first information being used to instruct the first device to perform one or more resource release tasks;

[0089] The first device is used to provide one or more computing power services to the second device, and a resource release task is used to release resources corresponding to one or more computing power services. Different resource release tasks correspond to different computing power services.

[0090] In conjunction with some embodiments of the second aspect, in some embodiments, the first device and the second device share computing power, and the second device is used to provide one or more of the computing power services to the first device.

[0091] In conjunction with some embodiments of the second aspect, in some embodiments, the first device is a network device and the second device is a terminal; or,

[0092] The first device is a terminal, and the second device is a network device.

[0093] In conjunction with some embodiments of the second aspect, in some embodiments, the resources corresponding to the computing power service include at least one of storage resources, communication transmission resources, and computing power resources;

[0094] The resource release task includes at least one of the following:

[0095] Storage resource release task;

[0096] Communication transmission resource release task;

[0097] Task to release computing resources.

[0098] In conjunction with some embodiments of the second aspect, in some embodiments, the resource corresponding to each computing power service includes at least one sub-resource, and each resource release task includes at least one sub-release task.

[0099] One sub-release task is used to release one or more sub-resources, and different sub-release tasks correspond to different sub-resources.

[0100] In conjunction with some embodiments of the second aspect, in some embodiments, different release tasks have different task identifiers, and / or, different sub-release tasks have different sub-task identifiers.

[0101] In conjunction with some embodiments of the second aspect, in some embodiments, the first information includes at least one task identifier and / or at least one subtask identifier;

[0102] The first information is used to instruct the first device to execute the resource release task corresponding to each task identifier included in the first information, and / or to execute the sub-release task corresponding to each sub-task identifier included in the first information.

[0103] In conjunction with some embodiments of the second aspect, in some embodiments, sending the first information to the first device includes:

[0104] Once it is determined that the first resource is no longer needed, the first information is sent to the first device. The first information includes the task identifier and / or subtask identifier corresponding to the first resource. The first resource includes at least one sub-resource corresponding to at least one computing power service provided by the first device.

[0105] In conjunction with some embodiments of the second aspect, in some embodiments, the second device further provides one or more computing power services to the first device, the method comprising:

[0106] The system receives second information sent by the first device. The second information is sent when the first device determines that it no longer needs the second resource provided by the second device. The second information includes a task identifier and / or a subtask identifier corresponding to the second resource. The second resource includes at least one sub-resource corresponding to at least one computing power service provided by the second device.

[0107] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0108] Send third information to the first device, the third information including at least one task identifier and / or at least one subtask identifier;

[0109] The third information is used by the first device to execute one or more resource release tasks when it determines that resources are insufficient.

[0110] In conjunction with some embodiments of the second aspect, in some embodiments, the third information is further used to indicate the priority corresponding to each task identifier and / or each subtask identifier in the third information.

[0111] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0112] The device receives a fourth message sent by the first device when it determines that resources are insufficient. The fourth message is used to instruct the first device to execute one or more resource release tasks.

[0113] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0114] The fifth message sent by the first device is received, and the fifth message includes at least one of the following:

[0115] The response information is used to indicate that the first device has executed one or more resource release tasks based on the first information sent by the second device;

[0116] The first identification information includes the task identifier corresponding to the resource release task that the first device has completed and / or the sub-task identifier corresponding to the sub-release task that has been completed.

[0117] The second identification information includes the task identifier corresponding to the resource release task that the first device did not execute and / or the sub-task identifier corresponding to the sub-release task that was not executed.

[0118] In conjunction with some embodiments of the second aspect, in some embodiments, the second device is used to provide one or more of the computing power services to the first device;

[0119] The method further includes:

[0120] Execute the resource release task corresponding to the task identifier included in the first identification information, and / or the sub-release task corresponding to the sub-task identifier included in the first identification information.

[0121] Thirdly, embodiments of this disclosure provide a communication device, including:

[0122] The processing module is configured to determine if there is a resource release requirement and execute one or more resource release tasks.

[0123] The first device is used to provide one or more computing power services to the second device, and a resource release task is used to release resources corresponding to one or more computing power services. Different resource release tasks correspond to different computing power services.

[0124] Fourthly, embodiments of this disclosure provide a communication device, comprising:

[0125] The processing module is configured to send first information to the first device, the first information being used to instruct the first device to perform one or more resource release tasks;

[0126] The first device is used to provide one or more computing power services to the second device, and a resource release task is used to release resources corresponding to one or more computing power services. Different resource release tasks correspond to different computing power services.

[0127] Fifthly, embodiments of this disclosure provide a communication device, comprising:

[0128] One or more processors;

[0129] The communication device is used to execute the resource release method described in the first or second aspect.

[0130] In a sixth aspect, embodiments of this disclosure provide a communication system comprising: a first device and a second device; wherein the second device is configured to perform the method described in the optional implementation of the second aspect, and the first device is configured to perform the method described in the optional implementation of the first aspect.

[0131] In a seventh aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method as described in the optional implementations of the first and second aspects.

[0132] Eighthly, embodiments of this disclosure provide a computer program product, including a computer program and / or instructions, which, when executed by a communication device, cause the communication device to perform the method as described in the optional implementations of the first and second aspects.

[0133] In a ninth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in alternative implementations of the first and second aspects.

[0134] In a tenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to optional implementations of the first and second aspects above.

[0135] It is understood that the first device, the second device, the communication system, the storage medium, the program product, the computer program, the chip, or the chip system described above are all used to perform the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0136] This disclosure provides a resource release method, apparatus, system, and storage medium. In some embodiments, the terms "resource release method" and "information processing method," "communication method," etc., can be used interchangeably; the terms "resource release device" and "information processing device," "communication device," etc., can be used interchangeably; and the terms "information processing system," "communication system," etc., can be used interchangeably.

[0137] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0138] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0139] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0140] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0141] In the embodiments disclosed herein, "multiple" refers to two or more.

[0142] In some embodiments, the terms “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0143] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0144] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0145] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0146] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0147] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0148] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0149] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0150] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0151] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0152] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0153] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0154] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0155] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0156] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0157] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0158] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0159] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1, the communication system 100 includes a first device 101 and a second device 102.

[0160] In some embodiments, the first device 101 is a network device and the second device 102 is a terminal device. In other embodiments, the first device 101 is a terminal device and the second device 102 is a network device.

[0161] In some embodiments, the terminal device includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0162] In some embodiments, network devices may include access network devices and core network devices.

[0163] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system.

[0164] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0165] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0166] In some embodiments, the core network equipment can be a single device, including a first network element, a second network element, etc., or it can be multiple devices or a group of devices, each including all or part of the first network element, the second network element, etc. Network elements can be virtual or physical. The core network includes, for example, at least one of the Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

[0167] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0168] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0169] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0170] In communication scenarios, AI / ML models can be used for various tasks, such as image recognition, speech recognition, natural language processing, and as alternatives to traditional wireless communication algorithms. However, training and inference of these AI models typically require significant computational resources.

[0171] In this regard, one embodiment utilizes computing power sharing to meet the corresponding computing resource requirements. Computing power sharing refers to opening up the idle computing power of multiple computing resources (such as servers, GPUs, TPUs, etc.) to other organizations or individuals for use in AI model inference tasks. Computing power sharing provides a flexible and efficient solution for AI model inference tasks, contributing to the development and application of AI technology.

[0172] In some embodiments, computing power sharing may be applied in the following four scenarios:

[0173] Scenario 1: Network side opens up computing power to terminals.

[0174] The network side provides computing power services to the terminal, such as using models deployed on the network side to provide computing power services for AI / ML model inference or model training to the terminal.

[0175] Scenario 2: Terminals open their computing power to the network.

[0176] The terminal provides computing power services to the network, such as participating in network-initiated federated learning according to the network's requirements, and providing AI / ML model training and model inference tasks to the network.

[0177] Scenario 3: Computing power sharing / collaboration between terminals.

[0178] Due to hardware resource limitations or other constraints, some terminals cannot apply AI / ML models. However, other terminals can provide AI / ML model applications. Terminals with strong computing power can provide computing services to terminals with weaker computing power. For example, terminals with strong computing power, such as mobile phones or cars, can provide AI / ML model inference services to other wearable products, such as watches, which have weaker computing power.

[0179] Scenario 4: Terminal and network perform computing power collaboration.

[0180] Some service types require collaboration between the terminal and the network. For example, AI / ML-based CSI compressed feedback includes both terminal-side and network-side models, which require collaboration between the two to complete the model training or inference.

[0181] In the above scenarios, if the network or terminal provides computing power services to other devices, it needs to provide certain computing resources for AI / ML model inference or training. When the device no longer needs the service, or due to reasons such as the service period expiring, the network or terminal must release the computing resources previously allocated for providing the computing power service.

[0182] It is understandable that while allocating computing power, other resources such as storage, network, and communication resources between the network and the terminal may also be allocated. Assuming the network provides computing power to the terminal, how the network releases these resources after receiving a request from the terminal to release computing power is a problem that needs to be solved.

[0183] In response, some embodiments of this disclosure propose possible ways to release allocated computing resources, storage resources, and communication resources for computing power sharing services, so as to reduce signaling overhead between terminals and networks while accurately releasing resources.

[0184] In some embodiments, the computing power of the first device and the second device is shared, such as when the computing power of the terminal and the network device is shared, which can also be referred to as the first device and the second device sharing computing power.

[0185] Figure 2 is an interactive schematic diagram of a resource release method according to an embodiment of the present disclosure. As shown in Figure 2, the embodiments of the present disclosure relate to a resource release method, which includes:

[0186] Step S2101: The second device sends the first information to the first device.

[0187] In some embodiments, the first device may provide one or more computing power services to the second device. Optionally, each computing power service may correspond to certain resources, that is, the first device may allocate certain resources to the second device to implement the corresponding computing power service.

[0188] In some embodiments, the first device is a network device and the second device is a terminal device; or, the first device is a terminal device and the second device is a network device. Optionally, the number of terminal devices may be one or more.

[0189] For example, a network device can provide one or more computing services and corresponding resources to one or more terminal devices, or one or more terminals can provide one or more computing services and corresponding resources to the network device.

[0190] In some embodiments, the resources corresponding to the computing power service include at least one of storage resources, communication transmission resources, and computing power resources. For example, a first device can provide some computing power services to a second device so that the second device can use the first device to train an AI / ML model. For instance, the first device can provide computing power service 1, computing power service 2, and computing power service 3 to the second device. For computing power service 1, the first device can allocate certain storage resources to the second device for storing training data. For computing power service 2, the first device can also allocate certain communication transmission resources for transmitting the training dataset and the model. For computing power service 3, the first device can allocate certain computing power resources for model training.

[0191] Optionally, the resources corresponding to a computing power service may also include one or more sub-resources. For example, the storage resources corresponding to computing power service 1 may include sub-storage resources for storing datasets and sub-storage resources for storing AI / ML models.

[0192] In some embodiments, the first device may configure one or more resource release services for one or more computing power services it provides to the second device. Optionally, a resource release service is used to release resources corresponding to one or more computing power services. Optionally, the computing power services corresponding to a resource release service are different. Optionally, different resource release tasks have different task identifiers.

[0193] For example, the first device provides computing power service 1, computing power service 2, and computing power service 3 to the second device. The resource corresponding to computing power service 1 is resource 1 (such as the storage resource used to store training data in the example above), the resource corresponding to computing power service 2 is resource 2 (such as the communication transmission resource used to transmit training datasets and models in the example above), and the resource corresponding to computing power service 3 is resource 3 (such as the computing power resource used for model training in the example above). The first device can be configured with resource release task 1, resource release task 2, and resource release task 3. Resource release task 1 can be used to release resources 1 and 2, resource release task 2 can be used to release resource 2, and resource release task 3 can be used to release resources 1 and 3.

[0194] In some embodiments, a resource release task may include at least one sub-release task, wherein a sub-release task is used to release one or more sub-resources, and different sub-release tasks correspond to different sub-resources. Optionally, different sub-release tasks have different sub-task identifiers.

[0195] In some embodiments, a resource release task includes at least one of the following: a storage resource release task; a communication transmission resource release task; and a computing power resource release task. Optionally, a resource release task can be used to release one or more of storage resources, communication transmission resources, and computing power resources.

[0196] Optionally, the storage resource release task can be used, for example, to clear the cache. Optionally, the communication resource release task can be used, for example, to close unnecessary connections, or to stop scheduling corresponding uplink or downlink transmission resources for a second device. Optionally, the computing resource release task can be used, for example, to suspend corresponding computing tasks, such as interrupting the corresponding computing process.

[0197] For example, the first device provides computing power service 2 as described in the previous example to the second device. For the computing power service 2, the first device allocates certain communication transmission resources to the second device. The communication transmission resources may include uplink transmission resources (e.g., identified as sub-resource 1) and downlink transmission resources (e.g., identified as sub-resource 2). The first device is also configured with a resource release task (e.g., resource release task 2 in the above example) for releasing the communication transmission resources. The resource release task 2 may include sub-release task 1 and sub-release task 2. Sub-release task 1 can be used to release sub-resource 1, and sub-release task 2 can be used to release sub-resource 1 and sub-resource 2.

[0198] In some embodiments, the first information is used to request or instruct the first device to release corresponding resources. Optionally, the first information includes at least one task identifier and / or at least one subtask identifier.

[0199] For example, the first information may include the task identifier corresponding to resource release task 3, and the subtask identifier corresponding to sub-release task 1 in resource release task 2. For example, the first information may be represented as {{Task ID 2, Sub_task ID 1}, Task ID 3}. In this case, the second device can request (or instruct) the first device to release resource 1, resource 3, and sub-resource 1 through the first information.

[0200] In some embodiments, the first information may be sent when the second device determines that the first resource is no longer needed. Optionally, the second device sends the first information after determining that the first resource is no longer needed. Optionally, the first information includes a task identifier and / or a subtask identifier corresponding to the first resource. Optionally, the first resource includes at least one sub-resource corresponding to at least one computing power service provided by the first device.

[0201] It is understandable that the resource release task corresponding to the task identifier included in the first information, and / or the sub-release task corresponding to the sub-task identifier, can be used to release the first resource.

[0202] For example, if the second device determines that the first device has completed the model training for the model and no longer needs resource 1, resource 3 and sub-resource 1 in the above example, then the first resource can include resource 1, resource 3 and sub-resource 1, and the second device can send the corresponding first information to request or instruct the first device to release resource 1, resource 3 and sub-resource 1.

[0203] In some embodiments, the first information may also be referred to as "release instruction information", "release request information", etc., and the name is not limited in this disclosure.

[0204] In some embodiments, the first device receives first information sent by the second device. Optionally, after receiving the first information, the first device executes step S2102. Optionally, the first device executes step S2102 in response to the instruction of the first information. Optionally, the first device agrees to the request of the first information and executes step S2102. Optionally, the first device disagrees with the request of the first information and sends a corresponding response message to reject the second device's request for resource release.

[0205] In step S2102, the first device executes one or more resource release tasks based on the first information.

[0206] In some embodiments, the first device executes a resource release task corresponding to each task identifier included in the first information, and / or executes a sub-release task corresponding to each sub-task identifier included in the first information.

[0207] For example, the first information includes the task identifier corresponding to resource release task 3 and the sub-task identifier corresponding to sub-release task 1 in resource release task 2. The first device can then execute resource release task 3 and sub-release task 1 in resource release task 2.

[0208] Step S2103: The first device sends the second information to the second device.

[0209] In some embodiments, the first device and the second device share computing power. Optionally, the second device also provides one or more computing power services to the first device.

[0210] In some embodiments, the first device determines that it no longer needs the resources corresponding to the second computing power service provided by the second device, and sends the second information to the second device.

[0211] For example, in an AI / ML-based CSI compressed feedback scenario, the CSI compressed feedback process requires the use of both a terminal-side model and a network-side model, necessitating their collaboration for model training or inference. In this process, either the network side or the terminal side provides computing power services to other devices and also provides certain computing resources to each other for AI / ML model inference or training. That is, both sides can provide each other with one or more computing power services and corresponding resources.

[0212] In some embodiments, when the second device provides one or more computing power services to the first device, it may also configure corresponding resource release tasks and / or sub-release tasks. Optional implementations can be found in the relevant content of step S2101, and will not be repeated here.

[0213] Furthermore, the alternative implementation of the first device sending the second information to the second device can also be found in the parts related to steps S2101 and S2102, which will not be repeated here.

[0214] In some embodiments, the second information may also be referred to as "release instruction information", "release request information", etc., and the name is not limited in this disclosure.

[0215] In step S2104, the first device determines that resources are insufficient and sends the fourth message to the second device.

[0216] In some embodiments, the first device determines that one or more of the storage resources, communication transmission resources, and computing power resources are insufficient, and sends a fourth message to the second device.

[0217] In some embodiments, the fourth information is used to instruct the first device to perform one or more resource release tasks. Optionally, the fourth information is used to indicate that the first device has insufficient resources.

[0218] In some embodiments, the first device determines that storage resources are insufficient and sends fourth information indicating insufficient storage resources to the second device. Optionally, the first device determines that communication transmission resources are insufficient and sends fourth information indicating insufficient communication resources to the second device. Optionally, the first device determines that computing power resources are insufficient and sends fourth information indicating insufficient computing power resources to the second device.

[0219] In some embodiments, the first device determines that storage resources are insufficient and sends fourth information instructing the first device to release storage resources. Optionally, the first device determines that communication transmission resources are insufficient and sends fourth information to the second device instructing the first device to release communication resources. Optionally, the first device determines that computing power resources are insufficient and sends fourth information to the second device instructing the first device to release computing power resources.

[0220] In some embodiments, after the first device sends the fourth information, step S2106 is executed.

[0221] In some embodiments, the fourth information is used to request the first device to send the third information. Optionally, after sending the fourth information, the first device expects to receive the third information from the second device.

[0222] In some embodiments, the fourth information may also be referred to as "resource release notification", "release request information", etc., and the name is not limited in this disclosure.

[0223] In step S2105, the second device sends third information to the first device.

[0224] In some embodiments, the third information is used to indicate candidate resource release tasks and / or candidate sub-release tasks. Optionally, the third information includes at least one task identifier and / or at least one sub-task identifier.

[0225] The resources corresponding to the candidate resource release tasks and / or candidate sub-release tasks, that is, the resources released by the first device when executing these tasks, can be resources that can be released by the second device.

[0226] In some embodiments, the third information is further used to indicate the priority corresponding to each task identifier and / or each subtask identifier in the third information. Optionally, the third information is used to indicate the priority of the candidate resource release task and / or the priority of the candidate sub-release task.

[0227] Optionally, the priority of candidate resource release tasks and / or the priority of candidate sub-release tasks can be configured based on the importance of the corresponding resources. Optionally, the priority of candidate resource release tasks and / or the priority of candidate sub-release tasks can be predefined.

[0228] In some embodiments, step S2105 is optional. Optionally, the candidate resource release task and / or candidate sub-release task can be predefined, that is, the first device can determine the corresponding candidate resource release task and / or candidate sub-release task itself. Optionally, each resource release task is a candidate resource release task, and / or each sub-release task is a candidate sub-release task, that is, the resource corresponding to each resource release task or sub-release task is releaseable for the second device.

[0229] In some embodiments, the third information may be referred to as "priority indication information", "candidate task indication information", etc., and this disclosure does not limit it.

[0230] In some embodiments, the first device receives third information sent by the second device. Optionally, the first device performs step S2106 based on the third information.

[0231] In step S2106, the first device determines that resources are insufficient and executes one or more resource release tasks.

[0232] In some embodiments, if the first device determines that resources are insufficient, it executes a resource release task corresponding to each computing power service provided by the first device, and / or a sub-release task corresponding to each sub-resource provided by the first device. Optionally, when the first device determines that resources are insufficient, it may release all resources allocated to the second device.

[0233] In some embodiments, if the first device determines that storage resources are insufficient, it executes a corresponding resource release task to release all or part of the storage resources provided to the second device. Optionally, if the first device determines that communication transmission resources are insufficient, it executes a corresponding resource release task to release all or part of the communication transmission resources provided to the second device. Optionally, if the first device determines that computing power resources are insufficient, it executes a corresponding resource release task to release all or part of the computing power resources provided to the second device.

[0234] In some embodiments, the first device determines that resources are insufficient and executes the N lowest priority resource release tasks and / or the M lowest priority sub-release tasks, wherein N is less than or equal to the total number of resource release tasks and M is less than or equal to the total number of sub-release tasks.

[0235] For example, if the first device is configured with resource release task 1, resource release task 2 and resource release task 3, and resource release task 1 has the highest priority and resource release task 3 has the lowest priority, when the first device determines that resources are insufficient, it can execute resource release task 3 to release the corresponding resources.

[0236] In some embodiments, if the first device determines that resources are insufficient, it may execute resource release tasks and / or sub-release tasks sequentially according to the priority of each task identifier (i.e., resource release task) and / or sub-task identifier (i.e., sub-release task).

[0237] For example, if the first device is configured with resource release task 1, resource release task 2 and resource release task 3, and resource release task 1 has the highest priority and resource release task 3 has the lowest priority, when the first device determines that resources are insufficient, resource release task 3 can be executed first to release the corresponding resources. If the first device still determines that resources are insufficient, resource release task 2 can be executed further.

[0238] In some embodiments, step S2106 is performed based on third information. Optionally, the first device determines that resources are insufficient and, based on the priority corresponding to each task identifier included in the third information, and / or the priority corresponding to each sub-task identifier included in the third information, sequentially executes resource release tasks and / or sub-resource release tasks until the resources meet the demand.

[0239] For example, if the first device is configured with resource release task 1, resource release task 2, resource release task 3 and resource release task 4, the third information includes the task identifiers corresponding to resource release task 1, resource release task 2 and resource release task 3, and the third information indicates that resource release task 1 has the highest priority and resource release task 3 has the lowest priority. When the first device determines that resources are insufficient, resource release task 3 can be executed first to release the corresponding resources. If the first device still determines that resources are insufficient, resource release task 2 can be executed further.

[0240] Step S2107: The first device sends the fifth information to the second device.

[0241] In some embodiments, the fifth information is used to indicate resources that the first device has released or has not released. Optionally, the fifth information is used by the first device to respond to the first information.

[0242] In some embodiments, the fifth information includes at least one of the following: response information, which indicates that the first device has executed one or more resource release tasks according to the first information sent by the second device; first identification information, which includes task identifiers corresponding to resource release tasks completed by the first device and / or subtask identifiers corresponding to completed sub-release tasks; and second identification information, which includes task identifiers corresponding to resource release tasks not executed by the first device and / or subtask identifiers corresponding to sub-release tasks not executed.

[0243] In some embodiments, step S2107 may be executed by the first device after receiving the first information, or it may be executed by the first device after executing step S2102 or step S2106.

[0244] In some embodiments, if step S2107 is executed after the first device executes step S2106, the fifth information may not include the response information described above.

[0245] In some embodiments, the first device and the second device share resources, and the second device also provides the first device with one or more computing power services and corresponding resources. The fifth information is also used to instruct the second device to perform a resource release task corresponding to the first device. Optionally, after receiving the fifth information sent by the first device, the second device executes step S2108.

[0246] In some embodiments, the fifth information is further used to instruct the second device to execute a resource release task corresponding to the task identifier included in the first identification information, and / or a sub-release task corresponding to the sub-task identifier included in the first identification information. It is understood that the first device and the second device can predefine unified task identifiers and / or sub-task identifiers for their respective configured resource release tasks and / or sub-release tasks, so that the first device and the second device can execute corresponding release tasks based on the same task identifiers and / or sub-task identifiers.

[0247] For example, suppose a terminal and a network device collaboratively train a two-sided model. The terminal trains the CSI generation partial model, and the network trains the CSI recovery model. Assuming the model training is complete and the trained model has been loaded into the corresponding hardware processor for inference, then the storage resources or uplink / downlink transmission resources of the corresponding training dataset no longer need to be retained. At this point, after the terminal executes the resource release task corresponding to Task ID1 and Task ID2, it can send the corresponding fifth message to the network device. This message can include Task ID1 and Task ID2. Upon receiving this message, the network device will also release the storage resources and downlink transmission resources corresponding to Task ID1 and Task ID2 configured on the network side.

[0248] In some embodiments, the fifth information may not include the first identification information and / or the second identification information described above. Optionally, after receiving the fifth information, the second device may not execute step S2108.

[0249] In some embodiments, the fifth information may be referred to as "resource release instruction information", "request response information", etc., and the name is not limited in this disclosure.

[0250] In step S2108, the second device executes one or more resource release tasks based on the fifth information.

[0251] In some embodiments, the second device executes a resource release task corresponding to the task identifier included in the first identification information, and / or a sub-release task corresponding to the sub-task identifier included in the first identification information.

[0252] In some embodiments, the principle by which the second device performs one or more resource release tasks based on the fifth information is the same as the principle by which the first device performs one or more resource release tasks based on the first information. Optional implementations of step S2108 can be found in steps S2102 and other related sections.

[0253] In some embodiments, after the second device performs the corresponding resource release task, it may also send a corresponding notification to the first device to inform it of the released resources.

[0254] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0255] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0256] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0257] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0258] In some embodiments, the terms “resource block (RB)”, “physical resource block (PRB)”, “sub-carrier group (SCG)”, “resource element group (REG)”, “PRB pair”, “RB pair”, “resource element (RE)”, and “sub-carrier” can be used interchangeably.

[0259] In some embodiments, the terms "precoding", "precoder", "weight", "precoding weight", "quasi-co-location (QCL)", "transmission configuration indication (TCI) status", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "the number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angular degree", "antenna", "antenna element", and "panel" can be used interchangeably.

[0260] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0261] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0262] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0263] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0264] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0265] The resource release method disclosed in this embodiment may include at least one of steps S2101 to S2108. For example, step S2102 may be implemented as a separate embodiment, step S2106 may be implemented as a separate embodiment, steps S2101 and S2103 may be implemented as separate embodiments, and steps S2106 to S2108 may be implemented as separate embodiments, but are not limited thereto.

[0266] In some embodiments, steps S2104 and S2106 may be performed in a different order or simultaneously, and steps S2102 and S2106 may be performed in a different order or simultaneously.

[0267] In some embodiments, steps S2101 and S2103 to S2108 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0268] In some embodiments, steps S2101 to S2105 and steps S2107 to S2108 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0269] In some embodiments, other optional implementations may be described before or after the specification corresponding to FIG2.

[0270] Figure 3A is a flowchart illustrating a resource release method according to an embodiment of the present disclosure. As shown in Figure 3A, the embodiment of the present disclosure relates to a resource release method (first device side), the method including:

[0271] Step S3101: Obtain the first information.

[0272] The optional implementation of step S3101 can be found in the optional implementation of step S2101 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0273] In some embodiments, the first device receives first information sent by the second device, but is not limited thereto; it may also receive first information sent by other entities.

[0274] In some embodiments, the first device acquires first information as defined by the protocol.

[0275] In some embodiments, the first device obtains first information from the upper layer(s).

[0276] In some embodiments, the first device processes the information to obtain the fifth information.

[0277] In some embodiments, step S3101 is omitted, the first device autonomously implements the function indicated by the first information, or the above function is a default or default setting.

[0278] Step S3102: Based on the first information, execute one or more resource release tasks.

[0279] The optional implementation of step S3102 can be found in the optional implementation of step S2102 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0280] Step S3103: Send the second message.

[0281] The optional implementation of step S3103 can be found in the optional implementation of step S2103 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0282] In some embodiments, the first device sends second information to the second device, but is not limited thereto; it may also send second information to other entities.

[0283] Step S3104: Determine that resources are insufficient, and send the fourth message to the second device.

[0284] The optional implementation of step S3104 can be found in the optional implementation of step S2104 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0285] In some embodiments, the first device sends fourth information to the second device, but is not limited thereto; it may also send fourth information to other entities.

[0286] Step S3105: Obtain third information.

[0287] The optional implementation of step S3105 can be found in the optional implementation of step S2105 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0288] In some embodiments, the first device receives third information sent by the second device, but is not limited thereto; it may also receive third information sent by other entities.

[0289] In some embodiments, the first device acquires third information as defined by the protocol.

[0290] In some embodiments, the first device obtains third information from the upper layer(s).

[0291] In some embodiments, the first device processes the information to obtain the fifth information.

[0292] In some embodiments, step S3105 is omitted, and the first device autonomously implements the function indicated by the third information, or the above function is default or default.

[0293] Step S3106: Determine if resources are insufficient, and execute one or more resource release tasks.

[0294] The optional implementation of step S3106 can be found in the optional implementation of step S2106 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0295] Step S3107: Send the fifth message to the second device.

[0296] The optional implementation of step S3107 can be found in the optional implementation of step S2107 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0297] In some embodiments, the first device sends the fifth information to the second device, but is not limited thereto; the fifth information may also be sent to other entities.

[0298] The resource release method disclosed in this embodiment may include at least one of steps S3101 to S3107. For example, step S3102 may be implemented as a separate embodiment, step S3106 may be implemented as a separate embodiment, steps S3101 and S3103 may be implemented as separate embodiments, and steps S3106 to S3107 may be implemented as separate embodiments, but are not limited thereto.

[0299] In some embodiments, steps S3104 and S3106 may be swapped in order or executed simultaneously, and steps S3102 and S3106 may be swapped in order or executed simultaneously.

[0300] In some embodiments, steps S3101 and S3103 to S3107 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0301] In some embodiments, steps S3101 to S3105 and step S3107 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0302] Figure 3B is an interactive schematic diagram illustrating a resource release method according to an embodiment of the present disclosure. As shown in Figure 3B, the embodiments of the present disclosure relate to a resource release method, which includes:

[0303] Step S3201: Obtain the first information.

[0304] The optional implementation of step S3201 can be found in the optional implementation of step S2101 in Figure 2, step S3101 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0305] Step S3202: Based on the first information, execute one or more resource release tasks.

[0306] The optional implementation of step S3201 can be found in the optional implementation of step S2102 in Figure 2, step S3102 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0307] Step S3203: Send the fifth message to the second device.

[0308] The optional implementation of step S3203 can be found in the optional implementation of step S2107 in Figure 2, step S3107 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0309] The resource release method disclosed in this embodiment may include at least one of steps S3201 to S3203. For example, step S3201 may be implemented as a standalone embodiment, step S3202 may be implemented as a standalone embodiment, steps S3201 and S3202 may be implemented as standalone embodiments, and steps S3202 to S3203 may be implemented as standalone embodiments, but is not limited thereto.

[0310] In some embodiments, steps S3201 and S3203 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0311] Figure 3C is an interactive schematic diagram illustrating a resource release method according to an embodiment of the present disclosure. As shown in Figure 3C, the embodiments of the present disclosure relate to a resource release method, which includes:

[0312] Step S3301: Determine that resources are insufficient, and send the fourth message to the second device.

[0313] The optional implementation of step S3301 can be found in the optional implementation of step S2104 in Figure 2, step S3104 in Figure 3A, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0314] Step S3302: Obtain third information.

[0315] The optional implementation of step S3302 can be found in step S2105 of Figure 2, the optional implementation of step S3105 of Figure 3A, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0316] Step S3303: Determine if resources are insufficient, and execute one or more resource release tasks.

[0317] The optional implementation of step S3303 can be found in step S2106 of Figure 2, the optional implementation of step S3106 of Figure 3A, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0318] Step S3304: Send the fifth message to the second device.

[0319] The optional implementation of step S3304 can be found in the optional implementation of step S2107 in Figure 2, step S3107 in Figure 3A, step S3203 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0320] The resource release method disclosed in this embodiment may include at least one of steps S3301 to S3304. For example, step S3301 may be implemented as a standalone embodiment, step S3303 may be implemented as a standalone embodiment, steps S3301 and S3302 may be implemented as standalone embodiments, and steps S3303 to S3304 may be implemented as standalone embodiments, but are not limited thereto.

[0321] In some embodiments, steps S3301 to S3302 and step S3304 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0322] Figure 3D is an interactive schematic diagram illustrating a resource release method according to an embodiment of the present disclosure. As shown in Figure 3D, the embodiments of the present disclosure relate to a resource release method, which includes:

[0323] Step S3401: Determine if resources are insufficient, and execute one or more resource release tasks.

[0324] The optional implementation of step S3401 can be found in the optional implementation of step S2106 in Figure 2, step S3106 in Figure 3A, step S3303 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0325] Step S3402: Send the fifth message to the second device.

[0326] The optional implementation of step S3402 can be found in the optional implementation of step S2107 in Figure 2, step S3107 in Figure 3A, step S3203 in Figure 3B, step S3304 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0327] The resource release method disclosed in this embodiment may include at least one of steps S3401 to S3402. For example, step S3401 may be implemented as a separate embodiment, and step S3403 may be implemented as a separate embodiment.

[0328] In some embodiments, step S3402 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0329] Figure 3E is an interactive schematic diagram illustrating a resource release method according to an embodiment of the present disclosure. As shown in Figure 3E, the embodiments of the present disclosure relate to a resource release method, which includes:

[0330] Step S3506: Determine if there is a resource release requirement, and execute one or more resource release tasks.

[0331] Optional implementations of step S3506 can be found in steps S2102 and / or S2106 in Figure 2, steps S3102 and / or S3106 in Figure 3A, steps S3303 in Figure 3C, optional implementations of step S3401 in Figure 3D, and other related parts in the embodiments involved in Figures 2, 3A, 3B, 3C, and 3D, which will not be repeated here.

[0332] In some embodiments, if a resource release requirement is determined, one or more resource release tasks are executed.

[0333] The first device is used to provide one or more computing power services to the second device, and a resource release task is used to release the resources corresponding to one or more computing power services. Different resource release tasks correspond to different computing power services.

[0334] In some embodiments, the first device and the second device share computing power, and the second device is used to provide one or more computing power services to the first device.

[0335] In some embodiments, the first device is a network device, and the second device is a terminal device; or...

[0336] The first device is a terminal device, and the second device is a network device;

[0337] The number of terminal devices is one or more.

[0338] In some embodiments, the resources corresponding to the computing power service include at least one of storage resources, communication transmission resources, and computing power resources.

[0339] Resource release tasks include at least one of the following:

[0340] Storage resource release task;

[0341] Communication transmission resource release task;

[0342] Task to release computing resources.

[0343] In some embodiments, the resources corresponding to each computing power service include at least one sub-resource, and each resource release task includes at least one sub-release task.

[0344] One sub-release task is used to release one or more sub-resources, and different sub-release tasks correspond to different sub-resources.

[0345] In some embodiments, different resource release tasks have different task identifiers, and / or, different sub-release tasks have different sub-task identifiers.

[0346] In some embodiments, if a resource release requirement is determined, one or more resource release tasks are executed, including:

[0347] Receive first information sent by the second device, the first information including at least one task identifier and / or at least one subtask identifier;

[0348] Execute the resource release task corresponding to each task identifier included in the first information, and / or execute the sub-release task corresponding to each sub-task identifier included in the first information.

[0349] In some embodiments, the first information is sent when the second device determines that the first resource is no longer needed. The first information includes a task identifier and / or a subtask identifier corresponding to the first resource. The first resource includes at least one sub-resource corresponding to at least one computing power service provided by the first device.

[0350] In some embodiments, the second device further provides one or more computing power services to the first device, the method comprising:

[0351] If it is determined that the second resource provided by the second device is no longer needed, second information is sent to the second device. The second information includes the task identifier and / or subtask identifier corresponding to the second resource. The second resource includes at least one sub-resource corresponding to at least one computing power service provided by the second device.

[0352] In some embodiments, if a resource release requirement is determined, one or more resource release tasks are executed, including:

[0353] If resources are insufficient, execute the resource release task corresponding to each computing power service provided by the first device, and / or, the sub-release task corresponding to each sub-resource provided by the first device; or...

[0354] If resources are insufficient, execute the N lowest priority resource release tasks and / or the M lowest priority sub-release tasks, where N is less than or equal to the total number of resource release tasks and M is less than or equal to the total number of sub-release tasks.

[0355] In some embodiments, if a resource release requirement is determined, one or more resource release tasks are executed, including:

[0356] Receive third information sent by the second device, the third information including at least one task identifier and / or at least one subtask identifier;

[0357] If resources are determined to be insufficient, resource release tasks and / or sub-resource release tasks are executed sequentially according to the priority corresponding to each task identifier included in the third information, and / or the priority corresponding to each sub-task identifier included in the third information, until the resources meet the demand.

[0358] In some embodiments, the third information is further used to indicate the priority corresponding to each task identifier and / or each subtask identifier in the third information.

[0359] In some embodiments, the method further includes:

[0360] If resources are determined to be insufficient, a fourth message is sent to the second device. The fourth message instructs the first device to perform one or more resource release tasks.

[0361] In some embodiments, the method includes:

[0362] Send a fifth message to the second device, the fifth message including at least one of the following:

[0363] The response information is used to indicate that the first device has executed one or more resource release tasks based on the first information sent by the second device;

[0364] The first identification information includes the task identifier corresponding to the resource release task that the first device has completed and / or the sub-task identifier corresponding to the sub-release task that has been completed.

[0365] The second identification information includes the task identifier corresponding to the resource release task that the first device did not execute and / or the sub-task identifier corresponding to the sub-release task that was not executed.

[0366] In some embodiments, the first device and the second device share computing power;

[0367] The fifth information is also used to instruct the second device to execute the resource release task corresponding to the task identifier included in the first identification information, and / or the sub-release task corresponding to the sub-task identifier included in the first identification information.

[0368] Figure 4A is an interactive schematic diagram of a resource release method according to an embodiment of the present disclosure. As shown in Figure 4A, the embodiment of the present disclosure relates to a resource release method (second device side), which includes:

[0369] Step S4101: Send the first message.

[0370] The optional implementation of step S4101 can be found in the optional implementation of step S2101 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0371] In some embodiments, the second device sends the first information to the first device, but is not limited thereto; the first information may also be sent to other entities.

[0372] Step S4102: Obtain the second information.

[0373] The optional implementation of step S4102 can be found in the optional implementation of step S2103 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0374] In some embodiments, the second device receives second information sent by the first device, but is not limited thereto; it may also receive second information sent by other entities.

[0375] In some embodiments, the second device acquires second information as defined by the protocol.

[0376] In some embodiments, the second device obtains second information from the upper layer(s).

[0377] In some embodiments, the second device processes the information to obtain the second information.

[0378] In some embodiments, step S4102 is omitted, and the network device autonomously implements the function indicated by the second information, or the above function is defaulted or set to default.

[0379] Step S4103: Obtain the fourth piece of information.

[0380] The optional implementation of step S4103 can be found in the optional implementation of step S2104 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0381] In some embodiments, the second device receives fourth information sent by the first device, but is not limited thereto; it may also receive fourth information sent by other entities.

[0382] In some embodiments, the second device acquires fourth information as defined by the protocol.

[0383] In some embodiments, the second device obtains fourth information from the upper layer(s).

[0384] In some embodiments, the second device processes the information to obtain the fourth information.

[0385] In some embodiments, step S4103 is omitted, and the network device autonomously implements the function indicated by the fourth information, or the above function is defaulted or set to default.

[0386] Step S4104: Send the third message.

[0387] The optional implementation of step S4104 can be found in the optional implementation of step S2105 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0388] In some embodiments, the second device sends third information to the first device, but is not limited thereto; it may also send third information to other entities.

[0389] Step S4105: Obtain the fifth piece of information.

[0390] The optional implementation of step S4105 can be found in the optional implementation of step S2107 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0391] In some embodiments, the second device receives the fifth information sent by the first device, but is not limited thereto; it may also receive the fifth information sent by other entities.

[0392] In some embodiments, the second device acquires the fifth information specified by the protocol.

[0393] In some embodiments, the second device obtains the fifth information from the upper layer(s).

[0394] In some embodiments, the second device processes the information to obtain the fifth information.

[0395] In some embodiments, step S4105 is omitted, and the network device autonomously implements the function indicated by the fifth information, or the above function is defaulted or set to default.

[0396] Step S4106: Based on the fifth information, execute one or more resource release tasks.

[0397] The optional implementation of step S4106 can be found in the optional implementation of step S2108 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0398] The resource release method disclosed in this embodiment may include at least one of steps S4101 to S4106. For example, step S4101 may be implemented as a standalone embodiment, step S4104 may be implemented as a standalone embodiment, and steps S4105 and S4106 may be implemented as standalone embodiments, but are not limited thereto.

[0399] In some embodiments, steps S4102 to S4106 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0400] In some embodiments, steps S4101 to S4103 and steps S4105 to S4106 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0401] Figure 4B is an interactive schematic diagram of a resource release method according to an embodiment of the present disclosure. As shown in Figure 4B, the embodiment of the present disclosure relates to a resource release method (second device side), the method including:

[0402] Step S4201: Obtain the fourth piece of information.

[0403] The optional implementation of step S4201 can be found in the optional implementation of step S2104 in Figure 2, step S4104 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0404] Step S4202: Send the third message.

[0405] The optional implementation of step S4202 can be found in the optional implementation of step S2105 in Figure 2, step S4105 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0406] The resource release method disclosed in this embodiment may include at least one of steps S4201 to S4202. For example, step S4201 may be implemented as a separate embodiment, and step S4202 may be implemented as a separate embodiment.

[0407] In some embodiments, step S4201 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0408] In some embodiments, step S4202 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0409] Figure 4C is an interactive schematic diagram of a resource release method according to an embodiment of the present disclosure. As shown in Figure 4C, the embodiment of the present disclosure relates to a resource release method (second device side), the method including:

[0410] Step S4301: Obtain the fifth piece of information.

[0411] The optional implementation of step S4301 can be found in the optional implementation of step S2107 in Figure 2, step S4105 in Figure 4A, and other related parts in the embodiments involved in Figures 2, 4A, and 4B, which will not be repeated here.

[0412] Step S4302: Based on the fifth information, execute one or more resource release tasks.

[0413] The optional implementation of step S4302 can be found in the optional implementation of step S2108 in Figure 2, step S4106 in Figure 4A, and other related parts in the embodiments involved in Figures 2, 4A, and 4B, which will not be repeated here.

[0414] The resource release method disclosed in this embodiment may include at least one of steps S4301 to S4302. For example, step S4301 may be implemented as a separate embodiment, and step S4302 may be implemented as a separate embodiment.

[0415] In some embodiments, step S4301 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0416] In some embodiments, step S4302 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0417] Figure 4D is an interactive schematic diagram of a resource release method according to an embodiment of the present disclosure. As shown in Figure 4D, the embodiment of the present disclosure relates to a resource release method (second device side), which includes:

[0418] Step S4401: Send the first message.

[0419] The optional implementation of step S4401 can be found in the optional implementation of step S2101 in Figure 2, step S4101 in Figure 4A, and other related parts in the embodiments involved in Figures 2, 4A, 4B, and 4C, which will not be repeated here.

[0420] In some embodiments, a first message is sent to the first device, the first message being used to instruct the first device to perform one or more resource release tasks;

[0421] The first device is used to provide one or more computing power services to the second device, and a resource release task is used to release the resources corresponding to one or more computing power services. Different resource release tasks correspond to different computing power services.

[0422] In some embodiments, the first device and the second device share computing power, and the second device is used to provide one or more computing power services to the first device.

[0423] In some embodiments, the first device is a network device, and the second device is a terminal; or...

[0424] The first device is a terminal, and the second device is a network device.

[0425] In some embodiments, the resources corresponding to the computing power service include at least one of storage resources, communication transmission resources, and computing power resources.

[0426] Resource release tasks include at least one of the following:

[0427] Storage resource release task;

[0428] Communication transmission resource release task;

[0429] Task to release computing resources.

[0430] In some embodiments, the resources corresponding to each computing power service include at least one sub-resource, and each resource release task includes at least one sub-release task.

[0431] One sub-release task is used to release one or more sub-resources, and different sub-release tasks correspond to different sub-resources.

[0432] In some embodiments, different release tasks have different task identifiers, and / or different sub-release tasks have different sub-task identifiers.

[0433] In some embodiments, the first information includes at least one task identifier and / or at least one subtask identifier;

[0434] The first information is used to instruct the first device to execute the resource release task corresponding to each task identifier included in the first information, and / or to execute the sub-release task corresponding to each sub-task identifier included in the first information.

[0435] In some embodiments, sending first information to the first device includes:

[0436] Once it is determined that the first resource is no longer needed, first information is sent to the first device. The first information includes the task identifier and / or subtask identifier corresponding to the first resource. The first resource includes at least one sub-resource corresponding to at least one computing power service provided by the first device.

[0437] In some embodiments, the second device further provides one or more computing power services to the first device, the method comprising:

[0438] The device receives second information sent by the first device. The second information is sent when the first device determines that it no longer needs the second resource provided by the second device. The second information includes a task identifier and / or a subtask identifier corresponding to the second resource. The second resource includes at least one sub-resource corresponding to at least one computing power service provided by the second device.

[0439] In some embodiments, the method further includes:

[0440] Send third information to the first device, the third information including at least one task identifier and / or at least one subtask identifier;

[0441] The third information is used by the first device to execute one or more resource release tasks when it determines that resources are insufficient.

[0442] In some embodiments, the third information is further used to indicate the priority corresponding to each task identifier and / or each subtask identifier in the third information.

[0443] In some embodiments, the method further includes:

[0444] The device receives a fourth message sent by the first device when it determines that resources are insufficient. The fourth message is used to instruct the first device to perform one or more resource release tasks.

[0445] In some embodiments, the method further includes:

[0446] Receive fifth information sent by the first device, the fifth information including at least one of the following:

[0447] The response information is used to indicate that the first device has executed one or more resource release tasks based on the first information sent by the second device;

[0448] The first identification information includes the task identifier corresponding to the resource release task that the first device has completed and / or the sub-task identifier corresponding to the sub-release task that has been completed.

[0449] The second identification information includes the task identifier corresponding to the resource release task that the first device did not execute and / or the sub-task identifier corresponding to the sub-release task that was not executed.

[0450] In some embodiments, the second device is used to provide one or more computing power services to the first device;

[0451] The method also includes:

[0452] Execute the resource release task corresponding to the task identifier included in the first identifier information, and / or the sub-release task corresponding to the sub-task identifier included in the first identifier information.

[0453] Figure 5 is a flowchart illustrating a resource release method according to an embodiment of the present disclosure. As shown in Figure 5, the present disclosure relates to a resource release method, which includes:

[0454] Step 5101: Upon receiving the request information or determining that resources are insufficient, the resource provider releases computing power services.

[0455] In some embodiments, the resource provider, i.e., the computing power service provider, can be a network device or a terminal. Optionally, in a shared computing power scenario, network devices and terminals can be each other's resource providers.

[0456] In some embodiments, the content released by the computing power service includes at least one of the following:

[0457] Release storage resources: such as the storage resources of datasets or models, or model storage resources may include the storage resources of model structure and model parameters;

[0458] Release communication transmission resources: such as resources used for uplink or downlink data transmission;

[0459] Release computing resources of different types: such as model training capabilities, model inference capabilities, or model monitoring capabilities.

[0460] In some embodiments, different task IDs or sub-task IDs (i.e., a certain event is further divided into different sub-events) are defined for the above-mentioned release content. For example, the release of computing resources, storage resources, communication transmission resources, and computing power type are defined as Task ID1, Task ID2, and Task ID3, respectively. Further, Task ID1 and Task ID3 are further divided into Sub-task ID1, Sub-task ID2, or Sub-task ID3. The above-mentioned Task IDs or Sub-task IDs can be determined by predefinition or assigned to the UE by the network side.

[0461] When providing computing power services from the network side to the terminal side:

[0462] In some embodiments, the terminal may request the network to release computing power services.

[0463] Specifically, on the terminal side: Optionally, the terminal sends a first message to the network via signaling indicating a request to release computing power. Optionally, this first message contains at least one or more Task IDs. Optionally, the terminal receives a response message from the network side indicating whether the network side has successfully released the computing power service. Optionally, the terminal then sends a reply message to the network side.

[0464] For the network side: Optionally, the computing power service is released based on the Task ID contained in the received first message. Optionally, a response message for the release of computing power service is sent to the terminal. Optionally, an acknowledgment message is then received from the terminal.

[0465] In some embodiments, the network may release computing power services on its own and instruct the terminal.

[0466] Specifically, on the network side, when network computing resources are insufficient, the network can send a second message to the terminal indicating that the computing power allocated to the terminal will be released. Optionally, the network can directly release some or all of the computing power services corresponding to Task IDs based on Task ID priority. Optionally, the network can release computing power services based on the Task IDs contained in the received third message. If the third message contains multiple Task IDs, the computing power services are released one by one according to the priority of the Task IDs. That is, the lower priority Task IDs are released first. If the network computing power service still needs to be released, the network then releases the next lower priority Task ID, and so on, until the current network computing power service no longer needs to be released. Optionally, the network sends a fourth message to the terminal, which contains the Task IDs that have not been released or have already been released.

[0467] On the terminal side, the terminal can send a third message to the network, which contains at least one or more Task IDs. When the indication message contains multiple Task IDs, different priorities are defined for each Task ID. Priorities can be determined based on predefined criteria, network indications, or terminal methods. For example, smaller Task IDs are defined to have higher priorities. Optionally, the terminal receives a fourth message and determines the Task IDs released by the network side based on the Task IDs contained in the fourth message. Optionally, the terminal sends a response message to the network, confirming that it has been informed of the Task IDs released by the network side.

[0468] When providing computing power services to the network side on the terminal side:

[0469] In some embodiments, the network side may request the terminal to release computing power services:

[0470] On the network side: Optionally, the network sends a fifth message to the terminal via signaling to indicate a computing power release request. This message can be a signaling message sent individually to each terminal, or it can be broadcast to multiple terminals. Optionally, the fifth message contains one or more Task IDs. Optionally, the network receives a response message from the terminal to determine whether the computing power service has been released. Optionally, the network then sends a confirmation message to the terminal.

[0471] For the terminal side: Optionally, the terminal releases the computing power service based on the Task ID contained in the received fifth message. Optionally, the terminal sends a response message to the network to release the computing power service. Optionally, the terminal receives a confirmation message from the network, enabling the network and the terminal to reach a consensus on releasing the computing power service.

[0472] In some embodiments, the terminal releases its computing power service and instructs the network.

[0473] The workflow of the terminal releasing computing power services and instructing the network can be the same as the workflow of the network releasing computing power services and instructing the terminal, except that the actions of the terminal and the network are interchanged.

[0474] When sharing computing power between a terminal and the network:

[0475] In some embodiments, the terminal and the network predefine a unified Task ID corresponding to different resources.

[0476] In some embodiments, the terminal and the network release resources corresponding to the same Task ID.

[0477] Optionally, when the terminal or network releases computing power services, it sends a sixth message to the peer, which includes one or more Task IDs. The peer releases the computing power services corresponding to the received Task ID. Optionally, the peer releases computing power services corresponding to other Task IDs and sends a seventh message containing those other Task IDs to the other end. The other end sends a corresponding response message to confirm the computing power services released by the peer.

[0478] In some embodiments, the terminal side or network does not release or releases resources corresponding to different Task IDs.

[0479] Optionally, the terminal or network sends an eighth message to the peer indicating the release of computing power services. The eighth message contains one or more Task IDs, and the peer exhibits at least one of the following behaviors:

[0480] The peer sends a response message indicating that it has received the computing power service that the terminal or network wants to release.

[0481] The peer then sends a ninth message to the other end (assuming the peer is the network, then the other end is the terminal) indicating the released computing power service. The ninth message contains one or more Task IDs of the peer. Optionally, the other end provides a corresponding response message upon receiving the ninth message.

[0482] In scenarios where the network side provides computing power services to the terminal side:

[0483] In a specific embodiment, assuming the UE has requested computing power services from the network, the gNB allocates certain storage resources to the UE for storing training data and trained AI / ML models, allocates uplink transmission resources for transmitting the training dataset, and allocates computing power resources to provide the UE with model training. Assume these computing power resources provided by the gNB are associated with Task ID1, Task ID2, and Task ID3. Task ID1 corresponds to storage resources, Task ID2 corresponds to communication transmission resources, and Task ID3 corresponds to computing power resources of different computing power types. Further, Task ID1 is divided into Sub-task ID1 and Sub-task ID2, which correspond to storing the training dataset and training AI / ML models, respectively. Task ID3 is further divided into Sub-task ID, Sub-task ID2, and Sub-task ID3, which correspond to releasing model training capabilities, model inference capabilities, and model monitoring capabilities, respectively. Based on the received training dataset, the gNB can complete the training of the corresponding model and transmit the trained model to the UE.

[0484] If the UE receives a model from the gNB that meets the performance requirements, the UE can send a request to the gNB to release computing resources. Considering that the UE may need the gNB to further update the model without requiring other allocated computing resources, the UE can send a first message to the gNB indicating the computing resource release request via physical layer or higher-layer signaling. This first message includes Sub-task ID1 of Task ID1, and Sub-task ID1 of Task ID2 and Task ID3.

[0485] Based on the received Task IDs and Sub-task IDs, the gNB releases the corresponding resources and sends a response message to the UE to indicate that the resource release is complete.

[0486] In another specific embodiment, if constrained by gNB hardware resources, the gNB needs to release some or all of the UE's storage or computing resources. The gNB sends a second message to the UE instructing the gNB to release the storage or computing resources to the UE. The second message may simply be a release instruction; optionally, the second message may also include the Task ID and Sub-Task ID corresponding to the released resources.

[0487] If the message is merely an indication of release, the UE, upon receiving it, sends a third message to the gNB. This third message can confirm agreement with the gNB regarding the resources to be released. It can also contain different Task IDs or Sub-Task IDs corresponding to different resources, each with its own priority. For example, consider Sub-task ID1, Task ID2, and Sub-task ID1 of Task ID3 assigned above. The priority is defined as Task ID3 > Task ID2 > Task ID1, meaning Task ID3 has the highest priority, and Task ID1 has the lowest. Each sub-Task ID within a Task ID can also have its own priority defined. The gNB will prioritize releasing tasks with lower priority based on the Task IDs contained in the received third message. For instance, it will prioritize releasing Sub-task ID1 within Task ID1. If releasing the resources still doesn't satisfy the gNB's requirements, the gNB will continue releasing the resources corresponding to Task ID2 until its needs are met.

[0488] Assuming the gNB satisfies its requirements by releasing Sub-task ID1 from Task ID1, the gNB sends a fourth message to the UE containing Sub-task ID1 from Task ID1, indicating that the storage resources for storing the training dataset have been released. Alternatively, the fourth message may contain Sub-task ID2 from Task ID1, where Task ID2 and Task ID3 indicate that the resources corresponding to these Task IDs have not been released. The UE can determine which resources the gNB has released based on these received Task IDs.

[0489] In scenarios where computing power is shared between the network side and the terminal side:

[0490] Suppose that collaboration between the terminal and the network is required to complete the model inference task, such as CSI compression feedback based on a bilateral model. On the UE side, a CSI generation part of the model is deployed for CSI compression feedback, while on the gNB side, the CSI generation part is deployed for CSI recovery. This can be viewed as computing power sharing between the UE and the gNB; that is, the UE provides computing power services to the gNB, and the gNB also provides corresponding computing power services to the UE. Each computing power service may provide different computing power resources, storage resources, or communication resources.

[0491] In one specific embodiment, the terminal and the network can release resources corresponding to the same Task ID. Assume the UE and gNB collaboratively train a bilateral model; the UE trains the CSI generation part of the model, and the gNB trains the CSI recovery model. Assume the model training is complete and the trained model has been loaded into the corresponding hardware processor for inference, then the corresponding training dataset or uplink / downlink transmission resources no longer need to be retained. At this point, the UE sends a sixth message to the gNB, which contains Task ID1 and Task ID2. Upon receiving the sixth message, the gNB will also release the storage resources and downlink transmission resources corresponding to Task ID1 and Task ID2 on its side. Optionally, the gNB also sends a response message to the UE to confirm that the release of the corresponding resources has been completed.

[0492] In another specific embodiment, the terminal or network may not release resources corresponding to different Task IDs, or may release resources at different times. For some bilateral models, when resources are released on one side, the other side may not necessarily release resources, or release resources corresponding to other Task IDs. For example, if the UE releases resources corresponding to Task ID1, Task ID2, and Task ID3 (meaning the UE no longer participates in providing computing power services), the UE sends an eighth message to the gNB, which includes the resources corresponding to these three Task IDs. After receiving the eighth message, the gNB only sends a response message to the UE; the gNB does not release its own resources. Optionally, the gNB releases the downlink transmission resources corresponding to Task ID2 and sends a ninth message to the UE as an indication; the ninth message includes Task ID2. After receiving the ninth message, the UE can send a response message to the gNB for confirmation.

[0493] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0494] This disclosure also provides an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0495] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0496] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0497] Figure 6A is a schematic diagram of the structure of the first device proposed in an embodiment of this disclosure. As shown in Figure 6A, the first device 6100 may include at least one of a transceiver module 6101, a processing module 6102, etc. Optionally, the transceiver module 6101 is used to perform at least one of the communication steps such as sending and / or receiving performed by the first device in any of the above methods, which will not be described in detail here. Optionally, the processing module 6102 is used to perform at least one of the other steps performed by the first device in any of the above methods, which will not be described in detail here.

[0498] Figure 6B is a schematic diagram of the structure of the second device proposed in an embodiment of this disclosure. As shown in Figure 6B, the second device 6200 may include at least one of a transceiver module 6201, a processing module 6202, etc. Optionally, the transceiver module 6201 is used to perform at least one of the communication steps such as sending and / or receiving performed by the second device in any of the above methods, which will not be described in detail here. Optionally, the processing module 6202 is used to perform at least one of the other steps performed by the second device in any of the above methods, which will not be described in detail here.

[0499] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0500] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0501] Figure 7A is a schematic diagram of the structure of the communication device 7100 proposed in an embodiment of this disclosure. The communication device 7100 can be a second device, a first device, a chip, chip system, or processor that supports the second device in implementing any of the above methods, or a chip, chip system, or processor that supports the first device in implementing any of the above methods. The communication device 7100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0502] As shown in Figure 7A, the communication device 7100 includes one or more processors 7101. The processor 7101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, first devices, first device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 7100 can be used to execute any of the above methods. Optionally, one or more processors 7101 can be used to invoke instructions to cause the communication device 7100 to execute any of the above methods.

[0503] In some embodiments, the communication device 7100 further includes one or more transceivers 7102. When the communication device 7100 includes one or more transceivers 7102, the transceiver 7102 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 7101 performs at least one of the other steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, sending unit, transmitter, sending circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0504] In some embodiments, the communication device 7100 further includes one or more memories 7103 for storing data. Optionally, all or part of the memories 7103 may be located outside the communication device 7100. In optional embodiments, the communication device 7100 may include one or more interface circuits 7104. Optionally, the interface circuits 7104 are connected to the memories 7103 and can be used to receive data from the memories 7103 or other devices, and to send data to the memories 7103 or other devices. For example, the interface circuits 7104 can read data stored in the memories 7103 and send the data to the processor 7101.

[0505] The communication device 7100 described in the above embodiments may be a second device or a first device, but the scope of the communication device 7100 described in this disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0506] Figure 7B is a schematic diagram of the structure of the chip 7200 according to an embodiment of this disclosure. For cases where the communication device 7100 can be a chip or a chip system, the schematic diagram of the chip 7200 shown in Figure 7B can be referenced, but is not limited thereto.

[0507] Chip 7200 includes one or more processors 7201. Chip 7200 is used to perform any of the above methods.

[0508] In some embodiments, chip 7200 further includes one or more interface circuits 7202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 7200 further includes one or more memories 7203 for storing data. Optionally, all or part of the memories 7203 may be located outside chip 7200. Optionally, interface circuit 7202 is connected to memory 7203, and interface circuit 7202 can be used to receive data from memory 7203 or other devices, and interface circuit 7202 can be used to send data to memory 7203 or other devices. For example, interface circuit 7202 can read data stored in memory 7203 and send the data to processor 7201.

[0509] In some embodiments, the interface circuit 7202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 7202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 7202 performs data interaction between the processor 7201, the chip 7200, the memory 7203, or the transceiver device. In some embodiments, the processor 7201 performs at least one of the other steps.

[0510] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0511] This disclosure also proposes a storage medium storing instructions that, when executed on the communication device 7100, cause the communication device 7100 to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0512] This disclosure also provides a program product that, when executed by the communication device 7100, causes the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0513] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A resource release method, characterized in that, Performed by a first device, the method includes: If a resource release requirement is identified, execute one or more resource release tasks; The first device is used to provide one or more computing power services to the second device, and a resource release task is used to release resources corresponding to one or more computing power services. Different resource release tasks correspond to different computing power services.

2. The method according to claim 1, characterized in that, The first device and the second device share computing power, and the second device is used to provide one or more of the computing power services to the first device.

3. The method according to any one of claims 1-2, characterized in that, The resources corresponding to the computing power service include at least one of storage resources, communication transmission resources, and computing power resources. The resource release task includes at least one of the following: Storage resource release task; Communication transmission resource release task; Task to release computing resources.

4. The method according to any one of claims 1-3, characterized in that, Each of the computing power services includes at least one sub-resource, and each of the resource release tasks includes at least one sub-release task. In this context, a sub-release task is used to release one or more sub-resources, and different sub-release tasks correspond to different sub-resources; different resource release tasks have different task identifiers, and / or, different sub-release tasks have different sub-task identifiers.

5. The method according to any one of claims 1-4, characterized in that, The determination that there is a need to release resources and the execution of one or more resource release tasks include: Receive first information sent by the second device, the first information including at least one task identifier and / or at least one subtask identifier; Execute the resource release task corresponding to each task identifier included in the first information, and / or execute the sub-release task corresponding to each sub-task identifier included in the first information.

6. The method according to claim 5, characterized in that, The first information is sent when the second device determines that it no longer needs the first resource. The first information includes the task identifier and / or subtask identifier corresponding to the first resource. The first resource includes at least one sub-resource corresponding to at least one computing power service provided by the first device.

7. The method according to claim 5 or 6, characterized in that, The second device also provides one or more of the computing power services to the first device, the method comprising: If it is determined that the second resource provided by the second device is no longer needed, second information is sent to the second device. The second information includes the task identifier and / or subtask identifier corresponding to the second resource. The second resource includes at least one sub-resource corresponding to at least one computing power service provided by the second device.

8. The method according to any one of claims 1-7, characterized in that, The determination that there is a need to release resources and the execution of one or more resource release tasks include: If resources are insufficient, execute the resource release task corresponding to each computing power service provided by the first device, and / or the sub-release task corresponding to each sub-resource provided by the first device; or... If resources are insufficient, execute the N lowest priority resource release tasks and / or the M lowest priority sub-release tasks, where N is less than or equal to the total number of resource release tasks and M is less than or equal to the total number of sub-release tasks.

9. The method according to any one of claims 1-8, characterized in that, The determination that there is a need to release resources and the execution of one or more resource release tasks include: Receive third information sent by the second device, the third information including at least one task identifier and / or at least one subtask identifier; If resource insufficiency is determined, resource release tasks and / or sub-resource release tasks are executed sequentially according to the priority corresponding to each task identifier included in the third information, and / or the priority corresponding to each sub-task identifier included in the third information, until resource availability is met. need.

10. The method according to claim 9, characterized in that, The third information is also used to indicate the priority corresponding to each task identifier and / or each subtask identifier in the third information.

11. The method according to any one of claims 8-10, characterized in that, The method further includes: If resources are insufficient, a fourth message is sent to the second device, which instructs the first device to perform one or more resource release tasks.

12. The method according to any one of claims 1-11, characterized in that, The method includes: Send a fifth message to the second device, the fifth message including at least one of the following: The response information is used to indicate that the first device has executed one or more resource release tasks based on the first information sent by the second device; The first identification information includes the task identifier corresponding to the resource release task that the first device has completed and / or the sub-task identifier corresponding to the sub-release task that has been completed. The second identification information includes the task identifier corresponding to the resource release task that the first device did not execute and / or the sub-task identifier corresponding to the sub-release task that was not executed.

13. The method according to claim 12, characterized in that, The first device and the second device share computing power; The fifth information is also used to instruct the second device to execute the resource release task corresponding to the task identifier included in the first identification information, and / or the sub-release task corresponding to the sub-task identifier included in the first identification information.

14. A resource release method, characterized in that, Performed by a second device, the method includes: Send first information to the first device, the first information being used to instruct the first device to perform one or more resource release tasks; The first device is used to provide one or more computing power services to the second device, and a resource release task is used to release resources corresponding to one or more computing power services. Different resource release tasks correspond to different computing power services.

15. The method according to claim 14, characterized in that, The first device and the second device share computing power, and the second device is used to provide one or more of the computing power services to the first device.

16. The method according to any one of claims 14-15, characterized in that, The resources corresponding to the computing power service include at least one of storage resources, communication transmission resources, and computing power resources. The resource release task includes at least one of the following: Storage resource release task; Communication transmission resource release task; Task to release computing resources.

17. The method according to any one of claims 14-16, characterized in that, Each of the computing power services includes at least one sub-resource, and each of the resource release tasks includes at least one sub-release task. One sub-release task is used to release one or more sub-resources, and different sub-release tasks correspond to different sub-resources; Different release tasks have different task identifiers, and / or different sub-release tasks have different sub-task identifiers.

18. The method according to any one of claims 14-17, characterized in that, The first information includes at least one task identifier and / or at least one subtask identifier; The first information is used to instruct the first device to execute the resource release task corresponding to each task identifier included in the first information, and / or to execute the sub-release task corresponding to each sub-task identifier included in the first information.

19. The method according to any one of claims 14-18, characterized in that, Sending the first information to the first device includes: Once it is determined that the first resource is no longer needed, the first information is sent to the first device. The first information includes the task identifier and / or subtask identifier corresponding to the first resource. The first resource includes at least one sub-resource corresponding to at least one computing power service provided by the first device.

20. The method according to any one of claims 14-19, characterized in that, The second device also provides one or more computing power services to the first device, the method comprising: The system receives second information sent by the first device. The second information is sent when the first device determines that it no longer needs the second resource provided by the second device. The second information includes a task identifier and / or a subtask identifier corresponding to the second resource. The second resource includes at least one sub-resource corresponding to at least one computing power service provided by the second device.

21. The method according to any one of claims 14-20, characterized in that, The method further includes: Send third information to the first device, the third information including at least one task identifier and / or at least one subtask identifier; The third information is used by the first device to execute one or more resource release tasks when it determines that resources are insufficient.

22. The method according to claim 21, characterized in that, The third information is also used to indicate the priority corresponding to each task identifier and / or each subtask identifier in the third information.

23. The method according to any one of claims 14-22, characterized in that, The method further includes: The first device receives a fourth message sent by the first device when it determines that resources are insufficient. The fourth message is used to instruct the first device to execute one or more resource release tasks.

24. The method according to any one of claims 14-23, characterized in that, The method further includes: The fifth message sent by the first device is received, and the fifth message includes at least one of the following: The response information is used to indicate that the first device has executed one or more resource release tasks based on the first information sent by the second device; The first identification information includes the task identifier corresponding to the resource release task that the first device has completed and / or the sub-task identifier corresponding to the sub-release task that has been completed. The second identification information includes the task identifier corresponding to the resource release task that the first device did not execute and / or the sub-task identifier corresponding to the sub-release task that was not executed.

25. The method according to claim 24, characterized in that, The second device is used to provide one or more of the computing power services to the first device; The method further includes: Execute the resource release task corresponding to the task identifier included in the first identification information, and / or the sub-release task corresponding to the sub-task identifier included in the first identification information.

26. A communication device, characterized in that, include: The processing module is configured to determine if there is a resource release requirement and execute one or more resource release tasks. The first device is used to provide one or more computing power services to the second device, and a resource release task is used to release resources corresponding to one or more computing power services. Different resource release tasks correspond to different computing power services.

27. A communication device, characterized in that, include: The processing module is configured to send first information to the first device, the first information being used to instruct the first device to perform one or more resource release tasks; The first device is used to provide one or more computing power services to the second device, and a resource release task is used to release resources corresponding to one or more computing power services. Different resource release tasks correspond to different computing power services.

28. A communication device, characterized in that, include: One or more processors; The communication device is used to execute the resource release method according to any one of claims 1-13 or any one of claims 14-25.

29. A communication system, characterized in that, The device includes a first device and a second device, wherein the first device is configured to implement the resource release method according to any one of claims 1-13, and the second device is configured to implement the resource release method according to any one of claims 14-25.

30. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the resource release method as claimed in any one of claims 1-13 or any one of claims 14-25.

31. A computer program product, comprising a computer program and / or instructions, characterized in that, When the computer program and / or the instructions are executed by the communication device, they implement the resource release method as claimed in any one of claims 1-13 or any one of claims 14-25.

Images