Signaling to support mobile integrated access and backhaul

Abstract

To provide a signaling to support mobile integrated access and backhaul.SOLUTION: Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a wireless communication device may receive mobility state information associated with an integrated access backhaul (IAB) node. The mobility state information may include information associated with at least one of a level of mobility of the IAB node, or a change in mobility of the IAB node. The wireless communication device may perform an operation based at least in part on the mobility state information associated with the IAB node. In some aspects, a wireless communication device may determine that mobility state information associated with an IAB node is to be transmitted, and may transmit the mobility state information associated with the IAB node based at least in part on the determination. Numerous other aspects are provided.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This patent application claims priority to U.S. Provisional Patent Application No. 62 / 884,584, filed August 8, 2019, entitled "SIGNALING TO SUPPORT MOBILE INTEGRATED ACCESS AND BACKHAUL," and U.S. Non-Provisional Patent Application No. 16 / 947,496, filed August 4, 2020, entitled "SIGNALING TO SUPPORT MOBILE INTEGRATED ACCESS AND BACKHAUL," both of which are expressly incorporated herein by reference.

[0002] Aspects of the present disclosure relate generally to wireless communications, and more particularly to techniques and apparatus for signaling to support mobility in integrated access and backhaul (IAB) networks. [Background technology]

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. A typical wireless communication system may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, or a combination thereof). Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the 3rd Generation Partnership Project (3GPP®).

[0004] The above multiple access technologies have been adopted in various telecommunications standards to provide common protocols that enable different user equipment (UE) devices to communicate at city, national, regional, and even global levels. New Radio (NR), sometimes referred to as 5G, is a set of extensions to the LTE mobile standard published by 3GPP. NR is designed to increase spectral efficiency, reduce costs, improve service, utilize new spectrum, better integrate with other open standards using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP-OFDM) on the downlink (DL) and CP-OFDM or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and better support mobile broadband Internet access by supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. However, as demand for mobile broadband access continues to grow, further improvements to LTE and NR technologies are needed. Preferably, these improvements are applicable to other multiple access technologies and telecommunications standards that employ these technologies.

[0005] A radio access network may include a wireless backhaul network, sometimes referred to as an integrated access and backhaul (IAB) network. In an IAB network, at least one base station acts as an anchor base station (also referred to as an IAB donor) that communicates with a core network (via a wired backhaul link). An IAB network may include one or more non-anchor base stations (also referred to as IAB nodes) that may communicate directly or indirectly (e.g., via one or more other non-anchor base stations) with the anchor base station via one or more wireless backhaul links to form a backhaul path to the core network. In a typical IAB network, the IAB nodes (e.g., non-anchor base stations) are fixed (i.e., not moving). Conversely, in a mobile IAB network, some of the IAB nodes may be moved or capable of movement throughout part or all of the IAB network. For example, such an IAB node (referred to herein as a "mobile IAB node") may be characterized as being in, or capable of being in, a state of movement (referred to herein as a "mobility state"). For example, mobile IAB nodes may be installed on vehicles (e.g., buses, trains, taxis). In a mobile IAB network, there may be a mix of fixed and mobile IAB nodes. The mobility state of a given IAB node may affect the operation of the mobile IAB network. For example, the execution of some IAB network-related operations may depend on the mobility state of the mobile IAB node. Such IAB network-related operations may include, for example, IAB topology and resource management, local scheduling, beam management, beam tracking, synchronization tracking, positioning, quality of service (QoS) type support identification, access, and paging, among other examples. Therefore, knowing the mobility state of a given IAB node may be desirable to facilitate the execution of a mobile IAB network. Summary of the Invention [Means for solving the problem]

[0006] In some aspects, a method of wireless communication performed by a wireless communication device may include receiving mobility state information associated with an integrated access backhaul (IAB) node, the mobility state information including information associated with at least one of a level of mobility of the IAB node or a change in mobility of the IAB node; and performing an action based at least in part on the mobility state information associated with the IAB node.

[0007] In some aspects, a method of wireless communication performed by a wireless communication device may include determining that mobility state information associated with an IAB node is to be transmitted, wherein the mobility state information includes information associated with at least one of a level of mobility of the IAB node or a change in mobility of the IAB node; and transmitting the mobility state information associated with the IAB node based at least in part on the determination that the mobility state information is to be transmitted.

[0008] In some aspects, a wireless communication device for wireless communication may include a memory and one or more processors operably coupled to the memory. The memory and the one or more processors may be configured to receive mobility state information associated with an IAB node, the mobility state information including information associated with at least one of a level of mobility of the IAB node or a change in mobility of the IAB node, and to perform an action based at least in part on the mobility state information associated with the IAB node.

[0009] In some aspects, a wireless communication device may include a memory and one or more processors operably coupled to the memory. The memory and the one or more processors may be configured to: determine that mobility state information associated with an IAB node is to be transmitted, the mobility state information including information associated with at least one of a level of mobility of the IAB node or a change in mobility of the IAB node; and transmit the mobility state information associated with the IAB node based at least in part on the determination that the mobility state information is to be transmitted.

[0010] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication that, when executed by one or more processors of a wireless communication device, may cause the one or more processors to receive mobility state information associated with an IAB node, the mobility state information including information associated with at least one of a level of mobility of the IAB node or a change in mobility of the IAB node, and perform an action based at least in part on the mobility state information associated with the IAB node.

[0011] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication that, when executed by one or more processors of a wireless communication device, may cause the one or more processors to: determine that mobility state information associated with an IAB node is to be transmitted, where the mobility state information includes information associated with at least one of a level of mobility of the IAB node or a change in mobility of the IAB node; and transmit the mobility state information associated with the IAB node based at least in part on the determination that the mobility state information is to be transmitted.

[0012] In certain aspects, an apparatus for wireless communication may include means for receiving mobility state information associated with an IAB node, the mobility state information including information associated with at least one of a level of mobility of the IAB node or a change in mobility of the IAB node; and means for performing an action based at least in part on the mobility state information associated with the IAB node.

[0013] In certain aspects, an apparatus for wireless communication may include means for determining that mobility state information associated with an IAB node is to be transmitted, the mobility state information including information associated with at least one of a level of mobility of the IAB node or a change in mobility of the IAB node; and means for transmitting the mobility state information associated with the IAB node based at least in part on the determination that the mobility state information is to be transmitted.

[0014] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, or processing system, as fully described with reference to and as illustrated by the drawings and this specification.

[0015] The foregoing has outlined rather broadly the features and technical advantages of examples according to the present disclosure so that the following detailed description may be better understood. Additional features and advantages are described below. The concepts and examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The nature of the concepts disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purpose of illustration and description, and not as a definition of the limits of the claims.

[0016] So that the above-mentioned features of the present disclosure can be understood in detail, a more detailed description briefly summarized above may be had by reference to embodiments, some of which are illustrated in the accompanying drawings. It should be noted, however, that the description may admit of other equally effective embodiments, and therefore the accompanying drawings illustrate only some typical embodiments of the present disclosure and should not be considered as limiting its scope. The same reference numbers in different drawings may identify the same or similar elements. [Brief explanation of the drawings]

[0017] [Figure 1] FIG. 1 is a block diagram illustrating an example wireless network in accordance with various aspects of the present disclosure. [Figure 2] FIG. 1 is a block diagram illustrating an example base station (BS) in communication with a user equipment (UE) in a wireless network, in accordance with various aspects of the present disclosure. [Figure 3] FIG. 1 illustrates an example of a wireless access network, in accordance with various aspects of the present disclosure. [Figure 4] FIG. 1 illustrates an example of an integrated access and backhaul (IAB) network architecture in accordance with various aspects of the present disclosure. [Figure 5] FIG. 1 illustrates an example of signaling for support of mobile IAB networking, in accordance with various aspects of the present disclosure. [Figure 6] FIG. 1 illustrates an example process performed by a wireless communication device supporting mobile IAB, according to various aspects of the present disclosure. [Figure 7] FIG. 1 illustrates an example process performed by a wireless communication device supporting mobile IAB, according to various aspects of the present disclosure. [Figure 8] FIG. 1 is a block diagram of an example apparatus for wireless communication in accordance with various aspects of the present disclosure. [Figure 9]FIG. 1 is a block diagram of an example apparatus for wireless communication in accordance with various aspects of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0018] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will appreciate that the scope of the present disclosure encompasses any aspect of the present disclosure disclosed herein, whether implemented independently or in combination with any other aspect of the present disclosure. For example, an apparatus may be implemented or a method may be practiced using any amount of the aspects described herein. In addition, the scope of the present disclosure encompasses such apparatuses or methods practiced using other structure, functions, or structure and functions in addition to or other than the various aspects of the present disclosure described herein. Any aspect of the present disclosure disclosed herein may be embodied by one or more elements of a claim.

