Configuration aspects of channels and signals in subband full duplexing scenario

Abstract

Disclosed is a device such as a user equipment, UE, for operating in a wireless communication network. The device is adapted to determine a resource allocation allocating resources of the wireless communication network and to use the allocated the resources based on whether the resources are within a subband full duplex. SBFD, time-frequency occasion.

Description

[0001]FH241001PEP 2024P67397EP 1 CONFIGURATION ASPECTS OF CHANNELS AND SIGNALS IN SUBBAND FULL DUPLEXING SCENARIO Description Embodiments of the present application relate to the field of wireless communication, and more specifically, to enhancing wireless communication in the field of wireless communication networks. Aspects of the present invention relate to apparatus and methods for determination of resource allocation and its use. Fig.1 is a schematic representation of an example of a terrestrial and / or non-terrestrial wireless network 100 including, as is shown in Fig.1(a), a core network 102 and one or more radio access networks RAN1, RAN2, …RANN. Fig.1(b) is a schematic representation of an example of a radio access network RANnthat may include one or more base stations gNB1to gNB5, each serving a specific area surrounding the base station schematically represented by respective cells 1061to 1065. The base stations are provided to serve users within a cell. The term base station, BS, refers to a gNB in 5G networks, an eNB in UMTS / LTE / LTE-A / LTE-A Pro, or just a BS in other mobile communication standards, e.g., 6G. A user may be a stationary device or a mobile device. The wireless communication system may also be accessed by mobile or stationary IoT devices which connect to a base station or to a user. The mobile devices or the IoT devices may include physical devices, ground based vehicles, such as robots or cars, aerial vehicles, such as manned or unmanned aerial vehicles (UAVs), the latter also referred to as drones, buildings and other items or devices having embedded therein electronics, software, sensors, actuators, or the like as well as network connectivity that enables these devices to collect and exchange data across an existing network infrastructure. Fig.1(b) shows an exemplary view of five cells, however, the RANnmay include more or less such cells, and RANnmay also include only one base station. Fig.1(b) shows two users UE1and UE2, also referred to as user equipment, UE, that are in cell 1062and that are served by base station gNB2. Another user UE3is shown in cell 1064which is served by base station gNB4. The arrows 1081, 1082and 1083schematically represent uplink / downlink connections for transmitting data from a user UE1, UE2and UE3to the base stations gNB2, gNB4 or for transmitting data from the base stations gNB2, gNB4to the users UE1, UE2, UE3. filing version an,rm FH241001PEP 2024P67397EP 2 Further, Fig.1(b) shows two IoT devices 1101and 1102in cell 1064, which may be stationary or mobile devices. The IoT device 1101accesses the wireless communication system via the base station gNB4to receive and transmit data as schematically represented by arrow 1121. The IoT device 1102accesses the wireless communication system via the user UE3as is schematically represented by arrow 1122. The respective base station gNB1to gNB5may be connected to the core network 102, e.g., via the S1 interface, via respective backhaul links 1141to 1145, which are schematically represented in Fig.1(b) by the arrows pointing to “core”. The core network 102 may be connected to one or more external networks. Further, some or all of the respective base station gNB1to gNB5may connected, e.g., via the S1 or X2 interface or the Xn interface in NR, with each other via respective backhaul links 1161to 1165, which are schematically represented in Fig.1(b) by the arrows pointing to “gNBs”. Embodiments described herein are not limited to terrestrial networks, TNs, but relate also to networks being implemented, at least in parts, as non-terrestrial network, NTN, as shown in Fig.1 with reference to a satellite S1that may operate, for example, to bridge communication between different base stations, to serve one or more UE and / or a cell on the ground, e.g., as a non- terrestrial base station, to communicate with a different satellite. For data transmission a physical resource grid may be used. The physical resource grid may comprise a set of resource elements to which various physical channels and physical signals are mapped. For example, the physical channels may include the physical downlink, uplink and sidelink shared channels (PDSCH, PUSCH, PSSCH) carrying user specific data, also referred to as downlink, uplink and sidelink payload data, the physical broadcast channel (PBCH) carrying for example a master information block (MIB), the physical downlink shared channel (PDSCH) carrying for example a system information block (SIB), the physical downlink, uplink and sidelink control channels (PDCCH, PUCCH, PSSCH) carrying for example the downlink control information (DCI), the uplink control information (UCI) and the sidelink control information (SCI). For the uplink, the physical channels, or more precisely the transport channels according to 3GPP, may further include the physical random access channel (PRACH or RACH) used by UEs for accessing the network once a UE is synchronized and has obtained the MIB and SIB. The physical signals may comprise reference signals or symbols (RS), synchronization signals and the like. The resource grid may comprise a frame or radio frame having a certain duration in the time domain and having a given bandwidth in the frequency domain. The frame may have a certain number of subframes of a predefined length, e.g., 1ms. Each subframe may include one or more slots of 12 or 14 OFDM symbols depending on the cyclic prefix (CP) length. All OFDM symbols may be used for DL or UL or only a subset, e.g., when utilizing shortened transmission time intervals (sTTI) or a mini- slot / non-slot-based frame structure comprising just a few OFDM symbols. filing version an,rm FH241001PEP 2024P67397EP 3 The wireless communication system may be any single-tone or multicarrier system using frequency-division multiplexing, like the orthogonal frequency-division multiplexing (OFDM) system, the orthogonal frequency-division multiple access (OFDMA) system, or any other IFFT-based signal with or without CP, e.g., DFT-s-OFDM. Other waveforms, like non- orthogonal waveforms for multiple access, e.g., filter-bank multicarrier (FBMC), generalized frequency division multiplexing (GFDM) or universal filtered multi carrier (UFMC), may be used. The wireless communication system may operate, e.g., in accordance with the LTE-Advanced pro standard or the NR (5G), New Radio, standard or a 6G standard. The wireless network or communication system 100 depicted in Fig.1 may by a heterogeneous network having distinct overlaid networks, e.g., a network of macro cells with each macro cell including a macro base station, like base station gNB1to gNB5, and a network of small cell base stations (not shown in Fig.1), like femto or pico base stations. In addition to the above-described terrestrial wireless network also non-terrestrial wireless communication networks exist including spaceborne transceivers, like satellites, and / or airborne transceivers, like unmanned aircraft systems. The non-terrestrial wireless communication network or system may operate in a similar way as the terrestrial system described above with reference to Fig.1, for example in accordance with the LTE-Advanced Pro standard or the NR (5G), new radio, standard. In mobile communication networks, for example in a network like that described above with reference to Fig.1, like an LTE or 5G / NR network, there may be UEs that communicate directly with each other over one or more sidelink (SL) channels, e.g., using the PC5 interface. UEs that communicate directly with each other over the sidelink may include vehicles communicating directly with other vehicles (V2V communication), vehicles communicating with other entities of the wireless communication network (V2X communication), for example roadside entities, like traffic lights, traffic signs, or pedestrians. Other UEs may not be vehicular related UEs and may comprise any of the above-mentioned devices. Such devices may also communicate directly with each other (D2D communication) using the SL channels. Therefore, the device described in this disclosure may be a UE, wherein the UE comprises one or more of the following: a power-limited UE, or a hand-held UE, like a UE used by a pedestrian, and referred to as a Vulnerable Road User, VRU, or a Pedestrian UE, P-UE, or an on-body or hand-held UE used by public safety personnel and first responders, and referred to as Public safety UE, PS-UE, or an IoT UE, e.g., a sensor, an actuator or a UE provided in a filing version an,rm FH241001PEP 2024P67397EP 4 campus network to carry out repetitive tasks and requiring input from a gateway node at periodic intervals, or a mobile terminal, or a stationary terminal, or a cellular IoT-UE, or a SL UE, or a vehicular UE, or a vehicular group leader UE, GL-UE, or a scheduling UE, S-UE, or an IoT or narrowband IoT, NB-IoT, device, a reduce capability device, RedCap, machine type communication UE, MTC-UE, mobile termination of an IAB-node, MT-IAB, a relay, a relay UE, a remote UE, a terrestrial UE, a non-terrestrial UE, NTN-UE, e.g., a plane, a high-altitude platform, a drone, or a spectrum controller, or a ground based vehicle, or an aerial vehicle, or a drone, or a moving base station, or road side unit, RSU, or a building, or any other item or device provided with network connectivity enabling the item / device to communicate using the wireless communication network, e.g., a sensor or actuator, or any other item or device provided with network connectivity enabling the item / device to communicate using a sidelink the wireless communication network, e.g., a sensor or actuator, or a Wi-Fi device, station (STA), access point (AP), node or mesh node, or mesh point, or Mesh AP, or any sidelink capable network entity. When considering two UEs directly communicating with each other over the sidelink, both UEs may be served by the same base station so that the base station may provide sidelink resource allocation configuration or assistance for the UEs. For example, both UEs may be within the coverage area of a base station, like one of the base stations depicted in Fig.1. This is referred to as an “in-coverage” scenario. Another scenario is referred to as an “out-of-coverage” scenario. It is noted that “out-of-coverage” does not mean that the two UEs are not within one of the cells depicted in Fig.1, rather, it means that these UEs - may not be connected to a base station, for example, they are not in an RRC connected state, so that the UEs do not receive from the base station any sidelink resource allocation configuration or assistance, and / or - may be connected to the base station, but, for one or more reasons, the base station may not provide sidelink resource allocation configuration or assistance for the UEs, and / or - may be connected to the base station that may not support NR V2X services, e.g., GSM, UMTS, LTE base stations. When considering two UEs directly communicating with each other over the sidelink, e.g., using the PC5 interface, one of the UEs may also be connected with a BS, and may relay information from the BS to the other UE via the sidelink interface. The relaying may be performed in the same frequency band (in-band-relay) or another frequency band (out-of-band relay) may be used. In the first case, communication on the Uu and on the sidelink may be decoupled using different time slots as in time division duplex, TDD, systems. filing version an,rm FH241001PEP 2024P67397EP 5 In an in-coverage scenario in which two UEs directly communicating with each other are both connected to a base station, the base station gNB has a coverage area which, basically, corresponds to the cell schematically represented in Fig.1. The UEs directly communicating with each other may be both in the coverage area of the base station gNB. Both UEs are possibly connected to the base station, e.g., a gNB and, in addition, they are connected directly with each other over the PC5 interface. The scheduling and / or interference management of the V2V traffic is assisted by the gNB via control signalling over the Uu interface, which is the radio interface between the base station and the UEs. In other words, the gNB provides SL resource allocation configuration or assistance for the UEs, and the gNB assigns the resources to be used for the V2V communication over the sidelink. This configuration is also referred to as a mode 1 configuration in NR V2X or as a mode 3 configuration in LTE V2X. In an out-of-coverage scenario in which the UEs directly communicating with each other are either not connected to a base station, although they may be physically within a cell of a wireless communication network, or some or all of the UEs directly communicating with each other are to a base station but the base station does not provide for the SL resource allocation configuration or assistance. UEs may directly communicate with each other over a sidelink, e.g., using the PC5 interface. The scheduling and / or interference management of the V2V traffic is based on algorithms implemented between the vehicles. This configuration is also referred to as a mode 2 configuration in NR V2X or as a mode 4 configuration in LTE V2X. As mentioned above, the out-of-coverage scenario does not necessarily mean that the respective mode 2 UEs (in NR) or mode 4 UEs (in LTE) are outside of the coverage of a base station, rather, it means that the respective mode 2 UEs (in NR) or mode 4 UEs (in LTE) are not served by a base station, are not connected to the base station of the coverage area, or are connected to the base station but receive no SL resource allocation configuration or assistance from the base station. Thus, there may be situations in which, within the coverage area, in addition to the NR mode 1 or LTE mode 3 UEs also NR mode 2 or LTE mode 4 UEs are present. Naturally, it is also possible that one of the UEs is covered by the gNB, i.e. connected with Uu to the gNB, wherein the second UE is not covered by the gNB and only connected via the PC5 interface to the first UE, or that the second vehicle is connected via the PC5 interface to the first vehicle UE but via Uu to another gNB. With an increase of an amount of communication and with an increase of requirements, flexibility of communication is an important issue for wireless communication allowing to adapt to specific needs and to increase an overall efficiency. filing version an,rm FH241001PEP 2024P67397EP 6 There is, thus, a need to improve wireless communications. It is noted that the information in the above section is only for enhancing the understanding of the background of the invention and therefore it may contain information that does not form prior art and is already known to a person of ordinary skill in the art. Embodiments of the present invention are described herein making reference to the appended drawings. Fig.1 shows a schematic representation of an example of a wireless communication system; Fig.2 is a schematic representation of a wireless communication system comprising a transceiver, like a base station or a relay, and a plurality of communication devices, like UEs, according to an embodiment; Fig.3 shows a schematic representation of a resource allocation in a wireless communication network, according to embodiments; Fig.4 shows a schematic representation of a resource allocation in a wireless communication network, according to embodiments; shows a schematic representation of a resource allocation in a wireless communication network, according to embodiments; Fig.6 shows a schematic representation of a resource allocation for SBFD and non- SBFD slots in a wireless communication network, according to embodiments; Fig.7 shows a schematic representation of a resource allocation for SBFD and non- SBFD slots in a wireless communication network, according to embodiments; Fig.8 shows a schematic representation of a resource allocation for SBFD and non- SBFD slots in a wireless communication network, according to embodiments; Fig.9 shows a schematic representation of a resource allocation for SBFD and non- SBFD slots in a wireless communication network, according to embodiments; filing version an,rm FH241001PEP 2024P67397EP 7 Fig.10 shows a schematic representation of determination rules related to a TBS calculation in a wireless communication system, according to embodiments; Fig.11 shows a schematic representation of a resource allocation in a wireless communication network, according to embodiments; Fig.12 shows a schematic representation of a resource allocation in a wireless communication network, according to embodiments; Fig.13 shows a schematic representation of a resource allocation for a plurality of SBFD symbols in a wireless communication network, according to embodiments; Fig.14 shows a schematic representation of a resource allocation for a plurality of SBFD symbols and a non-SBFD symbol in a wireless communication network, according to embodiments; Fig.15 shows a schematic representation of a resource allocation for a plurality of SBFD symbols and a non-SBFD symbol in a wireless communication network, according to embodiments; Fig.16 shows a schematic representation of resource allocations for SBFD and non-SBFD symbols in a wireless communication network, according to embodiments; Fig.17 shows a schematic representation of resource allocations for SBFD and non-SBFD symbols in a wireless communication network, according to embodiments; Fig.18 shows a schematic representation of a resource allocation in a wireless communication network, according to embodiments; Fig.19 shows a schematic representation of resource allocations for SBFD and non-SBFD slots in a wireless communication network, according to embodiments; Fig.20 shows a schematic representation of resource allocations for SBFD and non-SBFD slots in a wireless communication network, according to embodiments; filing version an,rm FH241001PEP 2024P67397EP 8 Figs.21a-k show schematic representations of derived resource allocations in a wireless communication network, according to embodiments; Fig.22 shows a schematic representation of derived resource allocation for SBFD slots in a wireless communication network, according to embodiments; Fig.23 shows a schematic representation of derived resource allocation for SBFD slots in a wireless communication network, according to embodiments; Fig.24 shows a schematic representation of derived resource allocation for SBFD slots in a wireless communication network, according to embodiments; Fig.25 shows a schematic representation of derived resource allocation for SBFD slots in a wireless communication network, according to embodiments; Fig.26 shows a schematic representation of valid and invalid resource allocations in a wireless communication network, according to embodiments; and Fig.27 illustrates an example of a computer system on which units or modules as well as the steps of the methods described in accordance with the inventive approach may execute. Equal or equivalent elements or elements with equal or equivalent functionality are denoted in the following description by equal or equivalent reference numerals or namings even if occurring in different figures. In the following description, a plurality of details are set forth to provide a more thorough explanation of embodiments of the present invention. However, it will be apparent to one skilled in the art that embodiments of the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form rather than in detail in order to avoid obscuring embodiments of the present invention. In addition, features of the different embodiments described hereinafter may be combined with each other, unless specifically noted otherwise. Embodiments of the present invention may be implemented in a wireless communication system or network as depicted in Fig.1 including a transceiver, like a base station, gNB, or relay, and a plurality of communication devices, like user equipment’s, UEs. Fig.2 is a filing version an,rm FH241001PEP 2024P67397EP 9 schematic representation of a wireless communication system comprising a transceiver 200, like a base station or a relay, and a plurality of communication devices 2021to 202n, like UEs. The UEs might communicated directly with each other via a wireless communication link or channel 203, like a radio link (e.g., using the PC5 interface (sidelink)). Further, the transceiver and the UEs 202 might communicate via a wireless communication link or channel 204, like a radio link (e.g., using the Uu interface). The transceiver 200 might include one or more antennas ANT or an antenna array having a plurality of antenna elements, a signal processor 200a and a transceiver unit 200b. The UEs 202 might include one or more antennas ANT or an antenna array having a plurality of antennas, a processor 202a1 to 202an, and a transceiver (e.g., receiver and / or transmitter) unit 202b1to 202bn. The base station 200 and / or the one or more UEs 202 may operate in accordance with the inventive teachings described herein. A base station (BS) capable of subband full duplex (SBFD) can perform uplink (UL) and downlink (DL) in the same time resources but different frequency resources known as subbands (SBs). The user equipment (UE) in the network is half duplex (HD) capable. The UE is configured with UL and DL SBs to perform either DL or UL at a time. The number of frequency domain DL / UL resources in a symbol configured with SBs (SBFD symbol) is smaller as compared to the number of frequency domain DL / UL resources in a symbol not configured with these SBs (non-SBFD symbol) for the same bandwidth due to sharing of DL and UL resources in frequency domain in the SBFD symbols. Further, the interference profile of the SBFD symbols is also different as compared to the non-SBFD symbols due to the presence of Cross Link Interference (CLI). In New Radio (NR) technology, there are various signals or channels which are periodic or repetitive in nature. These are in general configured by the BS or gNB in a way that parameters like frequency domain resource allocation and modulation order are provided same for all the occasions of the signal / channel. With SBFD enabled in the network, these parameters will be same across SBFD and non-SBFD symbols. However, as stated above, the number of resources, interference profile etc., are different for SBFD and non-SBFD symbols. Hence, using the same parameters is not an efficient way of implementing SBFD. Legacy procedures should be enhanced specific to SBFD to handle such cases and implement SBFD in an efficient way. Subband full duplex (SBFD) is a technique using which a wireless communication node can perform transmission and reception simultaneously in the time domain but in different frequency resources within the same band. The separate frequency resources for transmission and reception are known as subbands (SBs). E.g., a gNB or a base station (BS) in New Radio (NR) technology capable of SBFD is able to perform uplink (UL) and downlink (DL) at the same time but in different SBs which are non-overlapping with each other. The user equipment (UE) filing version an,rm FH241001PEP 2024P67397EP 10 can be half duplex (HD) capable, that is it performs UL and DL in orthogonal time frequency resources. Note, that a physical resource block, PRB, related to the actual transmitted signal, which may be located relative to a reference point A on a given resource grid. For this, the reference point A coincides with subcarrier 0 of common resource block, CRB, 0 for all subcarrier spacings. The resource grid may consist of a number of subcarriers, e.g., 12 subcarriers in frequency domain, and a number of OFDM symbols in time domain. In general, a PRB is defined by a start subcarrier, a number of subcarriers, and a subcarrier spacing, defined by the numerology. The numerology sets the subcarrier spacing and is defined per bandwidth part, BWP. The resource blocks are aligned across numerologies, such that two resource blocks at a subcarrier spacing s, occupy the same frequency range as one resource block at a subcarrier spacing of 2s. Furthermore, we may use resource block and physical resource block interchangeably. Finally, also the term virtual resource block, VRB, may be used, which contain the modulation symbols that are mapped to the PRBs in the bandwidth parts used for transmission. Note that VRBs may be mapped interleaved or non-interleaved to the PRBs, depending on the configuration. The discussion on implementation of SBFD at the gNB in NR with HD UEs in the network was initiated during the Release 18 Study Item phase. In Release 19, the Work Item Phase was initiated with the objective of discussing enhancements at the gNB and the user equipment (UE) side for the implementation of SBFD. Fig. 3 shows an SBFD configuration in time and frequency domain. Slot 0 is a DL slot, slots 1-3 are SBFD slots and slot 4 is an UL slot. D and U are DL and UL respectively. The SBFD slots shown in Fig.3 have the configuration of UD, where D is the DL SB and U is the UL SB. The frequency domain configuration can also be DU instead of UD. In this illustration, the slot is said to be SBFD since all the symbols in the slot have DL and UL SBs. A symbol will be called an SBFD symbol if it is configured with DL and UL SBs. There is a guard band in between the D and U SBs to mitigate the effect of interference from the UL SB to the DL SB. The presence of the guard band depends on the implementation at the gNB. Thus, any slot / symbol which has the DL and UL SBs configured in frequency domain are known as the SBFD slots / symbols. Similarly, the only DL slot (slot 0) and the only UL slot (slot 4) are known as the non-SBFD slots since they are not configured with SBs. Also, any symbol which is not configured with such SBs are known as SBFD symbols. Fig. 4 shows another SBFD configuration where the SBFD slots have DUD configuration in frequency domain. In this case, there can be 2 guard bands between the SBs. filing version an,rm FH241001PEP 2024P67397EP 11 Fig.3 exemplarily depicts a schematic representation 300 of a resource allocation in a wireless communication network, in accordance with embodiments. The resource allocation is described using a time-frequency grid. Here the horizontal direction denotes the time domain and the vertical direction denotes the frequency domain. In particular, Fig. 3 presents an example of SBFD configuration in time and frequency domain with DU. The time slots 3200-4,, i.e. slots numbered from 0 to 4, for resource allocation in the wireless communication network are shown. The time slots are shown to have equal slot lengths (e.g. slot duration). For example, each of the time slots may comprise a plurality of symbols usable (e.g. available) for the resource allocation. The time slots may each be allocated a portion or a whole of available frequency resources (e.g. available frequency spectrum, or available bandwidth). For instance, the time slots may be associated with a resource block, RB, or a frequency unit comprising a plurality of subcarriers. A first subset of the time slots may be associated with a band configured for signalling or communication in a specific link direction. For example, the time slot 0 may be associated with a band 330Dthat may be used for downlink, DL, denoted in the Fig.3 as D, and the time slot 4 may be associated with a band 330Uthat may be used for uplink, UL, denoted in the Fig.3 as U. Further, a second subset of the time slots may be associated with one or more sub-bands configured for signalling or communication in specific (e.g. pre- determined, pre-configured, certain) link directions (e.g. two or more specific link directions, or a plurality of link directions). For example, the time slots 1-3 may each be associated with two sub-bands 340D, 340Uthat may be used for downlink and uplink respectively. Thus, the one or more sub-bands within the single time slot allow for a full-duplexing configuration for the resource allocation in the wireless communication network. The one or more sub-bands 340 may be a portion (e.g. a smaller portion, a sub-portion, a slice) of the band 330 in the frequency domain. Although the one or more sub-bands could be overlapping, they are shown to be non- overlapping (e.g. orthogonal) in Fig.3. The time slots with bands may be referred to as non-SBFD slots while the time slots with sub- bands may be referred to as SBFD slot. The example described here therefore concerns a scenario wherein the first subset of the time slots are SBFD and the second subset of the time slots are non-SBFD. The SBFD time slots 3201-3may have the DU configuration. Here DU is specified in an order of increasing frequency values, although it could easily be referred to as UD if specified in an order of descending frequency values. The SBFD time slots may additionally comprise one or more guard bands 335. As depicted in Fig.3, the D sub-band and the U sub-band may be adjacent to a single guard band 335. That is, the guard band (e.g. one or more guard bands) may be in-between or arranged between filing version an,rm FH241001PEP 2024P67397EP 12 the sub-bands. The SBFD time slots may comprise a larger number of guard bands. Thus, it may be that one or more sub-bands and the guard bands may contiguously span a frequency bandwidth or frequency spectrum associated with the band. It is noted that the guard band may be optional, their presence (e.g. their configuration) may reduce possible interference associated with sub-bands of different (e.g. opposite) link directions. Therefore, in the absence of the guard bands, the sub-bands may themselves contiguously span or cover the frequency bandwidth or frequency spectrum associated with the band. A device such as UE operating in (e.g. belonging to, or served by any number of network entities belonging to) the wireless communication network may be provided or made aware of the availability or usability (e.g. by a network entity such as base station / gNB of the wireless communication network) of a portion (e.g. a subset), or a whole, of the frequency resources within a time slot. In Fig.4, this portion is depicted as a bandwidth part, BWP. For instance, the UE could use the BWP in each of the time slots 3200-4for DL (e.g. could also be UL). This BWP may be referred to as a DL BWP 342D. The resources within (e.g. or enclosed by) the DL BWP may be referred to as available DL resources. That is, the DL BWP 344Dmay be the set of frequency resources available (e.g. usable, or allowable for use, or not strictly forbidden from use) to the UE for DL signalling or communication with the corresponding time slot. In other words, the DL BWP 344D may be the set of frequency resources available (e.g. usable, or allowable for use, or not strictly forbidden from use) to the BS or a network entity for allocating DL signalling or communication within the corresponding time slot. In regard to the DL BWP within the SBFD time slots 3201-3, the DL BWP may span (e.g. extend, or range) from one sub-band to another sub-band. As shown in Fig.3, the DL BWP may overlap with the DL sub-band, the guard band and the UL sub-band. Since the BWP may be attributed to a single link direction (e.g. DL here), there may be no available resources, by virtue of being restricted or forbidden for signalling or communication, within the sub-band with a link direction being opposite to the single link direction. Therefore, the resources pertaining to DL BWP in the U- subband may not be available for DL signalling or communication. As previously described, in additional examples, the BWP may relate to UL and / or sidelink. Although here the BWP is same across the time slots, it could be that the BWP may be changed or adjusted depending on the time slot. In addition to the above described details, Fig.3 depicts allocated frequency resources 348 in each time slot 3200-4. The allocated frequency resources 348 may be the resources which may be allocated (or provided) by the network entity (e.g. BS / gNB) of the wireless communication network to one or more devices, such as UEs. By this measure, the devices, such as the UEs, could be informed (or signalled or communicated to) of the frequency resources allocated for the resource allocation. That is, the devices may be aware of which frequency resources to filing version an,rm FH241001PEP 2024P67397EP 13 use for determining and performing the resource allocation. In regard to the SBFD time slots, the allocated frequency resources 348 may overlap with the sub-bands and the guard bands, while in regard to the non-SBFD time slots, the allocated frequency resources 348 may be within the BWP 342. The allocated frequency resources 348 are depicted as having same dimensions in the time and frequency domains across each time slot. However, this may not be the case, the dimensions of the allocated frequency resources could be different across different time slots (e.g. which could further be based on a time slot being a SBFD or a non- SBFD one). Thus, it is feasible that the allocated frequency resources 348 may overlap differently within sub-bands, and if present guard bands, in SBFD time slots. Details and concepts in regard to Fig. 1 described so far are readily transferable onto other examples and / or embodiments, such as relating to configurations and / or other time frequency occasion, described further in this disclosure in a manner so as to be configured to apply such details and concepts onto these examples and / or embodiments in combinations as alternatives or additions. For the sake of brevity and conciseness of this disclosure, such details and concepts are not repeatedly explained or described. Fig.4 exemplarily depicts a schematic representation 400 of a resource allocation in a wireless communication network, in accordance with embodiments. In particular, Fig. 4 presents an example of another SBFD configuration in time and frequency domain with DUD. In contrast to Fig. 3, Fig. 4 depicts each SBFD time slots 4201-3, 428 being associated with three sub-bands 440 in a DUD configuration. That is, the SBFD slots may each comprise two DL SBs 440D1, 440D2 and a single UL SB 440U. Two guard bands 4351, 4352 are in-between or arranged between the sub-bands 440. Other arrangements involving a larger number of sub-bands and guard bands are feasible; in this regard, Fig.4 is an instantiation of such an arrangement. In NR, the gNB allocates UL and DL bandwidth parts (BWPs) to the UE to perform UL and DL respectively. The UE is expected to transmit UL within the UL BWP and receive DL within the DL BWP. Only one BWP can be active at a time, each for DL and UL. Since the UE is HD capable, it can either receive in DL or transmit in UL in the SBFD slots. Further, any frequency domain resource allocated to the UE using, for example, a frequency domain resource allocation (FDRA) message for DL / UL provided by the gNB to the UE for any signal / channel will be restricted to the DL BWP or UL BWP respectively of the UE. There are various signals or channels in NR which are periodic or repetitive in nature. E.g., physical downlink shared channel (PDSCH) and physical uplink shared channel (PUSCH) with repetition, semi- persistent scheduling (SPS) for DL, Configured grant (CG) for UL, multi-PDSCH, multi- filing version an,rm FH241001PEP 2024P67397EP 14 PUSCH, Transport block over multiple slots (TBoMS) for UL etc., which are configured by the gNB in a way that a single FDRA is provided for all the occasions. A single FDRA means that the same frequency domain resources will be used to transmit / receive the signal / channel for every occasion of transmission or reception. If this existing procedure is followed when the gNB is enabled with SBFD, a single FDRA will be provided by the gNB which is within the DL BWP and valid for all SBFD and non-SBFD symbols. An example is shown in Fig.3. A DL BWP is shown allocated for the slots 0-3. The size and location of the BWP are same across the slots. In the SBFD slots, the DL BWP overlaps with the UL SB and the guard (if allocated by the gNB). Since the UL SB is strictly restricted for UL transmissions, DL receptions are not allowed in the UL SB. Thus, in the SBFD slots, the number of available DL resources for actual reception are fewer as compared to the DL or non- SBFD slots. Further, the frequency domain resources allocated are within the DL BWP but they overlap with the UL SB in the SBFD slots. As the UE is not allowed to receive DL in the UL SB, the UE cannot receive any DL in the allocated frequency resources provided by the gNB in the SBFD symbols where it overlaps with the UL SB. E.g., the gNB configures SPS to the UE using the SPS-Config parameter in Radio Resource Control (RRC) in NR. Multiple SPS configurations are allowed for a single UE with different SPS Configuration indices (SPS-ConfigIndex in SPS-Config). For each SPS configuration, parameters like periodicity, number of hybrid automatic repeat request (HARQ) processes, HARQ Process ID offset etc. are provided. Within the given periodicity, the SPS might also be configured to be repeated based on the given number of repetitions. The SPS is activated using downlink control information (DCI) like DCI 1_1 which provides the FDRA and the time domain resource allocation (TDRA). Also, other parameters like modulation and coding scheme (MCS) are provided by the DCI. The activation DCI is also linked to a corresponding SPS-Config index of the SPS it wants to activate by the HARQ process number field. This field contains the SPS-Config index of the SPS to be activated. The HARQ process ID / number for each SPS-ConfigIndex is calculated based on number of HARQ processes and HARQ process ID offset. Multiple such SPS-Configs can be configured to the UE and activated / deactivated using DCI. The same HARQ process number field is used in the deactivation DCI as well. For all the SPS occasions, this same FDRA and TDRA configuration is used by the UE. Fig.5 shows different SPS occasions in every slot from slot 0 to slot 4. In slots 1-3, the SPS time frequency resources overlap with the UL SB. The UE either ignores the SPS occasions in the SBFD slots or can only receive in the available DL resources. Further, the gNB can provide separate FDRA configurations for SBFD symbols that do not overlap with the UL SB. filing version an,rm FH241001PEP 2024P67397EP 15 Similar issues will be prevalent in other signals / channels mentioned previously as examples as well. Thus, the reception procedures for various channels / signals need to be enhanced to accommodate such scenarios. Fig.5 exemplarily depicts a schematic representation 500 of a resource allocation in a wireless communication network, in accordance with embodiments. In particular, Fig. 5 presents an example of the resource allocation being periodic, or repetitive. As depicted in Fig. 5, the resource allocation could be a semi-persistent scheduling, SPS, across non-SBFD slots 5400,, 5404, 528 both exemplarily being configured for downlink, and non-SBFD slots 5401-3, 524 with the sub-bands being configured in DU configurations. Different SPS occasions 5500-5in the different slots 5200-5are depicted. For instance, it may be that the SPS occasions are configured for a specific link direction, such as DL. On one hand, the UE may receive resources associated with (e.g. allocated for) the SPS occasions 5500, 5504 in non-SBFD slots configured for the specific link direction, D, while on the other hand, the UE may receive a portion or part of the resources associated with (e.g. allocated for) the SPS occasions 5501-3 in SBFD slots 5201-3 for the specific link direction, D, wherein the portion or part of the resources may relate to the sub-band configured for the specific link direction, D. Alternatively, the UE may ignore the SPS occasion in the SBFD slots altogether. A part, or portion, 555 of the SPS occasion 550 which may overlap with the sub-band with an opposite link direction, here U, is also shown. Embodiments will be described further in the disclosure relating to determination of the resource allocation and the resource allocation depending on an occasion and its dependency on SBFD configurations. The next section discusses the detailed issues and solutions with SPS as an example. However, the technical solutions provided here can be applied in general to other signals / channels in UL and DL and / or in sidelink. With regards to embodiments described herein, there is made reference to subband full duplex, SBFD, which may be defined as time-frequency occasions where the uplink, UL, is happening in one or more UL subbands and downlink is happening in one or more DL subbands, in the same time resources and wherein each subband is within the system bandwidth, wherein the configuration may vary over time, e.g., for different slots or other time domain units. Subbands used for UL and subbands used for DL may be non-overlapping or may be overlapping partially or completely in the frequency domain. Note, although embodiments within this application are defined with respect to a downlink or uplink transmission, they may also be applied to other filing version an,rm FH241001PEP 2024P67397EP 16 type of communication such as a sidelink communication. In sidelink two or more UEs may communicate directly with and without coordination by a BS and / or network depending on the operational mode, e.g., mode 1 under control of a BS, mode 2, direct communication between devices. In connection with the described invention, it may be assumed that each subband has a bandwidth being smaller than the entire system bandwidth. The system bandwidth can be considered as a component carrier or an aggregation of several component carriers. Furthermore, the UL subband or the DL subband can be within a band or bandwidth part, BWP, which is operated in TDD or FDD mode, as paired of unpaired spectrum bands. A device in accordance with the present invention may operate on resources in a DL subband or the UL subband or a combination thereof, wherein said operation may be simultaneously or consecutively. In some examples, the device may use one or more occasions at a same time in UL and DL. Some devices described hereinafter relate to and make use of SBFD slots and / or SBFD symbols. Note, that the embodiments described in this invention are not limited to a slot or symbol time definition and may be defined as a radio frame, e.g., 10ms radioframe, a half- frame, e.g., of 5ms, a subframe or a slot or half-slot. Here, a subframe may comprise of one or more slots. SBFD slots and SBFD symbols may be considered as examples of an SBFD time-frequency occasion making reference exceeding the time domain consideration of TDRA applied to the FDRA by implementing a possible specific structure that is, however, not obligatory to benefit from at least some of the embodiments described herein. For examples, the advantageous modifications allowing to handle synchronous availability of UL resources and downlink resources may also applied in absence of a frame-, slot- and / or symbol-structure although such a structure is widely used. Equal or equivalent elements or elements with equal or equivalent functionality are denoted in the following description by equal or equivalent reference numerals or annotation / labeling even if occurring in different figures. In the following description, a plurality of details is set forth to provide a more thorough explanation of embodiments of the present invention. However, it will be apparent to those skilled in the art that embodiments of the present invention may be practiced without these specific details. In other instances, well known structures and devices are shown in block diagram form rather than in detail in order to avoid obscuring embodiments of the present filing version an,rm FH241001PEP 2024P67397EP 17 invention. In addition, features of the different embodiments described hereinafter may be combined with each other, unless specifically noted otherwise. SPS Configuration across SBFD and non-SBFD Symbols This section describes the various issues and related solutions for SPS configuration across SBFD and non-SBFD slots / symbols. Same frequency domain resources for SBFD and non-SBFD symbols In this case, the same frequency domain resources are provided by the gNB to the UE for both SBFD and non-SBFD symbols. As shown in Fig.6, slot 1 is a non-SBFD slot and slot 2 is an SBFD slot. The SPS resources in frequency domain for both the slots are the same. Fig.6 exemplarily depicts a schematic representation 600 of a resource allocation for SBFD and non-SBFD slots in a wireless communication network, in accordance with embodiments. In particular, Fig. 6 presents an example of same frequency resources for SBFD and non- SBFD time-frequency occasions. Fig.6 exemplarily depicts two consecutive time slots, a first slot 6201being a non-SBFD slot 624 and a second slot 6202being a SBFD slot 628, using a time-frequency grid. The SBFD slot 6202, 628 is shown in a UD configuration (or DU configuration, if a direction of increasing frequency is chosen). The SBFD slot may be configured with an UL SB 640U, a DL SB 640Uand a guard band 635 between them. The device may be adapted (e.g. indicated, signalled, communicated, or instructed) to determine the resource allocation, here SPS, for allocating resources. The UE may be provided information on a determination result, wherein the determination result concerns whether the resource allocation, e.g. SPS occasions 650, are within a SBFD slot. Such configurations of the UE could be performed by any network entity (such as a BS) of the wireless communication network may indicate (e.g. signal, communicate, or instruct) to the device (e.g. UE) to determine the resource allocation for allocating resources. For example, the BS could assist (e.g. help) by way of signals or messages or communication the device to determine the resource allocation. These signals or messages or communication could thus assist (e.g.) by way of signals or messages or communication he device (e.g. UE) in obtaining the determination result. The UE may be indicated (e.g. signalled, communicated, or instructed) to use the same frequency domain resources across SBFD slots 628 and non-SBFD slots 624. The UE could be indicated or assisted in determining that slot 26202is a SBFD slot 628. As a result, the SPS occasion 6502may be used by the UE in accordance with it being in a SBFD slot. In the filing version an,rm FH241001PEP 2024P67397EP 18 example of Fig.6, the UE may use determine a same result for using the SPS occasion across both SBFD 628 and non-SBFD slots 624. Here the same result being same frequency domain resources for both SBFD 624 and non-SBFD slots 628. The signalling or communication or instructions provided to the UE could be performed by any network entity of the network. Further, the device (e.g. UE) could receive the SPS occasion 6501as being valid for the non- SBFD slot, i.e. slot 1 and as being valid for the SBFD slot, i.e. slot 2. By this measure, the UE may be made aware that the resource allocation (here SPS occasion, but may be any resource allocation associated with any link direction) is allowable and could be used for both SBFD and non-SBFD slots alike. E.g., a single FDRA is provided to the UE by the activation DCI for SPS used for SBFD and non-SBFD symbols. This is shown in Fig.7. Fig.7 exemplarily depicts a schematic representation 700 of a resource allocation for SBFD and non-SBFD slots in a wireless communication network, in accordance with embodiments. In particular, Fig.7 presents an example of a single FDRA in activation DCI associated with SPS for SBFD and non-SBFD time-frequency occasions. The device (e.g. UE) may determine the resource allocation using a scheduling information. The scheduling information may indicate an allocation of frequency domain resources. This allocation could relate to a unit of the frequency domain resources, such as a bandwidth part, BWP, or at least one sub-band of the wireless communication network. The scheduling information may be a single scheduling information that may be provided or communicated to the device. The device may determine for each of a plurality of time-frequency occasions whether the resource allocation allocates resources to an SBFD time-frequency occasion or a non-SBFD time-frequency occasion. For example, the scheduling information may be a frequency domain resource allocation, FDRA. For example, the resource allocation could be provided to the device by an activation downlink control information, DCI. This may be the case for SPS, as depicted in Fig.7. The activation DCI with a single FDRA is depicted as a portion, or part, 760 of a non-SBFD slot 620n, 624, i.e. slot n. The slot n 620nmay be arranged earlier relative to slot 16201, 624 and slot 26202, 628. By virtue of reception of the activation DCI with single FDRA 760, the UE may use SPS in non-SBFD slots 624 and SBFD slots 628. As exemplarily depicted, the UE may be informed to use SPS 750 in a same manner for both SBFD and non-SBFD slots. That is, the SPS 750 may be valid for occasions in both SBFD and non-SBFD slots. filing version an,rm FH241001PEP 2024P67397EP 19 There might be a case where one occasion of the SPS falls across both SBFD and non-SBFD symbols. This is shown in Fig.8. In such a case, the UE either ignores that SPS occasion or the UE treats all the symbols in that occasion to be of a particular type. E.g., if at least ‘n’ number of symbols in the occasion are SBFD symbols then, all the symbols in that occasion are treated as SBFD symbols. The number n can be defined in the specification or provided by the gNB. Further, for example, when the non-SBFD symbols are treated as SBFD symbols, the same DL resources used for SPS reception in the SBFD symbols are used for SPS reception in the non-SBFD symbols as shown in Fig.8. Fig.8 exemplarily depicts a schematic representation 800 of a resource allocation for SBFD and non-SBFD symbols, in accordance with embodiments. In particular, Fig. 8 presents an example of a single SPS occasion spanning across SBFD symbols and non-SBFD symbols. The time-frequency occasion spanning 14 symbols 8220-13constituting a single time slot is exemplarily shown. While some symbols 8220, 8221-5may be associated with non-SBFD configurations, some symbols 8226-13may be associated with SBFD configurations. The symbols with non-SBFD configurations are depicted for downlink. The symbols with SBFD configurations as depicted comprise a plurality of sub-portions occupying different frequency resources, such as BWP. For instance, the SBFD symbols comprise a first sub-portion for downlink which is adjacent to a guard band and a second sub-portion for uplink which is adjacent to the same guard band. That is, the first sub-portion and the second sub-portion may have the guard band between them in the frequency domain. It may be that parts, or portions, of some non-SBFD symbols 8221-5and SBFD symbols 8226-11be muted or blanked. That is, parts and portions of the OFDM symbols 822#may not be used for UL, DL or SL. The resource allocation being SPS could occur for, or overlap across, multiple symbols. In the scenario of Fig. 8, the SPS occasion may be present across SBFD symbols and non-SBFD symbols. The resources 852 in DL which may be used for SPS reception are shown. The resources 852 are the same for SBFD and non-SBFD symbols. In accordance with embodiments, the device (e.g. UE) may be configured to ignore UL resources of a SBFD time-frequency occasion for a DL transmission that uses resources of the resource allocation. This may be the case for SPS. For example, the UE may ignore or suppress or forbid the UL transmission in resources which may have been configured for UL in the sub-portion of OFDM symbols. By this measure, the resource allocation, such as SPS without limiting other instances, may be performed in an efficient manner. filing version an,rm FH241001PEP 2024P67397EP 20 Further, the device may be configured to ignore DL resources of a SBFD time-frequency occasion for a UL transmission that uses resources of the resource allocation. In such cases, the resource allocation may be configured for UL transmissions. A first time-frequency occasion 8521of the resource allocation, SPS, may overlap with one or more SBFD symbols 8226-11of a SBFD time-frequency occasion. A second time-frequency occasion 8522of the resource allocation, SPS, may overlap with one or more non-SBFD symbols 8222-5. The device, e.g. UE, consider or treat all symbols of the first time-frequency occasion to be of a particular type, that is, either a SBFD type or a non-SBFD type. Further, the device, e.g. UE, may determine a number of symbols in the first time-frequency occasion 8521to either of SBFD type or of non-SBFD type depending on the number. If the number exceeds a threshold, the device may treat all symbols in the first time-frequency occasion 8521 as SBFD symbols. If the number does not exceed the threshold, the device may treat all symbols in the first time-frequency occasion 8521 as non-SBFD symbols. This threshold, e.g. number n, may be pre-defined (e.g. preconfigured or predetermined) or could be signalled by the wireless communication network (e.g. a BS). The device, e.g. UE, may treat non-SBFD symbols in the same way as SBFD symbols using a determination of the number of symbols. The device may use the same DL resources used for reception in the SBFD symbols for reception in the non-SBFD symbols in accordance with the resource allocation, e.g. SPS. MCS determination As explained in Fig.3, the available DL resources for the UE to receive the SPS is fewer in SBFD slots as compared to non-SBFD slots. This is also shown in Fig.9. Also, the presence of cross link interference (CLI) in the SBFD symbols make the interference conditions worse in an SBFD symbol as compared to a non-SBFD symbol. Hence, the DL MCS for the SPS in SBFD symbols can be reduced as compared to a non-SBFD symbol. As shown in Fig.9, the SPS in slot 1 (non-SBFD slot) uses MCS1 whereas the SPS in slot 2 (SBFD slot) uses MCS2. Fig.9 exemplarily depicts a schematic representation 900 of a resource allocation for a non- SBFD slot and a SBFD slot, in accordance with embodiments. In particular, Fig.9 presents an example of different MCS for resource allocation in SBFD and non-SBFD time-frequency occasions. The resources allocated for SPS in the non-SBFD time-frequency occasion associated with slot 1 may be the same, in terms of size in time domain and frequency domain, as the resources allocated for SPS in the SBFD-time frequency occasion associated with slot 2. Since filing version an,rm FH241001PEP 2024P67397EP 21 the non-SBFD occasion may be configured for SPS reception using DL, or D while the sub- band adapted for DL may be configured for SPS reception in the SBFD occasion, the resources available in DL for SPS reception in the non-SBFD and SBFD occasion may be different. For example, the resources available in DL for SPS reception are fewer in the SBFD occasion relative to the non-SBFD occasion. Therefore, the UE may use different modulation schemes for SBFD and non-SBFD occasions, or for respective symbols in the SBFD and non-SBFD occasions. Therefore, the device may achieve an efficient use of modulation schemes across different time-frequency occasions. As depicted in Fig.9, a whole of the resources available for SPS reception in the non-SBFD occasion 9201may be used by the device (e.g. UE) with a first MCS 9541, and a whole of the resources available for SPS reception in the SBFD occasion, within the sub-band for DL, may be used device (e.g. UE) with a second MCS 9542, wherein the second MCS 9542is different from the first MCS 9541. The device may thus receive explicit information indicating that different MCS be used across different time-frequency occasions, or symbols thereof. The different MCS may be received as a combined value or distinct (e.g. separate) values. Additionally, or alternatively, the device may decode the explicit information indicating that the different MCS be used across different time-frequency occasions, or symbols thereof. The different MCS may be decoded as a combined value or distinct (e.g. separate) values. The explicit information may be provided by the network entity (e.g. BS) to the device (e.g. UE). For instance, the device may receive two or more DCIs. A first DCI may comprise a first MCS value. The first MCS value may indicate the first MCS, e.g. MCS19541. A second DCI may comprise a second MCS value. The second MCS value may indicate the second MCS, e.g. MCS2 9542. The first DCI and the second DCI may each comprise a time domain resource allocation, TDRA. The device may decode the first DCI and the second DCI and may determine an association of TDRA with SBFD and non-SBFD symbols. That is, the device may determine which TDRA corresponds to SBFD symbols and which TDRA corresponds to non- SBFD symbols. The device may determine which of the two or more DCIs contain the TDRA associated with SBFD symbols. This determination may be performed by determining which TDRA overlaps with a SBFD symbol of a SBFD frequency-time occasion. For instance, the first DCI and the second DCI may be associated to (e.g. linked to) a plurality of SPS-Config index values indicating SPS-Config indices of separate SPS-Configs. The first SPS-Config index may correspond to SBFD symbols of SBFD time-frequency occasion. The second SPS-Config index may correspond to non-SBFD symbols of non-SBFD time-frequency occasion. For example, a SBFDIndicator parameter of one bit may form a part of the SPS Config. Depending on the value of the SBFDIndicator parameter, the SPS-Config index may be associated to filing version an,rm FH241001PEP 2024P67397EP 22 SBFD symbols or non-SBFD symbols. For example, if the SBFDIndicator parameter is set to 1, then the SPS-Config index may be for SBFD symbols while the SBFDIndicator parameter being set to 0, then the SPS-Config index may be for non-SBFD symbols, or vice versa. The first DCI and the second DCI may each comprise an indicator indicating whether the indicator may be related or associated to the SBFD symbol of the SBFD time-frequency occasion or non-SBFD symbols of the non-SBFD time-frequency slot. For example, the indicator may be indicated using at least one unused, or reserved, DCI bit. The unused or reserved nature of the DCI bit may be in accordance with a legacy NR standard. For example, it could be that the device may decode the first DCI and the second DCI and may associate a lower MCS value among the first and the second MCS values with SBFD symbols of the SBFD time-frequency occasion. Further, the device may be provided or receive, for instance from a BS, or gNB, a single DCI. The single DCI may indicate the first MCS and the second MCS using at least one unused, or reserved, DCI bit. The unused or reserved nature of the DCI bit may be in accordance with a legacy NR standard. The device may interpret a parameter in a configuration message for indicating whether a second MCS value for the SBFD symbols will be provided or not. That is, the device may determine that the provision of the second MCS value for the SBFD symbols will depend on the value of the parameter in the configuration message. For example, the parameter may be a one-bit field, such as SecondMCS in RRC. A field used for providing the MCS for a second transport block, TB, in DCI may be used to provide (e.g. send, transmit) the MCS for SBFD symbol of the SBFD occasions. The MCS values described previously may be in accordance with or determined (e.g. derived) using a reference MCS table supported by the wireless communication network. The reference MCS table may be a single MCS reference table. Alternatively, the MCS values may be in accordance with or determined (e.g. derived) using a plurality of MCS reference tables. Different MCS tables may be indicated or chosen for SBFD and non-SBFD symbols. The MCS table associated with the SBFD symbols may be derived from the same MCS reference table used for deriving or obtaining the non-SBFD symbols. For example, a parameter for reference to the same MCS reference table in SPS-Config may be used. Alternatively, the MCS values, i.e. the first and the second MCS values, associated with the SBFD symbol may be determined using, or derived from, a different MCS reference table than the MCS reference table used for the non-SBFD symbols. For example, the different MCS reference table may be a low spectral efficiency and code rate MCS table specified in existing standards. The MCS reference table for the non-SBFD symbols may be provided by a parameter, mcs-Table, in SPS-Config and the MCS reference table for the SBFD symbol may filing version an,rm FH241001PEP 2024P67397EP 23 be provided to the device by a different parameter, compared to mcs-Table, in SPS-Config or in RRC. A plurality of parameters, e.g. a first and a second parameter, for non-SBFD and SBFD symbols may be provided in SPS-Config or in RRC. For instance, the MCS reference table for the SBFD symbols may be provided in PDSCH-Config as a new parameter. This new parameter may be used in conjunction either with the existing parameter, mcs-Table, in SPS- Config for non-SBFD symbols or with another new parameter in PDSCH-Config for non-SBFD symbols. It may be that the MCS reference tables for both SBFD and non-SBFD symbols may be indicated in PDSCH-Config either using new parameters or using existing parameters. Although the UE may be provided MCS values in an explicit manner, alternatively, in accordance with embodiments, the UE may implicitly derive information indicating the first MCS and / or the second MCS. For instance, the UE may derive the MCS value for a SBFD symbol of the SBFD occasion based on (e.g. directly using, or indirectly using) the MCS value, or one or more MCS values, for the non-SBFD symbol(s) of the non-SBFD occasion(s). It may be that the device derives the MCS value(s) for the SBFD symbol based (e.g. directly using, or indirectly using) on a report provided (e.g. signalled, or communicated) to the wireless communication network. In this regard, the device may respond to a request of the base station, gNB, with a feedback, such as by way of one or more feedback messages. The feedback may be provided (e.g. signalled, or communicated) using higher layer signalling such as RRC or MAC. The feedback may be one or more parameters associated with interference in the wireless communication network. The one or more parameters associated with the interference may be at least one of: parameters related to interference (e.g. SINR), channel state related parameters for SBFD symbols, and channel state related parameters for non- SBFD symbols. The device (e.g. UE) may derive the MCS value for the SBFD symbol using the parameter related to interference such as SINR. Additionally, or alternatively, the device could derive the MCS value for the SBFD symbol using any other channel state related parameter for SBFD and non-SBFD symbols. The device could derive the MCS value for the SBFD symbol depending on, or using, a difference of the one or more parameters associated with the interference. The difference between parameters related to SINR and any other channel state related parameters for SBFD and non-SBFD symbols may be used by the device for deriving the MCS value. The device may derive the MCS value using a pre-configured formula involving the parameters relates to SINR and any other channel state related parameters for SBFD and non-SBFD symbols, and / or their differences, and / or their sums. It could be that device may derive the MCS value for the SBFD symbol based on a look up table relating the MCS value to different values of the one or more parameters associated with the interference. filing version an,rm FH241001PEP 2024P67397EP 24 The device may derive at least one parameter based on the MCS value to be applied (or used) for the SBFD symbols. For example, it could be that the device may calculate the MCS value based on the SINR of SBFD symbols. The device may directly report this value, for instance, to the BS, or gNB. The device may be provided, or made aware, of a baselines MCS value. The device could derive an MCS offset value by determining (e.g. deriving, estimating, or calculating) the MCS value for SBFD symbols and its offset relative to the baseline MCS value. In this regard, an offset may be a relative shift, or a difference. The device may then report the MCS offset value as the feedback to the BS, or gNB. The device may receive the resource allocation, SPS as exemplarily described, in one or more SBFD symbols with a same MCS value. The same MCS value may be determined (e.g. obtained) by the device. This determination, for instance, could be based on signalling received from the gNB. For instance, the determination of the same MCS value could be based on an acknowledgement, ACK, wherein the acknowledgement acknowledges the calculated MCS value. For example, the ACK bit being set to 1, the UE may be instructed, or made aware of, using the determined same MCS value; the ACK bit being set to 0, the UE may be made aware of a further reception of a different MCS value than the determined same MCS value. The device may then use the different MCS value once received from the gNB. The device may send a feedback to the gNB provided one or more conditions are fulfilled. As an example, if the difference between MCS values of SBFD and non-SBFD symbols is greater than a specific threshold, then the device may report the feedback related to the implicit derivation of the MCS value to the gNB. The specific threshold may be pre-configured, as specified in legacy standards, or could be provided, and hence configured, by the gNB to the UE. The device may use assistance information from the gNB for determining the MCS value for SBFD symbols. For instance, the assistance information may be information relating to the interference associated with the SBFD symbols. The device may then determine (e.g. calculate) the MCS value based on this information relating to the interference and report the determined MCS (e.g. calculated MCS) as the feedback to the gNB. It may be that the MCS values are provided or indicated to the UE in terms of a set of positions of values in the reference MCS table. The UE could receive a row number of the reference MCS table for provision or indication of MCS values for non-SBFD symbols. The UE may then derive the MCS value for the SBFD symbols based on a pre-configured MCS offset value and the MCS values for non-SBFD symbols. The device may obtain the MCS offset value as provided or indicated in one or more messages (e.g. SPS-Config, and / or configuration filing version an,rm FH241001PEP 2024P67397EP 25 messages of other possible resource allocations). The device may use the MCS offset value as provided or indicated the messages and the MCS values for non-SBFD symbols to derive or determine the MCS values for SBFD symbols. Alternatively, the device may use the MCS offset value as provided or indicated the messages and the MCS values for SBFD symbols to derive or determine the MCS values for non-SBFD symbols. Although Fig. 9 exemplarily depicts SBFD and non-SBFD time-frequency occasion, details described may be adapted so as to be transferred onto SBFD and non-SBFD symbols. Further, details which have been described in regard to SBFD and non-SBFD symbols may be adapted so as to be transferred onto SBFD and non-SBFD occasions. Currently in NR, there is only one mcs-Table provided in the SPS-Config for a single SPS- Config index which informs the UE which MCS table to refer to in the NR specifications. A single value from this MCS table is provided by the activation DCI to the UE. This MCS is used for all SPS occasions. This procedure can be enhanced in various ways to determine different MCS values for SBFD and non-SBFD symbols. 1. Explicit indication of MCS value for SBFD symbols ^ In this method, the gNB explicitly indicates the MCS values for SBFD and non-SBFD occasion. This is done in the following ways. ^ The gNB provides two separate DCIs, one for SBFD and the other for non-SBFD symbols containing 2 separate MCS. The UE needs to differentiate the DCI for SBFD symbols from the DCI for non-SBFD symbols. This can be done in the following ways. o If both the DCIs contain TDRA, the UE can decode them and check which TDRA corresponds to which type of symbols. If the TDRA overlaps with SBFD symbols, then the DCI containing the TDRA is for SBFD symbols. o The two DCIs are linked to 2 different values of SPS-Config indices in separate SPS-Configs. One SPS-Config index corresponds to SBFD symbols while the other corresponds to non-SBFD symbols. E.g., there is an SBFDIndicator parameter of one bit in the SPS-Config. For a particular SPS-Config index, if this parameter is set to 1, then the SPS-Config index is for SBFD symbols and otherwise for non-SBFD symbols. o The two DCIs contain an indicator in each one of them that indicates whether it is for SBFD or non-SBFD symbols using the unused / reserved filing version an,rm FH241001PEP 2024P67397EP 26 DCI bits. The unused DCI bits can be bit fields in the DCI not required for SPS in the current NR standards. o The UE decodes the two DCIs and the DCI with the lower MCS value is always considered as the DCI for SBFD occasion. ^ In another method, the gNB provides a single DCI to provide the 2 MCS values using the unused / reserved DCI bits. The unused DCI bits can be bit fields in the DCI not required for SPS in the current NR standards. o A parameter in the SPS-Config or in RRC can be used to indicate to the UE whether a second MCS value for the SBFD symbols will be provided to the UE or not. E.g., if a one bit field called SecondMCS in RRC is set to one, then the UE expects to receive an MCS value for SBFD symbols in the DCI. Otherwise, if it is set to one or the field is absent, the UE uses the same MCS for SBFD and non-SBFD symbols. o The field used for sending the MCS for a second transport block (TB) in DCI is used to send the MCS for SBFD symbols if SBFD is configured. Reference MCS tables for SBFD and non-SBFD The 2 MCS values can come from a single reference MCS table or from different reference MCS tables for SBFD and non-SBFD symbols as explained below. ^ The MCS for the SBFD symbols comes from the same MCS reference table used for non-SBFD symbols. E.g., the existing parameter for reference to MCS table in SPS-Config is used for this purpose. ^ The MCS for the SBFD symbols comes from a different MCS reference table than that is used for non-SBFD symbols. The MCS table can be from the existing MCS tables in NR or a separate new MCS table. E.g., the new separate MCS table can be a low spectral efficiency and code rate MCS table in the NR specification. ^ The MCS reference table for the non-SBFD symbols is provided by the existing parameter mcs-Table in SPS-Config and the MCS reference table for the SBFD symbols is provided by a new parameter in SPS-Config or in RRC. filing version an,rm FH241001PEP 2024P67397EP 27 ^ 2 new parameters for MCS reference tables for non-SBFD symbols and SBFD symbols are provided in SPS-Config or in RRC. In this case, the existing parameter mcs-Table in SPS-Config is ignored by the UE. ^ The MCS reference table for the SBFD symbols is provided in PDSCH-Config as a new parameter. In this case, the existing parameter mcs-Table in SPS-Config can be used for non-SBFD symbols. ^ The MCS reference tables for both the SBFD and non-SBFD symbols are provided in PDSCH-Config. 2. Implicit derivation of MCS value for SBFD symbols- ^ The UE can implicitly derive the MCS to be used for the SBFD symbols. This can be done in the following ways: ^ The gNB asks the UE for a feedback using higher layer signaling like RRC or Media Access Control (MAC). The feedback can be: o Some parameter derived based on the signal to noise and interference ratio (SINR) / interference or any other channel state related parameter for SBFD and non-SBFD symbols. The UE can also derive an MCS value for the SBFD symbols based on the parameter. The MCS value can be derived using some specified formula or from a look up table relating the MCS value to the parameter. o Some parameter derived based on the difference between (SINR) / interference or any other channel state related parameter for SBFD and non-SBFD symbols. The UE can also derive an MCS value for the SBFD symbols based on the parameter. The MCS value can be derived using some specified formula or from a look up table relating the MCS value to the parameter. o Some parameter derived based on the MCS value to be applied for the SBFD symbols. E.g., this MCS value is calculated by the UE based on the SINR of SBFD symbols and the UE directly reports this MCS value. o Some MCS offset to a baseline MCS. E.g., the baseline MCS value is provided by the gNB and the UE calculates the MCS value for SBFD filing version an,rm FH241001PEP 2024P67397EP 28 symbols. It then calculates the offset of the MCS for SBFD symbols compared to the baseline MCS. The UE is expected to receive SPS in SBFD symbols with the same MCS value it has calculated using one of the methods described above. However, whether the UE receives SPS in SBFD symbols with the same MCS value it has calculated can depend upon an acknowledgement sent by the gNB to the UE. E.g., a one bit acknowledgement is sent in RRC. If the acknowledgement bit is set to 1, then the UE expects the calculated MCS to be used. In other case, the gNB can provide a different MCS value as compared to the calculated one to the UE. Further, whether the UE sends the feedback to the gNB or not can be based upon a condition. E.g., if the difference between the MCS for SBFD and non-SBFD symbols is greater than a given threshold, then only the UE reports the feedback. The threshold can be pre-defined in the specification or provided by the gNB to the UE. ^ The gNB provides assistant information to the UE for the calculation of the MCS for SBFD symbols. E.g., the assistant information can be certain information about the interference on the SBFD symbols. The UE calculates the MCS based on this. It may provide this MCS as feedback to the gNB as well. ^ MCS is indicated to the UE by a row number from the reference MCS table. The UE receives the row number for the non-SBFD symbols. It derives the MCS for SBFD symbols based on it and a fixed offset value as defined in the specification. E.g., the value of 2 is given in the specification. It means that, if the DCI provides the MCS row index value of 6 for non-SBFD symbols, then the MCS row index for SBFD symbols will be 6-2=4. It can also be the other way round where the MCS for the SBFD symbols is provided and the MCS for the non-SBFD symbols is derived from it. 3. Explicit indication of MCS offset value ^ In this method, an MCS offset value is provided in the SPS-Config which will be used to derive the MCS for SBFD symbols. E.g., a single value of 2 is given. It means that, if the DCI provides the MCS row index value of 6 for non-SBFD symbols, then the MCS row index for SBFD symbols will be 6-2=4. Also, the MCS offset value can be provided in the DCI itself using any unused / reserved bits. It can filing version an,rm FH241001PEP 2024P67397EP 29 also be the other way round where the MCS offset is provided for the non-SBFD symbols. Transport block size (TBS) Calculation In the transport block size (TBS) calculation for the DL SPS data, the gNB and the UE uses the available number of DL resources in the SBFD symbols instead of the total number of resources in the DL active BWP. This is shown in Fig.10. The number of allocated resource blocks (RBs) is considered to be the number of available DL RBs for SBFD symbols. E.g., the RBs only within the DL SB are considered for this calculation. If a different MCS is provided or derived for SBFD symbols, then this is also considered to calculate the TBS. Further, the xOverhead parameter might be a different one provided explicitly for SBFD symbols or implicitly determined e.g., based on the available DL resources or the unavailable DL resources. Fig.10 exemplarily depicts a schematic representation 1000 of steps involved in determination of a transport block size, TBS, for resource allocation, in accordance with embodiments. In particular, Fig.10 presents an example of TBS calculation for SPS in SBFD symbols. The determination of the TBS for resource allocation being SPS may be based on an available number of DL resources in the SBFD symbols. The UE may preferably use the available number of DL resources in the SBFD symbols over the total number of resources in the DL active BWP for the TBS calculation. The device may use different MCS for SBFD and non- SBFD occasions, or symbols thereof, and thus may consider a number of allocated resource blocks, RBs, to be same as the number of available DL RBs for SBFD symbols. The device may determine the TBS by taking into account the different MCS for SBFD and non-SBFD symbols. Further, the device may take different values of a xOverhead parameter for SBFD and non- SBFD symbols into account for the TBS calculation. It may be that the xOverhead parameter may be explicitly made available to the device, or, alternatively, the device may implicitly determine the xOverhead parameter based on available DL resources or unavailable DL resources. For instance, the xOverhead parameter value may be affected by signalling related to CSI-RS, PTRS, PDCCH, SRS, SSB. Thus, fig. 8 illustrates the manner in which the device may adapt the TBS determination for SBFD symbols or occasions for SPS as the resource allocation. The device may be adapted to determine TBS for other resource allocations in a similar manner. filing version an,rm FH241001PEP 2024P67397EP 30 In one occasion of SPS, if at least n symbols are SBFD symbols then the UE performs one of the following checks and can fully ignore the SPS occasion. a. The number of available DL resources for the given FDRA in the SBFD symbols is lower than a threshold. E.g., if the number of RBs available for the DL reception is less than 4 RBs, then the reception is ignored. In this case, the threshold is in terms of number of RBs. This threshold can be specified in the NR specification or provided by the gNB to the UE using RRC or DCI. An example is shown in Fig.11. In slot 1, the SPS occasion is ignored since the available DL resources are very few and less than the threshold. b. The TBS calculated for the available for the given number of available DL resources and MCS is below a threshold. In this case, the threshold is in terms of number of RBs. This threshold can be specified in the NR specification or provided by the gNB to the UE using RRC or DCI. The value of n can be defined in the specification or provided by the gNB. E.g., n can be 1. However, if reception of the SPS in that occasion is of very high priority, then the UE can still perform the reception of SPS. E.g., if a high priority flag is indicated by the gNB, then the UE receives the SPS despite the conditions mentioned above are satisfied. Further, the gNB is also aware of the conditions under which the UE ignores the SPS. Hence, it will not transmit the SPS in that occasion. Fig. 11 exemplarily depicts a schematic representation 1100 of a resource allocation in a wireless communication network, in accordance with embodiments. In particular, Fig. 11 presents an example of an ignored SPS occasion. A plurality of SBFD slots 11201-3in a DU configuration and a plurality of non-SBFD slots 11204,5for DL, or D, are shown. The frequency allocation, i.e. a first SPS occasion 11501may be scheduled or assigned in the first SBFD slot 11201pertaining to slot 1 and a second SPS occasion 11502may be scheduled or assigned in the second non-SBFD slot 11205pertaining to slot 5. As exemplarily depicted, a first overlap between the first SPS occasion 11501and the sub- band 11301,Dfor reception in DL, or D, may be substantially, or relatively, smaller than a second overlap between the first SPS occasion and the sub-band 11301,Ufor transmission in UL, or U. filing version an,rm FH241001PEP 2024P67397EP 31 Thus, it may be that resources available for SPS DL reception may be limited. Depending on the first overlap, the SPS DL reception may be ignored, or skipped or suppressed. The device may ignore an occasion of the resource allocation, if at least a specific number of n symbols of the occasion are SBFD symbols related to one or more SBFD slots. For instance, if a number of resources, which could be specified in REs, or RBs, available, or allocated, for the resource allocation, here SPS, is smaller than a resource threshold, the UE may ignore the signalling or communication related to the resource allocation, while if the number of resources available, or allocated, for the resource allocation is equal to larger than the resource threshold, the UE may perform the signalling or communication related to the resource allocation. The resource threshold may be pre-configured, such as a priori agreed upon in accordance with a legacy standard, or alternatively, it could be configured or provided by the BS in an explicit or an implicit manner, such as by use of RRC or DCI. The device may determine whether a calculated TBS for the signalling or communication related to the resource allocation and based on an associated MCS is below a TBS threshold. The device may ignore the occasion depending on the calculated TBS value. The TBS threshold may be pre-configured, or pre-determined, such as a priori agreed upon value in accordance with a legacy standard, or provided explicitly or implicitly to the device. Further, the UE may perform the signalling or communication related to the resource allocation despite the number of available resources being smaller than the resource threshold, if the signalling or communication related to the resource allocation has been assigned a high or a very high priority. The priority indication could be indicated by a flag provided by the gNB. It may be that the BS, or gNB, is aware of the conditions according to which the UE may ignore the communication or signalling related to the resource allocation, and thus may itself not provide signalling or communication for the resource allocation to the UE. Postponing reception / transmission of SPS When a UE ignores the SPS reception in a particular time occasion, it can be postponed to a next available set of DL resources. An example is shown in Fig.12. The SPS occasion in slot 1 falls on SBFD symbols. The available DL resources are very few and less than the threshold and the UE is supposed to ignore the SPS occasion. However, a non-SBFD DL slot (slot 4) is available to the UE before the next scheduled SPS occasion in slot 5. The UE can expect that the SPS occasion in slot 1 is postponed to an SPS occasion in slot 4. Fig. 12 exemplarily depicts a schematic representation 1200 of a resource allocation in a wireless communication network, in accordance with embodiments. In particular, Fig. 11 presents an example of a postponed SPS occasion. filing version an,rm FH241001PEP 2024P67397EP 32 A plurality of SBFD occasions 12201-3in a DU configuration and a plurality of non-SBFD occasions 12204,5for DL, or D, are shown, similar to those in Fig.11. The frequency allocation, i.e. a first SPS occasion 12501may be scheduled or assigned in the first SBFD occasion 12201pertaining to slot 1 and a second SPS occasion 12502may be scheduled or assigned in the second non-SBFD occasion 12205pertaining to slot 5. The first SPS occasion 12501may be skipped, or ignored or suppressed, for DL reception in the first SBFD occasion 12201by virtue of a relatively, or substantially, small first overlap between the scheduled first SPS occasion and the sub-band 12301,Dfor reception in DL, or D. The SPS occasion may be ignored provided conditions configured for it are fulfilled, as described in reference to Fig.11. Therefore, the UE may postpone the first SPS occasion to a next available set of DL resources. That is, the device may configure or schedule the first SPS occasion, which was scheduled or configured for slot 1, to slot 4. Here the slot 4 may be selected by the device since slots 2 and 3 may be SBFD occasions and slot 4 may already have the second SPS occasion scheduled for it. It is noted that postponement here refers to a re-scheduling of the frequency allocation, the example of which being a SPS occasion is considered. This applies equally to any other resource allocation configured for other link directions, such as uplink, UL or U, and / or sidelink, SL or S. The device may configure the postponement of the resource allocation, here the first SPS occasion, in a manner so as to be associated with a next available occasion, such as next available non-SBFD occasion. It could be that the device may re-schedule or postpone the frequency allocation to a next available SBFD occasion, wherein the sub-bands of the next available SBFD occasion are configured to allow an increased amount of resources for the resource allocation relative to the originally, or previously, planned or scheduled resource allocation. For instance, the device may postpone communication or signalling related to the resource allocation provided at least one available non-SBFD occasion occurs before the next scheduled, or planned, occasion. For instance, the device may provide a capability information to the wireless communication network, wherein the capability information may indicate that the device is capable of performing the signalling or communication related to the resource allocation, here for example the SPS reception. The capability information could be provided to the gNB by the UE. Further, the postponement, or rescheduling, of the communication or signalling related to the resource allocation could be subject to one or more conditions. The occasion where the resource allocation is postponed or rescheduled to may be conditioned upon being within n number of slots, or symbols, time duration or specified in any other unit in time domain. The postponement, or rescheduling, of the communication or signalling related to the resource allocation could be conditioned on at least one of: HARQ timing; radio link failure, RLF, based filing version an,rm FH241001PEP 2024P67397EP 33 timing; and one or more code block groups, CBGs. It may be that a next slot for postponement, or rescheduling, could be chosen or selected such that the next slot occurs within the HARQ timing duration since reception of a HARQ-NACK related to a failed communication. It may be that the next slot for postponement, or rescheduling, could be chosen or selected such that the next slot occurs within a RLF timing duration. The RLF timing duration could be a time window with a last opportunity for the UE (e.g. cell edge UEs) to communicate with the wireless communication network in circumstances where the radio channel may be deteriorating or degrading. It may be that the next slot for postponement, or rescheduling, could be chosen or selected depending on signalling or communication of a plurality of CBGs. The BS, or gNB, may be aware of the conditions of the postponement, or rescheduling, by the UE, and thus may adapt its communication or signalling to the UE in accordance with the awareness of the conditions. For instance, the gNB may postpone its transmission to the UE, if the conditions for which the UE postpones reception are met. Further, the device, or UE, may postpone, or reschedule, the occasion to a different portion of the frequency domain (e.g. spectrum) such as different BWP or a different carrier. The device, or UE, could trigger a data duplication communication or a redundancy communication in the different portion of the frequency domain. This could be carried out to increase probability of a successful, or intended, communication. The data duplication communication or the redundancy communication could be related to at least one of: a location of the carrier (e.g. FR1, FR2, FR3); available bandwidth allocated to the carrier and / or a BWP; a configured numerology associated with the BWP (e.g. [15, 30, 60, 120, ...] kHz SCS); a utilization in a given band; and measurement related conditions (e.g. measured interference in the given band which could be characterized by SINR, RSRP or similar KPIs / metrics). Although the device may postpone, or reschedule, the signalling or communication of the resource allocation, it may consider the HARQ process ID to remain unchanged. That is, the device may associate a same HARQ process ID with the postponed, or rescheduled, communication as that of the originally scheduled communication. The scenario represented in Fig. 12 may be adapted for a converse scenario where the resource allocation pertains to an uplink transmission, instead of downlink reception as exemplarily depicted. For instance, the device may be adapted to use the allocated resources for UL transmission related to an SRS transmission. The UL transmission may be performed by preferring a usage of SBFD slots or symbols over other slots or symbols. In this regard, the device may assign or designate the other slots or symbols as invalid and the SBFD slots or symbols as valid. This means that the device may forbid (e.g. suppress, blank or mute) transmission and / or reception using the other slots or symbols. This assignment or designation may be performed with respect to, or reserved for (e.g. dedicated to), one or more signals. For filing version an,rm FH241001PEP 2024P67397EP 34 example, such one or more signals may be a SRS, DMRS, TBoMS repetition, PUCCH, PUCCH repetition, PUSCH, multi-PUSCH, PUSCH repetition, phase tracking reference signal, PTRS, PRACH, e.g., PRACH preamble, random access response (RAR) or equivalent signals. .... Further, the device may postpone, or re-schedule, the signalling or communication (e.g. UL transmissions, DL receptions) for the resource allocation if one or more occasions pertaining thereto are scheduled, or fall, or are to be carried out, in, or using, an invalid symbol type. It could be that the device may ignore such UL transmissions instead of postponing them. In this regard, the slots or symbols which are not subject to postponement may be available or valid. It may be that the device uses the allocated resources associated with the signalling or communication (e.g. UL transmissions, DL receptions) based on one or more conditions. The one or more conditions may be: available or valid slots of a specific symbol type for resources of the resource allocation, and timing requirements associated with trigger of the resources of the resource allocation. For example, in case of aperiodic SRS, the UE may be provided with information related to available or valid slots. The available or valid slots could be defined as those slots which fulfil the conditions: the slots may comprise one or more UL or flexible symbols which may not be configured with a specific symbol type, such as SBFD, for time domain pertaining to a set of SRS resources (e.g. all SRS resources from the resource set); and the slots satisfy the device (e.g. UE) capability on a minimum timing condition between triggering PDCCH and the SRS resources (e.g. all SRS resources from the resource set). In a different example, the specific symbol type may be non-SBFD. In accordance with embodiments, the SBFD time frequency occasion may comprise both SBFD symbols and non-SBFD symbols. In this regard, the SBFD time frequency occasion may be a collection of different symbol types, a first symbol type and a second symbol type, such as the SBFD symbol types and the non-SBFD symbol types. It may be that the SBFD time frequency occasion is such that only one (e.g. a single symbol type) of the different symbol types, i.e. the SBFD symbol type and the non-SBFD symbol type, is valid for the SBFD time frequency occasion. The device may determine that a first frequency time occasion of the resource allocation is valid in one of the different symbol types, i.e. the SBFD symbol type and the non-SBFD symbol type, and invalid in other of the different symbol type, i.e. the SBFD symbol type and the non-SBFD symbol type. In other words, the first symbol type and the second symbol type may form a group of SBFD symbols and a non-SBFD symbol, constituting the SBFD time frequency occasion. In this regard, both symbol types pertain to time-frequency occasions. filing version an,rm FH241001PEP 2024P67397EP 35 For instance, the first time-frequency occasion of the resource allocation could be related to the SRS transmission occasion. The first time-frequency occasion of the resource allocation may itself be a SRS transmission occasion. An example of valid and invalid assignments to resource allocation occasions depending on a slot or symbol type is described further in the disclosure, for instance, in regard to Fig.26. Conditions to determine when the SPS occasion is postponed: ^ An SPS occasion needs to be ignored by the UE due to some pre-defined conditions being satisfied. ^ There is at least one available non-SBFD DL slot where the configured frequency resources for SPS are available. ^ The at least one available non-SBFD slot occurs before the next scheduled SPS occasion. E.g., the available non-SBFD slot should be at least one slot or n symbols before the next SPS scheduled SPS occasion. ^ The UE should be capable of receiving a postponed SPS. The UE can provide this a capability information to the gNB. ^ Any other transmission / reception processing / delay timing related condition is satisfied. o The next available valid slot is within n slots / symbols / time duration from the slot being ignored, o A retransmission-related condition ^ e.g., HARQ-timing, needs to be satisfied, e.g., transmitting on the postponed slot is the only possibility to transmit in time, prior to receiving a HARQ-NACK for a failed transmission, ^ radio link failure, RLF, timing related issue, e.g., a last possibility to transmit in a scenario where the radio channel is degrading, e.g., a cell- edge UE, ^ a code block group, CBG,-based condition, e.g., the last n-CBGs have not been transmitted and the postponed transmission could avoid a transmission which would be either too late or which could be better utilized by other code blocks. ^ The type of data transmitted by the UE, e.g., in case the transmission belongs to a retransmission, the transmission may or may not be postponed, filing version an,rm FH241001PEP 2024P67397EP 36 ^ A signal received within the U-part of a previous SBFD slot, e.g., in case of a NACK and / or ACK, or a NACK for a CBG-based transmission was received within the SBFD slot. For UL transmissions and DL receptions across SBFD symbols and non-SBFD symbols in different slots (each transmission / reception within a slot has either all SBFD or all symbols) with Configuration 1, - For PUSCH repetition type A with available slot counting, A-SRS with available slot counting, TBoMS and PUCCH repetitions, UE postpones transmissions in the invalid symbol type. - For CG PUSCH with neither TBoMS nor PUSCH repetition type A with available slot counting,and SPS PDSCH, P / SP SRS, P / SP CSI-RS, P / SP PUCCH, SP-CSI on PUSCH, PUSCH repetition type A without available slot counting, multi- PUSCH / PDSCH scheduled by a single DCI, and PDSCH repetitions, transmissions / receptions in the invalid symbol type are dropped. For aperiodic SRS with available slot counting, o For SRS-ResourceSet configured for SBFD symbol, an available slot is a slot satisfying there are SBFD symbol(s) for the time-domain location(s) for all the SRS resources in the resource set and it satisfies UE capability on the minimum timing requirement between triggering PDCCH and all the SRS resources in the resource set. For SRS-ResourceSet configured for non-SBFD symbol, an available slot is a slot satisfying there are UL or flexible symbol(s) not configured as SBFD symbols for the time-domain location(s) for all the SRS resources in the resource set and it satisfies UE capability on the minimum timing requirement between triggering PDCCH and all the SRS resources in the resource set. Further, the gNB is also aware of the conditions under which the UE postpones the reception of the SPS. Hence, the gNB will also postpone the transmission of the SPS for that occasion. Further, the occasion can be postponed to a different BWP / carrier etc., or could trigger a data duplication or redundancy transmission in a different BWP / carrier, in order to increase the probability of a successful transmission. This could also be related to one or more of the following conditions: ^ the exact location of the carrier e.g., frequency band in FR1 or FR2 or FR3, ^ the available bandwidth given for a said carrier and / or BWP, filing version an,rm FH241001PEP 2024P67397EP 37 ^ the numerology configured for a said BWP, e.g., [15, 30, 60, …] kHz SCS, ^ the utilization in a given band, ^ measurement-related conditions, e.g., the interference in a given band, e.g., measured by RSRP, SINR, or similar KPIs. Even after postponing the reception of SPS to some other slot, the HARQ process ID is considered to remain same. Spreading reception / transmission of SPS over time domain As discussed in the previous section, based on certain conditions, the SPS occasion can be ignored or postponed by the UE mostly due to fewer available DL resources. The DL resources available are reduced in frequency domain because of the overlap with UL SB and guard bands. Hence, if a method can be used to allot more resources over time domain, that is, spreading the SPs over the next few available DL resources, might help to retain the SPS occasion. An example is shown in Fig.13. The scheduled SPS occasion is in an SBFD slot. The available DL resources are very few and less than the threshold resources for reception of SPS. However, in the consecutive time domain symbols, there are DL resources available that can be used to spread the reception of SPS. Thus, due to the spreading, the number of available DL resources increases and the SPS can be received. Fig. 13 exemplarily depicts a schematic representation 1300 of a resource allocation for a plurality of SBFD symbols. In particular, Fig. 13 presents an example of spreading of SPS resources in time domain across a plurality of SBFD symbols. A scheduled occasion for the resource allocation, here the resource allocation exemplarily being SPS, in a time slot configured for SBFD is shown. The overlap between the resources available in the DL sub-band and the scheduled SPS occasion is small. Thus, the UE may have fewer resources for SPS reception than preferred or desired. The time slot 1320 configured for SBFD is shown comprising a plurality of SBFD symbols 1322#. One or more DL sub-bands of one or more of the SBFD symbols may be used for SPS reception. These SBFD symbols may comprise a first portion 13501of the allocated resources, here pertaining to the SPS occasion. A second portion 13502of the SPS occasion, that is, a rest of the SPS occasion aside from the first portion, or the portion of the SPS occasion not available for reception using DL, may be spread into other available resources 1352#for reception, e.g. SPS reception, using DL. The spreading may thus be a mapping of the resources within the second portion (e.g. data or transport block) to the other available resources 1352#. filing version an,rm FH241001PEP 2024P67397EP 38 This spreading may be carried out using other available resources 1352#which are shifted relative to the allocated resources in the time domain. The other available resources 1352#may be resources subsequent in the time domain to the allocated resources, or prior in the time domain to the allocated resources. The device may receive the second portion of the allocated resources, pertaining to the SPS occasion, with same frequency domain resources as the first portion. For instance, as exemplarily depicted in Fig. 13, the spreading may be carried out using symbols 1322#which are consecutive in the time domain. A number of consecutive symbols used may depend on the size, or amount, of resources to be spread. In other words, the number of consecutive symbols which may be used for spreading depends on the portion of the allocated resources previously, or originally, unavailable for reception by the UE. The consecutive symbols could be SBFD symbols. These consecutive symbols may be after a last symbol of the allocated resources, or before a first symbol of the allocated resources. The number n of consecutive symbols to be used for spreading may be determined by the device. For instance, the number n may be determined by the UE using any of the steps either standalone or in combinations, depicted in Fig.10. Further, alternatively, the number n could be provided by the gNB to the UE, e.g. in RRC, MAC and / or DCI. The device may spread the second portion of the allocated resources for communication or signalling related to the scheduled occasion into the other available resources provided one or more conditions are fulfilled. These conditions may relate to fulfilment of at least one of: a transmission timing, a reception timing, a processing timing and a delay timing. Conditions when the SPS occasion is spread over in time domain ^ Consecutive symbols in time domain are available to the UE just after the last symbol of scheduled SPS occasion or before the first symbol of scheduled SPS occasion. o The same frequency domain resources that can be used for SPS reception as in the scheduled SPS occasion are available in the consecutive symbols. As shown in Fig. 13, if the symbols are SBFD symbols, and hence the same frequency resources are used. o If a symbol in the consecutive set of symbols is a non-SBFD symbol, then the frequency domain resource allocation for non-SBFD symbols is used. This is shown in Fig.14. o If a symbol in the consecutive set of symbols is a non-SBFD symbol, then the frequency domain resource allocation for SBFD symbols is used. This is shown in Fig.15. filing version an,rm FH241001PEP 2024P67397EP 39 o Any other transmission / reception processing / delay timing related condition is satisfied. ^ ‘n’ number of consecutive time domain symbols are available. ‘n’ can be derived in the following ways. o ‘n’ is calculated as the minimum number of time domain symbols such that the number of REs or the unquantized intermediate variable in step 3 or TBS in step 4 as shown in step 1 in Fig.10 is equal to or more than a given number of REs or unquantized intermediate variable or TBS respectively. ‘n’ is equivalent to the allocated number of symbols in the equation in step 1. In Fig. 14, ‘n’ is equal to 6. ^ The given number of REs or unquantized intermediate variable or TBS can be same as the number of REs or unquantized intermediate variable or TBS of the SPS occasion on non-SBFD symbols. ^ The given number of REs or unquantized intermediate variable or TBS can be provided by the gNB. o ‘n’ is provided by the gNB in RRC / MAC / DCI. Fig. 14 exemplarily depicts a schematic representation 1400 of a resource allocation for a plurality of SBFD symbols and a non-SBFD symbol, in accordance with embodiments. In particular, Fig.14 presents an example of spreading of SPS resources in time domain across all SBFD and non-SBFD symbols with different frequency domain resources. A slot comprising the plurality of SBFD symbols 14220-9,142211-13and a single non-SBFD symbols 142210are depicted. The spreading of the scheduled occasion for the resource allocation, here the resource allocation being SPS, may be across the SBFD symbols and the single non-SBFD symbol. The resources used for SPS reception 1452#may thus be additional resources used in time domain available to the UE, such as in the SBFD symbol 14229, 142211and the non-SBFD symbol 142210. This is in contrast to the example of Fig.13, where only SBFD symbols were involved in the spreading of the resources for the SPS occasion. Further in contrast to Fig.13, the resources are allocated differently in the frequency domain for the non-SBFD symbol 142210compared to the SBFD symbols 14220-9,142211-13. In accordance with details of Fig. 13, the resource allocation is the same in the frequency domain for all the SBFD symbols 14220-9,142211-13. Details and explanations, such as determination of the number of consecutive time domains symbols, described in reference to Fig.13 are applicable to the example of Fig.14 and are not filing version an,rm FH241001PEP 2024P67397EP 40 repeated herein. Although a single non-SBFD symbol is exemplarily depicted here, two or more SBFD symbols may be involved in spreading of resources for the SPS occasion. Fig. 15 exemplarily depicts a schematic representation 1500 of a resource allocation for a plurality of SBFD symbols and a non-SBFD symbol, in accordance with embodiments. In particular, Fig.15 presents an example of spreading of SPS resources in time domain across all SBFD and non-SBFD symbols with same frequency domain resources. Similar to Fig.14, a slot comprising the plurality of SBFD symbols 1522#(e.g. slots 0-9 and 11- 13) and a single non-SBFD symbols 152210is depicted, along with the spreading of the scheduled occasion for the resource allocation, here the resource allocation being SPS, configured across the SBFD symbols and the single non-SBFD symbol. Further in contrast to Fig. 14, the resources (e.g. additional resources 1552#) are allocated to be same in the frequency domain for the non-SBFD symbol 132210and the SBFD symbols 13220-9,132211-13. Thus, the UE may receive the portion of the resources for the scheduled SPS occasion which are unavailable for reception using DL and spread them equally, in the frequency domain, across one or more SBFD and non-SBFD symbols. Details and explanations, such as determination of the number of consecutive time domains symbols, described in reference to Fig.13 are applicable to the example of Fig.15 and are not repeated herein. Although a single non-SBFD symbol is exemplarily depicted here, two or more SBFD symbols may be involved in spreading of resources for the SPS occasion. Further, the gNB is also aware of the conditions under which the UE spreads the reception of the SPS. Hence, the gNB will also spread the transmission of the SPS for that occasion. As discussed in the previous section, spreading the SPS over the next few available DL resources, helps to retain the SPS occasion. Another way to retain the SPS occasion is to split the SPS occasion over multiple slots. An example is shown in Fig.16. As shown in Fig.16, the SPS occasion in slot 1 has very few available DL resources. Instead of ignoring the occasion, the occasion is split over slots 1, 2 and 3. In the given example, all the slots are SBFD slots and the same frequency resources are used over all the slots. Conditions when the SPS occasion is split over in time domain ^ Consecutive or non-consecutive slots in time domain are available to the UE just after the last symbol of scheduled SPS occasion or before the first symbol of scheduled SPS occasion. filing version an,rm FH241001PEP 2024P67397EP 41 o The same frequency domain resources that can be used for SPS reception as in the scheduled SPS occasion are available in the consecutive slots. As shown in Fig. 16, if the symbols are SBFD symbols, and hence the same frequency resources are used. o If a slot in the set of slots over which the splitting is performed is a non-SBFD slot, then the frequency domain resource allocation for non-SBFD symbols is used. An example is shown in Fig.17. Slot 2 is an UL slot, hence there are no available DL resources. Slot 3 is a non-SBFD slot, so more DL resources are available. Slots 4 and 5 are SBFD slots. o If a slot in the consecutive set of slots is a non-SBFD symbol, then the frequency domain resource allocation for SBFD symbols is used. o The same TDRA is followed in all the slots. o Any other transmission / reception processing / delay timing related condition is satisfied. ^ ‘n’ number of time domain slots are available. ‘n’ can be derived in the following ways. o ‘n’ is calculated as the minimum number of time domain slots such that the number of REs or the unquantized intermediate variable in step 3 or TBS in step 4 as shown in step 1 in Fig.10 is equal to or more than a given number of REs or unquantized intermediate variable or TBS respectively. ‘n’ is equivalent to the allocated number of symbols in the equation in step 1. ^ The given number of REs or unquantized intermediate variable or TBS can be same as the number of REs or unquantized intermediate variable or TBS of the SPS occasion on non-SBFD symbols. ^ The given number of REs or unquantized intermediate variable or TBS can be provided by the gNB. o ‘n’ is provided by the gNB in RRC / MAC / DCI. Fig.16 exemplarily depicts a schematic representation 1600 of resource allocations for SBFD and non-SBFD slots in a wireless communication network, in accordance with embodiments. In particular, Fig.16 presents an example of splitting reception of an SPS occasion over time domain with same frequency domain resources. filing version an,rm FH241001PEP 2024P67397EP 42 Two different scenarios for scheduling the SPS occasion are exemplarily depicted using a time-frequency grid. The first scenario shows two SPS occasions being scheduled in two different slots, slot 116221,1and slot 516225,1, wherein one 16221,1of the slots may be adapted for SBFD and the other 16225,1may be adapted for non-SBFD configuration. As depicted previously in a plurality of figures in this disclosure, the SPS occasion may be scheduled to have relatively fewer resources in DL as compared to UL. The second scenario shows such a SPS occasion being split (e.g. partitioned, or divided) into a plurality of SPS occasions across the plurality of slots adapted for SBFD configurations. In this manner, a second portion of the resources allocated for the SPS occasion may be split or distributed to at least one other slot, here two other slots 16222,2, 16223,2. By this measure, the device may improve the resource allocation by virtue of performing the splitting of resources across other slots. The other slots may be consecutive in time-domain or may be later, in time domain, than the originally scheduled single slot. These other slots could be earlier, in time domain, than the originally scheduled single slot. It may be that at least one of the other slots is earlier and at least another of the other slots is later than the originally scheduled single slot in time domain. By this measure, the device may improve the resource allocation by virtue of performing the splitting of resources across other slots. The other slots may be chosen or selected by the device on a basis of their availability. That is, the other slots may be those slots which are available to the UE. The other slots, for instance, may be either prior to or subsequent to the originally scheduled slot for the resource allocation. As exemplarily depicted in Fig. 16, the portions 16511-3of the resources available for SPS reception across the three slots 1622,1-3,2may together constitute a single SPS occasion. In other words, the UE may treat or consider the plurality of portions of the SPS occasions as a single SPS occasion. The plurality of portions may each have a same frequency domain resource. Thus, it may be that the splitting of the resources pertaining to resource allocation occasion may be such that the first portion, which constitutes the available resources in the originally scheduled single slot, may be equal in terms of frequency domain to the second portion, which constitutes the resources which are to be split or distributed, or have been split or distributed, by the UE. It may be that the device considers the HARQ process ID to remain same after splitting as it was prior to the splitting. That is, the HARQ process ID could be configured by the UE to be same across all slots which are used for the communication or signalling related to the resource allocation. Further, a number of the other slots, using which the resources of the originally scheduled resource allocation occasion could be split or distributed, may be either provided (e.g. signalled, or communicated) to the device by the gNB, or determined by the device itself. For instance, the number of the other slots may be determined by the UE using any of the steps, filing version an,rm FH241001PEP 2024P67397EP 43 either standalone or in combinations, as depicted in Fig. 10. For instance, alternatively, the number n could be provided by the gNB to the UE, e.g. in RRC, MAC and / or DCI. The device (e.g. UE) may split or distribute the second portion of the allocated resources for communication or signalling related to the scheduled occasion into the other available resources provided one or more conditions are fulfilled. These conditions may relate to fulfilment of at least one of: a transmission timing, a reception timing, a processing timing and a delay timing. The BS, or gNB, may be aware of such conditions and may adapt its communication to the UE accordingly. For instance, if the UE has chosen to split the occasion due to the one or more conditions being fulfilled, the gNB may be made aware of the fulfilment of such conditions and may adapt its transmissions to the UE. Fig.17 exemplarily depicts a schematic representation 1700 of a resource allocation for SBFD and non-SBFD slots in a wireless communication network, in accordance with embodiments. In particular, Fig.17 presents an example of splitting reception of an SPS occasion over time domain with different frequency domain resources. A plurality of slots 17221-7, some 17221,4,5of which are adapted for SBFD configurations and some 17222,3,6,7of which are adapted for non-SBFD configurations, are shown along with two scheduled SPS occasions 17501, 17502 (e.g. a plurality of originally scheduled SPS occasions). The first SPS occasion may be scheduled in a slot adapted for SBFD configurations and the second, or next to the first, SPS occasion may be scheduled in a slot adapted for non-SBFD configuration. In contrast to Fig. 16, the slots adapted for SBFD configurations may not all be consecutive in the time domain, such as the slots 17221, 17224, 17225. The UE may split or distribute the SPS occasion using (e.g. across) a plurality of other slots being adapted for SBFD and non-SBFD configurations. As exemplarily depicted in Fig.17, a second portion 1751 of the resources allocated for the SPS occasion 17501may be split or distributed to slot 3 , slot 4 and slot 5. The second portion may be split into a plurality of sub- portions 17532, 17533, 17534. The three sub-portions which may be scheduled across SBFD and non-SBFD slots together with a retained sub-portion 17531 of the original resource allocation 17501could constitute a single resource allocation, here being a single SPS occasion. The parameters related to the single SPS occasion being split in such a manner may be thus configured in accordance. The splitting or distribution may be performed by the UE in a manner such that different frequency resources are selected (or allocated) for SBFD slots compared to non-SBFD slots. Although the SBFD slots may have equal frequency domain resources for SPS reception, this filing version an,rm FH241001PEP 2024P67397EP 44 may be varied such that different SBFD slot may differing frequency domain resources for the SPS reception. Details and explanations, such as determination of the number of consecutive time domains symbols, described in reference to Fig.16 are applicable to the example of Fig.17 and are not repeated herein. Although a single non-SBFD symbol is exemplarily depicted here, two or more SBFD symbols may be involved in splitting of resources for the SPS occasion. Further, the gNB is also aware of the conditions under which the UE splits the reception of the SPS. Hence, the gNB will also split the transmission of the SPS for that occasion. Even after splitting the reception of SPS to some other slot, the HARQ process ID is considered to remain same. HARQ Process IDs for SPS across SBFD and non-SBFD symbols When the UE is provided with separate SPS-Configs for SBFD and non-SBFD symbols: ^ The same SPS-Config indices can be provided for both SBFD and non-SBFD symbols. In this case, the UE searches for more than one DCI with the same SPS-Config indices for activation. Whether the UE searches for more than one DCI, can be explicitly indicated by the gNB. o The HARQ process ID is kept the same for both of the SPS-Configs. ^ E.g., the HARQ process ID calculated for non-SBFD symbols is assumed to be for SBFD symbols as well. In another example, the HARQ process ID is calculated based on an occasion number instead of current slot number. The occasion number can be same for both SBFD and non-SBFD slots even if the slot numbers are different. ^ 2 different SPS config indices can be provided. o The HARQ process ID is kept the same for both of the SPS-Configs. Demodulation reference signal (DMRS) Bundling across multiple slots DMRS bundling across multiple slots is used in NR to improve the accuracy of channel estimation. E.g., repetition of PUSCH over multiple slots, multi-PUSCH, TB processing over multiple slots etc. use DMRS bundling to improve channel estimation accuracy. In case of repetition of PUSCH over multiple slots, the same TB is transmitted over multiple slots with the filing version an,rm FH241001PEP 2024P67397EP 45 same or different redundancy version (RV). However, each occasion of the transmission of the TB is restricted to one slot. In case of multi-PUSCH, each TB (each one is different) of UL is transmitted in a different slot scheduled by a single DCI. In case of TB processing over multiple slots, a single TB is spread across multiple slots and transmitted. Thus, the single TB is processed by the UE to be transmitted across the multiple slots and is also received and processed by the gNB over those slots. The two main parameters of DMRS bundling are pusch-TimeDomainWindowLength, which gives the number of consecutive slots from which the DMRS are processed together for channel estimation and, pusch- FrequencyHoppingInterval, which gives the number of consecutive slots for which the frequency hopping (FH) remains the same and the DMRS is also bundled. The signals like repetition of PUSCH, multi-PUSCH, TB processing over multiple slots etc. can spread over multiple slots of which some are SBFD while some are non-SBFD. In such a case, the DMRS bundling might be handled differently across SBFD and non-SBFD slots. Some of the ways are: 1. Same DMRS bundling parameters (pusch-FrequencyHoppingInterval, pusch- TimeDomainWindowLength) across SBFD and non-SBFD slots and the bundling can be done across SBFD and non-SBFD slots. 2. Different bundling parameters (pusch-FrequencyHoppingInterval and / or pusch- TimeDomainWindowLength) for SBFD and non-SBFD slots. 3. The value of the bundling parameter (pusch-FrequencyHoppingInterval and / or pusch- TimeDomainWindowLength) is minimum of the indicated value of the bundling parameter by the gNB and the number of consecutive slots of any one type. E.g., the value indicated for pusch-FrequencyHoppingInterval is 4 slots for SBFD. The number of consecutive SBFD slots where FH is applied is 2 while the next slot is a non-SBFD slot, then the value of pusch-FrequencyHoppingInterval is considered to be 2. Different frequency domain resources for SBFD and non-SBFD symbols In this case, the frequency domain resources for SBFD and non-SBFD symbols are different as shown in Fig.18. The FDRA is different for slot 1 and slot 2 but the TDRA is the same in Fig.18. However, the TDRA can be different as well. Fig. 18 exemplarily depicts a schematic representation 1800 of a resource allocation in a wireless communication network, in accordance with embodiments. In particular, Fig. 18 presents an example of different frequency domain resources for two slots – a first slot 18221filing version an,rm FH241001PEP 2024P67397EP 46 adapted for a non-SBFD configuration and a second slot 18222adapted for a SBFD configuration. The resource allocation here exemplarily relates to SPS and thus the device may receive SPS using DL. Other resource allocations, for instance, relating to the device allocating resources for transmission using UL are feasible. The resources allocated for SPS reception may be different, in terms of the frequency domain, and same, in terms of the time domain, across the two slots. The resource allocation for SPS may also be different, in terms of the time domain, across SBFD and non-SBFD slots. In contrast to the scenarios of previously described figures, there may be no overlap of the SPS occasion with the guard band and the UL, or U, sub-band. Thus, the device may allocate resources so as to avoid an overlap between a sub-band of a SBFD slot, wherein the sub- band may pertain, or be associated, with an opposite link direction relative to the link direction associated with the resource allocation. By this measure, the device may allocate resources for the resource allocation, here SPS, advantageously. Details described here in regard to the resource allocation are applicable to SBFD and non-SBFD symbols. For instance, the resources may be adapted to have a larger allocation in the time domain in the SBFD slot, within the available sub-band, relative to the allocation in the time domain in the non-SBFD slot. The difference between the allocation in the time domain may be configured so as to achieve an equal resource allocation across the SBFD and the non-SBFD slot. There might be a case where one occasion of the SPS falls across both SBFD and non-SBFD symbols. This is shown in Fig.8. In such a case, the UE either ignores that SPS occasion or the UE treats all the symbols in that occasion to be of a particular type. E.g., if at least n number of symbols in the occasion are SBFD symbols then, all the symbols in that occasion are treated as SBFD symbols. The number n can be defined in the specification or provided by the gNB. Methods for allocating frequency domain resources Fig.19 exemplarily depicts a schematic representation 1900 of a resource allocation for slots adapted for SBFD and non-SBFD configurations in a wireless communication network, in accordance with embodiments. In particular, Fig. 19 presents an example of different DCIs with different SPS-Config indices activating SPS for slots adapted for SBFD and non-SBFD configurations. A slot 1922n, slot n, adapted for non-SBFD configuration with DL band is depicted, along with a first slot 19221, slot 1, adapted for non-SBFD configuration with DL band and a second slot filing version an,rm FH241001PEP 2024P67397EP 47 19222, slot 2, adapted for SBFD configuration with a single UL sub-band and a single DL sub- band. The first slot and the second slot may relate to different resource allocation configurations, here different SPS configurations. As exemplarily depicted, the two slots may pertain to different frequency domain resource allocations. In particular, the frequency domain resource allocation in slot 2 may avoid the UL sub-band, and may not have any UL resources. A plurality of DCIs and a plurality of SPS-Config indices may be provided (e.g. signalled, or communicated) to the UE using resource scheduled in slot n 1922n. A first DCI 19601and an associated first SPS-Config index, SPS-Config index 1, and a second DCI 19602and an associated second SPS-Config, index SPS-Config index 2, may be provided to the UE using (e.g. by scheduling a signalling or communication thereof in; allowing a reception thereof in) the slot 1922n, slot n. The slot n may earlier, or prior to, the slots 1 and 2 in the time domain. Therefore, as shown in Fig.19, the first and the second DCI may be adapted to activate (e.g. trigger, or release, or allow) corresponding SPS occasions 19501, 19502in slot 119221and slot 219222. The SPS-Config indices associated with the two SPS occasions may be different from each other. However, in accordance with some embodiments, the SPS-Config indices may also be the same; in such a case the two distinct DCIs with different frequency resource allocations may be provided to the UE with the same SPS-Config index. The UE may itself distinguish among the first and the second DCI in terms of their association with SBFD and non-SBFD occasions. It may be that a single DCI with the different frequency resource allocations and the same SPS-Config index may be provided to the UE. The UE may use (e.g. decode) the single DCI and schedule the different resource allocation occasions, SPS occasions, accordingly. For instance, the UE may use new or unused or unreserved bits in SBFD symbols for performing the FDRA. Further, the device (e.g. UE) may derive the FDRA for the SBFD occasions, such as 19502, (or symbols thereof) based on (e.g. depending on, using) the FDRA for the non-SBFD occasions, such as 19501, (or symbols thereof), wherein the FDRA for the non-SBFD occasions, or symbols, may be provided to the device by the gNB. This provision could be explicit or implicit. It may be that, for the purpose of deriving the FDRA for the SBFD occasion or symbols, the device could implement or carry out a derivation. The derivation could be based on one or more explicit indications by the gNB. Alternatively, the derivation could be based on one or more explicit indications made as a part of virtual resource block to physical resource block (VRB-to-PRB) mapping of the allocated resources. Conversely, the device (e.g. UE) may derive the FDRA for the non-SBFD occasions, such as 19501, (or symbols thereof) based on (e.g. depending on, using) the FDRA for the SBFD filing version an,rm FH241001PEP 2024P67397EP 48 occasions, such as 19502, (or symbols thereof), wherein the FDRA for the SBFD occasions, or symbols, may be provided to the device by the gNB. This provision could be explicit or implicit. Fig. 20 exemplarily depicts a schematic representation 2000 of different cases of resource allocations in slots adapted for SBFD configurations in a wireless communication network, in accordance with embodiments. In particular, Fig.20 presents examples of SPS occasions in SBFD slots with the same frequency domain resources as scheduled in non-SBFD slots as five different cases. Each of the five cases, case 1-5, show a time slot adapted for SBFD configuration comprising an occasion associated with the resource allocation, i.e. a scheduled SPS occasion 2050#. In cases 1 and 2, each of the SBFD occasions comprises a single DL sub-band and a single UL sub-band in a DU configuration, while in cases 3-5 each of the SBFD occasions comprises a plurality of DL sub-bands and a single UL sub-band in a DUD configuration. As exemplarily depicted in cases 1-5, the sub-bands may be allocated different frequency domain resources. However, it is feasible that the sub-bands may be allocated equal frequency domain resources. The cases are distinguished from each other by way of arrangement, or placement, of the resource allocation occasion, here this being the scheduled SPS occasion. The SPS occasion may be transmitted from the BS, or gNB, to the UE in the network. Aside from the scenario where the SPS occasion may be schedule entirely or completely within the DL sub-band or the plurality of DL sub-bands, cases 1-5 present scenarios where the UE may derive the SPS occasion on account of it being scheduled either within (e.g. completely or entirely within) the UL sub-band or overlapping with a plurality of sub-bands (e.g. as in cases 2, 4 and 5). For cases 1-5, the UE may determine or derive the resources allocated for SPS reception within the respective SBFD occasion based on or from resources (e.g. frequency domain resources) of the non-SBFD occasions provided to the UE. Further, the time domain resource allocation of the SPS occasion could also be different from each other in cases 1-5. Additional details related to derivation of the SPS occasion in reference to each of these cases will be described further in this disclosure. Different ways of allocating frequency resources for SBFD and non-SBFD occasions are as follows: ^ One way to achieve this is to provide different SPS configurations (with same or separate SPS config indices) to the UE for SBFD and non-SBFD occasions. In this case, since the configurations are different, different DCIs can be provided to the UE for SBFD and non-SBFD symbols. As a result, different DCIs can consist of different filing version an,rm FH241001PEP 2024P67397EP 49 FDRAs. The FDRA provided for SBFD symbols can make sure that the frequency domain resource allocation does not overlap with the UL resources. An example is shown in Fig.19. DCI1 and DCI2 correspond to SPS-Config index 1 and SPS-Config index 2 respectively. They activate SPS with different FDRAs in slot 1 and slot 2. ^ In another method, separate DCIs with separate FDRAs are provided for the same SPS-Config. The UE can differentiate between the DCIs for SBFD and non-SBFD occasions using the methods explained previously in the invention. ^ In another method, a single DCI contains both the FDRAs for the same SPS-Config index. The FDRA for the SBFD symbols can be using new bits or unused / reserved bits. ^ In another method, the frequency domain resources for the SBFD symbols are derived from the frequency domain resources of the non-SBFD symbols or vice versa. The derivation can be based on some explicit indication by the gNB or included as a part of the virtual resource block-to-physical resource block (VRB-to-PRB) mapping of the SPS resources. In Fig.20, the SPS occasion in an SBFD slot with the same frequency domain resources as scheduled in non-SBFD slots are illustrated for UD and DUD scenarios. ^ For each of the scenarios (cases 1-5), the frequency domain resources to be used for SPS reception and / or transmission in SBFD slots can be derived as follows: o Case 1: UD scenario with the scheduled SPS occasion fully overlapping with UL SB and / or guard band. The actual frequency domain resources for SBFD slots to receive SPS can be derived as explained below. ^ The frequency domain resources for SBFD slots start from the start RB of the DL SB which is nearer to the UL SB. Also, an offset can be provided by the gNB. The offset can be provided in terms of number of some frequency units like RBs or Resource block groups (RBGs). This is shown in Fig.21a A. The start RB can have a specific distance to the UL SB, e.g., be the closest RB to the UL SB or at maximum distance and it can be within the DL SB or a reference RB outside the DL SB. Figs. 21a to 21k exemplarily depict schematics representations 2100a to 2100k related to derivation of the resource allocation occasion, exemplarily being SPS occasion, for case 1, in accordance with embodiments. filing version an,rm FH241001PEP 2024P67397EP 50 Fig.21a exemplarily depicts the schematic representation 2100a of a derived SPS occasion for case 1. Two different SBFD occasions 2120A, 2120B, as different time slots in the time domain, with a DU configuration, wherein each SBFD occasion 2120#comprising a guard band between the two sub-bands are shown. In both SBFD occasions 2120A,B, the scheduled resource allocation, i.e. the scheduled SPS occasion 2150A,B, may fully overlap with a respective UL SB 2140A,Band / or a guard band 2135A,B. For SBFD occasion, or SBFD slot, of scenario A, the device may derive, or determine, the derived resources for the resource allocation, here that being the derived SPS resources, based on or using at least one of: a start RB, an offset and a size of the derived resources, if available to the UE, or a size of the scheduled resources. The start RB could be associated with the SB which the scheduled resource allocation overlaps in. The start RB could be defined in terms of a distance related to the location, in frequency domain, of the SB in which the schedules resource allocation overlaps. For example, the start RB could be the start RB of the DL SB which is nearer, or nearest, to the UL SB, which corresponds to the UL SB the scheduled resource allocation is fully overlapping in. The start RB could be described or specified as a specific distance from this UL SB. For example, the start RB could be the closest RB to the UL SB. For example, the start RB could within the DL SB. For example, the start RB could a reference RB outside the DL SB. In scenario A, the device may derive or determine the derived SPS resources using the start RB, the offset from the start RB, and the size of the resources, each of which may be known to the UE, or derived by the UE. Similar to scenario A, in scenario B, the device may derive or determine the derived SPS resources using the start RB, the offset from the start RB, and the size of the resources, each of which may be known to the UE, or derived by the UE. For both scenarios, the size of the resources may be kept same as the size of the frequency domain resources for non-SBFD occasion, or slots. Alternatively, if a new size for the derived resources is provided, the UE may use the new size for deriving the derived SPS resources. For instance, the offset in scenarios A and / or B, may be provided to the UE by the gNB. This provision could be implicit or explicit. For instance, the offset may be an a priori agreed upon value available to the UE. That is, the offset may have a default value known to the UE, or provided to the UE. It is also feasible that the UE may determine the offset itself. The offset may be given in any unit of the frequency domain, such as resource blocks, RBs, or Resource Block Groups, RBGs. filing version an,rm FH241001PEP 2024P67397EP 51 Unlike in scenario A, in scenario B the derived SPS resources may be partially outside the DL sub-band of the SBFD occasion. Therefore, the device may ignore the portion 2157 of the derived resources which are present or extend outside the DL sub-band of the SBFD occasion. This can be further extended to UL signals or channels like PUSCH. In NR, UL resource allocation is generally of 2 types, type 0 and type 1. In type 0, a bitmap for each active virtual RBG is provided. The VRB-to-PRB mapping is non-interleaved for type 0. For type 1, a contiguous allocation of VRBs corresponding to a start VRB / virtual RBG within the BWP and the number of VRBs / virtual RBGs is provided using a resource indicator value (RIV). The VRB- to-PRB mapping can be interleaved or non-interleaved. As shown in Fig.21b A, the non-SBFD slot is an UL slot with some allocated resources. For both type 0 or type 1 allocation, there will be lowest frequency (RB or RBG) where the resource allocation starts. Also, based on the upper frequency RB / RBG where the resource allocation ends, the size of the allocated resources is defined. E.g., the FDRA provided by the DCI for PUSCH indicates the allocated resources. Fig. 21b exemplarily depicts the schematic representation 2100b of a derived resource allocation for a SBFD occasion, in accordance with embodiments. In particular, Fig. 21b presents an example of derived UL resources for SBFD slot with start RB as the lowest frequency of the UL SB. Unlike Fig.21a, the scenarios A and B relate to the resource allocation being associated with an uplink, UL or U, signal or channel, such as PUSCH or PUCCH, for transmission by the UE. A non-SBFD occasion 2120A,band a SBFD occasion 2120B,bwith a DU configuration, as different time slots in the time domain, are depicted. The device may use the resource allocation occasion 2150bof the non-SBFD occasion to determine, or derive, the resources for the resource allocation for the SBFD occasion. The resource allocation occasion for the non- SBFD occasion 2120A,bmay be associated with an interleaved or non-interleaved VRB-to-PRB mapping. The derived resource allocation for the SBFD occasion 2120B,bmay be associated with a same VRB-to-PRB mapping or a different VRB-to-PRB mapping, in terms of being interleaved or non-interleaved, as the resource allocation occasion for the non-SBFD occasion 2120A,b. The derived resources 2153bmay be derived (e.g. obtained, or determined) by the UE based on or using at least one of: a start RB, an offset and a size of the derived resources, if available to the UE, or a size of the scheduled resources. filing version an,rm FH241001PEP 2024P67397EP 52 In the scenario B exemplarily shown in Fig.21b, the derived resources 2153bmay be resources which are shifted relative to the resource allocation occasion 2150bin the non-SBFD occasion of scenario B. The shift of the resources is such that the derived resources 2153b, or shifted resources, may be located, or overlap, within the UL sub-band of the SBFD occasion. The overlap may be entirely or partial, Fig.21b presents the example where the overlap between the shifted resources 2153band the UL sub-band is complete, or they fully overlap. As exemplarily depicted in Fig.21b, the allocated resources 2150bin the non-SBFD occasion may have a first start frequency in the non-SBFD occasion 2120A,bwhich is different from a second start frequency of the allocated resources 2153bin the SBFD occasion 2120B,b. The shift may be indicated to the device by means of at least one of: a physical layer signalling, e.g., using a DCI transmitted via PDCCH; a use of MAC control elements, MAC CE; an RRC signalling, e.g., via RRC IEs via PDSCH; and a fixed offset configured by the network, e.g., via MIB, SIB, or configured using a fixed formular or value for a given carrier. Further, the shift may be determined, or derived, by the device by a calculation based on a formula or by means of prediction. The formula may be configured by the gNB or the UE or pre-configured. The prediction may be based on training data on known (e.g. past, or previously carried out) SBFD and / or non-SBFD transmissions, and may be obtained using AI / ML algorithm based predictors making use of said training data. The offset (e.g. offset value) may be defined with respect to the start RB. That is, the offset may start, or extend in the frequency domain from, the start RB. For instance, the start RB could be the starting reference point. In accordance with the schematic 2100b of Fig.21b, the start RB may be a lowest frequency of the UL SB 2140B,U,b. Therefore, in case of a zero or vanishing offset value, the derived resources may extend in the frequency domain from the lowest frequency of the UL SB 2140B,U,b.The offset, or offset value, may be provided implicitly or explicitly by the gNB to the UE. For instance, in case the UE is made aware of the start RB being the starting value for the offset, an end value for the offset (e.g. an end reference frequency point) may be derived or determined by the UE. For instance, the end value of the offset could be provided explicitly or implicitly by the gNB to the UE. The size of the resources for the resource allocation in SBFD occasion may be kept same as the size of the resources for the resource allocation in the non-SBFD occasion. For instance, the size, in terms of the frequency domain, may be given as FDRA, which may be provided to the UE. For instance, the size of the resources could be indicated by the DCI for PUSCH being associated with the resource allocation for the non-SBFD occasion. filing version an,rm FH241001PEP 2024P67397EP 53 In the SBFD slot as shown in Fig.21b B, the resource allocated for non-SBFD slot is shifted such that the shifted resources are contained within the UL BWP and the UL SB. This can be done using an offset. The offset will be with respect to the start RB which is the starting reference point. The start RB can be an RBG as well or in general a frequency resource. Further, there should be an end reference frequency point for the offset. E.g., as shown in Fig. 21b, the RB / RBG with lowest frequency of the shifted resources in the SBFD slot. It can also be the RB / RBG with highest frequency of the shifted resources in the SBFD slot or the lowest / highest frequency of the shifted resources in the non-SBFD / SBFD slot. ^ The start RB can be one of the following: A. The lowest frequency of the UL SB as shown in Fig.21b. B. The highest frequency of the UL SB. C. The lowest frequency of the UL BWP as shown in Fig.21c. D. The highest frequency of the UL BWP. E. Point A in NR F. The highest / lowest frequency of a DL SB. G. The lowest / highest frequency of the resources allocated in the non- SBFD / SBFD slot. Every RB in NR is identified with the help of a number. E.g., the RBs within a BWP are known as physical RBs (PRBs). The PRB with the lowest frequency in the BWP is numbered as PRB 0 and the highest one as PRB (n-1), if there are n PRBs within the BWP. Similarly, virtual RBs (VRBs) are also numbered within a BWP and common RBs (CRBs) are numbered within a frequency band starting with point A as reference in NR. The “number” of the start RB can be the CRB number / PRB number / VRB number in NR. The direction of the numbering of frequency resources can also follow the existing frequency resource numbering in NR. In another method, the “number” of the start RB can be based on the available UL frequency resources. Available UL frequency resources are the UL resources that overlap with the UL SB and the UL BWP. E.g., the lowest frequency resource of the available UL frequency resources is numbered as “0”. When the resources are shifted using the offset, the lowest VRB and highest VRB of the allocated resources in non-SBFD slot will correspond to the lowest VRB and highest VRB respectively of the derived resources in SBFD slot. In another method, the lowest VRB and highest VRB of the allocated resources in non-SBFD slot will correspond to the highest VRB and lowest VRB respectively of the derived resources in SBFD slot. filing version an,rm FH241001PEP 2024P67397EP 54 Fig.21c exemplarily depicts a schematic representation 2100c of a derived resource allocation for a SBFD occasion, in accordance with embodiments. In particular, Fig. 21b presents an example of derived UL resources for SBFD slot with start RB as the lowest frequency of the UL BWP. Unlike Fig.21a and similar to Fig.21b, the scenarios A and B relate to the resource allocation being associated with an uplink, UL or U, signal or channel, such as PUSCH or PUCCH, for transmission by the UE. Fig.21b and 21c differ from each other in terms of different values of RBs being employed for deriving the resource allocation for the SBFD occasion. In regard to Fig.21c, UL BWP 2157c, being a subset of portion of the non-SBFD occasion 2120A,cand the SBFD occasion 2120B,c, is depicted. In the scenarios A and B, the start RB may be a lowest frequency resource of the UL BWP 2157c. Thus, the offset may be, or may be defined, with respect to the starting frequency resource of the UL-bandwidth part. The starting frequency resource of the UL- bandwidth part may be a starting reference point. As depicted in Fig. 21c, the size of the resources 2153cin the UL sub-band 2140B,U,cfor the SBFD occasion 2120B,cmay be kept same as that of the resources in the UL band of the non-SBFD occasion 2120A,c. In regard to the resources allocated 2153cin the SBFD occasion 2120B,c, the resources allocated 2150cin the non-SBFD occasion 2120A,cmay be shifted, or be offset differently, with respect to the lowest frequency resource of the UL BWP 2157c. In regard to both Figs. 21b and 21c, the following is described. An identifier of the start frequency resource could be a counter or a number. The identifier of the start frequency resource may be at least one of: a common resource block number, a physical resource block number, and a virtual resource block number. For example, a number of the start frequency resource may be based on the available UL frequency resources. A lowest VRB and a highest VRB of the allocated resources in the non-SBFD occasion may correspond to a lowest VRB and a highest VRB respectively of the derived resources in the SBFD occasion, or alternatively a lowest VRB and a highest VRB of the allocated resources in the non-SBFD occasion may correspond to a highest VRB and a lowest VRB respectively of the derived resources in the SBFD occasion. In another method, as shown in Fig.21d, the offset can be provided with a direction. Here, the start RB is the lowest frequency of the allocated resources in the non-SBFD slot. This is the RBstart. Let the start RB for the derived resources be RBstart_new. In one method, the relation between RBstart_newand RBstartwill be given by, RBstart_new= RBstart+ offset. filing version an,rm FH241001PEP 2024P67397EP 55 In another method, it will be given by, RBstart_new= (RBstart+ offset) mod (N), where mod is modulus operation and N can be the available UL resources (overlapping resources of UL BWP with UL SB) / UL SB / UL BWP. In Fig.21d B, the offset is in the direction of lower frequency and in Fig. 21d C, the offset is in the direction of higher frequency. The direction can be explicitly signaled by the gNB, e.g., using a 1-bit indication where ‘1’ stands for towards lower frequency and ‘0’ stands for towards higher frequency. The direction can also be implicitly determined by the UE. E.g., if the UE knows that the UL SB is towards or closer to the upper side of the allocated UL resources, then it considers the offset to be towards that direction. In another method, the offset can be provided without a direction and the relation between RBstart_newand RBstartwill be given by, RBstart_new= RBstart+ offset or RBstart_new= (RBstart+ offset) mod (N), where mod is modulus operation and N can be the available UL resources (overlapping resources of UL BWP with UL SB) / UL SB / UL BWP. Fig.21d exemplarily depicts a schematic representation 2100d of a derived resource allocation for SBFD occasions, in accordance with embodiments. In particular, Fig. 21d presents an example of derived UL resources for SBFD slot with offset and direction for offset. Similar to Figs. 21a-c, a non-SBFD time slot, with a UL, or U, configuration comprising a resource allocation 2150dis depicted as scenario A. The two further scenarios B and C relate to two kinds of scenario differing in a manner of derivation of the resource allocation by the device. The scenarios B and C each relate to SBFD occasions 2120A,d, 2120B,d, as time slots, with a DU configuration, wherein the SBFD occasions comprise a guard band 2135B,d, 2135C,dbetween the two sub-bands 2140B,U,d, 2140B,D,d; 2140C,U,d, 2140C,D,d. The scenario B relates to a first resource allocation 2153B,dbased on, or using, the resource allocation 2150din the non-SBFD occasion 2120A,dwhile the scenario C relates to a second resource allocation 2153C,dbased on, or using, the resource allocation 2150din the non-SBFD occasion 2120A,d.Both the first and the second resource allocations may be derived with the offset being associated with a specific direction. The specific direction could be defined in the frequency domain or the time domain or a combination of the two. For instance, the specific direction could be along a direction of increasing frequency or decreasing frequency; and / or a direction of increasing time or decreasing time. The specific direction could be derived by the device itself or it could be provided to the device by the gNB. For instance, the specific direction could be explicitly provided, or signalled, using a 1-bit indication where 1 could indicate the specific direction being a direction of decreasing frequency and 0 could indicate the specific direction being a direction of increasing frequency, or vice vera. For instance, the specific direction may be filing version an,rm FH241001PEP 2024P67397EP 56 implicitly determined if the UE is either made aware by the gNB or is already aware of the UL SB being nearer or closer to the upper frequency limit of the allocated UL resources. The UE could the determine the specific direction of the offset as being towards the upper frequency limit of the allocated UL resources, or vice versa. As exemplarily depicted in Fig.21d, the start RB, or RBG, may be a lowest frequency for the allocated resources in the non-SBFD occasion, or slot. The derived resource allocation 2153B,d, i.e. the second resource allocation, for the first SBFD occasion 2120B,d, may be offset in the direction of lower, or decreasing frequency relative to the start RB. The derived resource allocation 2153C,d, i.e. the second resource allocation, for the second SBFD occasion 2120C,d, may be offset in the direction of higher, or increasing frequency relative to the start RB. Further, as shown, both the first and the second resource allocation may have a same size of time domain resources as that associated with the allocated resources in the non-SBFD occasion. In the case where the offset is provided or determined without any direction, e.g. specific direction, a relation between start RB, or RBstart, that is the start frequency resource of the resource allocation in the non-SBFD occasion, and RBstart_new, that is the start frequency resource of the resource allocation (e.g. pertaining to the shifted resource) in a SBFD occasion, may be determined according to the determination rule: RBstart_new= RBstart+ offset. In other words, the UE may determine RBstart_newas a sum of the start RB and the offset available to the UE. Alternatively, the relation could also be given by a different determination rule: RBstart_new= (RBstart+ offset) mod (N), where N may denote the available UL resources (or DL resources in other examples of the resource allocation being associated with DL) such as overlapping resources of UL BWP with UL SB or UL BWP. In other words, the shifted frequency resources may be determined using a modulo operation applied on a frequency of the allocated resources shifted by the offset. At least in case when PUSCH frequency hopping is not enabled, for a CG PUSCH configuration without repetitions, if the transmission occasions are across SBFD symbols and non-SBFD symbols where each transmission occasion has either all SBFD or all non-SBFD symbols (i.e. Configuration 2), for PUSCH repetition type-A across SBFD symbols and non- SBFD symbols in different slots where each repetition has either all SBFD or all non-SBFD symbols (i.e. Configuration 2), and for multi-PUSCH scheduled by a single DCI across SBFD symbols and non-SBFD symbols, where each PUSCH within a slot has either all SBFD or all non-SBFD symbols (i.e. Configuration 2), and for TBoMS across SBFD symbols and non- SBFD symbols in different slots, where each transmission within a slot has either all SBFD or all non-SBFD symbols (i.e. Configuration 2), for determining starting PRB for PUSCH transmissions in SBFD symbols, - ^^^^ௌ^ி^ ^^ ௌ^ ^^^ିௌ^ி^^௧^^௧ ൌ ^^^^^௧^^௧ ^ ൫^^^^^௧^^௧ ^ ^^^^^ௌ^^^ி^^^௧൯^^^^^^^^^^^^௭ௌ^^ filing version an,rm FH241001PEP 2024P67397EP 57 o If ^^^^^ௌ^^^ி^^^௧is not configured, it is zero The above equation describes a specific instantiation of RB start determination described earlier. The above equation is an example of the shifted resource allocation (e.g. here the resource allocation pertains to UL transmissions), where the staring resource frequency for SBFD slots may be determined based on the start RB of the UL SB and the UL BWP, the offset which may depend on: a start RB of the non-SBFD slot where the original resource allocation may have been scheduled as well as an offset for the SBFD slot which may be provided to the UE, and a size of the resources of the UL SB. The offset may be a sum of the start RB of the non-SBFD slot and the provided offset. In other example, a difference, instead of the sum, of the start RB of the non-SBFD slot and the provided offset may be preferred. A modulo operation in terms of the size of the available UL resources (PRBs that are both in the active UL BWP and in the UL SB)may be performed on the offset, a result of which when combined, as a sum, may be determined by the UE as the shifted resources. If the offset for the SBFD slot is not provided to the UE, the UE may set it to zero, or any other default value, which may be a priori agreed upon between the gNB and the UE. In the case of the provided offset being zero, the formula described above may be similar to the formulas described earlier. For instance, for a ^ In NR, UL signals / channels can have intra-slot or inter-slot frequency hopping (FH). In such a case, the start RB / frequency is provided for the first hop and the start RBs / frequencies for the subsequent hops within the slot or across slots are derived using FH-offset. A legacy FH formula exists in NR. The legacy formula may be expressed as [RBstart_new= (RBstart+ FH-offset) mod (BWP size) or RBstart_new= (RBstart+ FH-offset)]. o In one method, the start RB of the first hop is determined using any of the methods stated previously. Then, for the subsequent hops, the legacy NR FH formula is used on the determined start RB to determine the start RB of the subsequent hops. o In another method, the start RB of the first hop is determined using any of the methods stated previously. The start RBs of the subsequent hops are determined using the legacy NR FH formula based on the start RB as indicated by the gNB and shifted using the offset and methods described previously. That includes that the offset may be associated with a direction. E.g., in an SBFD slot, the start RB of the first hop is determined using any of the methods stated previously where it is based on the start RB of the UL resources in non-SBFD filing version an,rm FH241001PEP 2024P67397EP 58 slots. Then, the start RB of the second hop is calculated based on the start RB of the UL resources in non-SBFD slots. It is then shifted using the FH formula. o The “size of the UL BWP” in the formula for determining start RB for subsequent hops in legacy NR is replaced with either “size of UL SB” or “available resources in UL” as shown in Fig.21e. For instance, the determination of the frequency offset for the 2ndhop, with the update that the frequency offset for 2ndhop is based on the size of UL usable PRBs which is same as “available resources in UL”. This can be applied to e.g., Msg3 PUSCH transmission. For PUSCH intra-slot frequency hopping in SBFD symbols, the starting RB in each hop is given by: For PUSCH inter-slot frequency hopping in SBFD symbols and when pusch-DMRS-Bundling is not enabled, or for inter-slot frequency hopping for a PUSCH in SBFD symbols scheduled by RAR UL grant or DCI format 0_0 with CRC scrambled by TC-RNTI, the starting RB during slot given Where ^ RB^^ ୗ^ ^^ୟ୰^is the starting PRB index of UL usable PRBs with reference to the start of UL active BWP. ^ N^^୧^^^ୗ^is the number of UL usable PRBs. ^ RB^^ୟ୰^is the starting PRB index of the first PUSCH hop with reference to the start of UL active BWP. For PUSCH transmissions with Configuration 2, RB^^ୟ୰^is the starting PRB index with reference to the start of UL active BWP after applying RB offset between non-SBFD symbols and SBFD symbols. ^ RB offset is the frequency hopping offset for PUSCH in SBFD symbols ^ Note: Definition of is unchanged from existing The equations above describe a specific instantiation of RB start determination involving frequency hopping which will be described further in relation to Fig. 21e. Here the equation may be used, for example, for: an UL inter-slot FH in SBFD symbols, wherein pusch-DMRS- Bundling may be activated or enabled; or inter-slot FH for a PUSCH in SBFD symbols. The PUSCH of the latter option may be scheduled by RAR, UL grant, or DCI format 0_0 with CRC scrambled by TC-RNTI. filing version an,rm FH241001PEP 2024P67397EP 59 Fig. 21e exemplarily depicts a schematic representation 2100e of a determination rule associated with the derived frequency resources for a SBFD occasion, in accordance with embodiments. In particular, Fig.21e presents an example of an intra-slot frequency hopping formula. The determination rule pertains to the resource allocation comprising a frequency hopping, FH. The FH may shift a frequency of used resources in subsequent occasions by a FH-offset. The FH-offset may be an offset derived or determined based on FH. The start RB, or the start frequency of the resource allocation, which could be derived such as being shifted, for the SBFD occasion may be provided to the UE, such as by the gNB of the network, corresponding to a first hop associated with the FH. The first hop may be denoted as i=0, as exemplarily done for the determination rule of Fig. 21e. The start RB could be determined using a legacy NR formula, or as already described in this disclosure. The start RB for the subsequent hops, such as the second hop i=1 and / or any further hops if configured, may be determined based on the start RB available to the UE or previously derived or used; a FH-offset, denoted by RBoffset; and a size of the SB or BWP associated with the resource allocation. Here the RB start for the subsequent hops may be same as the one used for the first hop. It may also be different and the different value, or an indication therefor could be signalled to the UE. The RB start for the first hop and / or the subsequent hops may be determined using different choices of lowest frequency of a SB, or BWP, and / or highest frequency of a SB, or BWP, available or provided to the UE. The FH offset could be configured to be different for SBFD and non-SBFD occasions. It may, for instance, be associated with or provided with a direction, such as the specific direction described earlier, in frequency and / or time domain. The FH offset could be determined based in a current slot number, or an occasion number assigned to a SBFD or non-SBFD slot, or occasion. The size of the SB or BWP may be associated with a size, such as herein in terms of the frequency domain, of a SB, or BWP, or available resources in the SBFD occasion, a SBFD slot in time domain, for which the start RB is to be determined. In determination of the start RB, for instance for the second, or further hops if configured, a modulo operation of the size of the SB or BWP may be used. The start RB for subsequent hops may be determined using a legacy NR FH formula, or it could be determined as specified in the determination rule according to Fig.21e. Further, the FH-offset for the SBFD and non-SBFD slots might be different. Different start frequency resources could be specified for the SBFD and non-SBFD slots. Thus, different FH- filing version an,rm FH241001PEP 2024P67397EP 60 offsets and different start RBs may be used in determination of the resource allocation by the UE. Figs.21f and 21g exemplarily depict schematic representations 2100f, 2100g of determination rules associated with the derived frequency resources for a SBFD occasion, in accordance with embodiments. In particular, Fig. 21f presents an example of an inter-slot frequency hopping formula with pusch-DMRS Bundling disabled, while Fig.21g presents an example of an inter-slot frequency hopping formula with pusch-DMRS Bundling enabled. The determination of the start RB of the derived resource allocation for the SBFD occasion may be performed by the UE by taking a current slot number into account for scenarios where inter-slot frequency hopping may be used, or performed. The current slot number is denoted by nµs, where s indicates slot and µ indicates a subcarrier spacing configuration associated with the slot. It is commonly known that µ indicates the numerology configured, which defines the subcarrier spacing used in a given bandwidth part, BWP. The device may use or apply FH offset as comprising a same value or different values for the SBFD and non-SBFD slots. The device may use or apply a same set of DMRS bundling parameters for both SBFD and non-SBFD slots, or the device may use or apply a different set of DMRS bundling parameters for SBFD and non-SBFD slots. The DMRS bundling parameters may comprise at least one of: pusch-FrequencyHopping-Interval and pusch- TimeDomainWindowLength. In case pusch-DMRS-Bundling is disabled (e.g. a signalling therefor may be communicated or provided to the UE), the device may determine the start RB depending on the current slot number using a determination rule, which may itself be in accordance with a legacy FH formula or be provided, either implicitly or explicitly, to the UE by the gNB. The start RB determined by the UE may be conditioned on the current slot number fulfilling one or more conditions. An example of the one or more conditions that the current slot number may fulfil may relate to its even or odd property, as depicted in Fig.21f. For instance, if the current slot number is even, the start RB may take a value which is indicated by the gNB to the UE, and if the current slot number is odd, the start RB may be take a value which is determined by a determination rule, wherein the determination rule is configured to obtain a sum of the start RB, available or previously determined by the UE, and the FH offset, and to apply a modulo operation to the sum in terms of the size of the BWP pertaining to the resource allocation. It should be noted that the one or more conditions may be different than exemplarily depicted. Another example may be the current slot number being subjected to a modulo operation relative to a different number (e.g.3, 5, or the like). filing version an,rm FH241001PEP 2024P67397EP 61 In case pusch-DMRS-Bundling is enabled (e.g. a signalling therefor may be communicated or provided to the UE), the device may determine the start RB depending on the current slot number using a determination rule, which may itself be in accordance with a legacy FH formula or be provided, either implicitly or explicitly, to the UE by the gNB. The start RB determined by the UE may be conditioned on the current slot number and / or one or more of the sets of DMRS Bundling parameters fulfilling one or more conditions. For instance, the one or more conditions may be associated with the current slot number and the pusch-FrequencyHopping-Interval. It may be that the current slot number and the pusch-FrequencyHopping-Interval are subject to a function (e.g. a function subjecting the two to a division and a floor function operation) providing a condition value. The start RB may then be conditioned on this value being even or odd. For instance, if this condition value is even, the start RB may take a value which is indicated by the gNB to the UE, and if the condition value is odd, the start RB may be take a value which is determined by a determination rule, wherein the determination rule is configured to obtain a sum of the start RB, available or previously determined by the UE, and the FH offset, and to apply a modulo operation to the sum in terms of the size of the BWP pertaining to the resource allocation. It should be noted that the one or more conditions may be different than exemplarily depicted. Another example may be the condition value being subjected to a modulo operation relative to a different number (e.g. 3, 5, or the like), and / or a different function, or the same function with different attributes, such as other parameters of the set of the DMRS Bundling parameters. In regard to the bundling parameters, a value of at least one of the sets of bundling parameters may be a minimum of: an indicated value (e.g. as indicated by the gNB to the UE) and a number of consecutive slots of a slot type (e.g. SBFD or non-SBFD). exemplarily depicts a schematic representation 2100h of a time frame comprising different time slots, in accordance with embodiments. In particular, Fig. 21h presents an example of separate slot numbering, or counting, for SBFD and non-SBFD slots. A time frame 2121 is depicted using a time-frequency grid. The time frame (e.g. a radio frame) may comprise a plurality of time slots 2120#. The time slots 2120#may have associated with themselves an actual slot count. Here the subscript may indicate the actual slot count and may range from 0 to 9, as exemplarily depicted in 2100h. The time slots may be associated with SBFD and non-SBFD configurations, and hence may be referred to as SBFD 2128 and non- SBFD 214 slots, in accordance with the nomenclature of the disclosure. A different slot count may thus be associated with the time slots, wherein the different slot count may depend on (e.g. be related to) a type of the time slot. Thus, the UE may assign, or associate, a slot type count to the time slots, wherein the slot type count is different for different slot types (e.g. SBFD, non-SBFD). filing version an,rm FH241001PEP 2024P67397EP 62 The first SBFD slot 21203, 2128 in the time frame may be assigned, or have, a SBFD slot count of 0 in contrast to the actual slot count of 3 while the last SBFD slot 21208, 2128 in the time frame may be assigned, or have, a SBFD slot count of 2 in contrast to the actual slot count of 8. The SBFD slot count may range from 0 to 2, in accordance with a number of SBFD slots in the time frame. Thus, the UE may assign a SBFD slot count to SBFD slots in the frame, wherein the SBFD slot count differs from the actual slot count. The first non-SBFD slot 21200, 2124 in the time frame may be assigned, or have, a non-SBFD slot count of 0 coinciding with the actual slot count of 0 while the last non-SBFD slot 21209, 2124 in the time frame 2121 may be assigned, or have, a non-SBFD slot count of 6 in contrast to the actual slot count of 9. The non-SBFD slot count may range from 0 to 6, in accordance with a number of non-SBFD slots in the time frame. Thus, the UE may assign a non-SBFD slot count to non-SBFD slots in the frame, wherein the non-SBFD slot count differs from the actual slot count. Fig.21i exemplarily depicts a schematic representation 2100i of derived resource allocations for SBFD and non-SBFD slots, in accordance with embodiments. In particular, Fig. 21i presents an example of frequency hopping, FH, in successive non-SBFD / SBFD slots for increased (e.g. maximum) frequency diversity. A non-SBFD time slot 2120Awith a UL, or U, configuration 21301comprising a resource allocation 21501is depicted as scenario A. Scenario B pertains to derived (e.g. shifted) resource allocation determined, or derived, using the resource allocation 21501in the non- SBFD slot 2120A. Further scenarios C-D pertain to derived (e.g. shifted) resource allocation determined, or derived, using previous resource allocations in previous time slots, which may be SBFD slots. Scenarios B and C relating to resource allocations 2153B, 2153Cin SBFD time slots 2120B, 2120Cand scenario D relating to resource allocations 21502-4in non-SBFD time slots 2120D,1-3are exemplarily depicted. In regard to scenario B, a start RB of the derived resource allocation 21531may be determined, or derived, using details associated with intra-slot frequency hopping described earlier. It is noted that in scenario B, the FH may be limited to the bandwidth of the SBFD sub-band. Since the example presented here relates to the resource allocation in the UL, the FH for scenario B may be restricted to the bandwidth of the UL subband 2140U. In regard to scenario C, the start RB of the derived resource allocation 2153cmay be determined, or derived, depending on the previous resource allocation, here that being the resource allocation 2153Bof the SBFDs slot 2120B. The derived resource allocation 2153Cmay filing version an,rm FH241001PEP 2024P67397EP 63 be derived, for example, using an offset relative to an upper frequency of the previously derived resource allocation 2153Bin the SBFD slot 2120B. The offset may depend on FH such as the FH-offset, described previously. The FH-offset here may be specified in a direction of increasing frequency. Scenario D depicts three different resource allocations 2150D,1-3in respective non-SBFD slots 2120D,1-3. The resource allocation 2150D,1in the non-SBFD slot 2120D,1may be derived, or determined, using the resource allocation 2153Cin the SBFD slot 2120C. As exemplarily depicted, the resource allocation 2150D,1may be derived, for example, using an offset relative to an upper frequency of the previous resource allocation 2150Cin the SBFD slot 2120C. This offset may depend on FH such as the FH-offset, described previously. The FH-offset here may be specified in a direction of increasing frequency, similar to the previously used FH-offset; however, a value, or magnitude, of the FH offset here may be greater than the one used previously. The direction and / or magnitude, either as an absolute value or a value relative to the previously used FH-offset, may be provided explicitly or implicitly to the UE by the gNB. The direction and / or magnitude of the FH offset may be configured so as to obtain an increased, or maximum, frequency diversity. This means that a range of allowable, or accessible, frequencies by means of inter-slot FH may be increased, or maximised. As exemplarily depicted for non-SBFD slots 2120D,2, 2120D,3with UL, or U, configurations, the resource allocation 2150D,2, 2150D,3could be determined by the previous resource allocation of the previous non-SBFD slot 2120D,1.2120D,2respectively. Fig.21j exemplarily depicts a schematic representation 2100j of derived resource allocations for SBFD and non-SBFD slots, in accordance with embodiments. In particular, Fig. 21j presents an example of frequency hopping, FH, in successive non-SBFD slots, using same start RB of the previous slot. Similar to Fig.21i, Fig.21j depicts three scenarios A, B and C, where A relates to a resource allocation 2150Ain a first non-SBFD slot 2120A, B relates to a resource allocation 2153Bwhich may be determined, or derived, using the resource allocation 2150Ain the previous slot 2120A(the first non-SBFD slot) and C relates to a resource allocation 2153Cwhich may be derived using FH-based offset applied to the resource allocation 2153Bin the previous slot 2120B(the non-SBFD slot in scenario B). Further details described in reference to Fig. 21i may be applicable here either in addition or as alternatives. Two successive non-SBFD slots, the second non-SBFD slot 21202and the third non-SBFD slot 21203, are further depicted. In regard to the second non-SBFD slot 21202, the resource allocation 21502may be derived using a same RB as the resource allocation 2153Cof the previous slot, in this instance the previous slot being the SBFD slot 2120Cof scenario C. This filing version an,rm FH241001PEP 2024P67397EP 64 means that no FH may be applied in determination of the resource allocation 21502in the second non-SBFD slot 21202. Thus, the UE may be indicated or signalled to use the same RB as the previous slot, or to not perform FH in deriving the resource allocation for the second non-SBFD slot 21202. In regard to the third non-SBFD slot 21203, its resource allocation may be derived, or determined, based on the resource allocation 21502of the previous slot, that is, the second non-SBFD slot 21202. As exemplarily depicted, in the course of deriving the resource allocation 21503, a different start RB for it may be used or derived along with a FH-offset along a direction of increasing frequency. Such applications of the FH-offset and possible start RBs have already been described in the disclosure. Fig. 21k exemplarily depicts a schematic representation 2100k of additional resource allocations for SBFD and non-SBFD slots, in accordance with embodiments. In particular, Fig. 21k presents an example of ignoring resources and use of additional resources in frequency domain in SBFD and non-SBFD slots. A SBFD slot 2120Awith a DU configuration associated with a D sub-band 2140Dand a U sub- band 2140Ucomprising a guard band between them is depicted. The U sub-band 2140Ucomprises a resource allocation 2150Awhich may not be entirely, or fully, overlapping with the U sub-band 2140U. As exemplarily depicted, the resource allocation 2150Amay be scheduled to be partially outside, or fall outside of the UL SB 2140U. That is, one or more portions 2157 of the resource allocation 2150A, as scheduled or configured, may fall outside the SB, here the UL SB 2140U, of the SBFD slot 2120A(e.g. or a band of a non-SBFD slot, if the slot type is a non-SBFD). As described earlier in the disclosure, the UE may ignore the one or more portions 2157 of the resource allocation 2120Awhich fall, or are scheduled, outside the SB of the SBFD slot. The UE may be aware of size of the one or more portions 2157 of the resource allocation 2150Awhich it may ignore. Therefore, the UE may use additional resources in further available slots for allocating such ignored resources 2157. In regard to additional resources, two different scenarios B and C are depicted. Scenario B relates to a SBFD slot 2120B with a DU configuration wherein the resource allocation 2150B within the UL SB 2140Umay be configured to comprise one or more portions 2159 of additional resources. Scenario C relates to a non-SBFD slot 2120C with a U band 2130C wherein the resource allocation 2150C may be configured to comprise one or more portions 2159 of additional resources. For both scenarios, it is depicted in Fig.21k that the one or more portions 2159 of additional resources may be same as the originally scheduled resource allocation 2150A in the time domain. Further, a size of the one or more portions 2159 of the additional resources may be same as the size of the one or more portions 2157 of the ignored resource filing version an,rm FH241001PEP 2024P67397EP 65 allocation. This size may be provided to the UE by the gNB by means of explicit or implicit signalling. Alternatively, the UE may itself retain information about the ignored resources 2157, such as their size and therefore may adapt the resource allocation pertaining to the one or more portions 2159 of additional resources in accordance with the retained information of the ignored resources 2157. Additionally, it may be apparent to the UE in which direction the one or more portions 2159 of the additional resources may be scheduled. This direction may be based on an availability of the resources in the time slot. In case of the SBFD slot 2120B, since no resources may be scheduled in the DL SB, the UE may derive or determine that the direction which is available for the additional resources 2159 may be in a direction of increasing frequency. In case of the non-SBFD slot 2120C, the UE may select or choose, either upon additional signalling or rely upon communication by the gNB, in which direction the additional resources 2159 shall be scheduled. In the example of Fig. 21k, the additional resources 2159 in the non-SBFD slot 2120C are depicted in a direction of decreasing frequency. Additional directions, such as along increasing time or decreasing time, may be used, if available for the UE to use; in such cases, the additional resources 2159 may not be same in the time domain as the originally scheduled resource allocation 2150A. In case of inter-slot FH, the following additional methods are possible: a) The FH-offsets for SBFD and non-SBFD slots are different. That is, the FH-offset used for SBFD slots is different from the FH-offset used for non-SBFD slots and they might be independent. Instead of using the current slot number in the formula as shown in Fig.21f and Fig.21g, an occasion number of SBFD / non-SBFD slot is. E.g., SBFD slots and non-SBFD slots are numbered separately in a frame. An example is shown in Fig. 21h. Also, instead of “mod 2”, some other number can be used. b) The FH-offsets for SBFD and non-SBFD slots are the same. c) The pusch-FrequencyHopping-Interval can be same or different for SBFD and non- SBFD slots. Let the number of consecutive SBFD slots where frequency hopping is applicable be ‘n’ and the value of pusch-FrequencyHopping-Interval for SBFD slots be ‘m’ slots. In one method, if ‘n’ is less than ‘m’, then the value of ‘n’ is used as the pusch- FrequencyHopping-Interval. Similar method can be followed for non-SBFD slots. d) In another method, the start RB of the resources in a non-SBFD / SBFD slot will depend on a previous transmission / reception irrespective of SBFD or non-SBFD slot such that maximum frequency diversity is achieved in case of inter-slot FH. An example is shown in Fig.21i. The UL resources in the non-SBFD slot are shifted with respect to the UL resources in the SBFD slot, e.g., using an offset. It can be the other way round as well, that is, the UL resources in the SBFD slot are shifted with respect to the UL resources filing version an,rm FH241001PEP 2024P67397EP 66 in the non-SBFD slot. This can be based on explicit signaling or implicitly derived. Furthermore, the signaling can be contained in a joint configuration, for SBFD and non- SBFD slots, or in individual signaling, separate configurations, in the configuration for SBFD slots or in the configuration of non-SBFD slots. The FH-offset can be the same for all slots. The FH itself, can be based on the current FH formula in NR. e) In another embodiment, the start RB in a slot is same as the start RB in the previous slot if there is a transition from SBFD to non-SBFD slot or vice versa. An example is shown in Fig.21j. The start RB of the initial non-SBFD slot is the same as the previous SBFD slot. FH is then applied to the successive non-SBFD slots. ^ The size of the resources is kept same as the size of the frequency domain resources for non-SBFD slots or a new size is provided. If the size is such that it goes beyond the DL SB or DL BWP, then the resources outside the DL SB are ignored by the UE. This is illustrated in Fig.21 B. In case of UL resources as shown in example Figures 21b and 21c, the same method can be followed if the shifted resources fall outside the UL BWP / UL SB. This is shown in Fig. 21k. Further, instead of completely ignoring the resources, the resources can be spread / split / postpone across time / frequency / spatial / code domain, e.g. as described in the earlier sections. Also, additional resources can in frequency domain can be used if available to compensate for the loss in frequency resources as shown in Fig.21k B. Fig.21k C shows additional resources being used in frequency domain when there are more available frequency resources. In other words as seen, for example, in Fig.21 and / or Fig.21k, the distribution of resources within a bandwidth part may vary for different slots, e.g., based on implementing an UD, a DU or DUD scheme and / or with regard to a varying amount of resources associated with uplink or downlink within a same or different scheme. The distribution of resources allocated for transmission and resources allocated for reception within a bandwidth part, BWP, may, thus, be different for different occasions. A size of the resources in a SBFD slot may be kept same as the size of the frequency domain resources for non-SBFD slots or wherein a new size is provided. Same is true for different slots of a same type such as SBFD. The device may ignore resources of an occasion outside the bandwidth part, e.g., the UL SB / UL BWP for transmission; or may spread, split and / or postpone at last a part of the resources outside the UL SB / UL BWP across a domain relating to at least one of a time domain, a frequency domain, a spatial domain and a code domain filing version an,rm FH241001PEP 2024P67397EP 67 Fig.22 exemplarily depicts a schematic representation 2200 of a resource allocation for slots with SBFD configurations in a wireless communication network, in accordance with embodiments. In particular, Fig.22 presents an example of a scheduled SPS occasion and a derived SPS occasion in respective SBFD slots. This example relates to case 2 of the previously described Fig.20. A first SBFD time slot 2220Awith a UD configuration relates to scenario A. The first SBFD time slot 2220Acomprises a UL sub-band 2240U,A, a DL sub-band 2240D,Aand a single guard band 2235Abetween them. A resource allocation 2250A, here being the SPS, may be scheduled such that it overlaps with the UL SB 2240U,A, the guard band 2235Aand the DL SB 2240D,A. Since the resource allocation, the SPS, is configured for reception in DL, a part, or portion, of the resource allocation as scheduled may be unavailable for SPS reception to the UE. Thus, the UE may derive, or determine, a different resource allocation (e.g. actual resource allocation) 2253A. This may be done to benefit from using resources which may be available to the UE. The actual resource allocation may relate to different resources in the frequency domain. The UE may determine, or derive, the different resource allocation 2253A based on a starting frequency resource (e.g. start RB), an offset and a size of the scheduled resource allocation. For instance, the starting frequency resource may be an upper frequency value of the SB which is suited, or adapted, for the resource allocation. For example, the starting frequency resource, start RB, may be an upper frequency of the DL SB 2240D,A. For instance, the start RB may comprise a specific distance, in the frequency domain, to the UL SB (or the DL SB). For instance, the specific distance could be a minimum or a maximum distance from the UL SB within the time slot, in the frequency domain. Here the distance may be specified as distance relative to either of the start or the end of the UL SB. The start RB may be a reference RB outside the DL SB. The offset, which may, for instance, be defined relative from the starting frequency resource may be provided by the gNB to the UE, or could be determined by the UE. The size of the resources may be kept same as the size of the frequency domain resources of the scheduled, or original, resource allocation. Further options, or choices, for any of the following described in this disclosure: the start RB, the offset, and the size of the resources, are applicable either as additions or alternatives. A second SBFD time slot 2220B, different from the first SBFD time slot 2220Awith a UD configuration relates to scenario B. The first SBFD time slot 2220Acomprises a UL sub-band 2240U,B, a DL sub-band 2240D,Band a single guard band 2235Bbetween them. The UL sub- band 2240U,Bmay be larger in bandwidth in the frequency domain than the UL sub-band filing version an,rm FH241001PEP 2024P67397EP 68 2240U,A, while the DL sub-band 2240D,Bmay be smaller in bandwidth in the frequency domain than the DL sub-band 2240D,A. Similar to scenario A, in scenario B, the resource allocation 2250Bas originally scheduled may overlap with the UL SB 2240U,B, the guard band 2235Band the DL SB 2240D,B. As described earlier, the UE may derive, or determine, a different, or an actual, resource allocation, depending on at least one of: a starting frequency resource, an offset and a size of the resources. In scenario B, it may be that the one or more portions 2257 of the different resource allocation 2253B may fall or overlap outside of the DL SB. Therefore, the UE may ignore the one or more portions 2257 of the actual resource allocation 2253Bwhich it derived or determined (or which it was provided). o Case 2: UD scenario with the scheduled SPS occasion partially overlapping with UL SB and / or guard band. The actual frequency domain resources for SBFD slots to receive SPS can be derived as explained below. ^ The frequency domain resources for SBFD slots start from the start of the DL SB which is nearer to the UL SB. Also, an offset can be provided by the gNB. This is illustrated in Fig. 22 A. The start RB can have a specific distance to the UL SB, e.g., be the closest RB to the UL SB or at maximum distance and it can be within the DL SB or a reference RB outside the DL SB. ^ The size of the resources is kept same as the size of the frequency domain resources for non-SBFD slots or a new size is provided. If the size is such that it goes beyond the DL SB, then the resources outside the DL SB are ignored by the UE. This is illustrated in Fig.22 B. Fig.23 exemplarily depicts a schematic representation 2300 of different resource allocation for slots with SBFD configurations in a wireless communication network, in accordance with embodiments. In particular, Fig. 23 presents an example of scheduled SPS occasions and derived SPS occasion in respective SBFD slots. This example relates to case 3 of the previously described Fig.20. The SBFD slots 2320A-Cpertaining to the three depicted scenarios A, B and C each comprise a DUD configuration. This means that the SBFD slots 2320A-Ccomprise three SBs 2340, two of which are DL SBs 2340D1, D2and one which is a UL SB 2340U. Further, the SBs 2340 are separated from each other by guard bands 2335, resulting in two guard bands 2335 in each time slot. filing version an,rm FH241001PEP 2024P67397EP 69 In scenario A, the resource allocation 2350A, here SPS, may be scheduled or falling entirely within the UL SB 2340U. The device may derive, or determine, an actual resource allocation 2353Abased on: a starting frequency resource, start RB; an offset and a size of the original resource allocation, in terms of the frequency domain. As exemplarily depicted, the starting frequency resource may be an upper frequency of the second DL SB 2340D2and the size of the resource allocation for the actual resource allocation 2353Amay be kept same as the size of the original resource allocation 2350A, in the frequency domain. In this instance, the device may determine itself, or be provided information therefor, which of the two DL SBs 2340D1,2340D2is chosen, or selected, or configured for the actual resource allocation 2353A. This choice or selection may be based on the start RB and / or the offset. For instance, the offset may be provided to the UE by the gNB. The actual resource allocation 2353Amay be completely, or entirely, overlapping, or contained, within the second DL SB 2340D2. In scenario B, the resource allocation 2350B, here SPS, may be scheduled or falling overlapping with the UL SB 2340Uand the two guard bands 2335. As before, the device may derive, or determine, an actual resource allocation 2353Bbased on: a starting frequency resource, start RB; an offset and a size of the original resource allocation 2350B, in terms of the frequency domain. Details described in scenario A may be applied onto scenario B and are thus not repeated. In this instance, one or more parts 2357 of the actual resource allocation 2353B, as determined by the device or as provided to it by the gNB, may fall, or occur or overlap, outside of the second DL SB 2340D2. Therefore, the UE may ignore the one or more portions 2357 of the actual resource allocation 2353Bwhich it derived or determined (or which it was provided). In scenario C, the resource allocation 2350C, here SPS, may be scheduled or falling entirely within the UL SB 2340U. As before, the device may derive, or determine, an actual resource allocation 2353 based on: a starting frequency resource, start RB; an offset and a size of the original resource allocation 2350C, in terms of the frequency domain. Details described in scenario A and B may be applied onto scenario B and are thus not repeated. In this instance, the device may distribute, or partition, the original resource allocation 2350Cinto a plurality of portions 2353C,1,2353C,2together comprising the actual resource allocation 2353C. The plurality of portions 2353C,1,2353C,2may be arranged, or placed, or scheduled, equally across the DL SBs 2340D1, 2340D2, or the SBs, which are suitable for the resource allocation, in addition to the original resource allocation 2350C,3. It is noted that this instance may relate to a spreading of the original resource allocation, according to which there may still be a portion of the resource allocation in a UL SB. This partitioning, or distribution, may be performed in a manner so that a size of the actual resource allocation 2353Cmay remain the same as the size of the original resource allocation 2350C. Further, this partitioning, or distribution, could be performed filing version an,rm FH241001PEP 2024P67397EP 70 in a manner so that resources allocated in each SB may be equal to each other. That is, this partitioning, or distribution, may be performed in a manner so that the plurality of portions 2353C,1,2353C,2are equal to each other. However, the plurality of portions 2353C,1,2353C,2may not be restricted to simply be equal. As exemplarily depicted in Fig.23, a sum of the plurality of portions 2353C,1,2353C,2may equal the original resource allocation 2350C, in terms of the frequency domain. o Case 3: DUD scenario with the scheduled SPS occasion fully overlapping with UL SB and / or guard band. The actual frequency domain resources for SBFD slots to receive SPS can be derived as explained below. ^ The frequency domain resources for SBFD slots start from the start RB of one of the DL SBs which is nearer to the UL SB. Also, an offset can be provided by the gNB. Which DL SB to choose can be indicated by the gNB or define in the specification. This is shown in Fig.23 A. The start RB of the claim above can have a specific distance to the UL SB, e.g., be the closest RB to the UL SB or at maximum distance and it can be within one of the DL SBs or a reference RB outside the DL SB. ^ The size of the resources is kept same as the size of the frequency domain resources for non-SBFD slots. If the size is such that it goes beyond the DL SB, then the resources outside the DL SB are ignored by the UE. This is shown in Fig.23 B. ^ Another way is to consider the total number of RBs (size of the scheduled frequency domain resources) and spread it equally across the 2 DL SBs such that the available number of DL resources remain the same. Also, the size can be provided by the gNB. This is shown in Fig.23 C. ^ In another way, the UE chooses one of the 2 ways as explained above which maximizes the number of available DL RBs for SPS reception. Fig.24 exemplarily depicts a schematic representation 2400 of different resource allocation for slots with SBFD configurations in a wireless communication network, in accordance with embodiments. In particular, Fig. 24 presents an example of scheduled SPS occasions and derived SPS occasion in respective SBFD slots. This example relates to case 4 of the previously described Fig.20. filing version an,rm FH241001PEP 2024P67397EP 71 The SBFD slots 2420A-Cpertaining to the three depicted scenarios A and B each comprise a DUD configuration. This means that the SBFD slots 2420A,Bcomprise three SBs 2440, two of which are DL SBs 2440D1, D2and one which is a UL SB 2440U. Further, the SBs 2440 are separated from each other by guard bands 2435, resulting in two guard bands 2435 in each time slot. In scenario A, the resource allocation 2450A, here SPS, may be scheduled or falling as overlapping with, or across, the two DL SBs 2440D1, 2440D2, the UL SB 2440Uand the two guard bands 2435. The device may derive, or determine, an actual resource allocation 2453Abased on: a starting frequency resource, start RB; an offset and a size of the original resource allocation, in terms of the frequency domain. As exemplarily depicted, the starting frequency resource may be an upper frequency of the second DL SB 2440D2. The size of the resource allocation for the actual resource allocation 2453Amay not be kept same as the size of the original resource allocation 2450A, in the frequency domain and as exemplarily depicted, could be smaller. That is, the actual resource allocation may be smaller, in terms of its size in the frequency domain, than the original resource allocation. In this instance, the device may determine itself, or be provided information therefor, which of the two DL SBs 2440D1,2440D2is chosen, or selected, or configured for the actual resource allocation 2453A. This choice or selection may be based on the start RB and / or the offset. For instance, the offset may be provided to the UE by the gNB. As exemplarily depicted, the offset may correspond to a portion of the original resource allocation which overlaps with the SB in which the actual resource allocation is scheduled, or arranged, or configured. In the instance of scenario A, one or more parts 2457 of the actual resource allocation 2453A, as determined by the device or as provided to it by the gNB, may fall, or occur or overlap, outside of the second DL SB 2440D2. Therefore, the UE may ignore the one or more portions 2457 of the actual resource allocation 2453Awhich it derived or determined (or which it was provided). In scenario B, two SBFD time slots with DUD configurations are depicted. The first time slot 2420B1is same as the first time slot 2420Ain scenario A and is depicted only with the scheduled, or original, resource allocation 2350B3. The second time slot 2420B2depicts an actual resource allocation 2453Bwhich may be derived or determined by the device. As before, the device may derive, or determine, an actual resource allocation 2453 based on: a starting frequency resource, start RB; an offset and a size of the original resource allocation 2450C, in terms of the frequency domain. Details described in scenario A and B may be applied onto scenario B and are thus not repeated. In this instance, the device may split, or distribute, or partition, the original resource allocation 2450Binto a plurality of portions 2453B,1,2453B,2together comprising the actual resource allocation 2453B, wherein the plurality of portions 2453B,1,2453B,2are arranged in those SBs 2453D1,2453D2(e.g. first DL SB and second DL SB filing version an,rm FH241001PEP 2024P67397EP 72 here) which are suitable for the resource allocation. It is noted that this instance may relate to a splitting of the original resource allocation, according to which there may be no portion of the resource allocation in a UL SB. This partitioning, or distribution, may be performed in a manner so that a size of the actual resource allocation 2453Bmay remain the same as the size of the original resource allocation 2450C. Further, this partitioning, or distribution, could be performed in a manner so that resources allocated in each SB may be equal to each other. That is, this partitioning, or distribution, may be performed in a manner so that the plurality of portions 2453B,1,2453B,2are equal to each other. However, the plurality of portions 2453B,1,2453B,2may not be restricted to simply be equal. As exemplarily depicted in Fig.24, a sum of the plurality of portions 2453B,1,2453B,2may equal the original resource allocation 2450B, in terms of the frequency domain. The first portion 2453B,1may occupy an entirety of the first DL SB in the frequency domain, while the second portion 2453B,2may occupy a subset of the second DL SB in the frequency domain. o Case 4: DUD scenario with the scheduled SPS occasion partially overlapping with UL SB and / or guard band and partially overlapping with both the DL SBs. The actual frequency domain resources for SBFD slots to receive SPS can be derived as explained below. ^ The frequency domain resources for SBFD slots start from the start RB of one of the DL SBs which is nearer to the UL SB. Also, an offset can be provided by the gNB. Which DL SB to choose can be indicated by the gNB or define in the specification. This is shown in Fig.24 A. The start RB can have a specific distance to the UL SB, e.g., be the closest RB to the UL SB or at maximum distance and it can be within one of the DL SBs or a reference RB outside the DL SB. ^ The size of the resources is kept same as the size of the frequency domain resources for non-SBFD slots or a new size is provided. If the size is such that it goes beyond the DL SB, then the resources outside the DL SB are ignored by the UE. This is also shown in Fig.24 A. ^ Another way is to consider the total number of RBs (size of the scheduled frequency domain resources) and spread it equally across the 2 DL SBs such that the available number of DL resources remain the same. Also, the size can be provided by the gNB. This is shown in Fig.24 B. ^ In another way, the UE chooses one of the ways as explained above which maximizes the number of available DL RBs for SPS reception. filing version an,rm FH241001PEP 2024P67397EP 73 Fig.25 exemplarily depicts a schematic representation 2500 of different resource allocation for slots with SBFD configurations in a wireless communication network, in accordance with embodiments. In particular, Fig. 25 presents an example of scheduled SPS occasions and derived SPS occasion in respective SBFD slots. This example relates to case 5 of the previously described Fig.20. The SBFD slots 2520A-Cpertaining to the three depicted scenarios A and B each comprise a DUD configuration. This means that the SBFD slots 2520A,Bcomprise three SBs 2540, two of which are DL SBs 2540D1, D2and one which is a UL SB 2540U. Further, the SBs 2540 are separated from each other by guard bands 2535, resulting in two guard bands 2535 in each time slot. In scenario A, the resource allocation 2550A, here SPS, may be scheduled or falling as overlapping with, or across, one of the two DL SBs, here the one DL SB being 2540D2; the UL SB 2540Uand one of the two guard bands 2535, here the guard band being between the UL SB and the second DL SB. The device may itself determine which of the two DL SBs it may overlap with, or it could be provided signalling, or communication, therefor by the gNB. The device may derive, or determine, an actual resource allocation 2553Abased on: a starting frequency resource, start RB; an offset and a size of the original resource allocation, in terms of the frequency domain. As exemplarily depicted, the starting frequency resource may be an upper frequency of the second DL SB 2540D2. The size of the resource allocation for the actual resource allocation 2553Amay not be kept same as the size of the original resource allocation 2550A, in the frequency domain and as exemplarily depicted, could be smaller. That is, the actual resource allocation may be smaller, in terms of its size in the frequency domain, than the original resource allocation. In this instance, the device may determine itself, or be provided information therefor, which of the two DL SBs 2540D1,2540D2is chosen, or selected, or configured for the actual resource allocation 2553A. This choice or selection may be based on the start RB and / or the offset. For instance, the offset may be provided to the UE by the gNB. As exemplarily depicted, the offset may correspond to a portion of the original resource allocation which overlaps with the SB in which the actual resource allocation is scheduled, or arranged, or configured. In the instance of scenario A, one or more parts 2557 of the actual resource allocation 2553A, as determined by the device or as provided to it by the gNB, may fall, or occur or overlap, outside of the second DL SB 2540D2. Therefore, the UE may ignore the one or more portions 2557 of the actual resource allocation 2553Awhich it derived or determined (or which it was provided). filing version an,rm FH241001PEP 2024P67397EP 74 In scenario B, two SBFD time slots with DUD configurations are depicted. The first time slot 2520B1is same as the first time slot 2520Ain scenario A and is depicted only with the scheduled, or original, resource allocation 2350B3. The second time slot 2520B2depicts an actual resource allocation 2553Bwhich may be derived or determined by the device. As before, the device may derive, or determine, an actual resource allocation 2553 based on: a starting frequency resource, start RB; an offset and a size of the original resource allocation 2550C, in terms of the frequency domain. Details described in scenario A and B may be applied onto scenario B and are thus not repeated. In this instance, the device may split, or distribute, or partition, the original resource allocation 2550Binto a plurality of portions 2553B,1,2553B,2together comprising the actual resource allocation 2553B, wherein the plurality of portions 2553B,1,2553B,2are arranged in those SBs 2553D1,2553D2(e.g. first DL SB and second DL SB here) which are suitable for the resource allocation. It is noted that this instance may relate to a splitting of the original resource allocation, according to which there may be no portion of the resource allocation in a UL SB. This partitioning, or distribution, may be performed in a manner so that a size of the actual resource allocation 2553Bmay remain the same as the size of the original resource allocation 2550C. Further, this partitioning, or distribution, could be performed in a manner so that resources allocated in each SB may be equal to each other. That is, this partitioning, or distribution, may be performed in a manner so that the plurality of portions 2553B,1,2553B,2are equal to each other. However, the plurality of portions 2553B,1,2553B,2may not be restricted to simply be equal. As exemplarily depicted in Fig.25, a sum of the plurality of portions 2553B,1,2553B,2may equal the original resource allocation 2550B, in terms of the frequency domain. The first portion 2553B,1and the second portion 2553B,2may merely occupy a subset, or a part of their respective DL SBs in the frequency domain. o Case 5: DUD scenario with the scheduled SPS occasion partially overlapping with UL SB and / or guard band and partially overlapping with only one of the DL SBs. The actual frequency domain resources for SBFD slots to receive SPS can be derived as explained below. ^ The frequency domain resources for SBFD slots start from the start RB of one of the DL SBs which is nearer to the UL SB. Also, an offset can be provided by the gNB. Which DL SB to choose can be indicated by the gNB or defined in the specification. Also, the UE can select the DL SB with which the SPS occasion partially overlaps. This is shown in Fig. 25 A. The start RB can have a specific distance to the UL SB, e.g., be the closest RB to the UL SB or at maximum distance and it can be within one of the DL SBs or a reference RB outside the DL SB. filing version an,rm FH241001PEP 2024P67397EP 75 ^ The size of the resources is kept same as the size of the frequency domain resources for non-SBFD slots or a new size is provided. If the size is such that it goes beyond the DL SB, then the resources outside the DL SB are ignored by the UE. This is also shown in Fig.25 A. ^ Another way is to consider the total number of RBs (size of the scheduled frequency domain resources) and spread it equally across the 2 DL SBs such that the available number of DL resources remain the same. Also, the size can be provided by the gNB. This is shown in Fig.25 B. ^ In another way, the UE chooses one of the ways as explained above which maximizes the number of available DL RBs for SPS reception. In all the above cases, the TDRA can be kept the same as in case of non-SBFD slots or a different TDRA can be provided or spreading / splitting of the resources can be done over time domain resources. Further, a parameter can be provided in RRC or DCI by the gNB to indicate whether the UE derives the frequency domain resources for the SBFD symbols from the frequency domain resources of the non-SBFD symbols. Depending on the case, the UE can implicitly choose how to derive the resources. In another way, the UE can be explicitly indicated by the gNB, which way to derive the resources. Also, the derivation of frequency domain resources for SBFD symbols depends on UE capability which can be informed by the UE to the gNB. If the UE is not capable or the gNB does not indicate the UE to derive the resources, then the UE can use the same frequency domain resources as scheduled for SBFD symbols and receive SPS only in the available DL resources or follow any of the methods to receive SPS as discussed previously in the invention. ^ Another method is to have an SPS-Config with 2 SPS-Config indices, one for SBFD symbols and the other for non-SBFD symbols. The SPS-Config can have parameters that are common for both SBFD and non-SBFD symbols like periodicity as well as parameters separate for both like MCS table.2 separate DCIs are used to active the 2 SPS config indices. The 2 DCIs can have different TDRAs and FDRAs. ^ In another method, the VRB-to-PRB mapping is done across multiple time domain resources to compensate for the fewer available DL resources in SBFD symbols. E.g., the available frequency domain resources in SBFD symbols are spread across the next 3 symbols / slots when there is a 1 / 3 reduction in the number of resources in SBFD symbols as compared to non-SBFD symbols. filing version an,rm FH241001PEP 2024P67397EP 76 In all the above cases, separate MCS can also be provided with the separate FDRAs. The same procedures for MCS indication / derivation explained previously can be used with separate FDRAs. Also, similar procedures for HARQ process ID as discussed in the previous section will be applicable here. Also, similar or same procedures for DMRS bundling as discussed in the previous section will be applicable here. Only SPS PDSCH reception occasion in one symbol type is valid and SPS PDSCH reception occasion in the other symbol type is invalid. In this case, when the gNB provides an SPS-Config, the SPS-Config is valid for any one of the symbol types; SBFD or non-SBFD. That is, if the SPS-Config is valid only for non-SBFD symbols, then an SPS occasion falling on the SBFD slots will be ignored by the UE. This is shown in Fig.26. SPS occasions in slots 0 and 4 are valid but not in slot 2 since it is an SBFD slot. Fig. 26 exemplarily depicts a schematic representation 2600 of a resource allocation in a wireless communication network, in accordance with embodiments. In particular, Fig. 26 presents an example of SPS occasion being valid for non-SBFD slots while being invalid for other slots, such as SBFD slots. Fig.26 depicts five slots 26200-4, numbered 0 to 4, some 26200,4of which may be SBFD slots 2628 and rest 262001-3of which may be non-SBFD slots 2624 using a time-frequency grid. The SBFD slots 26200-3, 2628 may be in a UD configuration (e.g. or DU configuration, if referred to differently in a direction of increasing frequency). This means that each of the SBFD slots may comprise a UL SB and a DL SB. A guard band may be separating the UL and the DL SBs. Different SPS occasions 26500,3,4in different slots may be scheduled, or arranged, or configured. The subscript on the SPS occasion may indicate which time slot they could be scheduled or configured. It may be that the device derives, or determines, that a first time-frequency occasion, such as SPS occasions, of the resource allocation, such as being associated with a SPS PDSCH reception occasion, may be valid or allowable in a first symbol type, here exemplarily depicted as non-SBFD, and may be invalid or unallowable in a second symbol type, here exemplarily depicted as SBFD. Therefore, as shown in Fig.20, the SPS occasions 26500, 26504 may be determined as valid SPS occasions and the SPS occasion 26503 may be determined as an filing version an,rm FH241001PEP 2024P67397EP 77 invalid SPS occasion by the device. Thus, the SPS occasion 26503 may be ignored, or suppressed, or muted, by the device. In this regard, the device may ignore, or suppress, or mute, any SPS occasion falling within a SBFD slot or SBFD symbol. The converse scenario where the SPS occasion may be ignored, or muted, or suppressed, when falling within a non- SBFD symbol or non-SBFD slot is also feasible. Further, the device may use a same HARQ process ID irrespective of the symbol type. The choice of a symbol type being determined valid or invalid may be indicated or provided (e.g. signalled, or communicated) with the resource allocation to the device. For example, this provision may be using an SPS-Config. The indication or provision could be implicit or explicit and may be achieved, or performed, using one or more parameters. Additionally, or alternatively, this indication or provision may be subject to one or more criterions. For example, if the first time-frequency occasion occurs, or falls, on a non-SBFD symbol or slot, then further occasions, here being SPS, may be valid for subsequent non-SBFD symbols or slots and invalid for other symbols or slots. A further example of a condition may involve requiring the type of slots or symbols to be consecutive to be considered valid or invalid. Another example of a condition may involve an occurrence of the symbols or slots to be in accordance with a pattern, the pattern being pre-configured or pre-determined by the gNB and provided to the UE. There might be a case where one occasion of the SPS falls across both SBFD and non-SBFD symbols. This is shown in Fig.8. In such a case, the UE either ignores that SPS occasion or the UE treats all the symbols in that occasion to be of a particular type. E.g., if at least n number of symbols in the occasion are SBFD symbols then, all the symbols in that occasion are treated as SBFD symbols. The number n can be defined in the specification or provided by the gNB. The different ways to implement this are: ^ The gNB explicitly indicates to the UE whether the SPS-Config is valid for SBFD symbols or non-SBFD symbols using some parameter. o The explicit indication is based on a UE capability. E.g., if the UE is capable of handling both SBFD and non-SBFD symbols using one SPS-Config, then this indication is not provided by the gNB. ^ The UE implicitly determines whether the SPS-Config is valid for SBFD symbols or non-SBFD symbols based on certain rules. E.g., if the first SPS occasion falls on a non- SBFD slot, then the SPS is valid only for subsequent non-SBFD slots. filing version an,rm FH241001PEP 2024P67397EP 78 Also, similar procedures for HARQ process ID as discussed in the previous section will be applicable here. Also, similar or same procedures for DMRS bundling as discussed in the previous section will be applicable here. Based on the above, aspects of the present invention may be formulated as follows. It is noted, however, that the disclosure related to offsets described herein may be implemented independently from a consideration about using allocated resources based on whether the resources are within a subband full duplex, SBFD, time-frequency occasion. That is, as an alternative or in addition to a device being adapted to determine a resource allocation allocating resources of the wireless communication network, e.g., for uplink, UL, and / or downlink, DL, and / or sidelink and to use the allocated resources based on whether the resources are within a subband full duplex, SBFD, time-frequency occasion, a device may also be adapted to determine an allocation of resources, the allocation allocating resources of the wireless communication network to the device, e.g., for uplink, UL, and / or downlink, DL, of the device and to apply an offset to the allocation based on whether the occasion relates to a subband full duplex, SBFD, time-frequency occasion. Those aspects may be combined with each other in any combination as the consideration whether to operate in an SBFD slot (or not) and how to adapt communication may be implemented, partly or completely without an offset albeit benefiting therefrom. Further, to apply an offset in communication when using allocated resources may be implemented, partly or completely without the consideration whether to operate in an SBFD slot (or not) albeit benefitting therefrom. Here - Formal repetition of claims as aspects to appear after claims have been finalized. invention Various elements and features of the present invention may be implemented in hardware using analogue and / or digital circuits, in software, through the execution of instructions by one or more general purpose or special-purpose processors, or as a combination of hardware and software. For example, embodiments of the present invention may be implemented in the environment of a computer system or another processing system. Fig.27 illustrates an example of a computer system 2700. The units or modules as well as the steps of the methods filing version an,rm FH241001PEP 2024P67397EP 79 performed by these units may execute on one or more computer systems 2700. The computer system 2700 includes one or more processors 2702, like a special purpose or a general- purpose digital signal processor. The processor 2702 is connected to a communication infrastructure 2704, like a bus or a network. The computer system 2700 includes a main memory 2706, e.g., a random-access memory (RAM), and a secondary memory 2708, e.g., a hard disk drive and / or a removable storage drive. The secondary memory 2708 may allow computer programs or other instructions to be loaded into the computer system 2700. The computer system 2700 may further include a communications interface 2710 to allow software and data to be transferred between computer system 2700 and external devices. The communication may be in the form of electronic, electromagnetic, optical, or other signals capable of being handled by a communications interface. The communication may use a wire or a cable, fibre optics, a phone line, a cellular phone link, an RF link and other communications channels 2712. The terms “computer program medium” and “computer readable medium” are used to generally refer to tangible storage media such as removable storage units or a hard disk installed in a hard disk drive. These computer program products are means for providing software to the computer system 2700. The computer programs, also referred to as computer control logic, are stored in main memory 2706 and / or secondary memory 2708. Computer programs may also be received via the communications interface 2710. The computer program, when executed, enables the computer system 2700 to implement the present invention. In particular, the computer program, when executed, enables processor 2702 to implement the processes of the present invention, such as any of the methods described herein. Accordingly, such a computer program may represent a controller of the computer system 2700. Where the disclosure is implemented using software, the software may be stored in a computer program product and loaded into computer system 2700 using a removable storage drive, an interface, like communications interface 2710. The implementation in hardware or in software may be performed using a digital storage medium, for example cloud storage, a floppy disk, a DVD, a Blue-Ray, a CD, a ROM, a PROM, an EPROM, an EEPROM or a FLASH memory, having electronically readable control signals stored thereon, which cooperate (or are capable of cooperating) with a programmable computer system such that the respective method is performed. Therefore, the digital storage medium may be computer readable. filing version an,rm FH241001PEP 2024P67397EP 80 Some embodiments according to the invention comprise a data carrier having electronically readable control signals, which are capable of cooperating with a programmable computer system, such that one of the methods described herein is performed. Generally, embodiments of the present invention may be implemented as a computer program product with a program code, the program code being operative for performing one of the methods when the computer program product runs on a computer. The program code may for example be stored on a machine-readable carrier. Other embodiments comprise the computer program for performing one of the methods described herein, stored on a machine-readable carrier. In other words, an embodiment of the inventive method is, therefore, a computer program having a program code for performing one of the methods described herein, when the computer program runs on a computer. A further embodiment of the inventive methods is, therefore, a data carrier (or a digital storage medium, or a computer-readable medium) comprising, recorded thereon, the computer program for performing one of the methods described herein. A further embodiment of the inventive method is, therefore, a data stream or a sequence of signals representing the computer program for performing one of the methods described herein. The data stream or the sequence of signals may for example be configured to be transferred via a data communication connection, for example via the Internet. A further embodiment comprises a processing means, for example a computer, or a programmable logic device, configured to or adapted to perform one of the methods described herein. A further embodiment comprises a computer having installed thereon the computer program for performing one of the methods described herein. In some embodiments, a programmable logic device (for example a field programmable gate array) may be used to perform some or all of the functionalities of the methods described herein. In some embodiments, a field programmable gate array may cooperate with a microprocessor in order to perform one of the methods described herein. Generally, the methods are preferably performed by any hardware apparatus. The above described embodiments are merely illustrative for the principles of the present invention. It is understood that modifications and variations of the arrangements and the details described herein are apparent to others skilled in the art. It is the intent, therefore, to be limited only by the scope of the impending patent claims and not by the specific details presented by way of description and explanation of the embodiments herein. filing version an,rm FH241001PEP 2024P67397EP 81 In the following, additional embodiments and aspects of the invention will be described which can be used individually or in combination with any of the features and functionalities and details described herein. A first aspect relates to a device for operating in a wireless communication network, wherein the device is adapted to determine a resource allocation allocating resources of the wireless communication network, e.g., for uplink, UL, and / or downlink, DL, and / or sidelink and to use the allocated resources based on whether the resources are within a subband full duplex, SBFD, time-frequency occasion. According to a second aspect when referring back to the first aspect, the SBFD time frequency occasion is either an SBFD symbol or a non-SBFD symbol from which only one is a valid symbol type for the SBFD time frequency occasion; wherein the device is to determine that a first time-frequency occasion of the resource allocation, e.g., related to a SRS transmission occasion, is valid in one of the SBFD symbol type and the non-SBFD symbol type and invalid in the other symbol type According to a third aspect when referring back to the second aspect, the device is adapted to drop a transmission in an invalid symbol type; or adapted to postpone a transmission in an invalid symbol type according to the resource allocation to a next available set of UL resources. According to a fourth aspect when referring back to the third aspect, for an UL transmission across a SBFD occasion and a non-SBFD occasion in different slots the device is to postpone the transmission in the invalid symbol type, e.g., for a PUSCH repetition type A with available slot counting, A-SRS with available slot counting, TBoMS and PUCCH repetitions. According to a fifth aspect when referring back to any one of the third or fourth aspects, the device is adapted to drop the transmission for CG PUSCH with neither TBoMS nor PUSCH repetition type A with available slot counting, SPS PDSCH, P / SP SRS, P / SP CSI-RS, P / SP PUCCH, SP-CSI on PUSCH, PUSCH repetition type A without available slot counting, multi- PUSCH / PDSCH scheduled by a single DCI, and PDSCH repetitions in the invalid symbol type. According to a sixth aspect when referring back to the any one of the second to fifth aspects, the device is adapted to use the allocated resource for an uplink transmission related to an SBFD occasion, e.g., a SRS transmission, based on identifying that the resources are satisfying a condition according to which SBFD occasions are available or valid for the time- domain location(s) for all the SRS resources in the resource set and it satisfies the UE filing version an,rm FH241001PEP 2024P67397EP 82 capability on the minimum timing requirement between triggering PDCCH and all the SRS resources in the resource set. According to a seventh aspect when referring back to any one of the second to sixth aspects, the device is adapted to use the allocated resource for an uplink transmission related to a non- SBFD occasion, e.g., a SRS transmission, based on identifying that the resources are satisfying a condition according to which uplink symbols and / or flexible symbol(s) configured as non-SBFD symbols for at least one time-domain location for all resources in the resource set. According to an eighth aspect when referring back to any one of the first to seventh aspects, the device is to determine a starting resource for the uplink transmission in SBFD symbols according to, ^^^^ௌ^ி^ ^^ ௌ^ ^^^ିௌ^ி^^௧^^௧ ൌ ^^^^^௧^^௧ ^ ൫^^^^^௧^^௧ ^ ^^^^^ௌ^^^ி^^^௧൯^^^^^^^^^^^^௭ௌ^^ wherein ^^^^^ௌ^^^ி^^^௧is set to zero if unconfigured. According to a ninth aspect when referring back to any one of the first to eighth aspects, the resource allocation comprises a frequency hopping, FH, shifting a frequency of used resources in subsequent uplink occasions by a FH-offset, wherein a start frequency resource of the resource allocation is provided for a first hop and start frequency resources of subsequent hops within the slot or across slots are derived using a FH-offset, e.g., using a legacy formula. According to a tenth aspect when referring back to the ninth aspect, for an uplink intra-slot frequency hopping in SBFD symbols, a starting frequency, e.g., associated with a resource block, RB, in each hop is given by: According to an eleventh aspect when referring back to any one of the ninth or tenth aspects, for an uplink inter-slot frequency hopping in SBFD symbols and based on pusch-DMRS- Bundling being enabled, or for inter-slot frequency hopping for a PUSCH in SBFD symbols, e.g., scheduled by random access response, RAR, UL grant or DCI format 0_0 with CRC scrambled by TC-RNTI, the starting RB during slot is given by: filing version an,rm FH241001PEP 2024P67397EP 83 where ^ RB^^ ୗ^ ^^ୟ୰^is the starting PRB index of UL usable PRBs with reference to the start of UL active BWP, ^ N^^୧^^^ୗ^is the number of UL usable PRBs, ^ RB^^ୟ୰^is the starting PRB index of the first PUSCH hop with reference to the start of UL active BWP. For PUSCH transmissions with Configuration 2, RB^^ୟ୰^is the starting PRB index with reference to the start of UL active BWP after applying RB offset between non-SBFD symbols and SBFD symbols. ^ RB offset is the frequency hopping offset for PUSCH in SBFD symbols, ^ Note: Definition is unchanged from existing specifications. According to a twelfth aspect when referring back to any one of the ninth to eleventh aspects, the allocated resources comprise a first start frequency in a non-SBFD occasion and comprise a different second start frequency in an SBFD occasion. According to a thirteenth aspect when referring back to any one of the ninth to twelfth aspects, the second start frequency provides a shift of uplink resources of a non-SBFD occasion that are at least partially assigned to a downlink in the SBFD occasion to resources assigned to uplink in the SBFD occasion, wherein resources allocated for the occasion in a non-SBFD slot are shifted such that the shifted resources are contained within an UL bandwidth part, BWP, and the UL subband, SB. According to a fourteenth aspect when referring back to any one of the first to thirteenth aspects, the device is to determine whether the resources are within a subband full duplex, SBFD, time-frequency occasion and to adapt the use of the allocated resourced based on a determination result. According to a fifteenth aspect when referring back to any one of the first to fourteenth aspects, the resource allocation is a periodic allocation or a repetitive allocation, e.g., a semi-persistent scheduling, SPS. According to a sixteenth aspects when referring back to any one of the first to fifteenth aspects, the device is adapted to determine whether a slot is a SBFD-time-frequency occasion, e.g., a slot, or a non-SBFD time-frequency occasion and to determine a same or a different result for using the allocated resources in for the SBFD time frequency occasion and the non-SBFD time frequency occasion. filing version an,rm FH241001PEP 2024P67397EP 84 According to a seventeenth aspect when referring back to any one of the first to sixteenth aspects, the device is adapted to receive the resource allocation as valid for at least one SBFD time-frequency occasion and at least one non-SBFD time-frequency occasion. According to an eighteenth aspect when referring back to any one of the first to seventeenth aspects, the device is configurable with the resource allocation, e.g., using a scheduling information such as frequency domain resource allocation, FDRA, the scheduling information indicating an allocation of frequency domain resources, e.g., a bandwidth part, BWP, or at least one subband, of the wireless communication network. According to a nineteenth aspect when referring back to any one of the first to eighteenth aspects, device is configurable with the resource allocation with a single scheduling information provided to the device, e.g., by an activation downlink control information, DCI, e.g., for semi-persistent scheduling, SPS, and to determine for each of a plurality of -time- frequency occasion whether the resource allocation allocates resources to an SBFD -time- frequency occasion or a non-SBFD time-frequency occasion. According to a twentieth aspect when referring back to any one of the first to nineteenth aspects, the device is adapted to receive a single frequency domain resource allocation, FDRA, as at least a part of the resource allocation by an activation downlink control information, DCI, for SPS and for SBFD time-frequency occasion and non-SBFD time- frequency occasion. According to a twenty-first aspect when referring back to any one of the first to twentieth aspects, the device is adapted to ignore uplink resources of a SBFD time-frequency occasion for a downlink transmission that uses resources of the resource allocation; and / or wherein the device is adapted to ignore downlink resources of a SBFD time-frequency occasion for an uplink transmission that uses resources of the resource allocation. According to a twenty-second aspect when referring back to any one of the first to twenty-first aspects, a first time-frequency occasion of the frequency allocation overlaps with an SBFD symbol of an SBFD time-frequency occasion and a second time-frequency occasion of the frequency allocation overlaps with a non- SBFD time-frequency occasion, e.g., a slot or symbol, wherein the device is adapted to treat all symbols of the first time-frequency occasion to be of a particular type, e.g., type SBFD or non-SBFD. filing version an,rm FH241001PEP 2024P67397EP 85 According to a twenty-third aspect when referring back to the twenty-second aspect, the device is adapted to determine a number of symbols in the first time-frequency occasion to be of either SBFD type or of non-SBFD type, wherein in case the number exceeding a threshold the device is adapted to treat all symbols in the first time-frequency occasion as SBFD symbols; and / or in case the number not exceeding the threshold the device is adapted to treat all symbols in the first time-frequency occasion as non-SBFD symbols.. According to a twenty-fourth aspect when referring back to the twenty-third aspect, threshold, e.g., number n, is predefined or signalled by the wireless communication network. According to a twenty-fifth aspect when referring back to any one of the twenty-third or twenty- fourth aspect, the device is adapted to treat non-SBFD symbols the same way as SBFD symbols based on determining the number of symbols and to use same DL resources used for reception in the SBFD symbols for reception in the non-SBFD symbols according to the resource allocation. According to a twenty-sixth aspect when referring back to any one of the first to twenty-fifth aspects, the device is adapted to use a first modulation coding scheme, MCS, for a SBFD symbol of the SBFD time-frequency occasions and a second MCS for a non-SBFD symbol of a non-SBFD time-frequency occasions. According to a twenty-seventh aspect when referring back to the twenty-sixth aspect, the device is configured for receiving and / or decoding explicit information indicating the first MCS and the second MCS, e.g., as a combined value or as two separate values. According to a twenty-eighth aspect when referring back to the twenty-sixth or twenty-seventh aspect, the device is configured for receiving and / or decoding two different DCI, a first DCI containing a first MCS value indicating the first MCS and a second DCI containing a second MCS value indicating the second MCS. According to a twenty-ninth aspect when referring back to the twenty-eighth aspect, the first DCI and the second DCI contain a time domain resource allocation, TDRA, wherein the device is adapted to decode the first DCI and the second DCI and to determine which TDRA corresponds to SBFD symbols or non-SBFD symbols. filing version an,rm FH241001PEP 2024P67397EP 86 According to a thirtieth aspect when referring back to the twenty-ninth aspect, the device is adapted to determine the first or second DCI containing the TDRA is for SBFD symbols based on the TDRA overlapping with a SBFD symbol of a SBFD slot. According to a thirty-first aspect when referring back to any one of the twenty-eighth to thirtieth aspects, the first DCI and the second DCI are linked to two different values of SPS-Config indices in separate SPS-Configs, wherein a first SPS-Config index corresponds to SBFD symbols of the SBFD slot and a second SPS-Config index corresponds to non-SBFD symbols of the non-SBFD slot. According to a thirty-second aspect when referring back to the thirty-first aspect, an SBFDIndicator parameter of one bit forms a part of the SPS-Config, wherein for a particular SPS-Config index, if this parameter is set to 0 or 1, then the SPS-Config index is for SBFD symbols and otherwise for non-SBFD symbols. According to a thirty-third aspect when referring back to any one of the twenty-eighth to thirty- second aspects, the first DCI and the second DCI each comprise an indicator indicating whether it is for SBFD of the SBFD slot or non-SBFD symbols of the non-SBFD slot, e.g., using at least one unused / reserved DCI bit, for example, unused / reserved according to a legacy NR standard. According to a thirty-fourth aspect when referring back to any one of the twenty-eighth to thirty- third aspects, the device is adapted to decode the first DCI and second DCI and to associate a lower MCS value of the first MCS value and the second MCS value with SBFD symbols of the SBFD slot. According to a thirty-fifth aspect when referring back to any one of the twenty-sixth to thirty- fourth aspects, the device is adapted to receive, e.g., from a base station, gNB a single DCI indicating the first MCS and the second MCS, e.g., using at least one unused / reserved DCI bit, for example, unused / reserved according to a legacy NR standard. According to a thirty-sixth aspect when referring back to the thirty-fifth aspect, the device is adapted to interpret a parameter in a configuration message, e.g., a SPS-Config message or in an RRC message received from the gNB, as indicating whether a second MCS value for the SBFD symbols will be provided to the device or not. filing version an,rm FH241001PEP 2024P67397EP 87 According to a thirty-seventh aspect when referring back to the thirty-sixth aspect, the configuration message comprises a one bit field, e.g., called SecondMCS in RRC, is set to one of 1 and 0, wherein the device is adapted to expect to receive an MCS value for a SBFD symbol in the SBFD slot in the DCI; or is set to the other of 1 and 0 or in case the field is absent, the device is adapted to use a same MCS for an SBFD symbol and a non-SBFD symbol. According to a thirty-eighth aspect when referring back to any one of the thirty-fifth to thirty- seventh aspects, a field used for sending the MCS for a second transport block, TB, in DCI is used to send the MCS for a SBFD symbol of the SBFD time-frequency occasions, e.g., if SBFD is configured. According to a thirty-ninth aspect when referring back to any one of the twenty-sixth to thirty- eighth aspects, the first MCS and the second MCS are part of a same reference MCS table supported by the wireless communication network, or wherein the first MCS is indicated in a first MCS table and the second MCS is indicated in a second MCS table, wherein one of the first MCS table and the second MCS table is associated with SBFD symbols and the other is associated with non-SBFD symbol. According to a fortieth aspect when referring back to the thirty-ninth aspect, the MCS table associated with the SBFD symbol is derived from the same MCS reference table used for the non-SBFD symbol, e.g., an existing parameter for reference to MCS table in SPS-Config is used. According to a forty-first aspect when referring back to any one of the thirty-ninth or fortieth aspects, the MCS value of the first MCS value and the second MCS value that is associated with the SBFD symbol is derived from a different MCS reference table than that is used for non-SBFD symbols. According to a forty-second aspect when referring back to the forty-first aspect, a MCS reference table for the non-SBFD symbols is provided by a parameter mcs-Table in SPS- Config and the MCS reference table for SBFD symbol is provided to the device by a different parameter in SPS-Config or in radio resource control, RRC. According to a forty-third aspect when referring back to the forty-first or forty-second aspect, a first parameter and a second parameter for MCS reference tables for non-SBFD symbols and SBFD symbols are provided in SPS-Config or in RRC. filing version an,rm FH241001PEP 2024P67397EP 88 According to a forty-fourth aspect when referring back to any one of the forty-first to forty-third aspects, a MCS reference table for the SBFD symbols is provided in PDSCH-Config, e.g., as a new parameter, wherein optionally, a parameter mcs-Table in SPS-Config is used for the MCS value related to non-SBFD symbols. According to a forty-fifth aspect when referring back to any one of the forty-first to forty-fourth aspects, MCS reference tables for both the SBFD symbols and non-SBFD symbols are provided in PDSCH-Config. According to a forty-sixth aspect when referring back to any one of the twenty-sixth to forty- fifth aspects, the device is configured for implicitly deriving information indicating the first MCS and / or the second MCS. According to a forty-seventh aspect when referring back to the forty-sixth aspect, the device is configured for deriving the MCS value for a SBFD symbol of the SBFD time-frequency occasion from the MCS value for the non- SBFD symbol of the non-SBFD slot. According to a forty-eighth aspect when referring back to the forty-seventh aspect, the device is adapted to derive the MCS value for the SBFD symbol based on a report provided to the wireless communication network. According to a forty-ninth aspect when referring back to the forty-seventh or forty-eighth aspect, the device is adapted to respond a request of a base station, gNB with a feedback, e.g., using higher layer signalling like RRC or Media Access Control, MAC, wherein the device is adapted to derive the MCS value for the SBFD symbol based on the feedback. According to a fiftieth aspect when referring back to the forty-ninth aspect, the device is adapted to deriving the MCS value for the SBFD symbol from a parameter comprising an interference such as a signal to noise and interference ratio, SINR, and / or any other channel state related parameter for SBFD and non-SBFD symbols. According to a fifty-first aspect when referring back to any one of the forty-eighth to fiftieth aspects, the device is adapted to deriving the MCS value for the SBFD symbol from a difference of parameters comprising an interference such as a signal to noise and interference ratio, SINR, and / or any other channel state related parameter for SBFD and non-SBFD symbols. filing version an,rm FH241001PEP 2024P67397EP 89 According to a fifty-second aspect when referring back to any one of the forty-eighth to fifty- first aspects, the device is adapted to deriving the MCS value for the SBFD symbol based a specified formula or from a look up table relating the MCS value to the parameter. According to a fifty-third aspect when referring back to any one of the forty-eighth to fifty- second aspects, the device is adapted to deriving the parameter based on the difference between SINR or interference or any other channel state related parameter for SBFD and non- SBFD symbols; wherein the device optionally derives an MCS value for the SBFD symbols based on the parameter, e.g., using some specified formula or from a look up table relating the MCS value to the parameter. According to a fifty-fourth aspect when referring back to any one of the forty-eighth to fifty-third aspects, the device is adapted to derive at least one parameter based on the MCS value to be applied for the SBFD symbols, e.g., this MCS value is calculated by the device based on the SINR of SBFD symbols and the device directly reports this MCS value. According to a fifty-fifth aspect when referring back to any one of the forty-eighth to fifty-fourth aspects, the device is adapted to determine at least one of a first MCS value and a second MCS value based on a baseline MCS as an offset from the baseline MCS. According to a fifty-sixth aspect when referring back to any one of the forty-sixth to fifty-fifth aspects, the device is adapted to receive the resource allocation, e.g., SPS, in one or more SBFD symbols with a same MCS value the device has calculated and based on an acknowledgement received from the gNB, the acknowledgement acknowledging the calculated MCS value. According to a fifty-seventh aspect when referring back to the fifty-sixth aspect, the device is adapted to send a feedback to the gNB subject to the acknowledgement based upon a condition, e.g., if the difference between the MCS for SBFD and non-SBFD symbols is greater than a given threshold, then only the device reports the feedback, wherein the threshold can be pre-defined in the specification or provided by the gNB to the device. According to a fifty-eighth aspect when referring back to any one of the forty-sixth to fifty- seventh aspects, the device is adapted to use assistant information received from the gNB for a calculation of the MCS for SBFD symbols. filing version an,rm FH241001PEP 2024P67397EP 90 According to a fifty-ninth aspect when referring back to the fifty-eighth aspect, the assistant information comprises certain information about the interference on the SBFD symbols, wherein the device calculates the MCS based on the certain information and optionally provides this MCS as feedback to the gNB. According to a sixtieth aspect when referring back to any one of the forty-sixth to fifty-ninth aspects, the MCS related to non-SBFD symbols is indicated to the device by a row number of a reference MCS table; wherein the device is adapted to derive the MCS for SBFD symbols based on the MCS related to non-SBFD symbols and based on a fixed offset value; or wherein the MCS related to SBFD symbols is indicated to the device by a row number of a reference MCS table; wherein the device is adapted to derive the MCS for non-SBFD symbols based on the MCS related to SBFD symbols and based on a fixed offset value. According to a sixty-first aspect when referring back to any one of the twenty-sixth to sixtieth aspects, the device is adapted to obtain an MCS offset value provided in message such as a SPS-Config message and is adapted to use the MCS offset value to derive the MCS for SBFD symbols from the MCS used for non- SBFD symbols; or to use the MCS offset value to derive the MCS for non-SBFD symbols from the MCS used for SBFD symbols. According to a sixty-second aspect when referring back to any one of the first to sixty- first aspects, the device is to determine a transport block size, TBS, for DL SPS data, based on an available number of DL resources in the SBFD symbols, e.g., instead of the total number of resources in the DL active BWP. According to a sixty-third aspect when referring back to the sixty-second aspect, the device is adapted to use a first modulation coding scheme, MCS, for a SBFD symbol of a SBFD-slot as the SBFD time-frequency occasions and a second MCS for a non-SBFD symbol of a non- SBFD time-frequency occasion ; wherein the device is to consider a number of allocated resource blocks, RBs, to be the number of available DL RBs for SBFD symbols; wherein a different MCS is provided or derived for SBFD symbols when compared to non-SFBFD symbols, and to calculate the TBS based thereon. According to a sixty-fourth aspect when referring back to the sixty-third aspect, a xOverhead parameter comprises a different value when provided explicitly for SBFD symbols and when being implicitly determined, e.g., based on available DL resources or unavailable DL resources. filing version an,rm FH241001PEP 2024P67397EP 91 According to a sixty-fifth aspect when referring back to any one of the first to sixty-fourth aspects, the device is adapted for ignoring a time-frequency occasion of the frequency allocation, if at least a certain number of n symbols of the time-frequency occasion are SBFD symbols of one or more SBFD slots. According to a sixty-sixth aspect when referring back to the sixty-fifth aspect, the device is to determine a number of available DL resources of the resource allocation, e.g., a given FDRA, in the SBFD symbols and to ignore the time-frequency occasion in a case where the number of available DL resources is lower than a resource threshold. According a sixty-seventh aspect when referring back to the sixty-sixth aspect, the resource threshold is predetermined, e.g., specified in a NR specification, or provided by the wireless communication network, e.g., a gNB, for example, using RRC or DCI. According to a sixty-eighth aspect when referring back to any one of the sixty-fifth to sixty- seventh aspects, the device is adapted for determining whether a calculated TBS for the available DL resources and MCS is below a TBS threshold and for ignoring the time-frequency occasion based thereon. According to a sixty-ninth aspect when referring back to the sixty-eighth aspect, the TBS threshold is predetermined, e.g., specified in a NR specification, or provided by the wireless communication network, e.g., a gNB, for example, using RRC or DCI. According to a seventieth aspect when referring back any one of the sixty-fifth to sixty-ninth aspects, the value of n is preconfigured, e.g., defined in a specification, or is or provided by the wireless communication network, e.g., a gNB, wherein the value of n is at least 1. According to a seventy-first aspect when referring back to any one of the sixty-fifth to seventieth aspects, the device is to not ignore the time-frequency occasion based on a priority of a data transmission in that time-frequency occasion being at least a priority threshold, e.g., if a high priority flag is indicated by the gNB. According to a seventy-second aspect when referring back to any one of the sixty-fifth to seventy-first aspects, the device is adapted to not expecting a transmission from a gNB based on a condition for ignoring the time-frequency occasion being met. filing version an,rm FH241001PEP 2024P67397EP 92 According to a seventy-third aspect when referring back to any one of the sixty-fifth to seventy- second aspects, the device is based on a condition for ignoring the time-frequency occasion being met the device is adapted to postpone reception according to the resource allocation to a next available set of DL resources. According to a seventy-fourth aspect when referring back to the seventy-third aspect, the device is adapted to postpone reception based on the time-frequency occasion being ignored by the device due to some pre-defined conditions being satisfied. According to a seventy-fifth aspect when referring back to the seventy-third or seventy-fourth aspect, the device is adapted to postpone reception based on whether there is at least one available non-SBFD DL slot where the configured frequency resources of the resource allocation are available. According to a seventy-sixth aspect when referring back to any one of the seventy-third to seventy-fifth aspects, the device is adapted to postpone reception only if at least one available non-SBFD time-frequency occasion occurs before the next scheduled time-frequency occasion. According to a seventy-seventh aspect when referring back to any one of the seventy-third to seventy-sixth aspects, the device is adapted to provide a capability information to the wireless communication network indicating that the device capable of receiving a postponed reception. According to a seventy-eighth aspect when referring back to any one of the seventy-second to seventy-seventh aspects, the device is adapted to postpone or to ignore a reception or transmission only if a condition related to one or more of ^ a transmission, ^ a retransmission, ^ a reception, ^ a processing, ^ a delay, ^ a timing, is satisfied. filing version an,rm FH241001PEP 2024P67397EP 93 According to a seventy-ninth aspect when referring back to the seventy-eighth aspect, the condition related to a processing refers to one or more of ^ a signal processing capability of the UE, ^ a timing with respect to the signal processing, e.g., a processing delay. According to an eightieth aspect when referring back to any one of the seventy-eighth or seventy-ninth aspects, the condition comprises that a next available valid slot is within a configured or pre-configured or predefined number of n slots / symbols / time duration from the slot being ignored. According to an eighty-first aspect when referring back to any one of the seventy-eighth to eightieth aspects, the condition relating to a retransmission refers to at least one of: ^ a HARQ-timing condition to be satisfied, e.g., transmitting on the postponed slot is the only possibility to transmit in time, prior to receiving a HARQ-NACK for a failed transmission, ^ a radio link failure, RLF, timing related condition, e.g., a last possibility to transmit in a scenario where the radio channel is degrading, e.g., a cell-edge UE, ^ a code block group, CBG,-based condition, e.g., the last n-CBGs have not been transmitted and the postponed transmission could avoid a transmission which would be either too late or which could be better utilized by other code blocks. According to an eighty-second aspect when referring back to any one of the seventy-eighth to eighty-first aspects, the condition is as a transmission or retransmission related condition related to a type of the data transmitted. According to an eighty-third aspect when referring back to any one of the seventy-eighth to eighty-second aspects, the condition is as a reception related condition related to a type of the signal received. According to an eighty-fourth aspect when referring back to any one of the seventy-eighth to eighty-third aspects, the device is to postpone the occasion to a different frequency such as a transmission in a different bandwidth part, BWP, or carrier, or to trigger a data duplication transmission or redundancy transmission in the different frequency, e.g., in order to increase the probability of a successful transmission. filing version an,rm FH241001PEP 2024P67397EP 94 According to an eighty-fifth aspect when referring back to the eighty-fourth aspect, the postponing, data duplication transmission or redundance transmission is related to one or more of the following: ^ an exact location of a carrier e.g., frequency band in FR1 or FR2 or FR3, ^ an available bandwidth given for a said carrier and / or BWP, ^ a numerology configured for a said BWP, e.g., [15, 30, 60, …] SCS, ^ a utilization in a given band, ^ a measurement-related conditions, e.g., the interference in a given band, e.g., measured by RSRP, SINR, or similar KPIs. According to an eighty-sixth aspect when referring back to any one of the seventy-third to eighty-fifth aspects, the device is adapted to consider a HARQ process ID to remain same based on postponing reception. According to an eighty-seventh aspect when referring back to any one of the first to eighty- sixth aspects, the device is adapted to use, from a time-frequency occasion of the scheduling, a first portion of the allocated resources to map a first portion of a data / transport block and to spread, e.g., using consecutive symbols, a remaining second portion of the data / transport block into other available resources which are shifted in time with respect to the allocated resources [e.g. general: allowing earlier or later resources], e.g., to suffice the resource allocation. According to an eighty-eighth aspect when referring back to the eighty-seventh aspect, the other resources are subsequent resources or symbols, e.g., DL resources. According to an eighty-ninth aspect when referring back to the eighty-seventh or eighty-eighth aspect, the device is to expect reception of a signal to be spread to the second portion of the scheduled resources in a case where consecutive symbols in time domain are available to the device, e.g., just after the last symbol of the allocated resources in the time-frequency occasion or before the first symbol of the time-frequency occasion. According to a ninetieth aspect when referring back to any one of the eighty-seventh to eighty- ninth aspects, the device is to receive the second portion with same frequency domain resources as the first portion of resources. filing version an,rm FH241001PEP 2024P67397EP 95 According to a ninety-first aspect when referring back to any one of the eighty-seventh to ninetieth aspects, the device is to receive the second portion with different frequency domain resources in a consecutive symbol being a non-SBFD symbol. According to a ninety-second aspect when referring back to any one of the eighty-seventh to ninety-first aspects, the device is to receive the second portion using a same set of frequency domain resources in a consecutive symbol being a non-SBFD symbol. According to a ninety-third aspect when referring back to any one of the eighty-seventh to ninety-second aspects, the device is to expect reception of a signal to be spread to the second portion based on a condition relating to at least one of a transmission timing, a reception timing, a processing timing and a delay timing is satisfied. According to a ninety-fourth aspect when referring back to any one of the eighty-seventh to ninety-third aspects, the device is to expect reception of a signal to be spread to the second portion when a number of n consecutive time domain symbols are available. According to a ninety-fifth aspect when referring back to the ninety-fourth aspect, the number n is calculated, e.g., by the device, as a minimum number of time domain symbols such that the number of REs in the first portion and in the second portion is equal to or more than a given number N’ of resource elements, REs, determined based on the determination rule:RE^^′ ൌ ^^ோ^ ∙ ^^ ^^ െ ^^ ^ோ^ோா ^^ ^௬^^ ^ெோௌ െ ^^^^^ோ^, where ^ ^^′ is a number of Res for the data in an RB,ோாோ^^ ^^ is 12 (number of subcarrier in an RB),^^^^^ ^^ is the number of allocated symbols in a time domain,^௬^^^ோ^^ ^^ is the number of DMRS REs in the RB,^ெோௌ^ோ^^ ^^ overhead is configured by higher layer as xOverhead, and^^^ ^^^^^^ is explicitly provided for SBFD symbols. According to a ninety-sixth aspect when referring back to the ninety-fourth or ninety-fifth aspect, the number n is calculated, e.g., by the device, as a minimum number of time domain symbols such that the number of REs in the first portion and in the second portion is equal to or more than a given number N of resource elements, REs, determined based on theREdetermination rule: filing version an,rm FH241001PEP 2024P67397EP 96 ^^ோா ൌ min^156, ^^′ோா^ ∙ ^^^ோ^,where ^ ^^ோாis the number of Res for the data in an RB, ^ ^^^ோ^is the number of allocated RBs for the reception of the data, and ^ ^^^^^^ is only the allocated RS that are within the DL SB are used for SBFD symbols According to a ninety-seventh aspect when referring back to any one of the ninety-third to ninety-sixth aspects, the number n is calculated, e.g., by the device, as a minimum number of time domain symbols such that an unquantized intermediate variable is equal to or more than a given number of unquantized intermediate variable Ninf oor a TBS derived from the unquantized intermediate variable is equal to or more than a TBS derived from the given number of unquantized intermediate variable Ninf o, the given number of unquantized intermediate variable Ninf odetermined based on the determination rule: ^^୧୬^ ^ ൌ ^^ோா ∙ ^^ ∙ ^^^ ∙ ^^,where ^ ^^୧୬^ ^is the unquantized intermediate variable, ^ ^^ is the code rate, ^ ^^ is the modulation order, and ^ ^^ is the number of layers. According to a ninety-eighth aspect when referring back to any one of the ninety-fourth to ninety-seventh aspects, the number of REs or unquantized intermediate variable or TBS is equal to the number of REs or unquantized intermediate variable or TBS of the allocated resources in non-SBFD symbols. According to a ninety-ninth aspect when referring back to any one of the ninety-fourth to ninety- eighth aspects, the number of REs or unquantized intermediate variable or TBS is provided by the gNB. According to a one hundredth aspect when referring back to any one of the ninety-fourth to ninety-ninth aspects, the number n is provided by the gNB, e.g., in RRC, MAC and / or DCI. According to a one hundred and first aspect when referring back to any one of the first to one hundredth aspects, device is to use, from a time-frequency occasion of the scheduling, a first portion of the allocated resources to map a first portion of a data / transport block and to split a filing version an,rm FH241001PEP 2024P67397EP 97 remaining second portion of the data / transport block to at least one other slot to thereby split the resource allocation over a plurality of slots, e.g., optionally omitting an intermediate slot in the time domain, e.g., to suffice the resource allocation. According to a one hundred and second aspect when referring back to the one hundred and first aspect, the device is to split the resource allocation over consecutive or non-consecutive slots in time domain are available to the device, wherein at least one slot of the plurality of slots is later than a last slot of an actual time-frequency occasion of the scheduled resources; and / or wherein at least one slot of the plurality of slots is earlier than a first slot of the actual time- frequency occasion of the scheduled resources. According to a one hundred and third aspect when referring back to the one hundred and first or one hundred and second aspect, the device is to expect reception of a signal to be split to the second portion of the scheduled resources in a case where consecutive slots in time domain are available to the device, e.g., just after the last slot of the allocated resources in the time-frequency occasion or before the first slot of the time-frequency occasion. According to a one hundred and fourth aspect when referring back to any one of the one hundred and second to one hundred and third aspects, the device is to receive the second portion with same frequency domain resources as the first portion of resources. According to a one hundred and fifth aspect when referring back to any one of the one hundred and first to one hundred and fourth aspects, the device is to receive the second portion with different frequency domain resources in a consecutive symbol of a non-SBFD time-frequency occasion. According to a one hundred and sixth aspect when referring back to any one of the one hundred and first to one hundred and fifth aspects, the device is to receive the second portion using a same set of frequency domain resources in a consecutive slot being a non-SBFD symbol. According to a one hundred and seventh aspect when referring back to any one of the one hundred and first to one hundred and sixth aspects, the device is to expect reception of a signal to be split based on a condition relating to at least one of a transmission timing, a reception timing, a processing timing and a delay timing is satisfied. filing version an,rm FH241001PEP 2024P67397EP 98 According to a one hundred and eighth aspect when referring back to any one of the one hundred and first to one hundred and seventh aspects, the device is to expect reception of a signal to be split when a number of n consecutive time domain slots are available. According to a one hundred and ninth aspect when referring back the one hundred and eighth aspect, the number n is calculated, e.g., by the device, as a minimum number of time domain slots such that the number of REs in the first portion and in the second portion is equal to or more than a given number N’REof resource elements, REs, determined based on the determination rule: ^^′ ோ^ ^^ ^ோோா ൌ ^^^^ ∙ ^^^௬^^ െ ^^ ^^ெோௌ െ ^^^^^ோ^, where ^ ^^′ோாis the number of Res for the data in an RB, ^ ^^^ோ^^is 12 (number of subcarriers in an RB), ^ ^^^^௬^^^is the number of allocated symbols in the time domain, ^ number of DMRS Res in the RB, ^ ^^^^^ோ^is the overhead configured by higher layer as xOverhead, and ^ ^^^^^^ is the explicitly provided for SBFD symbols. According to a one hundred and tenth aspect when referring back to the one hundred and eighth or one hundred and ninth aspect, the number n is calculated, e.g., by the device, as a minimum number of time domain slots such that the number of REs in the first portion and in the second portion is equal to or more than a given number NREof resource elements, REs, determined based on the determination rule: ^^ோா ൌ min^156, ^^′ோா^ ∙ ^^^ோ^,where ^ ^^ோாis the number of Res for the data in an RB, ^ ^^^ோ^is the number of allocated RBs for the reception of the data, and ^ ^^^^^^ is only the allocated RBs that are within the DL SB are used for SBFD symbols. According to a one hundred and eleventh aspect when referring back to any one of the one hundred and eighth to one hundred and ninth aspects, the number n is calculated, e.g., by the device, as a minimum number of time domain slots such that an unquantized intermediate variable is equal to or more than a given number of unquantized intermediate variable Ninf oor filing version an,rm FH241001PEP 2024P67397EP 99 a TBS derived from the unquantized intermediate variable is equal to or more than a TBS derived from the given number of unquantized intermediate variable Ninf o, the given number of unquantized intermediate variable Ninf odetermined based on the determination rule: ^^୧୬^ ^ ൌ ^^ோா ∙ ^^ ∙ ^^^ ∙ ^^where ^ ^^ is the unquantized intermediate variable, ^ ^^ is the code rate, ^ ^^ is the modulation order, and ^ ^^ is different for SBFD symbols. According to a one hundred and twelfth aspect when referring back to any one of the one hundred and eighth to one hundred and eleventh aspects, the number of REs or unquantized intermediate variable or TBS is equal to the number of REs or unquantized intermediate variable or TBS of the allocated resources in non-SBFD symbols. According to a one hundred and thirteenth aspect when referring back to any one of the one hundred and eighth to one hundred and twelfth aspects, the number of REs or unquantized intermediate variable or TBS is provided by the gNB. According to a one hundred and fourteenth aspect when referring back to any one of the one hundred and eighth to one hundred and thirteenth aspects, the number n is provided by the gNB, e.g., in RRC, MAC and / or DCI. According to a one hundred and fifteenth aspect when referring back to any one of the one hundred and eighth to one hundred and fourteenth aspects, the device is adapted to consider a HARQ process ID to remain same based on the splitting. According to a one hundred and sixteenth aspect when referring back to any one of the first to one hundred and fifteenth aspects, the device is based on being provided with separate configurations, e.g., with one or more SPS-Config messages, for an SBFD symbol and for a non-SBFD symbol, the device is adapted or search to decode more than one DCI with a same SPS-Config index for activation of both configurations, expecting the same SPS-Config indices provided for both SBFD and non-SBFD symbols. filing version an,rm FH241001PEP 2024P67397EP 100 According to a one hundred and seventeenth aspect when referring back to the one hundred and sixteenth aspect, the device is to decode or search more than one DCI based on an indication, e.g., an explicit indication, received from the gNB. According to a one hundred and eighteenth aspect when referring back to the one hundred and sixteenth or one hundred and seventeenth aspect, the device is to keep a HARQ process ID the same for both configurations. According to a one hundred and nineteenth aspect when referring back to the one hundred and eighteenth aspect, the HARQ process ID calculated, e.g., by the device, for non-SBFD symbols and is assumed to be valid for SBFD symbols; or wherein the HARQ process ID calculated, e.g., by the device, for SBFD symbols and is assumed to be valid for non-SBFD symbols. According to a one hundred and twentieth aspect when referring back to the one hundred and eighteenth or one hundred and nineteenth aspect, the HARQ process ID is calculated, e.g., by the device, based on an occasion number, e.g., the occasion number being equal for both SBFD time-frequency occasion and non-SBFD time-frequency occasion even if the slot numbers are different. According to a one hundred and twenty-first aspect when referring back to any one of the first to one hundred and twentieth aspects, the device is based on being provided with separate configurations, the device is provided with different SPS-Config indices related to different SPS-Configs. According to a one hundred and twenty-second aspect when referring back to the one hundred and twenty-first aspect, the device is adapted to use a same HARQ process ID for both SPS- Configs. According to a one hundred and twenty-third aspect when referring back to any one of the first to one hundred and twenty-second aspects, different frequency domain resources are allocated for SBFD and non-SBFD symbols. According to a one hundred and twenty-fourth aspect when referring back to the one hundred and twenty-third aspect, a TDRA is the same or different for the SBFD and non-SBFD symbols of the resource allocation. filing version an,rm FH241001PEP 2024P67397EP 101 According to a one hundred and twenty-fifth aspect when referring back to the one hundred and twenty-third or one hundred and twenty-fourth aspect, different resource allocation configurations, e.g., SPS configurations, possibly with same or separate SPS config indices, are provided to the device for SBFD time-frequency occasions and non-SBFD occasions. According to a one hundred and twenty-sixth aspect when referring back to the one hundred and twenty-fifth aspect, different DCIs are be provided to the device for SBFD and non-SBFD symbols, the different DCIs relating to different FDRAs. According to a one hundred and twenty-seventh aspect when referring back to the one hundred and twenty-sixth aspect, the FDRA provided for SBFD symbols is adapted to exclude UL resources from the frequency domain resource allocation. According to a one hundred and twenty-eighth aspect when referring back to any one of the one hundred and twenty-third to one hundred and twenty-seventh aspects, the device is provided with separate DCIs with separate FDRAs for a same SPS-Config, wherein the device differentiates between the DCIs for SBFD.time-frequency occasions and non-SBFD occasions. According to a one hundred and twenty-ninth aspect when referring back to any one of the one hundred and twenty-third to one hundred and twenty-eighth aspects, the device is to decode a single DCI that contains both the different frequency domain resources and for a same SPS- Config index. According to a one hundred and thirtieth aspect when referring back to any one of the one hundred and twenty-third to one hundred and twenty-ninth aspects, the device is to derive the frequency domain resources for the SBFD time-frequency occasions, e.g., symbols, from frequency domain resources of the non-SBFD time-frequency occasions, e.g., symbols, e.g., symbols, provided to the device or vice versa. According to a one hundred and thirty-first aspect when referring back to the one hundred and thirtieth aspect, to derive the frequency domain resources for the SBFD symbols the device is to implement a derivation that is based on an explicit indication by the gNB or an explicit indication included as a part of a virtual resource block-to-physical resource block (VRB-to- PRB) mapping of the allocated resources. According to a one hundred and thirty-second aspect when referring back to the one hundred and thirtieth or one hundred and thirty-first aspect, in a first case relating to an UD scenario filing version an,rm FH241001PEP 2024P67397EP 102 with the scheduled resource allocation fully overlapping with an UL SB and / or a guard band, wherein the device is to derive the actual frequency domain resources for SBFD slots as the SBFD time-frequency occasion for reception; wherein frequency domain resources for SBFD slots as the SBFD time-frequency occasions start from a start RB ; wherein optionally, an offset is provided by the gNB; or a size of the resources is kept the same as the size of the frequency domain resources for non-SBFD slots or wherein a new size is provided; wherein the device is to ignore resources outside the DL SB for reception. According to a one hundred and thirty-third aspect when referring back to any one of the one hundred and thirtieth to one hundred and thirty-first aspects, in a first case relating to an UD or DU scenario with the scheduled DL resource allocation fully overlapping with an UL SB and / or a guard band, wherein the device is to derive the actual frequency domain resources for SBFD slots as the SBFD time-frequency occasion for reception; wherein frequency domain resources for SBFD slots as the SBFD time-frequency occasions start from a start RB; wherein a size of the resources is kept the same as the size of the frequency domain resources for non-SBFD slots or wherein a new size is provided; wherein the device is to ignore resources of an occasion outside the DL SB or DL BWP for reception; or to spread, split and / or postpone at last a part of the resources outside the DL SB or DL BWP across a domain relating to at least one of a time domain, a frequency domain, a spatial domain and a code domain. According to a one hundred and thirty-fourth aspect when referring back to any one of the first to one hundred and thirty-third aspects, a distribution of resources allocated for transmission and resources allocated for reception within a bandwidth part, BWP, is different for different occasions; wherein a size of the resources is kept the same as the size of the frequency domain resources for different slots, e.g., between non-SBFD slots and SBFD slots, or wherein a new size is provided; wherein the device is to ignore resources of an occasion outside the UL SB / UL BWP for transmission; or to spread, split and / or postpone at last a part of the resources outside the UL filing version an,rm FH241001PEP 2024P67397EP 103 SB / UL BWP across a domain relating to at least one of a time domain, a frequency domain, a spatial domain and a code domain. According to a one hundred and thirty-fifth aspect when referring back to the one hundred and thirty-fourth aspect, the device is adapted to use additional resources in the frequency domain and / or time domain and / or code domain and / or spatial domain. According to a one hundred and thirty-sixth aspect when referring back to the one hundred and thirty-third or one hundred and thirty-fifth aspect, for at least some resource allocations, i.e., optionally, for the allocation, an indication relating to an offset is provided by the gNB. According to a one hundred and thirty-seventh aspect when referring back to the one hundred and thirty-sixth aspect, the offset relates to a number of at least one frequency units such as resource blocks, RBs, or Resource block groups, RBGs. According to a one hundred and thirty-eighth aspect when referring back to any one of the first to one hundred and thirty-seventh aspects, the scheduled resources are associated with a downlink, DL, signal or channel and / or associated with an uplink, UL, signal or channel such as PUSCH or PUCCH and used for reception / transmission. According to a one hundred and thirty-ninth aspect when referring back to any one of the first to one hundred and thirty-eighth aspects, a virtual resource block-to-physical resource block, VRB-to-PRB, mapping related to the occasion is interleaved or non-interleaved. According to a one hundred and fortieth aspect when referring back to the one hundred and thirty-ninth aspect, whether the VRB-to-PRB mapping is interleaved or non-interleaved is a same for a non-SBFD occasion and a SBFD occasion; or varies between the non-SBFD occasion and a SBFD occasion from an interleaved structure to a non-interleaved structure or vice versa. According to a one hundred and forty-first aspect when referring back to any one of the first to one hundred and fortieth aspects, the allocated resources comprise a first start frequency in a non-SBFD occasion and comprise a different second start frequency in a SBFD occasion. According to a one hundred and forty-second aspect when referring back to the one hundred and forty-first aspect, the second start frequency provides a shift of uplink resources of a non- SBFD occasion that are at least partially assigned to downlink in the SBFD occasion to filing version an,rm FH241001PEP 2024P67397EP 104 resources assigned to uplink in the SBFD occasion; or wherein the second start frequency provides a shift of downlink resources of a non-SBFD occasion that are at least partially assigned to uplink in the SBFD occasion to resources assigned to downlink in the SBFD occasion According to a one hundred and forty-third aspect when referring back to the one hundred and forty-second aspect, the shift is indicated, e.g., to the device, by means of one or more of ^ a physical layer signalling, e.g., using a DCI transmitted via PDCCH, ^ a use of MAC control elements, MAC CE, ^ an RRC signalling, e.g., via RRC IEs via PDSCH, ^ a fixed offset configured by the network, e.g., via MIB, SIB, or configured using a fixed formular or value for a given carrier. According to a one hundred and forty-fourth aspect when referring back to the one hundred and forty-second aspect, the shift is determined by the device by means of ^ a calculation based on a formular configured or pre-configured at the UE, or ^ by means of prediction, e.g., based on training data on past SBFD / non-SBFD transmission calculated by an AI / ML algorithm. According to a one hundred and forty-fifth aspect when referring back to any one of the one hundred and forty-first to one hundred and forty-fourth aspects, for a non-SBFD slot being an UL slot with resources allocated to the device, a size of the resources is based on a lowest frequency, e.g., resource block, RB or resource block group, RBG, and based on an upper frequency RB / RBG where the resource allocation ends. According to a one hundred and forty-six aspect when referring back to any one of the one hundred and forty-first to one hundred and forty-fifth aspects, a FDRA provided, e.g., by downlink control information, DCI, for physical uplink shared channel, PUSCH, indicates the allocated resources. According to a one hundred and forty-seven aspect when referring back to any one of the one hundred and forty-first to one hundred and forty-six aspects, the second start frequency provides a shift of uplink resources of a non-SBFD occasion that are at least partially assigned to downlink in the SBFD occasion to resources assigned to uplink in the SBFD occasionwherein resources allocated for the occasion in a non-SBFD slot are shifted such that filing version an,rm FH241001PEP 2024P67397EP 105 the shifted resources are contained within an UL bandwidth part, BWP, and the UL subband, SB; or wherein the second start frequency provides a shift of downlink resources of a non-SBFD occasion that are at least partially assigned to uplink in the SBFD occasion to resources assigned to downlink in the SBFD occasion wherein resources allocated for the occasion in a non-SBFD slot are shifted such that the shifted resources are contained within an DL bandwidth part, BWP, and the DL subband, SB. According to a one hundred and forty-eighth aspect when referring back to the one hundred and forty-seventh aspect, the shift is associated with an offset indicated to the device or determined by the device. According to a one hundred and forty-ninth aspect when referring back to the one hundred and forty-eighth aspect, the offset is with respect to: ^ a start frequency resource of the SBFD slot as a starting reference point; ^ a start frequency resource of the UL-bandwidth part or DL-bandwidth part which is a starting reference point. According to a one hundred and fiftieth aspect when referring back to the one hundred and forty-ninth aspect, the start frequency resource, e.g., an RB or RBG is or comprises one of: ^ a lowest frequency of the UL SB; ^ a highest frequency of the UL SB; ^ a lowest frequency of the UL BWP; ^ a highest frequency of the UL BWP; ^ a reference point in the frequency domain such as Point A; ^ a highest / lowest frequency of a DL SB; ^ a lowest / highest frequency of the resources allocated in the non-SBFD of in the SBFD slot. According to a one hundred and fifty-first aspect when referring back to the one hundred and forty-ninth or one hundred and fiftieth aspect, an identifier of the start frequency resource such as a counter or number is one of: ^ a common resource block number; filing version an,rm FH241001PEP 2024P67397EP 106 ^ a physical resource block number; ^ a virtual resource block number. According to a one hundred and fifty-second aspect when referring back to any one of the one hundred and forty-ninth to one hundred and fifty-first aspects, a number of the start frequency resource is based on the available UL frequency resources. According to a one hundred and fifty-third aspect when referring back to any one of the one hundred and forty-eighth to one hundred and fifty-second aspects, wherein based on the offset the resources are shifted; and a lowest virtual resource block, VRB, and a highest VRB of the allocated resources in non- SBFD slot correspond to the lowest VRB and highest VRB respectively of the derived resources in SBFD slot; or the lowest VRB and highest VRB of the allocated resources in non-SBFD slot correspond to the highest VRB and lowest VRB respectively of the derived resources in SBFD slot. According to a one hundred and fifty-fourth aspect when referring back to any one of the one hundred and forty-eighth to one hundred and fifty-third aspects, wherein the offset is associated with or provided with a direction, e.g., in the frequency domain and / or time domain. According to a one hundred and fifty-fifth aspect when referring back to any one of the one hundred and forty-eighth to one hundred and fifty-fourth aspects, the shifted frequency resources correspond to a modulo operation executed on a frequency of the allocated resources shifted by the offset, e.g., based on the determination rules RBstart_new= RBstart+ offset; or RBstart_new= (RBstart+ offset) mod (N) where mod is a modulus operation and N represents the available UL resources, e.g., overlapping resources of UL BWP with UL SB / UL SB / UL BWP. filing version an,rm FH241001PEP 2024P67397EP 107 According to a one hundred and fifty-six aspect when referring back to the one hundred and fifty-fifth aspect, the direction associated with the offset is in the direction of a lower frequency or in a direction of a higher frequency. According to a one hundred and fifty-seventh aspect when referring back to the one hundred and fifty-fifth or one hundred and fifty-six aspects, the direction is explicitly signaled by the gNB, e.g., using a 1-bit indication such as ‘1’ representing towards lower frequency and ‘0’ representing towards higher frequency or vice versa. According to a one hundred and fifty-eighth aspect when referring back to any one of the one hundred and fifty-fifth to one hundred and fifty-seventh aspects, the direction is implicitly determined by the device, e.g., based on the UL SB being towards or closer to the upper frequency limit of the allocated UL resources, then the direction of the offset is determined to be towards that direction or vice versa. According to a one hundred and fifty-ninth aspect when referring back to any one of the one hundred and forty-eighth to one hundred and fifty-eighth aspects, the offset is provided, e.g., without a direction, wherein a relation between a start of frequency resources in shifted frequency resources, RBstart_new, and a start of frequency resources in unshifted frequency resources, RBstart, is based on a determination rule RBstart_new= RBstart+ offset; or RBstart_new= (RBstart+ offset) mod (N) where mod is modulus operation and N can be the available UL resources (overlapping resources of UL BWP with UL SB) or UL SB or UL BWP. According to a one hundred and sixtieth aspect when referring back to any one of the one hundred and forty-eighth to one hundred and fifty-ninth aspects, an end reference frequency point of the allocated resources is defined for the offset, such as a RB / RBG with a lowest frequency of the shifted resources in the SBFD slot; or a RB / RBG with a highest frequency of the shifted resources in the SBFD slot; or the lowest / highest frequency of the shifted resources in the non-SBFD / SBFD slot. According to a one hundred and sixty-first aspect when referring back to any one of the one hundred and forty-eighth to one hundred and sixtieth aspects, the resource allocation filing version an,rm FH241001PEP 2024P67397EP 108 comprises a frequency hopping, FH, shifting a frequency of used resources in subsequent occasions by a FH-offset, wherein a start frequency resource of the resource allocation is provided for a first hop and start frequency resources of subsequent hops within the slot or across slots are derived using a FH-offset, e.g., using a legacy formula. According to a one hundred and sixty-second aspect when referring back to the one hundred and sixty-first aspect, the start frequency resource is determined, e.g., signaled to the device or determined by the device based on at least one of: ^ a lowest frequency of the UL SB; ^ a highest frequency of the UL SB; ^ a lowest frequency of the UL BWP; ^ a highest frequency of the UL BWP; ^ a reference point in the frequency domain such as Point A; ^ a highest / lowest frequency of a DL SB; ^ a lowest / highest frequency of the resources allocated in the non-SBFD of in the SBFD slot; and for the subsequent hops, a determination rule such as [RBstart_new= (RBstart+ FH-offset) mod (BWP size) or RBstart_new= (RBstart+ FH-offset)] or a legacy NR FH formula, is used, e.g., by the device, on the determined start frequency resource to determine the start frequency resource of the subsequent hops. According to a one hundred and sixty-third aspect when referring back to the one hundred and sixty-first or one hundred and sixty-second aspect, the FH-offset is associated with or is provided with a direction, e.g., in the frequency domain. According to a one hundred and sixty-fourth aspect when referring back to any one of the one hundred and sixty-first to one hundred and sixty-third aspects, the start frequency resource is determined, e.g., signaled to the device or determined by the device based on at least one of: ^ a lowest frequency of the UL SB; ^ a highest frequency of the UL SB; ^ a lowest frequency of the UL BWP; filing version an,rm FH241001PEP 2024P67397EP 109 ^ a highest frequency of the UL BWP; ^ a reference point in the frequency domain such as Point A; ^ a highest / lowest frequency of a DL SB; ^ a lowest / highest frequency of the resources allocated in the non-SBFD of in the SBFD slot; and for the subsequent hops, a determination rule such as [RBstart_new= (RBstart+ FH-offset) mod (BWP size) or RBstart_new= (RBstart+ FH-offset)], or a legacy NR FH formula, is used, e.g., by the device, on the determined start frequency resource to determine a temporal start frequency resource of the subsequent hops; wherein the device is to further apply an offset to shift the temporal start frequency to obtain a shifted start frequency of the subsequent hop and to operate using the shifted start frequency. According to a one hundred and sixty-fifth aspect when referring back to the one hundred and sixty-fourth aspect, the FH-offset is associated with or is provided with a direction, e.g., in the frequency domain. According to a one hundred and sixty-sixth aspect when referring back to any one of the one hundred and sixty-first to one hundred and sixty-fifth aspects, the start frequency of the subsequent hop is determined based on the determination rule RB ൌ^ ^^ୟ୰^ , ^^ ൌ 0 first hop ^RB ^^௭^^^ୟ୰^ ^ RB୭^^^^^ ^ mod ^^ , ^^ ൌ 1 second hop ,^ ^^^where ^ ^^^^ is the starting RB of the UL resources, ^ ^^^^^௧^^௧is the starting RB of the UL resources as indicated by the gNB, ^ RB୭^^^^^^is the FH-offset. The FH offset can be different for the SBFD and non-SBFD slots, and ^ ^^^^^^௭^^ is the BWP size. BWP size can be replaced with UL SB size or available UL resources in SBFD slots. According to a one hundred and sixty-seventh aspect when referring back to the one hundred and sixty-sixth aspect, configured to apply a same or different FH-offset for SBFD slots and non-SBFD slots. filing version an,rm FH241001PEP 2024P67397EP 110 According to a one hundred and sixty-eighth aspect when referring back to any one of the one hundred and sixty-first to one hundred and sixty-seventh aspects, for an inter-slot FH the device is to use a different and optionally independent FH-offset for SBFD slots when compared to a non-SBFD slot for shifting the allocated resources and e.g., a same GH-offset for intra-slot FH. According to a one hundred and sixty-ninth aspect when referring back to any one of the one hundred and sixty-first to one hundred and sixty-eighth aspects, the FH offset is determined based on a current slot number; or an occasion number of SBFD / non-SBFD slot. According to a one hundred and seventieth aspect when referring back to any one of the one hundred and sixty-first to one hundred and sixty-ninth aspects, the FH offset is determined based the determination rule where ^ RB^^ୟ୰^is the starting RB of the UL resources, ^ ൫^^ఓ^൯ is the current slot number, ^ RB^^ୟ୰^is the starting RB of the UL resources as indicated by gNB, ^ RB୭^^^^^^is the FH-offset. FH-offset can be different for SBFD and non-SBFD slots, ^ ^^^^^^௭^^ is the BWP size. BWP size can be replaced with UL SB size or available UL resources in SBFD slots, and ^^ఓ^^ mod 2 ൌ 0ఓare the conditions; ^^^ mod 2 ൌ 1Or ,^ഋ ^ೞேಷಹ ^mod 2 ൌ 0mod ^^^^௭^^ഋ , ^^^ , ^ ೞ ேಷಹ ^mod 2 ൌ 1where ^ RB^^ୟ୰^is the starting RB of the UL resources, ^ ൫^^ఓ^൯ is the current slot number, ^ RB^^ୟ୰^is the starting RB of the UL resources as indicated by gNB, ^ RB୭^^^^^^is the FH-offset. FH-offset can be different for SBFD and non-SBFD slots, filing version an,rm FH241001PEP 2024P67397EP 111 ^ ^^^^^^௭^^ is the BWP size. BWP size can be replaced with UL SB size or available UL resources in SBFD slots, ^^^ ^ ^^^^^^^^^^^ is the pusch-FrequencyHoppipng-Interval. PUSCH-FreqeuncyHopping-Interval can have different values for SBFD and non-SBFD slots, and ഋ ^^ೞேಷಹ ^mod 2 ൌ 0^ ^ഋ are the conditions. ^ೞேಷಹ ^mod 2 ൌ 1According to a one hundred and seventy-first aspect when referring back to any one of the one hundred and sixty-first to one hundred and seventieth aspect, the device is to use a same or different DMRS bundling parameters such as (pusch-FrequencyHoppingInterval, pusch- TimeDomainWindowLength for SBFD and non-SBFD slots. According to a one hundred and seventy-second aspect when referring back to the one hundred and seventy-first aspect, a value of the bundling parameter is a minimum of the indicated value of the bundling parameter and the number of consecutive slots of any one type SBFD or non-SBFD. According to a one hundred and seventy-third aspect when referring back to the one hundred and seventy-first or one hundred and seventy-second aspect, a pusch-FrequencyHopping- Interval is determined based on a minimum value of a number of slots where frequency hopping is applicable, n, and a number of pusch-FrequencyHopping-Interval for SBFD slots, m; or wherein a pusch-FrequencyHopping-Interval is determined based on a minimum value of a number of slots where frequency hopping is applicable, n, and a number of pusch- FrequencyHopping-Interval for non-SBFD slots, m. According to a one hundred and seventy-fourth aspect when referring back to any one of the one hundred and sixty-first to one hundred and seventy-third aspects, an inter-slot FH is determined based on the determination rule: RB^^ୟ୰^ ^mod where ^ RB^^ୟ୰^is the starting RB of the UL resources, filing version an,rm FH241001PEP 2024P67397EP 112 ^ ൫^^ఓ^൯ is the current slot number , ^ RB^^ୟ୰^is the starting RB of the UL resources as indicated by gNB, ^ RB୭^^^^^^is the FH-offset. FH-offset can be different for SBFD and non-SBFD slots, ^ ^^^^^^௭^^ is the BWP size. BWP size can be replaced with UL SB size or available UL resources in SBFD slots, and ^ are the conditions. According to a one hundred and seventy-fifth aspect when referring back to any one of the one hundred and sixty-first to one hundred and seventy-fourth aspects, an inter-slot FH is determined based on the determination rule: 2ൌ 0, 2ൌ 1 where ^ RB^^ୟ୰^is the starting RB of the UL resources, ^ ൫^^ఓ^൯ is the current slot number, ^ RB^^ୟ୰^is the starting RB of the UL resources as indicated by gNB, ^ RB୭^^^^^^is the FH-offset. FH-offset can be different for SBFD and non-SBFD slots, ^ is the BWP size. BWP size can be replaced with UL SB size or available UL resources in SBFD slots,^is the pusch-FrequencyHoppipng-Interval. PUSCH-FreqeuncyHopping-Interval can have different values for SBFD and non-SBFD slots, and ഋ ^^ೞேಷಹ ^mod 2 ൌ 0^^ഋ are the conditions. ^ೞேಷಹ ^mod 2 ൌ 1According to a one hundred and seventy-sixth aspect when referring back to any one of the first to one hundred and seventy-fifth aspects, the allocated resources comprise a first start frequency in a non-SBFD occasion and comprise a different second start frequency in a SBFD occasion; filing version an,rm FH241001PEP 2024P67397EP 113 wherein a start frequency resource of the allocated resources in a non-SBFD or in a SBFD slot are based on a previous transmission / reception, e.g., irrespective of the SBFD or non-SBFD slot wherein a maximum frequency diversity is achieved in case of inter-slot FH. According to a one hundred and seventy-seventh aspect when referring back to the one hundred and seventy-sixth aspect, an offset is applied with respect to a start frequency resource of the previous transmission / reception, the offset relating to an offset to a shift of UL resources in a non-SBFD slot with respect to the UL resources in the SBFD slot; or vice versa. According to a one hundred and seventy-eighth aspect when referring back to any one of the first to one hundred and seventy-seventh aspects, the allocated resources comprise a first start frequency in a non-SBFD occasion and comprise a same start frequency in a SBFD occasion, e.g., the start RB of the initial non-SBFD slot is same as a previous SBFD slot; and wherein frequency hopping, FH is applied to successive non-SBFD slots. According to a one hundred and seventy-ninth aspect when referring back to the one hundred and seventy-eighth aspect, the start RB comprises a specific distance to the UL SB, e.g., be the closest RB to the UL SB or at maximum distance and it can be within the DL SB or a reference RB outside the DL SB. According to a one hundred and eightieth aspect when referring back to any one of the first to one hundred and seventy-ninth aspects, the device is to in case of shifted resources of an occasion, e.g., shifted by an offset or a frequency hopping offset, FH-offset, are outside an UL BWP and / or UL SB, the device is to: ^ ignoring the resources; ^ spread the resources across a domain relating to at least one of a time, a frequency, a spatial domain and a code domain; ^ split the resources across a domain relating to at least one of a time, a frequency, a spatial domain and a code domain; and / or ^ postpone the resources across a domain relating to at least one of a time, a frequency, a spatial domain and a code domain. According to a one hundred and eighty-first aspect when referring back to the one hundred and eighty-first aspect, the device is adapted to use additional resources in the frequency domain if available to compensate for the loss of the frequency resources outside the occasion. filing version an,rm FH241001PEP 2024P67397EP 114 According to a one hundred and eighty-second aspect when referring back to any one of the first to one hundred and eighty-first aspects, the device is adapted to operate in accordance with a demodulation reference signal, DMRS, bundling effective across multiple slots. According to a one hundred and eighty-third aspect when referring back to the one hundred and eighty-second aspect, the device is adapted to receive and / or transmit signals like repetition of PUSCH, multi-PUSCH, TB processing over multiple slots spread over a plurality of slots comprising at least one SBFD and at least one non-SBFD slot. According to a one hundred and eighty-fourth aspect when referring back to the one hundred and eighty-third aspect, the device is, adapted to implement the DMRS bundling differently for SBFD slots and non-SBFD slots. According to a one hundred and eighty-fifth aspect when referring back to the one hundred and eighty-third or one hundred and eighty-fourth aspect, the device is adapted to use same DMRS bundling parameters such as pusch-FrequencyHoppingInterval, pusch- TimeDomainWindowLength, for SBFD slots and non-SBFD slots; wherein the DMRS bundling is performed across SBFD and non-SBFD slots. According to a one hundred and eighty-sixth aspect when referring back to any one of the one hundred and eighty-third to one hundred and eighty-fifth aspects, the device is adapted to use different bundling parameters such as pusch-FrequencyHoppingInterval and / or pusch- TimeDomainWindowLength for SBFD and non-SBFD slots. According to a one hundred and eighty-seventh aspect when referring back to any one of the one hundred and eighty-third to one hundred and eighty-sixth aspects, the device is adapted to use a value of a bundling parameter such as pusch-FrequencyHoppingInterval and / or pusch-TimeDomainWindowLength as a minimum from the group of values comprising the bundling parameter indicated by the base station, gNB, and the number of consecutive slots of any one type. According to a one hundred and eighty-eighth aspect when referring back to any one of the one hundred and thirtieth to one hundred and eighty-seventh aspects, in a second case relating to an UD or DU scenario with the scheduled resource allocation partially overlapping with an UL SB and / or a guard band, wherein the device is to derive the actual frequency domain resources for SBFD slots as the SBFD time-frequency occasions for reception; filing version an,rm FH241001PEP 2024P67397EP 115 wherein the frequency domain resources for SBFD slots as the SBFD time-frequency occasions start from a start, wherein optionally an offset is provided by the gNB; or wherein a size of the resources is kept the same as a size of the frequency domain resources for non- SBFD slots or a new size is provided, wherein the device is adapted to ignore resources outside the DL SB are ignored for reception. According to a one hundred and eighty-ninth aspect when referring back to the one hundred and eighty-eighth aspect, a start RB comprises a specific distance to the UL SB, e.g., be the closest RB to the UL SB or at maximum distance and it can be within the DL SB or a reference RB outside the DL SB. According to a one hundred and ninetieth aspect when referring back to any one of the one hundred and thirtieth to one hundred and eighty-ninth aspects, in a third case relating to a DUD scenario with the scheduled SPS occasion as the SBFD time-frequency occasion fully overlapping with an UL SB and / or a guard band, wherein the device is to derive the actual frequency domain resources for SBFD slots as the SBFD time-frequency occasions for reception; wherein frequency domain resources for SBFD slots as the SBFD time-frequency occasions start from a start RB , wherein optionally an offset is provided by the gNB, wherein which DL SB to choose is indicated by the gNB or predefined; or wherein a size of the resources is kept the same as the size of the frequency domain resources for non-SBFD slots, wherein the device is to ignore resources outside the DL SB if the size is such that it goes beyond the DL SB; or wherein the device is to consider a total number of RBs, e.g., a size of the scheduled frequency domain resources, and to spread it equally across the two DL SBs such that an available number of DL resources remains the same, or wherein such a size is optionally provided by the gNB; or wherein the device chooses one of such options that maximizes the number of available DL RBs for SPS reception. According to a one hundred and ninety-first aspect when referring back to the one hundred and ninetieth aspect, the start RB comprises a specific distance to the UL SB, e.g., be the filing version an,rm FH241001PEP 2024P67397EP 116 closest RB to the UL SB or at maximum distance and it can be within one of the DL SBs or a reference RB outside the DL SB. According to a one hundred and ninety-second aspect when referring back to any one of the one hundred and thirtieth to one hundred and ninety-first aspects, in a fourth case relating to a DUD scenario with the scheduled SPS occasion as the SBFD time-frequency occasion partially overlapping with UL SB and / or a guard band and partially overlapping with both the DL SBs, the device is to derive the frequency domain resources for SBFD slots as the SBFD time-frequency occasions for reception; wherein the frequency domain resources for SBFD slots as the SBFD time-frequency occasions start from the start RB ; wherein optionally an offset is provided by the gNB; or wherein which DL SB to choose is indicated by the gNB or predefined; wherein a size of the resources is kept the same as the size of the frequency domain resources for non-SBFD slots or a new size is provided; wherein if the size is such that it goes beyond the DL SB, then the device is to ignore resources outside the DL SB; or wherein the device is to consider the total number of RBs, e.g., a size of the scheduled frequency domain resources, and to spread it equally across the two DL SBs such that an available number of DL resources remains the same, or wherein such a size is optionally provided by the gNB; or wherein the device chooses one of such options that maximizes the number of available DL RBs for SPS reception. According to a one hundred and ninety-third aspect when referring back to the one hundred and ninety-second aspect, the start RB comprises a specific distance to the UL SB, e.g., be the closest RB to the UL SB or at maximum distance and it can be within one of the DL SBs or a reference RB outside the DL SB. According to a one hundred and ninety-fourth aspect when referring back to any one of the one hundred and thirtieth to one hundred and ninety-third aspects, in a fifth case relating to a DUD scenario with the scheduled SPS occasion as the SBFD time-frequency occasion partially overlapping with UL SB and / or guard band and partially overlapping with only one of the DL SBs, the device is to derive the actual frequency domain resources for SBFD slots to receive SPS; filing version an,rm FH241001PEP 2024P67397EP 117 wherein the frequency domain resources for SBFD slots as the SBFD time-frequency occasions start from the start RB ; wherein optionally an offset is provided by the gNB; wherein which DL SB to choose is be indicated by the gNB or predefined; or wherein the device is to select the DL SB with which an occasion of the resource allocation partially overlaps; or wherein the frequency domain resources for SBFD slots as the SBFD time-frequency occasions start from the start RB of one of the DL SBs which is nearer to the UL SB; wherein optionally an offset is provided by the gNB; wherein which DL SB to choose is indicated by the gNB or predefined; or wherein the device is select the DL SB with which the SPS occasion partially overlaps; or wherein the device is to consider the total number of RBs, e.g., a size of the scheduled frequency domain resources, and to spread it equally across the two DL SBs such that an available number of DL resources remains the same, or wherein such a size is optionally provided by the gNB; or wherein the device chooses one of such options that maximizes the number of available DL RBs for SPS reception. According to a one hundred and ninety-fifth aspect when referring back to the one hundred and ninety-fourth aspect, the start RB comprises a specific distance to the UL SB, e.g., be the closest RB to the UL SB or at maximum distance and it can be within one of the DL SBs or a reference RB outside the DL SB. According to a one hundred and ninety-sixth aspect when referring back to any one of the one hundred and twenty-fourth to one hundred and ninety-fifth aspects, a TDRA of the resource allocation is kept the same as in case of non-SBFD slots; or wherein a different TDRA is provided; and / or a spreading and / or a splitting of the resources is done over time domain resources. According to a one hundred and ninety-seventh aspect when referring back to any one of the one hundred and twenty-third to one hundred and ninety-sixth aspects, a parameter is provided, e.g., in RRC or DCI, by the gNB to indicate whether the device is to derive the frequency domain resources for the SBFD symbols from the frequency domain resources of the non-SBFD symbols. filing version an,rm FH241001P...

