Resource block (RB) configuration of frequency domain resources

Abstract

A method, system, and apparatus for resource block (RB) set configuration in an integrated access and backhaul (IAB) network for frequency domain resources are disclosed. According to one aspect, a method in an IAB donor node communicating with a first IAB node includes receiving a resource multiplexing capability from the first IAB node. The method includes determining a resource block (RB) set configuration based at least in part on the resource multiplexing capability. The method further includes determining a DU resource configuration for the first IAB node based at least in part on the RB set configuration and transmitting the DU resource configuration to the first IAB node.

Description

[Technical field]

[0001] The present disclosure relates to wireless communications, and more particularly to resource block (RB) set configuration in an integrated access and backhaul (IAB) network for frequency domain resources. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP®) has developed and continues to develop standards for fourth-generation (4G) (also called Long Term Evolution (LTE)) and fifth-generation (5G) (also called New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WDs), as well as communication between network nodes and between WDs. Sixth-generation (6G) wireless communication systems are also under development.

[0003] Overview of Integrated Access and Backhaul Densification by deploying an increased number of base stations (macro or micro) is one of the mechanisms that can be used to meet the ever-increasing demand for more bandwidth and capacity in mobile networks. With more spectrum available in the millimeter wave (mmW) band, deploying small cells operating in this band is an attractive deployment option for these purposes. However, running fiber to the small cells, which is the usual way of installing small cells, would be very expensive and impractical. Therefore, using wireless links to connect small cells to the operator's network is a cheaper and more practical alternative that offers more flexibility and faster time to market.

[0004] One such solution is the Integrated Access and Backhaul (IAB) network, where operators can utilize a portion of their radio resources for the backhaul link.

[0005] Figure 1 shows an IAB deployment supporting multiple hops. An IAB donor node (IAB donor 2) has a wired connection to the core network, and IAB nodes 3 and 4 are wirelessly connected to IAB donor 2 using NR, either directly or indirectly via another IAB node. The connection between IAB donor node 2 and WD is called an access link, while the connection between the two IAB nodes 3 and 4, or between IAB donor 2 and IAB node 3, is called a backhaul link.

[0006] FIG. 2 shows a parent node 6 connected by a backhaul link to an IAB node 7 which is connected by another backhaul link to a child node 8. The parent node 6 is upstream of the IAB child node 8 which is downstream of the IAB node 7. Adjacent downstream nodes further away from the IAB donor node of the IAB node are called child nodes of the IAB node. The backhaul link between the parent node and the IAB node is called the parent (backhaul) link, while the backhaul link between the IAB node and the child node is called the child (backhaul) link.

[0007] IAB Architecture One difference between the IAB architecture and 3GPP® Technical Specification Release 10 (3GPP® Rel-10) LTE relay (apart from the lower layer differences) is that the IAB architecture adopts a CU / DU (Centralized Unit / Distributed Unit) split of the gNB. In such a split, time-critical functions are realized in the DU close to the radio station, while non-time-critical functions are placed in the CU with the opportunity for centralization. Based on this architecture, the IAB donor includes both CU and DU functions. In particular, it contains all the CU functions of the IAB nodes under the same IAB donor. Each IAB node then hosts the DU function(s) of the gNB. To be able to transmit and receive radio signals to and from the upstream IAB node or IAB donor, each IAB node has a Mobile Termination (MT), a logical unit that provides the required set of WD-like functions. Through the DU, the IAB node establishes a Radio Link Control (RLC) channel to the WD and / or MT of the connected IAB node. Through the MT, the IAB node establishes a backhaul radio interface towards the serving IAB node or the IAB donor. Figure 3 shows a reference diagram of a two-hop chain of IAB nodes under an IAB donor.

[0008] Resource Configuration Time Domain Resource Coordination For in-band operation, an IAB node is usually subject to half-duplex constraint, which means that it can only be in either transmit or receive mode at a time. 3GPP Rel-16 compliant IAB mainly considers the time division multiplexed (TDM) case where MT and DU resources of the same IAB node are separated in time. Based on this consideration, the following resource types are defined for IAB MT and DU, respectively:

[0009] As in 3GPP Rel-15, from the IAB node MT perspective, the following time domain resources may be indicated for the parent link: ● Downlink (DL) time resources ● Uplink (UL) time resources, and / or ● Flexible (F) time resources.

[0010] From the perspective of an IAB node DU, child links have the following types of time resources: ● DL Time Resources ● UL Time Resources ● F time resources, and / or ● Not Available (NA) time resources (resources not used for communication on the DU child link).

[0011] Each of the downlink, uplink, and flexible time resource types of the DU child link can belong to one of two categories: ● Hard (H): The corresponding time resource is always available in the DU child link. ● Soft (S): The availability of corresponding time resources for a DU child link is explicitly and / or implicitly controlled by the parent node.

[0012] The DU resources of IAB are configured per cell, and the H / S / NA attributes for DU resource configuration are explicitly indicated per resource type (D / U / F) in each slot. As a result, the semi-static time domain resources of the DU part can be of seven types in total: downlink hard (DL-H), downlink soft (DL-S), uplink hard (UL-H), uplink soft (UL-S), flexible hard (FH), flexible soft (FS), and unavailable (NA). The coordination relationship between MT resources and DU resources is listed in Table 1.

[0013] Table 1: Coordination between MT and DU resources of an IAB node.

[0014] ┌───────┬───────────────────────────────┐ │ │ MT configuration │ │ ├─────────┬─────────┬─────────┤ │ │ DL │ UL │ Flexible │ ├──┬────┼─────────┼─────────┼─────────┤ │ │DL-H│DU: Unlimited DL│DU: Unlimited DL│DU: Unlimited DL│ │ │ │ Can be sent with │ Can be sent with │ Can be sent with │ │ │ │MT:Unavailable │MT:Unavailable │MT:Unavailable │ │ ├────┼─────────┼─────────┼─────────┤ │ │DL-S│DU:Conditionally │DU:Conditionally │DU:Conditionally │ │ │ │ Can send │ Can send │ Can send │ │DU│ │MT:DL available│MT:UL available│MT:DL and UL│ │Con│ │ │ │Available │ │Fi├────┼─────────┼─────────┼─────────┤ │Gyu│UL-H│DU:UL without restrictions│DU:UL without restrictions│DU:UL without restrictions│ │Ray│ │Can be scheduled │Can be scheduled │Can be scheduled │ │Sho│ │MT:Not available │MT:Not available │MT:Not available │ │n ├────┼─────────┼──────────┼─────────┤ │ │UL-S│DU: UL without restrictions│DU: DL without restrictions│DU: DL without restrictions│ │ │ │Can be scheduled │ Can be sent on │ Can be sent on │ │ │ │MT:DL available│MT:UL available│MT:DL and UL│ │ │ │ │ │ Available │ │ ├────┼─────────┼─────────┼─────────┤ │ │FH │DU: No restrictions │DU: No restrictions │DU: No restrictions DL│ │ │ │ DL transmission possible │ DL transmission possible │ DL transmission possible │ │ │ │UL schedule available│UL schedule available│UL schedule available│ │ │ │MT:Unavailable │MT:Unavailable │MT:Unavailable │ │ ├────┼─────────┼─────────┼─────────┤ │ │FS │DU:Conditionally │DU:Conditionally │DU:Conditionally │ │ │ │ DL transmission possible │ DL transmission possible │ DL transmission possible │ │ │ │UL schedule available│UL schedule available│UL schedule available│ │ │ │MT:DL available│MT:UL available│MT:DL and UL│ │ │ │ │ │ Available │ │ ├────┼─────────┼─────────┼─────────┤ │ │NA │DU:Unavailable │DU:Unavailable │DU:Unavailable │ │ │ │MT:DL available│MT:UL available│MT:DL and UL│ │ │ │ │ │ Available │ └──┴────┴─────────┴──────────┴─────────┘

[0015] An example of a DU configuration is shown in Figure 4.

[0016] Frequency domain resource configuration Along with the time domain resource coordination between the IAB-MT and the co-located IAB-DU via the time domain H / S / NA, the frequency domain resources can also be coordinated by allocating the H / S / NA to frequency domain resource blocks (RBs). It can be assumed that: ● Hard (H): If the frequency resource is configured as hard, the IAB-DU can either transmit, receive, or transmit or receive according to its configuration; ● Soft (S): If a frequency resource is configured as soft, the IAB-DU can transmit, receive, or either transmit or receive only if it does not affect the actual ability of the IAB-MT to operate on this resource; ● Not Available (NA): The IAB-DU is unable to use the resource.

[0017] According to 3GPP's Rel-17 Extensions IAB Work Item Description (WID), the following duplex extensions may be specified: ● IAB node child and parent links (MT Tx / DU T Supports simultaneous operation (transmission and reception) of MT Tx / DU Rx, MT Rx / DU Tx, MT Rx / DU Rx, MT Rx / DU Rx.

[0018] 3GPP Rel-16 IAB specifications primarily consider the time division multiplexing (TDM) case where the IAB-MT and IAB-DU resources of the same IAB node are separated in time. 3GPP Rel-17 IAB addresses both frequency division multiplexing (FDM) and spatial division multiplexing (SDM) resource allocation cases between the IAB-MT and IAB-DU.

[0019] Regarding frequency domain H / S / NA resource configuration in the recent RAN1 meeting, the following was considered: RAN1 #105-e Study item: Extension of semi-static DU resource type indication to frequency domain resources within a carrier for H / S / NA resource types will be supported (in addition to the existing per carrier granularity in 3GPP Rel-16).

[0020] Consideration: The minimum resource size for configuring frequency domain granularity is a set of N resource blocks (RBs): ● Candidate values ​​for N: {4, 8, 16, other values ​​to be determined (TBD)}; ● N is at least the number of physical resource blocks (PRBs), which corresponds to the number of PRBs of the RBG of the MT; ● Future Research Questions (FFS): Scaling or configuration of N based on the size of the system bandwidth (BW) or IAB-MT bandwidth part (BWP).

[0021] RAN1 #106-e Considerations: Semi-static configuration of H / S / NA resource types in the frequency domain is provided per RB set per D / U / F resource type within a slot.

[0022] Consider: N is the number of PRBs configured, where N is configured by a CU: ● N = {2, 4, 8, 16, 32, 64} ● The value of N when multiple BWPs are configured in the FFS:IAB-MT, and ● This shall not abrogate existing RAN1 agreements.

[0023] RAN1 #106bis-e Consideration: A single value for the RB configuration size, N, is configured for the 3GPP Rel-17 frequency domain H / S / NA configuration of a given IAB-DU cell.

[0024] In case of simultaneous operation of IAB-MT and co-located IAB-DU, frequency domain resource coordination can be done by partitioning IAB-DU frequency resources and allocating them as H / S / NA. The IAB-DU frequency H / S / NA configuration depends on the overlap of IAB-MT and IAB-DU frequency resources. As considered in RAN1#106bis-e, the IAB-DU is only configured with one single value N for the size of resource block (RB) set, i.e., N RBs per RB set. Since the range of frequency domain resources is not specified, there is an ambiguity that the RB set configuration only has a value of N. Summary of the Invention

[0025] Some embodiments advantageously provide methods, systems, and apparatus for resource block (RB) set configuration in an integrated access and backhaul (IAB) network for frequency domain resources.

