Mobile integrated access and backhaul connectivity

Abstract

Methods, systems, and devices for wireless communication are described. A mobile wireless node (e.g., a mobile integrated access and backhaul (IAB) node) may send a control message indicating one or more supported network connectivity modes to a parent wireless node. A network connectivity mode may provide network connectivity to one or more user equipments (UEs) via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost. The parent wireless node may authorize the mobile wireless node to use a first network connectivity mode, and the mobile wireless node may communicate with a first UE according to the first network connectivity mode. In this way, even if the first UE is outside of the coverage area of the network, the mobile wireless node may extend coverage of the network to the first UE using a network connectivity mode.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. patent application No. 18 / 052,818, entitled “MOBILEINTEGREATED ACCESS AND BACKHAUL CONNECTIVITY,” filed by ABEDINI et al. on November 4, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The following relates to wireless communications, including mobile Integrated Access and Backhaul (IAB) connectivity. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE).

[0005] In some wireless communication systems, wireless backhaul connectivity between a mobile integrated access and backhaul (IAB) node and an IAB parent node may support the functionality of a mobile IAB node. However, in some cases, the wireless backhaul connectivity may be lost. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices and apparatuses for supporting mobile integrated access and backhaul (IAB) connectivity. For example, the described technology provides extended backhaul connectivity for mobile IAB nodes. Mobile IAB nodes such as vehicle-mounted IAB nodes can support multiple network connectivity modes. For example, the mobile IAB node can support IAB operation, non-IAB relay operation, repeater operation or UE relay, etc. The mobile IAB node can send a control message indicating multiple supported network connectivity modes to the IAB parent node. When the wireless backhaul connection (for example, between the mobile IAB node and the IAB parent node) is lost, each network connectivity mode can provide network connectivity to one or more UEs via the mobile IAB node. The IAB parent node can send a reply message that authorizes the mobile IAB node to use a first network connectivity node, and the mobile IAB node can communicate with the UE according to the first network connectivity mode. Therefore, when the wireless backhaul connection is lost, the mobile IAB node can communicate with the UE using a specific supported network connectivity node.

[0007] A method for wireless communication by a mobile wireless node is described. The method may include: sending a control message to a parent wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes being used to provide network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost; receiving a reply message from the parent wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes; and communicating one or more messages to a first UE of the one or more UEs based on the first network connectivity mode.

[0008] An apparatus for wireless communication by a mobile wireless node is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: send a control message to a parent wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes being used to provide network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost; receive a reply message from the parent wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes; and communicate one or more messages to a first UE of the one or more UEs based on the first network connectivity mode.

[0009] Another apparatus for wireless communication by a mobile wireless node is described. The apparatus may include: means for sending a control message to a parent wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes for providing network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost; means for receiving a reply message from the parent wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes; and means for communicating one or more messages to a first UE of the one or more UEs based on the first network connectivity mode.

[0010] A non-transitory computer-readable medium storing code for wireless communication by a mobile wireless node is described. The code may include instructions executable by a processor to perform the following actions: sending a control message to a parent wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes being used to provide network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost; receiving a reply message from the parent wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes; and communicating one or more messages to a first UE of the one or more UEs based on the first network connectivity mode.

[0011] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication of the first network connectivity mode to the one or more UEs.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication to the parent wireless node that the mobile wireless node may be operating using the first network connectivity mode to communicate with the first UE.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending a request to the parent wireless node to change between operating using the first network connectivity mode and operating using a second network connectivity mode of the one or more network connectivity modes; and receiving an indication from the parent wireless node to change between operating using the first network connectivity mode and operating using the second network connectivity mode.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a reply message from the parent wireless node indicating authorization to use a second network connectivity mode of the one or more network connectivity modes and indicating at least one criterion for changing between operating using the first network connectivity mode and operating using the second network connectivity mode.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication to the one or more UEs to change between operating using the first network connectivity mode and operating using the second network connectivity mode.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving a capability message indicating that the first UE supports sidelink communications; and sending an indication of a sidelink configuration for the first network connectivity mode.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving a first grant from the parent wireless node, the first grant scheduling sending a message to the mobile wireless node, the message being associated with the first UE; receiving the message based on the first grant; sending a second grant, the second grant scheduling sending the message to the first UE; and sending the message to the first UE based on the second grant.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving a grant from the parent wireless node, the grant scheduling a message to be sent to the mobile wireless node, the message being associated with the first UE; and relaying the message to the first UE based on the grant.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: communicating with the first UE using the first network connectivity mode, wherein the first network connectivity mode may be selected based on the capabilities of the first UE, quality of service (QoS) metrics, radio resource management (RRM) measurements, interference measurements, or any combination thereof.

[0020] A method for wireless communication by a parent wireless node is described. The method may include: receiving a control message from a mobile wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes being used to provide network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost; and sending a reply message to the mobile wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes.

[0021] An apparatus for wireless communication by a parent wireless node is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: receive a control message from a mobile wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes being used to provide network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost; and send a reply message to the mobile wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes.

[0022] Another apparatus for wireless communication by a parent wireless node is described. The apparatus may include: means for receiving a control message from a mobile wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes for providing network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost; and means for sending a reply message to the mobile wireless node, the reply message indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes.

[0023] A non-transitory computer-readable medium storing code for wireless communication by a parent wireless node is described. The code may include instructions executable by a processor to perform the following actions: receiving a control message from a mobile wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes being used to provide network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost; and sending a reply message to the mobile wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes.

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication from the mobile wireless node that the mobile wireless node may be operating using the first network connectivity mode to communicate with the first UE.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving a request from the mobile wireless node to change between operating using the first network connectivity mode and operating using a second network connectivity mode of the one or more network connectivity modes; and sending an indication to the mobile wireless node to change between operating using the first network connectivity mode and operating using the second network connectivity mode.

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending a reply message to the mobile wireless node, the reply message indicating authorization to use a second network connectivity mode of the one or more network connectivity modes and indicating at least one criterion for changing between operating using the first network connectivity mode and operating using the second network connectivity mode.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending a first grant to the mobile wireless node, the first grant scheduling a message to the mobile wireless node, the message being associated with the first UE; and sending the message based on the first grant.

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending a grant to the mobile wireless node, the grant scheduling sending a message to the mobile wireless node, the message associated with the first UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 An example of a wireless communication system supporting mobile integrated access and backhaul (IAB) connectivity according to one or more aspects of the present disclosure is illustrated.

[0030] Figure 2 An example of a network architecture supporting mobile IAB connectivity according to one or more aspects of the present disclosure is illustrated.

[0031] Figure 3An example of a wireless communication system supporting mobile IAB connectivity according to one or more aspects of the present disclosure is illustrated.

[0032] Figure 4 and Figure 5 An example of a network architecture supporting mobile IAB connectivity according to one or more aspects of the present disclosure is illustrated.

[0033] Figure 6 An example of a process flow for supporting mobile IAB connectivity according to one or more aspects of the present disclosure is illustrated.

[0034] Figure 7 and Figure 8 A block diagram of a device supporting mobile IAB connectivity according to one or more aspects of the present disclosure is shown.

[0035] Fig. 9 A block diagram of a communications manager supporting mobile IAB connectivity according to one or more aspects of the present disclosure is shown.

[0036] Fig.10 A diagram of a system including a device supporting mobile IAB connectivity is shown in accordance with one or more aspects of the present disclosure.

[0037] Fig.11 and Fig.12 A block diagram of a device supporting mobile IAB connectivity according to one or more aspects of the present disclosure is shown.

[0038] Fig.13 A block diagram of a communications manager supporting mobile IAB connectivity according to one or more aspects of the present disclosure is shown.

[0039] Fig.14 A diagram of a system including a device supporting mobile IAB connectivity is shown in accordance with one or more aspects of the present disclosure.

[0040] Figures 15 to 20 A flow chart illustrating a method of supporting mobile IAB connectivity according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0041] Some wireless communication systems support integrated access and backhaul (IAB) nodes, which may require backhaul connectivity to an IAB parent node or an IAB donor node that supports the functionality of the IAB node. For fixed IAB nodes, appropriate network deployment and planning can create an almost static and stable IAB network. However, for mobile IAB nodes that move freely throughout the network (e.g., IAB nodes installed on top of a car or other mobile vehicle), the wireless backhaul connectivity that supports the operation of the mobile IAB node may not be available in certain locations. Therefore, at certain times or locations, the mobile IAB node may not be able to continue its normal operation as an IAB node to serve one or more user equipment (UE), for example, when the mobile IAB node loses wireless backhaul connectivity when moving. If there is no wireless backhaul connectivity, the mobile wireless node may stop providing services to its connected UE (e.g., communicating with it). Therefore, the UE may encounter a radio link failure and try to find and connect to other cellular cells, which may be a time-consuming and power-consuming process and will limit UE communication.

[0042] The technology described herein supports extended backhaul connectivity for mobile IAB nodes. Mobile IAB nodes such as vehicle-mounted IAB nodes may support multiple network connectivity modes. For example, mobile IAB nodes may support IAB operation, non-IAB relay operation, repeater operation, or UE relay, etc. The mobile IAB node may send a control message indicating multiple supported network connectivity modes to the IAB parent node. When the wireless backhaul connection (for example, between the mobile IAB node and the IAB parent node) is lost, each network connectivity mode may provide network connectivity to one or more UEs via the mobile IAB node. The IAB parent node may send a reply message that authorizes the mobile IAB node to use a first network connectivity node, and the mobile IAB node may communicate with the UE according to the first network connectivity mode. Therefore, when the wireless backhaul connection is lost, the mobile IAB node may communicate with the UE using a specific supported network connectivity node, which may increase signaling throughput, reduce power consumption, and improve the communication quality between the UE and the mobile IAB node.