Claims

FH241001PEP 2024P67397EP 126 Claims 1. A device for operating in a wireless communication network, wherein the device is adapted to determine a resource allocation allocating resources of the wireless communication network, e.g., for uplink, UL, and / or downlink, DL, and / or sidelink and to use the allocated resources based on whether the resources are within a subband full duplex, SBFD, time-frequency occasion.

2. The device of claim 1, wherein the SBFD time frequency occasion is either an SBFD symbol or a non-SBFD symbol from which only one is a valid symbol type for the SBFD time frequency occasion; wherein the device is to determine that a first time-frequency occasion of the resource allocation, e.g., related to a SRS transmission occasion, is valid in one of the SBFD symbol type and the non-SBFD symbol type and invalid in the other symbol type 3. The device of claim 2, adapted to drop a transmission in an invalid symbol type; or adapted to postpone a transmission in an invalid symbol type according to the resource allocation to a next available set of UL resources.

4. The device of claim 3, wherein for an UL transmission across a SBFD occasion and a non-SBFD occasion in different slots the device is to postpone the transmission in the invalid symbol type, e.g., for a PUSCH repetition type A with available slot counting, A- SRS with available slot counting, TBoMS and PUCCH repetitions.

5. The device of claim 3 or 4, adapted to drop the transmission for CG PUSCH with neither TBoMS nor PUSCH repetition type A with available slot counting, SPS PDSCH, P / SP SRS, P / SP CSI-RS, P / SP PUCCH, SP-CSI on PUSCH, PUSCH repetition type A without available slot counting, multi-PUSCH / PDSCH scheduled by a single DCI, and PDSCH repetitions in the invalid symbol type.

