Method and apparatus for determining frequency domain resources

Abstract

The IAB node includes a receiver configured to receive information from a parent node or central unit (CU), where the information indicates at least one of a first frequency domain (FD) resource configuration associated with at least one bandwidth portion of an IAB mobile terminal (MT), a second FD resource configuration associated with an RB set configuration of an IAB distributed unit (DU), or a third FD resource configuration associated with the RB set configuration of the IAB DU, and a processor configured to determine, based on the first FD resource configuration, one or more FD resources for DL ​​or UL communication in the IAB MT and / or, based on at least one of the second FD resource configuration and the third FD resource configuration, FD resource units for resource allocation in parent links and child links of the IAB node.

Description

Technical Field

[0001] Embodiments of the present application relate to wireless communication technologies, and more particularly, to a method and apparatus for determining frequency domain resources.

Background Art

[0002] It has been agreed in RAN1#105e that the minimum resource size for constituting the frequency domain granularity is a set of N resource blocks (RBs), i.e., an RB set, and candidate values for N may include {4, 8, 16, other values}, provided that N is at least the number of physical resource blocks (PRBs) corresponding to the number of mobile terminals (MTs) among the physical resource blocks (PRBs) of a resource block group (RBG).

[0003] It has been agreed in RAN1#106e that N is the configured number of physical resource blocks (PRBs) and is configured by a central unit (CU), provided that the value for N may include {2, 4, 8, 16, 32, 64}.

Summary of the Invention

Problems to be Solved by the Invention

[0004] The present disclosure proposes several solutions for determining a distributed unit (DU) resource block (RB) set of an integrated access and backhaul (IAB) node.

Means for Solving the Problems

[0005] According to some embodiments of the present application, an integrated access backhaul (IAB) node includes a receiver configured to receive information from a parent node or central unit (CU), wherein the information indicates at least one of a first frequency domain resource configuration associated with at least one bandwidth part (BWP) of an IAB mobile terminal (MT), a second frequency domain resource configuration associated with a resource block (RB) set configuration of an IAB distributed unit (DU), or a third frequency domain resource configuration associated with an RB set configuration of an IAB DU; and a processor configured to determine one or more frequency domain resources for downlink or uplink communication in an IAB MT based on the first frequency domain resource configuration, and / or frequency domain resource units for resource allocation in parent and child links of an IAB node based on at least one of the second and third frequency domain resource configurations. For example, the information may represent 1) a first frequency domain resource, 2) a second frequency domain resource, 3) a third frequency domain resource, 4) a first frequency domain resource and a second frequency domain resource, 5) a first frequency domain resource and a third frequency domain resource, 6) a second frequency domain resource and a third frequency domain resource, or 7) a first frequency domain resource, a second frequency domain resource, and a third frequency domain resource.

[0006] In some embodiments, the first frequency-domain resource configuration is based on the size of the first RBG of at least one BWP of the IAB MT.

[0007] In some embodiments, the second frequency domain resource configuration is based on the size of the first set of RBs in the IAB DU, and its size differs from the sizes of the other sets of RBs in the IAB DU.

[0008] In some embodiments, the third frequency domain resource configuration is based on the size of the last RB set in the IAB DU, and its size differs from the sizes of the other RB sets in the IAB DU.

[0009] In some embodiments, the first frequency domain resource is determined based on at least one start boundary and reference start boundary of at least one BWP configuration, as well as at least one of the maximum RBG sizes among all BWPs in the IAB MT.

[0010] In some embodiments, the second frequency domain resource is determined based on the IAB DU carrier start boundary, the reference start boundary, and at least one of the maximum RBG size among all BWPs of the IAB MT.

[0011] In some embodiments, the third frequency domain resource is determined based on the termination boundary of the IAB DU carrier, the reference start boundary, the maximum RBG size among all BWPs of the IAB MT, and at least one of the termination boundaries of at least one BWP of the IAB MT.

[0012] In some embodiments, the reference start boundary is either explicitly configured, implicitly determined based on the start frequency domain position of the carrier, implicitly determined based on the start frequency domain position of the synchronization signal / physical broadcast channel (SSB), or implicitly determined based on the start frequency domain position of the minimum indexed BWP of the IAB MT.

[0013] In some embodiments, if the second frequency domain resource does not overlap with any PRB or any active BWP among the IAB MTs, the second frequency domain resource is determined to be a hard resource.

[0014] In some embodiments, if the third frequency domain resource does not overlap with any PRB or any active BWP of the IAB MT, the third frequency domain resource is determined to be a hard resource.

[0015] In some embodiments, when a time-domain resource is associated with frequency-domain multiplexing between parent and child links of an IAB node, at least one of a first frequency-domain resource, a second frequency-domain resource, and a third frequency-domain resource is applied to the time-domain resource.

[0016] In some embodiments, at least one of the second frequency domain resource and the third frequency domain resource is associated with the BWP index of the IAB MT.

[0017] In some embodiments, the BWP index includes a downlink (DL) BWP index, an uplink (UL) BWP index, or a combined index based on the DL BWP index and the UL BWP index.

[0018] In some embodiments, the receiver is further configured to receive a mapping relationship between the BWP index and at least one of the second and third frequency domain resources from the CU or parent node.

[0019] In some embodiments, the processor is further configured to determine that the BWP index, which should be a DL-active BWP index or a UL-active BWP index, is based on the transmission direction on the parent link of the network node.

[0020] In some embodiments, the first frequency domain resource, the second frequency domain resource, and the third frequency domain resource are represented by several PRBs associated with a reference SCS.

[0021] In some embodiments, the SCS is either explicitly configured, implicitly determined based on the SCS of the IAB MT BWP, or is the SCS of the IAB MT BWP having the lowest frequency band.

[0022] According to some embodiments of the present application, an integrated access and backhaul (IAB) node includes a transmitter configured to transmit information to a parent node or a central unit (CU), the information including at least one of the following: one or more bandwidth part (BWP) configurations, or physical resource block (PRB) numbers associated with a reference subcarrier spacing (SCS).

[0023] In some embodiments, one or more BWP configurations include at least one of the following: the BWP size for the BWP, the SCS associated with the BWP, and the resource block group (RBG) configuration of the BWP.

[0024] In some embodiments, the information is used to determine the size of a set of resource blocks (RBs) for an IAB distributed unit (DU).

[0025] In some embodiments, the transmitter is further configured to transmit a reference SCS having a PRB number.

