Frequency domain resource allocation interpretation

Abstract

Methods and systems are described for FDRA field interpretation and SBFD operation. Certain embodiments inform the UE if it should interpret the resource allocation field according to enhanced or legacy operation. Other embodiments may enable the gNB to know if the UE supports the enhanced resource allocation types before RRC capability signaling is available. In some embodiments, a UE can receive SBFD configurations and a resource allocation. The resource allocation can be interpreted based on the SBFD configuration.

Description

FREQUENCY DOMAIN RESOURCE ALLOCATION INTERPRETATION CROSS REFERENCE TO RELATED INFORMATION

[0001] This application claims the benefit of United States of America priority application No 63 / 555,316 filed on February 19, 2024, titled “Frequency Domain Resource Allocation Interpretation.” TECHNICAL FIELD

[0002] The present disclosure generally relates to systems and methods for SBFD operation. BACKGROUND

[0003] The present disclosure relates to the field of wireless communication, and more specifically to full duplex communication, SBFD, frequency domain resource allocation, PDSCH, interleaving, VRB-to-PRB mapping, initial access, downlink control information (DCI), MSG2, and MSG3. 3GPP NR Standard

[0004] New radio (NR) standard in 3GPP is being designed to provide service for multiple use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC), and machine type communication (MTC). More detail on this can be found in technical specification 3GPP TS 38.300 V17.5.0 (2023-06), https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.300 / 38300-h50.zip. Each of these services has different technical requirements. For example, the general requirement for eMBB is high data rate with moderate latency and moderate coverage, while URLLC service requires a low latency and high reliability transmission but perhaps for moderate data rates.

[0005] A NR slot consists of several OFDM symbols, according to current agreements either 7 or 14 symbols (OFDM subcarrier spacing ≤ 60 kHz) and 14 symbols (OFDMsubcarrier spacing > 60 kHz). Figure 1 illustrates a slot with 14 OFDM symbols, with T_s and T_symb denoting the slot and OFDM symbol duration respectively. Duplex Communication Mode Types

[0006] To support the many types of targeted use cases with varying requirements, different duplex communication modes are discussed in 3GPP standardization. As such, the same device may be capable of, for example, operating using different duplex modes to achieve different overall communication performance based on its needs.

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

[0008] Frequency Division Duplex (FDD), as illustrated in Figure 2(a), implies that transmission (TX) and reception (RX) take place in different – or sufficiently separated – carriers, requiring a paired spectrum. For FDD operation, there are two carrier frequencies, one for uplink (UL) transmission and one for downlink (DL) transmission. With respect to the UE in a cellular communication system, FDD can be either full duplex (FD-FDD) or half duplex (HD-FDD). In the FD-FDD case, a UE can transmit and receive simultaneously, while in HD-FDD operation, the UE cannot transmit and receive simultaneously. However, the BS is still capable of simultaneous RX / TX, such as when receiving from one UE while simultaneously transmitting to another UE. In LTE, a HD-FDD terminal is monitoring or receiving in the DL except when explicitly being instructed to transmit in a certain subframe.

[0009] Time Division Duplex (TDD), as illustrated in Figure 2(b), implies that TX and RX take place within the same carrier in different, non-overlapping time slots. This allows TDD to operate in an unpaired spectrum. For TDD operation there is only a single carrier frequency, resulting in UL and DL transmissions being always separated in time on a cell basis. As the same carrier frequency is used for UL and DL transmission, both the BS and the UEs need to switch from TX to RX, from RX to TX. An aspect of any TDD system is to provide the possibility for a sufficiently large guard time where neither DL or UL transmissions occur. This isrequired to avoid interference between UL and DL transmissions. For NR, this guard time is provided by special slots, which are split into three parts: symbols for DL, a guard period (GP), and symbols for UL. The remaining slots are either allocated to UL or DL transmission. Interferences existing in this configuration are among transmissions happening on the same link, inside the channel, and from an adjacent channel, if synchronization is also assumed among different operators. This is shown in Figure 3(a), where the two networks deployed in channels 1 and 2 are synchronized and will suffer only from in-channel and adjacent channel interference from the same link. Interference links are further illustrated in Figure 4(a). This approach is used by operators in Europe and recommended in regulations. It requires entire carrier bandwidth or all carriers in the same frequency band to be utilizing the same DL transmission or UL reception directions.

[0010] Dynamic TDD describes a mode of operation in which a network adapts the DL / UL subframe pattern according to traffic conditions. This causes interference between different links, such as the uplink and downlink. The interference may be Cross Link Interference (CLI), BS-to-BS interference, or UE-to-UE interference, as shown in Figure 4(b). CLI occurs inside the same operator and inter-operators, as shown in Figure 3(b). Here, the deployment on channel 1 requires additional UL slots to serve UL traffic. To accomplish that, the TDD patterns of BS1 and BS2 are adjusted to increase UL ratio. As a result, the deployment will suffer, inside the network, from BS-to-BS interference and UE-to-UE interference in slots 2 and 3. In addition, these patterns used in channel 1 are unsynchronized with respect to the static TDD pattern used in channel 2. Due to that, the deployment in channel 1 will suffer from BS-to-BS and UE-to-UE interference from the adjacent channel, in slots 2, 3 and 4. On channel 2, the deployment will suffer from UE-to-UE interference from the adjacent channel in slots 2, 3 and 4, but only from the same link interference inside channel 2.

[0011] Sub-Band Full Duplex (SBFD), as illustrated in Figure 2(c), is being studied in 3GPP Release 18 as a part of the 5G-Advanced standardization. See, 3GPP Technical Report TR 38.858 Study on evolution of NR duplex operation (Release 18), v 2.0, 3rd Generation Partnership Project Std., 2023. During SBFD operation, a portion of a wide bandwidth carrier, termed sub-band, may be used for a different communication direction than that of the rest of the carrier. Correspondingly, different non-overlapping sub-bands are used for DL and UL. This is unlike the conventional TDD operation, wherein the entire bandwidth of the carrier is always usedeither for DL or UL. SBFD operation can also be performed across different carriers within the same frequency band, wherein one or more carriers within a frequency band may be used for a different communication direction than that of the other carriers. This is unlike conventional TDD operation wherein all carriers within a frequency band are always used for the same communication direction. In the 3GPP Release 18 study, the scope has been limited such that during SBFD communication, only BSs transmit DL and receive UL simultaneously using corresponding non-overlapping sub-bands. An individual UE is scheduled in only one direction (DL or UL) at a time, following conventional HD TDD operation. However, for future 3GPP releases, SBFD operation at UEs wherein a UE transmits UL and receives DL simultaneously using corresponding non-overlapping sub-bands is also being discussed as a potential study topic. Interference links affecting SBFD Rel.18 deployments are shown in Figure 4(c).

