WO2024138760A1

WO2024138760A1 - Resource release method, apparatus, device, and storage medium

Info

Publication number: WO2024138760A1
Application number: PCT/CN2022/144375
Authority: WO
Inventors: 李艳华
Original assignee: 北京小米移动软件有限公司
Priority date: 2022-12-30
Filing date: 2022-12-30
Publication date: 2024-07-04

Abstract

The present disclosure relates to the technical field of communications and provides a resource release method, an apparatus, a device, and a storage medium. The method comprises: a first node receives release information, and according to the release information, releases a resource related to a third node, wherein the third node comprises a first logic unit and a second logic unit, and the first node is a source donor node of the first logic unit in the third node. The resource release method provided by the present disclosure can avoid resource waste, and improve the utilization rate of resources.

Description

A resource release method/device/equipment and storage medium

Technical Field

The present disclosure relates to the field of communication technology, and in particular to a resource releasing method/device/equipment and a storage medium.

Background technique

The Integrated access and backhaul (IAB) system supports millimeter wave base stations for wireless access and backhaul, which can effectively reduce the demand for fiber deployment when deploying dense networks, making wireless relay on the 5G radio access network (Next Generation Radio Access Network, NG RAN) possible. Therefore, improving the application method of the IAB system is a technical problem that needs to be solved urgently.

Summary of the invention

The present disclosure proposes a resource release method, device, equipment and storage medium for releasing resources of a node.

In a first aspect, an embodiment of the present disclosure provides a resource release method, which is executed by a first node and includes:

Receive release information;

According to the release information, releasing resources related to the third node;

Wherein, the third node includes a first logic unit and a second logic unit;

The first node is a source host node of a first logical unit in the third node.

In the resource release method provided by the present invention, when a node is switched out from a source host node and/or a node is migrated from a source host node, since the source host node of the node will no longer transmit the data of the node, the source host node will release the resources related to the node based on the received release information, thereby preventing the related resources of the switched out node from occupying the storage space of the source host node all the time, thereby avoiding waste of resources and improving resource utilization.

In a second aspect, an embodiment of the present disclosure provides a resource release method, which is executed by a second node and includes:

Sending release information to the first node, where the release information is used for: the first node to release resources related to the third node according to the release information;

Wherein, the third node includes a first logic unit and a second logic unit;

The first node is a source host node of the first logical unit in the third node;

The second node is a target host node of the first logical unit in the third node.

In a third aspect, an embodiment of the present disclosure provides a resource release method, which is executed by a third node and includes:

Wherein, the third node includes a first logic unit and a second logic unit;

The first node is a source host node of a first logical unit in the third node.

In a fourth aspect, an embodiment of the present disclosure provides a resource release method, which is executed by a fourth node and includes:

Sending second release information to the first node, where the second release information is used for: the first node to release resources related to the third node according to the second release information;

Wherein, the third node includes a first logic unit and a second logic unit;

The fourth node is a host node of the second logic unit in the third node.

In a fifth aspect, an embodiment of the present disclosure provides a communication device, including:

A transceiver module, used for receiving release information;

A processing module, configured to release resources related to the third node according to the release information;

Wherein, the third node includes a first logic unit and a second logic unit;

The first node is a source host node of a first logical unit in the third node.

In a sixth aspect, an embodiment of the present disclosure provides a communication device, including:

A transceiver module, configured to send release information to the first node, wherein the release information is used for: the first node to release resources related to the third node according to the release information;

Wherein, the third node includes a first logic unit and a second logic unit;

In a seventh aspect, an embodiment of the present disclosure provides a communication device, including:

Wherein, the third node includes a first logic unit and a second logic unit;

The first node is a source host node of the first logical unit in the third node.

In an eighth aspect, an embodiment of the present disclosure provides a communication device, which is configured in a base station, including:

A transceiver module, configured to send second release information to the first node, wherein the second release information is used for: the first node to release resources related to the third node according to the release information;

Wherein, the third node includes a first logic unit and a second logic unit;

The fourth node is a host node of the second logic unit in the third node.

In a ninth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in any one of the first to fourth aspects is executed.

In the tenth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in any one of the first to fourth aspects above.

In the eleventh aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in any one of the first to fourth aspects above.

In aspect 12, an embodiment of the present disclosure provides a communication system, the system comprising the communication device described in aspect 4 to the communication device described in aspect 8, or the system comprising the communication device described in aspect 9, or the system comprising the communication device described in aspect 10, or the system comprising the communication device described in aspect 11.

In the thirteenth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions used for the above-mentioned network device. When the instructions are executed, the terminal device executes the method described in any one of the above-mentioned first to fourth aspects.

In a fourteenth aspect, the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in any one of the first to fourth aspects above.

In a fifteenth aspect, the present disclosure provides a chip system, which includes at least one processor and an interface, and is used to support a network device to implement the functions involved in the method described in any one of the first aspect to the fourth aspect, for example, determining or processing at least one of the data and information involved in the above method. In one possible design, the chip system also includes a memory, and the memory is used to store computer programs and data necessary for the source auxiliary node. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

In a sixteenth aspect, the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the method described in any one of the first to fourth aspects above.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and/or additional aspects and advantages of the present disclosure will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

FIG1a is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;

FIG1b is a schematic diagram of an IAB-node performing a partial migration according to an embodiment of the present disclosure;

FIG1c is a schematic diagram of an IAB-node performing two partial migrations provided by an embodiment of the present disclosure;

FIG2 is a schematic flow chart of a resource release method provided by another embodiment of the present disclosure;

FIG3 is a schematic diagram of a flow chart of a resource release method provided in yet another embodiment of the present disclosure;

FIG4 is a schematic diagram of a flow chart of a resource release method provided by yet another embodiment of the present disclosure;

FIG5 is a schematic flow chart of a resource release method provided in another embodiment of the present disclosure;

FIG6 is a schematic diagram of a flow chart of a resource release method provided in yet another embodiment of the present disclosure;

FIG7 is a schematic flow chart of a resource release method provided by yet another embodiment of the present disclosure;

FIG8 is a schematic diagram of a flow chart of a resource release method provided by an embodiment of the present disclosure;

FIG9 is a schematic diagram of a flow chart of a resource release method provided by an embodiment of the present disclosure;

FIG10 is a schematic diagram of a flow chart of a resource release method provided by an embodiment of the present disclosure;

FIG11 is a schematic diagram of a flow chart of a resource release method provided by an embodiment of the present disclosure;

FIG12 is a schematic diagram of a flow chart of a resource release method provided by an embodiment of the present disclosure;

