Integrated routing and backhaul channel management in access and backhaul networks

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a wireless node in a wireless multi-hop network may determine a change in multiplexing capacity related to communications on one or more radio link control (RLC) channels; and transmit information to a central unit that enables the central unit to cause a modification of at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in multiplexing capacity. Numerous other aspects are provided.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 62 / 989,393, filed on March 13, 2020, entitled “ROUTING AND BACKHAUL CHANNEL MANAGEMENT IN AN INTEGRATED ACCESS AND BACKHAUL NETWORK,” and U.S. Non-Provisional Patent Application No. 17 / 249,632, filed on March 8, 2021, entitled “ROUTING AND BACKHAUL CHANNEL MANAGEMENT IN AN INTEGRATED ACCESS AND BACKHAUL NETWORK,” which are hereby expressly incorporated herein by reference.

[0003] Public domain

[0004] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for routing and backhaul channel management in an integrated access and backhaul (IAB) network.

[0005] background

[0006] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0007] A wireless network may include several base stations (BSs) that can support communications for several user equipments (UEs). A UE may communicate with a BS via a downlink and an uplink. A "downlink" (or "forward link") refers to a communication link from a BS to a UE, while an "uplink" (or "reverse link") refers to a communication link from a UE to a BS. As will be described in more detail herein, a BS may be referred to as a Node B, a gNB, an Access Point (AP), a Radio Head, a Transmit Receiving Point (TRP), a New Radio (NR) BS, a 5G Node B, and the like.

[0008] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate at the city, country, region, and even global level. NR (which may also be referred to as 5G) is an enhancement set to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to grow, further improvements to LTE, NR and other radio access technologies are still useful.

[0009] Overview

[0010] In some aspects, a wireless communication method performed by a wireless node in a wireless multi-hop network may include: determining a change in multiplexing capacity related to communications on one or more radio link control (RLC) channels; and transmitting information to a central unit that enables the central unit to cause a modification to at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in multiplexing capacity.

[0011] In some aspects, a wireless communication method performed by a central unit in a wireless multi-hop network may include: receiving information associated with a change in multiplexing capability related to communications on one or more RLC channels from a wireless node; and transmitting to at least one of the wireless node, a parent node of the wireless node, or a child node of the wireless node an indication to perform one or more actions involving modifying at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in multiplexing capability.

[0012] In some aspects, a wireless node in a wireless multi-hop network for wireless communications may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: determine a change in multiplexing capacity related to communications on one or more RLC channels; and transmit information to a central unit that enables the central unit to cause a modification of at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in multiplexing capacity.

[0013] In some aspects, a central unit in a wireless multi-hop network for wireless communications may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: receive information associated with a change in multiplexing capability related to communications on one or more RLC channels from a wireless node; and transmit to at least one of the wireless node, a parent node of the wireless node, or a child node of the wireless node an indication to perform one or more actions involving modifying at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in multiplexing capability.

[0014] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a wireless node in a wireless multi-hop network, may cause the one or more processors to: determine a change in multiplexing capacity related to communications on one or more RLC channels; and transmit information to a central unit that enables the central unit to cause a modification of at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in multiplexing capacity.

[0015] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a central unit in a wireless multi-hop network, may cause the one or more processors to: receive information associated with a change in multiplexing capability related to communications on one or more RLC channels from a wireless node; and transmit an indication to at least one of the wireless node, a parent node of the wireless node, or a child node of the wireless node to perform one or more actions involving modifying at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in multiplexing capability.

[0016] In some aspects, an apparatus in a wireless multi-hop network for wireless communications may include: a device for determining a change in multiplexing capacity associated with communications on one or more RLC channels; and a device for transmitting information to a central unit, the information enabling the central unit to cause a modification to at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in multiplexing capacity.

[0017] In some aspects, an apparatus in a wireless multi-hop network for wireless communications may include: a device for receiving information associated with a change in multiplexing capability related to communications on one or more RLC channels from a wireless node; and a device for transmitting to at least one of the wireless node, a parent node of the wireless node, or a child node of the wireless node an indication to perform one or more actions involving modifying at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in multiplexing capability.

[0018] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as substantially described herein with reference to and as illustrated in the accompanying figures and specification.

[0019] The foregoing has broadly outlined the features and technical advantages of examples according to the present disclosure in an effort to make the following detailed description better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples can be easily used as a basis for modifying or designing other structures for implementing the same purpose as the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description and is not intended to define limitations on the claims.

[0020] Although various aspects are described in the present disclosure by explaining some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip embodiments or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, or devices that enable artificial intelligence). Various aspects can be implemented in chip-level components, module components, non-module components, non-chip-level components, device-level components, or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include several components for analog and digital purposes (e.g., hardware components, including antennas, RF chains, power amplifiers, modulators, buffers, (all) processors, interleavers, adders, or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements, or end-user devices of various sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to understand the above-stated features of the present disclosure in detail, the above briefly summarized content may be described in more detail with reference to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and should not be considered to limit its scope, as the description may allow for other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0023] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0024] Figure 2 is a diagram illustrating an example in which a base station and a UE are in communication in a wireless network according to the present disclosure.

[0025] Figure 3 is a diagram illustrating an example of a radio access network according to the present disclosure.

[0026] Figure 4 is a diagram illustrating an example of an IAB network architecture according to the present disclosure.

[0027] Figure 5A and 5B is a diagram illustrating an example of routing and backhaul channel management in an IAB network according to the present disclosure.

[0028] Figure 6 is a diagram illustrating an example of routing and backhaul channel management in an IAB network according to the present disclosure.

[0029] Figure 7 is a diagram illustrating an example process performed, for example, by a wireless node in a wireless multi-hop network in accordance with the present disclosure.

[0030] Figure 8 is a diagram illustrating an example process performed, for example, by a central unit in a wireless multi-hop network according to the present disclosure.

[0031] Detailed Description

[0032] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be implemented in many different forms and should not be interpreted as being limited to any specific structure or function given throughout the present disclosure. On the contrary, these aspects are provided to make the present disclosure thorough and complete, and it will fully convey the scope of the present disclosure to those skilled in the art. Based on the teachings of this article, those skilled in the art will appreciate that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is independently implemented or implemented in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using supplements or other other structures, functionality, or structures and functionality as the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein can be implemented by one or more elements of the claims.

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

[0034] It should be noted that while various aspects may be described herein using terminology generally associated with 5G or NR radio access technologies (RATs), various aspects of the present disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and / or RATs after 5G (e.g., 6G).

[0035] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (NR) network and / or an LTE network, etc. or may include elements thereof. The wireless network 100 may include several base stations 110 (shown as BS110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE) and may also be referred to as an NR BS, a B node, a gNB, a 5G B node (NB), an access point, a transmit receive point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0036] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown in , BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. The BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "B node", "5G NB", and "cell" may be used interchangeably herein.

[0037] In some aspects, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of the mobile BS. In some aspects, the BSs may be interconnected to each other and / or to one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

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

[0039] The wireless network 100 may be a heterogeneous network including different types of BSs, such as a macro BS, a pico BS, a femto BS, a relay BS, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0040] A network controller 130 may be coupled to a set of BSs and may provide coordination and control of these BSs. The network controller 130 may communicate with each BS via a backhaul. The BSs may also communicate with each other directly or indirectly via a wireless or wired backhaul.

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