[0026] For example, a method for efficiently specifying ranges for RB sets and specifying RB set mapping in the frequency domain (e.g., using RB set indexing) to avoid unnecessary signaling. Furthermore, the IAB donor node, parent node, and IAB node should have a common understanding of the RB set configuration including the frequency domain mapping (e.g., indexing).

[0027] Some embodiments include a method for configuring an RB set for an IAB-DU, which includes frequency domain mapping (e.g., indexing) such that the IAB donor node, parent node, and IAB node can have a common understanding of the mapping between spectrum and the RB set, where the RB set includes a complete RB set for an IAB-DU cell and an incomplete RB set (which may exist because the IAB-DU carrier bandwidth is not an integer multiple of the RB set).

[0028] Some embodiments allow the IAB-DU to have an appropriate and efficient RB set configuration, taking into account the BWP of the IAB-MT. Some embodiments also allow the donor CU and parent node to efficiently configure and coordinate frequency domain resources based on the multiplexing conditions between the IAB-DU and the co-located IAB-MT. The method is also useful for reducing the signaling overhead of resource configuration.

[0029] According to one aspect, a method in a first integrated access and backhaul (IAB) node, the first IAB node including a mobile termination (MT) unit and a distribution unit (DU), the method includes receiving an IAB-DU cell and carrier configuration from a second network node, the second network node being one of an IAB donor CU and a parent IAB node, the second network node being upstream of the first IAB node. The method also includes reporting a resource multiplexing capability to the second network node. The method also includes receiving a resource block (RB) set configuration from the second IAB network node, the RB set configuration having an IAB-DU hard / soft / unavailable (H / S / NA) resource configuration, the IAB-DU H / S / NA resource configuration being based at least in part on the resource multiplexing capability. The method also includes mapping a resource block (RB) set of the DU based at least in part on the IAB-DU H / S / NA resource configuration and the IAB-DU cell and carrier configuration.

[0030] According to this aspect, in some embodiments, the method includes receiving a BWP configuration from a second network node and mapping RB sets to the BWPs based in part on the BWP configuration. According to some embodiments, the mapping includes allocating an integer number N of physical resource blocks (PRBs) to each RB set in the first set of RB sets and, if the IAB-DU frequency resources do not encompass all available PRBs, allocating a portion of the integer number N of PRBs to the remaining RB set. According to some embodiments, the mapping depends at least in part on whether an RB set of size N can encompass all available RBs, where N is an integer greater than 1. According to some embodiments, if the RB sets of the IAB-DU H / S / NA resource configuration do not cover the entire carrier bandwidth, the remaining RBs that are not part of the RB set configuration are considered to be included in the last RB set. According to some embodiments, the RB set configuration includes an index that points to the lowest RB in the first IAB-DU cell-and-carrier configuration. According to some embodiments, the starting RB index of the first RB set for the IAB-DU H / S / NA resource configuration is the lowest RB index in the IAB-DU cell. According to some embodiments, the IAB-DU cell-and-carrier configuration is based at least in part on carriers received from the IAB donor CU and configured by an operation and management function (OAM). According to some embodiments, the resource multiplexing capabilities for the MT unit and DU of the first IAB node include at least one of an indication of time division multiplexing, a TDM, requirement, an indication of frequency division multiplexing (FDM) requirement, and an indication of a transmit / receive state of the DU and MT unit. According to some embodiments, the method also includes receiving an RB set configuration from the second network node, where the RB set configuration includes at least one of an indication of an RB set size, an indication of a mapping method for determining a mapping of the RB sets, an indication of a number of RB sets, and an indication of an indexing method for indexing the RB sets.According to some embodiments, the IAB-DU H / S / NA resource configuration includes at least one of a time domain configuration, a frequency domain configuration, and an indication of which slots are to be time domain multiplexed (TDM) and which slots are to be frequency domain multiplexed (FDM). According to some embodiments, the method also includes receiving an indication of availability for a subset of the RB sets configured as soft. According to some embodiments, the DU of the first IAB node schedules resources based at least in part on the IAB-DU H / S / NA resource configuration. According to some embodiments, the maximum number of contiguous, non-overlapping RB sets configurable per cell in the IAB-DU cell-and-carrier configuration is eight.

[0031] According to another aspect, a first integrated access and backhaul (IAB) node is provided, where the first IAB node includes a mobile termination (MT) unit and a distribution unit (DU). The first IAB node includes a radio interface configured to receive an IAB-DU cell-and-carrier configuration from a second network node, where the second network node is one of an IAB donor CU and a parent IAB node, and the second network node is upstream of the first IAB node. The radio interface is further configured to report a resource multiplexing capability to the second network node and to receive a resource block (RB) set configuration from the second IAB network node, where the RB set configuration comprises an IAB-DU hard / soft / flexible (H / S / NA) resource configuration, and where the IAB-DU H / S / NA resource configuration is based at least in part on the resource multiplexing capability. The first IAB node also includes processing circuitry in communication with the air interface configured to map a resource block (RB) set of the DU based at least in part on the IAB-DU H / S / NA resource configuration and the IAB-DU cell and carrier configuration.

[0032] In this manner OkeruAccording to some embodiments, the radio interface is further configured to receive a BWP configuration from the second network node and map the RB sets to the BWP based in part on the BWP configuration. According to some embodiments, the mapping includes allocating an integer number N of physical resource blocks (PRBs) to each RB set in a first set of the plurality of RB sets, and allocating a portion of the integer number N of PRBs to the remaining RB set if the IAB-DU H / S / NA frequency resources do not encompass all available PRBs. According to some embodiments, the mapping depends at least in part on whether an RB set of size N can encompass all available RBs, where N is an integer greater than 1. According to some embodiments, if the RB sets of the IAB-DU H / S / NA resource configuration exceed N times the maximum number M of RB sets, the remaining RBs that are not part of the RB set configuration are considered to be included in the last RB set, where N and M are integers greater than zero. According to some embodiments, the RB set configuration includes an index that points to the lowest RB in the first IAB-DU cell-and-carrier configuration. According to some embodiments, a starting RB index of the first RB set for the IAB-DU H / S / NA resource configuration is the lowest RB index in the IAB-DU cell. According to some embodiments, the IAB-DU cell and carrier configuration is based at least in part on carriers received from the IAB donor CU and configured by an operations and management function (OAM). According to some embodiments, the resource multiplexing capabilities for the MT units and DUs of the first IAB node include at least one of an indication of a time division multiplexing (TDM) requirement, an indication of a frequency division multiplexing (FDM) requirement, and an indication of a transmit / receive status of the DUs and MT units.According to some embodiments, the radio interface is further configured to receive an RB set configuration from the second network node, where the RB set configuration includes at least one of an indication of an RB set size, an indication of a mapping method used to determine a mapping of the RB sets, an indication of a number of RB sets, and an indication of an indexing method used to index the RB sets. According to some embodiments, the IAB-DU H / S / NA resource configuration includes at least one of a time domain configuration, a frequency domain configuration, and an indication of which slots are to be time domain multiplexed (TDM) and which slots are to be frequency domain multiplexed (FDM). According to some embodiments, the radio interface is further configured to receive an availability indication for a subset of the RB sets configured as soft. According to some embodiments, the DU of the first IAB node schedules resources based at least in part on the IAB-DU H / S / NA resource configuration. According to some embodiments, the maximum number of contiguous and non-overlapping RB sets configurable per cell of the IAB-DU cell-and-carrier configuration is eight.

[0033] According to yet another aspect, a method in an integrated access and backhaul (IAB) donor node in communication with a first IAB node, where the first IAB node is downstream from the IAB donor node, includes receiving a resource multiplexing capability from the first IAB node, determining a resource block (RB) set configuration based at least in part on the resource multiplexing capability, determining a DU resource configuration for the first IAB node based at least in part on the RB set configuration, and transmitting the DU resource configuration to the first IAB node.

[0034] In this manner OkeruAccording to some embodiments, the method further includes omitting frequency domain configurations of hard / soft / not applicable (H / S / NA) attributes from the DU resource configuration if the RB sets of the RB set configuration do not overlap with the BWP. According to some embodiments, the DU resource configuration includes an IAB-DU cell-and-carrier configuration for the first IAB. According to some embodiments, the maximum number of contiguous and non-overlapping RB sets configurable per cell of the IAB-DU cell-and-carrier configuration is eight. According to some embodiments, the RB set configuration includes at least one of an indication of an RB set size, a number of RB sets, an indication of a mapping method used by the first IAB node to determine a mapping of the RB sets, and an indication of an indexing method used to index the RB sets. According to some embodiments, transmitting the DU resource configuration to the first IAB node includes transmitting the DU resource configuration via an F1 application protocol (AP).

[0035] According to another aspect, an integrated access and backhaul (IAB) donor node is provided, the IAB donor node in communication with a first IAB node, where the first IAB node is downstream of the IAB donor node. The IAB donor node includes a radio interface configured to receive a resource multiplexing capability from the first IAB node. The IAB donor node also includes processing circuitry in communication with the radio interface and configured to determine a resource block (RB) set configuration based at least in part on the resource multiplexing capability and to determine a DU resource configuration for the first IAB node based at least in part on the RB set configuration. The radio interface is further configured to transmit a DU resource configuration to the first IAB node.

[0036] In this manner OkeruAccording to some embodiments, the processing circuitry is further configured to omit frequency domain configuration of hard / soft / not applicable (H / S / NA) attributes from the DU resource configuration if the RB set of the RB set configuration does not overlap with the BWP. According to some embodiments, the DU resource configuration includes an IAB-DU cell-and-carrier configuration for the first IAB. According to some embodiments, the maximum number of contiguous and non-overlapping RB sets configurable per cell of the IAB-DU cell-and-carrier configuration is eight. According to some embodiments, the RB set configuration includes at least one of an indication of an RB set size, a number of RB sets, an indication of a mapping method used by the first IAB node to determine a mapping of the RB sets, and an indication of an indexing method used to index the RB sets. According to some embodiments, the radio interface is further configured to transmit the DU resource configuration to the first IAB node via an F1 application protocol (AP).

[0037] According to yet another aspect, a method in a parent integrated access and backhaul (IAB) node, the parent IAB node in communication with an IAB donor node and a first IAB node, where the parent IAB node is downstream of the IAB donor node and upstream of the first IAB node, the method includes activating a mobile termination (MT) unit bandwidth part for the first IAB node, receiving a distributed unit (DU) resource configuration for each cell of the first IAB node from the IAB donor node, receiving a resource block (RB) set configuration for each cell of the first IAB node from one of the IAB donor node and the first IAB node, and sending an indication of DU resource availability to the first IAB node, where the DU resource availability is based at least in part on the DU resource configuration and the RB set configuration for each cell of the first IAB node.

[0038] In this manner Okeru According to some embodiments, the DU resource configuration for each cell includes at least one hard / soft / unavailable (H / S / NA) attribute of the DU resource configuration. According to some embodiments, the RB set configuration for the cell includes an IAB-DU carrier configuration for the cell. According to some embodiments, the maximum number of contiguous and non-overlapping RB sets configurable per cell in the IAB-DU cell-and-carrier configuration is eight. According to some embodiments, the indication of DU resource availability is transmitted in downlink control information in DCI format 2_5. According to some embodiments, the method includes considering that if an RB set corresponding to the IAB-DU H / S / NA resource configuration does not cover the entire carrier bandwidth, the remaining RBs that are not part of the RB set configuration should be included in the last RB set.

