A communication method and related equipment for accessing and returning integrated IAB system

Abstract

The embodiment of the application provides a communication method and related device in an integrated access backhaul (IAB) system, which is used to flexibly configure the communication resource of a first IAB node according to the configuration information of a BH RLC CH from an IAB donor after the parent node of the first IAB node is changed from a source parent node to a target parent node. In the method, the IAB donor obtains the configuration information of a BH RLC CH of a backhaul link, the configuration information of the BH RLC CH being the configuration information of a BH RLC CH between a first integrated access backhaul (IAB) node and a source parent node of the first IAB node; then, the IAB donor sends the configuration information of the BH RLC CH to the target parent node of the first IAB node.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of communication, and in particular, to a communication method for an integrated access and backhaul (IAB) system and related equipment. BACKGROUND

[0002] In the network architecture of the 3rd-generation partnership project (3GPP) R15 integrated access and backhaul (IAB), there are IAB donor nodes (IAB donor) and IAB nodes (IAB node). In the case of considering the central unit (CU)-distributed unit (DU) architecture, the IAB donor includes an IAB donor CU and an IAB donor DU. The IAB node includes an IAB node mobile terminal (MT) functional unit and an IAB node DU. Among them, the IAB node MT functional unit acts as a user equipment (UE) module and is responsible for communication with its parent node. The IAB node DU acts as a DU and provides access services for the UE or other IAB nodes attached below it. Among them, the connection between the IAB node and the IAB donor CU is an F1 connection.

[0003] At present, due to the change of link quality between two communication nodes in the actual communication process, for example: radio link failure (RLF), or integrity protection failure, radio resource control (RRC) reconfiguration failure, etc., which may cause the parent node connected by the IAB node to change, and then trigger the IAB node to perform handover, that is, the IAB node releases the connection with the source parent node and establishes a new connection with the target parent node. Among them, the source parent node and the target parent node can be an intermediate IAB node on the path between the IAB node and the IAB donor, or an IAB donor DU in the IAB donor.

[0004] However, in the IAB network, due to the change of the parent node connected by the IAB node, the link resources between the IAB node and the target parent node need to be reconfigured, and how to flexibly configure the communication resources of the IAB node is a problem to be solved. SUMMARY

[0005] The embodiment of the application provides a communication method and related device for an integrated access and backhaul (IAB) system, which is used to flexibly configure the communication resource of a first IAB node according to the configuration information of a BH RLC CH from an IAB donor after the parent node of the first IAB node is changed from a source parent node to a target parent node.

[0006] The first aspect of the embodiment of the application provides a communication method for an integrated access and backhaul (IAB) system, which can be applied to an IAB donor and can also be applied to the components (such as a processor, a chip or a chip system, etc.) of the IAB donor. In the method, the IAB donor obtains the configuration information of a BH RLC CH of a backhaul link, and the configuration information of the BH RLC CH is the configuration information of a BH RLC CH between a first IAB node and a source parent node of the first IAB node; then, the IAB donor sends the configuration information of the BH RLC CH to a target parent node of the first IAB node.

[0007] Based on the above technical solution, the IAB donor obtains the configuration information of the BH RLC CH between the first IAB node and the source parent node of the first IAB node, and sends the configuration information of the BH RLC CH to the target parent node of the first IAB node. After the parent node of the first IAB node is changed from the source parent node to the target parent node, the target parent node of the first IAB node can use the configuration information of the BH RLC CH to further determine the configuration of the BH RLC CH between the first IAB node and the target parent node of the first IAB node. That is, when the target parent node of the first IAB node determines that the configuration information of the BH RLC CH from the IAB donor can be used for communication between the first IAB node, it is not necessary to send the configuration information of the BH RLC CH to the first IAB node, so that the first IAB node can communicate in the IAB network through the target parent node of the first IAB node, and the resource configuration overhead is saved; when the target parent node of the first IAB node determines that the configuration information of the BH RLC CH from the IAB donor is not used for communication between the first IAB node, the configuration information of the BH RLC CH corresponding to the first IAB node can be generated according to the air interface resource of the parent node, and the first IAB node can also communicate in the IAB network through the target parent node of the first IAB node. Therefore, the parent node can flexibly configure the communication resource of the first IAB node according to the configuration information of the BH RLC CH from the IAB donor.

[0008] It should be noted that in the embodiments of the present application, the target parent node of the first IAB node can be an intermediate IAB node on the path between the first IAB node and the IAB donor, or an IAB donor DU in the IAB donor, which is not limited here.

[0009] In a specific implementation manner of the first aspect of the embodiments of the present application, the configuration information of the BH RLC CH includes at least one of the following: an identifier of the BH RLC CH, a logical channel identifier corresponding to the BH RLC CH, configuration information of a radio link control channel (RLC), or configuration information of a logical channel.

[0010] Based on the above technical solution, the configuration information of the BH RLC CH can be implemented by at least one of the above multiple items, that is, multiple implementation manners of the IAB donor obtaining and sending the configuration information of the BH RLC CH are provided, and the realizability of the scheme is improved.

[0011] In a specific implementation manner of the first aspect of the embodiments of the present application, the IAB donor is a target IAB donor, the target parent node is connected with the target IAB donor, and the source parent node is connected with a source IAB donor.

[0012] Based on the above technical solution, the IAB donor connected by the first IAB node can also be changed, wherein the IAB donor connected by the source parent node of the first IAB node is a source IAB donor, and the IAB donor connected by the target parent node of the first IAB node is a target IAB donor, so that the scheme can be applied to the scenario that the IAB donor connected by the first IAB node changes, for example, an inter-donor-CU (Inter-donor-CU) re-establishment scenario.

[0013] In a specific implementation manner of the first aspect of the embodiments of the present application, the IAB donor obtaining the configuration information of the BH RLC CH includes: the IAB donor receiving an obtaining user equipment (UE) context response message from the source IAB donor, the obtaining UE context response message including the configuration information of the BH RLC CH.

[0014] Based on the above technical solution, when the IAB donor is a host node connected by a target parent node of the first IAB node (i.e., a target IAB donor), the IAB donor can obtain the configuration information of the BH RLC CH in the acquisition user equipment (UE) context response message sent by the host node connected by the source parent node of the first IAB node. A specific implementation of the IAB donor obtaining the configuration information of the BH RLC CH is provided, and the realizability of the scheme is improved.

[0015] In a specific implementation of the first aspect of the embodiments of the present application, the IAB donor sends first indication information to the first IAB node through the target parent node, and the first indication information is used to indicate that the IAB donor connected by the first IAB node changes.

[0016] Based on the above technical solution, when the IAB donor is a host node connected by a target parent node of the first IAB node (i.e., a target IAB donor), the IAB donor can obtain the configuration information of the BH RLC CH in the acquisition user equipment (UE) context response message sent by the host node connected by the source parent node of the first IAB node. A specific implementation of the IAB donor obtaining the configuration information of the BH RLC CH is provided, and the realizability of the scheme is improved.

[0017] In a specific implementation of the first aspect of the embodiments of the present application, the first indication information is carried in an RRC re-establishment message; or, the first indication information is carried in an RRC reconfiguration message.

[0018] Based on the above technical solution, the first indication information can be carried in an RRC re-establishment message or an RRC reconfiguration message, and multiple carrying modes of the first indication information are provided, and the realizability of the scheme is improved.

[0019] In a specific implementation of the first aspect of the embodiments of the present application, the IAB donor sends the Internet Protocol (IP) address information of the IAB donor to the first IAB node through the target parent node.

[0020] Based on the above technical solutions, when the IAB donor is a host node connected by the target parent node of the first IAB node (i.e., a target IAB donor), the IAB donor can also send IP address information of the target IAB donor to the first IAB node through the target parent node of the first IAB node, so that the first IAB node can trigger the establishment / re-establishment process of the F1 interface to the host node indicated by the IP address information, ensuring that the first IAB node can connect to the target IAB donor through the target parent node for communication.

[0021] In a specific implementation of the first aspect of the embodiments of the present application, the IP address information of the target IAB donor is carried in an RRC reconfiguration message.

[0022] Based on the above technical solutions, the carrying mode of the IP address information of the target IAB donor can be an RRC reconfiguration message, providing a specific implementation of the IP address information of the target IAB donor and improving the realizability of the scheme.

[0023] In a specific implementation of the first aspect of the embodiments of the present application, the method can further include: the IAB donor sending first configuration information to the first IAB node through the target parent node, the first configuration information including at least one of the following: a source identifier of a cell of the first IAB node, a target identifier of a cell of the first IAB node, a PLMN ID of a cell of the first IAB node, SSB information of a cell of the first IAB node, or activation indication information of a cell of the first IAB node.

[0024] Based on the above technical solutions, when the IAB donor is a host node connected by the target parent node of the first IAB node (i.e., a target IAB donor), the IAB donor can also send first configuration information to the first IAB node through the target parent node of the first IAB node, so that the first IAB node updates the network configuration of the first IAB node according to the first configuration information, ensuring that the first IAB node can connect to the target IAB donor through the target parent node for communication.

[0025] The second aspect of the embodiments of the present application provides a communication method for an integrated access and backhaul, IAB, system. The method can be applied to a target parent node of a first IAB node, or to a component (such as a processor, a chip, or a chip system) of the target parent node of the first IAB node. In the method, the target parent node of the first IAB node receives configuration information of a backhaul link radio link control channel, BH RLC CH, from an IAB donor. The configuration information of the BH RLC CH is the configuration information of a BH RLC CH between the first IAB node and a source parent node of the first IAB node. The target parent node determines the configuration of the BH RLC CH between the first IAB node and the target parent node according to the configuration information of the BH RLC CH.

[0026] Based on the above technical solution, the target parent node of the first IAB node receives the configuration information of the BH RLC CH between the first IAB node and the source parent node of the first IAB node from the IAB donor, and determines the configuration of the BH RLC CH between the first IAB node and the target parent node according to the configuration information of the BH RLC CH. After the parent node of the first IAB node is changed from the source parent node to the target parent node, the target parent node of the first IAB node can further determine the configuration of the BH RLC CH between the first IAB node and the target parent node using the configuration information of the BH RLC CH. That is, when the target parent node of the first IAB node determines that the configuration information of the BH RLC CH from the IAB donor can be used for communication between the first IAB node and the target parent node, the first IAB node can communicate in the IAB network through the target parent node of the first IAB node without sending the configuration information of the BH RLC CH to the first IAB node, thereby saving the resource configuration overhead. When the target parent node of the first IAB node determines that the configuration information of the BH RLC CH from the IAB donor cannot be used for communication between the first IAB node and the target parent node, the target parent node can generate the configuration information of the BH RLC CH corresponding to the first IAB node according to the air interface resources of the target parent node, and the first IAB node can also communicate in the IAB network through the target parent node of the first IAB node. Thus, the target parent node can flexibly configure the communication resources of the first IAB node according to the configuration information of the BH RLC CH from the IAB donor.

[0027] It should be noted that in the embodiments of the present application, the target parent node of the first IAB node can be an intermediate IAB node on the path between the first IAB node and the IAB donor, or an IAB donor DU in the IAB donor, which is not limited here.

[0028] In a specific implementation form of the second aspect of the embodiments of the present application, the configuration information of the BH RLC CH can include at least one of the following: an identifier of the BH RLC CH, an identifier of a logical channel corresponding to the BH RLC CH, configuration information of a radio link control channel (RLC), or configuration information of a logical channel.

[0029] Based on the above technical solution, the configuration information of the BH RLC CH can be implemented by at least one of the above multiple items, that is, multiple implementation forms of the IAB donor obtaining and sending the configuration information of the BH RLC CH are provided, and the realizability of the scheme is improved.

[0030] The third aspect of the embodiments of the present application provides a communication method in an integrated access backhaul (IAB) system. The method can be applied to a first IAB node, and can also be applied to a component (such as a processor, a chip, or a chip system) of the first IAB node. In the method, the first IAB node determines that RRC reestablishment with an IAB donor is completed; the first IAB node sends first information to a child node of the first IAB node; and the first information includes at least one of the following: indication information of a change of the IAB donor to which the first IAB node is connected, indication information of RRC reestablishment, identifier information of a base station of RRC reestablishment, and identifier information of a cell of RRC reestablishment.

[0031] Based on the above technical solution, after the first IAB node determines that RRC reestablishment with a target IAB donor is completed, that is, after the host node of the first IAB node is changed to the target IAB donor, the first IAB node sends first information to a child node of the first IAB node, so that the child node of the first IAB node triggers RRC reestablishment and / or establishment / reestablishment of an F1 connection with the target IAB donor according to the first information, and ensures that the child node of the first IAB node can work normally.

[0032] It should be noted that in the embodiments of the present application, the first IAB node is a parent node of the child node of the first IAB node, and the child node of the first IAB node can be an IAB node or a terminal device (such as a UE), which is not limited here.

[0033] In a specific implementation form of the third aspect of the embodiments of the present application, the first information is carried in a medium access control layer control element (MAC CE); or the first information is carried in a backhaul adaptation protocol control packet data unit (BAP control PDU).

[0034] Based on the technical solution, the carrying manner of the first information can be a media access control layer control element (MAC CE) or a BAP control PDU, which provides multiple carrying manners of the first information and improves the realizability of the scheme.

[0035] In a specific implementation manner of the third aspect of the embodiment, before the first IAB node sends the first information to the child node, the method further includes:

[0036] The first IAB node receives first indication information from the target IAB donor, where the first indication information is used to indicate that the IAB donor connected to the first IAB node changes.

[0037] Based on the technical solution, before the first IAB node sends the first information to the child node of the first IAB node, the first IAB node can further receive first indication information sent by the target IAB donor, where the first indication information is used to indicate that the IAB donor connected to the first IAB node changes, so that the first IAB node determines that the host node connected to the first IAB node and the child node changes. Subsequently, the child node of the first IAB node can be further notified, so that the child node of the first IAB node triggers RRC reestablishment and / or establishment / reestablishment of the F1 connection, to ensure that the child node of the first IAB node can be connected to the target IAB donor for communication through the first IAB node.

[0038] Optionally, the first IAB node can send the first information to the child node according to the first indication information.

[0039] In a specific implementation manner of the third aspect of the embodiment, the first indication information is carried in an RRC reestablishment message; or the first indication information is carried in an RRC reconfiguration message.

[0040] Based on the technical solution, the carrying manner of the first indication information can be an RRC reestablishment message or an RRC reconfiguration message, which provides multiple carrying manners of the first indication information and improves the realizability of the scheme.

[0041] In a specific implementation manner of the third aspect of the embodiment, before the first IAB node sends the first information to the child node of the first IAB node, the method can further include that the first IAB node determines that F1 connection establishment / reestablishment between the first IAB node and the IAB donor is completed or the F1 connection has been recovered.

[0042] Based on the above technical solution, the first IAB node sends the first information to the child node of the first IAB node after determining that the F1 connection establishment / re-establishment with the IAB donor is completed or the F1 connection has been recovered, so that the child node can trigger RRC re-establishment and / or F1 connection establishment / re-establishment according to the first information through the established / re-established F1 connection or the recovered F1 connection between the first IAB node and the IAB donor.

[0043] In a specific implementation manner of the third aspect of the embodiments of the present application, the method can further include: the first IAB node receiving the IP address information of the target IAB donor sent by the target IAB donor.

[0044] Based on the above technical solution, the first IAB node can also receive the IP address information of the target IAB donor sent by the target IAB donor through the target parent node of the first IAB node, so that the first IAB node can trigger the establishment / re-establishment process of the F1 interface to the host node indicated by the IP address information, ensuring that the first IAB node can work normally after being connected to the target IAB donor through the target parent node.

