Frequency domain resource allocation enhancement for sbfd

Abstract

According to some embodiments, a method is performed by a wireless device. The method comprises obtaining a subband full duplex (SBFD) configuration indicating one or more subbands of a frequency band for transmission / reception in a first direction and subbands of the frequency band for transmission / reception in a second direction. The method further comprises receiving a frequency domain resource allocation from a network node comprising a resource allocation for transmission / reception in the first direction for the frequency band. The resource allocation indicates a continuous range of virtual resource blocks (VRBs) available for transmission / reception. The method further comprises determining a mapping of VRBs to physical resource blocks (PRBs) based on the frequency domain resource allocation and the SBFD configuration. The mapped PRBs are within the subbands for transmission / reception in the first direction. The method further comprises performing transmission / reception in the first direction using the mapped PRBs.

Description

FREQUENCY DOMAIN RESOURCE ALLOCATION ENHANCEMENT FOR SBFD TECHNICAL FIELD

[0001] Embodiments of the present disclosure are directed to wireless communications and, more particularly, to frequency domain resource allocation enhancement for subband frequency division (SBFD). BACKGROUND

[0002] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

[0003] Third Generation Partnership Project (3GPP) New Radio (NR) standard (e.g., 38300- h50) is being designed to provide service for multiple use cases, such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC), and machine type communication (MTC). Each of these services has different technical requirements. For example, the general requirement for eMBB is high data rate with moderate latency and moderate coverage, while URLLC service requires a low latency and high reliability transmission but perhaps for moderate data rates.

[0004] An NR slot consists of several orthogonal frequency division multiplexing (OFDM) symbols, according to current agreements either 7 or 14 symbols (OFDM subcarrier spacing ≤ 60 kHz) and 14 symbols (OFDM subcarrier spacing > 60 kHz). FIGURE 1 illustrates a slot with 14 OFDM symbols. In FIGURE 1, ^^^^^^^^and ^^^^^^^^^^^^^^^^^^^^denote the slot and OFDM symbol duration, respectively.P110624WO01 PCT APPLICATION 2 of 49

[0005] NR supports different types of duplex communication modes. To support the many types of targeted use cases with varying requirements, different duplex communication modes are discussed in 3GPP standardization. Moreover, the same device may be capable of operating using different duplex modes, e.g., to achieve different overall communication performance based on its needs.

[0006] Transmission and reception from a wireless communication device, e.g., a base station (BS) or a user equipment (UE) in a cellular system, can be multiplexed in the frequency domain or in the time domain (or combinations thereof). The most relevant duplex modes are discussed below.

[0007] Duplex communication modes include frequency division duplex (FDD) and time division duplex (TDD).

[0008] FDD, as illustrated in the top left in FIGURE 2 (a), implies that transmission (TX) and reception (RX) take place in different, sufficiently separated carriers. Thus, FDD requires paired spectrum. For FDD operation, there are two carrier frequencies, one for uplink (UL) transmission and one for downlink (DL) transmission. At least with respect to the UE in a cellular communication system, FDD can be either full duplex (FD-FDD) or half duplex (HD- FDD).

[0009] In the FD-FDD case, a UE can transmit and receive simultaneously, while in HD-FDD operation, the UE cannot transmit and receive simultaneously (the BS is still capable of simultaneous RX / TX though, e.g., receiving from one UE while simultaneously transmitting to another UE). In Long Term Evolution (LTE), a HD-FDD terminal is monitoring / receiving in the DL except when explicitly being instructed to transmit in a certain subframe.

[0010] FIGURE 2 illustrates different types of duplex communication modes. (a) FDD, (b) TDD, (c) subband frequency division (SBFD), and (d) inband frequency division (IBFD).

[0011] FIGURE 3 illustrates a comparison of TDD operations, (a) static TDD in channel 1 and 2, and (b) static TDD in channel 2 and dynamic TDD in channel 1.

[0012] FIGURE 4 illustrates TDD operation options and interference cases.

[0013] For TDD, as illustrated to the top right in FIGURE 2 (b), TX and RX take place within the same carrier in different, non-overlapping time slots. Thus, TDD can operate in unpaired spectrum. For TDD operation, there is only a single carrier frequency and UL and DL transmissions are always separated in time also on a cell basis. Because the same carrierP110624WO01 PCT APPLICATION 3 of 49 frequency is used for UL and DL transmission, both the BS and the UEs need to switch from TX to RX and vice versa.

[0014] An essential aspect of any TDD system is to provide the possibility for a sufficiently large guard time where neither DL nor UL transmissions occur. This is required to avoid interference between UL and DL transmissions. For NR, this guard time is provided by special sots, which are split into three parts: symbols for DL, a guard period (GP), and symbols for UL. The remaining slots are either allocated to UL or DL transmission.

[0015] The only interference existing in this configuration is among transmissions happening on the same link, inside their own channel, and from an adjacent channel, if synchronization is also assumed among different operators. This is shown in FIGURE 3 (a), where the two networks deployed in channels 1 and 2 are synchronized and will suffer only from in-channel and adjacent channel interference from the same link.

[0016] Interference links are further described in FIGURE 4 (a). This option is, e.g., used by operators in Europe and recommended in regulations, and requires entire carrier bandwidth or all carriers in the same frequency band to use the same DL transmission or UL reception directions.

[0017] Dynamic TDD describes a mode of operation in which a network adapts the DL / UL subframe pattern according to traffic conditions. This causes interference between different links (uplink and downlink), and it is referred to as cross link interference (CLI), BS-to-BS and UE-to-UE, as it is shown in FIGURE 4 (b).

[0018] CLI interference happens inside the same operator and inter-operators. FIGURE 3 (b) provides an example. Specifically, the deployment on channel 1 requires additional UL slots to serve UL traffic, and to do that the TDD patterns of BS1 and BS2 are adjusted to increase UL ratio. Due to that, the deployment will suffer, inside the same network, from BS-to-BS and UE-to-UE interference in slots 2 and 3.

[0019] In addition, the patterns used in channel 1 are unsynchronized with respect to the static TDD pattern used in channel 2. Due to that, the deployment in channel 1 will suffer from BS- to-BS and UE-to-UE interference from the adjacent channel, in slots 2, 3 and 4. On channel 2 instead, the deployment will suffer from UE-to-UE interference from the adjacent channel in slots 2, 3 and 4, but only from same link interference inside channel 2.

[0020] Subband full duplex (SBFD), as illustrated to the bottom left in FIGURE 2 (c), is being studied in 3GPP Release 18 as a part of the 5G-Advanced standardization (e.g., 38211-i00).P110624WO01 PCT APPLICATION 4 of 49 For SBFD operation, a portion of a wide bandwidth carrier, termed subband, may be used for a different communication direction than that of the rest of the carrier. Correspondingly, different non-overlapping subbands are used for DL and UL. This is unlike the conventional TDD operation where the entire bandwidth of the carrier is always used either for DL or UL. SBFD operation can also be performed across different carriers within the same frequency band, where one or more carriers within a frequency band may be used for a different communication direction than that of the other carriers, which is again unlike conventional TDD operation where all carriers within a frequency band are always used for the same communication direction.

[0021] In the 3GPP Release 18 study, the scope has been limited such that during SBFD communication, only BSs transmit DL and receive UL simultaneously using corresponding non-overlapping subbands. An individual UE is scheduled in only one direction (DL or UL) at a time, following conventional HD TDD operation. However, for future 3GPP releases, SBFD operation at UEs where a UE transmits UL and receives DL simultaneously using corresponding non-overlapping subbands is also being discussed as a potential study topic. Interference links affecting a SBFD Rel.18 deployments are shown in FIGURE 4 (c).

[0022] Single frequency full duplex (SFFD) or in-band full duplex (IBFD), as illustrated at the bottom right in FIGURE 2 (d), has also been proposed to be studied in 3GPP standardization. It was discussed but excluded from the scope of Release 18, and it is now again being discussed during scoping discussions for future releases. For SFFD operation, the entire bandwidth of the same carrier in a single carrier system or all carriers in a multi-carrier system can be simultaneously used for DL and UL operations. In other words, the same time and frequency resources can be used for both TX and RX at the same device. Similar to SBFD operation, SFFD operation is also being discussed for both base stations and UEs.

[0023] Physical downlink shared channel (PDSCH) is the DL physical channel that delivers user data from gNB to UE. The network informs the UE about the frequency resources to be used for the reception of PDSCH using downlink control information (DCI). Within the DCI formats, the field ‘Frequency domain resource assignment’ carries the required resource allocation information.

[0024] NR supports two types of DL resource allocation schemes, Type 0 and Type 1 (e.g., 38214-i00). The network informs the UE about which resource allocation scheme to be used via Radio Resource Control (RRC) signaling within PDSCH-Config IE.P110624WO01 PCT APPLICATION 5 of 49

