Enhanced frequency domain resource allocation for SBFD

Abstract

According to some embodiments, a method is performed by a wireless device. The method includes 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 a frequency band for transmission / reception in a second direction. The method also includes receiving a frequency domain resource allocation from a network node, the frequency domain resource allocation including resource allocations for transmission / reception in the first direction of the frequency bands. The resource allocation indicates a contiguous range of virtual resource blocks (VRBs) available for transmission / reception. The method further includes 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 also includes performing transmission / reception in the first direction using the mapped PRBs.

Description

Technical Field

[0001] The embodiments of this disclosure are directed to wireless communication, and more specifically, to enhancements in frequency domain resource allocation for sub-band frequency division (SBFD). Background Technology

[0002] Generally, all terms used herein will be interpreted according to their ordinary meaning in the relevant art, unless explicitly given and / or implied from the context of their use. All references to an element, device, component, part, step, etc., are to be interpreted as referring to at least one instance of that element, device, component, part, step, etc., unless otherwise expressly stated. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is explicitly described as occurring after or before another step, and / or implicitly implied as occurring after or before another step. Any feature of any embodiment disclosed herein may be applied to any other embodiment where appropriate. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the appended embodiments will become apparent from the following description.

[0003] The 3GPP New Radio (NR) standards (e.g., 38300-h50) are designed to provide services for a variety of use cases, such as enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and machine-type communications (MTC). Each of these services has different technical requirements. For example, the general requirement for eMBB is a high data rate with moderate latency and moderate coverage, while URLLC services require low latency and high reliability transmission, but may have a moderate data rate.

[0004] According to the current protocol, an NR time slot consists of several orthogonal frequency division multiplexing (OFDM) symbols, either 7 or 14 symbols (OFDM subcarrier spacing ≤ 60 kHz) or 14 symbols (OFDM subcarrier spacing > 60 kHz). Figure 1 A time slot with 14 OFDM symbols is shown. Figure 1 middle, and These represent the time slot and the OFDM symbol duration, respectively.

[0005] NR supports different types of duplex communication modes. To support a variety of target use cases with different requirements, different duplex communication modes are discussed in the 3GPP standard. Furthermore, the same device may be able to operate using different duplex modes, for example, to achieve different overall communication performance based on its needs.

[0006] Transmissions and receptions from wireless communication devices (e.g., base stations (BS) or user equipment (UE) in a cellular system) can be multiplexed in the frequency domain or the time domain (or a combination thereof). The most relevant duplex modes are discussed below.

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

[0008] like Figure 2 As shown in the top left corner of (a), FDD means that transmission (TX) and reception (RX) occur on different, fully separated carriers. Therefore, 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 for the UE in a cellular communication system, FDD can be either full-duplex (FD-FDD) or half-duplex (HD-FDD).

[0009] In FD-FDD, a UE can transmit and receive simultaneously, while in HD-FDD operation, a UE cannot transmit and receive simultaneously (although the BS can still perform RX / TX simultaneously, for example, receiving from one UE while transmitting to another). In Long Term Evolution (LTE), HD-FDD terminals monitor / receive in the DL unless explicitly instructed to transmit in a specific subframe.

[0010] Figure 2 Different types of duplex communication modes are shown. (a) FDD, (b) TDD, (c) Subband Frequency Division (SBFD), and (d) In-band Frequency Division (IBFD).

[0011] Figure 3 A comparison of TDD operations is shown: (a) static TDD in channels 1 and 2, and (b) static TDD in channel 2 and dynamic TDD in channel 1.

[0012] Figure 4 The diagram illustrates TDD operation options and interference scenarios.

[0013] For TDD, such as Figure 2 As shown in the upper right of (b), TX and RX occur within the same carrier in different non-overlapping time slots. Therefore, TDD can operate in unpaired spectrum. For TDD operation, there is only a single carrier frequency, and UL and DL transmissions are always time-separated on a cell basis. Because the same carrier frequency is used for UL and DL transmissions, both the BS and UE need to switch from TX to RX, and vice versa.

[0014] A fundamental aspect of any TDD system is the possibility of providing a sufficiently large protection time during which neither DL (Deep Flow) nor UL (Ultra Flow) transmissions occur. This is required to avoid interference between UL and DL transmissions. For NR (Normally Infinite Flow), this protection time is provided by special time slots, which are divided into three parts: a symbol for DL, a protection period (GP), and a symbol for UL. The remaining time slots are allocated to either UL or DL ​​transmissions.

[0015] The only interference in this configuration occurs within transmissions on the same link, within their own channels, and from adjacent channels, assuming synchronization is also assumed across different operators. This is in Figure 3 As shown in (a), the two networks deployed in Channel 1 and Channel 2 are synchronized and will only be subject to in-channel and adjacent-channel interference from the same link.

[0016] exist Figure 4 Interference links are further described in (a). This option is used, for example, by European operators and recommended in regulations, and requires that all carriers across the entire carrier bandwidth or in the same frequency band use the same DL transmission or UL reception direction.

[0017] Dynamic TDD describes an operating mode in which the network adapts the DL / UL subframe mode according to service conditions. This leads to interference between different links (uplink and downlink), and this is known as Cross-Link Interference (CLI), i.e., BS-to-BS and UE-to-UE, such as... Figure 4 As shown in (b).

[0018] CLI interference can occur both within the same operator and between operators. Figure 3 (b) An example is provided. Specifically, deployment on channel 1 requires additional UL time slots to serve UL traffic, and for this purpose, the TDD modes of BS1 and BS2 are adjusted to increase the UL ratio. For this reason, within the same network, deployments will suffer BS-to-BS and UE-to-UE interference in time slots 2 and 3.

[0019] Furthermore, the mode used in Channel 1 is out of sync with the static TDD mode used in Channel 2. For this reason, deployments in Channel 1 will suffer BS-BS and UE-UE interference from adjacent channels (time slots 2, 3, and 4). Conversely, on Channel 2, deployments will suffer UE-UE interference from adjacent channels in time slots 2, 3, and 4, but only from the same link interference within Channel 2.

[0020] like Figure 2As shown in the lower left of (c), Subband Full-Duplex (SBFD) is being studied in 3GPP Release 18 as part of 5G advanced standardization (e.g., 38211-100). For SBFD operation, a portion of a wideband carrier, called a subband, can be used for a different communication direction than the rest of the carrier. Accordingly, different non-overlapping subbands are used for DL ​​and UL. This differs from regular TDD operation, in which the entire bandwidth of the carrier is always used for either DL or UL. SBFD operation can also be performed across different carriers within the same frequency band, where one or more carriers within the band can be used for communication directions different from those of other carriers. This also differs from regular TDD operation, in which all carriers within the band are always used for the same communication direction.

[0021] In the 3GPP Release 18 study, the scope was limited, meaning that during SBFD communication, only the BS (Base Station) used the corresponding non-overlapping subband to simultaneously transmit DL (Deep Length) and receive UL (Ultra Length). Following standard HD TDD operation, individual UEs were scheduled only in one direction (DL or UL) at a time. However, for future 3GPP releases, SBFD operation at the UE has also been discussed as a potential research topic, where the UE uses the corresponding non-overlapping subband to simultaneously transmit UL and receive DL. Interference links affecting SBFD Rel.18 deployment are... Figure 4 As shown in (c).

[0022] like Figure 2 As shown in the lower right corner of (d), Single-Frequency Full-Duplex (SFFD) or In-Band Full-Duplex (IBFD) has also been proposed for study in the 3GPP standardization. It was discussed but excluded from the scope of Release 18, and is now being discussed again in 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 used simultaneously for DL ​​and UL operations. In other words, the same time and frequency resources can be used for TX and RX on the same device. Similar to SBFD operation, SFFD operation for base stations and UEs is also being discussed.

[0023] The Physical Downlink Shared Channel (PDSCH) is the DL physical channel that delivers user data from the gNB to the UE. The network uses Downlink Control Information (DCI) to inform the UE of the frequency resources to be used for receiving the PDSCH. Within the DCI format, the "Frequency Domain Resource Allocation" field 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 which resource allocation scheme will be used via Radio Resource Control (RRC) signaling within the PDSCH-Config IE.

[0025] For downlink resource allocation type 0, the network requests the UE to use type 0 resource allocation via RRC signaling (resource allocation type 0) or via DCI. DL resource allocation type 0 is based on bitmap indication, where resource block (RB) allocation information includes a bitmap indicating the resource block group (RBG) allocated to the UE.

[0026] An RBG is a set of contiguous Virtual Resource Blocks (VRBs). For type 0 resource allocations, only non-interleaved VRB-to-PRB mappings are possible, which means... Mapped to Bitmap has The size of the bitmap is such that each bit in the bitmap corresponds to an RBG, making each RBG within the bandwidth portion (BWP) addressable. If the corresponding bit value in the bitmap is 1, the RBG is assigned to the UE, and if the bit value is 0, the RBG is not assigned to the UE.

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

[0028] The total number of RBGs in DL BWP is The size of the first RBG is The size of the last RBG is At that time , or otherwise P. The size of all other RBGs is P. For more details, see Section 5.1.2.2.1 of TS 38.214.

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

