IAB NODE DEVICE, IAB-DONOR DEVICE AND TRANSPORT ADDRESS DETERMINATION METHOD

1 . An integrated access and backhaul IAB node comprising:

a receiver configured to receive a first RRC (Radio Resource Control) reconfiguration message, the first RRC reconfiguration message including IP address information for the IAB node of an F1-terminating topology domain which includes a TNL (transport network layer) address anchored at a donor-DU under an F1-terminating donor-CU for the IAB node, or IP address information for the IAB node of a non-F1-terminating topology domain which includes a TNL address anchored at a donor-DU under a non-F1-terminating donor-CU for the IAB node.

2 . The IAB node according to claim 1 , wherein F1 connection of the IAB node is terminated at a first IAB-donor-CU, and the IAB node has RRC connection with a second IAB-donor-CU.

3 . The IAB node according to claim 2 , further comprising:

processor circuitry configured to determine that the first RRC reconfiguration message comprises the IP address information of the F1-terminating topology domain or the IP address information of the non-F1-terminating topology domain.

4 . The IAB node according to claim 2 , wherein the first IAB-donor-CU is a master node (MN) of the IAB node, and the second IAB-donor-CU is a secondary node (SN) of the IAB node.

5 . The IAB node according to claim 4 , wherein the first RRC reconfiguration message is an RRC reconfiguration message contained in a secondary cell group configuration field in the RRC reconfiguration message, and is carried by a second RRC reconfiguration message;

and the receiver receives, via SRB1, the second RRC reconfiguration message.

6 . The IAB node according to claim 4 , wherein the receiver receives, via SRB3, the first RRC reconfiguration message transmitted by the second IAB-donor-CU.

7 . The IAB node according to claim 2 , wherein the first IAB-donor-CU is the SN of the IAB node, and the second IAB-donor-CU is the MN of the IAB node;

and the first receiver receives, via SRB1, the first RRC reconfiguration message transmitted by the second IAB-donor-CU.

8 . The IAB node according to claim 2 , wherein the first IAB-donor-CU is a source donor-CU from which the IAB node is handed over, and the second IAB-donor-CU is a target donor-CU to which the IAB node is handed over;

and the first RRC reconfiguration message is a handover command RRC message generated by the second IAB-donor-CU forwarded by the first IAB-donor-CU.

9 . An integrated access and backhaul (IAB) donor device, applicable to a first IAB-donor-CU, the IAB donor device comprising:

a transmitter configured to transmit a first RRC (Radio Resource Control) reconfiguration message, the first RRC reconfiguration message including IP address information for an IAB node of an F1-terminating topology domain which includes a TNL (transport network layer) address anchored at a donor-DU under an F1-terminating donor-CU for the IAB node, or IP address information for an IAB node of a non-F1-terminating topology domain which includes a TNL address anchored at a donor-DU under a non-F1-terminating donor-CU for the IAB node;

wherein F1 connection of the IAB node is terminated at the first IAB-donor-CU.

10 . The IAB donor device according to claim 9 , wherein the first IAB-donor-CU is a master node (MN) of the IAB node, and the IAB node has RRC connection with a second IAB-donor-CU and the second IAB-donor-CU is a secondary node (SN) of the IAB node.

11 . The IAB donor device according to claim 10 , wherein

the first RRC reconfiguration message is an RRC reconfiguration message contained in a secondary cell group configuration field in the RRC reconfiguration message, and is carried by a second RRC reconfiguration message transmitted by the first IAB-donor-CU, and

the transmitter transmits, via SRB1, the second RRC reconfiguration message.

12 . The IAB donor device according to claim 9 , wherein the first IAB-donor-CU is a source donor-CU from which the IAB node is handed over, and the IAB node has RRC connection with a second IAB-donor-CU, the second IAB-donor-CU is a target donor-CU to which the IAB node is handed over;

and the first RRC reconfiguration message is a handover command RRC message generated by the second IAB-donor-CU forwarded by the first IAB-donor-CU.

13 . An integrated access and backhaul (IAB) donor device, applicable to a second IAB-donor-CU, the device comprising:

a transmitter configured to transmit a first RRC (Radio Resource Control) reconfiguration message, the first RRC reconfiguration message including IP address information for an IAB node of an F1-terminating topology domain, or IP address information for an IAB node of a non-F1-terminating topology domain;

wherein IP address information for the IAB node of a F1-terminating topology domain includes a TNL address anchored at a donor-DU under an F1-terminating donor-CU for the IAB node, IP address information for the IAB node of a non-F1-terminating topology domain includes a TNL address anchored at a donor-DU under a non-F1-terminating donor-CU for the IAB node;

wherein F1 connection of the IAB node is terminated at a first IAB-donor-CU.

14 . The device according to claim 13 , wherein the first IAB-donor-CU is the SN of the IAB node, and the IAB node has RRC connection with the second IAB-donor-CU and the second IAB-donor-CU is the MN of the LAB node;

and transmitter transmits, via SRB1, the first RRC reconfiguration message.

15 . The LAB donor device according to claim 13 , wherein

the first LAB-donor-CU is the MN of the LAB node, and the LAB node has RRC connection with the second LAB-donor-CU and the second LAB-donor-CU is the SN of the LAB node, and

transmitter transmits, via SRB3, the first RRC reconfiguration message.