[0012] Single frequency full duplex (SFFD) (i.e., In-band Full Duplex (IBFD), Conventional Full Duplex), as illustrated in Figure 2(d), has also been proposed to be studied in 3GPP standardization. It was discussed but excluded from the scope of Release 18, and is now being discussed again during scoping discussions for future releases. In case of SFFD operation, the entire bandwidth of the same carrier in a single carrier system or all carriers in a multi-carrier system can be simultaneously used for DL and UL operations. In other words, the same time and frequency resources can be used for both TX and RX at the same device. Similar to SBFD operation, SFFD operation is also being discussed for both BSs and UEs. PDSCH Resource Allocation in Frequency-Domain

[0013] PDSCH is the DL physical channel that delivers user data from gNB to UE. The network informs the UE about the frequency resources to be used for the reception of PDSCH using DCI . Within these DCI Formats, the field ‘Frequency domain resource assignment’ carries the required resource allocation information.

[0014] NR supports two types of DL resource allocation schemes, Type 0 and Type 1. See, technical specification 3GPP TS 38.214 v18.0.0 (2023-09), https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.214 / 38214-i00.zip. The network informssignaling within PDSCH- Config IE.Downlink Resource Allocation Type 0

[0015] The network asks the UE to use type 0 resource allocation, either via RRC signalling (resourceAllocationType0) or via DCI. The DL resource allocation type 0 is based on a bitmap indication where RB assignment information includes a bitmap indicating the Resource Block Group (RBG) that are allocated to a UE.

[0016] A RBG is a set of consecutive Virtual Resource Blocks (VRB). With type 0 resource allocation, only non-interleaved VRB-to-PRB mapping is possible, which means that ^^^^^^^is mapped to ^^^^^^^. The bitmap is of size ^^ோ^ீ, where each bit withing the bitmap corresponds to a RBG so that each RBG withing the BWP is addressable. An RBG is allocated to the UE if the corresponding bit value in the bitmap is 1, the RBG is not allocated to the UE if the bit value is 0.

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

[0018] The total number of RBGs within the DL BWP is: ^^ ^^௭^ோ^ீ ൌ ^^^^^^ ^ ^^^^^^௧^^^௧^^^^^^ ^^^ / ^^^ where, the size of the first^^^^^^^^௭^^ ൌ ^^ െ ^^^^^௧^^^௧^^^^^^ ^^ the size of the last RBG is^^^^^^^^௭^ ൌ ൫^^ ^௧^^௧ ^ ^^^^௭^൯ ^^^௭^ ^௧^^௧ ^^௭^^^^௧ ^^^ ^^^^^^^^ ^^, if ^^^^^^^^^௧ ൌ ൫^^^^^ ^ ^^^^^ ൯ ^^^^^^ ^^ ^ 0 or Pthe size of all other RBG is P.

[0019] More details are available in section 5.1.2.2.1 of technical specification 3GPP TS 38.214 v18.0.0 (2023-09). Downlink Resource Allocation Type 1

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

[0021] The procedure to derive the allocated PRBs in this case involves two steps: ^ - To use the Resource Indication Value (RIV) method to derive a set of contiguously allocated VRBs (start VRB and length of VRBs)^ - To perform VRB-to-PRB mapping: In this step, a set of VRBs (derived from step 1) are mapped onto a set of PRBs using interleaved or non-interleaved mapping procedure. RIV to derive contiguously allocated VRBs

[0022] DL type 1 resource allocation is based on a RIV corresponding to a starting VRB number ^^^^^௧^^௧and a length in terms of contiguously allocated VRB, ^^ோ^. The RIV value is defined as follows: ^^௭^ If ^^^ோ^ െ 1^ ^ ^^^^^^ൗ2 ^, ^^^^^^ ൌ ^^ ^^௭^^^^ ൈ ^^^ோ^ െ 1^ ^ ^^^^^௧^^௧

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

[0024] Once the starting VRB number and the number of consecutive VRBs are known, there is need to derive the actual PRBs required for the reception of PDSCH. To do so, VRB-to-PRB mapping needs to be done. See, technical specification 3GPP TS 38.211 V18.0.0 (2023-09), https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.211 / 38211-i00.zip.

[0025] Two different types of VRB-to-PRB mapping are currently supported in the standard:

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

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

[0028] The DCI may or may not include a single bit field ‘VRB-to-PRB mapping’. See, technical specification 3GPP TS 38.212 V18.0.0 (2023-09), https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.212 / 38212-i00.zip. When the bit is absent, Type 0. When the bit isis configured, if the bit is 1 interleaving is configured.

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

[0030] Depending upon the size of the BWP and the RBB size (L), the RBB sizes of the first and last RBB could be different to that of RBB size configured by the RRC. ^ Let the total number of RBs within BWP (Bandwidth Part) I be ^^^^^^௭^^,^^ Let the starting PRB position within BWP i be ^^^^^௧^^^௧,^^ Let ^^^be the RBB size for BWP i, as defined by RRC ^ The total number of RBBs for the BWP i is ^^^௨^ௗ^^ൌ ൫^^^^௭^^^^,^ ^ ^^^^௧^^௧^^^^^^ ^^^^൯ ^^^^,^ ^^^^ ^0 size^^௭^^௧^^௧is ^^^௨^ௗ^^,^,^ ൌ ^^^ െ ൫^^^^^,^^^^^^^ ^^^൯ resource blocksb. The size of the last Resource Block Bundle, ^^^௨^ௗ^^ െ 1 ,is ^^^^௨^௭^^ௗ^^,^^^௧,^ൌ ൫^^^௧^^௧,^ ^ ^^^^^^௭^^,^൯^௧^^௧ ^^௭^^^^^^^^^^ ^^^resource blocks if ൫^^^^^,^ ^ ^^^^^,^ ൯^^^^^^ ^^^ ^ 0, and^^^resource blocks otherwise c. All other resource block bundles consist of ^^^resource blocks ^VRBs in the interval ^^ ∈ ^0,1, …^^^௨^ௗ^^are mapped to PRBs according to:a. VRB ^^^௨^ௗ^^ െ 1 is mapped to PRB ^^^௨^ௗ^^ െ 1b. VRB bundle ^^ ∈ ^0,1, …^^^௨^ௗ^^ െ 2^ is mapped to PRB bundle ^^^^^^ where ^^^^^^ isdefined in TS38.211: i. ^^^^^^ ൌ ^^^^ ^ ^^ii. ^^ ൌ ^^^^ ^ ^^iii. ^^ ൌ 0,1, …^^ െ 1iv. ^^ ൌ 0,1, …^^ െ 1v. ^^ ൌ 2vi. ^^ ൌ ^^^^௨^ௗ^^ൗ 2 ^Enhancements