[0043] The specific implementations described in the present disclosure may be implemented to achieve one or more of the following potential advantages. For example, coverage of a mobile wireless node may be extended and communication between the mobile wireless node and each UE may be improved based on support for one or more network connectivity modes for establishing communication between the mobile wireless node and one or more UEs. In addition, by operating using different network connectivity modes based on wireless devices available for connectivity in a wireless communication system, the mobile wireless node may improve spectrum efficiency and increase signaling throughput.

[0044] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are then described in the context of a network architecture and process flow. Aspects of the present disclosure are further illustrated and described with reference to device diagrams, system diagrams, and flow charts related to mobile IAB connectivity.

[0045] Figure 1 An example of a wireless communication system 100 supporting mobile IAB connectivity according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0046] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0047] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices, such as Figure 1 Other UEs 115 or network entities 105 are shown.

[0048] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0049] In some examples, the network entities 105 may communicate with the core network 130 or with each other or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3 or other interface protocols). In some examples, the network entities 105 may communicate with each other via the backhaul communication links 120 (e.g., according to X2, Xn or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication links 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication links 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, the midhaul communication links 162 or the fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0050] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terminology). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0051] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0052] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of a protocol stack and DU 165 can support one or more different layers of a protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or layer 2 (L2) (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that communicate via such communication links.

[0053] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0054] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate a connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol defining a signaling message (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0055] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). The DU 165 may act as a distributed scheduling node toward child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node toward a parent node associated with the IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor may relay for transmissions to UEs through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, the IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the IAB child node 104 to receive signaling from the IAB parent node 104 , and a DU interface (eg, DU 165 ) may provide a Uu interface for the IAB parent node 104 to signal to the IAB child node 104 or the UE 115 .

[0056] For example, the IAB node 104 may be referred to as a parent node supporting communications for an IAB child node or as a child node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to the UE 115 via the IAB node 104, or may directly signal the transmissions to the UE 115, or both. The CU 160 of the IAB donor may signal the establishment of a communication link to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling via the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0057] Where the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support mobile IAB connectivity as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0058] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0059] The UE 115 described herein may be capable of communicating with various types of devices such as other UEs 115 which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0060] The UE 115 and the network entity 105 may use resources associated with one or more carriers to communicate wirelessly with each other via one or more communication links 125 (e.g., access links). The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined to support the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0061] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0062] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, among other transmission configurations. A carrier may carry either downlink communications or uplink communications (e.g., in an FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in a TDD mode).

[0063] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communications using a particular carrier bandwidth, or may be capable of being configured to support communications using one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

[0064] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a resource of a subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high rate of communication. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0065] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0066] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, for which Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0067] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of micro time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0068] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0069] According to various techniques, physical channels may be multiplexed using carriers for communication. Physical control channels and physical data channels may be multiplexed for signaling via downlink carriers, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0070] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier used to distinguish adjacent cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0071] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to a UE 115 that has a service subscription with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) than a macro cell, and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 that has a service subscription with a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0072] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0073] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0074] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for either synchronous operation or asynchronous operation.

[0075] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0076] Some UEs 115 may be configured to employ an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other energy-saving techniques for UE 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

[0077] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0078] In some examples, the UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0079] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0080] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0081] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0082] The wireless communication system 100 can utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to adopt License Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 can use carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands can be based on carrier aggregation configuration (e.g., LAA) in combination with component carriers operating using licensed bands. Operations using unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0083] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0084] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating along a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0085] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority processing and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map a transport channel to a physical channel.

[0086] In some examples, the IAB node may need wireless backhaul connectivity to an IAB parent node or an IAB donor node that can support IAB functionality. For fixed IAB nodes, using correct network deployment and planning can create an almost static and stable IAB network. Alternatively, some IAB nodes are mobile. For example, a mobile IAB node can be installed on the top of a bus or other mobile vehicle and can move freely throughout the network. However, wireless backhaul connectivity that supports mobile IAB operations may not be available in some scenarios. For example, due to the movement of the mobile IAB node, at a specific time or place (e.g., in the case of loss of wireless backhaul connectivity), the mobile IAB node may not be able to continue its normal operation as an IAB node to serve one or more UEs. If there is no wireless backhaul connectivity, the mobile wireless node may stop providing services (e.g., communicating with) to the UE 115 connected to it. Therefore, the UE 115 may encounter a radio link failure and try to find and connect to other cellular cells, which may be a time-consuming and power-consuming process and will limit the UE 115 communication.

[0087] When the wireless backhaul connection with the IAB parent node is lost, the wireless communication system 100 may support mobile IAB operation. Mobile IAB nodes such as vehicle-mounted IAB nodes may support multiple network connectivity modes. For example, the mobile IAB node may support IAB operation, non-IAB relay operation, repeater operation, or UE relay, etc. The mobile IAB node may send a control message indicating multiple supported network connectivity modes to the IAB parent node. When the wireless backhaul connection (e.g., between the mobile IAB node and the IAB parent node) is lost, each network connectivity mode may provide network connectivity to one or more UEs 115 via the mobile IAB node. The IAB parent node may send a reply message that authorizes the mobile IAB node to use the first network connectivity node, and the mobile IAB node may communicate with the UE 115 according to the first network connectivity mode.

[0088] Figure 2An example of a network architecture 200 (e.g., a decomposed base station architecture, a decomposed RAN architecture) supporting mobile IAB connectivity according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with the core network 130-a via a backhaul communication link 120-a, or indirectly communicate with the core network 130-a through one or more decomposed network entities 105 (e.g., a near RT RIC 175-b via an E2 link or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework) or both). The CU 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. The RU 170-a may be associated with a respective coverage area 110-a and may communicate with the UE 115-a via one or more communication links 125-a. In some implementations, the UE 115-a may be served by multiple RUs 170-a simultaneously.

[0089] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, these network entities 105 may include a wired interface that is configured to receive signals on a wired transmission medium or to send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver) configured to receive signals on a wireless transmission medium, or to send signals to one or more of the other network entities 105 on a wireless transmission medium, or both.

[0090] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to handle user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0091] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which depends at least in part on functional divisions, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU160-a.

[0092] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In this architecture, RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with RU 170-a may be controlled by the corresponding DU 165-a. In some examples, this configuration may enable DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0093] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate with components configured according to a 4G RAN (e.g., via an O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0094] The non-RT RIC 175-a may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that implement near real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

[0095] In some examples, in order to generate an AI / ML model to be deployed in the near-RT RIC 175-b, the non-RT RIC 175-a may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 175-b and may be received from a non-network data source or from a network function at the SMO 180-a or the non-RT RIC 175-a. In some examples, the non-RT RIC 175-a or the near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the non-RT RIC 175-a may monitor long-term trends and patterns of performance and employ an AI model or ML model to perform corrective actions through the SMO 180-a (e.g., via reconfiguration of O1) or via the generation of a RAN management policy (such as an A1 policy).

[0096] The network architecture 200 may support mobile IAB operation when the wireless backhaul connection with the IAB parent node is lost. A mobile IAB node, such as an in-vehicle IAB node, may support multiple network connectivity modes. For example, the mobile IAB node may support IAB operation, non-IAB relay operation, repeater operation, or UE relay, etc. The mobile IAB node may send a control message indicating multiple supported network connectivity modes to the IAB parent node. When the wireless backhaul connection (e.g., between the mobile IAB node and the IAB parent node) is lost, each network connectivity mode may provide network connectivity to one or more UEs 115 via the mobile IAB node. The IAB parent node may send a reply message that authorizes the mobile IAB node to use the first network connectivity node, and the mobile IAB node may communicate with the UE 115-a according to the first network connectivity mode.

[0097] Figure 3 An example of a wireless communication system 300 supporting mobile IAB connectivity according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 300 may implement aspects of the wireless communication system 100 and the network architecture 200, or may be implemented by aspects of the wireless communication system 100 and the network architecture 200. For example, the wireless communication system 300 may include a UE 115-b, a mobile wireless node 305 (e.g., a mobile IAB node), and a parent wireless node 310 (e.g., an IAB parent node), which may be examples of corresponding devices as described herein. In some examples, when the wireless backhaul connection with the parent wireless node 310 is lost, the mobile wireless node 305 may use a network connectivity mode to communicate with the UE 115-b, which may increase signaling throughput and improve the reliability of communication.

[0098] The wireless communication system 300 may support communication between the UE 115-b, the mobile wireless node 305, and the parent wireless node 310. For example, the mobile wireless node 305 and the parent wireless node 310 may communicate uplink transmissions and downlink transmissions via respective communication links 315, which may be referenced to Figure 1 An example of the described communication link 135. Additionally, the mobile wireless node 305 may communicate signaling with one or more UEs 115, including UE 115-b, via the communication link 315.

[0099] In some cases, the mobile wireless node 305 may be mounted on top of a bus, car, train, or other moving vehicle, such that the mobile wireless node 305 may move throughout the wireless communication system 300. In some examples, due to such movement, the mobile wireless node 305 may lose wireless backhaul connectivity with the parent wireless node 310 that may support the operation of the mobile wireless node 305. For example, the mobile wireless node 305 may move at a particular time or to a particular location outside of the coverage area of ​​the parent wireless node 310.

[0100] The mobile wireless node 305 may have a default operating mode (e.g., an IAB network connectivity mode). However, when the default operating mode is used, the functionality of the mobile wireless node 305 may not be supported (e.g., wireless backhaul connectivity with the parent wireless node 310 may be lost). In order to maintain communication with the UE 115-b when the wireless backhaul connectivity is lost, the mobile wireless node 305 may still be connected to another wireless device (e.g., a network entity, a gNB) within the coverage area of ​​the parent wireless node 310, where the wireless device may support the operation of the mobile wireless node 305. In addition, the mobile wireless node 305 may support a variety of other network connectivity modes (e.g., operating modes). Thus, if the wireless device supports the same network connectivity mode as the mobile wireless node 305, then despite the loss of wireless backhaul connectivity with the parent wireless node 310, the mobile wireless node 305 may use one of the network connectivity modes to provide service to the UE 115-b.