6. The device of one of claims 2 to 5, adapted to use the allocated resource for an uplink transmission related to an SBFD occasion, e.g., a SRS transmission, based on identifying that the resources are satisfying a condition according to which SBFD occasions are available or valid for the time-domain location(s) for all the SRS resources filing version an,rmFH241001PEP 2024P67397EP 127 in the resource set and it satisfies the UE capability on the minimum timing requirement between triggering PDCCH and all the SRS resources in the resource set.

7. The device of one of claims 2 to 6, adapted to use the allocated resource for an uplink transmission related to a non-SBFD occasion, e.g., a SRS transmission, based on identifying that the resources are satisfying a condition according to which uplink symbols and / or flexible symbol(s) configured as non-SBFD symbols for at least one time-domain location for all resources in the resource set.

8. The device of one of the previous claims, wherein the device is to determine a starting resource for the uplink transmission in SBFD symbols according to, ^^^^ௌ^ி^ ^^ ௌ^ ^^^ିௌ^ி^^௧^^௧ ൌ ^^^^^௧^^௧ ^ ൫^^^^^௧^^௧ ^ ^^^^^ௌ^^^ி^^^௧൯^^^^^^^^^^^^௭ௌ^^ wherein ^^^^^ௌ^^^ி^^^௧is set to zero if unconfigured.

