Establishing a signaling connection in a wireless network

1. A method for wireless communication at a radio access network (RAN) node, the method comprising:

communicating with a first scheduling entity over a first communication path using a first radio access technology (RAT);

communicating with a second scheduling entity over a second communication path using a second RAT that is different from the first RAT;

generating a first message comprising a first indication that the RAN node supports communication of information for a first signaling connection with the first scheduling entity via a second signaling connection over the second communication path, wherein the first signaling connection is associated with first Internet Protocol (IP) address information;

transmitting the first message comprising the first indication to the second scheduling entity via the second communication path prior to establishing the second signaling connection over the second communication path to the first scheduling entity;

receiving a second message from the second scheduling entity via the second communication path after transmitting the first message, wherein the second message comprises a second indication that the first scheduling entity supports the communication of the information for the first signaling connection via the second signaling connection over the second communication path, and wherein the second message comprises second IP address information that is different from the first IP address information from the first scheduling entity;

using the second IP address information to establish the second signaling connection over the second communication path to the first scheduling entity after receiving the second message comprising the second indication; and

communicating the information for the first signaling connection via the second signaling connection over the second communication path.

2. The method of claim 1 , wherein:

the RAN node comprises an integrated access backhaul (IAB) distributed unit; and

the first scheduling entity comprises an IAB donor control unit.

3. The method of claim 1 , wherein:

the second scheduling entity comprises a master base station for a dual connectivity mode of operation of the RAN node; and

the first scheduling entity comprises a secondary base station for the dual connectivity mode of operation.

4. The method of claim 1 , wherein:

the second scheduling entity comprises a secondary base station for a dual connectivity mode of operation; and

the first scheduling entity comprises a master base station for the dual connectivity mode of operation of the RAN node.

5. The method of claim 1 , wherein the using the second IP address information to establish the second signaling connection comprises:

establishing a stream control transmission protocol (SCTP) connection with the first scheduling entity responsive to the second message comprising the second indication.

6. The method of claim 5 , wherein the communicating the information for the first signaling connection via the second communication path comprises:

exchanging F1 control (F1-C) packets with the first scheduling entity via the SCTP connection.

7. The method of claim 1 , wherein the using the second IP address information to establish the second signaling connection comprises:

establishing a first path in a stream control transmission protocol (SCTP) connection to the first scheduling entity.

8. The method of claim 7 , wherein the communicating the information for the first signaling connection via the second communication path comprises:

exchanging F1 control (F1-C) packets with the first scheduling entity via the first path in the SCTP connection.

9. The method of claim 1 , wherein:

the second IP address information comprises an IP prefix; and

the using the second IP address information to establish the second signaling connection comprises deriving at least one IP address for the RAN node from the IP prefix.

10. The method of claim 1 , wherein the second IP address information comprises an IP address of the first scheduling entity.

11. The method of claim 1 , wherein the second IP address information comprises an IP address assigned to the RAN node by the first scheduling entity.

12. The method of claim 1 , wherein the first message comprises a UECapabilitylnformation message.

13. The method of claim 1 , wherein the second message comprises an RRCConnectionReconfiguration message or a DLlnformationTransfer message.

14. The method of claim 1 , wherein the method further comprises:

receiving, from the second scheduling entity, third IP address information for the RAN node; and

using the third IP address information for the RAN node to establish the second signaling connection to the first scheduling entity through a first integrated access backhaul (IAB) donor distributed unit of the second scheduling entity bypassing a first IAB donor control unit of the second scheduling entity.

15. The method of claim 1 , wherein:

the method further comprises establishing a first F1 control (F1-C) connection between an integrated access backhaul (IAB) distributed unit of the RAN node and a first IAB donor control unit (CU) of the first scheduling entity; and

the first signaling connection comprises a second F1-C connection between the IAB distributed unit and a second IAB donor control unit.

16. A radio access network (RAN) node, comprising:

a transceiver;

one or more memories storing processor-executable code; and

one or more processors configured to execute the processor-executable code to cause the RAN node to:

communicate with a first scheduling entity over a first communication path using a first radio access technology (RAT);

communicate with a second scheduling entity over a second communication path using a second RAT that is different from the first RAT;

generate a first message comprising a first indication that the RAN node supports communication of information for a first signaling connection with the first scheduling entity via a second signaling connection over the second communication path, wherein the first signaling connection is associated with first Internet Protocol (IP) address information;

transmit via the transceiver the first message comprising the first indication to the second scheduling entity via the second communication path prior to establishment of the second signaling connection over the second communication path to the first scheduling entity;

receive via the transceiver a second message from the second scheduling entity via the second communication path after transmission of the first message, wherein the second message comprises a second indication that the first scheduling entity supports the communication of the information for the first signaling connection via the second signaling connection over the second communication path, and wherein the second message comprises second IP address information that is different from the first IP address information from the first scheduling entity;

use the second IP address information to establish the second signaling connection over the second communication path to the first scheduling entity after receipt of the second message comprising the second indication; and

communicate via the transceiver the information for the first signaling connection via the second signaling connection over the second communication path.

17. The RAN node of claim 16 , wherein the second IP address information comprises an IP address of the first scheduling entity.

18. The RAN node of claim 16 , wherein the second IP address information comprises an IP address assigned to the RAN node by the first scheduling entity.

19. The RAN node of claim 16 , wherein the first message comprises a UECapabilitylnformation message.

20. The RAN node of claim 16 , wherein the second message comprises an RRCConnectionReconfiguration message or a DLlnformationTransfer message.

21. The RAN node of claim 16 , wherein the one or more processors are further configured to execute the processor-executable code to cause the RAN node to:

receive, from the second scheduling entity, third IP address information for the RAN node; and

use the third IP address information for the RAN node to establish the second signaling connection to the first scheduling entity through a first integrated access backhaul (IAB) donor distributed unit of the second scheduling entity bypassing a first IAB donor control unit of the second scheduling entity.

22. The RAN node of claim 16 , wherein:

the one or more processors are further configured to execute the processor-executable code to cause the RAN node to establish a first F 1 control (F1-C) connection between an integrated access backhaul (IAB) distributed unit of the RAN node and a first IAB donor control unit (CU) of the first scheduling entity; and

the first signaling connection comprises a second F1-C connection between the IAB distributed unit and a second IAB donor control unit.

23. The RAN node of claim 16 , wherein:

the RAN node comprises an integrated access backhaul (IAB) distributed unit; and

the first scheduling entity comprises an IAB donor control unit.

24. The RAN node of claim 16 , wherein:

the second scheduling entity comprises a master base station for a dual connectivity mode of operation of the RAN node; and

the first scheduling entity comprises a secondary base station for the dual connectivity mode of operation.

25. The RAN node of claim 16 , wherein:

the second scheduling entity comprises a secondary base station for a dual connectivity mode of operation; and

the first scheduling entity comprises a master base station for the dual connectivity mode of operation of the RAN node.

26. The RAN node of claim 16 , wherein the one or more processors are further configured to execute the processor-executable code to cause the RAN node to:

establish a stream control transmission protocol (SCTP) connection with the first scheduling entity.

27. The RAN node of claim 26 , wherein the one or more processors are further configured to execute the processor-executable code to cause the RAN node to:

exchange F1 control (F1-C) packets with the first scheduling entity via the SCTP connection.

28. The RAN node of claim 16 , wherein the one or more processors are further configured to execute the processor-executable code to cause the RAN node to:

establish a first path in a stream control transmission protocol (SCTP) connection to the first scheduling entity.

29. The RAN node of claim 28 , wherein the one or more processors are further configured to execute the processor-executable code to cause the RAN node to:

exchange F1 control (F1-C) packets with the first scheduling entity via the first path in the SCTP connection.

30. The RAN node of claim 16 , wherein:

the second IP address information comprises an IP prefix; and

the one or more processors are further configured to execute the processor-executable code to cause the RAN node to derive at least one IP address for the RAN node from the IP prefix.