[0026] According to some embodiments of the present application, an integrated access and backhaul (IAB) node includes a transmitter configured to transmit information to a child node or a distributed unit (DU), the information indicating at least one of a first frequency region resource configuration associated with at least one bandwidth part (BWP) of an IAB mobile terminal (MT), a second frequency region resource configuration associated with a resource block (RB) set configuration of the IAB distributed unit (DU), or a third frequency region resource configuration associated with the RB set configuration of the IAB DU.

[0027] In some embodiments, the first frequency domain resource configuration is based on the size of the first resource block group (RBG) of at least one bandwidth part (BWP) of the IAB mobile terminal (MT).

[0028] In some embodiments, the second frequency domain resource configuration is based on the size of the first resource block (RB) set of the IAB distributed unit (DU), and the size is different from that of other RB sets of the IAB DU.

[0029] In some embodiments, the third frequency domain resource configuration is based on the size of the last RB set of the IAB DU, and the size is different from that of other RB sets of the IAB DU.

[0030] In some embodiments, the first frequency domain resource is determined based on at least one of the start boundary of at least one BWP configuration, the reference start boundary, and at least one of the maximum RBG sizes among all BWPs of the IAB MT.

[0031] In some embodiments, the second frequency domain resource is determined based on at least one of the start boundary of the IAB DU carrier, the reference start boundary, and at least one of the maximum RBG sizes among all BWPs of the IAB MT. [[ID={17]]

[0032] In some embodiments, the third frequency domain resource is determined based on at least one of the end boundary of the IAB DU carrier, the reference start boundary, the maximum RBG size among all BWPs of the IAB MT, and the end boundary of at least one BWP of the IAB MT.

[0033] In some embodiments, the reference start boundary is explicitly configured, implicitly determined based on the start frequency domain position of the carrier, implicitly determined based on the start frequency domain position of the synchronization signal / physical broadcast channel (SSB), or implicitly determined based on the start frequency domain position of the BWP with the minimum index of the IAB MT.

[0034] In some embodiments, if the second frequency domain resource does not overlap with any PRB or any active BWP among the IAB MTs, the second frequency domain resource is determined to be a hard resource.

[0035] In some embodiments, if the third frequency domain resource does not overlap with any PRB or any active BWP in the IAB MT, the third frequency domain resource is determined to be a hard resource.

[0036] In some embodiments, when a time-domain resource is associated with frequency-domain multiplexing between parent and child links of an IAB node, at least one of a first frequency-domain resource, a second frequency-domain resource, and a third frequency-domain resource is applied to the time-domain resource.

[0037] In some embodiments, at least one of the second frequency domain resource and the third frequency domain resource is associated with the BWP index of the IAB MT.

[0038] In some embodiments, the BWP index includes a downlink (DL) BWP index, an uplink (UL) BWP index, or a combined index based on the DL BWP index and the UL BWP index.

[0039] In some embodiments, the transmitter is further configured to transmit a mapping relationship between the BWP index and at least one of a second frequency domain resource and a third frequency domain resource to the DU or child node.

[0040] In some embodiments, the first frequency domain resource, the second frequency domain resource, and the third frequency domain resource are represented by several PRBs associated with a reference SCS.

[0041] In some embodiments, the SCS is either explicitly configured, implicitly determined based on the SCS of the IAB MT BWP, or is the SCS of the IAB MT BWP having the lowest frequency bandwidth.

[0042] According to some embodiments of the present application, an integrated access backhaul (IAB) node includes a receiver configured to receive information from a parent node or central unit (CU), the information including at least one of the following: one or more bandwidth portion (BWP) configurations, or a physical resource block (PRB) number associated with a reference subcarrier interval (SCS).

[0043] In some embodiments, one or more BWP configurations include at least one of the following: a BWP size for the BWP, an SCS associated with the BWP, and a resource block group (RBG) configuration for the BWP.

[0044] In some embodiments, the information is used to determine the size of the resource block (RB) set for the IAB distributed unit (DU).

[0045] In some embodiments, the reference SCS is determined based on the frequency bandwidth or is the SCS of the BWP having the minimum index.

[0046] According to some embodiments of the present application, a method for determining frequency domain resources includes receiving information from a parent node or central unit (CU) indicating at least one of a first frequency domain resource configuration associated with at least one bandwidth portion (BWP) of an IAB mobile terminal (MT), a second frequency domain resource configuration associated with a resource block (RB) set configuration of an IAB distributed unit (DU), or a third frequency domain resource configuration associated with an RB set configuration of an IAB DU, and determining one or more frequency domain resources for downlink or uplink communication in an IAB MT based on the first frequency domain resource configuration, and / or frequency domain resource units for resource allocation in parent and child links of an IAB node based on at least one of the second and third frequency domain resource configurations.

[0047] In some embodiments, the first frequency-domain resource configuration is based on the size of the first RBG of at least one BWP of the IAB MT.

[0048] In some embodiments, the second frequency domain resource configuration is based on the size of the first set of RBs in the IAB DU, and its size differs from the sizes of the other sets of RBs in the IAB DU.

[0049] In some embodiments, the third frequency domain resource configuration is based on the size of the last RB set in the IAB DU, and its size differs from the sizes of the other RB sets in the IAB DU.

[0050] In some embodiments, the first frequency domain resource is determined based on at least one of the following: a starting boundary for at least one BWP configuration, a reference starting boundary, and the maximum RBG size among all BWPs in the IAB MT.

[0051] In some embodiments, the second frequency domain resource is determined based on the IAB DU carrier start boundary, the reference start boundary, and at least one of the maximum RBG size among all BWPs of the IAB MT.

[0052] In some embodiments, the third frequency domain resource is determined based on at least one of the following: the termination boundary of the IAB DU carrier, the reference start boundary, the maximum RBG size among all BWPs of the IAB MT, and the termination boundary of at least one BWP of the IAB MT.

[0053] In some embodiments, the reference start boundary is either explicitly configured, implicitly determined based on the start frequency domain position of the carrier, implicitly determined based on the start frequency domain position of the synchronization signal / physical broadcast channel (SSB), or implicitly determined based on the start frequency domain position of the minimum indexed BWP of the IAB MT.

[0054] In some embodiments, if the second frequency domain resource does not overlap with any PRB or any active BWP among the IAB MTs, the second frequency domain resource is determined to be a hard resource.

[0055] In some embodiments, if the third frequency domain resource does not overlap with any PRB or any active BWP in the IAB MT, the third frequency domain resource is determined to be a hard resource.

[0056] In some embodiments, when a time-domain resource is associated with frequency-domain multiplexing between parent and child links of an IAB node, at least one of a first frequency-domain resource, a second frequency-domain resource, and a third frequency-domain resource is applied to the time-domain resource.

[0057] In some embodiments, at least one of the second frequency domain resource and the third frequency domain resource is associated with the BWP index of the IAB MT.

[0058] In some embodiments, the BWP index includes a downlink (DL) BWP index, an uplink (UL) BWP index, or a combined index based on the DL BWP index and the UL BWP index.

[0059] In some embodiments, the method further includes receiving a mapping relationship between a BWP index and at least one of a second frequency domain resource and a third frequency domain resource from a CU or parent node.

[0060] In some embodiments, the method further includes determining that the BWP index, which should be a DL-active BWP index or a UL-active BWP index, is based on the transmission direction on the parent link of the network node.

[0061] In some embodiments, the first frequency domain resource, the second frequency domain resource, and the third frequency domain resource are represented by several PRBs associated with a reference SCS.

[0062] In some embodiments, the SCS is either explicitly configured, implicitly determined based on the SCS of the IAB MT BWP, or is the SCS of the IAB MT BWP having the lowest frequency bandwidth.

[0063] According to some embodiments of the present application, a method for determining frequency domain resources includes transmitting information to a parent node or central unit (CU), the information including at least one of the following: one or more bandwidth portion (BWP) configurations or physical resource block (PRB) numbers associated with a reference subcarrier interval (SCS).

[0064] In some embodiments, one or more BWP configurations include at least one of the following: a BWP size for the BWP, an SCS associated with the BWP, and a resource block group (RBG) configuration for the BWP.

[0065] In some embodiments, the information is used to determine the size of the resource block (RB) set for the IAB distributed unit (DU).

[0066] In some embodiments, the transmitter is further configured to transmit a reference SCS having a PRB number.

[0067] According to some embodiments of the present application, a method for determining frequency domain resources includes transmitting information to a child node or distributed unit (DU) that indicates at least one of a first frequency domain resource configuration associated with at least one bandwidth portion (BWP) of an IAB mobile terminal (MT), a second frequency domain resource configuration associated with a resource block (RB) set configuration of an IAB distributed unit (DU), or a third frequency domain resource configuration associated with an RB set configuration of an IAB DU.

[0068] In some embodiments, the first frequency-domain resource configuration is based on the size of the first RBG of at least one BWP of the IAB MT.

[0069] In some embodiments, the second frequency domain resource configuration is based on the size of the first set of RBs in the IAB DU, and its size differs from the sizes of the other sets of RBs in the IAB DU.

[0070] In some embodiments, the third frequency domain resource configuration is based on the size of the last RB set in the IAB DU, and its size differs from the sizes of the other RB sets in the IAB DU.

[0071] In some embodiments, the first frequency domain resource is determined based on at least one start boundary and reference start boundary of at least one BWP configuration, as well as at least one of the maximum RBG sizes among all BWPs in the IAB MT.

[0072] In some embodiments, the second frequency domain resource is determined based on the IAB DU carrier start boundary, the reference start boundary, and at least one of the maximum RBG size among all BWPs of the IAB MT.

[0073] In some embodiments, the third frequency domain resource is determined based on the termination boundary of the IAB DU carrier, the reference start boundary, the maximum RBG size among all BWPs of the IAB MT, and at least one of the termination boundaries of at least one BWP of the IAB MT.

[0074] In some embodiments, the reference start boundary is either explicitly configured, implicitly determined based on the start frequency domain position of the carrier, implicitly determined based on the start frequency domain position of the synchronization signal / physical broadcast channel (SSB), or implicitly determined based on the start frequency domain position of the minimum indexed BWP of the IAB MT.

[0075] In some embodiments, if the second frequency domain resource does not overlap with any PRB or any active BWP among the IAB MTs, the second frequency domain resource is determined to be a hard resource.

[0076] In some embodiments, if the third frequency domain resource does not overlap with any PRB or any active BWP in the IAB MT, the third frequency domain resource is determined to be a hard resource.

[0077] In some embodiments, when a time-domain resource is associated with frequency-domain multiplexing between parent and child links of an IAB node, at least one of a first frequency-domain resource, a second frequency-domain resource, and a third frequency-domain resource is applied to the time-domain resource.

[0078] In some embodiments, at least one of the second frequency domain resource and the third frequency domain resource is associated with the BWP index of the IAB MT.

[0079] In some embodiments, the BWP index includes a downlink (DL) BWP index, an uplink (UL) BWP index, or a combined index based on the DL BWP index and the UL BWP index.

[0080] In some embodiments, the method further includes sending a mapping relationship between the BWP index and at least one of a second frequency domain resource and a third frequency domain resource to the DU or child node.

[0081] In some embodiments, the first frequency domain resource, the second frequency domain resource, and the third frequency domain resource are represented by several PRBs associated with a reference SCS.

[0082] In some embodiments, the SCS is either explicitly configured, implicitly determined based on the SCS of the IAB MT BWP, or is the SCS of the IAB MT BWP having the lowest frequency bandwidth.

[0083] According to some embodiments of the present application, a method for determining frequency domain resources includes receiving information from a parent node or central unit (CU), the information including at least one of the following: one or more bandwidth portion (BWP) configurations, or a physical resource block (PRB) number associated with a reference subcarrier interval (SCS).

[0084] In some embodiments, one or more BWP configurations include at least one of the following: a BWP size for the BWP, an SCS associated with the BWP, and a resource block group (RBG) configuration for the BWP.

[0085] In some embodiments, the information is used to determine the size of the resource block (RB) set for the IAB distributed unit (DU).

[0086] In some embodiments, the reference SCS is determined based on the frequency bandwidth or is the SCS of the BWP having the minimum index. [Brief explanation of the drawing]

[0087] [Figure 1] This figure shows an exemplary IAB system according to several embodiments of the present disclosure. [Figure 2] This figure illustrates an exemplary description of links between IAB nodes according to some embodiments of the present disclosure. [Figure 3] This figure illustrates an exemplary description of determining the DU RB set configuration according to some embodiments of the present disclosure. [Figure 4] This figure shows another exemplary description of determining the DU RB configuration set according to some embodiments of the present disclosure. [Figure 5] This figure shows another exemplary description of determining the DU RB configuration set according to some embodiments of the present disclosure. [Figure 6] This figure illustrates an exemplary description of determining the DU RB set configuration according to some embodiments of the present disclosure. [Figure 7] This figure shows a method for wireless communication according to some embodiments of the present disclosure. [Figure 8] This is an exemplary block diagram of apparatus 800 according to some embodiments of the present disclosure. [Modes for carrying out the invention]

[0088] The detailed description in the accompanying drawings is intended to describe the currently preferred embodiments of this application and is not intended to represent the only form in which this application may be practiced. It should be understood that the same or equivalent functions may be achieved by various embodiments intended to be covered within the spirit and scope of this disclosure.

[0089] While operations are shown in a specific order in the drawings, those skilled in the art will readily recognize that such operations do not necessarily need to be performed in a specific or sequential order as shown, or that all illustrated operations may be performed, with one or more operations sometimes omitted, in order to achieve a desired result. Furthermore, the drawings may schematically illustrate another exemplary process in the form of a flowchart. However, other operations not illustrated may be incorporated into the schematically illustrated exemplary process. For example, one or more additional operations may be performed before, after, simultaneously with, or in between any of the illustrated operations. In some environments, multitasking and parallel processing may be advantageous.

[0090] Herein, several embodiments of the present application are described in detail, examples of which are shown in the accompanying drawings. For ease of understanding, embodiments are provided under specific network architectures and new service scenarios, such as 3GPP® 5G and 3GPP Long Term Evolution (LTE) Release 8. Those skilled in the art will know very well that, with the development of network architectures and new service scenarios, the embodiments in the present application are also applicable to similar technical problems, and moreover, the terminology used in the present application may change, but this should not affect the principles of the present disclosure.

[0091] Figure 1 shows an exemplary IAB system 100 according to several embodiments of the present application.

[0092] Referring to Figure 1, the IAB system 100 may include an IAB donor node (e.g., donor node 110), several IAB nodes (e.g., IAB node 120A, IAB node 120B, IAB node 120C, and IAB node 120D), and several UEs (e.g., UE130A and UE130B). For simplicity only, one donor node is shown in Figure 1, but in some other embodiments of this application, the IAB system 100 may include more donor nodes. Similarly, for simplicity only, four IAB nodes are shown in Figure 1, but in some other embodiments of this application, the IAB system 100 may include more or fewer IAB nodes. For simplicity only, two UEs are shown in Figure 1, but in some other embodiments of this application, the IAB system 100 may include more or fewer UEs.

[0093] IAB node 120A is directly connected to donor node 110. IAB node 120D is directly connected to donor node 110. In this example, donor node 110 is the parent node of IAB node 120A and also the parent node of IAB node 120D. IAB nodes 120A and 120D are child nodes of donor node 110. Link 180A between donor node 110 and IAB node 120A is the parent link of IAB node 120A. Link 180B between IAB node 120A and UE 130A is a child link of IAB node 120A. Link 180C between donor node 110 and IAB node 120D is the parent link of IAB node 120D. IAB node 120A may be connected to a donor node other than donor node 110 according to some other embodiments of this application. IAB node 120D may be connected to a donor node other than donor node 110 according to some other embodiments of this application.

[0094] IAB node 120C can reach donor node 110 by hopping through IAB node 120D. IAB node 120D is the parent node of IAB node 120C, and IAB node 120C is the child node of IAB node 120D. Link 180D between IAB node 120D and IAB node 120C is a child link of IAB node 120D and is also the parent link of IAB node 120C.

[0095] IAB node 120B can reach donor node 110 by hopping through IAB nodes 120C and 120D. IAB nodes 120C and 120D are upstream nodes of IAB node 120B, and IAB node 120C is the parent node of IAB node 120B. In other words, IAB node 120B is a child node of IAB node 120C. IAB nodes 120B and 120C are downstream nodes of IAB node 120D. Link 180E between IAB node 120C and IAB node 120B is a child link of IAB node 120C and is also the parent link of IAB node 120B.

[0096] UE130A is directly connected to IAB node 120A via link 180B, and UE130B is directly connected to IAB node 120B via link 180F. In other words, UE130A and UE130B are serviced by IAB node 120A and IAB node 120B, respectively. In some other embodiments of this application, UE130A and UE130B may also be referred to as child nodes of IAB node 120A and IAB node 120B, respectively. Link 180B is a child link of IAB node 120A. Link 180F is a child link of IAB node 120B.

[0097] Each of the IAB nodes 120A, 120B, 120C, and 120D may be directly connected to one or more UEs according to some other embodiments of this application.

[0098] Each of IAB node 120A, IAB node 120B, IAB node 120C, and IAB node 120D may be directly connected to one or more IAB nodes according to some other embodiments of this application.

[0099] Figure 2 illustrates an exemplary description of links between IAB nodes in some embodiments of the present disclosure.

[0100] Figure 2 shows three IAB nodes, namely IAB#1, IAB#2, and IAB#3, as well as a UE, namely UE#1. IAB#1 is considered the parent node to IAB#2, and IAB#3 is considered the child node to IAB#2. UE#1 is the serviced UE served by IAB#2. From IAB#2's perspective, link #1 is the parent link to IAB#2, link #2 is the child link of IAB#2, and link #3 is the access link to IAB#2.

[0101] The IAB node #2 shown in Figure 2 may include a mobile terminal (MT) and a distributed unit (DU). FDM is supported at IAB node #2. There may be multiple BWPs in the IAB MT of the IAB node. The multiple BWPs may have different BWP configurations, including different starting positions, different RBG sizes, different subcarrier spacings, etc. When FDM is employed between the parent link, i.e., link #1, and the child link, i.e., link #2, frequency domain matching between the IAB MT RBG configuration and the DU RB set configuration should be taken into consideration to improve spectral efficiency.

[0102] This disclosure focuses on determining the DU RB set configuration based on one or more BWPs of IAB MT.

[0103] Figure 3 illustrates an exemplary description of determining the DU RB set configuration according to several embodiments of the present disclosure.

[0104] Figure 3 shows two BWPs in the IAB MT, namely BWP#0 and BWP#1. Figure 3 also shows a DU RB set configuration, referred to as the "DU RB set configuration." The DU RB set is determined based on the two BWPs in the IAB MT. More specifically, the size of the DU RB set is determined using the following steps. - Step 1: Determine the PRB size for each BWP in the IAB MT based on the subcarrier spacing (SCS) of each BWP. Referring to Figure 3, the PRB size of BWP#0 is determined based on the SCS of BWP#0, and the PRB size of BWP#1 is determined based on the SCS of BWP#1. In the case of BWP#0, the smallest block in BWP#0 is the PRB, and the size of the PRB may be 15 × 12 = 180 kHz in the frequency domain and 1 ms in the time domain. In the case of BWP#1, the size of the PRB in BWP#1 may be 30 × 12 = 360 kHz in the frequency domain and 0.5 ms in the time domain. - Step 2: Determine the resource block group (RBG) size for each BWP in the IAB MT based on the BWP size and RBG configuration. RBG is a set of contiguous virtual resource blocks defined by the upper-layer parameter rbg-Size, which is configured by the PDSCH configuration (which may be expressed using the parameter PDSCH-Config), and the size of the bandwidth portion as shown in Table 1 below.

[0105] [Table 1]

[0106] As can be seen from the table, when the BWP size is 1 to 36, the RBG size is 2 according to configuration 1 and 4 according to configuration 2. When the BWP size is 37 to 72, the RBG size is 4 according to configuration 1 and 8 according to configuration 2. When the BWP size is 73 to 144, the RBG size is 8 according to configuration 1 and 8 according to configuration 16. When the BWP size is 145 to 275, the RBG size is 16 according to configuration 1 and 8 according to configuration 16. In Figure 3, the RBG size for both BWPs is 2PRB. - Step 3: Determine the DU frequency domain granularity that should result in the largest RBG size among the multiple BWPs of the IAB MT. In Figure 3, the RGB size for BWP#0 is 2PRB, and the size of 2PRB for BWP#1 is 2 × 180KHz, or 360KHz. The RGB size for BWP#1 is 2PRB, and the size of 2PRB for BWP#1 is 2 × 360KHz, or 720KHz. Therefore, the granularity of the DU frequency domain is 720 kHz. - Step 4: Determine the DU time domain granularity by the maximum symbol / slot length among the multiple BWPs of the IAB MT. In Figure 3, the slot length for BWP#1 is 1 ms, and the slot length for BWP#2 is 0.5 ms; therefore, the DU time-domain granularity is 1 ms. Based on the four steps described above, a DU RB set size of 720 kHz in the frequency domain and 1 ms in the time domain is determined.

[0107] As can be seen from the diagram, BWP-related configurations are necessary to determine the DU RB set configuration.

[0108] In some embodiments, an IAB node, for example IAB node #2 in Figure 2, will transmit BWP-related configuration information to the parent node. The BWP-related configuration information may include at least the following parameters: the BWP size for the BWP, the SCS associated with the BWP, and the RBG configuration for the BWP. For example, in Figure 3, the IAB node may transmit the bandwidth, the SCS for BWP#0 and BWP#1, and the RBG configuration to the parent node.

[0109] In some other embodiments, the IAB node may transmit the following parameters, namely the PRB number for the SCS, to the parent node. In some other scenarios, the SCS may be explicitly configured. In several other scenarios, the SCS is implicitly determined based on the IAB MT BWP SCS, the lowest IAB MT BWP SCS, the DU SCS, or the frequency band.

[0110] Please note that transmission may also apply to DUs and CUs. That is, a DU may send the above parameters to a CU.

[0111] Based on the bandwidth, the SCS of each BWP in the IAB MT, and the RBG configuration of the IAB MT, the RBG size of each BWP can be determined, and then the maximum time / frequency granularity can be determined. In other words, the parent node determines the maximum time / frequency granularity based on the BWP-related configuration information received from the IAB node. Similarly, the CU determines the maximum time / frequency granularity based on the BWP-related configuration information received from the DU.

[0112] Figure 4 shows an exemplary example of determining the DU RB set configuration according to some embodiments of the present disclosure.

[0113] Figure 4 shows two BWPs for the IAB MT, namely BWP#0 and BWP#1. As can be seen from the figure, BWP#0 has a lower starting position in the frequency domain compared to BWP#1. A reference boundary is determined, marked with "f_0". The reference starting boundary may be determined to be the same as the lowest frequency domain position among all IAB MT BWPs. In some other scenarios, the reference starting boundary may also be determined to be the same as the lowest carrier boundary, or the starting position of the SSB, or the starting position of coreset #0, or it may be explicitly configured to be the same.

[0114] The granularity f_g is determined based on the maximum RBG size in the frequency domain among all BWPs in the IAB MT. In Figure 4, the RBG size in the frequency domain in BWP#0 is 360 kHz, the RBG size in the frequency domain in BWP#1 is 720 kHz, the maximum RBG size is 720 kHz, and 720 kHz is determined as the frequency domain granularity f_g.

[0115] The possible termination boundary for the first RBG of each BWP in IAB MT is: f_1 = f_0 + n × f_g, where n = 0, 1, 2, ... That is the case.

[0116] For BWP#1, the end boundary of the first RBG is the nearest f_1 that is not smaller than the start frequency domain position of BWP#1.

[0117] If the size of RBG#1 is not equal to the frequency domain granularity f_g, RBG#1 is sometimes referred to as shift#1, as shown in Figure 4.

[0118] On the parent node side, the parent node determines the DU RB set configuration based on the BWP-related information of the IAB MT. Specifically, the DU RB set configuration should be matched with the BWP configuration in the frequency domain for the FDM multiplexing mode between the parent and child links of the IAB node.

[0119] This disclosure proposes configuring the DU RB set as follows:

[0120] The possible end and start positions in the frequency domain of the first RB set (marked as f_2 in Figure 4) are calculated as follows: f_2 = f_0 + n × f_g, where n = 0, 1, 2, ... Here, f_2 is greater than or equal to the DU carrier start boundary.

[0121] For example, in DU RB set configuration #0, f_2 = f_0 + f_g; in DU RB set configuration #1, f_2 = f_0; in DU RB set configuration #2, f_2 = f_0; and in DU RB set configuration #3, f_2 = f_0.

[0122] Resource shift #2 is determined by the DU carrier's start frequency (i.e., the start boundary of the DU RB set) and f_2. In detail, the size of shift #2 is from the DU carrier's start frequency to f_2, or from f_2 to the DU carrier's start frequency, depending on the values ​​of these two parameters. For example, shifts #2 for DU RB set configuration #0 and DU RB set configuration #3 are marked in Figure 4. The size of shift #2 may differ from the granularity f_g.

[0123] According to various scenarios, when the end boundary of the IAB DU carrier is larger than the end boundaries of all BWPs, the final RB set is determined differently. The final RB set may be determined by the difference between the end boundary of the IAB DU carrier and the largest end boundary of all BWPs, for example, RB set #7 in DU RB set configuration #2 is determined by that difference. RB set #7 is considered a shift and is referred to as "shift #3" in Figure 4. The size of shift #3 may be different from the granularity f_g.

[0124] When the end boundary of an IAB DU carrier is not greater than the end boundaries of all BWPs, for example, when the end boundary of an IAB DU carrier for DU RB set configuration #2 is not greater than the end boundary of BWP #0 or BWP #1, the last RB set #4 is determined based on the end boundary of the IAB DU carrier, the reference start boundary, and the largest RBG size among all BWPs of the IAB MT. More specifically, the size of the last RB set is equal to the remainder obtained by dividing (end boundary of IAB DU carrier - reference start boundary) by the largest RBG size. The size of the last RB set may be different from the granularity f_g.

[0125] Note that a DU RB set configuration may contain none, one, or both of the shifts, i.e., shift #2 and shift #3. For example, DU RB set configuration #1 contains no shifts, DU RB set configuration #3 contains shift #2, and DU RB set configuration #2 contains both shifts.

[0126] Based on the above calculations, all RB sets with shift #2 (if any), shift #3 (if any), and the maximum RBG size are determined, and therefore the DU RB set configuration is determined.

[0127] For an MT frequency shift, for example, in the case of shift #1, the only BWP start position configuration performed based on the start position may be f_1.

[0128] In some embodiments, when time-domain resources are used for FDM multiplexing mode between parent and child links of an IAB node, RB grouping is updated. This update means that the starting boundary of the first RB group with size f_g should be f_1. The determination of time-domain resources for FDM mode can be explicit or implicit.

[0129] Regarding DU frequency shift #2, which is also marked as RB set #0 in Figure 4, it is indicated from CU to IAB DU, or from the parent node of the IAB node. RB set #0 may be configured as a hard resource when it does not overlap with any resources of the IAB MT's BWP, i.e., when RB set #0 is not used for FDM. For example, RB set #0 in DU RB set configuration #2 may be configured as hard. RB set #0 in DU RB set configuration #0, which overlaps with the IAB MT's BWP, therefore cannot be configured as hard.

[0130] With respect to DU frequency shift #3, which is marked as the last RB set in Figure 4, for example, RB set #7 in DU RB set configuration #2 is indicated from CU to IAB DU, or from the parent node of the IAB node. When the last RB set does not overlap with any resources of the IAB MT's BWP, i.e., when the last RB set is not used for FDM, the last RB set may be configured as a hard resource. For example, RB set #7 in DU RB set configuration #2 may be configured as hard.

[0131] The reference SCS for frequency domain shifts can be explicitly configured or it can be the same as the SCS associated with the FDM multiplexing mode.

[0132] The above solution for determining the DU RB set configuration is static. In some other scenarios, the determination of the DU RB set configuration can be dynamic.

[0133] Active BWPs include downlink (DL) active BWPs and uplink (UL) active BWPs. This disclosure proposes that the transmission direction on the parent link of the IAB node for FDM multiplexing mode determines whether the active BWP is a DL active BWP or an UL active BWP.

[0134] In other words, when an IAB node performs simultaneous reception, the transmission direction on the IAB node's parent link is DL, and in this case, the active BWP is DL active BWP. When an IAB node performs simultaneous transmission, the transmission direction on the IAB node's parent link is UL, and in this case, the active BWP is UL active BWP.

[0135] In this scenario, the DU RB set configuration may also include DU frequency domain shifts, i.e., shifts #2 and #3 as shown in Figure 4, which are calculated in a similar manner.

[0136] Figure 5 shows another exemplary description of determining the DU RB set configuration according to some embodiments of the present disclosure.

[0137] In Figure 5, the DU RB set configuration is determined based on the active BWP#1 in the IAB MT.

[0138] In Figure 5, there is one active BWP, i.e., active BWP#1, and therefore the size of the DU RB set is determined according to active BWP#1. For example, the PRB size of BWP#1 is 180 kHz in the frequency domain and 1 ms in the time domain, and the RB size is 2. In this case, the size of the DU RB set is 360 kHz in the frequency domain and 1 ms in the time domain.

[0139] Shift #2 (i.e., RB set #0) is determined based on the start position of the active BWP #1 in the frequency domain and the start boundary of the DU carrier, and shift #3 (i.e., RB set #11) is determined based on the end position of the active BWP #1 in the frequency domain and the end boundary of the DU carrier. In the case of shift #3, it can be expressed in units of the number of RBs relative to the reference SCS.

[0140] Figure 6 illustrates another exemplary description of determining the DU RB set configuration according to some embodiments of the present disclosure.

[0141] In Figure 6, the DU RB set configuration is determined based on the active BWP#2 in the IAB MT.

[0142] In Figure 6, there is one active BWP, i.e., active BWP#2, and therefore the size of the DU RB set is determined according to active BWP#2. For example, the PRB size of BWP#1 is 360 kHz in the frequency domain and 0.5 ms in the time domain, and the RB size is 2. In this case, the size of the DU RB set is 720 kHz in the frequency domain and 0.5 ms in the time domain.

[0143] Shift #2 (i.e., RB set #0) is determined based on the start position in the frequency domain of the active BWP #2 and the start boundary of the DU carrier, and the final RB set #5 is determined based on the end boundary of the IAB DU carrier, the reference start boundary, and the RBG size of the active BWP of the IAB MT. In detail, the size of the final RB set is equal to the remainder obtained by dividing (end boundary of IAB DU carrier - reference start boundary) by the RBG size.

[0144] In the case of the last RB set in Figure 6, it can be expressed in units of the number of RBs relative to the reference SCS.

[0145] In both Figures 5 and 6, there is a one-to-one mapping relationship between the IAB MT BWP index and the DU frequency domain RB set configuration (shift #2 and shift #3). The BWP index may be the DL BWP index, the UL BWP index, or a combined index based on the DL BWP index and the UL BWP index.

[0146] Figure 7 shows a method for wireless communication according to a preferred embodiment of the present disclosure, which may be implemented on an IAB node, for example, IAB#2 in Figure 2.

[0147] In step 701, the IAB node receives information from the parent node or CU, which indicates at least one of the following: a first frequency-domain resource configuration associated with at least one BWP of the IAB MT, a second frequency-domain resource configuration associated with the RB set configuration of the IAB DU, and a third frequency-domain resource configuration associated with the RB set configuration of the IAB DU. For example, the first frequency-domain resource may be shift #1 in Figure 4, the second frequency-domain resource may be shift #2, and the third frequency-domain resource may be shift #3. In response, the parent node or CU sends information to the IAB node.

[0148] In step 702, the IAB node determines one or more frequency domain resources for downlink or uplink communication in the IAB MT based on the first frequency domain resource configuration, and / or frequency domain resource units for resource allocation in the parent and child links of the IAB node based on at least one of the second and third frequency domain resource configurations. That is, the IAB node determines the frequency domain resources in the IAB MT based on shift #1, and determines the RB sets in the parent and child links of the IAB node based on shift #2 and / or shift #3.

[0149] In some embodiments, the first frequency-domain resource configuration is based on the size of the first RBG of at least one BWP of the IAB MT. For example, in Figure 4, the size of shift #1 is identical to the size of RBG #1.

[0150] In some embodiments, the second frequency domain resource configuration is based on the size of the first RB set in the IAB DU, and its size differs from the sizes of other RB sets in the IAB DU. For example, in Figure 4, the size of shift #2 is the same as the size of RB set #0. The size of shift #2 differs from the sizes of other RB sets, such as RB set #1.

[0151] In some embodiments, the third frequency domain resource configuration is based on the size of the last RB set in the IAB DU, and its size differs from the sizes of other RB sets in the IAB DU. For example, in Figure 4, the size of the last RB set #4 in DU RB set configuration #0 is different from the sizes of other RB sets such as RB set #1.

[0152] In some embodiments, the first frequency domain resource is determined based on at least one start boundary and reference start boundary of at least one BWP configuration, as well as at least one of the maximum RBG sizes among all BWPs in the IAB MT. For example, in Figure 4, the size of RBG#1 in BWP#1 is determined based on the start boundary, reference start boundary, and maximum RBG size of BWP#1.

[0153] In some embodiments, the second frequency domain resource is determined based on at least one of the IAB DU carrier start boundary, reference start boundary, and the maximum RBG size among all BWPs of the IAB MT. For example, in Figure 4, the size of RB set #0 is determined based on the DU carrier start frequency, reference start boundary f_0, and maximum RBG size.

[0154] In some embodiments, the third frequency-domain resource is determined based on the termination boundary of the IAB DU carrier, the reference start boundary, the largest RBG size among all BWPs of the IAB MT, and at least one of the termination boundaries of at least one BWP of the IAB MT. For example, in Figure 4, the size of RB set #7 is determined by the difference between the termination boundary of the IAB DU carrier and the largest termination boundary of all BWPs.

[0155] In some embodiments, the reference start boundary is either explicitly configured, implicitly determined based on the start frequency domain position of the carrier, implicitly determined based on the start frequency domain position of the synchronization signal / physical broadcast channel (SSB), or implicitly determined based on the start frequency domain position of the minimum indexed BWP of the IAB MT.

[0156] In some embodiments, if the second frequency domain resource does not overlap with any PRB or any active BWP of the IAB MT, the second frequency domain resource is determined to be a hard resource. For example, in Figure 4, RB set #0 in DU RB set configuration #2 may be configured as hard.

[0157] In some embodiments, if the third frequency domain resource does not overlap with any PRB or any active BWP of the IAB MT, the third frequency domain resource is determined to be a hard resource. For example, in Figure 4, RB set #7 in DU RB set configuration #2 may be configured as hard.

[0158] In some embodiments, when a time-domain resource is associated with frequency-domain multiplexing between parent and child links of an IAB node, at least one of a first frequency-domain resource, a second frequency-domain resource, and a third frequency-domain resource is applied to the time-domain resource.

[0159] In some embodiments, at least one of a second frequency domain resource and a third frequency domain resource is associated with a BWP index in the IAB MT. The BWP index includes a DL BWP index, an UL BWP index, or a combined index based on the DL BWP index and the UL BWP index.

[0160] In some embodiments, the IAB node further receives a mapping relationship between the BWP index and at least one of the second and third frequency domain resources from the CU or parent node.

[0161] In some embodiments, the IAB node further determines that the BWP index, which should be a DL-active BWP index or a UL-active BWP index, is based on the transmission direction on the parent link of the network node.

[0162] In some embodiments, the first, second, and third frequency-domain resources are indicated by several PRBs associated with a reference SCS. In some embodiments, the SCS is either explicitly configured, implicitly determined based on the SCS of the IAB MT BWP, or is the SCS of the IAB MT BWP having the lowest frequency bandwidth.

[0163] An IAB node may transmit information to a parent node or CU, which includes at least one of the following: one or more BWP configurations and a PRB number associated with a reference SCS. In some embodiments, one or more BWP configurations include at least one of the following: a BWP size for a BWP, an SCS associated with a BWP, and a resource block group (RBG) configuration for a BWP.

[0164] In some embodiments, the information is used to determine the size of the RB set for the IAB DU. In some embodiments, the IAB node transmits a reference SCS having a PRB number.

[0165] Figure 8 shows an exemplary block diagram of apparatus 800 according to some embodiments of the present application. In some embodiments of the present application, apparatus 800 may be an IAB node or other device having similar functionality that can perform at least the method shown in Figure 7.

[0166] As shown in Figure 8, the device 800 may include at least one receiving circuit 801, at least one non-temporary computer-readable medium, and at least one transmitting circuit 802, as well as at least one processor 803 coupled to the at least one receiving circuit 801, the at least one transmitting circuit 802, and the at least one non-temporary computer-readable medium. Figure 8 shows that the at least one receiving circuit 801, the at least one transmitting circuit 802, and the at least one non-temporary computer-readable medium are directly coupled to the at least one processor 803, but it should be understood that all components in the device 800 may be coupled to a data bus to connect to and communicate with each other.

[0167] In Figure 8, elements such as the receiving circuit 801, the transmitting circuit 802, and the processor 803 are described in the singular, but unless explicitly stated otherwise, the plural is intended. In some embodiments of this application, at least one receiving circuit 801 and at least one transmitting circuit 802 may be combined in a single device such as a transceiver. In some embodiments of this application, the device 800 may further include an input device, memory, and / or other components.

[0168] In some embodiments of the present application, at least one non-temporary computer-readable medium may have computer-executable instructions stored thereon, such computer-executable instructions, programmed to cause at least one processor 803 to perform an operation of a method, such as as described in view of Figure 7, with at least one receiving circuit 801 and at least one transmitting circuit 802. For example, when executed, the instructions may cause at least one processor 803 to receive a first signaling via a first link using at least one receiving circuit 801, the first signaling indicating a first time-domain resource configuration for at least one multiplexing mode for the first and second links. The instructions may further cause at least one processor 803 to determine the time-domain resources associated with each of the at least one multiplexing mode based on the first time-domain resource configuration.

[0169] The method of this application may be implemented on a programmed processor. However, the controller, flowchart, and module may also be implemented in a general-purpose or dedicated computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, integrated circuits, discrete element circuits, or other hardware electronic or logic circuits, or programmable logic devices. In general, any device having a finite state machine capable of implementing the flowchart shown in the figure may be used to implement the processing functions of this disclosure.

[0170] While this application is described with respect to specific embodiments, it is evident that many alternative, modified, and variant forms will be apparent to those skilled in the art. For example, various components of these embodiments may be replaced, added, or substituted in other embodiments. Furthermore, not all elements shown in each figure are necessarily required for the operation of the disclosed embodiments. For example, a person skilled in the art of the disclosed embodiments may create and use the teachings of this application by simply employing the elements of the independent claims. Accordingly, the embodiments of this application as described herein are intended to be illustrative, not restrictive. Various modifications may be made without departing from the spirit and scope of this disclosure.

[0171] In this disclosure, relational terms such as “first,” “second,” etc., may be used simply to distinguish one entity or action from another entity or action, without necessarily requiring or implying an actual relationship or order between multiple entities or actions. The terms “to include,” “to have,” etc., or other variations thereof, apply to non-exclusive inclusions such that a process, method, article, or apparatus comprising an enumeration of elements may include other elements that are not explicitly enumerated or are specific to such process, method, article, or apparatus, rather than including only those elements. Elements progressing by “a,” “an,” etc., do not, without further constraint, exclude the existence of additional identical elements in a process, method, article, or apparatus comprising that element. The term “another” is defined as at least second or more. As used herein, terms such as “to include,” “to have,” etc., are defined as “to have.” [Explanation of symbols]

[0172] 100 IAB Systems 110 donor nodes 120A, 120B, 120C, 120D IAB nodes 130A, 130B UE 180A, 180B, 180C, 180D, 180E, 180F Links 800 equipment 801 Receiving Circuit 802 Transmitter Circuit 803 Processor

Claims

1. An Integrated Access Backhaul (IAB) node, A receiver configured to receive information from a parent node or central unit (CU), wherein the information is A second resource configuration for a second frequency domain resource associated with a resource block (RB) set configuration of an IAB distributed unit (DU), or A receiver showing at least one of a third resource configuration for a third frequency domain resource associated with the RB set configuration of the IAB DU, A processor configured to determine frequency domain resource units for resource allocation in the parent and child links of the IAB node based on at least one of the second and third resource configurations, Equipped with, The second frequency domain resource is different from the third frequency domain resource. Integrated Access Backhaul (IAB) node.

2. If the information further indicates a first resource configuration for a first frequency domain resource associated with at least one bandwidth portion (BWP) of an IAB mobile terminal (MT), The IAB node according to claim 1, wherein the first resource configuration is based on the size of the first RBG of the at least one BWP of the IAB MT.

3. If the information further indicates a first resource configuration for a first frequency domain resource associated with at least one bandwidth portion (BWP) of an IAB mobile terminal (MT), Based on the first resource configuration, the processor determines one or more frequency domain resources for downlink or uplink communication in the IAB MT. The IAB node according to claim 1.

4. The IAB node according to claim 1, wherein the second resource configuration is based on the size of the first set of RBs of the IAB DU, and the size is different from the sizes of other sets of RBs of the IAB DU.

5. The IAB node according to claim 1, wherein the third resource configuration is based on the size of the last set of RBs in the IAB DU, and the size is different from the sizes of other sets of RBs in the IAB DU.

6. The first frequency domain resource is a resource associated with at least one bandwidth portion (BWP) of an IAB mobile terminal (MT), and is determined based on the starting boundary and reference starting boundary of the configuration of at least one BWP of the IAB MT, and at least one of the maximum RBG size among all BWPs of the IAB MT. The IAB node according to claim 1.

7. The IAB node according to claim 1, wherein the second frequency domain resource is determined based on at least one of the IAB DU carrier start boundary, the reference start boundary, and the maximum RBG size among all BWPs of the IAB mobile terminal (MT).

8. The IAB node according to claim 1, wherein the third frequency domain resource is determined based on at least one of the following: the termination boundary of an IAB DU carrier, the reference start boundary, the maximum RBG size among all BWPs of an IAB mobile terminal (MT), and the termination boundary of at least one BWP of the IAB MT.

9. The IAB node according to any one of claims 6 to 8, wherein the reference start boundary is explicitly configured, implicitly determined based on the start frequency domain position of the carrier, implicitly determined based on the start frequency domain position of the synchronization signal / physical broadcast channel (SSB), or implicitly determined based on the start frequency domain position of the minimum indexed BWP of the IAB mobile terminal (MT).

10. The IAB node according to claim 1, wherein the second frequency domain resource is determined to be a hard resource if the second frequency domain resource does not overlap with any PRB or any active BWP of the IAB mobile terminal (MT).

11. When a time-domain resource is associated with frequency-domain multiplexing between the parent and child links of the IAB node, at least one of the first frequency-domain resource, the second frequency-domain resource, and the third frequency-domain resource is applied to the time-domain resource. The first frequency domain resource is a resource associated with at least one bandwidth portion (BWP) of an IAB mobile terminal (MT). The IAB node according to claim 1.

12. The IAB node according to claim 1, wherein at least one of the second frequency domain resource and the third frequency domain resource is associated with the BWP index of an IAB mobile terminal (MT).

13. The IAB node according to claim 12, wherein the BWP index includes a downlink (DL) BWP index, an uplink (UL) BWP index, or a combined index based on the DL BWP index and the UL BWP index.

14. The aforementioned receiver The CU or parent node is further configured to receive a mapping relationship between the BWP index and at least one of the second frequency domain resource and the third frequency domain resource from the CU or the parent node. The IAB node according to claim 12.

15. The IAB node according to claim 1, wherein at least the second frequency domain resource is indicated by several PRBs associated with a reference SCS.

Images