Patent Description:
<CIT> discloses a method for performing beamformed backhaul communications including determining first formats of subframes supporting access communications between the first TRP and user equipments (UEs) served by the first TRP, determining a subset of the subframes supporting access communications, the subset of the subframes supports backhaul communications between the first TRP and a second TRP, and communicating with a UE over an access link in accordance with the subset of subframes. R1-<NUM> and R1-<NUM> discuss mechanisms for resource multiplexing among backhaul and access links.

The underlying problem of the present invention is solved by the subject matter of the independent claims. In some aspects, a method of wireless communication, performed by an integrated access and backhaul (IAB) node, may include transmitting, to a parent node of the IAB node, full-duplex (FD) information based at least in part on a transmit power value for an FD mode; receiving an FD resource allocation for the IAB node, wherein the FD resource allocation identifies a resource to be used for a first communication link with the parent node and a second communication link in the FD mode, and wherein the FD resource allocation is based at least in part on the FD information; and communicating on the first communication link and the second communication link in accordance with the FD resource allocation.

In some aspects, a method of wireless communication, performed by an IAB node, may include receiving, from a child node of the IAB node, FD information based at least in part on a transmit power value for an FD mode; determining an FD resource allocation for the child node, wherein the FD resource allocation identifies a resource to be used for a first communication link with the child node and a second communication link in the FD mode, and wherein the FD resource allocation is based at least in part on the FD information; and transmitting information identifying the FD resource allocation to the child node.

In some aspects, an IAB node for wireless communication may include a memory; and one or more processors operatively coupled to the memory, the memory and the one or more processors configured to: transmit, to a parent node of the IAB node, FD information based at least in part on a transmit power value for an FD mode; receive an FD resource allocation for the IAB node, wherein the FD resource allocation identifies a resource to be used for a first communication link with the parent node and a second communication link in the FD mode, and wherein the FD resource allocation is based at least in part on the FD information; and communicate on the first communication link and the second communication link in accordance with the FD resource allocation.

In some aspects, an IAB node for wireless communication may include a memory; and one or more processors operatively coupled to the memory, the memory and the one or more processors configured to: receive, from a child node of the IAB node, FD information based at least in part on a transmit power value for an FD mode; determine an FD resource allocation for the child node, wherein the FD resource allocation identifies a resource to be used for a first communication link with the child node and a second communication link in the FD mode, and wherein the FD resource allocation is based at least in part on the FD information; and transmit information identifying the FD resource allocation to the child node.

In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of an IAB node, may cause the one or more processors to: transmit, to a parent node of the IAB node, FD information based at least in part on a transmit power value for an FD mode; receive an FD resource allocation for the IAB node, wherein the FD resource allocation identifies a resource to be used for a first communication link with the parent node and a second communication link in the FD mode, and wherein the FD resource allocation is based at least in part on the FD information; and communicate on the first communication link and the second communication link in accordance with the FD resource allocation.

In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of an IAB node, may cause the one or more processors to: receive, from a child node of the IAB node, full-duplex (FD) information based at least in part on a transmit power value for an FD mode; determine an FD resource allocation for the child node, wherein the FD resource allocation identifies a resource to be used for a first communication link with the child node and a second communication link in the FD mode, and wherein the FD resource allocation is based at least in part on the FD information; and transmit information identifying the FD resource allocation to the child node.

In some aspects, an apparatus for wireless communication may include means for transmitting, to a parent node of the apparatus, FD information based at least in part on a transmit power value for an FD mode; means for receiving an FD resource allocation for the apparatus, wherein the FD resource allocation identifies a resource to be used for a first communication link with the parent node and a second communication link in the FD mode, and wherein the FD resource allocation is based at least in part on the FD information; and means for communicating on the first communication link and the second communication link in accordance with the FD resource allocation.

In some aspects, an apparatus for wireless communication may include means for receiving, from a child node of the apparatus, FD information based at least in part on a transmit power value for an FD mode; means for determining an FD resource allocation for the child node, wherein the FD resource allocation identifies a resource to be used for a first communication link with the child node and a second communication link in the FD mode, and wherein the FD resource allocation is based at least in part on the FD information; and means for transmitting information identifying the FD resource allocation to the child node.

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

Based on the teachings herein one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure, all falling within the scope of the appended claims.

Controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform one or more techniques associated with data transfer for an IAB system using full-duplex, as described in more detail elsewhere herein. For example, controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform or direct operations of, for example, process <NUM> of <FIG>, process <NUM> of <FIG>, and/or other processes as described herein. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively. In some aspects, memory <NUM> and/or memory <NUM> may comprise a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, the one or more instructions, when executed by one or more processors of the base station <NUM> and/or the UE <NUM>, may perform or direction operations of, for example, process <NUM> of <FIG>, process <NUM> of <FIG>, and/or other processes as described herein.