[0025] For downlink resource allocation Type 0, the network asks the UE to use Type 0 resource allocation, either via RRC signaling (resourceAllocationType0) or via DCI. The DL resource allocation Type 0 is based on a bitmap indication where resource block (RB) assignment information includes a bitmap indicating the resource block group (RBG) that are allocated to a UE.

[0026] A RBG is a set of consecutive virtual resource blocks (VRB). With Type 0 resource allocation, only non-interleaved VRB-to-PRB mapping is possible, which means that ^^^^^^^^^^^^^^^^is mapped to ^^^^^^^^^^^^^^^^. The bitmap is of size ^^^^^^^^^^^^^^^^where each bit within the bitmap corresponds to a RBG, so that each RBG within the bandwidth part (BWP) is addressable. An RBG is allocated to the UE if the corresponding bit value in the bitmap is 1, and the RBG is not allocated to the UE if the bit value is 0.

[0027] The size of the bitmap varies depending on the size of the bandwidth part, the position of the bandwidth part inside the carrier resource block (CRB) grid and the RBG size (P).

[0028] The total number of RBGs within the DL BWP is ^^^^^^^^�, where the size of the first RBG is ^^^^^^^^^^^^^^^^^^^^^^^^^^^^0 = ^^^^^^^^^^^^^^^^ ^^^^, the size of the last RBGotherwise. The size of all other RBG is P. For more details, see TS 38.214, section 5.1.2.2.1.

[0029] In Type 1 resource allocation, the network provides the UE with an encoded value of starting RB number and the length of contiguously allocated interleaved or non-interleaved RBs. Type 1 resource allocation only supports contiguous allocation of VRBs.

[0030] The procedure to derive the allocated PRBs in this case involves two steps: • using the resource indication value (RIV) method to derive a set of contiguously allocated VRBs (start VRB and length of VRBs); and • performing VRB-to-PRB mapping: in this step, a set of VRBs (derived from step 1) are mapped onto a set of PRBs using interleaved or non-interleaved mapping procedure.

[0031] Regarding the RIV to derive contiguously allocated VRBs, DL Type 1 resource allocation is based on a RIV corresponding to a starting VRB number ^^^^^^^^^^^^^^^^^^^^^^^^^^^^and a length in terms of contiguously allocated VRB, ^^^^^^^^^^^^. The RIV value is defined as follows:P110624WO01 PCT APPLICATION 6 of 49where ^^^^ ≥ 1 shall not ex ^^^^^^^^^^^^^^^^^^^^^^^^ ceed ^^^^^^^^^^^^^^^^ − ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

[0032] When the scheduling grant is received with DCI format 1_2 or 1_3, a downlink Type 1 resource allocation field consists of a RIV corresponding to a starting resource block group RBGstart=0, 1, …, NRBG-1 and a length in terms of virtually contiguously allocated resource block groups LRBGs=1, …, NRBG, the expression is the same as above.

[0033] Regarding the VRB-to-PRB mapping, once the starting VRB number and the number of consecutive VRBs are known, there is need to derive the actual PRBs required for the reception of PDSCH. To do so, VRB-to-PRB mapping needs to be done (e.g., 38.211).

[0034] Two different types of VRB-to-PRB mapping are currently supported in the standard, non-interleaved mapping and interleaved mapping.

[0035] For non-interleaved VRB-to-PRB mapping, virtual resource block n is mapped to physical resource block n, and the modulated and precoded symbols are allocated to the PRB in a continuous and sequential manner. This strategy simplifies the mapping process, but results in reduced frequency diversity.

[0036] For interleaved VRB-to-PRB mapping, the mapping process is defined in terms of resource block bundles, based on a formulation defined in Rel. 15 in TS 38.211. The bundle size can be configured by the higher-layer parameter vrb-ToPRB-Interleaver, otherwise is assumed by the UE to be 2. The modulated and precoded symbols are allocated to PRB in a non-continuous non-sequential manner. This strategy increases frequency diversity by spreading the symbols across the available resources, improving resilience against frequency- selective fading and interference.

[0037] The DCI may or may not include a single bit field ‘VRB-to-PRB mapping’ (e.g., 38.212). When the bit is absent, non-interleaved mapping is assumed and Resource Allocation Type 0. When the bit is present, Type 1 Resource Allocation is considered, and if bit is 0 no interleaving is configured, if bit is 1, interleaving is configured.

[0038] When interleaved VRB-to-PRB mapping is indicated, the concept of resource block bundles (RBB), is defined where each RBB is a set of contiguous RBs. The size of the RBB is provided by PDSCH-Config via vrb-ToPRB-Interleaver. This field can configure the size of RBB as either 2 RBs or 4 RBs.

[0039] Depending upon the size of the BWP, and the RBB size (L), the RBB sizes of the first and last RBB could be different to that of RBB size configured by the RRC.P110624WO01 PCT APPLICATION 7 of 49 1- Let the total number of RBs within BWP (Bandwidth Part) I be ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^,^^^^a. Resource block bundle 0 size is= ^^^^^^^^ − ^^^^^^^^^^^^ resourceblocks. b. The size of the last Resource Block Bundle, ^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ − 1 ,is ^^^^^^^^^^^^^^^^^^^^^^^^^^^^,^^^^^^^^^^^^^^^^,^^^^ =�^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^,^^^^ + ^^^^^^^^^^^^^^^^,^^^^�^^^^^^^^^^^^ ^^^^^^^^ resource blocks if�^^^^^^^^^^^^^^^^,^^^^ + ^^^^ ^^^^^^^^^^^^^^^^^^^^,^^^^�^^^^^^^^^^^^ ^^^^^^^^ > 0, and^^^^^^^^resource blocks otherwise. c. All other resource block bundles consist of ^^^^^^^^resource blocks.5- VRBs in the interval ^^^^ ∈ {0,1, …^^^^^^^^^^^^^^^^^^^^^^^^^^^^ − 1} are mapped to PRBs according to:a. VRB ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ − 1 is mapped to PRB ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ − 1b. VRB bundle ^^^^ ∈ {0,1, …^^^^^^^^^^^^^^^^^^^^^^^^^^^^ − 2} is mapped to PRB bundle ^^^^(^^^^) where ^^^^(^^^^)is defined in TS38.211: i. ^^^^(^^^^) = ^^^^^^^^ + ^^^^ii. ^^^^ = ^^^^^^^^ + ^^^^iii. ^^^^ = 0,1, …^^^^ − 1iv. ^^^^ = 0,1, …^^^^ − 1v. ^^^^ = 2vi. ^^^^ =�^^^^^^^^^^^^^^^^^^^^^^^^^^^^� 2�

[0040] There currently exist certain challenges. For example, in SBFD operation, a carrier is partitioned into multiple subbands designated for DL or UL transmission. When there are more than one DL subbands in a SBFD carrier, the DL frequency resources (i.e., PRBs) are effectively segmented due to the presence of UL subbands and guard-bands between two adjacent DL subbands. To achieve efficient and flexible resource utilization in SBFD operation, it is beneficial that PDSCH can support frequency resource allocation across multiple DL subbands, so that a UE can be assigned with the most downlink resources in the carrier as possible, if needed.

[0041] Current NR specification supports two different DL resource allocation schemes in frequency domain, namely DL Resource Allocation Type 0 and Type 1, as described above. For DL Resource Allocation Type 0 the resource block assignment information includes a bitmap indicating the Resource Block Groups (RBGs) that are allocated to the scheduled UE where a RBG is a set of consecutive virtual resource blocks (VRBs). DL Resource Allocation Type 0 already supports non-contiguous resource allocation, therefore it can be directly usedP110624WO01 PCT APPLICATION 8 of 49 for PDSCH frequency resource allocation for UEs in SBFD operation where the allocated PRBs can potentially fall into multiple DL subbands. However, because the dimension of the DL subbands is reduced compared to that of the DL BWP, when SBFD is configured, the number of bits used in DCI to indicate the frequency domain resource assignment could be optimized for Release 19 and onwards UEs.

[0042] For DL Resource Allocation Type 1, the resource block assignment information indicates to a scheduled UE a set of contiguously allocated non-interleaved or interleaved virtual resource blocks (VRBs) within the active bandwidth part. For SBFD operation, DL Resource Allocation Type 1 with non-interleaved VRB-to-PRB mapping implies that a UE can only be assigned with contiguous resources confined within one DL subband. For DL Resource Allocation Type 1 with interleaved VRB-to-PRB mapping it is even not guaranteed that all the indicated VRBs, after interleaving, are mapped to the valid DL PRBs in the DL subbands. Therefore, to be able to allocate PDSCH resource across multiple DL subbands and to avoid indicated VRBs being mapped to PRBs outside the DL subbands after interleaving, DL Resource Allocation Type 1 needs to be enhanced. SUMMARY