[0039] According to another aspect, a parent integrated access and backhaul (IAB) node is provided in communication with an IAB donor node and a first IAB node, the parent IAB node being downstream of the IAB donor node and upstream of the first IAB node. The parent IAB node includes a processing circuit configured to activate a mobile termination (MT) unit bandwidth part for the first IAB node. The parent IAB node also includes a radio interface in communication with the processing circuit and is configured to receive from the IAB donor node a distributed unit (DU) resource configuration for each cell of the first IAB node, receive from one of the IAB donor node and the first IAB node a resource block (RB) set configuration for each cell of the first IAB node, and transmit an indication of DU resource availability to the first IAB node, where the availability of DU resources is based at least in part on the DU resource configuration and the RB set configuration for each cell of the first IAB node.

[0040] In this manner OkeruAccording to some embodiments, the DU resource configuration for each cell includes at least one hard / soft / unavailable (H / S / NA) attribute of the DU resource configuration. According to some embodiments, the RB set configuration for the cell includes an IAB-DU carrier configuration for the cell. According to some embodiments, the maximum number of contiguous and non-overlapping RB sets configurable per cell in the IAB-DU cell-and-carrier configuration is eight. According to some embodiments, an indication of DU resource availability is transmitted in downlink control information in DCI format 2_5. According to some embodiments, if an RB set corresponding to an IAB-DU H / S / NA resource configuration does not cover the entire carrier bandwidth, the remaining RBs that are not part of the RB set configuration are considered to be included in the last RB set. [Brief description of the drawings]

[0041] A more complete understanding of the present embodiments, along with their attendant advantages and features, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings, in which:

[0042] [Figure 1] shows an IAB deployment that supports multiple hops.

[0043] [Diagram 2] indicates the upstream parent node and downstream child IAB node of the IAB node, along with the parent / child backhaul links.

[0044] [Diagram 3] Figure 1 shows a reference diagram of a two-hop chain of IAB nodes under an IAB donor.

[0045] [Figure 4] 1 shows an exemplary DU configuration.

[0046] [Diagram 5]1 is a schematic diagram of an example network architecture illustrating a communication system according to the principles disclosed herein.

[0047] [Figure 6] 1 is a block diagram of a network node operating as an IAB node upstream from a wireless device over a wireless connection in accordance with some embodiments of the present disclosure.

[0048] [Figure 7] 7 is a block diagram of the network node of FIG. 6 in communication with an upstream IAB donor node.

[0049] [Figure 8] 1 is a flowchart of an example process in a network node for resource block (RB) set configuration in an integrated access and backhaul (IAB) network for frequency domain resources.

[0050] [Figure 9] 1 is a flowchart of an example process in a network node for resource block (RB) set configuration in an integrated access and backhaul (IAB) network for frequency domain resources.

[0051] [Figure 10] 1 is a flowchart of an example process in a network node for resource block (RB) set configuration in an integrated access and backhaul (IAB) network for frequency domain resources.

[0052] [Figure 11] 1 is a flowchart of an example processing in a first IAB node for RB set configuration in an IAB network in accordance with the principles disclosed herein.

[0053] [Figure 12]1 is a flowchart of an example processing in an IAB donor node for RB set configuration in an IAB network in accordance with the principles disclosed herein.

[0054] [Figure 13] 1 is a flowchart of an example processing in a parent IAB node for RB set configuration in an IAB network according to the principles disclosed herein.

[0055] [Figure 14] 1 is a diagram showing the IAB network.

[0056] [Figure 15] 1 is a flowchart of a first exemplary process in an IAB node.

[0057] [Figure 16] 1 is a flowchart of a second exemplary process in an IAB node.

[0058] [Figure 17] is a flowchart of a second exemplary process in an IAB node.

[0059] [Figure 18] 1 is a diagram showing a first example of mapping a BWP to RBs according to the principles disclosed herein.

[0060] [Figure 19] 1 is a diagram showing a second example of mapping BWPs to RBs according to the principles disclosed herein.

[0061] [Figure 20] 13 is a diagram showing a third example of mapping BWPs to RBs according to the principles disclosed herein.

[0062] [Figure 21]13 is a diagram showing a fourth example of mapping of BWPs to RBs according to the principles disclosed herein.

[0063] [Figure 22] FIG. 11 is a diagram showing a fifth example of mapping of BWPs to RBs according to the principles disclosed herein.

[0064] [Diagram 23] FIG. 13 illustrates a sixth example of mapping of BWPs to RBs according to the principles disclosed herein.

[0065] [Figure 24] FIG. 13 is a diagram showing a seventh example of mapping of BWPs to RBs according to the principles disclosed herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0066] Before describing the exemplary embodiment in detail, it should be noted that the embodiment is mainly a combination of device components and processing steps related to resource block (RB) set configuration in an integrated access and backhaul (IAB) network for frequency domain resources. Therefore, the components are appropriately represented by conventional symbols in the drawings, and only specific details relevant to understanding the embodiment are shown, so as not to obscure the present disclosure with details that will be readily apparent to those skilled in the art having the benefit of the description herein.

[0067] As used herein, relational terms such as "first" and "second", "upper" and "lower" may be used only to distinguish one entity or element from another entity or element and do not necessarily require or imply any physical or logical relationship or order between such entities or elements. The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit the concepts described herein. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms unless the context clearly indicates otherwise. The terms "comprises", "comprising", "having", and / or "including", as used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0068] According to embodiments described herein, coupling terms such as "in communication with" may be used to indicate electrical or data communication, which may be accomplished, for example, by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signals. Those skilled in the art will appreciate that multiple components may interoperate and modifications and variations are possible to accomplish electrical and data communication.

[0069] In accordance with certain embodiments described herein, terms such as "coupled," "connected," and the like may be used herein to indicate a connection, although not necessarily direct, and may include wired and / or wireless connections.

[0070] The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit the concepts described herein. As used herein, the singular forms "a," "an," and "the" are intended to include the plural unless the context clearly indicates otherwise. The terms "comprises," "comprising," "having," and / or "including," as used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0071] The term "network node" as used herein refers to any type of network node included in a wireless network, and may further include optionally a base station (BS), a radio base station, a base transceiver station (BTS), a base station controller (BSC), a radio network controller (RNC), a gNodeB (gNB), an evolved NodeB (eNB or eNodeB), a NodeB, a multi-standard (MSR) wireless node such as an MSR BS, a multi-cell / multicast coordination entity (MCE), a relay node, a donor node controlling a relay, a radio access point (AP), a transmission point, a transmission node, a remote radio unit (RRU), a remote radio head (RRH), a core network node (e.g., a mobile management entity (MME), a self-organizing network (SON) node, a coordination node, a positioning node, an MDT node, etc.), an external node (e.g., a third party node, an external node of the current network), a node in a distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. A network node may also include a test device. As used herein, the term "wireless node" may also be used to refer to a wireless device (WD) such as a wireless device (WD) or a wireless network node. The term "network node" encompasses an integrated access and backhaul (IAB) donor node, an IAB parent node, and an IAB child node.

[0072] According to some embodiments, the non-limiting terms wireless device (WD) or user equipment (UE) are used interchangeably. A WD in this specification may be any kind of wireless device capable of communicating with a network node or another WD via a wireless signal, such as a wireless device (WD). A WD may also be a wireless communication device, a target device, a device-to-device (D2D) WD, a machine-type WD capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet, a mobile termination, a smartphone, a laptop with embedded (LEE), a laptop-mounted equipment (LME), a USB dongle, a customer premises equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IOT) device, etc.

[0073] Also, according to some embodiments, the general term "radio network node" is used, which may be any kind of radio network node, which may comprise any of the following: base station, radio base station, base transceiver station, base station controller, network controller (RNC), evolved Node B (eNB), Node B, gNB, multi-cell / multicast coordination entity (MCE), relay node, access point, radio access point, remote radio unit (RRU), remote radio head (RRH).

[0074] It should be noted that, although terminology from one particular wireless system, such as, for example, 3GPP® LTE and / or New Radio (NR), may be used in this disclosure, this should not be construed as limiting the scope of this disclosure to only the aforementioned systems. Ultra Mobile Broadband (U M B), and For mobile communications Global System (G S Other wireless systems, including but not limited to, wireless LANs, wireless hubs, wireless LAN devices, wireless LAN systems ...

[0075] Furthermore, it should be noted that the functions described herein as being performed by a wireless device or a network node may be distributed across multiple wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network nodes and wireless devices described herein are not limited to performance by a single physical device, and may in fact be distributed among several physical devices. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. It will be further understood that the terms used herein should be interpreted to have a meaning consistent with their meaning in the context of the present specification and related art, and are not to be interpreted in an idealized or overly formal sense unless expressly defined herein.

[0076] Some embodiments are directed to resource block (RB) set configuration in an integrated access and backhaul (IAB) network for frequency domain resources. Referring again to the drawings, where like elements are referenced by like reference numerals, FIG. 5 shows a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP type cellular network that may support standards such as LTE and / or NR (5G), comprising an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a number of network nodes 16a, 16b, 16c, such as NBs, eNBs, gNBs, or other types of wireless access points (collectively referred to as network nodes 16), each defining a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). One or more of the network nodes 16a, 16b, 16c can be connected to the core network 14 via a wired or wireless connection 20. A first wireless device (WD) 22a located in the coverage area 18a is configured to wirelessly connect to or be paged by a corresponding network node 16a. A second WD 22b in the coverage area 18b is wirelessly connectable to a corresponding network node 16b. Although multiple WDs 22a, 22b (collectively referred to as wireless devices 22) are shown here, the present invention is equally applicable when a sole WD is in the coverage area or connects to a corresponding network node 16. For convenience, only two WDs 22 and three network nodes 16 are shown, but it should be noted that the communication system may include more WDs 22 and network nodes 16.

[0077] According to some embodiments, network 10 may include an IAB network where, for example, network node 16a is a parent IAB node or an IAB donor node, network node 16b is an IAB node that may be a parent IAB node, and network node 16c or WD22 is a child IAB node.

[0078] It is also contemplated that the WD 22 may communicate simultaneously and / or may be configured to communicate separately with more than one network node 16 and more than one type of network node 16. For example, the WD 22 may have dual connectivity with a network node 16 supporting LTE and the same or another network node 16 supporting NR. As an example, the WD 22 may communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0079] The network node 16 (eNB or gNB) is configured to include an RB set unit 24 configured to configure and / or transmit an RB set configuration. The RB set configuration may be based on a cell-and-carrier configuration. When the network node 16 is configured as a first IAB node downstream from one of an IAB donor CU and a parent IAB node, the RB set unit 24 may be configured to map an RB set of a distributed unit (DU) of the network node 16 based on the RB set configuration and at least in part on an H / S / NA resource configuration. When the network node 16 is configured as an IAB donor node, the RB set unit 24 may be configured to determine a DU resource configuration for the IAB node based at least in part on the RB set configuration. When the network node 16 is configured as a parent IAB node, the RB set unit 24 may be configured to receive a per-cell RB set configuration of the other IAB node from the IAB donor node and / or another IAB node.