[0031] United States Provisional Patent Application no.63 / 553,965, filed February 15, 2024, describes embodiments in which DL Resource Allocation Type 0 and 1 and the VRB- to-PRB mapping mechanism for PDSCH are enhanced for BSs deploying SBFD. The enhancement allows for Release 18 and older UEs to operate in transparent manner while Release 19 and onwards UEs, that support SBFD, can operate in an optimized manner with full potentiality even when an SBFD configuration having multiple discontinuous DL subbands (e.g., D-U-D) is considered. More specifically, it defines (1) options for Resource Allocation Type 0 and Type 1 so that the number of bits for frequency domain resource assignment in the scheduling DCI is optimized, (2) options for Resource Allocation Type 1 to support allocation of DL resources across multiple DL subbands for when interleaved VRB-to-PRB mapping is enabled or not, and (3) options for enhancement of interleaved VRB-to-PRB mapping for SBFD operation to ensure the indicated VRBs are mapped to PRBs in the DL subbands.

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

[0033] Current NR specification supports two different DL resource allocation schemes in the frequency domain, namely DL Resource Allocation Type 0 and Type 1, as previously described.

[0034] In United States Provisional Patent Application no. 63 / 553,965, different enhancements to DL Resource Allocation Type 0 and Type 1 have been proposed. In some of these enhanced resource allocation schemes, the frequency domain resource assignment (FDRA) is based on a VRB space which has the same dimension as the legacy VRB space. In other enhanced schemes, the VRB space is optimized and only includes the valid DL subbands resources, so that it is effectively reduced compared to the legacy dimension, which can represent a benefit in terms of saved bits in FDRA. In this case, it may be beneficial to have the gNB and UE agree on if the enhanced resource allocations are considered, including what VRB space the FDRA will refer to.

[0035] There are occasions when the network is unaware of the capabilities of the UE. For example, during initial access, the capabilities of a UE are typically unknown. That is, the gNB does not know if a particular UE supports the enhanced resource allocation schemes for SBFD. As another example, when a UE does CBRA in CONNECTED mode, the gNB does not know the UE identity nor if the UE supports the resource allocation enhancements. The ability of the gNB to determine the capability of the UEs as early as possible would allow use of SBFD enhancements for FDRA during initial access.

[0036] Thus, there is a need to inform the UE if it should interpret the resource allocation field according to enhanced or legacy operation, and for the gNB to determine, as soon as possible and before RRC capability signaling, if the UE supports the enhanced resource allocation types and is able to interpret the SBFD carrier configuration. SUMMARY

[0037] One embodiment under the present disclosure comprises a method performed by a UE for interpreting a FDRA field. The method includes: indicating, to a network node, one or more SBFD capabilities; receiving, from the network node, a SBFD subband configuration; receiving, from the network node, a resource allocation comprising a FDRA field; and interpreting the FDRA field based at least in part on the SBFD subband configuration.

[0038] Another possible method embodiment under the present disclosure is a method performed by a UE for indicating SBFD capability. The method includes indicating, to anetwork node, one or more SBFD capabilities, wherein the indicating is performed prior to any RRC messaging. Further steps include: if the UE is capable of SBFD operation, then receiving, from the network node, an indication of SBFD operation; and if the UE is not capable of SBFD operation, then receiving, from the network node, an indication of legacy operation.

[0039] Another possible method embodiment under the present disclosure is a method performed by a network node for indicating resource allocation for SBFD operation to a UE. The method includes: receiving, from the UE, one or more SBFD capabilities; transmitting, to the UE, a SBFD subband configuration; transmitting, to the UE, a resource allocation comprising a FDRA field, wherein the UE is configured to interpret the FDRA field based at least in part on the SBFD subband configuration.

[0040] Another possible method embodiment under the present disclosure is a method performed by a network node for indicating SBFD operation to a UE. The method includes receiving, from a UE, one or more SBFD capabilities, wherein the receiving is performed prior to any RRC messaging. Further steps include, if the UE is capable of SBFD operation, then transmitting, to the UE, an indication of SBFD operation; and if the UE is not capable of SBFD operation, then transmitting, to the UE, an indication of legacy operation.

[0041] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an indication of the scope of the claimed subject matter. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] For a more complete understanding of the present disclosure, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

[0043] Fig.1 illustrates a slot in NR;

[0044] Fig.2 illustrates different types of duplex communication modes;

[0045] Fig.3 illustrates a comparison of TDD operations;

[0046] Fig.4 illustrates TDD operation options and interference cases;

[0047] Fig. 5 illustrates a flow-chart of a method embodiment under the present disclosure;

[0048] Fig. 6 illustrates a flow-chart of a method embodiment under the present disclosure;

[0049] Fig. 7 illustrates a flow-chart of a method embodiment under the present disclosure;

[0050] Fig. 8 illustrates a flow-chart of a method embodiment under the present disclosure;

[0051] Fig. 9 illustrates a flow-chart of a method embodiment under the present disclosure;

[0052] Fig.10 illustrates a flow-chart of a method embodiment under the present disclosure;

[0053] Fig.11 shows a schematic of a communication system embodiment under the present disclosure;

[0054] Fig. 12 shows a schematic of a user equipment embodiment under the present disclosure; and

[0055] Fig.13 shows a schematic of a network node embodiment under the present disclosure. DETAILED DESCRIPTION

[0056] Before describing various embodiments of the present disclosure in detail, it is to be understood that this disclosure is not limited to the parameters of the particularly exemplified systems, methods, apparatus, products, processes, and / or kits, which may, of course, vary. Thus, while certain embodiments of the present disclosure will be described in detail, with reference to specific configurations, parameters, components, elements, etc., the descriptions are illustrative and are not to be construed as limiting the scope of the claimed embodiments. In addition, the terminology used herein is for the purpose of describing the embodiments and is not necessarily intended to limit the scope of the claimed embodiments.

[0057] As described above, there currently exist certain challenges. There are occasions when the network is unaware of the capabilities of the UE. For example, during initial access, the capabilities of a UE are typically unknown. That is, the gNB does not know if a particular UE supports the enhanced resource allocation schemes for SBFD. As another example, when a UE does CBRA in CONNECTED mode, the gNB does not know the UE identity nor ifthe UE supports the resource allocation enhancements. The ability of the gNB to determine the capability of the UEs as early as possible would allow use of SBFD enhancements for FDRA during initial access.

[0058] Thus, there is a need to inform the UE if it should interpret the resource allocation field according to enhanced or legacy operation, and for the gNB to determine, as soon as possible and before RRC capability signaling, if the UE supports the enhanced resource allocation types and is able to interpret the SBFD carrier configuration.

[0059] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Certain embodiments inform the UE if it should interpret the resource allocation field according to enhanced or legacy operation. Other embodiments may enable the gNB to know if the UE supports the enhanced resource allocation types before RRC capability signaling is available.

[0060] One embodiment can be summarized in the following method 500, shown in Figure 5. Method 500 comprises a method performed in a UE for determining how to interpret a resource allocation. Step 510 is receiving sub-band full duplex (SBFD) configurations. Step 520 is receiving a resource allocation. Step 530 is determining how to interpret the resource allocation. Step 540 is communicating, including receiving or transmitting, according to the resource allocation.