[0043] As described above, certain challenges currently exist with frequency domain resource allocation for subband frequency division (SBFD). Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, the object of particular embodiments described herein is threefold: 1) to define options for enhancement of downlink (DL) Resource Allocation Type 0 and Type 1, so that the frequency domain resource assignment field in the scheduling DCI is optimized for Release 19 and onwards user equipment (UE); 2) to define options for enhancement of DL Resource Allocation Type 1 so that frequency domain resource (i.e., physical resource blocks (PRBs)) across multiple subbands may be allocated to Release 19 and onwards UEs in SBFD operation, for both interleaved and non-interleaved virtual resource block (VRB)-to-PRB mapping; 3) to define options for enhancement of interleaved VRB-to-PRB mapping for SBFD operation to ensure the indicated VRBs are mapped to PRBs in the DL subbands. The enhancements may be transparent to Release 18 and older UEs.

[0044] Particular embodiments enhance DL Resource Allocation Type 0 and 1 and the VRB- to-PRB mapping mechanism for physical downlink shared channel (PDSCH) for base stationsP110624WO01 PCT APPLICATION 9 of 49 deploying SBFD in such a way that Release 18 and older UEs can operate in transparent manner, and Release 19 and onwards UEs that support SBFD can operate in optimized manner and with full potentiality even when SBFD configuration with multiple discontinuous DL subbands (e.g., D-U-D) is considered.

[0045] More specifically, particular embodiments define 1) options for Resource Allocation Type 0 and Type 1, so that the number of bits for frequency domain resource assignment in the scheduling DCI is optimized; 2) options for Resource Allocation Type 1 to support allocation of DL resources across multiple DL subbands, for both cases when interleaved VRB-to-PRB mapping is enabled and when not, and 3) options for enhancement of interleaved VRB-to-PRB mapping for SBFD operation to ensure the indicated VRBs are mapped to PRBs in the DL subbands.

[0046] Particular embodiments include a method of enhancement of DL Resource Allocation Type 0 and 1 for SBFD operation so that the frequency domain resource assignment field in DCI is transparent to Release 18 and older UEs and can be optimized for Release 19 and onwards UEs.

[0047] Particular embodiments include a method of enhancement of DL Resource Allocation Type 1 for SBFD operation so that the inclusion of the UL subband and guard-bands in frequency resource allocation is transparent to Release 18 and older UEs and is allowed with full potentiality for Release 19 and onwards UEs by explicit configuration, e.g., a field in RRC signaling.

[0048] Methods similar to these may also be extended and apply to UL resource allocation in SBFD, e.g., SBFD configurations such as U-D-U.

[0049] Particular embodiments include a method of enhancement of PDSCH VRB-to-PRB mapping in SBFD operation so that the indicated VRBs are mapped to PRBs in the DL subbands. When interleaved VRB-to-PRB mapping is disabled, for Resource Allocation Type 1, for Release 18 and older UEs, resource allocation across multiple DL subbands is not supported if DL Resource Allocation Type 1 is configured. For Release 19 and onwards UEs, DL Resource Allocation Type 1 is improved so that resource allocation indicates through RIV a range of consecutive VRBs, which can span one or more DL subbands, and some of which may fall into UL subband or guard-bands. When receiving such allocation, such VRBs falling into the UL subband or guard-bands should be considered as invalid by the UE and not used for PDSCH data mapping. Some embodiments require that a Rel-19 or onwards UE has alreadyP110624WO01 PCT APPLICATION 10 of 49 been provided with SBFD subband configuration, so that it understands what VRBs in the resource allocation are invalid.

[0050] For Release 19 and onwards UEs, DL Resource Allocation Type 1 is improved so that resource allocation indicates through RIV a range of consecutive VRBs, which can span one or more DL subbands. When receiving this indication, the UE is able to map the VRBs to the PRBs, starting from the VRB indicated by RIV. If the consecutive VRBs are more than those that can be contained in the first DL subband, the UE understands that the remaining VRBs are mapped to the second subband and apply to the VRB numbers a block-shift equivalent to the size of the UL subband and the guard bands. Some embodiments require that a Rel-19 UE has already been provided with SBFD subband configuration, so that it understands what shift to apply and from which VRB.

[0051] In some embodiments, Release 19 and onwards UEs may support one or a combination of methods described above, in which case the gNB explicitly instructs the UE about the variant of the resource allocation Type 1 to be applied.

[0052] When interleaved VRB-to-PRB mapping is enabled, the following options are possible to apply interleaving to SBFD: Option 1: interleaved VRB-to-PRB mapping is not applied to SBFD. Only non- interleaved mapping can be considered. Option 2: the VRB-to-PRB interleaved mapping rule defined in Rel.15 in TS38.211 is applied separately to the VRBs belonging to each specific DL subband, each with a specific starting RB and size. Option 3: A two-step VRB-to-PRB mapping with interleaving is applied to the VRBs in the DL subband(s). The VRB-to-PRB mapping rule for interleaving, defined in Rel.15 in TS38.211, is applied to the DL resources in the DL subband(s). Successively, a block-wise shift is applied to match the configuration of the SBFD carrier in terms of DL and UL subband and guard band configuration. Option 4: A one-step VRB-to-PRB mapping with interleaving is applied to the entire DL BWP. The VRB-to-PRB mapping rule for interleaving defined in Rel. 15 in TS38.211 is applied to the whole band of the BWP. The VRBs that are mapped to the PRBs belonging to the UL subband or guard bands are masked out.

[0053] Particular embodiments may be described generally as follows.P110624WO01 PCT APPLICATION 11 of 49

[0054] According to some embodiments, a method is performed by a wireless device. The method comprises obtaining a SBFD configuration indicating one or more subbands of a frequency band for transmission / reception in a first direction and one or more subbands of the frequency band for transmission / reception in a second direction. The method further comprises receiving a frequency domain resource allocation from a network node comprising a resource allocation for transmission / reception in the first direction for the frequency band. The resource allocation indicates a continuous range of VRBs available for transmission / reception. The method further comprises determining a mapping of VRBs to PRBs based on the frequency domain resource allocation and the SBFD configuration. The mapped PRBs are within the subbands for transmission / reception in the first direction. The method further comprises performing transmission / reception in the first direction using the mapped PRBs.

[0055] In particular embodiments, determining the mapping of VRBs to PRBs comprises determining a mapping of the VRBs to PRBs where VRBs that do not map to the one or more subbands for transmission / reception in the first direction are considered to be invalid and are not used for resource mapping.

[0056] In particular embodiments, interleaving is performed when determining the mapping of the VRBs to PRBs where VRBs that do not map to the one or more subbands for transmission / reception in the first direction are considered to be invalid and are not used for resource mapping.

[0057] In particular embodiments, determining the mapping of VRBs to PRBs comprises determining a mapping of the VRBs to PRBs where VRBs that do not map to a first subband of the one or more subbands for transmission / reception in the first direction are shifted to map to a second subband of the one or more subbands for transmission / reception in the first direction.

[0058] In particular embodiments, interleaving is performed when determining the mapping of VRBs to PRBs and the interleaving is performed on a bandwidth comprising a sum of all the subbands for transmission / reception in the first direction.

[0059] In particular embodiments, interleaving is performed when determining the mapping of the VRBs to PRBs wherein the interleaving pattern ensures that the mapped PRBs are within the subbands for transmission / reception in the first direction.P110624WO01 PCT APPLICATION 12 of 49

[0060] In particular embodiments, the first direction comprises downlink, the second direction comprises uplink, and performing transmission / reception in the first direction using the mapped PRBs comprises performing downlink reception in a PDSCH using the mapped PRBs.

[0061] In particular embodiments, the frequency domain resource allocation comprises a downlink Type 1 resource allocation scheme or a downlink Type 0 resource allocation scheme.

[0062] In particular embodiments, the first direction comprises uplink, the second direction comprises downlink, and performing transmission / reception in the first direction using the mapped PRBs comprises performing uplink transmission in a PUSCH using the mapped PRBs.

[0063] According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the methods of the wireless device described above.

[0064] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless device described above.

[0065] According to some embodiments, a method is performed by a network node. The method comprises obtaining a SBFD configuration for a wireless device. The SBFD configuration indicates one or more subbands of a frequency band for transmission / reception in a first direction and one or more subbands of the frequency band for transmission / reception in a second direction. The method further comprises transmitting a frequency domain resource allocation to the wireless device. The frequency domain resource allocation comprises a resource allocation for transmission / reception in the first direction for the frequency band. The resource allocation indicates a continuous range of VRBs available for transmission / reception. The method further comprises determining a mapping of VRBs to PRBs based on the frequency domain resource allocation and the SBFD configuration. The mapped PRBs are within the subbands for transmission / reception in the first direction. The method further comprises performing transmission / reception in the first direction using the mapped PRBs.