FIG13 is a schematic diagram of a flow chart of a resource release method provided by an embodiment of the present disclosure;

FIG14 is a schematic diagram of a flow chart of a resource release method provided by an embodiment of the present disclosure;

FIG15a is a schematic diagram of a flow chart of a resource release method provided by an embodiment of the present disclosure;

FIG15b is a schematic diagram of a flow chart of a resource release method provided by an embodiment of the present disclosure;

FIG16 is a schematic diagram of an interactive process of a resource release method provided in an embodiment of the present disclosure;

FIG17 is a schematic diagram of the structure of a communication device provided by an embodiment of the present disclosure;

FIG18 is a schematic diagram of the structure of a communication device provided by another embodiment of the present disclosure;

FIG19 is a schematic diagram of the structure of a communication device provided by an embodiment of the present disclosure;

FIG20 is a schematic diagram of the structure of a communication device provided by an embodiment of the present disclosure;

FIG21 is a block diagram of a user equipment provided by an embodiment of the present disclosure;

FIG22 is a block diagram of a network-side device provided by an embodiment of the present disclosure.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the embodiments of the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the embodiments of the present disclosure as detailed in the appended claims.

The terms used in the disclosed embodiments are only for the purpose of describing specific embodiments and are not intended to limit the disclosed embodiments. The singular forms of "a" and "the" used in the disclosed embodiments and the appended claims are also intended to include plural forms unless the context clearly indicates other meanings. It should also be understood that the term "and/or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

It should be understood that although the terms first, second, third, etc. may be used to describe various information in the disclosed embodiments, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the disclosed embodiments, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the words "if" and "if" as used herein may be interpreted as "at" or "when" or "in response to determination".

Embodiments of the present disclosure are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present disclosure, and should not be construed as limiting the present disclosure.

To facilitate understanding, the terms involved in this application are first introduced.

1. IAB-node

The relay node in the IAB system supports wireless access and backhaul through the New Radio (NR). The IAB-node is connected to the User Equipment (UE) downstream and to another IAB node or IAB-donor upstream.

2. IAB-donor

The terminating node of NR backhaul on the network side is called IAB-donor, which is a gNB with IAB functions attached. IAB-donor is connected to IAB-node downstream and core network upstream, and is used to transmit information between IAB-node and UE back to the core network, and transmit information from the core network to IAB-node and UE. IAB-donor is also responsible for managing IAB-node in the entire IAB network.

In order to better understand a resource release method disclosed in an embodiment of the present disclosure, a communication system to which the embodiment of the present disclosure is applicable is first described below.

Please refer to Figure 1a, which is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure. The communication system may include but is not limited to an IAB-donor and an IAB-node, wherein the number and form of devices shown in Figure 1a are only used for example and do not constitute a limitation on the embodiment of the present disclosure, and may include one or more IAB-donors or one or more IAB-nodes in actual applications. The communication system shown in Figure 1a takes one IAB-donor and two IAB-nodes as an example.

As shown in FIG1a, IAB-donor may include two parts: an integrated access and backhaul host node distributed unit (IAB-donor Distributed Unit, IAB-donor-DU) and an integrated access and backhaul host node centralized unit (IAB-donor Central Unit, IAB-donor-CU). In addition, IAB-node includes: an integrated access and backhaul mobile terminal (IAB Mobile Termination, IAB-MT) and IAB-DU, wherein IAB-MT and IAB-DU are not shown in FIG1a, but are shown in the subsequent FIG1b and FIG1c. In addition, the IAB-donor is connected to the 5G core network (5generation core, 5GC) upstream (such as access and mobility management function (AMF) network element or user plane function (UPF) network element), and is connected to the IAB-node downstream. The IAB-node is connected to other IAB-nodes upstream or to the IAB-donor-CU through the IAB-donor-DU, and is connected to the UE downstream. Therefore, the information of the IAB-node and the UE can be backtransmitted to the core network through the IAB-donor, and the information of the core network can be transmitted to the UE through the IAB-donor and the IAB-node, thereby realizing wireless backtransmission of information.

Among them, in R18, mobile IAB-node is supported. When IAB-node is mobile, the IAB-donor-CU connected to the IAB-node may change with the movement of the IAB-node, so it is necessary to perform the IAB-node migration process. Optionally, the migration process can be a partial migration, which means that only the IAB-MT on the IAB-node migrates (also called switching) to a new IAB-donor-CU, while the IAB-DU on the IAB-node still maintains the connection with the original IAB donor.

Among them, along with the movement of the IAB-node, the IAB-node may undergo multiple partial migrations. Figure 1b is a schematic diagram of an IAB-node provided in an embodiment of the present disclosure performing one partial migration; Figure 1c is a schematic diagram of an IAB-node provided in an embodiment of the present disclosure performing two partial migrations; as shown in Figure 1b, the IAB-node includes IAB-MT and IAB-DU1. Before the partial migration is performed, IAB-donor-CU1 is the donor of the initial service IAB-node, and IAB-donor-CU1 can be called F1 terminating IAB-donor-CU. At this time, the data of IAB-MT and IAB-DU1 are transmitted through IAB-donor-CU1. After the first partial migration, the IAB-MT of the IAB-node migrates from IAB-donor-CU1 to IAB-donor-CU2. IAB-donor-CU2 is called non F1 terminating IAB donor. At this time, IAB-MT is connected to IAB-donor-CU2 through IAB-donor-DU2, and the data of IAB-MT is transmitted through IAB-donor-CU2. Also, although IAB-DU1 is still connected to IAB-donor-CU1, the transmission path between IAB-DU1 and IAB-donor-CU1 has changed. The transmission path between IAB-DU1 and IAB-donor-CU1 has changed from "connected to IAB-donor-CU1 through IAB-donor-DU1" to "connected to IAB-donor-CU1 through IAB-donor-DU2". At this time, it is necessary to migrate the transmission path between IAB-DU1 and IAB-donor-CU1, specifically, to migrate the transmission path from "the transmission path of IAB-DU1 connecting to IAB-donor-CU1 through IAB-donor-DU1" to "the transmission path of IAB-DU1 connecting to IAB-donor-CU1 through IAB-donor-DU2", thereby allowing the data of IAB-DU1 to still be transmitted through IAB-donor-CU1 via IAB-donor-DU2.