9. The device of one of the previous claims, wherein the resource allocation comprises a frequency hopping, FH, shifting a frequency of used resources in subsequent uplink occasions by a FH-offset, wherein a start frequency resource of the resource allocation is provided for a first hop and start frequency resources of subsequent hops within the slot or across slots are derived using a FH-offset, e.g., using a legacy formula.

10. The device of claim 9, wherein for an uplink intra-slot frequency hopping in SBFD symbols, a starting frequency, e.g., associated with a resource block, RB, in each hop is given by:

11. The device of claim 9 or 10, wherein for an uplink inter-slot frequency hopping in SBFD symbols and based on pusch-DMRS-Bundling being enabled, or for inter-slot frequency hopping for a PUSCH in SBFD symbols, e.g., scheduled by random access response, RAR, UL grant or DCI format 0_0 with CRC scrambled by TC-RNTI, the starting RBwhere filing version an,rmFH241001PEP 2024P67397EP 128 ^ RB^^ ୗ^ ^^ୟ୰^is the starting PRB index of UL usable PRBs with reference to the start of UL active BWP, ^ N^^୧^^^ୗ^is the number of UL usable PRBs, ^ RB^^ୟ୰^is the starting PRB index of the first PUSCH hop with reference to the start of UL active BWP. For PUSCH transmissions with Configuration 2, RB^^ୟ୰^is the starting PRB index with reference to the start of UL active BWP after applying RB offset between non-SBFD symbols and SBFD symbols. ^ RB offset is the frequency hopping offset for PUSCH in SBFD symbols, ^ Note: Definition ofis unchanged from existing specifications.