[0080] In the following, an exemplary embodiment of the WD 22 and the network node 16 described in the previous paragraph will be described with reference to FIG.

[0081] The communication system 10 includes a network node 16b having hardware 28 disposed therein and capable of communicating with a WD 22. The hardware 28 may include a radio interface 30 for establishing and maintaining at least one wireless connection 32 with a WD 22 located in a coverage area 18 provided by the network node 16b. The radio interface 30 may be formed as or include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 30 includes an antenna array 34 for emitting and receiving signals carrying electromagnetic waves.

[0082] According to the illustrated embodiment, the hardware 28 of the network node 16b further includes a processing circuit 36. The processing circuit 36 ​​may include a processor 38 and a memory 40. In addition to or instead of a processor, such as a central processing unit and a memory, in particular, the processing circuit 36 ​​may comprise an integrated circuit for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (field programmable gate arrays) and / or ASICs (application specific integrated circuits) adapted to execute instructions. The processor 38 may be configured to access (e.g., write and / or read) a memory 40, which may comprise any kind of volatile and / or non-volatile memory, e.g., a cache memory and / or a buffer memory and / or a RAM (random access memory) and / or a ROM (read only memory) and / or an optical memory and / or an EPROM (erasable programmable read only memory).

[0083] Thus, the network node 16b further has software 42 stored, for example, internally in the memory 40 or stored in an external memory accessible by the network node 16b via an external connection (e.g., a database, a storage array, a network storage device, etc.). The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and / or processes described herein and / or cause such methods and / or processes to be performed, for example, by the network node 16. The processor 38 corresponds to one or more processors 38 for performing the functions of the network node 16b described herein. The memory 40 is configured to store data, program software code, and / or other information described herein. According to some embodiments, the software 42 may include instructions that, when executed by the processor 38 and / or the processing circuitry 36, cause the processor 38 and / or the processing circuitry 36 to perform the processes described herein with respect to the network node 16b. For example, the processing circuitry 36 of the network node 16 may include an RB set unit 24 configured to configure and / or transmit an RB set configuration. The RB set unit 24 may be configured to map the RB set of a distributed unit (DU) based at least in part on the H / S / NA resource configuration of the network node 16b and the cell-and-carrier configuration of the IAB-DU of the network node 16b. The RB set unit 24 may be configured to receive the RB set configuration of each cell of the other IAB node from the IAB donor node and / or another IAB node. The network node 16b also includes the MT unit 26 and the DU 27, and the communication system 10 further includes the WD 22 described above. In some cases, the WD 22 may be considered as a child IAB node downstream from its parent IAB node, i.e., the network node 16b.The WD 22 may have hardware 44 that may include a radio interface 46 configured to establish and maintain a wireless connection 32 with the network node 16b serving the coverage area 18 in which the WD 22 is currently located. The radio interface 46 may be formed as or include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 46 includes an array of antennas 48 for emitting and receiving signals carrying electromagnetic waves.

[0084] The hardware 44 of the WD 22 further includes a processing circuit 50. The processing circuit 50 may include a processor 52 and a memory 54. In addition to or instead of a processor, such as a central processing unit and memory, in particular, the processing circuit 50 may include integrated circuits for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (field programmable gate arrays) and / or ASICs (application specific integrated circuits) adapted to execute instructions. The processor 52 may be configured to access (e.g., write and / or read) the memory 54, which may include any type of volatile and / or non-volatile memory, such as cache memory and / or buffer memory and / or RAM (random access memory) and / or ROM (read only memory) and / or optical memory and / or EPROM (erasable programmable read only memory).

[0085] Thus, the WD 22 may further comprise software 56, for example, stored in memory 54 of the WD 22 or stored in an external memory accessible by the WD 22 (e.g., a database, a storage array, a network storage device, etc.). The software 56 may be executable by the processing circuitry 50. The software 56 may include a client application 58. The client application 58 may be operable to provide services to a human or non-human user via the WD 22.

[0086] The processing circuitry 50 may be configured to control any of the methods and / or processes described herein and / or cause such methods and / or processes to be performed, for example, by the WD22. The processor 52 corresponds to one or more processors 52 for performing the functions of the WD22 described herein. The WD22 includes a memory 54 configured to store data, program software code, and / or other information described herein. According to some embodiments, the software 56 and / or client application 58 may include instructions that, when executed by the processor 52 and / or the processing circuitry 50, cause the processor 52 and / or the processing circuitry 50 to perform the processes described herein with respect to the WD22.

[0087] According to some embodiments, the internal structure of network node 16b and WD 22 may be as shown in FIG. 6, and independently, the surrounding network topology may be that of FIG.

[0088] The wireless connection 32 between the WD 22 and the network node 16 follows the teachings of the embodiments described throughout this specification. More precisely, the teachings of some of these embodiments may improve data rates, latency, and / or power consumption, thereby providing advantages such as reduced user latency, relaxed file size limitations, better responsiveness, extended battery life, etc. According to some embodiments, measurement procedures may be provided for the purpose of monitoring the data rates, latency, and other factors that one or more embodiments improve.

[0089] 7 illustrates a network node 16b downstream from the IAB donor node 16a. Elements of the network node 16b and like-numbered elements of the network node 16a may perform similar functions and operate as described above. However, in the IAB donor node 16a, the RB set unit 24 may be configured to determine a DU resource configuration for the IAB node 16b based at least in part on the RB set configuration. The IAB donor node 16b also includes a CU 25.

[0090] 5 and 6 depict various "units," such as the RB set unit 24, as being within respective processors, it is contemplated that these units may be implemented such that portions of the units are stored in corresponding memories within the processing circuitry. In other words, the units may be implemented in hardware within the processing circuitry, or in a combination of hardware and software.

[0091] FIG. 8 illustrates a resource block diagram in an integrated access and backhaul (IAB) network for frequency domain resources. (RB)1 is a flowchart of an example process in a network node 16 for set configuration. One or more blocks described herein may be executed by one or more elements of the network node 16, for example, by one or more of the processing circuitry 36 (including the RB set unit 24), the processor 38, and / or the radio interface 30. Through the processing circuitry 36 and / or the processor 38 and / or the radio interface 30, etc., the network node 16 is configured to receive at least one bandwidth part (BWP) configuration (block S10) and receive resource block (RB) set configurations for the at least one BWP (block S12) from an integrated access and backhaul (IAB) donor centralization unit (CU), where the RB set configuration indicates a number of RB sets and a number of RBs per RB set. The process also includes determining an RB set index based on the RB set configuration (block S14) and scheduling RBs according to the determined RB set configuration (block S16).

[0092] In this manner Okeru According to some embodiments, the network node 16, the processing circuitry 36, and / or the radio interface 30 are further configured to receive an IAB distributed unit (DU) cell / carrier configuration and report resource multiplexing capabilities to the donor CU. According to some embodiments, the RB set mapping is determined based at least in part on a union of BWPs.

[0093] figure 91 is a flowchart of an example process in a network node 16 according to some embodiments disclosed herein. One or more blocks described herein may be executed by one or more elements of the network node 16, for example, by one or more of the processing circuitry 36 (including the RB set unit 24), the processor 38, and / or the radio interface 30. Through the processing circuitry 36 and / or the processor 38 and / or the radio interface 30, etc., the network node 16 is configured to transmit at least one bandwidth part (BWP) configuration to the integrated access and backhaul (IAB) MT unit 26 (block S18). The process also includes transmitting a resource block (RB) set configuration, transmitting an RB set configuration indicating a number of RB sets and a number of RBs per RB set (block S20), determining an IAB DU resource configuration based at least in part on the RB set configuration (block S22), and transmitting the IAB DU resource configuration to the IAB DU (block S24).

[0094] In this manner Okeru According to some embodiments, when the network node 16 is configured as a donor node, the processing circuitry 36 and / or the radio interface 30 are further configured to transmit the DU cell / carrier configuration of the IAB to a parent node of the DU of the IAB. According to some embodiments, the RB set configuration illustrates a method for determining the scope of the RB set configuration.

[0095] 10 is a flow chart of an example process in a network node 16 according to some embodiments disclosed herein. One or more blocks described herein may be executed by one or more elements of the network node 16, such as by one or more of the processing circuitry 36 (including the RB setting unit 24), the processor 38, and / or the radio interface 30. The processing circuitry 36 and / or the processor 38 and / or the radio interface 30, etc. Through The network node 16 is configured to activate a child node integrated access and backhaul (IAB) mobile termination (MT) bandwidth part (BWP) (block S26), receive a resource configuration of the child node's serving cell (block S28), receive a resource block (RB) set configuration of the child node's serving cell (block S30), and send an indication of the RB set configuration to the child node (block S32).

[0096] In this manner Okeru According to some embodiments, the resource configuration includes at least one of a time division duplex (TDD) pattern and a hard / soft / unavailable (H / S / N) configuration for each RB set. According to some embodiments, the RB set configuration includes an indication of a size of the RB set and / or a number of RB sets.

[0097] 11 is a flow chart of an example process in a network node 16 configured as a first IAB node having an MT unit and a DU, according to some embodiments disclosed herein. One or more blocks described herein may be performed by one or more elements of the network node 16, such as by one or more of the processing circuitry 36 (including the RB set unit 24, the MT unit 26 and the DU 27), the processor 38, and / or the wireless interface 30. The processing circuitry 36 and / or the processor 38 and / or the wireless interface 30, etc. Through The network node 16 is configured to receive an IAB-DU cell-and-carrier configuration from a second network node, the second network node being one of an IAB donor CU and a parent IAB node, the second network node being upstream of the first IAB node (block S34). The method also includes reporting a resource multiplexing capability to the second network node (block S36). The method also includes receiving a resource block (RB) set configuration from the second IAB network node, the RB set configuration having an IAB-DU hard / soft / unavailable (H / S / NA) resource configuration, the IAB-DU H / S / NA resource configuration based at least in part on the resource multiplexing capability (block S38). The method also includes mapping a resource block (RB) set of the DU based at least in part on the IAB-DU H / S / NA resource configuration and the IAB-DU cell-and-carrier configuration (block S40).