[0066] In particular embodiments, determining the mapping of VRBs to PRBs comprises determining a mapping of the VRBs to PRBs where VRBs that do not map to the one or more subbands for transmission / reception in the first direction are considered to be invalid and are not used for resource mapping.

[0067] In particular embodiments, interleaving is performed when determining the mapping of the VRBs to PRBs where VRBs that do not map to the one or more subbands forP110624WO01 PCT APPLICATION 13 of 49 transmission / reception in the first direction are considered to be invalid and are not used for resource mapping.

[0068] In particular embodiments, determining the mapping of VRBs to PRBs comprises determining a mapping of the VRBs to PRBs where VRBs that do not map to a first subband of the one or more subbands for transmission / reception in the first direction are shifted to map to a second subband of the one or more subbands for transmission / reception in the first direction.

[0069] In particular embodiments, interleaving is performed when determining the mapping of VRBs to PRBs and the interleaving is performed on a bandwidth comprising a sum of all the subbands for transmission / reception in the first direction.

[0070] In particular embodiments, interleaving is performed when determining the mapping of the downlink VRBs to PRBs wherein the interleaving pattern ensures that the mapped PRBs are within the subbands for transmission / reception in the first direction.

[0071] In particular embodiments, the first direction comprises downlink, the second direction comprises uplink, and performing transmission / reception in the first direction using the mapped PRBs comprises performing downlink transmission in a PDSCH using the mapped PRBs. In particular embodiments, the frequency domain resource allocation scheme comprises a downlink Type 1 resource allocation scheme or a downlink Type 0 resource allocation scheme.

[0072] In particular embodiments, the first direction comprises uplink, the second direction comprises downlink, and performing transmission / reception in the first direction using the mapped PRBs comprises performing uplink reception in a PUSCH using the mapped PRBs.

[0073] In particular embodiments, the method further comprises transmitting to the wireless device an indication of which variant of the mapping of VRBs to PRBs to use when mapping VRBs to PRBs.

[0074] According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.

[0075] Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network node described above.P110624WO01 PCT APPLICATION 14 of 49

[0076] Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments include enhancements for the frequency domain resource allocation in SBFD. The frequency multiplex of an uplink (UL) subband in the DL BWP generates new needs at resource allocation level in terms of optimization of bits in the DCI, full flexibility in the resource allocation of UEs across multiple subbands and feasible interleaving. Specifically, particular embodiments facilitate 1) optimizations of Resource Allocation Type 0 and Type 1 to reduce the number of bits in DCI devoted to frequency domain resource assignment; 2) enhancements for Resource Allocation Type 1, so that a UE can be flexibly allocated across multiple subbands; and 3) enhancements for VRB-to-PRB mapping when interleaving is enabled, so that the SBFD configuration is respected and the mapping is realized inside the limits of the available DL resources.

[0077] The focus of particular embodiments is on DL frequency resource allocation, with special emphasis to SBFD carrier configuration D-U-D (even if other configurations are not precluded), but examples and embodiments related to points 1 and 2 may be extended to the UL case for carrier configuration like, e.g., U-D-U.

[0078] The proposed enhancements are transparent to Release 18 UEs, while for Release 19 and onwards UEs, particular embodiments require that the UE is provided with SBFD configuration in terms of DL subband(s), UL subband(s) and guard-band(s). BRIEF DESCRIPTION OF THE DRAWINGS

[0079] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which: FIGURE 1 illustrates a slot with 14 OFDM symbols; FIGURE 2 illustrates different types of duplex communication modes. (a) frequency division duplex (FDD), (b) time division duplex (TDD), (c) subband full duplex (SBFD), and (d) inband full duplex (IBFD)); FIGURE 3 illustrates a comparison of TDD operations, (a) static TDD in channel 1 and 2, and (b) static TDD in channel 2 and dynamic TDD in channel 1; FIGURE 4 illustrates TDD operation options and interference cases; FIGURE 5 illustrates an example of improvement for non-contiguous Type 1 Resource Allocation (option 2);P110624WO01 PCT APPLICATION 15 of 49 FIGURE 6 illustrates an example of improvement for non-contiguous Type 1 Resource Allocation (option 3); FIGURE 7 illustrates an example of virtual resource block (VRB)-to-physical resource block (PRB) mapping, independent per downlink subband (option 2); FIGURE 8 illustrates an example of VRB-to-PRB mapping, combined for the 2 downlink subbands (option 3); FIGURE 9 illustrates an example of VRB-to-PRB mapping, over the entire downlink bandwidth part (BWP) (option 4); FIGURE 10 illustrates an example communication system, according to certain embodiments; FIGURE 11 illustrates an example user equipment (UE), according to certain embodiments; FIGURE 12 illustrates an example network node, according to certain embodiments; FIGURE 13 illustrates a method performed by a wireless device, according to certain embodiments; and FIGURE 14 illustrates a method performed by a network node, according to certain embodiments. DETAILED DESCRIPTION

[0080] As described above, certain challenges currently exist with frequency domain resource allocation for subband frequency division (SBFD). Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, the object of particular embodiments described herein is threefold: 1) to define options for enhancement of downlink (DL) Resource Allocation Type 0 and Type 1, so that the frequency domain resource assignment field in the scheduling DCI is optimized for Release 19 and onwards user equipment (UE); 2) to define options for enhancement of DL Resource Allocation Type 1 so that frequency domain resource (i.e., physical resource blocks (PRBs)) across multiple subbands may be allocated to Release 19 and onwards UEs in SBFD operation, for both interleaved and non-interleaved virtual resource block (VRB)-to-PRB mapping; 3) to define options for enhancement of interleaved VRB-to-PRB mapping for SBFD operation to ensure the indicated VRBs are mapped to PRBs in the DL subbands. The enhancements may be transparent to Release 18 and older UEs.P110624WO01 PCT APPLICATION 16 of 49

[0081] Particular embodiments are described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0082] Throughout the description of the embodiments described herein, it is assumed a UE in SBFD operation has received SBFD configuration from dedicated or common signaling from its serving gNB, which indicates to the UE the carrier is configured with DL subband(s), UL subband(s) and guard-band(s) and the location and size of each subband in the carrier, typically in a D-U-D pattern but other SBFD patterns are not precluded.

[0083] Even though the embodiments proposed herein focus mainly on DL resource allocation for D-U-D SBFD pattern, for one of skill in the art it is straightforward to apply similar methodologies to those proposed herein to UL resource allocation for other SBFD patterns (such as U-D-U).

[0084] Particular embodiments include enhancements of resource block assignment for DL Resource Allocation Type 0. For DL Resource Allocation Type 0, the resource block assignment includes a bitmap indicating the Resource Block Groups (RBGs) that are allocated to the scheduled UE where a RBG is a set of consecutive virtual resource blocks (VRBs). In SBFD operation, not all VRBs defined in the downlink bandwidth part can be allocated for DL transmission, because some of the VRBs are associated with UL subband(s) and guard-bands. Therefore, the current resource block assignment mechanism for DL Resource Allocation Type 0 may be enhanced for Release 19 and onwards UEs, so that the number of bits in DCI for the indication of the Frequency Domain Resource Assignment is optimized.

[0085] Option 1: In one variant of the embodiment, the size of the RBG allocation bitmap, NRBG, is given by the downlink bandwidth part (DL BWP) size in VRBs and the number of VRBs per RBG according to the rules specified in Rel-15, so that all RBGs in the DL BWP are addressable, including those that completely fall into the UL subbands and the guard-bands according to the SBFD configuration. This option is transparent to Release 18 UEs, because the BS will simply not allocate in the bitmap the RBGs in the invalid positions. In this case the VRB to PRB mapping rule specified in Rel-15 (non-interleaving mapping) may be reused. More specifically, mapping of an allocated VRBnto the corresponding PRBnis according tothe following rules: ^^^^^^^^^^^^^^^^ = ^^^^^^^^^^^^^^^^P110624WO01 PCT APPLICATION 17 of 49

[0086] Option 2: In another variant of the embodiment, NRBGis the number of RBGs in the DL subbands in the downlink bandwidth part, excluding the RBGs that completely fall into the UL subband(s) and the guard bands according to the SBFD configuration. To generate the bitmap, the rule defined in 38.214 may be applied separately to each DL subband, to define the RBGs. The first and the last RBGs in each subband may have a size smaller than the maximum size of the RBG (P) depending on the position of the DL subbands with respect to the carrier resource block (CRB) grid and on if some RBGs partly overlap with a guard-band or an UL subband. A UE in SBFD operation may, based on the previously received SBFD configuration, identify the mapping of an allocated VRBnin DL subband j to the corresponding PRBnin thecorresponding DL subband with the following rule: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^ = ^^^^^^^^^^^^^^^^ − ^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^+ ^^^^^^^^^^^^^^^^^^^^ ^^^^ ^^^^^^^^^^^^^^^^ ^^^^ ^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^, where ^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^and ^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^are the first VRB and the first PRB in DL subband j respectively which can be derived from the SBFD configuration: ^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^ ^^^^−1^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^ = ^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^+ 1,are the last VRB and the last PRB respectively in the immediately preceding DL subband and both should be set to -1 if DL subband j is the first DL subband in the downlink bandwidth part; G is the number of PRBs between DL subband j-1 and j including the number of PRBs in UL subband(s) andguard-bands between the two DL subbands. For a D-U-D SBFD configuration ^^^^ =the size of one guard bandthe size of UL subband in RBs in BWP i.