[0042] Some UEs may be considered as machine type communication (MTC) UEs, or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide connectivity to or to a network (e.g., a wide area network (such as the Internet) or a cellular network) via, for example, a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as client equipment (CPE). UE120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some aspects, a processor component and a memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0043] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a specific RAT and may operate on one or more frequencies. RAT may also be referred to as radio technology, air interface, etc. Frequency may also be referred to as carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

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

[0045] The devices of the wireless network 100 can communicate using an electromagnetic spectrum, which can be subdivided into various categories, frequency bands, channels, etc. based on frequency or wavelength. For example, the devices of the wireless network 100 can communicate using an operating band having a first frequency range (FR1) and / or can communicate using an operating band having a second frequency range (FR2), the first frequency range (FR1) can span 410 MHz to 7.125 GHz, and the second frequency range (FR2) can span 24.25 GHz to 52.6 GHz. Frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as a "sub-6 GHz" band. Similarly, FR2 is often referred to as a "millimeter wave" band, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as a "millimeter wave" band by the International Telecommunication Union (ITU). Therefore, unless otherwise specifically stated, it should be understood that the terms "sub-6 GHz" and the like, if used herein, may broadly refer to frequencies less than 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise specifically stated, it should be understood that the terms "millimeter wave" and the like, if used herein, may broadly refer to frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz). It is contemplated that the frequencies included in FR1 and FR2 may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0046] As indicated above, Figure 1 are provided as examples. Other examples may differ from those described in Figure 1 Examples described.

[0047] Figure 2 is a diagram illustrating an example 200 of a base station 110 and a UE 120 in communication in a wireless network 100 according to the present disclosure. The base station 110 may be equipped with T antennas 234a through 234t, and the UE 120 may be equipped with R antennas 252a through 252r, where in general T≥1 and R≥1.

[0048] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for the UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.

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

[0050] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0051] Antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include, or may be included within, one or more antenna panels, antenna groups, antenna element sets, and / or antenna arrays, etc. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include one or more antenna elements. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include coplanar antenna element sets and / or non-coplanar antenna element sets. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include antenna elements within a single housing and / or antenna elements within multiple housings. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include antenna elements coupled to one or more transmission and / or reception components (such as Figure 2 One or more antenna elements of one or more components).

[0052] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from a controller / processor 280. The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, where applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 254) of the UE 120 may be included in a modem of the UE 120. In some aspects, the UE 120 includes a transceiver. The transceiver may include any combination of antenna(s) 252, modulator and / or demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (e.g., as described with reference to Figure 6-8 described).

[0053] At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule the UE 120 for downlink and / or uplink communications. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 232) of the base station 110 may be included in a modem of the base station 110. In some aspects, the base station 110 includes a transceiver. The transceiver may include any combination of antenna(s) 234, modulator and / or demodulator 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., as described with reference to Figure 6-8 described).

[0054] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, or Figure 2 Any other components of the UE 120 may perform one or more techniques associated with routing and backhaul channel management in an IAB network, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 7 The process of 700 Figure 8 800, and / or operations of other processes as described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include: a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of base station 110 and / or UE 120, may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example Figure 7 The process of 700 Figure 8 In some aspects, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0055] In some aspects, a wireless node (e.g., an IAB node, a base station 110, a UE 120, etc.) in a wireless multi-hop network may include: means for determining a change in multiplexing capacity related to communications on one or more RLC channels; means for transmitting information to a central unit, the information enabling the central unit to cause modification of at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in multiplexing capacity; etc. In some aspects, such means may include in conjunction with Figure 2 One or more components of the UE 120 described, such as the controller / processor 280, the transmit processor 264, the TX MIMO processor 266, the MOD 254, the antenna 252, the DEMOD 254, the MIMO detector 256, the receive processor 258, etc. In some aspects, such an apparatus may include a combination of Figure 2 One or more components of base station 110 are depicted, such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, and the like.

[0056] In some aspects, a central unit (e.g., an IAB node, a base station 110, etc.) in a wireless multi-hop network may include: means for receiving information associated with a change in multiplexing capability related to communications on one or more RLC channels from a wireless node; means for transmitting to at least one of the wireless node, a parent node of the wireless node, or a child node of the wireless node an indication to perform one or more actions involving modifying at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in multiplexing capability; etc. In some aspects, such means may include in conjunction with Figure 2 One or more components of base station 110 are depicted, such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, and the like.

[0057] although Figure 2 The blocks in the 200 and 210 are illustrated as different components, but the functions described above with respect to these blocks may be implemented with a single hardware, software, or combined component or various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0058] As indicated above, Figure 2 are provided as examples. Other examples may differ from those described in Figure 2 Examples described.

[0059] Figure 3 is a diagram illustrating an example 300 of a radio access network according to the present disclosure.

[0060] As indicated by reference numeral 305, a conventional (e.g., 3G, 4G, LTE, etc.) radio access network may include a plurality of base stations 310 (e.g., access nodes (ANs)), each of which communicates with a core network via a wired backhaul link 315 (e.g., a fiber optic connection). The base stations 310 may communicate with the UEs 320 via access links 325 (which may be wireless links). In some aspects, Figure 3 The base station 310 shown in FIG. 3 may be Figure 1 In some aspects, Figure 3 The UE 320 shown in FIG. Figure 1 UE 120 is shown in FIG.

[0061] As shown by reference numeral 330, the radio access network may include a wireless backhaul network, sometimes referred to as an IAB network. In an IAB network, at least one base station is an anchor base station 335, which communicates with the core network via a wired backhaul link 340 (such as a fiber optic connection). The anchor base station 335 may also be referred to as an IAB donor (or IAB-donor). The IAB network may include one or more non-anchor base stations 345 (sometimes referred to as relay base stations or IAB nodes (or IAB-nodes)). The non-anchor base station 345 may communicate directly or indirectly with the anchor base station 335 via one or more backhaul links 350 (for example, via one or more non-anchor base stations 345) to form a backhaul path to the core network for carrying backhaul traffic. The backhaul link 350 may be a wireless link. The anchor base station(s) 335 or the non-anchor base station(s) 345 may communicate with one or more UEs 355 via an access link 360 (which may be a wireless link for carrying access traffic). In some aspects, Figure 3 The anchor base station 335 and / or the non-anchor base station 345 shown in FIG. Figure 1 In some aspects, Figure 3 The UE 355 shown in FIG. 3 may be Figure 1 UE 120 is shown in FIG.

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

[0063] Figure 3 The configuration of the base station and the UE in FIG. 1 is shown as an example, and other examples are contemplated. For example, Figure 3 The one or more base stations illustrated in the figure may be replaced by one or more UEs communicating via a UE-to-UE access network (e.g., a peer-to-peer network, a device-to-device network, etc.). In this case, an "anchor node" may refer to a UE that communicates directly with a base station (e.g., an anchor base station or a non-anchor base station).

[0064] As indicated above, Figure 3 are provided as examples. Other examples may differ from those described in Figure 3 Examples described.

[0065] Figure 4 is a diagram illustrating an example 400 of an IAB network architecture according to the present disclosure.

[0066] like Figure 4 As shown in , the IAB network may include an IAB donor 405 (shown as IAB-donor 405) connected to the core network via a wired connection (shown as wired backhaul). For example, the Ng interface of the IAB donor 405 may terminate at the core network. Additionally or alternatively, the IAB donor 405 may be connected to one or more devices of the core network that provide a core access and mobility management function (AMF). In some aspects, the IAB donor 405 may include a base station 110, such as described above in conjunction with Figure 3 Anchor base station described. As shown in the figure, the IAB donor 405 may include a central unit (CU), which may perform access node controller (ANC) functions, AMF functions, etc. The CU may configure the distributed units (DUs) of the IAB donor 405 and / or may configure one or more IAB nodes 410 (e.g., MTs and / or DUs of the IAB nodes 410) connected to the core network via the IAB donor 405. Thus, the CU of the IAB donor 405 may control or configure the entire IAB network connected to the core network via the IAB donor 405, such as by using control messages and / or configuration messages (e.g., radio resource control (RRC) configuration messages, F1 application protocol (F1AP) messages, etc.).