[0098] In this manner Okeru According to some embodiments, the method includes receiving a BWP configuration from a second network node and mapping RB sets to the BWP based in part on the BWP configuration. According to some embodiments, the mapping includes assigning an integer number N of physical resource blocks (PRBs) to each RB set of a first set of the plurality of RB sets and, if the IAB-DU frequency resource does not encompass all available PRBs, assigning an integer number N of the PRBs to each RB set of a first set of the plurality of RB sets. oneand allocating the remaining RBs to the remaining RB set. According to some embodiments, the mapping depends at least in part on whether an RB set of size N can encompass all available RBs, where N is an integer greater than 1. According to some embodiments, if the RB set of the IAB-DU H / S / NA resource configuration does not cover the entire carrier bandwidth, the remaining RBs that are not part of the RB set configuration are considered to be included in the last RB set. According to some embodiments, the RB set configuration includes an index pointing to the lowest RB in the first IAB-DU cell-and-carrier configuration. According to some embodiments, the starting RB index of the first RB set for the IAB-DU H / S / NA resource configuration is the lowest RB index of the IAB-DU cell. According to some embodiments, the IAB-DU cell-and-carrier configuration is based at least in part on the carriers received from the IAB donor CU and configured by an operation and management function (OAM). According to some embodiments, the resource multiplexing capabilities for the MT unit 26 and DU of the first IAB node include at least one of an indication of a time division multiplexing (TDM) requirement, an indication of a frequency division multiplexing (FDM) requirement, and an indication of a transmit / receive status of the DU and MT unit 26. According to some embodiments, the method also includes receiving an RB set configuration from the second network node, the RB set configuration including at least one of an indication of an RB set size, an indication of a mapping method used to determine a mapping of the RB sets, an indication of a number of RB sets, and an indication of an indexing method used to index the RB sets. According to some embodiments, the IAB-DU H / S / NA resource configuration includes at least one of a time domain configuration, a frequency domain configuration, and an indication of which slots are to be time domain multiplexed (TDM) and which slots are to be frequency domain multiplexed (FDM). According to some embodiments, the method also includes receiving an indication of availability for a subset of the RB sets configured as soft.According to some embodiments, the DU of the first IAB node schedules resources based at least in part on the IAB-DU H / S / NA resource configuration. According to some embodiments, the maximum number of contiguous and non-overlapping RB sets configurable per cell of the IAB-DU cell-and-carrier configuration is eight.

[0099] 12 is a flowchart of an example process in a network node 16 configured as an IAB donor node communicating with a first IAB node, according to some embodiments disclosed herein. One or more blocks described herein may be performed by one or more elements of the network node 16, such as by one or more of the processing circuitry 36 (including the RB set unit 24, the MT unit 26 and the DU 27), the processor 38, and / or the wireless interface 30. The processing circuitry 36 and / or the processor 38 and / or the wireless interface 30 may include, but are not limited to, the RB set unit 24, the MT unit 26, and the DU 27. Through these and other means, The network node 16 is configured to receive a resource multiplexing capability from the first IAB node (block S42). The process includes determining a resource block (RB) set configuration based at least in part on the resource multiplexing capability (block S44). The method also includes determining a DU resource configuration for the first IAB node based at least in part on the RB set configuration (block S46). Additionally, the method transmits the DU resource configuration to the first IAB node (block S48).

[0100] In this manner OkeruAccording to some embodiments, the method further includes omitting frequency domain configurations of hard / soft / not applicable (H / S / NA) attributes from the DU resource configuration if the RB sets of the RB set configuration do not overlap with the BWP. According to some embodiments, the DU resource configuration includes an IAB-DU cell-and-carrier configuration for the first IAB. According to some embodiments, the maximum number of contiguous and non-overlapping RB sets configurable per cell of the IAB-DU cell-and-carrier configuration is eight. According to some embodiments, the RB set configuration includes at least one of an indication of an RB set size, a number of RB sets, an indication of a mapping method used by the first IAB node to determine a mapping of the RB sets, and an indication of an indexing method used to index the RB sets. According to some embodiments, transmitting the DU resource configuration to the first IAB node includes transmitting the DU resource configuration via an F1 application protocol (AP).

[0101] 13 is a flowchart of an example process in a network node 16 configured as a parent IAB node communicating with an IAB donor node, according to some embodiments disclosed herein. One or more blocks described herein may be performed by one or more elements of the network node 16, such as by one or more of the processing circuitry 36 (including the RB set unit 24, the MT unit 26 and the DU 27), the processor 38, and / or the wireless interface 30. The processing circuitry 36 and / or the processor 38 and / or the wireless interface 30 may include, but are not limited to, the RB set unit 24, the MT unit 26, and the DU 27. Through these and other means,The network node 16 is configured to activate a mobile termination (MT) unit bandwidth part for the first IAB node (block S50). The process includes receiving a resource block (RB) set configuration from an IAB donor node, the RB set configuration including a per-cell distributed unit (DU) resource configuration of the first IAB node (block S52). The method also includes receiving a per-cell resource block (RB) set configuration of the first IAB node from one of the IAB donor node and the first IAB node (block S54). The process further includes sending an indication of DU resource availability to the first IAB node, the DU resource availability being based at least in part on the per-cell DU resource configuration and the RB set configuration of the first IAB node (block S56).

[0102] In this manner Okeru According to some embodiments, the DU resource configuration for each cell includes at least one hard / soft / unavailable (H / S / NA) attribute of the DU resource configuration. According to some embodiments, the RB set configuration for the cell includes an IAB-DU carrier configuration for the cell. According to some embodiments, the maximum number of contiguous and non-overlapping RB sets configurable per cell in the IAB-DU cell-and-carrier configuration is eight. According to some embodiments, the indication of DU resource availability is transmitted in downlink control information in DCI format 2_5. According to some embodiments, the method includes considering remaining RBs that are not part of the RB set configuration to be included in the last RB set if the RB set corresponding to the IAB-DU H / S / NA resource configuration exceeds N times the maximum number M of RB sets, where N and M are integers greater than zero.

[0103] Having described the general process flow of the configuration of the present disclosure and provided examples of hardware and software configurations for implementing the processes and functions of the present disclosure, the following sections provide configuration details and examples for resource block (RB) set configuration in an integrated access and backhaul (IAB) network for frequency domain resources.

[0104] An exemplary IAB network is shown in Figure 14, where an IAB node 16 may be connected downstream from a parent IAB node 16b, and upstream from devices and / or child IAB nodes 16c, 22. The parent IAB node 16b may in turn also connect devices or other IAB nodes 16, 22.

[0105] Aspects of an IAB node related to BWP or DU carrier signaling An aspect of some embodiments relates to mapping the RB set index to at least one BWP, or alternatively, mapping the RB set index to a DU carrier. The mapping may be signaled to another network node, for example, the parent IAB node 16b. Both alternatives are included in FIG. 15 by applying either step (100) or step (120), respectively.

[0106] Some embodiments include an IAB node for determining a resource multiplexing configuration between a DU 27 portion and an MT unit 26 portion of the IAB node 16 based on RB set configuration information from an IAB donor CU 16a.

[0107] In optional step (100), the IAB node 16 receives a BWP configuration from another network node, e.g., the IAB donor CU 16(a) or a parent IAB node (16b). This may typically be received as part of an initial access procedure from the IAB donor CU 25 via radio resource control (RRC) signaling, e.g., in the serving cell configuration information of the parent IAB node. In NR, the BWP configuration may include up to four different BWPs, and thus the IAB node 16 may receive up to four BWPs as part of the BWP configuration.

[0108] In step (110), the IAB node receives cell and / or carrier configuration for the IAB-DU 27 from the IAB donor CU 25 based on carriers configured by Operation and Administration (OAM). The IAB node may read such information from a file. The cell and carrier configuration information may be included in the IAB-DU serving cell information in SIB1. The authorized IAB-DU cells / carriers are activated by the network (e.g., by the IAB donor CU 25) and the signaling may be handled typically by RRC and F1 messages. Relevant parts of the information include the carrier bandwidths used for the IAB-DU cells. Also, the IAB node's hardware Eh Depending on the configuration, it may contain multiple IAB-DU cells and / or carriers.

[0109] In an optional step (120), the IAB node provides activated IAB-DU cell and / or carrier information to the parent IAB node 16b. Such information may be provided using established signaling, such as F1 or medium access control (MAC) control element (CE), etc.

[0110] Still referring to FIG. 15, in step (130), the IAB node 16 reports to the donor IAB node the resource multiplexing capabilities for the IAB-DU 27 and the IAB-MT unit 26, which may be one or more of the following: ● TDM is needed ● No need for TDM ● What is needed for FDM? ● MT TX and DU TX ● MT TX and DU RX ● MT RX and DU TX, and / or ● MT RX and DU RX.

[0111] The signaling me is included in the F1 message between IAB donor CU25 and IAB-DU27.

[0112] In step (140), the IAB node 16 receives an RB set configuration from the IAB donor CU 25. This configuration may include one or more of the following: ● An indication of the RB set size, i.e., the number of RBs contained in the RB set. Mapping between different RB sets and their corresponding frequency ranges method According to one embodiment, the RB set includes the first RB configured with the lowest carrier frequency. set Starting from , the RB sets are mapped to increasing values ​​across the DU carrier. Depending on the relationship between the RB sets and the carrier bandwidth, the last RB set may or may not exceed the highest carrier frequency. According to one embodiment, the RB sets are successively and incrementally mapped for at least one BWP such that the union of all BWPs includes the frequency ranges to which different RB sets are mapped. In the following, several examples of such mappings are provided. See, for example, Figures 17 and 18. ● Indication of how the RB set is indexed

[0113] The signaling from IAB donor CU25 may be, for example, F1.

[0114] In step (150), the IAB node 16 receives the DU H / S / NA configuration. This configuration may be provided for both the time domain and the frequency domain and may also include indications of which slots should use the time domain multiplexing (TDM) configuration and the frequency domain multiplexing (FDM) configuration, respectively. Alternatively, the TDM / FDM application may be implicitly determined based on specifications, for example, from 3GPP technical standard(s) 38.213 [2], or 38.473 [3], etc. The H / S / NA configuration may include indications of which RB sets should be considered hard, soft, and unavailable, respectively, by the DU 27.

[0115] In step (160), the IAB node 16 derives a mapping between various RB sets and their respective frequency ranges based on the received RB set configuration information from step (130).

[0116] In an optional step (170), the IAB node 16 receives a dynamic availability indication for a subset of the RB sets configured as soft. If both RB sets are indicated as available and no RB set is indicated as available, the use of soft resources by the DU 27 may be determined by specification.

[0117] In an optional step (180), the DU 27 schedules and uses resources according to its H / S / NA configuration and explicit and implicit availability indications. The implicit indication may be that for spatial division multiplexing (SDM) capable IAB nodes 16, the DU 27 may use soft resources implicitly if such use does not impact the operation of the IAB-MT.

[0118] Nodes for donor RB set configuration and H / S / NA configuration 16 is a flow chart of an example process associated with a donor node embodiment. In step (200), the IAB donor CU 25 provides the IAB-MT unit 26 with the configuration of the initial BWP for downlink (DL) and uplink (UL) and additional UL / DL BWP in an RRC message.

[0119] In step (210), the IAB donor CU 25 activates the IAB-DU cell configured by the OAM. The signaling between the IAB donor CU 25 and the IAB-DU 27 may be, for example, F1 and RRC.

[0120] In step (220), the IAB donor CU 25 receives the multiplexing capabilities of the IAB node, which may be one or more of the following: ● TDM is needed ● No need for TDM ● FDM is needed ● MT TX and DU TX ● MT TX and DU RX ● MT RX and DU TX, and / or ● MT RX and DU RX.

[0121] Signaling may be handled by F1 messages between IAB donor CU25 and IAB-DU27.