[0061] Method 500 can comprise a variety of additional, optional, or alternative steps. For example, in some embodiments the resource allocation is interpreted taking the SBFD configuration into account, while in other embodiments the SBFD configuration is not taken into account. The resource allocation may further be received 520, in some alternatives, via DCI. Other examples include embodiments where the determining step 530, when the resource allocation is received via DCI, is based on: the search space in which the DCI is received, an explicit indication in the DCI, which RNTI (Radio Network Temporary Identifier) the CRC of the DCI is scrambled with, or a combination thereof. In some variations, the determining step 530 may also be based a dedicated (i.e., UE-specific) RRC configuration, or based generally on the resource allocation itself.

[0062] Another embodiment is summarized in method 600, illustrated in Figure 6. Method 600 comprises a method performed in a node, such as a gNB, for determining 650 if a UE has SBFD capabilities before RRC capability signaling happens. Step 610 determines what RACH(Random Access Channel) occasion the UE uses. Step 620 determines the PRACH (Physical Random Access Channel) preamble. Step 630 determines paging. Step 640 determines early paging indication. In various embodiments the steps, 610, 620, 630, and 640 may collectively be used to determine 650 if SBFD capabilities are present, or in some combination thereof.

[0063] Certain embodiments may provide one or more of the following technical advantages. Firstly, an alignment between a transmitter and receiver of how resource allocation should be interpreted may allow for a receiver to be able to correctly receive downlink data (PDSCH) and uplink data (PUSCH). Additionally, an enhanced resource allocation scheme may be used earlier than typically possible, such as during the RACH procedure.

[0064] Some additional embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. When describing embodiments herein, a UE in SBFD operation may have already received SBFD configuration using dedicated or common signaling from its serving gNB. This serves as an indication to the UE that the carrier may be configured with DL subbands, UL subbands and guard-bands, and also provides the exact location and size of each subband in the carrier (e.g., a D-U-D pattern, other SBFD patterns).

[0065] The embodiments may refer to different ways of interpreting the frequency domain resource assignment field. One way is according to legacy procedures (Rel-18), which will be referend to as legacy operation. Another way is when the frequency domain resource allocation field is interpreted taking the SBFD configuration into account (e.g., the teachings of United States Provisional Patent Application no.63 / 553,965), which will be referred to as SBFD operation.

[0066] Though embodiments herein discuss DL resource allocation for D-U-D SBFD pattern, the methods or systems disclosed in the embodiments may also be used for UL resource allocation, may include different SBFD patterns (e.g., U-D-U), and may be applicable for PUSCH. Group 1 Embodiments

[0067] The embodiments of group 1 inform a UE on how to interpret a frequency domain resource allocation field according to legacy or SBFD operation.

[0068] Embodiment 1a includes determination based search space type. In one embodiment, a UE may determine how to interpret the frequency domain resource assignment field in DCI based on the search space type. When the DCI scheduling PDSCH / PUSCH is received in common search space, the UE may interpret the frequency domain field according to legacy operation. When the DCI scheduling PDSCH / PUSCH is received in UE-specific search space, including when the size of DCI scheduling PDSCH (DCI format 1_0) in UE-specific search space is derived from the size of DCI format 1_0 in common search space, the UE may interpret the frequency domain field according to SBFD operation. When the UE is not configured for SBFD operation, the UE may interpret the frequency domain field according to legacy operation.

[0069] Embodiment 1b includes explicit indication in DCI. In one embodiment, the UE can determine how to interpret the frequency domain resource assignment field in DCI based on signaling in the scheduling DCI itself. In one nonlimiting example, one addition bit is included when the UE is configured for SBFD operation. A value of ‘0’ can mean that the UE should interpret the frequency domain resource assignment according to legacy operation while a value of ‘1’ can indicate that the UE interprets the frequency domain field according to SBFD operation. The FDRA type (legacy FDRA types or SBFD FDRA type) could, in some embodiments, be configured via one of: the size of the FDRA field in DCI, a dedicated indicator in DCI, or RRC. As an alternative, a dedicated indicator in a cell-specific configuration (e.g., SIB1) may indicate to an SBFD-capable UE that it should interpret the frequency domain resource assignment according to legacy operation or SBFD operation.

[0070] Embodiment 1c includes determination based on RNTI type. In one embodiment, a UE may determine how to interpret the frequency domain resource assignment field in DCI based on a RNTI type. In one nonlimiting example, the UE may interpret the frequency domain field according to SBFD operation if the CRC of the DCI is scrambled with a UE unique RNTI such as: C-RNTI, CS-RNTI, or MCS-CS-RNTI. Otherwise, the UE may interpret the frequency domain resource assignment according to legacy operation.

[0071] Embodiment 1d includes determination based on DCI format. In one embodiment, a UE may determine how to interpret the frequency domain resource assignment field in DCI based on DCI type. In one nonlimiting example, the UE may interpret the frequency domain field according to SBFD operation for DCI formats that can only be configured in UE- specific search spaces, such as DCI format 1_1 and DCI format 1_2. As a variation, the UE coulddetermine how to interpret the FDRA based on sets of DCI formats supporting SBFD enhancement RA, such as non-fallback DCI formats.

[0072] Embodiment 1e includes indication through RRC configuration. In one embodiment, a UE may determine how to interpret the frequency domain resource assignment field in DCI based on dedicated RRC parameters. Before receiving such dedicated RRC signaling, the UE may interpret the frequency domain field according to legacy operation. In one nonlimiting example, the indication is added to the search space configuration. Here, one addition bit is included in case the UE is configured for SBFD operation. A value of ‘0’ can mean that the UE should interpret the frequency domain resource assignment according to legacy operation while a value of ‘1’ can indicate that the UE interprets the frequency domain field according to SBFD operation. As another example, the indication is added to PDSCH-Config or PDSCH- ConfigCommon. In a variation to this embodiment, a UE may determine how to interpret the frequency domain resource assignment field in DCI based on implicitly via other RRC parameters, such as if the UE is configured with SBFD frequency configuration, or a SBFD TDD pattern.

[0073] Embodiment 1f includes determination based on FDRA in the DCI. The Frequency Domain Resource Assignment (FDRA) in the DCI can refer to, in some embodiments, a VRB space with a dimension equal to the legacy VRB space or to an optimized VRB space whose dimension is reduced and does not include the guard bands or the UL subband. The FDRA indicator in the DCI may be transparent to Release 18 and older UEs, so that Resource Allocation Type 1 assigns to these kinds of UEs only contiguous DL resources in one DL subband. If the VRB space dimension is not optimized (i.e., equal to the legacy space) (United States Provisional Patent Application no. 63 / 553965, section 2.6.1.1 option 1 and section 2.6.1.2 options 1 and 2), and if the resource allocation Type 1 exceeds the limits of one DL subband, the Release 19 UE may interpret the FDRA with enhanced operation and consider as invalid the assignments which are associated to the guard bands and the UL subband. The Release 19 UE may already be provided with the SBFD configuration, via common or dedicated RRC signaling. Alternatively, if the VRB space dimension is optimized (see United States Provisional Patent Application no. 63 / 553965, section 2.6.1.1 option 2, and section 2.6.1.2 option 3), the Release 19 UE may be aware of this to add a gap to the resource assignment information communicated through the FDRA. This indication can be communicated to the UE through PDSCH-Config or PDSCH-ConfigCommon.Group 2 Embodiments