[0019] Several aspects of telecommunications systems are now presented with reference to various apparatus and techniques. These apparatus and techniques are described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, or combinations thereof (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0020] It should be noted that although aspects may be described herein using terminology commonly associated with 3G or 4G wireless technology, aspects of the present disclosure may be applied in other generation-based communication systems, such as 5G and beyond, including NR technology.

[0021] In a typical IAB network, IAB nodes (e.g., non-anchor base stations) are fixed (i.e., not moving). Conversely, in a mobile IAB network, some of the IAB nodes may be moved or capable of movement throughout part or all of the IAB network. For example, such IAB nodes (referred to herein as "mobile IAB nodes") may be characterized as being in or capable of being in a state of movement (referred to herein as a "mobility state"). For example, IAB nodes may be installed on vehicles (e.g., buses, trains, taxis) to provide network access to passengers within the vehicle. In a mobile IAB network, there may be a mix of fixed and mobile IAB nodes.

[0022] Information associated with the mobility state of an IAB node (referred to herein as mobility state information) may include, for example, information representing a level of mobility (e.g., fixed, slow mobility, medium mobility, fast mobility). As another example, mobility state information may include information representing a change or transition from one level of mobility to another (e.g., an IAB node's level of mobility may change or transition over time). For example, a mobile IAB node may transition to fixed (e.g., from slow mobility) or may transition from one mobility class to another mobility class (e.g., from medium mobility to fast mobility).

[0023] The mobility state of a given IAB node may affect the operation of a mobile IAB network. For example, the execution of several IAB network-related operations may depend on the mobility state of the mobile IAB node. Such IAB network-related operations may include, for example, IAB topology and resource management, local scheduling, beam management, beam tracking, synchronization tracking, positioning, QoS type support, access, and paging, among other examples. Therefore, knowing the mobility state of a given IAB node may be desirable to facilitate efficient operation and acceptable performance of a mobile IAB network.

[0024] Certain aspects described herein provide techniques and apparatus for signaling to support mobility in an IAB network (also referred to herein as supporting “mobile IAB”). In some aspects, as described below, mobility state information (e.g., including information associated with a given IAB node's level of mobility or mobility changes) may be received, transmitted, or requested by various nodes (e.g., an IAB donor, a non-donor IAB node, or a UE) in a mobile IAB network. For example, a wireless communication device, such as an IAB donor or an IAB node, may receive mobility state information associated with another IAB node and perform an operation based at least in part on the mobility state information. The operation may include, for example, transmitting or relaying the mobility state information to another device in the IAB network, or may include an IAB network-related operation, such as an operation associated with IAB topology and resource management, local scheduling, beam management, beam tracking, synchronization tracking, positioning, QoS type support, access, or paging. In some aspects, signaling over different interfaces and at different protocol stack layers may be defined to support transmission and reception of mobility state information, as described below.

[0025] Certain aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages: In some aspects, the described signaling for supporting mobile IAB allows the mobility state or other movement characteristics of a given IAB node to be taken into account by the IAB network. Taking IAB node mobility into account can improve the performance of IAB network-related operations that may be affected by the mobility of a given IAB node. Thus, the signaling for supporting mobile IAB can improve the overall performance of the IAB network and increase the efficiency (e.g., with respect to resource utilization) of the IAB network.

[0026] 1 is a block diagram illustrating an exemplary wireless network in accordance with various aspects of the present disclosure. The wireless network may be a Long Term Evolution (LTE) network or some other wireless network, such as a 5G or NR network. The wireless network may include multiple base stations (BSs) 110 (denoted as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A BS is an entity that communicates with user equipment (UE) and may also be referred to as a Node B, eNode B, eNB, gNB, NR BS, 5G Node B (NB), access point (AP), transmit reception point (TRP), or combinations thereof (these terms are used interchangeably herein). Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to the coverage area of ​​a BS serving this coverage area or a BS subsystem, depending on the context in which the term is used.

[0027] A BS may provide communication coverage for a macrocell, a picocell, a femtocell, or another type of cell. A macrocell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs with service subscriptions. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs that have an association with the femtocell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS for a macrocell may be referred to as a macroBS. A BS for a picocell may be referred to as a picoBS. A BS for a femtocell may be referred to as a femtoBS or homeBS. A BS may support one or multiple (e.g., three) cells.

[0028] A wireless network may be a heterogeneous network including different types of BSs, such as macro BSs, pico BSs, femto BSs, relay BSs, or a combination thereof. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in the wireless network. For example, a macro BS may have a high transmit power level (e.g., 5-40 watts), while pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1-2 watts). In the example shown in FIG. 1, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. Network controller 130 may couple to the set of BSs 110a, 110b, 110c, and 110d and may provide coordination and control for these BSs. Network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with one another directly or indirectly, eg, via wireless or wireline backhaul.

[0029] In some aspects, the cells may not be fixed; rather, the geographic area of ​​the cells may move according to the location of the mobile BS. In some aspects, the BSs may be interconnected to each other or to one or more other BSs or network nodes (not shown) in a wireless network through various types of backhaul interfaces, such as direct physical connections, virtual networks, or combinations thereof, using any suitable transport network.

[0030] A wireless network may also include relay stations. A relay station is an entity that can receive data transmissions from an upstream station (e.g., a BS or a UE) and send data transmissions to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. In the example shown in FIG. 1, relay station 110d may communicate with macro BS 110a and UE 120d to facilitate communication between BS 110a and UE 120d. A relay station may also be referred to as a relay BS, a relay base station, a relay, or a combination thereof.

[0031] UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout a wireless network, and each UE may be fixed or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, or a combination thereof. A UE may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate over a wireless medium.

[0032] Some UEs may be considered machine type communication (MTC) UEs or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and eMTC UEs include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, a location tag, or a combination thereof, that may communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered customer premises equipment (CPE). The UE 120 may be included within a housing that houses components of the UE 120, such as a processor component, a memory component, or a combination thereof.

[0033] Generally, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies or frequency channels. A frequency may also be referred to as a carrier, or a combination thereof. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different radio access technologies (RATs). In some cases, an NR RAT network or a 5G RAT network may be deployed.

[0034] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly with each other (e.g., without using a base station 110 as an intermediary) using one or more sidelink channels. For example, the UEs 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, a vehicle-to-everything (V2X) protocol (which may include, e.g., a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a combination thereof), a mesh network, or a combination thereof. In this case, the UEs 120 may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by the base station 110.

[0035] 2 is a block diagram illustrating an example base station (BS) in communication with user equipment (UE) in a wireless network in accordance with various aspects of the present disclosure. Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≧1 and R≧1.

[0036] At base station 110, transmit processor 220 may receive data for one or more UEs from data source 212, select one or more modulation and coding schemes (MCSs) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode) the data for each UE based at least in part on the MCS selected for the UE, and provide data symbols to all UEs. Transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI), or a combination thereof) and control information (e.g., CQI requests, grants, upper layer signaling, or a combination thereof) and provide overhead symbols and control symbols. Transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRSs)) and synchronization signals (e.g., primary synchronization signals (PSSs) and secondary synchronization signals (SSSs)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, or reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each MOD 232 may process a respective output symbol stream (e.g., for OFDM, or a combination thereof) to obtain an output sample stream. Each MOD 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from MODs 232a through 232t may be transmitted via T antennas 234a through 234t, respectively. According to various aspects described in more detail below, synchronization signals may be generated using location coding to convey additional information.

[0037] At UE 120, antennas 252a through 252r may receive downlink signals from base station 110 or other base stations and may provide received signals to R demodulators (DEMODs) 254a through 254r, respectively. Each DEMOD 254 may condition (e.g., filter, amplify, downconvert, and digitize) its received signal to obtain input samples. Each DEMOD 254 may further process the input samples (e.g., for OFDM, or a combination thereof) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R DEMODs 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 may process (e.g., decode) the detected symbols and provide decoded data for UE 120 to a data sink 260 and may provide decoded control and system information to controller / processor 280. The channel processor may determine a reference signal received power (RSRP), a received signal strength indicator (RSSI), a reference signal received quality (RSRQ), a channel quality indicator (CQI), or a combination thereof. In some aspects, one or more components of the UE 120 may be included within a housing.

[0038] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 as well as control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, CQI, or a combination thereof). The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if applicable, further processed by MODs 254a-254r (e.g., for discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM), orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM), or a combination thereof), and transmitted to the base station 110. At the base station 110, uplink signals from the UE 120 and other UEs may be received by an antenna 234, processed by a DEMOD 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0039] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, or any other component of FIG. 2 may perform one or more techniques associated with signaling to support mobile integrated access and backhaul (IAB), as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, or any other component of FIG. 2 may perform or direct the operation of, for example, the process of FIG. 6, the process of FIG. 7, or other processes as described herein. The memories 242 and 282 may store data and program codes for the base station 110 and the UE 120, respectively. The scheduler 246 may schedule UEs for data transmission on the downlink or uplink.