[0030] In this case, the process of exporting the assigned PRB involves two steps: Use the Resource Indicator Value (RIV) method to derive a set of contiguously allocated VRBs (starting VRB and length of the VRB); and Perform VRB to PRB mapping: In this step, an interleaved or non-interleaved mapping process is used to map a set of VRBs (derived from step 1) to a set of PRBs.

[0031] Regarding the RIV for exporting contiguously allocated VRBs, DL type 1 resource allocation is based on the number of initial VRBs. RB start The length of the RIV and the VRB according to the continuous allocation LRB The RIV value is defined as follows: if otherwise in No more than When receiving a scheduling grant in DCI format 1_2 or 1_3, the downlink type 1 resource allocation field is determined by the corresponding starting resource block group. RIV and resource block groups allocated according to virtual contiguous allocation The length composition is the same as above.

[0032] Regarding the VRB to PRB mapping, once the starting VRB number and the number of consecutive VRBs are known, it is necessary to derive the actual PRB required for receiving the PDSCH. This requires a VRB to PRB mapping (e.g., 38.211).

[0033] The standard currently supports two different types of VRB to PRB mapping: non-interleaved mapping and interleaved mapping.

[0034] 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 assigned to the PRB in a sequential and continuous manner. This strategy simplifies the mapping process but leads to a reduction in frequency diversity.

[0035] For interleaved VRB to PRB mapping, the mapping process is defined according to the resource block bundle, based on the formula defined in Rel.15 of TS 38.211. The bundle size can be determined by higher-level parameters. VRB-ToPRB-Interleaver The configuration is set to 2, otherwise it is assumed by the UE. Modulated and precoded symbols are allocated to the PRB in a non-contiguous and non-sequential manner. This strategy increases frequency diversity by extending symbols across available resources, thereby improving resistance to frequency-selective fading and interference.

[0036] DCI may or may not include a single bit field 'VRB to PRB mapping' (e.g., 38.212). When this bit is absent, a non-interleaved mapping is assumed, and the resource allocation type is 0. When this bit is present, a type 1 resource allocation is considered, and if the bit is 0, interleaving is not configured, and if the bit is 1, interleaving is configured.

[0037] When indicating the interleaved VRB to PRB mapping, the concept of Resource Block Bundles (RBBs) is defined, where each RBB is a set of contiguous RBs. The size of an RBB is determined by... PDSCH-Config Provided via VRB-ToPRB-Interleaver. This field allows you to configure the RBB size to be 2RB or 4RB.

[0038] Depending on the size of the BWP and the size of the RBB (L), the RBB size of the first and last RBBs can be different from the RBB size configured by the RRC.

[0039] 1- Let the total number of Rb within BWP (bandwidth portion) I be... 2- Let the starting PRB position within BWP i be... 3- Let L i The RBB size of BWPi, as defined by RRC. 4- The total number of RBBs in BWPi is a. Resource block bundle 0 size is Resource block.

[0040] b. The last resource block bundle The size is resource block, if And otherwise, L i Resource block.

[0041] c. All other resource block bundles are controlled by L i Resource block composition.

[0042] 5- Interval The VRB in the data is mapped to the PRB according to the following formula: a. VRB Mapped to PRB b. VRB bundle Mapped to PRB bundle ,in Defined in TS38.211: i. ii. iii. iv. v. vi. Several challenges exist. For example, in SBFD operation, the carrier is divided into multiple subbands designated for DL ​​or UL transmission. When there is more than one DL subband in an SBFD carrier, the DL frequency resources (i.e., PRB) 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, allowing the UE to allocate as many downlink resources as possible from the carrier if needed.

[0043] As mentioned above, the current NR specification supports two different DL resource allocation schemes in the frequency domain: DL resource allocation type 0 and type 1. For DL ​​resource allocation type 0, the resource block allocation information includes a bitmap indicating the resource block group (RBG) allocated to the scheduled UE, where the RBG is a group of contiguous virtual resource blocks (VRBs). DL resource allocation type 0 already supports non-contiguous resource allocation, so it can be directly used for PDSCH frequency resource allocation of the UE in SBFD operations, where the allocated PRBs may potentially fall into multiple DL subbands. However, because the dimension of DL subbands is reduced compared to the dimension of DL BWPs, the number of bits used in the DCI to indicate frequency domain resource allocation can be optimized for UEs of version 19 and later when configuring SBFD.

[0044] For DL ​​resource allocation type 1, resource block allocation information indicates to the scheduled UE a set of consecutively allocated non-interleaved or interleaved virtual resource blocks (VRBs) within the active bandwidth portion. For SBFD operations, DL resource allocation type 1 with non-interleaved VRB-to-PRB mappings means that the UE can only be allocated consecutive resources restricted to one DL subband. For DL ​​resource allocation type 1 with interleaved VRB-to-PRB mappings, it is not even guaranteed that all indicated VRBs will be mapped to valid DL PRBs in the DL subband after interleaving. Therefore, in order to be able to allocate PDSCH resources across multiple DL subbands and to avoid indicated VRBs being mapped to PRBs outside the DL subband after interleaving, DL resource allocation type 1 needs to be enhanced. Summary of the Invention

[0045] As described above, there are currently certain challenges in frequency domain resource allocation for Subband Frequency Division (SBFD). Certain aspects of this disclosure and its embodiments can provide solutions to these or other challenges. For example, the specific embodiments described herein have three objectives: 1) to define options for enhancing downlink (DL) resource allocation types 0 and 1 such that the frequency domain resource allocation field in the scheduling DCI is optimized for user equipment (UE) versions 19 and higher; 2) to define options for enhancing DL resource allocation type 1 such that, for interleaved and non-interleaved virtual resource block (VRB) to PRB mapping, frequency domain resources (i.e., physical resource blocks (PRBs)) across multiple subbands can be allocated to UEs of version 19 and higher in SBFD operations; 3) to define enhanced options for interleaved VRB to PRB mapping in SBFD operations to ensure that the indicated VRB is mapped to a PRB in the DL subband. The enhancements can be transparent to UEs of version 18 and older.

[0046] Specific implementations enhance the VRB-PRB mapping mechanism for DL ​​resource allocation types 0 and 1 and the physical downlink shared channel (PDSCH) of base stations for deploying SBFD, enabling UEs of version 18 and older to operate in a transparent manner, and SBFD-enabled UEs of version 19 and later to operate in an optimized manner, with full potential even when considering SBFD configurations with multiple discontinuous DL subbands (e.g., DUD).

[0047] More specifically, specific embodiments define 1) options for resource allocation type 0 and type 1 such that the number of bits used for frequency domain resource allocation in the scheduling DCI is optimized; 2) options for resource allocation type 1 to support DL resource allocation across multiple DL subbands for both cases with and without interleaved VRB-to-PRB mapping enabled; and 3) options for enhanced interleaved VRB-to-PRB mapping for SBFD operations to ensure that the indicated VRB is mapped to a PRB in the DL subband.

[0048] Specific embodiments include methods for enhanced DL resource allocation types 0 and 1 for SBFD operation, such that the frequency domain resource allocation field in the DCI is transparent to UEs of version 18 and older, and can be optimized for UEs of version 19 and higher.

[0049] Specific embodiments include an enhanced DL resource allocation type 1 method for SBFD operation, such that the inclusion of UL subbands and guard bands in frequency resource allocation is transparent to UEs of version 18 and older, and allows UEs of version 19 and higher to have their full potential through explicit configuration (e.g., fields in RRC signaling).

[0050] Similar methods can also be extended and applied to SBFD UL resource allocation, such as SBFD configurations like UDU. Specific embodiments include a method for enhancing PDSCH VRB-to-PRB mapping in SBFD operation, such that indicated VRBs are mapped to PRBs in DL subbands. When interleaved VRB-to-PRB mapping is disabled, for resource allocation type 1, for UEs of version 18 and earlier, resource allocation across multiple DL subbands is not supported if DL resource allocation type 1 is configured. For UEs of version 19 and later, DL resource allocation type 1 is improved such that resource allocation indicates the range of consecutive VRBs via RIV, which may span one or more DL subbands, and some of these may fall into UL subbands or guard bands. When such allocation is received, such VRBs falling into UL subbands or guard bands should be considered invalid by the UE and not used for PDSCH data mapping. Some embodiments require that Rel-19 or later UEs have been provided with SBFD subband configuration so that it understands which VRBs in the resource allocation are invalid.

[0051] For UEs of version 19 and later, DL resource allocation type 1 is improved so that resource allocation indicates the range of consecutive VRBs via RIV, which can span one or more DL subbands. Upon receiving this indication, the UE can map VRBs to PRBs starting from the VRB indicated by the RIV. If there are more consecutive VRBs than can be contained in the first DL subband, the UE knows that the remaining VRBs are mapped to the second subband and applies a block shift equal to the size of the UL subband and guard band to the number of VRBs. Some embodiments require that the Rel-19 UE has been provided with SBFD subband configuration so that it understands what shift to apply and from which VRB.

[0052] In some embodiments, UE versions 19 and later can support one or a combination of the methods described above, in which case the gNB explicitly indicates to the UE a variant of resource allocation type 1 to be applied.

[0053] When interleaving VRB to PRB mapping is enabled, the following options may apply interleaving to SBFD: Option 1: Interleaved VRB to PRB mapping is not applicable to SBFD. Only non-interleaved mappings can be considered.