[0122] In step (230), the IAB donor CU25 provides the IAB-DU27 with an RB set configuration that includes: ● An indication of the RB set size, i.e., the number of RBs contained in the RB set. ● (Optionally) an indication of how to map between each of the different RB sets and the frequency range. According to one embodiment, the RB sets are mapped consecutively and incrementally across the DU carriers, starting from the first RB set at the lowest carrier frequency. Depending on the relationship between the RB sets and the carrier bandwidth, the last RB set may or may not be above the highest carrier frequency. According to one embodiment, the RB sets are mapped consecutively and incrementally for at least one BWP, such that the union of all BWPs includes the frequency range to which the different RB sets are mapped. In the following, several examples of such mappings can be provided. Please refer to the detailed description of Figures 15 and 16. ● (Optionally) an indication as to how the RB set is indexed. See the descriptions of Figures 15 to 21.

[0123] Signaling from IAB donor CU25 to IAB-DU27 may be, for example, via an F1 message.

[0124] In an optional step (240), the IAB donor CU 25 may provide the RB set configuration from step (220), including carrier information for the IAB-DU cell, to the parent IAB node 16b.

[0125] In step (250), the IAB donor CU 25 determines the DU resource configuration of the IAB node (including TDD pattern and H / S / NA attributes) based on the RB set configuration.

[0126] In step (260), the IAB donor CU 25 provides a DU resource configuration (including TDD pattern and H / S / NA attributes) to the IAB node based on the RB set configuration.

[0127] According to some embodiments, for RB sets that do not overlap with any IAB-MT BWP, the IAB donor CU25 does not need to provide frequency domain H / S / NA configuration, thus reducing signaling overhead.

[0128] Embodiments of Parent Node Related to RB Set Configuration and Explicit Availability Indication of Soft Resources FIG. 17 shows a flow chart relating to a parent node embodiment.

[0129] In step (300), the parent IAB node 16b activates a BWP for the IAB-MT unit 26. The signaling can be one of downlink control information (DCI) or medium access control (MAC) control element (CE).

[0130] In an optional step (310), the parent IAB node 16b receives the IAB node's multiplexing capabilities, where the multiplexing capabilities may include one or more of the following: ● TDM is needed ● No need for TDM ● FDM is needed ● MT TX and DU TX ● MT TX and DU RX ● MT RX and DU TX, and / or ● MT RX and DU RX.

[0131] Signaling may be handled by F1 messages between the IAB donor CU25 and the parent IAB-DU27.

[0132] In step (320), the parent IAB node 16b receives the resource configuration of the IAB-DU cell, including the TDD pattern and H / S / NA attributes. The signaling may be handled by F1 messages between the IAB donor CU 25 and the parent IAB-DU 27.

[0133] In step (330), the parent IAB node 16b receives the RB set configuration of the IAB-DU cell and the carrier information of the IAB-DU cell. The signaling may be handled by an F1 message between the IAB donor CU 25 and the parent IAB-DU 27. Alternatively, the signaling may be handled by a MAC CE between the parent IAB node 16b and the IAB node, for example.

[0134] In step (340), the parent IAB node 16b may indicate explicit availability of IAB-DU resources using DCI format 2_5.

[0135] According to some embodiments, the parent IAB node 16b may provide DCI format 2_5 (availability indicator for dynamically indicating availability of IAB-DU soft frequency resources) based on the RB set index. According to some embodiments, based on the RB set index, the IAB donor CU 25 may configure frequency domain resource related RRC parameters, such as AvailabilityCombinationsPerCell and AvailabilityIndicator.

[0136] Referring again to FIG. 15, in step 140, for a given IAB-DU cell / carrier, the IAB-DU 27 may be configured with several resource block sets and the co-located IAB-MT unit 26 may be configured with several bandwidth parts (BWPs). See, for example, FIG. 18. At a given time, only one IAB-MT BWP is active. Since an IAB node cannot use IAB-MT resources that are not included in the configured BWP, there is no need to coordinate the IAB-MT unit 26 and the IAB-DU 27 for resources outside the configured BWP by configuring H / S / NA in the IAB-DU 27. Some embodiments determine the range of RB sets (and therefore the number of RB sets) in the IAB-DU cell by considering the union of the configured IAB-MT BWPs and the value N (i.e., the number of PRBs in the RB set). In this way, IAB-DU resources that are not mapped to an RB set do not receive H / S / NA configuration. Since the configured BWP is known to the parent node, the parent IAB node 16b will know about the configured RB set in IAB-DU 27 without any additional information about the carrier of the IAB-DU cell. As shown in Figure 18, this may result in at least one incomplete RB set having less than N RBs. See RB set 7 in Figure 18.

[0137] FIG. 19 shows an example of one alternative method for configuring RB sets, where the number of RB sets in an IAB-DU cell may be determined by the size of the IAB-DU cell / carrier (i.e., the entire DU cell of the IAB) and the value N. This method may also result in incomplete RB set(s) having less than N RBs. In this method, the IAB-DU resources are always mapped to a specific RB set. For the parent IAB node 16b to know about the RB sets configured in the IAB-DU 27, information about the IAB-DU carrier should be provided to the parent IAB node 16b.

[0138] RB Set Frequency Domain Mapping (i.e., RB Set Indexing) Aspects (Step 140): Depending on how the incomplete RB sets are specified, there are various ways to map frequency domain resources to multiple RB sets in the IAB-DU 27, which is called RB set indexing. Below are some examples assuming that there are a total of M RB sets configured in the IAB-DU cell:

[0139] Type A Indexing Figures 18 and 19 provide two examples of Type A indexing. In Figure 19, starting with the lowest RB of the IAB-DU carrier, the indexing of the RB sets begins with RB set 0, RB set 1, etc. The numbering continues until the last Mth RB set, i.e., RB set 9 in Figure 19. The first M-1 RB sets are complete RB sets, while the last RB set, i.e., the RB set with the highest index, may be an incomplete RB set, i.e., an RB set consisting of less than N RBs.

[0140] Type B Indexing FIG. 20 provides an example of Type B indexing. Starting with the lowest RB of the IAB-DU carrier, the indexing of the RB sets begins with RB set 1, RB set 2, etc. .numbering follows the penultimate, M-1 RB set, i.e., RB set 9 in the figure. The first M-1 RB sets are complete RB sets, but the last RB set may be an incomplete RB set, i.e., it may consist of less than N RBs. The last (potentially incomplete) RB set always has index 0.

[0141] Type C Indexing 21 provides an example of Type C indexing. Starting from the lowest RB of the IAB-DU carrier, the indexing of the RB sets begins with RB set 1, RB set 2, and so on. numberingcontinues until RB set M-1, i.e., RB set 9 in the figure. The last RB set always has index 0. Both the first RB set (RB set 1) and the last RB set (RB set 0) may be incomplete RB set(s). All other RB sets (RB set 2 to RB set M-1) are complete RB sets.

[0142] Type D Indexing Figure 22 shows a method for complete RB set indexing only. Starting from the lowest RB of the IAB-DU carrier, the RB set indexing begins with RB set 0, RB set 1, etc. The numbering continues to the last complete RB set M-1, i.e., RB set 8 in Figure 22.

[0143] According to one embodiment, the incomplete RB set may be merged with a neighboring RB set such that the combined RB set may be a larger RB set. Alternatively, a comparison with a threshold may determine whether the incomplete RB set should be merged or assigned an independent index. Alternatively, the incomplete RB set is not used by either the MT unit 26 or the IAB DU 27. FIG. 22 provides another example of Type-D indexing, where the incomplete RB set may be merged with a neighboring complete set, i.e., RB set 8 in FIG. 23, resulting in an extended RB set having more than N RBs. According to an alternative embodiment, the extended RB set (i.e., having more than N RBs) may have index 0.

[0144] According to some embodiments, a fixed RB set indexing may be applied to the IAB-DU cell, which may be one of Type A, or Type B, or Type C, or Type D mapping methods.

[0145] According to some embodiments, the indexing of the RB set can be changed. The decision of which type of indexing (Type A / Type B / Type C / Type D) should be applied to the IAB-DU cell may be performed in the IAB donor CU 25, and the activation signaling to inform the IAB-DU 27 about the selected type may be, for example, F1 or RRC.

[0146] According to some embodiments, the proposed method can be extended to the case where an IAB-MT unit 26 serving cell (configured with multiple IAB-MT BWPs) overlaps with multiple IAB-DU cells in the frequency domain. Figure 24 shows an example where an IAB-MT serving cell (configured with multiple IAB-MT BWPs) overlaps with two IAB-DU cells in the frequency domain. The RB set configuration can still be determined by the union of the configured IAB-MT BWPs that overlap with each IAB-DU frequency resource.

[0147] Some embodiments may include some or all of the following: Multi-BWP aspects of IAB nodes : 1. A method in an IAB node 16 for resource multiplexing configuration between its DU 27 and MT 26 portions, the method comprising: a. receiving at least one BWP configuration from a network node (e.g., a donor CU25); b. receiving an IAB-DU cell / carrier configuration; and c. reporting resource multiplexing capabilities to donor CU25; and d. receiving an RB set configuration for at least one received BWP, the RB set configuration including an indication of a number of RBs per RB set (number value N) and / or a number of RB sets; e. receiving an IAB-DU resource configuration including an H / S / NA configuration based on the RB set configuration; f. determining an RB set index (or RB set mapping) based on the RB set configuration; g. (Optionally) receiving a dynamic availability indication for a subset of the RB set; and / or h. Scheduling / using resources according to the determined configuration. 2. All of the above and RB set mappings are determined from the union of at least one BWP.

[0148] IAB Node DU Carrier Signaling Aspects 1. A method in an IAB node 16 for resource multiplexing configuration between a DU portion and a MT portion within the IAB node 16, the method comprising: a. receiving an IAB-DU cell / carrier configuration; b. (optionally) signaling the IAB-DU cell / carrier configuration to a parent node 16b; and c. reporting resource multiplexing capabilities to donor CU25; and d. receiving an RB set configuration, including an indication of a size of the RB set and (optionally) an indication of an RB set mapping / indexing method; e. receiving an IAB-DU resource configuration including an H / S / NA configuration based on the RB set configuration; f. determining an RB set index (or RB set mapping) based on the RB set configuration; and / or g. Scheduling / using resources according to the determined configuration.

[0149] IAB Donor Node Aspects 1. A method in a network node for providing an RB set configuration and a resource configuration to an IAB node 16 for resource multiplexing configuration between an IAB-DU part and an IAB-MT part, the method comprising: a. Providing the IAB-Node 16 with the configuration of the BWP; b. activating an IAB-DU cell based on an OAM configuration; and c. receiving at least one multiplexing capability from an IAB node 16; and d. providing an RB set configuration to the IAB node 16, where the RB set configuration includes: i. An indication of the size of the RB set (number N) ii. (Optional) An indication of the methodology for determining the RB set configuration range (e.g., BWP-based or carrier-based); iii. (Optional) An indication of the RB set mapping / indexing method e. (optionally) signaling the IAB-DU cell / carrier configuration to the IAB node's parent node 16b; and f. determining an IAB-DU resource configuration including an H / S / NA configuration based on the RB set configuration; and / or g. signaling the IAB-DU resource configuration to the IAB node.

