Signaling extensions for simultaneous multiplexing in integrated access and backhaul networks - Patents.com

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a parent node in an integrated access and backhaul (IAB) network may transmit signaling to an IAB node having a mobile terminal function (IAB-MT) and a distribution unit (IAB-DU) indicating a set of restricted IAB-DU beams and associating the set of restricted IAB-DU beams with one or more IAB-MT beams, the set of restricted IAB-DU beams being determined based on measurements related to interference caused by IAB-DU and IAB-MT performing simultaneous operation in one or more simultaneous multiplexing modes. Additionally or alternatively, the parent node may perform scheduling for IAB-MT based on signaling received from the IAB node indicating beam-specific parameters related to multiplexing capabilities for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam. Numerous other aspects are provided.

Description

Claiming priority

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This patent application claims priority to U.S. Non-Provisional Patent Application No. 17 / 445,071, entitled "SIGNALING ENHANCEMENTS FOR SIMULTANEOUS MULTIPLEXING IN AN INTEGRATED ACCESS AND BACKHAUL NETWORK," filed on August 13, 2021, which is expressly incorporated by reference into this specification. [Technical field]

[0002] Aspects of the present disclosure relate generally to wireless communications, and in particular to signaling enhancements for simultaneous multiplexing in integrated access and backhaul (IAB) networks. [Background technology]

[0003]

[0003] Wireless communication systems have been widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth or transmit power). 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 extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the 3rd Generation Partnership Project (3GPP).

[0004]

[0004] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that allows different UEs to communicate on a city, national, regional or global scale. New Radio (NR), sometimes referred to as 5G, is a set of extensions to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, lowering costs, improving services, utilizing new spectrum, and better integrating with other open standards using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink and Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access increases, further developments in LTE, NR, and other radio access technologies are still useful.

[0005] In an integrated access and backhaul (IAB) network, an IAB node may include a mobile terminal function (IAB-MT) configured to communicate with a parent node via a parent link, and the IAB node may further include a distributed unit (IAB-DU) configured to communicate with a child node via a child link. For example, the parent link may be a wireless backhaul link used to communicate with a parent IAB node or an IAB donor, and the child link may be a wireless backhaul link used to communicate with a child IAB node, or a wireless access link used to communicate with a served UE. In a typical operation, time division multiplexing (TDM) is used between the parent (backhaul) link and the child link, whereby an IAB node may transmit or receive via either the parent link or the child link (but not both) in a given frame, slot, or other time resource.

[0006]

[0006] In some cases, an IAB node may have an extended duplex capability to support simultaneous operation over a parent link and a child link. For example, the simultaneous operation may include simultaneous half-duplex operation, in which the IAB-MT and IAB-DU transmit simultaneously over the parent link and the child link, respectively, or receive simultaneously over the parent link and the child link, respectively. As another example, the simultaneous operation may include simultaneous full-duplex operation, in which the IAB-MT transmits or receives over the parent link while the IAB-DU receives or transmits over the child link, respectively. In this manner, an IAB node may support one or more simultaneous multiplexing modes to reduce latency, improve spectral efficiency, or enable more efficient resource utilization, among other examples. However, simultaneous operation presents various challenges, including the need to properly configure the IAB-MT and IAB-DU beam pairs with sufficient spatial separation or other beam-specific characteristics to limit inter-link interference or self-interference. Summary of the Invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a parent node. The method may include, for a distributed unit (DU) of an integrated access and backhaul (IAB) node (IAB-DU), determining a set of restricted IAB-DU beams that should not be used by the IAB-DU while a mobile terminal function (MT) (IAB-MT) of the IAB node is using one or more IAB-MT beams, where the determination of the set of restricted IAB-DU beams is based at least in part on one or more measurements related to interference caused by the IAB-DU and IAB-MT performing simultaneous operation in one or more simultaneous multiplexing modes. The method may include transmitting signaling to the IAB node indicating the set of restricted IAB-DU beams and associating the set of restricted IAB-DU beams with one or more IAB-MT beams.

[0008] Some aspects described herein relate to a method of wireless communication performed by a parent node. The method may include receiving, from an IAB node including an IAB-DU and an IAB-MT, signaling indicating one or more beam-specific parameters related to a multiplexing capability for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam. The method may include transmitting, to the IAB node, one or more scheduling parameters for the IAB-MT based at least in part on the signaling indicating the one or more beam-specific parameters.

[0009]

[0009] Some aspects described herein relate to a method of wireless communication performed by an IAB node including an IAB-DU and an IAB-MT. The method may include receiving signaling from a parent node indicating a set of restricted IAB-DU beams that should not be used by the IAB-DU while the IAB-MT is using one or more IAB-MT beams, based at least in part on one or more measurements related to interference caused by the IAB-DU and IAB-MT performing simultaneous operations in one or more simultaneous multiplexing modes, the signaling associating the set of restricted IAB-DU beams with one or more IAB-MT beams. The method may include performing, by the IAB-MT, a first transmission or reception operation using an IAB-MT beam included in the one or more IAB-MT beams associated with the set of restricted IAB-DU beams. The method may include performing, by the IAB-DU, a second transmission or reception operation using an IAB-DU beam not included in the set of restricted IAB-DU beams, simultaneously with the first transmission or reception operation.

[0010]

[0010] Some aspects described herein relate to a method of wireless communication performed by an IAB node including an IAB-DU and an IAB-MT. The method may include transmitting signaling to a parent node indicating one or more beam-specific parameters related to multiplexing capabilities for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam. The method may include receiving, from the parent node, one or more scheduling parameters for the IAB-MT based at least in part on the signaling indicating the one or more beam-specific parameters.

[0011]

[0011] Some aspects described herein relate to a parent node for wireless communication. The parent node may include at least one processor and at least one memory communicatively coupled to the at least one processor and storing processor-readable code. The processor-readable code, when executed by the at least one processor, may be configured to cause the parent node to determine, for a distributed unit of the IAB-DU, a set of restricted IAB-DU beams that should not be used by the IAB-DU while the IAB-MT is using one or more IAB-MT beams, the determination of the set of restricted IAB-DU beams being based at least in part on one or more measurements related to interference caused by the IAB-DU and IAB-MT performing simultaneous operation in one or more simultaneous multiplexing modes. The processor-readable code, when executed by the at least one processor, may be configured to cause the parent node to transmit signaling to the IAB node indicating the set of restricted IAB-DU beams and associating the set of restricted IAB-DU beams with one or more IAB-MT beams.

[0012]

[0012] Some aspects described herein relate to a parent node for wireless communication. The parent node may include at least one processor and at least one memory communicatively coupled to the at least one processor and storing processor-readable code. The processor-readable code, when executed by the at least one processor, may be configured to cause the parent node to receive signaling from an IAB node including an IAB-DU and an IAB-MT indicating one or more beam-specific parameters related to a multiplexing capability for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam. The processor-readable code, when executed by the at least one processor, may be configured to cause the parent node to transmit one or more scheduling parameters for the IAB-MT to the IAB node based at least in part on the signaling indicating the one or more beam-specific parameters.

[0013]

[0013] Some aspects described herein relate to an IAB node for wireless communication. The IAB node may include at least one processor and at least one memory communicatively coupled to the at least one processor and storing processor-readable code. The processor-readable code, when executed by the at least one processor, may be configured to cause the IAB node to receive signaling from a parent node indicating a set of restricted IAB-DU beams that should not be used by the IAB-DU while the IAB-MT is using one or more IAB-MT beams, based at least in part on one or more measurements related to interference caused by the IAB-DU and the IAB-MT performing simultaneous operation in one or more simultaneous multiplexing modes, the signaling associating the set of restricted IAB-DU beams with one or more IAB-MT beams. The processor-readable code, when executed by the at least one processor, may be configured to cause the IAB node to perform a first transmission or reception operation using an IAB-MT beam included in the one or more IAB-MT beams associated with the set of restricted IAB-DU beams. The processor readable code, when executed by the at least one processor, may be configured to cause the IAB node to perform a second transmission or reception operation using an IAB-DU beam that is not included in the set of restricted IAB-DU beams.

[0014]

[0014] Some aspects described herein relate to an IAB node for wireless communication. The IAB node may include at least one processor and at least one memory communicatively coupled to the at least one processor and storing processor-readable code. The processor-readable code, when executed by the at least one processor, may be configured to cause the IAB node to transmit signaling to a parent node indicating one or more beam-specific parameters related to multiplexing capabilities for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam. The processor-readable code, when executed by the at least one processor, may be configured to cause the IAB node to receive, from the parent node, one or more scheduling parameters for the IAB-MT based at least in part on the signaling indicating the one or more beam-specific parameters.

[0015]

[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a parent node. The set of instructions, when executed by one or more processors of the parent node, may cause the parent node to determine, for an IAB-DU, a set of restricted IAB-DU beams that should not be used by the IAB-DU while the IAB-MT is using one or more IAB-MT beams, the determination of the set of restricted IAB-DU beams being based at least in part on one or more measurements related to interference caused by the IAB-DU and IAB-MT performing simultaneous operation in one or more simultaneous multiplexing modes. The set of instructions, when executed by one or more processors of the parent node, may cause the parent node to transmit signaling to the IAB node indicating the set of restricted IAB-DU beams and associating the set of restricted IAB-DU beams with one or more IAB-MT beams.

[0016]

[0016] Certain aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a parent node. The set of instructions, when executed by one or more processors of the parent node, may cause the parent node to receive signaling from an IAB node including an IAB-DU and an IAB-MT indicating one or more beam-specific parameters related to multiplexing capabilities for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam. The set of instructions, when executed by one or more processors of the parent node, may cause the parent node to transmit one or more scheduling parameters for the IAB-MT to the IAB node based at least in part on the signaling indicating the one or more beam-specific parameters.

[0017]

[0017] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by an IAB node. The set of instructions, when executed by one or more processors of the IAB node, may cause the IAB node to receive signaling from a parent node indicating a set of restricted IAB-DU beams that should not be used by the IAB-DU while the IAB-MT is using one or more IAB-MT beams, based at least in part on one or more measurements related to interference caused by an IAB-DU and an IAB-MT performing simultaneous operation in one or more simultaneous multiplexing modes, and the signaling associates the set of restricted IAB-DU beams with one or more IAB-MT beams. The set of instructions, when executed by one or more processors of the IAB node, may cause the IAB node to perform a first transmission or reception operation using an IAB-MT beam included in the one or more IAB-MT beams associated with the set of restricted IAB-DU beams. The set of instructions, when executed by one or more processors of the IAB node, may cause the IAB node to perform a second transmit or receive operation using an IAB-DU beam that is not included in the set of restricted IAB-DU beams.

[0018]

[0018] Certain aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by an IAB node. The set of instructions, when executed by one or more processors of the IAB node, may cause the IAB node to transmit signaling to a parent node indicating one or more beam-specific parameters related to multiplexing capabilities for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam. The set of instructions, when executed by one or more processors of the IAB node, may cause the IAB node to receive, from the parent node, one or more scheduling parameters for the IAB-MT based at least in part on the signaling indicating the one or more beam-specific parameters.

[0019]

[0019] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for determining, for an IAB-DU, a set of restricted IAB-DU beams that should not be used by the IAB-DU while the IAB-MT is using one or more IAB-MT beams, where the determination of the set of restricted IAB-DU beams is based at least in part on one or more measurements related to interference caused by the IAB-DU and IAB-MT performing simultaneous operation in one or more simultaneous multiplexing modes. The apparatus may include means for transmitting signaling to an IAB node indicating the set of restricted IAB-DU beams and associating the set of restricted IAB-DU beams with one or more IAB-MT beams.

[0020]

[0020] Certain aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving signaling from an IAB node including an IAB-DU and an IAB-MT indicating one or more beam-specific parameters related to multiplexing capabilities for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam. The apparatus may include means for transmitting one or more scheduling parameters for the IAB-MT to the IAB node based at least in part on the signaling indicating the one or more beam-specific parameters.

[0021]

[0021] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving signaling from a parent node indicating a set of restricted DU beams that should not be used by a DU while the MT is using one or more MT beams, based at least in part on one or more measurements related to interference caused by a DU and a MT of the apparatus performing simultaneous operation in one or more simultaneous multiplexing modes, the signaling associating the set of restricted DU beams with one or more MT beams. The apparatus may include means for performing a first transmission or reception operation using an MT beam included in the one or more MT beams associated with the set of restricted DU beams. The apparatus may include means for performing a second transmission or reception operation using a DU beam not included in the set of restricted DU beams.

[0022]

[0022] Certain aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting signaling to a parent node indicating one or more beam-specific parameters related to multiplexing capabilities for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam. The apparatus may include means for receiving, from the parent node, one or more scheduling parameters for the IAB-MT based at least in part on the signaling indicating the one or more beam-specific parameters.

[0023]

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

[0024]

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

[0025]

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

[0026] [Figure 1] FIG. 1 illustrates an example of a wireless network in accordance with the present disclosure. [Diagram 2]

[0027] 1 illustrates an example base station in communication with user equipment (UE) in a wireless network in accordance with the present disclosure. [Diagram 3]

[0028] 1 illustrates an example of a radio access network in accordance with the present disclosure. [Figure 4]

[0029] FIG. 1 illustrates an example of an integrated access and backhaul (IAB) network architecture in accordance with the present disclosure. [Diagram 5]

[0030] FIG. 1 illustrates an example of resource types in an IAB network according to the present disclosure. [Figure 6]

[0031] FIG. 1 illustrates an example of a multiplexing mode in an IAB network according to the present disclosure. [Figure 7]

[0032] FIG. 1 illustrates an example relating to signaling extensions for simultaneous multiplexing in an IAB network in accordance with the present disclosure. [Figure 8] FIG. 1 illustrates an example relating to signaling extensions for simultaneous multiplexing in an IAB network in accordance with the present disclosure. [Figure 9]

[0033] 4 is a flowchart illustrating an example process performed, for example, by a parent node in an IAB network, in accordance with the present disclosure. [Figure 10] 4 is a flowchart illustrating an example process performed, for example, by a parent node in an IAB network, in accordance with the present disclosure. [Figure 11]

[0034] 4 is a flowchart illustrating an example process performed, for example, by an IAB node, in accordance with the present disclosure. [Figure 12] 4 is a flowchart illustrating an example process performed, for example, by an IAB node, in accordance with the present disclosure. [Figure 13]

[0035] 1 is a diagram of an example apparatus for wireless communication according to the present disclosure. [Figure 14] 1 is a diagram of an example apparatus for wireless communication according to the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0027]

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

