WO2022082683A1 - 一种用于接入回传一体化iab系统中的通信方法及相关设备 - Google Patents

一种用于接入回传一体化iab系统中的通信方法及相关设备 Download PDF

Info

Publication number
WO2022082683A1
WO2022082683A1 PCT/CN2020/123014 CN2020123014W WO2022082683A1 WO 2022082683 A1 WO2022082683 A1 WO 2022082683A1 CN 2020123014 W CN2020123014 W CN 2020123014W WO 2022082683 A1 WO2022082683 A1 WO 2022082683A1
Authority
WO
WIPO (PCT)
Prior art keywords
iab
node
donor
information
iab node
Prior art date
Application number
PCT/CN2020/123014
Other languages
English (en)
French (fr)
Inventor
刘菁
史玉龙
朱元萍
卓义斌
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN202080106330.2A priority Critical patent/CN116530142A/zh
Priority to PCT/CN2020/123014 priority patent/WO2022082683A1/zh
Priority to EP20958265.9A priority patent/EP4221338A4/en
Publication of WO2022082683A1 publication Critical patent/WO2022082683A1/zh
Priority to US18/304,468 priority patent/US20230262827A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0019—Control or signalling for completing the hand-off for data sessions of end-to-end connection adapted for mobile IP [MIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/36—Modification of an existing route due to handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0072—Transmission or use of information for re-establishing the radio link of resource information of target access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to a communication method and related equipment used in an integrated IAB system for access and backhaul.
  • the 3rd-generation partnership project (3GPP) R15 integrated access and backhaul (IAB) network architecture includes an IAB host node (IABdonor) and an IAB node (IABnode).
  • IABdonor includes IABdonorCU and IABdonorDU.
  • the IABnode includes an IABnode mobile terminal (mobile terminal, MT) functional unit and an IABnodeDU.
  • the IABnodeMT functional unit as a user equipment (userequipment, UE) module, is responsible for the communication with its parent node.
  • the IABnodeDU provides access services for the UE or other IABnodes attached to it.
  • the connection between IABnode and IABdonorCU is F1 connection.
  • the link quality between the two communication nodes may change, for example, a radio link failure (RLF), integrity protection failure, radio resource control (radio resource control) occurs. control, RRC) reconfiguration failure, etc., so that the parent node connected to the IAB node may change, then the IAB node will be triggered to perform handover, that is, the IAB node releases the connection with the source parent node and communicates with the target parent node. A new connection is established between nodes.
  • the source parent node and the target parent node may be the intermediate IAB node on the path between the IAB node and the IAB donor, or may be the IAB donor DU in the IAB donor.
  • Embodiments of the present application provide a communication method and related configuration for an integrated IAB system for access and backhaul, so that after the parent node of the first IAB node is changed from the source parent node to the target parent node, the first IAB
  • the target parent node of the 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.
  • the first 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 an integrated access and backhaul host IAB donor, and can also be applied to component execution of the IAB donor (eg processor, chip or system on chip, etc.).
  • the access and backhaul integrated host IAB donor obtains the configuration information of the radio link control channel BH RLC CH of the backhaul link, and the configuration information of the BH RLC CH is the first access and backhaul integrated IAB node and the configuration information of the BH RLC CH between the 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.
  • 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.
  • the target parent node of the first IAB node can use the configuration information of the BH RLC CH to further determine the first IAB node and the first IAB node. Configuration of the BH RLC CH between the node's target parent node.
  • 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 with the first IAB node, there is no need to send the configuration information of the BH RLC CH to the first IAB node.
  • the first IAB node communicates in the IAB network through the target parent node of the first IAB node, saving the overhead of resource configuration; the target parent node of the first IAB node determines the BH RLC CH from the IAB donor.
  • the configuration information corresponding to the BH RLC CH of the first IAB node may be generated according to the air interface resources of the parent node, or the first IAB node may pass the first IAB node through the first IAB node.
  • the target parent node of an IAB node communicates in the IAB network.
  • 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.
  • the target parent node of the first IAB node may be an intermediate IAB node on the path between the first IAB node and the IAB donor, or may be the IAB donor DU in the IAB donor, here Not limited.
  • 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, a wireless link The configuration information of the control channel RLC or the configuration information of the logical channel.
  • the configuration information of the BH RLC CH can be realized by at least one of the above items, that is, multiple implementations for the IAB donor to obtain and send the configuration information of the BH RLC CH are provided, which improves the achievability of the solution.
  • the IAB donor is a target IAB donor
  • the target parent node is connected with the target IAB donor
  • the source parent node is connected with the source IAB donor
  • the IAB donor connected to the first IAB node can also be changed, wherein 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 As the target IAB donor, the solution can be applied to the scenario where the IAB donor connected to the first IAB node changes, such as the re-establishment scenario of a cross-host CU (Inter-donor-CU).
  • Inter-donor-CU Inter-donor-CU
  • the IAB donor acquiring the configuration information of the BH RLC CH includes: the IAB donor receiving a user equipment UE context acquisition response message from the source IAB donor, and the acquiring UE The context response message includes the configuration information of the BH RLC CH.
  • the IAB donor 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 be the host node connected by the source parent node of the first IAB node.
  • the configuration information of the BH RLC CH is obtained in the obtained user equipment UE context response message sent.
  • a specific implementation method for the IAB donor to obtain the configuration information of the BH RLC CH is provided to improve the achievability of the solution.
  • 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 the first IAB node The connected IAB donor changed.
  • the IAB donor 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 to the first IAB node through the target parent node of the first IAB node.
  • the first indication information for indicating that the IAB donor connected by the first IAB node changes, so that the first IAB node determines that the host node of the first IAB node changes, and subsequently can trigger the establishment of the F1 interface to the target host node/ Re-establish the process to ensure that the first IAB node can communicate with the target IAB donor through the target parent node.
  • the first indication information is carried in an RRC re-establishment message; or, the first indication information is carried in an RRC reconfiguration message.
  • the bearing mode of the first indication information may be an RRC re-establishment message or an RRC reconfiguration message, which provides multiple bearing modes of the first indication information, and improves the practicability of the solution.
  • the IAB donor sends the Internet Protocol IP address information of the IAB donor to the first IAB node through the target parent node.
  • the IAB donor 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 to the first IAB node through the target parent node of the first IAB node.
  • the IP address information of the target IAB donor 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 be connected to the target through the target parent node. IAB donor to communicate.
  • the IP address information of the target IAB donor is carried in the RRC reconfiguration message.
  • the bearing method of the Internet Protocol IP address information of the target IAB donor can be the RRC reconfiguration message, which provides a specific implementation method of the Internet Internet Protocol IP address information of the target IAB donor, which improves the realization of the solution. sex.
  • the method may further include: the IAB donor sends first configuration information to the first IAB node through the target parent node, where the first configuration information includes the following At least one item: the source identifier of the cell of the first IAB node, the target identifier of the cell of the first IAB node, the PLMN ID of the cell of the first IAB node, the SSB information of the cell of the first IAB node, or the first IAB node cell Activation indication information of the cell of the IAB node.
  • the IAB donor 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 to the first IAB node through the target parent node of the first IAB node.
  • the first configuration information enables the first IAB node to update the network configuration of the first IAB node according to the first configuration information, ensuring that the first IAB node can be connected to the target IAB donor through the target parent node to communicate.
  • a second aspect of the embodiments of the present application provides a communication method for an integrated IAB system for access and backhaul.
  • the method can be applied to the target parent node of the first IAB node, and can also be applied to the target of the first IAB node.
  • the component execution of the parent node eg, processor, chip, or system-on-chip, etc.).
  • the method includes: the target parent node of the first access backhaul integrated IAB node receives the configuration information of the radio link control channel BH RLC CH of the backhaul link of the IAB host IAB donor, the BH RLC CH
  • the configuration information is the 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 first IAB node and the target parent node according to the configuration information of the BH RLC CH Configuration of BH RLC CH between nodes.
  • the target parent node of the first IAB node receives the configuration information of the BH RLC CH between the first access backhaul integrated IAB node from the IAB donor and the source parent node of the first IAB node, and according to the The configuration information of the BH RLC CH determines the configuration of the BH RLC CH with the first IAB node.
  • the target parent node of the first IAB node can use the configuration information of the BH RLC CH to further determine the relationship with the first IAB node The configuration of the BH RLC CH.
  • 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 with the first IAB node, there is no need to send the configuration information of the BH RLC CH to the first IAB node.
  • the first IAB node communicates in the IAB network through the target parent node of the first IAB node, saving the overhead of resource configuration; the target parent node of the first IAB node determines the BH RLC CH from the IAB donor.
  • the configuration information corresponding to the BH RLC CH of the first IAB node may be generated according to the air interface resources of the parent node, or the first IAB node may pass the first IAB node through the first IAB node.
  • the target parent node of an IAB node communicates in the IAB network.
  • 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.
  • the target parent node of the first IAB node may be an intermediate IAB node on the path between the first IAB node and the IAB donor, or may be the IAB donorDU in the IAB donor, which is not mentioned here. Do limit.
  • the configuration information of the BH RLC CH may include at least one of the following: an identifier of the BH RLC CH, a logical channel identifier corresponding to the BH RLC CH, a radio link The configuration information of the channel control channel RLC or the configuration information of the logical channel.
  • the configuration information of the BH RLC CH can be realized by at least one of the above items, that is, multiple implementations for the IAB donor to obtain and send the configuration information of the BH RLC CH are provided, which improves the achievability of the solution.
  • a third aspect of the embodiments of the present application provides a communication method used in an integrated access and backhaul IAB system, and the method can be applied to the first integrated IAB node of access and backhaul, and can also be applied to the first IAB node component execution (eg, processor, chip, or system-on-chip, etc.).
  • first IAB node component execution eg, processor, chip, or system-on-chip, etc.
  • the first access and backhaul integrated IAB node determines that the RRC re-establishment between it and the IAB host IAB donor is completed; the first IAB node sends first information to the child nodes of the first IAB node; the first IAB node sends first information to the child node of the first IAB node;
  • the information includes at least one of the following: indication information of the change of the IAB donor 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.
  • the first IAB node determines that the RRC re-establishment 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 first IAB node sends the first IAB node to the first IAB node.
  • the child node sends the first information, 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, ensuring that the first IAB node 's child nodes work fine.
  • the first IAB node is the parent node of the child nodes of the first IAB node, wherein the child nodes of the first IAB node may be an IAB node or a terminal device (such as a UE ), which is not limited here.
  • the first information is carried in the control unit MAC CE of the medium access control layer; or, the first information is carried in the backhaul adaptation protocol control packet In the data unit BAP control PDU.
  • the bearing mode of the first information can be the control unit MAC CE or BAP control PDU of the media access control layer, which provides multiple bearing modes of the first information and improves the practicability of the solution.
  • the method 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 that the IAB donor connected by the first IAB node is changed.
  • the first IAB node before the first IAB node sends the first information to the child nodes of the first IAB node, the first IAB node can also receive the change of the IAB donor sent from the target IAB donor and used to indicate that the first IAB node is connected The first indication information, so that the first IAB node determines that the host node to which the first IAB node and the child node are connected has changed.
  • the child node of the first IAB node may be further notified, so that the child node of the first IAB node triggers RRC re-establishment and/or establishment/re-establishment of the F1 connection, so as to ensure that the child node of the first IAB node can pass the first IAB node.
  • the IAB node connects to the target IAB donor for communication.
  • the first IAB node may send the first information to the child node according to the first indication information.
  • the first indication information is carried in an RRC re-establishment message; or, the first indication information is carried in an RRC reconfiguration message.
  • the bearing mode of the first indication information may be an RRC re-establishment message or an RRC reconfiguration message, which provides multiple bearing modes of the first indication information, and improves the practicability of the solution.
  • the method may further include: the first IAB node determines The F1 connection establishment/re-establishment with this IAB donor is complete or the F1 connection has been restored.
  • the first IAB node sends the first information to the child node of the first IAB node after determining that the establishment/re-establishment of the F1 connection with the IAB donor is completed or the F1 connection has been restored, so that the child node
  • the RRC re-establishment and/or the establishment/re-establishment of the F1 connection may be triggered according to the first information through the established/re-established F1 connection or the restored F1 connection between the first IAB node and the IAB donor.
  • the method may further include: the first IAB node receiving the IP address information of the IAB donor from the IAB donor.
  • the first IAB node can also receive the IP address information of the target IAB donor sent from the target IAB donor through the target parent node of the first IAB node, so that the first IAB node can send the information indicated by the IP address information to the first IAB node.
  • the host node triggers the establishment/re-establishment process of the F1 interface to ensure that the first IAB node can work normally after being connected to the target IAB donor through the target parent node.
  • the IP address information of the target IAB donor is carried in the RRC reconfiguration message.
  • the bearing mode of the IP address information of the target IAB donor can be the RRC reconfiguration message, which provides a specific implementation mode of the IP address information of the target IAB donor, and improves the achievability of the solution.
  • the method may further include: the first IAB node Receive first configuration information from the IAB donor, where the first configuration information includes at least one of the following: the source identity of the cell of the first IAB node, the target identity of the cell of the first IAB node, the The PLMN ID of the cell, the SSB information of the cell of the first IAB node, or the activation indication information of the cell of the first IAB node.
  • the first IAB node can also receive the first configuration information sent from the target IAB donor through the target parent node of the first IAB node, so that the first IAB node updates the first IAB node according to the first configuration information
  • the configuration ensures that the first IAB node can communicate with the target IAB donor by connecting to the target parent node.
  • a fourth aspect of the embodiments of the present application provides a communication method in an integrated IAB system for access and backhaul.
  • the method can be applied to a child node of the first IAB node, and can also be applied to a child node of the first IAB node.
  • component execution eg, processor, chip, or system-on-chip, etc.
  • the child node of the first access and backhaul integrated IAB node receives first information from the first IAB node, where the first information includes at least one of the following: the IAB donor connected to the first IAB node is changed
  • the indication information, the indication information of RRC re-establishment, the identification information of the base station of RRC re-establishment, the identification information of the cell of RRC re-establishment; the sub-node triggers at least one of the following procedures according to the first information: RRC re-establishment, F1 connection Establish or F1 connection re-establishment.
  • the child node of the first IAB node receives from the parent node.
  • the node is the first information sent by 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, ensuring that The child nodes of the first IAB node can communicate with the target IAB donor by connecting to the first IAB node.
  • the first IAB node is the parent node of the child nodes of the first IAB node, wherein the child nodes of the first IAB node may be an IAB node or a terminal device (such as a UE ), which is not limited here.
  • the first information is carried in the control unit MAC CE of the medium access control layer; or, the first information is carried in the backhaul adaptation protocol control packet In the data unit BAP control PDU.
  • the bearing mode of the first information can be the control unit MAC CE or BAP control PDU of the media access control layer, which provides multiple bearing modes of the first information and improves the practicability of the solution.
  • a fifth aspect of the embodiments of the present application provides a communication device, the device is an integrated host IAB donor for access and backhaul, and the device includes:
  • the processing unit is used to obtain the configuration information of the radio link control channel BH RLC CH of the backhaul link, where the configuration information of the BH RLC CH is the source parent of the first access backhaul integrated IAB node and the first IAB node Configuration information of BH RLC CH between nodes;
  • a transceiver unit configured to send the configuration information of the BHRLC CH to the target parent node of the first IAB node.
  • the configuration information of the BH RLC CH includes at least one of the following:
  • the IAB donor is a target IAB donor
  • the target parent node is connected with the target IAB donor
  • the source parent node is connected with the source IAB donor.
  • the processing unit is specifically configured to receive a user equipment UE context acquisition response message from the source IAB donor, where the UE context acquisition response message includes configuration information of the BH RLC CH.
  • the transceiver unit is further configured to:
  • the first indication information is carried in the RRC re-establishment message; or,
  • the first indication information is carried in the RRC reconfiguration message.
  • the transceiver unit is further configured to:
  • the IP address information of the target IAB donor is carried in the RRC reconfiguration message.
  • the transceiver unit is further configured to:
  • 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 component modules of the communication device may also be used to perform the steps performed in each possible implementation manner of the first aspect.
  • the first aspect which will not be repeated here.
  • a sixth aspect of an embodiment of the present application provides a communication device, where the device is a target parent node of the first IAB node, and the device includes:
  • the transceiver unit is used to receive the configuration information of the radio link control channel BH RLC CH of the backhaul link from the access backhaul integrated host IAB donor, where the configuration information of the BH RLC CH is the first access backhaul integration Configuration information of the BH RLC CH between the IAB node and the source parent node of the first IAB node;
  • a processing unit configured to determine the configuration of the BH RLC CH with the first IAB node according to the configuration information of the BH RLC CH.
  • the configuration information of the BH RLC CH includes at least one of the following:
  • the component modules of the communication device may also be used to perform the steps performed in each possible implementation manner of the second aspect.
  • the second aspect which will not be repeated here.
  • a seventh aspect of an embodiment of the present application provides a communication device, where the device is a first access and backhaul integrated IAB node, and the device includes:
  • the processing unit is used to determine that the RRC re-establishment is completed with the target access backhaul integrated host IAB donor;
  • transceiver unit configured to send the first information to the child nodes of the first IAB node
  • the first information includes at least one of the following:
  • the indication information of the change of the IAB donor connected to the first IAB node the indication information of the RRC re-establishment, the identification information of the base station of the RRC re-establishment, and the identification information of the cell of the RRC re-establishment.
  • the first information is carried in the control unit MAC CE of the medium access control layer; or,
  • the first information is carried in the backhaul adaptation protocol control packet data unit BAP control PDU.
  • the transceiver unit is further used for:
  • the first indication information is carried in the RRC re-establishment message; or,
  • the first indication information is carried in the RRC reconfiguration message.
  • the processing unit is further configured to: determine that the establishment/re-establishment of the F1 connection with the IAB donor is completed or the F1 connection has been restored.
  • the transceiver unit is further used for:
  • the IP address information of the target IAB donor is carried in the RRC reconfiguration message.
  • the transceiver unit is specifically used for:
  • the component modules of the communication device may also be used to perform the steps performed in each possible implementation manner of the third aspect.
  • the third aspect please refer to the third aspect, which will not be repeated here.
  • An eighth aspect of an embodiment of the present application provides a communication device, where the device is a sub-node of a first 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:
  • a processing unit configured to trigger at least one of the following procedures according to the first information: RRC re-establishment, F1 connection establishment or F1 connection re-establishment.
  • the first information is carried in the control unit MAC CE of the medium access control layer; or,
  • the first information is carried in the backhaul adaptation protocol control packet data unit BAP control PDU.
  • the component modules of the communication device may also be used to perform the steps performed in each possible implementation manner of the fourth aspect.
  • the fourth aspect which will not be repeated here.
  • a ninth aspect of an embodiment of the present application provides a communication device, wherein the communication device includes a processor, and the processor is coupled to a memory, where the memory is used for storing computer programs or instructions, and the processor is used for executing the computer in the memory A program or instruction to make the method described in the foregoing first aspect or any possible implementation manner of the first aspect to be performed.
  • a tenth aspect of an embodiment of the present application provides a communication device, wherein the communication device includes a processor, and the processor is coupled to a memory, where the memory is used for storing computer programs or instructions, and the processor is used for executing the computer in the memory A program or instruction to make the method described in the second aspect or any one possible implementation manner of the second aspect to be performed.
  • An eleventh aspect of an embodiment of the present application provides a communication device, wherein the communication device includes a processor, and the processor is coupled to a memory, and the memory is used for storing computer programs or instructions, and the processor is used for executing the A computer program or instruction to make the method described in the third aspect or any of the possible implementations of the third aspect to be performed.
  • a twelfth aspect of an embodiment of the present application provides a communication device, wherein the communication device includes a processor, the processor is coupled to a memory, the memory is used for storing computer programs or instructions, and the processor is used for executing the A computer program or instruction to make the method described in the foregoing fourth aspect or any one of the possible implementations of the fourth aspect to be performed.
  • a thirteenth aspect of an embodiment of the present application provides a computer-readable storage medium that stores one or more computer-executable instructions.
  • the processor executes the first aspect or any of the first aspects.
  • a possible implementation, or the processor executes the method described in the second aspect or any of the possible implementations of the second aspect, or the processor executes the third aspect or any one of the third aspects.
  • the method described in the possible implementation manner, or the processor executes the method described in the fourth aspect or any of the possible implementation manners of the fourth aspect.
  • a fourteenth aspect of the embodiments of the present application provides a computer program product (or computer program) that stores one or more computers.
  • the processor executes the first aspect or the first aspect above.
  • Any possible implementation manner of the aspect, or the processor executes the above-mentioned second aspect or any one possible implementation manner of the second aspect, or the processor executes the above-mentioned third aspect or any one possible implementation of the third aspect or the processor executes the fourth aspect or any of the possible implementations of the fourth aspect.
  • a fifteenth aspect of an embodiment of the present application provides a chip system, where the chip system includes a processor, configured to support a communication apparatus to implement the first aspect or any possible implementation manner of the first aspect, or to support a communication apparatus to implement the foregoing
  • the functions involved in the fourth aspect or any possible implementation manner of the fourth aspect are implemented.
  • the chip system may further include a memory for storing necessary program instructions and data of the access network device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • a sixteenth aspect of an embodiment of the present application provides a communication system, where the communication system includes one or more communication devices shown in the fifth to eighth aspects above, or the communication system includes the above ninth to tenth aspects One or more communication devices shown in the second aspect.
  • 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 information to the target of the first IAB node.
  • the parent node sends the configuration information of the BH RLC CH.
  • the target parent node of the first IAB node can use the configuration information of the BH RLC CH to further determine the relationship with the first IAB node The configuration of the BH RLC CH.
  • 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 with the first IAB node, there is no need to send the configuration information of the BH RLC CH to the first IAB node.
  • the first IAB node communicates in the IAB network through the target parent node of the first IAB node, saving the overhead of resource configuration; the target parent node of the first IAB node determines the BH RLC CH from the IAB donor.
  • the configuration information corresponding to the BH RLC CH of the first IAB node may be generated according to the air interface resources of the parent node, or the first IAB node may pass the first IAB node through the first IAB node.
  • the target parent node of an IAB node communicates in the IAB network.
  • 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.
  • Fig. 2 is a schematic diagram of a control plane protocol stack
  • Fig. 3 is a schematic diagram of the user plane protocol stack
  • Fig. 4 is a schematic diagram of two data return scenarios in the IAB system
  • Fig. 5 is another schematic diagram of the control plane protocol stack
  • Fig. 6 is another schematic diagram of user plane protocol stack
  • FIG. 7 is a schematic diagram of an implementation of establishing an F1 scene
  • Fig. 8 is a schematic diagram of Intra-donor-CU switching scene
  • Fig. 9 is a schematic diagram of Intra-donor-CU re-establishment process
  • 10-1 is a schematic diagram of an Inter-donor-CU switching scenario in an embodiment of the present application.
  • 10-2 is another schematic diagram of an Inter-donor-CU switching scenario in an embodiment of the present application.
  • 10-3 is another schematic diagram of an Inter-donor-CU switching scenario in an embodiment of the present application.
  • 10-4 is a schematic diagram of an Inter-donor-CU switching scenario in an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a communication method in an integrated IAB system for access and backhaul in an embodiment of the present application
  • FIG. 12 is another schematic diagram of a communication method in an integrated IAB system for access and backhaul in an embodiment of the present application
  • FIG. 13 is another schematic diagram of a communication method in an integrated IAB system for access and backhaul in an embodiment of the present application
  • FIG. 14 is another schematic diagram of a communication method in an integrated IAB system for access and backhaul in an embodiment of the present application
  • FIG. 15 is another schematic diagram of a communication method in an integrated IAB system for access and backhaul in an embodiment of the present application
  • 16 is a schematic diagram of a communication device in an embodiment of the present application.
  • 17 is another schematic diagram of a communication device in an embodiment of the present application.
  • FIG. 18 is a schematic diagram of the Inter-donor in the embodiment of the present application.
  • 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 after 5G communication systems, such as NR, device to device (device to device, D2D) communication systems, etc.
  • NB-IoT narrow band-internet of things
  • WLAN wireless local access network
  • LTE long term evolution
  • 5G mobile communication systems such as NR, device to device (device to device, D2D) communication systems, etc.
  • Network equipment including but not limited to evolved node B (evolved node base, eNB), radio network controller (radio network controller, RNC), node B (node B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (home evolved NodeB, or home node B, HNB), baseband unit (baseband Unit, BBU), evolved (evolved LTE, eLTE) ) base station, NR base station (next generation node B, gNB), etc.
  • evolved node B evolved node base, eNB
  • RNC radio network controller
  • node B node B
  • base station controller base station controller
  • BSC base transceiver station
  • BTS home base station
  • home evolved NodeB home evolved NodeB, or home node B, HNB
  • baseband unit baseband Unit
  • Terminal equipment including but not limited to user equipment (UE), mobile station, access terminal, subscriber unit, subscriber station, mobile station, remote station, remote terminal, mobile equipment, terminal, wireless communication equipment, user Proxy, station (ST) in wireless local access network (WLAN), cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) Stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices, other processing devices connected to wireless modems, in-vehicle devices, wearable devices, mobile stations in future 5G networks, and future evolutions Any one of the terminal equipment in the public land mobile network (PLMN) network.
  • PLMN public land mobile network
  • a wireless backhaul node (also referred to as an IAB node): used to provide a wireless backhaul service for a node (eg, a terminal) that wirelessly accesses the wireless backhaul node.
  • the wireless backhaul service refers to a data and/or signaling backhaul service provided through a wireless backhaul link.
  • the wireless backhaul node may be an IAB node, or a relay node (relay), and the solution of this application is not limited, and it may be one of the above-mentioned base stations or terminal devices with a forwarding function, or a kind of Standalone device form.
  • the wireless backhaul nodes can provide wireless access services for terminals, and connect to the donor base station (donor gNB) through a wireless backhaul link to transmit the user's business data.
  • donor base station donor gNB
  • the wireless backhaul node may also be equipment such as customer premises equipment (customer premises equipment, CPE for short), residential gateway (residential gateway, RG for short).
  • CPE customer premises equipment
  • residential gateway residential gateway
  • RG residential gateway
  • the method provided by the embodiment of the present application may also be applied to a scenario of home access (home access).
  • Link A path between two adjacent nodes in a path.
  • Access link a 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 donor node, or between a terminal device and a donor DU.
  • the access link includes a wireless link used by an IAB node to communicate with its parent node when it acts as a common terminal device.
  • an IAB node acts as a common terminal device, it does not provide backhaul services for any child nodes.
  • Access links include uplink access links and downlink access links.
  • the access link of the terminal device is a wireless link, so the access link may also be referred to as a wireless access link.
  • Backhaul link the link between the IAB node and the parent node when the IAB node acts as a wireless backhaul node, or the link between the IAB node and the parent node.
  • Backhaul links include uplink backhaul links and downlink backhaul links.
  • the backhaul link between the IAB node and the parent node is a wireless link, so the backhaul link may also be referred to as a wireless backhaul link.
  • Each IAB node regards the adjacent nodes that provide it with wireless access service and/or wireless backhaul service as a parent node. Accordingly, each IAB node can be regarded as a child node of its parent node.
  • a child node may also be referred to as a lower-level node or a downstream node
  • a parent node may also be referred to as an upper-level node or an upstream node.
  • Access IAB node refers to an IAB node accessed by a terminal, or an IAB node that provides access services for terminal equipment.
  • Intermediate IAB node refers to an IAB node that provides wireless backhaul services for other IAB nodes (eg, an access IAB node or other intermediate IAB nodes), or an IAB node on the path between the access IAB node and the IAB host.
  • IAB nodes eg, an access IAB node or other intermediate IAB nodes
  • the F1 interface refers to the logical interface between the DU part of the IAB node and the host node (or donor-CU).
  • the F1 interface can also be called the F1* interface, which supports the user plane and the control plane.
  • the protocol layer of the F1 interface refers to the communication protocol layer on the F1 interface.
  • the user plane protocol layer of the F1 interface may include one or more of an IP layer, a UDP layer, and a GTP-U layer.
  • control plane protocol layer of the F1 interface may include one or more of an IP layer, an SCTP layer, and an F1AP layer.
  • the gNB can adopt a distributed unit (CU)-distributed unit (DU) separation architecture, namely: the next generation wireless A gNB in an access network (next generation radio access network, NG RAN) consists of one gNB-CU and one or more gNB-DUs, where one gNB-DU can only be connected to one gNB-CU, and the gNB -The CU and gNB-DU are connected through the F1 interface, and the gNB-CU and 5GC (5G core network) are connected through the next generation (NG) interface, as shown in Figure 1.
  • CU distributed unit
  • the UE can access the gNB-CU through the gNB-DU shown in FIG. 1, that is, the physical (PHY) layer/medium access control (medium access control) equivalent to the UE , MAC) layer/radio link control (radio link control, RLC) layer function is located on the gNB-DU, and the packet data convergence protocol (packet data convergence protocol, PDCP) layer/service data adaptation protocol (Service Data) equivalent to the UE Adaptation Protocol, SDAP) layer/radio resource control (radio resource control, RRC) layer functions are located on the gNB-CU.
  • PHY physical
  • MAC layer/radio link control
  • RLC radio link control
  • RLC radio link control
  • packet data convergence protocol packet data convergence protocol
  • SDAP service data adaptation protocol
  • RRC radio resource control
  • the gNB-DU encapsulates the RRC message generated by the UE in the F1AP message of the F1 interface and sends it to the gNB-CU; in the DL direction, the gNB-DU
  • the CU encapsulates the RRC message in the F1 interface application protocol (F1 application protocol, F1AP) message and sends it to the gNB-DU.
  • the gNB-DU extracts the RRC message from the F1AP message and maps it to the signaling radio bearer corresponding to the Uu interface. bearer, SRB) (SRB0/SRB1/SRB2) and sent to the UE.
  • the gNB-DU maps the UE data packets received from the Uu interface data radio bearer (DRB) to the corresponding general packet radio service tunneling protocol (general packet radio service tunneling protocol, GTP) tunnel is sent to gNB-CU; in downlink (download, DL) direction, gNB-CU maps UE data packets to the corresponding GTP tunnel and sends to gNB-DU, gNB-DU
  • DRB Uu interface data radio bearer
  • GTP general packet radio service tunneling protocol
  • IAB nodes two IAB nodes
  • IAB donors IAB host nodes, or host IAB nodes
  • types of nodes can be gNB.
  • the host node may be an access network element with a complete base station function, or may be a form in which a centralized unit (CU) and a distributed unit (DU) are separated, that is, the host A node consists of a centralized unit of the donor base station and a distributed unit of the donor base station.
  • the centralized unit of the host node is also referred to as an IAB donor CU (also referred to as a donor CU, or directly referred to as a CU).
  • the distributed unit of the host node is also called IAB donor DU (or called donor DU).
  • the donor CU may also be separated from a control plane (control plane, CP) (referred to as CU-CP in this embodiment of the present application) and a user plane (user plane, UP) (referred to as CU-UP in this embodiment of the present application) form.
  • CP control plane
  • UP user plane
  • a CU may consist of one CU-CP and one or more CU-UPs.
  • IAB network adopts the CU-DU separation architecture, that is, the IAB donor is converted from the IAB donor-CU (referred to as the donor-CU) and IAB donor-DU (referred to as donor-DU) two parts
  • IAB node consists of IAB node-MT (referred to as IAB-MT) and IAB node-DU (referred to as IAB-DU) two parts.
  • IAB node-MT can also be called IAB node-UE (abbreviated as IAB-UE).
  • the function of donor-DU is similar to that of gNB-DU
  • the function of donor-CU is similar to that of gNB-CU.
  • the IAB-DU is similar in function to the gNB-DU, and is used to provide access services for its sub-nodes, wherein the sub-nodes of the IAB-DU may be UEs or other IAB nodes.
  • the IAB-MT has the function of the UE, and is used to provide data backhaul for the sub-nodes of the co-sited IAB-DU (that is, the IAB-DU and the IAB-MT belong to the same IAB node).
  • the IAB node can be divided into an access IAB node and an intermediate IAB node, that is, the IAB node accessed by the UE is called the access IAB node, and the IAB node on the path between the access IAB node and the IAB donor is called the intermediate IAB node. IAB node.
  • IAB node2 when the UE accesses IAB node2, then the IAB node2 is called the access IAB node of the UE (or the parent node of the UE), the UE is called the child node of the IAB node2, and the link between the UE and the IAB node2 is called for the access link.
  • IAB node1 is called the intermediate IAB node
  • the parent node of IAB node1 is IAB donor (the child node of IAB donor is IAB node1)
  • 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 called backhaul links.
  • the PHY layer, MAC layer and RLC layer equivalent to the UE are located on the access IAB node (ie: IAB2-DU), and the PDCP layer, SDAP layer and RRC layer equivalent to the UE are located on the donor-CU.
  • the IAB nodes all adopt the architecture of L2 data forwarding, and the specific user plane protocol stack and control plane protocol stack are shown in Figure 5 and Figure 6 respectively.
  • an F1 interface is established between the access IAB node (ie: IAB node2-DU) and IAB donor (ie: IAB donor-CU). .
  • IAB node2-DU access IAB node
  • IAB donor-CU IAB donor-CU
  • the F1-C interface is established between the IAB node2-DU and the donor CU-CP.
  • the RRC message of the UE is encapsulated and transmitted in the F1AP message of the F1-C interface.
  • the F1-U interface is established between the IAB node2-DU and the donor CU-UP, And establish a GTP tunnel of each UE bearer (per UE bearer) on the F1-U interface. That is to say, each UE DRB established on the interface between the UE and the IAB node2-DU corresponds to a separate GTP tunnel on the interface between the IAB2-DU and the donor CU-UP.
  • each protocol layer is: a packet data convergence protocol (PDCP) layer, a general packet radio service tunneling protocol user plane (general packet radio service tunneling protocol user plane, GTP-U) layer, user datagram protocol (user datagram protocol, UDP) layer, network interconnection protocol (internet protocol, IP) layer, L2 layer (layer 2), L1 layer (layer 1) , radio link control (radio link control, RLC) layer, medium access control (medium access control, MAC) layer, physical (physical, PHY) layer, radio resource control (radio resource control, RRC) layer, F1 application protocol (F1 application protocol, F1AP) layer, stream control transmission protocol (stream control transmission protocol, SCTP) layer.
  • PDCP packet data convergence protocol
  • GTP-U general packet radio service tunneling protocol user plane
  • user datagram protocol user datagram protocol
  • IP network interconnection protocol
  • L2 layer layer 2
  • L1 layer layer 1
  • radio link control radio link control
  • RLC medium access control
  • MAC medium access control
  • RRC radio resource
  • the L2 layer is the link layer.
  • the L2 layer may be the data link layer in the Open Systems Interconnection (OSI) reference model.
  • the L1 layer may be the physical layer.
  • the L1 layer may be the physical layer in the OSI reference model.
  • Radio bearers include data radio bearers (DRB) and signaling radio bearers (signaling radio bearers).
  • RRB data radio bearers
  • SRB signaling radio bearers
  • an RB can be considered as a logical channel for data transmission between the UE and the donor node.
  • each protocol layer is configured with a corresponding protocol layer entity, such as a PDCP entity, an RLC entity, and a MAC entity.
  • a protocol layer entity such as a PDCP entity, an RLC entity, and a MAC entity.
  • the data packets (such as IP data packets) of the UE are processed correspondingly at the PDCP layer, they are sent to the access backhaul node (such as the IAB node2 shown in Figure 4 through the RLC layer, the MAC layer and the PHY layer in turn) ) of the PHY layer.
  • the access backhaul node such as the IAB node2 shown in Figure 4 through the RLC layer, the MAC layer and the PHY layer in turn
  • an IAB node may contain a DU part and an MT part.
  • the MT part of the IAB node performs data forwarding on the backhaul link without requiring a complete protocol stack of the terminal device on the wireless access link.
  • the protocol stack of the communication link between it and the parent node is the same as the protocol stack of the wireless access link between the UE and the access IAB node, which is the same as the host CU.
  • the protocol stack between the UE and the host CU is the same as that between the UE and the host CU.
  • an IAB-DU can only be connected to one IAB donor-CU to establish an F1 connection. Take the scenario where the IAB node is directly connected to the IAB donor as an example, as shown in Figure 7 below, including the following steps.
  • Step 1 After the IAB-MT accesses the network through the IAB donor (ie: initial access), it can obtain the configuration of the IAB-DU from the operations, administration and maintenance (OAM) server through the connected IAB donor Information, including at least one of the following information: IAB-DU identifier (IAB-DU id, IAB-DU name), IAB-DU cell information (physical cell identifier (PCI) of the IAB-DU cell), cell cell identity, cell synchronization signal/physical broadcast channel block (synchronization signal/physical broadcast channel block, SS/PBCH block or SSB) information), peer network interconnection protocol of F1 interface of IAB-DU (internet protocol, IP) address (IP address of the IAB donor-CU).
  • IAB-DU id IAB-DU name
  • IAB-DU cell information physical cell identifier (PCI) of the IAB-DU cell
  • PCI cell identifier
  • cell identity cell identity
  • cell synchronization signal/physical broadcast channel block synchronization signal/physical broadcast channel block
  • the IAB-DU can also obtain the local IP address of the F1 interface of the IAB-DU through OAM, or the IAB-DU can request the connected IAB donor to obtain the local IP address of the F1 interface of the IAB-DU through the IAB-MT. .
  • Step 2 The IAB-DU uses the obtained IP address, and the IAB-DU establishes a TNLA association with the IAB donor-CU.
  • Step 3 The IAB-DU triggers the F1 configuration request (F1 Setup Request) message to the IAB donor-CU through the established TNLA association, and reports the configuration information it obtained from the OAM to the IAB donor-CU, so as to establish the F1 with the IAB donor-CU connect.
  • F1 configuration request F1 Setup Request
  • Step 4 The IAB donor-CU sends an F1 Configuration Response (F1 Setup Response) message to the IAB-DU to activate the designated IAB-DU cell so as to start the IAB-DU function, for example, the activated IAB-DU cell starts to perform system broadcast.
  • F1 Configuration Response F1 Setup Response
  • 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.
  • the IAB-DU triggers the gNB-DU configuration update (Configuration Update) process to the IAB donor-CU through the newly created TNLA association, that is, in step 6a, the IAB-DU sends the gNB-DU Configuration Update to the IAB donor-CU, and step 6bIAB
  • the donor-CU sends a gNB-DU Configuration Update response (Acknowledge) to the IAB-DU to notify the IAB donor-CU to update the TNLA association.
  • the old TNLA association between the IAB-DU and the IAB donor-CU can also be deleted through this process.
  • the IAB node includes two parts: IAB-MT and IAB-DU.
  • an IAB node that detects a radio link failure (RLF) or a link that detects a radio link failure may be detected.
  • the IAB nodes that RLF and attempt to recover are collectively referred to as recovery IAB nodes (recover IAB nodes).
  • the restoration of the IAB-MT part of the IAB node is referred to as restoration of the IAB-MT, and the restoration of the IAB-DU part of the IAB node is referred to as restoration of the IAB-DU.
  • the IAB donor-CU remains unchanged, and the F1 connection between the restored IAB-DU and the IAB donor-CU remains unchanged.
  • the IP address of the restored IAB-DU is allocated by the IAB donor-DU or IAB donor-CU, that is, the IP address of the restored 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 is changed, the IP address change of the IAB-DU is restored.
  • the source path refers to the transmission path between the source parent node and the source IAB donor-DU
  • the initial Path includes the source parent node (Initial ParrentIAB- node), the intermediate node in the source path (Intermediate hopIAB-node on the initial path), the source IAB-donor-DU (Initial IAB-donor-DU);
  • the target path/recovery path refers to the target parent node and The transmission path between the target IAB donor-DU, where the Recovery Path includes the target parent node (New ParrentIAB-node), the intermediate node in the target path (Intermediate hopIAB-node on the New path), the target IAB-donor-DU (New IAB-donor
  • the IAN-donor-CU can exchange uplink user data (Uplink user data) and downlink user data (Downlink user data) with the UE through the source path.
  • Uplink user data Uplink user data
  • Downlink user data Downlink user data
  • Step 1 Recovery IAB-MT detects the occurrence of BH RLF on the source path, that is, Determination of BH RLF on initial path on the original path.
  • Step 2 The recovery IAB-MT triggers the RRC to re-establish to the new parent node to recover the link, that is, to perform RRC reconstruction on the target IAB-donor-DU (RRC Re-establishment at recovery parent IAB-node DU).
  • the IAB-donor-CU can provide a new TNL address to the restored IAB-MT through an RRC message.
  • the IAB-donor-CU can also provide the restored IAB-MT with a default UL configuration through an RRC reconfiguration message, including: Configure the default BH RLC channel for UL F1-C/non-F1 service transmission on the target path, and the default backhaul adaptation protocol routing ID (backhaul adaptation protocol routing ID, BAP routing ID), etc.
  • RRC reconfiguration message including: Configure the default BH RLC channel for UL F1-C/non-F1 service transmission on the target path, and the default backhaul adaptation protocol routing ID (backhaul adaptation protocol routing ID, BAP routing ID), etc.
  • Step 3 The remaining part of the process follows steps 11 to 15 in the intra-CU switching process (Same as steps 11-15 of intra-CU topology adaptation procedure).
  • the implementation process of steps 11 to 15 may include the following steps.
  • Step 11 The IAB-donor-CU configures the corresponding BH RLC channel and BAP routing configuration for the target path of the restoration IAB-MT, and configures the DL bearer mapping on the target IAB donor-DU for the restoration of the IAB-MT.
  • Step 12 The F1-C connection update uses the new IP address of the restored IAB-DU.
  • the IAB-donor-CU updates the UL BH information associated with each GTP tunnel to the restored IAB-DU, that is, all F1-U tunnel updates use the new IP address of the restored IAB-DU.
  • Step 13 The IAB-donor-CU sends a UE Context Release Command (UE Context Release Command) message to the source parent node that restores the IAB-MT.
  • UE Context Release Command UE Context Release Command
  • Step 14 The source parent node of the restored IAB-MT releases the context of the restored IAB-MT, and sends a UE context release complete (UE Context Release Complete) message to the IAB-donor-CU as a response.
  • UE context release complete UE Context Release Complete
  • Step 15 The IAB-donor-CU releases and restores the BH RLC channel and backhaul adaptation protocol (BAP) routing configuration information on the source path between the source parent node of the IAB-MT and the source IAB donor-DU.
  • BAP backhaul adaptation protocol
  • the parent node connected to the restored IAB node will change, that is, from IAB donor-DU1 to IAB donor-DU2.
  • the link quality between the two communication nodes will change in the actual communication process, such as handover failure, radio link failure RLF, integrity protection failure, RRC reconfiguration failure, etc., it may cause IAB
  • the parent node to which the node is connected changes, that is, the IAB node releases the connection with the source parent node of the first IAB node, and establishes a new connection with the target parent node.
  • the source parent node and the target parent node may be an intermediate IAB node between the IAB node and the IAB donor, or may be an IAB donor DU in the IAB donor.
  • the RRC re-establishment scenario of the Inter-donor-CU is also a typical scenario.
  • the following describes the RRC re-establishment scenario of the Inter-donor-CU in the embodiment of the present application by way of illustrations.
  • FIG. 10-1 for an example of an RRC re-establishment scenario for Inter-donor-CU.
  • FIG. 10-2 for another example of an RRC re-establishment scenario for Inter-donor-CU.
  • the scenario shown in Figure 10-1 is further extended, that is, there is at least one other IAB node between the restored IAB node and the IAB donor-DU.
  • IAB node1 and IAB node2 restore the IAB node and the source IAB donor-DU (as shown in Figure 10- 2's IAB donor-DU1) exists between other IAB nodes (that can be called intermediate IAB nodes), IAB node3 and IAB node4 are the recovery IAB node and the target IAB donor-DU (IAB donor-DU2 in Figure 10-2). ) between other IAB nodes (that is, called intermediate IAB nodes).
  • case 1 that is, trigger at least one of the following processes: before the RRC re-establishment, F1 connection establishment or F1 connection re-establishment process, restore the IAB-MT to directly connect to the source IAB donor-DU; trigger at least one of the following processes : After the RRC re-establishment, F1 connection establishment or F1 connection re-establishment process, restore the IAB-MT to connect to the target IAB donor-DU through at least one other IAB node.
  • case 2 that is, triggering at least one of the following processes: before the RRC re-establishment, F1 connection establishment or F1 connection re-establishment process, restore the IAB-MT to connect to the source IAB donor-DU through at least one other IAB node; trigger At least one of the following procedures: after RRC re-establishment, F1 connection establishment or F1 connection re-establishment procedure, restore the IAB-MT to directly connect to the target IAB donor-DU.
  • the child node of the restored IAB node may be the UE, or may be other IAB nodes.
  • the path between the restored IAB-MT and the source IAB-donor CU IAB donor-CU1 in the figure
  • the restored IAB-MT and the target IAB donor-CU The path between the IAB donor-CU2 (as shown in the figure) is called the target path or the recovery path (target path).
  • the IAB donor-CU will change, resulting in a change in the F1 connection for restoring the IAB-DU (currently only one DU is supported to connect to one CU to establish an F1 connection), namely: Trigger at least one of the following processes: before the RRC re-establishment, F1 connection establishment or F1 connection re-establishment process, restore the F1 connection between the IAB-DU and the source IAB donor-CU; trigger at least one of the following processes: RRC re-establishment, F1 After the connection is established or the F1 connection is re-established, restoring the IAB-DU needs to establish/re-establish the F1 connection with the target IAB donor-CU, and release the F1 connection with the source IAB donor-CU.
  • restoring the descendant nodes of the IAB node also needs to establish/re-establish the F1 connection with the target IAB donor-CU, and the current IAB node does not support the process of replacing the F1 connection.
  • the IAB node will trigger the RRC re-establishment process after detecting the RLF on the link with the source parent node. However, since the link quality between the IAB node and its child nodes is still very good, the child nodes will not be able to. Triggered the RRC re-establishment process and did not work properly. However, the current IAB node does not support the process of replacing the F1 connection. Therefore, how to support the replacement of the F1 connection in the Inter-donor-CU scenario and how to notify its sub-nodes to trigger the RRC re-establishment process is also an urgent technical problem to be solved.
  • an embodiment of the present application provides a communication method used in the integrated IAB system for access and backhaul, please refer to FIG. 11 , the communication method for the integrated IAB system for access and backhaul includes the following step.
  • the IAB donor obtains the configuration information of the BH RLC CH.
  • 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 access and backhaul integrated IAB node and the source parent node of the first IAB node.
  • the configuration information of the BH RLC CH obtained by the IAB donor in step S101 may include at least one of the following: an identifier of the BH RLC CH, a logical channel identifier corresponding to the BH RLC CH, a radio link control channel RLC Configuration information or configuration information of a logical channel.
  • 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 be due to various Different scenarios lead to changes.
  • the parent node connected to the restored IAB node ie, the first IAB node
  • the parent node connected to the restored IAB node will be changed, that is, changed from IAB donor-DU1 to IAB donor-DU2.
  • the link quality between the two communication nodes will change in the actual communication process, such as handover failure, radio link failure RLF, integrity protection failure, RRC reconfiguration failure, etc., it may cause IAB
  • the parent node to which the node is connected will change, that is, 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.
  • the IAB donor can determine the relationship between the first IAB node and the IAB donor through the cache data of the device itself or historical data in step S101. Configuration information of the BH RLC CH between the source and parent nodes of the first IAB node.
  • the recovery IAB-MT (that is, the MT part of the first IAB node) passes through the source IAB donor-DU (as shown in Figure 10-1, Figure 10-2, Figure 10-3, and IAB donor-DU1 in Figure 10-4) Connect to the source IAB donor-CU ( Figure 10-1, Figure 10-2, Figure 10-3, Figure 10-4 IAB donor-CU1); trigger at least one of the following processes: RRC re-establishment, F1 connection establishment or After the F1 connection re-establishment process, restore the IAB-MT to connect to the target through the target IAB donor-DU (as shown in Figure 10-1, Figure 10-2, Figure 10-3, and IAB donor-DU2 in Figure 10-4) IAB donor-CU (IAB donor-CU2 in Figure 10-1, Figure 10-2, Figure 10-3, Figure 10-4).
  • the IAB donor may be a 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
  • the IAB donor connected to the target parent node of the first IAB node is the target IAB donor
  • Changed scenarios such as inter-CU (Inter-donor-CU) RRC re-establishment scenarios.
  • the IAB donor can determine the relationship between the first IAB node and the first IAB node through the message sent by the source IAB donor of the first IAB node in step S101. Configuration information of BH RLC CH between source parent nodes.
  • the IAB donor sends the configuration information of the BH RLC CH to the target parent node of the first IAB node.
  • 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 in step S102 Configuration information for BH RLC CH from IAB donor.
  • the target parent node of the first IAB node may be an intermediate IAB node on the path between the first IAB node and the IAB donor, or may be the IAB donor DU in the IAB donor, here Not limited.
  • the first IAB node may be represented by the restored IAB node, and correspondingly, the MT part and the DU part included in the first IAB node may be respectively represented by the restored IAB-MT and the restored IAB- DU said.
  • the configuration information of the BH RLC CH in step S102 may be carried in the message sent by the source IAB donor to the target IAB donor.
  • the target parent node of the first IAB node determines the configuration of the BH RLC CH with the first IAB node according to the configuration information of the BH RLC CH.
  • the target parent node of the first IAB node determines the configuration of the BH RLC CH with the first IAB node according to the configuration information of the BH RLC CH in step S103.
  • the target parent node of the first IAB node can use the configuration information of the BH RLC CH in step S103 to further determine the relationship with the first IAB node.
  • the configuration of the BH RLC CH between an IAB node to realize that the first IAB node communicates 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 with the first IAB node, there is no need to send the configuration information of the BH RLC CH to the first IAB node. , the first IAB node can communicate in the IAB network through the target parent node of the first IAB node, thereby saving the overhead of resource configuration.
  • the target parent node of the first IAB node may determine the configuration of the BH RLC CH between the first IAB node and the target parent node in various ways. For example: when the target parent node determines the air interface resources that need to be occupied according to the configuration of the BH RLC CH, if the target parent node has enough air interface resources, the target parent node can continue to use the configuration of the BH RLC CH received in step S102. Otherwise, the target parent node generates the 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.
  • the IAB donor sends the first indication information to the first IAB node through the target parent node of the first IAB node.
  • 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.
  • the first IAB node sends the first indication information through the target parent node of the first IAB node in step S104.
  • the node receives the first indication information from the IAB donor.
  • the first indication information is used to indicate that the IAB donor connected to the first IAB node is changed, or the IAB-donor-CU connected to the first IAB node is changed.
  • 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 by the first IAB node changes.
  • the application scenario of the IAB donor and the first IAB node is the RRC re-establishment scenario of the Inter-donor-CU shown in Figure 10-1, Figure 10-2, Figure 10-3, and Figure 10-4, that is, when the 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 the first indication information to the first IAB node through the target parent node of the first IAB node, to The first IAB node determines that the host node of the first IAB node has 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 may be carried in the message sent by the target IAB
  • 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.
  • 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.
  • the first IAB node passes the first IAB node's IP address in step S105.
  • the target parent node receives the IP address of the IAB donor from the IAB donor.
  • the IAB donor sends the IP address information of the IAB donor to the first IAB node through the target parent node.
  • the application scenario of the IAB donor and the first IAB node is the RRC re-establishment scenario of the Inter-donor-CU shown in Figure 10-1, Figure 10-2, Figure 10-3, and Figure 10-4, that is, when the When the IAB donor is the host node (ie the target IAB donor) connected to the target parent node of the first IAB node, the IAB donor can also send the IP address of the target IAB donor to the first IAB node through the target parent node of the first IAB node information, so that the first IAB node triggers the F1 connection establishment/re-establishment process to the target IAB donor indicated by the IP address information.
  • 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.
  • the first IAB node determines that the RRC re-establishment between the first IAB node and the IAB donor is completed.
  • the first IAB node determines in step S107 that the RRC re-establishment with the IAB donor is completed, and after step S106, executes steps S107 and S108.
  • the IAB donor sends the first configuration information to the first IAB node through the target parent node of the first IAB node.
  • 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.
  • the first IAB node sends the first configuration information through the target parent node of the first IAB node in step S107.
  • the node receives the first configuration information from the IAB donor.
  • the first IAB node may determine in step S107 that the RRC re-establishment with the IAB donor is completed.
  • the IAB donor may also determine in step S106 that the RRC re-establishment with the first IAB node is completed.
  • the IAB donor may perform step S107 after determining that the RRC re-establishment with the first IAB node is completed, that is, send the first configuration information to the first IAB node through the target parent node of the first IAB node.
  • the first configuration information includes at least one of the following: the source identity of the cell of the first IAB node, the target identity of the cell of the first IAB node, the PLMN ID of the cell of the first IAB node, the first IAB node SSB information of the cell 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 under the source IAB donor that the first IAB node is connected to through the source parent node.
  • the target identification of the cell of the first IAB node refers to the identification of the cell under the target IAB donor that the first IAB node is connected to through the target parent node.
  • the IAB donor can also be sent to the first IAB node through the target parent node of the first IAB node.
  • the first configuration information enables the first IAB node to update the network configuration of the first IAB node according to the first configuration information, and subsequently can use the updated network configuration to communicate in the IAB network.
  • the first IAB node sends the first information to the child nodes of the first IAB node.
  • the first IAB node sends the first information to the child nodes of the first IAB node in step S108, and correspondingly, the child nodes of the first IAB node receive the first information from the first IAB node in step S108 .
  • the first information includes at least one of the following: indication information of the change of the IAB donor connected to the first IAB node, indication information of RRC re-establishment, identity information of the base station to be re-established by RRC, identity information of the cell to be re-established by RRC .
  • 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.
  • the first IAB node is the parent node of the child node, and the child node of the first IAB node may be an IAB node or a terminal device (such as a UE), which is not used here. Do limit.
  • the first IAB node may send the first information to the child node according to the first indication information obtained in step S104.
  • the first information is carried in the control unit MAC CE of the medium access control layer; or, the first information is carried in the BAP control PDU.
  • the child node of the first IAB node triggers at least one of the following processes according to the first information: RRC re-establishment, F1 connection establishment, or F1 connection re-establishment.
  • the child node of the first IAB node triggers at least one of the following processes according to the first information received in step S108: RRC re-establishment, F1 connection establishment, or F1 connection re-establishment.
  • step S108 before the first IAB node sends the first information to the child nodes of the first IAB node in step S108, if the establishment of the F1 connection between the first IAB node and the IAB donor is not completed (or F1 connection re-establishment is not completed).
  • 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, it sends an RRC re-establishment request message or an F1 connection establishment/re-establishment request message 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 between the child node and the IAB donor is completed or the F1 connection establishment/re-establishment is completed.
  • the first IAB node may also determine the F1 connection with the IAB donor Build/Rebuild completed. That is, after the first IAB node determines that the establishment/re-establishment of the F1 connection with the IAB donor is completed, it sends the first information to the child node of the first IAB node, so that the child node can pass the first information in step S109.
  • An F1 connection that has been established/re-established between an IAB node and an IAB donor is triggered according to the first information to perform RRC re-establishment or F1 connection establishment/re-establishment to the IAB donor.
  • the first IAB node determines that the RRC re-establishment between the first IAB node and the target IABdonor is completed, that is, after the host node of the first node is changed to the target IABdonor, the first IAB node sends a message to the child node of the first IAB node. Send the first information, 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 IABdonor according to the first information, so as to realize the child node of the first IAB node. Communicate in the IAB network through the first IAB node.
  • the first IAB node obtains a new configuration, and notifies the descendant nodes (child nodes) to trigger the RRC re-establishment process, so that after the restored IAB node performs RRC reconstruction to the new IAB host, the descendant nodes of the restored IAB node will also be restored.
  • the descendant nodes of the restored IAB node will also be restored.
  • an example of a schematic flowchart of an RRC re-establishment scenario of an Inter-donor-CU may be as shown in FIG. 12 , and the RRC re-establishment process may include the following steps.
  • Step 1 When the recovery IAB node (ie the first IAB node) detects that the link with the source parent node fails to switch, the radio link fails RLF, the integrity protection fails, the RRC reconfiguration fails, etc., trigger RRC Reconnect. That is, step 1 is performed to restore the IAB-MT (that is, the MT part of the first IAB node) through the selected new parent node (the new parent node may also be called the target parent node, and the target parent node may be the IAB node or the target IAB node).
  • donor DU send an RRC re-establishment request message to the target IAB donor-CU.
  • the RRC re-establishment request message may carry the physical cell identity PCI of the restored IAB-MT access cell under the source parent node, and the restored IAB-MT identity C-RNTI under the access cell.
  • Step 2 The target IAB donor-CU sends a Retrieve UE Context Request message to the source IAB donor-CU.
  • the message may carry the PCI and C-RNTI information carried in the RRC re-establishment request message by the restore IAB-MT, and also carry the cell identity and integrity check of the IAB-MT to perform the re-establishment cell.
  • the cell that the IAB-MT performs re-establishment refers to the cell selected for performing cell selection in the process of triggering the RRC re-establishment by the IAB-MT.
  • Step 3 The source IAB donor-CU sends a query UE context response message (Retrieve UE Context Response) to the target IAB donor-CU.
  • query UE context response message Retrieve UE Context Response
  • the message may carry the context of the restored IAB node, including the context of the restored IAB-MT and the context of the restored IAB-DU.
  • restoring the context of the IAB-MT includes restoring the configuration of the BH RLC CH used by the IAB-MT access source parent node (or restoring the configuration information of the BH RLC CH established on the link between the IAB-MT and the source parent node), Include at least one of the following information:
  • the identifier of the BH RLC CH (BH RLC CH ID), the logical channel identifier (BH LCH ID) corresponding to the BH RLC CH, the configuration of the RLC (RLC-config), and the configuration of the logical channel (LCH-config).
  • the context for restoring the IAB-DU includes at least one of the following information:
  • IAB-DU identity (IAB-DU id and/or IAB-DU name), restore the identity of the base station to which the IAB-DU belongs (gNB ID), restore the cell local ID of the IAB-DU, restore the IAB node PLMN ID, restore the SSB information of the IAB-DU cell, etc.
  • Step 4 The target IAB donor-CU sends an RRC re-establishment message to the recovering IAB-MT.
  • the message carries the indication information of the donor-CU change, so that the restoration of the IAB-MT can trigger the establishment/re-establishment of the F1 connection with the target IAB donor-CU when the donor-CU is changed.
  • Step 5 The target IAB donor-CU sends a UE context setup request message (UE Context Setup Request) to the target parent node IAB-DU.
  • UE Context Setup Request UE Context Setup Request
  • the message carries the configuration of restoring the BH RLC CH used by the IAB-MT access source parent node, so that the target parent node decides whether to allocate a new configuration for the BH RLC CH.
  • step 4 The sequence between step 4 and step 5 is not limited.
  • Step 6 The target parent node IAB-DU sends a UE context setup response message (UE Context Setup Response) to the target IAB donor-CU.
  • UE context setup response message UE Context Setup Response
  • Step 7 The recovery IAB-MT sends an RRC re-establishment complete message to the target IAB donor-CU.
  • Step 8 The target IAB donor-CU sends an RRC reconfiguration message to the restoration IAB-MT, which carries the BAP address allocated by the target IAB donor-CU for the restoration IAB node, and the target IAB donor-CU is the restoration IAB node on the target path
  • the target path refers to the path between the recovery IAB node and the target IAB donor through the target parent node.
  • the message may also carry at least one of the following information:
  • the IP address of the target IAB donor-CU, and the indication information of the change of the donor-CU are the IP address of the target IAB donor-CU, and the indication information of the change of the donor-CU.
  • the indication information of the donor-CU change can be sent only once.
  • the RRC re-establishment message in step 4 carries the indication information of the donor-CU change
  • the RRC reconfiguration message in step 8 will not carry the indication information. Otherwise, if the indication information is not carried in step 4, the indication information will be carried in step 8.
  • the recovery IAB-MT completes the RRC re-establishment with the target IAB donor.
  • the schematic flowchart shown in FIG. 12 may be an example implementation process of the IAB donor acquiring the configuration information of the BH RLC CH in step S101 of the embodiment shown in FIG. 11 .
  • the IAB donor can also obtain the configuration information of the BH RLC CH in other ways.
  • the other steps after step S101 in the embodiment shown in FIG. 11 that is, the implementation process of step S102 to step S108 in the embodiment shown in FIG. 11 , may be further implemented on the basis of the implementation process of the process shown in FIG. 12 , or The process is not implemented through the flow shown in FIG. 12, but is further implemented based on other implementation processes, which is not specifically limited here.
  • the IAB donor acquiring the configuration information of the BH RLC CH may include: the IAB donor receiving information from the source The IAB donor obtains the user equipment UE context response message (that is, the Retrieve UE Context Response in step 3 shown in FIG. 12 ), the obtain UE context response message includes the configuration information of the BH RLC CH.
  • the IAB donor 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 be the acquisition sent by the host node connected to the source parent node of the first IAB node
  • the configuration information of the BH RLC CH is obtained from the UE context response message of the user equipment.
  • step S102 of the embodiment shown in FIG. 11 the IAB donor sending the configuration information of the BH RLC CH to the target parent node of the first IAB node may be implemented through step 5 shown in FIG. 12 , that is, by The UE Context Setup Request message (UE Context Setup Request) implements the sending process and the receiving process of the configuration information of the BH RLC CH.
  • UE Context Setup Request implements the sending process and the receiving process of the configuration information of the BH RLC CH.
  • step S104 of the embodiment shown in FIG. 11 the IAB donor sends first indication information to the first IAB node through the target parent node of the first IAB node, and the first indication information may specifically be The indication information of the donor-CU change shown in step 4 and step 8 in FIG. 12 .
  • step S104 can be implemented through step 4 shown in FIG. 12 , that is, the sending process and the receiving process of the first indication information are implemented through the RRC re-establishment message; in addition, it can also be implemented through step 8 shown in FIG. 12 , that is, through RRC reconfiguration The message implements the sending process and the receiving process of the first indication information.
  • 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.
  • the sending process and the receiving process of the IP address of the IAB donor are realized through the RRC reconfiguration message.
  • the first indication information in step S104 is also implemented through step 8 shown in FIG. 12 , that is, 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.
  • the application scenario of the IAB donor and the first IAB node is the RRC replay of the Inter-donor-CU shown in Figure 10-1, Figure 10-2, Figure 10-3, and Figure 10-4
  • this IAB donor is the host node (that is, the target IAB donor) that the target parent node of the first IAB node is connected to
  • the first IAB node in step S106 of the embodiment shown in FIG.
  • the first IAB node may determine that the RRC re-establishment with the IAB donor is completed after receiving the RRC re-establishment complete message sent from the target IAB donor in step 7 shown in FIG. 12 .
  • the configuration information for restoring the IAB-DU (the DU part in the first IAB node) needs to be updated. For example: restore the cell identity or CGI of the IAB-DU cell, restore the PLMN ID of the IAB-DU, restore the SSB information of the IAB-DU cell, etc.
  • restore the IAB-DU to obtain the new configuration, including: obtaining from the OAM server and obtaining from the target IAB donor.
  • the IAB donor may send the first configuration information to the first IAB node in various ways, which will be described below with examples of several implementation ways.
  • Manner 1 Obtain the first configuration information from the OAM server.
  • the recovery IAB-DU can obtain 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 it to the recovery IAB-DU. That is to say, in this scenario, the target IAB donor only plays the role of relaying and restoring the new configuration information transmission between the IAB-DU and the OAM server.
  • the new configuration for restoring the IAB-DU includes at least one of the following information: CGI/Cell identity of the IAB-DU cell, PLMN ID of the IAB-DU cell, and SSB information of the IAB-DU cell.
  • the recovering IAB node can obtain the IP address of the target IAB donor-CU through the OAM server, instead of obtaining it through the RRC reconfiguration message in step 8 in Figure 12 (that is, in Figure 12 ).
  • the RRC reconfiguration message in step 8 does not need to carry the IP address of the target IAB donor-CU).
  • the restored IAB node obtains the new configuration, it needs to trigger the establishment/re-establishment process of the F1 interface to the target IAB donor.
  • the specific recovery IAB node triggers the establishment/re-establishment flow diagram of the F1 interface to the target IAB donor, including the following steps.
  • the recovery IAB-DU uses the IP address assigned by the target IAB donor to trigger the establishment of a TNLA association with the target IAB donor-CU.
  • the restoration IAB-DU sends an F1 setup request message (F1 Setup Request) to the target IAB donor-CU, requesting to establish/re-establish an F1 connection between the restoration IAB-DU and the target IAB donor-CU.
  • F1 Setup Request F1 Setup Request
  • the target IAB donor-CU sends an F1 setup response message (F1 Setup Response) to the recovery IAB-DU.
  • F1 Setup Response F1 Setup Response
  • the recovery IAB-DU sends at least one of the following information (that is, the first information) to the child node, so that the child node triggers the RRC re-establishment process to the target IAB donor, including:
  • Indication information of donor-CU change indication information of RRC re-establishment, identity of re-established base station (eg gNB ID), identity of re-established cell (eg PCI).
  • the indication information of the change of the donor-CU (that is, the first indication information) is used to indicate that the IAB donor of the first IAB node connection is changed.
  • the indication information of the RRC re-establishment is used to instruct the child node to trigger the RRC re-establishment, so that the child node knows that the RRC re-establishment procedure needs to be performed.
  • the identifier of the re-established cell (eg PCI) is used to indicate to the child node the cell identifier corresponding to the selected cell in the RRC re-establishment process, so that the child node can perform cell selection to the corresponding re-established cell.
  • the identity of the re-established base station (eg gNB ID) is used to indicate to the child node the identity of the base station corresponding to the selected cell during the RRC re-establishment process, so that the child node can perform cell selection to the re-established cell under the designated base station (corresponding to the re-established cell).
  • the base station is the base station identified by the gNB ID).
  • the above information can be carried in the MAC CE and sent, or can be carried in the backhaul adaptation protocol control packet data unit (backhaul adaptation protocol control packet data unit, BAP control PDU) and sent.
  • step 4 is not limited.
  • Method 2 Obtain the first configuration information from the target IAB donor.
  • the difference from the mode 1 is that the new configuration information (that is, the first configuration information) of the restored IAB-DU is generated by the target IAB donor and then notified to restore the IAB-DU.
  • the process is reflected in the difference between step 2 and step 3.
  • restoring the IAB-DU obtains new configuration information through step 2.
  • the target IAB donor-CU sends an F1AP request message to the restoration IAB-DU, and the request message is used to establish/re-establish an F1 connection between the restoration IAB-DU and the target IAB donor-CU.
  • the F1AP request message carries an information list for modifying and restoring IAB-DU cells, and each information list contains at least one of the following information:
  • Restore the source identity of the IAB-DU cell for example: source CGI or source Cell identity
  • restore the new configuration of the IAB-DU restore the IAB-DU new cell activation indication information.
  • the F1AP request message may be an existing F1AP message (for example: gNB-CU Configuration Update), or may be a newly defined F1AP message.
  • the recovery IAB-DU sends an F1AP response message to the target IAB donor-CU.
  • recovering the IAB-DU obtains new configuration information through step 3.
  • the restoration IAB-DU sends an F1AP request message to the target IAB donor-CU, and the request message is used to establish/re-establish an F1 connection between the restoration IAB-DU and the target IAB donor-CU.
  • the target IAB donor-CU sends an F1AP response message to the recovering IAB-DU.
  • the F1AP request message carries an information list for modifying and restoring IAB-DU cells, and each information list contains at least one of the following information:
  • Restore the source identity of the IAB-DU cell for example: source CGI or source Cell identity
  • restore the new configuration of the IAB-DU restore the IAB-DU new cell activation indication information.
  • the F1AP request message may be an existing F1AP message (for example: gNB-DU Configuration Update Ack), or may be a newly defined F1AP message.
  • step S107 in the embodiment shown in FIG. 11 where the schematic flowcharts shown in FIG. 13 to FIG. 15 are located needs to be executed after step S106 in the embodiment shown in FIG. 11 , and does not depend on the steps in the embodiment shown in FIG. 11 .
  • the implementation process from S101 (the flow shown in FIG. 12 ) to step S103 is not limited in the embodiment of the present application on the execution order of step S107 , step S104 and step S105 in the embodiment shown in FIG. 11 .
  • the first IAB node may perform step S108 of the embodiment shown in FIG. 11 in step 4 in FIG. 13 to FIG. 15 .
  • the first IAB node may execute step S108 of the embodiment shown in FIG. 11 after step 4 in FIGS. 13 to 15 . That is, once the child node receives the MAC CE/BAP control PDU in step 4, it will trigger the RRC re-establishment process to the target IAB donor-CU, and the corresponding process is consistent with the RRC re-establishment process for restoring the IAB-MT ( Figure 12). , and will not be repeated here.
  • an embodiment of the present application provides a communication apparatus 1600, specifically, the communication apparatus 1600 includes: a processing unit 1601 and a transceiver unit 1602;
  • the implementation of the processing unit 1601 and the transceiver unit 1602 in the communication apparatus 1600 includes the following processes.
  • the processing unit 1601 is used to obtain the configuration information of the radio link control channel BH RLC CH of the backhaul link, where the configuration information of the BH RLC CH is the source of the first access backhaul integrated IAB node and the first IAB node Configuration information of BH RLC CH between parent nodes;
  • the transceiver unit 1602 is configured to send the configuration information of the BH RLC CH to the target parent node of the first IAB node.
  • the configuration information of the BH RLC CH includes at least one of the following:
  • the IAB donor is a target IAB donor
  • the target parent node is connected with the target IAB donor
  • the source parent node is connected with the source IAB donor.
  • the processing unit 1601 is specifically configured to receive a user equipment UE context acquisition response message from the source IAB donor, where the UE context acquisition response message includes configuration information of the BH RLC CH.
  • the transceiver unit 1602 is further configured to:
  • the first indication information is carried in the RRC re-establishment message; or,
  • the first indication information is carried in the RRC reconfiguration message.
  • the transceiver unit 1602 is further configured to:
  • the IP address information of the target IAB donor is carried in the RRC reconfiguration message.
  • the transceiver unit 1602 is further configured to:
  • 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 implementation of the processing unit 1601 and the transceiver unit 1602 in the communication apparatus 1600 includes the following processes.
  • Transceiver unit 1602 configured to receive configuration information of the radio link control channel BH RLC CH from the backhaul link of the integrated backhaul host IAB donor, where the configuration information of the BH RLC CH is the first integrated access backhaul The configuration information of the BH RLC CH between the IAB node and the source parent node of the first IAB node;
  • the processing unit 1601 is configured to determine the configuration of the BH RLC CH with the first IAB node according to the configuration information of the BH RLC CH.
  • the configuration information of the BH RLC CH includes at least one of the following:
  • the implementation of the processing unit 1601 and the transceiver unit 1602 in the communication apparatus 1600 includes the following processes.
  • the processing unit 1601 is used to determine that the RRC re-establishment between the integrated host IAB donor and the target access backhaul is completed;
  • a transceiver unit 1602 configured to send the first information to the child nodes of the first IAB node
  • the first information includes at least one of the following:
  • the indication information of the change of the IAB donor connected to the first IAB node the indication information of the RRC re-establishment, the identification information of the base station of the RRC re-establishment, and the identification information of the cell of the RRC re-establishment.
  • the first information is carried in the control unit MAC CE of the medium access control layer; or,
  • the first information is carried in the BAP control PDU.
  • the transceiver unit 1602 is further configured to:
  • the first indication information is carried in the RRC re-establishment message; or,
  • the first indication information is carried in the RRC reconfiguration message.
  • the processing unit 1601 is further configured to: determine that the establishment/re-establishment of the F1 connection with the IAB donor is completed or the F1 connection has been restored.
  • the transceiver unit 1602 is further configured to:
  • the IP address information of the target IAB donor is carried in the RRC reconfiguration message.
  • the transceiver unit 1602 is specifically used for:
  • the implementation of the processing unit 1601 and the transceiver unit 1602 in the communication apparatus 1600 includes the following processes.
  • a transceiver unit 1602 configured to receive first information from the first IAB node, where the first information includes at least one of the following:
  • the processing unit 1601 is configured to trigger at least one of the following procedures according to the first information: RRC re-establishment, F1 connection establishment, or F1 connection re-establishment.
  • the first information is carried in the control unit MAC CE of the medium access control layer; or,
  • the first information is carried in the BAP control PDU.
  • FIG. 17 is a schematic structural diagram of the communication device involved in the above-mentioned embodiment provided by the embodiment of the present application, wherein the communication device may specifically be the IAB donor in the foregoing embodiment, the target parent node of the first IAB node , the first IAB node or the child node of the first IAB node, the structure of the communication apparatus may refer to the structure shown in FIG. 17 .
  • 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 this embodiment of the present application, the connection may include various interfaces, transmission lines, or buses, which are not limited in this embodiment. .
  • Antenna 1715 is connected to transceiver 1713 .
  • the network interface 1714 is used to connect the communication device with other communication devices through a communication link.
  • the network interface 1714 may include a network interface between the communication device and the core network device, such as the S1 interface, and the network interface may include the communication device and other networks.
  • a network interface between devices such as other access network devices or core network devices, such as an X2 or Xn interface.
  • the processor 1711 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process data of the software programs, for example, to support the communication device to perform the actions described in the embodiments.
  • the communication device may include a baseband processor and a central processing unit.
  • the baseband processor is mainly used to process communication protocols and communication data.
  • the central processing unit is mainly used to control the entire terminal equipment, execute software programs, and process data of software programs. .
  • the processor 1711 in FIG. 17 may integrate the functions of a baseband processor and a central processing unit. Those skilled in the art can understand that the baseband processor and the central processing unit may also be independent processors, interconnected by technologies such as a bus.
  • a terminal device may include multiple baseband processors to adapt to different network standards, a terminal device may include multiple central processors to enhance its processing capability, and various components of the terminal device may be connected through various buses.
  • the baseband processor may also be expressed as a baseband processing circuit or a baseband processing chip.
  • the central processing unit can also be expressed as a central processing circuit or a central processing chip.
  • the function of processing the communication protocol and communication data may be built in the processor, or may be stored in the memory in the form of a software program, and the processor executes the software program to realize the baseband processing function.
  • the memory is mainly used to store software programs and data.
  • the memory 1712 may exist independently and be connected to the processor 1711 .
  • the memory 1712 may be integrated with the processor 1711, for example, in one chip.
  • the memory 1712 can store program codes for implementing the technical solutions of the embodiments of the present application, and is controlled and executed by the processor 1711 .
  • Figure 17 shows only one memory and one processor. In an actual terminal device, there may be multiple processors and multiple memories.
  • the memory may also be referred to as a storage medium or a storage device or the like.
  • the memory may be a storage element on the same chip as the processor, that is, an on-chip storage element, or an independent storage element, which is not limited in this embodiment of the present application.
  • the transceiver 1713 may be used to support the reception or transmission of radio frequency signals between the communication device and the terminal, and the transceiver 1713 may be connected to the antenna 1715 .
  • the transceiver 1713 includes a transmitter Tx and a receiver Rx.
  • one or more antennas 1715 can receive radio frequency signals
  • the receiver Rx of the transceiver 1713 is used to receive the radio frequency signals from the antennas, convert the radio frequency signals into digital baseband signals or digital intermediate frequency signals, and convert the digital
  • the baseband signal or digital intermediate frequency signal is provided to the processor 1711, so that the processor 1711 performs further processing on the digital baseband signal or digital intermediate frequency signal, such as demodulation processing and decoding processing.
  • the transmitter Tx in the transceiver 1713 is also used to receive the modulated digital baseband signal or digital intermediate frequency signal from the processor 1711, and convert the modulated digital baseband signal or digital intermediate frequency signal into a radio frequency signal, and pass a The radio frequency signal is transmitted by the antenna or antennas 1715.
  • the receiver Rx can selectively perform one or more stages of down-mixing processing and analog-to-digital conversion processing on the radio frequency signal to obtain a digital baseband signal or a digital intermediate frequency signal. The order of precedence is adjustable.
  • the transmitter Tx can selectively perform one or more stages of up-mixing processing and digital-to-analog conversion processing on the modulated digital baseband signal or digital intermediate frequency signal to obtain a radio frequency signal, and the up-mixing processing and digital-to-analog conversion processing
  • the sequence of s is adjustable.
  • Digital baseband signals and digital intermediate frequency signals can be collectively referred to as digital signals.
  • a transceiver may also be referred to as a transceiver unit, a transceiver, a transceiver, or the like.
  • the device used to implement the receiving function in the transceiver unit may be regarded as a receiving unit
  • the device used to implement the transmitting function in the transceiver unit may be regarded as a transmitting unit, that is, the transceiver unit includes a receiving unit and a transmitting unit, and the receiving unit also It can be called a receiver, an input port, a receiving circuit, etc.
  • the sending unit can be called a transmitter, a transmitter, or a transmitting circuit, etc.
  • the communication device shown in FIG. 17 can be specifically used to implement the steps implemented by the communication device in the method embodiments corresponding to FIG. 11 to FIG. 15 , and realize the technical effect corresponding to the communication device.
  • the communication device shown in FIG. 17 can be specifically used to implement the steps implemented by the communication device in the method embodiments corresponding to FIG. 11 to FIG. 15 , and realize the technical effect corresponding to the communication device.
  • FIG. 18 is a schematic structural diagram of an IAB donor provided by an embodiment of the present application, and the IAB donor may adopt a CU-DU separation architecture. As shown in FIG. 18 , the IAB donor can be applied to the system shown in FIG. 10-1 or FIG. 10-2 or FIG. 10-3 or FIG. 10-4 to realize the IAB donor (source IAB donor) in the above method embodiment. and/or target IAB donor).
  • An IAB donor may include one or more DUs 1101 and one or more CUs 1102.
  • the DU 1101 may 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 part is mainly used for the transmission and reception of radio frequency signals, the conversion of radio frequency signals and baseband signals, and part of baseband processing.
  • the CU 1102 may include at least one processor 11022 and at least one memory 11021 . Communication between the CU 1102 and the DU 1101 may be performed through an interface, wherein the control plane (control plane) interface may be F1-C, and the user plane (user plane) interface may be F1-U.
  • control plane control plane
  • user plane user plane
  • the CU 1102 part is mainly used to perform baseband processing, control the base station, and the like.
  • the DU 1101 and the CU 1102 may be physically set together, or may be physically separated, that is, a distributed base station.
  • the CU 1102 is the control center of the base station, which can also be called a processing unit, and is mainly used to complete the baseband processing function.
  • the CU 1102 may be used to control the base station to execute the operation flow of the network device in the foregoing method embodiments.
  • the baseband processing on the CU and the DU may be divided according to the protocol layer of the wireless network, and the above content may be referred to for details.
  • the CU 1102 may be composed of one or more boards, and the multiple boards may jointly support a wireless access network (such as a 5G network) with a single access indication, or may respectively support a wireless access network with different access standards.
  • Wireless access network (such as LTE network, 5G network or other access network).
  • the memory 11021 and the processor 11022 may serve one or more single boards. That is to say, the memory and processor can be provided separately on each single board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits may also be provided on each single board.
  • the DU 1101 can be composed of one or more single boards, and multiple single boards can jointly support a wireless access network (such as a 5G network) with a single access indication, or can support a wireless access network with different access standards (such as a 5G network). Such as LTE network, 5G network or other access network).
  • the memory 11014 and processor 11013 may serve one or more single boards. That is to say, the memory and processor can be provided separately on each single board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits can be provided on each board.
  • the CU 1102 can transmit with the child nodes of the IAB donor through the DU 1101, the CU 1102 can be connected with other IAB donors through the interface, and the CU 1102 can receive data from other IAB donors (such as CUs of other IAB donors) through the interface and/or messages, or the CU 1102 may send data and/or messages to the other IAB donor through the interface.
  • the CU 1102 can transmit with the child nodes of the IAB donor through the DU 1101
  • the CU 1102 can be connected with other IAB donors through the interface
  • the CU 1102 can receive data from other IAB donors (such as CUs of other IAB donors) through the interface and/or messages, or the CU 1102 may send data and/or messages to the other IAB donor through the interface.
  • Embodiments of the present application further provide a computer-readable storage medium that stores one or more computer-executable instructions.
  • the processor executes the method implemented by the above-mentioned communication device, such as the above-mentioned IAB donor , A method implemented by the target parent node of the first IAB node, the first IAB node or the child node of the first IAB node.
  • Embodiments of the present application also provide a computer program product (or computer program) that stores one or more computers.
  • the processor executes the method implemented by the above communication device, as described above.
  • An embodiment of the present application also provides a chip system, where the chip system includes a processor for supporting a communication device to implement the method implemented by the communication device, such as the above-mentioned IAB donor, the target parent node of the first IAB node, the first IAB A method implemented by a node or a child node of the first IAB node.
  • the chip system may further include a memory for storing necessary program instructions and data of the communication device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • An embodiment of the present application further provides a communication system, which includes the above communication device, such as the above 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.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium.
  • the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供了一种用于接入回传一体化IAB系统中的通信方法及相关配置，用于在第一IAB节点的父节点由源父节点改变为目标父节点之后，在第一IAB节点的目标父节点可以根据来自IAB donor的BH RLC CH的配置信息灵活地配置第一IAB节点的通信资源。在该方法中，IAB donor获取回传链路的无线链路控制信道BH RLC CH的配置信息，该BH RLC CH的配置信息为第一接入回传一体化IAB节点与第一IAB节点的源父节点之间的BH RLC CH的配置信息；然后，该IAB donor向第一IAB节点的目标父节点发送该BH RLC CH的配置信息。