[0101] In some cases, the mobile wireless node 305 may send a control message 320 to the parent wireless node indicating one or more network connectivity modes supported by the mobile wireless node 305. When wireless backhaul connectivity between the mobile wireless node 305 and the parent wireless node 310 is lost, the one or more network connectivity modes may provide network connectivity to one or more UEs 115 (such as UE 115-b) via the mobile wireless node 305. In some examples, the network connectivity modes may include an IAB network connectivity mode (including IAB-MT and IAB-DU), a non-IAB relay network connectivity mode (including UE and network entity), a repeater network connectivity mode (including network controlled repeater (NCR), autonomous repeater (AR), or regular or basic repeater (BR)), a UE relay network connectivity mode, or any combination thereof. In addition, the wireless communication system 300 may support alternative network connectivity modes, and the mobile wireless node 305 may change its operating mode accordingly.

[0102] The mobile wireless node 305 may change its network connectivity operation mode. For example, the mobile wireless node 305 may receive a reply message 325 from the parent wireless node 310 indicating authorization to use at least the first network connectivity mode. Accordingly, the mobile wireless node 305 may communicate one or more messages 330 with the UE 115-b (e.g., a first UE in the one or more UEs 115) according to the first network connectivity mode. Figure 4 and Figure 5 Examples of communications according to other network connectivity modes are described.

[0103] In some cases, the mobile wireless node 305 may select a network connectivity mode (e.g., a service mode or an operating mode) for a particular UE 115 based on one or more factors. The parent wireless node 310 may authorize the mobile wireless node 305 to operate in all supported network connectivity modes or a subset thereof. For example, the mobile wireless node 305 may select a network connectivity mode based on the capabilities of the UE 115-b (e.g., the capability to support sidelink communications), quality of service (QoS) metrics (e.g., QoS requirements), radio resource management (RRM) measurements (e.g., of external cells), interference measurements (e.g., self-interference (SI) or cross-link interference (CLI) measurements), or any combination thereof. For example, if the UE 115-b is capable of supporting sidelink communications, the mobile wireless node 305 may use the UE relay network connectivity mode. Alternatively, if other network connectivity modes are associated with other performance levels, and if the UE 115-b is a low-latency device, the mobile wireless node 305 may select a repeater-based network connectivity mode because it may be the simplest and fastest (e.g., lowest latency) operating mode. Using RRM measurements, the mobile wireless node 305 may determine that the UE 115-b lacks a strong or available connection to an external cell, and may therefore select a relay- or repeater-based operating mode that is most appropriate for the UE 115-b. Alternatively, some UEs 115 may be instructed to connect directly to an external cell. For some network connectivity modes, some backhaul and access connections may interfere with each other, and the efficiency of the operation of the mobile wireless node 305 in full-duplex mode may depend on the level of SI or CLI.

[0104] The mobile wireless node 305 may indicate one or more network connectivity modes, one or more activated network connectivity modes, and one or more future network connectivity modes that it supports to the UE 115-b and any other UEs 115 in wireless communication with the mobile wireless node 305. That is, the mobile wireless node 305 may send an indication of a first network connectivity mode to one or more UEs 115 (e.g., via broadcast or dedicated RRC signaling). Additionally or alternatively, the mobile wireless node 305 may indicate the network connectivity modes that it supports to a network node, which may include a parent wireless node 310, an IAB donor node, a CU, a core network, a gNB, etc. For example, the mobile wireless node 305 may send a message to the parent wireless node 310 indicating that the mobile wireless node 305 is operating using the first network connectivity mode to communicate with the UE 115-b.

[0105] In some examples, the mobile wireless node 305 may change its supported or active network connectivity mode. The mobile wireless node 305 may receive an indication of the change in network connectivity mode from the parent wireless node 310, or send an indication of the change to the UE 115-b, or both. In addition, the mobile wireless node 305 may request a change in network connectivity mode (e.g., across a number of network connectivity modes). For example, the mobile wireless node 305 may send a request to the parent wireless node 310 to change between operating using a first network connectivity mode and operating using a second network connectivity mode, and the mobile wireless node 305 may receive an indication from the parent wireless node 310 to change from operating using the first network connectivity mode to operating using the second network connectivity mode.

[0106] In some cases, the parent wireless node 310 may authorize the change of the network connectivity mode, and in some cases, may indicate the rules or criteria associated with the change. For example, the reply message 325 may indicate authorization to use the second network connectivity mode, and indicate at least one criterion for changing between operating using the first network connectivity mode and operating using the second network connectivity mode. In some examples, based on the trajectory (e.g., movement path) of the mobile wireless node 305, the mobile wireless node 305 may request to change the network connectivity mode based on a specific time or a specific location (i.e., information that the mobile wireless node 305 can share a priori on various entities or interfaces). Some rules or criteria may be based on signal power that meets a configuration threshold, a cell identifier associated with the parent wireless node 310, or some other criteria. As used herein, depending on the context, "meeting a configuration threshold" may refer to a value greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc. In addition, the mobile wireless node 305 may send an indication of the change to one or more UEs 115 that are wirelessly communicating with the mobile wireless node 305.

[0107] Figure 4 An example of a network architecture 400 supporting mobile IAB connectivity according to one or more aspects of the present disclosure is illustrated. In some examples, the network architecture 400 may implement aspects of the wireless communication systems 100 and 300, or may be implemented by aspects of the wireless communication systems 100 and 300. The network architecture 400 may support one or more network connectivity modes 405 supported by a mobile wireless node (e.g., a mobile IAB node), such as those described herein. Figure 3 Depicted mobile wireless node 305. For example, network architecture 400 may include network connectivity mode 405-a, network connectivity mode 405-b, or network connectivity mode 405-c.

[0108] The network connectivity mode 405-a may represent IAB operation and may include an IAB node 430 (e.g., a mobile wireless node) having an IAB-MT 435 and an IAB-DU 440. The core network 410-a may communicate with an IAB-donor-CU 415 via a communication link, which may be an example of a communication link 125 or a communication link 315 described herein. The IAB-donor-CU 415 may communicate with an IAB-donor-DU 420 via a communication link, where the IAB-donor-CU 415 and the IAB-donor-DU 420 may be a parent wireless node 425 (e.g., a parent wireless node 425 described herein with reference to FIG. 1 ). Figure 3 In some examples, the IAB-donor-CU 415 and the IAB-donor-DU 420 may be components of the parent wireless node 310 described herein. Figure 1 and Figure 2 An example of a CU 160 and a DU 165 described. The IAB-DU 440 may provide connectivity to a UE 445-a via a Uu interface (e.g., a link) so that the IAB node 430 may communicate with the UE 445-a. Additionally, the IAB-MT 435 may be connected to the IAB-donor-DU 420 of the parent wireless node 425 via a Uu interface. If traffic is to be forwarded to the UE 445-a, the IAB node 430 may receive and decode traffic from the parent wireless node 425, and the IAB-DU 440 may schedule the traffic to be sent to the UE 445-a.

[0109] In some cases, the parent wireless node 425 may provide control signaling to the IAB node 430. For example, the IAB-donor-CU 415 may send control signaling to the IAB node 430 via an F1 control (F1C) interface or RRC signaling, and the IAB-donor-DU 420 may send control signaling to the IAB node 430 via L1 or L2 signaling. In some examples, the IAB-MT 435 may forward the signaling to the IAB-DU 440. In this way, the parent wireless node 425 may provide control signaling and wireless backhaul connectivity to the IAB node 430 so that the IAB node 430 can communicate with the UE 445-a.

[0110] In some examples, wireless backhaul connectivity between a mobile wireless node (e.g., a mobile IAB node) and a parent wireless node (e.g., an IAB parent node, a network entity) may be lost, for example, when the mobile wireless node moves to a location where connectivity with the parent wireless node is lost and therefore certain features of the mobile wireless node are not supported. In this case, the mobile wireless node may use network connectivity mode 405-b or network connectivity mode 405-c to emulate IAB operation based on its connectivity to another wireless device so that the mobile wireless node can maintain communication with UE 445.

[0111] The network connectivity mode 405-b may represent non-IAB relay operation and may include a relay UE (R-UE) and a gNB (e.g., network entity, base station). The network connectivity mode 405-b may support the full functionality of the gNB, supporting connectivity of the gNB to the core network 410-b via an IP connection and via the R-UE. The core network 410-b may communicate with the R-UE user plane function (UPF) 450 via a communication link. The R-UE UPF 450 may communicate with the gNB-CU 455-a via a communication link. In addition, the gNB-CU 455-a may communicate with the gNB-DU 460-a via a communication link, where the gNB-CU 455-a and the gNB-DU 460-a may be components of the gNB. In some examples, the gNB-CU 455-a and the gNB-DU 460-a may be respectively as described herein. Figure 1 and Figure 2 Examples of CU 160 and DU 165 are described.