[0028]

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

[0029]

[0038] Various aspects relate generally to signaling that may be used to control one or more multiplexing modes in an integrated access and backhaul (IAB) network, which may include a time division multiplexing (TDM) mode and one or more simultaneous multiplexing modes. Some aspects, more particularly, relate to techniques in which a parent node in an IAB network may determine whether one or more simultaneous operations (e.g., performed in simultaneous half-duplex or simultaneous full-duplex modes) are supported using a beam pair including a mobile terminal (MT) beam and a distributed unit (DU) beam in an IAB node (sometimes referred to herein as an IAB-MT beam and an IAB-DU beam, respectively). For example, in some aspects, the parent node may determine whether the IAB-MT beam and the IAB-DU beam support simultaneous operations based on interference measurements obtained at the parent node, the IAB node, or one or more child nodes of the IAB node. Thus, based on the interference measurements, the parent node may transmit signaling to the IAB node indicating one or more sets of restricted IAB-DU beams that cannot be used in one or more simultaneous operations. Additionally, because the MT function of an IAB node (IAB-MT) and the DU of an IAB node (IAB-DU) may include multiple panels to support multiple IAB-MT or IAB-DU beams that may be associated with different levels of inter-link interference or self-interference, the signaling may associate each respective set of restricted IAB-DU beams with one or more IAB-MT beams (e.g., an IAB-MT beam that experiences or causes strong interference when paired with an IAB-DU beam in an associated set of restricted IAB-DU beams in one or more simultaneous multiplexing modes). Additionally, because different IAB-MT and IAB-DU beam pairs may have different levels of spatial separation, the supported multiplexing modes may vary for different IAB-MT and IAB-DU beam pairs.Thus, the IAB node may send signaling to the parent node indicating one or more beam-specific characteristics associated with the multiplexing capabilities at the IAB node (e.g., supported or unsupported multiplexing modes for each IAB-MT and IAB-DU beam pair, the need to switch between different multiplexing modes, requested or restricted IAB-DU beams to be associated with an IAB-MT beam, or resource utilization constraints for one or more IAB-MT beams, among other examples). In some aspects, the parent node may use the beam-specific characteristics associated with the multiplexing capabilities at the IAB node to make scheduling decisions for the IAB-MT.

[0030]

[0039] Certain aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages: In some examples, the described techniques may be used to indicate to an IAB node an association between a set of restricted beams in an IAB-DU and one or more IAB-MT beams such that different IAB-MT beams may be associated with different sets of restricted IAB-DU beams to mitigate inter-link or self-interference that may occur in different simultaneous multiplexing modes. For example, when an IAB node is communicating on a parent link using an IAB-MT beam associated with a set of restricted IAB-DU beams, the IAB node may be restricted (e.g., prohibited) from simultaneously using any of the IAB-DU beams in the associated set of restricted IAB-DU beams to communicate on a child link. In this manner, an association between a restricted IAB-DU beam and a particular IAB-MT beam may be used to mitigate self-interference that may be experienced at an IAB node, as the case may be, or to mitigate inter-link interference that may otherwise be experienced at a parent node, an IAB node, or a child node of the IAB node.

[0031]

[0040] Further, in some examples, the described techniques may be used by an IAB node to indicate to a parent node or an IAB donor beam-specific characteristics associated with the multiplexing capabilities at the IAB node. In this manner, the parent node may make a scheduling decision for the IAB-MT based on the beam-specific characteristics associated with the multiplexing capabilities at the IAB node, which may include configuring a multiplexing mode that provides sufficient spatial separation to enable simultaneous operation, or configuring time domain resources in a manner that may efficiently utilize the simultaneous multiplexing capabilities of the IAB node or may provide the IAB node with sufficient time resources to schedule child links of the IAB-DU.

[0032]

[0041] FIG. 1 illustrates an example of a wireless network according to the present disclosure. The wireless network 100 may be or include an element of a 5G (e.g., NR) network or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d), one or more user equipment (UE) 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), or other network entities. The base stations 110 are entities that communicate with the UEs 120. The base stations 110 (which may be referred to as BSs) may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, or transmit receiving points (TRPs). Each base station 110 may provide communication coverage for a particular geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of ​​a base station 110 or a base station subsystem serving this coverage area, depending on the context in which the term is used.

[0033]

[0042] A base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 having an association with a femto cell (e.g., a UE 120 in a Closed Subscriber Group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or an in-home base station.

[0034]

[0043] The wireless network 100 may be a heterogeneous network including different types of base stations 110, such as macro base stations, pico base stations, femto base stations, or relay base stations. These different types of base stations 110 may have different transmit power levels, different coverage areas, or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5-40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1-2 watts). In the example shown in FIG. 1, BS 110a may be a macro base station for a macro cell 102a, BS 110b may be a pico base station for a pico cell 102b, and BS 110c may be a femto base station for a femto cell 102c. A base station may support one or more (e.g., three) cells. A network controller 130 may couple to or communicate with a set of base stations 110 and may provide coordination and control of these base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may communicate with each other directly or indirectly via wireless or wireline backhaul communication links.

[0035]

[0044] In some examples, the cells may not necessarily be fixed and the geographic area of ​​the cells may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected to each other or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0036]

[0045] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a base station 110 or a UE 120) and send a transmission of the data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that can relay a transmission for another UE 120. In the example shown in FIG. 1, a BS 110d (e.g., a relay base station) may communicate with a BS 110a (e.g., a macro base station) and a UE 120d to facilitate communication between the BS 110a (e.g., a macro base station) and the UE 120d. A base station 110 that relays communication may be referred to as a relay station, a relay base station, or a relay.

[0037]

[0046] In some aspects, the wireless network 100 may be, include, or be included in a wireless backhaul network, which may be referred to as an integrated access and backhaul (IAB) network. In an IAB network, at least one base station (e.g., base station 110a) may be configured as an anchor base station for communicating with a core network over a wired backhaul link, such as a fiber connection. The anchor base station may also be referred to as an IAB donor (or IAB-donor), a central entity, a central unit (CU), or a donor CU, among other examples. The IAB network may include one or more non-anchor base stations, which may be referred to as a relay base station or an IAB node (or IAB-node). The non-anchor base station (e.g., relay base station 110d) may communicate directly or indirectly (e.g., via one or more non-anchor base stations) with an anchor base station over one or more backhaul links to form a backhaul path to the core network for carrying backhaul traffic. The backhaul link may be a wireless link. The anchor base station or the non-anchor base station may communicate with one or more UEs 120 over an access link, which may be a wireless link for carrying access traffic.

[0038]

[0047] In some aspects, a radio access network (RAN) including an IAB network may utilize millimeter wave technology or directional communications (e.g., beamforming or precoding, among other examples) for communications between base stations 110 or UEs 120 (e.g., between two base stations 110, between two UEs 120, or between a base station 110 and a UE 120). For example, wireless backhaul links between base stations 110 may use millimeter waves to carry information or may be directed to a target base station 110 using beamforming, precoding, or other suitable techniques. Similarly, wireless access links between UEs 120 and base stations 110 may use millimeter waves or may be directed to a target wireless node, such as a UE 120 or a base station 110. In this manner, interlink interference may be reduced.

[0039]

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

[0040]

[0049] Some UEs 120 may be considered as machine type communication (MTC) UEs or evolved or extended machine type communication (eMTC) UEs. MTC UEs or eMTC UEs may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, or a location tag that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. The UE 120 may be included in a housing that stores components of the UE 120, such as a processor component or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0041]

[0050] In general, any amount of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a particular RAT and may operate on one or more frequencies. The RAT may be referred to as a radio technology or air interface. The frequencies may be referred to as carriers or frequency channels. 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.

[0042]

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

[0043]

[0052] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, or channels. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and articles, although portions of FR1 are greater than 6 GHz. A similar nomenclature issue may arise with respect to FR2, which is often referred to (interchangeably) as the "mmWave" band in documents and articles, and is identified as such by the International Telecommunications Union (ITU), despite being distinct from the Extra High Frequency (EHF) band (30 GHz to 300 GHz).

[0044]

[0053] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR research has identified these mid-band frequency operating bands as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands that fall within FR3 may inherit FR1 or FR2 characteristics, thus effectively extending the features of FR1 or FR2 to mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0045]

[0054] With the above examples in mind, it should be understood that unless otherwise specified, the term "sub-6 GHz," as used herein, may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, it should be understood that unless otherwise specified, the term "millimeter wave," as used herein, may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0046]

[0055] In some aspects, a base station, such as base station 110a, may be configured as a parent node in an IAB network and may include a communications manager 140. As described in more detail elsewhere herein, the communications manager 140 may determine, for a distributed unit (DU) (IAB-DU) of the IAB node, a set of restricted IAB-DU beams based at least in part on one or more measurements related to interference caused by simultaneous operation by the IAB-DU and a mobile terminal capability (MT) (IAB-MT) of the IAB node, and transmit signaling to the IAB node indicating the set of restricted IAB-DU beams and associating the set of restricted IAB-DU beams with one or more IAB-MT beams that cannot be used with the set of restricted IAB-DU beams in one or more simultaneous multiplexing modes. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0047]

[0056] In some aspects, a base station, such as base station 110d, may be configured as an IAB node in an IAB network and may include a communications manager 150. As described in more detail elsewhere herein, communications manager 150 may receive signaling from a parent node indicating a set of restricted IAB-DU beams and associating the set of restricted IAB-DU beams with one or more IAB-MT beams that cannot be used with the set of restricted IAB-DU beams in one or more simultaneous multiplexing modes, based at least in part on one or more measurements related to interference caused by simultaneous operation by IAB-DU and IAB-MT, perform a first transmission or reception operation using an IAB-MT beam included in the one or more IAB-MT beams associated with the set of restricted IAB-DU beams, and perform a second transmission or reception operation using an IAB-DU beam not included in the set of restricted IAB-DU beams. Additionally or alternatively, communications manager 150 may perform one or more other operations described herein.

[0048]

[0057] 2 is a diagram illustrating an example base station in communication with a UE in a wireless network in accordance with the present disclosure. The base station may correspond to base station 110 of FIG. 1. Similarly, the UE may correspond to UE 120 of FIG. 1. Base station 110 may be equipped with a set of antennas 234a through 234t, such as T antennas, where T≧1. UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas, where R≧1.

[0049]

[0058] At the base station 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for a UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120. The base station 110 may process (e.g., encode and modulate) data for the UE 120 based at least in part on the MCS(es) selected for the UE 120 and provide data symbols to the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, or higher layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for a reference signal (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and a synchronization signal (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, overhead symbols, or reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), illustrated as modems 232a through 232t. For example, each output symbol stream may be provided to a modulator component (illustrated as MOD) of modem 232. Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may further use a respective modulator component to process (eg, convert to analog, amplify, filter, or upconvert) the output sample stream to obtain a downlink signal.Modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas), illustrated as antennas 234a through 234t.

[0050]

[0059] At the UE 120, a set of antennas 252 (depicted as antennas 252a through 252r) may receive downlink signals from the base station 110 or other base stations 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems), depicted as modems 254a through 254r. For example, each received signal may be provided to a demodulator component (depicted as DEMOD) of the modems 254. Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, or digitize) the received signal to obtain input samples. Each modem 254 may further use a demodulator component to process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modems 254, perform MIMO detection on the received symbols if applicable, and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control and system information to the 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, or a CQI parameter, among other examples. In some examples, one or more components of the UE 120 may be included in a housing.

[0051]

[0060] 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.

[0052]