[0045] In a specific implementation manner of the third aspect of the embodiments of the present application, the IP address information of the target IAB donor is carried in the RRC reconfiguration message.

[0046] Based on the above technical solution, the carrying manner of the IP address information of the target IAB donor can be the RRC reconfiguration message, which provides a specific implementation manner of the IP address information of the target IAB donor and improves the realizability of the scheme.

[0047] In a specific implementation manner of the third aspect of the embodiments of the present application, after the first IAB node determines that the RRC re-establishment with the IAB donor is completed, the method can further include: the first IAB node receiving first configuration information from the IAB donor, the first configuration information including at least one of the following: a source identifier of a cell of the first IAB node, a target identifier of a cell of the first IAB node, a PLMN ID of a cell of the first IAB node, SSB information of a cell of the first IAB node, or activation indication information of a cell of the first IAB node.

[0048] Based on the above technical solution, the first IAB node can also receive the first configuration information sent by the target IAB donor through the target parent node of the first IAB node, so that the first IAB node updates the configuration of the first IAB node according to the first configuration information, ensuring that the first IAB node can connect to the target IAB donor through the target parent node for communication.

[0049] The fourth aspect of the embodiments of the present application provides a communication method for an integrated access backhaul IAB system. The method can be applied to a child node of a first IAB node, or can be applied to a component (such as a processor, a chip, or a chip system) of the child node of the first IAB node. In the method, the child node of the first IAB node receives first information from the first IAB node, and the first information includes at least one of the following: indication information of a change of an IAB donor to which the first IAB node is connected, indication information of RRC reestablishment, identification information of a base station for RRC reestablishment, and identification information of a cell for RRC reestablishment. The child node triggers at least one of the following processes according to the first information: RRC reestablishment, F1 connection establishment, or F1 connection reestablishment.

[0050] Based on the above technical solution, after the first IAB node determines that the RRC reestablishment between the first IAB node and the target IAB donor is completed, that is, after the host node of the first IAB node is changed to the target IAB donor, the child node of the first IAB node receives first information sent by the parent node, that is, the first IAB node, so that the child node of the first IAB node triggers RRC reestablishment and / or F1 connection establishment / reestablishment between the first IAB node and the target IAB donor according to the first information, ensuring that the child node of the first IAB node can connect to the target IAB donor through the first IAB node for communication.

[0051] It should be noted that in the embodiments of the present application, the first IAB node is the parent node of the child node of the first IAB node, and the child node of the first IAB node can be an IAB node or a terminal device (such as a UE), which is not limited here.

[0052] In a specific implementation manner of the fourth aspect of the embodiments of the present application, the first information is carried in a medium access control layer control unit MAC CE; or, the first information is carried in a backhaul adaptation protocol control packet data unit BAP control PDU.

[0053] Based on the above technical solution, the first information can be carried in a medium access control layer control unit MAC CE or a BAP control PDU, providing multiple carrying modes of the first information and improving the realizability of the scheme.

[0054] The fifth aspect of the embodiments of the present application provides a communication device, the device being an integrated access and backhaul donor (IAB donor), the device comprising:

[0055] a processing unit, configured to obtain configuration information of a backhaul radio link control channel (BH RLC CH) of a backhaul link, the configuration information of the BH RLC CH being configuration information of a BH RLC CH between a first integrated access and backhaul (IAB) node and a source parent node of the first IAB node;

[0056] a transceiver, configured to send the configuration information of the BH RLC CH to a target parent node of the first IAB node.

[0057] In a specific implementation form of the fifth aspect of the embodiments of the present application, the configuration information of the BH RLC CH comprises at least one of the following:

[0058] an identifier of the BH RLC CH, a logical channel identifier corresponding to the BH RLC CH, configuration information of a radio link control (RLC) channel, or configuration information of a logical channel.

[0059] In a specific implementation form of the fifth aspect of the embodiments of the present application, the IAB donor is a target IAB donor, the target parent node is connected with the target IAB donor, and the source parent node is connected with a source IAB donor.

[0060] In a specific implementation form of the fifth aspect of the embodiments of the present application,

[0061] the processing unit is specifically configured to receive an obtain user equipment (UE) context response message from the source IAB donor, the obtain UE context response message comprising the configuration information of the BH RLC CH.

[0062] In a specific implementation form of the fifth aspect of the embodiments of the present application, the transceiver is further configured to:

[0063] send first indication information to the first IAB node through the target parent node, the first indication information being used to indicate that an IAB donor connected by the first IAB node is changed.

[0064] In a specific implementation form of the fifth aspect of the embodiments of the present application,

[0065] the first indication information is carried in an RRC reestablishment message; or

[0066] the first indication information is carried in an RRC reconfiguration message.

[0067] In a specific implementation form of the fifth aspect of the embodiments of the present application, the transceiver unit is further configured to:

[0068] send, by the target parent node, the Internet Protocol, IP, address information of the target IAB donor to the first IAB node.

[0069] In a specific implementation form of the fifth aspect of the embodiments of the present application, the IP address information of the target IAB donor is carried in a RRC reconfiguration message.

[0070] In a specific implementation form of the fifth aspect of the embodiments of the present application, the transceiver unit is further configured to:

[0071] send, by the target parent node, first configuration information to the first IAB node, the first configuration information comprising at least one of:

[0072] a source identity of a cell of the first IAB node, a target identity of the cell of the first IAB node, a PLMN ID of the cell of the first IAB node, SSB information of the cell of the first IAB node, or activation indication information of the cell of the first IAB node.

[0073] In the fifth aspect of the embodiments of the present application, the component modules of the communication device can also be configured to perform the steps performed in the various possible implementation forms of the first aspect, and the details can be referred to the first aspect, which will not be described here again.

[0074] The sixth aspect of the embodiments of the present application provides a communication device, which is a target parent node of a first IAB node, and the device comprises:

[0075] a transceiver unit configured to receive configuration information of a Backhaul Radio Link Control, BH RLC, channel from an access backhaul integrated donor IAB donor, the configuration information of the BH RLC channel being configuration information of a BH RLC channel between a first IAB node and a source parent node of the first IAB node;

[0076] a processing unit configured to determine, according to the configuration information of the BH RLC channel, a configuration of the BH RLC channel between the first IAB node.

[0077] In a specific implementation form of the sixth aspect of the embodiments of the present application, the configuration information of the BH RLC channel comprises at least one of:

[0078] an identity of the BH RLC channel, a logical channel identity corresponding to the BH RLC channel, configuration information of a Radio Link Control, RLC, channel, or configuration information of a logical channel.

[0079] In a sixth aspect of the embodiments of the present application, the component modules of the communication device can also be used to perform the steps performed in the various possible implementation manners of the second aspect, and details can be referred to the second aspect, which will not be repeated here.

[0080] In a seventh aspect of the embodiments of the present application, a communication device is provided, which is a first integrated access and backhaul, IAB, node, and the device comprises:

[0081] a processing unit configured to determine that RRC reestablishment with a target IAB donor is completed;

[0082] a transceiver configured to send first information to a child node of the first IAB node;

[0083] The first information comprises at least one of:

[0084] indication information of a change of an IAB donor to which the first IAB node is connected, indication information of RRC reestablishment, identification information of a base station of RRC reestablishment, and identification information of a cell of RRC reestablishment.

[0085] In a specific implementation manner of the seventh aspect of the embodiments of the present application,

[0086] The first information is carried in a medium access control layer control element, MAC CE, or

[0087] The first information is carried in a backhaul adaptation protocol control packet data unit, BAP control PDU.

[0088] In a specific implementation manner of the seventh aspect of the embodiments of the present application, the transceiver is further configured to:

[0089] receive first indication information from the target IAB donor, the first indication information being used to indicate a change of an IAB donor to which the first IAB node is connected.

[0090] In a specific implementation manner of the seventh aspect of the embodiments of the present application,

[0091] The first indication information is carried in an RRC reestablishment message, or

[0092] The first indication information is carried in an RRC reconfiguration message.

[0093] In a specific implementation manner of the seventh aspect of the embodiments of the present application, the processing unit is further configured to determine that F1 connection establishment / reestablishment with the IAB donor is completed or the F1 connection has been recovered.

[0094] In a specific implementation form of the seventh aspect of the embodiments of the present application, the transceiver unit is further configured to:

[0095] receive the IP address information of the target IAB donor from the target IAB donor.

[0096] In a specific implementation form of the seventh aspect of the embodiments of the present application, the IP address information of the target IAB donor is carried in an RRC reconfiguration message.

[0097] In a specific implementation form of the seventh aspect of the embodiments of the present application, the transceiver unit is specifically configured to:

[0098] receive first configuration information from the target IAB donor, the first configuration information comprising at least one of:

[0099] a source identity of a cell of the first IAB node, a target identity of the cell of the first IAB node, a PLMN ID of the cell of the first IAB node, SSB information of the cell of the first IAB node, or activation indication information of the cell of the first IAB node.

[0100] In the seventh aspect of the embodiments of the present application, the component modules of the communication device can also be configured to perform the steps performed in each possible implementation form of the third aspect, and details can be referred to the third aspect, which will not be described here.

[0101] The eighth aspect of the embodiments of the present application provides a communication device, which is a child node of a first IAB node, and the device comprises:

[0102] a transceiver unit configured to receive first information from the first IAB node, the first information comprising at least one of:

[0103] indication information that an IAB donor connected to the first IAB node is changed, indication information of RRC reestablishment, identity information of a base station for RRC reestablishment, and identity information of a cell for RRC reestablishment.

[0104] a processing unit configured to trigger at least one of the following processes: RRC reestablishment, F1 connection establishment, or F1 connection reestablishment, according to the first information.

[0105] In a specific implementation form of the eighth aspect of the embodiments of the present application,

[0106] the first information is carried in a media access control layer control element (MAC CE); or

[0107] the first information is carried in a backhaul adaptation protocol control packet data unit (BAP control PDU).

[0108] In an eighth aspect, the constituent modules of the communication apparatus can also be configured to perform the steps performed in the various possible implementation manners of the fourth aspect, and details can be referred to the fourth aspect, which will not be repeated here.

[0109] In a ninth aspect, the communication apparatus includes a processor and a memory. The memory is configured to store computer programs or instructions. The processor is configured to execute the computer programs or instructions in the memory, so that the method of the first aspect or any one of the possible implementation manners of the first aspect is executed.

[0110] In a tenth aspect, the communication apparatus includes a processor and a memory. The memory is configured to store computer programs or instructions. The processor is configured to execute the computer programs or instructions in the memory, so that the method of the second aspect or any one of the possible implementation manners of the second aspect is executed.

[0111] In an eleventh aspect, the communication apparatus includes a processor and a memory. The memory is configured to store computer programs or instructions. The processor is configured to execute the computer programs or instructions in the memory, so that the method of the third aspect or any one of the possible implementation manners of the third aspect is executed.

[0112] In a twelfth aspect, the communication apparatus includes a processor and a memory. The memory is configured to store computer programs or instructions. The processor is configured to execute the computer programs or instructions in the memory, so that the method of the fourth aspect or any one of the possible implementation manners of the fourth aspect is executed.

[0113] In a thirteenth aspect, the application provides a computer readable storage medium storing one or more computer-executable instructions, which, when executed by a processor, cause the processor to perform the method of the first aspect or any one of the possible implementation manners of the first aspect, or the method of the second aspect or any one of the possible implementation manners of the second aspect, or the method of the third aspect or any one of the possible implementation manners of the third aspect, or the method of the fourth aspect or any one of the possible implementation manners of the fourth aspect.

[0114] The fourteenth aspect of the embodiments of the present application provides a computer program product (or computer program) for storing one or more computers, when the computer program product is executed by the processor, the processor executes the method of the first aspect or any possible implementation manner of the first aspect, or the processor executes the method of the second aspect or any possible implementation manner of the second aspect, or the processor executes the method of the third aspect or any possible implementation manner of the third aspect, or the processor executes the method of the fourth aspect or any possible implementation manner of the fourth aspect.

[0115] The fifteenth aspect of the embodiments of the present application provides a chip system, which includes a processor, and is used for supporting the communication device to implement the functions involved in the first aspect or any possible implementation manner of the first aspect, or supporting the communication device to implement the functions involved in the second aspect or any possible implementation manner of the second aspect, or supporting the communication device to implement the functions involved in the third aspect or any possible implementation manner of the third aspect, or supporting the communication device to implement the functions involved in the fourth aspect or any possible implementation manner of the fourth aspect. In a possible design, the chip system can further include a memory, and the memory is used for storing necessary program instructions and data of the access network device. The chip system can be composed of a chip, or can include the chip and other discrete devices.

[0116] The sixteenth aspect of the embodiments of the present application provides a communication system, which includes one or more communication devices shown in the fifth aspect to the eighth aspect, or the communication system includes one or more communication devices shown in the ninth aspect to the twelfth aspect.

[0117] The technical effects brought by the fifth, ninth, thirteenth, fourteenth, fifteenth, sixteenth aspects or any possible implementation manner thereof can refer to the technical effects brought by the first aspect or different possible implementation manners of the first aspect.

[0118] The technical effects brought by the sixth, tenth, thirteenth, fourteenth, fifteenth, sixteenth aspects or any possible implementation manner thereof can refer to the technical effects brought by the second aspect or different possible implementation manners of the second aspect.

[0119] The technical effects brought by the seventh, eleventh, thirteenth, fourteenth, fifteenth, sixteenth aspects or any possible implementation manner thereof can refer to the technical effects brought by the third aspect or different possible implementation manners of the third aspect.

[0120] The technical effects brought by the eighth, twelfth, thirteenth, fourteenth, fifteenth, sixteenth aspects or any possible implementation manner thereof can refer to the technical effects brought by the fourth aspect or different possible implementation manners of the fourth aspect.

[0121] From the above technical solutions, it can be seen that the embodiments of the present application have the following advantages: the IAB donor obtains the configuration information of the BH RLC CH between the first IAB node and the source parent node of the first IAB node, and sends the configuration information of the BH RLC CH to the target parent node of the first IAB node. Wherein, after the parent node of the first IAB node is changed from the source parent node to the target parent node, the target parent node of the first IAB node can use the configuration information of the BH RLC CH to further determine the configuration of the BH RLC CH between the target parent node and the first IAB node. That is, when the target parent node of the first IAB node determines that the configuration information of the BH RLC CH from the IAB donor can be used for communication between the target parent node and the first IAB node, the first IAB node can communicate in the IAB network through the target parent node of the first IAB node without sending the configuration information of the BH RLC CH to the first IAB node, thereby saving the resource configuration overhead; when the target parent node of the first IAB node determines that the configuration information of the BH RLC CH from the IAB donor is not used for communication between the target parent node and the first IAB node, the configuration information of the BH RLC CH corresponding to the first IAB node can be generated according to the air interface resource of the parent node, and the first IAB node can also communicate in the IAB network through the target parent node of the first IAB node. Therefore, the parent node can flexibly configure the communication resource of the first IAB node according to the configuration information of the BH RLC CH from the IAB donor. BRIEF DESCRIPTION OF DRAWINGS

[0122] Figure 1 An architecture diagram of a communication system suitable for the technical solutions of the present application;

[0123] Figure 2 A schematic diagram of a control plane protocol stack;

[0124] Figure 3 A schematic diagram of a user plane protocol stack;

[0125] Figure 4 A schematic diagram of two data backhaul scenarios in an IAB system;