[0054] Option 2: The VRB to PRB interleaving mapping rules defined in Rel.15 of TS38.211 are applied to VRBs belonging to each specific DL subband, each subband having a specific starting RB and size.

[0055] Option 3: A two-step VRB-PRB mapping with interleaving is applied to the VRBs in the DL subband. The VRB-PRB mapping rules for interleaving, defined in version 15 of TS38.211, are applied to the DL resources in the DL subband. Subsequently, block-by-block shifting is applied to match the configuration of the SBFD carrier with respect to the DL and UL subbands and guard band configurations.

[0056] Option 4: A one-step VRB-PRB mapping with interleaving is applied to the entire DL BWP. The VRB-PRB mapping rules for interleaving, defined in Rel.15 of TS38.211, apply to the entire band of the BWP. VRBs mapped to PRBs belonging to UL subbands or guard bands are shielded.

[0057] Specific embodiments can be broadly described as follows.

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

[0059] In a particular embodiment, determining the VRB to PRB mapping includes determining the VRB to PRB mapping, wherein VRBs that are not mapped to one or more subbands for transmission / reception in the first direction are considered invalid and are not used for resource mapping.

[0060] In a particular embodiment, when determining the VRB-to-PRB mapping, interleaving is performed, wherein VRBs not mapped to one or more subbands for transmission / reception in the first direction are considered invalid and are not used for resource mapping.

[0061] In a particular embodiment, determining the VRB to PRB mapping includes determining the VRB to PRB mapping, wherein VRBs that are not mapped to a first subband for transmission / reception in a first direction are shifted to be mapped to a second subband for transmission / reception in a first direction.

[0062] In a particular embodiment, interleaving is performed when the VRB-PRB mapping is determined, and interleaving is performed on the bandwidth including the sum of all subbands used for transmission / reception in the first direction.

[0063] In a particular embodiment, when determining the VRB-PRB mapping, interleaving is performed, wherein the interleaving mode ensures that the mapped PRB is within a subband for transmission / reception in the first direction.

[0064] In a particular embodiment, the first direction includes a downlink, the second direction includes an uplink, and performing transmission / reception in the first direction using the mapped PRB includes performing downlink reception in the PDSCH using the mapped PRB.

[0065] In a particular embodiment, frequency domain resource allocation includes a downlink type 1 resource allocation scheme or a downlink type 0 resource allocation scheme.

[0066] In a particular embodiment, the first direction includes an uplink, the second direction includes a downlink, and performing transmission / reception in the first direction using the mapped PRB includes performing uplink transmission in the PUSCH using the mapped PRB.

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

[0068] A computer program product is also disclosed, comprising a non-transitory computer-readable medium storing computer-readable program code that, when executed by processing circuitry, is operable to perform any method performed by the aforementioned wireless device.

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

[0070] In a particular embodiment, determining the VRB to PRB mapping includes determining the VRB to PRB mapping, wherein VRBs that are not mapped to one or more subbands for transmission / reception in the first direction are considered invalid and are not used for resource mapping.

[0071] In a particular embodiment, when determining the VRB-to-PRB mapping, interleaving is performed, wherein VRBs not mapped to one or more subbands for transmission / reception in the first direction are considered invalid and are not used for resource mapping.

[0072] In a particular embodiment, determining the VRB to PRB mapping includes determining the VRB to PRB mapping, wherein VRBs that are not mapped to a first subband for transmission / reception in a first direction are shifted to be mapped to a second subband for transmission / reception in a first direction.

[0073] In a particular embodiment, interleaving is performed when the VRB-PRB mapping is determined, and interleaving is performed on the bandwidth including the sum of all subbands used for transmission / reception in the first direction.

[0074] In a particular embodiment, when determining the mapping from a downlink VRB to a PRB, interleaving is performed, wherein the interleaving mode ensures that the mapped PRB is within a subband for transmission / reception in the first direction.

[0075] In a particular embodiment, the first direction includes a downlink, the second direction includes an uplink, and performing transmission / reception in the first direction using the mapped PRB includes performing downlink transmission in the PDSCH using the mapped PRB. In a particular embodiment, the frequency domain resource allocation scheme includes a downlink type 1 resource allocation scheme or a downlink type 0 resource allocation scheme.

[0076] In a particular embodiment, the first direction includes an uplink, the second direction includes a downlink, and performing transmission / reception in the first direction using the mapped PRB includes performing uplink reception in the PUSCH using the mapped PRB.

[0077] In a particular embodiment, the method further includes transmitting to the wireless device an indication of which variant of the VRB-to-PRB mapping is used when mapping the VRB to the PRB.

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

[0079] Another type of computer program product includes a non-transitory computer-readable medium storing computer-readable program code that, when executed by processing circuitry, is operable to perform any method performed by the aforementioned network node.

[0080] Certain embodiments may provide one or more of the following technical advantages. For example, a particular embodiment includes enhancements to frequency domain resource allocation for the SBFD. The bit optimization of uplink (UL) subband frequency reuse in the DCI, the full flexibility of resource allocation for UEs across multiple subbands, and feasible interleaving aspects create new requirements at the resource allocation level. Specifically, the particular embodiment helps to 1) optimize resource allocation types 0 and 1 to reduce the number of bits dedicated to frequency domain resource allocation in the DCI; 2) enhance resource allocation type 1 to enable flexible allocation of UEs across multiple subbands; and 3) enhance VRB-to-PRB mapping when interleaving is enabled, enabling mapping with respect to SBFD configuration and within the constraints of available DL resources.

[0081] The focus of this particular embodiment is on DL frequency resource allocation, with particular emphasis on SBFD carrier configuration DUD (even if other configurations are not excluded). However, the examples and embodiments related to points 1 and 2 can be extended to UL cases for carrier configurations such as UDU. The proposed enhancements are transparent to UEs of version 18, while for UEs of version 19 and later, specific implementations require SBFD configuration for the UE in terms of DL subband, UL subband, and guard band. Attached Figure Description

[0082] To gain a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description in conjunction with the accompanying drawings, wherein: Figure 1 The time slot with 14 OFDM symbols is shown; Figure 2 Different types of duplex communication modes are shown. (a) Frequency Division Duplex (FDD), (b) Time Division Duplex (TDD), (c) Subband Full Duplex (SBFD), and (d) In-Band Full Duplex (IBFD); Figure 3 A comparison of TDD operations is shown: (a) static TDD in channels 1 and 2, and (b) static TDD in channel 2 and dynamic TDD in channel 1. Figure 4 The TDD operation options and interference scenarios are shown; Figure 5 An improved example of non-contiguous type 1 resource allocation (option 2) is shown; Figure 6An improved example of non-contiguous type 1 resource allocation (option 3) is shown; Figure 7 An example of virtual resource block (VRB) - physical resource block (PRB) mapping independent of each downlink subband is shown (Option 2); Figure 8 An example of VRB to PRB mapping for a combination of two downlink subbands is shown (Option 3); Figure 9 An example of VRB to PRB mapping is shown throughout the entire downlink bandwidth portion (BWP) (Option 4); Figure 10 An example communication system according to certain embodiments is shown; Figure 11 An example user equipment (UE) according to certain embodiments is shown; Figure 12 An example network node according to some embodiments is shown; Figure 13 A method performed by a wireless device according to certain embodiments is shown; and Figure 14 A method performed by a network node according to certain embodiments is shown. Detailed Implementation

[0083] As described above, there are currently certain challenges in frequency domain resource allocation for Subband Frequency Division (SBFD). Certain aspects of this disclosure and its embodiments can provide solutions to these or other challenges. For example, the specific embodiments described herein have three objectives: 1) to define options for enhancing downlink (DL) resource allocation types 0 and 1 such that the frequency domain resource allocation field in the scheduling DCI is optimized for user equipment (UE) versions 19 and higher; 2) to define options for enhancing DL resource allocation type 1 such that, for interleaved and non-interleaved virtual resource block (VRB) to PRB mapping, frequency domain resources (i.e., physical resource blocks (PRBs)) across multiple subbands can be allocated to UEs of version 19 and higher in SBFD operations; 3) to define enhanced options for interleaved VRB to PRB mapping in SBFD operations to ensure that the indicated VRB is mapped to a PRB in the DL subband. The enhancements can be transparent to UEs of version 18 and older.

[0084] Specific embodiments are described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as limiting itself to 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. Throughout the description of the embodiments described herein, it is assumed that the UE in SBFD operation has received SBFD configuration from dedicated or public signaling from its serving gNB, which indicates to the UE that the carrier is configured with DL subbands, UL subbands, and guard bands, as well as the position and size of each subband in the carrier, typically in DUD mode, but other SBFD modes are not excluded.

[0085] Although the embodiments presented herein focus primarily on DL resource allocation in DUD SBFD mode, it is straightforward for those skilled in the art to apply similar methods to UL resource allocation in other SBFD modes (e.g., UDU).

[0086] Specific embodiments include enhancements to resource block allocation for DL ​​resource allocation type 0. For DL ​​resource allocation type 0, resource block allocation includes a bitmap indicating resource block groups (RBGs) allocated to the scheduled UE, where an RBG is a contiguous set of virtual resource blocks (VRBs). In SBFD operation, not all VRBs defined in the downlink bandwidth portion can be allocated for DL ​​transmission, as some VRBs are associated with UL subbands and guard bands. Therefore, the current resource block allocation mechanism for DL ​​resource allocation type 0 can be enhanced for UEs of version 19 and later, optimizing the number of bits in the DCI used to indicate frequency domain resource allocation.