In some aspects, UE <NUM> may include means for transmitting, to a parent node of the IAB node, full-duplex (FD) information based at least in part on a transmit power value for an FD mode; means for receiving an FD resource allocation for the IAB node, wherein the FD resource allocation identifies a resource to be used for a first communication link with the parent node and a second communication link in the FD mode, and wherein the FD resource allocation is based at least in part on the FD information; means for communicating on the first communication link and the second communication link in accordance with the FD resource allocation; means for transmitting non-FD information to the parent node; means for receiving a non-FD resource allocation from the parent node, wherein the non-FD resource allocation is based at least in part on the non-FD information; means for communicating on the first communication link and the second communication link using the non-FD resource allocation and the FD resource allocation; means for communicating on multiple second communication links with multiple receivers or transmitters in accordance with the FD resource allocation; and/or the like. In some aspects, such means may include one or more components of UE <NUM> described in connection with <FIG>, such as controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, and/or the like.

In some aspects, base station <NUM> may include means for receiving, from a child node of the IAB node, FD information based at least in part on a transmit power value for an FD mode; means for determining an FD resource allocation for the child node, wherein the FD resource allocation identifies a resource to be used for a first communication link with the child node and a second communication link in the FD mode, and wherein the FD resource allocation is based at least in part on the FD information; means for transmitting information identifying the FD resource allocation to the child node; means for determining the FD resource allocation using the reference signal and the transmit power reduction value; means for receiving non-FD information from the child node; means for transmitting a non-FD resource allocation to the child node, wherein the non-FD resource allocation is based at least in part on the non-FD information; means for determining the non-FD resource allocation using a reference signal transmitted by the child node; means for determining the FD resource allocation using the reference signal and the transmit power value; and/or the like. In some aspects, such means may include one or more components of base station <NUM> described in connection with <FIG>, such as antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like.

In a half-duplex IAB system, transmission and reception cannot be performed concurrently for an IAB node. This may constrain concurrent communication across certain types of communication links, as described in more detail below. When transmission and reception traffic are static or change slowly, the pattern for non-concurrent transmission and reception time slots can be determined according to the proportion of transmission traffic and reception traffic. However, when transmission and reception traffic are dynamic or change rapidly, such as when urgent traffic occurs in an inverse-direction time slot, such a non-concurrent transmission-reception pattern may fail to satisfy traffic requirements, such as latency requirements, reliability requirements, throughput requirements, and/or the like.

Some techniques and apparatuses described herein use full-duplex (FD) technology to provide concurrent transmission and reception at an IAB node. This enables dynamic traffic allocation, thereby providing improved system capacity and the capability to quickly deliver traffic in any direction (UL or DL) as the traffic changes direction.

Furthermore, it is challenging to decide the optimal transport format and transmit power in an IAB node chain where FD communication is activated at each IAB node, because the DL/UL metrics along the chain are coupled. Techniques and apparatuses described herein provide an efficient technique for the parent node of an IAB node chain to determine resource allocations, modulation and coding schemes, and/or the like for backhaul links toward a parent node based at least in part on an IAB node's feedback information regarding FD communication of the IAB node. Thus, FD performance is improved. Furthermore, techniques and apparatuses described herein provide self-interference control techniques by using transmit power values (e.g., transmit power reduction values or transmit power restriction values) to determine the resource allocations and/or configurations described above.

<FIG> is a diagram illustrating examples <NUM> of radio access networks, in accordance with various aspects of the disclosure.

As shown by reference number <NUM>, a traditional (e.g., <NUM>, <NUM>, LTE, and/or the like) radio access network may include multiple base stations <NUM> (e.g., access nodes (AN)), where each base station <NUM> communicates with a core network via a wired backhaul link <NUM>, such as a fiber connection. A base station <NUM> may communicate with a UE <NUM> via an access link <NUM>, which may be a wireless link. In some aspects, a base station <NUM> shown in <FIG> may correspond to a base station <NUM> shown in <FIG>. Similarly, a UE <NUM> shown in <FIG> may correspond to a UE <NUM> shown in <FIG>.