As shown in reference figure 1c, after the second partial migration, the IAB-MT of the IAB-node migrates from IAB-donor-CU2 to IAB-donor-CU3. At this time, the data of the IAB-MT is transmitted through IAB-donor-CU3, and the transmission path between IAB-DU1 and IAB-donor-CU1 is also migrated, so that the data of IAB-DU1 is still transmitted through IAB-donor-CU1 via IAB-donor-DU3, while the data of IAB-MT and IAB-DU1 are no longer transmitted through IAB-donor-CU2 and IAB-donor-DU2, that is, IAB-donor-CU2 and IAB-donor-DU2 will no longer transmit the data of IAB-MT and IAB-DU1 in the future, but IAB-donor-CU2 and IAB-donor-DU2 will still keep the relevant resources of the IAB-node (such as context and transmission path), which will cause waste of resources.

Therefore, in view of the situation where multiple partial migrations of IAB-node occur, it is urgent to propose a resource release method to release relevant resources of IAB-donor that no longer transmits data of IAB-node, so as to avoid waste of resources and improve resource utilization.

It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

The resource release method, apparatus, device and storage medium provided in the embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

It should be noted that in the present disclosure, the resource release method provided in any embodiment can be executed alone, and any implementation method in the embodiment can also be executed alone, or combined with other embodiments, or possible implementation methods in other embodiments, and can also be executed together with any technical solution in the related technology.

FIG2 is a flow chart of a resource release method provided by an embodiment of the present disclosure. The method is executed by a first node. As shown in FIG2 , the resource release method may include the following steps:

Step 201: Receive release information.

In an embodiment of the present disclosure, the "release information" may also be referred to as "information for indicating release", and both have the same meaning. Furthermore, the release information may be used for: the first node to release resources related to the third node according to the release information.

The third node may include a first logic unit and a second logic unit, and the first node may be a source host node of the first logic unit in the third node. For example, the third node may be an IAB-node or a mobile IAB-node (hereinafter referred to as "IAB-node"), the first logic unit may be an IAB-MT in the IAB-node, the second logic unit may be an IAB-DU in the IAB-node, and the first node may be a source IAB-donor-CU of the IAB-MT in the IAB-node, that is, the IAB-donor-CU to which the IAB-MT in the IAB-node is connected before partial migration.

Optionally, in one embodiment of the present disclosure, the method shown in FIG. 2a can be applied to the scenario where the first logic unit of the third node is partially migrated to switch out from the first node. Specifically, when the first logic unit of the third node is partially migrated, the host node to which the first logic unit of the third node is connected will change, while the host node to which the second logic unit of the third node is connected will not change. That is, only the first logic unit of the third node is switched from the source host node to the target host node, while the second logic unit of the third node is still connected to the original host node. And, when the partial migration of the first logic unit of the third node is completed, the second logic unit will also be migrated, wherein the transmission path between the second logic unit and the host node of the second logic unit can be migrated (for example, the aforementioned migration of the transmission path from "IAB-DU1 connected to IAB-donor-CU1 via IAB-donor-DU1" to "IAB-DU1 connected to IAB-donor-CU1 via IAB-donor-DU2"), thereby realizing the partial migration of the first logic unit of the third node.

Optionally, in one embodiment of the present disclosure, the release information may include first release information and/or second release information. The first release information may be sent to the first node when the first logical unit of the third node has completed partial migration, and the first release information may be included in a message indicating that the switching of the first logical unit is completed, such as being included in UE context release information. The second release information may be sent to the first node when the second logical unit of the third node has completed migration; the second release information may be included in a message indicating that the migration of the second logical unit is completed, such as being included in a migration completion message.

Optionally, in an embodiment of the present disclosure, the first release information may include at least one of the following:

The first indication information is used to instruct the first node to perform a release operation;

Identification information is used to indicate the identification of the third node. The identification information may be, for example, NG-RAN node UE XnAP ID.

Optionally, in an embodiment of the present disclosure, the second release information may include at least one of the following:

The second indication information is used to indicate that the migration of the second logical unit of the third node is completed. For example, the value of the migration process of the second logical unit indicated by the second indication information may be {True};

Optionally, in an embodiment of the present disclosure, the receiving of the first release information may include:

Receive first release information sent by the second node and/or the third node.

Optionally, in one embodiment of the present disclosure, the second node may be the target host node of the first logical unit in the third node, that is, the second node is: the host node to which the first logical unit in the third node is connected after being switched from the first node. By way of example, the second node may be the target IAB-donor-CU of the IAB-MT in the IAB-node.

Optionally, in an embodiment of the present disclosure, the receiving of the second release information may include:

Receive second release information sent by at least one of the second node, the third node, and the fourth node.

Optionally, in an embodiment of the present disclosure, the fourth node may be a host node of the second logic unit of the third node. For example, the fourth node may be an IAB-donor-CU of an IAB-DU in an IAB-node.

Optionally, in some embodiments, when the above-mentioned release information is sent by different nodes, the identification information included therein may also be different. Specifically, when the second release information is received by the first node from the fourth node, the above-mentioned identification information may include the NG-RAN node UE XnAP ID of the third node in the IAB-DU's IAB-donor-CU and/or the NG-RAN node UE XnAP ID of the third node in the IAB-MT's source IAB-donor-CU; in other embodiments, when the release information is received by the first node from the second node, the above-mentioned identification information may include the NG-RAN node UE XnAP ID of the third node in the IAB-MT's target IAB-donor-CU and/or the NG-RAN node UE XnAP ID of the third node in the IAB-MT's source IAB-donor-CU.

Step 202: Release resources related to the third node according to the release information.

In one embodiment of the present disclosure, it can be seen from the foregoing content that when the first node receives the above-mentioned release information, it indicates that the first logical unit of the third node has been switched out from the first node, that is, the data of the first logical unit of the third node is no longer transmitted via the first node, or it also indicates that the second logical unit of the third node has also been migrated from the first node, that is, the transmission of the second logical unit of the third node no longer passes through the first node. At this time, the first node can release the resources related to the third node.

Optionally, in one embodiment of the present disclosure, the execution premise of the above-mentioned "releasing resources related to the third node" should be that the third node has currently undergone at least two partial migrations. Specifically, if the third node has not currently undergone at least two partial migrations, but has only undergone one partial migration, at this time, the source host node of the first logical unit in the third node (that is, the aforementioned first node) is actually the host node that initially serves the third node, and because the host node of the second logical unit of the third node does not switch, the host node of the second logical unit of the third node is always connected to the host node that initially serves the third node, that is, the first node is both the source host node of the first logical unit of the third node and no longer transmits data of the first logical unit of the third node. At the same time, the first node also serves the second logical unit of the third node, that is, the first node also transmits the second logical unit of the third node. Data (refer to IAB-donor-CU1 in the aforementioned FIG1b). At this time, if the first node releases the resources related to the third node, the data of the second logical unit of the third node may be unable to be transmitted. Therefore, in order to avoid affecting the transmission, when the third node has only undergone one partial migration, the source host node of the first logical unit of the third node (i.e., the first node) no longer releases the data related to the third node. Only when the third node has undergone at least two partial migrations, since the source host node of the first logical unit of the third node (i.e., the first node) no longer transmits the data of the third node (refer to IAB-donor-CU2 in the aforementioned FIG1c), the data related to the third node can be released.