[0061] One or more antennas (e.g., antennas 234a-t or antennas 252a-r) may include or be contained within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. An antenna panel, antenna group, set of antenna elements, or antenna array may include one or more antenna elements (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled to one or more transmitting or receiving components, such as one or more of the components in FIG.

[0053]

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

[0054]

[0063] At the base station 110, uplink signals from the UE 120 or other UEs may be received by an antenna 234, processed by a modem 232 (e.g., a demodulator component, denoted as DEMOD, of the modem 232), detected by a MIMO detector 236, if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antennas 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to implement aspects of any of the methods described herein.

[0055]

[0064] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, or any other component of FIG. 2 may perform one or more techniques associated with signaling extensions for simultaneous multiplexing in an IAB network, as described in more detail elsewhere herein. In some aspects, a parent node or IAB node described herein is, is included in, or includes one or more components of the base station 110 shown in FIG. 2. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, or any other component of FIG. 2 may perform or direct operations of, for example, process 900 of FIG. 9, process 1000 of FIG. 10, process 1100 of FIG. 11, process 1200 of FIG. 12, or other processes described herein. The memory 242 and the memory 282 may store data and program codes for the base station 110 and the UE 120, respectively. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of base station 110 or UE 120 (e.g., directly or after being compiled, translated, or interpreted), may cause the one or more processors, UE 120, or base station 110 to perform or direct operations of, for example, process 900 of FIG. 9, process 1000 of FIG. 10, process 1100 of FIG. 11, process 1200 of FIG. 12, or other processes described herein. In some examples, executing instructions may include running instructions, translating instructions, compiling instructions, or interpreting instructions, among other examples.

[0056]

[0065] In some aspects, the base station 110 is configured as a parent node and includes means for determining, for a DU of the IAB node (IAB-DU), a set of restricted IAB-DU beams that should not be used by the IAB-DU while a mobile terminal function (MT) (IAB-MT) of the IAB node is using one or more IAB-MT beams, and means for transmitting signaling to the IAB node indicating the set of restricted IAB-DU beams and associating the set of restricted IAB-DU beams with one or more IAB-MT beams, the determination of the set of restricted IAB-DU beams being based at least in part on one or more measurements related to interference caused by the IAB-DU and IAB-MT performing simultaneous operation in one or more simultaneous multiplexing modes. Additionally or alternatively, the parent node includes means for receiving signaling from an IAB node including an IAB-DU and an IAB-MT indicating one or more beam-specific parameters related to multiplexing capabilities for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam, or means for transmitting one or more scheduling parameters for the IAB-MT to the IAB node based at least in part on the signaling indicating the one or more beam-specific parameters. In some aspects, the means for the parent node to perform the operations described herein may include, for example, one or more of the communications manager 140, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antennas 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0057]

[0066] In some aspects, the base station 110 is configured as an IAB node and includes means for receiving signaling from a parent node indicating a set of restricted IAB-DU beams that should not be used by the IAB-DU while the IAB-MT is using one or more IAB-MT beams, based at least in part on one or more measurements related to interference caused by the IAB-DU and IAB-MT of the IAB node performing simultaneous operation in one or more simultaneous multiplexing modes, the signaling associating the set of restricted IAB-DU beams with one or more IAB-MT beams, performing by the IAB-MT a first transmission or reception operation using an IAB-MT beam included in the one or more IAB-MT beams associated with the set of restricted IAB-DU beams, or performing by the IAB-DU a second transmission or reception operation concurrently with the first transmission or reception operation using an IAB-DU beam not included in the set of restricted IAB-DU beams. Additionally or alternatively, the IAB node includes means for transmitting signaling to a parent node indicating one or more beam-specific parameters related to multiplexing capabilities for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam, or means for receiving one or more scheduling parameters for the IAB-MT from the parent node based at least in part on the signaling indicating the one or more beam-specific parameters. In some aspects, the means for the IAB node to perform operations described herein may include, for example, one or more of the communications manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antennas 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0058]

[0067] FIG. 3 is a diagram illustrating an example RAN 300 in accordance with the present disclosure. As shown in FIG. 3, a conventional (e.g., 3G, 4G, or LTE) RAN 305 may include multiple base stations 310 (e.g., access nodes (ANs)), where each base station 310 communicates with a core network via a wired backhaul link 315, such as a fiber connection. The base stations 310 may communicate with a UE 320 via an access link 325, which may be a wireless link. In some aspects, the base station 310 illustrated in FIG. 3 may be the base station 110 illustrated in FIG. 1. In some aspects, the UE 320 illustrated in FIG. 3 may be the UE 120 illustrated in FIG. 1.

[0059]