As shown by reference number <NUM>, a radio access network may include a wireless backhaul network, sometimes referred to as an integrated access and backhaul (IAB) network. In an IAB network, at least one base station is an anchor base station <NUM> that communicates with a core network via a wired backhaul link <NUM>, such as a fiber connection. An anchor base station <NUM> may also be referred to as an IAB donor (or IAB-donor). The IAB network may include one or more non-anchor base stations <NUM>, sometimes referred to as relay base stations or IAB nodes (or IAB-nodes). The non-anchor base station <NUM> may communicate directly or indirectly (e.g., via one or more non-anchor base stations <NUM>) with the anchor base station <NUM> via one or more backhaul links <NUM> to form a backhaul path to the core network for carrying backhaul traffic. Backhaul link <NUM> may be a wireless link. Anchor base station(s) <NUM> and/or non-anchor base station(s) <NUM> may communicate with one or more UEs <NUM> via access links <NUM>, which may be wireless links for carrying access traffic. In some aspects, an anchor base station <NUM> and/or a non-anchor base station <NUM> shown in <FIG> may correspond to a base station <NUM> shown in <FIG>. Similarly, a UE <NUM> shown in <FIG> may correspond to a UE <NUM> shown in <FIG>.

As shown by reference number <NUM>, in some aspects, a radio access network that includes an IAB network may utilize millimeter wave technology and/or directional communications (e.g., beamforming, precoding and/or the like) for communications between base stations and/or UEs (e.g., between two base stations, between two UEs, and/or between a base station and a UE). For example, wireless backhaul links <NUM> between base stations may use millimeter waves to carry information and/or may be directed toward a target base station using beamforming, precoding, and/or the like. Similarly, the wireless access links <NUM> between a UE and a base station may use millimeter waves and/or may be directed toward a target wireless node (e.g., a UE and/or a base station). In this way, inter-link interference may be reduced.

The configuration of base stations and UEs in <FIG> is shown as an example, and other examples are possible. For example, one or more base stations illustrated in <FIG> may be replaced by one or more UEs that communicate via a UE-to-UE access network (e.g., a peer-to-peer network, a device-to-device network, and/or the like). In this case, an anchor node may refer to a UE that is directly in communication with a base station (e.g., an anchor base station or a non-anchor base station).

Some techniques and apparatuses described herein provide FD communication among the nodes and/or UEs of the network shown in <FIG>.

<FIG> is a diagram illustrating an example <NUM> of communication links between IAB nodes and/or UEs of a network. As shown, example <NUM> includes a parent node <NUM>, an IAB node <NUM>, a child node <NUM>, and a UE <NUM>. Parent node <NUM>, IAB node <NUM>, and child node <NUM> may each be an IAB node (e.g., a BS <NUM>, a relay BS <NUM>, a wireless node, and/or the like). In some aspects, parent node <NUM> may be an IAB donor. Parent node <NUM> is a parent node of IAB node <NUM>, and child node <NUM> is a child node of IAB node <NUM>. Child node <NUM> may be referred to as a grandchild node of parent node <NUM>, and parent node <NUM> may be referred to as a grandparent node of child node <NUM>.

The nodes <NUM>, <NUM>, <NUM>, and the UE <NUM>, are associated with communication links between each other. Downlink (DL) communication links are shown by reference numbers <NUM>, <NUM>, and <NUM>. DL parent backhaul (BH) link <NUM> provides a DL backhaul (i.e., backhaul link) from parent node <NUM> to IAB node <NUM>. DL child BH link <NUM> provides a DL backhaul from IAB node <NUM> to child node <NUM>. DL access link <NUM> provides a DL access link from IAB node <NUM> to UE <NUM>. Uplink (UL) communication links are shown by reference numbers <NUM>, <NUM>, and <NUM>. UL parent backhaul (BH) link <NUM> provides a UL backhaul to parent node <NUM> from IAB node <NUM>. UL child BH link <NUM> provides a UL backhaul to IAB node <NUM> from child node <NUM>. UL access link <NUM> provides a UL access link to IAB node <NUM> from UE <NUM>.

Some techniques and apparatuses described herein provide configuration of FD communications on the communication links <NUM> through <NUM>, such as by IAB node <NUM> via links <NUM> and <NUM>, by IAB node <NUM> via links <NUM> and <NUM>, by IAB node <NUM> via links <NUM> and <NUM>, by IAB node <NUM> via links <NUM> and <NUM>, or via other combinations of links.

<FIG> is a call flow diagram illustrating an example <NUM> of configuration of downlink FD-mode communication between IAB nodes and/or UEs of a network. For a description of uplink FD-mode communication, refer to the description accompanying <FIG>. As shown, example <NUM> includes a parent node <NUM>, an IAB node <NUM>, a child node <NUM>, and a UE <NUM>.