12. The device of one of claims 9 to 11, wherein the allocated resources comprise a first start frequency in a non-SBFD occasion and comprise a different second start frequency in an SBFD occasion.

13. The device of one of claims 9 to 12, wherein the second start frequency provides a shift of uplink resources of a non-SBFD occasion that are at least partially assigned to a downlink in the SBFD occasion to resources assigned to uplink in the SBFD occasion, wherein resources allocated for the occasion in a non-SBFD slot are shifted such that the shifted resources are contained within an UL bandwidth part, BWP, and the UL subband, SB.

14. The device according to one of the previous claims, wherein the device is to determine whether the resources are within a subband full duplex, SBFD, time-frequency occasion and to adapt the use of the allocated resourced based on a determination result.

15. The device according to one of the previous claims, wherein the resource allocation is a periodic allocation or a repetitive allocation, e.g., a semi-persistent scheduling, SPS.

16. The device according to one of previous claims, wherein the device is adapted to determine whether a slot is a SBFD-time-frequency occasion, e.g., a slot, or a non-SBFD time-frequency occasion and to determine a same or a different result for using the allocated resources in for the SBFD time frequency occasion and the non-SBFD time frequency occasion.

17. The device according to one of previous claims, wherein the device is adapted to receive the resource allocation as valid for at least one SBFD time-frequency occasion and at least one non-SBFD time-frequency occasion. filing version an,rmFH241001PEP 2024P67397EP 129 18. The device according to one of previous claims, wherein the device is configurable with the resource allocation, e.g., using a scheduling information such as frequency domain resource allocation, FDRA, the scheduling information indicating an allocation of frequency domain resources, e.g., a bandwidth part, BWP, or at least one subband, of the wireless communication network.