[0087] Option 1: In a variant of the embodiment, according to the rules specified in Rel-15, the size of the RBG allocation bitmap NRBG is given by the size of the downlink bandwidth portion (DL BWP) in the VRB and the number of VRBs for each RBG, such that all RBGs in the DL BWP are addressable, including RBGs that fall entirely within the UL subband and guard band according to the SBFD configuration. This option is transparent to UEs of version 18 because the BS will not simply allocate RBGs in invalid locations in the bitmap. In this case, the VRB-to-PRB mapping rules specified in Rel-15 (non-interleaved mapping) can be reused. More specifically, the allocated VRBs... n To the corresponding PRB n The mapping is based on the following rules: Option 2: In another variation of the embodiment, N RBGThis refers to the number of RBGs in the DL subband within the downlink bandwidth portion, excluding RBGs that fall entirely within the UL subband and guard band configured according to SBFD. To generate the bitmap, the rules defined in 38.214 can be applied individually to each DL subband to define the RBGs. Depending on the position of the DL subband relative to the Carrier Resource Block (CRB) grid and whether some RBGs partially overlap with the guard band or UL subband, the sizes of the first and last RBGs in each subband can be smaller than the maximum size of RBG(P). During SBFD operation, the UE can identify the VRBs allocated in DL subband j based on the previously received SBFD configuration using the following rules. n To the corresponding PRB in the corresponding DL subband n Mapping: ,in and These are the first VRB and the first PRB in DL subband j, respectively, which can be exported from the SBFD configuration: , ,in and These are the last VRB and last PRB 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 portion; G is the number of PRBs between DL subband j-1 and j, including the number of PRBs in the guard band (one or more) of the UL subband and between the two DL subbands. For DUD SBFD configuration ,in It is the size of a protective strip in RB, and It is the size of the UL subband in RB of BWP i. For example, suppose the downlink bandwidth portion comprises 272 RBs, with 216 allocated to 2 DL subbands, 48 ​​to the UL subband, and 8 to the guard band, following a DUD SBFD configuration: 108-4-48-4-108 (in RBs). In this example, It is 0. It is 107. It is 108. It is 215. It is 0. It is 107. It is 164 and It is 271.

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

[0089] Some implementations include enhancements to 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: Option 1: For UE version 18 and older, if DL resource allocation type 1 is configured, resource allocation across multiple DL subbands is not supported.

[0090] Option 2: For DL ​​resource allocation type 1, the resource allocation indicates the range of consecutive VRBs via RIV, which can span one or more DL subbands, and some of them can fall into the UL subband or guard band. For UEs of version 19 and later, if an SBFD subband configuration was previously provided, it is understood that VRBs falling into the UL subband or guard band will be considered invalid and not used for PDSCH data mapping.

[0091] For example, suppose a DL BWP comprises 272 RBs, with 216 allocated to 2 DL subbands, 48 ​​to UL subbands, and 8 to the guard band, following a DUD SBFD configuration: 108-4-48-4-108 (in the RBs). In this example, assume resource allocation type 1 is configured, and the RIV indicates a set of consecutive non-interleaved VRBs with a starting VRB 0 and a length of 192 VRB within a DL BWP of size 272 VRB (in this option, the DL BWP size and VRB space include both the UL subband and the guard band). Upon receiving the RIV and knowing the SBFD configuration, the UE can deduce that the PDSCH is mapped to PRBs 0, ..., 107, 164, ..., 191. According to the SBFD configuration, VRBs from 108 to 163 belong to the UL subband and the guard band, and are therefore considered invalid.

[0092] Figure 5 An improved example of non-contiguous type 1 resource allocation (option 2) is shown.

[0093] Option 3: DL resource allocation type 1 can be improved so that resource allocation indicates the range of consecutive VRBs via RIV, which can span one or more DL subbands. Upon receiving this indication, a UE of version 19 or later can map VRBs to PRBs starting from the indicated VRB. If there are more adjacent VRBs than can be contained in the first DL subband, then if an SBFD subband configuration was previously provided, the UE knows that the remaining VRBs are mapped to the next DL subband and applies a block shift equal in size to the UL subband and guard band between the DL subbands. That is, for VRBs in DL subband 1, the mapping is... For VRB in DL subband 2, the mapping is as follows: ,in , It is the size of a guard band in RB, and It is the size of the UL sub-band in RB.

[0094] Assuming the same DL BWP and SBFD configurations as in the previous example, in this option, the RIV rules can be modified so that the DL BWP size is the size of the DL subband, equivalent to 216 VRBs (in this option, the DL BWP size and VRB space do not include the UL subband and guard band). Assuming resource allocation type 1 is configured, and the RIV indicates a set of consecutive non-interleaved VRBs with a starting VRB of 0 and a length of 136 VRBs, upon receiving this RIV and knowing the SBFD configuration, the UE can deduce that the PDSCH is mapped to PRBs 0, ..., 107 in the first DL subband, and because 136 > 108, the UE applies a block shift of 56 (the size of the UL subband and guard band), and in the second DL subband, the allocated PRBs are 164, ..., 191.

[0095] Figure 6 An improved example of non-contiguous type 1 resource allocation (option 3) is shown.

[0096] In another enhanced variant, those skilled in the art can apply this method to situations where the DCI size of DCI format 1_0 in the UE-specific search space (USS) is derived from the size of DCI format 1_0 in the common search space (CSS), but is applied to an active BWP that has a corresponding starting resource block. resource indicator value Size and resource blocks allocated according to virtual contiguous allocation The length, where if the community is configured with Then by The size is given, or if no configuration is provided for the cell. The value is given by the initial DL BWP size.

[0097] Some embodiments include enhancements to interleaved VRB-PRB mapping for DL ​​resource allocation type 1. When interleaved VRB-PRB mapping is enabled, for resource allocation type 1, one of the following options can be considered to enhance VRB-PRB mapping for SBFD operations: Option 1: Apply non-interlaced mapping. In this case, options 1, 2, and above can be used repeatedly.

[0098] Option 2: Based on the SBFD carrier configuration (DUD, DU, or UD), and considering the specific start position of each subband, modify the VRB interleaving to operate individually on each DL subband. In this option, the Rel.15 formula is then applied to the individual subbands as follows: - Let the total number of Rb in BWP (bandwidth portion) i and subband j be... - Let the starting PRB positions within BWPi and subband j be... - set up The RB bundle size of BWP i is specified by the RRC configuration.

[0099] - The total number of RB bundles in each subband is The size of resource block bundle 0 in subband j is Resource block.

[0100] o Last Resource Block Bundle (RBB) The size is resource block, if ,otherwise .

[0101] o All other RB packages are by composition.

[0102] - The starting position of the interleaved DL subband relative to the BWP The initial RB definition is as follows: o If DU, then o If DUD: Option A: ,and in It is the size of each protective band in RB.

[0103] Option B: and o If UD, - Interval The virtual resource blocks in the system are mapped to physical resource blocks according to the rules in TS 38.211.

[0104] Using this VRB to PRB mapping option, 1) resources can only be allocated in one subband; 2) if option A is considered for the start position of the subband, for version 19 UE, if improved type 1 resource allocation is considered, the embodiment can allocate resources across different subbands, following option 3b above; and 3) if option B is considered for the start position of the subband, for version 19 UE, if improved type 1 resource allocation is considered, the embodiment can allocate resources across different subbands, following option 3b above.

[0105] Figure 7 An example of VRB to PRB mapping independent of each DL subband is shown (Option 2).

[0106] Option 3: Modify VRB interleaving to operate on the complete set of DL resources (the sum of resources in different DL subbands) independently of the carrier configuration, and then apply block-by-block shift. In this option, Rel.15 formula is applied to the bandwidth of all DL subband resource sizes. For this, a two-step approach can be considered, where: 1- Let the total amount of Rb allocated to DL within BWP (bandwidth portion) i be... In the case of two DL subbands, 2- Let the starting PRB position within BWPi be... 3- Let It is the bundle size of BWP i as defined by RRC. The total number of RB bundles in 4-BWP ​​i is a. Resource block bundle 0 size is Resource block.

[0107] b. Last Resource Block Bundle (RBB) The size is resource block, if Otherwise Resource block.

[0108] c. All other resource block bundles are made by Resource block composition.

[0109] 5- Finally, a block-by-block shift G is applied to achieve the final PRB mapping, and this depends on the SBFD carrier configuration: a. If DU, b. If DUD, {0, 1, 2, ..., A-1, A, A+1, ..., Nbundle-1} --> {0, 1, 2, ..., A-1, A+G, A+G+1, ..., Nbundle-1}, where G is the size of DUD, then DUD is the size of DUD. ,in This is the size of each guard band in RB. In this case, the number of bundles in each sub-band must be derived so that the dimensions of the two sub-bands are equal. For example, if If it is even, then the second sub-band follows the bundle. Begin. Otherwise, if If it is non-uniform, the central bundle must be split into two bundles, where RB is less than 1 / 2. .

[0110] c. If UD, {0, 1, 2, ..., A-1, A, A+1, ..., Nbundle-1} --> {G, 1+G, 2+G, ..., A-1+G, A+G+1, ..., Nbundle-1}, where G is the size of UD. ,in It refers to the size of the protective band in RB.