[0067] like Figure 4 As further shown in FIG. 4 , the IAB network may include IAB nodes 410 (shown as IAB-node 1, IAB-node 2, and IAB-node 3) connected to the core network via an IAB donor 405. As shown, the IAB node 410 may include a mobile termination (MT) function (sometimes also referred to as a UE function (UEF)), and may include a DU function (sometimes also referred to as an access node function (ANF)). The MT function of an IAB node 410 (e.g., a child node) may be controlled and / or scheduled by another IAB node 410 (e.g., a parent node of the child node) and / or by the IAB donor 405. The DU function of an IAB node 410 (e.g., a parent node) may control and / or schedule other IAB nodes 410 (e.g., a child node of the parent node) and / or UE 120. Thus, the DU may be referred to as a scheduling node or a scheduling component, and the MT may be referred to as a scheduled node or a scheduled component. In some aspects, the IAB donor 405 may include a DU function but not an MT function. That is, the IAB donor 405 may configure, control and / or schedule the communication of the IAB node 410 and / or the UE 120. The UE 120 may include only the MT function and not the DU function. That is, the communication of the UE 120 may be controlled or scheduled by the IAB donor 405 and / or the IAB node 410 (e.g., the parent node of the UE 120).

[0068] When the first node controls and / or schedules communication for the second node (for example, when the first node provides DU functionality for the MT of the second node), the first node may be referred to as the parent node of the second node, and the second node may be referred to as the child node of the first node. The child node of the second node may be referred to as the grandchild node of the first node. Thus, the DU functionality of the parent node may control and / or schedule communication for the child node of the parent node. The parent node may be an IAB donor 405 or an IAB node 410, and the child node may be an IAB node 410 or a UE 120. Communication of the MT functionality of the child node may be controlled and / or scheduled by the parent node of the child node.

[0069] like Figure 4 As further shown in FIG. 4 , the link between UE 120 (e.g., which has only MT functionality but not DU functionality) and IAB donor 405, or between UE 120 and IAB node 410, may be referred to as access link 415. Access link 415 may be a wireless access link that provides UE 120 with radio access to the core network via IAB donor 405 and optionally via one or more IAB nodes 410. Thus, Figure 4 The network illustrated in may be referred to as a multi-hop network or a wireless multi-hop network.

[0070] like Figure 4 As further shown in FIG. 4 , the link between the IAB donor 405 and the IAB node 410 or between two IAB nodes 410 may be referred to as a backhaul link 420. The backhaul link 420 may be a wireless backhaul link that provides radio access to the core network to the IAB node 410 via the IAB donor 405 and optionally via one or more other IAB nodes 410. In the IAB network, network resources (e.g., time resources, frequency resources, space resources, etc.) for wireless communication may be shared between the access link 415 and the backhaul link 420. In some aspects, the backhaul link 420 may be a primary backhaul link or a secondary backhaul link (e.g., a backup backhaul link). In some aspects, if the primary backhaul link fails, becomes congested, becomes overloaded, etc., the secondary backhaul link may be used. For example, if the primary backhaul link between the IAB-node 2 and the IAB-node 1 fails, the backup link 425 between the IAB-node 2 and the IAB-node 3 may be used for backhaul communication. As used herein, a “node” or “wireless node” may refer to an IAB donor 405 or an IAB node 410 .

[0071] The access link 415 may include one or more access radio link control (RLC) channels. The access RLC channels may carry packet data convergence protocol (PDCP) communications (e.g., radio resource control (RRC) communications, data radio bearer communications, etc.) from the UE 120 or the MT function of the IAB node 410 to the IAB donor 405 or the DU function of the IAB node 410.

[0072] The backhaul link 420 may include one or more backhaul RLC channels. The backhaul RLC channel may carry bandwidth allocation protocol (BAP) communications (e.g., backhaul for access traffic) from the MT function of the IAB node 410 to the DU function of the IAB donor 405 or the IAB node 410 (e.g., the corresponding backhaul RLC channel may jump between the route from the access IAB node 410 and the DU function of the IAB donor 405). Accordingly, the radio bearer for the access traffic of the UE 120, or the MT function of the IAB node 410, may be mapped to the backhaul RLC channel, which may be an existing backhaul RLC channel or a backhaul RLC channel established for the radio bearer. As a result, different mappings between the radio bearer and the backhaul RLC channel are possible. For example, a specific backhaul RLC channel may be mapped to a single radio bearer or multiple radio bearers, such as two radio bearers or three radio bearers. Furthermore, the parent node may not have information about a specific mapping between radio bearers and RLC channels used by the child node, and the child node may not have information about a specific mapping between radio bearers and RLC channels used by the parent node.

[0073] As indicated above, Figure 4 are provided as examples. Other examples may differ from those described in Figure 4 Examples described.

[0074] Figure 5A is a diagram illustrating an example 500 of routing and backhaul channel management in an IAB network according to the present disclosure. Figure 5A As shown in FIG. 5 , and through network 505 and network 510, a first IAB node (shown as IAB Node 1) and a second IAB node (shown as IAB Node 2) may communicate on one or more backhaul RLC channels 515. The backhaul RLC channels 515 may be used for backhaul of access traffic for a first UE (shown as UE 1), a second UE (shown as UE 2), and a third UE (shown as UE 3).

[0075] Traffic for the first UE may be associated with a first radio bearer (shown as bearer 1), traffic for the second UE may be associated with a second radio bearer (shown as bearer 2), and traffic for the third UE may be associated with a third radio bearer (shown as bearer 3). As shown in conjunction with network 505, the first, second, and third radio bearers may be mapped to an RLC channel 515 between the first and second IAB nodes. In other words, the mapping between the radio bearers and the RLC channels 515 may be 3:1. As shown in conjunction with network 510, the first radio bearer may be mapped to a first RLC channel 515 between the first and second IAB nodes, the second radio bearer may be mapped to a second RLC channel 515 between the first and second IAB nodes, and the third radio bearer may be mapped to a third RLC channel 515 between the first and second IAB nodes. In other words, the mapping between the radio bearers and the RLC channels 515 may be 1:1.

[0076] Traffic scheduling 520 and traffic scheduling 525 illustrate an example of scheduling a second IAB node by a first IAB node in a network 505 that uses a 3:1 radio bearer to RLC channel 515 mapping (e.g., which is not optimized for the spatial division multiplexing (SDM) capabilities of the second IAB node). Schedules 520 and 525 illustrate that, using a 3:1 radio bearer to RLC channel 515 mapping, the first IAB node may schedule transmissions from the second IAB node to the UE to occur over two time slots. For example, as shown by schedule 520, the second IAB node may be scheduled to receive data for the first UE from the first IAB node in the first and second time slots, to transmit data to the first UE in the third and fourth time slots, to receive data for the second UE from the first IAB node in the fifth and sixth time slots, to transmit data to the second UE in the seventh and eighth time slots, and so on. Such scheduling may reduce spectral efficiency, increase latency, and so on.