As shown by reference number <NUM>, the parent node <NUM> may transmit a reference signal <NUM> to the IAB node <NUM>. In some aspects, the reference signal (RS) may include a channel state information (CSI) reference signal (CSI-RS) and/or the like. In some aspects, the parent node <NUM> may transmit multiple CSI-RSs to the IAB node <NUM> (e.g., corresponding to different resources for which the IAB node <NUM> is to determine feedback). In some aspects, the parent node <NUM> may provide a CSI report configuration to the IAB node <NUM>. The CSI report configuration may indicate a location of the CSI-RS, a format of the CSI report, a periodicity or trigger condition associated with the CSI report, and/or the like.

As shown by reference number <NUM>, the IAB node <NUM> may determine a transmit power value (shown here as a transmit power restriction value) for the FD mode. Furthermore, as shown by reference number <NUM>, the IAB node <NUM> may determine CSI for the non-FD mode and/or CSI for the FD mode. The transmit power restriction value may identify a maximum transmit power (sometimes expressed as P_tx_max) for an FD communication based at least in part on a self-interference condition at the IAB node <NUM>.

To determine the transmit power restriction value and the CSI, the IAB node <NUM> may determine a transmit power in a DL child BH to child node <NUM> or a DL access link to UE <NUM>. In some cases, the transmit power may be a static or fixed value. In some cases, the transmit power may be based at least in part on pathloss in the DL child BH link or the DL access link. The IAB node <NUM> may determine a self-interference strength from the transmitted signal on the DL child BH link or the DL access link to the DL parent BH link, based at least in part on the transmit power in the DL child BH link or the DL access link and a self-interference cancellation ratio of the IAB node <NUM>. For example, the self-interference strength may be equal to the transmit power in the DL child BH link or the DL access link subtracting the self-interference cancellation ratio. The IAB node <NUM> may determine CSI for the FD mode based at least in part on the self-interference strength and a channel status estimation using the CSI-RS received on the DL parent BH link. For example, if the self-interference strength is larger than interference-plus-noise power for the non-FD mode, the CSI derived from the CSI-RS for the non-FD mode may be degraded in accordance with the self-interference strength for the FD mode, to determine the CSI for the FD mode. Since this CSI for FD mode is based at least in part on the determined transmit power in a DL child BH to child node <NUM> or a DL access link to UE <NUM>, when executing the data transfer in DL parent link based at least in part on the report of this CSI, the actual transmit power in a DL child BH or a DL access link may not exceed the determined transmit power, and thus the determined transmit power is referred to as the transmit power restriction value.

As shown by reference number <NUM>, the IAB node <NUM> may provide CSI feedback to the parent node <NUM>. For example, the IAB node <NUM> may provide a CSI report indicating CSI values for the FD mode and/or for the non-FD mode.

As shown by reference number <NUM>, the parent node <NUM> may determine modulation and coding scheme (MCS) values and resource allocations for at least one of the FD mode and/or the non-FD mode. The MCS values and the resource allocations may be for the DL parent BH link. In some aspects, the parent node <NUM> may determine a first MCS value for the FD mode and a second MCS value for the non-FD mode. The first MCS value may be more conservative than the second MCS value (e.g., more robust, higher reliability, lower throughput, and/or the like) due to the increased self-interference in the FD zone relative to the non-FD zone. A more detailed description of the resource allocations for the FD mode and the non-FD mode in the DL is provided in connection with <FIG>.

As shown by reference number <NUM>, the parent node <NUM> may provide a downlink grant to the IAB node <NUM>. As further shown, the downlink grant may include an indication of whether the downlink grant is associated with the FD mode or the non-FD mode. The downlink grant may include information identifying the MCS value for the FD mode, the MCS value for the non-FD mode, the resource allocation for the FD mode, and/or the resource allocation for the non-FD mode.

A communication using the non-FD mode is shown by reference number <NUM>. For example, this communication may use the non-FD mode resource allocation and the non-FD mode MCS. This communication may occur contemporaneously with the FD mode communications shown by reference number <NUM> (e.g., using different frequency resources) or may occur on a same frequency resource as the FD mode communications shown by reference number <NUM> (e.g., using different time resources). Communications using the FD mode are shown within the dashed box indicated by reference number <NUM>. The IAB node <NUM> may schedule these communications in accordance with the transmit power restriction value for the FD mode and based at least in part on the resource allocations provided by the parent node <NUM>. As shown by reference number <NUM>, a DL parent BH link (sometimes referred to as a first communication link) between the parent node <NUM> and the IAB node <NUM> may use an FD resource. The FD resource may also be used for at least one of a DL child BH link (shown by reference number <NUM>) or a DL access link (shown by reference number <NUM>). In some aspects, one or more of the communication links shown by reference numbers <NUM> and <NUM> may be referred to as second communication links.

Thus, the parent node <NUM> determines MCS and resource allocations for an FD mode communication and/or a non-FD mode communication in accordance with CSI that is determined using a transmit power restriction value provided by the IAB node <NUM> for the FD mode and/or the non-FD mode. This may improve throughput, enables the handling of unexpected traffic in either link direction, and improves flexibility of the network.