[0074] The embodiments of group 2 can allow a node (e.g., gNB) to determine if a UE is capable of SBFD operation or not prior to RRC signaling. Previously, such determination would be done using RRC capability signaling. These embodiments may be combined with Group 1 Embodiments so that the node may indicate SBFD operation to UEs supporting SBFD and legacy operation to UEs not supporting SBFD.

[0075] Embodiment 2a includes UE capability determination through RACH Occasion (RO). In one embodiment, a gNB can assume that a UE is SBFD capable if it uses one of the RACH occasions that are defined in an SBFD symbol. If the UE uses a RO occasion in a non-SBFD symbol, the gNB can assume that the UE is not SBFD capable until it has received RRC capability signaling from that UE.

[0076] Embodiment 2b includes UE capability determination through PRACH preamble. In one embodiment, a set of PRACH preambles are split into two sets. If a UE is capable of SBFD it may use a preamble from the first set. If the UE is not capable of SBFD it may use a preamble from the second set. Legacy UEs may use legacy RACH configuration, therefore the second set of preambles may be configured there. The first set of preambles may be configured in a new RACH configuration that only SBFD capable UEs can understand. If the gNB detects a preamble from the first set, the gNB assumes that the UE is SBFD capable.

[0077] Embodiment 2c can includes UE capability determination through paging. In one embodiment, a paging mechanism may be utilized to determine if a UE is capable of SBFD or not. A gNB may send a paging message consisting of details such as the Paging Identity (Paging- ID) and the UE’s Temporary Mobile Subscriber Identity (TMSI). The UE can monitor one Paging Occasion (PO) per DRX cycle associated with a Paging Frame (PF). Specifically, PF is derived from system frame numbers (SFNs) using: (SFN + PF_offset) mod T = (T div N)*(UE_ID mod N), and PO associated with PS is pointed out by index i_s such that: i _s = floor (UE_ID / N) mod Ns, where T is the DRX cycle of the UE, N is the number of total paging frames per DRX cycle, Ns is the number of paging occasions for a PF, PF_offset is the offset used to shift the PF, and UE_ID is 5G-S-TMSI mod 1024. The gNB may configure the DRX parameters differently from other configuration parameters to identify the UEs capable of SBFD compared to the legacy UEs. If aspecific UE responds based on the distinct DRX cycle than that of the settings used for the legacy, the gNB assumes that the UE is SBFD capable.

[0078] Embodiment 2d can include UE capability determination through early paging indication and subgrouping. NR may also support, in an embodiment, the Early Paging Indication feature in release-17 as an enhancement to traditional paging. Specifically, Early Paging Indication (EPI) informs the UE whether to receive the next PO while sub-grouping enables dividing the UEs of one PO into N sub-groups. The gNB can partition the sub-groups between the legacy and SBFD-capable UEs and, depending on how each UE responds to the paging, the gNB can infer if a specific is SBFD capable or not.

[0079] The foregoing are not an exhaustive list of possible example embodiments. Further possible, and non-limiting, embodiments are described below. Additional Embodiments

[0080] The methods described in this disclosure, if they were accepted by 3GPP, would require updates in several 3GPP specifications: TS 38.212, description on DL DCI formats; and TS 38.214, description on DL Resource Allocation Type 0 and Type 1 in SBFD operation.

[0081] Another possible method embodiment under the present disclosure is shown in Figure 7. Method 800 comprises a method performed by a UE for interpreting a FDRA field. Step 810 is indicating, to a network node, one or more SBFD capabilities. Step 820 is receiving, from the network node, a SBFD subband configuration. Step 830 is receiving, from the network node, a resource allocation comprising a FDRA field. Step 840 is interpreting the FDRA field based at least in part on the SBFD subband configuration. Method 800 can comprise multiple variations and embodiments and / or additional and / or alternative steps.

[0082] Another possible method embodiment under the present disclosure is shown in Figure 8. Method 1000 comprises a method performed by a UE for indicating SBFD capability. Step 1010 is indicating, to a network node, one or more SBFD capabilities, wherein the indicating is performed prior to any RRC messaging. Step 1020 is, if the UE is capable of SBFD operation, then receiving, from the network node, an indication of SBFD operation. Step 1030 is, if the UE is not capable of SBFD operation, then receiving, from the network node, an indication of legacy operation. Method 1000 can comprise multiple variations and embodiments and / or additional and / or alternative steps.

[0083] Another possible method embodiment under the present disclosure is shown in Figure 9. Method 1200 comprises a method performed by a network node for indicating resource allocation for SBFD operation to a UE. Step 1210 is receiving, from the UE, one or more SBFD capabilities. Step 1220 is transmitting, to the UE, a SBFD subband configuration. Step 1230 is transmitting, to the UE, a resource allocation comprising a FDRA field, wherein the UE is configured to interpret the FDRA field based at least in part on the SBFD subband configuration. Method 1200 can comprise multiple variations and embodiments and / or additional and / or alternative steps.

[0084] Another possible method embodiment under the present disclosure is shown in Figure 10. Method 1400 comprises a method performed by a network node for indicating SBFD operation to a UE. Step 1410 is receiving, from a UE, one or more SBFD capabilities, wherein the receiving is performed prior to any RRC messaging. Step 1420 is, if the UE is capable of SBFD operation, then transmitting, to the UE, an indication of SBFD operation. Step 1430 is, if the UE is not capable of SBFD operation, then transmitting, to the UE, an indication of legacy operation. Method 1400 can comprise multiple variations and embodiments and / or additional and / or alternative steps.

