Patent Description:
"Downlink" (or "forward link") refers to the communication link from the BS to the UE, and "uplink" (or "reverse link") refers to the communication link from the UE to the BS, as for example described in 3GPP R3-<NUM> and 3GPP R3-<NUM>.

Embodiments and aspects that do not fall within the scope of the claims are merely examples used for explanation of the invention. Wording such as "may" and "for example" used in the description in conjunction with features of the independent claims should not be interpreted to mean that those features are merely optional. In some aspects, a method of wireless communication performed by a network node includes transmitting, to an integrated access and backhaul (IAB) donor central unit (CU), information indicating a cell served by the network node and associated with another CU; and receiving, from the IAB donor CU, a distributed unit (DU) cell resource configuration for the cell.

In some aspects, a method of wireless communication performed by an IAB donor CU includes receiving, from a network node, information indicating a cell served by the network node and associated with another CU; and transmitting, to the network node, a DU cell resource configuration for the cell.

In some aspects, a network node for wireless communication includes a memory and one or more processors coupled to the memory, the one or more processors configured to: transmit, to an IAB donor CU, information indicating a cell served by the network node and associated with another CU; and receive, from the IAB donor CU, a DU cell resource configuration for the cell.

In some aspects, an IAB donor CU for wireless communication includes a memory and one or more processors coupled to the memory, the one or more processors configured to: receive, from a network node, information indicating a cell served by the network node and associated with another CU; and transmit, to the network node, a DU cell resource configuration for the cell.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to: transmit, to an IAB donor CU, information indicating a cell served by the network node and associated with another CU; and receive, from the IAB donor CU, a DU cell resource configuration for the cell.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of an IAB donor CU, cause the IAB donor CU to: receive, from a network node, information indicating a cell served by the network node and associated with another CU; and transmit, to the network node, a DU cell resource configuration for the cell.

In some aspects, an apparatus for wireless communication includes means for transmitting, to an IAB donor CU, information indicating a cell served by the apparatus and associated with another CU; and means for receiving, from the IAB donor CU, a DU cell resource configuration for the cell.

In some aspects, an apparatus for wireless communication includes means for receiving, from a network node, information indicating a cell served by the network node and associated with another CU; and means for transmitting, to the network node, a DU cell resource configuration for the cell.

While aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios. Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements. For example, some aspects may be implemented via integrated chip embodiments or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, or artificial intelligence-enabled devices). Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, or system-level components. Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals may include a number of components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processor(s), interleavers, adders, or summers). It is intended that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, or end-user devices of varying size, shape, and constitution.

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, 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 include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the base station <NUM> and/or the UE <NUM>, may cause the one or more processors, the UE <NUM>, and/or the base station <NUM> to perform or direct operations of, for example, process <NUM> of <FIG>, process <NUM> of <FIG>, and/or other processes as described herein. In some aspects, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

In some aspects, a network node (e.g., BS <NUM>) includes means for transmitting, to an integrated access and backhaul (IAB) donor central unit (CU), information indicating a cell served by the network node and associated with another CU; and/or means for receiving, from the IAB donor CU, a distributed unit (DU) cell resource configuration for the cell. The means for the network node to perform operations described herein may include, for example, transmit processor <NUM>, TX MIMO processor <NUM>, modulator <NUM>, antenna <NUM>, demodulator <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or scheduler <NUM>.

In some aspects, the network node includes means for communicating on the cell based at least in part on the DU cell resource configuration. In some aspects, the network node includes means for providing service to a child node of the network node, wherein the child node is associated with a radio resource control connection to the other CU. In some aspects, the network node includes means for receiving an indication, from the other CU, that the cell is activated; and/or means for communicating on the cell based at least in part on the DU cell resource configuration and based at least in part on receiving the indication. In some aspects, the network node includes means for transmitting, to the IAB donor CU, information indicating an activation status of the cell based at least in part on receiving the indication. In some aspects, the network node includes means for receiving, from the other CU, configuration information for the cell; and/or means for transmitting, to the IAB donor CU, at least part of the configuration information, wherein the DU cell resource configuration is based at least in part on the configuration information. In some aspects, the network node includes means for communicating with a parent node of the network node based at least in part on configuration information associated with the cell.

In some aspects, the IAB donor CU includes means for receiving, from a network node, information indicating a cell served by the network node and associated with another CU; and/or means for transmitting, to the network node, a DU cell resource configuration for the cell. The means for the IAB donor CU to perform operations described herein may include, for example, transmit processor <NUM>, TX MIMO processor <NUM>, modulator <NUM>, antenna <NUM>, demodulator <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or scheduler <NUM>.

