Inter-donor topology discovery in integrated access and backhaul (IAB)

Abstract

Various aspects of this disclosure provide techniques for donor-to-donor topology discovery in an IAB network during the migration of Integrated Access and Backhaul (IAB) nodes. A method that can be performed by a first IAB donor includes: establishing a first signaling connection with an IAB node; receiving an indication that the IAB node has a second signaling connection with a second IAB donor; and in response to receiving the indication: transmitting information related to the IAB node to the second IAB donor; re-establishing service between the first IAB donor and the IAB node via the topology of the second IAB donor; or any combination thereof.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Application No. 17 / 321,234, filed May 14, 2021, which has been assigned to the assignee of this application and whose entire contents are incorporated herein by reference. Technical Field

[0003] Various aspects of this disclosure relate to wireless communications, and more specifically, to techniques for donor-to-donor topology discovery in IAB networks during the migration of Integrated Access and Backhaul (IAB) nodes. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, broadcasting, and so on. These wireless communication systems can employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access systems include 3GPP Long Term Evolution (LTE) systems, LTE-A Advanced systems, 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, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, to name just a few.

[0005] In some examples, a wireless multiple access communication system may include a number of base stations (BSs), each capable of simultaneously supporting communication for multiple communication devices (otherwise referred to as user equipment (UE)). In LTE or LTE-A networks, a set of one or more base stations may define an eNodeB (eNB). In other examples (e.g., in next-generation, new radio (NR), or 5G networks), a wireless multiple access communication system may include multiple distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmit / receive points (TRPs), etc.) communicating with multiple central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), wherein a set of one or more DUs communicating with a CU may define an access node (e.g., which may be referred to as a BS, a next-generation node B (gNB or gNodeB), a TRP, etc.). The BS or DU can communicate with a set of UEs on both downlink (DL) channels (e.g., for transmissions from the BS or DU to the UE) and uplink (UL) channels (e.g., for transmissions from the UE to the BS or DU).

[0006] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, country, region, and even global levels. New radios (e.g., 5G NR) are examples of emerging telecommunications standards. NR is a collection of enhancements to the LTE mobile standard released by 3GPP. NR is designed to better support mobile broadband internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and better integrating with other open standards using OFDMA with cyclic prefixes (CP) on DL and UL. For these purposes, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0007] With the continued increase in demand for mobile broadband access, further improvements to NR and LTE technologies are needed. These improvements should also be applicable to other multiple access technologies and telecommunications standards that employ them. Summary of the Invention

[0008] The systems, methods, and apparatuses of this disclosure each have several aspects, and no single aspect is solely responsible for its desired properties. After considering these discussions, and especially after reading the section entitled "Detailed Description," one will understand how the features of this disclosure provide advantages, including improved wireless communication between wireless communication devices.

[0009] Some aspects provide a method for wireless communication via an Integrated Access and Backhaul (IAB) node. This method typically includes: establishing a first signaling connection with a first IAB donor; establishing a second signaling connection with a second IAB donor; and sending an indication to the second IAB donor that the IAB node has the first signaling connection with the first IAB donor.

[0010] Certain aspects of this disclosure relate to an apparatus for wireless communication for an IAB node. The apparatus typically includes: at least one processor; and a memory coupled to the at least one processor, the memory including instructions executable by the at least one processor to cause the apparatus to: establish a first signaling connection with a first IAB donor; establish a second signaling connection with a second IAB donor; and send an indication to the second IAB donor that the IAB node has a first signaling connection with the first IAB donor.

[0011] Certain aspects of this disclosure relate to an apparatus for wireless communication performed by an IAB node. The apparatus typically includes: units for establishing a first signaling connection with a first IAB donor; units for establishing a second signaling connection with a second IAB donor; and units for sending an indication to the second IAB donor that the IAB node has the first signaling connection with the first IAB donor.

[0012] Certain aspects of this disclosure relate to a computer-readable medium having instructions stored thereon for performing the following operations: establishing a first signaling connection with a first IAB donor; establishing a second signaling connection with a second IAB donor; and sending an indication to the second IAB donor that the IAB node has a first signaling connection with the first IAB donor.

[0013] Some aspects provide a method for wireless communication performed by a first IAB donor. The method typically includes: establishing a first signaling connection with an IAB node; receiving an indication that the IAB node has a second signaling connection with a second IAB donor; and in response to receiving the indication: transmitting information related to the IAB node to the second IAB donor; re-establishing service between the first IAB donor and the IAB node via the topology of the second IAB donor; or any combination thereof.

[0014] Certain aspects of this disclosure relate to an apparatus for wireless communication performed by a first IAB donor. The apparatus typically includes: at least one processor; and memory coupled to the at least one processor, the memory including instructions executable by the at least one processor to cause the apparatus to: establish a first signaling connection with an IAB node; receive an indication that the IAB node has a second signaling connection with a second IAB donor; and, in response to receiving the indication, transmit information related to the IAB node to the second IAB donor; re-establish service between the first IAB donor and the IAB node via the topology of the second IAB donor; or any combination thereof.

[0015] Certain aspects of this disclosure relate to an apparatus for wireless communication performed by a first IAB donor. The apparatus typically includes: a unit for establishing a first signaling connection with an IAB node; a unit for receiving an indication that the IAB node has a second signaling connection with a second IAB donor; and, in response to receiving the indication, a unit for transmitting information related to the IAB node to the second IAB donor; a unit for re-establishing service between the first IAB donor and the IAB node via the topology of the second IAB donor; or any combination thereof.

[0016] Certain aspects of this disclosure relate to a computer-readable medium having instructions stored thereon for performing: establishing a first signaling connection with an IAB node; receiving an instruction regarding the IAB node having a second signaling connection with a second IAB donor; and, in response to receiving the instruction: transmitting information related to the IAB node to the second IAB donor; re-establishing service between the first IAB donor and the IAB node via the topology of the second IAB donor; or any combination thereof.

[0017] Some aspects provide a method for wireless communication performed by a first IAB donor. The method typically includes: establishing a first signaling connection with an IAB node; receiving from the IAB node a first indication that the IAB node has a second signaling connection with a second IAB donor; and sending to the second IAB donor a second indication that the first IAB donor has the first signaling connection with the IAB node.

[0018] Certain aspects of this disclosure relate to an apparatus for wireless communication performed by a first IAB donor. The apparatus typically includes: at least one processor; and a memory coupled to the at least one processor, the memory including instructions executable by the at least one processor to cause the apparatus to: establish a first signaling connection with an IAB node; receive from the IAB node a first indication that the IAB node has a second signaling connection with a second IAB donor; and send to the second IAB donor a second indication that the first IAB donor has a first signaling connection with an IAB node.

[0019] Certain aspects of this disclosure relate to an apparatus for wireless communication performed by a first IAB donor. The apparatus typically includes: units for establishing a first signaling connection with an IAB node; units for receiving from the IAB node a first indication that the IAB node has a second signaling connection with a second IAB donor; and units for sending to the second IAB donor a second indication that the first IAB donor has a first signaling connection with the IAB node.

[0020] Certain aspects of this disclosure relate to a computer-readable medium having stored thereon instructions for performing the following operations: establishing a first signaling connection with an IAB node; receiving from the IAB node a first indication that the IAB node has a second signaling connection with a second IAB donor; and sending to the second IAB donor a second indication that the first IAB donor has a first signaling connection with the IAB node.

[0021] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings illustrate certain illustrative features of the one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of each aspect can be employed. Attached Figure Description

[0022] To gain a more detailed understanding of the features of this disclosure, a more specific description of the brief overview above can be obtained by referring to some of the aspects shown in the accompanying drawings. However, it should be noted that the drawings illustrate only some typical aspects of this disclosure, and the description may allow for other equally valid aspects.

[0023] Figure 1 This is a block diagram conceptually illustrating an example wireless communication system according to certain aspects of this disclosure.

[0024] Figure 2 The block diagrams are conceptually illustrated based on certain aspects of this disclosure, showing the design of an example base station (BS) and user equipment (UE).

[0025] Figure 3 This is a diagram illustrating an example of a radio access network (RAN) according to certain aspects of this disclosure.

[0026] Figure 4 This is a diagram illustrating an example of an integrated access and backhaul (IAB) network architecture based on certain aspects of this disclosure.

[0027] Figure 5A and 5B This is a diagram illustrating an example migration of a mobile terminal (MT) component via a handover (HO) process of an IAB node according to certain aspects of this disclosure.

[0028] Figure 6A and 6B This is a diagram illustrating an example migration of the MT component of an IAB node via a link re-establishment process, according to certain aspects of this disclosure.

[0029] Figure 7A and 7B This is a diagram illustrating an example migration of the MT component of an IAB node when the MT and Distributed Unit (DU) components of the IAB node are not co-located prior to the migration, according to certain aspects of this disclosure.

[0030] Figure 8 This is a flowchart illustrating example operations of wireless communication performed by nodes in an Integrated Access and Backhaul (IAB) network, according to certain aspects of this disclosure.

[0031] Figure 9 This is a flowchart illustrating example operations for wireless communication performed by a donor node in an IAB network, according to certain aspects of this disclosure.

[0032] Figure 10 This is another flowchart illustrating example operations of wireless communication performed by a donor node in an IAB network, according to certain aspects of this disclosure.

[0033] Figure 11A This is a call flowchart illustrating an example method for donor-to-donor topology discovery in an IAB network, based on certain aspects of this disclosure.

[0034] Figure 11B This is another call flowchart illustrating an example method for donor-to-donor topology discovery in IAB networks, based on certain aspects of this disclosure.

[0035] Figure 12 This describes a communication device that, according to certain aspects of this disclosure, may include various components configured to perform operations using the techniques disclosed herein.

[0036] Figure 13 This describes a communication device that, according to certain aspects of this disclosure, may include various components configured to perform operations using the techniques disclosed herein.

[0037] Figure 14 This describes a communication device that, according to certain aspects of this disclosure, may include various components configured to perform operations using the techniques disclosed herein.

[0038] To facilitate understanding, the same reference numerals have been used wherever possible to designate the same elements that are common to the accompanying drawings. It is conceivable that elements disclosed in one aspect may be advantageously used in other aspects without specific description. Detailed Implementation

[0039] Various aspects of this disclosure provide techniques for donor-to-donor topology discovery in an IAB network during the migration of Integrated Access and Backhaul (IAB) nodes. In some cases, the Mobile Terminal (MT) and Distributed Unit (DU) components (also referred to herein as MT or DU parts) of an IAB node may not be co-located. In other words, the context of the MT component of an IAB node may be maintained at a first IAB donor, while the context of the DU component of an IAB node may be maintained at a second IAB donor. In such cases, when the MT component of an IAB node migrates due to a handover (HO) or link re-establishment, the second IAB donor may be blind (e.g., undetected) to the context passing of the MT component from the first IAB donor to another IAB donor with whom the MT establishes a new signaling connection. The IAB donor knows that the passing may be important in order to continue communicating with the DU component of the IAB node (and its descendant nodes), and in some cases, to initiate context passing against these entities.

[0040] Various aspects of this disclosure provide techniques for discovering donor topology among IAB donors in an IAB network architecture to notify (unnotified) IAB donors of the delivery of information. In some cases, the IAB node itself can notify a second IAB donor. In other cases, another IAB donor with a new connection to the MT component of an IAB node can notify a second IAB donor.

[0041] The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in the examples. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described for some examples may be combined in other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Moreover, the scope of this disclosure is intended to cover such apparatus or methods that are practiced using structures, functions, or structures and functions other than or different from the aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims. The term “exemplary” as used herein means “as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.

[0042] Generally, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific Radio Access Technology (RAT) and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, subcarrier, frequency channel, tone, subband, etc. To avoid interference between wireless networks using different RATs, each frequency can support a single RAT within a given geographical area. In some cases, 5G NR RAT networks can be deployed.

[0043] Example wireless communication system