[0126] Figure 5 Another schematic diagram of a control plane protocol stack;

[0127] Figure 6 Another schematic diagram of a user plane protocol stack;

[0128] Figure 7 An implementation schematic diagram of an F1 establishment scenario;

[0129] Figure 8 One example of an Intra-donor-CU handover scenario;

[0130] Figure 9 One example of an Intra-donor-CU re-establishment procedure;

[0131] Figure 10-1 One example of an Inter-donor-CU handover scenario in embodiments of the application;

[0132] Figure 10-2 Another example of an Inter-donor-CU handover scenario in embodiments of the application;

[0133] Figure 10-3 Another example of an Inter-donor-CU handover scenario in embodiments of the application;

[0134] Figure 10-4 One example of an Inter-donor-CU handover scenario in embodiments of the application;

[0135] Figure 11 One example of a communication method in an integrated access backhaul, IAB, system in embodiments of the application;

[0136] Figure 12 Another example of a communication method in an integrated access backhaul, IAB, system in embodiments of the application;

[0137] Figure 13 Another example of a communication method in an integrated access backhaul, IAB, system in embodiments of the application;

[0138] Figure 14 Another example of a communication method in an integrated access backhaul, IAB, system in embodiments of the application;

[0139] Figure 15 Another example of a communication method in an integrated access backhaul, IAB, system in embodiments of the application;

[0140] Figure 16 One example of a communication device in embodiments of the application;

[0141] Figure 17 Another example of a communication device in embodiments of the application;

[0142] Figure 18 One example of an Inter-donor in embodiments of the application. DETAILED DESCRIPTION

[0143] The technical solutions in the embodiments of the present application will be described clearly and completely in the following with reference to the drawings in the embodiments of the present application.

[0144] In the description of the present application, unless otherwise specified, " / " represents the meaning of or, for example, A / B can represent A or B. "And / or" in this paper is only a description of the association relationship of the associated object, which means that there can be three relationships, for example, A and / or B can represent: A exists alone, A and B exist together, and B exists alone. And in the description of the present application, unless otherwise specified, "multiple" means two or more than two. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, "first", "second" and the like are used to distinguish the same or similar items with basically the same function and role. The skilled in the art can understand that "first", "second" and the like do not limit the quantity and execution order, and "first", "second" and the like do not necessarily mean different.

[0145] First, some terms in the embodiments of the present application are explained and described in order to facilitate the understanding of the skilled in the art.

[0146] 1. Communication system: including but not limited to narrow band-internet of things (NB-IoT) system, wireless local access network (WLAN) system, LTE system, next generation 5G mobile communication system or communication system after 5G, such as NR, device to device (D2D) communication system, etc.

[0147] 2. Network device: or base station, including but not limited to evolved node B (eNB), radio network controller (RNC), node B (NB), base station controller (BSC), base transceiver station (BTS), home evolved NodeB or home node B (HNB), baseband unit (BBU), evolved LTE (eLTE) base station, NR base station (next generation node B, gNB), etc.

[0148] 3、Terminal device: includes but is not limited to any one of user equipment (UE), mobile station, access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile device, terminal, wireless communication device, user agent, station (ST) in a wireless local access network (WLAN), cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication function, computing device, other processing device connected to a wireless modem, vehicle-mounted device, wearable device, mobile station in a future 5G network, and terminal device in a future evolved public land mobile network (PLMN) network, etc.

[0149] 4、Wireless backhaul node (also referred to as IAB node): used to provide wireless backhaul service for nodes (e.g., terminals) wirelessly accessing the wireless backhaul node. The wireless backhaul service refers to the data and / or signaling backhaul service provided through the wireless backhaul link. The wireless backhaul node can be an IAB node or a relay, and the scheme of the present application is not limited thereto, which can be one of the above-mentioned base stations or terminal devices with forwarding function, or an independent device form. In a network containing a wireless backhaul node (taking an IAB network as an example for illustration), the wireless backhaul node can provide wireless access service for terminals and transmit user's service data through a wireless backhaul link connected to a donor gNB.

[0150] Exemplarily, the wireless backhaul node can also be a customer premises equipment (CPE), a residential gateway (RG), etc. In this case, the method provided by the embodiments of the present application can also be applied to the scene of home access.

[0151] Further, the concepts involved in the IAB system are briefly introduced as follows.

[0152] Link: refers to the path between two adjacent nodes in a path.

[0153] Access link: the link between a terminal device and a base station, or between a terminal device and an IAB node, or between a terminal device and a host node, or between a terminal device and a host DU. Alternatively, the access link includes the wireless link used by a certain IAB node when it communicates as a normal terminal device role with its parent node. The IAB node, when acting as a normal terminal device role, does not provide backhaul services for any child node. The access link includes the uplink access link and the downlink access link. In this application, the access link of a terminal device is a wireless link, so the access link can also be referred to as a wireless access link.

[0154] Backhaul link: the link between an IAB node and its parent node when the IAB node acts as a wireless backhaul node, or the link between an IAB node and its parent node. The IAB node, when acting as a wireless backhaul node, provides wireless backhaul services for child nodes. The backhaul link includes the uplink backhaul link and the downlink backhaul link. In this application, the backhaul link between an IAB node and its parent node is a wireless link, so the backhaul link can also be referred to as a wireless backhaul link.

[0155] Parent node and child node: each IAB node considers a neighboring node that provides it with wireless access services and / or wireless backhaul services as a parent node. Correspondingly, each IAB node can be considered as a child node of its parent node.

[0156] Alternatively, the child node can also be referred to as a lower node or a downstream node, and the parent node can also be referred to as an upper node or an upstream node.

[0157] Access IAB node: refers to an IAB node accessed by a terminal, or an IAB node that provides access services for a terminal device.

[0158] Intermediate IAB node: refers to an IAB node that provides wireless backhaul services for other IAB nodes (e.g., access IAB nodes or other intermediate IAB nodes), or an IAB node on the path between an access IAB node and an IAB host.

[0159] F1 interface, protocol layer of F1 interface: the F1 interface refers to the logical interface between the DU part of an IAB node and a host node (or donor-CU), the F1 interface can also be referred to as the F1* interface, and supports user plane and control plane. The protocol layer of the F1 interface refers to the communication protocol layer on the F1 interface.

[0160] For example, the user plane protocol layer of the F1 interface can include one or more of the IP layer, the UDP layer, and the GTP-U layer.

[0161] For example, the control plane protocol layer of the F1 interface can include one or more of the IP layer, the SCTP layer, and the F1AP layer.

[0162] The names of all nodes and messages in this application are only set for the convenience of description, and the names in the actual network may be different, and the names of various nodes and messages should not be understood as being limited by this application. On the contrary, any name with the same or similar function as the nodes or messages used in this application is considered as a method or equivalent replacement of this application, and is within the protection scope of this application, which will not be described below.

[0163] Please refer to Figure 1 , taking the network device gNB as an example. In the third generation partnership project (3rd generation partnership project, 3GPP) Rel-15 NR, the gNB can adopt a centralized unit (central Unit, CU)-distributed unit (distributed Unit, DU) separation architecture, that is, the gNB in the next generation wireless access network (next generation radio access network, NG RAN) is composed of 1 gNB-CU and 1 or more gNB-DU, wherein one gNB-DU can only be connected to one gNB-CU, and the gNB-CU and the gNB-DU are connected through the F1 interface, and the gNB-CU and the 5GC (5G core network) are connected through the next generation (next generation, NG) interface, as shown in Figure 1 .

[0164] Further, taking the terminal device UE as an example, the UE can access the gNB-CU through the gNB-DU as shown in Figure 1 , that is, the physical (physical, PHY) layer / medium access control (medium access control, MAC) layer / radio link control (radio link control, RLC) layer function equal to the UE is located on the gNB-DU, and the packet data convergence protocol (packet data convergence protocol, PDCP) layer / service data adaptation protocol (Service Data Adaptation Protocol, SDAP) layer / radio resource control (radio resource control, RRC) layer function equal to the UE is located on the gNB-CU. Specifically as shown in Figure 2 and Figure 3 .

[0165] Please refer to Figure 2For control plane data, in uplink (UL) direction, gNB-DU encapsulates the UE generated RRC message in F1AP message and sends to gNB-CU; in downlink (DL) direction, gNB-CU encapsulates the RRC message in F1 application protocol (F1AP) message and sends to gNB-DU, gNB-DU extracts the RRC message from F1AP message and sends to UE on the corresponding signaling radio bearer (SRB) (SRB0 / SRB1 / SRB2) of Uu interface.

[0166] Please refer to Figure 3 For user plane data, in UL direction, gNB-DU maps the UE data packet received from data radio bearer (DRB) of Uu interface into corresponding general packet radio service tunneling protocol (GTP) tunnel and sends to gNB-CU; in DL direction, gNB-CU maps the UE data packet into corresponding GTP tunnel and sends to gNB-DU, gNB-DU extracts the UE data packet from GTP tunnel and maps the UE data packet onto the corresponding DRB of Uu interface and sends to UE.

[0167] In addition, in 3GPP Rel-15 integrated access and backhaul (IAB), two types of nodes, IAB node (referred to as IAB node) and IAB donor (referred to as IAB donor node, or host IAB node), are also introduced. Among them, the IAB donor can be a gNB.

[0168] Among them, the host node (IAB donor) can be an access network element with complete base station function, and also can be a form of separation of centralized unit (CU) and distributed unit (DU), that is, the host node is composed of the centralized unit of the host base station and the distributed unit of the host base station. In the embodiment of the application, the centralized unit of the host node is also called IAB donor CU (also called donor CU, or directly called CU). The distributed unit of the host node is also called IAB donor DU (or called donor DU). Among them, the donor CU can also be in the form of separation of control plane (control plane, CP) (referred to as CU-CP in the embodiment of the application) and user plane (user plane, UP) (referred to as CU-UP in the embodiment of the application). For example, the CU can be composed of one CU-CP and one or more CU-UPs.

[0169] Please refer to Figure 4 Taking a two-hop data backhaul scenario (backhaul is abbreviated as BH) as an example, in Figure 4 , the IAB network adopts a CU-DU separation architecture, that is: the IAB donor is composed of two parts of IAB donor-CU (referred to as donor-CU) and IAB donor-DU (referred to as donor-DU), and the IAB node is composed of two parts of IAB node-MT (referred to as IAB-MT) and IAB node-DU (referred to as IAB-DU). Among them, the IAB node-MT can also be referred to as IAB node-UE (referred to as IAB-UE).

[0170] Among them, for the IAB donor, the donor-DU is similar to the function of the gNB-DU, and the donor-CU is similar to the function of the gNB-CU. For the IAB node, the IAB-DU is similar to the function of the gNB-DU, and is used to provide access services for its child nodes, wherein the child nodes of the IAB-DU can be UEs or other IAB nodes. The IAB-MT has the function of the UE, and is used to provide data backhaul for the child nodes of the co-site IAB-DU (that is, the IAB-DU and the IAB-MT belong to the same IAB node).

[0171] Further, the IAB node can be divided into access IAB node and intermediate IAB node, that is: the IAB node accessed by the UE is called access IAB node, and the IAB node on the path between the access IAB node and the IAB donor is called intermediate IAB node.

[0172] As Figure 4As shown, UE accesses IAB node2, then IAB node2 is called the access IAB node of UE (or the parent node of UE), UE is called the child node of IAB node2, and the link between UE and IAB node2 is called access link. IAB node1 is called intermediate IAB node, the parent node of IAB node1 is IAB donor (the child node of IAB donor is IAB node1), and the child node of IAB node1 is IAB node2 (the parent node of IAB node2 is IAB node1). The link between IAB node1 and IAB node2, and the link between IAB node1 and IAB donor are all called backhaul link. Among them, the PHY layer, MAC layer and RLC layer equivalent to UE are located on the access IAB node (i.e. IAB2-DU), and the PDCP layer, SDAP layer and RRC layer equivalent to UE are located on donor-CU. The IAB nodes all adopt L2 data forwarding architecture, and the specific control plane protocol stack and user plane protocol stack are as shown in Figure 5 and Figure 6 .

[0173] Please refer to Figure 5 , based on the control plane protocol stack of two-hop data backhaul as shown in Figure 4 , the F1 interface is established between the access IAB node (i.e. IAB node2-DU) and the IAB donor (i.e. IAB donor-CU). Specifically, if the IAB donor adopts CP-UP separation architecture, the F1-C interface is established between the IAB node2-DU and the donor CU-CP. The RRC message of UE is encapsulated in the F1AP message of F1-C interface and transmitted.

[0174] Please refer to Figure 6 , based on the user plane protocol stack of two-hop data backhaul as shown in Figure 4 , if the IAB donor adopts CP-UP separation architecture, the F1-U interface is established between the IAB node2-DU and the donor CU-UP, and the GTP tunnel of each UE bearer is established on the F1-U interface. That is to say, each UE DRB established on the interface between UE and IAB node2-DU corresponds to a separate GTP tunnel on the interface between IAB2-DU and donor CU-UP.

[0175] As shown in Figure 6 , in Figure 6In the protocol architecture shown, the meaning of each protocol layer is: packet data convergence protocol (PDCP) layer, general packet radio service tunneling protocol user plane (GTP-U) layer, user datagram protocol (UDP) layer, internet protocol (IP) layer, L2 layer, L1 layer, radio link control (RLC) layer, medium access control (MAC) layer, physical (PHY) layer, radio resource control (RRC) layer, F1 application protocol (F1AP) layer, stream control transmission protocol (SCTP) layer. Among them, the L2 layer is a link layer. For example, the L2 layer can be a data link layer in the open systems interconnection (OSI) reference model. The L1 layer can be a physical layer. For example, the L1 layer can be a physical layer in the OSI reference model.

[0176] In order to meet the quality of service requirements of different types of services of terminal devices, one or more radio bearers (RBs) are introduced in a wireless network, including data radio bearers (DRBs) and signaling radio bearers (SRBs), which are used to transmit different types of service data (including control plane signaling and user plane data) between UEs and base stations. In an IAB network, an RB can be considered as a logical channel for transmitting data between a UE and a donor node.

[0177] Each protocol layer is configured with a corresponding protocol layer entity, such as a PDCP entity, an RLC entity, and a MAC entity, etc. In uplink transmission, the data packet (such as an IP data packet) of the UE is sent to the PHY layer of the access backhaul node (such as the IAB node2 shown in FIG. 1) after being processed by the PDCP layer, the RLC layer, the MAC layer, and the PHY layer in turn. Figure 4

[0178] ​As described previously, in an IAB network, an IAB node can contain a DU part and an MT part. When the IAB node acts as a wireless backhaul node, the MT part of the IAB node does not need a complete protocol stack of the terminal device in the wireless access link to perform data forwarding in the backhaul link. Among them, when the IAB node acts as a role of a wireless terminal, the protocol stack of the communication link between the IAB node and the parent node is the same as the protocol stack of the wireless access link between the UE and the access IAB node, and the protocol stack between the IAB node and the host CU is the same as the protocol stack between the UE and the host CU.

[0179] Similar to 3GPP Rel-15 NR, in R16 IAB, one IAB-DU can also only connect to one IAB donor-CU to establish an F1 connection. Taking the scenario that the IAB node is directly connected to the IAB donor as an example, as shown in the following figure, the steps include the following steps. Figure 7