[0077] Some techniques and apparatus described herein implement modifying RLC channel mappings based at least in part on the SDM capabilities of the nodes, thereby increasing spectral efficiency, reducing latency, and the like. Traffic schedule 530 and traffic schedule 535 illustrate an example of scheduling a second IAB node by a first IAB node in a network 510 that uses a 1:1 mapping of radio bearers to RLC channels 515 (e.g., which is optimized for the SDM capabilities of the second IAB node). Schedules 530 and 535 illustrate that, when the second IAB node is capable of SDM (spatial division multiplexing) of communications on the first RLC channel 515 (carrying traffic for the first UE) and the second RLC channel 515 (carrying traffic for the second UE), using a 1:1 mapping of radio bearers to RLC channels 515, the first IAB node can schedule transmissions from the second IAB node to the first and second UEs to occur in one time slot. For example, as shown by schedule 530, the second IAB node may be scheduled to receive data for the first UE from the first IAB node in the first time slot and to receive data for the second UE in the second time slot, be scheduled to transmit data to the first UE and the second UE in the third time slot (in an SDM manner), and so on.

[0078] As indicated above, Figure 5A are provided as examples. Other examples may differ from those described in Figure 5A Examples described.

[0079] Figure 5B is a diagram illustrating an example 550 of routing and backhaul channel management in an IAB network according to the present disclosure. Figure 5B A network 505 is shown, as described above. In addition, Figure 5B A network 555 is shown in which a first IAB node and a second IAB node can communicate on multiple backhaul RLC channels 515, which can be used for backhauling access traffic for a first UE, a second UE, and a third UE. As shown by the network 555, a first radio bearer can be mapped to a first RLC channel 515 between the first and second IAB nodes (e.g., 1:1 mapping), and a second and third radio bearer can be mapped to a second RLC channel 515 between the first and second IAB nodes (e.g., 2:1 mapping).

[0080] Traffic scheduling 560 shows an example of scheduling a second IAB node by a first IAB node in a network 505 that uses a 3:1 mapping of radio bearers to RLC channels 515 (e.g., which is not optimized for the frequency duplex (FD) capabilities of the second IAB node). Scheduling 560 shows that, using a 3:1 mapping of radio bearers to RLC channels 515, the first IAB node can schedule the reception and transmission of the second IAB node to occur in alternating time slots (e.g., reception and transmission do not occur in the same time slot). For example, as shown by scheduling 560, the second IAB node can be scheduled to receive data for the first UE from the first IAB node in the first time slot, the second time slot, and the third time slot, be scheduled to transmit data to the first UE in the fourth time slot, the fifth time slot, and the sixth time slot, and so on. Such scheduling may reduce spectral efficiency, increase latency, and so on.

[0081] Some techniques and apparatus described herein implement modifying RLC channel mappings based at least in part on the FD capabilities of the nodes to thereby increase spectral efficiency, reduce latency, and the like. Traffic scheduling 565 illustrates an example of scheduling a second IAB node by a first IAB node in a network 555 that uses a 1:1 mapping (e.g., which is optimized for the FD capabilities of the second IAB node) for a first radio bearer and a first RLC channel 515. Scheduling 565 illustrates that, when the second IAB node is capable of FD (full duplex) for communications on the first RLC channel 515 between the first and second IAB nodes (carrying traffic for the first UE), using a 1:1 mapping for the first radio bearer and the first RLC channel 515, the first IAB node can schedule reception and transmission of the second IAB node to occur in the same time slot. For example, as shown by schedule 565, the second IAB node may be scheduled to receive data for the first UE from the first IAB node in a first time slot, scheduled to receive data for the first UE from the first IAB node in a second time slot and (e.g., concurrently) transmit data for the first UE in the second time slot, scheduled to receive data for the first UE from the first IAB node in a third time slot and (e.g., concurrently) transmit data for the first UE in the third time slot, and so on.

[0082] In addition, some techniques and apparatus described herein enable modifying routing in a wireless multi-hop network based at least in part on the SDM and / or FD capabilities of a node. For example, communications may be routed via nodes capable of SDM and / or FD to thereby increase spectral efficiency, reduce latency, and the like. In some aspects, routing of communications via nodes may be enabled by modifying RLC channel mappings, as described above.

[0083] As indicated above, Figure 5Bare provided as examples. Other examples may differ from those described in Figure 5B Examples described.

[0084] Figure 6 6 is a diagram illustrating an example 600 of routing and backhaul channel management in an IAB network according to the present disclosure. Specifically, Figure 6 Communication between nodes of a wireless multi-hop network is shown. For example, the wireless multi-hop network includes a wireless node 605, a parent node 610 (e.g., which schedules the wireless node 605), a child node 615 (e.g., which is scheduled by the wireless node 605), a UE 120 (e.g., which is served by the child node 615), and a central unit 620. In some aspects, the wireless multi-hop network is an IAB network, as described above. In this example, the wireless node 605, the parent node 610, and the child node 615 can be an IAB node (e.g., an IAB node 410), and the central unit 620 can include a CU function of an IAB donor (e.g., an IAB donor 405).

[0085] In some aspects, the wireless multi-hop network may include additional and / or different than Figure 6 For example, the wireless node 605 may be associated with one or more additional parent nodes, one or more additional child nodes, may serve one or more additional UEs, etc. In some aspects, the child node 615 may be a UE and / or the parent node 610 may be a DU function of an IAB donor.

[0086] like Figure 6 , communications in a wireless multi-hop network may be carried on RLC channels 625. One or more backhaul RLC channels 625 between a wireless node 605 and a parent node 610 may carry backhaul traffic related to communications of a UE 120. One or more backhaul RLC channels 625 between a child node 615 and the wireless node 605 may carry backhaul traffic related to communications of a UE 120. One or more access RLC channels 625 between a UE 120 and a child node 615 may carry communications of a UE 120.

[0087] As indicated by reference numeral 630, the wireless node 605 may determine a change in the multiplexing capability of the wireless node 605. The change in multiplexing capability may involve SDM capability and / or FD capability. In SDM, the wireless node 605 may use multiple beams to concurrently transmit or receive communications with multiple child nodes (e.g., concurrently transmit to a first child node using a first beam and transmit to a second child node using a second beam), or communications with a child node and a parent node 610 (e.g., concurrently receive from a child node using a first beam and receive from a parent node using a second beam). For example, the wireless node 605 may serve one or more UEs 120, and because the UEs 120 move into a particular spatial arrangement, the wireless node 605 may determine that communications for one or more UEs 120 may use SDM. In FD, the wireless node 605 may concurrently transmit and receive communications with multiple child nodes (e.g., concurrently transmit to a first child node and receive from a second child node), or communicate with a child node and a parent node 610 (e.g., concurrently transmit to a child node and receive from a parent node). The change in multiplexing capability may be a gain of multiplexing capability or a loss of multiplexing capability.

[0088] The change in multiplexing capability may relate to communications (e.g., traffic) of the wireless node 605 on one or more access links (e.g., with one or more child nodes, such as child node 615, one or more UEs 120, etc.) and / or backhaul links (e.g., with child node 615, parent node 610, etc.). For example, the wireless node 605 may determine a change in multiplexing capability regarding one or more RLC channels between the wireless node 605 and the parent node 610 (e.g., backhaul RLC channels and / or access RLC channels), one or more RLC channels between the wireless node 605 and the child node 615 (e.g., backhaul RLC channels and / or access RLC channels), and / or one or more RLC channels between the wireless node 605 and one or more UEs 120 (e.g., access RLC channels).