[0085] Figure 11 shows an example of a communication system 3100 in accordance with some embodiments. In the example, the communication system 3100 includes a telecommunication network 3102 that includes an access network 3104, such as a RAN, and a core network 2106, which includes one or more core network nodes 3108. The access network 3104 includes one or more access network nodes, such as network nodes 3110a and 3110b (one or more of which may be generally referred to as network nodes 3110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 3110 facilitate direct or indirect connection of UE, such as by connecting UEs 3112a, 3112b, 3112c, and 3112d (one or more of which may be generally referred to as UEs 3112) to the core network 3106 over one or more wireless connections.

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

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

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

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

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

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

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

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

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

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

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

[0097] The UE 3200 includes processing circuitry 3202 that is operatively coupled via a bus 3204 to an input / output interface 3206, a power source 3208, a memory 3210, a communication interface 3212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 12. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

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

[0099] In the example, the input / output interface 3206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 3200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence- sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. [000100] In some embodiments, the power source 3208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 3208 may further include power circuitry for delivering power from the power source 3208 itself, and / or an external power source, to the various parts of the UE 3200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 3208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 3208 to make the power suitable for the respective components of the UE 3200 to which power is supplied. [000101] The memory 3210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 3210 includes one or more application programs 3214, such as an operating system, web browser application, awidget, gadget engine, or other application, and corresponding data 3216. The memory 3210 may store, for use by the UE 3200, any of a variety of various operating systems or combinations of operating systems. [000102] The memory 3210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 3210 may allow the UE 3200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 3210, which may be or comprise a device-readable storage medium. [000103] The processing circuitry 3202 may be configured to communicate with an access network or other network using the communication interface 3212. The communication interface 3212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 3222. The communication interface 3212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 3218 and / or a receiver 3220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 3218 and receiver 3220 may be coupled to one or more antennas (e.g., antenna 3222) and may share circuit components, software or firmware, or alternatively be implemented separately. [000104] In the illustrated embodiment, communication functions of the communication interface 3212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimediacommunication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. [000105] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 3212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient). [000106] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input. [000107] A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehiclecharging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and / or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 3200 shown in Figure 12. [000108] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation. [000109] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. [000110] Figure 13 shows a network node 3300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). [000111] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the providedamount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). [000112] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs). [000113] The network node 3300 includes a processing circuitry 3302, a memory 3304, a communication interface 3306, and a power source 3308. The network node 3300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 3300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 3304 for different RATs) and some components may be reused (e.g., a same antenna 3310 may be shared by different RATs). The network node 3300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1300.[000114] The processing circuitry 3302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 3300 components, such as the memory 3304, to provide network node 3300 functionality. [000115] In some embodiments, the processing circuitry 3302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 3302 includes one or more of radio frequency (RF) transceiver circuitry 3312 and baseband processing circuitry 3314. In some embodiments, the radio frequency (RF) transceiver circuitry 3312 and the baseband processing circuitry 3314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 3312 and baseband processing circuitry 3314 may be on the same chip or set of chips, boards, or units. [000116] The memory 3304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read- only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 3302. The memory 3304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 3302 and utilized by the network node 3300. The memory 3304 may be used to store any calculations made by the processing circuitry 3302 and / or any data received via the communication interface 3306. In some embodiments, the processing circuitry 3302 and memory 3304 is integrated. [000117] The communication interface 3306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 3306 comprises port(s) / terminal(s) 3316 to send and receive data, for example to and from a network over a wired connection. The communication interface 3306 also includes radio front-end circuitry 3318 that may be coupled to, or in certainembodiments a part of, the antenna 3310. Radio front-end circuitry 3318 comprises filters 3320 and amplifiers 3322. The radio front-end circuitry 3318 may be connected to an antenna 3310 and processing circuitry 3302. The radio front-end circuitry may be configured to condition signals communicated between antenna 3310 and processing circuitry 3302. The radio front-end circuitry 3318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 3318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 3320 and / or amplifiers 3322. The radio signal may then be transmitted via the antenna 3310. Similarly, when receiving data, the antenna 3310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 3318. The digital data may be passed to the processing circuitry 3302. In other embodiments, the communication interface may comprise different components and / or different combinations of components. [000118] In certain alternative embodiments, the network node 3300 does not include separate radio front-end circuitry 3318, instead, the processing circuitry 3302 includes radio front- end circuitry and is connected to the antenna 3310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 3312 is part of the communication interface 3306. In still other embodiments, the communication interface 3306 includes one or more ports or terminals 3316, the radio front-end circuitry 3318, and the RF transceiver circuitry 3312, as part of a radio unit (not shown), and the communication interface 3306 communicates with the baseband processing circuitry 3314, which is part of a digital unit (not shown). [000119] The antenna 3310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 3310 may be coupled to the radio front-end circuitry 3318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 3310 is separate from the network node 3300 and connectable to the network node 3300 through an interface or port. [000120] The antenna 3310, communication interface 3306, and / or the processing circuitry 3302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 3310, the communication interface 3306, and / or the processing circuitry 3302 may be configured to perform any transmitting operations described herein as beingperformed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment. [000121] The power source 3308 provides power to the various components of network node 3300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 3308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 3300 with power for performing the functionality described herein. For example, the network node 3300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 3308. As a further example, the power source 3308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail. [000122] Embodiments of the network node 3300 may include additional components beyond those shown in Figure 13 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 3300 may include user interface equipment to allow input of information into the network node 3300 and to allow output of information from the network node 3300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 3300. [000123] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a largerbox, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. [000124] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally. [000125] It will be appreciated that computer systems are increasingly taking a wide variety of forms. In this description and in the claims, the terms “controller,” “computer system,” or “computing system” are defined broadly as including any device or system—or combination thereof—that includes at least one physical and tangible processor and a physical and tangible memory capable of having thereon computer-executable instructions that may be executed by a processor. By way of example, not limitation, the term “computer system” or “computing system,” as used herein is intended to include personal computers, desktop computers, laptop computers, tablets, hand-held devices (e.g., mobile telephones, PDAs, pagers), microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, multi-processor systems, network PCs, distributed computing systems, datacenters, message processors, routers, switches, and even devices that conventionally have not been considered a computing system, such as wearables (e.g., glasses).[000126] The computing system also has thereon multiple structures often referred to as an “executable component.” For instance, the memory of a computing system can include an executable component. The term “executable component” is the name for a structure that is well understood to one of ordinary skill in the art in the field of computing as being a structure that can be software, hardware, or a combination thereof. For instance, when implemented in software, one of ordinary skill in the art would understand that the structure of an executable component may include software objects, routines, methods, and so forth, that may be executed by one or more processors on the computing system, whether such an executable component exists in the heap of a computing system, or whether the executable component exists on computer-readable storage media. The structure of the executable component exists on a computer-readable medium in such a form that it is operable, when executed by one or more processors of the computing system, to cause the computing system to perform one or more functions, such as the functions and methods described herein. Such a structure may be computer-readable directly by a processor—as is the case if the executable component were binary. Alternatively, the structure may be structured to be interpretable and / or compiled—whether in a single stage or in multiple stages—so as to generate such binary that is directly interpretable by a processor. [000127] The terms “component,” “service,” “engine,” “module,” “control,” “generator,” or the like may also be used in this description. As used in this description and in this case, these terms—whether expressed with or without a modifying clause—are also intended to be synonymous with the term “executable component” and thus also have a structure that is well understood by those of ordinary skill in the art of computing. [000128] In terms of computer implementation, a computer is generally understood to comprise one or more processors or one or more controllers, and the terms computer, processor, and controller may be employed interchangeably. When provided by a computer, processor, or controller, the functions may be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by a plurality of individual computers or processors or controllers, some of which may be shared or distributed. Moreover, the term “processor” or “controller” also refers to other hardware capable of performing such functions and / or executing software, such as the example hardware recited above. [000129] In general, the various exemplary embodiments may be implemented in hardware or special purpose chips, circuits, software, logic, or any combination thereof. Forexample, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor, or other computing device, although the disclosure is not limited thereto. While various aspects of the exemplary embodiments of this disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques, or methods described herein may be implemented in, as non- limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof. [000130] While not all computing systems require a user interface, in some embodiments a computing system includes a user interface for use in communicating information from / to a user. The user interface may include output mechanisms as well as input mechanisms. The principles described herein are not limited to the precise output mechanisms or input mechanisms as such will depend on the nature of the device. However, output mechanisms might include, for instance, speakers, displays, tactile output, projections, holograms, and so forth. Examples of input mechanisms might include, for instance, microphones, touchscreens, projections, holograms, cameras, keyboards, stylus, mouse, or other pointer input, sensors of any type, and so forth. Abbreviations and Defined Terms [000131] To assist in understanding the scope and content of this written description and the appended claims, a select few terms are defined directly below. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present disclosure pertains. [000132] The terms “approximately,” “about,” and “substantially,” as used herein, represent an amount or condition close to the specific stated amount or condition that still performs a desired function or achieves a desired result. For example, the terms “approximately,” “about,” and “substantially” may refer to an amount or condition that deviates by less than 10%, or by less than 5%, or by less than 1%, or by less than 0.1%, or by less than 0.01% from a specifically stated amount or condition. [000133] Various aspects of the present disclosure, including devices, systems, and methods may be illustrated with reference to one or more embodiments or implementations, whichare exemplary in nature. As used herein, the term “exemplary” means “serving as an example, instance, or illustration,” and should not necessarily be construed as preferred or advantageous over other embodiments disclosed herein. In addition, reference to an “implementation” of the present disclosure or embodiments includes a specific reference to one or more embodiments thereof, and vice versa, and is intended to provide illustrative examples without limiting the scope of the present disclosure, which is indicated by the appended claims rather than by the present description. [000134] As used in the specification, a word appearing in the singular encompasses its plural counterpart, and a word appearing in the plural encompasses its singular counterpart, unless implicitly or explicitly understood or stated otherwise. Thus, it will be noted that, as used in this specification and the appended claims, the singular forms “a,” “an” and “the” include plural referents unless the context clearly dictates otherwise. For example, reference to a singular referent (e.g., “a widget”) includes one, two, or more referents unless implicitly or explicitly understood or stated otherwise. Similarly, reference to a plurality of referents should be interpreted as comprising a single referent and / or a plurality of referents unless the content and / or context clearly dictate otherwise. For example, reference to referents in the plural form (e.g., “widgets”) does not necessarily require a plurality of such referents. Instead, it will be appreciated that independent of the inferred number of referents, one or more referents are contemplated herein unless stated otherwise. [000135] References in the specification to "one embodiment," "an embodiment," "an example embodiment," and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. [000136] It shall be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element,without departing from the scope of example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed terms. [000137] It will be further understood that the terms "comprises", "comprising", "has", "having", "includes" and / or "including", when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof. Conclusion [000138] The present disclosure includes any novel feature or combination of features disclosed herein either explicitly or any generalization thereof. Various modifications and adaptations to the foregoing exemplary embodiments of this disclosure may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings. However, any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of this disclosure. [000139] It is understood that for any given component or embodiment described herein, any of the possible candidates or alternatives listed for that component may generally be used individually or in combination with one another, unless implicitly or explicitly understood or stated otherwise. Additionally, it will be understood that any list of such candidates or alternatives is merely illustrative, not limiting, unless implicitly or explicitly understood or stated otherwise. [000140] In addition, unless otherwise indicated, numbers expressing quantities, constituents, distances, or other measurements used in the specification and claims are to be understood as being modified by the term “about,” as that term is defined herein. Accordingly, unless indicated to the contrary, the numerical parameters set forth in the specification and attached claims are approximations that may vary depending upon the desired properties sought to be obtained by the subject matter presented herein. At the very least, and not as an attempt to limit the application of the doctrine of equivalents to the scope of the claims, each numerical parameter should at least be construed in light of the number of reported significant digits and by applying ordinary rounding techniques. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the subject matter presented herein are approximations, the numerical values set forth in the specific examples are reported as precisely as possible. Any numericalvalues, however, inherently contain certain errors necessarily resulting from the standard deviation found in their respective testing measurements. [000141] Any headings and subheadings used herein are for organizational purposes only and are not meant to be used to limit the scope of the description or the claims. The terms and expressions which have been employed herein are used as terms of description and not of limitation, and there is no intention in the use of such terms and expressions of excluding any equivalents of the features shown and described or portions thereof, but it is recognized that various modifications are possible within the scope of the present disclosure. Thus, it should be understood that although the present disclosure has been specifically disclosed in part by certain embodiments, and optional features, modification and variation of the concepts herein disclosed may be resorted to by those skilled in the art, and such modifications and variations are considered to be within the scope of this present description. [000142] It will also be appreciated that systems, devices, products, kits, methods, and / or processes, according to certain embodiments of the present disclosure may include, incorporate, or otherwise comprise properties or features (e.g., components, members, elements, parts, and / or portions) described in other embodiments disclosed and / or described herein. Accordingly, the various features of certain embodiments can be compatible with, combined with, included in, and / or incorporated into other embodiments of the present disclosure. Thus, disclosure of certain features relative to a specific embodiment of the present disclosure should not be construed as limiting application or inclusion of said features to the specific embodiment. Rather, it will be appreciated that other embodiments can also include said features, members, elements, parts, and / or portions without necessarily departing from the scope of the present disclosure. [000143] Moreover, unless a feature is described as requiring another feature in combination therewith, any feature herein may be combined with any other feature of a same or different embodiment disclosed herein. Furthermore, various well-known aspects of illustrative systems, methods, apparatus, and the like are not described herein in particular detail in order to avoid obscuring aspects of the example embodiments. Such aspects are, however, also contemplated herein. [000144] It will be apparent to one of ordinary skill in the art that methods, devices, device elements, materials, procedures, and techniques other than those specifically described herein can be applied to the practice of the described embodiments as broadly disclosed hereinwithout resort to undue experimentation. All art-known functional equivalents of methods, devices, device elements, materials, procedures, and techniques specifically described herein are intended to be encompassed by this present disclosure. [000145] When a group of materials, compositions, components, or compounds is disclosed herein, it is understood that all individual members of those groups and all subgroups thereof are disclosed separately. When a Markush group or other grouping is used herein, all individual members of the group and all combinations and sub-combinations possible of the group are intended to be individually included in the disclosure. [000146] The above-described embodiments are examples only. Alterations, modifications, and variations may be effected to the particular embodiments by those of skill in the art without departing from the scope of the description, which is defined solely by the appended claims.