[0044] Figure 1 An example wireless communication network 100 in which aspects of this disclosure can be implemented is shown. Figure 1 As shown, the wireless communication network 100 may include components configured to perform... Figure 8 The integrated access and backhaul (IAB) node (implemented as user equipment (UE) 120a or base station (BS) 110a) of operation 800. Similarly, the wireless communication network 100 may include nodes configured to perform Figure 9 Operation 900 or Figure 10 Operation 1000 of the IAB donors (implemented as BS110a) to assist the IAB nodes in performing Figure 8Operation 800. For example, an IAB node implemented as UE 120a includes migration manager 122, and an IAB node or IAB donor implemented as BS 110a includes migration manager 112. According to various aspects of this disclosure, migration manager 122 and migration manager 112 can be configured to perform inter-donor topology discovery during the migration of an IAB node.

[0045] like Figure 1 As shown, the wireless communication network 100 may include several BS110a-z (each BS is also referred to individually as BS110 or collectively as BS110 herein) and other network entities. A BS may be a station communicating with a UE. Each BS110 may provide communication coverage for a specific geographic area. In 3GPP, depending on the context in which the terminology is used, the term "cell" may refer to the coverage area of ​​a Node B (NB) and / or the Node B subsystem serving that coverage area. In NR systems, the term "cell" and Next Generation Node B (gNB), New Radio (NR) BS, 5G NB, Access Point (AP), or Transmitter Receiver Point (TRP) may be interchangeable. In some examples, the cell need not be stationary, and the geographic area of ​​the cell may move depending on the location of the mobile BS. In some examples, BS110 may use any suitable transport network to interconnect with each other and / or connect to one or more other BSs or network nodes (not shown) in the wireless communication network 100 via various types of backhaul interfaces (e.g., direct physical connection, wireless connection, virtual network, etc.).

[0046] Generally, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific Radio Access Technology (RAT) and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, subcarrier, frequency channel, tone, subband, etc. To avoid interference between wireless networks using different RATs, each frequency can support a single RAT within a given geographical area. In some cases, NR or 5G RAT networks can be deployed.

[0047] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or other types of cells. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access for UEs with service subscriptions. A picocell can cover a relatively small geographic area and allow unrestricted access for UEs with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a home) and allow restricted access by UEs associated with the femtocell (e.g., UEs in a Closed Subscriber Group (CSG), UEs of users in a home, etc.). A BS used for macrocells may be referred to as a macro BS. A BS used for picocells may be referred to as a pico BS. A BS used for femtocells may be referred to as a femto BS or a home BS. Figure 1 In the examples shown, BS110a, 110b, and 110c can be macroBSs for macrocells 102a, 102b, and 102c, respectively. BS110x can be a picoBS for picocell 102x. BS110y and 110z can be femtoBSs for femtocells 102y and 102z, respectively. A BS can support one or more (e.g., three) cells.

[0048] The wireless communication network 100 may also include relay stations (e.g., relay station 110r) (also referred to as relays, etc.) that receive data and / or other information transmissions from upstream stations (e.g., BS 110 or UE 120r) and transmit such data and / or other information transmissions to downstream stations (e.g., UE 120 or BS 110), or relay transmissions between UEs 120 to facilitate communication between devices. Figure 1 In the example shown, relay station 110r can communicate with BS110a and UE 120r to facilitate communication between BS110a and UE 120r. A relay station can also be referred to as a relay BS, repeater, etc.

[0049] The wireless communication network 100 can be a heterogeneous network, comprising different types of base stations (BSs), such as macro BSs, pico BSs, femto BSs, repeaters, etc. These different types of BSs can have different transmit power levels, different coverage areas, and different effects on interference to the wireless communication network 100. For example, a macro BS can have a high transmit power level (e.g., 20 watts), while a pico BS, femto BS, and repeaters can have a lower transmit power level (e.g., 1 watt).

[0050] The wireless communication network 100 can support synchronous or asynchronous operation. For synchronous operation, the base stations (BSs) can have similar frame timings, and transmissions from different BSs can be approximately time-aligned. For asynchronous operation, the BSs can have different frame timings, and transmissions from different BSs can be out of time-aligned. The techniques described herein can be used for both synchronous and asynchronous operations.

[0051] UE 120 (e.g., UE 120x, UE 120y, etc.) may be distributed throughout the wireless communication network 100, and each UE may be stationary or mobile. UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premises equipment (CPE), cellular phone, smartphone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, appliance, medical device or medical apparatus, biometric sensor / device, wearable device (e.g., smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), entertainment device (e.g., music device, video device, satellite radio unit, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, GPS device, or any other suitable device configured to communicate via wireless or wired media. Some UEs can be considered machine-type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that can communicate with a BS, another device (e.g., a remote device), or some other entity. Wireless nodes can provide connectivity to or to a network, for example, via wired or wireless communication links. Some UEs can be considered Internet of Things (IoT) devices, which can be narrowband IoT (NB-IoT) devices.

[0052] Certain wireless networks (e.g., LTE) use Orthogonal Frequency Division Multiplexing (OFDM) on the downlink (DL) and Single-Carrier Frequency Division Multiplexing (SC-FDM) on the uplink (UL). OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, frequency bands, etc. Each subcarrier can be modulated using data. Typically, modulation symbols are transmitted using OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kHz and the minimum resource allocation (called a "resource block" (RB)) can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, the nominal Fast Fourier Transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into multiple subbands. For example, a subband can cover 1.08MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25, 2.5, 5, 10, or 20MHz, there can be 1, 2, 4, 8, or 16 subbands respectively.

[0053] While the aspects of the examples described herein may be associated with LTE technology, aspects of this disclosure are applicable to other wireless communication systems (e.g., NR). NR can utilize OFDM with CP on both UL and DL, and includes the use of TDD to support half-duplex operation. Beamforming can be supported and beam direction can be dynamically configured. MIMO transmission using precoding can also be supported. MIMO configurations in DL can support up to eight transmit antennas with up to eight streams and up to two streams per UE for multi-layer DL transmission. Multi-layer transmission with up to two streams per UE can be supported. Aggregation of multiple cells can be supported using up to eight serving cells.

[0054] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., a BS) allocates resources for communication among some or all devices and apparatuses within its service area or cell. The scheduling entity can be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities use the resources allocated by the scheduling entity. A BS is not the only entity that can act as a scheduling entity. In some examples, a UE can act as a scheduling entity and can schedule resources for one or more subordinate entities (e.g., one or more other UEs), and other UEs can utilize the resources scheduled by that UE for wireless communication. In some examples, a UE can act as a scheduling entity in a peer-to-peer (P2P) network or a mesh network. In mesh network examples, in addition to communicating with a scheduling entity, UEs can also communicate directly with each other.

[0055] exist Figure 1 In the diagram, a solid line with a double arrowhead indicates the desired transmission between the UE and the BS providing the service, where the BS is designated to provide the service to the UE on the DL and / or UL. A thin dashed line with a double arrowhead indicates interference transmission between the UE and the BS.

[0056] Network controller 130 can be coupled to a group of BS110s and provide coordination and control for these BS110s. Network controller 130 can communicate with the BS110s via backhaul. The BS110s can also communicate with each other via wireless or wired backhaul (e.g., directly or indirectly).

[0057] Figure 2 The BS110 and UE 120 are shown (e.g., in...). Figure 1 Example components of the wireless communication network 100 can be used to implement various aspects of this disclosure. For example, antenna 252, processors 266, 258, 264 and / or controller / processor 280 of UE 120, and / or antenna 234, processors 220, 230, 238 and / or controller / processor 240 of BS 110 can be used to perform the various techniques and methods described herein.

[0058] It should be noted that, although Figure 2 The diagram illustrates UE 120 communicating with BS110, but IAB nodes can similarly communicate with IAB donors (or other network entities), and each can (e.g., separately) have information about... Figure 2 Similar components to those discussed. In other words, an IAB node can have components similar to UE 120 and can be configured to perform... Figure 8 Operation 800, while the IAB donor (or other network entity) can have components similar to BS110 and can be configured to perform... Figure 9 Operation 900 or Figure 10 Operation 1000.

[0059] At BS110, the transmit processor 220 can receive data from data source 212 and control information from controller / processor 240. The control information can be used for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Common PDCCH (GCPDCCH), etc. The data can be used for the Physical Downlink Shared Channel (PDSCH), etc. The processor 220 can process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The processor 220 can also generate reference symbols, for example, for the Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), and Cell-Specific Reference Signal (CRS). The transmit (TX) Multiple-Input Multiple-Output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, and / or reference symbols (if applicable), and can provide an output symbol stream to the modulators (MODs) in 232a-232t. Each modulator 232 can (e.g., for OFDM, etc.) process the corresponding output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a DL signal. The DL signal from modulators 232a-232t can be transmitted via antennas 234a-234t respectively.