[0089] As indicated by reference numeral 635, the wireless node 605 may transmit, and the central unit 620 may receive, information associated with the state of the wireless node 605. In some aspects, the wireless node 605 may transmit the information via an RRC message, an F1AP message, or the like. In some aspects, the wireless node 605 may transmit the information according to a configuration that provides a time interval for transmitting the information (e.g., the information is transmitted periodically according to the time interval) or a condition for transmitting the information (e.g., the information is transmitted upon determining a change in multiplexing capability). In some aspects, the central unit 620 may transmit the configuration to the wireless node 605 via an RRC message, an F1AP message, or the like. In some aspects, the central unit 620 may transmit a request to transmit the information to the wireless node 605 (e.g., to transmit an indication of multiplexing capability, to transmit a rate at which the wireless node 605 can communicate with one or more sub-nodes, etc.), and the wireless node 605 may transmit the information in response to the request.

[0090] In some aspects, the information may indicate that the wireless node 605 is associated with a multiplexing capability, or is not associated with a multiplexing capability, on one or more links of the wireless node 605. The information may indicate that the multiplexing capability relates to at least one of an SDM capability or an FD capability of the wireless node 605. The information may indicate that the multiplexing capability relates to communications of the wireless node 605 with at least one of a single UE 120 (e.g., single-user MIMO) or multiple UEs 120 (e.g., multi-user MIMO). The information may indicate that the multiplexing capability relates to at least one of a parent link or a child link of the wireless node 605. The information may indicate that the multiplexing capability relates to at least one of a transmit beam or a receive beam used by the wireless node 605. The information may indicate that the multiplexing capability relates to at least one of an uplink communication or a downlink communication of the wireless node 605.

[0091] In some aspects, the information may indicate that the multiplexing capability relates to one or more RLC channels 625. For example, the information may indicate one or more RLC channels (e.g., an ingress RLC channel or an egress RLC channel at the wireless node 605) on which communications may be multiplexed (e.g., if the change in multiplexing capability is a gain) or may no longer be multiplexed (e.g., if the change in multiplexing capability is a loss). As described above, radio bearers associated with communications of UE 120 may be mapped to RLC channels. Accordingly, for example, if the wireless node 605 determines that communications for a first UE 120 associated with a first radio bearer and communications for a second UE 120 associated with a second radio bearer may be multiplexed, the information may indicate the RLC channel(s) mapped to the first radio bearer and the second radio bearer. The RLC channels may be identified in the information by an RLC channel identifier, a logical channel identifier (LCID) mapped to the RLC channel, and the like. In some aspects, the RLC channels may be identified in the information by a pointer (e.g., an index value) mapped to the RLC channel.

[0092] In some aspects, the information may indicate a rate at which the wireless node 605 is able to communicate with one or more child nodes (e.g., child nodes 615, one or more UEs 120, etc.) served by the wireless node 605. The rate may be used to schedule communications for the wireless node 605 (e.g., on a link with the wireless node 605 or on one or more RLC channels with the wireless node 605) so that the rates of incoming and outgoing traffic at the wireless node 605 correspond. The wireless node 605 may indicate the rate by indicating a particular MCS. Additionally or alternatively, the wireless node 605 may indicate the rate by indicating one or more channel quality metrics (e.g., channel quality information) associated with the rate. The channel quality metrics may include self-interference measurements for the wireless node 605.

[0093] The indicated rates may relate to a particular multiplexing pattern of the wireless node 605. For example, the wireless node 605 may indicate a first rate at which the wireless node 605 is able to communicate with a subnode when communications for the subnode are not multiplexed, a second rate at which the wireless node 605 is able to communicate with the subnode when communications for the subnode are multiplexed, and so on. In some aspects, the wireless node 605 may indicate a first rate at which the wireless node 605 is able to communicate with a subnode when communications for the subnode are multiplexed using SDM, a second rate at which the wireless node 605 is able to communicate with the subnode when communications for the subnode are multiplexed using FD, and so on.

[0094] As indicated by reference numeral 640, the central unit 620 may determine one or more modifications for the wireless multi-hop network based at least in part on information transmitted by the wireless node 605. In some aspects, the central unit 620 may determine that routing in the network is to be modified. For example, the central unit 620 may determine that traffic for the UE 120 is to be routed via the wireless node 605, or is not to be routed via the wireless node 605 (e.g., the traffic may be routed via another wireless node that is a child node of the parent node 610 and a parent node of the child node 615). The modification of routing in the network may be based at least in part on a change in the multiplexing capability of the wireless node 605. For example, if the wireless node 605 has acquired multiplexing capability, then certain communications may be routed via the wireless node 605, or if the wireless node 605 has lost multiplexing capability, then certain communications may not be routed via the wireless node 605.

[0095] In some aspects, the central unit 620 may determine that an RLC channel mapping in the network is to be modified. For example, the central unit 620 may determine that a DU function of an IAB donor node, a wireless node 605, a parent node 610, and / or a child node 615 is to establish one or more RLC channels 625, remove one or more RLC channels 625, or modify a mapping of one or more RLC channels 625. The modification of the RLC channel mapping in the network may be based at least in part on a change in the multiplexing capability of the wireless node 605. For example, an RLC channel may have a 1:1 mapping with a radio bearer that is associated with a gain in the multiplexing capability of the wireless node 605 to enable multiplexing of communications on the RLC channel at the wireless node 605.

[0096] As indicated by reference numerals 645a, 645b, and 645c, the central unit 620 may transmit an indication that one or more actions involving modifying routing or RLC channel mapping in a wireless multi-hop network are to be performed, and the wireless node 605, the parent node 610, and / or the child node 615 may receive the indication. That is, the central unit 620 may cause modification of routing or RLC channel mapping in the network by instructing the wireless node 605, the parent node 610 (e.g., an upstream node), and / or the child node (e.g., a downstream node) to perform one or more actions. In some aspects, the central unit 620 may transmit such an indication to the DU function of the IAB donor node. The indication may be included in a message, such as a BAP configuration message.

[0097] The action may be to use a particular routing identifier for communications (e.g., protocol data units (PDUs)) on a particular RLC channel 625 (or another logical channel). For example, an ingress node, such as a DU function of an IAB donor node and / or an access node (e.g., child node 615 as shown) may use (e.g., insert) a routing identifier for PDUs to or from a particular UE 120. In such a case, the indication may identify the routing identifier to be used (e.g., for PDUs for a particular UE 120). In some aspects, the routing identifier may be a BAP routing identifier or a BAP path identifier.

[0098] The action may be to update a routing table (e.g., a BAP routing update). For example, one or more nodes (e.g., intermediate hop nodes, such as wireless node 605, parent node 610, and / or child node 615) may update a routing table so that communications (e.g., PDUs) on a particular ingress link and / or RLC channel 625 are routed to an updated egress link and / or RLC channel 625. That is, the routing table may be updated to forward PDUs associated with a particular routing identifier being used. In some aspects, using a particular routing identifier and / or updating a routing table may be performed in conjunction with one or more actions related to modification of an RLC channel, as described below.

[0099] The action may be to establish one or more RLC channels 625 (e.g., on one or more backhaul links). For example, a parent node (e.g., wireless node 605, parent node 610, IAB donor node, etc.) may establish one or more RLC channels 625 on the DU side of the backhaul link, and a child node (e.g., wireless node 605, parent node 610, child node 615, etc.) may establish one or more corresponding RLC channels 625 on the MT side of the backhaul link. The action may be to remove one or more RLC channels 625. For example, a parent node may remove one or more RLC channels 625 on the DU side of the backhaul link, and a child node may remove one or more corresponding RLC channels 625 on the MT side of the backhaul link. The action may be to modify a mapping of radio bearers to RLC channels 625. For example, a node may remap one or more radio bearers to one or more RLC channels 625.