[0150] IAB Parent Node Behavior 1. A method in an IAB node 16 for indication of explicit availability of a child IAB-DU soft resource, the method comprising: a. Child IAB-MT BWP Yes To enable b. (optionally) receiving resource multiplexing capabilities for the (child) IAB-DU 27 and IAB-MT units 26; and c. receiving a resource configuration of a (child) IAB-DU serving cell, where the resource configuration includes at least: i. TDD patterns, ii. H / S / NA configuration per RB set; d. receiving an RB set configuration of a child IAB-DU serving cell, where the RB set configuration includes at least: i. (Optional) DU cell / carrier configuration ii. Indication of RB set size iii. (Optionally) an indication of an RB set indexing method (e.g., RB set frequency domain mapping); and / or iv. (Optional) An indication of the RB set range (e.g., BWP-based or carrier-based). e. Provide DCI format 2_5 to child IAB nodes for explicit availability indication of IAB-DU RB set. thing This can be based, for example, on the following: i. Child IAB-MT BWP Configuration ii. Child IAB-DU Resource Configuration.

[0151] Some embodiments may include one or more of the following.

[0152] Embodiment A1 A network node 16 comprising a wireless interface and / or a processing circuit configured as follows: Receiving At least one Bandwidth Part (BWP) configuration from an Integrated Access and Backhaul (IAB) donor Concentration Unit (CU) 25; A resource block (RB) set configuration for at least one BWP; and Receive, Here, the RB set configuration indicates the number of RB sets and the number of RBs for each RB set, Determine an RB set index based on the RB set configuration; RBs are scheduled according to the determined RB set configuration.

[0153] Embodiment A2 The network node 16 of embodiment A1, the processing circuitry 36 and / or the radio interface 30 are further configured to: receive IAB distributed unit (DU) cell / carrier configuration and report resource multiplexing capabilities to the donor CU 25;

[0154] Embodiment A3 The network node 16 of any of embodiments A1 and A2, wherein the RB set mapping is determined based at least in part on a union of BWPs.

[0155] Embodiment B1 A method implemented in a network node 16, the method including: Receiving At least one Bandwidth Part (BWP) configuration from an Integrated Access and Backhaul (IAB) donor Concentration Unit (CU) 25; A resource block (RB) set configuration for at least one BWP; and Here, the RB set configuration indicates the number of RB sets and the number of RBs per RB set, determining an RB set index based on the RB set configuration; Scheduling RBs according to the determined RB set configuration.

[0156] Embodiment B2 The method of embodiment B1, further comprising: receiving an IAB distributed unit (DU) cell / carrier configuration. To do , reporting resource multiplexing capabilities to donor CU25.

[0157] Embodiment B3 The method of any of embodiments B1 and B2, wherein the RB set mapping is determined based at least in part on a union of BWPs.

[0158] Embodiment C1 A network node 16 configured as follows and / or including a radio interface 30 and / or including processing circuitry 36 configured as follows. Transmitting At least one Bandwidth Part (BWP) configuration to an Integrated Access and Backhaul (IAB) Distribution Unit (DU) 27; A resource block (RB) set configuration for at least one BWP; where the RB set configuration indicates a number of RB sets and a number of RBs for each RB set; determining an IAB DU resource configuration based at least in part on the RB set configuration; Sending IAB DU resource configuration to IAB DU27.

[0159] Embodiment C2 In the network node 16 of embodiment C1, the network node 16, the processing circuitry 36, and / or the radio interface 30 are further configured to transmit the IAB DU cell / carrier configuration to the parent node 16b of the IAB DU.

[0160] Embodiment C3 The network node of any of embodiments C1 and C2, wherein the RB set configuration indicates a method for determining a range of the RB set configuration.

[0161] Embodiment D1 A method implemented in a network node 16, the method comprising: Transmitting At least one Bandwidth Part (BWP) configuration to an Integrated Access and Backhaul (IAB) Distribution Unit (DU) 27; transmitting a resource block (RB) set configuration for at least one BWP, where the RB set configuration indicates a number of RB sets and a number of RBs per RB set; determining an IAB DU resource configuration based at least in part on the RB set configuration; Sending the IAB DU resource configuration to IAB DU27.

[0162] Embodiment D2 The method of embodiment D1, wherein the network node, processing circuitry, and / or wireless interface is further configured to transmit the IAB DU cell / carrier configuration to a parent node of the IAB DU27.

[0163] Embodiment D3 The method of any one of embodiments D1 and D2, wherein the RB set configuration indicates a method for determining a range of the RB set configuration.

[0164] Embodiment E1 A network node 16 configured and / or including a radio interface 30 and / or including a processing circuit 36 ​​configured as follows: Activating the child node Integrated Access and Backhaul (IAB) Mobile Termination (MT) 26 Bandwidth Part (BWP); and receiving a resource configuration of a serving cell of a child IAB node 16c, 22b; receiving a resource block (RB) set configuration of a serving cell of the child IAB node 16c, 22; Sending an indication of the RB set configuration to the child node.

[0165] Embodiment E2 The network node of embodiment E1, wherein the resource configuration includes at least one of a time division duplex (TDD) pattern and a hard / soft / unavailable (H / S / N) configuration for each RB set.

[0166] Embodiment E3 The network node of any of embodiments E1 and E2, wherein the RB set configuration includes an indication of a size of an RB set.

[0167] Embodiment F1 A method implemented in a network node 16, the method comprising: Activating the child node Integrated Access and Backhaul (IAB) Mobile Termination (MT26) Bandwidth Part (BWP); and receiving a resource configuration of a serving cell of the child IAB node 16c; receiving a resource block (RB) set configuration of a serving cell of a child IAB node 16c; sending an indication of the RB set configuration to the child IAB node 16c; Includes.

[0168] Embodiment F2 The method of embodiment F1, wherein the resource configuration includes at least one of a time division duplex (TDD) pattern and a hard / soft / unavailable (H / S / N) configuration for each RB set.

[0169] Embodiment F3 The method of any of embodiments F1 and F2, wherein the RB set configuration includes an indication of a size of an RB set.

[0170] As will be appreciated by those skilled in the art, the concepts described herein may be implemented in a variety of ways, including: method, System, data processing system, Store executable computer programsThe present disclosure may be embodied as a computer program product and / or computer storage medium. Thus, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects, all generally referred to herein as "circuits" or "modules," and any process, step, action, and / or function described herein may be performed by and / or associated with a corresponding module that may be implemented in software and / or firmware and / or hardware. Furthermore, the present disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized, including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0171] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer (to create a special purpose computer), a special purpose computer, or other programmable data processing apparatus to create a machine such that the instructions, executed via the processor of the computer or other programmable data processing apparatus, create means for implementing the function / acts specified in the block or blocks of the flowchart illustrations and / or block diagrams.

[0172] These computer program instructions may also be stored in a computer-readable memory or storage medium that can instruct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture that includes instruction means that implement the function / act specified in the block or blocks of the flowcharts and / or block diagrams.

[0173] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus and cause the computer or other programmable data processing apparatus to perform a series of operational steps to generate a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions / operations specified in the blocks or blocks of the flowcharts and / or block diagrams.

[0174] It should be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational diagrams. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending on the functions / acts involved. Additionally, some of the figures may be illustrated as separate blocks of communication. direction Although arrows are included on the communication paths to illustrate this, it should be understood that communication may occur in the direction opposite to that depicted arrow.

[0175] Computer program code for carrying out the operations of the concepts described herein may be written in an object-oriented programming language such as Python, Java@ or C++. However, computer program code for carrying out the operations of the present disclosure may also be written in a conventional procedural programming language such as the "C" programming language. The program code may run entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer, partially on a remote computer, or entirely on a remote computer. In the latter case, the remote computer may be connected to the user's computer via a local area network (LAN) or wide area network (WAN) or may be connected to an external computer (e.g., via the Internet using an Internet Service Provider).

[0176] In this specification, the above description and drawings Related Many different embodiments have been disclosed. It will be understood that literally describing and illustrating every combination and subcombination of these embodiments would be unduly repetitive and obfuscated. Thus, all embodiments can be combined in any manner and / or combination, and the specification, including the drawings, shall be construed as constituting a complete written description of all combinations and subcombinations of the embodiments described herein, and methods and processes for making and using them, and shall support claims to any such combinations or subcombinations.

[0177] It will be appreciated by those skilled in the art that the embodiments described herein are not limited to those particularly shown and described hereinabove. In addition, it should be noted that, unless otherwise noted above, all of the accompanying drawings are not to scale. Various modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

1. A method in a first integrated access and backhaul (IAB) node (16b), the first IAB node (16b) having a mobile termination (MT) unit (26) and a distribution unit (DU) (27), the method comprising: receiving an IAB-DU cell and carrier configuration from a second network node (S34), where the second network node is one of an IAB donor concentration unit (25) and a parent IAB node (16b), the second network node being upstream of the first IAB node; Reporting resource multiplexing capabilities to the second network node (S36); and receiving a resource block (RB) set configuration from the second IAB network node (S38), where the RB set configuration comprises an IAB-DU hard / soft / unavailable (H / S / NA) resource configuration, the IAB-DU H / S / NA resource configuration being based at least in part on the resource multiplexing capability; Mapping (S40) a resource block (RB) set of the DU (27) based at least in part on the IAB-DU H / S / NA resource configuration and the IAB-DU cell and carrier configuration; A method comprising:

2. 2. The method of claim 1, further comprising: receiving a BWP configuration from the second network node; and mapping the RB set to the BWP based in part on the BWP configuration.

3. 3. The method of claim 2, wherein the mapping comprises: allocating an integer number N of physical resource blocks (PRBs) to each RB set of a first set of RB sets; and, if the IAB-DU frequency resources do not encompass all available PRBs, allocating a portion of the integer number N of PRBs to the remaining RB sets.

4. 4. The method of claim 3, wherein the mapping depends at least in part on whether an RB set of size N can encompass all available RBs, where N is an integer greater than one.

5. The method according to any one of claims 1 to 3, wherein if the RB sets of an IAB-DU H / S / NA resource configuration exceed N times the maximum number M of RB sets, the remaining RBs that are not part of the RB set configuration are considered to be included in the last RB set, where N and M are integers greater than zero.

6. The method according to any one of claims 1 to 5, wherein the RB set configuration comprises an index pointing to the lowest RB in the first IAB-DU cell-and-carrier configuration.

7. The method according to any one of claims 1 to 6, wherein a starting RB index of an initial RB set for the IAB-DU H / S / NA resource configuration is the lowest RB index in the IAB-DU cell.

8. 8. The method of claim 1, wherein the IAB-DU cell and carrier configuration is based at least in part on carriers received from the IAB donor CU (25) and configured by an Operations and Management Function (OAM).

9. 9. The method of claim 1, wherein the resource multiplexing capabilities for the MT unit (26) and the DU (27) of the first IAB node (16b) include at least one of an indication of a time division multiplexing (TDM) requirement, an indication of a frequency division multiplexing (FDM) requirement, and an indication of a transmission / reception status of the DU (27) and the MT unit (26).

10. 10. The method of claim 1, further comprising receiving an RB set configuration from the second network node, the RB set configuration including at least one of an indication of an RB set size, an indication of a mapping method for determining the mapping of RB sets, an indication of a number of RB sets, and an indication of an indexing method for indexing RB sets.

11. 11. The method of claim 1, wherein the IAB-DU H / S / NA resource configuration includes at least one of a time domain configuration, a frequency domain configuration, and an indication of which slots are to be time domain multiplexed (TDM) and which slots are to be frequency domain multiplexed (FDM).