[0111] According to option 3c above, this option allows resources to be allocated to UEs of version 19 across different DL subbands, if improved type 1 resource allocation is taken into consideration.

[0112] Figure 8 An example of VRB to PRB mapping for a 2 DL subband combination is shown (Option 3).

[0113] Option 4: Modify VRB interleaving to operate on the full BWP by masking PRBs mapped to the UL subband and guard band. In this option, as in non-SBFD scenarios, the VRB-to-PRB mapping is applied to the full BWP bandwidth, meaning interleaving is also applied to the RBBs that will be mapped to the UL subband and guard band. UEs previously configured with SBFD can recognize PRBs in the UL subband and guard band as invalid and mask the corresponding VRBs.

[0114] Using this option, resources can be allocated to a version 19 UE across different DL subbands using one of the following options: In a variant of this embodiment, the starting VRB number (RB) indicated by the RIV. start ) and contiguously allocated resource blocks (L RB The length of the data includes invalid VRBs. The UE should assume that invalid VRBs are not used for PDSCH data mapping (this is equivalent to enhanced type 1 resource allocation, following option 3b above).

[0115] In another variation of this embodiment, the initial VRB number (RB) is indicated by the RIV. start ) and the length of contiguously allocated resource blocks (L RB This excludes invalid VRBs. The latter variant offers the benefit of a reduced resource allocation field size in the scheduling DCI. (Following...) Figure 9 The example in the example, and assuming the BS wants to assign the first 8 useful VRBs in the DL BWP to a certain UE, establishes a first variant of this embodiment considering RB. start =0 and L RB =12 RIV; the second variant considers an optimized RIV, RB start =0, and L RB =8.

[0116] Figure 9 An example of VRB to PRB mapping is shown throughout the entire DL BWP (Option 4).

[0117] Figure 10 An example of a communication system 100 according to some embodiments is shown. In this example, the communication system 100 includes a telecommunications network 102, which 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 are generally referred to as network node 110), or any other similar 3GPP access node or non-3GPP access point. Network node 110 facilitates direct or indirect connections of user equipment (UE), such as connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be collectively referred to as UE 112) to the core network 106 via one or more wireless connections.

[0118] Examples of wireless communication via wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or other conductors. Furthermore, in various embodiments, communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals, whether via wired or wireless connections. Communication system 100 may include any type of communication, telecommunications, data, cellular, radio network, and / or other similar system and / or be connected to any type of communication, telecommunications, data, cellular, radio network, and / or other similar system via an interface.

[0119] UE 112 can be any communication device of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with network node 110 and other communication devices. Similarly, network node 110 is arranged, capable, configured, and / or operable to communicate directly or indirectly with UE 112 and / or with other network nodes or devices in telecommunication network 102 to enable and / or provide network access (such as wireless network access) and / or to perform other functions (such as management in telecommunication network 102).

[0120] In the depicted example, core network 106 connects network node 110 to one or more hosts (such as host 116). These connections may be direct or indirect, via one or more intermediate networks or devices. In other examples, network nodes may be directly coupled to hosts. Core network 106 includes one or more core network nodes (e.g., core network node 108) constructed from hardware and software components. The characteristics of these components may be substantially similar to those described with respect to UEs, network nodes, and / or hosts, such that the description generally applies to the corresponding components of core network node 108. Example core network nodes include functions of one or more of the following: 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 Dehiding Function (SIDF), Unified Data Management (UDM), Secure Edge Protection Agent (SEPP), Network Open Function (NEF), and / or User Plane Function (UPF).

[0121] Host 116 may be owned or controlled by a service provider other than the operator or provider of telecommunications network 102 and / or access network 104, and may be operated by or on behalf of the service provider. Host 116 may host various applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services (such as retrieving and compiling data on various environmental conditions detected by multiple UEs), analytics functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by the server.

[0122] on the whole, Figure 10The communication system 100 enables connectivity between the UE, network nodes, and hosts. In that sense, the communication system 500 can be configured to operate according to predefined rules or procedures, such as specific standards, including but 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 next-generation standard (e.g., 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as 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.

[0123] In some examples, telecommunications network 102 is a cellular network implementing 3GPP standardized features. Therefore, telecommunications network 102 can support network slicing to provide different logical networks to different devices connected to it. For example, telecommunications network 102 can 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 another UE.

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

[0125] In the example, hub 114 communicates with 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, hub 114 may be a controller, router, content source and analytics, or any other communication device described herein with respect to a UE. For example, hub 114 may be a broadband router for enabling access to core network 106 for a UE. As another example, hub 114 may be a controller that sends commands or instructions to one or more actuators in a UE. Commands or instructions may be received from the UE, network node 110, or may be received via executable code, scripts, procedures, or other instructions in hub 114. As another example, hub 114 may be a data collector that acts as a temporary storage device for UE data, and in some embodiments, hub 114 may perform data analytics or other processing. As another example, hub 114 may be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, hub 114 can retrieve VR assets, video, audio, or other media or data related to sensory information via a network node. Hub 114 then provides the VR assets, video, audio, or other media or data related to sensory information to the UE directly, after performing local processing, and / or after adding additional local content. In another example, hub 114 acts as a proxy server or coordinator for the UE, particularly if one or more of the UEs are low-power IoT devices.

[0126] Hub 114 may have a constant / persistent or intermittent connection to network node 110b. Hub 114 may also accommodate different communication schemes and / or scheduling between hub 114 and UEs (e.g., UEs 112c and / or 112d) and between hub 114 and core network 106. In other examples, hub 114 is connected to core network 106 and / or one or more UEs via a wired connection. Furthermore, hub 114 may be configured to connect to an M2M service provider via access network 104 and / or to another UE via a direct connection. In some scenarios, a UE can establish a wireless connection to network node 110 while still being connected via hub 114 through a wired or wireless connection. In some embodiments, hub 114 may be a dedicated hub—that is, a hub whose primary function is to route communication from network node 110b to UE / to network node 110b. In other embodiments, hub 114 may be a non-dedicated hub—that is, a device capable of operating to route communication between the UE and network node 110b, but also capable of operating as a communication start and / or end point for certain data channels.

[0127] Figure 11 A UE 200 according to some embodiments is illustrated. As used herein, a UE refers to a device capable of, configured, arranged, and / or operable to wirelessly communicate with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicles, mounted or vehicle-embedded / integrated wireless devices, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including Narrowband Internet of Things (NB-IoT) UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs.

[0128] The UE can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidechain communication, dedicated short-range communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, the UE may not necessarily be a user in the sense of a human user owning and / or operating the associated device. Instead, the UE may represent a device intended for sale to or operated by a human user but which may not or can not initially be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, the UE may represent a device not intended for sale to or operated by an end user but which may be associated with or operated for the benefit of a user (e.g., a smart meter).

[0129] UE 200 includes processing circuitry 202, which is operatively coupled via bus 204 to input / output interface 206, power supply 208, memory 210, communication interface 212, and / or any other component, or any combination thereof. Some UEs may utilize... Figure 11 All or a subset of the components shown. The level of integration between components can vary from one UE to another. Furthermore, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0130] Processing circuitry 202 is configured to process instructions and data and can be configured to implement any sequential state machine that operates to execute instructions stored in memory 210 as a machine-readable computer program. Processing circuitry 202 can 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 along with appropriate firmware; one or more stored computer programs, a general-purpose processor such as a microprocessor or digital signal processor (DSP), along with appropriate software; or any combination of the above. For example, processing circuitry 202 may include multiple central processing units (CPUs).

[0131] In the example, input / output interface 206 can be configured to provide interfaces or multiple interfaces to input devices, output devices, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, other output devices, or any combination thereof. Input devices can allow users to capture information into UE 200. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital camcorders, webcams, etc.), microphones, sensors, mice, trackballs, orientation pads, trackpads, scroll wheels, smart cards, etc. Presence-sensitive displays may include capacitive or resistive touch sensors to sense input from the user. Sensors may be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, light sensors, proximity sensors, biosensors, etc., or any combination thereof. Output devices can use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port can be used to provide input and output devices.

[0132] In some embodiments, power supply 208 is configured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a storage battery, may be used. Power supply 208 may also include power supply circuitry for delivering power from power supply 208 itself and / or an external power source to various parts of UE 200 via an interface or input circuitry such as a power cable. The delivery of power may, for example, be used for charging power supply 208. The power supply circuitry may perform any formatting, conversion, or other modifications on the power from power supply 208 to suit the power for the respective components of the UE 200 being powered.

[0133] 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), disk, optical disk, hard disk, removable cassette tape, flash drive, etc. In one example, memory 210 includes one or more applications 214 (such as an operating system, web browser application, widget, gadget engine, or other application) and corresponding data 216. Memory 210 can store any of a wide variety of different operating systems for use by UE 200, or a combination of operating systems.

[0134] Memory 210 can be configured to include multiple physical drive units such as a redundant array of independent disks (RAID), flash memory, USB flash drive, external hard drive, thumb drive, pen drive, key drive, high-density digital universal disc (HD-DVD) optical disc drive, internal hard drive, Blu-ray 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, smart card memory such as a tamper-proof module in the form of a universal integrated circuit card (UICC) (including one or more subscriber identity modules (SIMs), such as USIM and / or ISIM), other memory, or any combination thereof. The UICC can be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a "SIM card". Memory 210 can allow UE 200 to access instructions, applications, etc., stored on transient or non-transient memory media to offload or upload data. Articles such as those utilizing communication systems may be tangibly embodied in or contained in memory 210, which may be or include a device-readable storage medium.