[0068] As further illustrated in FIG. 3, the RAN may include a wireless backhaul network 330, sometimes referred to herein as an IAB network 330. In the IAB network 330, at least one base station is an anchor base station 335 that communicates with a core network via a wired backhaul link 340, such as a fiber connection. The anchor base station 335 may also be referred to as an IAB donor (or IAB-donor) or a donor central unit (CU), among other examples. The IAB network 330 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 stations 345 may communicate directly or indirectly with the anchor base station 335 via one or more backhaul links 350 (e.g., 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 335 or the non-anchor base station 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, the anchor base station 335 or the non-anchor base station 345 shown in FIG. 3 may be the base station 110 shown in FIG. 1. In some aspects, the UE 355 shown in FIG. 3 may be the UE 120 shown in FIG. 1.

[0060]

[0069] As further shown in FIG. 3, the RAN may include an IAB network 365 that may utilize millimeter wave technology or directional communications (e.g., beamforming) for communication between base stations or UEs (e.g., between two base stations, between two UEs, or between a base station and a UE). For example, a wireless backhaul link 370 between base stations may use millimeter wave signals to carry information or may be directed toward a target base station using beamforming. Similarly, a wireless access link 375 between a UE and a base station may use millimeter wave signals or may be directed toward a target wireless node (e.g., a UE or a base station). In this manner, interlink interference may be reduced.

[0061]

[0070] The configuration of base stations and UEs in Figure 3 is shown as an example, and other examples are contemplated. For example, one or more base stations shown in Figure 3 may be replaced with one or more UEs that communicate via a UE-to-UE access network (e.g., a peer-to-peer network, or a device-to-device network). In this case, an "anchor node" may refer to a UE that is in direct communication with a base station (e.g., an anchor base station or a non-anchor base station).

[0062]

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

[0063]

[0072] As further illustrated in FIG. 4, the IAB network may include IAB nodes 410 (shown as IAB-node 1, IAB-node 2, and IAB-node 3) that connect to a core network via an IAB donor 405. As illustrated, the IAB nodes 410 may include a mobile terminated (MT) function (sometimes referred to as a UE function (UEF)) and a DU function (sometimes referred to as an access node function (ANF)). The MT function of an IAB node 410 (e.g., a child node) may be controlled or scheduled by another IAB node 410 (e.g., a parent node of a child node) or by the IAB donor 405. The DU function of an IAB node 410 (e.g., a parent node) may control or schedule other IAB nodes 410 (e.g., a child node of a parent node) or UE 120. Thus, a DU may be referred to as a scheduling node or scheduling component, and a MT may be referred to as a scheduled node or 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, or schedule communications of the IAB node 410 or the UE 120. The UE 120 may only include MT functionality and not DU functionality. That is, communications of the UE 120 may be controlled or scheduled by the IAB donor 405 or the IAB node 410 (e.g., a parent node of the UE 120).

[0064]

[0073] When a first node controls or schedules communications for a second node (e.g., when the first node provides a DU function for the MT function of the second node), the first node may be referred to as a parent node of the second node, and the second node may be referred to as a child node of the first node. The child node of the second node may be referred to as a grandchild node of the first node. Thus, the DU function of the parent node may control or schedule communications 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. The communications of the MT function of the child node may be controlled or scheduled by the parent node of the child node.

[0065]

[0074] 4, the link between the UE 120 (e.g., having only MT capabilities and no DU capabilities) and the IAB donor 405, or the link between the UE 120 and the IAB node 410, may be referred to as an access link 415. The access link 415 may be a wireless access link that provides the UE 120 with radio access to the core network via the IAB donor 405 and possibly via one or more IAB nodes 410. Thus, the IAB network shown in FIG. 4 may be referred to as a multi-hop network or a wireless multi-hop network.

[0066]

[0075] As further illustrated in FIG. 4, a link between an IAB donor 405 and an IAB node 410, or a link 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 the IAB node 410 with wireless access to the core network via the IAB donor 405 and possibly via one or more other IAB nodes 410. In an IAB network, network resources (e.g., time resources, frequency resources, or spatial resources) 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, the secondary backhaul link may be used if the primary backhaul link fails, becomes congested, or becomes overloaded, among other examples. For example, if the primary backhaul link between IAB-node 2 and IAB-node 1 fails, the backup link 425 between IAB-node 2 and IAB-node 3 may be used for backhaul communications. As used herein, a “node” or a “wireless node” may refer to an IAB donor 405 or an IAB node 410.

[0067]

[0076] FIG. 5 illustrates an example 500 of resource types in an IAB network according to the present disclosure. In an IAB network, time domain resources (sometimes referred to as time resources) may be configured as downlink only, uplink only, flexible, or unavailable (e.g., unavailable). When a time resource is configured as downlink only for a wireless node, the time resource may be available only for downlink communications of the wireless node, but not for uplink communications. Similarly, when a time resource is configured as uplink only for a wireless node, the time resource may be available only for uplink communications of the wireless node, but not for downlink communications. When a time resource is configured as flexible for a wireless node, the time resource may be available for both downlink and uplink communications of the wireless node. When a time resource is configured as unavailable for a wireless node, the time resource may not be used for any communications of the wireless node, with the possible exception of cell-specific signals.

[0068]

[0077] Examples of downlink communications include synchronization signal blocks (SSBs), channel state information reference signals (CSI-RS), physical downlink control channel (PDCCH) communications, or physical downlink shared channel (PDSCH) communications. Examples of uplink communications include physical random access channel (PRACH) communications, physical uplink control channel (PUCCH) communications, physical uplink shared channel (PUSCH) communications, or sounding reference signals (SRS).

[0069]

[0078] A time resource in an IAB network configured as downlink only, uplink only, or flexible may be further configured as a hard resource or a soft resource. When a time resource is configured as a hard resource for a wireless node, the time resource is always available for the wireless node's communications. For example, a hard downlink dedicated time resource is always available for only the wireless node's downlink communications, a hard uplink dedicated time resource is always available for only the wireless node's uplink communications, and a hard flexible time resource is always available for the wireless node's uplink and downlink communications.

[0070]

[0079] When a time resource is configured as a soft resource for a wireless node, the availability of the time resource is conditional and dynamically controlled by the parent node of the wireless node. For example, the parent node may indicate (e.g., explicitly or implicitly) whether the soft time resource is available for communication of the wireless node. Thus, the soft time resource may be in one of two states: a schedulable state (e.g., when the soft time resource is available for scheduling or communication of the wireless node) and a non-schedulable state (e.g., when the soft time resource is not available for scheduling and is not available for communication of the wireless node).

[0071]

[0080] For example, when a parent node of a wireless node indicates that soft downlink dedicated time resources are available, the soft downlink dedicated time resources are available only for the wireless node's downlink communications. Similarly, when a parent node of a wireless node indicates that soft uplink dedicated time resources are available, the soft uplink dedicated time resources are available only for the wireless node's uplink communications. When a parent node of a wireless node indicates that soft flexible time resources are available, the soft flexible time resources are available only for the wireless node's uplink and downlink communications.

[0072]

[0081] As an example, in the first use case 505, a time resource may be configured as a hard resource for a child node and as unavailable for the parent node of the child node. In the first use case 505, the parent node cannot communicate using the time resource, but the child node can schedule communication during or communicate using the time resource. This configuration may reduce interference between the parent node and the child node, or may reduce scheduling conflicts between the parent node and the child node.

[0073]

[0082] As another example, in the second use case 510, the time resource may be configured as unavailable for the child node and may be configured as a hard resource, a soft resource, or an unavailable resource for the parent node (e.g., depending on the network configuration, network conditions, or configuration of the parent node of the parent node). In the second use case 510, the child node cannot schedule communication during the time resource and cannot communicate using the time resource.

[0074]

[0083] As another example, in the third use case 515, a time resource may be configured as a soft resource for a child node and may be configured as a hard resource, a soft resource, or an unavailable resource for a parent node (e.g., depending on the network configuration, network conditions, or configuration of the parent node of the parent node). In the third use case 515, a child node cannot schedule or communicate using a time resource unless it receives an indication (e.g., a release indication) from the parent node (e.g., explicitly or implicitly) that the time resource is available (e.g., released) for use by the child node. If the child node receives such an indication, the child node can schedule a communication during or communicate using the time resource.

[0075]

[0084] FIG. 6 is a diagram illustrating an example 600 of a multiplexing mode in an IAB network according to the present disclosure. As shown in FIG. 6, the example 600 includes communication between an IAB node 610, a parent node 605 (e.g., a parent IAB node or an IAB donor) of the IAB node 610, and one or more child nodes 615 (e.g., a child IAB node or a UE) of the IAB node 610. As further shown, the IAB node 610 may include an MT function (sometimes referred to herein as IAB-MT) that communicates with the parent node 605 via a parent link (e.g., a wireless backhaul link) and a DU (sometimes referred to herein as IAB-DU) that communicates with the child node 615 via one or more respective child links (e.g., a wireless backhaul link when the child node 615 is a child IAB node, or a wireless access link when the child node 615 is a child UE). As shown in FIG. 6, the parent node 605 may be a parent IAB node that includes an MT and a DU. Alternatively, in some cases, the parent node 605 may be an IAB donor that includes a DU for scheduling MTs of the IAB node 610 and a CU for configuring and controlling the entire IAB network that connects to the core network through the parent node 605. In some aspects, the parent node 605, the IAB node 610, and the child node 615 may be included in an IAB network, such as the wireless network 100 or any one or more of the IAB networks 330, 365, 400 described in further detail above.

[0076]

[0085] In general, the IAB node 610 may support at least a time division multiplexing (TDM) mode in which time resources (e.g., frames or slots) are allocated to either a parent link of the IAB node 610 or a child link of the IAB node 610. In other words, when communicating in a TDM mode, the IAB node 610 may either communicate with the parent node 605 via the parent link or communicate with one or more child nodes 615 via one or more child links in a given transmission time interval. For example, in a first TDM operation 620, the parent (backhaul) link is active such that the IAB node 610 may perform transmissions to or receive transmissions from the parent node 605, and the child links are inactive such that no communication occurs over the child links while the IAB node 610 is communicating over the parent link. In another example, in the second TDM operation 625, the child link is active such that the IAB node 610 may transmit to or receive transmissions from the child node 615, and the parent link is inactive such that no communication occurs over the parent link while the IAB node 610 is communicating over the child link.

[0077]

[0086] Additionally, in some cases, the IAB node 610 may have an enhanced duplex capability that supports simultaneous operation over a parent link and a child link (e.g., using spatial division multiplexing (SDM)). For example, the first simultaneous half-duplex operation 630 may be an MT-RX / DU-RX operation in which the IAB-MT receives transmissions from the parent node 605 on the parent link and the IAB-DU simultaneously receives transmissions from one or more child nodes 615 via one or more respective child links. As further illustrated in FIG. 6, the second simultaneous half-duplex operation 632 may be an MT-TX / DU-TX operation in which the IAB-MT simultaneously transmits to the parent node 605 on the parent link and the IAB-DU simultaneously transmits to one or more child nodes 615 via one or more respective child links. As further illustrated in FIG. 6, the first simultaneous full-duplex operation 634 may be an MT-RX / DU-TX operation in which the IAB-MT simultaneously receives transmissions from the parent node 605 on the parent link and the IAB-DU simultaneously transmits to one or more child nodes 615 via one or more respective child links. In another example, the second simultaneous full-duplex operation 636 may be an MT-RX / DU-RX operation in which the IAB-MT transmits on the parent link to the parent node 605 and the IAB-DU simultaneously receives transmissions from one or more child nodes 615 via one or more respective child links.

[0078]

[0087] In this manner, the IAB node 610 may support one or more simultaneous multiplexing modes to reduce latency, improve spectral efficiency, or enable more efficient resource utilization, among other examples. For example, utilizing simultaneous half-duplex or simultaneous full-duplex communication may reduce latency by allowing the IAB node 610 to transmit or receive downlink signals in uplink-only slots or transmit or receive uplink signals in downlink-only slots. Additionally, the simultaneous multiplexing mode may improve spectral efficiency or throughput or enable more efficient resource utilization by simultaneously utilizing time resources to communicate over parent and child links. However, the simultaneous multiplexing mode presents various challenges, including the need to properly configure IAB-MT and IAB-DU beam pairs with sufficient spatial separation or other beam-specific characteristics to limit inter-link interference or self-interference. For example, in the simultaneous multiplexing mode, the IAB node 610 may be restricted from using some IAB-MT or IAB-DU beams or beam pairs that may result in inter-link interference or self-interference. For example, in some cases, a beam pair including an IAB-MT beam and an IAB-DU beam may not provide sufficient spatial separation if the IAB-MT beam and the IAB-DU beam cause inter-link or self-interference that may occur when the IAB-MT beam and the IAB-DU beam are associated with the same antenna panel or when a signal transmitted via the IAB-MT beam interferes with reception of a signal transmitted via the IAB-DU beam, or vice versa. Thus, whether the IAB node 610 can use an extended duplex mode, such as simultaneous half-duplex or simultaneous full-duplex, may depend on selecting and properly configuring or scheduling communications via an IAB-MT beam, an IAB-DU beam, or an IAB-MT and IAB-DU beam pair to reduce or minimize inter-link or self-interference via spatial separation or to efficiently utilize time and frequency resources.

[0079]

[0088] Various aspects relate generally to signaling that may be used to control one or more multiplexing modes in an IAB network, which may include a TDM mode and one or more simultaneous multiplexing modes. Some aspects relate more particularly to techniques in which a parent node in an IAB network may determine whether one or more simultaneous operations (e.g., performed in simultaneous half-duplex or simultaneous full-duplex modes) are supported using a beam pair including an MT beam and a DU beam in an IAB node (sometimes referred to herein as an IAB-MT beam and an IAB-DU beam, respectively). For example, the parent node may determine whether the IAB-MT beam and the IAB-DU beam support simultaneous operations based on interference measurements obtained at the parent node, the IAB node, or one or more child nodes of the IAB node. Thus, based on the interference measurements, the parent node may transmit signaling to the IAB node indicating one or more sets of restricted IAB-DU beams that cannot be used in one or more simultaneous operations. Additionally, because the IAB-MT and IAB-DU can include multiple panels to support multiple IAB-MT or IAB-DU beams that may be associated with different levels of inter-link interference or self-interference, the signaling may associate each respective set of restricted IAB-DU beams with one or more IAB-MT beams (e.g., an IAB-MT beam that experiences or causes strong interference when paired with an IAB-DU beam in an associated set of restricted IAB-DU beams in one or more simultaneous multiplexing modes). Additionally, because different IAB-MT and IAB-DU beam pairs may have different levels of spatial separation, the supported multiplexing modes may vary for different IAB-MT and IAB-DU beam pairs.Thus, the IAB node may send signaling to the parent node indicating one or more beam-specific characteristics associated with the multiplexing capabilities at the IAB node (e.g., supported or unsupported multiplexing modes for each IAB-MT and IAB-DU beam pair, the need to switch between different multiplexing modes, requested or restricted IAB-DU beams to be associated with an IAB-MT beam, or resource utilization constraints for one or more IAB-MT beams, among other examples). In some aspects, the parent node may use the beam-specific characteristics associated with the multiplexing capabilities at the IAB node to make scheduling decisions for the IAB-MT.

[0080]

[0089] Certain aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages: In some examples, the described techniques may be used to indicate to an IAB node an association between a set of restricted beams in an IAB-DU and one or more IAB-MT beams such that different IAB-MT beams may be associated with different sets of restricted IAB-DU beams to mitigate inter-link or self-interference that may occur in different simultaneous multiplexing modes. For example, when an IAB node is communicating on a parent link using an IAB-MT beam associated with a set of restricted IAB-DU beams, the IAB node may be restricted (e.g., prohibited) from simultaneously using any of the IAB-DU beams in the associated set of restricted IAB-DU beams to communicate on a child link. In this manner, an association between a restricted IAB-DU beam and a particular IAB-MT beam may be used to mitigate self-interference that may be experienced at an IAB node, as the case may be, or to mitigate inter-link interference that may otherwise be experienced at a parent node, an IAB node, or a child node of the IAB node.

[0081]

[0090] Further, in some examples, the described techniques may be used by an IAB node to indicate to a parent node or an IAB donor beam-specific characteristics associated with the multiplexing capabilities at the IAB node. In this manner, the parent node may make a scheduling decision for the IAB-MT based on the beam-specific characteristics associated with the multiplexing capabilities at the IAB node, which may include configuring a multiplexing mode that provides sufficient spatial separation to enable simultaneous operation, or configuring time domain resources in a manner that may efficiently utilize the simultaneous multiplexing capabilities of the IAB node or may provide the IAB node with sufficient time resources to schedule child links of the IAB-DU.

[0082]

[0091] 7 is a diagram illustrating an example 700 related to signaling enhancements for simultaneous multiplexing in an IAB network according to the present disclosure. As shown in FIG. 7, the example 700 includes communication between an IAB node 710, a parent node 705 (e.g., a parent IAB node or an IAB donor) of the IAB node 710, and one or more child nodes 715 (e.g., a child IAB node or a UE) of the IAB node 710. As further shown, the IAB node 710 may include an IAB-MT that communicates with the parent node 705 via a parent link, and an IAB-DU that communicates with the child node 715 via one or more respective child links (e.g., a wireless backhaul link when the child node 715 is a child IAB node, or a wireless access link when the child node 715 is a child UE). In some aspects, the parent node 705 may be a parent IAB node including an MT and a DU, or the parent node 705 may be an IAB donor including a DU for scheduling IAB-MTs and a CU for configuring and controlling the entire IAB network that connects to a core network through the parent node 705. In some aspects, the parent node 705, the IAB node 710, and the child node 715 may be included in an IAB network, such as any one or more of the wireless network 100 or the IAB networks 330, 365, 400 described in further detail above.

[0083]

[0092] In some aspects, the IAB node 710 may support communication on parent and child links using a TDM configuration, where either the parent or child link is active in any given transmission time interval. For example, as described in further detail above with reference to FIG. 5, the parent node 705 may configure a semi-static time division duplex (TDD) pattern in which each respective time resource is configured as a downlink dedicated resource, an uplink dedicated resource, a flexible resource, or an unavailable resource, and further, each downlink dedicated resource, uplink dedicated resource, or flexible resource is configured as a hard resource or a soft resource. Additionally or alternatively, the parent node 705 may provide dynamic instructions to configure the parent or child links of the IAB node 710 such that only one link is active in a given transmission time interval. Furthermore, in some cases, the IAB node 710 may support one or more simultaneous multiplexing modes, as described above with reference to FIG. 6. Generally, when an IAB node 710 communicates in a simultaneous multiplexing mode, a parent link of the IAB node 710 and a child link of the IAB node 710 may be active in the same transmission time interval, which may result in inter-link interference or self-interference.

[0084]

[0093] For example, in a first simultaneous multiplexing operation 720 (e.g., in an MT-RX / DU-RX simultaneous half-duplex mode), the IAB node 710 may receive a desired transmission from a parent node 705 on a parent link via an IAB-MT beam and may simultaneously receive a desired transmission from one or more child nodes 715 on one or more respective child links via one or more IAB-DU beams. However, in some cases, a desired transmission via an IAB-MT beam may be received at the IAB-DU, which may cause inter-link interference with respect to reception of the desired transmission via the IAB-DU beam. Additionally, as shown, a desired transmission via an IAB-DU beam may be received at the IAB-MT, which may cause inter-link interference with respect to reception of the desired transmission via the IAB-MT beam. In another example, in a second simultaneous multiplexing operation 722 (e.g., in MT-TX / DU-TX simultaneous half-duplex mode), the IAB node 710 may perform a desired transmission on a parent link via an IAB-MT beam to a parent node 705 and may simultaneously perform a desired transmission on one or more respective child links via one or more IAB-DU beams to one or more child nodes 715. In such a case, the desired transmission via the IAB-MT beam may be received at one or more of the child nodes 715, which may cause inter-link interference with respect to reception of the desired transmission via the IAB-DU beam. Additionally, as shown, the desired transmission via the IAB-DU beam may be received at the parent node 705, which may cause inter-link interference with respect to reception of the desired transmission via the IAB-MT beam.

[0085]

[0094] Furthermore, if the IAB node 710 supports a full-duplex mode in which the IAB node 710 transmits and receives in the same transmission time interval, another problem that may arise is self-interference caused by simultaneous transmission and reception. For example, self-interference may occur when a transmit signal leaks into a receive port (e.g., leaks from a first panel configured for transmission to a second panel configured for reception) or when objects in the environment surrounding the IAB node 710 reflect the transmit signal back to the receive port (e.g., causing a clutter echo effect). For example, in a third simultaneous multiplexing operation 724 (e.g., in an MT-RX / DU-TX full-duplex mode), the IAB node 710 may receive a desired transmission from a parent node 705 on a parent link via an IAB-MT beam and may simultaneously perform a desired transmission to one or more child nodes 715 on one or more respective child links via one or more IAB-DU beams. In such a case, the desired transmission via the IAB-MT beam may be received at one or more of the child nodes 715, which may cause inter-link interference with respect to reception of the desired transmission via the IAB-DU beam, and the desired transmission via the IAB-DU beam may be received at the IAB-MT, which may cause self-link interference with respect to reception of the desired transmission via the IAB-MT beam. In another example, in a fourth simultaneous multiplexing operation 726 (e.g., in MT-TX / DU-RX full duplex mode), the IAB node 710 may receive a desired transmission from one or more child nodes 715 on a child link via one or more IAB-DU beams and may simultaneously perform a desired transmission to the parent node 705 on a parent link via the IAB-MT beam. In such a case, the desired transmission via the IAB-DU beam may be received at the parent node 705, which may cause inter-link interference with respect to reception of the desired transmission via the IAB-MT beam, and the desired transmission via the IAB-MT beam may be received at the IAB-DU, which may cause self-link interference with respect to reception of the desired transmission via the IAB-DU beam.

[0086]

[0095] Thus, in some aspects, in operation 730, the parent node 705 may transmit signaling to the IAB node 710 indicating a set of one or more IAB-DU restricted beams, which may generally refer to a set of beams that the IAB-DU is restricted from using to communicate with the child node 715 in one or more simultaneous multiplexing modes. For example, in some aspects, the parent node 705 may determine whether an IAB-MT beam and an IAB-DU beam may be paired with each other in a particular simultaneous operation (e.g., MT-RX / DU-RX simultaneous multiplexing mode 720, MT-TX / DU-TX simultaneous multiplexing mode 722, MT-RX / DU-TX simultaneous multiplexing mode 724, or MT-TX / DU-RX simultaneous multiplexing mode 726). In some aspects, the parent node 705 may determine whether an IAB-MT beam and an IAB-DU beam may be paired in simultaneous operation based generally on interference measurements at one or more of the parent node 705, the IAB node 710, or the child node 715. For example, in some aspects, the parent node 705 may perform interference measurements related to link-to-link interference caused by a desired transmission via an IAB-DU beam, may receive measurement reports including interference measurements obtained at an IAB node 710 related to link-to-link interference or self-interference caused by a desired transmission via an IAB-MT or IAB-DU beam, or may receive measurement reports including interference measurements obtained at a child node 705 related to link-to-link interference caused by a desired transmission via an IAB-MT beam.

[0087]

[0096] In some aspects, based on interference measurements performed at parent node 705, IAB node 710, or child node 715, parent node 705 may determine whether a given IAB-MT beam and an IAB-DU beam may be paired in simultaneous operation (e.g., when simultaneous operation via an IAB-MT beam and an IAB-DU beam causes inter-link interference or self-interference that meets a threshold) and may determine a set of restricted IAB-DU beams accordingly (e.g., an IAB-DU beam may be restricted when simultaneous operation via an IAB-DU beam and one or more IAB-MT beams causes inter-link interference or self-interference that cannot meet a threshold). In other words, a restricted IAB-DU beam may experience or cause inter-link interference or self-interference that cannot meet a threshold (e.g., exceeds a threshold) when paired with one or more IAB-MT beams in a simultaneous multiplexing mode. Furthermore, in some cases, (e.g., when the IAB-MT includes multiple spatially separated antenna panels) the IAB-MT may support multiple serving beams (e.g., different IAB-MT beams) over the parent link. Thus, in such cases, an IAB-DU beam may cause interference that may not meet a threshold or may be unsuitable to be paired with a first IAB-MT beam, while an IAB-DU beam may cause interference that meets a threshold or may be suitable to be paired with a second IAB-MT beam. In other words, whether an IAB-DU beam may be paired with an IAB-MT beam may be a beam-specific decision, whereby signaling indicating a set of restricted IAB-DU beams that cannot be used in simultaneous operation may be associated with one or more IAB-MT beams.For example, in some aspects, the signaling may include one or more fields indicating one or more IAB-MT beams associated with a particular set of restricted IAB-DU beams such that, for a particular set of restricted IAB-DU beams, the IAB node 710 cannot use any of the restricted IAB-DU beams simultaneously with any of the associated IAB-MT beams. Alternatively, if the signaling indicating the set of restricted IAB-DU beams omits one or more fields indicating the associated IAB-MT beams, the set of restricted IAB-DU beams may be (e.g., implicitly) associated with all IAB-MT beams. In this case, whenever the IAB node 710 performs a transmit or receive operation using an IAB-MT beam, the IAB node 710 may be restricted from using any of the IAB-DU beams in the set of restricted IAB-DU beams. For example, when an IAB-MT performs a first transmission or reception operation using an IAB-MT beam associated with a restricted set of IAB-DU beams, the IAB-DU may perform a simultaneous transmission or reception operation using an IAB-DU that is not included in the restricted set of IAB-DU beams. Further, in some aspects, the signaling may indicate that the restricted set of IAB-DU beams is restricted in one or more simultaneous multiplexing modes or that association with one or more IAB-MT beams is limited to one or more simultaneous multiplexing modes.

[0088]

[0097] 8 is a diagram illustrating an example 800 related to signaling enhancements for simultaneous multiplexing in an IAB network according to the present disclosure. As shown in FIG. 8, the example 800 includes communications between an IAB node 810, a parent node 805 (e.g., a parent IAB node or an IAB donor) of the IAB node 810, one or more child nodes 815 (e.g., a first child node 815-1 and a second child node 815-2) of the IAB node 810, and a UE 820 that may communicate with the parent node 805 over a wireless access link. As further shown, the IAB node 810 may include an IAB-MT that communicates with the parent node 805 via a parent link and an IAB-DU that communicates with the child node 815 via one or more respective child links. In some aspects, the parent node 805 may be a parent IAB node including an MT and a DU, or the parent node 805 may be an IAB donor including a DU for scheduling IAB-MTs and a CU for configuring and controlling the entire IAB network that connects to a core network through the parent node 805. In some aspects, the parent node 805, the IAB node 810, the child node 815, and the UE 820 may be included in an IAB network, such as the wireless network 100 or any one or more of the IAB networks 330, 365, 400 described in further detail above.

[0089]

[0098] As described herein, the IAB node 810 may support communication in one or more multiplexing modes, which may include at least a (default) TDM mode, and the IAB node 810 may further support one or more simultaneous multiplexing modes (e.g., one or more simultaneous half-duplex or full-duplex modes) in some cases. However, in some cases, the multiplexing capabilities of the IAB node 810 may be beam specific, whereby the supported multiplexing modes may vary across different IAB-MT and IAB-DU beam pairs (e.g., due to different levels of spatial separation). For example, as shown in FIG. 8, the IAB node 810 may communicate with a first child node 815-1 using a first IAB-DU beam and may communicate with a second child node 815-2 using a second IAB-DU beam, and the first and second IAB-DU beams may be associated with different beam directions. Thus, in the example 800 shown in FIG. 8, the IAB node 810 may support one or more simultaneous multiplexing modes for a beam pair including an IAB-MT beam used to communicate with the parent node 805 and a first IAB-DU beam used to communicate with the first child node 815-1, but the IAB node 810 may support only a default TDM mode for a beam pair including an IAB-MT beam used to communicate with the parent node 805 and a second IAB-DU beam used to communicate with the second child node 815-2.

[0090]

[0099] Thus, in some aspects, the IAB node 810 may include a subset of IAB-MT and IAB-DU beam pairs that can support all multiplexing modes (including the default TDM mode and the four simultaneous multiplexing modes 630-636 or 720-726 shown in Figures 6 and 7, respectively), another subset of IAB-MT and IAB-DU beam pairs that support only the default TDM mode, or another subset of IAB-MT and IAB-DU beam pairs that support the default TDM mode and one or more (but not all) simultaneous multiplexing modes. However, if the IAB node 810 uses existing signaling techniques to indicate its multiplexing capabilities to the parent node 805, the signaling may generally indicate any multiplexing mode that the IAB node 810 can support using at least one IAB-MT and IAB-DU beam pair. For example, in FIG. 8, because the IAB node 810 supports simultaneous multiplexing for communicating with the first child node 815-1, the IAB node 810 will report a multiplexing capability that includes all four simultaneous multiplexing modes in addition to the default TDM mode, which may lead to scheduling issues in the IAB-DU for communication via the second IAB-DU beam, which may only be operated in TDM mode.

[0091]

[0100] Furthermore, an additional problem that may arise when the IAB node 810 has beam-specific multiplexing capabilities is that there may be a need for the IAB node 810 to dynamically switch between different multiplexing modes (e.g., from TDM mode to simultaneous multiplexing mode or vice versa, or from a first simultaneous multiplexing mode to a second simultaneous multiplexing mode) on a fast time scale, such as slot or minislot granularity. For example, the need to dynamically switch between different multiplexing modes may be based on a scheduling decision of the IAB-DU related to communication with one or more child nodes 815 that are not generally known by the parent node 805, or the need to dynamically switch between different multiplexing modes may be based on the scheduling of the IAB-MT by the parent node 805. Thus, one approach to adapt the beam-specific multiplexing mode used in the IAB node 810 may be to configure the IAB-DU to make scheduling decisions for child links (including the corresponding multiplexing mode to be used for each child link) based on prior knowledge of the scheduling status of the IAB-MT. For example, the IAB-DU may prioritize one or more child links that support only the default TDM mode to be scheduled in one or more slots where the IAB-MT is not scheduled to transmit or receive (e.g., in slots where the parent link is inactive) and to minimize scheduling in slots where the IAB-MT is scheduled to transmit or receive (e.g., in slots where the parent link is inactive). On the other hand, the IAB-DU may schedule a child link that supports one or more simultaneous multiplexing modes in one or more slots regardless of whether the IAB-MT is scheduled to transmit or receive. However, if one or more child links support only the TDM mode and one or more child links support simultaneous multiplexing, the IAB-DU may prioritize scheduling a child link that supports simultaneous multiplexing in a slot where the IAB-MT is scheduled to conserve sufficient resources for the child link that supports only the TDM mode.

[0092]

[0101] However, when the IAB-DU has prior knowledge of the scheduling state of the IAB-MT, the IAB-DU may be able to schedule the child link based on the supported multiplexing mode, but there are various situations in which the IAB-DU may not know the scheduling status of the IAB-MT in advance. For example, the IAB-DU may know the scheduling status of the IAB-MT in advance in one or more slots with semi-static resource allocation, in a downlink or uplink slot lacking a PDCCH opportunity, in a downlink slot with a PDCCH opportunity canceled due to a slot format indicator (SFI) or PDCCH skipping, or in a downlink slot with a PDCCH opportunity and a minimum scheduling gap greater than zero (0) (e.g., when cross-slot scheduling is used). In contrast, the IAB-DU may not have prior knowledge of the scheduling status of the IAB-MT in a downlink slot with a PDCCH opportunity and a minimum scheduling gap equal to 0 (e.g., when same-slot scheduling is used). Furthermore, if an IAB node 810 indicates a supported multiplexing capability without indicating different beam-specific characteristics of the supported multiplexing capability, the parent node 805 may not be aware of the beam-specific multiplexing capability and may schedule the IAB-MT of the IAB node 710 inefficiently. For example, in some cases, the parent node 805 may make an aggressive scheduling decision for the IAB-MT, which may cause the IAB-DU to have insufficient time resources available to schedule one or more child links (e.g., child links that support only the default TDM mode). Although the IAB node 710 may have the ability to cancel one or more transmission or reception operations by the IAB-MT, the cancellation of the IAB-MT operation may affect system performance. For example, the cancellation of a transmission or reception operation by the IAB-MT may increase the block error rate (BLER), which degrades performance on the parent link.In another example, even if the IAB node 810 cancels the receiving operation over the IAB-MT, the parent node 805 still performs transmission, which may interfere with the communication of the IAB-DU over one or more child links, thereby increasing the BLER and degrading performance on one or more child links. Furthermore, the simultaneous multiplexing capability of the IAB node 810 may not be fully utilized if the parent node 805 makes more conservative scheduling decisions to ensure that the IAB-DU has sufficient time resources available to schedule the child links.

[0093]

[0102] Thus, in a first operation 830, the IAB node 810 may transmit signaling to the parent node 805 indicating one or more beam-specific parameters or beam-specific characteristics associated with a multiplexing capability supported at the IAB node 810. For example, the signaling may include a medium access control (MAC) control element (MAC-CE) or uplink control information (UCI) if the parent node 805 is a parent IAB node, or the signaling may include F1-AP signaling if the parent node 805 is an IAB donor or donor CU. In some aspects, the signaling indicating the beam-specific multiplexing capabilities of the IAB node 810 may indicate one or more multiplexing modes supported for a given IAB-MT and IAB-DU beam pair (e.g., whether the IAB-MT and IAB-DU beam pair supports only a default TDM mode or supports one or more simultaneous multiplexing modes in addition to the default TDM mode). Furthermore, in some aspects, the signaling may include a request to perform a fast switch between different multiplexing modes (e.g., between different simultaneous multiplexing modes, or between a simultaneous multiplexing mode and a default TDM mode). In such cases, the signaling may indicate a time scale associated with the switch, which may be indicated with a granularity of one or more slots, one or more frames, one or more milliseconds, or another granularity.

[0094]

[0103] Additionally or alternatively, the signaling may indicate one or more constraints on resource utilization for one or more IAB-MT beams (e.g., for preferred or requested IAB-MT beams or non-preferred or unrequested IAB-MT beams). For example, the signaling may indicate a maximum resource utilization (e.g., a ratio or percentage value) for an IAB-MT beam to ensure that the IAB-DU has sufficient time resources available to schedule child links that support only TDM mode. Additionally or alternatively, the signaling may indicate time-frequency resources requested to be associated with one or more IAB-MTs. For example, the IAB node 810 may determine a desired time-frequency resource pattern based on a scheduling plan for the IAB-DU or a scheduling plan for switching between different multiplexing modes. Further, in some aspects, signaling transmitted from the IAB node 810 to the parent node 805 may indicate one or more IAB-DU beams that are requested (e.g., preferred) to be used on one or more child links simultaneously with an associated IAB-MT beam, or one or more IAB-DU beams that are restricted from being used on one or more child links simultaneously with an associated IAB-MT beam.

[0095]

[0104] As further illustrated in FIG. 8, in a second operation 835, the parent node 805 may transmit one or more scheduling parameters for IAB-MT to the IAB node 810 based on the signaling indicating the beam-specific characteristics associated with the multiplexing capability of the IAB node 810. Additionally, if the parent node 805 is a parent IAB node, the parent node 805 may forward the beam-specific characteristics associated with the multiplexing capability of the IAB node 810 to the parent of the parent node 805 so that the multiplexing capability of the IAB node 810 may be reported to the IAB donor or donor CU. The IAB donor or donor CU may then update the resource configuration on the parent node 805 and the IAB node 810 based on the beam-specific characteristics associated with the multiplexing capability of the IAB node 810. For example, in some aspects, the resource configuration updated by the IAB donor and communicated to the parent node 805 and the IAB node 810 may configure each time resource in the set of time resources as one of a hard resource, a soft resource, or an unavailable resource. Additionally or alternatively, the resource configuration updated by the IAB donor and communicated to the parent node 805 and the IAB node 810 may include a TDD configuration that configures each time resource in the set of time resources as one of a downlink dedicated resource, an uplink dedicated resource, or a flexible resource. For example, in some aspects, the IAB donor or donor CU may update the resource configuration for the parent node 805 or the IAB node 810 to have fewer overlapping hard resources across the parent node 805 and the IAB node 810 or to have more soft resources for the IAB node 810 if there is beam-specific simultaneous multiplexing capability.

[0096]

[0105] 9 is a flow chart illustrating an example process 900 performed, for example, by a parent node in an IAB network, in accordance with the present disclosure. The example process 900 is an example of a parent node (e.g., parent node 605, parent node 705, or parent node 805) performing operations associated with signaling extensions for simultaneous multiplexing in an IAB network.

[0097]

[0106] 9, in some aspects, the process 900 may include determining, for the IAB-DU, a set of restricted IAB-DU beams that should not be used by the IAB-DU while the IAB-MT of the IAB node is using one or more IAB-MT beams, the determination of the set of restricted IAB-DU beams being based at least in part on one or more measurements related to interference caused by the IAB-DU and IAB-MT performing simultaneous operation in one or more simultaneous multiplexing modes (block 910). For example, the parent node (e.g., by using the communications manager 140 or the determination component 1308 shown in FIG. 13) may determine, for the IAB-DU, a set of restricted IAB-DU beams that should not be used by the IAB-DU while the IAB-MT of the IAB node is using one or more IAB-MT beams, the determination of the set of restricted IAB-DU beams being based at least in part on one or more measurements related to interference caused by the IAB-DU and IAB-MT performing simultaneous operation in one or more simultaneous multiplexing modes, as described above.

[0098]

[0107] 9, in some aspects, process 900 may include transmitting signaling to the IAB node indicating the set of restricted IAB-DU beams and associating the set of restricted IAB-DU beams with one or more IAB-MT beams (block 920). For example, a parent node (e.g., by using the communications manager 140 or the transmitting component 1304 shown in FIG. 13) may transmit signaling to the IAB node indicating the set of restricted IAB-DU beams and associating the set of restricted IAB-DU beams with one or more IAB-MT beams, as described above.

[0099]

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

[0100]

[0109] In a first additional aspect, the signaling includes one or more fields that associate a restricted set of IAB-DU beams with one or more IAB-MT beams.

[0101]

[0110] In a second additional aspect, alone or in combination with the first aspect, the signaling indicates that each IAB-DU beam included in the set of restricted IAB-DU beams is associated with all IAB-MT beams, based at least in part on omitting one or more fields for associating the set of restricted IAB-DU beams with any of one or more IAB-MT beams.

[0102]

[0111] 9 illustrates example blocks of process 900, in some aspects process 900 may include additional, fewer, different, or differently configured blocks than those shown in FIG 9. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0103]