Based on this, in one embodiment of the present disclosure, the above-mentioned “releasing resources related to the third node” may include at least one of the following:

First, in response to the third node being movable, releasing resources associated with the third node;

Among them, when the third node is movable, it means that the third node may have undergone multiple partial migrations, that is, more than two partial migrations may have occurred, and the prerequisite for release is met. At this time, the resources related to the third node can be released.

Second, in response to the first node not being the host node of the second logical unit of the third node, releasing resources related to the third node.

Optionally, since the first node is the host node of the second logical unit of the third node only during the first partial migration, and the first node is not the host node of the second logical unit of the third node during subsequent partial migrations, when the first node is not the host node of the second logical unit of the third node, it means that the current partial migration is not the first partial migration, that is, the current partial migration may be the second or Nth (N is greater than 2) partial migration, and the prerequisite for release is met, and the resources related to the third node can be released at this time.

A third type is to release resources related to the third node in response to the third node having performed at least one partial migration before performing the current partial migration.

Optionally, when the third node has performed at least one partial migration before performing this partial migration, it means that at least two partial migrations have been performed currently, and the prerequisite for release is met. At this time, the resources related to the third node can be released.

Optionally, in an embodiment of the present disclosure, the specific release operation of “releasing resources related to the third node” may include at least one of the following:

releasing context information of the third node, where the context information of the third node may include context information of the first logical unit in the third node and/or context information of the second logical unit in the third node;

Release the identifier of the third node;

A communication path of the third node in the first node network topology is released.

Optionally, in one embodiment of the present disclosure, the above-mentioned “communication path of the third node under the first node network topology” may include: the communication path of the first logical unit of the third node under the first node network topology, and/or, the communication path of the second logical unit of the third node under the first node network topology.

Optionally, in an embodiment of the present disclosure, the aforementioned “release” is merely an illustrative illustration of the present disclosure, and it should be understood that “release” has the same meaning as words such as “not save”, “delete”, and “eliminate”, and other words that are synonyms of “release” are all within the protection scope of the present disclosure.

In summary, in the resource release method provided by the embodiment of the present disclosure, when the first node receives the release information, it will release the resources related to the third node according to the release information; wherein the third node includes a first logical unit and a second logical unit; the first node is the source host node of the first logical unit in the third node. It can be seen that in the embodiment of the present disclosure, when a node is switched out from the source host node and/or when a node is migrated from the source host node, since the source host node of the node will no longer transmit the data of the node, the source host node will release the resources related to the node based on the received release information, thereby preventing the related resources of the node that has been switched out from occupying the storage space of the source host node, thereby avoiding the waste of resources and improving the utilization of resources.

FIG3 is a flow chart of a resource release method provided by an embodiment of the present disclosure. The method is executed by a first node. As shown in FIG3 , the resource release method may include the following steps:

Step 301: Receive first release information sent by a second node.

For example, in one embodiment of the present disclosure, the third node may be an IAB-node, or a movable IAB-node; the first node may be a source IAB-donor-CU of an IAB-MT in the IAB-node; the second node may be a target IAB-donor-CU of an IAB-MT in the IAB-node; and the fourth node may be an IAB-donor-CU of an IAB-DU in the IAB-node.

For a detailed description of step 301, please refer to the description of the aforementioned embodiment.

To summarize, in the resource release method provided by the embodiments of the present invention, when a node is switched out from a source host node and/or when a node is migrated from a source host node, since the source host node of the node will no longer transmit the data of the node, the source host node will release the resources related to the node based on the received release information, thereby preventing the related resources of the switched out node from occupying the storage space of the source host node all the time, thereby avoiding waste of resources and improving resource utilization.

FIG4 is a flow chart of a resource release method provided by an embodiment of the present disclosure. The method is executed by a first node. As shown in FIG4 , the resource release method may include the following steps:

Step 401: Receive first release information sent by a third node.

For a detailed description of step 401, please refer to the description of the aforementioned embodiment.

FIG5 is a flow chart of a resource release method provided by an embodiment of the present disclosure. The method is executed by a first node. As shown in FIG5 , the resource release method may include the following steps:

Step 501: Receive second release information sent by a second node.

For a detailed description of step 501, please refer to the description of the aforementioned embodiment.

FIG6 is a flow chart of a resource release method provided by an embodiment of the present disclosure. The method is executed by a first node. As shown in FIG6 , the resource release method may include the following steps:

Step 601: Receive second release information sent by a third node.

For a detailed description of step 601, please refer to the description of the aforementioned embodiment.

To summarize, in the resource releasing method provided by the embodiments of the present invention, when a node is switched out from a source host node and/or when a node is migrated from a source host node, since the source host node of the node will no longer transmit the data of the node, the source host node will release the resources related to the node based on the received release information, thereby preventing the related resources of the switched out node from occupying the storage space of the source host node all the time, thereby avoiding waste of resources and improving resource utilization.

FIG. 7 is a flow chart of a resource release method provided in an embodiment of the present disclosure. The method is executed by a first node. As shown in FIG. 7 , the resource release method may include the following steps:

Step 701: Receive second release information sent by the fourth node.

For a detailed description of step 701, please refer to the description of the aforementioned embodiment.

FIG8 is a flow chart of a resource release method provided by an embodiment of the present disclosure. The method is executed by a first node. As shown in FIG8 , the resource release method may include the following steps:

Step 801: In response to a first node being a host node of a second logical unit of a third node, resources related to the third node are not released.

Optionally, in one embodiment of the present disclosure, when the first node is the host node of the second logical unit of the third node, it means that the current is the first partial switching of the first logical unit. At this time, the data of the second logical unit of the third node still needs to be transmitted through the first node, so that the resources related to the third node may not be released.

Optionally, in an embodiment of the present disclosure, the aforementioned “not releasing” is merely an illustrative illustration of the present disclosure, and it should be understood that “not releasing” has the same meaning as words such as “saving” and “storing”, and other words that are synonymous with “not releasing” are all within the protection scope of the present disclosure.