[0135] Processing circuitry 202 can be configured to communicate with an access network or other network using communication interface 212. Communication interface 212 may include one or more communication subsystems and may include or be communicatively coupled to antenna 222. Communication interface 212 may include one or more transceivers for communication, such as through communication with one or more remote transceivers of another device capable of wireless communication (e.g., a network node in the access network or another UE). Each transceiver may include a transmitter 218 and / or a receiver 220 adapted to provide network communication (e.g., optical, electrical, frequency allocation, etc.). Furthermore, transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuitry, software, or firmware, or alternatively, transmitter 218 and receiver 220 may be implemented separately.

[0136] In the illustrated embodiment, the communication functions of the communication interface 212 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth and near-field communication, location-based communication such as using a global positioning system (GPS) to determine location, another similar communication function, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards such as IEEE 802.11, Code Division Multiple 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), etc.

[0137] Regardless of the type of sensor, the UE can provide the output of data captured by its sensors via its communication interface 212 or via a wireless connection to a network node. Data captured by the UE's sensors can be transmitted via another UE via a wireless connection to a network node. The output can be periodic (e.g., every 15 minutes if it reports the sensed temperature), random (e.g., to balance the load of reports from several sensors), responsive to a triggered event (e.g., sending an alarm when humidity is detected), responsive to a request (e.g., a user-initiated request), or a continuous stream (e.g., live video feed of a patient).

[0138] As another example, the UE includes actuators, motors, or switches associated with a communication interface configured to receive wireless input from a network node via a wireless connection. The state of the actuator, motor, or switch can change in response to the received wireless input. For example, the UE may include motors for adjusting control surfaces or rotors of a drone in flight based on received input, or for controlling a robotic arm performing a medical procedure based on received input.

[0139] When a UE takes the form of an Internet of Things (IoT) device, it can be a device intended for use in one or more application domains, including but not limited to urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices include or are embedded in the following: connected refrigerators or freezers, TVs, connected lighting devices, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electric door locks, connected doorbells, heat pump-like air conditioning systems, autonomous vehicles, monitoring systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearable devices for haptic or sensory enhancement, sprinklers, animal or object tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical device such as heart rate monitors or remotely controlled surgical robots. (Except as per the above...) Figure 11 In addition to the other components described in UE 200 shown, UEs in the form of IoT devices include circuitry and / or software that depend on the intended application of the IoT device.

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

[0141] In practice, any number of UEs can be used together for a single use case. For example, the first UE can be an unmanned aerial vehicle (UAV) or can be integrated into the UAV and provide the UAV's speed information (obtained via a speed sensor) to a second UE, which acts as a remote controller for operating the UAV. When a user makes a change from the remote controller, the first UE can adjust a throttle valve on the UAV (e.g., by controlling an actuator) to increase or decrease the UAV's speed. The first and / or second UEs can also include more than one of the functions described above. For example, the UE can include sensors and actuators and handle communication of data from both the speed sensor and the actuator.

[0142] Figure 12 A network node 300 according to some embodiments is illustrated. As used herein, a network node refers to a device that is capable of, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points) and base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR Node Bs (gNBs)).

[0143] Base stations can be classified based on the coverage they provide (or, in other words, their transmission power levels), and therefore, depending on the coverage provided, a base station can be referred to as a femtobase, picobase, microbase, or macrobase. A base station can be a relay node or a relay donor node controlling a relay. Network nodes can also include one or more (or all) portions of a distributed radio base station such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio headend (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio device. A portion of a distributed radio base station can also be referred to as a node in a distributed antenna system (DAS).

[0144] Other examples of network nodes include multi-transmission point (multi-TRP) 5G access nodes, MSR devices such as multi-standard radio (MSR) BS, network controllers such as radio network controller (RNC) or base station controller (BSC), base transceiver station (BTS), transmission point, transmission node, multi-cell / multicast coordination entity (MCE), operation and maintenance (O&M) node, operation support system (OSS) node, self-organizing network (SON) node, location node (e.g., evolved servicing mobile location center (E-SMLC)), and / or minimized drive test (MDT).

[0145] Network node 300 includes processing circuitry 302, memory 304, communication interface 306, and power supply 308. Network node 300 may consist of multiple physically separate components (e.g., node B components and RNC components, or BTS components and BSC components, etc.), each of which may have its own corresponding components. In some scenarios where network node 300 includes multiple separate components (e.g., BTS and BSC components), one or more of these separate components may be shared among several network nodes. For example, a single RNC can control multiple node Bs. In such scenarios, each unique node B and RNC pair may be considered a single, independent network node in some instances. In some embodiments, 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., the same antenna 310 may be shared by different RATs). Network node 300 may also include a collection of various described components for integrating into network node 300 different wireless technologies, such as 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 chips or chipsets and other components within network node 300.

[0146] The processing circuitry 302 may include: 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 coding logic operable to provide network node 300 functionality, either alone or in combination with other network node 300 components such as memory 304.

[0147] 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 a radio frequency (RF) transceiver circuitry 312 and a baseband processing circuitry 314. In some embodiments, the RF transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or chipsets), boards, or units such as radio units and digital units. In alternative embodiments, some or all of the RF transceiver circuitry 312 and the baseband processing circuitry 314 may be on the same chip or chipset, board, or unit.

[0148] Memory 304 may include any form of volatile or non-volatile computer-readable memory, including, but not limited to, permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disks), removable storage media (e.g., flash drives, CDs, or DVDs), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory that stores information, data, and / or instructions that can be used by processing circuitry 702. Memory 304 may store any suitable instructions, data, or information, including applications, software, computer programs, and / or other instructions that contain logic, rules, codes, tables, or one or more of these and can be executed by processing circuitry 302 and utilized by network node 700. Memory 304 may be used to store any calculations performed by processing circuitry 702 and / or any data received via communication interface 306. In some embodiments, processing circuitry 302 and memory 304 are integrated.

[0149] Communication interface 306 is used in wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As illustrated, communication interface 306 includes one or more ports / terminals 316 for transmitting data to and receiving data from the network, for example, via a wired connection. Communication interface 306 also includes radio front-end circuitry 318 that may be coupled to antenna 310 or, in some embodiments, is part of antenna 310. Radio front-end circuitry 318 includes filter 320 and amplifier 322. Radio front-end circuitry 318 may be connected to antenna 310 and processing circuitry 302. Radio front-end circuitry may be configured to modulate the signal transmitted between antenna 310 and processing circuitry 302. Radio front-end circuitry 318 may receive digital data to be transmitted to other network nodes or UEs via a wireless connection. Radio front-end circuitry 318 may use a combination of filter 320 and / or amplifier 322 to convert digital data into radio signals with appropriate channel and bandwidth parameters. The radio signals may then be transmitted via antenna 310. Similarly, when receiving data, antenna 310 can collect radio signals and then convert them into digital data via radio front-end circuitry 318. The digital data can then be passed to processing circuitry 302. In other embodiments, the communication interface may include different components and / or different combinations of components.

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

[0151] Antenna 310 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 310 may be coupled to radio front-end circuitry 318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 310 is decoupled from network node 300 and may be connected to network node 300 via an interface or port.

[0152] Antenna 310, communication interface 306, and / or processing circuitry 302 can be configured to perform any receive operation and / or certain acquire operation described herein as being performed by a network node. Any information, data, and / or signals can be received from the UE, another network node, and / or any other network device. Similarly, antenna 310, communication interface 306, and / or processing circuitry 302 can be configured to perform any transmit operation described herein as being performed by a network node. Any information, data, and / or signals can be transmitted to the UE, another network node, and / or any other network device.

[0153] Power supply 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). Power supply 308 may also include or be coupled to power management circuitry to power the components of network node 300 for performing the functionality described herein. For example, network node 300 may be connectable to an external power source (e.g., mains or electrical outlet) via input circuitry or interface such as a cable, thereby supplying power to the power circuitry of power supply 308. As another example, power supply 708 may include a power source in the form of a battery or battery pack, connected to or integrated into the power circuitry. The battery can provide backup power in the event of an external power failure.

[0154] Embodiments of network node 300 may include, except Figure 12Additional components beyond those shown herein are used to provide certain aspects of the functionality of the network node, including any of the functions described herein and / or any functions necessary to support the topics described herein. For example, network node 300 may include user interface devices for allowing information to be input to and output from network node 300. This allows users to perform diagnostic, maintenance, repair, and other management functions for network node 300.

[0155] Figure 13 This is a flowchart illustrating example methods in a wireless device according to certain embodiments. In a particular embodiment, Figure 13 One or more steps can be referenced Figure 11 The UE 200 described is used for execution.

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

[0157] For SBFD operation, a portion of a wideband carrier, called a subband, can be used for communication directions different from the rest of the carrier. Accordingly, different non-overlapping subbands are used for the downlink and uplink. SBFD configurations can include any SBFD configuration described with respect to the embodiments and examples described herein (e.g., DUD, UDU, etc.).

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