19. The device according to one of previous claims, wherein the device is configurable with the resource allocation with a single scheduling information provided to the device, e.g., by an activation downlink control information, DCI, e.g., for semi-persistent scheduling, SPS, and to determine for each of a plurality of -time-frequency occasion whether the resource allocation allocates resources to an SBFD -time-frequency occasion or a non- SBFD time-frequency occasion.

20. The device according to one of previous claims, adapted to receive a single frequency domain resource allocation, FDRA, as at least a part of the resource allocation by an activation downlink control information, DCI, for SPS and for SBFD time-frequency occasion and non-SBFD time-frequency occasion.

21. The device according to one of previous claims, wherein the device is adapted to ignore uplink resources of a SBFD time-frequency occasion for a downlink transmission that uses resources of the resource allocation; and / or wherein the device is adapted to ignore downlink resources of a SBFD time-frequency occasion for an uplink transmission that uses resources of the resource allocation.

22. The device according to one of previous claims, wherein a first time-frequency occasion of the frequency allocation overlaps with an SBFD symbol of an SBFD time-frequency occasion and a second time-frequency occasion of the frequency allocation overlaps with a non- SBFD time-frequency occasion, e.g., a slot or symbol, wherein the device is adapted to treat all symbols of the first time-frequency occasion to be of a particular type, e.g., type SBFD or non-SBFD.