Claims

CLAIMS What is claimed is:

1. A method (800) performed by a user equipment, UE (2200), for interpreting a frequency domain resource assignment, FDRA, field, the method comprising indicating (810), to a network node (3300), one or more sub-band full duplex, SBFD, capabilities; receiving (820), from the network node, a SBFD subband configuration; receiving (830), from the network node, a resource allocation comprising a Frequency Domain Resource Assignment, FDRA, field; and interpreting (840) the FDRA field based at least in part on the SBFD subband configuration.

2. The method of claim 1, further comprising performing an operation according to the resource allocation.

3. The method of claim 2, wherein the operation comprises at least one of: receiving; transmitting.

4. The method of any of claims 1 to 3, wherein the UE interprets the FDRA field based at least in part on a search space type.

5. The method of claim 4, wherein; if the UE is configured for SBFD operation, and the FDRA field is included in a scheduling Downlink Control Information, DCI, detected in a UE-specific search space, then the UE interprets the FDRA field according to SBFD operation; and if the UE is configured for SBFD operation, and the FDRA field is included in a scheduling DCI detected in a common search space, then the UE interprets the FDRA field according to legacy operation; and if the UE is not configured for SBFD operation, then the UE interprets the FDRA field according to legacy operation.

6. The method of any of claims 1 to 3, wherein the UE interprets the FDRA field based at least in part on an explicit indication in a scheduling DCI.