[0159] For example, a network node notifies a radio device of downlink frequency domain resources for receiving PDSCH via DCI. This configuration may include, for example, type 0 or type 1 configurations.

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

[0161] At step 1316, the wireless device determines the VRB-PRB mapping based on frequency domain resource allocation and SBFD configuration. The mapped PRB is within the subband used for transmission / reception in the first direction.

[0162] For example, if the first direction is downlink, the mapped PRB is within the downlink subband, but not within the uplink subband or any guard subband. If the first direction is uplink, the mapped PRB is within the uplink subband, but not within the downlink subband or any guard subband.

[0163] This mapping can be performed in various different ways. Some embodiments include interleaving, while others do not.

[0164] In a particular embodiment, determining the VRB-to-PRB mapping includes determining a VRB-to-PRB mapping where VRBs not mapped to one or more subbands for transmission / reception in the first direction are considered invalid and not used for resource mapping. The above refers to the non-interleaved VRB-to-PRB mapping for DL ​​resource allocation type 1 and option 2, and... Figure 5 An example is described.

[0165] In a particular embodiment, when determining the VRB-to-PRB mapping, interleaving is performed, where VRBs not mapped to one or more subbands for transmission / reception in the first direction are considered invalid and not used for resource mapping. The above describes the interleaved VRB-to-PRB mapping for DL ​​resource allocation type 1 and option 4, and... Figure 9 An example is described.

[0166] In a particular embodiment, determining the VRB-to-PRB mapping includes determining a VRB-to-PRB mapping where VRBs not mapped to a first subband for transmission / reception in a first direction are shifted to be mapped to a second subband for transmission / reception in the first direction. The above refers to the non-interleaved VRB-to-PRB mapping for DL ​​resource allocation types 1 and option 3, and... Figure 6 An example is described. This example uses block shifting in the mapping to skip unused subbands. Another example was described above for VRB to PRB mapping for DL ​​resource allocation type 0 and option 2. In this example, shifting is part of the mapping rules.

[0167] In a particular embodiment, interleaving is performed when the VRB-to-PRB mapping is determined, and interleaving is performed on the bandwidth including the sum of all subbands used for transmission / reception in the first direction. The above refers to the interleaving of VRB-to-PRB mappings for DL ​​resource allocation types 1 and 3, and... Figure 8 An example is described.

[0168] In a particular embodiment, when determining the VRB-to-PRB mapping, interleaving is performed, wherein the interleaving mode ensures that the mapped PRB is within the subband used for transmission / reception in the first direction. The above refers to DL resource allocation type 1 and option 2, and... Figure 7 An example of interleaved VRB to PRB mapping is described.

[0169] Although a specific mapping is described for step 1316, the wireless device may perform the mapping according to any of the embodiments and examples described herein.

[0170] In a particular embodiment, the first direction includes a downlink, the second direction includes an uplink, and performing transmission / reception in the first direction using the mapped PRB includes performing downlink reception in the PDSCH using the mapped PRB.

[0171] In a particular embodiment, the first direction includes an uplink, the second direction includes a downlink, and performing transmission / reception in the first direction using the mapped PRB includes performing uplink transmission in the PUSCH using the mapped PRB.

[0172] At step 1318, the wireless device performs transmission / reception in the first direction using the mapped PRB. Transmission / reception is described in more detail with reference to the embodiments and examples described herein.

[0173] Can be Figure 13 Method 1300 can be modified, added to, or omitted. Furthermore, Figure 13 One or more steps in the method can be performed in parallel or in any suitable order.

[0174] Figure 14 This is a flowchart illustrating example methods in a network node according to certain embodiments. In a particular embodiment, Figure 14 One or more steps can be referenced Figure 12 The network node 300 described is used for execution.

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

[0176] At step 1412, the network node obtains the SBFD configuration of the wireless device. The SBFD configuration indicates one or more sub-bands of the frequency band used for transmission / reception in the first direction, and one or more sub-bands of the frequency band used for transmission / reception in the second direction. The SBFD configuration may include any SBFD configuration described with respect to the embodiments and examples described herein (e.g., DUD, UDU, etc.).

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

[0178] At step 1416, the network node determines the VRB-to-PRB mapping based on frequency domain resource allocation and SBFD configuration. The mapped PRB is within the subband used for transmission / reception in the first direction. The network node uses a reference... Figure 13 The mapping is determined in the same manner as described in step 1316 of the wireless device. In certain embodiments, network nodes may perform mapping according to any of the embodiments and examples described herein.

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

[0180] Can be Figure 14 Method 1400 can be modified, added to, or omitted. Furthermore, Figure 14 One or more steps in the method can be performed in parallel or in any suitable order.

[0181] The foregoing description sets forth many specific details. However, it is understood that embodiments can be implemented without these specific details. In other instances, well-known circuits, structures, and techniques have not been shown in detail so as not to obscure the understanding of this specification. Based on the included description, those skilled in the art will be able to implement appropriate functions without undue experimentation.

[0182] References to "an embodiment," "embodiment," "example embodiment," etc., in this specification indicate that the described embodiment may include specific features, structures, or characteristics, but each embodiment does not necessarily include those specific features, structures, or characteristics. Furthermore, these phrases do not necessarily refer to the same embodiment. Additionally, when a specific feature, structure, or characteristic is described in connection with an embodiment, it is believed that implementing such a feature, structure, or characteristic in conjunction with other embodiments is within the knowledge of those skilled in the art, whether explicitly described or not.

[0183] Although this disclosure has been described with reference to certain embodiments, variations and substitutions of the embodiments will be apparent to those skilled in the art. Therefore, the above description of the embodiments does not limit this disclosure. Other changes, substitutions, and modifications are possible without departing from the scope of this disclosure as defined by the following claims.

[0184] Some example implementations are described below.

[0185] Group A Examples 1. A method performed by a wireless device, the method comprising: - Any wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.

[0186] 2. The method according to the foregoing embodiments further includes one or more of the additional wireless device steps, features, or functions described above.

[0187] 3. The method according to any one of the foregoing two embodiments further includes: - Provide user data; and - User data is forwarded to the host via transmission to the base station.

[0188] Group B Implementation Examples 4. A method performed by a base station, the method comprising: - Any step, feature, or function described above regarding the base station, either alone or in combination with other steps, features, or functions described above.

[0189] 5. The method according to the foregoing embodiments further includes one or more additional base station steps, features, or functions as described above.

[0190] 6. The method according to any of the foregoing embodiments further includes: - Obtain user data; and - Forward user data to the host or wireless device.

[0191] Group C Implementation Examples 7. A mobile terminal, comprising: - The processing circuitry is configured to perform any step of any of the embodiments in group A; and - Power supply circuitry, configured to supply power to wireless devices.

[0192] 8. A base station, comprising: - The processing circuitry is configured to perform any step of any of the Group B embodiments; - Power supply circuitry, configured to supply power to wireless devices.

[0193] 9. A user equipment (UE), comprising: - Antenna, configured to transmit and receive wireless signals; - Radio front-end circuitry, connected to the antenna and processing circuitry, and configured to modulate the signal transmitted between the antenna and processing circuitry; - The processing circuitry is configured to perform any step of any of the Group A embodiments; - An input interface, connected to the processing circuitry, and configured to allow information to be input into the UE for processing by the processing circuitry; - An output interface, connected to the processing circuitry, and configured to output information from the UE that has already been processed by the processing circuitry; and - A battery, connected to the processing circuit, and configured to power the UE.

[0194] 10. A communication system including a host computer, comprising: - Processing circuitry, configured to provide user data; and - A communication interface configured to forward user data to the cellular network for transmission to the user equipment (UE). - Wherein, the cellular network includes a base station having a radio interface and processing circuitry, the processing circuitry of which is configured to perform any step of any of the Group B embodiments.

[0195] 11. The communication system according to the foregoing embodiments further includes a base station.

[0196] 12. The communication system according to the foregoing two embodiments further includes a UE, wherein the UE is configured to communicate with a base station.

Claims

1. A method performed by a wireless device, the method comprising: Obtain (1312) subband full-duplex SBFD configuration, the SBFD configuration indicating one or more subbands of the 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 (1314) frequency domain resource allocation from network node, the frequency domain resource allocation including resource allocation for transmission / reception in the first direction of the frequency band, the resource allocation indicating a continuous range of virtual resource blocks (VRBs) available for transmission / reception; Based on the frequency domain resource allocation and the SBFD configuration, a mapping (1316) from VRB to physical resource block PRB is determined, wherein the mapped PRB is within the subband used for transmission / reception in the first direction; and Transmission / reception in the first direction is performed using the mapped PRB (1318).

2. The method according to claim 1, wherein, Determining the VRB to PRB mapping includes determining the VRB to PRB mapping, wherein VRBs that are not mapped to one or more subbands for transmission / reception in the first direction are considered invalid and not used for resource mapping.

3. The method according to claim 2, wherein, When the mapping from VRB to PRB is determined, interleaving is performed, wherein VRBs that are not mapped to one or more subbands for transmission / reception in the first direction are considered invalid and are not used for resource mapping.

4. The method according to claim 1, wherein, Determining the VRB to PRB mapping includes determining the VRB to PRB mapping, wherein VRBs that are not mapped to a first subband of the one or more subbands for transmission / reception in the first direction are shifted to be mapped to a second subband of the one or more subbands for transmission / reception in the first direction.