<FIG> is a call flow diagram illustrating an example <NUM> of configuration of uplink FD-mode communication between IAB nodes and/or UEs of a network.

As shown by reference number <NUM>, the IAB node <NUM> may transmit a reference signal <NUM> to the parent node <NUM>. In some aspects, the reference signal <NUM> may include a sounding reference signal (SRS) and/or the like.

As shown by reference number <NUM>, the IAB node <NUM> may determine a transmit power value (shown here as a transmit power reduction value) for the FD mode. The transmit power reduction value may identify a reduction of a transmit power in the FD mode as an absolute value, or relative to the transmit power in the non-FD mode. To determine the transmit power reduction value, the IAB node <NUM> may determine an allowable self-interference strength at a receiver of the UL child BH link or the UL access link. In some cases, the allowable self-interference strength may be a static or fixed value. In some aspects, the allowable self-interference strength may be based at least in part on the received signal strength and target signal-to-interference-plus-noise ratio (SINR) on the UL child BH link or the UL access link. The IAB node <NUM> may determine the transmit power reduction value for the FD mode based at least in part on the allowable self-interference strength and a self-interference cancellation ratio of the IAB node <NUM>. Specifically, the transmit power for the FD mode may be equal to the allowable self-interference strength in the UL child BH link or the UL access link plus the self-interference cancellation ratio, and then the transmit power reduction value is equal to the transmit power for the non-FD mode subtracting the transmit power for the FD mode.

As shown by reference number <NUM>, the IAB node <NUM> may indicate the transmit power reduction value for the FD mode to the parent node <NUM>. For example, the IAB node <NUM> may use any suitable messaging format, such as a media access control (MAC) control element (CE) and/or the like. As shown by reference number <NUM>, the parent node <NUM> may determine modulation and coding scheme (MCS) values and resource allocations for at least one of the FD mode and/or the non-FD mode using the transmit power reduction value provided by the IAB node <NUM>. The MCS values and the resource allocations may be for communications between the parent node <NUM> and the IAB node <NUM> on the UL parent BH link. In some aspects, the parent node <NUM> may determine a first MCS value for the FD mode and a second MCS value for the non-FD mode. The first MCS value may be more conservative than the second MCS value (e.g., more robust, higher reliability, lower throughput, etc.) due to the reduced transmit power in the FD zone relative to the non-FD zone. A more detailed description of the resource allocations for the FD mode and the non-FD mode in the DL is provided in connection with <FIG>.

In some aspects, the parent node <NUM> may determine the MCS and resource allocation based at least in part on the SRS. For example, the parent node <NUM> may determine a channel status estimation using the SRS on the UL parent BH link. The parent node <NUM> may determine the MCS and the resource allocation for the non-FD mode based at least in part on the channel status estimation. The parent node <NUM> may determine the MCS and resource allocation for the FD mode based at least in part on the channel status estimation and the received transmit power reduction value. For example, the transmit power at FD mode may be determined to be equal to the transmit power at non-FD mode subtracting the transmit power reduction value. Thus, the parent node <NUM> may determine a more conservative (e.g., lower, more robust) MCS value for the FD zone on the UL parent BH link based at least in part on the lower transmit power in the FD zone.

As shown by reference number <NUM>, the parent node <NUM> may provide an uplink grant to the IAB node <NUM>. As further shown, the uplink grant may include an indication of whether the uplink grant is associated with the FD mode or the non-FD mode. The uplink grant may include information identifying the MCS value for the FD mode, the MCS value for the non-FD mode, the resource allocation for the FD mode, and/or the resource allocation for the non-FD mode.

A communication using the non-FD mode is shown by reference number <NUM>. For example, this communication may use the non-FD mode resource allocation and the non-FD mode MCS. This communication may occur contemporaneously with the FD mode communications shown by reference number <NUM> (e.g., using different frequency resources) or may occur on a same frequency resource as the FD mode communications shown by reference number <NUM> (e.g., using different time resources).

Communications using the FD mode are shown within the dashed box indicated by reference number <NUM>. As shown by reference number <NUM>, a UL parent BH link (sometimes referred to as a first communication link) between the parent node <NUM> and the IAB node <NUM> may use an FD resource. The IAB node <NUM> may transmit communications on the UL parent BH link using the transmit power reduction value. The FD resource may also be used for at least one of a UL child BH link (shown by reference number <NUM>) or a UL access link (shown by reference number <NUM>). In some aspects, one or more of the communication links shown by reference numbers <NUM> and <NUM> may be referred to as second communication links.