[0040] In some aspects, a wireless communications device (e.g., a base station 110) may include means for receiving mobility state information associated with an IAB node, where the mobility state information includes information associated with at least one of a level of mobility of the IAB node or a change in mobility of the IAB node, means for performing an action based at least in part on the mobility state information associated with the IAB node, or a combination thereof. In some aspects, such means may include one or more components of the base station 110 described with respect to FIG.

[0041] In some aspects, a wireless communications device (e.g., a base station 110) may include means for determining that mobility state information associated with an IAB node is to be transmitted, where the mobility state information includes information associated with at least one of a level of mobility of the IAB node or a change in mobility of the IAB node, means for transmitting the mobility state information associated with the IAB node based at least in part on the determination that the mobility state information is to be transmitted, or a combination thereof. In some aspects, such means may include one or more components of the base station 110 described with respect to FIG.

[0042] 3 is a diagram illustrating an example of a radio access network in accordance with various aspects of the present disclosure. As indicated by reference numeral 305, a conventional (e.g., 3G, 4G, LTE, 5G, NR) radio access network may include multiple base stations 310 (e.g., access nodes (ANs)), where each base station 310 communicates with a core network via a wired backhaul link 315, such as a fiber connection. The base stations 310 may communicate with a UE 320 via a wireless access link 325. In some aspects, the base station 310 illustrated in FIG. 3 may correspond to the base station 110 illustrated in FIG. 1. Similarly, the UE 320 illustrated in FIG. 3 may correspond to the UE 120 illustrated in FIG. 1.

[0043] As indicated by reference numeral 330, the radio access network may include a wireless backhaul network, sometimes referred to as an integrated access and backhaul (IAB) network. In an IAB network, at least one base station is an anchor base station 335 that communicates with a core network via a wired backhaul link 340, such as a fiber connection. The anchor base station 335 may also be referred to as an IAB donor. The IAB network may include one or more non-anchor base stations 345, sometimes referred to as relay base stations or simply IAB nodes. The non-anchor base stations 345 may communicate directly or indirectly (e.g., via one or more other non-anchor base stations 345) with the anchor base station 335 via one or more wireless backhaul links 350 to form a backhaul path to the core network for carrying backhaul traffic. That is, in some aspects, the IAB network may be a multi-hop network, also referred to herein as a multi-hop wireless backhaul. In some aspects, each node in the IAB network may use the same radio access technology (e.g., 5G / NR). An anchor base station 335 or a non-anchor base station 345 may communicate with one or more UEs 355 via a wireless access link 360 that carries access traffic. In some aspects, nodes of an IAB network may share resources for access links and backhaul links, such as time, frequency, or spatial resources. In some aspects, the anchor base station 335 or the non-anchor base station 345 shown in FIG. 3 may correspond to the base station 110 shown in FIG. 1. Similarly, the UE 355 shown in FIG. 3 may correspond to the UE 120 shown in FIG. 1.

[0044] As indicated by reference numeral 365, in some aspects, a radio access network, including an IAB network, may utilize millimeter wave technology or directional communications (e.g., beamforming, precoding) for communications between base stations or UEs (e.g., between two base stations, between two UEs, or between a base station and a UE). For example, a wireless backhaul link 370 between base stations may use millimeter waves to carry information that may be directed to a target base station using precoding or beamforming. Similarly, a wireless access link 375 between a UE and a base station may use millimeter waves that may be directed to a target wireless node (e.g., a UE or a base station). By using beamforming for directional transmissions, link-to-link interference may be reduced.

[0045] In some aspects, an IAB donor includes a central unit (CU) that configures IAB nodes that access the core network through the IAB donor and a distributed unit (DU) that schedules and communicates with child nodes of the IAB donor. In some aspects, an IAB node includes a mobile termination component (MT) that is scheduled by and communicates with the DU of a parent node and a DU that schedules and communicates with child nodes of the IAB node. The DU of an IAB node may perform the functions described with respect to a base station for that IAB node, and the MT of an IAB node may perform the functions described with respect to a UE for that IAB node.

[0046] FIG. 4 illustrates an example of an IAB network architecture according to various aspects of the present disclosure. As shown in FIG. 4, the IAB network may include an IAB donor 405 that connects to a core network via a wired connection (e.g., as a wireline fiber). For example, the Ng interface of the IAB donor 405 may terminate in the core network. Additionally or alternatively, the IAB donor 405 may connect to one or more devices of the core network that provide core access and mobility management functions (AMF). In some aspects, the IAB donor 405 may include a base station 110, such as an anchor base station, as described above with respect to FIG. 3. As shown, the IAB donor 405 may include a CU, which may perform ANC or AMF functions. The CU may constitute a DU of the IAB donor 405 or may constitute one or more IAB nodes 410 (e.g., MTs or DUs of the IAB node 410) that connect to the core network via the IAB donor 405. Thus, the CU of the IAB donor 405 may control or configure the entire IAB network that connects to the core network via the IAB donor 405, such as by using control or configuration messages (e.g., Radio Resource Control (RRC) configuration messages, or F1 Application Protocol (F1AP) messages).

[0047] As described above, an IAB network may include non-donor IAB nodes 410 (denoted as IAB nodes 1-4) that connect to a core network via an IAB donor 405. As shown, an IAB node 410 may include an MT and a DU. An MT of an IAB node 410 (e.g., a child node) may be controlled or scheduled by another IAB node 410 (e.g., a parent node) or by the IAB donor 405. A DU of an IAB node 410 (e.g., a parent node) may control or schedule other IAB nodes 410 (e.g., child nodes of a parent node) or UEs 120. Thus, a DU may be referred to as a scheduling node or scheduling component, and an MT may be referred to as a scheduled node or scheduled component. In some aspects, an IAB donor 405 may include a DU but not an MT. That is, a CU of an IAB donor 405 may configure, control, or schedule communications for all IAB nodes 410 or UEs 120. As another example, the UE 120 may include only an MT and no DU, i.e., the UE 120's communications may be entirely controlled or scheduled by the IAB donor 405 or IAB node 410 (e.g., the UE 120's parent node).