[0087] For example, assuming a downlink bandwidth part consisting of 272 RBs, of which 216 are allocated to 2 DL subbands, 48 to an UL subband and 8 to guard-bands, following a D-U- D SBFD configuration: 108-4-48-4-108 (in RBs). In this example ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^0^^^^^^^^^^^is 0, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^0^^^^^^^^is107, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^1^^^^^^^^^^^is 108, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^1^^^^^^^^is 215, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^0^^^^^^^^^^^is 0, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^0^^^^^^^^is 107, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^1^^^^^^^^^^^is 164 and ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^1^^^^^^^^is 271.

[0088] This variant of the embodiment offers the benefit of reduced size of the resource allocation field in the scheduling DCI, and because it requires the UE to be provided with the SBFD configuration, can be considered only for Release 19 and onwards UEs.

[0089] Some embodiments include enhancements of non-interleaved VRB-to-PRB mapping for DL Resource Allocation Type 1. When interleaved VRB-to-PRB mapping is disabled, for Resource Allocation Type 1:P110624WO01 PCT APPLICATION 18 of 49

[0090] Option 1: For Release 18 and older UEs, resource allocation across multiple DL subbands is not supported if DL Resource Allocation Type 1 is configured.

[0091] Option 2: For DL Resource Allocation Type 1 the resource allocation indicates through RIV a range of consecutive VRBs, which can span one or more DL subbands, and some of which may fall into UL subband or guard-bands. A Release 19 and onwards UE, if previously provided with SBFD subband configuration, understands that VRBs falling into the UL subband or guard-bands, are to be considered as invalid and not used for PDSCH data mapping.

[0092] For example, assuming a DL BWP consisting of 272 RBs, of which 216 are allocated to 2 DL subbands, 48 to an UL subband and 8 to guard-bands, following a D-U-D SBFD configuration: 108-4-48-4-108 (in RBs). In this example, assume Resource Allocation Type 1 is configured and the RIV indicates a set of contiguous non-interleaved VRB with start VRB 0 and a length of 192 VRBs in a DL BWP of size 272 VRBs (in this option the DL BWP size and the VRB space include the UL subband and guard-bands). Receiving the RIV and being aware of the SBFD configuration, the UE can derive that PDSCH is mapped to PRBs 0, …, 107, 164, …, 191. VRBs from 108 to 163 fall into the UL subband and the guard-bands according to the SBFD configuration and are therefore considered as invalid.

[0093] FIGURE 5 illustrates an example of improvement for non-contiguous Type 1 Resource Allocation (option 2).

[0094] Option 3: DL Resource Allocation Type 1 may be improved so that resource allocation indicates through RIV a range of contiguous VRBs, which can span one or more DL subbands. When receiving this indication, the Release 19 or onwards UE is able to map the VRBs to PRBs, starting from the indicated VRB. If the contiguous VRBs are more than those that can be contained in the first DL subband, the UE, if previously provided with SBFD subband configuration, understands that the remaining VRBs are mapped to the next DL subband and applies a block-shift equivalent to the size of the UL subband and the guard bands in-betweenthe DL subbands. That is, for VRBs in DL subband 1, the mapping is ^^^^^^^^^^^^^^^^ = ^^^^^^^^^^^^^^^^; for VRBsin DL subband 2, the mappingis the size of one guard band in RBs, and ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^,^^^^,^^^^^^^^^^^^^^^^is the size of UL subband in RBs.

[0095] Assuming the same DL BWP configuration and the same SBFD configuration as in the previous example, in this option, the RIV rule described above may be modified so that the DL BWP size is that of the DL subbands, equivalent to 216 VRBs (in this option the DL BWP sizeP110624WO01 PCT APPLICATION 19 of 49 and the VRB space do not include the UL subband and guard bands). Assuming Resource Allocation Type 1 is configured and the RIV indicates a set of contiguous non-interleaved VRB with start VRB 0 and a length of 136 VRBs, receiving this RIV and being aware of the SBFD configuration, the UE may derive that PDSCH is mapped to PRBs 0, …, 107 in the first DL subband, and because 136>108, the UE applies a block-wise shift of 56 (the size of UL subband and guard-bands), and in the second DL subband the allocated PRBs are 164, …, 191.

[0096] FIGURE 6 illustrates an example of improvement for non-contiguous Type 1 Resource Allocation (option 3).

[0097] In another variant of enhancement, one of skill in the art may adapt the method to the case the DCI size for DCI format 1_0 in UE-specific search space (USS) is derived from the size of DCI format 1_0 in common search space (CSS) but applied to an active BWP with size of ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^with resource indication value corresponding to a starting resource block ^^^^^^^^^^^^^^^^^^^^^^^^^^^^=0,^^^^, 2.^^^^, … ,�^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^and a length in terms of virtually contiguously allocated resourceblocks ^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ = ^^^^ ,2.^^^^, … ,^^^^^^^^^^^^^^^^ .^^^^ where ^^^^^^^^^^^^^^^^ is given by the size of CORESET0 ifCORESET0 is configured for the cell or the size of initial DL BWP if CORESET0 is not configured for the cell.

[0098] Some embodiments include enhancement of interleaved VRB-to-PRB mapping for DL Resource Allocation Type 1. When interleaved VRB-to-PRB mapping is enabled, for Resource Allocation Type 1, the VRB-to-PRB mapping may be enhanced for SBFD operation considering one of the following options:

[0099] Option 1: Non interleaved mapping is applied. Option 1, 2 and above may be reused for this case.

[0100] Option 2: Modify VRB interleaving to operate separately on each DL subband, considering a specific starting position for each subband, depending on the SBFD carrier configuration (D-U-D, D-U or U-D). In this option the Rel. 15 formulation is then applied to the single subband, as follows: - Let the total number of RBs within BWP (Bandwidth Part) i and subband j be^^^^^^^^^^^^^^^^- Let the starting PRB position within BWP i and subband j be ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^,^^^^,^^^^- Let ^^^^^^^^be the RB bundle size for BWP i, as specified by RRC configuration. - The total number of RB bundles for each subband is ^^^^^^^^^^^^^^^^^^^^^^^^^^^^,^^^^=P110624WO01 PCT APPLICATION 20 of 49 oResource block bundle 0 size, in subband j, is ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^,0,^^^^,^^^^ = ^^^^^^^^ −�^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^,^^^^^^^,^^^^^^^^^^^^^^^^ ^^^^^^^^� resource blocks. oThe size of the last Resource Block Bundle (RBB), ^^^^^^^^^^^^^^^^^^^^^^^^^^^^,^^^^ − 1 ,is^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^,^^^^^^^^^^^^^^^^,^^^^,^^^^ =�^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^,^^^^,^^^^ + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^,^^^^,^^^^�^^^^^^^^^^^^ ^^^^^^^^ resource blocks if^^^^^^^^ > 0, and ^^^^^^^^ RBs otherwise.o All other RB bundles consist of ^^^^^^^^RBs. - The starting positions of the DL subband to which interleaving is applied is defined with respect to the starting RB of BWP ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^,^^^^, as follows: o If D-U, theo If D-U-D: ^ ^- Virtual resource blocks in the … ,^^^^^^^^^^^^^^^^^^^^^^^^^^^^,^^^^ − 1� are mapped to physicalresource blocks according to the rule in TS 38.211.

[0101] With this VRB-to-PRB mapping option, 1) it is only possible to allocate resources in one subband; 2) if Option A is considered for the starting position of the subbands, for Release 19 UEs, embodiments may allocate resources across different subbands, if improved Type 1 Resource Allocation is considered, following option 3b above; and 3) if Option B is considered for the starting position of the subbands, for Release 19 UEs, embodiments may allocate resources across different subbands if improved Type 1 Resource Allocation is considered, following option 3b above.

[0102] FIGURE 7 illustrates an example of VRB-to-PRB mapping, independent per DL subband (option 2).