[0060] At UE 120, antennas 252a-252r can receive DL signals from BS110 or IAB donors, or IAB nodes can receive DL signals from IAB donors, and can provide the received signals to demodulators (DEMODs) 254a-254r in the transceiver. Each demodulator can adjust (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator can further process the input sample (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 can obtain received symbols from all demodulators 254a-254r in the transceiver, perform MIMO detection on the received symbols (if applicable), and provide the detected symbols. Receiver processor 258 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120 to data sink 260, and provide decoded control information to controller / processor 280.

[0061] At the UL, at the UE 120 or IAB node, the transmit processor 264 can receive data (e.g., for the Physical Uplink Shared Channel (PUSCH) or PSSCH) from the data source 262, and control information (e.g., for the Physical Uplink Control Channel (PUCCH) or PSCCH) from the controller / processor 280, and process that data and control information. The transmit processor 264 can also generate reference symbols for a reference signal (RS) (e.g., for a sounding reference signal (SRS)). Symbols from the transmit processor 264 can be pre-encoded (if applicable) by the TX MIMO processor 266, further processed by demodulators in transceivers 254a-254r (e.g., for SC-FDM, etc.), and transmitted to the BS110 or IAB donor.

[0062] At the BS110 or IAB donor, the UL signal from the UE 120 or IAB node can be received by antenna 234, processed by modulator 232, detected by MIMO detector 236 (if applicable), and further processed by receiver processor 238 to obtain decoded data and control information transmitted by the UE 120 or IAB node. Receiver processor 238 can provide the decoded data to data sink 239 and the decoded control information to controller / processor 240.

[0063] Controllers / processors 240 and 280 can respectively direct operations at BS110 and UE 120 (or at the IAB donor and IAB node, respectively). Controllers / processors 240 and / or other processors and modules at BS110 can execute or direct the execution of processes using the techniques described herein. Controllers / processors 280 and / or other processors and modules at UE 120 can execute or direct the execution of processes using the techniques described herein. Memory 242 and 282 can respectively store data and program code for BS110 and UE 120. Scheduler 244 can schedule data transmission by the UE on DL and / or UL.

[0064] Figure 3 This is a diagram illustrating an example of a radio access network (RAN) according to certain aspects of this disclosure.

[0065] As shown by reference numeral 305 in the attached figure, a conventional (e.g., 3G, 4G, or LTE) radio access network may include multiple BS 310s (e.g., access nodes (ANs)), wherein each BS 310 communicates with the core network via a wired backhaul link 315 (such as a fiber optic connection). BS 310 may communicate with UE 320 via an access link 325 (which may be a radio link). In some aspects, Figure 3The BS 310 shown can correspond to Figure 1 The BS110 shown. Similarly, Figure 3 The UE 320 shown can correspond to Figure 1 The UE 120 shown.

[0066] As indicated by reference numeral 330 in the attached figure, the RAN may include a wireless backhaul network. In some aspects or scenarios, the wireless backhaul network may sometimes be referred to as an IAB network. An IAB network may include multiple BSs, and sometimes the BSs may have different types or different operating characteristics. For example, in some aspects, an IAB network may have at least one BS 335 as an anchor BS. The anchor BS may communicate with the core network via a wired backhaul link 340 (e.g., a fiber optic connection). The anchor BS 335 may also be referred to as an IAB donor. The anchor BS may be configured to communicate with other types of BSs or other communication devices (such as radio networks or devices in the IAB network).

[0067] The IAB network may also include one or more non-anchored BSs 345. A non-anchored BS may be referred to as a relay BS or IAB node. A non-anchored BS 345 may communicate directly or indirectly with an anchored BS 335 via one or more backhaul links 350 (e.g., via one or more other non-anchored base stations 345) to form a backhaul path to the core network for carrying backhaul services. The backhaul link 350 may be a radio link. Anchored BS 335 or non-anchored BS 345 may communicate with one or more UEs 355 via an access link 360, which may be a radio link used to carry access services. In some aspects, Figure 3 The anchored BS 335 or non-anchored BS 345 shown can correspond to Figure 1 The BS110 shown. Similarly, Figure 3 The non-anchored BS 345 or UE 355 shown can correspond to Figure 1 The UE 120 shown.

[0068] As indicated by reference numeral 365 in the attached figure, in some aspects, the RAN including the IAB network can utilize various spectrum types. For example, the IAB network can utilize various different radio frequency bands. In some specific examples and according to some aspects, millimeter wave (mmW) technology or directional communication (e.g., beamforming, precoding) can be used for communication between BSs or UEs (e.g., between two BSs, between two UEs, or between a BS and a UE). In another or alternative aspect or example, the radio backhaul link 370 between BSs can use millimeter waves to carry information, or can use beamforming, precoding, to point towards a target BS. Similarly, the radio access link 375 between a UE and a BS can use millimeter waves or can be pointed towards a target radio node (e.g., a UE or a BS). In this way, inter-link interference can be reduced.

[0069] In some aspects, IAB networks can support multi-hop networks or multi-hop wireless backhaul. Alternatively, each node in an IAB network can use the same RAT (e.g., 5G / NR). Alternatively, nodes in an IAB network can share resources for access links and backhaul links, such as time resources, frequency resources, and spatial resources. Furthermore, various architectures for IAB nodes or IAB donors can be supported.

[0070] In some respects, an IAB donor may include a central unit (CU) that configures IAB nodes to access the core network via the IAB donor, and may include a distributed unit (DU) that schedules and communicates with the child nodes of the IAB donor.

[0071] In some aspects, an IAB node may include a mobile terminal component (MT) scheduled and communicating with a DU of the IAB donor, and may include a DU that schedules and communicates with a child node of the IAB node or UE. The DU of the IAB node may perform the functions described in BS110 for the IAB node, and the MT of the IAB node may perform the functions described in UE 120 for the IAB node.

[0072] Figure 4 This is a diagram illustrating an example of an IAB network architecture based on certain aspects of this disclosure. (See diagram for example.) Figure 4 As shown, the IAB network may include an IAB donor 405 connected to the core network via a wired connection (e.g., as a wired fiber optic cable). For example, the Ng interface of the IAB donor 405 may terminate at the core network. Alternatively or concurrently, the IAB donor 405 may connect to one or more devices of the core network providing core access and mobility management functions (AMF). In some aspects, the IAB donor 405 may include a BS110, such as an anchor BS, as described above. Figure 3As described, the IAB donor 405 may include a CU that can perform ANC or AMF functions. The CU can configure the DU of the IAB donor 405 or can configure one or more IAB nodes 410 (e.g., the MT or DU of IAB node 410) connected to the core network via the IAB donor 405. Therefore, the CU of the IAB donor 405 can control or configure the entire IAB network connected to the core network via the IAB donor 405, for example, by using control messages or configuration messages (e.g., Radio Resource Control (RRC) configuration messages, F1 Application Protocol (F1AP) messages).

[0073] As described above, the IAB network may include IAB nodes 410 (shown as IAB nodes 1 to 4) connected to the core network via IAB donor 405. As shown, IAB node 410 may include a MT and may include a DU. The MT of IAB node 410 (e.g., a child IAB node) may be controlled or scheduled by another IAB node 410 (e.g., a parent IAB node) or by IAB donor 405. The DU of IAB node 410 (e.g., a parent IAB node) may control or schedule other IAB nodes 410 (e.g., child nodes of the parent node) or UE 120. Therefore, the DU may be referred to as a scheduling node or scheduling component, and the MT may be referred to as a scheduled node or scheduled component. In some aspects, IAB donor 405 may include DU instead of MT. That is, IAB donor 405 may configure, control, or schedule communications of IAB node 410 or UE 120. UE 120 may include only the MT and not the DU. That is, the communication of UE 120 can be controlled or scheduled by IAB donor 405 or IAB node 410 (e.g., the parent node of UE 120).

[0074] Depending on certain aspects, certain nodes can be configured to participate in control / scheduling processes. For example, in some aspects, when a first node controls or schedules communication for a second node (e.g., when the first node provides DU functionality for the second node's MT), the first node can be referred to as the parent node of the second node, and the second node can be referred to as the child node of the first node. The child node of the second node can be referred to as the grandchild node of the first node. Therefore, the DU of the parent node can control or schedule the communication of the parent node's child node. The parent node can be IAB donor 405 or IAB node 410, and the child node can be IAB node 410 or UE 120. The communication of the child node's MT can be controlled or scheduled by the child node's parent node.

[0075] like Figure 4As shown, the link between UE 120 and IAB donor 405 or between UE 120 and IAB node 410 can be referred to as access link 415. Each access link 415 can be a radio access link that provides radio access to the core network to UE 120 via IAB donor 405 and potentially via one or more IAB nodes 410.

[0076] like Figure 4 As further illustrated, the link between IAB donor 405 and IAB node 410, or between two IAB nodes 410, can be referred to as a backhaul link 420. Each backhaul link 420 can be a wireless backhaul link that provides radio access to the core network to IAB node 410 via IAB donor 405 and potentially via one or more other intermediate IAB nodes 410. In some aspects, backhaul link 420 can be a primary backhaul link or a secondary backhaul link (e.g., a backup backhaul link). In some aspects, a secondary backhaul link can be used if the primary backhaul link fails, becomes congested, or becomes overloaded. In the IAB network, network resources (e.g., time resources, frequency resources, spatial resources) used for wireless communication can be shared between access link 415 and backhaul link 420.

[0077] As mentioned above, in a typical IAB network, IAB nodes (e.g., non-anchored BSs) are stationary (i.e., do not move). The stated goal of next-generation (5G) wireless networks is to provide ultra-high data rates and support a wide range of application scenarios. IAB systems are being studied in 3GPP as a possible solution to help achieve these goals.

[0078] As mentioned above, in IAB, a wireless backhaul solution is used to connect cells (IAB nodes) to the core network (which uses wired backhaul). Some attractive features of IAB are its support for multi-hop wireless backhaul, sharing the same technologies (e.g., NR) and resources (e.g., frequency bands) used for both access and backhaul links.

[0079] There are multiple possible architectures for IAB nodes, including Layer 2 (L2) and Layer 3 (L3) solutions, and the specific architecture deployed can depend on which protocol stack layers are implemented in the intermediate node (IAB node). For example, an L2 relay can implement the Physical (PHY) / Media Access Control (MAC) / Radio Link Control (RLC) layers.

[0080] Example migration of integrated access and backhaul (IAB) nodes

[0081] This disclosure relates to various aspects of the migration process of Integrated Access and Backhaul (IAB) nodes, and more specifically, to the migration process of IAB nodes during IAB donor-initiated handover (HO) procedures or IAB node-initiated link re-establishment procedures.

[0082] The IABHO procedure can be used to direct an IAB node from a source IAB donor to a target IAB donor. In some cases, the HO procedure can be used when the quality of the link between the distributed unit (DU) component (also referred to herein as a part) of a parent IAB node (also referred to herein as an IAB-DU) and the mobile terminal component (MT) of a child IAB node (also referred to herein as an IAB-MT) has degraded. In some cases, the HO procedure can be used for load balancing of other IAB nodes in the IAB network. A re-establishment procedure can be used when a link failure is detected between the parent IAB node's IAB-DU and the child IAB node's IAB-MT.

[0083] The migration of an IAB node can involve any combination of three parts, including (1) migrating the MT component of the IAB node from a first IAB donor (e.g., from the central unit (CU) of the first IAB donor) to a second IAB donor (e.g., to the CU of the second IAB donor), (2) migrating the DU component of the IAB node from the first IAB donor to the second IAB donor, and (3) migrating the descendant nodes of the IAB node (e.g., user equipment (UE) having a link connection to the DU component of the IAB node) from the first IAB donor to the second IAB donor. As described herein, the migration from the first IAB donor to the second IAB donor involves the migration of the CU and DU components of the first IAB donor to the CU and DU components of the second IAB donor. As described herein, an IAB donor may include the CU of the IAB node configured to access the core network via the IAB donor, and may include the DU that schedules and communicates with the child nodes of the IAB donor.

[0084] Figure 5A and 5B This is a diagram illustrating an example migration of the MT component of an IAB node via the HO process, according to certain aspects of this disclosure. (See diagram for example.) Figure 5AAs shown, in the IAB network architecture 500A, a first IAB donor (such as IAB donor 1) and a second IAB donor (such as IAB donor 2) can be connected to an Internet Protocol (IP) network. IAB donor 1 may include a CU (e.g., donor CU1), which can configure the DU of IAB donor 1 and one or more IAB nodes. For example, donor CU1 can configure IAB node 1 (including both IAB-MT1 and IAB-DU1) and IAB node 3 (including both IAB-MT3 and IAB-DU3). Therefore, the context of each of the descendant nodes (e.g., UE1) of IAB-MT1, IAB-DU1, IAB-MT3, IAB-DU3, and IAB node 3 can be maintained at donor CU1.

[0085] Similarly, IAB donor 2 may include a CU (e.g., donor CU2), which can configure the DUs (including both IAB-MT2 and IAB-DU2) of IAB donor 2 and IAB node 2. Therefore, the context of each of IAB-MT2 and IAB-DU2 can be maintained at donor CU2.

[0086] As used in this document, "context" refers to configurations related to the control plane, configurations related to the user plane, and / or how connections to the core network for that node are managed. For example, the context of UE1 may include the UE's physical configuration, the number of cells serving the UE, the UE's carrier aggregation (CA) information, quality of service (QoS) data quality, one or more services of the UE (e.g., voice calls and video downloads are different services and may require different processing), the vertebrae of communications to the core network for the UE, etc.

[0087] At time t1, donor CU1 may initiate HO preparation from IAB-MT3 to donor CU2 for reasons discussed in this paper (including link degradation and load balancing between IAB-DU1 and IAB-MT3). Therefore, as Figure 5B As shown in the IAB network architecture 500B, at time t2, when the HO process is completed, a signaling connection can be established between IAB-MT3 and donor CU2.

[0088] In this scenario, IAB-DU3 can still maintain its IP network connection with donor CU1. In other words, the contexts of IAB-DU3 and UE1 remain with donor CU1, and UE1 can still be served within the same cell. However, the context of IAB-MT3 can be passed from donor CU1 to donor CU2. Donor CU1 may be aware of the IAB-MT3 context transfer from donor CU1 to donor CU2 because the HO procedure (such as MT transfer) was initiated by donor CU1. Therefore, donor CU1 may be aware of the new signaling connection established between IAB-MT3 and IAB-DU2.

[0089] At time t2, donor CU1 can decide to take further action against IAB-DU3 and UE1. In some cases, donor CU1 can decide to keep the context of IAB-DU3 and UE1 at donor CU1, so donor CU1 can re-establish service between donor CU1 and IAB-DU3 and UE1 via donor CU2's topology (e.g., re-establish the backhaul path). In other words, donor CU1 can use the connections already established by donor CU2 (e.g., links and nodes extending from donor CU2 to IAB node 3) to re-establish the connection with IAB-DU3. To re-establish service, donor CU1 and donor CU2 can exchange information, including at least one of QoS information, QoS mapping information, Backhaul Adaptation Protocol (BAP) configuration assigned to IAB-MT3, or IP configuration assigned to IAB-MT3. In other cases, donor CU1 may decide to also pass the context of each of IAB-DU3 and UE1 to donor CU2, so that in addition to the context of descendant nodes of IAB node3 (such as UE1), the context of the MT and DU components of IAB node3 is also maintained at donor CU2. In either case, donor CU1 knows whether to complete the service re-establishment or context passing.

[0090] Figure 6A and 6B This is a diagram illustrating an example migration of the MT component of an IAB node via a link re-establishment process, according to certain aspects of this disclosure. Figure 5A Similarly, such as Figure 6AAs shown in the IAB network architecture 600A, IAB donor 1 and IAB donor 2 can be connected to an IP network. IAB donor 1 may include donor CU1, which can be configured with IAB-MT1, IAB-DU1, IAB-MT3, and IAB-DU3. Therefore, the context of each of the descendant nodes (e.g., UE1) of IAB-MT1, IAB-DU1, IAB-MT3, IAB-DU3, and IAB-DU3 can be maintained at donor CU1. IAB donor 2 may include donor CU2, which can be configured with IAB-MT2 and IAB-DU2, so the context of each of IAB-MT2 and IAB-DU2 can be maintained at donor CU2.

[0091] In this process, donor CU1 initiates the HO procedure to migrate IAB-MT3 to donor CU2. Figure 5A The difference lies in Figure 6A In this process, IAB node 3 can initiate a re-establishment procedure to migrate IAB-MT3 to donor CU2. As described in this article, a re-establishment procedure can be initiated when the link connection fails. Figure 6A As shown, the link connection between IAB-MT3 and IAB-DU1 may be lost (e.g., this means that there is no longer a connection between IAB-MT3 and any IAB donor in IAB Network Architecture 600A), therefore, IAB-MT3 can initiate a re-establishment. Since the MT component of an IAB node is similar to a User Equipment (UE), when the MT of an IAB node experiences a link failure, the MT can initiate and re-establish the signaling connection. Therefore, IAB-MT3 can initiate the re-establishment of the connection.

[0092] At time t2, such as Figure 6B As shown in the IAB network architecture 600B, IAB-MT3 can establish a connection with donor CU2 during the re-establishment process by sending a re-establishment request to donor CU2. This re-establishment request can provide donor CU2 with sufficient information to determine that IAB-MT3 was initially served by donor CU1. Donor CU2 can use this information to obtain the IAB-MT3 context from donor CU1. When donor CU1 obtains the IAB-MT3 context from donor CU2, donor CU2 may become aware of the new signaling connection established between IAB-MT3 and donor CU2.

[0093] and Figure 5A and 5BSimilar to the HO procedure shown, during this re-establishment process, the contexts of IAB-DU3 and UE1 can be retained at donor CU1. Therefore, at time t2, donor CU1 can decide to (1) retain the contexts of IAB-DU3 and UE1 at donor CU1 and re-establish service between donor CU1 and IAB-DU3 and UE1 via donor CU2 topology (e.g., re-establish the backhaul path), or (2) transfer the context of each of IAB-DU3 and UE1 to donor CU2, such that the contexts of the MT and DU components of IAB node 3 are also maintained at donor CU2, in addition to the contexts of the descendant nodes of IAB node 3 (e.g., UE1). In either case, given that donor CU1 knows the connection between IAB-MT3 and donor CU2 when donor CU2 obtains (e.g., acquires) the context of IAB-MT3, donor CU1 may know to complete either service re-establishment or context transfer.

[0094] Although Figure 5A , 5B Figures 6A and 6B show that a signaling connection with donor CU2 can be established during the HO or re-establishment process, but any donor in the IAB network can establish a connection with an IAB node during these processes.

[0095] However, in some scenarios, the MT and DU components of an IAB node may not be co-located before the HO and re-establishment processes. In other words, the context of the MT component of an IAB node may be maintained at the first IAB donor, while the context of the DU component of an IAB node may be maintained at the second IAB donor. In such cases, when the MT component of an IAB node migrates due to HO or link re-establishment, the second IAB donor may be blind (e.g., undetected) to the context transfer of the MT component from the first IAB donor to another IAB donor with whom the MT establishes a new signaling connection.

[0096] Figure 7A and 7B This is a diagram illustrating an example migration of the MT component of an IAB node when the MT and DU components of the IAB node are not co-located prior to the migration, according to certain aspects of this disclosure. Figure 7AAs shown in the 700A IAB network architecture, IAB donor 1, IAB donor 2, and IAB donor 3 can connect to an IP network. IAB donor 1 may include donor CU1, which can configure IAB-MT1, IAB-DU1, and IAB-MT3, and the context of each of IAB-MT1, IAB-DU1, and IAB-MT3 can be maintained at donor CU1. IAB donor 2 may include donor CU2, which can configure IAB-MT2 and IAB-DU2, and the context of each of IAB-MT2 and IAB-DU2 can be maintained at donor CU2. IAB donor 3 may include donor CU3, which can configure IAB-DU3 and the descendant node (UE1) of IAB node 3, and the context of each of IAB-DU3 and UE1 can be maintained at donor CU3.

[0097] In a steady state, at time t1, the signaling connection between IAB-MT3 of IAB Node 3 and donor CU1 can be a Radio Resource Control (RRC) connection with donor CU1, and the signaling connection between IAB-DU3 of IAB Node 3 can be a wired interface connection using at least one of the F1 Control Plane (F1-C) protocol or the F1 Application Layer Signaling Protocol (F1-AP). In this case, donor CU3 can use the topology of donor CU1 to communicate with IAB-DU3 and UE1.

[0098] Since IAB node 3 has more than one signaling connection with the IAB donor of the IAB network architecture 600A, the context of IAB-MT3 is maintained at donor CU1, and the context of IAB-DU3 is maintained at donor CU2. Therefore, it can be said that the MT and DU components of IAB-3 are not co-located at time t1.

[0099] At time t1, the HO or re-establishment process may be initiated for the reasons discussed herein. Specifically, the HO process may be initiated by donor CU1, or the re-establishment process may be initiated by IAB-MT3. At time t2, IAB-MT3 may migrate from donor CU1 to donor CU2, thereby establishing a signaling connection between IAB-MT3 and donor CU2 when the HO or re-establishment process is completed.

[0100] Regardless of whether the IAB-MT3 migration occurs due to a HO initiated by donor CU1 or a re-establishment process initiated by IAB-MT3, donor CU3 may be unaware that the IAB-MT3 context has changed. For example, suppose the IAB-MT3 migration occurs due to a HO initiated by donor CU1. Given the pass initiated by donor CU1, donor CU1 may be aware of the migration, and because donor CU2 is the donor establishing the new connection with IAB-MT3, donor CU2 may also be aware of the migration; however, donor CU3 may not be involved in the process. Similarly, suppose the IAB-MT3 migration occurs due to a re-establishment process initiated by IAB-MT3. When donor CU2 obtains the IAB-MT3 context from donor CU1, donor CU1 may be aware of the pass, and because donor CU2 is the donor establishing the new connection with IAB-MT3, donor CU2 may also be aware of the pass; however, donor CU3 may not be involved in the process. In other words, donor CU3 may be blind to the migration.

[0101] Donor DU3 understands that the passover may be important in order to continue communicating with IAB-DU3 and UE1. As mentioned above, prior to the migration, Donor CU3 could communicate with IAB-DU3 and UE1 using Donor CU1's topology. However, when IAB-MT3 establishes a new signaling connection with Donor CU2, Donor CU3 may no longer be able to communicate with IAB-DU3 and UE1 using Donor CU1's topology. Without knowing the passover, Donor CU3 may be unable to re-establish service with these entities, and communication may be lost. Furthermore, if Donor CU3 decides to initiate a context passover for these entities, Donor CU3 understands that the passover may be important to allow Donor CU3 to pass the context of IAB-DU3 and / or UE1 to Donor CU1.

[0102] Example donor-to-donor topology discovery in Integrated Access and Backhaul (IAB)

[0103] Various aspects of this disclosure provide solutions for scenarios where components of an Integrated Access and Backhaul (IAB) node are not co-located prior to the migration of at least one component of the IAB node. In some cases, the Mobile Terminal (MT) component and the Distributed Unit (DU) component of an IAB node may not be co-located; therefore, the context of the MT may be maintained at a first IAB donor, while the context of the DU may be maintained at a second IAB donor. When the MT component of an IAB node migrates, the second IAB donor may be blind (e.g., undetected) to the context transfer of the MT component from the first IAB donor to another IAB donor (e.g., the establishment of a new signaling connection between the MT component and another IAB donor is blind). Various aspects of this disclosure provide techniques for discovering donor topology among IAB donors in the IAB network architecture to notify the second IAB donor of the transfer. In some cases, the IAB node itself may notify the second IAB donor of the transfer. In other cases, an IAB donor with a new connection to the MT component of an IAB node may notify the second IAB donor of the transfer.

[0104] Figure 8 This is a flowchart illustrating an example operation 800 for wireless communication performed by an IAB node (e.g., having DU and MT components) according to certain aspects of this disclosure. For example, operation 800 can be performed by an IAB node having non-co-located MT and DU components.

[0105] Operation 800 can be implemented in one or more processors (e.g., Figure 2 The software components executed and running on the controller / processor 280. Furthermore, the transmission and reception of signals by the IAB node in operation 800 can be, for example, by one or more antennas (e.g., Figure 2 This can be achieved via antenna 252. In some aspects, the transmission and / or reception of signals by the IAB node can be achieved via a bus interface used by one or more processors (e.g., controllers / processors 258, 264, 266 and / or 280) to acquire and / or output signals.

[0106] Operation 800 can begin at box 802, whereby the IAB node establishes a first signaling connection with the first IAB donor. The first signaling connection can be an RRC connection.

[0107] At box 804, the IAB node establishes a second signaling connection with the second IAB donor. The second signaling connection may be a wired interface connection using at least one of the following: F1 Control Plane (F1-C) protocol or F1 Application Layer Signaling Protocol (F1-AP).

[0108] At box 806, the IAB node sends an indication to the second IAB donor that the IAB node has a first signaling connection with the first IAB donor.

[0109] As an illustrative example, using Figure 7A and 7B As shown, at point 802, IAB node 3 can establish a first signaling connection with IAB donor 2. At point 804, IAB node 3 can establish a second signaling connection with IAB donor 3. At point 806, IAB node 3 can send an indication to IAB donor 3 regarding the first signaling connection between IAB node 3 and IAB donor 2.

[0110] Figure 9 This is a flowchart illustrating an example operation 900 for wireless communication performed by a first IAB donor (e.g., having DU and central unit (CU) components) according to certain aspects of this disclosure. For example, operation 900 can be performed by... Figure 7A and 7B The operation is executed by IAB donor 3. Operation 900 can be considered as being executed by the IAB node. Figure 8 The operation of 800 is a supplement.

[0111] Operation 900 can be implemented in one or more processors (e.g., Figure 2 The software components executed and running on the controller / processor 240. Furthermore, the transmission and reception of signals by the IAB donor in operation 900 can be, for example, by one or more antennas (e.g., Figure 2 Antenna 234) is used to achieve this. In some aspects, the transmission and / or reception of signals by the IAB donor can be achieved via a bus interface used by one or more processors (e.g., controllers / processors 230, 220, 238, 240 and / or 244) to acquire and / or output signals.

[0112] Operation 900 can begin at box 902, whereby the IAB donor and the IAB node establish a first signaling connection. The first signaling connection can be a wired interface connection using at least one of the following protocols: F1-C or F1-AP.

[0113] At box 904, the IAB donor receives an indication that the IAB node has a second signaling connection with the second IAB donor. The IAB donor may receive the indication from at least one of the IAB node or the second IAB donor.

[0114] At box 906, in response to receiving an instruction, the IAB donor transmits information related to the IAB node to the second IAB donor, and re-establishes the service between the first IAB donor and the IAB node, or any combination thereof, through the topology of the second IAB donor.

[0115] As an illustrative example, using Figure 7A and 7B As shown, at 902, IAB donor 3 can establish a first signaling connection with IAB node 3. At 904, IAB donor 3 can receive an indication that IAB node 3 has a second signaling connection with IAB donor 2. At 906, in response to receiving the indication, IAB donor 3 can transmit information related to IAB node 3 to IAB donor 2 to re-establish services between IAB donor 3 and IAB node 3 via the topology of IAB donor 2, or any combination thereof.

[0116] Figure 10 This is a flowchart illustrating an example operation 1000 for wireless communication performed by a first IAB donor (e.g., having DU and CU components) according to certain aspects of this disclosure. For example, operation 1000 can be performed by... Figure 7A and 7B The operation is executed by IAB donor 2. Operation 1000 can be considered as being executed by the IAB node. Figure 8 The operation of 800 is a supplement.

[0117] Operation 1000 can be implemented in one or more processors (e.g., Figure 2 The software components executed and running on the controller / processor 240. Furthermore, the transmission and reception of signals by the IAB donor in operation 1000 can, for example, be performed by one or more antennas (e.g., Figure 2 Antenna 234) is used to achieve this. In some aspects, the transmission and / or reception of signals by the IAB donor can be achieved via a bus interface used by one or more processors (e.g., controllers / processors 230, 220, 238, 240 and / or 244) to acquire and / or output signals.

[0118] Operation 1000 can begin at box 1002, where the IAB donor establishes the first signaling connection with the IAB node.

[0119] At box 1004, the IAB donor receives a first indication from the IAB node that the IAB node has a second signaling connection with the second IAB donor.

[0120] At box 1006, the IAB donor sends a second indication to the second IAB donor that the first IAB donor has a first signaling connection with the IAB node.

[0121] As an illustrative example, using Figure 7A and 7BAs shown, at point 1002, IAB donor 3 can establish a first signaling connection with IAB node 2. At point 1004, IAB donor 2 can receive a first indication from IAB node 3 regarding IAB node 3 having a second signaling connection with IAB donor 3. At point 1006, IAB donor 2 sends a second indication to IAB donor 3 regarding IAB donor 2 having a first signaling connection with IAB node 3.

[0122] Figure 8 and 9 Operations 800 and 900 can be used as a reference. Figure 11A Described, Figure 11A This is a call flowchart illustrating an example method for donor-to-donor topology discovery in an IAB network, based on certain aspects of this disclosure. Figure 8 and 10 Operations at 800 and 1000 can be used as a reference. Figure 11B Described, Figure 11B This is another call flowchart illustrating an example method for donor-to-donor topology discovery in IAB networks, based on certain aspects of this disclosure.

[0123] exist Figure 11A In the illustrative example, an IAB node can notify the (unaware) IAB donor of the context passing of the IAB node's MT component. For example... Figure 11A As shown, the IAB node can establish a first signaling connection 1102 with the first IAB donor.

[0124] In some aspects, the establishment of a first signaling connection with the first IAB donor occurs due to the migration of the IAB node caused by an HO procedure. In other aspects, the establishment of a first signaling connection with the first IAB donor occurs due to the migration of the IAB node caused by a re-establishment procedure initiated by the IAB node. The first signaling connection may be an RRC connection between the MT component of the IAB node and the first IAB donor. The RRC connection may be established via at least one of the following: an RRC connection establishment request, an RRC reconfiguration request, an RRC connection re-establishment request, or an RRC connection recovery request (depending on whether the first signaling connection is established based on an HO procedure or a re-establishment procedure).

[0125] After establishing the first signaling connection 1102, the IAB node can establish a second signaling connection 1104 with the second IAB donor. The second signaling connection can be a wired interface connection using at least one of the following protocols: F1-C or F1-AP. In some aspects, the wired interface connection can be established via the first IAB donor (e.g., via the first IAB donor's DU).

[0126] In some aspects, establishing a second signaling connection 1104 to the second IAB donor can be a redirection of an initial (or previous) connection to the second IAB donor. For example, an initial signaling connection 1108 between the IAB node and the second IAB donor may have been established before the establishment of the first signaling connection 1102. This initial signaling connection 1108 may have been interrupted, at least in part, due to the migration of the IAB node (e.g., migration of the MT component of the IAB node during HO or re-establishment). Therefore, the established second signaling connection 1104 can be viewed as a redirection of the initial signaling connection 1108 on the recovery path toward the first IAB donor.

[0127] Because the MT and DU of the IAB node are not co-located prior to the migration of the MT (e.g., not co-located prior to the establishment of the first signaling connection 1102), the second IAB donor may be blind (e.g., unaware) to the context passing from the MT component to the first IAB donor. Therefore, the IAB node can send indication 1106 (originating from the DU of the IAB node) to the second IAB donor. This indication can indicate that the IAB node has a first signaling connection with the first IAB donor. In some aspects, the IAB node can send the BAP address assigned to the IAB node, which is notified by the first IAB donor to the second IAB donor. In some aspects, the IAB node can send the identifier of the first IAB donor to notify the second IAB donor.

[0128] exist Figure 11B In the illustrative example, the first IAB donor can send an instruction to the second IAB donor to notify the second IAB donor of the context passing of the MT component of the IAB node, instead of as... Figure 11A The IAB node shown sends an instruction to the second IAB donor.

[0129] and Figure 11A Similarly, in Figure 11B In this context, an IAB node can establish a first signaling connection 1102 with a first IAB donor and a second signaling connection 1104 with a second IAB donor. Establishing the second signaling connection to the second IAB donor 1104 can be a redirection of the initial (or previous) signaling connection 1108 to the second IAB donor.

[0130] However with Figure 11A The difference is that, in Figure 11BIn this context, an IAB node can send the identifier 1110 of the second IAB donor to the first IAB donor, thereby allowing the first IAB donor to send an indication 1112 to the second IAB donor indicating that the IAB node has a first signaling connection with the first IAB donor. In some aspects, the identifier 1110 may be the gNB-ID of the second IAB donor (given that the second IAB donor is a gNB). In some aspects, the identifier 1110 may be the cell ID (e.g., carrying the gNB-ID of the second IAB donor) of the cell (or old cell) on which the IAB node is currently (or was) served by the second IAB donor. For example, the gNB-ID may be part of a cell ID (such as a New Radio Cell Global Identifier (NCGI)) / New Radio Cell Identifier (NCI); thus, in the case where a gNB (such as an IAB donor) serves ten cells, each of these cells may have a concatenated cell ID as a gNB-ID and a local ID. Therefore, when sent to the first IAB donor, the cell ID can inform the second IAB donor because the cell ID can carry the gNB-ID of the second IAB donor. In some aspects, the identifier 1110 can be the routing information (e.g., IP address) of the second IAB donor.

[0131] Regardless of the entity (e.g.) Figure 11A The IAB node shown or Figure 11B The first IAB donor (as shown) sends an instruction, and the second IAB donor can receive an instruction regarding the IAB node having a first signaling connection with the first IAB donor. In response to receiving the instruction, the second IAB donor can transmit information related to the IAB node to the first IAB donor to re-establish the service between the second IAB donor and the IAB node via the topology of the first IAB donor, or any combination thereof.

[0132] According to some aspects, transmitting information related to an IAB node to the first IAB donor may include transmitting at least one of the following: the context of the MT component (or part) of the IAB node, the context of the DU component (or part) of the IAB node, the context of a child node of the IAB node, or the context of a descendant node (e.g., a UE) of the IAB node. In some aspects, the second IAB donor may receive an acknowledgment (ACK) feedback from the first IAB donor in response to the transmission of information related to the IAB node.

[0133] According to certain aspects, re-establishing services between the second IAB donor and the IAB node may include: the exchange of service information between the second IAB donor and the first IAB donor related to the MT component, DU component, child nodes, descendant nodes, or any combination thereof of the IAB node. The service information may include at least one of the following: QoS information, QoS mapping information, BAP configuration assigned to the IAB node, or IP configuration assigned to the IAB node. For example, BAP configuration and / or IP configuration may be exchanged to establish BAP / IP transport for rerouted services via the topology of the first IAB donor. The BAP configuration may include BAP address, BAP route ID / path ID, Radio Link Control (RLC) Channel (CH) ID, mappings, etc. In some cases, the BAP configuration may be provided on an RRC connection, but in most cases, it may be provided on an F1 connection. Therefore, the BAP configuration may be provided by the CU of the first IAB donor or the CU of the second IAB donor. IP configurations (such as IP addresses) can be assigned on RRC connections; therefore, which CU assigns the IP configuration can depend on whether it is for a migrated IAB node or a descendant node of the migrated IAB node that is re-establishing services (e.g., for a migrated node it is the first IAB donor, but for a descendant node it could be the second IAB donor).

[0134] Depending on the circumstances, re-establishing services between the second IAB donor and the IAB node may include re-establishing F1 services or re-establishing non-F1 services.

[0135] Example wireless communication device

[0136] Figure 12 This illustrates operations that may include being configured to perform the techniques disclosed herein (such as...). Figure 8 The communication device 1200 (e.g., a transmitter such as a UE) comprises various components (e.g., corresponding functional unit module components) of the operation shown herein. The communication device 1200 includes a processing system 1202 coupled to a transceiver 1208 (e.g., a transmitter and / or a receiver). The transceiver 1208 is configured to transmit and receive signals for the communication device 1200 via an antenna 1210, such as various signals as described herein. The processing system 1202 may be configured to perform processing functions for the communication device 1200, including processing signals received by and / or to be transmitted by the communication device 1200.

[0137] Processing system 1202 includes processor 1204 coupled to computer-readable medium / memory 1212 via bus 1206. In some aspects, computer-readable medium / memory 1212 is configured to store instructions (e.g., computer-executable code) that, when executed by processor 1204, cause processor 1204 to perform... Figure 8 The operations shown herein or other operations used to perform the various techniques discussed herein.

[0138] In some aspects, the computer-readable medium / memory 1212 stores code 1214 for establishing and code 1216 for transmitting. In some aspects, code 1214 for establishing may include code for establishing a first signaling connection with a first IAB donor. In some aspects, code 1214 for establishing may include code for establishing a second signaling connection with a second IAB donor. In some aspects, code 1216 for transmitting may include code for sending an indication to the second IAB donor that the IAB node has a first signaling connection with the first IAB donor.

[0139] In a particular aspect, processor 1204 has circuitry configured to implement code stored in computer-readable medium / memory 1212. Processor 1204 includes circuitry 1224 for establishing and circuitry 1226 for transmitting.

[0140] In some aspects, the circuitry 1224 for establishing a connection may include circuitry for establishing a first signaling connection with a first IAB donor. In some aspects, the circuitry 1224 for establishing a connection may include circuitry for establishing a second signaling connection with a second IAB donor. In some aspects, the circuitry 1224 for establishing a connection may include circuitry for sending an indication to the second IAB donor that the IAB node has a first signaling connection with the first IAB donor.

[0141] In some aspects, it can be implemented by one or more functional unit module components. Figure 8 The operations shown herein, as well as other operations described herein, are examples. For instance, in some aspects, such operations can be implemented by a unit for establishing and a unit for transmitting.

[0142] In some aspects, the unit for establishing and the unit for transmitting include a processing system, which may include one or more processors, such as in... Figure 2 The UE 120 shown includes a receive processor 258, a transmit processor 264, a TX MIMO processor 266, and / or a controller / processor 280 and / or Figure 12 The processing system 1202 of the communication equipment 1200.

[0143] Transceiver 1208 can provide a unit for receiving or transmitting information. It can also transmit information to other components of communication device 1200. Antenna 1210 can correspond to a single antenna or a group of antennas. Transceiver 1208 can provide a unit for transmitting signals generated by other components of communication device 1200.

[0144] The unit for receiving or the unit for obtaining may include in Figure 2 The receiver (such as receiver processor 258) or antenna 252 of the UE 120 shown. Units for transmitting or for output may be included in... Figure 2 The transmitter (such as transmit processor 264) or antenna 252 of the UE 120 shown.

[0145] It is worth noting that, Figure 12 This is just one example; many other examples and configurations of the communication device 1200 are possible.

[0146] Figure 13 The illustration shows operations that may include being configured to perform the techniques disclosed herein (such as...). Figure 9 The communication device 1300 (e.g., a receiver such as a gNB) comprises various components (e.g., corresponding functional unit module components) of the operation shown herein. The communication device 1300 includes a processing system 1302 coupled to a transceiver 1308 (e.g., a transmitter and / or receiver). The transceiver 1308 is configured to transmit and receive signals for the communication device 1300 via an antenna 1310, such as the various signals described herein. The processing system 1302 may be configured to perform processing functions for the communication device 1300, including processing signals received and / or to be transmitted by the communication device 1300.

[0147] Processing system 1302 includes processor 1304 coupled to computer-readable medium / memory 1312 via bus 1306. In some aspects, computer-readable medium / memory 1312 is configured to store instructions (e.g., computer-executable code) that, when executed by processor 1304, cause processor 1304 to perform... Figure 9 The operations shown herein or other operations used to perform the various techniques discussed herein.

[0148] In some aspects, the computer-readable medium / memory 1312 stores: code 1314 for establishing; code 1316 for receiving; code 1318 for transmitting; and code 1320 for re-establishing. In some aspects, the code 1314 for establishing may include code for establishing a first signaling connection with the IAB node. In some aspects, the code 1316 for receiving may include code for receiving an indication that the IAB node has a second signaling connection with a second IAB donor. In some aspects, the code 1318 for transmitting may include code for transmitting information related to the IAB node to the second IAB donor in response to receiving the indication. In some aspects, the code 1320 for re-establishing may include code for re-establishing service between the first IAB donor and the IAB node via the topology of the second IAB donor in response to receiving an indication.

[0149] In some aspects, processor 1304 has circuitry configured to implement code stored in computer-readable medium / memory 1312. Processor 1304 includes circuitry 1324 for establishing, circuitry 1326 for receiving, circuitry 1328 for transmitting, and circuitry 1330 for re-establishing.

[0150] In some aspects, the circuitry 1324 for establishing a connection may include circuitry for establishing a first signaling connection with the IAB node. In some aspects, the circuitry 1326 for receiving may include circuitry for receiving an indication that the IAB node has a second signaling connection with a second IAB donor. In some aspects, the circuitry 1328 for transmitting information may include circuitry for transmitting information related to the IAB node to the second IAB donor in response to receiving an indication. In some aspects, the circuitry 1330 for re-establishing a connection may include circuitry for re-establishing service between the first IAB donor and the IAB node via the topology of the second IAB donor in response to receiving an indication.

[0151] In some aspects, it can be implemented by one or more functional unit module components. Figure 9 The operations shown herein, as well as other operations described herein, are illustrated. For example, in some aspects, such operations can be implemented using units for establishing, units for receiving, units for transmitting, and units for re-establishing.

[0152] In some aspects, the units for establishing, the units for transmitting, and the units for re-establishing include a processing system, which may include one or more processors, such as in... Figure 2 The BS110 shown includes a receiver processor 238, a transmitter processor 220, a TX MIMO processor 230, and / or a controller / processor 240 and / or Figure 13 The processing system 1302 of the communication device 1300.

[0153] Transceiver 1308 can provide a unit for receiving or transmitting information. It can also transmit information to other components of communication device 1300. Antenna 1310 can correspond to a single antenna or a group of antennas. Transceiver 1308 can provide a unit for transmitting signals generated by other components of communication device 1300.

[0154] The unit for receiving or the unit for obtaining may include in Figure 2 The receiver (such as receiver processor 238) or antenna 234 of the BS110 shown. Units for transmitting or for output (units for transmission) may be included in... Figure 2 The transmitter (such as transmit processor 220) or antenna 234 of the BS110 shown.

[0155] It is worth noting that, Figure 13 This is just one example, and many other examples and configurations of the communication device 1300 are possible.

[0156] Figure 14 The illustration shows operations that may include being configured to perform the techniques disclosed herein (such as...). Figure 10 The communication device 1400 (e.g., a receiver such as a gNB) comprises various components (e.g., corresponding functional unit module components) of the operation shown herein. The communication device 1400 includes a processing system 1402 coupled to a transceiver 1408 (e.g., a transmitter and / or receiver). The transceiver 1408 is configured to transmit and receive signals for the communication device 1400 via an antenna 1410, such as the various signals described herein. The processing system 1402 may be configured to perform processing functions for the communication device 1400, including processing signals received and / or to be transmitted by the communication device 1400.

[0157] Processing system 1402 includes processor 1404 coupled to computer-readable medium / memory 1412 via bus 1406. In some aspects, computer-readable medium / memory 1412 is configured to store instructions (e.g., computer-executable code) that, when executed by processor 1404, cause processor 1404 to perform actions... Figure 10 The operations shown herein or other operations used to perform the various techniques discussed herein.

[0158] In some respects, the computer-readable medium / memory 1412 stores code 1414 for establishing, code 1416 for receiving, and code 1418 for transmitting.

[0159] In some aspects, the establishment code 1414 may include code for establishing a first signaling connection with the IAB node. In some aspects, the receiving code 1416 may include code for receiving from the IAB node a first indication that the IAB node has a second signaling connection with a second IAB donor. In some aspects, the sending code 1418 may include code for sending to the second IAB donor a second indication that the first IAB donor has a first signaling connection with the IAB node.

[0160] In some aspects, processor 1404 has circuitry configured to implement code stored in computer-readable medium / memory 1412. Processor 1404 includes circuitry 1424 for establishing, circuitry 1426 for receiving, and circuitry 1428 for transmitting.

[0161] In some aspects, the circuitry 1424 for establishing a first signaling connection with the IAB node may include circuitry for establishing a first signaling connection with the IAB node. In some aspects, the circuitry 1426 for receiving may include circuitry for receiving from the IAB node a first indication that the IAB node has a second signaling connection with a second IAB donor. In some aspects, the circuitry 1428 for transmitting may include circuitry for transmitting to the second IAB donor a second indication that the first IAB donor has a first signaling connection with the IAB node.

[0162] In some aspects, it can be implemented by one or more functional unit module components. Figure 10 The operations shown herein, as well as other operations described herein, are examples of such operations. For instance, in some aspects, such operations can be implemented by units for establishing, receiving, and transmitting.

[0163] In some aspects, the unit used for establishing includes a processing system, which may include one or more processors, such as in... Figure 2 The BS110 shown includes a receiver processor 238, a transmitter processor 220, a TXMIMO processor 230, and / or a controller / processor 240 and / or Figure 14 The processing system 1402 of the communication device 1400.

[0164] Transceiver 1408 can provide a unit for receiving or transmitting information. It can also transmit information to other components of communication device 1400. Antenna 1410 can correspond to a single antenna or a group of antennas. Transceiver 1408 can provide a unit for transmitting signals generated by other components of communication device 1400.

[0165] The unit for receiving or the unit for obtaining may include in Figure 2The receiver (such as receiver processor 238) or antenna 234 of the BS110 shown. Units for transmitting or for output may be included in... Figure 2 The transmitter (such as transmit processor 220) or antenna 234 of the BS110 shown.

[0166] It is worth noting that, Figure 14 This is just one example, and many other examples and configurations of the communication device 1400 are possible.

[0167] Example Terms

[0168] Examples of implementation methods are described in the following numbered clauses:

[0169] Clause 1: An apparatus for wireless communication via an Integrated Access and Backhaul (IAB) node, comprising: at least one processor; and a memory coupled to the at least one processor, the memory including instructions executable by the at least one processor to cause the apparatus to: establish a first signaling connection with a first IAB donor; establish a second signaling connection with a second IAB donor; and send an indication to the second IAB donor that the IAB node has a first signaling connection with the first IAB donor.

[0170] Clause 2: The apparatus according to Clause 1, wherein the establishment of a first signaling connection with the first IAB donor is due to at least one of the following: migration of the IAB node caused by a handover (HO) procedure; or migration of the IAB node caused by a re-establishment procedure initiated by the IAB node.

[0171] Clause 3: The apparatus according to Clause 1 or 2, wherein the first signaling connection includes a Radio Resource Control (RRC) connection.

[0172] Clause 4: The apparatus according to Clause 3, wherein the establishment of an RRC connection is via at least one of the following: an RRC connection establishment request; an RRC reconfiguration request; an RRC connection re-establishment request; or an RRC connection restoration request.

[0173] Clause 5: The apparatus according to any one of Clauses 1-4, wherein the second signaling connection includes a wired interface connection using at least one of the following: F1 Control Plane (F1-C) protocol; or F1 Application Layer Signaling Protocol (F1-AP).

[0174] Clause 6: The apparatus according to Clause 5, wherein the establishment of the wired interface connection is via the distributed unit (DU) of the first IAB donor.

[0175] Clause 7: The apparatus according to any one of Clauses 1-6, wherein: the initial signaling connection between the IAB node and the second IAB donor established prior to the establishment of the first signaling connection with the first IAB donor is interrupted at least in part due to the migration of the IAB node; and in order to establish the second signaling connection with the second IAB donor, the memory further includes instructions executable by at least one processor to cause the apparatus to: redirect the initial signaling connection on a recovery path toward the first IAB donor.

[0176] Clause 8: The apparatus according to any one of Clauses 1-7, wherein, in order to indicate to the second IAB donor that the IAB node has a first signaling connection with the first IAB donor, the memory further includes instructions executable by at least one processor to cause the apparatus to: send to the second IAB donor a Backhaul Adaptation Protocol (BAP) address assigned to the IAB node by the first IAB donor.

[0177] Clause 9: The apparatus according to any one of Clauses 1-8, wherein, in order to indicate to the second IAB donor that the IAB node has a first signaling connection with the first IAB donor, the memory further includes instructions executable by at least one processor to cause the apparatus to send the identifier of the first IAB donor to the second IAB donor.

[0178] Clause 10: The apparatus according to any one of Clauses 1-9, wherein the memory further comprises instructions executable by at least one processor to cause the apparatus to: send an identifier of a second IAB donor to a first IAB donor, thereby allowing the first IAB donor to indicate to the second IAB donor that the IAB node has a first signaling connection with the first IAB donor.

[0179] Clause 11: An apparatus for wireless communication by a first Integrated Access and Backhaul (IAB) donor, comprising: at least one processor; and a memory coupled to the at least one processor, the memory including instructions executable by the at least one processor to cause the apparatus to: establish a first signaling connection with an IAB node; receive an indication that the IAB node has a second signaling connection with a second IAB donor; and in response to receiving the indication: transmit information related to the IAB node to the second IAB donor; re-establish service between the first IAB donor and the IAB node via the topology of the second IAB donor; or any combination thereof.

[0180] Clause 12: The apparatus according to Clause 11, wherein a first IAB donor receives an instruction from at least one of: an IAB node; or a second IAB donor.

[0181] Clause 13: The apparatus according to Clause 11 or 12, wherein the information relating to the IAB node includes at least one of the following: the context of the mobile terminal (MT) portion of the IAB node; the context of the distributed unit (DU) portion of the IAB node; the context of the child nodes of the IAB node; or the context of the descendant nodes of the IAB node.

[0182] Clause 14: The apparatus according to any one of Clauses 11-13, wherein the memory further includes instructions executable by at least one processor to cause the apparatus to: receive an acknowledgment (ACK) feedback from a second IAB donor in response to sending information associated with the IAB node.

[0183] Clause 15: The apparatus according to any one of Clauses 11-14, wherein, in order to re-establish service between the first IAB donor and the IAB node, the memory further includes instructions executable by at least one processor to cause the apparatus to perform the following operations: exchanging service information with the second IAB donor related to the mobile terminal (MT) portion of the IAB node, the distributed unit (DU) portion of the IAB node, the child nodes of the IAB node, the descendant nodes of the IAB node, or any combination thereof.

[0184] Clause 16: The apparatus according to Clause 15, wherein the service information includes at least one of the following: Quality of Service (QoS) information; QoS mapping information; Backhaul Adaptation Protocol (BAP) configuration assigned to the IAB node; or Internet Protocol (IP) configuration assigned to the IAB node.

[0185] Clause 17: The apparatus according to any one of Clauses 11-16, wherein re-establishing the service between the first IAB donor and the IAB node includes: re-establishing F1 service; or re-establishing non-F1 service.

[0186] Clause 18: An apparatus according to any one of Clauses 11-17, wherein the first signaling connection includes a wired interface connection using at least one of the following: F1 Control Plane (F1-C) protocol; or F1 Application Layer Signaling Protocol (F1-AP).

[0187] Clause 19: The apparatus according to any one of Clauses 11-18, wherein: the initial signaling connection between the first IAB donor and the IAB node established before the establishment of the second signaling connection with the second IAB donor is interrupted at least in part due to the migration of the IAB node; and wherein, in order to establish the first signaling connection with the IAB node, the memory further includes instructions executable by at least one processor to cause the apparatus to: redirect the initial signaling connection on a recovery path toward the IAB node.

[0188] Clause 20: The apparatus described in Clause 19, wherein the migration of the IAB node occurs due to at least one of the following: a handover (HO) process; or a re-establishment process initiated by the IAB node.

[0189] Clause 21: An apparatus for wireless communication by a first Integrated Access and Backhaul (IAB) donor, comprising: at least one processor; and a memory coupled to the at least one processor, the memory including instructions executable by the at least one processor to cause the apparatus to: establish a first signaling connection with an IAB node; receive from the IAB node a first indication that the IAB node has a second signaling connection with a second IAB donor; and send to the second IAB donor a second indication that the first IAB donor has a first signaling connection with an IAB node.

[0190] Clause 22: The apparatus according to Clause 21, wherein the first instruction includes an identifier of the second IAB donor.

[0191] Clause 23: The apparatus according to Clause 21 or 22, in response to sending a second instruction, wherein the memory further includes instructions executable by at least one processor to cause the apparatus to: receive information related to the IAB node from a second IAB donor; exchange service information related to the IAB node with the second IAB donor; or any combination thereof.

[0192] Clause 24: The apparatus according to Clause 23, wherein the information relating to the IAB node includes at least one of the following: the context of the mobile terminal (MT) portion of the IAB node; the context of the distributed unit (DU) portion of the IAB node; the context of the child nodes of the IAB node; or the context of the descendant nodes of the IAB node.

[0193] Clause 25: The apparatus according to Clause 23 or 24, wherein the memory further includes instructions executable by at least one processor to cause the apparatus to: send an acknowledgment (ACK) feedback to a second IAB donor in response to receiving information related to the IAB node.

[0194] Clause 26: The apparatus according to any one of Clauses 23-25, wherein the service information related to the IAB node includes service information related to the mobile terminal (MT) portion of the IAB node, the distributed unit (DU) portion of the IAB node, the child nodes of the IAB node, the descendant nodes of the IAB node, or any combination thereof.

[0195] Clause 27: The apparatus according to Clause 26, wherein the service information includes at least one of the following: Quality of Service (QoS) information; QoS mapping information; Backhaul Adaptation Protocol (BAP) configuration assigned to the IAB node; or Internet Protocol (IP) configuration assigned to the IAB node by the first IAB donor.

[0196] Clause 28: The apparatus according to Clauses 21-27, wherein the first signaling connection includes a Radio Resource Control (RRC) connection.

[0197] Clause 29: The apparatus according to any one of Clauses 21-28, wherein the establishment of the first signaling connection with the IAB node is due to at least one of the following: migration of the IAB node caused by a handover (HO) procedure; or migration of the IAB node caused by a re-establishment procedure initiated by the IAB node.

[0198] Clause 30: A method of wireless communication by a first Integrated Access and Backhaul (IAB) donor, comprising: establishing a first signaling connection with an IAB node; receiving an indication that the IAB node has a second signaling connection with a second IAB donor; and in response to receiving the indication: transmitting information related to the IAB node to the second IAB donor; re-establishing service between the first IAB donor and the IAB node via the topology of the second IAB donor; or any combination thereof.

[0199] Clause 31: A method of wireless communication by a first Integrated Access and Backhaul (IAB) donor, comprising: establishing a first signaling connection with an IAB node; receiving an indication that the IAB node has a second signaling connection with a second IAB donor; and in response to receiving the indication: transmitting information related to the IAB node to the second IAB donor; re-establishing service between the first IAB donor and the IAB node via the topology of the second IAB donor; or any combination thereof.

[0200] Clause 32: A method for wireless communication by a first Integrated Access and Backhaul (IAB) donor, comprising: establishing a first signaling connection with an IAB node; receiving from the IAB node a first indication that the IAB node has a second signaling connection with a second IAB donor; and sending to the second IAB donor a second indication that the first IAB donor has a first signaling connection with the IAB node.

[0201] Clause 33: An apparatus comprising a unit for performing the method described pursuant to any one of Clauses 1-29.

[0202] Clause 34: A non-transitory computer-readable medium comprising: executable instructions that, when executed by one or more processors of a device, cause the device to perform the method described in any one of Clauses 1-29.

[0203] Other considerations

[0204] The techniques described in this article can be used in various wireless communication technologies, such as 3GPP Long Term Evolution (LTE), LTE-Advanced (LTE-A), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), and other networks. The terms "network" and "system" are often used interchangeably.

[0205] CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA) and cdma2000. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers the IS-2000, IS-95, and IS-856 standards. TDMA networks can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, and more. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE and LTE-A are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). cdma2000 and UMB are described in documents from an organization called “3rd Generation Partnership Project 2” (3GPP2).

[0206] The techniques described herein can be used in the aforementioned wireless networks and radio technologies, as well as other wireless networks and radio technologies. For clarity, although this document may use terms commonly associated with 3G, 4G, and / or 5G wireless technologies to describe aspects, aspects of this disclosure can be applied to communication systems based on other generations.

[0207] New Radio (NR) is an emerging wireless communication technology under development, integrated with the 5G Technology Forum (5GTF). NR access (e.g., 5G NR) can support a variety of wireless communication services, such as Enhanced Mobile Broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or higher), Millimeter Wave (mmW) targeting high carrier frequencies (e.g., 25 GHz or higher), Massive Machine Type Communication (mMTC) targeting non-backward compatible MTC technologies, and / or mission-critical services targeting Ultra-Reliable Low Latency Communication (URLLC). These services may include latency and reliability requirements. These services may also have different Transmission Time Intervals (TTIs) to meet corresponding Quality of Service (QoS) requirements. Furthermore, these services can coexist in the same subframe.

[0208] In 3GPP, the term "cell" can refer to the coverage area of ​​a Node B (NB) and / or the NB subsystem serving that coverage area, depending on the context in which the term is used. In NR systems, the term "cell" is used interchangeably with BS, Next Generation Node B (gNB or gNodeB), Access Point (AP), Distributed Unit (DU), Carrier, or Transmitter Receiver Point (TRP). A BS can provide communication coverage for macrocells, picocells, femtocells, and / or other types of cells. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access for UEs with service subscriptions. A picocell can cover a relatively small geographic area and can allow unrestricted access for UEs with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UEs associated with that femtocell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in a residential area, etc.). A BS used for a macrocell may be called a macro BS. A BS used for a picocell may be called a pico BS. A femtocell BS can be referred to as a femtocell BS or a home BS.

[0209] A UE can also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premises equipment (CPE), cellular phone, smartphone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, appliance, medical device or medical apparatus, biometric sensor / device, wearable device (e.g., smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), entertainment device (e.g., music device, video device, satellite radio unit, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, GPS device, or any other suitable device configured to communicate via wireless or wired media. Some UEs can be considered as machine-type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that can communicate with a BS, another device (e.g., a remote device), or some other entity. Wireless nodes can provide connectivity to or to a network, for example, via wired or wireless communication links. Some UEs can be considered Internet of Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.

[0210] Certain wireless networks (e.g., LTE) use Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single-Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, often referred to as tones, frequency bands, etc. Each subcarrier can be modulated using data. Typically, modulation symbols are transmitted using OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing could be 15 kHz and the minimum resource allocation (called a "resource block" (RB)) could be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, the nominal Fast Fourier Transform (FFT) size could be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into multiple subbands. For example, a subband can cover 1.8 MHz (e.g., 6 RBs), and for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, there can be 1, 2, 4, 8, or 16 subbands respectively. In LTE, the basic transmission time interval (TTI) or packet duration is a 1 ms subframe.

[0211] NR can utilize OFDM with CP on both uplink and downlink, and can include support for half-duplex operation using TDD. In NR, subframes are still 1ms, but the basic TTI is called a slot. Subframes contain a variable number of slots (e.g., 1, 2, 4, 8, 16 slots), depending on the subcarrier spacing. NRRB consists of 12 consecutive frequency subcarriers. NR can support a basic subcarrier spacing of 15kHz, and other subcarrier spacings can be defined relative to the basic subcarrier spacing, such as 30kHz, 60kHz, 120kHz, 240kHz, etc. Symbol and slot lengths are proportional to the subcarrier spacing. The CP length also depends on the subcarrier spacing. Beamforming can be supported, and beam direction can be dynamically configured. MIMO transmission using precoding can also be supported. In some examples, MIMO configurations in DL can support up to 8 transmit antennas, with multilayer DL transmissions supporting up to 8 streams and up to 2 streams per UE. In some examples, multilayer transmissions with up to 2 streams per UE can be supported. Up to eight serving cells can be used to support the aggregation of multiple cells.

[0212] In some examples, access to the air interface can be scheduled. A scheduling entity (e.g., a BS) allocates resources for communication between some or all devices and equipment within its service area or cell. The scheduling entity can be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, the subordinate entity uses the resources allocated by the scheduling entity. A base station is not the only entity that can act as a scheduling entity. In some examples, a UE can act as a scheduling entity and can schedule resources for one or more subordinate entities (e.g., one or more other UEs), and other UEs can utilize the resources scheduled by that UE for wireless communication. In some examples, a UE can act as a scheduling entity in a peer-to-peer (P2P) network and / or in a mesh network. In the mesh network example, in addition to communicating with a scheduling entity, UEs can also communicate directly with each other.

[0213] In some examples, two or more dependent entities (e.g., UEs) can communicate with each other using sidelink signals. Real-world applications of such sidelink communication can include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communication, Internet of Things (IoE) communication, IoT communication, mission-critical mesh networks, and / or various other suitable applications. Typically, a sidelink signal can refer to a signal transmitted from one dependent entity (e.g., UE1) to another dependent entity (e.g., UE2) without requiring relaying by a scheduling entity (e.g., UE or BS), even if the scheduling entity may be used for scheduling and / or control purposes. In some examples, licensed spectrum can be used to transmit sidelink signals (unlike wireless LANs that typically use unlicensed spectrum).

[0214] The methods disclosed herein include one or more steps or actions for implementing the methods. The steps and / or actions of the methods may be interchanged without departing from the scope of the claims. That is, unless a specific order of steps or actions is specified, the order and / or use of a particular step and / or action may be modified without departing from the scope of the claims.

[0215] As used herein, the phrase “at least one of” in a list of entries refers to any combination of those entries (including a single member). For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0216] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, deduction, investigation, lookup (e.g., searching in a table, database, or other data structure), assertion, and so on. Moreover, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and so on. Furthermore, "determine" can include parsing, selecting, picking, building, and so on.

[0217] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims, wherein, unless otherwise specified, reference to an element in the singular is not intended to mean “one and only one”, but rather “one or more”. Unless otherwise specified, the term “some” means one or more. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to or will later be known to a person skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. No claim element should be construed in accordance with 35 U.SC §112(f) unless the element is expressly recited using the phrase “unit for…” or, in the case of a method claim, using the phrase “step for…”.

[0218] The various operations described above can be performed by any suitable unit capable of performing the corresponding function. This unit may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors. Generally, in the presence of the operations shown in the accompanying drawings, these operations may have corresponding functional module unit components.

[0219] The various illustrative logic blocks, modules, and circuits described in connection with this disclosure can be implemented or executed using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors and a DSP core, or any other such configuration.

[0220] If implemented in hardware, an exemplary hardware configuration may include a processing system in a wireless node. This processing system can be implemented using a bus architecture. Depending on the specific application and overall design constraints of the processing system, the bus may include any number of interconnect buses and bridges. The bus can link various circuits together, including processors, machine-readable media, and bus interfaces. The bus interface can be used to connect network adapters, etc., to the processing system via the bus. The network adapter can be used to implement signal processing functions of the PHY layer. In the case of a user terminal, a user interface (e.g., keyboard, display, mouse, joystick, etc.) can also be connected to the bus. The bus can also connect various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, etc., which are well known in the art and therefore will not be described further. The processor can be implemented using one or more general-purpose processors and / or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuit systems capable of executing software. Those skilled in the art will recognize how best to implement the functions of the processing system depends on the specific application and the overall design constraints imposed on the system. For example, in some cases, such as Figure 2 The processor shown can be configured to perform operation 600 of Figure 6 and / or operation 700 of Figure 7.

[0221] If implemented in software, functionality can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Software should be broadly interpreted as representing instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or others. Computer-readable media includes both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one location to another. The processor may be responsible for managing the bus and general-purpose processing, which includes executing software modules stored on the machine-readable storage medium. The computer-readable storage medium may be coupled to the processor, allowing the processor to read information from and write information to it. Alternatively, the storage medium may be integrated with the processor. As an example, the machine-readable medium may include a transmission line, a carrier wave modulated by data, and / or a separate computer-readable storage medium containing instructions stored thereon, all accessible to the processor via a bus interface. Alternatively or additionally, the machine-readable medium or any portion thereof may be integrated into the processor, for example, in the case of a cache and / or a general-purpose register file. As an example, examples of machine-readable storage media may include RAM (random access memory), flash memory, ROM (read-only memory), PROM (programmable read-only memory), EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), registers, disks, optical disks, hard disks, or any other suitable storage media, or any combination thereof. Machine-readable media may be embodied in a computer program product.

[0222] Software modules may comprise a single instruction or a number of instructions, and may be distributed across several different code segments, within different programs, and across multiple storage media. Computer-readable media may include several software modules. A software module includes instructions that, when executed by a device such as a processor, cause the processing system to perform various functions. Software modules may include send and receive modules. Each software module may reside in a single storage device or be distributed across multiple storage devices. For example, when a triggering event occurs, a software module may be loaded from a hard disk drive into RAM. During the execution of a software module, the processor may load some of the instructions into a cache to improve access speed. One or more cache lines may then be loaded into a general-purpose register file for processor execution. When the functionality of a software module is referred to below, it will be understood that such functionality is implemented by the processor when executing the instructions from that software module.

[0223] Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, optical fiber, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio, and microwave, then that coaxial cable, optical fiber, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used herein, disks and optical discs include compressed optical discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and... Optical discs, where magnetic disks typically copy data magnetically, use lasers to optically copy data. Therefore, in some aspects, computer-readable media can include non-transitory computer-readable media (e.g., tangible media). Furthermore, in other aspects, computer-readable media can include transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0224] Therefore, a particular aspect may include a computer program product for performing the operations given herein. For example, such a computer program product may include a computer-readable medium having instructions stored (and / or encoded thereon) thereon, which are executable by one or more processors to perform the operations described herein. For example, instructions for performing the operations described herein and shown in FIG6 and / or FIG7.

[0225] Furthermore, it should be understood that modules and / or other suitable units for performing the methods and techniques described herein can be downloaded and / or otherwise obtained by the user terminal and / or base station where applicable. For example, such a device can be coupled to a server to facilitate the delivery of units for performing the methods described herein. Alternatively, the various methods described herein can be provided via storage units (e.g., RAM, ROM, physical storage media such as compressed optical discs (CDs) or floppy disks, etc.), so that the user terminal and / or base station can obtain the various methods when the storage units are coupled to or provided to the device. Furthermore, any other suitable techniques for providing the methods and techniques described herein to the device can be used.

[0226] It should be understood that the claims are not limited to the precise configuration and components described above. Various modifications, alterations, and variations may be made to the arrangement, operation, and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. An apparatus for wireless communication via an Integrated Access and Backhaul (IAB) node, comprising: At least one processor; as well as A memory coupled to the at least one processor, the memory including instructions executable by the at least one processor to cause the device to perform the following operations: Establish the first signaling connection with the first IAB donor; Establish a second signaling connection with the second IAB donor; and Send an indication to the second IAB donor that the IAB node has a first signaling connection with the first IAB donor. In order to indicate to the second IAB donor that the IAB node has a first signaling connection with the first IAB donor, the memory further includes instructions executable by the at least one processor to cause the device to perform the following operations: Send the Backhaul Adaptation Protocol (BAP) address, which was assigned to the IAB node by the first IAB donor, to the second IAB donor.

2. The apparatus according to claim 1, wherein, The establishment of the first signaling connection with the first IAB donor occurs due to at least one of the following: Migration of the IAB node resulting from a handover (HO) process; or The migration of the IAB node caused by the re-establishment process initiated by the IAB node.

3. The apparatus according to claim 1, wherein, The first signaling connection includes a Radio Resource Control (RRC) connection.

4. The apparatus according to claim 3, wherein, The RRC connection is established via at least one of the following: RRC connection establishment request; RRC reconfiguration request; RRC connection re-establishment request; or RRC connection restoration request.

5. The apparatus according to claim 1, wherein, The second signaling connection includes a wired interface connection using at least one of the following: F1 Control Plane (F1-C) protocol; or F1 Application Layer Signaling Protocol (F1-AP).

6. The apparatus according to claim 5, wherein, The wired interface connection is established via the distributed unit (DU) of the first IAB donor.

7. The apparatus according to claim 1, wherein: The initial signaling connection between the IAB node and the second IAB donor, established before the first signaling connection was established with the first IAB donor, was interrupted at least in part due to the migration of the IAB node; as well as In order to establish the second signaling connection with the second IAB donor, the memory further includes instructions executable by the at least one processor to cause the device to redirect the initial signaling connection on a recovery path toward the first IAB donor.

8. The apparatus according to claim 1, wherein, In order to indicate to the second IAB donor that the IAB node has the first signaling connection with the first IAB donor, the memory further includes instructions executable by the at least one processor to cause the device to send the identifier of the first IAB donor to the second IAB donor.

9. The apparatus according to claim 1, wherein, The memory also includes instructions executable by the at least one processor to cause the device to perform the following operations: The identifier of the second IAB donor is sent to the first IAB donor, thereby allowing the first IAB donor to indicate to the second IAB donor that the IAB node has the first signaling connection with the first IAB donor.

10. An apparatus for wireless communication via a first integrated access and backhaul (IAB) donor, comprising: At least one processor; as well as A memory coupled to the at least one processor, the memory including instructions executable by the at least one processor to cause the device to perform the following operations: Establish the first signaling connection with the IAB node; Receive an indication that the IAB node has a second signaling connection with a second IAB donor; and In response to receiving the instruction: Transmit information related to the IAB node to the second IAB donor; Re-establish service between the first IAB donor and the IAB node via the topology of the second IAB donor; or Any combination thereof, The memory further includes instructions executable by the at least one processor to cause the device to perform the following operations: Receive the Backhaul Adaptation Protocol (BAP) address assigned to the IAB node by the second IAB donor from the IAB node.

11. The apparatus according to claim 10, wherein, The first IAB donor receives the instruction from at least one of the following: The IAB node; or The second IAB donor.

12. The apparatus according to claim 10, wherein, Information related to the IAB node includes at least one of the following: The context of the mobile terminal (MT) portion of the IAB node; The context of the Distributed Unit (DU) portion of the IAB node; The context of the child nodes of the IAB node; or The context of the descendant nodes of the IAB node.

13. The apparatus according to claim 10, wherein, The memory also includes instructions executable by the at least one processor to cause the device to perform the following operations: The second IAB donor receives an acknowledgment (ACK) response in response to sending the information associated with the IAB node.

14. The apparatus according to claim 10, wherein, In order to re-establish the service between the first IAB donor and the IAB node, the memory also includes instructions executable by the at least one processor to cause the device to perform the following operations: exchange service information with the second IAB donor related to the mobile terminal (MT) portion of the IAB node, the distributed unit (DU) portion of the IAB node, the child nodes of the IAB node, the descendant nodes of the IAB node, or any combination thereof.

15. The apparatus according to claim 14, wherein, The business information includes at least one of the following: Quality of Service (QoS) information; QoS mapping information; The Backhaul Adaptation Protocol (BAP) configuration assigned to the IAB node; or The Internet Protocol (IP) configuration assigned to the IAB node.

16. The apparatus according to claim 10, wherein, Re-establishing services between the first IAB donor and the IAB node includes: Re-establish F1 business; or Re-establish non-F1 business.

17. The apparatus according to claim 10, wherein, The first signaling connection includes a wired interface connection using at least one of the following: F1 Control Plane (F1-C) protocol; or F1 Application Layer Signaling Protocol (F1-AP).

18. The apparatus according to claim 10, wherein: The initial signaling connection between the first IAB donor and the IAB node, established before the establishment of the second signaling connection with the second IAB donor, was interrupted at least in part due to the migration of the IAB node; as well as In order to establish the first signaling connection with the IAB node, the memory further includes instructions executable by the at least one processor to cause the device to redirect the initial signaling connection on a recovery path toward the IAB node.

19. The apparatus according to claim 18, wherein, The migration of the IAB node occurred due to at least one of the following: Switching (HO) process; or The re-establishment process initiated by the IAB node.

20. An apparatus for wireless communication via a first integrated access and backhaul IAB donor, comprising: At least one processor; as well as A memory coupled to the at least one processor, the memory including instructions executable by the at least one processor to cause the device to perform the following operations: Establish the first signaling connection with the IAB node; Receive a first indication from the IAB node regarding the IAB node having a second signaling connection with a second IAB donor; as well as Send a second indication to the second IAB donor regarding the first IAB donor having the first signaling connection with the IAB node. The memory further includes instructions executable by the at least one processor to cause the device to perform the following operations: Assign Backhaul Adaptation Protocol (BAP) addresses to the IAB nodes.

21. The apparatus according to claim 20, wherein, The first instruction includes the identifier of the second IAB donor.

22. The apparatus of claim 20, in response to sending the second instruction, wherein, The memory also includes instructions executable by the at least one processor to cause the device to perform the following operations: Receive information related to the IAB node from the second IAB donor; Exchange service information related to the IAB node with the second IAB donor; or Any combination thereof.

23. The apparatus according to claim 22, wherein, The information associated with the IAB node includes at least one of the following: The context of the mobile terminal (MT) portion of the IAB node; The context of the Distributed Unit (DU) portion of the IAB node; The context of the child nodes of the IAB node; or The context of the descendant nodes of the IAB node.

24. The apparatus according to claim 22, wherein, The memory also includes instructions executable by the at least one processor to cause the device to perform the following operations: In response to receiving the information related to the IAB node, an acknowledgment (ACK) feedback is sent to the second IAB donor.

25. The apparatus according to claim 22, wherein, The service information related to the IAB node includes service information related to the mobile terminal (MT) part of the IAB node, the distributed unit (DU) part of the IAB node, the child nodes of the IAB node, the descendant nodes of the IAB node, or any combination thereof.

26. The apparatus according to claim 25, wherein, The business information includes at least one of the following: Quality of Service (QoS) information; QoS mapping information; The Backhaul Adaptation Protocol (BAP) configuration assigned to the IAB node; or The Internet Protocol (IP) configuration assigned to the IAB node by the first IAB donor.

27. The apparatus according to claim 20, wherein, The first signaling connection includes a Radio Resource Control (RRC) connection.

28. The apparatus according to claim 20, wherein, The establishment of the first signaling connection with the IAB node occurs due to at least one of the following: Migration of the IAB node resulting from a handover (HO) process; or The migration of the IAB node caused by the re-establishment process initiated by the IAB node.

29. A method for wireless communication by a first integrated access and backhaul IAB donor, comprising: Establish the first signaling connection with the IAB node; Receive an indication that the IAB node has a second signaling connection with a second IAB donor; as well as In response to receiving the instruction: Transmit information related to the IAB node to the second IAB donor; The service is re-established between the first IAB donor and the IAB node via the topology of the second IAB donor; or Any combination thereof, The method further includes: Receive the Backhaul Adaptation Protocol (BAP) address assigned to the IAB node by the second IAB donor from the IAB node.

Images