[0112] The gNB-DU 460-a may provide connectivity to the UE 445-b via a Uu interface so that the gNB may communicate with the UE 445-b. Additionally, the gNB-DU 460-a of the gNB may be connected to the R-UE 470 of the wireless node 465. If traffic is to be forwarded to the UE 445-b, the R-UE 470 and the gNB 475 of the wireless node 465 may receive and decode traffic from the gNB-DU 460-a and schedule the traffic to be sent to the UE 445-b. For example, the R-UE 470 may receive a first grant from the gNB-DU 460-a that schedules the sending of a message associated with the UE 445-b to the R-UE 470. The R-UE 470 may receive the message based on the first grant and send a second grant to the gNB 475 that schedules the sending of the message to the UE 445-b. gNB 475 may send the message to UE 445-b based on the second grant. Thus, the connection from UE 445-b is terminated at gNB 475, and gNB 475 may process the signal for UE 445-b. In this way, gNB-CU 455-a and gNB-DU 460-a may provide connectivity to wireless node 465 so that wireless node 465 can communicate with UE 445-b when wireless backhaul connectivity with the parent wireless node is lost.

[0113] The network connectivity mode 405-c may represent UE relay operation. When the wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost, the network connectivity mode 405-c may emulate IAB operation based on the connectivity between the gNB and the UE 445-c. That is, if the UE 445-c is within the coverage area of ​​the gNB, the UE 445-c may effectively extend the coverage of the gNB to the UE 445-d outside the coverage area of ​​the gNB via sidelink communication.

[0114] In some examples, the core network 410-c may communicate with the gNB-CU 455-b via a communication link. The gNB-CU 455-b may communicate with the gNB-DU 460-b (e.g., NCR gNB-DU) via a communication link, where the gNB-CU 455-b and the gNB-DU 460-b may be components of the gNB. The gNB-CU 455-b and the gNB-DU 460-b may be respectively as described herein. Figure 1 and Figure 2 An example of a CU 160 and a DU 165 described. In some examples, the gNB-DU 460-b may provide connectivity to a UE relay 480 via a Uu interface, where the UE relay 480 may be a component of the UE 445-c. Additionally, the UE relay 480 may be connected to the UE 445-d via a PC5 interface so that the UE relay 480 may forward signaling from the gNB to the UE 445-d. In this way, connectivity from the gNB may be extended to the UE 445-d via the UE 445-c, where both the UE 445-c and the UE 445-d may support and communicate with each other via sidelink communications.

[0115] In some cases, the gNB may provide control signaling to UE 445-c. For example, gNB-CU 455-b may send control signaling to UE 445-c via RRC signaling, and gNB-DU 460-b may send control signaling to UE 445-c via RRC signaling. In some examples, UE relay 480 may forward signaling from the gNB to UE 445-d. In some cases, UE 445-d may send a capability message indicating that it supports sidelink communications. Therefore, the gNB may send an indication of the sidelink configuration of the network connectivity mode 405-c to UE 445-c via UE 445-c, so that sidelink communications can be achieved between UE 445-c and UE 445-d. In this way, the gNB may provide control signaling and wireless backhaul connectivity to UE 445-c, so that UE 445-d can communicate with UE 445-d via a sidelink connection.

[0116] Figure 5An example of a network architecture 500 supporting mobile IAB connectivity according to one or more aspects of the present disclosure is illustrated. In some examples, the network architecture 500 can implement aspects of the wireless communication systems 100 and 300, or can be implemented by aspects of the wireless communication systems 100 and 300. The network architecture 500 can support one or more network connectivity modes 505 supported by a mobile wireless node (e.g., a mobile IAB node), such as those described herein. Figure 3 The mobile wireless node 305 is described. For example, the network architecture 500 may include network connectivity mode 505-a, network connectivity mode 505-b, or network connectivity mode 505-c. The network connectivity mode 505 may represent various repeater-based operating modes, wherein the repeater 525 may receive, amplify, and forward signals from a gNB or other parent wireless node to the UE 540 (e.g., to extend coverage from the gNB to the UE 540). In some examples, the UE 540 may include a functional subset of an eMBB UE, but may also include additional features and functionality.

[0117] In some examples, wireless backhaul connectivity between a mobile wireless node (e.g., a mobile IAB node) and a parent wireless node (e.g., an IAB parent node, a network entity) may be lost, for example, when the mobile wireless node moves to a location where connectivity with the parent wireless node is lost and therefore certain features of the mobile wireless node are not supported. In this case, the mobile wireless node may use network connectivity mode 505 to emulate IAB operation based on its connectivity to another wireless device so that the mobile wireless node can maintain communication with UE 540. In some cases, to facilitate such connectivity, the forwarder 525 may receive a grant from a gNB or other parent wireless node that schedules the transmission of a message associated with UE 540 to the forwarder 525. The forwarder 525 may then relay the message to the UE 540 based on the grant.

[0118] The network connectivity mode 505-a may represent NCR operation. NCRs such as repeaters 525-a may be simulated repeaters that can be controlled by the network. For example, the network may configure the repeater to turn on and off, receive and forward signals in a specific direction, etc. In some examples, the core network 510-a may communicate with the gNB-CU 515-a via a communication link, which may be an example of the communication link 125 or the communication link 315 described herein. The gNB-CU 515-a may be connected to a gNB-DU 520-a (e.g., an NCR gNB-DU) via a communication link, where the gNB-CU 515-a and the gNB-DU 520-a may be components of a gNB or other parent wireless node. In some examples, the gNB-CU 515-a and the gNB-DU 520-a may be respectively as described herein with reference to Figure 1 and Figure 2 Examples of CU 160 and DU 165 are described.

[0119] In some examples, the repeater 525-a may include an RF / IF amplifier 535-a that forwards signaling to the UE 540-a via a Uu interface (e.g., a link). In addition, the repeater 525-a may include a UE 530-a (e.g., an NCR-UE) that is connected to a gNB (e.g., a network) via a Uu interface. In this way, the gNB-DU 520-a may be connected to the UE 530-a and the RF / IF amplifier 535-a of the repeater 525-a via a corresponding Uu interface. For example, the repeater 525-a may receive a signal from the gNB, and the RF / IF amplifier 535-a may amplify and forward the signal to the UE 540-a so that the repeater 525-a can provide connectivity between the UE 445-a and the gNB.

[0120] In some cases, the gNB may provide control signaling to the forwarder 525-a. For example, the gNB-CU 515-a may send control signaling to the forwarder 525-a via RRC signaling, and the gNB-DU 520-a may relay the control signaling to the forwarder 525-a via L1 or L2 signaling. In this way, the gNB may provide control signaling and wireless backhaul connectivity to the forwarder 525-a so that the gNB can communicate with the UE 540-a.

[0121] The network connectivity mode 505-b may represent AR (e.g., autonomous intelligent forwarder) operation. An AR such as a forwarder 525-b may autonomously receive, amplify, and forward signals in a particular direction to a UE such as a UE 540-b. That is, in the absence of instructions from a gNB (e.g., a network), the forwarder 525-b may determine the power, direction, and other factors associated with receiving, amplifying, and forwarding signals. In some examples, the core network 510-b may communicate with a gNB-CU 515-b via a communication link, which may be an example of a communication link 125 or a communication link 315 described herein. The gNB-CU 515-b may be connected to a gNB-DU 520-b (e.g., an NCR gNB-DU) via a communication link, where the gNB-CU 515-b and the gNB-DU 520-b may be components of a gNB or other parent wireless node. In some examples, the gNB-CU 515-b and the gNB-DU 520-b may be respectively as described herein with reference to Figure 1 and Figure 2 Examples of CU 160 and DU 165 are described.

[0122] In some examples, the repeater 525-b may include an RF / IF amplifier 535-b that forwards signaling to the UE 540-b via a Uu interface (e.g., a link). In addition, the repeater 525-b may include a UE 530-b (e.g., an AR-UE) that is connected to a gNB (e.g., a network) via a Uu interface. In this way, the gNB-DU 520-b may be connected to the UE 530-b and the RF / IF amplifier 535-b of the repeater 525-b via a corresponding Uu interface. For example, the repeater 525-b may receive a signal from the gNB, and the RF / IF amplifier 535-b may amplify and forward the signal to the UE 540-b so that the repeater 525-b can provide connectivity between the UE 445-b and the gNB.

[0123] The network connectivity mode 505-c may represent BR operation. A BR such as a repeater 525-c may perform basic receive, amplify, and forward operations for a UE 540-c. In some examples, the core network 510-c may communicate with a gNB-CU 515-c via a communication link, which may be an example of a communication link 125 or a communication link 315 described herein. The gNB-CU 515-c may be connected to a gNB-DU 520-c (e.g., an SR gNB-DU) via a communication link, where the gNB-CU 515-c and the gNB-DU 520-c may be components of a gNB or other parent wireless node. In some examples, the gNB-CU 515-c and the gNB-DU 520-c may be respectively as described herein with reference to Figure 1 and Figure 2 Examples of CU 160 and DU 165 are described.

[0124] In some examples, the repeater 525-c may include an RF / IF amplifier 535-c that forwards signaling to the UE 540-c via a Uu interface (e.g., a link). In addition, the repeater 525-c may include a UE 530-c (e.g., an AR-UE) that is connected to a gNB (e.g., a network) via a Uu interface. In this way, the gNB-DU 520-c may be connected to the UE 530-c and the RF / IF amplifier 535-c of the repeater 525-c via a corresponding Uu interface. For example, the repeater 525-c may receive a signal from the gNB, and the RF / IF amplifier 535-c may amplify and forward the signal to the UE 540-c so that the repeater 525-c can provide connectivity between the UE 445-c and the gNB.

[0125] Figure 6An example of a process flow 600 for supporting mobile IAB connectivity according to one or more aspects of the present disclosure is illustrated. The process flow 600 may implement aspects of the wireless communication systems 100 and 300, or may be implemented by aspects of the wireless communication systems 100 and 300. For example, the process flow 600 may illustrate operations between a UE 115-c, a mobile wireless node 605 (e.g., a mobile IAB node), and a parent wireless node 610 (e.g., an IAB parent node), which may be examples of corresponding devices described herein. In the following description of the process flow 600, operations between the UE 115-c, the mobile wireless node 605, and the parent wireless node 610 may be sent in an order different from the example order shown, or operations performed by the UE 115-c, the mobile wireless node 605, and the parent wireless node 610 may be performed in a different order or at a different time. Some operations may also be omitted from the process flow 600, and other operations may be added to the process flow 600.