In addition, for a detailed description of step 801, reference may be made to the description of the aforementioned embodiment.

In summary, in the resource release method provided by the embodiment of the present disclosure, in response to the first node being the host node of the second logical unit of the third node, the resources related to the third node are not released. That is, when the third node undergoes the first partial switching, since the source host node (i.e., the first node) of the first logical unit of the third node is the same as the host node of the second logical unit of the third node, the first node should not release the resources related to the third node to ensure that the second logical unit of the third node can transmit data normally.

FIG9 is a flow chart of a resource release method provided by an embodiment of the present disclosure. The method is executed by the second node. As shown in FIG9 , the resource release method may include the following steps:

Step 901: Send release information to the first node.

Optionally, in an embodiment of the present disclosure, the release information may be used for: the first node to release resources related to the third node according to the release information. For the introduction of the first node, the second node, and the third node, reference may be made to the above embodiments.

Optionally, in one embodiment of the present disclosure, the release information may include first release information and second release information. The first release information may be included in a message indicating that the first logical unit switching is completed, such as included in UE context release information. In one embodiment of the present disclosure, for the second node, "the first logical unit switching is completed" is specifically reflected as follows: when the second node receives a Radio Resource Control (RRC) reconfiguration complete (Reconfiguration Complete) message sent by the third node, it is considered that the first logical unit switching of the first node is completed.

Optionally, the second release information may be included in a message indicating completion of the migration of the second logical unit (e.g., a migration completion message or a transmission migration completion message). Optionally, the message indicating completion of the migration of the second logical unit may be an XnAP message. Optionally, "completion of the migration of the second logical unit" may be specifically embodied as follows: when the transmission path between the second logical unit and the host node of the second logical unit is migrated from the topology of the source host node of the first logical unit to the topology of the target host node of the first logical unit, the migration of the second logical unit is considered to be completed or the transmission migration is completed.

For a detailed description of the above step 901, please refer to the description of the above embodiment.

FIG10 is a flow chart of a resource release method provided in an embodiment of the present disclosure. The method is executed by the second node. As shown in FIG10 , the resource release method may include the following steps:

Step 1001: Send first release information to a first node.

For a detailed description of the above step 1001, please refer to the description of the above embodiment.

FIG11 is a flow chart of a resource release method provided in an embodiment of the present disclosure. The method is executed by a second node. As shown in FIG11 , the resource release method may include the following steps:

Step 1101: Send second release information to the first node.

FIG12 is a flow chart of a resource release method provided in an embodiment of the present disclosure. The method is executed by a third node. As shown in FIG12 , the resource release method may include the following steps:

Step 1201: Send release information to the first node.

Optionally, in one embodiment of the present disclosure, the release information may include first release information and second release information. The first release information may be included in a message indicating that the first logical unit switching is completed, for example, included in an RRC reconfiguration complete message, or, as included in UE context release information.

Optionally, the second release information may be included in a message indicating completion of migration of the second logical unit (e.g., a migration completion message or a transmission migration completion message). Optionally, the message indicating completion of migration of the second logical unit is an XnAP message. Optionally, "completion of migration of the second logical unit" may be specifically embodied as follows: when the transmission path between the second logical unit and the host node of the second logical unit is migrated from the topology of the source host node of the first logical unit to the topology of the target host node of the first logical unit, the migration of the second logical unit is considered to be completed or the transmission migration is completed.

For a detailed description of the above step 1201, please refer to the description of the above embodiment.

FIG13 is a flow chart of a resource release method provided in an embodiment of the present disclosure. The method is executed by a third node. As shown in FIG13 , the resource release method may include the following steps:

Step 1301: Send first release information to a first node.

For a detailed description of the above step 1301, please refer to the description of the above embodiment.

FIG. 14 is a flow chart of a resource release method provided in an embodiment of the present disclosure. The method is executed by a third node. As shown in FIG. 14 , the resource release method may include the following steps:

Step 1401: Send second release information to the first node.

For a detailed description of the above step 1401, please refer to the description of the above embodiment.

FIG. 15a is a flow chart of a resource release method provided by an embodiment of the present disclosure. The method is executed by a fourth node. As shown in FIG. 15a , the resource release method may include the following steps:

Step 1501a: Send release information to the first node.

Optionally, in one embodiment of the present disclosure, the release information may include second release information. Optionally, the second release information may be included in a message indicating that the migration of the second logical unit is complete (e.g., a migration completion message or a transmission migration completion message). Optionally, the message indicating that the migration of the second logical unit is complete is an XnAP message. Optionally, "the second logical unit migration is complete" may be specifically reflected as follows: when the transmission path between the second logical unit and the host node of the second logical unit is migrated from the topology of the source host node of the first logical unit to the topology of the target host node of the first logical unit, the second logical unit migration is considered to be complete or the transmission migration is complete.

For a detailed description of the above step 1501a, please refer to the description of the aforementioned embodiment.

FIG15b is a flow chart of a resource release method provided by an embodiment of the present disclosure. The method is executed by a fourth node. As shown in FIG15 , the resource release method may include the following steps:

Step 1501b: Send second release information to the first node.

Optionally, in an embodiment of the present disclosure, the second release information may be used for: the first node releases resources related to the third node according to the second release information. The relevant introduction of the first node, the second node, the third node, and the fourth node may refer to the above embodiment.

Optionally, the second release information may be included in a message indicating that the migration of the second logical unit is completed (e.g., a migration completion message or a transmission migration completion message). Optionally, the message indicating that the migration of the second logical unit is completed may be an XnAP message. Optionally, "the migration of the second logical unit is completed" may be specifically embodied as follows: when the transmission path between the second logical unit and the host node of the second logical unit is migrated from the topology of the source host node of the first logical unit to the topology of the target host node of the first logical unit, the migration of the second logical unit is considered to be completed or the transmission migration is completed. .

For a detailed description of the above step 1501, please refer to the description of the aforementioned embodiment.

Based on the above description, FIG16 is a schematic diagram of an interaction process of a resource release method provided by an embodiment of the present disclosure, wherein the IAB-node in FIG16 is the aforementioned third node, the IAB-DU in the IAB-node is the aforementioned second logical unit of the third node, and the IAB-MT in the AB node is the aforementioned first logical unit of the third node; the IAB-DU's IAB-donor is the aforementioned fourth node, the IAB-MT's Source IAB-donor is the aforementioned first node, and the IAB-MT's Target IAB-donor is the aforementioned second node. As shown in FIG16, the interaction method may include the following steps:

Step 0, after a partial migration, the IAB-DU's IAB-donor-CU and IAB-MT's source IAB-donor-CU retain the NG-RAN node UE XnAP IDs of the IAB-node.

Step 1-5, the IAB-MT on the IAB-node performs the handover.

In step 5, IAB-MT's target IAB-donor-CU or IAB-dono sends a UE context release message to IAB-MT's source IAB-donor-CU.

In one embodiment, if the IAB-node is a mobile IAB-node, after receiving the UE context release message, the IAB-MT's source IAB-donor-CU performs a release operation related to the IAB-node.

In another embodiment, if the IAB-MT's source IAB-donor-CU is different from the IAB-DU's IAB-donor-CUB, the IAB-MT's source IAB-donor-CU performs a release operation related to the IAB-node after receiving the UE context release message.

In another embodiment, if the IAB-node has performed at least one partial migration, the IAB-MT's source IAB-donor-CU performs a release operation related to the IAB-node after receiving the UE context release message.

In some other embodiments, the UE context release message includes a first indication (e.g., a release indication) for indicating that the first node can perform a release operation related to a third node, and the IAB-MT's source IAB-donor-CU performs a release operation related to the IAB-node according to the first indication.

Among them, executing the release operation related to the third node includes: not retaining or releasing the IAB-DU's IAB-donor-CU and IAB-MT's source IAB-donor-CU will retain the NG-RAN node UE XnAP IDs of the IAB-node.

In step 6-11, the IAB-DU's IAB-donor-CU initiates the IAB transport migration management process to migrate the communication path between the IAB-node and the IAB-DU's IAB-donor-CU from the path under the IAB-MT's source IAB-donor-CU to the IAB-MT's target IAB-donor-CU communication path.

In step 12, the IAB-MT's source IAB-donor-CU receives second information from the IAB-DU's IAB-donor-CU or the IAB-MT's target IAB-donor-CU or the IAB-node.

The second information includes at least one of the following information:

-Information used to indicate the completion of the IAB transfer migration management process;

- Used to indicate the release operation information related to the execution of IAB-node;

-NG-RAN node UE XnAP IDs used to indicate IAB-node

In some embodiments, the IAB-MT's source IAB-donor-CU receives second information from the IAB-DU's IAB-donor-CU, and the NG-RAN node UE XnAP IDs for indicating the IAB-node include the NG-RAN node UE XnAP ID of the IAB-node in the IAB-DU's IAB-donor-CU and/or the NG-RAN node UE XnAP ID of the IAB-MT's source IAB-donor-CU; in other embodiments In the embodiment, the IAB-MT's source IAB-donor-CU receives second information from the IAB-MT's target IAB-donor-CU, and the NG-RAN node UE XnAP IDs for indicating the IAB-node include the NG-RAN node UE XnAP ID of the IAB-node in the IAB-MT's target IAB-donor-CU and/or the NG-RAN node UE XnAP ID of the IAB-MT's source IAB-donor-CU.

In some embodiments, the second information is included in an XnAP message, for example, the second information is a migration completion notification message, etc.

The IAB-MT's source IAB-donor-CU performs a release operation related to the IAB-node according to the second information, and the release operation related to the IAB-node includes at least one of the following:

- Release the IAB-MT context;

- Release the UE identity that retains IAB-MT (i.e., NG-RAN node UE XnAP ID) or do not retain the UE identity that retains IAB-MT;

- Release the communication path of IAB-node under IAB-MT's source IAB-donor;

FIG. 17 is a schematic diagram of the structure of a communication device provided by an embodiment of the present disclosure. As shown in FIG. 17 , the device may include:

A transceiver module, used for receiving release information;

Wherein, the third node includes a first logic unit and a second logic unit;

The first node is a source host node of a first logical unit in the third node.

In summary, in the communication device provided in the embodiment of the present disclosure, when the first node receives the release information, it will release the resources related to the third node according to the release information; wherein the third node includes a first logical unit and a second logical unit; the first node is the source host node of the first logical unit in the third node. It can be seen that in the embodiment of the present disclosure, when a node is switched out from the source host node and/or when a node is migrated from the source host node, since the source host node of the node will no longer transmit the data of the node, the source host node will release the resources related to the node based on the received release information, thereby preventing the related resources of the node that has been switched out from occupying the storage space of the source host node all the time, thereby avoiding the waste of resources and improving the utilization of resources.

Optionally, in an embodiment of the present disclosure, the release information includes at least one of the following:

first release information, wherein the first release information is included in a message indicating that the switching of the first logical unit is completed;

The second release information is included in a message indicating that the migration of the second logical unit is completed.

Optionally, in one embodiment of the present disclosure, the first logic unit is a mobile terminal MT; and the second logic unit is a distributed unit DU.

first indication information, used to instruct the first node to perform a release operation to release resources related to the third node;

The second indication information is used to indicate that the migration of the second logical unit of the third node is completed;

The identification information is used to indicate the identification of the third node.

Optionally, in an embodiment of the present disclosure, the transceiver module is used for at least one of the following:

receiving the first release information sent by the second node and/or the third node;

Receive the second release information sent by at least one of the second node, the third node, and the fourth node.

Optionally, in an embodiment of the present disclosure, the second node is a target host node of the first logical unit of the third node;

The fourth node is a host node of the second logical unit of the third node.

Optionally, in an embodiment of the present disclosure, the processing module is used for at least one of the following:

In response to the third node being movable, releasing resources associated with the third node;

In response to the first node not being a host node of a second logical unit of a third node, releasing resources associated with the third node;

In response to the third node having performed at least one partial migration before performing the current partial migration, resources related to the third node are released.

Optionally, in one embodiment of the present disclosure, the device is further used for:

In response to the first node being a host node of a second logical unit of a third node, resources associated with the third node are not released.

Optionally, in an embodiment of the present disclosure, the processing module is further used for at least one of the following:

releasing context information of the third node, wherein the context information of the third node includes context information of the first logical unit in the third node and/or context information of the second logical unit in the third node;

releasing the identifier of the third node;

The communication path of the third node in the first node network topology is released.

Optionally, in an embodiment of the present disclosure, the third node is an integrated access and backhaul node IAB-node, or a movable IAB-node;

The first node is a source integrated access and backhaul host node centralized unit IAB-donor-CU of an integrated access and backhaul node mobile terminal IAB-MT in the IAB-node;

The second node is the target IAB-donor-CU of the IAB-MT in the IAB-node;

The fourth node is the IAB-donor-CU- of the integrated access and backhaul node distributed unit IAB-DU in the IAB-node.