Description

一种用于接入回传一体化IAB系统中的通信方法及相关设备 技术领域
本申请实施例涉及通信领域，尤其涉及一种用于接入回传一体化IAB系统中的通信方法及相关设备。
背景技术
在第三代合作伙伴计划(3rd-generationpartnershipproject，3GPP)R15接入回转一体化(integratedaccessandbackhaul，IAB)的网络架构中，包括IAB宿主节点(IABdonor)和IAB节点(IABnode)。在考虑集中式单元(centralunit，CU)-分布式单元(distributedunit，DU)架构的情况下，IABdonor包括IABdonorCU和IABdonorDU。IABnode包括IABnode移动终端(mobileterminal，MT)功能单元和IABnodeDU。其中，IABnodeMT功能单元作为用户设备(userequipment，UE)模块，负责与其父节点的通信。IABnodeDU作为DU，为其下附着的UE或其他IABnode提供接入服务。其中，IABnode与IABdonorCU之间的连接为F1连接。
目前，由于在实际通信过程中，两个通信节点之间的链路质量可能发生改变，例如：发生无线链路失败(radio link failure，RLF)、或者完整性保护失败、无线资源控制(radio resource control，RRC)重配置失败等情况，从而导致IAB节点所连接的父节点可能会发生改变，则将触发IAB节点执行切换，即该IAB节点释放与源父节点之间的连接，并与目标父节点之间建立新的连接。其中，该源父节点和目标父节点可以是IAB节点与IAB donor之间路径上的中间IAB节点，也可以是IAB donor中的IAB donor DU。
然而，在IAB网络中，由于该IAB节点所连接的父节点发生改变，导致该IAB节点和目标父节点之间的链路资源需要重新配置，如何灵活地配置IAB节点的通信资源是一个亟待解决的问题。
发明内容
本申请实施例提供了一种用于接入回传一体化IAB系统中的通信方法及相关配置，用于在第一IAB节点的父节点由源父节点改变为目标父节点之后，第一IAB节点的目标父节点可以根据来自IAB donor的BH RLC CH的配置信息灵活地配置第一IAB节点的通信资源。
本申请实施例第一方面提供了一种用于接入回传一体化IAB系统中的通信方法，该方法可以应用于接入回传一体化宿主IAB donor，也可以应用于IAB donor的部件执行(例如处理器、芯片或芯片系统等)。在该方法中，接入回传一体化宿主IAB donor获取回传链路的无线链路控制信道BH RLC CH的配置信息，该BH RLC CH的配置信息为第一接入回传一体化IAB节点与该第一IAB节点的源父节点之间的BH RLC CH的配置信息；然后，该IAB donor向该第一IAB节点的目标父节点发送该BH RLC CH的配置信息。
基于上述技术方案，IAB donor获取第一IAB节点与第一IAB节点的源父节点之间的BH RLC CH的配置信息，并向第一IAB节点的目标父节点发送该BH RLC CH的配置信息。 其中，在第一IAB节点的父节点由源父节点改变为目标父节点之后，使得该第一IAB节点的目标父节点可以使用该BH RLC CH的配置信息进一步确定第一IAB节点与第一IAB节点的目标父节点之间的BH RLC CH的配置。即在第一IAB节点的目标父节点确定来自IAB donor的BH RLC CH的配置信息可以用于与第一IAB节点之间进行通信时，无需再向该第一IAB节点发送BH RLC CH的配置信息，就可以实现该第一IAB节点通过该第一IAB节点的目标父节点在IAB网络中通信，节省了资源配置的开销；在第一IAB节点的目标父节点确定来自IAB donor的BH RLC CH的配置信息不用于与第一IAB节点之间进行通信时，可以根据该父节点的空口资源生成对应于该第一IAB节点的BH RLC CH的配置信息，也可以实现该第一IAB节点通过该第一IAB节点的目标父节点在IAB网络中通信。从而，该父节点可以根据来自IAB donor的BH RLC CH的配置信息灵活地配置第一IAB节点的通信资源。
需要说明的是，本申请实施例中，第一IAB节点的目标父节点可以是第一IAB节点与IAB donor之间路径上的中间IAB节点，也可以是IAB donor中的IAB donor DU，此处不做限定。
在本申请实施例第一方面的一种具体的实现方式中，该BH RLC CH的配置信息包括以下至少一项：该BH RLC CH的标识、该BH RLC CH对应的逻辑信道标识、无线链路控制信道RLC的配置信息或者逻辑信道的配置信息。
基于上述技术方案，BH RLC CH的配置信息可以通过上述多项中的至少一项实现，即提供了IAB donor获取以及发送BH RLC CH的配置信息的多种实现方式，提升方案的可实现性。
在本申请实施例第一方面的一种具体的实现方式中，该IAB donor为目标IAB donor，该目标父节点与该目标IAB donor连接，该源父节点与源IAB donor连接。
基于上述技术方案，第一IAB节点所连接的IAB donor也可以发生改变，其中，第一IAB节点的源父节点连接的IAB donor为源IAB donor，第一IAB节点的目标父节点连接的IAB donor为目标IAB donor，使得该方案可以应用于第一IAB节点连接的IAB donor发生改变的场景，例如跨宿主CU的(Inter-donor-CU)重建立场景。
在本申请实施例第一方面的一种具体的实现方式中，该IAB donor获取BH RLC CH的配置信息包括：该IAB donor接收来自该源IAB donor的获取用户设备UE上下文响应消息，该获取UE上下文响应消息包括该BH RLC CH的配置信息。
基于上述技术方案，当该IAB donor为第一IAB节点的目标父节点连接的宿主节点(即目标IAB donor)时，该IAB donor可以是通过该第一IAB节点的源父节点连接的宿主节点所发送的获取用户设备UE上下文响应消息中获取得到BH RLC CH的配置信息。提供了IAB donor获取BH RLC CH的配置信息的一种具体的实现方式，提升方案的可实现性。
在本申请实施例第一方面的一种具体的实现方式中，该IAB donor通过该目标父节点向该第一IAB节点发送第一指示信息，该第一指示信息用于指示该第一IAB节点连接的IAB donor改变。
基于上述技术方案，当该IAB donor为第一IAB节点的目标父节点连接的宿主节点(即目标IAB donor)时，该IAB donor还可以通过第一IAB节点的目标父节点向第一IAB节 点发送用于指示该第一IAB节点连接的IAB donor改变的第一指示信息，以使得该第一IAB节点确定该第一IAB节点的宿主节点发生改变，后续可以向目标宿主节点触发F1接口的建立/重建立流程，保证该第一IAB节点可以通过目标父节点连接到目标IAB donor进行通信。
在本申请实施例第一方面的一种具体的实现方式中，该第一指示信息携带在RRC重建立消息中；或，该第一指示信息携带在RRC重配置消息中。
基于上述技术方案，第一指示信息的承载方式可以为RRC重建立消息或者是RRC重配置消息，提供了第一指示信息的多种承载方式，提升方案的可实现性。
在本申请实施例第一方面的一种具体的实现方式中，该IAB donor通过该目标父节点向该第一IAB节点发送该IAB donor的网际互联协议IP地址信息。
基于上述技术方案，当该IAB donor为第一IAB节点的目标父节点连接的宿主节点(即目标IAB donor)时，该IAB donor还可以通过第一IAB节点的目标父节点向第一IAB节点发送该目标IAB donor的IP地址信息，以使得该第一IAB节点可以向该IP地址信息指示的宿主节点触发F1接口的建立/重建立流程，保证该第一IAB节点可以通过目标父节点连接到目标IAB donor进行通信。
在本申请实施例第一方面的一种具体的实现方式中，该目标IAB donor的IP地址信息携带在RRC重配置消息中。
基于上述技术方案，目标IAB donor的网际互联协议IP地址信息的承载方式可以为RRC重配置消息，提供了目标IAB donor的网际互联协议IP地址信息的一种具体的实现方式，提升方案的可实现性。
在本申请实施例第一方面的一种具体的实现方式中，该方法还可以包括：该IAB donor通过该目标父节点向该第一IAB节点发送第一配置信息，该第一配置信息包括以下至少一项：该第一IAB节点的小区的源标识、该第一IAB节点的小区的目标标识、该第一IAB节点的小区的PLMN ID、该第一IAB节点小区的SSB信息或者该第一IAB节点的小区的激活指示信息。
基于上述技术方案，当该IAB donor为第一IAB节点的目标父节点连接的宿主节点(即目标IAB donor)时，该IAB donor还可以通过第一IAB节点的目标父节点向第一IAB节点发送第一配置信息，使得该第一IAB节点根据该第一配置信息更新该第一IAB节点的网络配置，保证该第一IAB节点可以通过目标父节点连接到目标IAB donor进行通信。
本申请实施例第二方面提供了一种用于接入回传一体化IAB系统中的通信方法，该方法可以应用于第一IAB节点的目标父节点，也可以应用于第一IAB节点的目标父节点的部件执行(例如处理器、芯片或芯片系统等)。在该方法中，包括：第一接入回传一体化IAB节点的目标父节点接收来自IAB宿主IAB donor的回传链路的无线链路控制信道BH RLC CH的配置信息，该BH RLC CH的配置信息为该第一IAB节点与该第一IAB节点的源父节点之间的BH RLC CH的配置信息；该目标父节点根据该BH RLC CH的配置信息确定该第一IAB节点与该目标父节点之间的BH RLC CH的配置。
基于上述技术方案，第一IAB节点的目标父节点接收来自IAB donor的第一接入回传一体化IAB节点与第一IAB节点的源父节点之间的BH RLC CH的配置信息，并根据该BH RLC  CH的配置信息确定与该第一IAB节点之间的BH RLC CH的配置。其中，在第一IAB节点的父节点由源父节点改变为目标父节点之后，使得该第一IAB节点的目标父节点可以使用该BH RLC CH的配置信息进一步确定与该第一IAB节点之间的BH RLC CH的配置。即在第一IAB节点的目标父节点确定来自IAB donor的BH RLC CH的配置信息可以用于与第一IAB节点之间进行通信时，无需再向该第一IAB节点发送BH RLC CH的配置信息，就可以实现该第一IAB节点通过该第一IAB节点的目标父节点在IAB网络中通信，节省了资源配置的开销；在第一IAB节点的目标父节点确定来自IAB donor的BH RLC CH的配置信息不用于与第一IAB节点之间进行通信时，可以根据该父节点的空口资源生成对应于该第一IAB节点的BH RLC CH的配置信息，也可以实现该第一IAB节点通过该第一IAB节点的目标父节点在IAB网络中通信。从而，该父节点可以根据来自IAB donor的BH RLC CH的配置信息灵活地配置第一IAB节点的通信资源。
需要说明的是，本申请实施例中，第一IAB节点的目标父节点可以是第一IAB节点与IAB donor之间路径上的中间IAB节点，也可以是IAB donor中的IAB donorDU，此处不做限定。
在本申请实施例第二方面的一种具体的实现方式中，该BH RLC CH的配置信息可以包括以下至少一项：该BH RLC CH的标识、该BH RLC CH对应的逻辑信道标识、无线链路控制信道RLC的配置信息或者逻辑信道的配置信息。
基于上述技术方案，BH RLC CH的配置信息可以通过上述多项中的至少一项实现，即提供了IAB donor获取以及发送BH RLC CH的配置信息的多种实现方式，提升方案的可实现性。
本申请实施例第三方面提供了一种用于接入回传一体化IAB系统中的通信方法，该方法可以应用于第一接入回传一体化IAB节点，也可以应用于第一IAB节点的部件执行(例如处理器、芯片或芯片系统等)。在该方法中，第一接入回传一体化IAB节点确定与IAB宿主IAB donor之间的RRC重建立完成；该第一IAB节点向该第一IAB节点的子节点发送第一信息；该第一信息包括以下至少一项：该第一IAB节点连接的IAB donor改变的指示信息、RRC重建立的指示信息、RRC重建立的基站的标识信息、RRC重建立的小区的标识信息。
基于上述技术方案，第一IAB节点在确定与目标IAB donor之间的RRC重建立完成之后，即第一IAB节点的宿主节点改变为该目标IAB donor之后，该第一IAB节点向第一IAB节点的子节点发送第一信息，使得该第一IAB节点的子节点根据该第一信息触发与目标IAB donor之间的RRC重建立和/或F1连接的建立/重建立，保证该第一IAB节点的子节点可以正常工作。
需要说明的是，本申请实施例中，第一IAB节点为该第一IAB节点的子节点的父节点，其中，第一IAB节点的子节点可以为IAB节点，也可以是终端设备(如UE)，此处不做限定。
在本申请实施例第三方面的一种具体的实现方式中，该第一信息携带在媒体接入控制层的控制单元MAC CE中；或，该第一信息携带在回传适配协议控制分组数据单元BAP  control PDU中。
基于上述技术方案，第一信息的承载方式可以为媒体接入控制层的控制单元MAC CE或者是BAP control PDU，提供了第一信息的多种承载方式，提升方案的可实现性。
在本申请实施例第三方面的一种具体的实现方式中，在该第一IAB节点向该子节点发送该第一信息之前，该方法还包括：
该第一IAB节点接收来自该目标IAB donor的第一指示信息，该第一指示信息用于指示该第一IAB节点连接的IAB donor改变。
基于上述技术方案，在第一IAB节点向第一IAB节点的子节点发送第一信息之前，第一IAB节点还可以接收来自目标IAB donor发送的用于指示该第一IAB节点连接的IAB donor改变的第一指示信息，以使得该第一IAB节点确定该第一IAB节点以及子节点连接的宿主节点发生改变。后续可以进一步通知该第一IAB节点的子节点，使得该第一IAB节点的子节点触发RRC重建立和/或F1连接的建立/重建立，保证该第一IAB节点的子节点可以通过第一IAB节点连接到目标IAB donor进行通信。
可选地，第一IAB节点可以根据该第一指示信息向子节点发送该第一信息。
在本申请实施例第三方面的一种具体的实现方式中，该第一指示信息携带在RRC重建立消息中；或，该第一指示信息携带在RRC重配置消息中。
基于上述技术方案，第一指示信息的承载方式可以为RRC重建立消息或者是RRC重配置消息，提供了第一指示信息的多种承载方式，提升方案的可实现性。
在本申请实施例第三方面的一种具体的实现方式中，在该第一IAB节点向该第一IAB节点的子节点发送第一信息之前，该方法还可以包括：该第一IAB节点确定与该IAB donor之间的F1连接建立/重建立完成或F1连接已经恢复。
基于上述技术方案，第一IAB节点在确定与该IAB donor之间的F1连接建立/重建立完成或F1连接已经恢复之后，再向第一IAB节点的子节点发送第一信息，使得该子节点可以通过该第一IAB节点与IAB donor之间已建立/重建立的F1连接或已恢复的F1连接，根据该第一信息触发RRC重建立和/或F1连接的建立/重建立。
在本申请实施例第三方面的一种具体的实现方式中，该方法还可以包括：该第一IAB节点接收来自该IAB donor的该IAB donor的IP地址信息。
基于上述技术方案，第一IAB节点还可以通过第一IAB节点的目标父节点接收来自目标IAB donor发送的该目标IAB donor的IP地址信息，使得该第一IAB节点可以向该IP地址信息指示的宿主节点触发F1接口的建立/重建立流程，保证该第一IAB节点通过目标父节点连接到目标IAB donor后可以正常工作。
在本申请实施例第三方面的一种具体的实现方式中，该目标IAB donor的IP地址信息携带在RRC重配置消息中。
基于上述技术方案，目标IAB donor的IP地址信息的承载方式可以为RRC重配置消息，提供了目标IAB donor的IP地址信息的一种具体的实现方式，提升方案的可实现性。
在本申请实施例第三方面的一种具体的实现方式中，在所述第一IAB节点确定与IAB宿主IAB donor之间的RRC重建立完成之后，该方法还可以包括：该第一IAB节点接收来 自该IAB donor的第一配置信息，该第一配置信息包括以下至少一项：该第一IAB节点的小区的源标识、该第一IAB节点的小区的目标标识、该第一IAB节点的小区的PLMN ID、该第一IAB节点小区的SSB信息或者该第一IAB节点的小区的激活指示信息。
基于上述技术方案，第一IAB节点还可以通过第一IAB节点的目标父节点接收来自目标IAB donor发送的第一配置信息，使得该第一IAB节点根据该第一配置信息更新该第一IAB节点的配置，保证该第一IAB节点可以通过目标父节点连接到目标IAB donor进行通信。
本申请实施例第四方面提供了一种用于接入回传一体化IAB系统中的通信方法，该方法可以应用于第一IAB节点的子节点，也可以应用于第一IAB节点的子节点的部件执行(例如处理器、芯片或芯片系统等)。在该方法中，第一接入回传一体化IAB节点的子节点接收来自该第一IAB节点的第一信息，该第一信息包括以下至少一项：该第一IAB节点连接的IAB donor改变的指示信息、RRC重建立的指示信息、RRC重建立的基站的标识信息、RRC重建立的小区的标识信息；该子节点根据该第一信息触发以下至少一项流程：RRC重建立、F1连接建立或者F1连接重建立。
基于上述技术方案，第一IAB节点在确定与目标IAB donor之间的RRC重建立完成之后，即第一IAB节点的宿主节点改变为该目标IAB donor之后，第一IAB节点的子节点接收来自父节点即第一IAB节点所发送的第一信息，使得该第一IAB节点的子节点根据该第一信息触发与目标IAB donor之间的RRC重建立和/或F1连接的建立/重建立，保证该第一IAB节点的子节点可以通过第一IAB节点连接到目标IAB donor进行通信。
需要说明的是，本申请实施例中，第一IAB节点为该第一IAB节点的子节点的父节点，其中，第一IAB节点的子节点可以为IAB节点，也可以是终端设备(如UE)，此处不做限定。
在本申请实施例第四方面的一种具体的实现方式中，该第一信息携带在媒体接入控制层的控制单元MAC CE中；或，该第一信息携带在回传适配协议控制分组数据单元BAP control PDU中。
基于上述技术方案，第一信息的承载方式可以为媒体接入控制层的控制单元MAC CE或者是BAP control PDU，提供了第一信息的多种承载方式，提升方案的可实现性。
本申请实施例第五方面提供了一种通信装置，该装置为接入回传一体化宿主IAB donor，该装置包括：
处理单元，用于获取回传链路的无线链路控制信道BH RLC CH的配置信息，该BH RLC CH的配置信息为第一接入回传一体化IAB节点与该第一IAB节点的源父节点之间的BH RLC CH的配置信息；
收发单元，用于向该第一IAB节点的目标父节点发送该BH RLC CH的配置信息。
在本申请实施例第五方面的一种具体的实现方式中，该BH RLC CH的配置信息包括以下至少一项：
该BH RLC CH的标识、该BH RLC CH对应的逻辑信道标识、无线链路控制信道RLC的配置信息或者逻辑信道的配置信息。
在本申请实施例第五方面的一种具体的实现方式中，该IAB donor为目标IAB donor，该目标父节点与该目标IAB donor连接，该源父节点与源IAB donor连接。
在本申请实施例第五方面的一种具体的实现方式中，
该处理单元，具体用于接收来自该源IAB donor的获取用户设备UE上下文响应消息，该获取UE上下文响应消息包括该BH RLC CH的配置信息。
在本申请实施例第五方面的一种具体的实现方式中，该收发单元，还用于：
通过该目标父节点向该第一IAB节点发送第一指示信息，该第一指示信息用于指示该第一IAB节点连接的IAB donor改变。
在本申请实施例第五方面的一种具体的实现方式中，
该第一指示信息携带在RRC重建立消息中；或，
该第一指示信息携带在RRC重配置消息中。
在本申请实施例第五方面的一种具体的实现方式中，该收发单元，还用于：
通过该目标父节点向该第一IAB节点发送该目标IAB donor的网际互联协议IP地址信息。
在本申请实施例第五方面的一种具体的实现方式中，该目标IAB donor的IP地址信息携带在RRC重配置消息中。
在本申请实施例第五方面的一种具体的实现方式中，该收发单元，还用于：
通过该目标父节点向该第一IAB节点发送第一配置信息，该第一配置信息包括以下至少一项：
该第一IAB节点的小区的源标识、该第一IAB节点的小区的目标标识、该第一IAB节点的小区的PLMN ID、该第一IAB节点小区的SSB信息或者该第一IAB节点的小区的激活指示信息。
本申请实施例第五方面中，通信装置的组成模块还可以用于执行第一方面的各个可能实现方式中所执行的步骤，具体均可以参阅第一方面，此处不再赘述。
本申请实施例第六方面提供了一种通信装置，该装置为第一IAB节点的目标父节点，该装置包括：
收发单元，用于接收来自接入回传一体化宿主IAB donor的回传链路的无线链路控制信道BH RLC CH的配置信息，该BH RLC CH的配置信息为第一接入回传一体化IAB节点与该第一IAB节点的源父节点之间的BH RLC CH的配置信息；
处理单元，用于根据该BH RLC CH的配置信息确定与该第一IAB节点之间的BH RLC CH的配置。
在本申请实施例第六方面的一种具体的实现方式中，该BH RLC CH的配置信息包括以下至少一项：
该BH RLC CH的标识、该BH RLC CH对应的逻辑信道标识、无线链路控制信道RLC的配置信息或者逻辑信道的配置信息。
本申请实施例第六方面中，通信装置的组成模块还可以用于执行第二方面的各个可能实现方式中所执行的步骤，具体均可以参阅第二方面，此处不再赘述。
本申请实施例第七方面提供了一种通信装置，该装置为第一接入回传一体化IAB节点，该装置包括：
处理单元，用于确定与目标接入回传一体化宿主IAB donor之间RRC重建立完成；
收发单元，用于向该第一IAB节点的子节点发送第一信息；
该第一信息包括以下至少一项：
该第一IAB节点连接的IAB donor改变的指示信息、RRC重建立的指示信息、RRC重建立的基站的标识信息、RRC重建立的小区的标识信息。
在本申请实施例第七方面的一种具体的实现方式中，
该第一信息携带在媒体接入控制层的控制单元MAC CE中；或，
该第一信息携带在回传适配协议控制分组数据单元BAP control PDU中。
在本申请实施例第七方面的一种具体的实现方式中，该收发单元，还用于：
接收来自该目标IAB donor的第一指示信息，该第一指示信息用于指示该第一IAB节点连接的IAB donor改变。
在本申请实施例第七方面的一种具体的实现方式中，
该第一指示信息携带在RRC重建立消息中；或，
该第一指示信息携带在RRC重配置消息中。
在本申请实施例第七方面的一种具体的实现方式中，该处理单元还用于：确定与该IAB donor之间的F1连接建立/重建立完成或F1连接已经恢复。
在本申请实施例第七方面的一种具体的实现方式中，该收发单元，还用于：
接收来自该目标IAB donor的该目标IAB donor的IP地址信息。
在本申请实施例第七方面的一种具体的实现方式中，该目标IAB donor的IP地址信息携带在RRC重配置消息中。
在本申请实施例第七方面的一种具体的实现方式中，该收发单元，具体用于：
接收来自该目标IAB donor的第一配置信息，该第一配置信息包括以下至少一项：
该第一IAB节点的小区的源标识、该第一IAB节点的小区的目标标识、该第一IAB节点的小区的PLMN ID、该第一IAB节点小区的SSB信息或者该第一IAB节点的小区的激活指示信息。
本申请实施例第七方面中，通信装置的组成模块还可以用于执行第三方面的各个可能实现方式中所执行的步骤，具体均可以参阅第三方面，此处不再赘述。
本申请实施例第八方面提供了一种通信装置，该装置为第一IAB节点的子节点，该装置包括：
收发单元，用于接收来自该第一IAB节点的第一信息，该第一信息包括以下至少一项：
该第一IAB节点连接的IAB donor改变的指示信息、RRC重建立的指示信息、RRC重建立的基站的标识信息、RRC重建立的小区的标识信息；
处理单元，用于根据该第一信息触发以下至少一项流程：RRC重建立、F1连接建立或者F1连接重建立。
在本申请实施例第八方面的一种具体的实现方式中，
该第一信息携带在媒体接入控制层的控制单元MAC CE中；或，
该第一信息携带在回传适配协议控制分组数据单元BAP control PDU中。
本申请实施例第八方面中，通信装置的组成模块还可以用于执行第四方面的各个可能实现方式中所执行的步骤，具体均可以参阅第四方面，此处不再赘述。
本申请实施例第九方面提供一种通信装置，其中，该通信装置包括处理器，该处理器与存储器耦合，该存储器用于存储计算机程序或指令，该处理器用于执行存储器中的所述计算机程序或指令，使得前述第一方面或第一方面任意一种可能的实现方式所述的方法被执行。
本申请实施例第十方面提供一种通信装置，其中，该通信装置包括处理器，该处理器与存储器耦合，该存储器用于存储计算机程序或指令，该处理器用于执行存储器中的所述计算机程序或指令，使得前述第二方面或第二方面任意一种可能的实现方式所述的方法被执行。
本申请实施例第十一方面提供一种通信装置，其中，该通信装置包括处理器，该处理器与存储器耦合，该存储器用于存储计算机程序或指令，该处理器用于执行存储器中的所述计算机程序或指令，使得前述第三方面或第三方面任意一种可能的实现方式所述的方法被执行。
本申请实施例第十二方面提供一种通信装置，其中，该通信装置包括处理器，该处理器与存储器耦合，该存储器用于存储计算机程序或指令，该处理器用于执行存储器中的所述计算机程序或指令，使得前述第四方面或第四方面任意一种可能的实现方式所述的方法被执行。
本申请实施例第十三方面提供一种存储一个或多个计算机执行指令的计算机可读存储介质，当计算机执行指令被处理器执行时，该处理器执行如上述第一方面或第一方面任意一种可能的实现方式、或者该处理器执行如上述第二方面或第二方面任意一种可能的实现方式所述的方法、或者该处理器执行如上述第三方面或第三方面任意一种可能的实现方式所述的方法、或者该处理器执行如上述第四方面或第四方面任意一种可能的实现方式所述的方法。
本申请实施例第十四方面提供一种存储一个或多个计算机的计算机程序产品(或称计算机程序)，当计算机程序产品被该处理器执行时，该处理器执行上述第一方面或第一方面任意一种可能实现方式、或者该处理器执行上述第二方面或第二方面任意一种可能的实现方式的方法、或者该处理器执行上述第三方面或第三方面任意一种可能的实现方式的方法、或者该处理器执行上述第四方面或第四方面任意一种可能的实现方式的方法。
本申请实施例第十五方面提供了一种芯片系统，该芯片系统包括处理器，用于支持通信装置实现上述第一方面或第一方面任意一种可能的实现方式、或者支持通信装置实现上述第二方面或第二方面任意一种可能的实现方式中所涉及的功能、或者支持通信装置实现上述第三方面或第三方面任意一种可能的实现方式中所涉及的功能、或者支持通信装置实现上述第四方面或第四方面任意一种可能的实现方式中所涉及的功能。在一种可能的设计中，该芯片系统还可以包括存储器，存储器，用于保存该接入网设备必要的程序指令和数 据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
本申请实施例第十六方面提供了一种通信系统，该通信系统包括上述第五方面至第八方面所示的一个或多个通信装置，或，该通信系统包括上述第九方面至第十二方面所示的一个或多个通信装置。
其中，第五、第九、第十三、第十四、第十五、第十六方面或者其中任一种可能实现方式所带来的技术效果可参见第一方面或第一方面不同可能实现方式所带来的技术效果。
其中，第六、第十、第十三、第十四、第十五、第十六方面或者其中任一种可能实现方式所带来的技术效果可参见第二方面或第二方面不同可能实现方式所带来的技术效果。
其中，第七、第十一、第十三、第十四、第十五、第十六方面或者其中任一种可能实现方式所带来的技术效果可参见第三方面或第三方面不同可能实现方式所带来的技术效果。
其中，第八、第十二、第十三、第十四、第十五、第十六方面或者其中任一种可能实现方式所带来的技术效果可参见第四方面或第四方面不同可能实现方式所带来的技术效果。
从以上技术方案可以看出，本申请实施例具有以下优点：IAB donor获取第一IAB节点与第一IAB节点的源父节点之间的BH RLC CH的配置信息，并向第一IAB节点的目标父节点发送该BH RLC CH的配置信息。其中，在第一IAB节点的父节点由源父节点改变为目标父节点之后，使得该第一IAB节点的目标父节点可以使用该BH RLC CH的配置信息进一步确定与该第一IAB节点之间的BH RLC CH的配置。即在第一IAB节点的目标父节点确定来自IAB donor的BH RLC CH的配置信息可以用于与第一IAB节点之间进行通信时，无需再向该第一IAB节点发送BH RLC CH的配置信息，就可以实现该第一IAB节点通过该第一IAB节点的目标父节点在IAB网络中通信，节省了资源配置的开销；在第一IAB节点的目标父节点确定来自IAB donor的BH RLC CH的配置信息不用于与第一IAB节点之间进行通信时，可以根据该父节点的空口资源生成对应于该第一IAB节点的BH RLC CH的配置信息，也可以实现该第一IAB节点通过该第一IAB节点的目标父节点在IAB网络中通信。从而，该父节点可以根据来自IAB donor的BH RLC CH的配置信息灵活地配置第一IAB节点的通信资源。
附图说明
图1为适用于本申请的技术方案的通信系统的一个架构图；
图2为控制面协议栈的一个示意图；
图3为用户面协议栈的一个示意图；
图4为IAB系统中两条数据回传场景的一个示意图；
图5为控制面协议栈的另一个示意图；
图6为用户面协议栈的另一个示意图；
图7为建立F1场景的一个实现示意图；
图8为Intra-donor-CU切换场景的一个示意图；
图9为Intra-donor-CU重建立流程的一个示意图；
图10-1为本申请实施例中Inter-donor-CU切换场景的一个示意图；
图10-2为本申请实施例中Inter-donor-CU切换场景的另一个示意图；
图10-3为本申请实施例中Inter-donor-CU切换场景的另一个示意图；
图10-4为本申请实施例中Inter-donor-CU切换场景的一个示意图；
图11为本申请实施例中用于接入回传一体化IAB系统中的通信方法的一个示意图；
图12为本申请实施例中用于接入回传一体化IAB系统中的通信方法的另一个示意图；
图13为本申请实施例中用于接入回传一体化IAB系统中的通信方法的另一个示意图；
图14为本申请实施例中用于接入回传一体化IAB系统中的通信方法的另一个示意图；
图15为本申请实施例中用于接入回传一体化IAB系统中的通信方法的另一个示意图；
图16为本申请实施例中通信装置的一个示意图；
图17为本申请实施例中通信装置的另一个示意图；
图18为本申请实施例中Inter-donor的一个示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。
其中，在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B。本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
首先，对本申请实施例中的部分用语进行解释说明，以便于本领域技术人员理解。
1、通信系统：包括但不限于窄带物联网(narrow band-internet of things，NB-IoT)系统、无线局域网(wireless local access network,WLAN)系统、LTE系统、下一代5G移动通信系统或者5G之后的通信系统，例如NR、设备到设备(device to device，D2D)通信系统等。
2、网络设备：或称为基站，包括但不限于演进型节点B(evolved node base，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station,BTS)、家庭基站(home evolved NodeB，或home node B，HNB)、基带单元(baseband Unit，BBU)、演进的(evolved LTE,eLTE)基站、NR基站(next generation node B,gNB)等。
3、终端设备：包括但不限于用户设备(user equipment,UE)、移动台、接入终端、用户单元、用户站、移动站、远方站、远程终端、移动设备、终端、无线通信设备、用户代理、无线局域网(wireless local access network,WLAN)中的站点(station,ST)、蜂窝电话、无绳电话、会话启动协议(session initiation protocol,SIP)电话、无线本地环路 (wireless local loop，WLL)站、个人数字处理(personal digital assistant,PDA)、具有无线通信功能的手持设备、计算设备、连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、未来5G网络中的移动台以及未来演进的公共陆地移动网络(public land mobile network,PLMN)网络中的终端设备等中的任意一种。
4、无线回传节点(也可以称为IAB节点)：用于为无线接入无线回传节点的节点(例如，终端)提供无线回传(backhaul)服务。其中，无线回传服务是指通过无线回传链路提供的数据和/或信令回传服务。无线回传节点可以是IAB节点，也可以是中继节点(relay)，本申请的方案不做限定，可以是一种具有转发功能的上述基站或者终端设备中的一种，也可以是一种独立的设备形态。在包含无线回传节点的网络(以IAB网络为例进行说明)中，无线回传节点可以为终端提供无线接入服务，并通过无线回传链路连接到宿主基站(donor gNB)传输用户的业务数据。
示例性的，无线回传节点还可以是用户驻地设备(customer premises equipment，简称CPE)、家庭网关(residential gateway，简称RG)等设备。该情况下，本申请实施例提供的方法还可以应用于家庭连接(home access)的场景中。
进一步地，下面对IAB系统中涉及到的概念作简单介绍。
链路：是指一条路径中的两个相邻节点之间的路径。
接入链路：终端设备与基站之间，或者终端设备与IAB节点之间，或者终端设备与宿主节点之间，或者终端设备与宿主DU之间的链路。或者，接入链路包括某个IAB节点作为普通终端设备角色时和它的父节点进行通信时所使用的无线链路。IAB节点作为普通终端设备角色时，不为任何子节点提供回传服务。接入链路包括上行接入链路和下行接入链路。本申请中，终端设备的接入链路为无线链路，故接入链路也可被称为无线接入链路。
回传链路：IAB节点作为无线回传节点时与父节点之间的链路，或者IAB节点与父节点之间的链路。IAB节点作为无线回传节点时，为子节点提供无线回传服务。回传链路包括上行回传链路，以及下行回传链路。本申请中，IAB节点与父节点之间的回传链路为无线链路，故回传链路也可被称为无线回传链路。
父节点与子节点：每个IAB节点将为其提供无线接入服务和/或无线回传服务的相邻节点视为父节点(parent node)。相应地，每个IAB节点可视为其父节点的子节点(child node)。
可替换地，子节点也可以称为下级节点或者下游节点，父节点也可以称为上级节点或者上游节点。
接入IAB节点：是指终端接入的IAB节点，或者说为终端设备提供接入服务的IAB节点。
中间IAB节点：是指为其它IAB节点(例如，接入IAB节点或其它中间IAB节点)提供无线回传服务的IAB节点，或者说为接入IAB节点和IAB宿主之间路径上的IAB节点。
F1接口、F1接口的协议层：F1接口是指IAB节点的DU部分和宿主节点(或donor-CU)之间的逻辑接口，F1接口也可以称为F1*接口，支持用户面以及控制面。F1接口的协议层是指在F1接口上的通信协议层。
示例性的，F1接口的用户面协议层可以包括IP层、UDP层、GTP-U层中的一个或多个。
示例性的，F1接口的控制面协议层可以包括IP层、SCTP层、F1AP层中的一个或多个。
本申请中所有节点、消息的名称仅仅是为了描述方便而设定的名称，在实际网络中的名称可能不同，不应该理解本申请限定各种节点、消息的名称。相反，任何具有和本申请中用到的节点或消息具有相同或类似功能的名称都视作本申请的方法或等效替换，都在本申请的保护范围之内，以下不再赘述。
请参阅图1，以网络设备为gNB为例。在第三代合作伙伴计划(3rd generation partnership project，3GPP)Rel-15NR中，gNB可以采用分布式单元(central Unit，CU)-集中式单元(distributed Unit，DU)分离架构，即：下一代无线接入网络(next generation radio access network，NG RAN)中的gNB由1个gNB-CU以及1个或者多个gNB-DU组成，其中，一个gNB-DU仅能连接到一个gNB-CU，且gNB-CU与gNB-DU之间通过F1接口相连，gNB-CU与5GC(5G核心网)之间通过下一代(next generation，NG)接口相连，如图1所示。
进一步地，以终端设备为UE为例，UE可以通过图1所示gNB-DU接入gNB-CU，即：与UE对等的物理(physical，PHY)层/媒介接入控制(medium access control，MAC)层/无线链路控制(radio link control，RLC)层功能位于gNB-DU上，与UE对等的分组数据汇聚协议(packet data convergence protocol，PDCP)层/业务数据适应协议(Service Data Adaptation Protocol，SDAP)层/无线资源控制(radio resource control，RRC)层功能位于gNB-CU上。具体如图2和图3所示。
请参阅图2，对于控制面数据而言，上行(uplink，UL)方向上，gNB-DU将UE生成的RRC消息封装在F1接口的F1AP消息中发送到gNB-CU；DL方向上，gNB-CU将RRC消息封装在F1接口应用层协议(F1 application protocol，F1AP)消息中发送到gNB-DU，gNB-DU从F1AP消息中提取出RRC消息映射到Uu接口对应的信令无线承载(signaling radio bearer，SRB)(SRB0/SRB1/SRB2)上发送给UE。
请参阅图3，对于用户面数据而言，UL方向上，gNB-DU将从Uu接口数据无线承载(data radio bearer，DRB)上收到的UE数据包映射到对应的通用分组无线服务隧道协议(general packet radio service tunneling protocol，GTP)隧道中发送到gNB-CU；下行(download，DL)方向上，gNB-CU将UE数据包映射到对应的GTP隧道中发送到gNB-DU，gNB-DU从GTP隧道中提取出UE数据包，并将该UE数据包映射到Uu接口对应的DRB上发送给UE。
此外，在3GPP Rel-15的接入回转一体化(integrated access and backhaul，IAB)中，还引入了IAB node(称为IAB节点)和IAB donor(称为IAB宿主节点，或者宿主IAB节点)两种类型的节点。其中，IAB donor可以是gNB。
其中，宿主节点(IAB donor)可以是一个具有完整基站功能的接入网网元，还可以是集中式单元(centralized unit，CU)和分布式单元(distributed unit，DU)分离的形态，即宿主节点由宿主基站的集中式单元和宿主基站的分布式单元组成。本申请实施例中，宿主节点的集中式单元也称为IAB donor CU(也可称作donor CU，或直接称为CU)。宿主节点的分布式单元也称为IAB donor DU(或称作donor DU)。其中donor CU还有可能是控制面(control plane，CP)(本申请实施例中简称为CU-CP)和用户面(user plane，UP)(本申 请实施例中简称为CU-UP)分离的形态。例如CU可由一个CU-CP和一个或多个CU-UP组成。
请参阅图4，以两跳数据回传场景为例(回传简称BH)，在图4中，IAB网络采用CU-DU分离架构，即：IAB donor由IAB donor-CU(简称donor-CU)和IAB donor-DU(简称donor-DU)两部分组成，IAB node由IAB node-MT(简称IAB-MT)和IAB node-DU(简称IAB-DU)两部分组成。其中，IAB node-MT又可以称为IAB node-UE(简称IAB-UE)。
其中，对于IAB donor而言，donor-DU与gNB-DU的功能类似，donor-CU与gNB-CU的功能类似。对于IAB节点而言，IAB-DU与gNB-DU的功能类似，用于为其子节点提供接入服务，其中，IAB-DU的子节点可以是UE，也可以是其他IAB节点。IAB-MT具有UE的功能，用于为共站IAB-DU(即该IAB-DU和IAB-MT属于同一个IAB节点)的子节点提供数据回传。
进一步的，IAB节点又可以分为接入IAB节点和中间IAB节点，即：UE接入的IAB节点称为接入IAB节点，接入IAB节点和IAB donor之间路径上的IAB节点称为中间IAB节点。
如图4所示，UE接入IAB node2，则IAB node2称为UE的接入IAB节点(或者UE的父节点)，UE称为IAB node2的子节点，UE和IAB node2之间的链路称为接入链路。IAB node1称为中间IAB节点，IAB node1的父节点为IAB donor(IAB donor的子节点为IAB node1)，IAB node1的子节点为IAB node2(IAB node2的父节点为IAB node1)。IAB node1和IAB node2之间的链路，以及IAB node1和IAB donor之间的链路均称为回传链路。其中，与UE对等的PHY层、MAC层和RLC层位于接入IAB节点上(即：IAB2-DU)，而与UE对等的PDCP层、SDAP层和RRC层位于donor-CU上。IAB节点均采用L2数据转发的架构，具体的用户面协议栈和控制面协议栈分别如图5和图6所示。
请参阅图5，基于图4所示两跳数据回传的控制面协议栈中，接入IAB节点(即：IAB node2-DU)和IAB donor(即：IAB donor-CU)之间建立F1接口。具体的，如果IAB donor采用CP-UP分离架构，则IAB node2-DU和donor CU-CP之间建立F1-C接口。UE的RRC消息封装在F1-C接口的F1AP消息中传输。
请参阅图6，基于图4所示两跳数据回传的控制面协议栈中，如果IAB donor采用CP-UP分离架构，则IAB node2-DU和donor CU-UP之间建立F1-U接口，并在该F1-U接口上建立每一个UE承载(per UE bearer)的GTP隧道。也就是说，UE和IAB node2-DU之间接口上建立的每一个UE DRB，在IAB2-DU和donor CU-UP之间接口上对应一个单独的GTP隧道。
如图6中所示，在图6所示的协议架构中，各个协议层的含义为：分组数据汇聚协议(packet data convergence protocol，PDCP)层、通用分组无线服务隧道协议用户面(general packet radio service tunneling protocol user plane，GTP-U)层、用户数据报协议(user datagram protocol，UDP)层、网络互连协议(internet protocol，IP)层、L2层(layer 2)、L1层(layer 1)、无线链路控制(radio link control，RLC)层、媒介接入控制(medium access control，MAC)层、物理(physical，PHY)层、无线资源控制(radio resource control，RRC)层、F1应用协议(F1 application protocol，F1AP)层、流控制传输协议(stream control transmission protocol，SCTP)层。其中，L2层为链路层。示例性的，L2层可以为开放式通信系统互联(open systems interconnection，OSI)参考模 型中的数据链路层。L1层可以为物理层。示例性的，L1层可以为OSI参考模型中的物理层。
为了满足终端设备不同类型业务的业务质量要求，无线网络中引入了一个或多个无线承载(radio bearer，RB)，无线承载包括数据无线承载(data radio bearer，DRB)和信令无线承载(signaling raido bearer，SRB)，用于在UE和基站之间传输不同类型的业务数据(包括控制面信令以及用户面数据)。在IAB网络中，RB可以认为是UE和宿主节点之间传输数据的逻辑通道。
其中，每个协议层都会被配置与之对应的协议层实体，例如PDCP实体，RLC实体以及MAC实体等。在上行传输中，UE的数据包(例如IP数据包)在PDCP层经过相应处理之后，依次经过RLC层，MAC层和PHY层发送给接入回传节点(例如图4中所示的IAB node2)的PHY层。
如前文所述，在IAB网络中，IAB节点可以包含DU部分和MT部分。在IAB节点作为无线回传节点时，IAB节点的MT部分在回传链路执行数据转发不需要终端设备在无线接入链路的完整协议栈。其中，当IAB节点作为无线终端的角色时，其与父节点之间的通信链路的协议栈与UE和接入IAB节点之间的无线接入链路的协议栈相同，其与宿主CU之间的协议栈与UE和宿主CU之间的协议栈相同。
类似于3GPP Rel-15NR，在R16 IAB中，一个IAB-DU也只能连接到一个IAB donor-CU建立F1连接。以IAB节点直接连接到IAB donor的场景为例进行说明，如下图7所示，包括如下步骤。
步骤1.IAB-MT通过IAB donor接入网络(即：初始接入)后，可以通过接入的IAB donor从操作、管理和维护(operations,administration and maintenance，OAM)服务器获取IAB-DU的配置信息，包括以下至少一种信息：IAB-DU的标识(IAB-DU id、IAB-DU name)、IAB-DU的小区信息(IAB-DU小区的物理小区标识(physical cell identifier，PCI)、小区的小区身份标识(cell identity)、小区的同步信号/物理广播信道块(synchronization signal/physical broadcast channel block，SS/PBCH block或SSB)信息)、IAB-DU的F1接口的对端网络互连协议(internet protocol，IP)地址(IAB donor-CU的IP地址)。
此外，IAB-DU还可以通过OAM获取IAB-DU的F1接口的本端IP地址，或者，IAB-DU通过IAB-MT向接入的IAB donor请求获取IAB-DU的F1接口的本端IP地址。
步骤2.IAB-DU使用获取到的IP地址，IAB-DU与IAB donor-CU建立TNLA关联。
步骤3.IAB-DU通过建立的TNLA关联向IAB donor-CU触发F1配置请求(F1 Setup Request)消息，将其从OAM获取的配置信息上报给IAB donor-CU，以便与IAB donor-CU建立F1连接。
步骤4.IAB donor-CU向IAB-DU发送F1配置响应(F1 Setup Response)消息，激活指定的IAB-DU小区，以便启动IAB-DU功能，例如：激活的IAB-DU小区开始进行系统广播。
步骤5.如果IAB-DU的IP地址更新，则使用新IP地址与IAB donor-CU建立新TNLA关联。
步骤6.IAB-DU通过该新建TNLA关联向IAB donor-CU触发gNB-DU配置更新(Configuration Update)流程，即步骤6a中IAB-DU向IAB donor-CU发送gNB-DU  Configuration Update，和步骤6bIAB donor-CU向IAB-DU发送gNB-DU Configuration Update响应(Acknowledge)，以便通知IAB donor-CU进行TNLA关联的更新。可选的，还可以通过该流程来删除IAB-DU和IAB donor-CU之间的旧TNLA关联。
此外，当前在R16 IAB中，只考虑宿主CU内(Intra-donor-CU)的重建立场景，没有考虑跨宿主CU的(Inter-donor-CU)重建立场景。
请参阅图8，Intra-donor-CU重建立场景中，如果IAB-MT检测到与IAB donor-DU1之间的链路发生RLF，则IAB-MT将执行小区选择，通过RRC重建立到IAB donor-DU2的小区来进行链路的恢复，其中，IAB donor-DU1和IAB donor-DU2连接到同一个IAB donor-CU。
如图8所示，IAB节点包括IAB-MT和IAB-DU两部分，本申请实施例中，可以将检测到无线链路失败(radio link failure，RLF)的IAB节点，或者，检测到链路RLF并尝试恢复的IAB节点，统称为恢复IAB节点(recover IAB节点)。其中，恢复IAB节点的IAB-MT部分，简称恢复IAB-MT，恢复IAB节点的IAB-DU部分，简称恢复IAB-DU。
类似于UE，链路RLF之前，恢复IAB-MT连接到源IAB宿主，即：通过IAB donor-DU1连接到IAB donor-CU。链路RLF之后，恢复IAB-MT通过RRC重建立到目标IAB宿主来进行链路的恢复，即：通过IAB donor-DU2连接到IAB donor-CU。
由于恢复IAB-MT触发RRC重建立流程来恢复链路前后，IAB donor-CU不变，则恢复IAB-DU和IAB donor-CU之间的F1连接维持不变。
此外，由于恢复IAB-DU的IP地址由IAB donor-DU或者IAB donor-CU分配，即：恢复IAB-DU的IP地址需要与IAB donor-DU的IP地址属于同一网段或者具有相同的网络前缀，因此，一旦IAB donor-DU改变，则恢复IAB-DU的IP地址改变。
请参阅图9，以多跳场景(恢复IAB节点和IAB donor-DU之间存在至少一个其他IAB节点)为例。在图9所示IAB intra-CU重建立流程中，源路径(initial Path)指的是源父节点和源IAB donor-DU之间的传输路径，其中，intial Path包括源父节点(Initial ParrentIAB-node)、源路径中的中间节点(Intermediate hopIAB-node onthe initial path)、源IAB-donor-DU(Initial IAB-donor-DU)；目标路径/恢复路径(Recovery Path)指的是目标父节点和目标IAB donor-DU之间的传输路径，其中，Recovery Path包括目标父节点(New ParrentIAB-node)、目标路径中的中间节点(Intermediate hopIAB-node onthe New path)、目标IAB-donor-DU(New IAB-donor-DU)。具体的切换流程如图9所示。
在步骤1之前，IAN-donor-CU可以与UE之间，通过源路径交互上行用户数据(Uplink user data)和下行用户数据(Downlink user data)。
步骤1.恢复IAB-MT检测到源路径上发生BH RLF,即在原始路径上测定BH RLF(Determination of BH RLF on initial path)。
步骤2.恢复IAB-MT触发RRC重建立到新父节点来进行链路的恢复，即在目标IAB-donor-DU上进行RRC重建(RRC Re-establishment at recovery parent IAB-node DU)。该流程中，IAB-donor-CU可以通过RRC消息向恢复IAB-MT提供新TNL地址，进一步的，IAB-donor-CU还可以通过RRC重配置消息向恢复IAB-MT提供默认UL配置，包括：配置目标路径上用于UL F1-C/non-F1业务传输的默认BH RLC channel、默认回传适配协议路由 ID(backhaul adaptation protocol routing ID，BAP routing ID)等。
步骤3.剩余部分流程沿用intra-CU切换流程中的步骤11～15(Same as steps 11-15of intra-CU topology adaptation procedure)。其中，步骤11～15的实现过程可以包括如下步骤。
步骤11：IAB-donor-CU为恢复IAB-MT的目标路径配置对应的BH RLC channel和BAP路由配置，以及为恢复IAB-MT在目标IAB donor-DU上配置DL承载映射。
步骤12：F1-C连接更新使用恢复IAB-DU的新IP地址。IAB-donor-CU向恢复IAB-DU更新每个GTP隧道关联的UL BH information信息，即所有F1-U隧道更新使用恢复IAB-DU的新IP地址。
步骤13：IAB-donor-CU向恢复IAB-MT的源父节点发送UE上下文释放命令(UE Context Release Command)消息。
步骤14：恢复IAB-MT的源父节点释放恢复IAB-MT的上下文，并向IAB-donor-CU发送UE上下文释放完成(UE Context Release Complete)消息作为响应。
步骤15：IAB-donor-CU释放恢复IAB-MT的源父节点和源IAB donor-DU之间源路径上的BH RLC channel和回传适配协议(backhaul adaptation protocol，BAP)路由配置信息。
如图8和图9所示Intra-donor-CU的RRC重建立场景中，恢复IAB节点所连接的父节点会发生改变，即由IAB donor-DU1改变为IAB donor-DU2。此外，由于在实际通信过程中两个通信节点之间的链路质量会发生改变，例如切换失败、无线链路失败RLF、完整性保护失败、RRC重配置失败等情况发生时，都可能导致IAB节点所连接的父节点发生改变，即该IAB节点释放与第一IAB节点的源父节点之间的连接，并与目标父节点之间建立新的连接。其中，该源父节点和目标父节点可以是IAB节点与IAB donor之间的中间IAB节点，也可以是IAB donor中的IAB donor DU。
然而，在IAB网络中，IAB节点所连接的父节点发生改变时，如何灵活地配置IAB节点的通信资源是一个亟待解决的问题。
此外，当前的IAB网络中，仅考虑Intra-donor-CU的RRC重建立场景，即IAB donor-CU不改变，因此，恢复IAB-DU的小区配置信息不改变，并且恢复IAB-DU和IAB donor-CU之间的F1连接保持不变，同理，恢复IAB节点的子节点(例如：其他IAB节点)的小区配置信息也不改变，并且恢复IAB节点的子节点和IAB donor-CU之间的F1连接也保持不变。
可是，Inter-donor-CU的RRC重建立场景也是一种典型的场景，示例性地，下面将通过图示对本申请实施例中Inter-donor-CU的RRC重建立场景进行介绍。
请参阅图10-1，为Inter-donor-CU的RRC重建立场景的一个示例。在该场景中，触发以下至少一项流程：RRC重建立、F1连接建立或者F1连接重建立流程之前，恢复IAB-MT通过源IAB donor-DU(如图10-1的IAB donor-DU1)连接到源IAB donor-CU(如图10-1的IAB donor-CU1)；触发以下至少一项流程：RRC重建立、F1连接建立或者F1连接重建立流程之后，恢复IAB-MT通过目标IAB donor-DU(如图10-1的IAB donor-DU2)连接到目标IAB donor-CU(如图10-1的IAB donor-CU2)。
请参阅图10-2，为Inter-donor-CU的RRC重建立场景的另一个示例。在该场景中， 对图10-1所示场景进一步扩展，即：恢复IAB节点和IAB donor-DU之间存在至少一个其他IAB node。如图10-2所示：触发以下至少一项流程：RRC重建立、F1连接建立或者F1连接重建立流程之前，IAB node1和IAB node2为恢复IAB节点和源IAB donor-DU(如图10-2的IAB donor-DU1)之间存在的其他IAB节点(即可称为中间IAB节点)，IAB node3和IAB node4为恢复IAB节点和目标IAB donor-DU(如图10-2的IAB donor-DU2)之间存在的其他IAB节点(即可称为中间IAB节点)。
请参阅图10-3，为Inter-donor-CU的RRC重建立场景的另一个示例。在该场景中，对图10-1和图10-2所示场景进一步扩展。具体为情况1(Case1)：即触发以下至少一项流程：RRC重建立、F1连接建立或者F1连接重建立流程之前，恢复IAB-MT直接连接到源IAB donor-DU；触发以下至少一项流程：RRC重建立、F1连接建立或者F1连接重建立流程之后，恢复IAB-MT通过至少一个其他IAB node连接到目标IAB donor-DU。
请参阅图10-4，为Inter-donor-CU的RRC重建立场景的另一个示例。在该场景中，对图10-1和图10-2所示场景进一步扩展。具体为情况2(Case2)：即触发以下至少一项流程：RRC重建立、F1连接建立或者F1连接重建立流程之前，恢复IAB-MT通过至少一个其他IAB node连接到源IAB donor-DU；触发以下至少一项流程：RRC重建立、F1连接建立或者F1连接重建立流程之后，恢复IAB-MT直接连接到目标IAB donor-DU。
在上述示例中，恢复IAB节点的子节点可以是UE，也可以是其他IAB节点。此外，上述RRC重建立场景下，恢复IAB-MT和源IAB-donor CU(如图中IAB donor-CU1)之间路径称为源路径(source path)，恢复IAB-MT和目标IAB donor-CU(如图中IAB donor-CU2)之间的路径称为目标路径或者恢复路径(target path)。
显然，在Inter-donor-CU所示场景下，IAB donor-CU将发生改变，从而导致恢复IAB-DU的F1连接发生改变(当前只支持一个DU连接到一个CU建立一个F1连接)，即：触发以下至少一项流程：RRC重建立、F1连接建立或者F1连接重建立流程之前，恢复IAB-DU与源IAB donor-CU之间建立F1连接；触发以下至少一项流程：RRC重建立、F1连接建立或者F1连接重建立流程之后，恢复IAB-DU需要与目标IAB donor-CU之间建立/重建立F1连接，并释放与源IAB donor-CU之间的F1连接。同理，恢复IAB节点的后代节点(例如：其他IAB节点)也需要建立/重建立和目标IAB donor-CU之间的F1连接，而当前IAB节点并不支持更换F1连接的流程。
综上所述，目前在IAB网络中，至少存在以下问题：
问题1、IAB节点所连接的父节点发生改变时，即该IAB节点释放与源父节点之间的连接，并与目标父节点之间建立新的连接，由于该IAB节点所连接的父节点发生改变，导致该IAB节点和目标父节点之间的链路资源需要重新配置，如何灵活地配置IAB节点的通信资源是一个亟待解决的问题。
问题2、IAB节点检测到与源父节点之间的链路发生RLF后将触发RRC重建立流程，可是由于该IAB节点和其子节点之间的链路质量还很好，将导致子节点无法触发RRC重建立流程而无法正常工作。而当前的IAB节点并不支持更换F1连接的流程，因此，如何在Inter-donor-CU场景下支持更换F1连接以及如何通知其子节点触发RRC重建立流程也是 一个亟待解决的技术问题。
为了解决上述问题，本申请实施例提供了一种用于接入回传一体化IAB系统中的通信方法，请参阅图11，该用于接入回传一体化IAB系统中的通信方法包括如下步骤。
S101、IAB donor获取BH RLC CH的配置信息。
本实施例中，IAB donor在步骤S101中获取BH RLC CH的配置信息。其中，该BH RLC CH的配置信息为第一接入回传一体化IAB节点与该第一IAB节点的源父节点之间的BH RLC CH的配置信息。
具体地，IAB donor在步骤S101中获取得到的该BH RLC CH的配置信息可以包括以下至少一项：该BH RLC CH的标识、该BH RLC CH对应的逻辑信道标识、无线链路控制信道RLC的配置信息或者逻辑信道的配置信息。
在步骤S101中，该BH RLC CH的配置信息为第一IAB节点与该第一IAB节点的源父节点之间的BH RLC CH的配置信息，其中，第一IAB节点的父节点可能由于多种不同的场景导致发生改变。
在一种可能的实现方式中，如图8和图9所示Intra-donor-CU的RRC重建立场景中。恢复IAB节点(即第一IAB节点)所连接的父节点会发生改变，即由IAB donor-DU1改变为IAB donor-DU2。此外，由于在实际通信过程中两个通信节点之间的链路质量会发生改变，例如切换失败、无线链路失败RLF、完整性保护失败、RRC重配置失败等情况发生时，都可能导致IAB节点所连接的父节点会发生改变，即该IAB节点释放与该IAB节点的源父节点之间的连接，并与目标父节点之间建立新的连接。
具体地，在该实现方式中，由于第一IAB节点的IAB donor并未发生变化，因此，IAB donor在步骤S101中可以通过设备自身的缓存数据，或者是历史数据确定出第一IAB节点与该第一IAB节点的源父节点之间的BH RLC CH的配置信息。
在另一种可能的实现方式中，如图10-1、图10-2、图10-3、图10-4所示Inter-donor-CU的RRC重建立场景中。恢复IAB-MT(即第一IAB节点的MT部分)通过源IAB donor-DU(如图10-1、如图10-2、如图10-3、如图10-4的IAB donor-DU1)连接到源IAB donor-CU(如图10-1、图10-2、图10-3、图10-4的IAB donor-CU1)；触发以下至少一项流程：RRC重建立、F1连接建立或者F1连接重建立流程之后，恢复IAB-MT通过目标IAB donor-DU(如图10-1、如图10-2、如图10-3、如图10-4的IAB donor-DU2)连接到目标IAB donor-CU(如图10-1、图10-2、图10-3、图10-4的IAB donor-CU2)。
具体地，在该实现方式中，由于第一IAB节点的IAB donor发生变化，即由源IAB donor改变为目标IAB donor。其中，该IAB donor可以为目标IAB donor，第一IAB节点的目标父节点与该目标IAB donor连接，第一IAB节点的源父节点与源IAB donor连接。其中，第一IAB节点的源父节点连接的IAB donor为源IAB donor，第一IAB节点的目标父节点连接的IAB donor为目标IAB donor，使得该方案可以应用于第一IAB节点连接的IAB donor发生改变的场景，例如跨CU的(Inter-donor-CU)RRC重建立场景。此时，由于第一IAB节点的IAB donor发生变化，因此，IAB donor在步骤S101中可以通过第一IAB节点的源IAB donor所发送的消息，确定出第一IAB节点与该第一IAB节点的源父节点之间的BH RLC  CH的配置信息。
值得注意的是，本申请中提到的IAB donor发生变化或者IAB donor改变具体指的是IAB donor-CU发生变化或者改变。
S102、IAB donor向第一IAB节点的目标父节点发送BH RLC CH的配置信息。
本实施例中，IAB donor在步骤S102中向第一IAB节点的目标父节点发送步骤S101中获取得到的BH RLC CH的配置信息，相应的，第一IAB节点的目标父节点在步骤S102中接收来自IAB donor的BH RLC CH的配置信息。
需要说明的是，本申请实施例中，第一IAB节点的目标父节点可以是第一IAB节点与IAB donor之间路径上的中间IAB节点，也可以是IAB donor中的IAB donor DU，此处不做限定。此外，在本实施例及后续实施例中，第一IAB节点可以通过恢复IAB节点来表示，相应的，第一IAB节点所包含的MT部分和DU部分可以分别由恢复IAB-MT和恢复IAB-DU表示。
在一种具体的实现方式中，如果IAB donor和第一IAB节点的应用场景为图10-1、图10-2、图10-3、图10-4所示Inter-donor-CU的RRC重建立场景时，步骤S102中的BH RLC CH的配置信息可以携带于源IAB donor向目标IAB donor所发送的消息中。
S103、第一IAB节点的目标父节点根据BH RLC CH的配置信息确定与第一IAB节点之间的BH RLC CH的配置。
本实施例中，第一IAB节点的目标父节点在步骤S103中根据BH RLC CH的配置信息确定与第一IAB节点之间的BH RLC CH的配置。
其中，在第一IAB节点的父节点由源父节点改变为目标父节点之后，使得该第一IAB节点的目标父节点在步骤S103中，可以使用该BH RLC CH的配置信息进一步确定与该第一IAB节点之间的BH RLC CH的配置，以实现该第一IAB节点通过该第一IAB节点的目标父节点在IAB网络中通信。即在第一IAB节点的目标父节点确定来自IAB donor的BH RLC CH的配置信息可以用于与第一IAB节点之间进行通信时，无需再向该第一IAB节点发送BH RLC CH的配置信息，就可以实现该第一IAB节点通过该第一IAB节点的目标父节点在IAB网络中通信，从而节省了资源配置的开销。
具体地，第一IAB节点的目标父节点在步骤S103中可以通过多种方式确定第一IAB节点与目标父节点之间的BH RLC CH的配置。例如：当该目标父节点根据该BH RLC CH的配置确定需要占用的空口资源，如果该目标父节点有足够的空口资源，则该目标父节点可以沿用步骤S102接收得到的BH RLC CH的配置。否则，该目标父节点根据自己的空口资源生成对应的BH RLC CH的配置信息。从而，该父节点可以根据来自IAB donor的BH RLC CH的配置信息灵活地配置第一IAB节点的通信资源。
S104、IAB donor通过第一IAB节点的目标父节点向第一IAB节点发送第一指示信息。
本实施例中，IAB donor在步骤S104中通过第一IAB节点的目标父节点向第一IAB节点发送第一指示信息，相应的，第一IAB节点在步骤S104中通过第一IAB节点的目标父节点接收来自IAB donor的第一指示信息。其中，第一指示信息用于指示该第一IAB节点连接的IAB donor改变，或者指示该第一IAB节点连接的IAB-donor-CU改变。
在一种具体的实现方式中，该IAB donor通过该目标父节点向该第一IAB节点发送第一指示信息，该第一指示信息用于指示该第一IAB节点连接的IAB donor改变。其中，如果IAB donor和第一IAB节点的应用场景为图10-1、图10-2、图10-3、图10-4所示Inter-donor-CU的RRC重建立场景时，即当该IAB donor为第一IAB节点的目标父节点连接的宿主节点(即目标IAB donor)时，该IAB donor还可以通过第一IAB节点的目标父节点向第一IAB节点发送该第一指示信息，以使得该第一IAB节点确定该第一IAB节点的宿主节点发生改变，后续可以与目标宿主节点在IAB网络中通信。其中，步骤S104中的BH RLC CH的配置信息可以携带于目标IAB donor向第一IAB节点所发送的消息中。
S105、IAB donor通过第一IAB节点的目标父节点向第一IAB节点发送IAB donor的IP地址。
本实施例中，IAB donor在步骤S105中通过第一IAB节点的目标父节点向第一IAB节点发送IAB donor的IP地址，相应的，第一IAB节点在步骤S105中通过该第一IAB节点的目标父节点接收来自IAB donor的IAB donor的IP地址。
在一种具体的实现方式中，该IAB donor通过该目标父节点向该第一IAB节点发送该IAB donor的IP地址信息。其中，如果IAB donor和第一IAB节点的应用场景为图10-1、图10-2、图10-3、图10-4所示Inter-donor-CU的RRC重建立场景时，即当该IAB donor为第一IAB节点的目标父节点连接的宿主节点(即目标IAB donor)时，该IAB donor还可以通过第一IAB节点的目标父节点向第一IAB节点发送该目标IAB donor的IP地址信息，以便该第一IAB节点向该IP地址信息指示的目标IAB donor触发F1连接建立/重建立流程。其中，步骤S105中的IAB donor的IP地址可以携带于目标IAB donor向第一IAB节点所发送的消息中。
S106、第一IAB节点确定与IAB donor之间RRC重建立完成。
本实施例中，第一IAB节点在步骤S107中确定与IAB donor之间RRC重建立完成，并在步骤S106之后，执行步骤S107和步骤S108。
S107、IAB donor通过第一IAB节点的目标父节点向第一IAB节点发送第一配置信息。
本实施例中，IAB donor在步骤S107中通过第一IAB节点的目标父节点向第一IAB节点发送第一配置信息，相应的，第一IAB节点在步骤S107中通过第一IAB节点的目标父节点接收来自IAB donor的第一配置信息。
具体地，在步骤S106中第一IAB节点可以在步骤S107中确定与IAB donor之间RRC重建立完成，相应的，IAB donor也可以在步骤S106中确定与第一IAB节点之间RRC重建立完成。并且，IAB donor可以在确定与第一IAB节点之间RRC重建立完成之后，执行步骤S107，即通过第一IAB节点的目标父节点向第一IAB节点发送第一配置信息。
其中，第一配置信息包括以下至少一项：该第一IAB节点的小区的源标识、该第一IAB节点的小区的目标标识、该第一IAB节点的小区的PLMN ID、该第一IAB节点小区的SSB信息或者该第一IAB节点的小区的激活指示信息。其中，该第一IAB节点的小区的源标识指的是该第一IAB节点通过源父节点连接到源IAB donor下的小区的标识。该第一IAB节点的小区的目标标识指的是该第一IAB节点通过目标父节点连接到目标IAB donor下的小 区的标识。
在一种具体的实现方式中，如果IAB donor和第一IAB节点的应用场景为图10-1、图10-2、图10-3、图10-4所示Inter-donor-CU的RRC重建立场景时，即当该IAB donor为第一IAB节点的目标父节点连接的宿主节点(即目标IAB donor)时，该IAB donor还可以通过第一IAB节点的目标父节点向第一IAB节点发送第一配置信息，使得该第一IAB节点根据该第一配置信息更新该第一IAB节点的网络配置，后续可以使用更新后的网络配置在IAB网络中通信。
S108、第一IAB节点向第一IAB节点的子节点发送第一信息。
本实施例中，第一IAB节点在步骤S108中向第一IAB节点的子节点发送第一信息，相应的，第一IAB节点的子节点在步骤S108中接收来自第一IAB节点的第一信息。其中，该第一信息包括以下至少一项：该第一IAB节点连接的IAB donor改变的指示信息、RRC重建立的指示信息、RRC重建立的基站的标识信息、RRC重建立的小区的标识信息。
其中，该第一IAB节点连接的IAB donor改变的指示信息指的是donor-CU改变的指示信息。
需要说明的是，本申请实施例中，第一IAB节点为该子节点的父节点，其中，第一IAB节点的子节点可以为IAB节点，也可以是终端设备(如UE)，此处不做限定。
可选地，第一IAB节点可以根据步骤S104获取得到的第一指示信息向子节点发送该第一信息。
在一种具体的实现方式中，该第一信息携带在媒体接入控制层的控制单元MAC CE中；或，该第一信息携带在BAP control PDU中。
S109、第一IAB节点的子节点根据第一信息触发以下至少一项流程：RRC重建立、F1连接建立或者F1连接重建立。
本实施例中，第一IAB节点的子节点根据步骤S108中接收得到的第一信息触发以下至少一项流程：RRC重建立、F1连接建立或者F1连接重建立。
在一种具体的实施方式中，当步骤S108该第一IAB节点向该第一IAB节点的子节点发送第一信息之前，若该第一IAB节点与该IAB donor之间的F1连接建立未完成(或F1连接重建立未完成)时。在步骤S109中，第一IAB节点的子节点根据该第一信息触发RRC重建立或者F1连接建立/重建立时，即向第一IAB节点发送RRC重建立的请求消息或者F1连接建立/重建立的请求消息时，第一IAB节点可以缓存收到的请求消息，并在确定第一IAB节点与该IAB donor之间的F1连接建立/重建立完成之后，再向该IAB donor发送缓存的请求消息，以使得该子节点与该IAB donor之间的RRC重建立完成或者F1连接建立/重建立完成。
在另一种具体的实现方式中，在步骤S108该第一IAB节点向该第一IAB节点的子节点发送第一信息之前，该第一IAB节点还可以确定与该IAB donor之间的F1连接建立/重建立完成。即，第一IAB节点在确定与该IAB donor之间的F1连接建立/重建立完成之后，再向第一IAB节点的子节点发送第一信息，使得该子节点在步骤S109中可以通过该第一IAB节点与IAB donor之间已建立/重建立的F1连接，根据该第一信息触发向IAB donor 进行RRC重建立或者F1连接建立/重建立。
基于上述技术方案，第一IAB节点在确定与目标IABdonor之间的RRC重建立完成之后，即第一节点的宿主节点改变为该目标IABdonor之后，该第一IAB节点向第一IAB节点的子节点发送第一信息，使得该第一IAB节点的子节点根据该第一信息触发与目标IABdonor之间的RRC重建立和/或F1连接的建立/重建立，以实现该第一IAB节点的子节点通过该第一IAB节点在IAB网络中通信。即通过上述方案使得第一IAB节点获取到新的配置，并通知后代节点(子节点)触发RRC重建立流程，使得恢复IAB节点执行RRC重建到新IAB宿主后，该恢复IAB节点的后代节点还能正常工作，并与目标IAB donor建立/重建立F1连接。
本申请实施例中，Inter-donor-CU的RRC重建立场景的流程示意图的一个示例可以如图12所示，该RRC重建立流程可以包括如下步骤。
步骤1.当恢复IAB节点(即第一IAB节点)检测到与源父节点之间的链路发生切换失败、无线链路失败RLF、完整性保护失败、RRC重配置失败等情况时，触发RRC重连接。即执行步骤1，恢复IAB-MT(即第一IAB节点的MT部分)通过选择的新父节点(新父节点也可称为目标父节点，目标父节点可以是IAB节点，也可以是目标IAB donor DU)，向目标IAB donor-CU发送RRC重建立请求消息。
可选的，在该RRC重建立请求消息中可以携带恢复IAB-MT在源父节点下的接入小区的物理小区标识PCI，恢复IAB-MT在该接入小区下的标识C-RNTI。
步骤2.目标IAB donor-CU向源IAB donor-CU发送查询UE上下文请求消息(Retrieve UE Context Request)。
可选的，该消息中可以携带恢复IAB-MT在RRC重建立请求消息中携带的PCI和C-RNTI信息之外，还携带IAB-MT执行重建立小区的小区标识Cell Identity以及完整性校验值shortMAC-I。其中，IAB-MT执行重建立小区指的是IAB-MT触发RRC重建立流程中执行小区选择选定的小区。
步骤3.源IAB donor-CU向目标IAB donor-CU发送查询UE上下文响应消息(Retrieve UE Context Response)。
可选的，该消息中可以携带恢复IAB节点的上下文，包括恢复IAB-MT的上下文和恢复IAB-DU的上下文信息。
其中，恢复IAB-MT的上下文包括恢复IAB-MT接入源父节点使用的BH RLC CH的配置(或者恢复IAB-MT与源父节点之间链路上建立的BH RLC CH的配置信息)，包括以下至少一种信息：
BH RLC CH的标识(BH RLC CH ID)、BH RLC CH对应的逻辑信道标识(BH LCH ID)、RLC的配置(RLC-config)、逻辑信道的配置(LCH-config)。
恢复IAB-DU的上下文包括以下至少一种信息：
恢复IAB-DU的标识(IAB-DU id和/或IAB-DU name)、恢复IAB-DU所属基站的标识(gNB ID)、恢复IAB-DU的小区本地标识(cell local ID)、恢复IAB节点的PLMN ID、恢复IAB-DU小区的SSB信息等。
步骤4.目标IAB donor-CU向恢复IAB-MT发送RRC重建立消息。
可选的，该消息中携带donor-CU改变的指示信息，以便在donor-CU改变时恢复IAB-MT能够触发与目标IAB donor-CU建立/重建立F1连接。
步骤5.目标IAB donor-CU向目标父节点IAB-DU发送UE上下文建立请求消息(UE Context Setup Request)。
可选的，该消息中携带恢复IAB-MT接入源父节点使用的BH RLC CH的配置，以便目标父节点决定是否为BH RLC CH分配新的配置。
其中，步骤4和步骤5之间的顺序不限定。
步骤6.目标父节点IAB-DU向目标IAB donor-CU发送UE上下文建立响应消息(UE Context Setup Response)。
步骤7.恢复IAB-MT向目标IAB donor-CU发送RRC重建立完成消息。
其中，步骤5、6与步骤7之间的顺序不限定。
步骤8.目标IAB donor-CU向恢复IAB-MT发送RRC重配置消息，该消息中携带目标IAB donor-CU为恢复IAB节点分配的BAP地址、目标IAB donor-CU为恢复IAB节点在目标路径上新分配的默认BH RLC CH ID和默认路由routing ID、目标IAB donor为恢复IAB节点分配的IP地址。其中，目标路径指的是恢复IAB节点通过目标父节点连接到目标IAB donor之间的路径。
可选的，该消息中还可以携带以下至少一种信息：
目标IAB donor-CU的IP地址、donor-CU改变的指示信息。
此外，为了节省目标IAB donor-CU与IAB-MT之间的信令消耗，donor-CU改变的指示信息可以仅发送一次。可选地，如果步骤4中RRC重建立消息中携带了donor-CU改变的指示信息，则步骤8中的RRC重配置消息中将不会再携带该指示信息。否则，如果步骤4中没有携带该指示信息，则步骤8中将携带该指示信息。
至此，恢复IAB-MT完成与目标IAB donor之间的RRC重建立。
需要说明的是，图12所示流程示意图可以为图11所示实施例的步骤S101中IAB donor获取BH RLC CH的配置信息的一种示例的实现过程，由上述描述可知，除了图12所示实现过程，IAB donor还可以通过其他方式获取BH RLC CH的配置信息。此外，图11所示实施例在步骤S101之后的其它步骤，即图11所示实施例的步骤S102至步骤S108的实现过程，可以在图12所示流程实现过程的基础上进一步实现，也可以不通过图12所示流程实现过程，而基于其它实现过程进一步实现，此处不做具体的限定。
在一种可能的实现方式中，由图12所示流程示意图可知，在图11所示实施例的步骤S101中，该IAB donor获取BH RLC CH的配置信息可以包括：该IAB donor接收来自该源IAB donor的获取用户设备UE上下文响应消息(即图12所示步骤3中的Retrieve UE Context Response)，该获取UE上下文响应消息包括该BH RLC CH的配置信息。即，当该IAB donor为第一IAB节点的目标父节点连接的宿主节点(即目标IAB donor)时，该IAB donor可以是通过该第一IAB节点的源父节点连接的宿主节点所发送的获取用户设备UE上下文响应消息中获取得到BH RLC CH的配置信息。
在一种可能的实现方式中，在图11所示实施例的步骤S102中IAB donor向第一IAB 节点的目标父节点发送BH RLC CH的配置信息可以通过图12所示步骤5实现，即通过UE上下文建立请求消息(UE Context Setup Request)实现BH RLC CH的配置信息的发送过程与接收过程。
在一种可能的实现方式中，在图11所示实施例的步骤S104中IAB donor通过第一IAB节点的目标父节点向第一IAB节点发送第一指示信息，该第一指示信息具体可以是图12中步骤4和步骤8中所示的donor-CU改变的指示信息。从而，步骤S104可以通过图12所示步骤4实现，即通过RRC重建立消息实现第一指示信息的发送过程和接收过程；此外，也可以通过图12所示步骤8实现，即通过RRC重配置消息实现第一指示信息的发送过程和接收过程。
在一种可能的实现方式中，在图11所示实施例的步骤S105中IAB donor通过第一IAB节点的目标父节点向第一IAB节点发送IAB donor的IP地址。如，通过图12所示步骤8实现，即通过RRC重配置消息实现IAB donor的IP地址的发送过程和接收过程。其中，当步骤S104中第一指示信息也通过图12所示步骤8实现，即通过RRC重配置消息实现时，该第一指示信息可以与步骤S105中的IAB donor的IP地址携带于同一条消息中，即两者均携带于该RRC重配置消息中。
在一种可能的实现方式中，如果IAB donor和第一IAB节点的应用场景为图10-1、图10-2、图10-3、图10-4所示Inter-donor-CU的RRC重建立场景时，即当该IAB donor为第一IAB节点的目标父节点连接的宿主节点(即目标IAB donor)时，该第一IAB节点在图11所示实施例的步骤S106中，可以在与目标IAB donor之间的RRC重建立过程中确定与IAB donor之间RRC重建立完成。即第一IAB节点可以在图12所示步骤7接收到来自目标IAB donor发送的RRC重建立完成消息之后，确定与IAB donor之间RRC重建立完成。
此外，由于在Inter-donor-CU场景下，第一IAB节点的IAB donor发生改变，导致恢复IAB-DU(第一IAB节点中的DU部分)的配置信息需要更新。例如：恢复IAB-DU小区的小区标识Cell identity或者CGI，恢复IAB-DU的PLMN ID，恢复IAB-DU小区的SSB信息等。恢复IAB-DU获取新配置存在两种方式，包括：从OAM服务器获取，从目标IAB donor获取。在图11所示实施例的步骤S107中，IAB donor可以通过多种方式向第一IAB节点发送第一配置信息，下面将通过几种实现方式的示例进行举例描述。
方式一、从OAM服务器获取第一配置信息。
请参阅图13，恢复IAB-MT(第一IAB节点的MT部分)完成与目标IAB donor之间的RRC重建立之后，恢复IAB-DU可以通过目标IAB donor从OAM服务器获取新的配置信息。即：目标IAB donor获取到从OAM服务器发送的新的配置信息后，进一步发送到恢复IAB-DU。也就是说，该场景下，目标IAB donor只是起到中转恢复IAB-DU和OAM服务器之间新的配置信息传输的作用。
恢复IAB-DU的新配置包括以下至少一种信息：IAB-DU小区的标识CGI/Cell identity、IAB-DU小区的PLMN ID、IAB-DU小区的SSB信息。
可选的，该场景下，恢复IAB节点可以通过OAM服务器来获取目标IAB donor-CU的IP地址，而不需要通过图12中的步骤8中的RRC重配置消息来获取(即图12中的step 8 中的RRC重配置消息中不需要携带目标IAB donor-CU的IP地址)。一旦恢复IAB节点获取到新配置后，需要向目标IAB donor触发F1接口的建立/重建立流程。具体恢复IAB节点向目标IAB donor触发F1接口的建立/重建立流程示意图包括如下步骤。
1.恢复IAB-DU使用目标IAB donor为其分配的IP地址，触发与目标IAB donor-CU建立TNLA关联。
2.恢复IAB-DU向目标IAB donor-CU发送F1建立请求消息(F1 Setup Request)，请求建立/重建立该恢复IAB-DU和目标IAB donor-CU之间的F1连接。
3.目标IAB donor-CU向恢复IAB-DU发送F1建立响应消息(F1 Setup Response)。
4.恢复IAB-DU向子节点发送以下至少一种信息(即第一信息)，以便子节点向目标IAB donor触发RRC重建立流程，包括：
donor-CU改变的指示信息、RRC重建立的指示信息、重建立基站的标识(例如gNB ID)、重建立小区的标识(例如PCI)。
其中，donor-CU改变的指示信息(即第一指示信息)，用于指示该第一IAB节点连接的IAB donor改变。RRC重建立的指示信息用于指示子节点触发RRC重建立，以便子节点获知需要执行RRC重建立流程。重建立小区的标识(例如PCI)用于向子节点指示在RRC重建过程中，选择的小区对应的小区标识，以便子节点执行小区选择到对应的重建立小区。重建立基站的标识(例如gNB ID)用于向子节点指示在RRC重建过程中，选择的小区所对应的基站标识，以便子节点执行小区选择到指定基站下的重建立小区(重建立小区对应的基站为该gNB ID标识的基站)。上述信息可以携带在MAC CE中发送，也可以携带在回传适配协议控制分组数据单元(backhaul adaptation protocol control packet data unit，BAP control PDU)中发送。
可选地，在图13所示过程中，步骤4与步骤1或步骤2或步骤3之间的顺序不限定。
方式二：从目标IAB donor获取第一配置信息。
与方式1的不同在于，恢复IAB-DU的新配置信息(即第一配置信息)由目标IAB donor生成后再通知恢复IAB-DU，流程上体现在步骤2和步骤3不同。
作为一种可能的实现方式，如图14所示，恢复IAB-DU通过步骤2来获取新的配置信息。
2.目标IAB donor-CU向恢复IAB-DU发送F1AP请求消息，该请求消息用于建立/重建立恢复IAB-DU和目标IAB donor-CU之间的F1连接。该F1AP请求消息中携带修改恢复IAB-DU小区的信息列表，每个信息列表包含以下至少一种信息：
恢复IAB-DU小区的源标识(例如：源CGI或者源Cell identity)、恢复IAB-DU的新配置、恢复IAB-DU新小区激活指示信息。
该F1AP请求消息可以是现有的F1AP消息(例如：gNB-CU Configuration Update)，也可以是新定义的F1AP消息。
3.恢复IAB-DU向目标IAB donor-CU发送F1AP响应消息。
作为另一种可能的实现方式，如图15所示，恢复IAB-DU通过步骤3来获取新的配置信息。
2.恢复IAB-DU向目标IAB donor-CU发送F1AP请求消息，该请求消息用于建立/重建立恢复IAB-DU和目标IAB donor-CU之间的F1连接。
3.目标IAB donor-CU向恢复IAB-DU发送F1AP响应消息。该F1AP请求消息中携带修改恢复IAB-DU小区的信息列表，每个信息列表包含以下至少一种信息：
恢复IAB-DU小区的源标识(例如：源CGI或者源Cell identity)、恢复IAB-DU的新配置、恢复IAB-DU新小区激活指示信息。
该F1AP请求消息可以是现有的F1AP消息(例如：gNB-DU Configuration Update Ack)，也可以是新定义的F1AP消息。
需要说明的是，图13至图15所示流程示意图为在图11所示实施例的步骤S107中IAB donor向第一IAB节点发送第一配置信息的几种示例的实现过程，除了图13至图15所示实现过程，IAB donor还可以将第一配置信息携带在IAB donor向第一IAB节点发送的其它消息中，此处不做限定。此外，对于图13至图15所示流程示意图所在的图11所示实施例的步骤S107，需要在图11所示实施例的步骤S106之后执行，而不依赖于图11所示实施例的步骤S101(图12所示流程)至步骤S103的实现过程，且本申请实施例中对前述图11所示实施例的步骤S107、步骤S104以及步骤S105之间的执行顺序不做限定。
此外，当应用于图13至图15所示场景时，第一IAB节点可以在图13至图15中的步骤4中执行图11所示实施例的步骤S108。
具体地，当应用于图13至图15所示场景时，第一IAB节点可以在图13至图15中的步骤4之后，执行图11所示实施例的步骤S108。即一旦子节点收到步骤4中的MAC CE/BAP control PDU后，将触发向目标IAB donor-CU进行RRC重建立流程，对应的流程与恢复IAB-MT的RRC重建立流程(图12)一致，此处不再赘述。
上面从方法的角度对本申请实施例进行了说明，下面从具体装置实现的角度对本申请实施例中的通信装置进行介绍。
请参阅图16，本申请实施例提供了一种通信装置1600，具体该通信装置1600包括：处理单元1601和收发单元1602；
在通信装置1600用于实现上述IAB donor所对应的功能时，该通信装置1600中的处理单元1601和收发单元1602的实现包括如下过程。
处理单元1601，用于获取回传链路的无线链路控制信道BH RLC CH的配置信息，该BH RLC CH的配置信息为第一接入回传一体化IAB节点与该第一IAB节点的源父节点之间的BH RLC CH的配置信息；
收发单元1602，用于向该第一IAB节点的目标父节点发送该BH RLC CH的配置信息。
在一种具体的实现方式中，该BH RLC CH的配置信息包括以下至少一项：
该BH RLC CH的标识、该BH RLC CH对应的逻辑信道标识、无线链路控制信道RLC的配置信息或者逻辑信道的配置信息。
在一种具体的实现方式中，该IAB donor为目标IAB donor，该目标父节点与该目标IAB donor连接，该源父节点与源IAB donor连接。
在一种具体的实现方式中，
该处理单元1601，具体用于接收来自该源IAB donor的获取用户设备UE上下文响应消息，该获取UE上下文响应消息包括该BH RLC CH的配置信息。
在一种具体的实现方式中，该收发单元1602，还用于：
通过该目标父节点向该第一IAB节点发送第一指示信息，该第一指示信息用于指示该第一IAB节点连接的IAB donor改变。
在一种具体的实现方式中，
该第一指示信息携带在RRC重建立消息中；或，
该第一指示信息携带在RRC重配置消息中。
在一种具体的实现方式中，该收发单元1602，还用于：
通过该目标父节点向该第一IAB节点发送该目标IAB donor的网际互联协议IP地址信息。
在一种具体的实现方式中，该目标IAB donor的IP地址信息携带在RRC重配置消息中。
在一种具体的实现方式中，该收发单元1602，还用于：
通过该目标父节点向该第一IAB节点发送第一配置信息，该第一配置信息包括以下至少一项：
该第一IAB节点的小区的源标识、该第一IAB节点的小区的目标标识、该第一IAB节点的小区的PLMN ID、该第一IAB节点小区的SSB信息或者该第一IAB节点的小区的激活指示信息。
需要说明的是，上述通信装置1600的单元的信息执行过程等内容，具体可参见本申请前述所示的方法实施例中IAB donor对应的叙述，此处不再赘述。
在通信装置1600用于实现上述第一IAB节点的目标父节点所对应的功能时，该通信装置1600中的处理单元1601和收发单元1602的实现包括如下过程。
收发单元1602，用于接收来自接入回传一体化宿主IAB donor的回传链路的无线链路控制信道BH RLC CH的配置信息，该BH RLC CH的配置信息为第一接入回传一体化IAB节点与该第一IAB节点的源父节点之间的BH RLC CH的配置信息；
处理单元1601，用于根据该BH RLC CH的配置信息确定与该第一IAB节点之间的BH RLC CH的配置。
在一种具体的实现方式中，该BH RLC CH的配置信息包括以下至少一项：
该BH RLC CH的标识、该BH RLC CH对应的逻辑信道标识、无线链路控制信道RLC的配置信息或者逻辑信道的配置信息。
需要说明的是，上述通信装置1600的单元的信息执行过程等内容，具体可参见本申请前述所示的方法实施例中第一IAB节点的目标父节点对应的叙述，此处不再赘述。
在通信装置1600用于实现上述第一IAB节点所对应的功能时，该通信装置1600中的处理单元1601和收发单元1602的实现包括如下过程。
处理单元1601，用于确定与目标接入回传一体化宿主IAB donor之间RRC重建立完成；
收发单元1602，用于向该第一IAB节点的子节点发送第一信息；
该第一信息包括以下至少一项：
该第一IAB节点连接的IAB donor改变的指示信息、RRC重建立的指示信息、RRC重建立的基站的标识信息、RRC重建立的小区的标识信息。
在一种具体的实现方式中，
该第一信息携带在媒体接入控制层的控制单元MAC CE中；或，
该第一信息携带在BAP control PDU中。
在一种具体的实现方式中，该收发单元1602，还用于：
接收来自该目标IAB donor的第一指示信息，该第一指示信息用于指示该第一IAB节点连接的IAB donor改变。
在一种具体的实现方式中，
该第一指示信息携带在RRC重建立消息中；或，
该第一指示信息携带在RRC重配置消息中。
在一种具体的实现方式中，该处理单元1601还用于：确定与该IAB donor之间的F1连接建立/重建立完成或F1连接已经恢复。
在一种具体的实现方式中，该收发单元1602，还用于：
接收来自该目标IAB donor的该目标IAB donor的IP地址信息。
在一种具体的实现方式中，该目标IAB donor的IP地址信息携带在RRC重配置消息中。
在一种具体的实现方式中，该收发单元1602，具体用于：
接收来自该目标IAB donor的第一配置信息，该第一配置信息包括以下至少一项：
该第一IAB节点的小区的源标识、该第一IAB节点的小区的目标标识、该第一IAB节点的小区的PLMN ID、该第一IAB节点小区的SSB信息或者该第一IAB节点的小区的激活指示信息。
需要说明的是，上述通信装置1600的单元的信息执行过程等内容，具体可参见本申请前述所示的方法实施例中第一IAB节点对应的叙述，此处不再赘述。
在通信装置1600用于实现上述第一IAB节点的子节点所对应的功能时，该通信装置1600中的处理单元1601和收发单元1602的实现包括如下过程。
收发单元1602，用于接收来自该第一IAB节点的第一信息，该第一信息包括以下至少一项：
该第一IAB节点连接的IAB donor改变的指示信息、RRC重建立的指示信息、RRC重建立的基站的标识信息、RRC重建立的小区的标识信息；
处理单元1601，用于根据该第一信息触发以下至少一项流程：RRC重建立、F1连接建立或者F1连接重建立。
在本申请实施例第八方面的一种具体的实现方式中，
该第一信息携带在媒体接入控制层的控制单元MAC CE中；或，
该第一信息携带在BAP control PDU中。
需要说明的是，上述通信装置1600的单元的信息执行过程等内容，具体可参见本申请前述所示的方法实施例中第一IAB节点的子节点对应的叙述，此处不再赘述。
请参阅图17，为本申请的实施例提供的上述实施例中所涉及的通信装置的结构示意图， 其中，该通信装置具体可以为前述实施例中的IAB donor、第一IAB节点的目标父节点、第一IAB节点或第一IAB节点的子节点，该通信装置的结构可以参考图17所示的结构。
通信装置包括至少一个处理器1711、至少一个存储器1712、至少一个收发器1713、至少一个网络接口1714和一个或多个天线1715。处理器1711、存储器1712、收发器1713和网络接口1714相连，例如通过总线相连，在本申请实施例中，所述连接可包括各类接口、传输线或总线等，本实施例对此不做限定。天线1715与收发器1713相连。网络接口1714用于使得通信装置通过通信链路，与其它通信设备相连，例如网络接口1714可以包括通信装置与核心网设备之间的网络接口，例如S1接口，网络接口可以包括通信装置和其他网络设备(例如其他接入网设备或者核心网设备)之间的网络接口，例如X2或者Xn接口。
处理器1711主要用于对通信协议以及通信数据进行处理，以及对整个通信装置进行控制，执行软件程序，处理软件程序的数据，例如用于支持通信装置执行实施例中所描述的动作。通信装置可以可以包括基带处理器和中央处理器，基带处理器主要用于对通信协议以及通信数据进行处理，中央处理器主要用于对整个终端设备进行控制，执行软件程序，处理软件程序的数据。图17中的处理器1711可以集成基带处理器和中央处理器的功能，本领域技术人员可以理解，基带处理器和中央处理器也可以是各自独立的处理器，通过总线等技术互联。本领域技术人员可以理解，终端设备可以包括多个基带处理器以适应不同的网络制式，终端设备可以包括多个中央处理器以增强其处理能力，终端设备的各个部件可以通过各种总线连接。所述基带处理器也可以表述为基带处理电路或者基带处理芯片。所述中央处理器也可以表述为中央处理电路或者中央处理芯片。对通信协议以及通信数据进行处理的功能可以内置在处理器中，也可以以软件程序的形式存储在存储器中，由处理器执行软件程序以实现基带处理功能。
存储器主要用于存储软件程序和数据。存储器1712可以是独立存在，与处理器1711相连。可选的，存储器1712可以和处理器1711集成在一起，例如集成在一个芯片之内。其中，存储器1712能够存储执行本申请实施例的技术方案的程序代码，并由处理器1711来控制执行，被执行的各类计算机程序代码也可被视为是处理器1711的驱动程序。
图17仅示出了一个存储器和一个处理器。在实际的终端设备中，可以存在多个处理器和多个存储器。存储器也可以称为存储介质或者存储设备等。存储器可以为与处理器处于同一芯片上的存储元件，即片内存储元件，或者为独立的存储元件，本申请实施例对此不做限定。
收发器1713可以用于支持通信装置与终端之间射频信号的接收或者发送，收发器1713可以与天线1715相连。收发器1713包括发射机Tx和接收机Rx。具体地，一个或多个天线1715可以接收射频信号，该收发器1713的接收机Rx用于从天线接收所述射频信号，并将射频信号转换为数字基带信号或数字中频信号，并将该数字基带信号或数字中频信号提供给所述处理器1711，以便处理器1711对该数字基带信号或数字中频信号做进一步的处理，例如解调处理和译码处理。此外，收发器1713中的发射机Tx还用于从处理器1711接收经过调制的数字基带信号或数字中频信号，并将该经过调制的数字基带信号或数字中频信号转换为射频信号，并通过一个或多个天线1715发送所述射频信号。具体地，接收机 Rx可以选择性地对射频信号进行一级或多级下混频处理和模数转换处理以得到数字基带信号或数字中频信号，所述下混频处理和模数转换处理的先后顺序是可调整的。发射机Tx可以选择性地对经过调制的数字基带信号或数字中频信号时进行一级或多级上混频处理和数模转换处理以得到射频信号，所述上混频处理和数模转换处理的先后顺序是可调整的。数字基带信号和数字中频信号可以统称为数字信号。
收发器也可以称为收发单元、收发机、收发装置等。可选的，可以将收发单元中用于实现接收功能的器件视为接收单元，将收发单元中用于实现发送功能的器件视为发送单元，即收发单元包括接收单元和发送单元，接收单元也可以称为接收机、输入口、接收电路等，发送单元可以称为发射机、发射器或者发射电路等。
需要说明的是，图17所示通信装置具体可以用于实现图11至图15对应方法实施例中通信装置所实现的步骤，并实现通信装置对应的技术效果，图17所示通信装置的具体实现方式，均可以参考图11至图15对应的各个方法实施例中的叙述，此处不再一一赘述。
图18是本申请实施例提供的IAB donor的一种结构示意图，该IAB donor可以采用CU-DU分离的架构。如图18所示，该IAB donor可应用于如图10-1或图10-2或图10-3或图10-4所示的系统中，实现上述方法实施例中IAB donor(源IAB donor和/或目标IAB donor)的功能。
IAB donor可包括一个或多个DU 1101和一个或多个CU 1102。所述DU 1101可以包括至少一个天线11011，至少一个射频单元11012，至少一个处理器11013和至少一个存储器11014。所述DU 1101部分主要用于射频信号的收发以及射频信号与基带信号的转换，以及部分基带处理。CU1102可以包括至少一个处理器11022和至少一个存储器11021。CU 1102和DU 1101之间可以通过接口进行通信，其中，控制面(control plane)接口可以为F1-C，用户面(user Plane)接口可以为F1-U。
所述CU 1102部分主要用于进行基带处理，对基站进行控制等。所述DU 1101与CU 1102可以是物理上设置在一起，也可以物理上分离设置的，即分布式基站。所述CU 1102为基站的控制中心，也可以称为处理单元，主要用于完成基带处理功能。例如所述CU 1102可以用于控制基站执行上述方法实施例中关于网络设备的操作流程。
具体的，CU和DU上的基带处理可以根据无线网络的协议层划分，具体可以参考上文的内容。
在一个实例中，所述CU 1102可以由一个或多个单板构成，多个单板可以共同支持单一接入指示的无线接入网(如5G网)，也可以分别支持不同接入制式的无线接入网(如LTE网，5G网或其他接入网)。所述存储器11021和处理器11022可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。所述DU 1101可以由一个或多个单板构成，多个单板可以共同支持单一接入指示的无线接入网(如5G网)，也可以分别支持不同接入制式的无线接入网(如LTE网，5G网或其他接入网)。所述存储器11014和处理器11013可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有 必要的电路。
可选的，CU 1102可以通过DU 1101与IAB donor的子节点进行传输，CU 1102可以通过接口与其他IAB donor相连，CU 1102可以通过该接口从其他IAB donor(例如其他IAB donor的CU)接收数据和/或消息，或者CU 1102可以通过该接口向该其他IAB donor发送数据和/或消息。
本申请实施例还提供一种存储一个或多个计算机执行指令的计算机可读存储介质，当计算机执行指令被处理器执行时，该处理器执行如上述通信装置所实现的方法，如上述IAB donor、第一IAB节点的目标父节点、第一IAB节点或第一IAB节点的子节点所实现的方法。
本申请实施例还提供一种存储一个或多个计算机的计算机程序产品(或称计算机程序)，当计算机程序产品被该处理器执行时，该处理器执行上述通信装置所实现的方法，如上述IAB donor、第一IAB节点的目标父节点、第一IAB节点或第一IAB节点的子节点所实现的方法。
本申请实施例还提供了一种芯片系统，该芯片系统包括处理器，用于支持通信装置实现上述通信装置所实现的方法，如上述IAB donor、第一IAB节点的目标父节点、第一IAB节点或第一IAB节点的子节点所实现的方法。在一种可能的设计中，该芯片系统还可以包括存储器，存储器，用于保存该通信装置必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
本申请实施例还提供了一种通信系统，该通信系统包括上述通信装置，如上述IAB donor、第一IAB节点的目标父节点、第一IAB节点和/或第一IAB节点的子节点。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、 随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (47)

  1. 一种用于接入回传一体化IAB系统中的通信方法，其特征在于，包括：
    接入回传一体化宿主IAB donor获取回传链路的无线链路控制信道BH RLC CH的配置信息，所述BH RLC CH的配置信息为第一接入回传一体化IAB节点与所述第一IAB节点的源父节点之间的BH RLC CH的配置信息；
    所述IAB donor向所述第一IAB节点的目标父节点发送所述BH RLC CH的配置信息。
  2. 根据权利要求1所述的方法，其特征在于，所述BH RLC CH的配置信息包括以下至少一项：
    所述BH RLC CH的标识、所述BH RLC CH对应的逻辑信道标识、无线链路控制信道RLC的配置信息或者逻辑信道的配置信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述IAB donor为目标IAB donor，所述目标父节点与所述目标IAB donor连接，所述源父节点与源IAB donor连接。
  4. 根据权利要求3所述的方法，其特征在于，
    所述IAB donor获取BH RLC CH的配置信息包括：
    所述IAB donor接收来自所述源IAB donor的获取用户设备UE上下文响应消息，所述获取UE上下文响应消息包括所述BH RLC CH的配置信息。
  5. 根据权利要求3或4所述的方法，其特征在于，所述方法还包括：
    所述IAB donor通过所述目标父节点向所述第一IAB节点发送第一指示信息，所述第一指示信息用于指示所述第一IAB节点连接的IAB donor改变。
  6. 根据权利要求5所述的方法，其特征在于，
    所述第一指示信息携带在RRC重建立消息中；或，
    所述第一指示信息携带在RRC重配置消息中。
  7. 根据权利要求3至6任一项所述的方法，其特征在于，所述方法还包括：
    所述IAB donor通过所述目标父节点向所述第一IAB节点发送所述IAB donor的网际互联协议IP地址信息。
  8. 根据权利要求7所述的方法，其特征在于，所述目标IAB donor的IP地址信息携带在RRC重配置消息中。
  9. 根据权利要求3至8任一项所述的方法，其特征在于，所述方法还包括：
    所述IAB donor通过所述目标父节点向所述第一IAB节点发送第一配置信息，所述第一配置信息包括以下至少一项：
    所述第一IAB节点的小区的源标识、所述第一IAB节点的小区的目标标识、所述第一IAB节点的小区的PLMNID、所述第一IAB节点小区的SSB信息或者所述第一IAB节点的小区的激活指示信息。
  10. 一种用于接入回传一体化IAB系统中的通信方法，其特征在于，包括：
    第一接入回传一体化IAB节点的目标父节点接收来自IAB宿主IAB donor的回传链路的无线链路控制信道BH RLC CH的配置信息，所述BH RLC CH的配置信息为所述第一IAB节点与所述第一IAB节点的源父节点之间的BH RLC CH的配置信息；
    所述目标父节点根据所述BH RLC CH的配置信息确定所述第一IAB节点与所述目标父节点之间的BH RLC CH的配置。
  11. 根据权利要求10所述的方法，其特征在于，所述BH RLC CH的配置信息包括以下至少一项：
    所述BH RLC CH的标识、所述BH RLC CH对应的逻辑信道标识、无线链路控制信道RLC的配置信息或者逻辑信道的配置信息。
  12. 一种用于接入回传一体化IAB系统中的通信方法，其特征在于，包括：
    第一接入回传一体化IAB节点确定与IAB宿主IAB donor之间的RRC重建立完成；
    所述第一IAB节点向所述第一IAB节点的子节点发送第一信息；
    所述第一信息包括以下至少一项：
    所述第一IAB节点连接的IAB donor改变的指示信息、RRC重建立的指示信息、RRC重建立的基站的标识信息、RRC重建立的小区的标识信息。
  13. 根据权利要求12所述的方法，其特征在于，
    所述第一信息携带在媒体接入控制层的控制单元MAC CE中；或，
    所述第一信息携带在回传适配协议控制分组数据单元BAP control PDU中。
  14. 根据权利要求12或13所述的方法，其特征在于，在所述第一IAB节点向所述子节点发送所述第一信息之前，所述方法还包括：
    所述第一IAB节点接收来自所述目标IAB donor的第一指示信息，所述第一指示信息用于指示所述第一IAB节点连接的IAB donor改变。
  15. 根据权利要求14所述的方法，其特征在于，
    所述第一指示信息携带在RRC重建立消息中；或，
    所述第一指示信息携带在RRC重配置消息中。
  16. 根据权利要求12至15任一项所述的方法，其特征在于，在所述第一IAB节点向所述第一IAB节点的子节点发送第一信息之前，所述方法还包括：
    所述第一IAB节点确定与所述IAB donor之间的F1连接建立/重建立完成或F1连接已经恢复。
  17. 根据权利要求12至16任一项所述的方法，其特征在于，所述方法还包括：
    所述第一IAB节点接收来自所述IAB donor的所述IAB donor的IP地址信息。
  18. 根据权利要求17所述的方法，其特征在于，所述IAB donor的IP地址信息携带在RRC重配置消息中。
  19. 根据权利要求12至18任一项所述的方法，其特征在于，在所述第一IAB节点确定与IAB宿主IAB donor之间的RRC重建立完成之后，所述方法还包括：
    所述第一IAB节点接收来自所述IAB donor的第一配置信息，所述第一配置信息包括以下至少一项：
    所述第一IAB节点的小区的源标识、所述第一IAB节点的小区的目标标识、所述第一IAB节点的小区的PLMNID、所述第一IAB节点小区的SSB信息或者所述第一IAB节点的小区的激活指示信息。
  20. 一种用于接入回传一体化IAB系统中的通信方法，其特征在于，包括：
    第一接入回传一体化IAB节点的子节点接收来自所述第一IAB节点的第一信息，所述第一信息包括以下至少一项：
    所述第一IAB节点连接的IAB donor改变的指示信息、RRC重建立的指示信息、RRC重建立的基站的标识信息、RRC重建立的小区的标识信息；
    所述子节点根据所述第一信息触发以下至少一项流程：RRC重建立、F1连接建立或者F1连接重建立。
  21. 根据权利要求20所述的方法，其特征在于，
    所述第一信息携带在媒体接入控制层的控制单元MAC CE中；或，
    所述第一信息携带在回传适配协议控制分组数据单元BAP control PDU中。
  22. 一种通信装置，其特征在于，所述装置为接入回传一体化宿主IAB donor，所述装置包括：
    处理单元，用于获取回传链路的无线链路控制信道BHRLCCH的配置信息，所述BHRLCCH的配置信息为第一接入回传一体化IAB节点与所述第一IAB节点的源父节点之间的BHRLCCH的配置信息；
    收发单元，用于向所述第一IAB节点的目标父节点发送所述BHRLCCH的配置信息。
  23. 根据权利要求22所述的装置，其特征在于，所述BHRLCCH的配置信息包括以下至少一项：
    所述BHRLCCH的标识、所述BHRLCCH对应的逻辑信道标识、无线链路控制信道RLC的配置信息或者逻辑信道的配置信息。
  24. 根据权利要求22或23所述的装置，其特征在于，所述IAB donor为目标IABdonor，所述目标父节点与所述目标IABdonor连接，所述源父节点与源IABdonor连接。
  25. 根据权利要求24所述的装置，其特征在于，
    所述处理单元，具体用于接收来自所述源IABdonor的获取用户设备UE上下文响应消息，所述获取UE上下文响应消息包括所述BHRLCCH的配置信息。
  26. 根据权利要求24或25所述的装置，其特征在于，所述收发单元，还用于：
    通过所述目标父节点向所述第一IAB节点发送第一指示信息，所述第一指示信息用于指示所述第一IAB节点连接的IAB donor改变。
  27. 根据权利要求26所述的装置，其特征在于，
    所述第一指示信息携带在RRC重建立消息中；或，
    所述第一指示信息携带在RRC重配置消息中。
  28. 根据权利要求24至27任一项所述的装置，其特征在于，所述收发单元，还用于：
    通过所述目标父节点向所述第一IAB节点发送所述目标IABdonor的IP地址信息。
  29. 根据权利要求28所述的装置，其特征在于，所述目标IABdonor的IP地址信息携带在RRC重配置消息中。
  30. 根据权利要求24至29任一项所述的装置，其特征在于，所述收发单元，还用于：
    通过所述目标父节点向所述第一IAB节点发送第一配置信息，所述第一配置信息包括 以下至少一项：
    所述第一IAB节点的小区的源标识、所述第一IAB节点的小区的目标标识、所述第一IAB节点的小区的PLMNID、所述第一IAB节点小区的SSB信息或者所述第一IAB节点的小区的激活指示信息。
  31. 一种通信装置，其特征在于，所述装置为第一IAB节点的目标父节点，所述装置包括：
    收发单元，用于接收来自接入回传一体化宿主IAB donor的回传链路的无线链路控制信道BHRLCCH的配置信息，所述BHRLCCH的配置信息为第一接入回传一体化IAB节点与所述第一IAB节点的源父节点之间的BHRLCCH的配置信息；
    处理单元，用于根据所述BHRLCCH的配置信息确定与所述第一IAB节点之间的BH RLC CH的配置。
  32. 根据权利要求31所述的装置，其特征在于，所述BHRLCCH的配置信息包括以下至少一项：
    所述BHRLCCH的标识、所述BHRLCCH对应的逻辑信道标识、无线链路控制信道RLC的配置信息或者逻辑信道的配置信息。
  33. 一种通信装置，其特征在于，所述装置为第一接入回传一体化IAB节点，所述装置包括：
    处理单元，用于确定与目标接入回传一体化宿主IAB donor之间RRC重建立完成；
    收发单元，用于向所述第一IAB节点的子节点发送第一信息；
    所述第一信息包括以下至少一项：
    所述第一IAB节点连接的IAB donor改变的指示信息、RRC重建立的指示信息、RRC重建立的基站的标识信息、RRC重建立的小区的标识信息。
  34. 根据权利要求33所述的装置，其特征在于，
    所述第一信息携带在媒体接入控制层的控制单元MACCE中；或，
    所述第一信息携带在回传适配协议控制分组数据单元BAPcontrolPDU中。
  35. 根据权利要求33或34所述的装置，其特征在于，所述收发单元，还用于：
    接收来自所述目标IABdonor的第一指示信息，所述第一指示信息用于指示所述第一IAB节点连接的IAB donor改变。
  36. 根据权利要求35所述的装置，其特征在于，
    所述第一指示信息携带在RRC重建立消息中；或，
    所述第一指示信息携带在RRC重配置消息中。
  37. 根据权利要求33至36任一项所述的装置，其特征在于，所述处理单元，还用于：
    确定与所述IAB donor之间的F1连接建立/重建立完成或F1连接已经恢复。
  38. 根据权利要求33至37任一项所述的装置，其特征在于，所述收发单元，还用于：
    接收来自所述目标IAB donor的所述目标IABdonor的网际互联协议IP地址信息。
  39. 根据权利要求38所述的装置，其特征在于，所述目标IABdonor的IP地址信息携带在RRC重配置消息中。
  40. 根据权利要求33至39任一项所述的装置，其特征在于，所述收发单元，具体用于：
    接收来自所述目标IABdonor的第一配置信息，所述第一配置信息包括以下至少一项：
    所述第一IAB节点的小区的源标识、所述第一IAB节点的小区的目标标识、所述第一IAB节点的小区的PLMNID、所述第一IAB节点小区的SSB信息或者所述第一IAB节点的小区的激活指示信息。
  41. 一种通信装置，其特征在于，所述装置为第一接入回传一体化IAB节点的子节点，所述装置包括：
    收发单元，用于接收来自所述第一IAB节点的第一信息，所述第一信息包括以下至少一项：
    所述第一IAB节点连接的IAB donor改变的指示信息、RRC重建立的指示信息、RRC重建立的基站的标识信息、RRC重建立的小区的标识信息；
    处理单元，用于根据所述第一信息触发以下至少一项流程：RRC重建立、F1连接建立或者F1连接重建立。
  42. 根据权利要求41所述的装置，其特征在于，
    所述第一信息携带在媒体接入控制层的控制单元MACCE中；或，
    所述第一信息携带在回传适配协议控制分组数据单元BAPcontrolPDU中。
  43. 一种通信装置，其特征在于，包括：处理器，所述处理器与存储器耦合，所述存储器用于存储计算机程序或指令，所述处理器用于执行存储器中的该计算机程序或指令，使得所述通信装置执行权利要求1至9任一项所述的用于接入回传一体化IAB系统中的通信方法，或者使得所述通信装置执行权利要求10至11任一项所述的用于接入回传一体化IAB系统中的通信方法，或者使得所述通信装置执行权利要求12至19任一项所述的用于接入回传一体化IAB系统中的通信方法，或者使得所述通信装置执行权利要求20至21任一项所述的用于接入回传一体化IAB系统中的通信方法。
  44. 一种芯片，其特征在于，所述芯片包括处理器和通信接口；
    其中，所述通信接口和所述处理器耦合，所述处理器用于运行计算机程序或指令，以实现如权利要求1至9任一项所述的用于接入回传一体化IAB系统中的通信方法，或者以实现如权利要求10至11任一项所述的用于接入回传一体化IAB系统中的通信方法，或者以实现如权利要求12至19任一项所述的用于接入回传一体化IAB系统中的通信方法，或者以实现如权利要求20至21任一项所述的用于接入回传一体化IAB系统中的通信方法。
  45. 一种计算机可读存储介质，所述存储介质用于存储计算机程序或指令，所述计算机程序或指令被执行时，使得所述计算机执行权利要求1至9任一项所述的用于接入回传一体化IAB系统中的通信方法，或者使得所述计算机执行权利要求10至11任一项所述的用于接入回传一体化IAB系统中的通信方法，或者使得所述计算机执行权利要求12至19任一项所述的用于接入回传一体化IAB系统中的通信方法，或者使得所述计算机执行权利要求20至21任一项所述的用于接入回传一体化IAB系统中的通信方法。
  46. 一种计算机程序产品，所述计算机程序产品包括计算机程序或指令，其特征在于， 在所述计算机程序产品在计算机上运行时，使得所述计算机执行如权利要求1至9中任一项所述的方法，或，使得所述计算机执行如权利要求10至11中任一项所述的方法，或，使得所述计算机执行如权利要求12至19中任一项所述的方法，或，使得所述计算机执行如权利要求20至21中任一项所述的方法。
  47. 一种通信系统，其特征在于，
    所述通信系统包括如权利要求22至30任一项所述的通信装置，如权利要求31至32任一项所述的通信装置、如权利要求33至40任一项所述的通信装置和/或如权利要求41至42任一项所述的通信装置；
    或，
    所述通信系统包括如权利要求43所述的通信装置。