[0112] 10 is a flow chart illustrating an example process 1000 performed, for example, by a parent node in an IAB network, in accordance with the present disclosure. The example process 1000 is an example of a parent node (e.g., parent node 605, parent node 705, or parent node 805) performing operations associated with signaling extensions for simultaneous multiplexing in an IAB network.

[0104]

[0113] 10, in some aspects, process 1000 may include receiving signaling from an IAB node including an IAB-DU and an IAB-MT indicating one or more beam-specific parameters related to multiplexing capabilities for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam (block 1010). For example, a parent node may receive (such as by using the communications manager 140 or receiving component 1302 shown in FIG. 13) signaling from an IAB node including an IAB-DU and an IAB-MT indicating one or more beam-specific parameters related to multiplexing capabilities for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam.

[0105]

[0114] 10, in some aspects, process 1000 may include transmitting, to the IAB node, one or more scheduling parameters for the IAB-MT based at least in part on the signaling indicating the one or more beam-specific parameters (block 1020). For example, the parent node may transmit (e.g., by using the communications manager 140 or the transmitting component 1308 shown in FIG. 13) to the IAB node one or more scheduling parameters for the IAB-MT based at least in part on the signaling indicating the one or more beam-specific parameters.

[0106]

[0115] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects, in connection with one or more other processes described below or elsewhere herein.