Thus, the parent node <NUM> determines MCS and resource allocations for an FD mode communication and/or a non-FD mode communication in accordance with SRS and/or a transmit power reduction value provided by the IAB node <NUM> for the FD mode and/or the non-FD mode. This may improve throughput, enables the handling of unexpected traffic in either link direction, and improves flexibility of the network.

<FIG> is a diagram illustrating an example <NUM> of an IAB node radio resource division in the time domain. Resources on a variety of BH and access links are shown by reference numbers <NUM> through <NUM> (referring back to <FIG>). For example, example <NUM> shows that the DL parent BH link <NUM> may carry at least one of a non-FD communication <NUM> and an FD communication <NUM>, which are separated in time and concurrent in frequency. The non-FD communication <NUM> and the FD communication <NUM> may be associated with different interference levels and thus different MCSs. Furthermore, a FD communication <NUM>, on the DL child BH link <NUM> may self-interfere with the FD communication <NUM> on the DL parent BH link <NUM> as shown by reference number <NUM>. This is because the IAB node <NUM> (not shown in <FIG>), which transmits the FD communication <NUM> on the DL child BH link <NUM> to the child node <NUM> (not shown in <FIG>), may self-interfere with reception of the FD communication <NUM> on the DL parent BH link <NUM>. Similar self-interference may occur due to the IAB node <NUM>'s FD communication to the UE <NUM> on the DL access link <NUM>, which may interfere with the FD communication from the parent node <NUM> on the DL parent BH <NUM>. Furthermore, it can be seen that similar self interference may occur on the uplink, such as an FD communication on the UL parent BH <NUM> interfering with the FD communication from the child node <NUM> on the UL child BH <NUM> and the FD communication on the UL parent BH <NUM> interfering with the FD communication from the UE <NUM> on the UL access link <NUM>. On the uplink, different transmit powers in the FD mode and the non-FD mode may cause different MCS values for the non-FD communication and the FD communication.

<FIG> is a diagram illustrating an example <NUM> of an IAB node radio resource division in the frequency domain. Resources on a variety of BH and access links are shown by reference numbers <NUM> through <NUM> (referring back to <FIG>). For example, example <NUM> shows that the DL parent BH link <NUM> may carry at least one of a non-FD communication <NUM> and an FD communication <NUM>, which are separated in frequency and concurrent in time. The self-interference of the FD mode communications and the non-FD mode communications, and the differences in interference, transmit power, and MCS between the FD communications and the non-FD communications, are described in more detail in connection with <FIG>.

<FIG> is a diagram illustrating an example <NUM> of downlink FD data transfer for concatenated IAB nodes. As shown, <FIG> includes an IAB donor <NUM> (e.g., parent node <NUM>, BS <NUM>, anchor base station <NUM>, and/or the like), IAB nodes <NUM>-<NUM> and <NUM>-<NUM> (e.g., parent node <NUM>, IAB node <NUM>, child node <NUM>, and/or the like), and a UE <NUM>. As shown by reference number <NUM>, a DL parent BH link is provided from IAB donor <NUM> to IAB node <NUM>-<NUM> (denoted as DL parent BH <NUM> to distinguish from the DL Parent BH link from IAB node <NUM>-<NUM> to IAB node <NUM>-<NUM>). As shown by reference number <NUM>, a DL child BH link is provided from IAB node <NUM>-<NUM> to IAB node <NUM>-<NUM>. This link is also shown as a DL parent BH link, since IAB node <NUM>-<NUM> is a parent node to IAB node <NUM>-<NUM>, which is a parent node to UE <NUM> (e.g., via DL access link <NUM>).

As shown by reference number <NUM>, IAB node <NUM>-<NUM> may report CSI for the FD mode and for the non-FD mode to IAB donor <NUM>. Similarly, IAB node <NUM>-<NUM> may report CSI for the FD mode and for the non-FD mode to IAB node <NUM>-<NUM>, and UE <NUM> may report CSI for the non-FD mode (since UE <NUM> does not perform FD communication) to the IAB node <NUM>-<NUM>. Accordingly, IAB donor <NUM> may handle scheduling and MCS determination on DL parent BH link <NUM>, IAB node <NUM>-<NUM> may handle scheduling and MCS determination on DL child BH link <NUM>, and IAB node <NUM>-<NUM> may handle scheduling and MCS determination on DL access link <NUM>.

The timeline shown by reference number <NUM> illustrates communications on the DL parent BH <NUM> link <NUM>, the timeline shown by reference number <NUM> illustrates communications on the DL parent BH <NUM> link <NUM>, and the timeline shown by reference number <NUM> illustrates communications on the DL access link <NUM>. Reference number <NUM> indicates another example of a communication between IAB nodes <NUM>-<NUM> and <NUM>-<NUM> and UE <NUM>.