[0100] In such a case, the indication may also include a configuration for mapping radio bearers to RLC channels. For example, the configuration may indicate one or more radio bearers to be mapped to an established RLC channel 625, one or more radio bearers to be remapped to one or more RLC channels 625 due to removal of an RLC channel 625, one or more radio bearers to be remapped to one or more existing RLC channels 625, and the like.

[0101] In some aspects, the indication may provide an association between one or more actions and a change in the multiplexing capability of the wireless node 605. For example, the indication may provide an association between one or more actions and a gain or loss in the SDM capability or FD capability of the wireless node 605. In some aspects, a node (e.g., a parent node 610, a child node 615, etc.) may prioritize communications with the wireless node 605 based at least in part on the association. For example, the node may modify the scheduling of the wireless node 605, modify the selection of data from the RLC channels 625 for transmission to the wireless node 605, modify soft resource management (e.g., release and / or reclaim soft resources), etc. In this way, spectral efficiency and / or latency may be improved.

[0102] As an example, the parent node 610 may establish a backhaul RLC channel 625 associated with FD capability on a link with the wireless node 605, and determine that communications of the wireless node related to the RLC channel 625 are to be scheduled such that the wireless node 605 receives and transmits concurrently (e.g., soft resources are not released to the wireless node 605). As another example, the parent node 610 may remap a radio bearer associated with SDM capability of the shared RLC channel 625 to a separate RLC channel 625, and determine that communications of the wireless node related to the separate RLC channel 625 are to be scheduled for SDM (e.g., a single time slot is scheduled for the wireless node 605 to transmit communications for the separate RLC channel 625).

[0103] In some aspects, the central unit 620 may transmit, and nodes (e.g., wireless nodes 605, parent nodes 610, child nodes 615, DUs of IAB donors, etc.) may receive resource allocations based at least in part on the change in the multiplexing capability of the wireless node 605. For example, the central unit 620 may transmit resource allocations for one or more RLC channels 625 associated with the change in the multiplexing capability. In some aspects, the resource allocations may allocate hard resources to the nodes. For example, when the wireless node 605 indicates FD capabilities for communication on a link with the parent node 610 and communication on a link with the child node 615, the central unit 620 may allocate hard resources to the wireless node 605, the parent node 610, and the child node 615.

[0104] As indicated above, Figure 6 are provided as examples. Other examples may differ from those described herein. Figure 6 Examples described.

[0105] Figure 77 is a diagram illustrating an example process 700 performed, for example, by a wireless node in a wireless multi-hop network in accordance with the present disclosure. Example process 700 is an example in which a wireless node (e.g., base station 110, UE 120, IAB node 410, wireless node 605, parent node 610, child node 615, etc.) performs operations associated with routing and backhaul channel management in an IAB network.

[0106] like Figure 7 As shown in , in some aspects, process 700 may include determining a change in multiplexing capabilities related to communications on one or more RLC channels (block 710). For example, a wireless node (e.g., using controller / processor 240, controller / processor 280, etc.) may determine a change in multiplexing capabilities related to communications on one or more RLC channels, as described above.

[0107] like Figure 7 As further shown in FIG. 7 , in some aspects, process 700 may include transmitting information to a central unit that enables the central unit to cause modification of at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in multiplexing capacity (block 720). For example, a wireless node (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, etc.) may transmit information to a central unit that enables the central unit to cause modification of at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in multiplexing capacity, as described above.

[0108] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0109] In a first aspect, the information indicates that the change in multiplexing capability is related to one or more of: at least one of the spatial division multiplexing capability or the full-duplex capability of the wireless node; communication with a single UE or at least one of multiple UEs; at least one of the parent link or child link of the wireless node; at least one of the transmit beam or receive beam used by the wireless node; at least one of the uplink communication or downlink communication of the wireless node; or at least one of the one or more RLC channels.

[0110] In a second aspect, alone or in combination with the first aspect, the information is transmitted in response to a request of the central unit.

[0111] In a third aspect, alone or in combination with one or more of the first and second aspects, the information indicates a rate at which the wireless node is able to communicate with one or more child nodes of the wireless node.

[0112] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the rate is related to a specific multiplexing pattern of the wireless node.

[0113] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 700 includes receiving an indication from the central unit that one or more actions are to be performed to thereby modify the at least one of routing or RLC channel mapping.

[0114] In the sixth aspect, alone or in combination with one or more of the first to fifth aspects, the one or more actions include one or more of the following: establishing an RLC channel; removing an RLC channel in the one or more RLC channels; modifying the mapping used for the RLC channel in the one or more RLC channels; using a specific routing identifier for communications on the RLC channel in the one or more RLC channels; or updating a routing table.

[0115] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the central unit is to transmit to a parent node of the wireless node an indication that one or more actions are to be performed to thereby modify at least one of the routing or the RLC channel mapping.

[0116] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the indication indicates an association between the one or more actions and a change in the multiplexing capability.

[0117] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, process 700 includes receiving, from the central unit, a resource allocation based at least in part on the change in multiplexing capabilities.

[0118] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the information is transmitted according to a configuration that provides a time interval for transmitting the information or a condition for transmitting the information.

[0119] although Figure 7 An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 700. Additionally or alternatively, two or more blocks of the process 700 may be executed in parallel.

[0120] Figure 88 is a diagram illustrating an example process 800 performed, for example, by a central unit according to the present disclosure. Example process 800 is an example in which a central unit (e.g., base station 110, CU of IAB donor 405, central unit 620, etc.) performs operations associated with routing and backhaul channel management in an IAB network.

[0121] like Figure 8 As shown in , in some aspects, process 800 may include receiving information associated with a change in multiplexing capability related to communications on one or more RLC channels from a wireless node (block 810). For example, a central unit (e.g., using antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, etc.) may be used to receive information associated with a change in multiplexing capability related to communications on one or more RLC channels from a wireless node, as described above.

[0122] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include transmitting to at least one of a wireless node, a parent node of the wireless node, or a child node of the wireless node an indication to perform one or more actions involving modifying at least one of routing or RLC channel mapping in a wireless multi-hop network based at least in part on a change in multiplexing capability (block 820). For example, a central unit (e.g., using transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, controller / processor 240, memory 242, scheduler 246, etc.) may transmit to at least one of a wireless node, a parent node of the wireless node, or a child node of the wireless node an indication to perform one or more actions involving modifying at least one of routing or RLC channel mapping in a wireless multi-hop network based at least in part on a change in multiplexing capability, as described above.

[0123] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0124] In a first aspect, the information indicates that the change in multiplexing capability is related to one or more of: at least one of the spatial division multiplexing capability or the full-duplex capability of the wireless node; communication with a single UE or at least one of multiple UEs; at least one of the parent link or child link of the wireless node; at least one of the transmit beam or receive beam used by the wireless node; at least one of the uplink communication or downlink communication of the wireless node; or at least one of one or more RLC channels.

[0125] In a second aspect, alone or in combination with the first aspect, process 800 includes transmitting a request to the wireless node to transmit the information.

[0126] In a third aspect, alone or in combination with one or more of the first and second aspects, the information indicates a rate at which the wireless node is able to communicate with one or more child nodes of the wireless node.

[0127] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the rate is related to a specific multiplexing pattern of the wireless node.