[0126] At 615, the mobile wireless node 605 may send a control message to the parent wireless node 610 indicating one or more network connectivity modes supported by the mobile wireless node 605 for providing network connectivity to one or more UEs 115 (including UE 115-c) via the mobile wireless node 605 when wireless backhaul connectivity is lost between the mobile wireless node 605 and the parent wireless node 610. In some cases, the one or more network connectivity modes may include an IAB mode, a non-IAB relay mode, a repeater mode, a UE relay mode, or some other network connectivity mode.

[0127] At 620, the mobile wireless node 605 may receive a reply message from the parent wireless node 610 indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes. For example, based on one or more criteria (e.g., power conservation, UE capabilities), the parent wireless node 610 may authorize the mobile wireless node 605 to communicate with one or more UEs 115 using all supported network connectivity modes or a subset thereof.

[0128] At 625, the mobile wireless node 605 may send an indication to the parent wireless node 610 that the mobile wireless node 605 is operating using the first network connectivity mode to communicate with the UE 115-c (e.g., the first UE). Additionally, in some cases, the mobile wireless node 605 may send a request to change from operating using the first network connectivity mode to operating using the second network connectivity mode, and the parent wireless node 610 may authorize the mobile wireless node 605 to change its operation.

[0129] At 630, the mobile wireless node 605 may send an indication of the first network connectivity mode to the UE 115-c. That is, in some cases, the UE 115-c may be aware of the operation of the mobile wireless node 605 and its connectivity source. In other cases, the UE 115-c may not be aware of which network connectivity mode the mobile wireless node 605 is operating in.

[0130] The mobile wireless node 605 may communicate one or more messages with the UE 115-c according to the first network connectivity mode at 635. That is, the mobile wireless node 605 may communicate with the UE 115-c using wireless connectivity established based on the first network connectivity mode.

[0131] Figure 7 A block diagram 700 of a device 705 supporting mobile IAB connectivity according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of a mobile wireless node as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0132] Receiver 710 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, and information channels related to mobile IAB connectivity), user data, control information, or any combination thereof. The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0133] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, and information channels related to mobile IAB connectivity), user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0134] The communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof or various components thereof may be examples of means for performing various aspects of mobile IAB connectivity as described herein. For example, the communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0135] In some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0136] Additionally or alternatively, in some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be performed by a general purpose processor (e.g., a component configured or otherwise supported to perform the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0137] In some examples, the communication manager 720 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 can receive information from the receiver 710, transmit information to the transmitter 715, or integrate with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0138] According to examples as disclosed herein, the communication manager 720 may support wireless communications by a mobile wireless node. For example, the communication manager 720 may be configured to or otherwise support components for sending a control message to a parent wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes being used to provide network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost. The communication manager 720 may be configured to or otherwise support components for receiving a reply message from the parent wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes. The communication manager 720 may be configured to or otherwise support components for communicating one or more messages to a first UE of the one or more UEs according to the first network connectivity mode.

[0139] By including or configuring a communication manager 720 according to examples as described herein, the device 705 (e.g., a processor controlling the receiver 710, the transmitter 715, the communication manager 720, or a combination thereof or otherwise coupled thereto) can support techniques for mobile IAB connectivity that can increase signaling throughput, increase coverage of mobile IAB nodes, and improve communications between mobile IAB nodes and one or more UEs.

[0140] Figure 8 A block diagram 800 of a device 805 supporting mobile IAB connectivity according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the device 705 or mobile wireless node 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0141] The receiver 810 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, and information channels related to mobile IAB connectivity), user data, control information, or any combination thereof. The information may be passed to other components of the device 805. The receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0142] The transmitter 815 may provide means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, and information channels related to mobile IAB connectivity), user data, control information, or any combination thereof. In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0143] Device 805 or its various components may be examples of components for performing various aspects of mobile IAB connectivity as described herein. For example, communication manager 820 may include network connectivity mode component 825, reply message component 830, communication component 835, or any combination thereof. Communication manager 820 may be an example of various aspects of communication manager 720 as described herein. In some examples, communication manager 820 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, and send) using or otherwise in conjunction with receiver 810, transmitter 815, or both. For example, communication manager 820 may receive information from receiver 810, transmit information to transmitter 815, or integrate with receiver 810, transmitter 815, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0144] According to examples as disclosed herein, the communication manager 820 may support wireless communications by a mobile wireless node. The network connectivity mode component 825 may be configured to or otherwise support components for sending a control message indicating one or more network connectivity modes supported by the mobile wireless node to a parent wireless node, the one or more network connectivity modes being used to provide network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost. The reply message component 830 may be configured to or otherwise support components for receiving a reply message from the parent wireless node, the reply message indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes. The communication component 835 may be configured to or otherwise support components for communicating one or more messages to a first UE of the one or more UEs according to the first network connectivity mode.

[0145] Fig. 9 A block diagram 900 of a communication manager 920 supporting mobile IAB connectivity according to one or more aspects of the present disclosure is shown. The communication manager 920 may be an example of various aspects of the communication manager 720, the communication manager 820, or both as described herein. The communication manager 920 or its various components may be examples of components for performing various aspects of mobile IAB connectivity as described herein. For example, the communication manager 920 may include a network connectivity mode component 925, a reply message component 930, a communication component 935, an indication component 940, an indication component 945, a change component 950, an authorization component 955, a side link component 960, a relay component 965, a repeater component 970, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0146] According to examples as disclosed herein, the communication manager 920 may support wireless communications by a mobile wireless node. The network connectivity mode component 925 may be configured to or otherwise support components for sending a control message indicating one or more network connectivity modes supported by the mobile wireless node to a parent wireless node, the one or more network connectivity modes being used to provide network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost. The reply message component 930 may be configured to or otherwise support components for receiving a reply message from the parent wireless node, the reply message indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes. The communication component 935 may be configured to or otherwise support components for communicating one or more messages to a first UE of the one or more UEs according to the first network connectivity mode.

[0147] In some examples, indication component 940 may be configured or otherwise support means for sending an indication of the first network connectivity mode to the one or more UEs. In some examples, indication component 945 may be configured or otherwise support means for sending an indication to a parent wireless node that the mobile wireless node is operating using the first network connectivity mode to communicate with the first UE.

[0148] In some examples, the change component 950 can be configured as or otherwise support means for sending a request to a parent wireless node to change between operating using a first network connectivity mode and operating using a second network connectivity mode of the one or more network connectivity modes. In some examples, the change component 950 can be configured as or otherwise support means for receiving an indication from a parent wireless node to change between operating using a first network connectivity mode and operating using a second network connectivity mode.

[0149] In some examples, authorization component 955 may be configured to or otherwise support components for receiving a reply message from a parent wireless node indicating authorization to use a second of the one or more network connectivity modes and indicating at least one criterion for changing between operating using the first network connectivity mode and operating using the second network connectivity mode.

[0150] In some examples, changing component 950 may be configured as or otherwise support means for sending an indication to the one or more UEs to change between operating using a first network connectivity mode and operating using a second network connectivity mode.

[0151] In some examples, sidelink component 960 may be configured or otherwise support components for receiving a capability message indicating that the first UE supports sidelink communications. In some examples, sidelink component 960 may be configured or otherwise support components for sending an indication of a sidelink configuration for a first network connectivity mode.

[0152] In some examples, the relay component 965 may be configured to or otherwise support components for receiving a first grant from a parent wireless node, the first grant scheduling a message to be sent to a mobile wireless node, the message being associated with a first UE. In some examples, the relay component 965 may be configured to or otherwise support components for receiving a message based on the first grant. In some examples, the relay component 965 may be configured to or otherwise support components for sending a second grant, the second grant scheduling a message to be sent to the first UE. In some examples, the relay component 965 may be configured to or otherwise support components for sending a message to the first UE based on the second grant.

[0153] In some examples, the forwarder component 970 may be configured or otherwise support components for receiving a grant from a parent wireless node that schedules sending a message to a mobile wireless node that is associated with a first UE. In some examples, the forwarder component 970 may be configured or otherwise support components for relaying the message to the first UE based on the grant.

[0154] In some examples, the network connectivity mode component 925 may be configured to or otherwise support components for communicating with a first UE using a first network connectivity mode, where the first network connectivity mode is selected based on capabilities of the first UE, QoS metrics, RRM measurements, interference measurements, or any combination thereof.

[0155] Fig.10 A diagram of a system 1000 including a device 1005 supporting mobile IAB connectivity according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of a device 705, a device 805, or a mobile wireless node as described herein or include components of these devices. The device 1005 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1020, an I / O controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, a code 1035, and a processor 1040. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1045).

[0156] I / O controller 1010 can manage input signals and output signals of device 1005. I / O controller 1010 can also manage peripheral devices that are not integrated into device 1005. In some cases, I / O controller 1010 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1010 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1010 may be implemented as part of a processor, such as processor 1040. In some cases, a user may interact with device 1005 via I / O controller 1010 or via hardware components controlled by I / O controller 1010.

[0157] In some cases, the device 1005 may include a single antenna 1025. However, in some other cases, the device 1005 may have more than one antenna 1025, which is capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1015 may communicate bidirectionally via one or more antennas 1025, wired or wireless links as described herein. For example, the transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1015 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1025 for transmission; and demodulating packets received from one or more antennas 1025. The transceiver 1015 or the transceiver 1015 and one or more antennas 1025 may be examples of transmitters 715, transmitters 815, receivers 710, receivers 810, or any combination thereof or components thereof as described herein.