As shown, self-interference may occur at IAB node <NUM>-<NUM> from the FD communication to IAB node <NUM>-<NUM> on the DL child BH <NUM> link <NUM>. Furthermore, self-interference may occur at IAB node <NUM>-<NUM> on the FD communication with the IAB node <NUM>-<NUM> due to the FD communication to the UE <NUM> on the DL access link <NUM>, which may be concurrent with the FD communication with the IAB node <NUM>-<NUM>. The interference mitigation and FD communication scheduling techniques described herein may mitigate interference in multi-hop scenarios by providing different MCSs for non-FD and FD communications, scheduling a combination of non-FD and FD communications, and/or the like.

<FIG> is a call flow diagram illustrating an example <NUM> of uplink FD data transfer for concatenated IAB nodes. Reference numbers for IAB donor <NUM> and IAB nodes <NUM>-<NUM> and <NUM>-<NUM> are reproduced from <FIG>. As shown, a UL parent BH <NUM> link <NUM> is provided between IAB donor <NUM> and IAB node <NUM>-<NUM>, a UL child BH <NUM> link <NUM> (also shown as a UL parent BH <NUM> link) is provided between IAB node <NUM>-<NUM> and IAB node <NUM>-<NUM>, and a UL access link <NUM> is provided between IAB node <NUM>-<NUM> and UE <NUM>.

As shown by reference number <NUM>, IAB node <NUM>-<NUM> may transmit an SRS and/or information indicating a transmit power value (e.g., a transmit power reduction value) to IAB donor <NUM>. Similarly, IAB node <NUM>-<NUM> may transmit the SRS and the transmit power value to IAB node <NUM>-<NUM>, and UE <NUM> may transmit only an SRS (since UE <NUM> does not perform FD communication) to the IAB node <NUM>-<NUM>. Accordingly, IAB donor <NUM> may handle scheduling and MCS determination on UL parent BH 1link <NUM>, IAB node <NUM>-<NUM> may handle scheduling and MCS determination on UL child BH <NUM> link <NUM>, and IAB node <NUM>-<NUM> may handle scheduling and MCS determination on UL access link <NUM>.

The timeline shown by reference number <NUM> illustrates communications on the UL parent BH <NUM> link <NUM>, the timeline shown by reference number <NUM> illustrates communications on the UL parent BH <NUM> link <NUM>, and the timeline shown by reference number <NUM> illustrates communications on the UL access link <NUM>. Reference number <NUM> indicates another example of a communication between IAB nodes <NUM>-<NUM> and <NUM>-<NUM> and UE <NUM>.

As shown, self-interference may occur at IAB node <NUM>-<NUM> due to the FD communication on the UL child BH <NUM> link <NUM>. The self-interference may occur on the UL child BH <NUM> link <NUM> for an FD communication. Furthermore, self-interference may occur at IAB node <NUM>-<NUM> due to the FD communication with the IAB node <NUM>-<NUM>. The self-interference may occur on the UL access link <NUM>, which may be concurrent with the FD communication with the IAB node <NUM>-<NUM>. The interference mitigation and FD communication scheduling techniques described herein may mitigate interference in multi-hop scenarios by providing different MCSs for non-FD and FD communications, scheduling a combination of non-FD and FD communications, and/or the like.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by an IAB node, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where an IAB node (e.g., BS <NUM>, UE <NUM>, parent node <NUM>, IAB node <NUM>, child node <NUM>, IAB node <NUM>, and/or the like) performs operations associated with data transfer for an IAB system using full-duplex.