[0107]

[0116] In a first additional aspect, the one or more beam-specific parameters indicate whether the beam pair supports one or more simultaneous multiplexing modes.

[0108]

[0117] In a second additional aspect, alone or in combination with the first aspect, the signaling received from the IAB node includes a request to switch the beam pair from the first simultaneous multiplexing mode to the second simultaneous multiplexing mode.

[0109]

[0118] In a third additional aspect, alone or in combination with one or more of the first and second aspects, the one or more beam-specific parameters include a time scale associated with switching.

[0110]

[0119] In a fourth additional aspect, alone or in combination with one or more of the first through third aspects, the one or more beam-specific parameters include one or more constraints on resource utilization on IAB-MT beams included in the beam pair.

[0111]

[0120] In a fifth additional aspect, alone or in combination with one or more of the first through fourth aspects, the one or more beam-specific parameters include a time-frequency resource pattern to associate with an IAB-MT beam included in the beam pair.

[0112]

[0121] In a sixth additional aspect, alone or in combination with one or more of the first through fifth aspects, the one or more beam-specific parameters indicate one or more IAB-DU beams or IAB-DU child links that are required to be associated with or restricted from being associated with an IAB-MT beam included in the beam pair.

[0113]

[0122] In a seventh additional aspect, alone or in combination with one or more of the first to sixth aspects, the signaling indicating the one or more beam-specific parameters includes F1-AP signaling, MAC-CE, or UCI, indicating the one or more beam-specific parameters.

[0114]

[0123] In an eighth additional aspect, alone or in combination with one or more of the first through seventh aspects, the one or more scheduling parameters configure each respective time resource of the plurality of time resources at one or more of the parent nodes or IAB nodes as one of a hard resource, a soft resource, or an unavailable resource.

[0115]

[0124] In a ninth additional aspect, alone or in combination with one or more of the first to eighth aspects, the one or more scheduling parameters configure, at one or more of the parent node or the IAB node, each respective time resource of the plurality of time resources as one of a downlink dedicated resource, an uplink dedicated resource, or a flexible resource.

[0116]

[0125] 10 illustrates example blocks of process 1000, in some aspects process 1000 may include additional, fewer, different, or differently configured blocks than those illustrated in FIG 10. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0117]

[0126] 11 is a flow chart illustrating an example process 1100 performed by an IAB node, e.g., including an IAB-MT and an IAB-DU, in accordance with the present disclosure. The example process 1100 is an example of an IAB node (e.g., IAB node 610, IAB node 710, or IAB node 810) performing operations associated with signaling extensions for simultaneous multiplexing in an IAB network.

[0118]

[0127] As shown in FIG. 11, in some aspects, process 1100 may include receiving signaling from a parent node indicating a set of restricted IAB-DU beams that should not be used by the IAB-DU while the IAB-MT is using one or more IAB-MT beams based at least in part on one or more measurements related to interference caused by the IAB-DU and IAB-MT performing simultaneous operation in one or more simultaneous multiplexing modes, the signaling associating the set of restricted IAB-DU beams with the one or more IAB-MT beams (block 1110). For example, the IAB node may receive (such as by using the communications manager 150 or receiving component 1402 shown in FIG. 1402) signaling from a parent node indicating a set of restricted IAB-DU beams that should not be used by the IAB-DU while the IAB-MT is using one or more IAB-MT beams, based at least in part on one or more measurements related to interference caused by the IAB-DU and IAB-MT performing simultaneous operation in one or more simultaneous multiplexing modes, as described above, and the signaling associates the set of restricted IAB-DU beams with one or more IAB-MT beams.

[0119]

[0128] 11, in some aspects, process 1100 may include performing a first transmission or reception operation using an IAB-MT beam included in one or more IAB-MT beams associated with the set of restricted IAB-DU beams (block 1120). For example, the IAB node may perform a first transmission or reception operation using an IAB-MT beam included in one or more IAB-MT beams associated with the set of restricted IAB-DU beams (such as by using the communications manager 150 or execution component 1408 shown in FIG. 14), as described above.

[0120]

[0129] 11, in some aspects, the process 1100 may include performing a second transmission or reception operation using an IAB-DU beam not included in the set of restricted IAB-DU beams (block 1130). For example, the IAB node may perform (such as by using the communications manager 150 or the execution component 1408 shown in FIG. 14) a second transmission or reception operation using an IAB-DU beam not included in the set of restricted IAB-DU beams, as described above.

[0121]

[0130] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects, in connection with one or more other processes described below or elsewhere herein.

[0122]

[0131] In a first additional aspect, the signaling includes one or more fields that associate a restricted set of IAB-DU beams with one or more IAB-MT beams.

[0123]

[0132] In a second additional aspect, alone or in combination with the first aspect, the signaling indicates that each IAB-DU beam included in the set of restricted IAB-DU beams is associated with all IAB-MT beams, based at least in part on omitting one or more fields for associating the set of restricted IAB-DU beams with any of one or more IAB-MT beams.

[0124]

[0133] 11 illustrates example blocks of process 1100, in some aspects process 1100 may include additional, fewer, different, or differently configured blocks than those illustrated in FIG 11. Additionally or alternatively, two or more of the blocks of process 1100 may be performed in parallel.

[0125]

[0134] 12 is a flow chart illustrating an example process 1200 performed by an IAB node, e.g., including an IAB-MT and an IAB-DU, in accordance with the present disclosure. The example process 1200 is an example of an IAB node (e.g., IAB node 610, IAB node 710, or IAB node 810) performing operations associated with signaling extensions for simultaneous multiplexing in an IAB network.

[0126]

[0135] 12, in some aspects, process 1200 may include transmitting signaling to a parent node indicating one or more beam-specific parameters related to multiplexing capabilities for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam (block 1210). For example, the IAB node may transmit (such as by using the communications manager 150 or the transmitting component 1404 shown in FIG. 14) signaling to a parent node indicating one or more beam-specific parameters related to multiplexing capabilities for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam.

[0127]

[0136] 12, in some aspects, the process 1200 may include receiving, from a parent node, one or more scheduling parameters for the IAB-MT based at least in part on the signaling indicating the one or more beam-specific parameters (block 1220). For example, the IAB node may receive (such as by using the communications manager 150 or the receiving component 1402 shown in FIG. 14) from a parent node, one or more scheduling parameters for the IAB-MT based at least in part on the signaling indicating the one or more beam-specific parameters.

[0128]

[0137] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects, in connection with one or more other processes described below or elsewhere herein.

[0129]

[0138] In a first additional aspect, the one or more beam-specific parameters indicate whether the beam pair supports one or more simultaneous multiplexing modes.

[0130]

[0139] In a second additional aspect, alone or in combination with the first aspect, the signaling transmitted to the parent node includes a request to switch the beam pair from the first simultaneous multiplexing mode to the second simultaneous multiplexing mode.

[0131]

[0140] In a third additional aspect, alone or in combination with one or more of the first and second aspects, the one or more beam-specific parameters include a time scale associated with switching.

[0132]

[0141] In a fourth additional aspect, alone or in combination with one or more of the first through third aspects, the one or more beam-specific parameters include one or more constraints on resource utilization on IAB-MT beams included in the beam pair.

[0133]

[0142] In a fifth additional aspect, alone or in combination with one or more of the first through fourth aspects, the one or more beam-specific parameters include a time-frequency resource pattern to associate with an IAB-MT beam included in the beam pair.

[0134]

[0143] In a sixth additional aspect, alone or in combination with one or more of the first through fifth aspects, the one or more beam-specific parameters indicate one or more IAB-DU beams or IAB-DU child links that are required to be associated with or restricted from being associated with an IAB-MT beam included in the beam pair.

[0135]

[0144] In a seventh additional aspect, alone or in combination with one or more of the first to sixth aspects, the signaling indicating the one or more beam-specific parameters includes F1-AP signaling, MAC-CE, or UCI, indicating the one or more beam-specific parameters.