[0158] Memory 1030 may include RAM and ROM. Memory 1030 may store computer-readable, computer-executable code 1035 including instructions that, when executed by processor 1040, cause device 1005 to perform various functions described herein. Code 1035 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1035 may not be directly executable by processor 1040, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1030 may include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0159] Processor 1040 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1040. Processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) to enable device 1005 to perform various functions (e.g., functions or tasks supporting mobile IAB connectivity). For example, device 1005 or a component of device 1005 may include processor 1040 and memory 1030 coupled to or coupled to processor 1040, and processor 1040 and memory 1030 are configured to perform various functions described herein.

[0160] According to examples as disclosed herein, the communication manager 1020 may support wireless communications by a mobile wireless node. For example, the communication manager 1020 may be configured to or otherwise support components for sending a control message to a parent wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes being used to provide network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost. The communication manager 1020 may be configured to or otherwise support components for receiving a reply message from the parent wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes. The communication manager 1020 may be configured to or otherwise support components for communicating one or more messages to a first UE of the one or more UEs according to the first network connectivity mode.

[0161] By including or configuring the communication manager 1020 according to examples as described herein, the device 1005 can support techniques for mobile IAB connectivity that can increase signaling throughput, enhance coverage of mobile IAB nodes, and improve communications between mobile IAB nodes and one or more UEs.

[0162] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1015, one or more antennas 1025, or any combination thereof. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or executed by the processor 1040, the memory 1030, the code 1035, or any combination thereof. For example, the code 1035 may include instructions that can be executed by the processor 1040 to cause the device 1005 to perform various aspects of mobile IAB connectivity as described herein, or the processor 1040 and the memory 1030 may be otherwise configured to perform or support such operations.

[0163] Fig.11 A block diagram 1100 of a device 1105 supporting mobile IAB connectivity according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of a parent wireless node as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0164] Receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1105. In some examples, receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0165] The transmitter 1115 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0166] The communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof or various components thereof may be examples of means for performing various aspects of mobile IAB connectivity as described herein. For example, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0167] In some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0168] Additionally or alternatively, in some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0169] In some examples, communication manager 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in conjunction with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0170] According to examples as disclosed herein, the communication manager 1120 may support wireless communications by a parent wireless node. For example, the communication manager 1120 may be configured to or otherwise support components for receiving a control message from a mobile wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes being used to provide network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost. The communication manager 1120 may be configured to or otherwise support components for sending a reply message to the mobile wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes.

[0171] By including or configuring a communication manager 1120 according to the examples described herein, the device 1105 (e.g., a processor controlling the receiver 1110, the transmitter 1115, the communication manager 1120, or a combination thereof or otherwise coupled thereto) can support techniques for mobile IAB connectivity that can increase signaling throughput, increase coverage of mobile IAB nodes, and improve communications between mobile IAB nodes and one or more UEs.

[0172] Fig.12 A block diagram 1200 of a device 1205 supporting mobile IAB connectivity according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of aspects of the device 1105 or parent wireless node 115 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0173] Receiver 1210 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1205. In some examples, receiver 1210 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1210 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0174] The transmitter 1215 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1205. For example, the transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1215 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1215 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1215 and the receiver 1210 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0175] Device 1205 or its various components may be examples of components for performing various aspects of mobile IAB connectivity as described herein. For example, communication manager 1220 may include control message component 1225, reply component 1230, or any combination thereof. Communication manager 1220 may be an example of various aspects of communication manager 1120 as described herein. In some examples, communication manager 1220 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, and send) using or otherwise in conjunction with receiver 1210, transmitter 1215, or both. For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or integrate with receiver 1210, transmitter 1215, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0176] According to examples as disclosed herein, the communication manager 1220 can support wireless communications by a parent wireless node. The control message component 1225 can be configured to or otherwise support components for receiving a control message from a mobile wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes for providing network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost. The reply component 1230 can be configured to or otherwise support components for sending a reply message to the mobile wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes.

[0177] Fig.13 A block diagram 1300 of a communication manager 1320 supporting mobile IAB connectivity according to one or more aspects of the present disclosure is shown. The communication manager 1320 may be an example of aspects of the communication manager 1120, the communication manager 1220, or both as described herein. The communication manager 1320 or its various components may be examples of components for performing various aspects of mobile IAB connectivity as described herein. For example, the communication manager 1320 may include a control message component 1325, a reply component 1330, an indication receiving component 1335, a request component 1340, a change authorization component 1345, a grant component 1350, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0178] According to examples as disclosed herein, the communication manager 1320 can support wireless communications by a parent wireless node. The control message component 1325 can be configured to or otherwise support components for receiving a control message from a mobile wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes for providing network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost. The reply component 1330 can be configured to or otherwise support components for sending a reply message to the mobile wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes.

[0179] In some examples, indication receiving component 1335 may be configured or otherwise support components for receiving an indication from a mobile wireless node that the mobile wireless node is operating using a first network connectivity mode to communicate with a first UE.

[0180] In some examples, request component 1340 may be configured or otherwise support means for receiving a request from a mobile wireless node to change between operating using a first network connectivity mode and operating using a second network connectivity mode of the one or more network connectivity modes. In some examples, request component 1340 may be configured or otherwise support means for sending an indication to a mobile wireless node to change between operating using a first network connectivity mode and operating using a second network connectivity mode.

[0181] In some examples, the change authorization component 1345 may be configured as or otherwise support components for sending a reply message to the mobile wireless node indicating authorization to use a second network connectivity mode of the one or more network connectivity modes and indicating at least one criterion for changing between operating using the first network connectivity mode and operating using the second network connectivity mode.

[0182] In some examples, grant component 1350 may be configured or otherwise support components for sending a first grant to a mobile wireless node, the first grant scheduling a message to the mobile wireless node, the message associated with the first UE. In some examples, grant component 1350 may be configured or otherwise support components for sending a message based on the first grant.

[0183] In some examples, grant component 1350 may be configured or otherwise support components for sending a grant to a mobile wireless node, the grant scheduling sending a message to the mobile wireless node, the message associated with the first UE.

[0184] Fig.14 A diagram of a system 1400 of a device 1405 supporting mobile IAB connectivity according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of a device 1105, a device 1205, or a parent wireless node as described herein or include components of these devices. The device 1405 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1420, a transceiver 1410, an antenna 1415, a memory 1425, a code 1430, and a processor 1435. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1440).

[0185] The transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1410 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1410 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1405 may include one or more antennas 1415 that are capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1410 may also include a modem that is used to: modulate a signal; provide the modulated signal for transmission (e.g., via one or more antennas 1415, via a wired transmitter); receive the modulated signal (e.g., from one or more antennas 1415, from a wired receiver); and demodulate the signal. In some implementations, the transceiver 1410 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1415 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1415 configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1410 may include or be configured to be coupled to one or more processors or memory components, which may be operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination of the above. In some implementations, the transceiver 1410, or the transceiver 1410 and one or more antennas 1415, or the transceiver 1410 and one or more antennas 1415 and one or more processors or memory components (e.g., processor 1435 or memory 1425 or both) may be included in a chip or chip assembly installed in the device 1405. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0186] Memory 1425 may include RAM and ROM. Memory 1425 may store computer-readable, computer-executable code 1430 including instructions that, when executed by processor 1435, cause device 1405 to perform various functions described herein. Code 1430 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1430 may not be directly executable by processor 1435, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1425 may include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0187] Processor 1435 may include an intelligent hardware device (e.g., a general-purpose processor, DSP, ASIC, CPU, FPGA, microcontroller, programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof). In some cases, processor 1435 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1435. Processor 1435 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1425) to enable device 1405 to perform various functions (e.g., functions or tasks supporting mobile IAB connectivity). For example, device 1405 or a component of device 1405 may include processor 1435 and memory 1425 coupled to processor 1435, and processor 1435 and memory 1425 are configured to perform various functions described herein. Processor 1435 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software (such as an operating system, a virtual machine, or a container instance)), which may host functions (e.g., by executing code 1430) to perform functions of device 1405. The processor 1435 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1405 (such as in the memory 1425). In some specific implementations, the processor 1435 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce a set of outputs (which may be delivered to, for example, other systems or components of the device 1405). For example, the processing system of the device 1405 may refer to a system including various other components or subcomponents of the device 1405, such as the processor 1435, or the transceiver 1410, or the communication manager 1420, or other components or combinations of components of the device 1405. The processing system of the device 1405 may interface with other components of the device 1405, and may process information (such as inputs or signals) received from other components or output information to other components. For example, a chip or modem of the device 1405 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that the device 1405 can send information output from the chip or modem. Additionally or alternatively, in some specific implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, so that the device 1405 can obtain information or signal input, and the information can be passed to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0188] In some examples, bus 1440 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1440 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1405, or communications performed between different components of device 1405 that may be co-located or located in different locations (e.g., where device 1405 may refer to a system in which one or more of communication manager 1420, transceiver 1410, memory 1425, code 1430, and processor 1435 may be located in one of the different components or divided between the different components).

[0189] In some examples, the communication manager 1420 can manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1420 can manage the delivery of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 1420 can manage communications with other network entities 105 and can include a controller or scheduler for controlling communications with the UE 115 in coordination with the other network entities 105. In some examples, the communication manager 1420 can support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0190] According to examples as disclosed herein, the communication manager 1420 may support wireless communications by a parent wireless node. For example, the communication manager 1420 may be configured to or otherwise support components for receiving a control message from a mobile wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes being used to provide network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost. The communication manager 1420 may be configured to or otherwise support components for sending a reply message to the mobile wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes.

[0191] By including or configuring a communication manager 1420 according to examples as described herein, the device 1405 can support techniques for mobile IAB connectivity that can increase signaling throughput, improve coverage of mobile IAB nodes, and improve communications between mobile IAB nodes and one or more UEs.