5. The method according to claim 4, wherein, When the VRB to PRB mapping is determined, interleaving is performed, and the interleaving is performed on the bandwidth including the sum of all the subbands used for transmission / reception in the first direction.

6. The method according to claim 1, wherein, Interleaving is performed when the mapping from VRB to PRB is determined, wherein the interleaving mode ensures that the mapped PRB is within the subband for transmission / reception in the first direction.

7. The method according to any one of claims 1-6, wherein, The first direction includes a downlink, the second direction includes an uplink, and performing transmission / reception in the first direction using the mapped PRB includes performing downlink reception in the Physical Downlink Shared Channel (PDSCH) using the mapped PRB.

8. The method according to claim 7, wherein, The frequency domain resource allocation includes a downlink type 1 resource allocation scheme.

9. The method according to any one of claims 2 and 4, wherein, The frequency domain resource allocation includes a downlink type 0 resource allocation scheme.

10. The method according to any one of claims 1-6, wherein, The first direction includes an uplink, the second direction includes a downlink, and performing transmission / reception in the first direction using the mapped PRB includes performing uplink transmission in the Physical Uplink Shared Channel (PUSCH) using the mapped PRB.

11. A wireless device (200) including processing circuitry (202), said processing circuitry being operable to: Obtain a subband full-duplex SBFD configuration, the SBFD configuration indicating one or more subbands of the 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 frequency domain resource allocation from network node (300), the frequency domain resource allocation including resource allocation for transmission / reception in the first direction of the frequency band, the resource allocation indicating a continuous range of virtual resource blocks (VRBs) available for transmission / reception; Based on the frequency domain resource allocation and the SBFD configuration, a mapping from VRB to physical resource block (PRB) is determined, wherein the mapped PRB is within the subband used for transmission / reception in the first direction; and Transmission / reception in the first direction is performed using the mapped PRB.

12. The wireless device according to claim 11, wherein, The processing circuitry is configured to determine the VRB-PRB mapping by determining the VRB-PRB mapping, wherein VRBs not mapped to the one or more subbands used for transmission / reception in the first direction are considered invalid and not used for resource mapping.

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

14. The wireless device according to claim 11, wherein, The processing circuitry is operable to determine the VRB-PRB mapping by determining the VRB-PRB mapping, wherein VRBs not mapped to a first subband of the one or more subbands for transmission / reception in the first direction are shifted to be mapped to a second subband of the one or more subbands for transmission / reception in the first direction.

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

16. The wireless device according to claim 11, wherein, The processing circuitry is operable to perform interleaving when determining the mapping from the VRB to the PRB, wherein the interleaving mode ensures that the mapped PRB is within the subband for transmission / reception in the first direction.

17. The wireless device according to any one of claims 11-16, wherein, The first direction includes a downlink, the second direction includes an uplink, and the processing circuitry is operable to perform transmission / reception in the first direction using the mapped PRB by performing downlink reception in the Physical Downlink Shared Channel (PDSCH) using the mapped PRB.

18. The wireless device according to claim 17, wherein, The frequency domain resource allocation includes a downlink type 1 resource allocation scheme.

19. The wireless device according to any one of claims 12 and 14, wherein, The frequency domain resource allocation includes a downlink type 0 resource allocation scheme.

20. The wireless device according to any one of claims 11-16, wherein, The first direction includes an uplink, the second direction includes a downlink, and the processing circuitry is operable to perform transmission / reception in the first direction using the mapped PRB by performing uplink transmission in the Physical Uplink Shared Channel (PUSCH) using the mapped PRB.

21. A method performed by a network node, the method comprising: Obtain (1412) a subband full-duplex SBFD configuration for a wireless device, the SBFD configuration indicating one or more subbands of the 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; (1414) Frequency domain resource allocation is transmitted to the wireless device, the frequency domain resource allocation including resource allocation for transmission / reception in the first direction of the frequency band, the resource allocation indicating a continuous range of virtual resource blocks (VRBs) available for transmission / reception; Based on the frequency domain resource allocation and the SBFD configuration, a mapping (1416) of VRB to physical resource block PRB is determined, wherein the mapped PRB is within the subband used for transmission / reception in the first direction; and Transmission / reception in the first direction is performed using the mapped PRB (1418).

22. The method according to claim 21, wherein, Determining the VRB to PRB mapping includes determining the VRB to PRB mapping, wherein VRBs that are not mapped to one or more subbands for transmission / reception in the first direction are considered invalid and not used for resource mapping.

23. The method according to claim 22, wherein, When the mapping from VRB to PRB is determined, interleaving is performed, wherein VRBs that are not mapped to one or more subbands for transmission / reception in the first direction are considered invalid and are not used for resource mapping.

24. The method of claim 21, wherein determining the VRB-to-PRB mapping comprises determining the VRB-to-PRB mapping, wherein VRBs not mapped to a first subband of the one or more subbands for transmission / reception in the first direction are shifted to be mapped to a second subband of the one or more subbands for transmission / reception in the first direction.

25. The method according to claim 24, wherein, Interleaving is performed when the VRB to PRB mapping is determined, and the interleaving is performed on a bandwidth that includes the sum of all the subbands used for transmission / reception in the first direction.

26. The method according to claim 21, wherein, Interleaving is performed when the mapping from the downlink VRB to the PRB is determined, wherein the interleaving mode ensures that the mapped PRB is within the subband for transmission / reception in the first direction.

27. The method according to any one of claims 21-26, wherein, The first direction includes a downlink, the second direction includes an uplink, and performing transmission / reception in the first direction using the mapped PRB includes performing downlink transmission in the Physical Downlink Shared Channel (PDSCH) using the mapped PRB.

28. The method according to claim 27, wherein, The frequency domain resource allocation scheme includes a downlink type 1 resource allocation scheme.

29. The method according to any one of claims 22 and 24, wherein, The frequency domain resource allocation includes a downlink type 0 resource allocation scheme.

30. The method according to any one of claims 21-26, wherein, The first direction includes an uplink, the second direction includes a downlink, and performing transmission / reception in the first direction using the mapped PRB includes performing uplink reception in the Physical Uplink Shared Channel (PUSCH) using the mapped PRB.

31. The method according to any one of claims 21-30, further comprising transmitting (1410) to the wireless device an indication of which variant of the VRB-to-PRB mapping is used when mapping the VRB to the PRB.

32. A network node (300) including processing circuitry (302), said processing circuitry being operable to: Obtain a subband full-duplex SBFD configuration for a wireless device, the SBFD configuration indicating one or more subbands of the 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; A frequency domain resource allocation is transmitted to the wireless device, the frequency domain resource allocation including resource allocation for transmission / reception in the first direction of the frequency band, the resource allocation indicating a continuous range of Virtual Resource Blocks (VRBs) available for transmission / reception; Based on the frequency domain resource allocation and the SBFD configuration, a mapping from VRB to physical resource block (PRB) is determined, wherein the mapped PRB is within the subband used for transmission / reception in the first direction; and Transmission / reception in the first direction is performed using the mapped PRB.

33. The network node according to claim 32, wherein, The processing circuitry is operable to determine the VRB-PRB mapping by determining the VRB-PRB mapping, wherein VRBs not mapped to the one or more subbands used for transmission / reception in the first direction are considered invalid and not used for resource mapping.

34. The network node according to claim 33, wherein, The processing circuitry is operable to perform interleaving when determining the VRB-PRB mapping, wherein VRBs not mapped to one or more subbands for transmission / reception in the first direction are considered invalid and not used for resource mapping.

35. The network node according to claim 32, wherein, The processing circuitry is operable to determine the VRB-PRB mapping by determining the VRB-PRB mapping, wherein VRBs not mapped to the one or more subbands for transmission / reception in the first direction are shifted to be mapped to a second subband for transmission / reception in the one or more subbands in the first direction.

36. The network node according to claim 25, wherein, The processing circuitry is operable to perform interleaving when determining the VRB to PRB mapping, and the interleaving is performed on a bandwidth that includes the sum of all subbands used for transmission / reception in the first direction.

37. The network node according to claim 32, wherein, The processing circuitry is operable to perform interleaving when determining the mapping from the downlink VRB to the PRB, wherein the interleaving mode ensures that the mapped PRB is within the subband for transmission / reception in the first direction.

38. The network node according to any one of claims 32-37, wherein, The first direction includes a downlink, the second direction includes an uplink, and the processing circuitry is operable to perform transmission / reception in the first direction using the mapped PRB by performing downlink transmission in the Physical Downlink Shared Channel (PDSCH) using the mapped PRB.

39. The network node according to claim 38, wherein, The frequency domain resource allocation scheme includes a downlink type 1 resource allocation scheme.

40. The network node according to any one of claims 33 and 35, wherein, The frequency domain resource allocation includes a downlink type 0 resource allocation scheme.

41. The network node according to any one of claims 32-37, wherein, The first direction includes an uplink, the second direction includes a downlink, and performing transmission / reception in the first direction using the mapped PRB includes performing uplink reception in the Physical Uplink Shared Channel (PUSCH) using the mapped PRB.

42. The network node according to any one of claims 32-41, wherein the processing circuitry is further operable to transmit to the wireless device an indication of which variant of the VRB-to-PRB mapping to use when mapping a VRB to a PRB.

Images