[0103] Option 3: Modify VRB interleaving to operate on the full set of DL resources (sum of resources in the different DL subbands), independently on the carrier configuration, and then apply a block wise shift. In this option, Rel. 15 formulation is applied to a bandwidth of the size of all DL subbands resources. For this, a 2-step approach may be considered where: 1- Let the total number of RBs allocated to DL within BWP (Bandwidth Part) i, be ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^,^^^^. In case of two DL subbands,2- Let the starting PRB position within BWP i be ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^,^^^^^^^P110624WO01 PCT APPLICATION 21 of 49 3- Let ^^^^^^^^be the bundle size for BWP i, as defined by RRC 4- The total number of RB bundles for the BWP i is ^^^^^^^^^^^^^^^^^^^^^^^^^^^^=a. Resource block bundle 0 size is ^^^^^^^^^^^^^^^^^^^^ = ^^^^^^^^ −blocks. b. The size of the last Resource Block Bundle (RBB), ^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ − 1 ,is ^^^^^^^^^^^^^^^^^^^^^^^^^^^^,^^^^^^^^^^^^^^^^,^^^^ =and ^^^^^^^^resource blocks otherwise. c. All other resource block bundles consist of ^^^^^^^^resource blocks. 5- Finally, a block-wise shift G, is applied to achieve the final PRB mapping, and this depends on the SBFD carrier configuration: a. If D-U, {0,1,2,…,A-1, A, A+1, …, Nbundle-1} ->{0,1,2,…,A-1, A, A+1, …, Nbundle- 1} b. If D-U-D, {0,1,2,…,A-1, A, A+1, …, Nbundle-1} ->{0,1,2,…,A-1, A+G, A+G+1, …, N -1}, where G is the sizesize of each guard band in RBs. In this case, the number of bundles in each subband has to be derived so that the dimension of the two subbands is equivalent. For example, if ^^^^^^^^^^^^^^^^^^^^^^^^^^^^is even, the second subband starts from bundle ^^^^^^^^^^^^^^^^^^^^^^^^^^^^� 2 − 1.Otherwise, if ^^^^^^^^^^^^^^^^^^^^^^^^^^^^is uneven, the central bundle has to be split in two bundles with less RBs than ^^^^^^^^. c. If U-D, {0,1,2,…,A-1, A, A+1, …, Nbundle-1} ->{G,1+G,2+G,…,A-1+G, A+G, A+G+1, …, N -1}, where G is the sizeis the size of the guard band in RBs.

[0104] With this option, a Release 19 UE may be allocated resources across different DL subbands, if Improved Type 1 Resource Allocation is considered, following option 3c above.

[0105] FIGURE 8 illustrates an example of VRB-to-PRB mapping, combined for the 2 DL subbands (option 3).

[0106] Option 4: Modify VRB interleaving to operate on the full BWP by masking out the PRBs mapped to UL subband and guard-bands. In this option, the VRB-to-PRB mapping is applied to the bandwidth of the full BWP as in non-SBFD scenarios, which means that theP110624WO01 PCT APPLICATION 22 of 49 interleaving is applied also to RBBs that will be mapped to the UL subband and the guard bands. The UE, which was previously provided with the SBFD configuration, may identify the PRBs in UL subbands and guard bands as invalid and mask out the corresponding VRBs.

[0107] With this option, a Release 19 UE may be allocated resources across different DL subbands, with one of the following options: In one variant of this embodiment, the starting VRB number (RBstart) and the length of contiguously allocated resource block (LRBs) indicated by RIV includes the invalid VRBs. The UE should assume the invalid VRBs are not used for PDSCH data mapping (this is equivalent to enhanced Type 1 resource allocation, following option 3b above).

[0108] In another variant of this embodiment, the starting VRB number (RBstart) and the length of contiguously allocated resource block (LRBs) indicated by RIV does not include the invalid VRBs. The later variant offers the benefit of a reduced size of the resource allocation field in the scheduling DCI. Following the example in FIGURE 9, and assuming that the BS wants to allocate to a certain UE the first 8 useful VRBs in the DL BWP, the first variant of this embodiment builds a RIV considering RBstart=0, and LRB=12; the second variant instead considers an optimized RIV with RBstart=0, and LRB=8.

[0109] FIGURE 9 illustrates an example of VRB-to-PRB mapping, over the entire DL BWP (option 4).

[0110] FIGURE 10 illustrates an example of a communication system 100 in accordance with some embodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

[0111] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communicationP110624WO01 PCT APPLICATION 23 of 49 system 100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0112] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 102.

[0113] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0114] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunication network 102 and may be operated by the service provider or on behalf of the service provider. The host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remoteP110624WO01 PCT APPLICATION 24 of 49 devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0115] As a whole, the communication system 100 of FIGURE 10 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0116] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive IoT services to yet further UEs.

[0117] In some examples, the UEs 112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC).

[0118] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and / or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described hereinP110624WO01 PCT APPLICATION 25 of 49 regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.

[0119] The hub 114 may have a constant / persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub – that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 110b. In other embodiments, the hub 114 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0120] FIGURE 11 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console orP110624WO01 PCT APPLICATION 26 of 49 device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0121] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0122] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 11. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0123] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry 202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processorP110624WO01 PCT APPLICATION 27 of 49 (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs).

[0124] In the example, the input / output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0125] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and / or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.

[0126] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine,P110624WO01 PCT APPLICATION 28 of 49 or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

[0127] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device-readable storage medium.

[0128] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 218 and / or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0129] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-basedP110624WO01 PCT APPLICATION 29 of 49 communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0130] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0131] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0132] A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for AugmentedP110624WO01 PCT APPLICATION 30 of 49 Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and / or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 200 shown in FIGURE 11.

[0133] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0134] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0135] FIGURE 12 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).

[0136] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, orP110624WO01 PCT APPLICATION 31 of 49 macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0137] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0138] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.P110624WO01 PCT APPLICATION 32 of 49

[0139] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.

[0140] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.

[0141] The memory 304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and / or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated.

[0142] The communication interface 306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodimentsP110624WO01 PCT APPLICATION 33 of 49 a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and / or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0143] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).

[0144] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.

[0145] The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 310, the communication interface 306, and / or the processing circuitry 302 may be configured to perform any transmitting operations described herein as beingP110624WO01 PCT APPLICATION 34 of 49 performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0146] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0147] Embodiments of the network node 300 may include additional components beyond those shown in FIGURE 12 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.

[0148] FIGURE 13 is a flowchart illustrating an example method in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 13 may be performed by UE 200 described with respect to FIGURE 11.

[0149] The method may begin at step 1312, where the wireless device (e.g., UE 200) obtains a SBFD configuration indicating one or more subbands of a frequency band for transmission / reception in a first direction and one or more subbands of the frequency band for transmission / reception in a second direction. In some embodiments, the wireless device may obtain the SBFD configuration from a network node.

[0150] For SBFD operation, a portion of a wide bandwidth carrier, referred to as a subband, may be used for a different communication direction than that of the rest of the carrier. Correspondingly, different non-overlapping subbands are used for downlink and uplink. TheP110624WO01 PCT APPLICATION 35 of 49 SBFD configuration may comprise any of the SBFD configurations described with respect to the embodiments and examples described herein (e.g., D-U-D, U-D-U, etc.).

[0151] At step 1314, the wireless device receives a frequency domain resource allocation from a network node comprising a resource allocation for transmission / reception in the first direction for the frequency band. The resource allocation indicates a continuous range of VRBs available for transmission / reception.

[0152] For example, a network node informs the wireless device about downlink frequency domain resources for reception of PDSCH via a DCI. The configuration may comprise a Type 0 or Type 1 configuration, for example.

[0153] The frequency domain resource allocation for both downlink and uplink is described in more detail with respect to the embodiments and examples described herein.

[0154] At step 1316, the wireless device determines a mapping of VRBs to PRBs based on the frequency domain resource allocation and the SBFD configuration. The mapped PRBs are within the subbands for transmission / reception in the first direction.

[0155] For example, if the first direction is downlink, then the mapped PRBs are within the subbands for downlink and not within the subbands for uplink or any guard subbands. If the first direction is uplink, then the mapped PRBs are within the subbands for uplink and not within the subbands for downlink or any guard subbands.

[0156] The mapping may be performed in various different ways. Some embodiments include interleaving and some do not.

[0157] In particular embodiments, determining the mapping of VRBs to PRBs comprises determining a mapping of the VRBs to PRBs where VRBs that do not map to the one or more subbands for transmission / reception in the first direction are considered to be invalid and are not used for resource mapping. An example is described above with respect to non-interleaved VRB-to-PRB mapping for DL Resource Allocation Type 1 and Option 2 and FIGURE 5.

[0158] In particular embodiments, interleaving is performed when determining the mapping of the VRBs to PRBs where VRBs that do not map to the one or more subbands for transmission / reception in the first direction are considered to be invalid and are not used for resource mapping. An example is described above with respect to interleaved VRB-to-PRB mapping for DL Resource Allocation Type 1 and Option 4 and FIGURE 9.