[0192] In some examples, the communication manager 1420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof. Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or executed by the transceiver 1410, the processor 1435, the memory 1425, the code 1430, or any combination thereof. For example, the code 1430 may include instructions that can be executed by the processor 1435 to cause the device 1405 to perform various aspects of mobile IAB connectivity as described herein, or the processor 1435 and the memory 1425 may be otherwise configured to perform or support such operations.

[0193] Fig.15 1 is a flowchart illustrating a method 1500 for supporting mobile IAB connectivity according to one or more aspects of the present disclosure. The operations of the method 1500 may be implemented by a mobile wireless node or components thereof as described herein. For example, the operations of the method 1500 may be implemented by a mobile wireless node or components thereof as described herein. Figures 1 to 10 The described mobile wireless node performs. In some examples, the mobile wireless node may execute an instruction set to control the functional elements of the mobile wireless node to perform the described functions. Additionally or alternatively, the mobile wireless node may use dedicated hardware to perform various aspects of the described functions.

[0194] At 1505, the method may include sending a control message to the parent wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes for providing network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig. 9 The described network connectivity mode component 925 is executed.

[0195] At 1510, the method may include receiving a reply message from the parent wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig. 9 The described reply message component 930 is executed.

[0196] At 1515, the method may include communicating one or more messages to a first UE of the one or more UEs according to the first network connectivity mode. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig. 9 The described communication component 935 is executed.

[0197] Fig.16 1 is a flowchart illustrating a method 1600 for supporting mobile IAB connectivity according to one or more aspects of the present disclosure. The operations of the method 1600 may be implemented by a mobile wireless node or components thereof as described herein. For example, the operations of the method 1600 may be implemented by a mobile wireless node or components thereof as described herein. Figures 1 to 10 The described mobile wireless node performs. In some examples, the mobile wireless node may execute an instruction set to control the functional elements of the mobile wireless node to perform the described functions. Additionally or alternatively, the mobile wireless node may use dedicated hardware to perform various aspects of the described functions.

[0198] At 1605, the method may include sending a control message to the parent wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes for providing network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig. 9 The described network connectivity mode component 925 is executed.

[0199] At 1610, the method may include receiving a reply message from the parent wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig. 9 The described reply message component 930 is executed.

[0200] At 1615, the method may include sending an indication of the first network connectivity mode to the one or more UEs. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig. 9 The described instructions are performed by component 940.

[0201] At 1620, the method may include communicating one or more messages to a first UE of the one or more UEs according to the first network connectivity mode. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Fig. 9 The described communication component 935 is executed.

[0202] Fig.17 1 is a flowchart illustrating a method 1700 for supporting mobile IAB connectivity according to one or more aspects of the present disclosure. The operations of the method 1700 may be implemented by a mobile wireless node or components thereof as described herein. For example, the operations of the method 1700 may be implemented by a mobile wireless node or components thereof as described herein. Figures 1 to 10 The described mobile wireless node performs. In some examples, the mobile wireless node may execute an instruction set to control the functional elements of the mobile wireless node to perform the described functions. Additionally or alternatively, the mobile wireless node may use dedicated hardware to perform various aspects of the described functions.

[0203] At 1705, the method may include sending a control message to the parent wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes for providing network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig. 9 The described network connectivity mode component 925 is executed.

[0204] At 1710, the method may include receiving a reply message from the parent wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig. 9 The described reply message component 930 is executed.

[0205] At 1715, the method may include sending an indication to the parent wireless node that the mobile wireless node is operating using the first network connectivity mode to communicate with the first UE. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig. 9 The described instructions are performed by component 945.

[0206] At 1720, the method may include communicating one or more messages to a first UE of the one or more UEs according to the first network connectivity mode. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described in reference to Fig. 9 The described communication component 935 is executed.

[0207] Fig.18 1 is a flowchart illustrating a method 1800 for supporting mobile IAB connectivity according to one or more aspects of the present disclosure. The operations of the method 1800 may be implemented by a parent wireless node or components thereof as described herein. For example, the operations of the method 1800 may be implemented by a parent wireless node or components thereof as described herein. Figures 1 to 6 and Figures 11 to 14 In some examples, the parent wireless node may execute an instruction set to control the functional elements of the parent wireless node to perform the described functions. Additionally or alternatively, the parent wireless node may use dedicated hardware to perform various aspects of the described functions.

[0208] At 1805, the method may include receiving a control message from a mobile wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes for providing network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and a parent wireless node is lost. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.13 The described control message component 1325 is executed.

[0209] At 1810, the method may include sending a reply message to the mobile wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.13 The described reply component 1330 is executed.

[0210] Fig.19 1 is a flowchart illustrating a method 1900 for supporting mobile IAB connectivity according to one or more aspects of the present disclosure. The operations of the method 1900 may be implemented by a parent wireless node or components thereof as described herein. For example, the operations of the method 1900 may be implemented by a parent wireless node or components thereof as described herein. Figures 1 to 6 and Figures 11 to 14 In some examples, the parent wireless node may execute an instruction set to control the functional elements of the parent wireless node to perform the described functions. Additionally or alternatively, the parent wireless node may use dedicated hardware to perform various aspects of the described functions.

[0211] At 1905, the method may include receiving a control message from a mobile wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes for providing network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and a parent wireless node is lost. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Fig.13 The described control message component 1325 is executed.

[0212] At 1910, the method may include sending a reply message to the mobile wireless node indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described in reference to Fig.13 The described reply component 1330 is executed.

[0213] At 1915, the method may include receiving a request from the mobile wireless node to change between operating using the first network connectivity mode and operating using a second network connectivity mode of the one or more network connectivity modes. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described in reference to Fig.13 The described request component 1340 is executed.

[0214] At 1920, the method may include sending an indication to the mobile wireless node to change between operating using the first network connectivity mode and operating using the second network connectivity mode. The operations of 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed as described in reference to Fig.13 The described request component 1340 is executed.

[0215] Fig. 20 2000 for supporting mobile IAB connectivity according to one or more aspects of the present disclosure. The operations of the method 2000 may be implemented by a parent wireless node or components thereof as described herein. For example, the operations of the method 2000 may be implemented by a parent wireless node or components thereof as described herein. Figures 1 to 6 and Figures 11 to 14 In some examples, the parent wireless node may execute an instruction set to control the functional elements of the parent wireless node to perform the described functions. Additionally or alternatively, the parent wireless node may use dedicated hardware to perform various aspects of the described functions.

[0216] At 2005, the method may include receiving a control message from a mobile wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes for providing network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and a parent wireless node is lost. The operations of 2005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed as described in reference to Fig.13 The described control message component 1325 is executed.

[0217] At 2010, the method may include sending a reply message to the mobile wireless node, the reply message indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes. The operations of 2010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed as described in reference to Fig.13 The described reply component 1330 is executed.

[0218] At 2015, the method may include sending a grant to the mobile wireless node, the grant scheduling sending a message to the mobile wireless node, the message associated with the first UE. The operations of 2015 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2015 may be performed as described in reference to Fig.13 The described grant component 1350 is executed.

[0219] The following provides an overview of various aspects of the disclosure:

[0220] Aspect 1: A method for wireless communication by a mobile wireless node, the method comprising: sending a control message to a parent wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes being used to provide network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost; receiving a reply message from the parent wireless node, the reply message indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes; and conveying one or more messages to a first UE of the one or more UEs based on the first network connectivity mode.

[0221] Aspect 2: According to the method of aspect 1, the method also includes: sending an indication of the first network connectivity mode to the one or more UEs.

[0222] Aspect 3: According to the method according to any one of aspects 1 to 2, the method also includes: sending an indication to the parent wireless node that the mobile wireless node is operating using the first network connectivity mode to communicate with the first UE.

[0223] Aspect 4: According to the method described in any one of Aspects 1 to 3, the method further includes: sending a request to the parent wireless node to change between operating using the first network connectivity mode and operating using a second network connectivity mode among the one or more network connectivity modes; and receiving an indication from the parent wireless node to change between operating using the first network connectivity mode and operating using the second network connectivity mode.

[0224] Aspect 5: According to the method described in any one of Aspects 1 to 4, the method further includes: receiving a reply message from the parent wireless node, the reply message indicating authorization to use a second network connectivity mode among the one or more network connectivity modes and indicating at least one criterion for changing between operating using the first network connectivity mode and operating using the second network connectivity mode.

[0225] Aspect 6: According to the method according to any one of Aspects 1 to 5, the method also includes: sending an indication to the one or more UEs to change between operating using the first network connectivity mode and operating using the second network connectivity mode.

[0226] Aspect 7: According to the method described in any one of Aspects 1 to 6, the method further includes: receiving a capability message indicating that the first UE supports sidelink communication; and sending an indication of the sidelink configuration of the first network connectivity mode.

[0227] Aspect 8: According to the method described in any one of Aspects 1 to 7, the method also includes: receiving a first grant from the parent wireless node, the first grant scheduling sending a message to the mobile wireless node, the message being associated with the first UE; receiving the message based at least in part on the first grant; sending a second grant, the second grant scheduling sending the message to the first UE; and sending the message to the first UE based at least in part on the second grant.

[0228] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method also includes: receiving a grant from the parent wireless node, the grant scheduling sending a message to the mobile wireless node, the message being associated with the first UE; and relaying the message to the first UE based at least in part on the grant.

[0229] Aspect 10: According to any one of Aspects 1 to 9, the method further includes: communicating with the first UE using the first network connectivity mode, wherein the first network connectivity mode is selected at least in part based on the capabilities of the first UE, QoS metrics, RRM measurements, interference measurements, or any combination thereof.