FIG. 18 is a schematic diagram of the structure of a communication device provided by an embodiment of the present disclosure. As shown in FIG. 18 , the device may include:

Wherein, the third node includes a first logic unit and a second logic unit;

In summary, in the communication device provided in the embodiment of the present disclosure, in response to the first node being the host node of the second logical unit of the third node, the resources related to the third node are not released. That is, when the third node undergoes the first partial switching, since the source host node (i.e., the first node) of the first logical unit of the third node is the same as the host node of the second logical unit of the third node, the first node should not release the resources related to the third node to ensure that the second logical unit of the third node can transmit data normally.

Optionally, in an embodiment of the present disclosure, the first logic unit is MT; and the second logic unit is DU.

Optionally, in an embodiment of the present disclosure, the third node is an IAB-node, or a movable IAB-node;

The first node is a source IAB-donor-CU of the IAB-MT in the IAB-node;

The second node is a target IAB-donor-CU of the IAB-MT in the IAB-node.

FIG. 19 is a schematic diagram of the structure of a communication device provided by an embodiment of the present disclosure. As shown in FIG. 19 , the device may include:

Wherein, the third node includes a first logic unit and a second logic unit;

The first node is a source host node of a first logical unit in the third node.

The first node is a source IAB-donor-CU of the IAB-MT in the IAB-node;

The second node is a target IAB-donor-CU of the IAB-MT in the IAB-node.

FIG. 20 is a schematic diagram of the structure of a communication device provided by an embodiment of the present disclosure. As shown in FIG. 20 , the device may include:

Wherein, the third node includes a first logic unit and a second logic unit;

The fourth node is a host node of the second logic unit in the third node.

Optionally, in an embodiment of the present disclosure, the release information includes:

The first node is a source IAB-donor-CU of the IAB-MT in the IAB-node;

The second node is a target IAB-donor-CU of the IAB-MT in the IAB-node.

Please refer to Figure 21, which is a schematic diagram of the structure of a communication device 2100 provided in an embodiment of the present application. The communication device 2100 can be a network device, or a terminal device, or a chip, a chip system, or a processor that supports the network device to implement the above method, or a chip, a chip system, or a processor that supports the terminal device to implement the above method. The device can be used to implement the method described in the above method embodiment, and the details can be referred to the description in the above method embodiment.

The communication device 2100 may include one or more processors 2101. The processor 2101 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process the communication protocol and communication data, and the central processing unit may be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute a computer program, and process the data of the computer program.

Optionally, the communication device 2100 may further include one or more memories 2102, on which a computer program 2104 may be stored, and the processor 2101 executes the computer program 2104 so that the communication device 2100 performs the method described in the above method embodiment. Optionally, data may also be stored in the memory 2102. The communication device 2100 and the memory 2102 may be provided separately or integrated together.

Optionally, the communication device 2100 may further include a transceiver 2105 and an antenna 2106. The transceiver 2105 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., for implementing a transceiver function. The transceiver 2105 may include a receiver and a transmitter, the receiver may be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function.

Optionally, the communication device 2100 may further include one or more interface circuits 2107. The interface circuit 2107 is used to receive code instructions and transmit them to the processor 2101. The processor 2101 runs the code instructions to enable the communication device 2100 to execute the method described in the above method embodiment.

In one implementation, the processor 2101 may include a transceiver for implementing the receiving and sending functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and sending functions may be separate or integrated. The above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

In one implementation, the processor 2101 may store a computer program 2103, which runs on the processor 2101 and enables the communication device 2100 to perform the method described in the above method embodiment. The computer program 2103 may be fixed in the processor 2101, in which case the processor 2101 may be implemented by hardware.

In one implementation, the communication device 2100 may include a circuit that can implement the functions of sending or receiving or communicating in the aforementioned method embodiments. The processor and transceiver described in the present application can be implemented in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal oxide semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

The communication device described in the above embodiments may be a network device or a terminal device, but the scope of the communication device described in the present application is not limited thereto, and the structure of the communication device may not be limited by FIG. 21. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

(1) Independent integrated circuit IC, or chip, or chip system or subsystem;

(2) having a set of one or more ICs, and optionally, the IC set may also include a storage component for storing data and computer programs;

(3) ASIC, such as modem;

(4) Modules that can be embedded in other devices;

(5) Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;

(6)Others

For the case where the communication device can be a chip or a chip system, please refer to the schematic diagram of the chip structure shown in Figure 22. The chip shown in Figure 22 includes a processor 2201 and an interface 2202. The number of processors 2201 can be one or more, and the number of interfaces 2202 can be multiple.

Optionally, the chip also includes a memory 2203, and the memory 2203 is used to store necessary computer programs and data.

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

The present application also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

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

A person skilled in the art may understand that the various numerical numbers such as first and second involved in the present application are only used for the convenience of description and are not used to limit the scope of the embodiments of the present application, but also indicate the order of precedence.

At least one in the present application can also be described as one or more, and a plurality can be two, three, four or more, which is not limited in the present application. In the embodiments of the present application, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", etc., and there is no order of precedence or size between the technical features described by the "first", "second", "third", "A", "B", "C" and "D".

The corresponding relationships shown in each table in the present application can be configured or predefined. The values of the information in each table are only examples and can be configured as other values, which are not limited by the present application. When configuring the corresponding relationship between the information and each parameter, it is not necessarily required to configure all the corresponding relationships illustrated in each table. For example, in the table in the present application, the corresponding relationships shown in some rows may not be configured. For another example, appropriate deformation adjustments can be made based on the above table, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables can also use other names that can be understood by the communication device, and the values or representations of the parameters can also be other values or representations that can be understood by the communication device. When implementing the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables.

The predefined in the present application may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

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

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

Claims

A resource release method, characterized in that the method is executed by a first node, and the method includes:

Receive release information;

According to the release information, releasing resources related to the third node;

Wherein, the third node includes a first logic unit and a second logic unit;

The first node is a source host node of a first logical unit in the third node.
The method according to claim 1, wherein the release information includes at least one of the following:

first release information, wherein the first release information is included in a message indicating that the switching of the first logical unit is completed;

The second release information is included in a message indicating that the migration of the second logical unit is completed.
The method according to claim 1 is characterized in that the first logical unit is a mobile terminal MT; and the second logical unit is a distributed unit DU.
The method according to claim 2, wherein the release information includes at least one of the following:

first indication information, used to instruct the first node to perform a release operation to release resources related to the third node;

The second indication information is used to indicate that the migration of the second logical unit of the third node is completed;