[0159] In particular embodiments, determining the mapping of VRBs to PRBs comprises determining a mapping of the VRBs to PRBs where VRBs that do not map to a first subbandP110624WO01 PCT APPLICATION 36 of 49 of the one or more subbands for transmission / reception in the first direction are shifted to map to a second subband of the one or more subbands for transmission / reception in the first direction. An example is described above with respect to non-interleaved VRB-to-PRB mapping for DL Resource Allocation Type 1 and Option 3 and FIGURE 6. This example uses a block shift in the mapping to jump over the unused subbands. Another example is described above with respect to VRB-to-PRB mapping for DL Resource Allocation Type 0 and Option 2. In this example, the shift is part of the mapping rule.

[0160] In particular embodiments, interleaving is performed when determining the mapping of VRBs to PRBs and the interleaving is performed on a bandwidth comprising a sum of all the subbands for transmission / reception in the first direction. An example is described above with respect to interleaved VRB-to-PRB mapping for DL Resource Allocation Type 1 and Option 3 and FIGURE 8.

[0161] In particular embodiments, interleaving is performed when determining the mapping of the VRBs to PRBs wherein the interleaving pattern ensures that the mapped PRBs are within the subbands for transmission / reception in the first direction. An example is described above with respect to interleaved VRB-to-PRB mapping for DL Resource Allocation Type 1 and Option 2 and FIGURE 7.

[0162] Although particular mappings are described with respect to step 1316, the wireless device may perform the mapping according to any of the embodiments and examples described herein.

[0163] In particular embodiments, the first direction comprises downlink, the second direction comprises uplink, and performing transmission / reception in the first direction using the mapped PRBs comprises performing downlink reception in a PDSCH using the mapped PRBs.

[0164] In particular embodiments, the first direction comprises uplink, the second direction comprises downlink, and performing transmission / reception in the first direction using the mapped PRBs comprises performing uplink transmission in a PUSCH using the mapped PRBs.

[0165] At step 1318, the wireless device performs transmission / reception in the first direction using the mapped PRBs. The transmission / reception is described in more detail with respect to the embodiments and examples described herein.

[0166] Modifications, additions, or omissions may be made to method 1300 of FIGURE 13. Additionally, one or more steps in the method of FIGURE 13 may be performed in parallel or in any suitable order.P110624WO01 PCT APPLICATION 37 of 49

[0167] FIGURE 14 is a flowchart illustrating an example method in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 14 may be performed by network node 300 described with respect to FIGURE 12.

[0168] The method may begin at step 1410, where the network node (e.g., network node 300) transmits to the wireless device an indication of which variant of the mapping of VRBs to PRBs to use when mapping VRBs to PRBs. For example, the wireless device may support a capability of performing more than one mapping variant, and thus the network node configures the wireless device with a preferred variant.

[0169] At step 1412, the network node obtains a SBFD configuration for a wireless device. The SBFD configuration indicates one or more subbands of a frequency band for transmission / reception in a first direction and one or more subbands of the frequency band for transmission / reception in a second direction. The SBFD configuration may comprise any of the SBFD configurations described with respect to the embodiments and examples described herein (e.g., D-U-D, U-D-U, etc.).

[0170] At step 1414, the network node transmits a frequency domain resource allocation to the wireless device. The frequency domain resource allocation comprises a resource allocation for transmission / reception in the first direction for the frequency band. The resource allocation indicates a continuous range of VRBs available for transmission / reception. The frequency domain resource allocation for both downlink and uplink is described in more detail with respect to the embodiments and examples described herein.

[0171] At step 1416, the network node determines a mapping of VRBs to PRBs based on the frequency domain resource allocation and the SBFD configuration. The mapped PRBs are within the subbands for transmission / reception in the first direction. The network node determines the mapping in the same way as the wireless device described with respect to step 1316 of FIGURE 13. In particular embodiments, the network node may perform the mapping according to any of the embodiments and examples described herein.

[0172] At step 1418, the network node performs transmission / reception in the first direction using the mapped PRBs. The transmission / reception is described in more detail with respect to the embodiments and examples described herein.

[0173] Modifications, additions, or omissions may be made to method 1400 of FIGURE 14. Additionally, one or more steps in the method of FIGURE 14 may be performed in parallel or in any suitable order.P110624WO01 PCT APPLICATION 38 of 49

[0174] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

[0175] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0176] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.

[0177] Some example embodiments are described below. Group A Embodiments 1. A method performed by a wireless device, the method comprising: − any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. 2. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above. 3. The method of any of the previous two embodiments, further comprising: − providing user data; and − forwarding the user data to a host computer via the transmission to the base station.

Claims

P110624WO01 PCT APPLICATION 39 of 49 4. A method performed by a base station, the method comprising: − any of the steps, features, or functions described above with respect to base stations, either alone or in combination with other steps, features, or functions described above.

5. The method of the previous embodiment, further comprising one or more additional base station steps, features or functions described above.

6. The method of any of the previous embodiments, further comprising: − obtaining user data; and − forwarding the user data to a host computer or a wireless device.

7. A mobile terminal comprising: − processing circuitry configured to perform any of the steps of any of the Group A embodiments; and − power supply circuitry configured to supply power to the wireless device.

8. A base station comprising: − processing circuitry configured to perform any of the steps of any of the Group B embodiments; − power supply circuitry configured to supply power to the wireless device.

9. A user equipment (UE) comprising: − an antenna configured to send and receive wireless signals; − radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; − the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; − an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;P110624WO01 PCT APPLICATION 40 of 49 − an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and − a battery connected to the processing circuitry and configured to supply power to the UE.

10. A communication system including a host computer comprising: − processing circuitry configured to provide user data; and − a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), − wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.

11. The communication system of the pervious embodiment further including the base station.

12. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.P110624WO01 PCT APPLICATION 41 of 49 CLAIMS:

1. A method performed by a wireless device, the method comprising: obtaining (1312) a subband full duplex, SBFD, configuration, the SBFD configuration indicating one or more subbands of a frequency band for transmission / reception in a first direction and one or more subbands of the frequency band for transmission / reception in a second direction; receiving (1314) a frequency domain resource allocation from a network node, the frequency domain resource allocation comprising a resource allocation for transmission / reception in the first direction for the frequency band, the resource allocation indicating a continuous range of virtual resource blocks, VRBs, available for transmission / reception; determining (1316) a mapping of VRBs to physical resource blocks, PRBs, based on the frequency domain resource allocation and the SBFD configuration, wherein the mapped PRBs are within the subbands for transmission / reception in the first direction; and performing (1318) transmission / reception in the first direction using the mapped PRBs.

2. The method of claim 1, wherein determining the mapping of VRBs to PRBs comprises determining a mapping of the VRBs to PRBs where VRBs that do not map to the one or more subbands for transmission / reception in the first direction are considered to be invalid and are not used for resource mapping.

3. The method of claim 2, wherein interleaving is performed when determining the mapping of the VRBs to PRBs where VRBs that do not map to the one or more subbands for transmission / reception in the first direction are considered to be invalid and are not used for resource mapping.

4. The method of claim 1, wherein determining the mapping of VRBs to PRBs comprises determining a mapping of the VRBs to PRBs where VRBs that do not map to a first subband of the one or more subbands for transmission / reception in the first direction are shifted to map to a second subband of the one or more subbands for transmission / reception in the first direction.P110624WO01 PCT APPLICATION 42 of 49 5. The method of claim 4, wherein interleaving is performed when determining the mapping of VRBs to PRBs and the interleaving is performed on a bandwidth comprising a sum of all the subbands for transmission / reception in the first direction.

6. The method of claim 1, wherein interleaving is performed when determining the mapping of the VRBs to PRBs wherein the interleaving pattern ensures that the mapped PRBs are within the subbands for transmission / reception in the first direction.

7. The method of any one of claims 1-6, wherein the first direction comprises downlink, the second direction comprises uplink, and performing transmission / reception in the first direction using the mapped PRBs comprises performing downlink reception in a physical downlink shared channel, PDSCH, using the mapped PRBs.

8. The method of claim 7, wherein the frequency domain resource allocation comprises a downlink Type 1 resource allocation scheme.

9. The method of any one of claims 2 and 4, wherein the frequency domain resource allocation comprises a downlink Type 0 resource allocation scheme.

10. The method of any one of claims 1-6, wherein the first direction comprises uplink, the second direction comprises downlink, and performing transmission / reception in the first direction using the mapped PRBs comprises performing uplink transmission in a physical uplink shared channel, PUSCH, using the mapped PRBs.