[0128] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 800 includes causing modification of at least one of routing or RLC channel mapping in a wireless multi-hop network based at least in part on a change in multiplexing capacity.

[0129] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the one or more actions include one or more of: establishing an RLC channel; removing an RLC channel; modifying a mapping for an RLC channel; using a specific routing identifier for communications on the RLC channel; or updating a routing table.

[0130] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the indication indicates an association between the one or more actions and the change in the multiplexing capability.

[0131] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 800 includes transmitting to at least one of a wireless node, a parent node of the wireless node, or a child node of the wireless node a resource allocation based at least in part on the change in multiplexing capability.

[0132] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the information is received according to a configuration that provides a time interval for transmitting the information or a condition for transmitting the information.

[0133] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 800. Additionally or alternatively, two or more blocks of process 800 may be executed in parallel.

[0134] The following provides an overview of some aspects of the disclosure:

[0135] Aspect 1: A wireless communication method performed by a wireless node in a wireless multi-hop network, comprising: determining a change in multiplexing capacity related to communications on one or more radio link control (RLC) channels; and transmitting information to a central unit, the information enabling the central unit to cause a modification to at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in multiplexing capacity.

[0136] Aspect 2: A method as described in Aspect 1, wherein the information indicates that the change in multiplexing capability is related to one or more of: at least one of the spatial division multiplexing capability or full-duplex capability of the wireless node; communication with a single user equipment (UE) or at least one of multiple UEs; at least one of the parent link or child link of the wireless node; at least one of the transmit beam or receive beam used by the wireless node; at least one of the uplink communication or downlink communication of the wireless node; or at least one of one or more RLC channels.

[0137] Aspect 3: The method as described in any one of aspects 1-2, wherein the information is transmitted in response to a request of the central unit.

[0138] Aspect 4: The method as described in any one of aspects 1-3, wherein the information indicates a rate at which the wireless node can communicate with one or more child nodes of the wireless node.

[0139] Aspect 5: The method as described in Aspect 4, wherein the rate is related to a specific multiplexing mode of the wireless node.

[0140] Aspect 6: The method as described in any one of aspects 1-5 further comprises: receiving an indication from the central unit that one or more actions are to be performed to thereby modify at least one of the route or the RLC channel mapping.

[0141] Aspect 7: A method as described in Aspect 6, wherein the one or more actions include one or more of the following: establishing an RLC channel; removing an RLC channel from the one or more RLC channels; modifying a mapping for an RLC channel from the one or more RLC channels; using a specific routing identifier for communications on an RLC channel from the one or more RLC channels; or updating a routing table.

[0142] Aspect 8: The method as described in any one of Aspects 6-7, wherein the indication indicates an association between the one or more actions and the change in the multiplexing capability.

[0143] Aspect 9: The method as recited in any one of aspects 1-8, further comprising: receiving from the central unit a resource allocation based at least in part on the change in multiplexing capability.

[0144] Aspect 10: The method as described in any one of aspects 1 to 9, wherein the information is transmitted according to a configuration that provides a time interval for transmitting the information or a condition for transmitting the information.

[0145] Aspect 11: A wireless communication method performed by a central unit in a wireless multi-hop network, comprising: receiving information associated with a change in multiplexing capability related to communications on one or more radio link control (RLC) channels from a wireless node; and transmitting to at least one of the wireless node, a parent node of the wireless node, or a child node of the wireless node an indication to perform one or more actions involving modifying at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in multiplexing capability.

[0146] Aspect 12: A method as described in Aspect 11, wherein the information indicates that the change in multiplexing capability is related to one or more of: at least one of the spatial division multiplexing capability or the full-duplex capability of the wireless node; communication with a single user equipment (UE) or at least one of multiple UEs; at least one of the parent link or child link of the wireless node; at least one of the transmit beam or receive beam used by the wireless node; at least one of the uplink communication or downlink communication of the wireless node; or at least one of one or more RLC channels.

[0147] Aspect 13: The method as described in any one of aspects 11-12 further comprises: transmitting a request to the wireless node to transmit the information.

[0148] Aspect 14: The method as described in any of aspects 11-13, wherein the information indicates a rate at which the wireless node can communicate with one or more child nodes of the wireless node.

[0149] Aspect 15: The method as described in Aspect 14, wherein the rate is related to a specific multiplexing mode of the wireless node.

[0150] Aspect 16: The method as described in any of aspects 11-15 further comprises: causing modification of at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in multiplexing capability.

[0151] Aspect 17: A method as described in any of Aspects 11-16, wherein the one or more actions include one or more of the following: establishing an RLC channel; removing an RLC channel; modifying a mapping for an RLC channel; using a specific routing identifier for communications on the RLC channel; or updating a routing table.

[0152] Aspect 18: The method as described in any one of aspects 11-17, wherein the indication indicates an association between the one or more actions and the change in the multiplexing capability.

[0153] Aspect 19: The method as described in any of aspects 11-18 further includes: transmitting the changed resource allocation based at least in part on the multiplexing capability to at least one of the wireless node, the parent node of the wireless node, or the child node of the wireless node.

[0154] Aspect 20: The method as described in any one of aspects 11-19, wherein the information is received according to a configuration of the wireless node that provides a time interval for transmitting the information or a condition for transmitting the information.

[0155] Aspect 21: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as described in one or more of Aspects 1-10.

[0156] Aspect 22: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method as described in one or more of aspects 1-10.

[0157] Aspect 23: An apparatus for wireless communication, comprising at least one means for performing the method as described in one or more of aspects 1-10.

[0158] Aspect 24: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 1-10.

[0159] Aspect 25: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of aspects 1-10.

[0160] Aspect 26: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as described in one or more of Aspects 11-20.

[0161] Aspect 27: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method as described in one or more of aspects 11-20.

[0162] Aspect 28: An apparatus for wireless communication, comprising at least one means for performing the method as described in one or more of aspects 11-20.

[0163] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method as described in one or more of aspects 11-20.

[0164] Aspect 30: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of aspects 11-20.

[0165] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired by practice of the various aspects.

[0166] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. "Software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, etc., whether it is described in software, firmware, middleware, microcode, hardware description language or other terms. As used herein, processors are implemented with hardware, and / or a combination of hardware and software. It will be obvious that the systems and / or methods described herein can be implemented in different forms of hardware, and / or a combination of hardware and software. The actual dedicated control hardware or software code for implementing these systems and / or methods does not limit various aspects. Thus, the operation and behavior of these systems and / or methods are described herein without reference to specific software codes--it is understood that software and hardware can be designed to implement these systems and / or methods based at least in part on the description herein.

[0167] As used herein, satisfying a threshold may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0168] Although specific feature combinations are described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in a manner not specifically described in the claims and / or undisclosed in the specification. Although each dependent claim listed below can be directly subordinate to only one claim, the disclosure of various aspects includes that each dependent claim is combined with each other claim in this group of claims. As used herein, the phrase quoting "at least one of" a column of items refers to any combination of these items, including single members. As an example, "at least one of a, b or c" is intended to cover: a, b, c, ab, ac, bc and abc, and any combination with multiple identical elements (for example, aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc and ccc, or any other sorting of a, b and c).

[0169] Elements, actions or instructions used herein should not be interpreted as key or necessary unless explicitly described as such. Moreover, as used herein, the articles "one" and "a" are intended to include one or more projects, and can be used interchangeably with "one or more". In addition, as used herein, the article "the" is intended to include one or more projects quoted in conjunction with the article "the", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set (set, group)" and "group" are intended to include one or more projects (for example, related items, non-related items, or a combination of related items and non-related items), and can be used interchangeably with "one or more". In the occasion of intending to have only one project, the phrase "only one" or similar language is used. Moreover, as used herein, the terms "have", "contain", "include" etc. are intended to be open terms. In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a sequence is intended to be inclusive and may be used interchangeably with "and / or" unless explicitly stated otherwise (e.g., when used in conjunction with "either of" or "only one of").