23. The device according to claim 22, wherein the device is adapted to determine a number of symbols in the first time-frequency occasion to be of either SBFD type or of non-SBFD type, wherein in case the number exceeding a threshold the device is adapted to treat all symbols in the first time-frequency occasion as SBFD symbols; and / or in case the number not exceeding the threshold the device is adapted to treat all symbols in the first time-frequency occasion as non-SBFD symbols.. filing version an,rmFH241001PEP 2024P67397EP 130 24. The device according to claim 23, wherein the threshold, e.g., number n, is predefined or signalled by the wireless communication network.

25. The device according to claim 23 or 24, wherein the device is adapted to treat non-SBFD symbols the same way as SBFD symbols based on determining the number of symbols and to use same DL resources used for reception in the SBFD symbols for reception in the non-SBFD symbols according to the resource allocation.

26. The device according to one of previous claims, adapted to use a first modulation coding scheme, MCS, for a SBFD symbol of the SBFD time-frequency occasions and a second MCS for a non-SBFD symbol of a non-SBFD time-frequency occasions.

27. The device of claim 26, configured for receiving and / or decoding explicit information indicating the first MCS and the second MCS, e.g., as a combined value or as two separate values.

28. The device of claim 26 or 27, configured for receiving and / or decoding two different DCI, a first DCI containing a first MCS value indicating the first MCS and a second DCI containing a second MCS value indicating the second MCS.

29. The device of claim 28, wherein the first DCI and the second DCI contain a time domain resource allocation, TDRA, wherein the device is adapted to decode the first DCI and the second DCI and to determine which TDRA corresponds to SBFD symbols or non- SBFD symbols.

30. The device of claim 29, wherein the device is adapted to determine the first or second DCI containing the TDRA is for SBFD symbols based on the TDRA overlapping with a SBFD symbol of a SBFD slot.

31. The device of one of claims 28 to 30, wherein the first DCI and the second DCI are linked to two different values of SPS-Config indices in separate SPS-Configs, wherein a first SPS-Config index corresponds to SBFD symbols of the SBFD slot and a second SPS- Config index corresponds to non-SBFD symbols of the non-SBFD slot.

32. The device of claim 31, wherein an SBFDIndicator parameter of one bit forms a part of the SPS-Config, wherein for a particular SPS-Config index, if this parameter is set to 0 filing version an,rmFH241001PEP 2024P67397EP 131 or 1, then the SPS-Config index is for SBFD symbols and otherwise for non-SBFD symbols.

33. The device of one of claims 28 to 32, wherein the first DCI and the second DCI each comprise an indicator indicating whether it is for SBFD of the SBFD slot or non-SBFD symbols of the non-SBFD slot, e.g., using at least one unused / reserved DCI bit, for example, unused / reserved according to a legacy NR standard.

34. The device of one of claims 28 to 33, wherein the device is adapted to decode the first DCI and second DCI and to associate a lower MCS value of the first MCS value and the second MCS value with SBFD symbols of the SBFD slot.

35. The device of one of claims 26 to 34, wherein the device is adapted to receive, e.g., from a base station, gNB a single DCI indicating the first MCS and the second MCS, e.g., using at least one unused / reserved DCI bit, for example, unused / reserved according to a legacy NR standard.

36. The device of claim 35, wherein the device is adapted to interpret a parameter in a configuration message, e.g., a SPS-Config message or in an RRC message received from the gNB, as indicating whether a second MCS value for the SBFD symbols will be provided to the device or not.

37. The device of claim 36, wherein the configuration message comprises a one bit field, e.g., called SecondMCS in RRC, is set to one of 1 and 0, wherein the device is adapted to expect to receive an MCS value for a SBFD symbol in the SBFD slot in the DCI; or is set to the other of 1 and 0 or in case the field is absent, the device is adapted to use a same MCS for an SBFD symbol and a non-SBFD symbol.

38. The device of one of claims 35 to 37, wherein a field used for sending the MCS for a second transport block, TB, in DCI is used to send the MCS for a SBFD symbol of the SBFD time-frequency occasions, e.g., if SBFD is configured.

39. The device of one of claims 26 to 38, wherein the first MCS and the second MCS are part of a same reference MCS table supported by the wireless communication network, or wherein the first MCS is indicated in a first MCS table and the second MCS is indicated in a second MCS table, wherein one of the first MCS table and the second MCS table is associated with SBFD symbols and the other is associated with non-SBFD symbol. filing version an,rmFH241001PEP 2024P67397EP 132 40. The device of claim 39, wherein the MCS table associated with the SBFD symbol is derived from the same MCS reference table used for the non-SBFD symbol, e.g., an existing parameter for reference to MCS table in SPS-Config is used.

41. The device of claim 39 or 40, wherein the MCS value of the first MCS value and the second MCS value that is associated with the SBFD symbol is derived from a different MCS reference table than that is used for non-SBFD symbols.

42. The device of claim 41, wherein a MCS reference table for the non-SBFD symbols is provided by a parameter mcs-Table in SPS-Config and the MCS reference table for SBFD symbol is provided to the device by a different parameter in SPS-Config or in radio resource control, RRC.

43. The device of claim 41 or 42, wherein a first parameter and a second parameter for MCS reference tables for non-SBFD symbols and SBFD symbols are provided in SPS-Config or in RRC.

44. The device of one of claims 41 to 43, wherein a MCS reference table for the SBFD symbols is provided in PDSCH-Config, e.g., as a new parameter, wherein optionally, a parameter mcs-Table in SPS-Config is used for the MCS value related to non-SBFD symbols.

45. The device of one of claims 41 to 44, wherein MCS reference tables for both the SBFD symbols and non-SBFD symbols are provided in PDSCH-Config.

46. The device of one of claims 26 to 45, configured for implicitly deriving information indicating the first MCS and / or the second MCS.

47. The device of claim 46, configured for deriving the MCS value for a SBFD symbol of the SBFD time-frequency occasion from the MCS value for the non- SBFD symbol of the non-SBFD slot.

48. The device of claim 47, adapted to derive the MCS value for the SBFD symbol based on a report provided to the wireless communication network. filing version an,rmFH241001PEP 2024P67397EP 133 49. The device of claim 47 or 48, wherein the device is adapted to respond a request of a base station, gNB with a feedback, e.g., using higher layer signalling like RRC or Media Access Control, MAC, wherein the device is adapted to derive the MCS value for the SBFD symbol based on the feedback.

50. The device of claim 49, wherein the device is adapted to deriving the MCS value for the SBFD symbol from a parameter comprising an interference such as a signal to noise and interference ratio, SINR, and / or any other channel state related parameter for SBFD and non-SBFD symbols.

51. The device of claim 48 to 50, wherein the device is adapted to deriving the MCS value for the SBFD symbol from a difference of parameters comprising an interference such as a signal to noise and interference ratio, SINR, and / or any other channel state related parameter for SBFD and non-SBFD symbols.

52. The device of one of claims 48 to 51, wherein the device is adapted to deriving the MCS value for the SBFD symbol based a specified formula or from a look up table relating the MCS value to the parameter.

53. The device of one of claims 48 to 52, wherein the device is adapted to deriving the parameter based on the difference between SINR or interference or any other channel state related parameter for SBFD and non-SBFD symbols; wherein the device optionally derives an MCS value for the SBFD symbols based on the parameter, e.g., using some specified formula or from a look up table relating the MCS value to the parameter.

54. The device of one of claims 48 to 53, wherein the device is adapted to derive at least one parameter based on the MCS value to be applied for the SBFD symbols, e.g., this MCS value is calculated by the device based on the SINR of SBFD symbols and the device directly reports this MCS value.

55. The device of one of claims 48 to 54, wherein device is adapted to determine at least one of a first MCS value and a second MCS value based on a baseline MCS as an offset from the baseline MCS.

56. The device of one of claims 46 to 55, adapted to receive the resource allocation, e.g., SPS, in one or more SBFD symbols with a same MCS value the device has calculated filing version an,rmFH241001PEP 2024P67397EP 134 and based on an acknowledgement received from the gNB, the acknowledgement acknowledging the calculated MCS value.

57. The device according to claim 56, wherein the device is adapted to send a feedback to the gNB subject to the acknowledgement based upon a condition, e.g., if the difference between the MCS for SBFD and non-SBFD symbols is greater than a given threshold, then only the device reports the feedback, wherein the threshold can be pre-defined in the specification or provided by the gNB to the device.

58. The device of one of claims 46 to 57, wherein the device is adapted to use assistant information received from the gNB for a calculation of the MCS for SBFD symbols.

59. The device of claim 58, wherein the assistant information comprises certain information about the interference on the SBFD symbols, wherein the device calculates the MCS based on the certain information and optionally provides this MCS as feedback to the gNB.

60. The device of one of claims 46 to 59, wherein the MCS related to non-SBFD symbols is indicated to the device by a row number of a reference MCS table; wherein the device is adapted to derive the MCS for SBFD symbols based on the MCS related to non-SBFD symbols and based on a fixed offset value; or wherein the MCS related to SBFD symbols is indicated to the device by a row number of a reference MCS table; wherein the device is adapted to derive the MCS for non- SBFD symbols based on the MCS related to SBFD symbols and based on a fixed offset value.

61. The device of one of claims 26 to 60, wherein the device is adapted to obtain an MCS offset value provided in message such as a SPS-Config message and is adapted to use the MCS offset value to derive the MCS for SBFD symbols from the MCS used for non- SBFD symbols; or to use the MCS offset value to derive the MCS for non-SBFD symbols from the MCS used for SBFD symbols.

62. The device of one of previous claims, wherein the device is to determine a transport block size, TBS, for DL SPS data, based on an available number of DL resources in the SBFD symbols, e.g., instead of the total number of resources in the DL active BWP. filing version an,rmFH241001PEP 2024P67397EP 135 63. The device of claim 62, adapted to use a first modulation coding scheme, MCS, for a SBFD symbol of a SBFD-slot as the SBFD time-frequency occasions and a second MCS for a non-SBFD symbol of a non-SBFD time-frequency occasion ; wherein the device is to consider a number of allocated resource blocks, RBs, to be the number of available DL RBs for SBFD symbols; wherein a different MCS is provided or derived for SBFD symbols when compared to non-SFBFD symbols, and to calculate the TBS based thereon.

64. The device of claim 63, wherein a xOverhead parameter comprises a different value when provided explicitly for SBFD symbols and when being implicitly determined, e.g., based on available DL resources or unavailable DL resources.

65. The device of one of previous claims, adapted for ignoring a time-frequency occasion of the frequency allocation, if at least a certain number of n symbols of the time-frequency occasion are SBFD symbols of one or more SBFD slots.

66. The device of claim 65, wherein the device is to determine a number of available DL resources of the resource allocation, e.g., a given FDRA, in the SBFD symbols and to ignore the time-frequency occasion in a case where the number of available DL resources is lower than a resource threshold.

67. The device of claim 66, wherein the resource threshold is predetermined, e.g., specified in a NR specification, or provided by the wireless communication network, e.g., a gNB, for example, using RRC or DCI.

68. The device of one of claims 65 to 67, adapted for determining whether a calculated TBS for the available DL resources and MCS is below a TBS threshold and for ignoring the time-frequency occasion based thereon.

69. The device of claim 68, wherein the TBS threshold is predetermined, e.g., specified in a NR specification, or provided by the wireless communication network, e.g., a gNB, for example, using RRC or DCI.

70. The device of one of claims 65 to 69, wherein the value of n is preconfigured, e.g., defined in a specification, or is or provided by the wireless communication network, e.g., a gNB, wherein the value of n is at least 1. filing version an,rmFH241001PEP 2024P67397EP 136 71. The device of one of claims 65 to 70, wherein the device is to not ignore the time- frequency occasion based on a priority of a data transmission in that time-frequency occasion being at least a priority threshold, e.g., if a high priority flag is indicated by the gNB.

72. The device of one of claims 65 to 71, adapted to not expecting a transmission from a gNB based on a condition for ignoring the time-frequency occasion being met.

73. The device of one of claims 65 to 72, wherein based on a condition for ignoring the time- frequency occasion being met the device is adapted to postpone reception according to the resource allocation to a next available set of DL resources.

74. The device of claim 73, adapted to postpone reception based on the time-frequency occasion being ignored by the device due to some pre-defined conditions being satisfied.

75. The device of claim 73 or 74, adapted to postpone reception based on whether there is at least one available non-SBFD DL slot where the configured frequency resources of the resource allocation are available.

76. The device of one of claims 73 to 75, adapted to postpone reception only if at least one available non-SBFD time-frequency occasion occurs before the next scheduled time- frequency occasion.

77. The device of one of claims 73 to 76, wherein the device is adapted to provide a capability information to the wireless communication network indicating that the device capable of receiving a postponed reception.

78. The device of one of claims 72 to 77, adapted to postpone or to ignore a reception or transmission only if a condition related to one or more of ^ a transmission, ^ a retransmission, ^ a reception, ^ a processing, ^ a delay, ^ a timing, is satisfied. filing version an,rmFH241001PEP 2024P67397EP 137 79. The device of claim 78, wherein the condition related to a processing refers to one or more of ^ a signal processing capability of the UE, ^ a timing with respect to the signal processing, e.g., a processing delay.

80. The device of claim 78 or 79, wherein the condition comprises that a next available valid slot is within a configured or pre-configured or predefined number of n slots / symbols / time duration from the slot being ignored.

81. The device of one of claims 78 to 80, wherein the condition relating to a retransmission refers to at least one of: ^ a HARQ-timing condition to be satisfied, e.g., transmitting on the postponed slot is the only possibility to transmit in time, prior to receiving a HARQ-NACK for a failed transmission, ^ a radio link failure, RLF, timing related condition, e.g., a last possibility to transmit in a scenario where the radio channel is degrading, e.g., a cell-edge UE, ^ a code block group, CBG,-based condition, e.g., the last n-CBGs have not been transmitted and the postponed transmission could avoid a transmission which would be either too late or which could be better utilized by other code blocks.

82. The device of one of claims 78 to 81, wherein the condition is as a transmission or retransmission related condition related to a type of the data transmitted.

83. The device of one of claims 78 to 82, wherein the condition is as a reception related condition related to a type of the signal received.

84. The device of one of claims 78 to 83, wherein the device is to postpone the occasion to a different frequency such as a transmission in a different bandwidth part, BWP, or carrier, or to trigger a data duplication transmission or redundancy transmission in the different frequency, e.g., in order to increase the probability of a successful transmission.

85. The device of claim 84, wherein the postponing, data duplication transmission or redundance transmission is related to one or more of the following: ^ an exact location of a carrier e.g., frequency band in FR1 or FR2 or FR3, ^ an available bandwidth given for a said carrier and / or BWP, ^ a numerology configured for a said BWP, e.g., [15, 30, 60, …] SCS, filing version an,rmFH241001PEP 2024P67397EP 138 ^ a utilization in a given band, ^ a measurement-related conditions, e.g., the interference in a given band, e.g., measured by RSRP, SINR, or similar KPIs.

86. The device of one of claims 73 to 85, adapted to consider a HARQ process ID to remain same based on postponing reception.

87. The device of one of previous claims, adapted to use, from a time-frequency occasion of the scheduling, a first portion of the allocated resources to map a first portion of a data / transport block and to spread, e.g., using consecutive symbols, a remaining second portion of the data / transport block into other available resources which are shifted in time with respect to the allocated resources [e.g. general: allowing earlier or later resources], e.g., to suffice the resource allocation.

88. The device of claim 87, wherein the other resources are subsequent resources or symbols, e.g., DL resources.

89. The device of claim 87 or 88, wherein the device is to expect reception of a signal to be spread to the second portion of the scheduled resources in a case where consecutive symbols in time domain are available to the device, e.g., just after the last symbol of the allocated resources in the time-frequency occasion or before the first symbol of the time- frequency occasion.

90. The device of one of claims 87 to 89, wherein the device is to receive the second portion with same frequency domain resources as the first portion of resources.

91. The device of one of claims 87 to 90, wherein the device is to receive the second portion with different frequency domain resources in a consecutive symbol being a non-SBFD symbol.

92. The device of one of claims 87 to 91, wherein the device is to receive the second portion using a same set of frequency domain resources in a consecutive symbol being a non- SBFD symbol.

93. The device of one of claims 87 to 92, wherein the device is to expect reception of a signal to be spread to the second portion based on a condition relating to at least one of a filing version an,rmFH241001PEP 2024P67397EP 139 transmission timing, a reception timing, a processing timing and a delay timing is satisfied.

94. The device of one of claims 87 to 93, wherein the device is to expect reception of a signal to be spread to the second portion when a number of n consecutive time domain symbols are available.