11. A wireless device (200) comprising processing circuitry (202), the processing circuitry operable to: obtain a subband full duplex, SBFD, configuration, the SBFD configuration indicating one or more subbands of a frequency band for transmission / reception in a first direction and one or more subbands of the frequency band for transmission / reception in a second direction; receive a frequency domain resource allocation from a network node (300), the frequency domain resource allocation comprising a resource allocation forP110624WO01 PCT APPLICATION 43 of 49 transmission / reception in the first direction for the frequency band, the resource allocation indicating a continuous range of virtual resource blocks, VRBs, available for transmission / reception; determine a mapping of VRBs to physical resource blocks, PRBs, based on the frequency domain resource allocation and the SBFD configuration, wherein the mapped PRBs are within the subbands for transmission / reception in the first direction; and perform transmission / reception in the first direction using the mapped PRBs.

12. The wireless device of claim 11, wherein the processing circuitry is operable to determine the mapping of VRBs to PRBs by determining a mapping of the VRBs to PRBs where VRBs that do not map to the one or more subbands for transmission / reception in the first direction are considered to be invalid and are not used for resource mapping.

13. The wireless device of claim 12, wherein the processing circuitry is operable to perform interleaving when determining the mapping of the VRBs to PRBs and VRBs that do not map to the one or more subbands for transmission / reception in the first direction are considered to be invalid and are not used for resource mapping.

14. The wireless device of claim 11, wherein the processing circuitry is operable to determine the mapping of VRBs to PRBs by determining a mapping of the VRBs to PRBs where VRBs that do not map to a first subband of the one or more subbands for transmission / reception in the first direction are shifted to map to a second subband of the one or more subbands for transmission / reception in the first direction.

15. The wireless device of claim 14, wherein the processing circuitry is operable to perform interleaving when determining the mapping of VRBs to PRBs and the interleaving is performed on a bandwidth comprising a sum of all the subbands for transmission / reception in the first direction.

16. The wireless device of claim 11, wherein the processing circuitry is operable to perform interleaving when determining the mapping of the VRBs to PRBs wherein the interleaving pattern ensures that the mapped PRBs are within the subbands forP110624WO01 PCT APPLICATION 44 of 49 transmission / reception in the first direction.

17. The wireless device of any one of claims 11-16, wherein the first direction comprises downlink, the second direction comprises uplink, and the processing circuitry is operable to perform transmission / reception in the first direction using the mapped PRBs by performing downlink reception in a physical downlink shared channel, PDSCH, using the mapped PRBs.

18. The wireless device of claim 17, wherein the frequency domain resource allocation comprises a downlink Type 1 resource allocation scheme.

19. The wireless device of any one of claims 12 and 14, wherein the frequency domain resource allocation comprises a downlink Type 0 resource allocation scheme.

20. The wireless device of any one of claims 11-16, wherein the first direction comprises uplink, the second direction comprises downlink, and the processing circuitry is operable to perform transmission / reception in the first direction using the mapped PRBs by performing uplink transmission in a physical uplink shared channel, PUSCH, using the mapped PRBs.

21. A method performed by a network node, the method comprising: obtaining (1412) a subband full duplex, SBFD, configuration for a wireless device, the SBFD configuration indicating one or more subbands of a frequency band for transmission / reception in a first direction and one or more subbands of the frequency band for transmission / reception in a second direction; transmitting (1414) a frequency domain resource allocation to the wireless device, the frequency domain resource allocation comprising a resource allocation for transmission / reception in the first direction for the frequency band, the resource allocation indicating a continuous range of virtual resource blocks, VRBs, available for transmission / reception; determining (1416) a mapping of VRBs to physical resource blocks, PRBs, based on the frequency domain resource allocation and the SBFD configuration, wherein the mappedP110624WO01 PCT APPLICATION 45 of 49 PRBs are within the subbands for transmission / reception in the first direction; and performing (1418) transmission / reception in the first direction using the mapped PRBs.

22. The method of claim 21, wherein determining the mapping of VRBs to PRBs comprises determining a mapping of the VRBs to PRBs where VRBs that do not map to the one or more subbands for transmission / reception in the first direction are considered to be invalid and are not used for resource mapping.

23. The method of claim 22, wherein interleaving is performed when determining the mapping of the VRBs to PRBs where VRBs that do not map to the one or more subbands for transmission / reception in the first direction are considered to be invalid and are not used for resource mapping.

24. The method of claim 21, wherein determining the mapping of VRBs to PRBs comprises determining a mapping of the VRBs to PRBs where VRBs that do not map to a first subband of the one or more subbands for transmission / reception in the first direction are shifted to map to a second subband of the one or more subbands for transmission / reception in the first direction. 25 The method of claim 24, wherein interleaving is performed when determining the mapping of VRBs to PRBs and the interleaving is performed on a bandwidth comprising a sum of all the subbands for transmission / reception in the first direction.

26. The method of claim 21, wherein interleaving is performed when determining the mapping of the downlink VRBs to PRBs wherein the interleaving pattern ensures that the mapped PRBs are within the subbands for transmission / reception in the first direction.

27. The method of any one of claims 21-26, wherein the first direction comprises downlink, the second direction comprises uplink, and performing transmission / reception in the first direction using the mapped PRBs comprises performing downlink transmission in a physical downlink shared channel, PDSCH, using the mapped PRBs.P110624WO01 PCT APPLICATION 46 of 49 28. The method of claim 27, wherein the frequency domain resource allocation scheme comprises a downlink Type 1 resource allocation scheme.

29. The method of any one of claims 22 and 24, wherein the frequency domain resource allocation comprises a downlink Type 0 resource allocation scheme.

30. The method of any one of claims 21-26, wherein the first direction comprises uplink, the second direction comprises downlink, and performing transmission / reception in the first direction using the mapped PRBs comprises performing uplink reception in a physical uplink shared channel, PUSCH, using the mapped PRBs.

31. The method of any one of claims 21-30, further comprising transmitting (1410) to the wireless device an indication of which variant of the mapping of VRBs to PRBs to use when mapping VRBs to PRBs.

32. A network node (300) comprising processing circuitry (302), the processing circuitry operable to: obtain a subband full duplex, SBFD, configuration for a wireless device, the SBFD configuration indicating one or more subbands of a frequency band for transmission / reception in a first direction and one or more subbands of the frequency band for transmission / reception in a second direction; transmit a frequency domain resource allocation to the wireless device, the frequency domain resource allocation comprising a resource allocation for transmission / reception in the first direction for the frequency band, the resource allocation indicating a continuous range of virtual resource blocks, VRBs, available for transmission / reception; determine a mapping of VRBs to physical resource blocks, PRBs, based on the frequency domain resource allocation and the SBFD configuration, wherein the mapped PRBs are within the subbands for transmission / reception in the first direction; and perform transmission / reception in the first direction using the mapped PRBs.

33. The network node of claim 32, wherein the processing circuitry is operable to determine the mapping of VRBs to PRBs by determining a mapping of the VRBs to PRBsP110624WO01 PCT APPLICATION 47 of 49 where VRBs that do not map to the one or more subbands for transmission / reception in the first direction are considered to be invalid and are not used for resource mapping.

34. The network node of claim 33, wherein the processing circuitry is operable to perform interleaving when determining the mapping of the VRBs to PRBs where VRBs that do not map to the one or more subbands for transmission / reception in the first direction are considered to be invalid and are not used for resource mapping.

35. The network node of claim 32, wherein the processing circuitry is operable to determine the mapping of VRBs to PRBs by determining a mapping of the VRBs to PRBs where VRBs that do not map to a first subband of the one or more subbands for transmission / reception in the first direction are shifted to map to a second subband of the one or more subbands for transmission / reception in the first direction. 36 The network node of claim 25, wherein the processing circuitry is operable to perform interleaving when determining the mapping of VRBs to PRBs and the interleaving is performed on a bandwidth comprising a sum of all the subbands for transmission / reception in the first direction.

37. The network node of claim 32, wherein the processing circuitry is operable to perform interleaving when determining the mapping of the downlink VRBs to PRBs wherein the interleaving pattern ensures that the mapped PRBs are within the subbands for transmission / reception in the first direction.

38. The network node of any one of claims 32-37, wherein the first direction comprises downlink, the second direction comprises uplink, and the processing circuitry is operable to perform transmission / reception in the first direction using the mapped PRBs by performing downlink transmission in a physical downlink shared channel, PDSCH, using the mapped PRBs.

39. The network node of claim 38, wherein the frequency domain resource allocation scheme comprises a downlink Type 1 resource allocation scheme.P110624WO01 PCT APPLICATION 48 of 49 40. The network node of any one of claims 33 and 35, wherein the frequency domain resource allocation comprises a downlink Type 0 resource allocation scheme.

41. The network node of any one of claims 32-37, wherein the first direction comprises uplink, the second direction comprises downlink, and performing transmission / reception in the first direction using the mapped PRBs comprises performing uplink reception in a physical uplink shared channel, PUSCH, using the mapped PRBs.

42. The network node of any one of claims 32-41, the processing circuitry further operable to transmit to the wireless device an indication of which variant of the mapping of VRBs to PRBs to use when mapping VRBs to PRBs.

Images