[0230] Aspect 11: A method for wireless communication by a parent wireless node, the method comprising: receiving a control message from a mobile wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes being used to provide network connectivity to one or more UEs via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost; and sending a reply message to the mobile wireless node, the reply message indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes.

[0231] Aspect 12: The method according to aspect 11, the method further comprising: receiving an indication from the mobile wireless node that the mobile wireless node is operating using the first network connectivity mode to communicate with the first UE.

[0232] Aspect 13: According to the method described in any one of Aspects 11 to 12, the method further includes: receiving a request from the mobile wireless node to change between operating using the first network connectivity mode and operating using a second network connectivity mode among the one or more network connectivity modes; and sending an indication to the mobile wireless node to change between operating using the first network connectivity mode and operating using the second network connectivity mode.

[0233] Aspect 14: According to the method described in any one of Aspects 11 to 13, the method further includes: sending a reply message to the mobile wireless node, the reply message indicating authorization to use a second network connectivity mode among the one or more network connectivity modes and indicating at least one criterion for changing between operating using the first network connectivity mode and operating using the second network connectivity mode.

[0234] Aspect 15: According to the method described in any one of Aspects 11 to 14, the method also includes: sending a first grant to the mobile wireless node, the first grant scheduling sending a message to the mobile wireless node, the message being associated with the first UE; and sending the message at least partially based on the first grant.

[0235] Aspect 16: According to the method according to any one of aspects 11 to 15, the method further includes: sending a grant to the mobile wireless node, the grant scheduling sending a message to the mobile wireless node, and the message is associated with the first UE.

[0236] Aspect 17: A device for wireless communication by a mobile wireless node, the device comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the device to perform a method according to any one of Aspects 1 to 10.

[0237] Aspect 18: An apparatus for wireless communication by a mobile wireless node, the apparatus comprising: at least one component for performing the method according to any one of aspects 1 to 10.

[0238] Aspect 19: A non-transitory computer-readable medium storing a code for wireless communication by a mobile wireless node, the code comprising instructions executable by a processor to perform a method according to any one of aspects 1 to 10.

[0239] Aspect 20: An apparatus for wireless communication by a parent wireless node, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 11 to 16.

[0240] Aspect 21: An apparatus for wireless communication by a parent wireless node, the apparatus comprising: at least one component for performing the method according to any one of aspects 11 to 16.

[0241] Aspect 22: A non-transitory computer-readable medium storing a code for wireless communication by a parent wireless node, the code comprising instructions executable by a processor to perform a method according to any one of aspects 11 to 16.

[0242] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and other implementations are possible. In addition, aspects from two or more methods may be combined.

[0243] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0244] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0245] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0246] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions can also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0247] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transmitted from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device or can be used for carrying or storing desired program code parts and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disks and optical disks used herein include CDs, laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, while optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0248] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0249] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

[0250] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

[0251] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific implementation includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0252] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A device for wireless communication by a mobile wireless node, the device include: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending a control message to a parent wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes for providing network connectivity to one or more user equipment (UE) via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost; receiving a reply message from the parent wireless node, the reply message indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes; as well as One or more messages are communicated to a first UE of the one or more UEs according to the first network connectivity mode.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: An indication of the first network connectivity mode is sent to the one or more UEs.

3. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: An indication is sent to the parent wireless node that the mobile wireless node is operating using the first network connectivity mode to communicate with the first UE.

4. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: sending a request to the parent wireless node to change between operating using the first network connectivity mode and operating using a second network connectivity mode of the one or more network connectivity modes; and An indication is received from the parent wireless node to change between operating using the first network connectivity mode and operating using the second network connectivity mode.

5. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The reply message is received from the parent wireless node, the reply message indicating authorization to use a second network connectivity mode of the one or more network connectivity modes and indicating at least one criterion for changing between operating using the first network connectivity mode and operating using the second network connectivity mode.

6. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: An indication is sent to the one or more UEs to change between operating using the first network connectivity mode and operating using a second network connectivity mode.

7. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a capability message indicating that the first UE supports sidelink communication; and An indication of a sidelink configuration for the first network connectivity mode is sent.

8. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a first grant from the parent wireless node, the first grant scheduling transmission of a message to the mobile wireless node, the message associated with the first UE; receiving the message based at least in part on the first grant; sending a second grant, the second grant scheduling sending the message to the first UE; as well as The message is sent to the first UE based at least in part on the second grant.

9. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a grant from the parent wireless node, the grant scheduling transmission of a message to the mobile wireless node, the message being associated with the first UE; and The message is relayed to the first UE based at least in part on the grant.

10. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: communicating with the first UE using the first network connectivity mode, Wherein the first network connectivity mode is selected based at least in part on capabilities of the first UE, quality of service metrics, radio resource management measurements, interference measurements, or any combination thereof.

11. An apparatus for wireless communication by a parent wireless node, the apparatus include: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving a control message from a mobile wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes for providing network connectivity to one or more user equipment (UE) via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost; as well as A reply message is sent to the mobile wireless node, the reply message indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes.

12. The apparatus of claim 11, wherein the instructions are further executable by the processor to cause the apparatus to: An indication is received from the mobile wireless node that the mobile wireless node is operating using the first network connectivity mode to communicate with a first UE.

13. The apparatus of claim 11, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a request from the mobile wireless node to change between operating using the first network connectivity mode and operating using a second network connectivity mode of the one or more network connectivity modes; and An indication is sent to the mobile wireless node to change between operating using the first network connectivity mode and operating using the second network connectivity mode.

14. The apparatus of claim 11, wherein the instructions are further executable by the processor to cause the apparatus to: The reply message is sent to the mobile wireless node, the reply message indicating authorization to use a second network connectivity mode of the one or more network connectivity modes and indicating at least one criterion for changing between operating using the first network connectivity mode and operating using the second network connectivity mode.

15. The apparatus of claim 11, wherein the instructions are further executable by the processor to cause the apparatus to: sending a first grant to the mobile wireless node, the first grant scheduling sending a message to the mobile wireless node, the message being associated with a first UE; and The message is sent based at least in part on the first grant.

16. The apparatus of claim 11, wherein the instructions are further executable by the processor to cause the apparatus to: A grant is sent to the mobile wireless node, the grant scheduling sending a message to the mobile wireless node, the message being associated with a first UE.

17. A method for wireless communication by a mobile wireless node, the method include: sending a control message to a parent wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes for providing network connectivity to one or more user equipment (UE) via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost; receiving a reply message from the parent wireless node, the reply message indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes; as well as One or more messages are communicated to a first UE of the one or more UEs according to the first network connectivity mode.

18. The method according to claim 17, further comprising: include: An indication of the first network connectivity mode is sent to the one or more UEs.

19. The method according to claim 17, further comprising: include: An indication is sent to the parent wireless node that the mobile wireless node is operating using the first network connectivity mode to communicate with the first UE.

20. The method according to claim 17, further comprising: include: sending a request to the parent wireless node to change between operating using the first network connectivity mode and operating using a second network connectivity mode of the one or more network connectivity modes; as well as An indication is received from the parent wireless node to change between operating using the first network connectivity mode and operating using the second network connectivity mode.

21. The method according to claim 17, further comprising: include: A reply message is received from the parent wireless node, the reply message indicating authorization to use a second one of the one or more network connectivity modes and indicating at least one criterion for changing between operating using the first network connectivity mode and operating using the second network connectivity mode.

22. The method according to claim 17, further comprising: include: An indication is sent to the one or more UEs to change between operating using the first network connectivity mode and operating using a second network connectivity mode.

23. The method according to claim 17, further comprising: include: receiving a capability message indicating that the first UE supports sidelink communication; as well as An indication of a sidelink configuration for the first network connectivity mode is sent.

24. The method according to claim 17, further comprising: include: receiving a first grant from the parent wireless node, the first grant scheduling transmission of a message to the mobile wireless node, the message associated with the first UE; receiving the message based at least in part on the first grant; sending a second grant, the second grant scheduling sending the message to the first UE; as well as The message is sent to the first UE based at least in part on the second grant.

25. The method according to claim 17, further comprising: include: receiving a grant from the parent wireless node, the grant scheduling a message to be sent to the mobile wireless node, the message being associated with the first UE; as well as The message is relayed to the first UE based at least in part on the grant.

26. The method according to claim 17, further comprising: include: communicating with the first UE using the first network connectivity mode, Wherein the first network connectivity mode is selected based at least in part on capabilities of the first UE, quality of service metrics, radio resource management measurements, interference measurements, or any combination thereof.

27. A method for wireless communication by a parent wireless node, the method include: receiving a control message from a mobile wireless node indicating one or more network connectivity modes supported by the mobile wireless node, the one or more network connectivity modes for providing network connectivity to one or more user equipment (UE) via the mobile wireless node when wireless backhaul connectivity between the mobile wireless node and the parent wireless node is lost; as well as A reply message is sent to the mobile wireless node, the reply message indicating authorization to use at least a first network connectivity mode of the one or more network connectivity modes.

28. The method according to claim 27, further comprising: include: An indication is received from the mobile wireless node that the mobile wireless node is operating using the first network connectivity mode to communicate with a first UE.

29. The method according to claim 27, further comprising: include: receiving, from the mobile wireless node, a request to change between operating using the first network connectivity mode and operating using a second network connectivity mode of the one or more network connectivity modes; as well as An indication is sent to the mobile wireless node to change between operating using the first network connectivity mode and operating using the second network connectivity mode.

30. The method according to claim 27, further comprising: include: A reply message is sent to the mobile wireless node, the reply message indicating authorization to use a second one of the one or more network connectivity modes and indicating at least one criterion for changing between operating using the first network connectivity mode and operating using the second network connectivity mode.

Images