[0180] Step 1. After the IAB-MT accesses the network through the IAB donor (i.e., initial access), the IAB-DU can obtain the configuration information of the IAB-DU from the operations, administration and maintenance (OAM) server through the accessed IAB donor, including at least one of the following information: the identity of the IAB-DU (IAB-DU id, IAB-DU name), the cell information of the IAB-DU (the physical cell identifier (PCI) of the IAB-DU cell, the cell identity of the cell, the synchronization signal / physical broadcast channel block (SS / PBCH block or SSB) information of the cell), and the IP address of the opposite end of the F1 interface of the IAB-DU (the IP address of the IAB donor-CU).

[0181] In addition, the IAB-DU can also obtain the IP address of the local end of the F1 interface of the IAB-DU through the OAM, or the IAB-DU requests the accessed IAB donor to obtain the IP address of the local end of the F1 interface of the IAB-DU through the IAB-MT.

[0182] Step 2. The IAB-DU establishes a TNLA association with the IAB donor-CU using the obtained IP address.

[0183] ​Step 3. The IAB-DU triggers a F1 Setup Request message to the IAB donor-CU through the established TNLA association, reporting the configuration information it gets from the OAM to the IAB donor-CU, in order to establish the F1 connection with the IAB donor-CU.

[0184] Step 4. The IAB donor-CU sends a F1 Setup Response message to the IAB-DU, activating the specified IAB-DU cell, in order to start the IAB-DU function, e.g. the activated IAB-DU cell starts to do system broadcast.

[0185] Step 5. If the IP address of the IAB-DU is updated, a new TNLA association is established with the IAB donor-CU using the new IP address.

[0186] Step 6. The IAB-DU triggers a gNB-DU Configuration Update procedure to the IAB donor-CU through the newly established TNLA association, i.e. the IAB-DU sends a gNB-DU Configuration Update to the IAB donor-CU in step 6a, and the IAB donor-CU sends a gNB-DU Configuration Update Acknowledge to the IAB-DU in step 6b, in order to inform the IAB donor-CU to update the TNLA association. Optionally, the old TNLA association between the IAB-DU and the IAB donor-CU can also be deleted through this procedure.

[0187] In addition, currently in R16 IAB, only Intra-donor-CU re-establishment scenarios are considered, without considering Inter-donor-CU re-establishment scenarios.

[0188] Please refer to Figure 8 , in the Intra-donor-CU re-establishment scenario, if the IAB-MT detects RLF on the link with the IAB donor-DU1, the IAB-MT will perform cell selection and re-establish the RRC connection to the cell of the IAB donor-DU2 in order to recover the link, where the IAB donor-DU1 and the IAB donor-DU2 are connected to the same IAB donor-CU.

[0189] As Figure 8As shown, the IAB node includes both IAB-MT and IAB-DU parts, in the embodiments of the present application, the IAB node that detects radio link failure (RLF) or the IAB node that detects link RLF and attempts to recover can be collectively referred to as a recover IAB node. Among them, the IAB-MT part of the recover IAB node is referred to as recover IAB-MT, and the IAB-DU part of the recover IAB node is referred to as recover IAB-DU.

[0190] Similar to the UE, before the link RLF, the recover IAB-MT is connected to the source IAB donor, that is, connected to the IAB donor-CU through the IAB donor-DU1. After the link RLF, the recover IAB-MT performs link recovery by RRC reestablishment to the target IAB donor, that is, connected to the IAB donor-CU through the IAB donor-DU2.

[0191] Since the IAB donor-CU does not change before and after the recover IAB-MT triggers the RRC reestablishment procedure to recover the link, the F1 connection between the recover IAB-DU and the IAB donor-CU is maintained.

[0192] In addition, since the IP address of the recover IAB-DU is allocated by the IAB donor-DU or the IAB donor-CU, that is, the IP address of the recover IAB-DU needs to belong to the same network segment or have the same network prefix as the IP address of the IAB donor-DU, therefore, once the IAB donor-DU changes, the IP address of the recover IAB-DU changes.

[0193] Please refer to Figure 9 Take the multi-hop scenario (there is at least one other IAB node between the recover IAB node and the IAB donor-DU) as an example. In the multi-hop scenario, the recover IAB-MT is connected to the target IAB donor through the IAB donor-DU2 and the IAB donor-DU1. Figure 9In the IAB intra-CU re-establishment procedure shown, the initial path refers to the transmission path between the source parent node and the source IAB donor-DU, wherein the initial path includes the source parent node (Initial Parrent IAB-node), the intermediate hop IAB-node on the initial path, and the source IAB-donor-DU (Initial IAB-donor-DU); the recovery path refers to the transmission path between the target parent node and the target IAB donor-DU, wherein the recovery path includes the target parent node (New Parrent IAB-node), the intermediate hop IAB-node on the new path, and the target IAB-donor-DU (New IAB-donor-DU). The specific switching procedure is as follows Figure 9

[0194] Before step 1, the IAB-donor-CU can interact with the UE through the source path to transmit uplink user data and downlink user data.

[0195] Step 1. The recovery IAB-MT detects that the BH RLF occurs on the source path, i.e., the determination of the BH RLF on the initial path.

[0196] Step 2. The recovery IAB-MT triggers the RRC re-establishment to the new parent node to recover the link, i.e., the RRC re-establishment at the recovery parent IAB-node DU. In this procedure, the IAB-donor-CU can provide the new TNL address to the recovery IAB-MT through the RRC message, and further, the IAB-donor-CU can also provide the default UL configuration to the recovery IAB-MT through the RRC reconfiguration message, including: configuring the default BH RLC channel for UL F1-C / non-F1 traffic transmission on the target path, the default backhaul adaptation protocol routing ID (BAP routing ID), etc. ​

[0197] Step 3. The remaining part of the procedure follows steps 11-15 of the intra-CU topology adaptation procedure (Same as steps 11-15 of intra-CU topology adaptation procedure). The implementation of steps 11-15 can include the following steps.

[0198] Step 11: The IAB-donor-CU configures the corresponding BH RLC channel and BAP routing configuration for the target path to recover the IAB-MT, and configures the DL bearer mapping on the target IAB donor-DU to recover the IAB-MT.

[0199] Step 12: The F1-C connection is updated using the new IP address of the recovered IAB-DU. The IAB-donor-CU updates the UL BH information associated with each GTP tunnel for the recovered IAB-DU, i.e. all F1-U tunnels are updated to use the new IP address of the recovered IAB-DU.

[0200] Step 13: The IAB-donor-CU sends a UE Context Release Command message to the source parent node of the recovered IAB-MT.

[0201] Step 14: The source parent node of the recovered IAB-MT releases the context of the recovered IAB-MT and sends a UE Context Release Complete message to the IAB-donor-CU in response.

[0202] Step 15: The IAB-donor-CU releases the BH RLC channel and backhaul adaptation protocol (BAP) routing configuration information on the source path between the source parent node of the recovered IAB-MT and the source IAB donor-DU.

[0203] As Figure 8 and Figure 9 ​In the shown Intra-donor-CU RRC re-establishment scenario, the parent node to which the IAB node is connected changes, i.e., from the IAB donor-DU1 to the IAB donor-DU2. In addition, due to the change of the link quality between the two communication nodes in the actual communication process, for example, when the handover fails, the radio link failure (RLF), the integrity protection fails, the RRC reconfiguration fails, and the like, the parent node to which the IAB node is connected can change, i.e., the IAB node releases the connection between the source parent node and the first IAB node, and establishes a new connection with the target parent node. The source parent node and the target parent node can be an intermediate IAB node between the IAB node and the IAB donor, or an IAB donor DU in the IAB donor.

[0204] However, in the IAB network, when the parent node to which the IAB node is connected changes, how to flexibly configure the communication resources of the IAB node is a problem to be solved.

[0205] In addition, in the current IAB network, only the Intra-donor-CU RRC re-establishment scenario is considered, i.e., the IAB donor-CU does not change, therefore, the cell configuration information of the IAB-DU is not changed, and the F1 connection between the IAB-DU and the IAB donor-CU remains unchanged, and the cell configuration information of the child node (e.g., other IAB nodes) of the IAB node is also not changed, and the F1 connection between the child node of the IAB node and the IAB donor-CU also remains unchanged.

[0206] However, the Inter-donor-CU RRC re-establishment scenario is also a typical scenario, and the Inter-donor-CU RRC re-establishment scenario in the embodiments of the present application will be introduced by way of illustration.