[0136]

[0145] In an eighth additional aspect, alone or in combination with one or more of the first through seventh aspects, the one or more scheduling parameters configure each respective time resource of the plurality of time resources at the IAB node as one of a hard resource, a soft resource, or an unavailable resource.

[0137]

[0146] In a ninth additional aspect, alone or in combination with one or more of the first to eighth aspects, the one or more scheduling parameters configure each respective time resource of the plurality of time resources at the IAB node as one of a downlink dedicated resource, an uplink dedicated resource, or a flexible resource.

[0138]

[0147] 12 illustrates example blocks of process 1200, in some aspects process 1200 may include additional, fewer, different, or differently configured blocks than those illustrated in FIG 12. Additionally or alternatively, two or more of the blocks of process 1200 may be performed in parallel.

[0139]

[0148] 13 is a diagram of an example apparatus 1300 for wireless communication in accordance with the present disclosure. The apparatus 1300 may be a parent node or a parent node may include the apparatus 1300. In some aspects, the apparatus 1300 includes a receiving component 1302, a transmitting component 1304, and a communications manager 140, which may be in communication with each other (e.g., via one or more buses). As shown, the apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using the receiving component 1302 and the transmitting component 1304.

[0140]

[0149] In some aspects, the apparatus 1300 may be configured to perform one or more operations described herein with respect to Figures 7-8. Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as process 900 of Figure 9, process 1000 of Figure 10, or a combination thereof. In some aspects, the apparatus 1300 may include one or more components of a base station described above with respect to Figure 2, an IAB donor 405 described above with respect to Figure 4, or an IAB node 410 described above with respect to Figure 4.

[0141]

[0150] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1306. The receiving component 1302 may provide the received communications to one or more other components of the device 1300, such as the communications manager 140. In some aspects, the receiving component 1302 may perform signal processing on the received communications (such as filtering, amplifying, demodulating, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) and provide the processed signals to one or more other components. In some aspects, the receiving component 1302 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the base station described above with respect to FIG. 2.

[0142]

[0151] The transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1306. In some aspects, the communications manager 140 may generate communications and transmit the generated communications to the transmitting component 1304 for transmission to the device 1306. In some aspects, the transmitting component 1304 may perform signal processing on the generated communications (such as filtering, amplifying, modulating, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) and transmit the processed signals to the device 1306. In some aspects, the transmitting component 1304 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or combinations thereof, of the base station described above with respect to FIG. 2. In some aspects, the transmitting component 1304 may be co-located with the receiving component 1302 in a transceiver.

[0143]

[0152] The communications manager 140 may determine, for the IAB-DU, a set of restricted IAB-DU beams that should not be used by the IAB-DU while the IAB-MT is using one or more IAB-MT beams, the determination of the set of restricted IAB-DU beams being based at least in part on one or more measurements related to interference caused by the IAB-DU and IAB-MT performing simultaneous operation in one or more simultaneous multiplexing modes. The communications manager 140 may transmit, or cause the transmitting component 1304 to transmit, signaling to the IAB node indicating the set of restricted IAB-DU beams and associating the set of restricted IAB-DU beams with one or more IAB-MT beams. Additionally or alternatively, the communications manager 140 may receive, or cause the receiving component 1302 to receive, signaling from an IAB node including an IAB-DU and an IAB-MT indicating one or more beam-specific parameters related to multiplexing capabilities for a beam pair including an IAB-MT beam and an IAB-DU beam associated with an IAB-MT beam. The communications manager 140 may transmit, or cause to be transmitted to the transmitting component 1304, one or more scheduling parameters for the IAB-MT based at least in part on the signaling indicating the one or more beam-specific parameters. In some aspects, the communications manager 140 may perform one or more operations described elsewhere herein as being performed by one or more components of the communications manager 140.

[0144]

[0153] The communications manager 140 may include a controller / processor, memory, scheduler, communication unit, or combination thereof of the base station described above with respect to FIG. 2. In some aspects, the communications manager 140 includes a set of components, such as the determining component 1308, among other examples. Alternatively, the set of components may be separate and distinct from the communications manager 140. In some aspects, one or more components of the set of components may include or be implemented within a controller / processor, memory, scheduler, communication unit, or combination thereof of the base station described above with respect to FIG. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the functions or operations of the component.

[0145]

[0154] The determining component 1308 may determine, for the IAB-DU, a set of restricted IAB-DU beams that should not be used by the IAB-DU while the IAB-MT is using one or more IAB-MT beams, the determination of the set of restricted IAB-DU beams being based at least in part on one or more measurements related to interference caused by the IAB-DU and IAB-MT performing simultaneous operation in one or more simultaneous multiplexing modes. The transmitting component 1304 may transmit signaling to the IAB node indicating the set of restricted IAB-DU beams and associating the set of restricted IAB-DU beams with one or more IAB-MT beams.

[0146]

[0155] The receiving component 1302 may receive signaling from an IAB node including an IAB-DU and an IAB-MT indicating one or more beam-specific parameters related to multiplexing capabilities for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam. The transmitting component 1304 may transmit one or more scheduling parameters for the IAB-MT to the IAB node based at least in part on the signaling indicating the one or more beam-specific parameters.

[0147]

[0156] The number and configuration of components shown in Figure 13 are provided as an example. In practice, there may be additional, fewer, different, or differently configured components than those shown in Figure 13. Furthermore, two or more of the components shown in Figure 13 may be implemented within a single component, or a single component shown in Figure 13 may be implemented as multiple distributed components. Additionally or alternatively, a set of components (or components) shown in Figure 13 may perform one or more functions described as being performed by another set of components shown in Figure 13.

[0148]

[0157] 14 is a diagram of an example apparatus 1400 for wireless communication in accordance with the present disclosure. The apparatus 1400 may be an IAB node or the IAB node may include the apparatus 1400. In some aspects, the apparatus 1400 includes a receiving component 1402, a transmitting component 1404, and a communications manager 150, which may be in communication with each other (e.g., via one or more buses). As shown, the apparatus 1400 may communicate with another apparatus 1406 (such as a UE, a base station, or another wireless communication device) using the receiving component 1402 and the transmitting component 1404.

[0149]

[0158] In some aspects, the apparatus 1400 may be configured to perform one or more operations described herein with respect to Figures 7-8. Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as process 1100 of Figure 11, process 1200 of Figure 12, or a combination thereof. In some aspects, the apparatus 1400 may include one or more components of the base station described above with respect to Figure 2 or the IAB node 410 described above with respect to Figure 4.

[0150]

[0159] The receiving component 1402 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1406. The receiving component 1402 may provide the received communications to one or more other components of the device 1400, such as the communications manager 150. In some aspects, the receiving component 1402 may perform signal processing on the received communications (such as filtering, amplifying, demodulating, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) and provide the processed signals to one or more other components. In some aspects, the receiving component 1402 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the base station described above with respect to FIG. 2.

[0151]

[0160] The transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1406. In some aspects, the communications manager 150 may generate communications and transmit the generated communications to the transmitting component 1404 for transmission to the device 1406. In some aspects, the transmitting component 1404 may perform signal processing on the generated communications (such as filtering, amplifying, modulating, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) and transmit the processed signals to the device 1406. In some aspects, the transmitting component 1404 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or combinations thereof, of the base station described above with respect to FIG. 2. In some aspects, the transmitting component 1404 may be co-located with the receiving component 1402 in a transceiver.

[0152]

[0161] The communications manager 150 may receive, or cause the receiving component 1402 to receive, signaling from a parent node indicating a set of restricted IAB-DU beams that should not be used by the IAB-DU while the IAB-MT is using one or more IAB-MT beams, based at least in part on one or more measurements related to interference caused by the IAB-DU and IAB-MT performing simultaneous operations in one or more simultaneous multiplexing modes, and the signaling associates the set of restricted IAB-DU beams with one or more IAB-MT beams. The communications manager 150 may perform, or cause the receiving component 1402 or the transmitting component 1404 to perform, a first transmission or reception operation using an IAB-MT beam included in one or more IAB-MT beams associated with the set of restricted IAB-DU beams. The communications manager 150 may perform, or cause the receiving component 1402 or the transmitting component 1404 to perform, a second transmission or reception operation using an IAB-DU beam not included in the set of restricted IAB-DU beams. Additionally or alternatively, communications manager 150 may transmit, or cause transmitting component 1404 to transmit, signaling to a parent node indicating one or more beam-specific parameters related to multiplexing capabilities for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam. Communications manager 150 may receive, or cause receiving component 1402 to receive, one or more scheduling parameters for the IAB-MT from the parent node based at least in part on the signaling indicating the one or more beam-specific parameters. In some aspects, communications manager 150 may perform one or more operations described elsewhere herein as being performed by one or more components of communications manager 150.

[0153]

[0162] The communications manager 150 may include a controller / processor, memory, scheduler, communication unit, or combination thereof, of the base station described above with respect to FIG. 2. In some aspects, the communications manager 150 includes a set of components, such as the execution component 1408, among other examples. Alternatively, the set of components may be separate and distinct from the communications manager 150. In some aspects, one or more components of the set of components may include or be implemented within a controller / processor, memory, scheduler, communication unit, or combination thereof, of the base station described above with respect to FIG. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the functions or operations of the component.

[0154]

[0163] The receiving component 1402 may receive signaling from a parent node indicating a set of restricted IAB-DU beams that should not be used by the IAB-DU while the IAB-MT is using one or more IAB-MT beams, based at least in part on one or more measurements related to interference caused by the IAB-DU and IAB-MT performing simultaneous operations in one or more simultaneous multiplexing modes, the signaling associating the set of restricted IAB-DU beams with one or more IAB-MT beams. The executing component 1408 may perform a first transmit or receive operation using an IAB-MT beam included in the one or more IAB-MT beams associated with the set of restricted IAB-DU beams. The executing component 1408 may perform a second transmit or receive operation using an IAB-DU beam not included in the set of restricted IAB-DU beams.

[0155]

[0164] The transmitting component 1404 may transmit signaling to a parent node indicating one or more beam-specific parameters related to multiplexing capabilities for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam. The receiving component 1402 may receive one or more scheduling parameters for the IAB-MT from the parent node based at least in part on the signaling indicating the one or more beam-specific parameters.

[0156]

[0165] The number and configuration of components shown in Figure 14 are provided as an example. In practice, there may be additional, fewer, different, or differently configured components than those shown in Figure 14. Furthermore, two or more of the components shown in Figure 14 may be implemented within a single component, or a single component shown in Figure 14 may be implemented as multiple distributed components. Additionally or alternatively, a set of components (or components) shown in Figure 14 may perform one or more functions described as being performed by another set of components shown in Figure 14.

[0157]

[0166] The following provides an overview of several aspects of the disclosure.

[0158]

[0167] Aspect 1: A method of wireless communications performed by a parent node, comprising: for a distributed unit (DU) (IAB-DU) of an integrated access and backhaul (IAB) node, determining a set of restricted IAB-DU beams that should not be used by the IAB-DU while a mobile terminal function (MT) (IAB-MT) of the IAB node is using one or more IAB-MT beams; and transmitting signaling to the IAB node indicating the set of restricted IAB-DU beams and associating the set of restricted IAB-DU beams with one or more IAB-MT beams, wherein the determination of the set of restricted IAB-DU beams is based at least in part on one or more measurements related to interference caused by the IAB-DU and IAB-MT performing simultaneous operation in one or more simultaneous multiplexing modes.

[0159]

[0168] Aspect 2: The method of aspect 1, wherein the signaling includes one or more fields that associate the set of restricted IAB-DU beams with one or more IAB-MT beams.

[0160]

[0169] Aspect 3: The method of aspect 1, wherein the signaling indicates that each IAB-DU beam included in the set of restricted IAB-DU beams is associated with all IAB-MT beams based at least in part on omitting one or more fields for associating the set of restricted IAB-DU beams with any of one or more IAB-MT beams.

[0161]

[0170] Aspect 4: A method of wireless communication performed by a parent node, comprising: receiving signaling from an IAB node including an IAB-DU and an IAB-MT indicating one or more beam-specific parameters related to multiplexing capability for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam; and transmitting one or more scheduling parameters for the IAB-MT to the IAB node based at least in part on the signaling indicating the one or more beam-specific parameters.

[0162]

[0171] Aspect 5: The method of aspect 4, wherein the one or more beam-specific parameters indicate whether the beam pair supports one or more simultaneous multiplexing modes.

[0163]

[0172] Aspect 6: The method of aspect 4 or 5, wherein the signaling received from the IAB node includes a request to switch the beam pair from a first simultaneous multiplexing mode to a second simultaneous multiplexing mode.

[0164]

[0173] Aspect 7: The method of aspect 6, wherein the one or more beam-specific parameters include a time scale associated with switching.

[0165]

[0174] Aspect 8: A method as described in any of aspects 4 to 7, wherein the one or more beam-specific parameters include one or more constraints regarding resource utilization on IAB-MT beams included in the beam pair.

[0166]

[0175] Aspect 9: A method as described in any of aspects 4 to 8, wherein the one or more beam-specific parameters include a time-frequency resource pattern to associate with an IAB-MT beam included in the beam pair.