Claims

1. A wireless node in a wireless multi-hop network for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors configured to: determining a change in space division multiplexing capability or full duplex capability associated with communications on one or more radio link control (RLC) channels; as well as Information is transmitted to a central unit, the information enabling the central unit to cause a modification of at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in the spatial division multiplexing capability or the full duplex capability.

2. The wireless node of claim 1 , wherein the information indicates that the change in the spatial division multiplexing capability or the full duplex capability is related to one or more of: at least one of the spatial division multiplexing capability or the full duplex capability of the wireless node; communication with a single user equipment (UE) or at least one of a plurality of UEs; at least one of a parent link or a child link of the wireless node; at least one of a transmit beam or a receive beam used by the wireless node; At least one of an uplink communication or a downlink communication of the wireless node; or At least one of the one or more RLC channels.

3. The wireless node of claim 1, wherein the information is transmitted in response to a request by the central unit.

4. The wireless node of claim 1, wherein the information indicates a rate at which the wireless node can communicate with one or more child nodes of the wireless node.

5. The wireless node of claim 4, wherein the rate is related to a specific multiplexing pattern of the wireless node.

6. The wireless node of claim 1 , wherein the one or more processors are further configured to: An indication is received from the central unit that one or more actions are to be performed to thereby modify the at least one of the routing or the RLC channel mapping.

7. The wireless node of claim 6, wherein the one or more actions include one or more of the following: Establishing RLC channel; removing an RLC channel from the one or more RLC channels; modifying a mapping for an RLC channel of the one or more RLC channels; using a particular routing identifier for communications on an RLC channel of the one or more RLC channels; or Update the routing table.

8. The wireless node of claim 6, wherein the indication specifies an association between the one or more actions and the change in the spatial division multiplexing capability or the full duplex capability.

9. The wireless node of claim 1 , wherein the one or more processors are further configured to: A resource allocation based at least in part on the change in the spatial division multiplexing capability or the full duplex capability is received from the central unit.

10. The wireless node of claim 1, wherein the information is transmitted according to a configuration that provides a time interval for transmitting the information or a condition for transmitting the information.

11. A central unit in a wireless multi-hop network for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors configured to: receiving, from a wireless node, information associated with a change in spatial division multiplexing capability or full duplex capability related to communications on one or more radio link control (RLC) channels; as well as An indication is transmitted to at least one of the wireless node, a parent node of the wireless node, or a child node of the wireless node to perform one or more actions involving modifying at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in the spatial division multiplexing capability or the full-duplex capability.

12. The central unit of claim 11, wherein the information indicates that the change in the space division multiplexing capability or the full duplex capability is related to one or more of: at least one of the spatial division multiplexing capability or the full duplex capability of the wireless node; communication with a single user equipment (UE) or at least one of a plurality of UEs; at least one of a parent link or a child link of the wireless node; at least one of a transmit beam or a receive beam used by the wireless node; At least one of an uplink communication or a downlink communication of the wireless node; or At least one of the one or more RLC channels.

13. The central unit of claim 11, wherein the one or more processors are further configured to: A request is transmitted to the wireless node to transmit the information.

14. The central unit of claim 11, wherein the information indicates a rate at which the wireless node can communicate with one or more child nodes of the wireless node.

15. The central unit of claim 14, wherein the rate is related to a specific multiplexing pattern of the wireless nodes.

16. The central unit of claim 11, wherein the one or more processors are further configured to: The at least one of routing or RLC channel mapping in the wireless multi-hop network is caused to be modified based at least in part on the change in the spatial division multiplexing capability or the full-duplex capability.

17. The central unit of claim 11, wherein the one or more actions include one or more of the following: Establishing RLC channel; Remove RLC channel; Modifying the mapping for RLC channels; using a specific routing identifier for communications over the RLC channel; or Update the routing table.

18. The central unit of claim 11, wherein the indication specifies an association between the one or more actions and the change in the spatial division multiplexing capability or the full duplex capability.

19. The central unit of claim 11, wherein the one or more processors are further configured to: A resource allocation based at least in part on the change in the spatial division multiplexing capability or the full duplex capability is transmitted to at least one of the wireless node, a parent node of the wireless node, or a child node of the wireless node.

20. The central unit of claim 11, wherein the information is received according to a configuration of the wireless node that provides a time interval for transmitting the information or a condition for transmitting the information.

21. A wireless communication method performed by a wireless node in a wireless multi-hop network, comprising: determining a change in space division multiplexing capability or full duplex capability associated with communications on one or more radio link control (RLC) channels; as well as Information is transmitted to a central unit, the information enabling the central unit to cause a modification of at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in the spatial division multiplexing capability or the full duplex capability.

22. The method of claim 21, wherein the information indicates that the change in the spatial division multiplexing capability or the full duplex capability is related to one or more of: at least one of the spatial division multiplexing capability or the full duplex capability of the wireless node; communication with a single user equipment (UE) or at least one of a plurality of UEs; at least one of a parent link or a child link of the wireless node; at least one of a transmit beam or a receive beam used by the wireless node; At least one of an uplink communication or a downlink communication of the wireless node; or At least one of the one or more RLC channels.

23. The method of claim 21, wherein the information indicates a rate at which the wireless node can communicate with one or more child nodes of the wireless node.

24. The method of claim 21, further comprising: An indication is received from the central unit that one or more actions are to be performed to thereby modify at least one of the routing or the RLC channel mapping.

25. The method of claim 24, wherein the one or more actions include one or more of the following: Establishing RLC channel; removing an RLC channel from the one or more RLC channels; modifying a mapping for an RLC channel of the one or more RLC channels; using a particular routing identifier for communications on an RLC channel of the one or more RLC channels; or Update the routing table.

26. The method of claim 21, further comprising: A resource allocation based at least in part on the change in multiplexing capabilities is received from the central unit.

27. A wireless communication method performed by a central unit in a wireless multi-hop network, comprising: receiving, from a wireless node, information associated with a change in spatial division multiplexing capability or full duplex capability related to communications on one or more radio link control (RLC) channels; as well as An indication is transmitted to at least one of the wireless node, a parent node of the wireless node, or a child node of the wireless node to perform one or more actions involving modifying at least one of routing or RLC channel mapping in the wireless multi-hop network based at least in part on the change in the spatial division multiplexing capability or the full-duplex capability.

28. The method of claim 27, wherein the information indicates that the change in the spatial division multiplexing capability or the full duplex capability is related to one or more of: at least one of the spatial division multiplexing capability or the full duplex capability of the wireless node; communication with a single user equipment (UE) or at least one of a plurality of UEs; at least one of a parent link or a child link of the wireless node; at least one of a transmit beam or a receive beam used by the wireless node; At least one of an uplink communication or a downlink communication of the wireless node; or At least one of the one or more RLC channels.

29. The method of claim 27, wherein the information indicates a rate at which the wireless node can communicate with one or more child nodes of the wireless node.

30. The method of claim 27, wherein the one or more actions include one or more of the following: Establishing RLC channel; Remove RLC channel; Modifying the mapping for RLC channels; using a specific routing identifier for communications over the RLC channel; or Update the routing table.

Images