PCT/CN2020/123014 2020-10-22 2020-10-22 一种用于接入回传一体化iab系统中的通信方法及相关设备 WO2022082683A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN202080106330.2A CN116530142A (zh) 2020-10-22 2020-10-22 一种用于接入回传一体化iab系统中的通信方法及相关设备
PCT/CN2020/123014 WO2022082683A1 (zh) 2020-10-22 2020-10-22 一种用于接入回传一体化iab系统中的通信方法及相关设备
EP20958265.9A EP4221338A4 (en) 2020-10-22 2020-10-22 COMMUNICATION METHOD FOR INTEGRATED ACCESS AND BACKHAUL SYSTEM (IAB) AND ASSOCIATED APPARATUS
US18/304,468 US20230262827A1 (en) 2020-10-22 2023-04-21 Communication method applied to integrated access and backhaul iab system and related device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/123014 WO2022082683A1 (zh) 2020-10-22 2020-10-22 一种用于接入回传一体化iab系统中的通信方法及相关设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/304,468 Continuation US20230262827A1 (en) 2020-10-22 2023-04-21 Communication method applied to integrated access and backhaul iab system and related device

Publications (1)

Publication Number Publication Date
WO2022082683A1 true WO2022082683A1 (zh) 2022-04-28

Family

ID=81291386

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/123014 WO2022082683A1 (zh) 2020-10-22 2020-10-22 一种用于接入回传一体化iab系统中的通信方法及相关设备