[0207] Please refer to Figure 10-1 , which is an example of the Inter-donor-CU RRC re-establishment scenario. In this scenario, before triggering at least one of the following processes: RRC re-establishment, F1 connection establishment, or F1 connection re-establishment process, the IAB-MT is connected to the source IAB donor-CU (e.g., the IAB donor-CU1 of Figure 10-1 ) through the source IAB donor-DU (e.g., the IAB donor-DU1 of Figure 10-1 ); after triggering at least one of the following processes: RRC re-establishment, F1 connection establishment, or F1 connection re-establishment process, the IAB-MT is connected to the target IAB donor-CU (e.g., the IAB donor-CU2 of Figure 10-1IAB donor-CU (e.g. IAB donor-CU2) of the target IAB donor-DU (e.g. IAB donor-DU2). Figure 10-1 IAB donor-CU (e.g. IAB donor-CU2) of the target IAB donor-DU (e.g. IAB donor-DU2).

[0208] Please refer to Figure 10-2 , another example of the Inter-donor-CU RRC Re-establishment scenario. In this scenario, the RRC Re-establishment procedure is triggered for the IAB-MT of the IAB node (e.g. IAB node1) connected to the source IAB donor-DU (e.g. IAB donor-DU1) of the source IAB donor-CU (e.g. IAB donor-CU1). Figure 10-1 The scenario is further extended as shown in Figure 10-2 : Before the RRC Re-establishment, F1 Connection Setup or F1 Connection Re-establishment procedure is triggered, the IAB node1 and IAB node2 exist at least one other IAB node between the IAB node and the source IAB donor-DU (e.g. IAB donor-DU1) of the source IAB donor-CU (e.g. IAB donor-CU1). The IAB node3 and IAB node4 exist at least one other IAB node between the IAB node and the target IAB donor-DU (e.g. IAB donor-DU2) of the target IAB donor-CU (e.g. IAB donor-CU2). Figure 10-2 The scenario is further extended as shown in Figure 10-2 : Before the RRC Re-establishment, F1 Connection Setup or F1 Connection Re-establishment procedure is triggered, the IAB node1 and IAB node2 exist at least one other IAB node between the IAB node and the source IAB donor-DU (e.g. IAB donor-DU1) of the source IAB donor-CU (e.g. IAB donor-CU1). The IAB node3 and IAB node4 exist at least one other IAB node between the IAB node and the target IAB donor-DU (e.g. IAB donor-DU2) of the target IAB donor-CU (e.g. IAB donor-CU2).

[0209] Please refer to Figure 10-3 , another example of the Inter-donor-CU RRC Re-establishment scenario. In this scenario, the RRC Re-establishment procedure is triggered for the IAB-MT of the IAB node (e.g. IAB node1) connected to the source IAB donor-DU (e.g. IAB donor-DU1) of the source IAB donor-CU (e.g. IAB donor-CU1). Figure 10-1 The scenario is further extended as shown in Figure 10-2 : Case 1: Before the RRC Re-establishment, F1 Connection Setup or F1 Connection Re-establishment procedure is triggered, the IAB-MT is directly connected to the source IAB donor-DU. After the RRC Re-establishment, F1 Connection Setup or F1 Connection Re-establishment procedure is triggered, the IAB-MT is connected to the target IAB donor-DU through at least one other IAB node.

[0210] Please refer to Figure 10-4 , another example of the Inter-donor-CU RRC Re-establishment scenario. In this scenario, the RRC Re-establishment procedure is triggered for the IAB-MT of the IAB node (e.g. IAB node1) connected to the source IAB donor-DU (e.g. IAB donor-DU1) of the source IAB donor-CU (e.g. IAB donor-CU1). Figure 10-1 The scenario is further extended as shown in Figure 10-2The illustrated scenario is further extended. Specifically, Case 2: before triggering at least one of the following procedures: RRC re-establishment, F1 connection setup or F1 connection re-establishment procedure, the IAB-MT is recovered to connect to the source IAB donor-DU through at least one other IAB node; after triggering at least one of the following procedures: RRC re-establishment, F1 connection setup or F1 connection re-establishment procedure, the IAB-MT is recovered to connect to the target IAB donor-DU directly.

[0211] In the above example, the child node of the recovered IAB node can be a UE or another IAB node. In addition, in the above RRC re-establishment scenario, the path between the recovered IAB-MT and the source IAB-donor CU (e.g., IAB donor-CU1 in the figure) is referred to as the source path, and the path between the recovered IAB-MT and the target IAB donor-CU (e.g., IAB donor-CU2 in the figure) is referred to as the target path or the recovery path.

[0212] Obviously, in the Inter-donor-CU scenario, the IAB donor-CU will change, resulting in a change in the F1 connection of the recovered IAB-DU (currently only one DU is connected to one CU to establish one F1 connection), i.e., before triggering at least one of the following procedures: RRC re-establishment, F1 connection setup or F1 connection re-establishment procedure, the recovered IAB-DU establishes an F1 connection with the source IAB donor-CU; after triggering at least one of the following procedures: RRC re-establishment, F1 connection setup or F1 connection re-establishment procedure, the recovered IAB-DU needs to establish / re-establish an F1 connection with the target IAB donor-CU and release the F1 connection with the source IAB donor-CU. Similarly, the descendant nodes (e.g., other IAB nodes) of the recovered IAB node also need to establish / re-establish an F1 connection with the target IAB donor-CU, and the current IAB node does not support the procedure of changing the F1 connection.

[0213] In summary, at least the following problems exist in the current IAB network:

[0214] Problem 1: When the parent node connected to the IAB node changes, i.e., the IAB node releases the connection with the source parent node and establishes a new connection with the target parent node, since the parent node connected to the IAB node changes, the link resources between the IAB node and the target parent node need to be reconfigured, and how to flexibly configure the communication resources of the IAB node is a problem that needs to be solved urgently.

[0215] Problem 2, after the IAB node detects that the link with the source parent node occurs RLF, the RRC reestablishment process will be triggered, but due to the good link quality between the IAB node and its child node, it will cause the child node to fail to trigger the RRC reestablishment process and cannot work normally. The current IAB node does not support the process of replacing the F1 connection, therefore, how to support replacing the F1 connection in the Inter-donor-CU scenario and how to notify the child node to trigger the RRC reestablishment process are also technical problems to be solved urgently.

[0216] To solve the above problems, the embodiment of the application provides a communication method for an integrated access backhaul (IAB) system, please refer to Figure 11 The communication method for an integrated access backhaul (IAB) system includes the following steps.

[0217] S101, the IAB donor obtains the configuration information of the BH RLC CH.

[0218] In the embodiment, the IAB donor obtains the configuration information of the BH RLC CH in step S101. The configuration information of the BH RLC CH is the configuration information of the BH RLC CH between the first integrated access backhaul (IAB) node and the source parent node of the first IAB node.

[0219] Specifically, the configuration information of the BH RLC CH obtained by the IAB donor in step S101 can include at least one of the following: the identification of the BH RLC CH, the logical channel identification corresponding to the BH RLC CH, the configuration information of the radio link control (RLC) channel or the configuration information of the logical channel.

[0220] In step S101, the configuration information of the BH RLC CH is the configuration information of the BH RLC CH between the first IAB node and the source parent node of the first IAB node, wherein the parent node of the first IAB node may change due to various different scenarios.

[0221] In one possible implementation, as Figure 8 and Figure 9In the RRC re-establishment scenario of Intra-donor-CU as shown in FIG. 1, the parent node to which the IAB node (i.e., the first IAB node) is connected changes, i.e., changes from the IAB donor-DU1 to the IAB donor-DU2. In addition, due to the change in the link quality between the two communication nodes in the actual communication process, for example, when the handover fails, the radio link failure (RLF) occurs, the integrity protection fails, the RRC reconfiguration fails, and the like, the parent node to which the IAB node is connected can change, i.e., the IAB node releases the connection with the source parent node of the IAB node and establishes a new connection with the target parent node.

[0222] Specifically, in this implementation manner, since the IAB donor of the first IAB node does not change, the IAB donor can determine the configuration information of the BH RLC CH between the first IAB node and the source parent node of the first IAB node through the cache data of the device itself or the historical data in step S101.

[0223] In another possible implementation manner, in the RRC re-establishment scenario of Inter-donor-CU as shown in FIG. 2, the IAB-MT (i.e., the MT part of the first IAB node) is connected to the source IAB donor-CU (such as the IAB donor-CU1 in FIG. 2) through the source IAB donor-DU (such as the IAB donor-DU1 in FIG. 2); after triggering at least one of the following processes: the RRC re-establishment process, the F1 connection establishment process, or the F1 connection re-establishment process, the IAB-MT is connected to the target IAB donor-CU (such as the IAB donor-CU2 in FIG. 2) through the target IAB donor-DU (such as the IAB donor-DU2 in FIG. 2). Figure 10-1 Figure 10-2 Figure 10-3 Figure 10-4 In the RRC re-establishment scenario of Inter-donor-CU as shown in FIG. 2, the IAB-MT (i.e., the MT part of the first IAB node) is connected to the source IAB donor-CU (such as the IAB donor-CU1 in FIG. 2) through the source IAB donor-DU (such as the IAB donor-DU1 in FIG. 2); after triggering at least one of the following processes: the RRC re-establishment process, the F1 connection establishment process, or the F1 connection re-establishment process, the IAB-MT is connected to the target IAB donor-CU (such as the IAB donor-CU2 in FIG. 2) through the target IAB donor-DU (such as the IAB donor-DU2 in FIG. 2). Figure 10-1 Figure 10-2 Figure 10-3 Figure 10-4 In the RRC re-establishment scenario of Inter-donor-CU as shown in FIG. 2, the IAB-MT (i.e., the MT part of the first IAB node) is connected to the source IAB donor-CU (such as the IAB donor-CU1 in FIG. 2) through the source IAB donor-DU (such as the IAB donor-DU1 in FIG. 2); after triggering at least one of the following processes: the RRC re-establishment process, the F1 connection establishment process, or the F1 connection re-establishment process, the IAB-MT is connected to the target IAB donor-CU (such as the IAB donor-CU2 in FIG. 2) through the target IAB donor-DU (such as the IAB donor-DU2 in FIG. 2). Figure 10-1 Figure 10-2 Figure 10-3 Figure 10-4 In the RRC re-establishment scenario of Inter-donor-CU as shown in FIG. 2, the IAB-MT (i.e., the MT part of the first IAB node) is connected to the source IAB donor-CU (such as the IAB donor-CU1 in FIG. 2) through the source IAB donor-DU (such as the IAB donor-DU1 in FIG. 2); after triggering at least one of the following processes: the RRC re-establishment process, the F1 connection establishment process, or the F1 connection re-establishment process, the IAB-MT is connected to the target IAB donor-CU (such as the IAB donor-CU2 in FIG. 2) through the target IAB donor-DU (such as the IAB donor-DU2 in FIG. 2). Figure 10-1 Figure 10-2 Figure 10-3 Figure 10-4 In the RRC re-establishment scenario of Inter-donor-CU as shown in FIG. 2, the IAB-MT (i.e., the MT part of the first IAB node) is connected to the source IAB donor-CU (such as the IAB donor-CU1 in FIG. 2) through the source IAB donor-DU (such as the IAB donor-DU1 in FIG. 2); after triggering at least one of the following processes: the RRC re-establishment process, the F1 connection establishment process, or the F1 connection re-establishment process, the IAB-MT is connected to the target IAB donor-CU (such as the IAB donor-CU2 in FIG. 2) through the target IAB donor-DU (such as the IAB donor-DU2 in FIG. 2). Figure 10-1 Figure 10-2 Figure 10-3 Figure 10-4 In the RRC re-establishment scenario of Inter-donor-CU as shown in FIG. 2, the IAB-MT (i.e., the MT part of the first IAB node) is connected to the source IAB donor-CU (such as the IAB donor-CU1 in FIG. 2) through the source IAB donor-DU (such as the IAB donor-DU1 in FIG. 2); after triggering at least one of the following processes: the RRC re-establishment process, the F1 connection establishment process, or the F1 connection re-establishment process, the IAB-MT is connected to the target IAB donor-CU (such as the IAB donor-CU2 in FIG. 2) through the target IAB donor-DU (such as the IAB donor-DU2 in FIG. 2).

[0224] ​​​​​​​​​​​​​​​Specifically, in this implementation, the IAB donor of the first IAB node changes, i.e., changes from a source IAB donor to a target IAB donor. The IAB donor can be the target IAB donor, the target parent node of the first IAB node is connected to the target IAB donor, and the source parent node of the first IAB node is connected to the source IAB donor. The IAB donor connected to the source parent node of the first IAB node is the source IAB donor, and the IAB donor connected to the target parent node of the first IAB node is the target IAB donor, so that the scheme can be applied to the scenario where the IAB donor connected to the first IAB node changes, such as the Inter-donor-CU RRC re-establishment scenario. At this time, since the IAB donor of the first IAB node changes, the IAB donor can determine the configuration information of the BH RLC CH between the first IAB node and the source parent node of the first IAB node through the message sent by the source IAB donor of the first IAB node in step S101.

[0225] It is worth noting that the change of the IAB donor mentioned in this application specifically refers to the change of the IAB donor-CU.

[0226] S102, the IAB donor sends the configuration information of the BH RLC CH to the target parent node of the first IAB node.

[0227] In this embodiment, the IAB donor sends the configuration information of the BH RLC CH obtained in step S101 to the target parent node of the first IAB node in step S102, and correspondingly, the target parent node of the first IAB node receives the configuration information of the BH RLC CH from the IAB donor in step S102.

[0228] It should be noted that in the embodiments of the present application, the target parent node of the first IAB node can be an intermediate IAB node on the path between the first IAB node and the IAB donor, or an IAB donor DU in the IAB donor, which is not limited here. In addition, in this embodiment and the subsequent embodiments, the first IAB node can be represented by a recovery IAB node, and correspondingly, the MT part and the DU part of the first IAB node can be represented by a recovery IAB-MT and a recovery IAB-DU, respectively.

[0229] In a specific implementation, if the application scenario of the IAB donor and the first IAB node is Figure 10-1, Figure 10-2 , Figure 10-3 , Figure 10-4 In the RRC re-establishment scenario of the Inter-donor-CU shown in FIG. 10, the configuration information of the BH RLC CH in step S102 can be carried in the message sent by the source IAB donor to the target IAB donor.

[0230] S103, the target parent node of the first IAB node determines the configuration of the BH RLC CH between the first IAB node according to the configuration information of the BH RLC CH.

[0231] In this embodiment, the target parent node of the first IAB node determines the configuration of the BH RLC CH between the first IAB node according to the configuration information of the BH RLC CH in step S103.

[0232] Wherein, after the parent node of the first IAB node is changed from the source parent node to the target parent node, the target parent node of the first IAB node can further determine the configuration of the BH RLC CH between the first IAB node using the configuration information of the BH RLC CH in step S103, so as to realize the communication of the first IAB node in the IAB network through the target parent node of the first IAB node. That is, when the target parent node of the first IAB node determines that the configuration information of the BH RLC CH from the IAB donor can be used for communication between the first IAB node and the target parent node of the first IAB node, the first IAB node can realize communication in the IAB network through the target parent node of the first IAB node without sending the configuration information of the BH RLC CH to the first IAB node, thereby saving the resource configuration overhead.

[0233] Specifically, the target parent node of the first IAB node can determine the configuration of the BH RLC CH between the first IAB node and the target parent node in step S103 in multiple ways. For example: when the target parent node determines that it needs to occupy air interface resources according to the configuration of the BH RLC CH, if the target parent node has enough air interface resources, the target parent node can use the BH RLC CH configuration received in step S102. Otherwise, the target parent node generates corresponding BH RLC CH configuration information according to its own air interface resources. Thus, the parent node can flexibly configure the communication resources of the first IAB node according to the configuration information of the BH RLC CH from the IAB donor.

[0234] S104, the IAB donor sends first indication information to the first IAB node through the target parent node of the first IAB node.

[0235] In this embodiment, the IAB donor sends the first indication information to the first IAB node through the target parent node of the first IAB node in step S104, and correspondingly, the first IAB node receives the first indication information from the IAB donor through the target parent node of the first IAB node in step S104. The first indication information is used to indicate that the IAB donor connected by the first IAB node is changed, or to indicate that the IAB-donor-CU connected by the first IAB node is changed.

[0236] In a specific implementation, the IAB donor sends the first indication information to the first IAB node through the target parent node. The first indication information is used to indicate that the IAB donor connected by the first IAB node is changed. When the application scenario of the IAB donor and the first IAB node is the RRC re-establishment scenario of the inter-donor-CU as shown in Figure 10-1 、 Figure 10-2 、 Figure 10-3 、 Figure 10-4 , i.e., when the IAB donor is the target parent node connected by the first IAB node (i.e., the target IAB donor), the IAB donor can also send the first indication information to the first IAB node through the target parent node of the first IAB node, so that the first IAB node determines that the host node of the first IAB node is changed, and can subsequently communicate with the target host node in the IAB network. The configuration information of the BH RLC CH in step S104 can be carried in the message sent by the target IAB donor to the first IAB node.

[0237] In step S105, the IAB donor sends the IP address of the IAB donor to the first IAB node through the target parent node of the first IAB node.

[0238] In this embodiment, the IAB donor sends the IP address of the IAB donor to the first IAB node through the target parent node of the first IAB node in step S105, and correspondingly, the first IAB node receives the IP address of the IAB donor from the IAB donor through the target parent node of the first IAB node in step S105.

[0239] In a specific implementation, the IAB donor sends the IP address information of the IAB donor to the first IAB node through the target parent node. When the application scenario of the IAB donor and the first IAB node is the RRC re-establishment scenario of the inter-donor-CU as shown in Figure 12 、 Figure 12 、 Figure 11 、 Figure 12When the RRC reestablishment scenario of the Inter-donor-CU is shown, that is, when the IAB donor is a host node connected to the target parent node of the first IAB node (that is, the target IAB donor), the IAB donor can also send the IP address information of the target IAB donor to the first IAB node through the target parent node of the first IAB node, so that the first IAB node triggers the F1 connection establishment / reestablishment process to the target IAB donor indicated by the IP address information. Wherein, the IP address of the IAB donor in step S105 can be carried in the message sent by the target IAB donor to the first IAB node.

[0240] S106, the first IAB node determines that the RRC reestablishment with the IAB donor is completed.

[0241] In this embodiment, the first IAB node determines that the RRC reestablishment with the IAB donor is completed in step S106, and after step S106, steps S107 and S108 are executed.

[0242] S107, the IAB donor sends the first configuration information to the first IAB node through the target parent node of the first IAB node.

[0243] In this embodiment, the IAB donor sends the first configuration information to the first IAB node through the target parent node of the first IAB node in step S107, and correspondingly, the first IAB node receives the first configuration information from the IAB donor through the target parent node of the first IAB node in step S107.

[0244] Specifically, the first IAB node can determine that the RRC reestablishment with the IAB donor is completed in step S106, and correspondingly, the IAB donor can also determine that the RRC reestablishment with the first IAB node is completed in step S106. And the IAB donor can execute step S107 after determining that the RRC reestablishment with the first IAB node is completed, that is, sending the first configuration information to the first IAB node through the target parent node of the first IAB node.

[0245] The first configuration information includes at least one of the following: a source identifier of the cell of the first IAB node, a target identifier of the cell of the first IAB node, a PLMN ID of the cell of the first IAB node, SSB information of the cell of the first IAB node, or activation indication information of the cell of the first IAB node. The source identifier of the cell of the first IAB node refers to the identifier of the cell to which the first IAB node is connected via a source parent node and is under a source IAB donor. The target identifier of the cell of the first IAB node refers to the identifier of the cell to which the first IAB node is connected via a target parent node and is under a target IAB donor.

[0246] In a specific implementation, if the application scenario of the IAB donor and the first IAB node is Figure 11 、 Figure 11 、 Figure 12 、 Figure 12 In the RRC re-establishment scenario of the Inter-donor-CU shown, that is, when the IAB donor is the host node (that is, the target IAB donor) connected to the target parent node of the first IAB node, the IAB donor can also send first configuration information to the first IAB node through the target parent node of the first IAB node, so that the first IAB node updates the network configuration of the first IAB node according to the first configuration information, and can subsequently use the updated network configuration to communicate in the IAB network.

[0247] S108: The first IAB node sends first information to a child node of the first IAB node.

[0248] In this embodiment, the first IAB node sends first information to a child node of the first IAB node in step S108. Accordingly, the child node of the first IAB node receives the first information from the first IAB node in step S108. The first information includes at least one of the following: an indication of a change in an IAB donor to which the first IAB node is connected, an indication of RRC re-establishment, identification information of a base station for RRC re-establishment, and identification information of a cell for RRC re-establishment.

[0249] The indication information of the change of the IAB donor connected to the first IAB node refers to the indication information of the change of the donor-CU.

[0250] It should be noted that, in the embodiment of the present application, the first IAB node is the parent node of the child node, wherein the child node of the first IAB node can be an IAB node or a terminal device (such as UE), which is not limited here.

[0251] Optionally, the first IAB node can send the first information to the child node according to the obtained first indication information in step S104.

[0252] In a specific implementation, the first information is carried in a media access control layer control element (MAC CE); or, the first information is carried in a BAP control PDU.

[0253] In step S109, the child node of the first IAB node triggers at least one of the following procedures according to the first information: RRC re-establishment, F1 connection establishment, or F1 connection re-establishment.

[0254] In the embodiment, the child node of the first IAB node triggers at least one of the following procedures according to the first information received in step S108: RRC re-establishment, F1 connection establishment, or F1 connection re-establishment.

[0255] In a specific implementation, before the first IAB node sends the first information to the child node of the first IAB node in step S108, if the F1 connection establishment (or F1 connection re-establishment) between the first IAB node and the IAB donor is not completed. In step S109, when the child node of the first IAB node triggers RRC re-establishment or F1 connection establishment / re-establishment according to the first information, i.e., when the child node of the first IAB node sends a request message for RRC re-establishment or a request message for F1 connection establishment / re-establishment to the first IAB node, the first IAB node can cache the received request message, and after determining that the F1 connection establishment / re-establishment between the first IAB node and the IAB donor is completed, send the cached request message to the IAB donor, so that the RRC re-establishment or the F1 connection establishment / re-establishment between the child node and the IAB donor is completed.

[0256] In another specific implementation, before the first IAB node sends the first information to the child node of the first IAB node in step S108, the first IAB node can also determine that the F1 connection establishment / re-establishment between the first IAB node and the IAB donor is completed. That is, the first IAB node sends the first information to the child node of the first IAB node after determining that the F1 connection establishment / re-establishment between the first IAB node and the IAB donor is completed, so that the child node can trigger RRC re-establishment or F1 connection establishment / re-establishment to the IAB donor according to the first information through the established / re-established F1 connection between the first IAB node and the IAB donor in step S109.

[0257] Based on the above technical solution, after the first IAB node determines that the RRC re-establishment with the target IAB donor is completed, i.e., the host node of the first node is changed to the target IAB donor, the first IAB node sends the first information to the child node of the first IAB node, so that the child node of the first IAB node triggers the RRC re-establishment and / or the establishment / re-establishment of the F1 connection with the target IAB donor according to the first information, to realize that the child node of the first IAB node communicates in the IAB network through the first IAB node. That is, through the above scheme, the first IAB node obtains a new configuration, and notifies the descendant node (child node) to trigger the RRC re-establishment process, so that after the recovery IAB node performs the RRC re-establishment to the new IAB host, the descendant node of the recovery IAB node can also work normally, and establish / re-establish the F1 connection with the target IAB donor.

[0258] In the embodiments of the present application, an example of a flowchart of an Inter-donor-CU RRC re-establishment scenario can be as shown in Figure 12 The RRC re-establishment process can include the following steps.

[0259] Step 1. When the recovery IAB node (i.e., the first IAB node) detects that the link switching between the source parent node fails, the radio link failure RLF, the integrity protection failure, the RRC reconfiguration failure, etc., the RRC reconnection is triggered. That is, step 1 is executed, and the recovery IAB-MT (i.e., the MT part of the first IAB node) sends an RRC re-establishment request message to the target IAB donor-CU through the selected new parent node (the new parent node can also be called the target parent node, and the target parent node can be an IAB node or a target IAB donor DU).

[0260] Optionally, the physical cell identifier PCI of the access cell of the recovery IAB-MT under the source parent node and the identifier C-RNTI of the recovery IAB-MT under the access cell can be carried in the RRC re-establishment request message.

[0261] Step 2. The target IAB donor-CU sends a query UE context request message (Retrieve UE Context Request) to the source IAB donor-CU.

[0262] Optionally, the message can carry the cell identity of the IAB-MT performing the re-establishment cell and the integrity check value shortMAC-I in addition to the PCI and C-RNTI information carried by the IAB-MT in the RRC re-establishment request message. The IAB-MT performing the re-establishment cell refers to the cell selected by the IAB-MT performing the cell selection in the RRC re-establishment process.

[0263] Step 3. The source IAB donor-CU sends a query UE context response message (Retrieve UE Context Response) to the target IAB donor-CU.

[0264] Optionally, the message can carry the context of the IAB node, including the context of the IAB-MT and the context information of the IAB-DU.

[0265] The context of the IAB-MT includes the configuration of the BH RLC CH used by the IAB-MT to access the source parent node (or the configuration information of the BH RLC CH established between the IAB-MT and the source parent node), including at least one of the following information:

[0266] The identity of the BH RLC CH (BH RLC CH ID), the logical channel identity corresponding to the BH RLC CH (BH LCH ID), the configuration of the RLC (RLC-config), and the configuration of the logical channel (LCH-config).

[0267] The context of the IAB-DU includes at least one of the following information:

[0268] The identity of the IAB-DU (IAB-DU id and / or IAB-DU name), the identity of the base station to which the IAB-DU belongs (gNB ID), the cell local identity of the IAB-DU (cell local ID), the PLMN ID of the IAB node, the SSB information of the IAB-DU cell, etc.

[0269] Step 4. The target IAB donor-CU sends an RRC re-establishment message to the IAB-MT.

[0270] Optionally, the message carries indication information of the donor-CU change, so that the IAB-MT can trigger the establishment / re-establishment of the F1 connection with the target IAB donor-CU when the donor-CU changes.

[0271] Step 5. The target IAB donor-CU sends a UE Context Setup Request message to the target parent node IAB-DU.

[0272] Optionally, the message carries the configuration of the BH RLC CH used by the recovery IAB-MT’s access source parent node, so that the target parent node decides whether to allocate a new configuration for the BH RLC CH.

[0273] Wherein, the order between step 4 and step 5 is not limited.

[0274] Step 6. The target parent node IAB-DU sends a UE Context Setup Response message to the target IAB donor-CU.

[0275] Step 7. The recovery IAB-MT sends an RRC Reestablishment Complete message to the target IAB donor-CU.

[0276] Wherein, the order between step 5, 6 and step 7 is not limited.

[0277] Step 8. The target IAB donor-CU sends an RRC Reconfiguration message to the recovery IAB-MT, which carries the BAP address allocated by the target IAB donor-CU for the recovery IAB node, the default BH RLC CH ID and routing ID newly allocated by the target IAB donor-CU for the recovery IAB node on the target path, and the IP address allocated by the target IAB donor for the recovery IAB node. Wherein, the target path refers to the path between the recovery IAB node and the target IAB donor connected through the target parent node.

[0278] Optionally, the message can also carry at least one of the following information:

[0279] The IP address of the target IAB donor-CU, and the indication information of donor-CU change.

[0280] In addition, in order to save the signaling consumption between the target IAB donor-CU and the IAB-MT, the indication information of donor-CU change can be sent only once. Optionally, if the indication information of donor-CU change is carried in the RRC Reestablishment message in step 4, the indication information will not be carried in the RRC Reconfiguration message in step 8. Otherwise, if the indication information is not carried in step 4, the indication information will be carried in step 8.

[0281] At this point, the recovering IAB-MT completes the RRC re-establishment with the target IAB donor.

[0282] It should be noted that Figure 11 The flow chart shown can be Figure 12 In step S101 of the embodiment shown, the IABdonor obtains the configuration information of the BH RLC CH. Figure 11 In the implementation process shown, the IAB donor can also obtain the configuration information of the BH RLC CH through other methods. Figure 12 The other steps after step S101 in the embodiment shown are: Figure 11 The implementation process of steps S102 to S108 of the embodiment shown in FIG. Figure 12 Further implementation can be achieved based on the process shown in the figure, or not through Figure 12 The process shown is an implementation process, and further implementation is based on other implementation processes, which are not specifically limited here.

[0283] In one possible implementation, Figure 12 As shown in the flow chart, Figure 11 In step S101 of the embodiment shown, the IAB donor obtaining the configuration information of the BH RLC CH may include: the IAB donor receiving a user equipment UE context response message (ie, Figure 12 In step 3, the Retrieve UEContext Response message includes the BH RLC CH configuration information. Specifically, when the IAB donor is a donor node connected to the target parent node of the first IAB node (i.e., a target IAB donor), the IAB donor may be the BH RLC CH configuration information obtained from the Retrieve UEContext Response message sent by the donor node connected to the source parent node of the first IAB node.

[0284] In one possible implementation, Figure 12 In step S102 of the embodiment shown, the IAB donor sends the BH RLC CH configuration information to the target parent node of the first IAB node. Figure 10-1 Step 5 shown is implemented by sending and receiving the configuration information of the BH RLC CH through a UE context setup request message (UE Context Setup Request).

[0285] In one possible implementation, Figure 10-2The IAB donor in step S104 of the embodiment sends first indication information to the first IAB node through the target parent node of the first IAB node, which can be Figure 10-3 the donor-CU change indication information shown in steps 4 and 8 in the middle. Thus, step S104 can be implemented by Figure 10-4 Step 4, that is, the sending process and the receiving process of the first indication information are implemented through the RRC reestablishment message; in addition, the sending process and the receiving process of the first indication information can also be implemented by Figure 11 Step 8, that is, the sending process and the receiving process of the first indication information are implemented through the RRC reconfiguration message.

[0286] In a possible implementation, in Figure 12 Step S105 of the embodiment, the IAB donor sends the IP address of the IAB donor to the first IAB node through the target parent node of the first IAB node. For example, the sending process and the receiving process of the IP address of the IAB donor are implemented by Figure 11 Step 8, that is, the sending process and the receiving process of the IP address of the IAB donor are implemented through the RRC reconfiguration message. Figure 13 When the first indication information in step S104 is also implemented by Step 8, that is, the sending process and the receiving process are implemented through the RRC reconfiguration message, the first indication information can be carried in the same message as the IP address of the IAB donor in step S105, that is, both are carried in the RRC reconfiguration message.

[0287] Figure 12 In a possible implementation, if the application scenario of the IAB donor and the first IAB node is Figure 12 , Figure 13 , Figure 14 The RRC reestablishment scenario of the Inter-donor-CU, that is, when the IAB donor is the target parent node connected to the first IAB node (that is, the target IAB donor), the first IAB node can determine that the RRC reestablishment between the IAB donor is completed in Figure 15 Step S106 of the embodiment, that is, the first IAB node can determine that the RRC reestablishment between the IAB donor is completed after Figures 13-15 Step 7 receives the RRC reestablishment completion message sent by the target IAB donor.

[0288] In addition, since the IAB donor of the first IAB node changes in the Inter-donor-CU scenario, the configuration information of the recovery IAB-DU (the DU part in the first IAB node) needs to be updated. For example: the cell identity or CGI of the recovery IAB-DU cell, the PLMN ID of the recovery IAB-DU, the SSB information of the recovery IAB-DU cell, etc. There are two ways for the recovery IAB-DU to obtain the new configuration, including: obtaining from the OAM server, and obtaining from the target IAB donor. In Figure 11 In step S107 of the embodiment shown, the IAB donor can send the first configuration information to the first IAB node in multiple ways, which will be described below by way of example of several implementation manners.

[0289] Manner one, obtaining the first configuration information from the OAM server.

[0290] Referring to Figures 13-15 , after the recovery IAB-MT (the MT part of the first IAB node) completes the RRC re-establishment with the target IAB donor, the recovery IAB-DU can obtain the new configuration information from the OAM server through the target IAB donor. That is: after the target IAB donor obtains the new configuration information sent from the OAM server, it further sends the new configuration information to the recovery IAB-DU. That is to say, in this scenario, the target IAB donor only plays the role of transferring the new configuration information between the recovery IAB-DU and the OAM server.

[0291] The new configuration of the recovery IAB-DU includes at least one of the following information: the CGI / Cell identity of the IAB-DU cell, the PLMN ID of the IAB-DU cell, and the SSB information of the IAB-DU cell.

[0292] Optionally, in this scenario, the recovery IAB node can obtain the IP address of the target IAB donor-CU through the OAM server, without the need to obtain it through the RRC reconfiguration message in step 8 in Figures 13-15 Figure 11 In this scenario, the IP address of the target IAB donor-CU does not need to be carried in the RRC reconfiguration message in step 8 in Figure 11 Once the recovery IAB node obtains the new configuration, it needs to trigger the establishment / re-establishment procedure of the F1 interface to the target IAB donor. The specific flowchart of the recovery IAB node triggering the establishment / re-establishment procedure of the F1 interface to the target IAB donor includes the following steps.

[0293] 1. The IAB-DU resumes using the IP address assigned by the target IAB donor, and triggers the establishment of TNLA association with the target IAB donor-CU.

[0294] 2. The IAB-DU sends an F1 Setup Request message to the target IAB donor-CU, requesting to establish / re-establish the F1 connection between the resuming IAB-DU and the target IAB donor-CU.

[0295] 3. The target IAB donor-CU sends an F1 Setup Response message to the resuming IAB-DU.

[0296] 4. The resuming IAB-DU sends at least one of the following information (i.e., first information) to the child node, so that the child node triggers the RRC re-establishment procedure to the target IAB donor, including:

[0297] an indication information of donor-CU change, an indication information of RRC re-establishment, an identity of re-establishment base station (e.g., gNB ID), and an identity of re-establishment cell (e.g., PCI).

[0298] The indication information of donor-CU change (i.e., first indication information) is used to indicate that the IAB donor connected by the first IAB node is changed. The indication information of RRC re-establishment is used to indicate that the child node triggers the RRC re-establishment, so that the child node knows that the RRC re-establishment procedure needs to be performed. The identity of re-establishment cell (e.g., PCI) is used to indicate the cell identity corresponding to the selected cell in the RRC re-establishment procedure to the child node, so that the child node performs cell selection to the corresponding re-establishment cell. The identity of re-establishment base station (e.g., gNB ID) is used to indicate the base station identity corresponding to the selected cell in the RRC re-establishment procedure to the child node, so that the child node performs cell selection to the re-establishment cell under the specified base station (the base station corresponding to the re-establishment cell is the base station identified by the gNB ID). The above information can be sent in a MAC CE or a backhaul adaptation protocol control packet data unit (BAP control PDU).

[0299] Optionally, in the process shown in FIG. 4, the order between step 4 and step 1 or step 2 or step 3 is not limited. Figure 11

[0300] Method two: obtaining the first configuration information from the target IAB donor.

[0301] ​The difference from mode 1 is that the new configuration information (i.e., the first configuration information) of the recovery IAB-DU is generated by the target IAB donor and then notified to the recovery IAB-DU, which is embodied in steps 2 and 3.

[0302] As a possible implementation, as shown in Figure 11 , the recovery IAB-DU acquires the new configuration information through step 2.

[0303] 2. The target IAB donor-CU sends an F1AP request message to the recovery IAB-DU, and the request message is used to establish / re-establish the F1 connection between the recovery IAB-DU and the target IAB donor-CU. The F1AP request message carries a list of information for modifying the recovery IAB-DU cell, and each information list contains at least one of the following information:

[0304] The source identity (e.g., source CGI or source Cell identity) of the recovery IAB-DU cell, the new configuration of the recovery IAB-DU, and the new cell activation indication information of the recovery IAB-DU.

[0305] The F1AP request message can be an existing F1AP message (e.g., gNB-CU Configuration Update) or a newly defined F1AP message.

[0306] 3. The recovery IAB-DU sends an F1AP response message to the target IAB donor-CU.

[0307] As another possible implementation, as shown in Figure 12 , the recovery IAB-DU acquires the new configuration information through step 3.

[0308] 2. The recovery IAB-DU sends an F1AP request message to the target IAB donor-CU.

[0309] 3. The target IAB donor-CU sends an F1AP response message to the recovery IAB-DU. The F1AP response message carries a list of information for modifying the recovery IAB-DU cell, and each information list contains at least one of the following information:

[0310] The source identity (e.g., source CGI or source Cell identity) of the recovery IAB-DU cell, the new configuration of the recovery IAB-DU, and the new cell activation indication information of the recovery IAB-DU.

[0311] The F1AP request message can be an existing F1AP message (for example, gNB-DU Configuration UpdateAck) or a newly defined F1AP message.

[0312] It should be noted that, Figure 11 The flowchart shown is in the case of Figures 13-15 The implementation process of the several examples of the first IAB node sending the first configuration information to the IAB donor in step S107 of the embodiment shown, in addition to Figures 13-15 The implementation process of the several examples of the first IAB node sending the first configuration information to the IAB donor in step S107 of the embodiment shown, in addition to Figure 11 The flowchart shown is in the case of Figures 13-15 Step S107 of the embodiment shown, needs to be executed after step S106 of the embodiment shown, and does not depend on the implementation process of steps S101 ( Figures 13-15 The implementation process of steps S102 and S103 of the embodiment shown, and the execution order between the foregoing steps S107, S104, and S105 of the embodiment shown is not limited in the embodiments of the present application. Figure 11 Figure 12 In addition, when applied to the scenario shown in Figure 16 The first IAB node can execute step S108 of the embodiment shown in step 4 in

[0313] In addition, when applied to the scenario shown in Figure 17 The first IAB node can execute step S108 of the embodiment shown after step 4 in Figure 17 . Figure 17

[0314] Specifically, when applied to the scenario shown in Figure 17 The first IAB node can execute step S108 of the embodiment shown after step 4 in Figure 17 . Figures 11-15 Namely, once the child node receives the MAC CE / BAPcontrol PDU in step 4, the RRC reestablishment process to the target IAB donor-CU will be triggered, and the corresponding process is consistent with the RRC reestablishment process to recover the IAB-MT ( Figure 17 ), which will not be described here.

[0315] The embodiments of the present application are described above from the perspective of methods, and the communication device in the embodiments of the present application is introduced from the perspective of specific device implementation.

[0316] Please refer to Figures 11-15 The communication device 1600 provided by the embodiments of the present application, specifically the communication device 1600 includes a processing unit 1601 and a transceiver unit 1602. ​​

[0317] In a process of implementing the functions of the IAB donor described above, the implementation of the processing unit 1601 and the transceiver unit 1602 in the communication apparatus 1600 includes the following processes.

[0318] The processing unit 1601 is configured to obtain configuration information of a backhaul link radio link control channel (BH RLC CH) between the first IAB node and a source parent node of the first IAB node.

[0319] The transceiver unit 1602 is configured to send the configuration information of the BH RLC CH to a target parent node of the first IAB node.

[0320] In a specific implementation, the configuration information of the BH RLC CH includes at least one of the following:

[0321] The identification of the BH RLC CH, the logical channel identification corresponding to the BH RLC CH, the configuration information of the radio link control channel (RLC), or the configuration information of the logical channel.

[0322] In a specific implementation, the IAB donor is a target IAB donor, the target parent node is connected to the target IAB donor, and the source parent node is connected to a source IAB donor.

[0323] In a specific implementation,

[0324] The processing unit 1601 is specifically configured to receive an obtain user equipment (UE) context response message from the source IAB donor, and the obtain UE context response message includes the configuration information of the BH RLC CH.

[0325] In a specific implementation, the transceiver unit 1602 is further configured to:

[0326] The transceiver unit 1602 is further configured to send first indication information to the first IAB node through the target parent node, and the first indication information is used to indicate that the IAB donor connected by the first IAB node is changed.

[0327] In a specific implementation,

[0328] The first indication information is carried in an RRC reestablishment message; or

[0329] The first indication information is carried in an RRC reconfiguration message.

[0330] In a specific implementation, the transceiver unit 1602 is further configured to:

[0331] sending, by the target parent node, internet protocol (IP) address information of the target IAB donor to the first IAB node.

[0332] In a specific implementation, the IP address information of the target IAB donor is carried in an RRC reconfiguration message.

[0333] In a specific implementation, the transceiver 1602 is further configured to:

[0334] sending, by the target parent node, first configuration information to the first IAB node, the first configuration information comprising at least one of:

[0335] a source identity of a cell of the first IAB node, a target identity of the cell of the first IAB node, a PLMN ID of the cell of the first IAB node, SSB information of the cell of the first IAB node, or activation indication information of the cell of the first IAB node.

[0336] It should be noted that the information execution process and the like of the units of the communication apparatus 1600 described above can be specifically referred to the corresponding descriptions of the IAB donor in the method embodiments described above, and will not be described herein.

[0337] When the communication apparatus 1600 is configured to implement the functions of the target parent node of the first IAB node described above, the implementation of the processing unit 1601 and the transceiver 1602 in the communication apparatus 1600 includes the following processes.

[0338] The transceiver 1602 is configured to receive configuration information of a backhaul link control channel (BH RLC CH) from an integrated access backhaul donor (IAB donor), the configuration information of the BH RLC CH being configuration information of a BH RLC CH between a first IAB node and a source parent node of the first IAB node.

[0339] The processing unit 1601 is configured to determine the configuration of the BH RLC CH between the first IAB node according to the configuration information of the BH RLC CH.

[0340] In a specific implementation, the configuration information of the BH RLC CH comprises at least one of:

[0341] an identity of the BH RLC CH, a logical channel identity corresponding to the BH RLC CH, configuration information of a radio link control (RLC) channel, or configuration information of a logical channel.

[0342] It should be noted that the information execution process and the like of the units of the communication apparatus 1600 described above can be specifically refer to the description of the target parent node of the first IAB node in the foregoing method embodiment of the present application, and will not be described here.

[0343] When the communication apparatus 1600 is used to implement the functions of the first IAB node described above, the implementation of the processing unit 1601 and the transceiver unit 1602 in the communication apparatus 1600 includes the following processes.

[0344] The processing unit 1601 is configured to determine that RRC reestablishment with a target access backhaul integration donor IAB donor is completed.

[0345] The transceiver unit 1602 is configured to send first information to a child node of the first IAB node.

[0346] The first information includes at least one of the following:

[0347] The indication information of the change of the IAB donor to which the first IAB node is connected, the indication information of the RRC reestablishment, the identification information of the base station of the RRC reestablishment, and the identification information of the cell of the RRC reestablishment.

[0348] In a specific implementation manner,

[0349] The first information is carried in a medium access control layer control unit MAC CE; or

[0350] The first information is carried in a BAP control PDU.

[0351] In a specific implementation manner, the transceiver unit 1602 is further configured to:

[0352] Receive first indication information from the target IAB donor, the first indication information being used to indicate that the IAB donor to which the first IAB node is connected is changed.

[0353] In a specific implementation manner,

[0354] The first indication information is carried in an RRC reestablishment message; or

[0355] The first indication information is carried in an RRC reconfiguration message.

[0356] In a specific implementation manner, the processing unit 1601 is further configured to determine that F1 connection establishment / reestablishment with the IAB donor is completed or the F1 connection has been restored.

[0357] In a specific implementation manner, the transceiver unit 1602 is further configured to:

[0358] receiving the IP address information of the target IAB donor from the target IAB donor.

[0359] In a specific implementation, the IP address information of the target IAB donor is carried in an RRC reconfiguration message.

[0360] In a specific implementation, the transceiver 1602 is specifically configured to:

[0361] receive first configuration information from the target IAB donor, the first configuration information including at least one of:

[0362] a source identity of a cell of the first IAB node, a target identity of the cell of the first IAB node, a PLMN ID of the cell of the first IAB node, SSB information of the cell of the first IAB node, or activation indication information of the cell of the first IAB node.

[0363] It should be noted that the information execution process and the like of the units of the communication apparatus 1600 described above can be specifically referred to the corresponding description of the first IAB node in the method embodiments described above, and will not be described here.

[0364] When the communication apparatus 1600 is used to implement the functions corresponding to the child node of the first IAB node described above, the implementation of the processing unit 1601 and the transceiver 1602 in the communication apparatus 1600 includes the following processes.

[0365] The transceiver 1602 is configured to receive first information from the first IAB node, the first information including at least one of:

[0366] indication information that an IAB donor connected to the first IAB node is changed, indication information of RRC reestablishment, identity information of a base station for RRC reestablishment, and identity information of a cell for RRC reestablishment.

[0367] The processing unit 1601 is configured to trigger at least one of the following processes according to the first information: RRC reestablishment, F1 connection establishment, or F1 connection reestablishment.

[0368] In a specific implementation of the eighth aspect of the embodiments of the present application,

[0369] The first information is carried in a medium access control layer control unit MAC CE; or

[0370] The first information is carried in a BAP control PDU.

[0371] It should be noted that the information execution process and the like of the units of the communication device 1600 described above can be specifically referred to the description of the first IAB node of the method embodiments of the present application, and will not be described here.

[0372] Please refer to Figure 18 The structure of the communication device provided in the above embodiments of the embodiments of the present application, wherein the communication device can be specifically the IAB donor, the target parent node of the first IAB node, the first IAB node or the child node of the first IAB node in the foregoing embodiments, and the structure of the communication device can refer to the structure shown in Figure 18 .

[0373] The communication device includes at least one processor 1711, at least one memory 1712, at least one transceiver 1713, at least one network interface 1714 and one or more antennas 1715. The processor 1711, the memory 1712, the transceiver 1713 and the network interface 1714 are connected, for example, through a bus, in the embodiments of the present application, the connection can include various interfaces, transmission lines or buses, etc., and the present embodiment does not limit this. The antenna 1715 is connected to the transceiver 1713. The network interface 1714 is used to connect the communication device to other communication devices through a communication link, for example, the network interface 1714 can include the network interface between the communication device and the core network device, for example, the S1 interface, the network interface can include the network interface between the communication device and other network devices (for example, other access network devices or core network devices), for example, the X2 or Xn interface.

[0374] The processor 1711 is mainly used for processing communication protocols and communication data, and controlling the whole communication device, executing software programs, processing data of software programs, for example, for supporting the communication device to perform the actions described in the embodiments. The communication device can include a baseband processor and a central processor, the baseband processor is mainly used for processing communication protocols and communication data, and the central processor is mainly used for controlling the whole terminal device, executing software programs, and processing data of software programs. Figure 10-1The processor 1711 in the terminal device can integrate the functions of a baseband processor and a central processor. Those skilled in the art can understand that the baseband processor and the central processor can also be independent processors, and are interconnected through a bus or the like. Those skilled in the art can understand that the terminal device can include multiple baseband processors to accommodate different network standards, and the terminal device can include multiple central processors to enhance the processing capability. The various components of the terminal device can be connected through various buses. The baseband processor can also be referred to as a baseband processing circuit or a baseband processing chip. The central processor can also be referred to as a central processing circuit or a central processing chip. The functions of processing communication protocols and communication data can be built into the processor, or the functions can be stored in the memory in the form of a software program, and the processor executes the software program to implement the baseband processing functions.

[0375] The memory is mainly used for storing software programs and data. The memory 1712 can exist independently and be connected to the processor 1711. Alternatively, the memory 1712 can be integrated with the processor 1711, for example, in a chip. The memory 1712 can store program codes for implementing the technical solutions of the embodiments of the present application, and the processor 1711 controls the execution. The various computer programs executed can also be regarded as a driver of the processor 1711.

[0376] Figure 10-2 Only one memory and one processor are shown. In actual terminal devices, multiple processors and multiple memories can exist. The memory can also be referred to as a storage medium or a storage device, etc. The memory can be a storage element on the same chip as the processor, that is, an on-chip storage element, or an independent storage element, and the embodiments of the present application do not limit this.

[0377] The transceiver 1713 can be configured to support the receiving or transmitting of radio frequency signals between the communication device and a terminal. The transceiver 1713 can be connected to the antenna 1715. The transceiver 1713 includes a transmitter Tx and a receiver Rx. Specifically, one or more antennas 1715 can receive radio frequency signals, and the receiver Rx of the transceiver 1713 is configured to receive the radio frequency signals from the antenna and convert the radio frequency signals into digital baseband signals or digital intermediate frequency signals, and provide the digital baseband signals or digital intermediate frequency signals to the processor 1711 for further processing, such as demodulation processing and decoding processing. In addition, the transmitter Tx in the transceiver 1713 is also configured to receive modulated digital baseband signals or digital intermediate frequency signals from the processor 1711, and convert the modulated digital baseband signals or digital intermediate frequency signals into radio frequency signals, and transmit the radio frequency signals through one or more antennas 1715. Specifically, the receiver Rx can selectively perform one or more levels of down-mixing processing and analog-to-digital conversion processing on the radio frequency signals to obtain digital baseband signals or digital intermediate frequency signals, and the order of the down-mixing processing and the analog-to-digital conversion processing can be adjustable. The transmitter Tx can selectively perform one or more levels of up-mixing processing and digital-to-analog conversion processing on the modulated digital baseband signals or digital intermediate frequency signals to obtain radio frequency signals, and the order of the up-mixing processing and the digital-to-analog conversion processing can be adjustable. The digital baseband signals and the digital intermediate frequency signals can be collectively referred to as digital signals.

[0378] The transceiver can also be referred to as a transceiving unit, a transceiver, a transceiving device, etc. Optionally, the devices in the transceiving unit for implementing the receiving function can be regarded as a receiving unit, and the devices in the transceiving unit for implementing the transmitting function can be regarded as a transmitting unit, that is, the transceiving unit includes the receiving unit and the transmitting unit. The receiving unit can also be referred to as a receiver, an input port, a receiving circuit, etc. The transmitting unit can be referred to as a transmitter, a transmitter, or a transmitting circuit, etc.

[0379] It should be noted that, Figure 10-3 The communication device shown can be specifically used to implement Figure 10-4 the steps implemented by the communication device in the corresponding method embodiment, and achieve the corresponding technical effects of the communication device, ​ the specific implementation of the communication device shown, ​ the description in the corresponding various method embodiments, which will not be repeated here.

[0380] ​ is a structural schematic diagram of an IAB donor provided by an embodiment of the present application. The IAB donor can adopt a CU-DU separated architecture. As ​ shown, the IAB donor can be applied to, for example, ​ or ​or ​ or ​ In the system shown, the functions of the IAB donor (source IAB donor and / or target IAB donor) in the above method embodiments are implemented.

[0381] The IAB donor can include one or more DUs 1101 and one or more CUs 1102. The DU 1101 can include at least one antenna 11011, at least one radio frequency unit 11012, at least one processor 11013, and at least one memory 11014. The DU 1101 is mainly used for the transceiving of radio frequency signals and the conversion between radio frequency signals and baseband signals, and part of the baseband processing. The CU 1102 can include at least one processor 11022 and at least one memory 11021. The CU 1102 and the DU 1101 can communicate through an interface, wherein the control plane interface can be F1-C, and the user plane interface can be F1-U.

[0382] The CU 1102 is mainly used for baseband processing, controlling the base station, etc. The DU 1101 and the CU 1102 can be physically arranged together or physically arranged separately, i.e., a distributed base station. The CU 1102 is the control center of the base station, also known as the processing unit, and is mainly used to complete the baseband processing function. For example, the CU 1102 can be used to control the base station to perform the operation process of the network device in the above method embodiments.

[0383] Specifically, the baseband processing on the CU and the DU can be divided according to the protocol layer of the wireless network, which can be referred to the above content.

[0384] In an example, the CU 1102 can be composed of one or more boards, and the plurality of boards can jointly support a single-access-indicated wireless access network (e.g., a 5G network) or separately support wireless access networks of different access modes (e.g., an LTE network, a 5G network, or other access networks). The memory 11021 and the processor 11022 can serve one or more boards. That is, the memory and the processor can be separately arranged on each board. Alternatively, the plurality of boards can share the same memory and processor. In addition, each board can be further provided with necessary circuits. The DU 1101 can be composed of one or more boards, and the plurality of boards can jointly support a single-access-indicated wireless access network (e.g., a 5G network) or separately support wireless access networks of different access modes (e.g., an LTE network, a 5G network, or other access networks). The memory 11014 and the processor 11013 can serve one or more boards. That is, the memory and the processor can be separately arranged on each board. Alternatively, the plurality of boards can share the same memory and processor. In addition, each board can be further provided with necessary circuits.

[0385] Optionally, the CU 1102 can transmit with a child node of the IAB donor through the DU 1101, the CU 1102 can be connected with another IAB donor through an interface, the CU 1102 can receive data and / or messages from the other IAB donor (e.g., a CU of the other IAB donor) through the interface, or the CU 1102 can send data and / or messages to the other IAB donor through the interface.

[0386] The embodiments of the present disclosure further provide a computer readable storage medium storing one or more computer-executable instructions, which, when executed by a processor, cause the processor to perform the method implemented by the communication apparatus, the method implemented by the IAB donor, the target parent node of the first IAB node, the first IAB node, or the child node of the first IAB node.

[0387] The embodiments of the present disclosure further provide a computer program product (or computer program) storing one or more computers, which, when executed by the processor, cause the processor to perform the method implemented by the communication apparatus, the method implemented by the IAB donor, the target parent node of the first IAB node, the first IAB node, or the child node of the first IAB node.

[0388] The embodiments of the present application further provide a chip system, which comprises a processor and is configured to support a communication device to implement the method implemented by the communication device, such as the method implemented by the IAB donor, the target parent node of the first IAB node, the first IAB node, or the child node of the first IAB node. In a possible design, the chip system can further comprise a memory configured to store necessary program instructions and data of the communication device. The chip system can be composed of a chip, or can comprise the chip and other discrete devices.

[0389] The embodiments of the present application further provide a communication system, which comprises the communication device, such as the IAB donor, the target parent node of the first IAB node, the first IAB node, and / or the child node of the first IAB node.

[0390] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented by other manners. For example, the device embodiments described above are merely illustrative, for example, the division of the units is merely a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units or components shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0391] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiments.

[0392] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0393] The integrated unit, if implemented in the form of a software function unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application essentially or the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

Claims

1. A communication method for accessing an integrated IAB system, characterized in that: include: The integrated access and backhaul host IAB donor obtains configuration information of a radio link control channel (BH RLC CH) of a backhaul link, wherein the configuration information of the BH RLC CH is configuration information of the BH RLC CH between a first integrated access and backhaul IAB node and a source parent node of the first IAB node; The IAB donor sends the BH RLC CH configuration information to the target parent node of the first IAB node, where the BH RLC CH configuration information is used by the target parent node to configure communication resources of the first IAB node.

2. The method according to claim 1, characterized in that The configuration information of the BH RLC CH includes at least one of the following: The identifier of the BH RLC CH, the identifier of the logical channel corresponding to the BH RLC CH, the configuration information of the radio link control channel RLC or the configuration information of the logical channel.

3. The method according to claim 1 or 2, characterized in that The IAB donor is a target IAB donor, the target parent node is connected to the target IAB donor, and the source parent node is connected to the source IAB donor.

4. The method according to claim 3, characterized in that The IAB donor obtains the configuration information of the BH RLC CH including: The IAB donor receives a Get UE Context Response message from the source IAB donor, where the Get UE Context Response message includes configuration information of the BH RLC CH.

5. The method according to claim 3 or 4, characterized in that The method further comprises: The IAB donor sends first indication information to the first IAB node through the target parent node, where the first indication information is used to indicate that the IAB donor connected to the first IAB node is changed.

6. The method according to claim 5, characterized in that The first indication information is carried in an RRC re-establishment message; or, The first indication information is carried in an RRC reconfiguration message.

7. The method according to any one of claims 3 to 6, characterized in that The method further comprises: The IAB donor sends the Internet Protocol (IP) address information of the IAB donor to the first IAB node through the target parent node.

8. The method according to claim 7, characterized in that The IP address information of the target IAB donor is carried in the RRC reconfiguration message.

9. The method according to any one of claims 3 to 8, characterized in that The method further comprises: The IAB donor sends first configuration information to the first IAB node through the target parent node, where the first configuration information includes at least one of the following: The source identifier of the cell of the first IAB node, the target identifier of the cell of the first IAB node, the PLMNID of the cell of the first IAB node, the SSB information of the cell of the first IAB node, or the activation indication information of the cell of the first IAB node.

10. A communication method for accessing and backhauling integrated IAB system, characterized in that: include: The target parent node of the first access and backhaul integrated IAB node receives configuration information of a radio link control channel (BH RLC CH) of a backhaul link from an IAB donor, where the configuration information of the BH RLC CH is configuration information of the BH RLC CH between the first IAB node and the source parent node of the first IAB node; The target parent node determines the BH RLC CH configuration between the first IAB node and the target parent node according to the BH RLC CH configuration information, and the BH RLC CH configuration information is used by the target parent node to configure communication resources of the first IAB node.

11. The method according to claim 10, characterized in that The configuration information of the BH RLC CH includes at least one of the following: The identifier of the BH RLC CH, the identifier of the logical channel corresponding to the BH RLC CH, the configuration information of the radio link control channel RLC or the configuration information of the logical channel.

12. A communication method for accessing and backhauling integrated IAB system, characterized in that: include: The first access-backhaul integrated IAB node determines that RRC re-establishment with the IAB donor is complete, and the target parent node of the first IAB node configures communication resources of the first IAB node according to BH RLC CH configuration information from the IAB donor, where the BH RLC CH configuration information is BH RLC CH configuration information between the first IAB node and the source parent node of the first IAB node; The first IAB node sends first information to a child node of the first IAB node; The first information includes at least one of the following: Indication information of IAB donor change connected to the first IAB node, indication information of RRC re-establishment, identification information of the base station for RRC re-establishment, and identification information of the cell for RRC re-establishment.

13. The method according to claim 12, characterized in that The first information is carried in a control unit MAC CE of a media access control layer; or, The first information is carried in a backhaul adaptation protocol control packet data unit BAP control PDU.

14. The method according to claim 12 or 13, characterized in that Before the first IAB node sends the first information to the child node, the method further includes: The first IAB node receives first indication information from the target IAB donor, where the first indication information is used to indicate a change in the IAB donor connected to the first IAB node.

15. The method according to claim 14, characterized in that The first indication information is carried in an RRC re-establishment message; or, The first indication information is carried in an RRC reconfiguration message.

16. The method according to any one of claims 12 to 15, characterized in that Before the first IAB node sends the first information to the child node of the first IAB node, the method further includes: The first IAB node determines that the F1 connection establishment / re-establishment with the IAB donor is completed or the F1 connection has been restored.

17. The method according to any one of claims 12 to 16, characterized in that The method further comprises: The first IAB node receives the IP address information of the IAB donor from the IAB donor.

18. The method according to claim 17, characterized in that The IP address information of the IAB donor is carried in the RRC reconfiguration message.

19. The method according to any one of claims 12 to 18, characterized in that After the first IAB node determines that the RRC re-establishment between the node and the IAB donor is completed, the method further includes: The first IAB node receives first configuration information from the IAB donor, where the first configuration information includes at least one of the following: The source identifier of the cell of the first IAB node, the target identifier of the cell of the first IAB node, the PLMNID of the cell of the first IAB node, the SSB information of the cell of the first IAB node, or the activation indication information of the cell of the first IAB node.

20. A communication method for accessing an integrated IAB system, characterized in that: include: The child node of the first integrated access and backhaul IAB node receives first information from the first IAB node, where the first information includes at least one of the following: Indication information of a change in the IAB donor to which the first IAB node is connected, indication information of an RRC re-establishment, identification information of the base station for the RRC re-establishment, and identification information of the cell for the RRC re-establishment; communication resources of the first IAB node are configured by the target parent node of the first IAB node according to configuration information of a BH RLC CH from the IAB donor; the configuration information of the BHRLC CH is configuration information of the BH RLC CH between the first IAB node and the source parent node of the first IAB node; The subnode triggers at least one of the following processes according to the first information: RRC re-establishment, F1 connection establishment, or F1 connection re-establishment.

21. The method according to claim 20, characterized in that The first information is carried in a control unit MAC CE of a media access control layer; or, The first information is carried in a backhaul adaptation protocol control packet data unit BAP control PDU.

22. A communication device, characterized in that: The device is an integrated access and return host (IAB) donor, and includes: a processing unit, configured to obtain configuration information of a radio link control channel (BHRLCCH) of a backhaul link, wherein the configuration information of the BHRLCCH is configuration information of the BHRLCCH between a first access and backhaul integrated IAB node and a source parent node of the first IAB node; The transceiver unit is configured to send the BHRLCCH configuration information to the target parent node of the first IAB node, where the BHRLCCH configuration information is used by the target parent node to configure communication resources of the first IAB node.

23. The device according to claim 22, characterized in that The BHRLCCH configuration information includes at least one of the following: The identifier of the BHRLCCH, the identifier of the logical channel corresponding to the BHRLCCH, the configuration information of the radio link control channel RLC or the configuration information of the logical channel.

24. The device according to claim 22 or 23, characterized in that The IAB donor is a target IABdonor, the target parent node is connected to the target IABdonor, and the source parent node is connected to the source IABdonor.

25. The device according to claim 24, characterized in that The processing unit is specifically configured to receive a user equipment UE context acquisition response message from the source IABdonor, where the UE context acquisition response message includes the configuration information of the BHRLCCH.

26. The device according to claim 24 or 25, characterized in that The transceiver unit is further configured to: First indication information is sent to the first IAB node through the target parent node, where the first indication information is used to indicate that an IAB donor connected to the first IAB node is changed.

27. The device according to claim 26, characterized in that The first indication information is carried in an RRC re-establishment message; or, The first indication information is carried in an RRC reconfiguration message.

28. The device according to any one of claims 24 to 27, characterized in that The transceiver unit is further configured to: The IP address information of the target IABdonor is sent to the first IAB node through the target parent node.

29. The device according to claim 28, characterized in that The IP address information of the target IABdonor is carried in the RRC reconfiguration message.

30. The device according to any one of claims 24 to 29, characterized in that The transceiver unit is further configured to: First configuration information is sent to the first IAB node through the target parent node, where the first configuration information includes at least one of the following: The source identifier of the cell of the first IAB node, the target identifier of the cell of the first IAB node, the PLMNID of the cell of the first IAB node, the SSB information of the cell of the first IAB node, or the activation indication information of the cell of the first IAB node.

31. A communication device, characterized in that: The device is a target parent node of a first IAB node, and the device includes: a transceiver unit configured to receive configuration information of a radio link control channel (BHRLCCH) of a backhaul link from an integrated access and backhaul host (IAB) donor, wherein the configuration information of the BHRLCCH is configuration information of the BHRLCCH between a first integrated access and backhaul IAB node and a source parent node of the first IAB node; The processing unit is configured to determine the configuration of the BH RLCCH between the target parent node and the first IAB node according to the configuration information of the BHRLCCH, wherein the configuration information of the BH RLCCH is used by the target parent node to configure communication resources of the first IAB node.

32. The device according to claim 31, characterized in that The BHRLCCH configuration information includes at least one of the following: The identifier of the BHRLCCH, the identifier of the logical channel corresponding to the BHRLCCH, the configuration information of the radio link control channel RLC or the configuration information of the logical channel.

33. A communication device, characterized in that: The device is a first access and backhaul integrated IAB node, and the device includes: a processing unit, configured to determine that RRC re-establishment with a target access backhaul integrated host (IAB) donor is complete, wherein communication resources of the first IAB node are configured by the target parent node of the first IAB node according to BHRLC CH configuration information from the IAB donor, wherein the BHRLC CH configuration information is BH RLC CH configuration information between the first IAB node and the source parent node of the first IAB node; a transceiver unit, configured to send first information to a child node of the first IAB node; The first information includes at least one of the following: Indication information of IAB donor change connected to the first IAB node, indication information of RRC re-establishment, identification information of the base station for RRC re-establishment, and identification information of the cell for RRC re-establishment.

34. The device according to claim 33, characterized in that The first information is carried in a control unit MACCE of a media access control layer; or The first information is carried in a backhaul adaptation protocol control packet data unit BAPcontrolPDU.

35. The device according to claim 33 or 34, characterized in that The transceiver unit is further configured to: Receive first indication information from the target IAB donor, where the first indication information is used to indicate a change in an IAB donor to which the first IAB node is connected.

36. The device according to claim 35, characterized in that The first indication information is carried in an RRC re-establishment message; or, The first indication information is carried in an RRC reconfiguration message.

37. The device according to any one of claims 33 to 36, characterized in that The processing unit is further configured to: It is determined that the F1 connection establishment / re-establishment with the IAB donor is complete or the F1 connection has been restored.

38. The device according to any one of claims 33 to 37, characterized in that The transceiver unit is further configured to: Receive Internet Protocol (IP) address information of the target IAB donor from the target IAB donor.

39. The device according to claim 38, characterized in that The IP address information of the target IABdonor is carried in the RRC reconfiguration message.

40. The device according to any one of claims 33 to 39, characterized in that The transceiver unit is specifically used to: Receive first configuration information from the target IAB donor, where the first configuration information includes at least one of the following: The source identifier of the cell of the first IAB node, the target identifier of the cell of the first IAB node, the PLMNID of the cell of the first IAB node, the SSB information of the cell of the first IAB node, or the activation indication information of the cell of the first IAB node.

41. A communication device, characterized in that The device is a subnode of the first access and backhaul integrated IAB node, and the device includes: a transceiver unit, configured to receive first information from the first IAB node, where the first information includes at least one of the following: Indication information of a change in an IAB donor to which the first IAB node is connected, indication information of an RRC re-establishment, identification information of a base station for RRC re-establishment, and identification information of a cell for RRC re-establishment; communication resources of the first IAB node are configured by a target parent node of the first IAB node according to configuration information of a BH RLC CH from the IAB donor, where the configuration information of the BH RLC CH is configuration information of a BH RLCCH between the first IAB node and the source parent node of the first IAB node; A processing unit is used to trigger at least one of the following processes according to the first information: RRC re-establishment, F1 connection establishment or F1 connection re-establishment.

42. The device according to claim 41, characterized in that The first information is carried in a control unit MACCE of a media access control layer; or The first information is carried in a backhaul adaptation protocol control packet data unit BAPcontrolPDU.

43. A communication device, characterized in that include: A processor, the processor being coupled to a memory, the memory being used to store a computer program or instruction, the processor being used to execute the computer program or instruction in the memory, so that the communication device performs the communication method for accessing the integrated backhaul IAB system as described in any one of claims 1 to 9, or the communication device performs the communication method for accessing the integrated backhaul IAB system as described in any one of claims 10 to 11, or the communication device performs the communication method for accessing the integrated backhaul IAB system as described in any one of claims 12 to 19, or the communication device performs the communication method for accessing the integrated backhaul IAB system as described in any one of claims 20 to 21.

44. A chip, characterized in that The chip includes a processor and a communication interface; The communication interface is coupled to the processor, and the processor is used to run a computer program or instruction to implement the communication method for accessing the integrated backhaul IAB system according to any one of claims 1 to 9, or to implement the communication method for accessing the integrated backhaul IAB system according to any one of claims 10 to 11, or to implement the communication method for accessing the integrated backhaul IAB system according to any one of claims 12 to 19, or to implement the communication method for accessing the integrated backhaul IAB system according to any one of claims 20 to 21.

45. A computer-readable storage medium, wherein the storage medium is used to store a computer program or instruction, which, when executed, causes the computer to execute the communication method for accessing an integrated backhaul IAB system as described in any one of claims 1 to 9, or causes the computer to execute the communication method for accessing an integrated backhaul IAB system as described in any one of claims 10 to 11, or causes the computer to execute the communication method for accessing an integrated backhaul IAB system as described in any one of claims 12 to 19, or causes the computer to execute the communication method for accessing an integrated backhaul IAB system as described in any one of claims 20 to 21.

46. ​​A computer program product comprising a computer program or instructions, characterized in that: When the computer program product runs on a computer, the computer is caused to execute the method according to any one of claims 1 to 9, or the computer is caused to execute the method according to any one of claims 10 to 11, or the computer is caused to execute the method according to any one of claims 12 to 19, or the computer is caused to execute the method according to any one of claims 20 to 21.

47. A communication system, characterized in that The communication system comprises the communication device according to any one of claims 22 to 30, the communication device according to any one of claims 31 to 32, the communication device according to any one of claims 33 to 40, and / or the communication device according to any one of claims 41 to 42; or, The communication system includes the communication device according to claim 43.

Images