7. The method of any of claims 1 to 3, wherein the UE interprets the FDRA field based at least in part on a Radio Network Temporary Identifier, RNTI, type used for the scheduling DCI.

8. The method of any of claims 1 to 3, wherein the UE interprets the FDRA field based at least in part on Downlink Control Information, DCI, format.

9. The method of any of claims 1 to 3, wherein the UE interprets the FDRA field based at least in part on an indication through Radio Resource Control, RRC, configuration.

10. The method of any of claims 1 to 3, wherein the UE interprets the FDRA field based at least in part on FDRA in a Downlink Control Information, DCI. The UE interprets the FDRA field differently compared to legacy UEs with regard to the definition of the Virtual Resource Block, VRB, space.

11. The method of any of claims 1 to 10, wherein the indicating is performed prior to any Radio Resource Control, RRC, messaging.

12. A method (1000) performed by a user equipment, UE (2200), for indicating sub-band full duplex, SBFD, capability, the method comprising indicating (1010), to a network node (3300), one or more sub-band full duplex, SBFD, capabilities, wherein the indicating is performed prior to any Radio Resource Control, RRC, messaging; and if the UE is capable of SBFD operation, then receiving (1020), from the network node, an indication of SBFD operation; and if the UE is not capable of SBFD operation, then receiving (1030), from the network node, an indication of legacy operation.

13. The method of claim 12, further comprising; receiving, from the network node, a resource allocation comprising a Frequency Domain Resource Assignment, FDRA, field; and interpreting the FDRA field based at least in part on the one or more SBFD capabilities.

14. The method of claim 12 or 13, wherein the indicating is performed via the selection of Random Access Channel Occasion, RO.

15. The method of any of claims 12 to 13, wherein the indicating is performed via the selection of Physical Random Access Channel, PRACH, preamble.

16. The method of any of claims 12 to 13, wherein the indicating is performed via the selection of Paging Occasion, PO.

17. The method of any of claims 12 to 13, wherein the indicating is performed via early paging indication and subgrouping.

18. The method of claim 12, further comprising any of the steps of any of claims 1 to 11.

19. A method (1200) performed by a network node (3300) for indicating resource allocation for sub-band full duplex, SBFD, operation to a user equipment, UE (2200), the method comprising receiving (1210), from the UE, one or more SBFD capabilities; transmitting (1220), to the UE, a SBFD subband configuration; and transmitting (1230), to the UE, a resource allocation comprising a Frequency Domain Resource Assignment, FDRA, field, wherein the UE is configured to interpret the FDRA field based at least in part on the SBFD subband configuration.

20. The method of claim 19, further comprising performing an operation according to the resource allocation.

21. The method of claim 20, wherein the operation comprises at least one of: communicating; receiving; transmitting.

22. The method of any of claims 19 to 21, wherein the UE interprets the FDRA field based at least in part on a search space type.

23. The method of claim 22, wherein; if the UE is configured for SBFD operation, then the UE interprets the FDRA field according to SBFD operation; and if the UE is not configured for SBFD operation, then the UE interprets the FDRA field according to legacy operation.

24. The method of any of claims 19 to 21, wherein the UE interprets the FDRA field based at least in part on signaling in a scheduling Downlink Control Information, DCI.

25. The method of any of claims 19 to 21, wherein the UE interprets the FDRA field based at least in part on a Radio Network Temporary Identifier, RNTI, type.

26. The method of any of claims 19 to 21, wherein the UE interprets the FDRA field based at least in part on Downlink Control Information, DCI, format.

27. The method of any of claims 19 to 21, wherein the UE interprets the FDRA field based at least in part on a Radio Resource Control, RRC, Configuration.

28. The method of any of claims 19 to 21, wherein the UE interprets the FDRA field based at least in part on FDRA in a Downlink Control Information, DCI.

29. The method of any of claims 19 to 28, wherein the receiving is performed prior to any Radio Resource Control, RRC, messaging.

30. A method (1400) performed by a network node (3300) for indicating sub-band full duplex, SBFD, operation to a user equipment, UE (2200), the method comprising receiving (1410), from a UE, one or more sub-band full duplex, SBFD, capabilities, wherein the receiving is performed prior to any Radio Resource Control, RRC, messaging; and if the UE is capable of SBFD operation, then transmitting (1420), to the UE, an indication of SBFD operation; and if the UE is not capable of SBFD operation, then transmitting (1430), to the UE, an indication of legacy operation.

31. The method of claim 30, further comprising; transmitting, to the UE, a resource allocation comprising a Frequency Domain Resource Assignment, FDRA, field, wherein the UE is configured to interpret the FDRA field based at least in part on the one or more SBFD capabilities.

32. The method of claim 30 or 31, wherein the receiving is performed via Random Access Channel Occasion, RO.

33. The method of any of claims 30 to 31, wherein the receiving is performed via Physical Random Access Channel, PRACH, preamble.

34. The method of any of claims 30 to 31, wherein the receiving is performed via paging.

35. The method of any of claims 30 to 31, wherein the receiving is performed via early paging indication and subgrouping.

36. The method of any of claims 30 to 35, further comprising any of the steps of any of claims 19 to 29.

37. A user equipment, UE (2200), for interpreting a frequency domain resource assignment, FDRA, field and / or performing sub-band full duplex, SBFD, operations, comprising: processing circuitry (2202); anda memory (2210)storing instructions whereby the processing circuitry is operable to perform any of the steps of any of claims 1 to 18.

38. A network node (3300) for indicating resource allocation for sub-band full duplex, SBFD, operation and / or indicating SBFD operation, to a user equipment, UE (2200), the network node comprising: processing circuitry (3302); and a memory (3304) storing instructions whereby the processing circuitry is operable to perform any of the steps of any of claims 19 to 36.

Images