Country Status (4)

Country Link
US (1) US20230262827A1 (zh)
EP (1) EP4221338A4 (zh)
CN (1) CN116530142A (zh)
WO (1) WO2022082683A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110636561A (zh) * 2018-06-21 2019-12-31 中兴通讯股份有限公司 信息传输方法及装置、存储介质、电子装置
WO2020073196A1 (en) * 2018-10-09 2020-04-16 Lenovo (Beijing) Limited Handover requests with network information
CN111093286A (zh) * 2019-08-15 2020-05-01 中兴通讯股份有限公司 连接建立方法、装置、集合接入回传节点及存储介质
CN111526544A (zh) * 2019-02-01 2020-08-11 北京三星通信技术研究有限公司 连接重建方法、上下文获取方法、上下文管理方法、连接重建方法、节点和介质

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113940112B (zh) * 2019-03-28 2023-09-12 中兴通讯股份有限公司 用于iab切换的系统和方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110636561A (zh) * 2018-06-21 2019-12-31 中兴通讯股份有限公司 信息传输方法及装置、存储介质、电子装置
WO2020073196A1 (en) * 2018-10-09 2020-04-16 Lenovo (Beijing) Limited Handover requests with network information
CN111526544A (zh) * 2019-02-01 2020-08-11 北京三星通信技术研究有限公司 连接重建方法、上下文获取方法、上下文管理方法、连接重建方法、节点和介质
CN111093286A (zh) * 2019-08-15 2020-05-01 中兴通讯股份有限公司 连接建立方法、装置、集合接入回传节点及存储介质

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CATT: "(TP for NR_IAB BL CR for TS 38.401) Inter-CU IAB-node migration", 3GPP DRAFT; R3-195365 (TP FOR NR_IAB BL CR FOR TS 38.401) INTER-CU IAB-NODE MIGRATION, vol. RAN WG3, 3 October 2019 (2019-10-03), Chongqing, China, pages 1 - 9, XP051792402 *
See also references of EP4221338A4 *
ZTE, SANECHIPS: "Discussion on inter-CU IAB migration handling", 3GPP DRAFT; R3-195694 DISCUSSION ON INTER-CU IAB MIGRATION HANDLING, vol. RAN WG3, 4 October 2019 (2019-10-04), Chongqing, China, pages 1 - 4, XP051792719 *