95. The device of claim 94, wherein the number n is calculated, e.g., by the device, as a minimum number of time domain symbols such that the number of REs in the first portion and in the second portion is equal to or more than a given number N’REof resource elements, REs, determined based on the determination rule: ^^′ ^^ ^ோோா ൌ ^^ோ^ ^^^ ∙ ^^^௬^^ െ ^^^ெோௌ െ ^^^^^ோ^, where ^ ^^′ோாis a number of Res for the data in an RB, ^ ^^^ோ^^is 12 (number of subcarrier in an RB), ^ ^^^^௬^^^is the number of allocated symbols in a time domain, ^number of DMRS REs in the RB, ^ ^^^^^ோ^overhead is configured by higher layer as xOverhead, and ^ ^^^^^^ is explicitly provided for SBFD symbols.

96. The device of claim 94 or 95, wherein the number n is calculated, e.g., by the device, as a minimum number of time domain symbols such that the number of REs in the first portion and in the second portion is equal to or more than a given number NREof resource elements, REs, determined based on the determination rule: ^^ோா ൌ min^156, ^^′ோா^ ∙ ^^^ோ^,where ^ ^^ோாis the number of Res for the data in an RB, ^ ^^^ோ^is the number of allocated RBs for the reception of the data, and ^ ^^^^^^ is only the allocated RS that are within the DL SB are used for SBFD symbols.

97. The device of one of claims 93 to 96, wherein the number n is calculated, e.g., by the device, as a minimum number of time domain symbols such that an unquantized intermediate variable is equal to or more than a given number of unquantized intermediate variable Ninf oor a TBS derived from the unquantized intermediate variable filing version an,rmFH241001PEP 2024P67397EP 140 is equal to or more than a TBS derived from the given number of unquantized intermediate variable Ninf o, the given number of unquantized intermediate variable Ninf odetermined based on the determination rule:where ^unquantized intermediate variable, ^ ^^ is the code rate, ^ ^^ is the modulation order, and ^ ^^ is the number of layers.

98. The device of one of claims 94 to 97, wherein the number of REs or unquantized intermediate variable or TBS is equal to the number of REs or unquantized intermediate variable or TBS of the allocated resources in non-SBFD symbols.

99. The device of one of claims 94 to 98, wherein the number of REs or unquantized intermediate variable or TBS is provided by the gNB.

100. The device of one of claims 94 to 99, wherein the number n is provided by the gNB, e.g., in RRC, MAC and / or DCI.

101. The device of one of previous claims, wherein the device is to use, from a time-frequency occasion of the scheduling, a first portion of the allocated resources to map a first portion of a data / transport block and to split a remaining second portion of the data / transport block to at least one other slot to thereby split the resource allocation over a plurality of slots, e.g., optionally omitting an intermediate slot in the time domain, e.g., to suffice the resource allocation.

102. The device of claim 101, wherein the device is to split the resource allocation over consecutive or non-consecutive slots in time domain are available to the device, wherein at least one slot of the plurality of slots is later than a last slot of an actual time-frequency occasion of the scheduled resources; and / or wherein at least one slot of the plurality of slots is earlier than a first slot of the actual time-frequency occasion of the scheduled resources.

103. The device of claim 101 or 102, wherein the device is to expect reception of a signal to be split to the second portion of the scheduled resources in a case where consecutive filing version an,rmFH241001PEP 2024P67397EP 141 slots in time domain are available to the device, e.g., just after the last slot of the allocated resources in the time-frequency occasion or before the first slot of the time-frequency occasion.

104. The device of one of claims 102 to 103, wherein the device is to receive the second portion with same frequency domain resources as the first portion of resources.

105. The device of one of claims 101 to 104, wherein the device is to receive the second portion with different frequency domain resources in a consecutive symbol of a non- SBFD time-frequency occasion.

106. The device of one of claims 101 to 105, wherein the device is to receive the second portion using a same set of frequency domain resources in a consecutive slot being a non-SBFD symbol.

107. The device of one of claims 101 to 106, wherein the device is to expect reception of a signal to be split based on a condition relating to at least one of a transmission timing, a reception timing, a processing timing and a delay timing is satisfied.

108. The device of one of claims 101 to 107, wherein the device is to expect reception of a signal to be split when a number of n consecutive time domain slots are available.

109. The device of claim 108, wherein the number n is calculated, e.g., by the device, as a minimum number of time domain slots such that the number of REs in the first portion and in the second portion is equal to or more than a given number N’REof resource elements, REs, determined based on the determination rule: ^^′ ^^ ^ோோா ൌ ^^ோ^^^ ∙ ^^^௬^^ െ ^^ ^^ெோௌ െ ^^^^^ோ^, where ^ ^^′ோாis the number of Res for the data in an RB, ^ ^^^ோ^^is 12 (number of subcarriers in an RB), ^ ^^^^௬^^^is the number of allocated symbols in the time domain, ^number of DMRS Res in the RB, ^ ^^^^^ோ^is the overhead configured by higher layer as xOverhead, and ^ ^^^^^^ is the explicitly provided for SBFD symbols. filing version an,rmFH241001PEP 2024P67397EP 142 110. The device of claim 108 or 109, wherein the number n is calculated, e.g., by the device, as a minimum number of time domain slots such that the number of REs in the first portion and in the second portion is equal to or more than a given number NREof resource elements, REs, determined based on the determination rule: ^^ோா ൌ min^156, ^^′ோா^ ∙ ^^^ோ^,where ^ ^^ோாis the number of Res for the data in an RB, ^ ^^^ோ^is the number of allocated RBs for the reception of the data, and ^ ^^^^^^ is only the allocated RBs that are within the DL SB are used for SBFD symbols.

111. The device of one of claims 108 to 109, wherein the number n is calculated, e.g., by the device, as a minimum number of time domain slots such that an unquantized intermediate variable is equal to or more than a given number of unquantized intermediate variable Ninf oor a TBS derived from the unquantized intermediate variable is equal to or more than a TBS derived from the given number of unquantized intermediate variable Ninf o, the given number of unquantized intermediate variable Ninf odetermined based on the determination rule: ^^୧୬^ ^ ൌ ^^ோா ∙ ^^ ∙ ^^^ ∙ ^^where ^ ^^ is the unquantized intermediate variable, ^ ^^ is the code rate, ^ ^^ is the modulation order, and ^ ^^ is different for SBFD symbols.

112. The device of one of claims 108 to 111, wherein the number of REs or unquantized intermediate variable or TBS is equal to the number of REs or unquantized intermediate variable or TBS of the allocated resources in non-SBFD symbols.

113. The device of one of claims 108 to 112, wherein the number of REs or unquantized intermediate variable or TBS is provided by the gNB.

114. The device of one of claims 108 to 113, wherein the number n is provided by the gNB, e.g., in RRC, MAC and / or DCI. filing version an,rmFH241001PEP 2024P67397EP 143 115. The device of one of claims 108 to 114, adapted to consider a HARQ process ID to remain same based on the splitting.

116. The device of one of previous claims, wherein based on being provided with separate configurations, e.g., with one or more SPS-Config messages, for an SBFD symbol and for a non-SBFD symbol, the device is adapted or search to decode more than one DCI with a same SPS-Config index for activation of both configurations, expecting the same SPS-Config indices provided for both SBFD and non-SBFD symbols.

117. The device of claim 116, wherein the device is to decode or search more than one DCI based on an indication, e.g., an explicit indication, received from the gNB.

120. The device of claim 116 or 117, wherein the device is to keep a HARQ process ID the same for both configurations.

121. The device of claim 118, wherein the HARQ process ID calculated, e.g., by the device, for non-SBFD symbols and is assumed to be valid for SBFD symbols; or wherein the HARQ process ID calculated, e.g., by the device, for SBFD symbols and is assumed to be valid for non-SBFD symbols.

120. The device of claim 118 or 119, wherein the HARQ process ID is calculated, e.g., by the device, based on an occasion number, e.g., the occasion number being equal for both SBFD time-frequency occasion and non-SBFD time-frequency occasion even if the slot numbers are different.

121. The device of one of previous claims, wherein based on being provided with separate configurations, the device is provided with different SPS-Config indices related to different SPS-Configs.

122. The device of claim 121, wherein the device is adapted to use a same HARQ process ID for both SPS-Configs.

123. The device of one of previous claims, wherein different frequency domain resources are allocated for SBFD and non-SBFD symbols. filing version an,rmFH241001PEP 2024P67397EP 144 124. The device of claim 123, wherein a TDRA is the same or different for the SBFD and non- SBFD symbols of the resource allocation.

125. The device of claim 123 or 124, wherein different resource allocation configurations, e.g., SPS configurations, possibly with same or separate SPS config indices, are provided to the device for SBFD time-frequency occasions and non-SBFD occasions.

126. The device of claim 125, wherein different DCIs are be provided to the device for SBFD and non-SBFD symbols, the different DCIs relating to different FDRAs.

127. The device of claim 126, wherein the FDRA provided for SBFD symbols is adapted to exclude UL resources from the frequency domain resource allocation.

128. The device of one of claims 123 to 127, wherein the device is provided with separate DCIs with separate FDRAs for a same SPS-Config, wherein the device differentiates between the DCIs for SBFD.time-frequency occasions and non-SBFD occasions.

129. The device of one of claims 123 to 128, wherein the device is to decode a single DCI that contains both the different frequency domain resources and for a same SPS-Config index.

130. The device of one of claims 123 to 129, wherein the device is to derive the frequency domain resources for the SBFD time-frequency occasions, e.g., symbols, from frequency domain resources of the non-SBFD time-frequency occasions, e.g., symbols, e.g., symbols, provided to the device or vice versa.

131. The device of claim 130, wherein to derive the frequency domain resources for the SBFD symbols the device is to implement a derivation that is based on an explicit indication by the gNB or an explicit indication included as a part of a virtual resource block-to-physical resource block (VRB-to-PRB) mapping of the allocated resources.

132. The device of claim 130 or 131, wherein in a first case relating to an UD scenario with the scheduled resource allocation fully overlapping with an UL SB and / or a guard band, wherein the device is to derive the actual frequency domain resources for SBFD slots as the SBFD time-frequency occasion for reception; filing version an,rmFH241001PEP 2024P67397EP 145 wherein frequency domain resources for SBFD slots as the SBFD time-frequency occasions start from a start RB ; wherein optionally, an offset is provided by the gNB; or a size of the resources is kept the same as the size of the frequency domain resources for non-SBFD slots or wherein a new size is provided; wherein the device is to ignore resources outside the DL SB for reception.

133. The device of one of claims 130 to 131, wherein in a first case relating to an UD or DU scenario with the scheduled DL resource allocation fully overlapping with an UL SB and / or a guard band, wherein the device is to derive the actual frequency domain resources for SBFD slots as the SBFD time-frequency occasion for reception; wherein frequency domain resources for SBFD slots as the SBFD time-frequency occasions start from a start RB; wherein a size of the resources is kept the same as the size of the frequency domain resources for non-SBFD slots or wherein a new size is provided; wherein the device is to ignore resources of an occasion outside the DL SB or DL BWP for reception; or to spread, split and / or postpone at last a part of the resources outside the DL SB or DL BWP across a domain relating to at least one of a time domain, a frequency domain, a spatial domain and a code domain.

134. The device of one of previous claims, wherein a distribution of resources allocated for transmission and resources allocated for reception within a bandwidth part, BWP, is different for different occasions; wherein a size of the resources is kept the same as the size of the frequency domain resources for different slots, e.g., between non-SBFD slots and SBFD slots, or wherein a new size is provided; wherein the device is to ignore resources of an occasion outside the UL SB / UL BWP for transmission; or to spread, split and / or postpone at last a part of the resources outside the UL SB / UL BWP across a domain relating to at least one of a time domain, a frequency domain, a spatial domain and a code domain.

135. The device of claim 134, adapted to use additional resources in the frequency domain and / or time domain and / or code domain and / or spatial domain. filing version an,rmFH241001PEP 2024P67397EP 146 136. The device of claim 133 or 135, wherein for at least some resource allocations, i.e., optionally, for the allocation, an indication relating to an offset is provided by the gNB.

137. The device of claim 136, wherein the offset relates to a number of at least one frequency units such as resource blocks, RBs, or Resource block groups, RBGs.

138. The device of one of previous claims, wherein the scheduled resources are associated with a downlink, DL, signal or channel and / or associated with an uplink, UL, signal or channel such as PUSCH or PUCCH and used for reception / transmission.

139. The device of one of previous claims, wherein a virtual resource block-to-physical resource block, VRB-to-PRB, mapping related to the occasion is interleaved or non- interleaved.

140. The device of claim 139, wherein whether the VRB-to-PRB mapping is interleaved or non-interleaved is a same for a non-SBFD occasion and a SBFD occasion; or varies between the non-SBFD occasion and a SBFD occasion from an interleaved structure to a non-interleaved structure or vice versa.

141. The device of one of previous claims, wherein the allocated resources comprise a first start frequency in a non-SBFD occasion and comprise a different second start frequency in a SBFD occasion.

142. The device according to claim 141, wherein the second start frequency provides a shift of uplink resources of a non-SBFD occasion that are at least partially assigned to downlink in the SBFD occasion to resources assigned to uplink in the SBFD occasion; or wherein the second start frequency provides a shift of downlink resources of a non- SBFD occasion that are at least partially assigned to uplink in the SBFD occasion to resources assigned to downlink in the SBFD occasion 143. The device of claim 142, wherein the shift is indicated, e.g., to the device, by means of one or more of ^ a physical layer signalling, e.g., using a DCI transmitted via PDCCH, ^ a use of MAC control elements, MAC CE, ^ an RRC signalling, e.g., via RRC IEs via PDSCH, filing version an,rmFH241001PEP 2024P67397EP 147 ^ a fixed offset configured by the network, e.g., via MIB, SIB, or configured using a fixed formular or value for a given carrier.

144. The device of claim 142, wherein the shift is determined by the device by means of ^ a calculation based on a formular configured or pre-configured at the UE, or ^ by means of prediction, e.g., based on training data on past SBFD / non-SBFD transmission calculated by an AI / ML algorithm.

145. The device of one of claims 141 to 144, wherein for a non-SBFD slot being an UL slot with resources allocated to the device, a size of the resources is based on a lowest frequency, e.g., resource block, RB or resource block group, RBG, and based on an upper frequency RB / RBG where the resource allocation ends.

146. The device of one of claims 141 to 145, wherein a FDRA provided, e.g., by downlink control information, DCI, for physical uplink shared channel, PUSCH, indicates the allocated resources.

147. The device of one of claims 141 to 146, wherein the second start frequency provides a shift of uplink resources of a non-SBFD occasion that are at least partially assigned to downlink in the SBFD occasion to resources assigned to uplink in the SBFD occasionwherein resources allocated for the occasion in a non-SBFD slot are shifted such that the shifted resources are contained within an UL bandwidth part, BWP, and the UL subband, SB; or wherein the second start frequency provides a shift of downlink resources of a non-SBFD occasion that are at least partially assigned to uplink in the SBFD occasion to resources assigned to downlink in the SBFD occasion wherein resources allocated for the occasion in a non-SBFD slot are shifted such that the shifted resources are contained within an DL bandwidth part, BWP, and the DL subband, SB.

148. The device of claim 147, wherein the shift is associated with an offset indicated to the device or determined by the device.

149. The device of claim 148, wherein the offset is with respect to: ^ a start frequency resource of the SBFD slot as a starting reference point; filing version an,rmFH241001PEP 2024P67397EP 148 ^ a start frequency resource of the UL-bandwidth part or DL-bandwidth part which is a starting reference point.

150. The device of claim 149, wherein the start frequency resource, e.g., an RB or RBG is or comprises one of: ^ a lowest frequency of the UL SB; ^ a highest frequency of the UL SB; ^ a lowest frequency of the UL BWP; ^ a highest frequency of the UL BWP; ^ a reference point in the frequency domain such as Point A; ^ a highest / lowest frequency of a DL SB; ^ a lowest / highest frequency of the resources allocated in the non-SBFD of in the SBFD slot.

151. The device claims 149 or 150, wherein an identifier of the start frequency resource such as a counter or number is one of: ^ a common resource block number; ^ a physical resource block number; ^ a virtual resource block number.

152. The device of claim 149 to 151, wherein a number of the start frequency resource is based on the available UL frequency resources.

153. The device of one of claims 148 to 152, wherein based on the offset the resources are shifted; and a lowest virtual resource block, VRB, and a highest VRB of the allocated resources in non-SBFD slot correspond to the lowest VRB and highest VRB respectively of the derived resources in SBFD slot; or the lowest VRB and highest VRB of the allocated resources in non-SBFD slot correspond to the highest VRB and lowest VRB respectively of the derived resources in SBFD slot.

154. The device of one of claims 148 to 153, wherein the offset is associated with or provided with a direction, e.g., in the frequency domain and / or time domain.

155. The device of one of claims 148 to 154, wherein the shifted frequency resources correspond to a modulo operation executed on a frequency of the allocated resources shifted by the offset, e.g., based on the determination rules filing version an,rmFH241001PEP 2024P67397EP 149 RBstart_new= RBstart+ offset; or RBstart_new= (RBstart+ offset) mod (N) where mod is a modulus operation and N represents the available UL resources, e.g., overlapping resources of UL BWP with UL SB / UL SB / UL BWP.

156. The device of claim 155, wherein the direction associated with the offset is in the direction of a lower frequency or in a direction of a higher frequency.

157. The device of claim 155 or 156, wherein the direction is explicitly signaled by the gNB, e.g., using a 1-bit indication such as ‘1’ representing towards lower frequency and ‘0’ representing towards higher frequency or vice versa.

158. The device of one of claims 155 to 157, wherein the direction is implicitly determined by the device, e.g., based on the UL SB being towards or closer to the upper frequency limit of the allocated UL resources, then the direction of the offset is determined to be towards that direction or vice versa.

159. The device according to one of claims 148 to 158, wherein the offset is provided, e.g., without a direction, wherein a relation between a start of frequency resources in shifted frequency resources, RBstart_new, and a start of frequency resources in unshifted frequency resources, RBstart, is based on a determination rule RBstart_new= RBstart+ offset; or RBstart_new= (RBstart+ offset) mod (N) where mod is modulus operation and N can be the available UL resources (overlapping resources of UL BWP with UL SB) or UL SB or UL BWP.

160. The device of one of claims 148 to 159, wherein an end reference frequency point of the allocated resources is defined for the offset, such as a RB / RBG with a lowest frequency of the shifted resources in the SBFD slot; or a RB / RBG with a highest frequency of the shifted resources in the SBFD slot; or the lowest / highest frequency of the shifted resources in the non-SBFD / SBFD slot. filing version an,rmFH241001PEP 2024P67397EP 150 161. The device of one of claims 148 to 160, wherein the resource allocation comprises a frequency hopping, FH, shifting a frequency of used resources in subsequent occasions by a FH-offset, wherein a start frequency resource of the resource allocation is provided for a first hop and start frequency resources of subsequent hops within the slot or across slots are derived using a FH-offset, e.g., using a legacy formula.

162. The device of claim 161, wherein the start frequency resource is determined, e.g., signaled to the device or determined by the device based on at least one of: ^ a lowest frequency of the UL SB; ^ a highest frequency of the UL SB; ^ a lowest frequency of the UL BWP; ^ a highest frequency of the UL BWP; ^ a reference point in the frequency domain such as Point A; ^ a highest / lowest frequency of a DL SB; ^ a lowest / highest frequency of the resources allocated in the non-SBFD of in the SBFD slot; and for the subsequent hops, a determination rule such as [RBstart_new= (RBstart+ FH- offset) mod (BWP size) or RBstart_new= (RBstart+ FH-offset)] or a legacy NR FH formula, is used, e.g., by the device, on the determined start frequency resource to determine the start frequency resource of the subsequent hops.

163. The device of claim 161 or 162, wherein the FH-offset is associated with or is provided with a direction, e.g., in the frequency domain.

164. The device of claim 161 to 163, wherein the start frequency resource is determined, e.g., signaled to the device or determined by the device based on at least one of: ^ a lowest frequency of the UL SB; ^ a highest frequency of the UL SB; ^ a lowest frequency of the UL BWP; ^ a highest frequency of the UL BWP; ^ a reference point in the frequency domain such as Point A; ^ a highest / lowest frequency of a DL SB; ^ a lowest / highest frequency of the resources allocated in the non-SBFD of in the SBFD slot; filing version an,rmFH241001PEP 2024P67397EP 151 and for the subsequent hops, a determination rule such as [RBstart_new= (RBstart+ FH- offset) mod (BWP size) or RBstart_new= (RBstart+ FH-offset)], or a legacy NR FH formula, is used, e.g., by the device, on the determined start frequency resource to determine a temporal start frequency resource of the subsequent hops; wherein the device is to further apply an offset to shift the temporal start frequency to obtain a shifted start frequency of the subsequent hop and to operate using the shifted start frequency.

165. The device of claim 164, wherein the FH-offset is associated with or is provided with a direction, e.g., in the frequency domain.

166. The device of one of claims 161 to 165, wherein the start frequency of the subsequent hop is determined based on the determination rule RB ൌ^ ^^ୟ୰^, ^^ ൌ 0 first hop^^ୟ୰^ ^RB ^^௭^^^ୟ୰^ ^ RB୭ ^ mod ^^ , ^^ ൌ 1 second hop ,^^^^^^ ^^^where ^ ^^^^ is the starting RB of the UL resources, ^ ^^^^^௧^^௧is the starting RB of the UL resources as indicated by the gNB, ^ RB୭^^^^^^is the FH-offset. The FH offset can be different for the SBFD and non- SBFD slots, and ^ ^^^^^^௭^^ is the BWP size. BWP size can be replaced with UL SB size or available UL resources in SBFD slots.

167. The device of claim 166, configured to apply a same or different FH-offset for SBFD slots and non-SBFD slots.

168. The device of one of claims 161 to 167, wherein for an inter-slot FH the device is to use a different and optionally independent FH-offset for SBFD slots when compared to a non- SBFD slot for shifting the allocated resources and e.g., a same GH-offset for intra-slot FH.

169. The device of one of claims 161 to 168, wherein the FH offset is determined based on a current slot number; or an occasion number of SBFD / non-SBFD slot.

170. The device of one of claims 161 to 169, wherein the FH offset is determined based the determination rule filing version an,rmFH241001PEP 2024P67397EP 152 ,^^ఓ^ mod 2 ൌ 0mod ^^^^௭^, ^^ఓ, ^^^ ^ mod 2 ൌwhere ^ RB^^ୟ୰^is the starting RB of the UL resources, ^ ൫^^ఓ^൯ is the current slot number, 5 ^ RB^^ୟ୰^is the starting RB of the UL resources as indicated by gNB, ^ RB୭^^^^^^is the FH-offset. FH-offset can be different for SBFD and non-SBFD slots, ^ ^^^^௭^BWP size. BWP size can be replaced with UL SB size or UL resources in SBFD slots, and ^^ఓ10 ^^ mod 2 ൌ 0ఓare the conditions; ^^^ mod 2 ൌ 1Or RB15 where ^ RB^^ୟ୰^is the starting RB of the UL resources, ^ ൫^^ఓ^൯ is the current slot number, ^ RB^^ୟ୰^is the starting RB of the UL resources as indicated by gNB, ^ RB୭^^^^^^is the FH-offset. FH-offset can be different for SBFD and non-SBFD slots, 20 ^ is the BWP size. BWP size can be replaced with UL SB size or available resources in SBFD slots, ^ is the pusch-FrequencyHoppipng-Interval. PUSCH-FreqeuncyHopping- Interval can have different values for SBFD and non-SBFD slots, and ഋ ^^ೞேಷಹ ^mod 2 ൌ 0^ are the 2ൌ 125 171. The device of one of claims 161 to 170, wherein the device is to use a same or different DMRS bundling parameters such as (pusch-FrequencyHoppingInterval, pusch- TimeDomainWindowLength for SBFD and non-SBFD slots. filing version an,rmFH241001PEP 2024P67397EP 153 172. The device of claim 171, wherein a value of the bundling parameter is a minimum of the indicated value of the bundling parameter and the number of consecutive slots of any one type SBFD or non-SBFD.

173. The device of claim 171 or 172, wherein a pusch-FrequencyHopping-Interval is determined based on a minimum value of a number of slots where frequency hopping is applicable, n, and a number of pusch-FrequencyHopping-Interval for SBFD slots, m; or wherein a pusch-FrequencyHopping-Interval is determined based on a minimum value of a number of slots where frequency hopping is applicable, n, and a number of pusch- FrequencyHopping-Interval for non-SBFD slots, m.

174. The device of one of claims 161 to 173, wherein an inter-slot FH is determined based on the determination rule: ఓ RB, ^^^ mod 2 ൌ 0^modwhere ^ RB^^ୟ୰^is the starting RB of the UL resources, ^ ൫^^ఓ^൯ is the current slot number, ^ RB^^ୟ୰^is the starting RB of the UL resources as indicated by gNB, ^ RB୭^^^^^^is the FH-offset. FH-offset can be different for SBFD and non-SBFD slots, ^ ^^^^^^௭^^ is the BWP size. BWP size can be replaced with UL SB size or available UL resources in SBFD slots, and ^ are the conditions.

175. The device of one of claims 161 to 174, wherein an inter-slot FH is determined based on the determination rule:where ^ RB^^ୟ୰^is the starting RB of the UL resources, ^ ൫^^ఓ^൯ is the current slot number, filing version an,rmFH241001PEP 2024P67397EP 154 ^ RB^^ୟ୰^is the starting RB of the UL resources as indicated by gNB, ^ RB୭^^^^^^is the FH-offset. FH-offset can be different for SBFD and non-SBFD slots, ^BWP size. BWP size can be replaced with UL SB size or available UL resources in SBFD slots, ^^^^ ^^ ^^^^^ is the pusch-FrequencyHoppipng-Interval. PUSCH-FreqeuncyHopping- ^^^^Interval can have different values for SBFD and non-SBFD slots, and ഋ ^^ೞேಷಹ ^mod 2 ൌ 0^^ഋ are the conditions. ^ೞேಷಹ ^mod 2 ൌ 1176. The device of one of previous claims, wherein the allocated resources comprise a first start frequency in a non-SBFD occasion and comprise a different second start frequency in a SBFD occasion; wherein a start frequency resource of the allocated resources in a non-SBFD or in a SBFD slot are based on a previous transmission / reception, e.g., irrespective of the SBFD or non-SBFD slot wherein a maximum frequency diversity is achieved in case of inter- slot FH.

177. The device of claim 176, wherein an offset is applied with respect to a start frequency resource of the previous transmission / reception, the offset relating to an offset to a shift of UL resources in a non-SBFD slot with respect to the UL resources in the SBFD slot; or vice versa.

178. The device of one of previous claims, wherein the allocated resources comprise a first start frequency in a non-SBFD occasion and comprise a same start frequency in a SBFD occasion, e.g., the start RB of the initial non-SBFD slot is same as a previous SBFD slot; and wherein frequency hopping, FH is applied to successive non-SBFD slots.

179. The device of claim 178, wherein the start RB comprises a specific distance to the UL SB, e.g., be the closest RB to the UL SB or at maximum distance and it can be within the DL SB or a reference RB outside the DL SB.

180. The device of one of previous claims, wherein the device is to in case of shifted resources of an occasion, e.g., shifted by an offset or a frequency hopping offset, FH-offset, are outside an UL BWP and / or UL SB, the device is to: filing version an,rmFH241001PEP 2024P67397EP 155 ^ ignoring the resources; ^ spread the resources across a domain relating to at least one of a time, a frequency, a spatial domain and a code domain; ^ split the resources across a domain relating to at least one of a time, a frequency, a spatial domain and a code domain; and / or ^ postpone the resources across a domain relating to at least one of a time, a frequency, a spatial domain and a code domain.

181. The device of claim 180, adapted to use additional resources in the frequency domain if available to compensate for the loss of the frequency resources outside the occasion.

182. The device according to one of previous claims, adapted to operate in accordance with a demodulation reference signal, DMRS, bundling effective across multiple slots.

183. The device according to claim 182, adapted to receive and / or transmit signals like repetition of PUSCH, multi-PUSCH, TB processing over multiple slots spread over a plurality of slots comprising at least one SBFD and at least one non-SBFD slot.

184. The device according to claim 183, adapted to implement the DMRS bundling differently for SBFD slots and non-SBFD slots.

185. The device according to claim 183 or 184, adapted to use same DMRS bundling parameters such as pusch-FrequencyHoppingInterval, pusch- TimeDomainWindowLength, for SBFD slots and non-SBFD slots; wherein the DMRS bundling is performed across SBFD and non-SBFD slots.

186. The device according to one of claims 183 to 185, adapted to use different bundling parameters such as pusch-FrequencyHoppingInterval and / or pusch- TimeDomainWindowLength for SBFD and non-SBFD slots.

187. The device according to one of claims 183 to 186, adapted to use a value of a bundling parameter such as pusch-FrequencyHoppingInterval and / or pusch- TimeDomainWindowLength as a minimum from the group of values comprising the bundling parameter indicated by the base station, gNB, and the number of consecutive slots of any one type. filing version an,rmFH241001PEP 2024P67397EP 156 188. The device of one of claims 130 to 187, wherein in a second case relating to an UD or DU scenario with the scheduled resource allocation partially overlapping with an UL SB and / or a guard band, wherein the device is to derive the actual frequency domain resources for SBFD slots as the SBFD time-frequency occasions for reception; wherein the frequency domain resources for SBFD slots as the SBFD time-frequency occasions start from a start , wherein optionally an offset is provided by the gNB; or wherein a size of the resources is kept the same as a size of the frequency domain resources for non-SBFD slots or a new size is provided, wherein the device is adapted to ignore resources outside the DL SB are ignored for reception.

189. The device of claim 188, wherein a start RB comprises a specific distance to the UL SB, e.g., be the closest RB to the UL SB or at maximum distance and it can be within the DL SB or a reference RB outside the DL SB.

190. The device of one of claims 130 to 189, wherein in a third case relating to a DUD scenario with the scheduled SPS occasion as the SBFD time-frequency occasion fully overlapping with an UL SB and / or a guard band, wherein the device is to derive the actual frequency domain resources for SBFD slots as the SBFD time-frequency occasions for reception; wherein frequency domain resources for SBFD slots as the SBFD time-frequency occasions start from a start RB , wherein optionally an offset is provided by the gNB, wherein which DL SB to choose is indicated by the gNB or predefined; or wherein a size of the resources is kept the same as the size of the frequency domain resources for non-SBFD slots, wherein the device is to ignore resources outside the DL SB if the size is such that it goes beyond the DL SB; or wherein the device is to consider a total number of RBs, e.g., a size of the scheduled frequency domain resources, and to spread it equally across the two DL SBs such that an available number of DL resources remains the same, or wherein such a size is optionally provided by the gNB; or wherein the device chooses one of such options that maximizes the number of available DL RBs for SPS reception. filing version an,rmFH241001PEP 2024P67397EP 157 191. The device of claim 190, wherein the start RB comprises a specific distance to the UL SB, e.g., be the closest RB to the UL SB or at maximum distance and it can be within one of the DL SBs or a reference RB outside the DL SB.

192. The device of one of claims 130 to 191, wherein in a fourth case relating to a DUD scenario with the scheduled SPS occasion as the SBFD time-frequency occasion partially overlapping with UL SB and / or a guard band and partially overlapping with both the DL SBs, the device is to derive the frequency domain resources for SBFD slots as the SBFD time-frequency occasions for reception; wherein the frequency domain resources for SBFD slots as the SBFD time-frequency occasions start from the start RB ; wherein optionally an offset is provided by the gNB; or wherein which DL SB to choose is indicated by the gNB or predefined; wherein a size of the resources is kept the same as the size of the frequency domain resources for non-SBFD slots or a new size is provided; wherein if the size is such that it goes beyond the DL SB, then the device is to ignore resources outside the DL SB; or wherein the device is to consider the total number of RBs, e.g., a size of the scheduled frequency domain resources, and to spread it equally across the two DL SBs such that an available number of DL resources remains the same, or wherein such a size is optionally provided by the gNB; or wherein the device chooses one of such options that maximizes the number of available DL RBs for SPS reception.

193. The device of claim 192, wherein the start RB comprises a specific distance to the UL SB, e.g., be the closest RB to the UL SB or at maximum distance and it can be within one of the DL SBs or a reference RB outside the DL SB.

194. The device of one of claims 130 to 193, wherein in a fifth case relating to a DUD scenario with the scheduled SPS occasion as the SBFD time-frequency occasion partially overlapping with UL SB and / or guard band and partially overlapping with only one of the DL SBs, the device is to derive the actual frequency domain resources for SBFD slots to receive SPS; filing version an,rmFH241001PEP 2024P67397EP 158 wherein the frequency domain resources for SBFD slots as the SBFD time-frequency occasions start from the start RB ; wherein optionally an offset is provided by the gNB; wherein which DL SB to choose is be indicated by the gNB or predefined; or wherein the device is to select the DL SB with which an occasion of the resource allocation partially overlaps; or wherein the frequency domain resources for SBFD slots as the SBFD time-frequency occasions start from the start RB of one of the DL SBs which is nearer to the UL SB; wherein optionally an offset is provided by the gNB; wherein which DL SB to choose is indicated by the gNB or predefined; or wherein the device is select the DL SB with which the SPS occasion partially overlaps; or wherein the device is to consider the total number of RBs, e.g., a size of the scheduled frequency domain resources, and to spread it equally across the two DL SBs such that an available number of DL resources remains the same, or wherein such a size is optionally provided by the gNB; or wherein the device chooses one of such options that maximizes the number of available DL RBs for SPS reception.

195. The device of claim 194, wherein the start RB comprises a specific distance to the UL SB, e.g., be the closest RB to the UL SB or at maximum distance and it can be within one of the DL SBs or a reference RB outside the DL SB.

196. The device of one of claims 124 to 195, wherein a TDRA of the resource allocation is kept the same as in case of non-SBFD slots; or wherein a different TDRA is provided; and / or a spreading and / or a splitting of the resources is done over time domain resources.

197. The device of one of claims 123 to 196, wherein a parameter is provided, e.g., in RRC or DCI, by the gNB to indicate whether the device is to derive the frequency domain resources for the SBFD symbols from the frequency domain resources of the non-SBFD symbols. filing version an,rmFH241001PEP 2024P67397EP 159 198. The device of one of claims 123 to 193, wherein the device is adapted to implicitly choose how to derive the resources; or is explicitly indicated by the gNB, which way to derive the resources.

199. The device of one of claims 123 to 198, adapted to derive the frequency domain resources for SBFD symbols based on a device capability; wherein optionally the device is adapted to inform the gNB about the to the capability.

200. The device of claim 199, wherein based on an inability of the device or based on a lack of indication from gNB to derive the resources, the device is adapted to use the same frequency domain resources as scheduled for SBFD symbols and receive with the frequency allocation only in the available DL resources thereof; or follow a different scheme.

201. The device of one of claims 133 to 200, wherein the device is to decode a SPS-Config message with two SPS-Config indices, and to use a first index for SBFD symbols and a second index non-SBFD symbols.

202. The device of claim 201, wherein the device is to decode from the SPS-Config parameters that are common for both SBFD and non-SBFD symbols, like periodicity, and / or parameters separate for both such as like MCS table.

203. The device of claim 201 or 202, wherein the device is to decode two separate DCIs to active the two SPS config indices, wherein optionally the two DCIs comprise different TDRAs and / or FDRAs.

204. The device of one of claims 123 to 203, wherein the device is to perform a VRB-to-PRB mapping across multiple time domain resources to compensate for the fewer available DL resources in SBFD symbols when compared to non- SBFD symbols.

205. The device of one of claims 123 to 204, wherein the device is to be provided with separate MCS with the different frequency domain resources, FDRAs. 206.The device of one of claims 123 to 204, wherein the device is adapted to use a same HARQ process ID for the different frequency domain resources, FDRAs. filing version an,rmFH241001PEP 2024P67397EP 160 207. The device of one of previous claims, adapted to determine that a first time-frequency occasion of the resource allocation, e.g., related to a SPS PDSCH reception occasion, is valid in a first symbol type and invalid in a second symbol type, the first symbol type being one of a SBFD symbol type and a non-SBFD symbol type and the second symbol type being other of the SBFD symbol type and the non-SBFD symbol type.

208. The device of claim 207, wherein the device is provided with the resource allocation, e.g., an SPS-Config, the device is to consider the resource allocation as valid for any one of the symbol types; SBFD or non-SBFD.

209. The device of claim 207 or 208, wherein in a case where the resource allocation is valid only for non-SBFD symbols, the device is adapted to ignore a time-frequency occasion of the resource allocation falling on SBFD slots or SBFD symbols.

210. The device of one of claims 207 to 209, wherein in a case where time-frequency occasions falls across both SBFD and non-SBFD symbols, the device is adapted to ignore that time-frequency occasion; or the device is adapted to treats all the symbols in that time-frequency occasion to be of a particular type, e.g., type SBFD or non-SBFD.

211. The device of claim 210, wherein the device is adapted to be provided with an explicit indication from the gNB whether the resource allocation is valid for SBFD symbols or non-SBFD symbols, e.g., using a parameter.

212. The device of claim 211, wherein the explicit indication is based on a device capability.

213. The device of one of claims 210 to 212, wherein the device is adapted to device determine whether the resource allocation is valid for SBFD symbols or non-SBFD symbols based on an implicit indication and based on certain rules such as whether a first time-frequency occasion of the resource allocation falls on a non-SBFD slot, then the SPS is valid only for subsequent non-SBFD slots.

214. The device of one of claims 210 to 213, wherein the device is adapted to use a same HARQ process ID for the different types of symbols.

215. The device of one of previous claims, wherein the device is a user device, UE, an Internet of Things, IoT, device, a part of an integrated access and backhaul, IAB, node such as filing version an,rmFH241001PEP 2024P67397EP 161 a mobile termination or a distributed unit or a relay device or a vehicle-to-everything, V2X UE or roadside unit .

216. The device of one of previous claims, wherein the SBFD occasion comprises at least one SBFD symbol or an SBFD slot.

217. A base station configured for operating in a wireless communication network and to schedule the scheduled resources as the resource allocation for a device according to one of previous claims, e.g., as semi-persistent scheduling, SPS.

218. The base station of claim 217, adapted for scheduling resources for the device and transmitting a signal using spread resources based on knowledge that the device spreads a reception to extend the scheduled resources and to transmit the signal accordingly.

219. The base station of claim 217 or 218, wherein the base station is adapted to send a signal to the device based on an awareness of conditions under which the device splits the reception of the signal; and to split the transmission of the signal accordingly, e.g., in a time-frequency occasion of the resource allocation.

220. A method for operating a device in a wireless communication network, the method comprising: determining a resource allocation allocating resources of the wireless communication network, e.g., for uplink, UL, and / or downlink, DL, and using the allocated resources based on whether the resource allocation allocates resources in a subband full duplex, SBFD, time-frequency occasion.

221. A method for operating a base station in a wireless communication network, the method comprising: scheduling scheduled resources as a resource allocation for a device according to one of claims 1 to 199, e.g., as semi-persistent scheduling, SPS. filing version an,rmFH241001PEP 2024P67397EP 162 222. A computer readable digital storage medium having stored thereon a computer program having a program code for performing, when running on a computer, a method according to claim 220 or 221. filing version an,rm

Images