The identification information is used to indicate the identification of the third node.
The method according to any one of claims 1 to 4, wherein the receiving release information comprises at least one of the following:

receiving first release information sent by the second node and/or the third node;

Receive second release information sent by at least one of the second node, the third node, and the fourth node.
The method according to claim 5, wherein the second node is a target host node of the first logical unit of the third node;

The fourth node is a host node of the second logical unit of the third node.
The method according to any one of claims 1 to 4, characterized in that the releasing of resources related to the third node comprises at least one of the following:

In response to the third node being movable, releasing resources associated with the third node;

In response to the first node not being a host node of a second logical unit of a third node, releasing resources associated with the third node;

In response to the third node having performed at least one partial migration before performing the current partial migration, resources related to the third node are released.
The method according to any one of claims 1 to 4, characterized in that the method further comprises:

In response to the first node being a host node of a second logical unit of a third node, resources associated with the third node are not released.
The method according to any one of claims 1 to 7, wherein the releasing of resources related to the third node comprises at least one of the following:

releasing context information of the third node, wherein the context information of the third node includes context information of the first logical unit in the third node and/or context information of the second logical unit in the third node;

releasing the identifier of the third node;

The communication path of the third node in the first node network topology is released.
The method according to any one of claims 1 to 9, characterized in that:

The third node is an integrated access and backhaul node IAB-node, or a movable IAB-node;

The first node is a source integrated access and backhaul host node centralized unit IAB-donor-CU of an integrated access and backhaul node mobile terminal IAB-MT in the IAB-node;

The second node is the target IAB-donor-CU of the IAB-MT in the IAB-node;

The fourth node is the IAB-donor-CU of the integrated access and backhaul node distributed unit IAB-DU in the IAB-node.
A resource release method, characterized in that the method is executed by a second node, and the method includes:

Sending release information to the first node, where the release information is used for: the first node to release resources related to the third node according to the release information;

Wherein, the third node includes a first logic unit and a second logic unit;

The first node is a source host node of the first logical unit in the third node;

The second node is a target host node of the first logical unit in the third node.
The method according to claim 11, characterized in that the release information includes at least one of the following:

first release information, wherein the first release information is included in a message indicating that the switching of the first logical unit is completed;

The second release information is included in a message indicating that the migration of the second logical unit is completed.
The method according to claim 11, characterized in that the first logical unit is an MT; and the second logical unit is a DU.
The method according to any one of claims 11 to 13, characterized in that

The third node is an IAB-node, or a movable IAB-node;

The first node is a source IAB-donor-CU of the IAB-MT in the IAB-node;

The second node is a target IAB-donor-CU of the IAB-MT in the IAB-node.
A resource release method, characterized in that the method is executed by a third node, and the method includes:

Sending release information to the first node, where the release information is used for: the first node to release resources related to the third node according to the release information;

Wherein, the third node includes a first logic unit and a second logic unit;

The first node is a source host node of the first logical unit in the third node.
The method of claim 15, wherein the release information includes at least one of the following:

first release information, wherein the first release information is included in a message indicating that the switching of the first logical unit is completed;

The second release information is included in a message indicating that the migration of the second logical unit is completed.
The method according to claim 15, characterized in that the first logical unit is an MT; and the second logical unit is a DU.
The method according to any one of claims 15 to 17, characterized in that:

The third node is an IAB-node, or a movable IAB-node;

The first node is a source IAB-donor-CU of the IAB-MT in the IAB-node.
A resource release method, characterized in that the method is executed by a fourth node, and the method includes:

Sending release information to the first node, where the release information is used for: the first node to release resources related to the third node according to the release information;

Wherein, the third node includes a first logic unit and a second logic unit;

The first node is a source host node of the first logical unit in the third node;

The fourth node is a host node of the second logic unit in the third node.
The method according to claim 19, wherein the release information comprises:

The second release information is included in a message indicating that the migration of the second logical unit is completed.
The method according to claim 19, characterized in that the first logical unit is an MT; and the second logical unit is a DU.
The method according to any one of claims 19 or 21, characterized in that

The third node is an IAB-node, or a movable IAB-node;

The first node is a source IAB-donor-CU of the IAB-MT in the IAB-node;

The fourth node is the IAB-donor-CU of the IAB-DU in the IAB-node.
A communication device, characterized in that it is configured in a first node, comprising:

A transceiver module, used for receiving release information;

A processing module, configured to release resources related to the third node according to the release information;

Wherein, the third node includes a first logic unit and a second logic unit;

The first node is a source host node of a first logical unit in the third node.
A communication device, characterized in that it is configured in a second node, comprising:

A transceiver module, configured to send release information to the first node, wherein the release information is used for: the first node to release resources related to the third node according to the release information;

Wherein, the third node includes a first logic unit and a second logic unit;

The first node is a source host node of the first logical unit in the third node;

The second node is a target host node of the first logical unit in the third node.
A communication device, characterized in that it is configured in a third node, comprising:

A transceiver module, configured to send release information to the first node, wherein the release information is used for: the first node to release resources related to the third node according to the release information;

Wherein, the third node includes a first logic unit and a second logic unit;

The first node is a source host node of the first logical unit in the third node.
A communication device, characterized in that it is configured in a fourth node, comprising:

A transceiver module, configured to send release information to the first node, wherein the release information is used for: the first node to release resources related to the third node according to the release information;

Wherein, the third node includes a first logic unit and a second logic unit;

The first node is a source host node of the first logical unit in the third node;

The fourth node is a host node of the second logic unit in the third node.
A communication device, characterized in that the device comprises a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory so that the device performs the method as described in any one of claims 1 to 10, or the processor executes the computer program stored in the memory so that the device performs the method as described in any one of claims 11 or 14, or the processor executes the computer program stored in the memory so that the device performs the method as described in claim 15 or 18, or the processor executes the computer program stored in the memory so that the device performs the method as described in claims 19 to 22.
A communication device, comprising: a processor and an interface circuit, wherein

The interface circuit is used to receive code instructions and transmit them to the processor;

The processor is used to run the code instructions to execute the method as described in any one of claims 1 to 10, or to run the code instructions to execute the method as described in claim 11 or 14, or to run the code instructions to execute the method as described in claims 15 to 18, or to run the code instructions to execute the method as described in claims 19 to 22.
A computer-readable storage medium for storing instructions, which, when executed, implement the method according to any one of claims 1 to 10, or implement the method according to claim 11 or 14, or implement the method according to claim 15 to 18, or implement the method according to claim 19 to 22.