Also Published As

Publication number Publication date
EP4221338A4 (en) 2023-11-29
US20230262827A1 (en) 2023-08-17
CN116530142A (zh) 2023-08-01
EP4221338A1 (en) 2023-08-02

Similar Documents

Publication Publication Date Title
US20210112471A1 (en) Method for establishing a fronthaul interface, method for performing access for a ue, method and apparatus for performing a handover for a ue, data forwarding method, user equipment and base station
US11582656B2 (en) 5GSM handling on invalid PDU session
WO2020034909A1 (zh) 通信方法和通信装置
US10342061B2 (en) Radio communication system and control method
US11832322B2 (en) Wireless backhaul communication processing method and related device
WO2022082679A1 (zh) 一种通信方法及相关设备
WO2022041249A1 (zh) 一种节点的切换方法以及相关设备
CN104396293B (zh) 无线电通信系统和基站
US20230239940A1 (en) Data transmission method and apparatus
WO2023011245A1 (zh) 通信方法和通信装置
WO2021238882A1 (zh) 一种实现业务连续性的方法及装置
US20230262557A1 (en) Methods and devices for enhancing integrated access backhaul networks for new radio
WO2018014154A1 (zh) 一种rrc连接重建方法和装置
WO2021026706A1 (zh) 一种f1接口管理方法及装置
US20200008268A1 (en) Enhanced Procedure Transaction ID Handling
US11246064B2 (en) PDN connection supports interworking to 5GS
TW202327396A (zh) 多路徑的傳輸方法和使用者設備
WO2022151298A1 (zh) 群组迁移方法、装置和系统
WO2022082683A1 (zh) 一种用于接入回传一体化iab系统中的通信方法及相关设备
WO2022082690A1 (zh) 群组切换的方法、装置和系统
WO2023246746A1 (zh) 一种通信方法及相关设备
WO2023150975A1 (zh) Iab宿主设备以及传输迁移回退方法
WO2023010364A1 (zh) 集成的接入和回传的通信装置以及方法
TWI843376B (zh) 用於無線通訊的方法及使用者設備
WO2023184542A1 (zh) 配置信息的方法、装置和通信系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20958265

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202080106330.2

Country of ref document: CN

ENP Entry into the national phase

Ref document number: 2020958265

Country of ref document: EP

Effective date: 20230425

NENP Non-entry into the national phase

Ref country code: DE