[0048] When a first node controls or schedules communications for a second node (e.g., when the first node provides DU functionality for the second node's MT), the first node may be referred to as the second node's parent node, and the second node may be referred to as the first node's child node. Similarly, the second node's child node may be referred to as the first node's grandchild node. Thus, the parent node's DU may control or schedule communications for the parent node's child node, as well as, in some cases, the parent node's grandchild node. A parent node may be an IAB donor 405 or an IAB node 410 with at least one child node, while a child node may be a UE 120 or an IAB node 410 with at least one parent node. Communications of the child node's MT may be controlled or scheduled by the child node's parent node.

[0049] 4, the direct link between the UE 120 and the IAB donor 405 or between the UE 120 and the IAB node 410 may be referred to as an access link 415. Each access link 415 may be a direct wireless access link between the respective devices that ultimately provides the UE 120 with access to the core network via the IAB donor 405 (and potentially via one or more backhaul links between the IAB node 410 and the IAB donor 405, as described in more detail below).

[0050] As further shown in FIG. 4, the wireless link between an IAB donor 405 and an IAB node 410, or between two IAB nodes 410, may be referred to as a backhaul link 420. Each backhaul link 420 may be a wireless backhaul link that provides the IAB node 410 with wireless access to the core network via the IAB donor 405, and potentially via one or more other intermediate IAB nodes 410 and associated backhaul links 420. In some aspects, the backhaul link 420 may be a primary backhaul link or a secondary backhaul link (e.g., a backup backhaul link to the same parent node or to a different parent node). In some aspects, the secondary backhaul link may be used if the primary backhaul link fails, is congested, or is overloaded. In an IAB network, network resources (e.g., time resources, frequency resources, spatial resources) for wireless communication may be shared between the access link 415 and the backhaul link 420.

[0051] As described above, in a typical IAB network, IAB nodes (e.g., non-anchor base stations) are fixed (i.e., not moving). Conversely, in a mobile IAB network, some of the IAB nodes may be moved or capable of movement throughout part or all of the IAB network. For example, such IAB nodes (referred to herein as "mobile IAB nodes") may be characterized as being in or capable of being in a state of movement (referred to herein as a "mobility state"). For example, IAB nodes may be installed on vehicles (e.g., buses, trains, taxis). In a mobile IAB network, there may be a mix of fixed and mobile IAB nodes. In some cases, mobile IAB nodes may be constrained to be "leaf" nodes in the mobile IAB network. For example, a mobile IAB node may be permitted to be only a last-hop IAB node, i.e., an IAB node that is not permitted to have any child IAB nodes. In some other cases, a mobile IAB node may also be permitted to have another IAB node as a child node.

[0052] In some examples, a mobile IAB node may provide an independently moving cell site. In such cases, a moving cell site (e.g., a vehicle such as a bus, train, or taxi) may serve surrounding UEs (e.g., in an urban area). Depending on various factors such as the type of vehicle, the mobile IAB node may move relatively randomly, at relatively slow speeds (e.g., urban speeds), or over relatively large distances. In such examples, the mobility of a given UE not carried in or on a vehicle is independent of the mobility of the IAB node (i.e., the UE's movement is not predictable based on the movement of the mobile IAB node), but may also be at a relatively slow speed (similar to the mobile IAB node).

[0053] In some other examples, a mobile IAB node may serve a cell site (e.g., a high-speed train) that moves together. In such cases, the mobile IAB node may be mounted in or on the moving cell site (e.g., on a high-speed train) to serve UEs on or within the moving cell site (e.g., UEs inside the high-speed train). Here, the movement of the mobile IAB node is predictable at relatively high speeds and may span large distances. In this use case, the UEs on or within the moving cell site move together with the mobile IAB node (i.e., the UE's movement is predictable based on the movement of the mobile IAB node).

[0054] In some other examples, a mobile IAB node may facilitate platooning, for example, when a loose group of UEs are traveling together. In such cases, a single IAB node may provide network connectivity for multiple nearby UEs. For example, a mobile IAB node mounted on a first vehicle traveling on a highway may provide network connectivity for UEs in the first vehicle as well as for UEs in other vehicles in the vicinity of the first vehicle that may be traveling on the highway in the same direction and at a similar speed. In such cases, the mobile IAB node connects to the network, but the other vehicles may house their own child nodes. Here, the mobile IAB node moves at a relatively constant speed and over relatively large distances with local predictability. Furthermore, the UEs travel together with the mobile IAB node.

[0055] Information associated with the mobility state of an IAB node (referred to herein as mobility state information) may include, for example, information representing a level of mobility (e.g., fixed, slow mobility, medium mobility, fast mobility). As another example, mobility state information may include information representing a change or transition from one level of mobility to another (e.g., an IAB node's level of mobility may change or transition over time). For example, a mobile IAB node may transition to fixed (e.g., from slow mobility) or may transition from one mobility class to another mobility class (e.g., from medium mobility to fast mobility). In some instances, there may be a timer associated with such transitions (e.g., an IAB node may transition from one state to another within an indicated time window).

[0056] The mobility state of a given IAB node may affect the operation of a mobile IAB network. For example, the execution of several IAB network-related operations may depend on the mobility state of the mobile IAB node. Such IAB network-related operations may include, for example, IAB topology and resource management, local scheduling, beam management, beam tracking, synchronization tracking, positioning, QoS type support, access, and paging, among other examples. Therefore, knowing the mobility state of a given IAB node may be desirable to facilitate efficient and acceptable execution of a mobile IAB network.

[0057] Certain aspects described herein provide techniques and apparatus for signaling to support mobility in an IAB network (also referred to herein as supporting “mobile IAB”). In some aspects, as described below, mobility state information (e.g., including information associated with a given IAB node's level of mobility or mobility changes) may be received, transmitted, or requested by various nodes (e.g., an IAB donor, a non-donor IAB node, or a UE) in a mobile IAB network. For example, a wireless communication device, such as an IAB donor or an IAB node, may receive mobility state information associated with another IAB node and perform an operation based at least in part on the mobility state information. The operation may include, for example, transmitting or relaying the mobility state information to another device in the IAB network, or may include an IAB network-related operation, such as an operation associated with IAB topology and resource management, local scheduling, beam management, beam tracking, synchronization tracking, positioning, QoS type support, access, or paging. In some aspects, signaling over different interfaces and at different protocol stack layers may be defined to support transmission and reception of mobility state information, as described below.

[0058] Certain aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages: In some aspects, the described signaling for supporting mobile IAB allows the mobility state or other movement characteristics of a given IAB node to be taken into account by the IAB network. Taking IAB node mobility into account can improve the performance of IAB network-related operations that may be affected by the mobility of a given IAB node. Thus, the signaling for supporting mobile IAB can improve the overall performance of the IAB network and increase the efficiency (e.g., with respect to resource utilization) of the IAB network.

[0059] 5 illustrates an example diagram relating to signaling for supporting mobile IAB networking in accordance with various aspects of the present disclosure. In FIG. 5, a first wireless communication device (identified as WCD1) and a second wireless communication device (identified as WCD2) are nodes in a mobile IAB network. In some aspects, the first wireless communication device may be an IAB node, such as the first base station 110, the first anchor base station 335, the first non-anchor base station 345, the first IAB donor 405, or the first IAB node 410. Similarly, the second wireless communication device may be another IAB node, such as the second base station 110, the second anchor base station 335, the second non-anchor base station 345, the second IAB donor 405, or the second IAB node 410.

[0060] As shown in FIG. 5, in a first operation 505, a second wireless communication device may determine that mobility state information associated with an IAB node (e.g., IAB node 410) is to be transmitted (e.g., transmitted by the second wireless communication device for reception by the first wireless communication device). For example, the second wireless communication device may receive a request or an instruction to provide mobility state information associated with the IAB node to the first wireless communication device. In some aspects, the determination may be that mobility state information associated with the second wireless communication device is to be transmitted (i.e., the determination may be that the second wireless communication device is to transmit mobility state information associated with itself). In this scenario, the second wireless communication device is the IAB node referred to in the first operation 505. In some aspects, the determination may be that mobility state information associated with a third wireless communication device is to be transmitted (i.e., the determination may be that the second wireless communication device is to transmit mobility state information associated with the third wireless communication device, for example, after receiving mobility state information from the third wireless communication device). In this scenario, the third wireless communication device is the IAB node mentioned in the first operation 505. Thus, in some aspects, the IAB node to which the mobility state information is associated may be the IAB node itself, a parent node of the IAB node, a child node of the IAB node, or another IAB node detected by the IAB node.

[0061] In some aspects, mobility information associated with an IAB node may include information indicating a mobility state of the IAB node. For example, the mobility state information may include information associated with a level or state of the mobility of the IAB node, such as information indicating whether the IAB node is stationary, has low-speed mobility (e.g., moving at a speed that is less than or equal to a first threshold), has medium-speed mobility (e.g., moving at a speed that is greater than a first threshold but less than or equal to a second threshold), or has high-speed mobility (e.g., moving at a speed greater than a second threshold). As another example, the mobility state information may include information associated with a change (i.e., transition) in the mobility of the IAB node, such as information indicating a transition from one mobility state to another, such as from a stationary state to a low-speed state. In some aspects, the mobility state information may include information indicating a time when a transition has occurred or will occur. As another example, the mobility state information may include a measurement report associated with the IAB node, such as a radio resource measurement (RRM) measurement report. As yet another example, mobility state information may include information indicating whether an IAB node is capable of moving or being moved (e.g., an indication of whether the IAB node is a non-mobile IAB node). As explained above, the mobility state of a given IAB node may affect the operation of a mobile IAB network, and therefore, knowledge of the mobility state may be required to facilitate efficient and acceptable execution of the mobile IAB network.

[0062] In some aspects, the determination that the mobility state information will be transmitted may be based at least in part on an explicit request for mobility state information associated with an IAB node. For example, a first wireless communication device may request mobility state information associated with an IAB node by sending a request to a second wireless communication device. Here, the second wireless communication device may receive the request and transmit the mobility state information based at least in part on the request (e.g., after determining the mobility state information or receiving the mobility state information from the IAB node).

[0063] In some aspects, the determination that the mobility state information will be transmitted may be based at least in part on a reporting configuration for transmitting mobility state information associated with the IAB node. For example, a first wireless communication device may provide a reporting configuration for transmitting mobility state information associated with the IAB node to a second wireless communication device. In some aspects, the reporting configuration may indicate periodic reporting of the mobility state information (e.g., to cause the second wireless communication device to automatically transmit the mobility state information periodically). In some aspects, the reporting configuration may indicate aperiodic reporting of the mobility state information (e.g., to cause the second wireless communication device to dynamically transmit the mobility state information aperiodically, e.g., when requested by the first wireless communication device). In some aspects, the reporting configuration may indicate event-triggered reporting of the mobility state information (e.g., to cause the second wireless communication device to transmit the mobility state information based at least in part on detecting an event indicated by the reporting configuration). Here, the second wireless communication device may receive the reporting configuration and provide mobility state information based at least in part on the reporting configuration (e.g., periodically, aperiodically, or at least in part on detection of an event).

[0064] 5, in a second operation 510, the second wireless communication device may transmit mobility state information associated with the IAB node, and the first wireless communication device may receive the mobility state information associated with the IAB node. In some aspects, the second wireless communication device may transmit, and the first wireless communication device may receive, the mobility state information in an RRC message, a downlink control information (DCI), a Layer 1 reference signal, a medium access control (MAC) control element, a master information block (MIB), a random access channel (RACH) message, a system information block (SIB), a handover request message, a secondary node (SN) addition request message, or another type of communication. In some aspects, when transmitting the mobility state information, the second wireless communication device may broadcast the mobility state information for reception by the first wireless communication device or one or more other wireless communication devices (e.g., one or more other IAB nodes 410). In some aspects, the reporting configuration may indicate a configuration for broadcasting the mobility state information.

[0065] In some aspects, the second wireless communication device may transmit at least a portion of the mobility state information in a communication that explicitly indicates the mobility state information. Thus, in some aspects, the first wireless communication device may receive the mobility state information in a communication that includes or otherwise explicitly indicates the mobility state information. Additionally or alternatively, in some aspects, the second wireless communication device may transmit at least a portion of the mobility state information in a communication that implicitly indicates the mobility state information. For example, at least a portion of the mobility state information may be implicitly indicated based at least in part on a set of resources over which a signal is transmitted. Thus, in some aspects, the first wireless communication device may receive the mobility state information in a communication that implicitly indicates the mobility state information based on which resources are selected for transmission of the signal.

[0066] 5, in a third operation 515, the first wireless communication device may perform an operation based at least in part on mobility state information associated with the IAB node. For example, the first wireless communication device may perform an operation associated with IAB topology and resource management, local scheduling, beam management, beam tracking, synchronization tracking, positioning, QoS type support, access procedures, paging, or another type of IAB network-related operation. As another example, the first wireless communication device may provide mobility state information associated with the IAB node (i.e., the operation may include providing the mobility state information associated with the IAB node). In some aspects, the first wireless communication device may transmit an indication of the mobility state information to an IAB donor (e.g., the IAB donor 405) for provision to a CU of the IAB donor, or to another IAB node (i.e., an IAB node 410 other than the one with which the mobility state information is associated) for provision to a DU or MT of the other IAB node. In one example, the first wireless communication device may be a parent node (e.g., the first IAB node 410), and the second wireless communication device may be a child node (e.g., the second IAB node 410). Here, the parent node may be provided with mobility state information associated with the child IAB node. The mobility state information may be used for various purposes such as resource management, local scheduling, beam management, beam tracking, synchronization tracking, positioning, QoS type support, paging, among other examples. For such purposes, the mobility state information should be provided to the DU of the parent node. In some examples, the DU of the child node may broadcast the mobility state information for reception by the DU of the parent node. In some other examples, the MT of the child node may provide the mobility state information directly to the DU of the parent node (e.g., over the Uu interface). In some other examples, the CU of the IAB donor (e.g., the IAB donor 405) may provide the mobility state information to the DU of the parent node.As a specific example, an MT of a child node may provide mobility state information to a CU of an IAB donor (e.g., via an RRC message), and the CU of the IAB donor may provide the mobility state information to a DU of a parent node (e.g., via an F1-AP message). As another specific example, a DU of a child node may provide mobility state information to a CU of an IAB donor (e.g., via an F1-AP message), and the CU of the IAB donor may provide the mobility state information to a DU of a parent node (e.g., via an F1-AP message).

[0067] In another example, the first wireless communication device may be a child node, and the second wireless communication device may be a parent node of the child node. Here, the child node may be provided with mobility state information associated with the parent node. The mobility state information may be used for various purposes such as beam management, beam tracking, synchronization tracking, positioning, QoS type support, access procedures, among other examples. For such purposes, the mobility state information should be provided to the DU or MT of the child node. In some examples, the DU of the parent node may broadcast the mobility state information for reception by the DU or MT of the child node. In some other examples, the DU of the parent node may provide the mobility state information directly to the MT of the child node (e.g., over the Uu interface). In some other examples, the CU of the IAB donor may provide the mobility state information to the child node. As a specific example, an MT of a parent node may provide mobility state information to a CU of an IAB donor (e.g., via an RRC message), and the CU of the IAB donor may provide mobility state information to a DU of the parent node (e.g., via an F1-AP message) or provide mobility state information to an MT of a child node (e.g., via an RRC message). As another specific example, a DU of a parent node may provide mobility state information to a CU of an IAB donor (e.g., via an F1-AP message), and the CU of the IAB donor may provide mobility state information to a DU of the parent node (e.g., via an F1-AP message) or provide mobility state information to an MT of a child node (e.g., via an RRC message).

[0068] In another example, the first wireless communication device may be an IAB donor, and the second wireless communication device may be an IAB node. Here, the CU of the IAB donor may be provided with the mobility state of the IAB node. The mobility state information may be used for various purposes, such as IAB topology and resource management, beam management, synchronization, positioning, QoS type support, access procedures, paging, or another type of IAB network-related operation. Additionally or alternatively, the CU may provide or relay the mobility state information to a third wireless communication device (e.g., another IAB node or network entity, such as another IAB node 410). In some examples, an MT of the IAB node may provide the mobility state information to the CU of the IAB donor (e.g., via an RRC message). In some other examples, a DU of the IAB node may provide the mobility state information to the CU of the IAB donor (e.g., via an F1-AP message).

[0069] As described above, in some examples, the first wireless communication device may be an IAB donor (e.g., IAB donor 405), and the mobility state information may be received by a CU of the IAB donor. Here, the second wireless communication device may be an IAB node (i.e., an IAB node with which the mobility state information is associated), and a DU or MT of the second wireless communication device may transmit the mobility state information to the CU of the IAB donor. Alternatively, the second wireless communication device may be another IAB node (i.e., an IAB node 410 other than the IAB node with which the mobility state information is associated), and a DU or MT of the second wireless communication device may transmit the mobility state information to the CU of the IAB donor. In some aspects, when the mobility state information is transmitted and received by the DU and CU, respectively, the mobility state information may be communicated via the F1-AP interface. In some aspects, when the mobility state information is transmitted and received by the MT and CU, respectively, the mobility state information may be communicated via the Uu interface (e.g., in an RRC message, such as in a SIB).

[0070] As another alternative, when the first wireless communication device is an IAB donor, the second wireless communication device may be another IAB donor (e.g., another IAB donor 405). Here, the CU of the second wireless communication device may transmit mobility state information to the CU of the first wireless communication device. In some aspects, when the mobility state information is transmitted and received by the CU and CU, respectively, the mobility state information may be communicated over an X2 / Xn interface. In some aspects, CU-CU communication of mobility state information may be used for inter-donor parent-node migration or dual connectivity (DC) via multiple IAB donors. In some such examples, the mobility state information may be included in a handover request message sent by the serving IAB donor to the target IAB donor. In some other examples, the mobility state information may be included in an SN addition request message, for example, associated with NR DC, multi-RAT (MR) DC, or evolved universal terrestrial radio access NR (EN) DC. In particular, in some cases, the IAB donor may reject an RRC setup message, or an X2 / Xn handover request, or an SN addition request, for example, with a cause of "unsupported mobility state."

[0071] In some aspects, the first wireless communication device may not be the IAB donor, but may be another IAB node (e.g., the first IAB node 410), and the mobility state information may be received by the DU of the first wireless communication device. Here, the second wireless communication device may be the IAB node with which the mobility state information is associated, and an MT of the second wireless communication device may transmit the mobility state information to the DU of the first wireless communication device. Alternatively, the second wireless communication device may be a different IAB node from the IAB node with which the mobility state information is associated, and an MT of the second wireless communication device may transmit the mobility state information to the DU of the first wireless communication device. In some aspects, when the mobility state information is transmitted and received by the MT and the DU, respectively, the mobility state information may be communicated over the Uu interface (e.g., in a DCI, Layer 1 reference signal, MAC control element, MIB, SIB1, uplink control information (UCI)).

[0072] 6 illustrates an example process 600 performed, for example, by a wireless communication device, in accordance with various aspects of the present disclosure. The process illustrated in FIG. 6 is an example of a wireless communication device (e.g., a base station 110, an anchor base station 335, a non-anchor base station 345, an IAB donor 405, an IAB node 410) performing operations associated with signaling to support mobile IAB.

[0073] 6, in some aspects, an example process may include receiving mobility state information associated with an IAB node, where the mobility state information includes information associated with at least one of a level of mobility of the IAB node or a change in mobility of the IAB node (block 610). For example, a wireless communication device (e.g., using the transmit processor 220, the receive processor 238, the controller / processor 240, the memory 242) may receive mobility state information associated with an IAB node (e.g., a non-anchor base station 345 or an IAB node 410), where the mobility state information includes information associated with at least one of a level of mobility of the IAB node or a change in mobility of the IAB node, as described above.

[0074] 6, in some aspects, an example process may include performing an operation based at least in part on mobility state information associated with the IAB node (block 620). For example, the wireless communication device (e.g., using the transmit processor 220, the receive processor 238, the controller / processor 240, the memory 242) may perform an operation based at least in part on mobility state information associated with the IAB node, as described above.

[0075] The process shown in FIG. 6 may include additional aspects, such as any single aspect or any combination of aspects described below or with respect to one or more other processes described elsewhere herein.

[0076] In a first additional aspect, process 600 may further include requesting mobility state information associated with the IAB node, wherein the mobility state information is received based at least in part on requesting the mobility state information.

[0077] In a second additional aspect, alone or in combination with the first aspect, process 600 may further include providing a reporting configuration for transmitting mobility state information associated with the IAB node, the mobility state information being received based at least in part on the reporting configuration.

[0078] In a third additional aspect, alone or in combination with one or more of the first and second aspects, the reporting configuration indicates at least one of periodic reporting of the mobility state information, aperiodic reporting of the mobility state information, or event-triggered reporting of the mobility state information.

[0079] In a fourth additional aspect, alone or in combination with one or more of the first through third aspects, the operations include providing mobility state information associated with the IAB node to at least one of a CU of the IAB donor (e.g., IAB donor 405), a DU of another IAB node (e.g., another IAB node 410), or an MT of another IAB node.

[0080] In a fifth additional aspect, alone or in combination with one or more of the first through fourth aspects, the wireless communication device is a CU of an IAB donor (e.g., IAB donor 405).

[0081] In a sixth additional aspect, alone or in combination with one or more of the first to fifth aspects, mobility state information is received from a DU of an IAB node.

[0082] In a seventh additional aspect, alone or in combination with one or more of the first through sixth aspects, the IAB node is a first IAB node, and the mobility state information is received from a DU of a second IAB node (e.g., second IAB node 410).

[0083] In an eighth additional aspect, alone or in combination with one or more of the first through seventh aspects, mobility state information is received from an MT of an IAB node.

[0084] In a ninth additional aspect, alone or in combination with one or more of the first to eighth aspects, the IAB node is a first IAB node, and the mobility state information is received from an MT of a second IAB node.

[0085] In a tenth additional aspect, alone or in combination with one or more of the first through ninth aspects, mobility state information is received from a CU of another IAB donor.

[0086] In an eleventh additional aspect, alone or in combination with one or more of the first through tenth aspects, the IAB node is a first IAB node and the wireless communication device is a DU of a second IAB node.

[0087] In a twelfth additional aspect, alone or in combination with one or more of the first through eleventh aspects, mobility state information is received from an MT of the first IAB node.

[0088] In a thirteenth additional aspect, alone or in combination with one or more of the first through twelfth aspects, mobility state information is received from an MT of a third IAB node.

[0089] In a fourteenth additional aspect, alone or in combination with one or more of the first to thirteenth aspects, receiving mobility state information includes receiving the mobility state information in at least one of an RRC message, a DCI, a Layer 1 reference signal, a MAC control element, a MIB, a RACH message, a SIB, a handover request message, or an SN addition request message.

[0090] In a fifteenth additional aspect, alone or in combination with one or more of the first to fourteenth aspects, receiving the mobility state information includes receiving the mobility state information in a communication that explicitly indicates the mobility state information.

[0091] In a sixteenth additional aspect, alone or in combination with one or more of the first to fifteenth aspects, receiving the mobility state information includes receiving the mobility state information in a communication that implicitly indicates the mobility state information.

[0092] In a seventeenth additional aspect, alone or in combination with one or more of the first through sixteenth aspects, the operations are associated with at least one of IAB topology and resource management, local scheduling, beam management, beam tracking, synchronization tracking, positioning, QoS type support, access procedures, or paging.

[0093] 7 illustrates an example process 700 performed, for example, by a base station, in accordance with various aspects of the present disclosure. The process illustrated in FIG. 7 is an example of a wireless communication device (e.g., base station 110, anchor base station 335, non-anchor base station 345, IAB donor 405, IAB node 410) performing operations associated with signaling to support mobile IAB.

[0094] 7, in some aspects, an example process may include determining (block 710) that mobility state information associated with an IAB node is to be transmitted, where the mobility state information includes information associated with at least one of a level of mobility of the IAB node or a change in mobility of the IAB node. For example, a wireless communication device (e.g., using the transmit processor 220, the receive processor 238, the controller / processor 240, the memory 242) may determine that mobility state information associated with an IAB node (e.g., IAB node 410) is to be transmitted, where the mobility state information includes information associated with at least one of a level of mobility of the IAB node or a change in mobility of the IAB node, as described above.

[0095] 7, in some aspects, an example process may include transmitting mobility state information associated with an IAB node based at least in part on a determination that the mobility state information is to be transmitted (block 720). For example, the wireless communication device (e.g., using the transmit processor 220, the receive processor 238, the controller / processor 240, the memory 242) may transmit mobility state information associated with an IAB node based at least in part on a determination that the mobility state information is to be transmitted, as described above.

[0096] The example process shown in FIG. 7 may include additional aspects, such as any single aspect or any combination of aspects described below or with respect to one or more other processes described elsewhere herein.

[0097] In a first additional aspect, the determination that the mobility state information will be transmitted is based at least in part on an explicit request for mobility state information associated with the IAB node.

[0098] In a second additional aspect, alone or in combination with the first aspect, process 700 may further include receiving a reporting configuration for transmitting mobility state information, wherein the mobility state information is transmitted based at least in part on the reporting configuration.

[0099] In a third additional aspect, alone or in combination with one or more of the first and second aspects, the reporting configuration indicates at least one of periodic reporting of the mobility state information, aperiodic reporting of the mobility state information, or event-triggered reporting of the mobility state information.

[0100] In a fourth additional aspect, alone or in combination with one or more of the first through third aspects, transmitting the mobility state information includes transmitting the mobility state information to a CU of an IAB donor (e.g., IAB donor 405).

[0101] In a fifth additional aspect, alone or in combination with one or more of the first through fourth aspects, the wireless communication device is a DU of an IAB node.

[0102] In a sixth additional aspect, alone or in combination with one or more of the first through fifth aspects, the IAB node is a first IAB node and the wireless communication device is a DU of a second IAB node (e.g., second IAB node 410).

[0103] In a seventh additional aspect, alone or in combination with one or more of the first through sixth aspects, the wireless communication device is a MT of an IAB node.

[0104] In an eighth additional aspect, alone or in combination with one or more of the first through seventh aspects, the IAB node is a first IAB node and the wireless communication device is an MT of a second IAB node.

[0105] In a ninth additional aspect, alone or in combination with one or more of the first through eighth aspects, transmitting the mobility state information includes transmitting the mobility state information to a CU of another IAB donor.

[0106] In a tenth additional aspect, alone or in combination with one or more of the first to ninth aspects, the IAB node is a first IAB node, and transmitting the mobility state information includes transmitting the mobility state information to a DU of a second IAB node.

[0107] In an eleventh additional aspect, alone or in combination with one or more of the first through tenth aspects, the wireless communication device is a MT of the first IAB node.

[0108] In a twelfth additional aspect, alone or in combination with one or more of the first through eleventh aspects, the wireless communication device is a MT of a third IAB node.

[0109] In a thirteenth additional aspect, alone or in combination with one or more of the first to twelfth aspects, transmitting the mobility state information includes transmitting the mobility state information in at least one of an RRC message, a DCI, a Layer 1 reference signal, a MAC control element, a MIB, a RACH message, a SIB, a handover request message, or an SN addition request message.

[0110] In a fourteenth additional aspect, alone or in combination with one or more of the first to thirteenth aspects, transmitting the mobility state information includes transmitting the mobility state information in a communication that explicitly indicates the mobility state information.

[0111] In a fifteenth additional aspect, alone or in combination with one or more of the first to fourteenth aspects, transmitting the mobility state information includes transmitting the mobility state information in a communication that implicitly indicates the mobility state information.

[0112] 7 illustrates example blocks of process 700, in some aspects process 700 may include additional, fewer, different, or differently arranged blocks compared to the blocks illustrated in FIG 7. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.

[0113] 8 is a block diagram of an example apparatus 800 for wireless communication in accordance with various aspects of the present disclosure. The apparatus 800 may be a wireless communication device, or a wireless communication device may include the apparatus 800. In some aspects, the apparatus 800 includes a receiving component 802, a communications manager 804, and a transmitting component 806, which may be in communication with one another (e.g., via one or more buses). As shown, the apparatus 800 may communicate with another apparatus 808 (such as a UE, a base station, or another wireless communication device) using the receiving component 802 and the transmitting component 806.

[0114] In some aspects, apparatus 800 may be configured to perform one or more operations described herein with respect to FIG. 5. Additionally or alternatively, apparatus 800 may be configured to perform one or more processes described herein, such as process 600 of FIG. 6. In some aspects, apparatus 800 may include one or more components of the wireless communication device described above with respect to FIG.

[0115] The receiving component 802 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 808. The receiving component 802 may provide the received communications to one or more other components of the device 800, such as the communications manager 804. In some aspects, the receiving component 802 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communications and provide the processed signals to one or more other components. In some aspects, the receiving component 802 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof of a wireless communication device described above with respect to FIG.

[0116] The transmitting component 806 may transmit communications such as reference signals, control information, data communications, or combinations thereof to the device 808. In some aspects, the communications manager 804 may generate communications and transmit the generated communications to the transmitting component 806 for transmission to the device 808. In some aspects, the transmitting component 806 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communications and transmit the processed signals to the device 808. In some aspects, the transmitting component 806 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof of the wireless communication device described above with respect to FIG. 2. In some aspects, the transmitting component 806 may be collocated with the receiving component 802 in a transceiver.

[0117] In some aspects, the communications manager 804 may receive, or cause the receiving component 802 to receive, mobility state information associated with the IAB node. Here, the mobility state information may include information associated with at least one of a level of mobility of the IAB node or a change in the mobility of the IAB node. In some aspects, the communications manager 804 may perform an operation based at least in part on the mobility state information associated with the IAB node. In some aspects, the communications manager 804 may include a controller / processor, a memory, a scheduler, a communication unit, or a combination thereof, of a wireless communication device described above with respect to FIG. 2.

[0118] In some aspects, the communications manager 804 may request, or cause the receiving component 802 to request, mobility state information associated with the IAB node, where the mobility state information may be received based at least in part on the request.

[0119] In some aspects, the communications manager 804 may provide, or cause the transmitting component 806 to provide, a reporting configuration for transmitting mobility state information associated with an IAB node, where the mobility state information may be received based at least in part on the reporting configuration.

[0120] In some aspects, communications manager 804 may include a set of components, such as operational component 810. Alternatively, the set of components may be separate and distinct from communications manager 804. In some aspects, one or more components of the set of components may include or be implemented within a controller / processor, memory, scheduler, communication unit, or combination thereof, of a wireless communication device described above with respect to FIG. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0121] The receiving component 802 may receive mobility state information associated with an IAB node, where the mobility state information includes information associated with a level of mobility of the IAB node or a change in the mobility of the IAB node.

[0122] The action component 810 may perform an action based at least in part on the mobility state information associated with the IAB node.

[0123] The number and arrangement of components shown in Figure 8 are provided as an example. In practice, there may be additional, fewer, different, or differently arranged components compared to those shown in Figure 8. Furthermore, two or more components shown in Figure 8 may be implemented within a single component, or a single component shown in Figure 8 may be implemented as multiple distributed components. Additionally or alternatively, a set of components shown in Figure 8 may perform one or more functions described as being performed by another set of components shown in Figure 8.

[0124] 9 is a block diagram of an example apparatus 900 for wireless communication in accordance with various aspects of the present disclosure. The apparatus 900 may be a wireless communication device, or a wireless communication device may include the apparatus 900. In some aspects, the apparatus 900 includes a receiving component 902, a communications manager 904, and a transmitting component 906, which may be in communication with one another (e.g., via one or more buses). As shown, the apparatus 900 may communicate with another apparatus 908 (such as a UE, a base station, or another wireless communication device) using the receiving component 902 and the transmitting component 906.

[0125] In some aspects, apparatus 900 may be configured to perform one or more operations described herein with respect to FIG. 5. Additionally or alternatively, apparatus 900 may be configured to perform one or more processes described herein, such as process 700 of FIG. 7. In some aspects, apparatus 900 may include one or more components of the wireless communication device described above with respect to FIG.

[0126] The receiving component 902 may receive communications such as reference signals, control information, data communications, or combinations thereof from the device 908. The receiving component 902 may provide the received communications to one or more other components of the device 900, such as the communications manager 904. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communications and provide the processed signals to one or more other components. In some aspects, the receiving component 902 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof of the wireless communication device described above with respect to FIG.

[0127] The transmitting component 906 may transmit communications such as reference signals, control information, data communications, or combinations thereof to the device 908. In some aspects, the communications manager 904 may generate communications and transmit the generated communications to the transmitting component 906 for transmission to the device 908. In some aspects, the transmitting component 906 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communications and transmit the processed signals to the device 908. In some aspects, the transmitting component 906 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof of the wireless communication device described above with respect to FIG. 2. In some aspects, the transmitting component 906 may be collocated with the receiving component 902 in a transceiver.

[0128] In some aspects, the communications manager 904 may determine that mobility state information associated with the IAB node is to be transmitted, where the mobility state information may include information associated with at least one of a level of mobility of the IAB node or a change in the mobility of the IAB node. The communications manager 904 may transmit, or cause the transmitting component 906 to transmit, the mobility state information associated with the IAB node based at least in part on the determination that the mobility state information is to be transmitted. In some aspects, the communications manager 904 may include a controller / processor, a memory, a scheduler, a communication unit, or a combination thereof, of a wireless communication device described above with respect to FIG. 2.

[0129] In some aspects, the determination that the mobility state information will be transmitted is based at least in part on an explicit request for mobility state information associated with the IAB node.

[0130] In some aspects, the communications manager 904 may receive, or cause the receiving component 902 to receive, a reporting configuration for transmitting mobility state information associated with an IAB node, where the communications manager 904 may transmit, or cause the transmitting component 906 to transmit, the mobility state information based at least in part on the reporting configuration.

[0131] In some aspects, the communications manager 904 may include a set of components, such as the mobility state determination component 910. Alternatively, the set of components may be separate and distinct from the communications manager 904. In some aspects, one or more components of the set of components may include or be implemented within a controller / processor, memory, scheduler, communication unit, or combination thereof, of a wireless communication device described above with respect to FIG. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0132] The mobility state determination component 910 may determine that mobility state information associated with the IAB node is to be transmitted, where the mobility state information includes information associated with at least one of a level of mobility of the IAB node or a change in the mobility of the IAB node. In some aspects, the mobility state determination component 910 may determine characteristics of the movement of the IAB node and may determine a mobility state and / or mobility state information associated with the IAB node based on the characteristics. The transmitting component 906 may transmit the mobility state information associated with the IAB node based at least in part on the determination that the mobility state information is to be transmitted.

[0133] The number and arrangement of components shown in Figure 9 are provided as an example. In practice, there may be additional, fewer, different, or differently arranged components compared to those shown in Figure 9. Furthermore, two or more components shown in Figure 9 may be implemented within a single component, or a single component shown in Figure 9 may be implemented as multiple distributed components. Additionally or alternatively, a set of components shown in Figure 9 may perform one or more functions described as being performed by another set of components shown in Figure 9.

[0134] The above disclosure provides illustration and description, and is not intended to be exhaustive or to limit the embodiments to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the embodiments.

[0135] As used herein, the term "component" shall be broadly interpreted as hardware, firmware, or a combination of hardware and software. As used herein, a processor may be implemented in hardware, firmware, or a combination of hardware and software.

[0136] Some aspects are described herein in terms of thresholds. As used herein, "meeting a threshold" can refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or combinations thereof, depending on the context.

[0137] It will be apparent that the systems or methods described herein may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems or methods is not a limiting aspect. Thus, the operation and behavior of the systems or methods are described herein without reference to specific software code. It should be understood that software and hardware may be designed to implement the systems or methods based at least in part on the descriptions herein.

[0138] Although particular combinations of features are recited in the claims or disclosed herein, these combinations do not limit the disclosure of various aspects. Indeed, many of these features may be combined in ways not specifically recited in the claims or disclosed herein. While each dependent claim listed below may depend directly on only one claim, the disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. A phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to encompass a, b, c, ab, ac, bc, and abc, as well as any combination having multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other order of a, b, and c).

[0139] No element, act, or instruction used herein should be construed as critical or essential unless expressly described as such. Also, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more." Furthermore, as used herein, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, or a combination thereof) and may be used interchangeably with "one or more." Where only one item is intended, the phrase "only one" or similar language is used. Also, as used herein, the terms "has," "have," "having," or combinations thereof are intended to be open-ended terms. Furthermore, the phrase "based on" is intended to mean "based at least in part on," unless expressly specified otherwise. [Explanation of symbols]

[0140] 102a Macrocell 102b Picocell 102c Femtocell 110 base station (BS), base station, first base station, second base station 110a BS, Macro BS 110b, 110c BS 110d BS, relay station 120, 120a, 120b, 120c, 120d, 120e, 320, 355UE 130 Network Controller 212, 262 data sources 220, 264 Transmit Processor 230 Transmit (TX) Multiple Input Multiple Output (MIMO) Processor 232 MOD, DEMOD 232a~232t Modulator (MOD), MOD 234, 234a-234t, 252a-252r antennas 236, 256 MIMO detector 238, 258 Receive Processor 239, 260 Data sink 240, 280, 290 Controller / Processor 242, 282, 292 memory 244, 294 communication unit 246 Scheduler 254 DEMOD 254a~254r Demodulator (DEMOD), DEMOD, MOD 266 TX MIMO Processor 310 base station 315, 340, 370 Wired Backhaul Links 325, 360, 375 Wireless Access Links 335 anchor base station, first anchor base station, second anchor base station 345 non-anchor base station, first non-anchor base station, second non-anchor base station 350 Wireless Backhaul Links 405 IAB donors, 1st IAB donors, 2nd IAB donors 410 IAB node, non-donor IAB node, intermediate IAB node, first IAB node, second IAB node 415 Access Link 420 Backhaul Link 800 equipment 802, 902 receiving components 804, 904 Communications Manager 806, 906 Transmission Components 808, 908 Another device, device 810 Operational Components 910 Mobility State Determination Component

Claims

1. a first integrated access backhaul (IAB) donor node for wireless communications, the first integrated access backhaul donor node comprising: one or more memories; one or more processors coupled to the one or more memories, wherein the one or more processors: determining that mobility state information associated with the first IAB donor node or the second IAB node will be transmitted based at least on at least one of a request for the mobility state information, an indication of the mobility state information, or a reporting configuration for transmitting the mobility state information, wherein the mobility state information includes information indicating whether the first IAB donor node or the second IAB node is capable of moving or being moved; transmitting the mobility state information based at least on a determination that the mobility state information will be transmitted; and a first IAB donor node configured to:

2. The first IAB donor node of claim 1 , wherein the second IAB node is a child node of the first IAB donor node.

3. To determine that the mobility state information will be transmitted, the one or more processors: detecting the second IAB node based at least on the at least one of the request, the indication, or the reporting configuration; determining that the mobility state information associated with the second IAB node will be transmitted based at least on detecting the second IAB node; 10. The first IAB donor node of claim 1, configured to:

4. 2. The first IAB donor node of claim 1, wherein to transmit the mobility state information, the one or more processors are configured to transmit the mobility state information to a third IAB node different from the second IAB node.

5. 2. The first IAB donor node of claim 1, wherein to transmit the mobility state information, the one or more processors are configured to transmit the mobility state information via a handover request message.

6. 5. The first IAB donor node of claim 4, wherein to transmit the mobility state information to the third IAB node, the one or more processors are configured to transmit the mobility state information to a distributed unit of the third IAB node.

7. 5. The first IAB donor node of claim 4, wherein the third IAB node is a second IAB donor node, and wherein transmitting the mobility state information to the third IAB node includes transmitting the mobility state information to a central unit of the second IAB donor node.

8. 2. The first IAB donor node of claim 1, wherein to transmit the mobility state information, the one or more processors are configured to transmit the mobility state information over an X2 / Xn interface.

9. The first IAB donor node of claim 1 , wherein the one or more processors are further configured to receive the reporting configuration.

10. To determine that the mobility state information will be transmitted, the one or more processors: Detecting an event for transmitting the mobility state information indicated in the reporting configuration; and determining that the mobility state information will be transmitted based at least on detecting the event; and 10. The first IAB donor node of claim 1, configured to:

11. 2. The first IAB donor node of claim 1, wherein, to transmit the mobility state information, the one or more processors are configured to transmit the mobility state information in a communication that explicitly indicates the mobility state information.

12. 2. The first IAB donor node of claim 1, wherein, to transmit the mobility state information, the one or more processors are configured to transmit the mobility state information in the communication that implicitly indicates the mobility state information over a set of resources on which the communication is transmitted.

13. 1. A method of wireless communication performed by a first integrated access backhaul (IAB) donor node, comprising: determining that mobility state information associated with the first IAB donor node or the second IAB node will be transmitted based at least on at least one of a request for the mobility state information, an indication of the mobility state information, or a reporting configuration for transmitting the mobility state information, wherein the mobility state information includes information indicating whether the first IAB donor node or the second IAB node is capable of moving or being moved; transmitting the mobility state information based at least on a determination that the mobility state information will be transmitted; and A method comprising:

14. The method of claim 13 , wherein the second IAB node is a child node of the first IAB donor node.

15. determining that the mobility state information will be transmitted, detecting the second IAB node based at least on the at least one of the request, the indication, or the reporting configuration; determining that the mobility state information associated with the second IAB node will be transmitted based at least on detecting the second IAB node; 14. The method of claim 13, comprising:

16. 14. The method of claim 13, wherein transmitting the mobility state information comprises transmitting the mobility state information to a third IAB node different from the second IAB node.

17. The method of claim 13 , wherein transmitting the mobility state information comprises transmitting the mobility state information via a handover request message.

18. 17. The method of claim 16, wherein transmitting the mobility state information to the third IAB node comprises transmitting the mobility state information to a distributed unit of the third IAB node.

19. 17. The method of claim 16, wherein the third IAB node is a second IAB donor node, and wherein transmitting the mobility state information to the third IAB node comprises transmitting the mobility state information to a central unit of the second IAB donor node.

20. The method of claim 13 , wherein transmitting the mobility state information comprises transmitting the mobility state information over an X2 / Xn interface.

21. The method of claim 13 , further comprising receiving the reporting configuration.

22. determining that the mobility state information will be transmitted, detecting an event for transmitting the mobility state information indicated in the reporting configuration; determining that the mobility state information will be transmitted based at least on detecting the event; 14. The method of claim 13, comprising:

23. The method of claim 13 , wherein transmitting the mobility state information comprises transmitting the mobility state information in a communication that explicitly indicates the mobility state information.

24. 14. The method of claim 13, wherein transmitting the mobility state information comprises transmitting the mobility state information in the communication that implicitly indicates the mobility state information over a set of resources over which the communication is transmitted.

Images