As shown in <FIG>, in some aspects, process <NUM> may include transmitting, to a parent node of the IAB node, full-duplex (FD) information based at least in part on a transmit power value for an FD mode (block <NUM>). For example, the IAB node (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may transmit, to a parent node of the IAB node, full-duplex (FD) information based at least in part on a transmit power value for an FD mode, as described above.

As shown in <FIG>, in some aspects, process <NUM> may include transmitting non-FD information to the parent node (block <NUM>). For example, the IAB node (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may transmit, to a parent node of the IAB node, non-FD information.

As further shown in <FIG>, in some aspects, process <NUM> may include receiving an FD resource allocation for the IAB node, wherein the FD resource allocation identifies a resource to be used for a first communication link with the parent node and a second communication link in the FD mode, and wherein the FD resource allocation is based at least in part on the FD information (block <NUM>). For example, the IAB node (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may receive an FD resource allocation for the IAB node, as described above. In some aspects, the FD resource allocation identifies a resource to be used for a first communication link with the parent node and a second communication link in the FD mode. In some aspects, the FD resource allocation is based at least in part on the FD information.

As shown in <FIG>, in some aspects, process <NUM> may include receiving a non-FD resource allocation from the parent node, wherein the non-FD resource allocation is based at least in part on the non-FD information (block <NUM>). For example, the IAB node (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may receive a non-FD resource allocation from the parent node. The non-FD resource allocation may be based at least in part on the non-FD information.

As further shown in <FIG>, in some aspects, process <NUM> may include communicating on the first communication link and the second communication link in accordance with the FD resource allocation (block <NUM>). For example, the IAB node (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may communicate on the first communication link and the second communication link in accordance with the FD resource allocation, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include communicating on the first communication link and the second communication link using the non-FD resource allocation and the FD resource allocation (block <NUM>). For example, the IAB node (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may communicate on the first communication link and the second communication link using the non-FD resource allocation and the FD resource allocation.

As further shown in <FIG>, in some aspects, process <NUM> may include communicating on multiple second communication links with multiple receivers or transmitters in accordance with the FD resource allocation (block <NUM>). For example, the IAB node (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may communicate on multiple second communication links with multiple receivers or transmitters in accordance with the FD resource allocation.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by an IAB node, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where an IAB node (e.g., BS <NUM>, UE <NUM>, parent node <NUM>, IAB node <NUM>, child node <NUM>, donor node <NUM>, IAB node <NUM>, and/or the like) performs operations associated with data transfer for an IAB system using full-duplex.

As shown in <FIG>, in some aspects, process <NUM> may include receiving, from a child node of the IAB node, FD information based at least in part on a transmit power value for an FD mode (block <NUM>). For example, the IAB node (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may receive, from a child node of the IAB node, FD information based at least in part on a transmit power value for an FD mode, as described above. The FD information may include, for example, a CSI report, an SRS, information identifying a transmit power value (e.g., a transmit power restriction or a transmit power reduction value), and/or the like.

As further shown in <FIG>, in some aspects, process <NUM> may include receiving non-FD information from the child node (block <NUM>). For example, the IAB node (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may receive non-FD information from the child node, as described above. The non-FD information may include, for example, a CSI report, an SRS, and/or the like.

As further shown in <FIG>, in some aspects, process <NUM> may include determining an FD resource allocation for the child node, wherein the FD resource allocation identifies a resource to be used for a first communication link with the child node and a second communication link in the FD mode, and wherein the FD resource allocation is based at least in part on the FD information (block <NUM>). For example, the IAB node (e.g., using controller/processor <NUM> and/or the like) may determine an FD resource allocation for the child node, as described above. In some aspects, the FD resource allocation identifies a resource to be used for a first communication link with the child node and a second communication link in the FD mode. In some aspects, the FD resource allocation is based at least in part on the FD information.

As further shown in <FIG>, in some aspects, process <NUM> may include determining a non-FD resource allocation using a reference signal transmitted by the child node (block <NUM>). For example, the IAB node (e.g., using controller/processor <NUM> and/or the like) may determine the non-FD resource allocation using a reference signal transmitted by the child node, as described above. In some aspects, the IAB node (e.g., using controller/processor <NUM> and/or the like) may determine the FD resource allocation using the reference signal and the transmit power reduction value.

As further shown in <FIG>, in some aspects, process <NUM> may include transmitting information identifying the FD resource allocation to the child node (block <NUM>). For example, the IAB node (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may transmit information identifying the FD resource allocation to the child node, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include transmitting the non-FD resource allocation to the child node, wherein the non-FD resource allocation is based at least in part on the non-FD information (block <NUM>). For example, the IAB node (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may transmit the non-FD resource allocation to the child node, wherein the non-FD resource allocation is based at least in part on the non-FD information, as described above. In some aspects, the IAB node may communicate with the child node and/or another node using the FD resource allocation and/or the non-FD resource allocation.

Modifications and variations may be made in light of the above disclosure and within the scope of the appended claims.

Claim 1:
A method (<NUM>) of wireless communication performed by an integrated access and backhaul, IAB, node (<NUM>), comprising:
transmitting (<NUM>), to a parent node (<NUM>) of the IAB node, full-duplex, FD, information based at least in part on a transmit power value for an FD mode;
receiving (<NUM>) an FD resource allocation for the IAB node, wherein the FD resource allocation identifies a resource to be used for a first communication link with the parent node in the FD mode and a second communication link with a child node (<NUM>) of the IAB node or an access link to a User Equipment, UE, (<NUM>) in the FD mode, and wherein the FD resource allocation is based at least in part on the FD information; and
communicating (<NUM>) on the first communication link and the second communication link in accordance with the FD resource allocation.