12. The method of any one of claims 1 to 11, further comprising receiving an availability indication for a subset of a soft configured RB set.

13. 13. The method of claim 1, wherein the DU (27) of the first IAB node (16b) schedules resources based at least in part on the IAB-DU H / S / NA resource configuration.

14. The method according to any one of claims 1 to 13, wherein the maximum number of contiguous and non-overlapping RB sets configurable per cell in the IAB-DU cell-and-carrier configuration is eight.

15. A first integrated access and backhaul (IAB) node, the first IAB node (16b) having a mobile termination (MT) unit (26) and a distribution unit (DU) (27), the first IAB node (16b) comprising: A wireless interface (30), receiving an IAB-DU cell and carrier configuration from a second network node, where the second network node is one of an IAB donor concentration unit (CU) (25) and a parent IAB node (16b), the second network node being upstream of the first IAB node; reporting resource multiplexing capabilities to the second network node; a radio interface (30) configured to receive a resource block (RB) set configuration from a second IAB network node, where the RB set configuration comprises an IAB-DU Hard / Soft / Flexible (H / S / NA) resource configuration, the IAB-DU H / S / NA resource configuration being based at least in part on the resource multiplexing capability; a processing circuit (36) in communication with the radio interface (30) and configured to map a resource block (RB) set of the DU (27) based at least in part on the IAB-DU H / S / NA resource configuration and the IAB-DU cell and carrier configuration; A first IAB node,

16. 16. The first IAB node of claim 15, wherein the radio interface is further configured to receive a BWP configuration from the second network node and to map the RB set to the BWP based in part on the BWP configuration.

17. 17. The first IAB node of claim 16, wherein the mapping includes: allocating an integer number N of physical resource blocks (PRBs) to each RB set of the first set of RB sets; and, if IAB-DU H / S / NA frequency resources do not encompass all available PRBs, allocating a portion of the integer number N of PRBs to remaining RB sets.

18. 20. The first IAB node of claim 17, wherein the mapping depends at least in part on whether an RB set of size N can encompass all available RBs, where N is an integer greater than 1.

19. 18. The first IAB node according to any one of claims 15 to 17, wherein if the RB sets of an IAB-DU H / S / NA resource configuration exceed N times the maximum number M of RB sets, the remaining RBs that are not part of the RB set configuration are considered to be included in the last RB set, where N and M are integers greater than 0.

20. 20. The first IAB node according to claim 15, wherein the RB set configuration includes an index pointing to the lowest RB in the first IAB-DU cell and carrier configuration.

21. The method according to any one of claims 15 to 20, wherein a starting RB index of an initial RB set for the IAB-DU H / S / NA resource configuration is the lowest RB index in the IAB-DU cell.

22. 22. The first IAB node of claim 15, wherein the IAB-DU cell and carrier configuration is based at least in part on carriers received from the IAB donor CU (25) and configured by an Operations and Management Function (OAM).

23. 23. A first IAB node according to claim 15, wherein the resource multiplexing capabilities for the MT unit (26) and DU (27) of the first IAB node include at least one of an indication of a time division multiplexing (TDM) requirement, an indication of a frequency division multiplexing (FDM) requirement, and an indication of a transmit / receive state of the DU (27) and the MT unit (26).

24. 24. The first IAB node of any one of claims 15 to 23, wherein the radio interface (30) is further configured to receive an RB set configuration from the second network node, the RB set configuration including at least one of an indication of an RB set size, an indication of a mapping method for determining a mapping of RB sets, an indication of a number of RB sets, and an indication of an indexing method for indexing RB sets.

25. 25. The first IAB node of claim 15, wherein the IAB-DU H / S / NA resource configuration includes at least one of a time domain configuration, a frequency domain configuration, and an indication of which slots are to be time domain multiplexed (TDM) and which slots are to be frequency domain multiplexed (FDM).

26. 26. The first IAB node of claim 15, wherein the radio interface (30) is further configured to receive an availability indication for a subset of a soft configured RB set.

27. 27. The first IAB node of claim 15, wherein the DU (27) of the first IAB node (16b) schedules resources based at least in part on the IAB-DU H / S / NA resource configuration.

28. 28. The first IAB node according to claim 15, wherein the maximum number of contiguous and non-overlapping RB sets configurable per cell of the IAB-DU cell and carrier configuration is eight.

29. 1. A method in an integrated access and backhaul (IAB) donor node (16a), the IAB donor node (16a) in communication with a first IAB node (16b, 16c), the first IAB node (16b, 16c) being downstream from the IAB donor node (16a), the method comprising: Receiving resource multiplexing capabilities from the first IAB node (16b, 16c) (S42); determining (S44) a resource block (RB) set configuration based at least in part on the resource multiplexing capability; determining (S46) a DU resource configuration for the first IAB node (16b, 16c) based at least in part on the RB set configuration; and transmitting the DU resource configuration to the first IAB node (16b, 16c) (S48); A method comprising:

30. 30. The method of claim 29, further comprising omitting a frequency domain configuration of hard / soft / not applicable (H / S / NA) attributes from the DU resource configuration if an RB set of the RB set configuration does not overlap with a BWP.

31. 31. The method of claim 29, wherein the DU resource configuration includes an IAB-DU cell and carrier configuration for the first IAB node (16b, 16c).

32. The method according to any one of claims 29 to 31, wherein the maximum number of contiguous and non-overlapping RB sets configurable per cell in the IAB-DU cell-and-carrier configuration is eight.

33. 33. The method of any one of claims 29 to 32, wherein the RB set configuration includes at least one of an indication of an RB set size, a number of RB sets, an indication of a mapping method for determining a mapping of RB sets by the first IAB node, and an indication of an indexing method for indexing RB sets.

34. 34. The method of claim 29, wherein transmitting the DU resource configuration to the first IAB node (16b, 16c) comprises transmitting the DU resource configuration via an F1 application protocol (AP).

35. An integrated access and backhaul (IAB) donor node, the IAB donor node (16a) in communication with a first IAB node (16b, 16c), the first IAB node (16b, 16c) being downstream from the IAB donor node, the IAB donor node (16b, 16c) comprising: a radio interface (30) configured to receive resource multiplexing capabilities from the first IAB node; a processing circuit (36) in communication with the wireless interface (30), determining a resource block (RB) set configuration based at least in part on the resource multiplexing capability; and a processing circuit (36) configured to determine a DU resource configuration for the first IAB node (16b, 16c) based at least in part on the RB set configuration; The IAB donor node, wherein the wireless interface is further configured to transmit the DU resource configuration to the first IAB node (16b, 16c).

36. 36. The IAB donor node of claim 35, wherein the processing circuitry is further configured to omit a frequency domain configuration of hard / soft / not applicable (H / S / NA) attributes from the DU resource configuration if an RB set of the RB set configuration does not overlap with a BWP.

37. 37. The IAB donor node of claim 35 or 26, wherein the DU resource configuration includes an IAB-DU cell-and-carrier configuration for the first IAB (16b, 16c).

38. 38. The IAB donor node according to claim 35, wherein the maximum number of contiguous and non-overlapping RB sets configurable per cell in the IAB-DU cell and carrier configuration is eight.

39. 39. The IAB donor node of claim 35, wherein the RB set configuration includes at least one of an indication of an RB set size, a number of RB sets, an indication of a mapping method for determining a mapping of RB sets by the first IAB node, and an indication of an indexing method for indexing RB sets.

40. 40. The IAB donor node of claim 35, wherein the wireless interface (30) is further configured to transmit the DU resource configuration to the first IAB node via an F1 application protocol (AP).

41. 1. A method in a parent integrated access and backhaul (IAB) node (16b), the parent IAB node (16b) in communication with an IAB donor node (16a) and a first IAB node (16c), the parent IAB node (16b) being downstream of the IAB donor node (16a) and upstream of the first IAB node (16c), the method comprising: Optionally activating (S50) a mobile termination (MT) unit bandwidth part for said first IAB node (16c); receiving (S52) a resource block (RB) set configuration from the IAB donor node (16a), where the RB set configuration includes a distributed unit (DU) resource configuration per cell of the first IAB node (16c); receiving (S54) a resource block (RB) set configuration per cell of the first IAB node (16c) from one of the IAB donor node (16a) and the first IAB node (16c); and transmitting (S56) an indication of DU resource availability to the first IAB node (16c), the availability of the DU resources being based at least in part on the DU resource configuration and the RB set configuration per cell of the first IAB node (16c).

42. 42. The method of claim 41, wherein the DU resource configuration for each cell includes at least one hard / soft / unavailable (H / S / NA) attribute of the DU resource configuration.

43. 43. The method of claim 41, wherein the RB set configuration for a cell includes an IAB-DU carrier configuration for the cell.

44. The method according to any one of claims 41 to 43, wherein the maximum number of contiguous and non-overlapping RB sets configurable per cell in the IAB-DU cell-and-carrier configuration is eight.

45. A method according to any one of claims 41 to 44, wherein the indication of availability of the DU resource is transmitted in downlink control information in DCI format 2_5.

46. 46. ​​The method according to any one of claims 41 to 45, further comprising: considering remaining RBs that are not part of the RB set configuration to be included in a last RB set if the RB set corresponding to the IAB-DU H / S / NA resource configuration exceeds N times a maximum number M of RB sets, where N and M are integers greater than zero.

47. a parent integrated access and backhaul (IAB) node (16b), the parent IAB node (16b) in communication with an IAB donor node (16a) and a first IAB node (16c), the parent IAB node being downstream from the IAB donor node and upstream from the first IAB node (16c), the parent IAB node (16b) a processing circuit configured to optionally activate a mobile termination (MT) unit bandwidth part for the first IAB node (16c); a wireless interface (30) in communication with the processing circuit (36), receiving a per-cell distributed unit (DU) resource configuration for the first IAB node (16c) from the IAB donor node (16a); receiving, from one of the IAB donor node (16a) and the first IAB node (16c), a resource block (RB) set configuration for each cell of the first IAB node (16c); a parent IAB node configured to transmit an indication of availability of DU resources to the first IAB node (16c), the availability of DU resources being based at least in part on the DU resource configuration and the RB set configuration of each cell of the first IAB node (16c).

48. 48. The parent IAB node of claim 47, wherein the DU resource configuration for each cell includes at least one hard / soft / unavailable (H / S / NA) attribute of the DU resource configuration.

49. 49. A parent IAB node as recited in any of claims 47 and 48, wherein the RB set configuration for a cell is based at least in part on an IAB-DU carrier configuration for the cell.

50. 50. A parent IAB node according to any one of claims 47 to 49, wherein the maximum number of contiguous and non-overlapping RB sets configurable per cell of the IAB-DU cell-and-carrier configuration is eight.

51. A parent IAB node according to any one of claims 47 to 50, wherein the indication of availability of DU resources is transmitted in downlink control information in DCI format 2_5.

52. 52. A parent IAB node according to any one of claims 47 to 51, wherein if the RB set corresponding to the IAB-DU H / S / NA resource configuration exceeds N times the maximum number M of RB sets, the remaining RBs that are not part of the RB set configuration are considered to be included in the last RB set, where N and M are integers greater than 0.

Images