[0167]

[0176] Aspect 10: A method as described in any of aspects 4 to 9, wherein one or more beam-specific parameters indicate one or more IAB-DU beams or IAB-DU child links that are required to be associated with, or restricted from being associated with, an IAB-MT beam included in the beam pair.

[0168]

[0177] Aspect 11: A method as described in any of aspects 4 to 10, wherein the signaling indicating one or more beam-specific parameters includes F1-AP signaling, MAC-CE, or UCI indicating one or more beam-specific parameters.

[0169]

[0178] Aspect 12: A method as described in any of aspects 4 to 11, wherein one or more scheduling parameters configure each respective time resource of the plurality of time resources as one of a hard resource, a soft resource, or an unavailable resource at one or more of the parent node or IAB node.

[0170]

[0179] Aspect 13: A method as described in any of aspects 4 to 12, wherein the one or more scheduling parameters configure, in one or more of the parent node or the IAB node, each respective time resource of the plurality of time resources as one of a downlink dedicated resource, an uplink dedicated resource, or a flexible resource.

[0171]

[0180] Aspect 14: A method of wireless communications performed by an integrated access and backhaul (IAB) node including a distributed unit (IAB-DU) and a mobile terminal function (IAB-MT), the method comprising receiving signaling from a parent node indicating a set of restricted IAB-DU beams that should not be used by the IAB-DU while the IAB-MT is using one or more IAB-MT beams based at least in part on one or more measurements related to interference caused by the IAB-DU and IAB-MT performing simultaneous operation in one or more simultaneous multiplexing modes, the signaling associating the set of restricted IAB-DU beams with one or more IAB-MT beams, performing by the IAB-MT a first transmission or reception operation using an IAB-MT beam included in the one or more IAB-MT beams associated with the set of restricted IAB-DU beams, and performing by the IAB-DU concurrently with the first transmission or reception operation a second transmission or reception operation using an IAB-DU beam not included in the set of restricted IAB-DU beams.

[0172]

[0181] Aspect 15: The method of aspect 14, wherein the signaling includes one or more fields that associate the set of restricted IAB-DU beams with one or more IAB-MT beams.

[0173]

[0182] Aspect 16: The method of aspect 14, wherein the signaling indicates that each IAB-DU beam included in the set of restricted IAB-DU beams is associated with all IAB-MT beams based at least in part on omitting one or more fields for associating the set of restricted IAB-DU beams with any of one or more IAB-MT beams.

[0174]

[0183] Aspect 17: A method of wireless communication performed by an integrated access and backhaul (IAB) node including a distributed unit (IAB-DU) and a mobile terminal function (IAB-MT), comprising: transmitting, to a parent node, signaling indicating one or more beam-specific parameters related to multiplexing capability for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam; and receiving, from the parent node, one or more scheduling parameters for the IAB-MT based at least in part on the signaling indicating the one or more beam-specific parameters.

[0175]

[0184] Aspect 18: The method described in aspect 17, wherein the one or more beam-specific parameters indicate whether the beam pair supports one or more simultaneous multiplexing modes.

[0176]

[0185] Aspect 19: The method of aspect 17 or 18, wherein the signaling transmitted to the parent node includes a request to switch the beam pair from the first simultaneous multiplexing mode to the second simultaneous multiplexing mode.

[0177]

[0186] Aspect 20: The method described in aspect 19, wherein the one or more beam-specific parameters include a time scale associated with the switching.

[0178]

[0187] Aspect 21: A method described in any of aspects 17 to 20, wherein the one or more beam-specific parameters include one or more constraints regarding resource utilization on IAB-MT beams included in the beam pair.

[0179]

[0188] Aspect 22: A method described in any of aspects 17 to 21, wherein the one or more beam-specific parameters include a time-frequency resource pattern to associate with an IAB-MT beam included in the beam pair.

[0180]

[0189] Aspect 23: A method as described in any of aspects 17 to 22, wherein one or more beam-specific parameters indicate one or more IAB-DU beams or IAB-DU child links that are required to be associated with, or restricted from being associated with, an IAB-MT beam included in the beam pair.

[0181]

[0190] Aspect 24: A method as described in any of aspects 17 to 23, wherein the signaling indicating one or more beam-specific parameters includes F1-AP signaling, MAC-CE, or UCI indicating one or more beam-specific parameters.

[0182]

[0191] Aspect 25: A method as described in any of aspects 17 to 24, wherein one or more scheduling parameters configure each respective time resource of a plurality of time resources at an IAB node as one of a hard resource, a soft resource, or an unavailable resource.

[0183]

[0192] Aspect 26: A method as described in any of aspects 17 to 25, wherein the one or more scheduling parameters configure each respective time resource of a plurality of time resources at the IAB node as one of a downlink dedicated resource, an uplink dedicated resource, or a flexible resource.

[0184]

[0193] Aspect 27: An apparatus for wireless communication in a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform the methods described in one or more of aspects 1 to 3.

[0185]

[0194] Aspect 28: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the methods described in one or more of aspects 1 to 3.

[0186]

[0195] Aspect 29: An apparatus for wireless communication, comprising at least one means for performing the method recited in one or more of aspects 1 to 3.

[0187]

[0196] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the methods described in one or more of aspects 1 to 3.

[0188]

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

[0189]

[0198] Aspect 32: An apparatus for wireless communication in a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform the methods described in one or more of aspects 4 to 13.

[0190]

[0199] Aspect 33: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the methods described in one or more of aspects 4 to 13.

[0191]

[0200] Aspect 34: An apparatus for wireless communication, comprising at least one means for performing the method recited in one or more of aspects 4 to 13.

[0192]

[0201] Aspect 35: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the methods described in one or more of aspects 4 to 13.

[0193]

[0202] Aspect 36: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method described in one or more of aspects 4 to 13.

[0194]

[0203] Aspect 37: An apparatus for wireless communication in a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform the methods described in one or more of aspects 14 to 16.

[0195]

[0204] Aspect 38: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the methods described in one or more of aspects 14 to 16.

[0196]

[0205] Aspect 39: An apparatus for wireless communication, comprising at least one means for performing the method recited in one or more of aspects 14 to 16.

[0197]

[0206] Aspect 40: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the methods described in one or more of aspects 14 to 16.

[0198]

[0207] Aspect 41: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method described in one or more of aspects 14 to 16.

[0199]

[0208] Aspect 42: An apparatus for wireless communication in a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform the methods described in one or more of aspects 17 to 26.

[0200]

[0209] Aspect 43: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the methods described in one or more of aspects 17 to 26.

[0201]

[0210] Aspect 44: An apparatus for wireless communication, comprising at least one means for performing the method recited in one or more of aspects 17 to 26.

[0202]

[0211] Aspect 45: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the methods described in one or more of aspects 17 to 26.

[0203]

[0212] Aspect 46: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method described in one or more of aspects 17 to 26.

[0204]

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

[0205]

[0214] The term "component" as used herein is intended to be broadly construed as hardware or a combination of hardware and software. "Software" is intended to be broadly construed to mean, among other examples, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, or functions, whether termed software, firmware, middleware, microcode, hardware description language, or the like. A "processor" as used herein is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in different forms of hardware or combinations of hardware and software. The actual specialized control hardware or software code used to implement these systems or methods is not intended to limit the aspects. Thus, the operation and behavior of the systems or methods are described herein without reference to specific software code, as one skilled in the art will appreciate that software and hardware may be designed to implement the systems or methods based at least in part on the description herein.

[0206]

[0215] As used herein, depending on the context, "meeting a threshold" can refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold, among other examples.

[0207]

[0216] Although certain combinations of features are recited in the claims or disclosed herein, these combinations do not limit the disclosure of the various aspects. Many of these features may be combined in ways not specifically recited in the claims or disclosed herein. The disclosure of the various aspects includes each dependent claim in combination with any other claim in the claims. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to include a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other order of a, b, and c).

[0208]

[0217] No element, act, or instruction used herein should be construed as critical or essential unless expressly described as such. Additionally, the articles "a" and "an" as used herein include one or more items and may be used interchangeably with "one or more." Additionally, the article "the" as used herein includes one or more items referenced with the article "the" and may be used interchangeably with "one or more." Additionally, the terms "set" and "group" as used herein include one or more items and may be used interchangeably with "one or more." When only one item is intended, the phrase "only one" or similar language is used. Additionally, the terms "has," "have," "having," and similar terms as used herein are intended to be open-ended terms that do not limit the elements they modify (e.g., an element that "has" A may also have B). Additionally, the phrase "based on" is intended to mean "based at least in part on," unless otherwise specified. Additionally, as used herein, the term "or" is inclusive when used in a sequence and may be used interchangeably with "and / or" unless otherwise noted (e.g., when used in combination with "either" or "only one of").

Claims

A method of wireless communication performed by a parent node, comprising: receiving, from an integrated access and backhaul (IAB) node including a distributed unit (IAB-DU) and a mobile terminal function (IAB-MT), signaling indicating one or more beam-specific parameters related to the multiplexing capability for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam; transmitting, to the IAB node, one or more scheduling parameters for the IAB-MT based at least in part on the signaling indicating the one or more beam-specific parameters; A method comprising the above. The method according to claim 1, wherein the one or more beam-specific parameters indicate whether the beam pair supports one or more simultaneous multiplexing modes. The signaling received from the IAB node includes a request to switch the beam pair from a first simultaneous multiplexing mode to a second simultaneous multiplexing mode. In particular, the one or more beam-specific parameters include a time scale associated with the switching. In particular, the one or more beam-specific parameters include one or more constraints on resource utilization on the IAB-MT beam included in the beam pair. The method according to claim 1, wherein the one or more beam-specific parameters include a time-frequency resource pattern for associating with the IAB-MT beam included in the beam pair. The method according to claim 1, wherein the one or more beam-specific parameters indicate one or more IAB-DU beams or IAB-DU sub-links that are required to be associated with or are restricted from being associated with the IAB-MT beam included in the beam pair. The method according to claim 1, wherein the signaling indicating the one or more beam-specific parameters includes F1 application protocol (F1-AP) signaling, media access control (MAC) control element (MAC-CE), or uplink control information (UCI) indicating the one or more beam-specific parameters. **Claim 6**: The method according to claim 1, wherein the one or more scheduling parameters configure each of the plurality of time resources as one of a hard resource, a soft resource, or an unavailable resource in one or more of the parent node or the IAB node. **Claim 7**: The method according to claim 1, wherein the one or more scheduling parameters configure each of the plurality of time resources as one of a downlink dedicated resource, an uplink dedicated resource, or a flexible resource in one or more of the parent node or the IAB node. **Claim 8** A parent node, comprising at least one processor, and at least one memory storing processor-readable code communicatively coupled to the at least one processor, wherein the processor-readable code is configured to cause the at least one processor to execute the method according to any one of claims 1 to 7 when executed by the at least one processor. **Claim 9**: A method of wireless communication performed by an integrated access and backhaul (IAB) node including a distributed unit (IAB-DU) and a mobile terminal function (IAB-MT), comprising transmitting, by a parent node, signaling indicating one or more beam-specific parameters related to a multiplexing capability for a beam pair including an IAB-MT beam and an IAB-DU beam associated with the IAB-MT beam; and receiving, by the IAB-MT from the parent node, one or more scheduling parameters for the IAB-MT based at least in part on the signaling indicating the one or more beam-specific parameters. **Claim 10**: The method according to claim 9, wherein the one or more beam-specific parameters indicate whether the beam pair supports one or more simultaneous multiplexing modes. **Claim 11**: The method according to claim 9, wherein the signaling transmitted to the parent node includes a request to switch the beam pair from a first simultaneous multiplexing mode to a second simultaneous multiplexing mode. **Claim 12**: The one or more beam-specific parameters include a time scale associated with the switching. In particular, the one or more beam-specific parameters include one or more constraints regarding resource utilization on the IAB-MT beam included in the beam pair. In particular, the one or more beam-specific parameters include a time-frequency resource pattern for associating with the IAB-MT beam included in the beam pair. In particular, the one or more beam-specific parameters indicate one or more IAB-DU beams or IAB-DU sub-links that are required to be associated with, or are restricted from being associated with, the IAB-MT beam included in the beam pair, according to the method of claim 9.

13. The signaling indicating the one or more beam-specific parameters includes F1-AP signaling, MAC-CE, or UCI indicating the one or more beam-specific parameters. In particular, each of the plurality of time resources at the IAB node is configured as one of a hard resource, a soft resource, or an unavailable resource by the one or more scheduling parameters. In particular, each of the plurality of time resources at the IAB node is configured as one of a downlink dedicated resource, an uplink dedicated resource, or a flexible resource by the one or more scheduling parameters, according to the method of claim 9.

14. An integrated access and backhaul (IAB) node including a distributed unit (IAB-DU) and a mobile terminal function (IAB-MT), at least one processor, at least one memory storing processor-readable code communicatively coupled to the at least one processor, The integrated access and backhaul (IAB) node is configured such that when the processor-readable code is executed by the at least one processor, the IAB node executes the method according to any one of claims 9 to 13.

15. A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to execute the method according to any one of claims 1 to 7 and claims 9 to 13.

Images