In some aspects, the IAB donor CU includes means for receiving, from the network node, information indicating an activation status of the cell. In some aspects, the IAB donor CU includes means for receiving, from the network node, configuration information for the cell, wherein the DU cell resource configuration is based at least in part on the configuration information. In some aspects, the IAB donor CU includes means for transmitting, to a parent node of the network node, configuration information regarding the cell.

<FIG> is a diagram illustrating examples <NUM> of radio access networks, in accordance with 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 be a base station <NUM> shown in <FIG>. In some aspects, a UE <NUM> shown in <FIG> may be 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 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 with the anchor base station <NUM> via one or more backhaul links <NUM> (e.g., via one or more non-anchor base stations <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 be a base station <NUM> shown in <FIG>. In some aspects, a UE <NUM> shown in <FIG> may be 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 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 wave signals to carry information and/or may be directed toward a target base station using beamforming and/or the like. Similarly, the wireless access links <NUM> between a UE and a base station may use millimeter wave signals 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 contemplated. 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, "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).

<FIG> is a diagram illustrating an example <NUM> of an IAB network architecture, in accordance with the disclosure.

As shown in <FIG>, an IAB network may include an IAB donor <NUM> (shown as IAB-donor) that connects to a core network via a wired connection (shown as a wireline backhaul). For example, an Ng interface (e.g., a user plane interface between the next generation radio access network (NG-RAN) node and the user plane function) of an IAB donor <NUM> may terminate at a core network. Additionally, or alternatively, an IAB donor <NUM> may connect to one or more devices of the core network that provide a core access and mobility management function (AMF). In some aspects, an IAB donor <NUM> may include a base station <NUM>, such as an anchor base station, as described above in connection with <NUM>. As shown, an IAB donor <NUM> may include a CU, which may perform access node controller (ANC) functions, AMF functions, and/or the like. The CU may configure a DU of the IAB donor <NUM> and/or may configure one or more IAB nodes <NUM> (e.g., an mobile termination (MT) and/or a DU of an IAB node <NUM>) that connect to the core network via the IAB donor <NUM>. Thus, a CU of an IAB donor <NUM> may control and/or configure the entire IAB network that connects to the core network via the IAB donor <NUM>, such as by using control messages and/or configuration messages (e.g., a radio resource control (RRC) configuration message, an F1 application protocol (F1AP) message, and/or the like). An IAB node may function as a Layer <NUM> relay for traffic transported via an IAB network configured or managed by a CU.

A CU (whether associated with an IAB donor or a gNB) may perform RRC layer functions and packet data convergence protocol (PDCP) functions. A DU may act as a scheduling node that schedules child nodes of a network node associated with the DU. For example, the DU may perform radio link control (RLC), medium access control (MAC), and physical (PHY) layer functions.

As further shown in <FIG>, the IAB network may include IAB nodes <NUM> (shown as IAB-node <NUM>, IAB-node <NUM>, and IAB-node <NUM>) that connect to the core network via the IAB donor <NUM>. As shown, an IAB node <NUM> may include MT functions (also sometimes referred to as UE functions (UEF)) and may include DU functions (also sometimes referred to as access node functions (ANF)). The MT functions of an IAB node <NUM> (e.g., a child node) may be controlled and/or scheduled by another IAB node <NUM> (e.g., a parent node of the child node) and/or by an IAB donor <NUM>. The DU functions of an IAB node <NUM> (e.g., a parent node) may control and/or schedule other IAB nodes <NUM> (e.g., child nodes of the parent node) and/or UEs <NUM>. Thus, a DU may be referred to as a scheduling node or a scheduling component, and an MT may be referred to as a scheduled node or a scheduled component. In some aspects, an IAB donor <NUM> may include DU functions and not MT functions. That is, an IAB donor <NUM> may configure, control, and/or schedule communications of IAB nodes <NUM> and/or UEs <NUM>. A UE <NUM> may include only MT functions, and not DU functions. That is, communications of a UE <NUM> may be controlled and/or scheduled by an IAB donor <NUM> and/or an IAB node <NUM> (e.g., a parent node of the UE <NUM>).

When a first node controls and/or schedules communications for a second node (e.g., when the first node provides DU functions for the second node's MT functions), 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. A child node of the second node may be referred to as a grandchild node of the first node. Thus, a DU function of a parent node may control and/or schedule communications for child nodes of the parent node. A parent node may be an IAB donor <NUM> or an IAB node <NUM>, and a child node may be an IAB node <NUM> or a UE <NUM>. Communications of an MT function of a child node may be controlled and/or scheduled by a parent node of the child node.

As further shown in <FIG>, a link between a UE <NUM> (e.g., which only has MT functions, and not DU functions) and an IAB donor <NUM>, or between a UE <NUM> and an IAB node <NUM>, may be referred to as an access link <NUM>. Access link <NUM> may be a wireless access link that provides a UE <NUM> with radio access to a core network via an IAB donor <NUM>, and optionally via one or more IAB nodes <NUM>. Thus, the network illustrated in <NUM> may be referred to as a multi-hop network or a wireless multi-hop network.

As further shown in <FIG>, a link between an IAB donor <NUM> and an IAB node <NUM> or between two IAB nodes <NUM> may be referred to as a backhaul link <NUM>. Backhaul link <NUM> may be a wireless backhaul link that provides an IAB node <NUM> with radio access to a core network via an IAB donor <NUM>, and optionally via one or more other IAB nodes <NUM>. In an IAB network, network resources for wireless communications (e.g., time resources, frequency resources, spatial resources, and/or the like) may be shared between access links <NUM> and backhaul links <NUM>. In some aspects, a backhaul link <NUM> may be a primary backhaul link or a secondary backhaul link (e.g., a backup backhaul link). In some aspects, a secondary backhaul link may be used if a primary backhaul link fails, becomes congested, becomes overloaded, and/or the like. For example, a backup link <NUM> between IAB-node <NUM> and IAB-node <NUM> may be used for backhaul communications if a primary backhaul link between IAB-node <NUM> and IAB-node <NUM> fails. As used herein, "node" or "wireless node" may refer to an IAB donor <NUM> or an IAB node <NUM>.

<FIG> is a diagram illustrating an example <NUM> of resource types in an IAB network, in accordance with the disclosure.

In an IAB network, time domain resources (sometimes referred to as time resources) may be configured as downlink-only, uplink-only, flexible, or not available (e.g., NA, unavailable). For example, time domain resources may be configured via a DU cell resource configuration, such as a gNB-DU cell resource configuration, as described in more detail in connection with <FIG>. When a time resource is configured as downlink-only for a wireless node, that time resource may be available for only downlink communications of the wireless node, and not uplink communications. Similarly, when a time resource is configured as uplink-only for a wireless node, that time resource may be available for only uplink communications of the wireless node, and not downlink communications. When a time resource is configured as flexible for a wireless node, that time resource may be available for both downlink communications and uplink communications of the wireless node. When a time resource is configured as not available for a wireless node, that time resource may not be used for any communications of the wireless node.

Examples of downlink communications include synchronization signal blocks (SSBs) (both cell defining SSBs (CD-SSBs) and non-CD-SSBs), channel state information reference signals (CSI-RS), physical downlink control channel (PDCCH) communications, physical downlink shared channel (PDSCH) communications, and/or the like. Examples of uplink communications include physical random access channel (PRACH) communications, physical uplink control channel (PUCCH) communications, physical uplink shared channel (PUSCH) communications, sounding reference signals (SRS), and/or the like.

Time resources in an IAB network that are configured as downlink-only, uplink-only, or flexible may be further configured as hard resources or soft resources. When a time resource is configured as a hard resource for a wireless node, that time resource is always available for communications of the wireless node. For example, a hard downlink-only time resource is always available for only downlink communications of the wireless node, a hard uplink-only time resource is always available for only uplink communications of the wireless node, and a hard flexible time resource is always available for uplink and downlink communications of the wireless node.

When a time resource is configured as a soft resource for a wireless node, the availability of that time resource is controlled by a parent node of the wireless node. For example, the parent node may indicate (e.g., explicitly or implicitly) whether a soft time resource is available for communications of the wireless node. Thus, a soft time resource may be in one of two states: a schedulable state (e.g., when the soft time resource is available for scheduling and/or communications 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 communications of the wireless node).

For example, a soft downlink-only time resource is only available for downlink communications of the wireless node when a parent node of the wireless node indicates that the soft downlink-only time resource is available. Similarly, a soft uplink-only time resource is only available for uplink communications of the wireless node when a parent node of the wireless node indicates that the soft uplink-only time resource is available. A soft flexible time resource is only available for uplink and downlink communications of the wireless node when a parent node of the wireless node indicates that the soft flexible time resource is available.

As an example, and as shown by reference number <NUM>, a time resource may be configured as hard for a child node and may be configured as not available for a parent node of the child node. In this case, the parent node cannot communicate using that time resource, but the child node can schedule communications in that time resource and/or communicate using that time resource. This configuration may reduce interference between the parent node and the child node, may reduce scheduling conflicts between the parent node and the child node, and/or the like.

As another example, and as shown by reference number <NUM>, a time resource may be configured as not available for the child node, and may be configured as hard, soft, or not available for the parent node (e.g., depending on a network configuration, network conditions, a configuration of a parent node of the parent node, and/or the like). In this case, the child node cannot schedule communications in that time resource and cannot communicate using that time resource.

As another example, and as shown by reference number <NUM>, a time resource may be configured as soft for the child node, and may be configured as hard, soft, or not available for the parent node (e.g., depending on a network configuration, network conditions, a configuration of a parent node of the parent node, and/or the like). In this case, the child node cannot schedule or communicate using the time resource unless the child node receives an indication (e.g., a release indication), from the parent node (e.g., explicitly or implicitly), that the time resource is available (i.e., released) for use by the child node. If the child node receives such an indication, then the child node can schedule communications in that time resource and/or communicate using that time resource.

<FIG> is a diagram illustrating an example <NUM> of DU cell resource configuration for IAB, in accordance with the present disclosure. Example <NUM> includes an IAB-donor CU. The IAB-donor CU may be associated with a gNB. The IAB-donor CU may handle resource configuration for the parent DU and the IAB node. Thus, the IAB-donor CU may accommodate half-duplex constraints of the parent DU, the IAB node, and/or other nodes of the IAB network.

The IAB-donor CU may provide a resource configuration via a cell resource configuration, shown as "gNB-DU cell resource configuration. " In some aspects, as shown by reference number <NUM>, the cell resource configuration may be specific to a cell. For example, the IAB-donor CU may provide a respective cell resource configuration for each cell served by a DU. The cell resource configuration may indicate at least part of the information described with regard to <FIG>.

The term "cell" may refer to a logical communication entity used for communication with a base station (e.g., over a carrier), and may be associated with an identifier for distinguishing neighboring cells operating via the same or a different carrier. In some examples, the cells may support different service and/or device types (e.g., MTC, narrowband Internet-of-Things (NB-IoT), enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and others). In some cases, the term "cell" may refer to a portion of a geographic coverage area (e.g., a sector) over which the logical entity operates. A cell may be referred to as "served by" a DU if the DU handles scheduling for communications via the cell.

A cell may have a cell global identifier (CGI), such as an NR CGI (NCGI). The NCGI uniquely identifies a cell. The NCGI includes a public land mobile networks (PLMN) identifier and an NR cell identifier. The PLMN identifier (which may include <NUM> bits) may include an MCC (e.g., <NUM> bits) and an MNC (e.g., <NUM> bits). The NCI (e.g., <NUM> bits in <NUM>) may include a gNB identifier (e.g., a leftmost <NUM> to <NUM> bits) and a local cell identifier (e.g., the remaining bits of the NCI). The gNB may be unique within a gNB, and may be common for all cells (e.g., all IAB-donor DUs and all IAB-node DUs) served by the gNB with one IAB-donor CU. Equivalently, the PLMN and gNB ID may globally identify a gNB.

<FIG> is a diagram illustrating an example <NUM> of radio access network (RAN) sharing for IAB, in accordance with the present disclosure.

As shown in <FIG>, in a RAN sharing scenario, there may be two CUs: an IAB donor CU1 (referred to as a CU1) and a gNB CU2 (referred to as a CU2). CU1 may be associated with an enhanced gNB that supports IAB functionality. CU2 may be associated with an access network gNB or an IAB-supporting gNB. CU2 may treat the DUs of the parent DU and the IAB-node (shown as DU2) as wireline DUs. In other words, in some cases, CU2 may not know that the DUs of example <NUM> are part of an IAB network and are associated with a wireless backhaul. For example, CU2 may communicate with the DUs of the parent DU and the IAB-node based at least in part on an F1 control (F1-C) protocol or an RRC protocol in the Internet Protocol (IP) layer. In some aspects, CU1 and CU2 may be associated with different networks, such as different PLMNs or different non-public networks (NPNs). In some aspects, CU1 and CU2 may be associated with the same network, such as the same PLMN or the same NPN. In some aspects, CU1 and CU2 may be associated with different mobile network operators. In some aspects, the parent DUs of the IAB node may be associated with the IAB-donor CU1. For example, the parent DUs may be implemented by a gNB associated with the IAB-donor CU1. In some aspects, the parent DUs of the IAB node may be associated with a parent node of the IAB node.

In some aspects, a cell may be associated with one CU (e.g., IAB-donor CU1) and another cell associated with another CU (e.g., gNB-CU2) may be served on the same physical resources (e.g., the same antenna, the same transmit or receive resources, the same network node, and/or the like). In some aspects, the same cell may serve children of two CUs. In this example, the cell may be associated with multiple NCIs (but may still have a unique NCGI).

CU1 may provide cell resource configurations for the parent DU and the IAB-node, since CU1 supports IAB functionality. Thus, CU1 may accommodate half-duplex constraints of the parent DU and/or the IAB node. However, if an IAB node is associated with DUs that are associated with two or more different CUs (such as CU1 and CU2 of example <NUM>), then a cell associated with a first CU may cause interference with a cell associated with a second CU. For example, an IAB node may be associated with a RAN sharing configuration and may be associated with two or more CUs. Thus, if an IAB-donor CU is not aware that an IAB node is associated with DUs associated with multiple different CUs, the IAB-donor CU may provide a cell resource configuration that causes interference between cells associated with DUs associated with different CUs. Such interference may diminish throughput, cause radio link failure, and necessitate aggressive interference mitigation, thus consuming network resources.

Some techniques and apparatuses described herein according to the present invention provide signaling that enables an IAB node to indicate, to an IAB donor CU associated with the IAB node, that the IAB node is associated with one or more cells or DUs that are associated with multiple CUs. Thus, the IAB donor CU can provide cell resource configurations that take into account the one or more cells or DUs that are associated with multiple CUs. By providing cell resource configurations that take into account the one or more cells or DUs that are associated with multiple CUs, the IAB donor CU may reduce interference, improve efficiency of communication, and improve utilization of network resources.

Other examples may differ from what was described with regard to <FIG>.

<FIG> is a diagram illustrating an example <NUM> of signaling associated with indicating, to an IAB donor CU, that a network node is associated with cells or DUs associated with multiple CUs, in accordance with the present disclosure. As shown, example <NUM> includes a network node, an IAB donor CU1 (referred to hereinafter as CU1) and a gNB CU2 (referred to hereinafter as CU2). The network node may include, for example, the IAB node of <FIG>. The IAB donor CU1 may include the IAB donor CU1 of <FIG>. For example, the IAB donor CU1 may oversee resource management for IAB. The gNB CU2 may include the gNB CU2 of <FIG>. For example, the gNB CU2 may use an IAB network managed by the IAB donor CU1 for traffic transport.

In some aspects, CU2 may be an IAB donor CU. In some aspects, the network node may provide a DU associated with CU1 and a DU associated with CU2. In some aspects, the network node may be an IAB node, such as an IAB donor DU associated with CU1. In some aspects, the network node may have a signaling connection with CU1. For example, the signaling connection may be associated with an F1-C protocol or an RRC protocol, among other examples. In some aspects, the network node may have a signaling connection with CU2. For example, the signaling connection may be associated with an F1-C protocol or an RRC protocol, among other examples.

As shown in <FIG>, and by reference number <NUM>, in some aspects, CU2 may provide, to the network node, configuration information for a cell. For example, in some aspects, the cell may be configured by CU2. If the cell is configured by CU2, then the cell may be associated with an identifier associated with CU2, such as an NCI that carries an identifier of the gNB associated with the gNB CU2. In some aspects, the cell may be configured by CU1. If the cell is configured by CU1, then the network node may receive the configuration information for the cell from CU1. In some aspects, the cell may be associated with a time division duplexing (TDD) mode. For example, the cell may be a TDD cell. In some aspects, the cell may be associated with a frequency division duplexing (FDD) mode. For example, the cell may be an FDD cell.

According to the present invention, the cell is associated with an identifier associated with CU1. For example, the cell may have an NCI that carries an identifier of CU1. In this case, the cell is deactivated by CU1 or access is barred for child nodes that select a PLMN associated with CU1. In some aspects, the cell may provide service to a child node that is connected to CU2 (not shown in <FIG>). For example, the child node may be RRC connected to CU2. The child node may be a UE or an IAB node.

The configuration information may include, for example, a transmit configuration of CD-SSBs associated with the cell, an IAB SSB transmission configuration (STC) configuration for the cell, a random access channel (RACH) configuration for the cell, a CSI-RS configuration for the cell, a scheduling request (SR) configuration for the cell, a PDCCH configuration for the cell, a subcarrier spacing for transmissions of the cell, multiplexing information for communications of the first cell and a second cell served by a parent node or child node of the network node, a combination thereof, or similar information.

In some aspects, CU1 may transmit, to a parent node (e.g., the parent DU described in connection with <FIG>) of the network node, configuration information regarding the cell associated with CU2. For example, CU1 may forward at least part of the configuration information described above to the parent node. As another example, CU1 may transmit, to the parent node of the network node, a DU cell resource configuration for the cell. The DU cell resource configuration is described in more detail in connection with reference number <NUM>, below. The parent node of the network node may communicate with the network node based at least in part on the configuration information, as described elsewhere herein.

As shown by reference number <NUM>, the network node may provide, to CU1, information indicating the cell served by the network node and associated with CU2. For example, the network node may report an indication that the cell served by the network node is associated with CU2. In some aspects, the network node may provide at last part of the configuration information described with regard to reference number <NUM>. In some aspects, the network node may provide the information indicating the cell based at least in part on the cell being activated by CU2. For example, and as described in more detail below, CU2 may activate the cell, and the network node may provide the information indicating the cell based at least in part on CU2 activating the cell.

As shown by reference number <NUM>, according to the present invention, CU1 provides a DU cell resource configuration for the cell. For example, CU1 may determine the DU cell resource configuration for the cell and may transmit information indicating the DU cell resource configuration to the network node. In some aspects, CU1 may determine the DU cell resource configuration based at least in part on configuration information associated with the cell, such as the configuration information described in connection with reference number <NUM>. In some aspects, CU1 may determine the DU cell resource configuration so that half duplex constraints of the network node and/or other nodes of the IAB network are accommodated (e.g., are not violated). Thus, the DU cell resource configuration may reduce interference in the IAB network and may improve throughput of the IAB network.

In some aspects, the DU cell resource configuration may include at least part of the information described in connection with the cell resource configuration of <FIG>. For example, the DU cell resource configuration may be a gNB DU cell resource configuration. In some aspects, if the cell is associated with an FDD mode, then the DU cell resource configuration may include a configuration for uplink communications and a configuration for downlink communications. In some aspects, the DU cell resource configuration may indicate the availability of a communication resource of the cell (e.g., whether the communication resource is available, not available, or conditionally available). In some aspects, the DU cell resource configuration may indicate a direction associated with a communication resource of the cell (e.g., whether the resource is an uplink resource, a downlink resource, or a flexible resource). In some aspects, the DU cell resource configuration may indicate a cell direction associated with the cell (e.g., whether the cell is an uplink cell, a downlink cell, or a bidirectional cell). The communication resource may be a time resource, a frequency resource, and/or a spatial resource.

In some aspects, the DU cell resource configuration may be defined at a per-slot granularity. For example, the DU cell resource configuration may indicate a resource configuration for the cell and for a slot. In some aspects, the DU cell resource configuration may be defined at a per-symbol granularity. For example, the DU cell resource configuration may indicate a resource configuration for the cell and for a symbol of a slot. In some aspects, the DU cell resource configuration may be defined at a per-symbol-group granularity. For example, the DU cell resource configuration may indicate a resource configuration for the cell and for a group of one or more symbols within a slot (e.g., symbols associated with a same uplink/downlink direction).

In some aspects, the DU cell resource configuration may be defined at a frequency granularity. For example, the DU cell resource configuration may be defined for a carrier associated with the first cell. As another example, the DU cell resource configuration may be defined at a per-bandwidth-part granularity. As yet another example, the DU cell resource configuration may be defined per resource block of the cell, or per group of resource blocks of the cell.

In some aspects, the DU cell resource configuration may be associated with a spatial region. For example, the DU cell resource configuration may be associated with a beam direction (e.g., a set of quasi-colocation parameters indicating the beam direction). As another example, the DU cell resource configuration may be associated with an SSB area (e.g., an area associated with a particular SSB).

In some aspects, the DU cell resource configuration may be associated with a node. For example, the DU cell resource configuration may be specific to a child node served by the cell (e.g., a child node of the network node).

As shown by reference number <NUM>, CU2 may activate the cell. For example, CU2 may provide, via an F1-C or RRC interface, signaling to cause the network node to activate the cell. In some aspects, CU2 may activate the cell prior to CU1 providing the DU cell resource configuration. For example, CU2 may activate the cell, and then CU1 may provide the DU cell resource configuration based at least in part on CU2 activating the cell.

As shown by reference number <NUM>, the network node may provide, to CU1, an indication of an activation status of the cell. For example, the network node may report the activation of the cell to CU1. In some aspects, the network node may provide the indication of the activation status based at least in part on CU2 activating the cell. In some aspects, the network node may provide the indication of the activation status of the cell prior to receiving the DU cell resource configuration. For example, the network node may provide the indication of the activation status of the cell based at least in part on the cell being activated by CU2, and CU1 may provide the DU cell resource configuration based at least in part on the indication of the activation status of the cell.

As shown by reference number <NUM>, the network node may communicate on the cell based at least in part on the DU cell resource configuration. For example, a DU of the network node that serves the cell may schedule communications on the cell in accordance with the DU cell resource configuration. More particularly, the DU of the network node may schedule communications in accordance with availability, directions, and/or cell directions indicated by the DU cell resource configuration.

By determining the DU cell resource configuration based at least in part on the cell being associated with CU2, CU1 may improve utilization of communication resources of the network node and/or nodes associated with the network node (e.g., parent nodes, child nodes, or other upstream or downstream nodes). Thus, throughput may be increased, interference may be reduced, and efficiency of the IAB network may be improved.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a network node, in accordance with the present disclosure. Example process <NUM> is an example where the network node (e.g., non-anchor base station <NUM>, IAB node <NUM>, the IAB-node of <FIG>, the IAB-node of <FIG>, the network node of <FIG>, or one or more DUs described herein) performs operations associated with cell reporting for IAB RAN sharing.

As shown in <FIG>, in some aspects, process <NUM> may include transmitting, to an IAB donor CU, information indicating a cell served by the network node and associated with another CU (block <NUM>). For example, the network node (e.g., using transmission component <NUM>, depicted in <FIG>) may transmit, to an IAB donor CU, information indicating a cell served by the network node and associated with another CU, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include receiving, from the IAB donor CU, a DU cell resource configuration for the cell (block <NUM>). For example, the network node (e.g., using reception component <NUM>, depicted in <FIG>) may receive, from the IAB donor CU, a DU cell resource configuration for the cell, as described above. The DU cell resource configuration is also referred to herein as a cell resource configuration or a gNB-DU cell resource configuration.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by an IAB donor CU, in accordance with the present disclosure. Example process <NUM> is an example where the IAB donor CU (e.g., anchor base station <NUM>, IAB-donor <NUM>, the IAB-donor CU of <FIG>, the IAB-donor CU1 of <FIG>, or the IAB donor CU1 of <FIG>) performs operations associated with cell reporting for integrated access and backhaul radio access network sharing.

As shown in <FIG>, in some aspects, process <NUM> may include receiving, from a network node, information indicating a cell served by the network node and associated with another CU (block <NUM>). For example, the IAB donor CU (e.g., using reception component <NUM> of <FIG>) may receive, from a network node, information indicating a cell served by the network node and associated with another CU, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include transmitting, to the network node, a DU cell resource configuration for the cell (block <NUM>). For example, the IAB donor CU (e.g., using transmission component <NUM>, depicted in <FIG>) may transmit, to the network node, a DU cell resource configuration for the cell, as described above.

<FIG> is a block diagram of an example apparatus <NUM> for wireless communication. The apparatus <NUM> may be a network node, or a network node may include the apparatus <NUM>. In some aspects, the apparatus <NUM> includes a reception component <NUM> and a transmission component <NUM>, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus <NUM> may communicate with another apparatus <NUM> (such as a UE, a base station, or another wireless communication device) using the reception component <NUM> and the transmission component <NUM>. As further shown, the apparatus <NUM> may include a scheduling component <NUM>, among other examples.

In some aspects, the apparatus <NUM> may be configured to perform one or more operations described herein in connection with <FIG>. Additionally, or alternatively, the apparatus <NUM> may be configured to perform one or more processes described herein, such as process <NUM> of <FIG>. In some aspects, the apparatus <NUM> and/or one or more components shown in <FIG> may include one or more components of the network node described above in connection with <FIG>. Additionally, or alternatively, one or more components shown in <FIG> may be implemented within one or more components described above in connection with <FIG>. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a 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 a processor to perform the functions or operations of the component.

In some aspects, the reception component <NUM> may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the network node described above in connection with <FIG>.

In some aspects, the transmission component <NUM> may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the network node described above in connection with <FIG>. In some aspects, the transmission component <NUM> may be collocated with the reception component <NUM> in a transceiver.

The transmission component <NUM> may transmit, to an IAB donor CU, information indicating a cell served by the network node and associated with another CU. The reception component <NUM> may receive, from the IAB donor CU, a DU cell resource configuration for the cell.

In some aspects, the scheduling component <NUM>, the transmission component <NUM>, and/or the reception component <NUM> may communicate on the cell based at least in part on the DU cell resource configuration. In some aspects, the scheduling component <NUM> may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the base station described above in connection with <FIG>. In some aspects, the scheduling component <NUM> may be associated with a DU.

In some aspects, the scheduling component <NUM> may also provide service to a child node of the network node, wherein the child node is associated with a radio resource control connection to the other CU.

In some aspects, the reception component <NUM> may receive an indication, from the other CU, that the cell is activated.

In some aspects, the scheduling component <NUM>, the transmission component <NUM>, and/or the reception component <NUM> may communicate on the cell based at least in part on the DU cell resource configuration and based at least in part on receiving the indication.

In some aspects, the transmission component <NUM> may transmit, to the IAB donor CU, information indicating an activation status of the cell based at least in part on receiving the indication.

In some aspects, the reception component <NUM> may receive, from the other CU, configuration information for the cell.

The transmission component <NUM> may transmit, to the IAB donor CU, at least part of the configuration information, wherein the DU cell resource configuration is based at least in part on the configuration information.

In some aspects, the scheduling component <NUM>, the transmission component <NUM>, and/or the reception component <NUM> may communicate with a parent node of the network node based at least in part on configuration information associated with the cell.

<FIG> is a block diagram of an example apparatus <NUM> for wireless communication. The apparatus <NUM> may be an IAB donor CU, or an IAB donor CU may include the apparatus <NUM>. In some aspects, the apparatus <NUM> includes a reception component <NUM> and a transmission component <NUM>, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus <NUM> may communicate with another apparatus <NUM> (such as a UE, a base station, or another wireless communication device) using the reception component <NUM> and the transmission component <NUM>. As further shown, the apparatus <NUM> may include a configuration component <NUM>, among other examples.

In some aspects, the apparatus <NUM> may be configured to perform one or more operations described herein in connection with <FIG>. Additionally, or alternatively, the apparatus <NUM> may be configured to perform one or more processes described herein, such as process <NUM> of <FIG>. In some aspects, the apparatus <NUM> and/or one or more components shown in <FIG> may include one or more components of the IAB donor CU described above in connection with <FIG>. Additionally, or alternatively, one or more components shown in <FIG> may be implemented within one or more components described above in connection with <FIG>. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a 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 a processor to perform the functions or operations of the component.

In some aspects, the reception component <NUM> may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the base station described above in connection with <FIG>.

In some aspects, the transmission component <NUM> may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the base station described above in connection with <FIG>. In some aspects, the transmission component <NUM> may be collocated with the reception component <NUM> in a transceiver.

The reception component <NUM> may receive, from a network node, information indicating a cell served by the network node and associated with another CU. The transmission component <NUM> may transmit, to the network node, a DU cell resource configuration for the cell.

In some aspects, the reception component <NUM> may receive, from the network node, information indicating an activation status of the cell. In some aspects, the reception component <NUM> may receive, from the network node, configuration information for the cell, wherein the DU cell resource configuration is based at least in part on the configuration information.

In some aspects, the transmission component <NUM> or the configuration component <NUM> may transmit, to a parent node of the network node, configuration information regarding the cell. In some aspects, the configuration component <NUM> may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof.

Claim 1:
A network node for wireless communication, comprising:
a memory; and
one or more processors, coupled to the memory, configured to:
transmit (<NUM>), to an integrated access and backhaul, IAB, donor central unit, CU, information indicating a cell served by the network node and associated with another CU; and
receive (<NUM>), from the IAB donor CU, a distributed unit, DU, cell resource configuration for the cell, wherein the cell is associated with a New Radio cell identifier that identifies the IAB donor CU, and wherein the cell is deactivated by the IAB donor CU or access is barred for child nodes that select a public land mobile network associated with the IAB donor CU.