Collision handling rules with sbfd

WO2026202237A1PCT designated stage Publication Date: 2026-10-01FRAUNHOFER GESELLSCHAFT ZUR FORDERUNG DER ANGEWANDTEN FORSCHUNG EV
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2026/058731
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-03-27
Filing Date
2026-03-26
Publication Date
2026-10-01

Smart Images

  • Figure EP2026058731_01102026_PF_FP_ABST
    Figure EP2026058731_01102026_PF_FP_ABST
Patent Text Reader

Abstract

At least one of the first symbol and the second symbol is a full duplex, FD, symbol.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] 2025F68137 - 25014 1

[0002] COLLISION HANDLING RULES WITH SBFD

[0003] Description

[0004] Embodiments of the present application relate to the field of wireless communication, and more specifically, to signal processing used for the wireless communication. Some embodiments relate to providing a low physical layer, PHY, flexible radio link.

[0005] Fig. 1 is a schematic representation of an example of a terrestrial wireless network 100 including, as is shown in Fig. 1(a), a core network 102 and one or more radio access networks RANi, 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 gNBi to gNBs, each serving a specific area surrounding the base station schematically represented by respective cells IO61 to IO65. 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 or an advanced BS, aBS, in other mobile communication standards, e.g., 6G or 6G radio, 6GR. A user may be a stationary device or a mobile device. The wireless communication system may also be accessed by mobile or stationary loT devices which connect to a base station or to a user. The mobile devices or the loT 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.

[0006] 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 UE1 and UE2, also referred to as user equipment, UE, that are in cell IO62 and that are served by base station gNB2. Another user UE3 is shown in cell IO64 which is served by base station gNB4. The arrows IO81, IO82 and IO83 schematically represent uplink / downlink connections for transmitting data from a user UE1, UE2 and UE3 to the base stations gNB2, gNB4 or for transmitting data from the base stations gNB2, gNB4 to the users UE1, UE2, UE3.

[0007] Further, Fig. 1(b) shows two loT devices 110i and HO2 in cell IO64, which may be stationary or mobile devices. The loT device 110i accesses the wireless communication system via the base station gNB4 to receive and transmit data as schematically represented by arrow 112i. The loT device HO2 accesses the wireless communication system via the user UE3 as is2025F68137 - 25014 2

[0008] schematically represented by arrow 1122. The respective base station gNBi to gNBs may be connected to the core network 102, e.g., via the S1 interface, via respective backhaul links 114i to 114s, 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 gNBi to gNBs may connected, e.g., via the S1 orX2 interface or the XN interface in NR, with each other via respective backhaul links 116i to 116s, 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 Si that 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 nonterrestrial base station, to communicate with a different satellite.

[0009] 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, PLISCH, 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, PLICCH, PSSCH) carrying for example the downlink control information (DCI), the uplink control information (UCI) and / or 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., 1 ms. 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. Note, when mentioning control signalling in the embodiments, control data can be configured and / or preconfigured. Furthermore, this can be exchanged using higher layer, RRC signalling, RRC lEs, and / or MAC-layer signalling, e.g., MAC-CE, or using physical layer signalling, PHY, e.g., DCI or UCI or SSB or SSS or PSS or MIB or SIB. In addition, under certain conditions, signalling2025F68137 - 25014 3

[0010] can be done in a redundant manner, e.g., using RRC as well as PHY signalling, e.g., signalled via downlink or uplink or sidelink control information, DCI, UCI or SCI. Furthermore, configuration can also be done on a global basis using one type of signalling, e.g., via RRC, and can be re-defined, overwritten or enhanced using the same type of signalling, e.g., the same or other RRC information elements, RRC-IEs. In addition, some configurations may be time-critical, and thus a certain type of signalling is used, e.g., PHY-signalling, while other signalling can be on a more relaxed time scale, e.g., using a higher layer type of configuration, e.g., using RRC signalling or even over-the-top configuration via Internet protocol, IP, packets transmitted via TCP / IP, UDP or QIIIC. In case of signalling restrictions, more details are specified in the individual embodiments.

[0011] 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 (LIFMC), 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 or 6GR standard.

[0012] 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 gNBi to gNBs, and a network of small cell base stations (not shown in Fig. 1), like femto or pico base stations.

[0013] 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.

[0014] 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 with2025F68137 - 25014 4

[0015] 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.

[0016] 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 or mode 1 in NR, mode 3 in LTE. Another scenario is referred to as an “out-of-coverage” scenario or mode 2 in NR, mode 4 in LTE. 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

[0017] 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

[0018] 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

[0019] may be connected to the base station that may not support NR V2X services, e.g., GSM, UMTS, LTE base stations.

[0020] 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.

[0021] 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 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 resource2025F68137 - 25014 5

[0022] 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.

[0023] 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.

[0024] 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.

[0025] With an increase of an amount of communication and with an increase of mobility, stable and reliable communication using transmission reception points, TRP, is an important issue for wireless communication.

[0026] There is, thus, a need to improve wireless communications.

[0027] In general, wireless communication systems may utilized time division duplex, TDD, or frequency division duplex, FDD schemes.

[0028] Time division duplex (TDD) is a method used in wireless communication systems, such as LTE or NR, to allow for bidirectional communication on the same frequency. In TDD systems, the uplink (UL) and downlink (DL) transmissions share the same frequency channel, but they do2025F68137 - 25014 6

[0029] not occur simultaneously. One of the advantages of TDD is its flexibility to dynamically allocate resources between the UL and DL phases based on traffic demands, e.g., using different configurations for number of UL and DL time resources, e.g., having a 50% - 50% UL to DL ratio or having a 70% to 30% DL to UL ratio. This dynamic resource allocation can help optimize the system capacity and throughput, especially in asymmetric traffic scenarios where the UL and DL data rates are different. Note, that neighbouring base stations in TDD are typically synchronized, e.g., using GPS-locked clocks, and TDD configurations, e.g., UL and DL cycles are aligned. This is due to neighbouring interference, adjacent channel interference ratio (ACIR), which mainly results from the high transmit power in the downlink of a base station, which can, if not fully synchronized, interfere with the uplink receiver in a neighbouring base station. This may result in the neighbouring station not being able to receive any uplink data, since the transmit power of associated UEs may be well below the transmit power of a base station.

[0030] Frequency Division Duplex (FDD) is a method used in wireless communication systems, such as 5G New Radio (NR), to enable simultaneous bidirectional communication by using separate frequency bands for the uplink (UL) and downlink (DL) transmissions. In FDD systems, different frequency bands are allocated for UL and DL communication, allowing for concurrent or full-duplex transmission and reception. Note, there may be also device categories with limited or reduced processing or hardware capabilities, e.g., RedCap device, which may only support half-duplex FDD processing. This implies that these devices can either process the UL or the DL carrier in a FDD system. Thus, these devices need to switch between processing of UL or DL, which requires a switching time for adapting the analogue components within the device. The switching time may be dependent on the device capability or device category. Some device, e.g., loT devices, may not be able to switch at all, and may only transmit or receive data in the particular link direction, e.g., sensor nodes used in sensing systems such as integrated communication and sensing, ICAS, nodes.

[0031] One of the advantages of FDD in NR is its ability to provide constant and consistent UL and DL data rates, as there is no need to switch between UL and DL modes like in Time Division Duplex (TDD) systems for certain devices. FDD is well-suited for applications where symmetric data rates are required in the UL and DL.

[0032] In FDD or TDD, symbol type can be downlink, DL or D, uplink, UL or U, or sidelink, SL or S. Furthermore, it can be marked as flexible symbol, F. Flexible symbols can be either used as D or U or S, and throughout this application, a flexible symbol F can be used interchangeable with D or U or S. Although in most embodiments uplink or downlink is mentioned, either can2025F68137 - 25014 7

[0033] also be exchanged for a sidelink communication, which involves direct communication between devices without having to relay data via a base station.

[0034] The inventors found that communication may be improved by use of carrier aggregation in connection with full duplex, FD, such as subband full duplex, SBFD. Note, that in case it is referred to a full duplex, FD, symbol, this can be used also as subband full duplex, SBFD, symbol, interchangeably.

[0035] 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.

[0036] Embodiments of the present invention are described herein making reference to the appended drawings.

[0037] Fig. 1 shows a schematic representation of an example of a wireless communication system;

[0038] Fig. 2 is a schematic representation of a wireless communication system comprising a transceiver, like a base station ora relay, and a plurality of communication devices, like UEs, according to an embodiment;

[0039] Fig. 3a-c show schematic representations of different types of carrier aggregation, CA underlying embodiments described herein;

[0040] Fig. 4a-c show schematic representations of aggregated carriers with regards to subband full duplex symbols in the carriers, according to embodiments;

[0041] Fig. 5 is a schematic representation of aggregated carriers experiencing the effect of unwanted emissions, according to embodiments;

[0042] Fig. 6 is a schematic representation of carriers of different duplex schemes that are aggregated according to embodiments;

[0043] Fig. 7 is a schematic representation of aggregated carriers to enable continuous uplink transmission and a downlink boost according to embodiments;2025F68137 - 25014 8

[0044] Fig. 8a-b show schematic representations of aggregated carriers enabling uplink slot skipping and shifted uplink transmission according to embodiments;

[0045] Fig. 9a-b show schematic representations of aggregated carriers having shifted slot structures when compared to each other and according to embodiments;

[0046] Fig. 10a-b show schematic representations of aggregated carriers having gaps within the provided resources according to embodiments; and

[0047] Fig. 11 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.

[0048] 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.

[0049] 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.

[0050] 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.

[0051] Fig. 2 is a schematic representation of a wireless communication system comprising a transceiver 200, like a basestation or a relay, and a plurality of communication devices 202i to 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 more2025F68137 - 25014 9

[0052] antennas ANT or an antenna array having a plurality of antennas, a processor 202ai to 202an, and a transceiver (e.g., receiver and / or transmitter) unit 202bi to 202bn. The basestation 200 and / or the one or more UEs 202 may operate in accordance with the inventive teachings described herein.

[0053] In niche or longtail applications — for example, Industrial loT (HoT) — that have specific requirements for Ultra Reliable and Low Latency Communication (URLLC) in combination with low-, medium- or high-data rates, the DSP design space requirements easily exceed those of a unified standard set of parameters. A standardized mechanism is thus need to embed domain and application specific DSP requirements for longtail application. To facilitate a DSP alternative on a wireless link between at least two nodes, the transmitter and receiver pair have to be provided with means to be DSP configurable on-demand. This includes without limitation the download of DSP modules and / or code together with their installation, configuration, activation, synchronization and the open-loop or closed-loop control of such DSP modules. These software modules have to be embedded on low PHY or mid PHY in order to provide the required wireless link enhancements needed for longtail applications. Furthermore, the facilitating scheme proposed by the inventors should allow to embed and use DSP modules which fit into the given standardized and regulatory framework, while being in detail implementation specific and therefore quasi proprietary.

[0054] In the context of wireless communications, the core network may refer to the central part of a telecommunications network that provides essential services and manages communication traffic. It facilitates connectivity between various elements of the network, including user devices and external networks. In the context of mobile telecommunications, the core network is a crucial component that handles tasks such as call routing, data transfer, and subscriber management. The core network itself may have connection to other parts of the network or different networks, e.g., accessing the internet, such a link may possibly suffer from failures or unavailability. For a device, a similar situation may occur, at least in connection with embodiments, when a connection from a serving base station to the core network becomes unavailable or when the core network loses such higher-level connection.

[0055] 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.

[0056] Embodiments of the present invention relate to resources. In connection with embodiments, a resource may comprise one or more of the following:2025F68137 - 25014 10

[0057] • A number of subcarriers in frequency domain, a number of symbols, e.g., OFDM symbols in time domain, possibly organized in slots (e.g., 14 OFDM symbols and 12 subcarriers), sub-slots, mini-slots, frames, radioframes, half-frames, hyperframes, • a resource element, RE,

[0058] • a resource block or physical resource block, PRB, or common resource block, CRB, or virtual resource block, VRB,

[0059] • resource block groups, RBG,

[0060] • spatial resources, e.g., precoded or beamformed resources and / or selection of different base stations, BS, or transmission reception point, TRP, or multi TRP, mTRP, consisting of more than one TRP connected to the same or different BSs. Note, a beam may be formed in case antenna elements are grouped, and signals are radiated by using such antenna elements, as in utilized a MIMO or massive MIMO, mMIMO antenna,

[0061] • a code resource, e.g., CDMA resource or using cover codes, e.g., orthogonal cover codes, OCC.

[0062] As a frequency resource embodiments may relate to one or more of:

[0063] • a bandwidth part, BWP,

[0064] • a carrier, e.g., a component carrier,

[0065] • a carrier aggregation, CA, e.g., contiguous or non-contiguous carriers within FR1 and / or FR2 and / or FR3, supplemental carried, e.g., supplemental uplink and / or downlink, SUL or SDL,

[0066] • a subband,

[0067] • a sub channel,

[0068] • a subcarrier,

[0069] a subband or sub channel containing a number of subcarriers with a subcarrier spacing (SCS) depending on the numerology, e.g., 15 kHz or 30 kHz SCS or higher SCS, e.g., for FR2 or FR3.

[0070] Embodiments described herein relate to Carrier Aggregation, CA.

[0071] 1.1 Carrier Aggregation Types

[0072] Carrier aggregation (CA) in NR are basically of 3 types as shown in Fig 3a-c.2025F68137 - 25014 11

[0073] In Fig. 3a the figure above in a, the 2 carriers, carrier 302i and carrier 3022 are within the same band A and are contiguous. Hence, this is called intra-band contiguous CA. In Fig. 3b, the carriers 302i and 3022 are non-contiguous but in the same band, band A. Hence, it is called intra-band non-contiguous. In Fig. 3c, the carriers 302i and 3022 are in different bands, e.gh., carrier 302i is in band A and carrier 3022 is in band B, hence such a situation is called interband CA.

[0074] Further, the carriers can be LIL / DL FDD carriers or TDD carriers. In NR, there is a primary cell (PCell) to which the UE is connected, and multiple carriers can be aggregated as secondary cells (SCells) which can serve the UE. The cell specific and UE specific configurations for each SCell can be dedicatedly provided to the UE. E.g., the TDD configurations like tdd-UL-DL-ConfigurationDedicated for each SCell is provided in the ServingCellConfig in RRC. Further, every serving cell has a cell index to identify it.

[0075] The UE has capabilities with respect to supporting CA defined in CA-ParametersNR. For example, parameters like simultaneousRxTxInterBandCA, half-DuplexTDD-CA-SameSCS-r16 etc. are defined. If simultaneousRxTxInterBandCA is supported, then the UE can transmit and receive at the same time in different cells in different bands.

[0076] Further, a set of serving cells can be provided with directionalCollisionHandling-r16 = 'enabled'. In such a case, certain rules on UE behavior are defined in the specification for transmissions and receptions across these cells. An example is given in the following.

[0077] Section 11.1 in TS38.213 V18.5.0 (2024-12)defines

[0078] If a UE

[0079] is configured with multiple serving cells and is provided with directionalCollisionHandling-r16 = 'enabled' for a set of serving cell(s) among the configured multiple serving cells, and

[0080] indicates support of half-DuplexTDD-CA-SameSCS-r16 capability, and

[0081] is not configured to monitor PDCCH for detection of DCI format 2_0 on any of the multiple serving cells,

[0082] the UE determines a reference cell for a symbol as an active cell with the smallest cell index among2025F68137 - 25014 12

[0083] - the configured multiple serving cells if the UE is not capable of simultaneous transmission and reception as indicated by simultaneousRxTxInterBandCA among the multiple serving cells, and

[0084] - the cells of each band respectively if the UE is capable of simultaneous transmission and reception by simultaneousRxTxInterBandCA for the configured multiple serving cells.

[0085] Where the symbol is configured as

[0086] downlink, or uplink, as indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL- ConfigurationDedicated

[0087] uplink, if the symbol is flexible and the UE is configured to transmit SRS, PUCCH, PUSCH, or PRACH on the symbol

[0088] downlink, if the symbol is flexible and the UE is configured to receive PDCCH, PDSCH or CSI-RS on the symbol.

[0089] With regards to embodiments described herein, let this symbol of the reference cell be called reference symbol.

[0090] The existing rules for collision handling rules according to 3GPP TS38.213 V18.5.0 (2024-12), section 11.1 in a CA scenario are defied as:

[0091] If another cell among the cells configured with directionalCollisionHandling-r16 operates in the same frequency band as the reference cell, the UE does not expect

[0092] - a symbol to be indicated as downlink or uplink on the reference cell and as uplink or downlink on another cell, respectively, by tdd-UL-DL-ConfigurationCommon or by tdd- UL-DL-ConfigurationDedicated,

[0093] - tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated to indicate a symbol as downlink on the reference cell and to detect a DCI format scheduling a transmission on the symbol on another cell, and

[0094] - to be configured by higher layers to receive PDCCH, PDSCH, or CSI-RS on a flexible symbol on the reference cell and to detect a DCI format scheduling a transmission on the symbol on another cell.

[0095] If the reference cell and another cell among the cells configured with directionalCollisionHandling-r16 operate in different frequency bands, the UE2025F68137 - 25014 13

[0096] assumes symbol as flexible, is not required to receive higher layer configured PDCCH, PDSCH, or CSI-RS and not expected to transmit higher layer configured SRS, PLICCH, PLISCH, or PRACH, when tdd-UL-DLConfigurationCommon or tdd-UL-DL- ConfigurationDedicated indicates symbol as downlink or uplink on another cell and as uplink or downlink for the reference cell, respectively,

[0097] - transmits a signal / channel scheduled by a DCI format on a symbol of another cell when the symbol is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL- DL-ConfigurationDedicated for the reference cell,

[0098] is not required to receive a higher layer configured PDCCH, PDSCH, or CSI-RS on flexible symbols on the reference cell in a set of symbols, if the UE detects a DCI format scheduling a transmission on one or more symbols in the set of symbols on another cell.

[0099] Regardless of whether the reference cell and another cell operate in same or different frequency bands, the UE

[0100] does not expect tdd-UL-DL-ConfigurationCommon or tdd-UL-DL- ConfigurationDedicated for the reference cell to indicate a symbol as uplink and to detect a DCI format scheduling a reception on the symbol on another cell

[0101] does not expect to be configured by higher layers to transmit SRS, PUCCH, PUSCH, or PRACH on a flexible symbol on the reference cell and to detect a DCI format scheduling a reception on the symbol on another cell

[0102] does not transmit a PUCCH, PUSCH or PRACH that is configured by higher layers on a set of symbols on another cell if at least one symbol from the set of symbols is indicated as downlink by tdd-UL-DLConfigurationCommon or tdd-UL-DL- ConfigurationDedicated or is a symbol corresponding to a PDCCH, PDSCH, or CSI- RS reception that is configured by higher layers on the reference cell

[0103] does not transmit a SRS that is configured by higher layers on a set of symbols on another cell if the set of symbols is indicated as downlink by tdd-UL-DL- ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or corresponds to a PDCCH, PDSCH or CSI-RS reception that is configured by higher layers on the reference cell

[0104] does not receive a PDCCH, PDSCH or CSI-RS that is configured by higher layers on a set of symbols on another cell if at least one symbol from the set of symbols is indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL- ConfigurationDedicated or is a symbol corresponding to a SRS, PUCCH, PUSCH, or PRACH transmission that is configured by higher layers on the reference cell2025F68137 - 25014 14

[0105] assumes a symbol indicated as downlink or uplink by tdd-UL-DL- ConfigurationCommon or tdd-UL-DLConfigurationDedicated on another cell to be flexible, if the UE is respectively configured by higher layers to transmit SRS, PLICCH, PLISCH, or PRACH or to receive PDCCH, PDSCH, or CSI-RS on the reference cell does not expect to detect a first DCI format scheduling a transmission or reception on a symbol on a first cell and a second DCI format scheduling a reception or transmission on the symbol on a second cell, respectively.

[0106] After the UE applies the procedures described above for directional collision handling within the set of cells that have been configured with directionalCollisionHandling-r16, the UE does not expect any directional collision among the serving cells that the UE is not capable of simultaneous transmission and reception.

[0107] With said content of TS 38.213 as a background, amended in view of the symbol of the reference cell to be called reference symbol it is noted that in accordance with embodiments, component carriers used in carrier aggregation can be active or inactive. Furthermore, one of the carriers can be distinctive, from the other carriers, e.g., and can be used as a base carrier or reference carrier. Note, this may be signalled from the base station. Furthermore, a reference carrier may be also a reference cell. This may be the carrier that is used for the initial setup of carrier aggregation or as carrier used for receiving the timing reference and / or for calculating the carrier frequency offset, CFO. Furthermore, the reference carrier may be used when a UE experiences a radio link failure, RLF, so that the UE can use this carrier as a fallback carrier for performing random access, e.g., PRACH, or for performing a RACH-less reconnection to a base station, BS. Furthermore, a certain reference carrier may be used for performing blind decodes, in order to reduce power consumption, e.g., by limiting blind decoding by performing blind decoding only on a restricted or limited bandwidth.

[0108] Possible carrier aggregation scenarios with a reference cell and another cell in the context of SBFD are depicted below. Note, that CA may also involve more than one another cell, e.g., 4 another cells, e.g., in case 5 carriers are aggregated. Furthermore, the SBFD symbol within the reference cell or another cell may be in different layouts and in accordance with embodiments, the SBFD symbol may be configured having one of the following subband combinations:

[0109] Downlink- uplink, e.g. DU,

[0110] Uplink - Downlink, e.g., UD,

[0111] Downlink - Uplink - Downlink, e.g., DUD,2025F68137 - 25014 15

[0112] Uplink - Downlink - Uplink, e.g., UDU.

[0113] Optionally, D and U or U and D, regardless whether further parts are contained, may be separated by a guard band and the following acronyms may be used throughout within the present disclosure: D = downlink = DL, and U = uplink = UL.

[0114] In addition or as an alternative, a D and / or a U may be exchanged with a flexible symbol, e.g., F, which may be used as either downlink or uplink transmission, depending on a criterion. In this case, the configuration of the symbol or SBFD symbol may be DF, FD, UF, FU, DFD, FDF, UFU, FUF, etc. That is at least a fourth part may be added. That is, this may also be not limited to 2 or 3 subbands, but may also have additional subband, e.g., in case the carrier is wideband, e.g., 400 MHz, there may be a configuration like DFDFD etc. It is noted that although carrier aggregation in Fig. 4a-c is depicted as having TDD configured for both reference cell providing TDD carrier 312i and the another cell providing TDD carrier 3122, embodiments defined in this invention are not limited this scenario. Thus, the carrier depicted as reference cell or the another cell can also be configured as a DL or UL carrier, which is associated with a corresponding UL or DL carrier as in FDD; or alternatively, it can be configured as a supplemental DL, SDL, or supplemental UL, SUL, carrier. As shown in Fig. 4a, according to embodiments, symbols 314u, i= 1 ,... ,5 as a non-limiting example in TDD carrier 312i may be of type UL as shown for 314i,i„ 314i ,3 and 314i,s or may be of type SBFD, e.g., having one or more DL sections and one or more UL sections as shown for symbol 314i ,2 and 314i ,4, wherein the symbols 3142, j with j=1, ...5, being of type DL or UL.

[0115] According to Fig. 4b, the carrier 3122 of the another cell is operated to comprise SBFD symbols 3142,2 and 3142,4 whilst carrier 312i is operated with UL and DL symbols, possibly without SBFD symbols.

[0116] Fig. 4c shows a mixture of Fig. 4a and Fig. 4b where both carriers 312i and 3122 are operated to comprise SBFD symbols 314I,2 and 314I,4 besides UL symbols 314i,i, 314I,3 and 314i,s, SBFD symbols 3142,2 and 3142,4 besides UL symbols 3142, 1, 3142,3 and 3142,5, respectively.

[0117] In other words Fig. 4a-c show example definitions of a reference cell and another cell in the context of SBFD according to embodiments.

[0118] 1.2 Subband Full Duplex2025F68137 - 25014 16

[0119] For UL transmissions and DL receptions across SBFD symbols and non-SBFD symbols in different slots, each transmission / reception within a slot may in known systems, e.g., NR, be either all SBFD or all non-SBFD symbols, for an SBFD aware UE, the SBFD-aware UE is provided with one of the configurations:

[0120] ■ Configuration 1: The transmissions / receptions are restricted to SBFD symbols only or non-SBFD symbols only,

[0121] ■ Configuration 2: The transmissions / receptions can be in SBFD symbols and non- SBFD symbols.

[0122] In NR, various collision handling rules are defined for the UE. A collision means when there is a conflict between what the UE has been instructed to do in a symbol by the gNB. For example, the UE cannot be indicated as downlink by TDD common configuration in a symbol and also configured (semi-statically or dynamically) to transmit in uplink. Semi-static signalling mostly refers to signalling using RRC or MAC CE while dynamic signalling is using lower layer or Physical layer signalling like DCI. Another example is how the UE behaves when a symbol is semi-statically configured with some uplink transmission like periodic SRS and also dynamically triggered to transmit PUSCH. Such collisions among different / same link directions with semi-static / dynamic signalling can occur at the UE and rules need to be defined so that the UE knows what to do in such a situation. These are known as the collision handling rules. Also, the rules are defined based upon the UE capabilities as well. The collision handling rules are defined for various scenarios like TDD / FDD carriers, aggregated carriers, carrier with SBFD configuration etc.

[0123] 1.3 Co-existence

[0124] Sufficient frequency separation between component carriers needs to be configured, such that cross-carrier interference is minimized or avoided. This can be caused by power leakage from one carrier to another, e.g., from an adjacent radio channel, or by spurious emission, e.g., caused by harmonics, resulting from non-linearities in the transmitters, e.g., amplifiers or filters, of the radio systems. Typically, the out-of-band emissions requirement for the BS or UE transmitter is specified both in terms of Adjacent Channel Leakage Power Ratio (ACLR) and operating band unwanted emissions (OBUE). The ACLR is the ratio of the filtered mean power centered on the assigned channel frequency to the filtered mean power centered on an adjacent channel frequency. Note, that the ACLR may also be measured as cumulative ACLR (CACLR). The ACLR may depend on one or more of a center frequency, the channel bandwidth, the center frequency of the adjacent channel and the filter or filter bandwidth used on the adjacent channel. Furthermore, the adjacent channel interference ratio, ACIR may be2025F68137 - 25014 17

[0125] derived from this. The ACIR is typically specified in terms of a fixed value, e.g., 43 dBm for BS-to-BS interference, dependent on the power class of a particular device, e.g., BS or UE, and may be according to the following table:

[0126]

[0127] An example of unwanted emission from a carrier 326i to an adjacent carrier 3262 is shown in Fig. 5. Transmit power and filters have to be adopted such that unwanted emissions 322 are below a well-defined interference ratio or interference threshold 324. This is especially important in case of an uplink subband / band or in case SBFD with uplink subband is configured on the adjacent carrier 3262 being adjacent to carrier 326i. As shown in Fig. 5, the resulting interference in the adjacent subband must be below this interference threshold, such that the neighbouring base station is able to receive data in the uplink. In case this interference threshold is violated, the automatic gain control, AGC, of the BS receiver may run into saturation, such that UL signals cannot be decoded. Note that the carrier 326i and adjacent carrier 3262 can belong to the same or also to different operators. Furthermore, these might also support different transmit power, or these carriers might also be operated by different base station types, e.g., the carrier is a Macro gNB, while the adjacent carrier is a small cell, e.g., micro or low power base station.

[0128] 2. Problem statement

[0129] In the known specification, CA is allowed among FDD and / or TDD carriers which can have symbols that are uplink, downlink or flexible. A flexible symbol means that the symbol can be configured as downlink or as uplink. However, a gNB can be capable of subband full duplexing (SBFD). With SBFD, the gNB can transmit and receive in different subbands at the same time. The subbands are configured to the UE. An SBFD symbol is a symbol which has these subbands. E.g., a symbol has an uplink subband and a downlink subband: DU / UD configuration or an uplink subband between 2 downlink subbands; DUD configuration. A non-SBFD symbol is a symbol which is fully uplink or downlink. Since a carrier can be configured with SBFD, at least one carrier among the carriers aggregated for CA can have a SBFD2025F68137 - 25014 18

[0130] configuration. Note, also more than one carrier in a CA scenario can be configured with SBFD, in order to increase scheduling flexibility in the system, in case of heavy usage of SBFD symbols. In such a case, a symbol can now be SBFD or non-SBFD symbol apart from just being downlink or uplink where the SBFD symbol has both uplink and downlink resources. Hence, the existing rules on UE behavior that are defined in the specification for transmissions and receptions across these cells will be impacted.

[0131] 3. Technical solutions

[0132] With regards to the invention described herein, embodiments provide for devices and radio devices.

[0133] A device according to embodiments may be implemented as a user equipment or a different device and may be configured for operating in a wireless communications network comprising a plurality of cells. The device is configured for carrier aggregation comprising aggregating at least a first part of a first symbol of a first carrier of the wireless communication network and at least a second part of a second symbol of a second carrier of the wireless communication network, wherein at least one of the first symbol and the second symbol is a full duplex, FD, symbol. Aggregating carriers providing SBFD symbols allows for a high flexibility in using resources.

[0134] Aspects of the device relate and of devices communicating therewith are described in the following:

[0135] 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.

[0136] A first aspect relates to a device such as a user equipment configured for operating in a wireless communications network comprising a plurality of cells, wherein the device is configured for carrier aggregation comprising aggregating at least a first part of a first symbol of a first carrier of the wireless communication network and at least a second part of a second symbol of a second carrier of the wireless communication network, wherein at least one of the first symbol and the second symbol is a full duplex, FD, symbol.2025F68137 - 25014 19

[0137] According to a second aspect when referring back to the first aspect, the device is adapted for the carrier aggregation to comprise exactly one carrier as a full duplex carrier that comprises FD symbols comprising the FD symbol.

[0138] According to a third aspect when referring back to the first aspect, the device is adapted for the carrier aggregation to comprise exactly one carrier to comprise a band or subband associated with full duplex, e.g., a subband full duplex subband.

[0139] According to a fourth aspect when referring back to the first aspect, a full duplex, FD, symbol has frequency resources in uplink direction, II, and downlink direction, D, in the same time resource(s), that are one of:

[0140] full-overlapping,

[0141] partial overlapping,

[0142] non-overlapping, e.g., an SBFD symbol having uplink and downlink subbands.

[0143] According to a fifth aspect when referring back to any of the first to fourth aspects, the FD symbol comprises frequency resources in uplink direction and frequency resources in downlink direction and optionally flexible frequency resources.

[0144] According to a sixth aspect when referring back to any of the first to fifth aspects, the device is adapted to operate according to a full-duplex configuration received from a base station.

[0145] According to a seventh aspect when referring back to any of the first to sixth aspects, the device is adapted to use the first part and the second part simultaneously or subsequently.

[0146] According to an eighth aspect when referring back to any of the first to seventh aspects, the first carrier and the second carrier implement the same duplexing scheme.

[0147] According to a ninth aspect when referring back to any of the first to eighth aspects, the device is to aggregate at least the first part, the second part and at least a third part of a third symbol of a third carrier of the wireless communication network, e.g., a third symbol, e.g., to aggregate more than two carriers.

[0148] According to a tenth aspect when referring back to any of the first to ninth aspects, the device is adapted to operate on the first carrier and the second carrier as synchronized carriers.2025F68137 - 25014 20

[0149] According to an eleventh aspect when referring back to any of the first to tenth aspects, the device is adapted to use uplink resources of the first part for an uplink and for using downlink resources of the second part for downlink.

[0150] According to a twelfth aspect when referring back to any of the first to eleventh aspects, the device is adapted to use uplink resources of the first part for an uplink and for using uplink resources of the second part for uplink.

[0151] According to a thirteenth aspect when referring back the twelfth aspect, the device is adapted to implement a continuous uplink transmission in time domain by subsequently using the first part and the second part.

[0152] According to a fourteenth aspect when referring back to any of the first to thirteenth aspects, the device is adapted to use downlink resources of the first part for a downlink and for using downlink resources of the second part for downlink.

[0153] According to a fifteenth aspect when referring back to the fourteenth aspect, the device is adapted to implement a downlink boost in terms of downlink resources by simultaneously using the first part and the second part.

[0154] According to a sixteenth aspect when referring back to any of the first to fifteenth aspects, the device is adapted to operate on the first carrier and the second carrier comprising a frequency separation therebetween to mitigate cross-carrier interference.

[0155] According to a seventeenth aspect when referring back to the sixteenth aspect, the device is adapted to operate in accordance with an adjacent channel interference ratio, ACIR.

[0156] According to an eighteenth aspect when referring back to the sixteenth or seventeenth aspect, the device is adapted to adopt at least one of a transmit power and / or at least one filter to maintain interfering emissions below a defined interference ratio.

[0157] According to a nineteenth aspect when referring back to any of the first to eighteenth aspects, the device is adapted to operate on the first carrier and the second carrier as being operated by the same or different operators.2025F68137 - 25014 21

[0158] According to a twentieth aspect when referring back to any of the first to nineteenth aspects, the device is adapted to operate on the first carrier and the second carrier as being operated by the same or different base station types.

[0159] According to a twenty-first aspect when referring back to the twentieth aspect, a base station type is a radio device for communicating with one or more user devices, UEs, of a wireless communication system, the UEs when referring back to any one or more of the first to twentieth aspects wherein the radio device is to communicate with the one or more UEs using a radio signal comprising a plurality of time blocks in a time domain, and frequency block in a frequency domain; optionally being one or more of the following: a base station, BS, a macro cell base station, or a small cell base station, or a central unit, CU, of a base station, or a distributed unit, DU, of a base station, or an Integrated Access and Backhaul, IAB, node, or a road side unit, RSU, or a WiFi access point, AP, or a UE, or a sidelink, SL, UE, or a group leader UE, GL-UE, ora relay ora remote radio head, or an AMF, or an SMF, ora core network, CN, entity, or mobile edge computing, MEC, entity, or a network slice as in the NR or 5G core context, or any transmission and reception point, TRP, one of a TRP as in multi-TRP, mTRP, enabling an item or a device to communicate using the wireless communication network, the item or device being provided with network connectivity to communicate using the wireless communication network, or a non-terrestrial device, e.g., a moving or stationary air-borne device, like a drone, an unmanned aerial vehicle, UAV, or an airplane, or a moving or stationary space-borne device, like a low earth orbit, LEO, satellite, like a LEO-600 satellite or a LEO-1200 satellite, a medium earth orbit, MEO, satellite, or a geosynchronous earth orbit, GEO, satellite; or one or more of

[0160] - a macro base station,

[0161] - a micro base station,

[0162] - a small-cell base station,

[0163] - a non terrestrial network, NTN, base station,

[0164] - an integrated access and backhaul, lAB-node, a distributed unit, DU, or central unit, CU.

[0165] According to a twenty-second aspect when referring back to any of the first to twenty-first aspects, the device is adapted for using the first carrier as a time division duplex, TDD, carrier and for using the second carrier as a TDD carrier.

[0166] According to a twenty-third aspect when referring back to any of the first to twenty-second aspects, the device is adapted for using the first carrier as a time division duplex, TDD, carrier and for using the second carrier as a frequency division duplex FDD carrier.2025F68137 - 25014 22

[0167] According to a twenty-fourth aspect when referring back to any of the first to twenty-third aspects, the device is adapted for using the first carrier as a time division duplex, TDD, carrier and for using the second carrier as a supplemental uplink carrier, SUL, carrier.

[0168] According to a twenty-fifth aspect when referring back to any of the first to twenty-fourth aspects, the device is adapted for using the first carrier as a time division duplex, TDD, carrier and for using the second carrier as a supplemental downlink carrier, SDL, carrier.

[0169] According to a twenty-sixth aspect when referring back to any of the first to twenty-fifth aspects, the device is adapted for using the first carrier as a frequency division duplex, FDD, carrier and for using the second carrier as an FDD carrier.

[0170] According to a twenty-seventh aspect when referring back to any of the first to twenty-sixth aspects, the device is adapted for using the second part as an uplink part during a downlink cycle of the first carrier.

[0171] According to a twenty-eighth aspect when referring back to any of the first to twenty-seventh aspects, using a first carrier and one or more second carriers form a base carrier, e.g., the base carrier being formed as a combination comprising at least one of a) TDD / TDD, b) TDD / FDD, c) FDD / TDD and d) FDD / FDD.

[0172] According to a twenty-ninth aspect when referring back to any of the first to twenty-eighth aspects, the device is adapted for using the first carrier as a frequency division duplex, FDD, carrier and for using the second carrier as supplemental uplink carrier, SUL, carrier.

[0173] According to a thirtieth aspect when referring back to any of the first to twenty-ninth aspects, the device is adapted for using the second part as an uplink part paired with a downlink band of the first carrier.

[0174] According to a thirty-first aspect when referring back to any of the first to thirtieth aspects, the device is adapted to use the first carrier (FDD) to form a base carrier and to use the second carrier to perform a boost in the UL direction.

[0175] According to a thirty-second aspect when referring back to any of the first to thirty-first aspects, the device is adapted for using the first carrier as a frequency division duplex, FDD, carrier and for using the second carrier as an supplementary downlink, SDL, carrier.2025F68137 - 25014 23

[0176] According to a thirty-third aspect when referring back to any of the first to thirty-second aspects, the device is adapted for using the second part as a downlink part paired with an uplink band of the first carrier.

[0177] According to a thirty-fourth aspect when referring back to any of the first to thirty-third aspects, the device is adapted to use the first carrier (FDD) to form a base carrier and to use the second carrier to perform a boost in the DL direction.

[0178] According to a thirty-fifth aspect when referring back to any of the first to thirty-fourth aspects, the device is adapted to access the first carrier as being operated in a first cell of the wireless communication network and to access the second carrier as being operated in a second cell of the wireless communication network.

[0179] According to a thirty-sixth aspect when referring back to the thirty-fifth aspect, the device is adapted to simultaneously connect to the first cell and the second cell.

[0180] According to a thirty-seventh aspect when referring back to any of the first to thirty-sixth aspects, the device is adapted to receive and process signalling received with the first carrier, the signalling indicating a use of the second part.

[0181] According to a thirty-eighth aspect when referring back to the thirty-seventh aspects, the device is adapted to receive the signalling as a configuration or pre-configuration.

[0182] According to a thirty-ninth aspect when referring back to the thirty-seventh or thirty-eighth aspect, the device is adapted to receive the signalling via a physical layer, PHY, a medium access control control element, MAC-CE, a radio resource control, RRC, or a higher-layer configuration.

[0183] According to a fortieth aspect when referring back to any of the thirty-seventh to thirty-ninth aspects, the device is adapted to implement the carrier aggregation based on the signalling as a semi-persistent configuration or a semi-persistent scheduling, SPS or a configured grant, CG, configuration.

[0184] According to a forty-first aspect when referring back to any of the thirty-seventh to fortieth aspects, the device is adapted to process the signalling based on a basic configuration or2025F68137 - 25014 24

[0185] global basis, e.g., RRC, as a first level of signalling and for processing a second level of signalling, e.g., via RRC or PHY, wherein the device is adapted to

[0186] - skip or drop [i.e. , to again use other scheduled slots] at least one transmission and / or reception within an FD slot of an aggregated carrier, e.g., the secondary carrier(s),

[0187] - skip or drop all transmissions and / or receptions within the aggregated carrier, e.g., the secondary carrier(s), and / or base carrier and / or primary carrier, - change the link direction within the aggregated carrier and / or base carrier and / or primary carrier, e.g., in case the link direction within the SBFD-slot of a aggregated carrier is supposed to be used for uplink, II, the device uses the downlink, D, link direction within the same carrier, or vice versa, - transmit and / or receive only on the primary carrier and / or the secondary carrier(s),

[0188] - transmit and / or receive only on the aggregated carrier, e.g., the secondary carrier(s), e.g., without transmitting in the primary carrier,

[0189] - switch carriers.

[0190] According to a forty-second aspect when referring back to the forty-first aspect, a carrier switch is configured by one or more of the following

[0191] - a secondary carrier is configured as the primary carrier,

[0192] - the primary carrier is configured as a secondary carrier,

[0193] - carrier aggregation is stopped, e.g., fallback to the primary carrier, - the primary carrier can be removed from the aggregated carriers, e.g., device is reconfigured with one of the secondary carriers as primary carrier.

[0194] According to a forty-third aspect when referring back to the forty-first or forty-second aspect, the device is adapted for a power saving mode during a time there the skipped transmission is scheduled.

[0195] According to a forty-fourth aspect when referring back to any of the thirty-seventh to forty-third aspects, the device is adapted to process the signalling based on a previous, e.g., last received control signalling, e.g., based on a type of a symbol used for transmitting the control signal.

[0196] According to a forty-fifth aspect when referring back to any of the thirty-seventh to forty-fourth aspects, the device is adapted to use UL or DL FD resources of the first part or of the second part with a defined pattern and / or for a defined time duration or period and to then switch back to a fallback configuration, according to the signalling.2025F68137 - 25014 25

[0197] According to a forty-sixth aspect when referring back to any of the thirty-seventh to forty-fifth aspects, the device is adapted to use UL or DL FD resources dependent on at least one of - a carrier frequency of the UL or DL FD resources, e.g., based on a lower frequency causing less path loss to allow less transmit power being required, - an amount of transmit power reduction achieved by using a lower carrier frequency,

[0198] - a QoS criterion, e.g.,

[0199] o number of resources to be transmitted by the device, e.g., in case this exceeds a certain threshold, the UL or DL FD resources are used, otherwise they are not used,

[0200] o a packet delay budget, PDB, in case this is below a configured or preconfigured threshold, the additional UL or DL FD resources are used in order to fulfil the PDB

[0201] o reliability, e.g., using redundancy transmission or data duplication, in order to increase successful packet delivery.

[0202] According to a forty-seventh aspect when referring back to any of the first to forty-sixth aspects, the device is adapted to receive and process signalling received with the second carrier as an aggregated carrier, the signalling indicating a use of the first part related to the first carrier as a base carrier.

[0203] According to a forty-eighth aspect when referring back to any of the first to forty-seventh aspects, the device is configured or pre-configured or adapted to process implicit and / or explicit signalling indicating where to blind decode resource maps for the carrier aggregation and to operate accordingly.

[0204] According to a forty-ninth aspect when referring back to any of the first to forty-eighth aspects, the device is adapted to return from the carrier aggregation to an operation on the first carrier or the second carrier as a base carrier based on at least one of an explicit signalling, after a timeout and after reception and / or transmission of a certain number of data symbols within the FD part of the aggregated carrier.

[0205] According to a fiftieth aspect when referring back to the forty-ninth aspect, the device is adapted to return to the operation on the base carrier as a fallback immediately; or after a certain number of transmissions on the aggregated band; or after a timeout; or after a number of failed transmissions, e.g., for which the UE received no NACKs or a number of NACKs.2025F68137 - 25014 26

[0206] According to a fifty-first aspect when referring back to the fiftieth aspect, the device is adapted to return to the operation on the base carrier as a fallback based on one or more of

[0207] - an indication from the base station, e.g., a signalling received from the base station,

[0208] - as a result of a request of the device,

[0209] - by its own decision:

[0210] o sending a request to the base station,

[0211] o informing the base station about its action, e.g., return to the operation on the base carrier as a fallback.

[0212] - by a timeout, e.g., the fallback will be automatically triggered in case a timeout is reached,

[0213] - by an event-triggered timeout, e.g., battery limit reached.

[0214] According to a fifty-second aspect when referring back to any of the forty-ninth to fifty-first aspects, based on returning from the carrier aggregation a transmissions or receptions on the base carrier could be skipped, e.g., thus, the power consumption of the UE, e.g., by not performing blind decodes or by not having to transmit on the base carrier in a subsequent time domain resources, could be reduced.

[0215] According to a fifty-third aspect when referring back to any of the forty-ninth to fifty-second aspects, based on a transmission using the carrier aggregation using the FD symbol, the device is to skip at least one of a transmission and a reception on a base carrier of the carrier aggregation.

[0216] According to a fifty-fourth aspect when referring back to the fifty-third aspect the device is adapted to perform power saving based on a symbol being skipped on the base carrier or on an aggregated carrier, e.g., DRX, e.g., the UE does not have to perform blind decoding on either base carrier or aggregated carrier.

[0217] According to a fifty-fifth aspect when referring back to any of the first to fifty-fourth aspects, the device is adapted for using the carrier aggregation for boosting at least one of an uplink, UL, and a downlink, DL, capacity; and / or for redundancy transmissions, e.g., to increase at least one of a data rate, a spectral efficiency and a reliability.2025F68137 - 25014 27

[0218] According to a fifty-sixth aspect when referring back to any of the first to fifty-fifth aspects, the device is to aggregate based on the first carrier and the second carrier being operated as TDD carriers that are shifted in the time domain by a time offset.

[0219] According to a fifty-seventh aspect when referring back to the fifty-sixth aspect, the device is to use the second part in an opposite link direction when compared to the first part.

[0220] According to a fifty-eighth aspect when referring back to the fifty-seventh aspect, the device is adapted for a continuous UL transmission and / or DL reception in time domain using the aggregated parts.

[0221] According to a fifty-ninth aspect when referring back to any of the fifty-seventh or fifty-eighth aspect, for using an SBFD symbol for using the FD symbol for boosting an uplink of the other symbol or for increasing a downlink capacity of the other symbol, e.g., to increase at least one of a data rate, a spectral efficiency and a reliability.

[0222] According to a sixtieth aspect when referring back to any of the fifty-seventh to fifty-ninth aspects, the device is to operate on the first carrier and the second carrier as separated in the frequency domain and / or in a spatial domain.

[0223] According to a sixty-first aspect when referring back to any of the fifty-seventh to sixtieth aspects, the time offset is within a time resource, which is one or more of

[0224] - a number of samples,

[0225] - a number of OFDM symbols,

[0226] - a mini-slot or a half slot or a slot or a subslot,

[0227] - a frame, a half-frame or a radioframe or a hyperframe,

[0228] - is within a guard period or cyclic prefix,

[0229] - limited by a threshold, e.g., shorter than a guard period,

[0230] - depending on the used numerology, e.g., 7 OFDM symbols for 15kHz SOS, 14 OFDM symbols for 30kHz SOS.

[0231] According to a sixty-second aspect when referring back to any of the fifty-seventh to sixty-first aspects, the position of the time offset is at the beginning of a time resource, or at the end of a time resource, e.g., in TDD before or after a DL symbol or UL symbol or flexible symbol.2025F68137 - 25014 28

[0232] According to a sixty-third aspect when referring back to any of the fifty-seventh to sixty-second aspects, the resources used within the aggregated SBFD symbol are randomized, or wherein the resources are used according to a configured and / or pre-configured pattern.

[0233] According to a sixty-fourth aspect when referring back to any of the fifty-seventh to sixty-third aspects, the device is adapted to blank or puncture out a part of a base carrier or aggregated carrier.

[0234] According to a sixty-fifth aspect when referring back to any of the fifty-seventh to sixty-fourth aspects, the adapting is with respect to an aggregated part where an overlap of opposite link directions of the FD symbol with respect to the other part occurs.

[0235] According to a sixty-sixth aspect when referring back to any of the first to sixty-fifth aspects, the device is adapted to operate on the first part and the second part based on a gap or guard between an UL and a DL direction or a UL and a flexible direction, F, or a DL and a flexible direction, F, within a carrier.

[0236] According to a sixty-seventh aspect when referring back to the sixty-sixth aspect, the gap is adapted for allowing switching between UL and DL transmission, e.g., reconfiguration of analogue components of a UE, e.g., power amplifiers, PAs, or filters, or wherein the device is adapted to use the gap for power saving, e.g., DRX.

[0237] According to a sixty-eighth aspect when referring back to any of the sixty-sixth or sixty-seventh aspect, the gap is defined as a time resource.

[0238] According to a sixty-ninth aspect when referring back to the sixty-eighth aspect, the time resource is one or more of

[0239] - a number of samples,

[0240] - a number of OFDM symbols,

[0241] - a mini-slot or a half slot or a slot or a subslot,

[0242] - a frame, a half-frame or a radioframe or a hyperframe,

[0243] - is within a guard period or cyclic prefix,

[0244] - limited by a threshold, e.g., shorter than a guard period,

[0245] - depending on the used numerology, e.g., 7 OFDM symbols for 15kHz SOS, 14 OFDM symbols for 30kHz SOS.2025F68137 - 25014 29

[0246] According to a seventieth aspect when referring back to any of the sixty-sixth to sixty-ninth aspects, the gap is configured or pre-configured, e.g., via RRC and / or MAC-CE and / or PHY-signalling or higher layer signalling, or wherein the device is to determine the gap based on a FD slot configuration.

[0247] According to a seventy-first aspect when referring back to any of the sixty-sixth to seventieth aspects, the gap is configured over a whole frequency range of a carrier, or is defined for at least one certain subband within the frequency range of a carrier.

[0248] According to a seventy-second aspect when referring back to any of the sixty-sixth to seventy-first aspects, the device is adapted to operate according to a configuration where the gap is configured on one of the carriers, e.g., the carrier containing the FD slot or symbol, or on a carrier having no FD slot, or on both carriers.

[0249] According to a seventy-third aspect when referring back to any of the sixty-sixth to seventy-second aspects, the device is adapted to operate according to a configuration where the gap is related to a same or different radio characteristics applying to the first carrier and the second carrier.

[0250] According to a seventy-fourth aspect when referring back to the seventy-third aspect, the different radio characteristics relate to an asymmetric use of a first communication technology used for the first carrier and a second communication technology used for the second carrier.

[0251] According to a seventy-fifth aspect when referring back to the seventy-fourth aspect, one of the first communication technology and the second communication technology is a terrestrial communication and the other is a non-terrestrial communication.

[0252] According to a seventy-sixth aspect when referring back to any of the sixty-sixth to seventyfifth aspects, different gaps of different bandwidth and / or time duration are implemented in the first carrier and in the second carrier.

[0253] According to a seventy-seventh aspect when referring back to any of the first to seventy-sixth aspects, at least one of the first carrier and the second carrier is operated with a slot format comprising downlink symbols, uplink symbols, and flexible symbols.

[0254] According to a seventy-eighth aspect when referring back to the seventy-seventh aspect, the first part is associated with a reference cell to which the second part is aggregated, wherein2025F68137 - 25014 30

[0255] the symbol of the reference cell is a reference symbol, wherein the reference symbol and / or of the aggregated part is a FD symbol.

[0256] According to a seventy-ninth aspect when referring back to the seventy-eighth aspect, the reference symbol is one of:

[0257] • downlink, or uplink, e.g., as indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL- DL-ConfigurationDedicated,

[0258] • uplink, if the reference symbol is a flexible symbol or a FD symbol, wherein the device is adapted to transmit an uplink signal or channel, e.g., at least one of SRS, PLICCH, PLISCH, or PRACH on the reference symbol,

[0259] • downlink, if the reference symbol is a flexible symbol or a FD symbol, wherein the device is configured to receive at least a downlink signal or channel, e.g., one of PDCCH, PDSCH or CSI-RS on the reference symbol,

[0260] • FD symbol, as indicated.

[0261] According to an eightieth aspect when referring back to the seventy-eighth or seventy-ninth aspect, the reference symbol is a downlink symbol or a flexible symbol which is converted to a FD symbol.

[0262] According to an eighty-first aspect when referring back to the eightieth aspect, the device is to operate according to a TDD common configuration that configures the reference symbol to be downlink and to operate according to a FD configuration that indicates that it is a FD symbol; or wherein the device is to operate according to the TDD common configuration that configures the reference symbol to be a flexible symbol, and wherein the device is to operate according to a FD configuration indicating the reference symbol to be a FD symbol.

[0263] According to an eighty-second aspect when referring back to any of the seventy-eighth to eighty-first aspects, the device is to select the reference cell as a cell without FD configuration.

[0264] According to an eighty-third aspect when referring back to any of the seventy-eighth to eighty-second aspects, the device is adapted to select a cell as reference cell that comprises a cell index nearest to a cell index of a cell with FD configuration.

[0265] According to an eighty-fourth aspect when referring back to any of the seventy-eighth to eighty-third aspects, the device is adapted to select the cell based on a capability.2025F68137 - 25014 31

[0266] According to an eighty-fifth aspect when referring back to any of the seventy-eighth to eightyfourth aspects, the device is to select a reference cell with FD configuration as reference cell.

[0267] According to an eighty-sixth aspect when referring back to any of the seventy-eighth to eightyfifth aspects, whether the device is to select a reference cell with FD configuration as reference cell is based on a device capability.

[0268] According to an eighty-seventh aspect when referring back to the eighty-fifth or eighty-sixth aspect, the device is to select the reference cell with FD configuration as reference cell based on all uplink and / or downlink or certain defined uplink and / or downlink signals / channels are with Configuration 1.

[0269] According to an eighty-eighth aspect when referring back to the eighty-seventh aspect, whether the device is to select the reference cell with FD configuration as reference cell based on all uplink and / or downlink or certain defined uplink and / or downlink are with Configuration 1 is based on a device capability.

[0270] According to an eighty-ninth aspect when referring back to the eighty-seventh or eighty-eighth aspect, Configuration 1 relates to all transmissions and / or receptions are confined to only one symbol type being a FD or non-FD symbol, e.g., based on a device capability.

[0271] According to a ninetieth aspect when referring back to any of the seventy-eighth to eighty-ninth aspects, the device is adapted to use a cell with FD configuration for the carrier aggregation based on satisfying a condition that all uplink and / or downlink signals or channels, or certain defined uplink and / or downlink signals or channels are with Configuration 1.

[0272] According to a ninety-first aspect when referring back to the ninetieth aspect, in case a valid symbol type of Configuration 1 is non-FD, the device is to operate accordingly for carrier aggregation.

[0273] According to a ninety-second aspect when referring back to the ninetieth or ninety-first aspect, Configuration 1 relates to all transmissions and / or receptions are confined to only one symbol type being a FD or non-FD symbol, e.g., based on a device capability.

[0274] According to a ninety-third aspect when referring back to any of the seventy-seventh to ninety-second aspects, the device is adapted to operate according to FD symbols on a reference cell and / or other cells being equivalent to flexible symbols.2025F68137 - 25014 32

[0275] According to a ninety-fourth aspect when referring back to the ninety-third aspect, the device is adapted to apply a behavior for flexible symbols to FD symbols.

[0276] According to a ninety-fifth aspect when referring back to the ninety-fourth aspect, the device is adapted to not expect to be configured, e.g., by higher layers, to receive PDCCH, PDSCH, or CSI-RS on a flexible symbol / SBFD symbol on the reference cell and to detect a DCI format scheduling a transmission on the symbol on another cell, if another cell among the cells configured with direction collision handling, e.g., directionalCollisionHandling-r16, operates in the same frequency band as the reference cell.

[0277] According to a ninety-sixth aspect when referring back to any of the seventy-seventh to ninetyfifth aspects, the device is adapted to receive link directions indicating uplink and / or downlink for FD symbols in reference cells or other cells and to operate accordingly.

[0278] According to a ninety-seventh aspect when referring back to the ninety-sixth aspect, the device is adapted to operate according to link directions being semi-static or dynamic.

[0279] According to a ninety-eighth aspect when referring back to any of the ninety-sixth or ninetyseventh aspect, the device is adapted to operate based on rules for collision handling in a carrier aggregation scenario considering the uplink and / or downlink and semi-static and / or dynamic link direction in the FD symbols.

[0280] According to a ninety-ninth aspect when referring back to any of the seventy-seventh to ninetyeighth aspects, the device is adapted to not expect downlink and / or uplink in the reference symbol and uplink and / or downlink, respectively, in another cell for a case where the symbol of the reference cell is a reference symbol of type FD.

[0281] According to a one-hundredth aspect when referring back to the eighty-eighth aspect, the device is adapted to operate based on the another cell among a plurality of available cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, operating in a same or different band as the reference cell.

[0282] According to a one-hundred-first aspect when referring back to the ninety-ninth or one-hundredth aspect, the device is adapted to operate according to a signalling that indicates a symbol as one of a) FD; b) both downlink and FD; and c) both flexible and FD on the reference cell and as at least one of uplink; flexible; or downlink on another cell respectively.2025F68137 - 25014 33

[0283] According to a one-hundred-second aspect when referring back to the one-hundred-first aspect, the device is adapted to operate in a scenario where another cell among the cells is configured with directional collision handling, e.g., directionalCollisionHandling-r16, operates in the same band as the reference cell.

[0284] According to a one-hundred-third aspect when referring back to the one-hundred-first or one-hundred-second aspect, the device is adapted to operate according to an uplink or downlink or flexible link direction being indicated by one or more of: tdd-UL-DL-ConfigurationCommon, by tdd-UL-DL-ConfigurationDedicated, DCI, SFI, MAC CE, scheduling of uplink / downlink signals / channels, e.g., semi-static scheduling of PDCCH, CSI-RS, PDSCH, PLICCH, PRACH, SRS, PUSCH etc.

[0285] According to a one-hundred-fourth aspect when referring back to any of the one-hundred-first to one-hundred-third aspects, the device is adapted to operate according to a signalling indicating the symbol as downlink by TDD common configuration and also as FD symbol.

[0286] According to a one-hundred-fifth aspect when referring back to any of the one-hundred-first to one-hundred-fourth aspects, the device is adapted to operate according to a signalling indicating the symbol as flexible by TDD common configuration and also indicated as FD symbol.

[0287] According to a one-hundred-sixth aspect when referring back to any of the one-hundred-first to one-hundred-fifth aspects, the device is adapted to operate according to a signalling indicating the symbol as FD or downlink + SBFD or flexible + SBFD and configures the symbol semi-statically or dynamically as downlink and / or uplink on the reference cell and as uplink and / or downlink on another cell respectively.

[0288] According to a one-hundred-seventh aspect when referring back to the one-hundred-sixth aspect, when another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, operates in the same band as the reference cell, the uplink and / or downlink on the another cell and / or reference cell is a semi-static configuration, a dynamic configuration or both.

[0289] According to a one-hundred-eighth aspect when referring back to the one-hundred-seventh aspect, for semi-static downlink configuration of the reference cell and / or the another cell, the indication can be using any RRC or MAC CE, or tdd-UL-DL-ConfigurationCommon or by tdd-2025F68137 - 25014 34

[0290] UL-DL-ConfigurationDedicated, or a downlink signal / channel semi-statically configured, e.g., semi-static scheduling of PDCCH, CSI-RS, PDSCH, etc. or a link direction signal indicating downlink reception.

[0291] According to a one-hundred-ninth aspect when referring back to the one-hundred-seventh or one-hundred-eighth aspect, for semi-static uplink configuration of the reference cell / another cell, the indication can be using RRC or MAC CE, or tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, or an uplink signal / channel semi-statically configured, e.g., semi-static scheduling of PLICCH, SRS, PLISCH, PRACH etc or a link direction signal indicating uplink transmission.

[0292] According to a one-hundred-tenth aspect when referring back to any of the one-hundred-seventh to one-hundred-ninth aspects, for dynamic configuration of the reference cell or another cell, it can be using one or more of SFI, DCI, dynamic link direction signal etc.

[0293] According to a one-hundred-eleventh aspect when referring back to any of the ninety-ninth to one-hundred-tenth aspects, the device is to operate accordingly in a case where the symbol in the another cell is FD and the reference cell is not configured with FD.

[0294] According to a one-hundred-twelfth aspect when referring back to any of the seventy-seventh to one-hundred-eleventh aspects, the device is adapted to not expect downlink receptions in the reference symbol, e.g., SBFD symbol, in only one downlink subband when uplink transmissions in another cell are configured semi-statically or dynamically.

[0295] According to a one-hundred-thirteenth aspect when referring back to the one-hundred-twelfth aspects, the device is adapted to operate based on another cell among a plurality of available cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, operates in the same or different band as the reference cell, e.g., in a case when the cell has more than one downlink subband.

[0296] According to a one-hundred-fourteenth aspect when referring back to any of the one-hundred-twelfth to one-hundred-thirteenth aspects, the device is adapted to select a downlink subband from a plurality of available downlink subbands based on a criterion.

[0297] According to a one-hundred-fifteenth aspect when referring back to the one-hundred-fourteenth aspects, the criterion is related to a downlink subband which will be least interfered at the device side from the other aggregated carriers is used for reception.2025F68137 - 25014 35

[0298] According to a one-hundred-sixteenth aspect when referring back to any of the one-hundred-fourteenth to one-hundred-fifteenth aspects, the device is adapted to operate on an uplink or downlink on the another cell or reference cell being configured in a semi-static and / or dynamic manner.

[0299] According to a one-hundred-seventeenth aspect when referring back to the one-hundred-sixteenth aspects, the device is adapted for determining an indication of the semi-static downlink configuration of the reference cell and / or the another cell, by using any RRC or MAC CE, or tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, or a downlink signal / channel semi-statically configured, e.g., semi-static scheduling of PDCCH, CSI-RS, PDSCH, etc or a link direction signal indicating downlink reception.

[0300] According to a one-hundred-eighteenth aspect when referring back to any of the one-hundred-sixteenth to one-hundred-seventeenth aspects, the device is adapted for determining an indication of the semi-static uplink configuration of the reference cell and / or another cell, by using RRC or MAC CE, or tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, or an uplink signal / channel semi-statically configured, e.g., semistatic scheduling of PLICCH, SRS, PLISCH etc or a link direction signal indicating uplink transmission.

[0301] According to a one-hundred-nineteenth aspect when referring back to any of the one-hundred-sixteenth to one-hundred-eighteenth aspects, the device is adapted for determining an indication of the dynamic configuration of the reference cell and / or another cell by using one or more of SFI, DCI, dynamic link direction signal etc.

[0302] According to a one-hundred-twentieth aspect when referring back to any of the one-hundred-sixteenth to one-hundred-nineteenth aspects, the device is adapted to operate accordingly if the symbol in the another cell is FD and the reference cell is not configured with FD.

[0303] According to a one-hundred-twenty-first aspect when referring back to any of the seventyseventh to one-hundred-twentieth aspects, the device is adapted to expect uplink transmissions in the reference symbol and downlink receptions in another cell based on special conditions for uplink transmissions in a case where the reference symbol is FD.

[0304] According to a one-hundred-twenty-second aspect when referring back the one-hundred-twenty-first aspect, the special condition relates to at least one of:2025F68137 - 25014 36

[0305] o when the uplink transmission is restricted to an uplink subband,

[0306] o when the uplink transmission is restricted to an uplink subband, based on a certain configuration, e.g., an uplink in between 2 downlink subbands, DUD or a DU or UD configuration or any combination thereof.

[0307] According to a one-hundred-twenty-third aspect when referring back to the one-hundred-twenty-first or one-hundred-twenty-second aspect, the device is adapted to operate with another cell among a plurality of cells configured with collision handling, e.g., directionalCollisionHandling-r16, in a same and / or different band as the reference cell.

[0308] According to a one-hundred-twenty-fourth aspect when referring back to any of the one-hundred-twenty-first to one-hundred-twenty-third aspects, the device is adapted to operate on an uplink and / or downlink on the another cell and / or reference cell being configured in a semistatic and / or dynamic manner.

[0309] According to a one-hundred-twenty-fifth aspect when referring back to the one-hundred-twenty-fourth aspect, the device is adapted for determining an indication of the semi-static downlink configuration of the reference cell and / or the another cell, by using any RRC or MAC CE, or tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, or a downlink signal / channel semi-statically configured, e.g., semi-static scheduling of PDCCH, CSI-RS, PDSCH, etc or a link direction signal indicating downlink reception.

[0310] According to a one-hundred-twenty-sixth aspect when referring back to the one-hundred-twenty-fourth or one-hundred-twenty-fifth aspect, the device is adapted for determining an indication of the semi-static uplink configuration of the reference cell and / or another cell, by using RRC or MAC CE, or tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, or an uplink signal / channel semi-statically configured, e.g., semistatic scheduling of PUCCH, SRS, PUSCH etc or a link direction signal indicating uplink transmission.

[0311] According to a one-hundred-twenty-seventh aspect when referring back to any of the one-hundred-twenty-fourth to one-hundred-twenty-sixth aspects, the device is adapted for determining an indication of the dynamic configuration of the reference cell and / or another cell by using one or more of SFI, DCI, dynamic link direction signal etc.

[0312] According to a one-hundred-twenty-eighth aspect when referring back to any of the one-hundred-twenty-first to one-hundred-twenty-seventh aspects, the device is adapted to operate2025F68137 - 25014 37

[0313] accordingly if the symbol in the another cell is FD and the reference cell is not configured with FD.

[0314] According to a one-hundred-twenty-ninth aspect when referring back to any of the seventyseventh to one-hundred-twenty-eighth aspects, the device is adapted to not expect a symbol to be indicated as only downlink, e.g., non-FD, on a reference cell which has FD configuration and uplink on another cell, respectively, by tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, e.g., if the another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, it operates in the same band as the reference cell.

[0315] According to a one-hundred-thirtieth aspect when referring back to any of the seventy-seventh to one-hundred-twenty-ninth aspects, the device is adapted to not expect a symbol to be indicated as uplink on the reference cell and only downlink (not SBFD) on another cell, which has SBFD configuration respectively, by tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, e.g., if the another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, it operates in the same band as the reference cell.

[0316] According to a one-hundred-thirty-first aspect when referring back to any of the seventyseventh to one-hundred-thirtieth aspects, the device is adapted to transmit a signal or channel scheduled by a DCI format on a symbol of another cell where the transmissions are within the uplink subband of an SBFD symbol when the symbol is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for the reference cell, e.g., if the reference cell and another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, they operate in different frequency bands.

[0317] According to a one-hundred-thirty-second aspect when referring back to any of the seventyseventh to one-hundred-thirty-first aspects, the device is adapted to transmit a signal or channel scheduled by a DCI format on a symbol of another cell where the transmissions are in an only uplink symbol when the symbol is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for the reference cell, e.g., if the reference cell and another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, they operate in different frequency bands.

[0318] According to a one-hundred-thirty-third aspect when referring back to any of the seventyseventh to one-hundred-thirty-second aspects, the device is adapted to transmit a signal or2025F68137 - 25014 38

[0319] channel scheduled by a DCI format on a symbol of another cell when the symbol is indicated as only downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for the reference cell configured with SBFD, e.g., if the reference cell and another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, they operate in different frequency bands.

[0320] According to a one-hundred-thirty-fourth aspect when referring back to any of the seventyseventh to one-hundred-thirty-third aspects, the device is adapted to transmit a signal or channel scheduled by a DCI format on a symbol of another cell when the symbol is indicated as SBFD for the reference cell configured with SBFD, e.g., if the reference cell and another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, they operate in different frequency bands.

[0321] According to a one-hundred-thirty-fifth aspect when referring back to the one-hundred-thirty-fourth aspect, the device is adapted to operate on a symbol indicated as FD symbol that has semi-static downlink configuration using any RRC or MAC CE, or tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, or a downlink signal / channel semi-statically configured, e.g., semi-static scheduling of PDCCH, CSI-RS, PDSCH, etc. or a link direction signal indicating downlink reception.

[0322] According to a one-hundred-thirty-sixth aspect when referring back to the one-hundred-thirty-fourth or one-hundred-thirty-fifth aspect, the device is adapted to operate on a symbol indicated as FD that has dynamic downlink configuration using one or more of an SFI, a DCI, a dynamic link direction signal etc.

[0323] According to a one-hundred-thirty-seventh aspect when referring back to any of the seventyseventh to one-hundred-thirty-sixth aspects, the device is adapted for deriving a DCI format scheduling a transmission on one or more symbols in a set of symbols on another cell and to operate the carrier aggregation without receiving a higher layer configured PDCCH, PDSCH, or CSI-RS on flexible or SBFD symbols on the reference cell, if the UE, e.g., if the reference cell and another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, operate in different frequency bands.

[0324] According to a one-hundred-thirty-eighth aspect when referring back to any of the seventyseventh to one-hundred-thirty-seventh aspects, the device is adapted for deriving a DCI format scheduling a transmission on one or more symbols in the set of symbols on another cell where the one or more symbols are non-SBFD; and to the carrier aggregation without receiving a2025F68137 - 25014 39

[0325] higher layer configured PDCCH, PDSCH, or CSI-RS on flexible symbols on the reference cell in a set of symbols, e.g., if the reference cell and another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, operate in different frequency bands.

[0326] According to a one-hundred-thirty-ninth aspect when referring back to any of the seventyseventh to one-hundred-thirty-eighth aspects, the device is adapted for deriving a DCI format scheduling a transmission on one or more symbols in the set of symbols on another cell where the one or more symbols are SBFD symbols, and to operate the carrier aggregation without receiving a higher layer configured PDCCH, PDSCH, or CSI-RS on flexible symbols on the reference cell in a set of symbols, e.g., if the reference cell and another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, operate in different frequency bands.

[0327] According to a one-hundred-fortieth aspect when referring back to any of the seventy-seventh to one-hundred-thirty-ninth aspects, the device is adapted to assume a symbol as flexible symbol or FD symbol and to operate the carrier aggregation without receiving a higher layer configured PDCCH, PDSCH, or CSI-RS; and wherein the device is to avoid transmission of a higher layer configured SRS, PLICCH, PLISCH, or PRACH, when tdd-UL-DLConfigurationCommon or tdd-UL-DL-ConfigurationDedicated indicates a symbol as downlink or uplink on another cell and as uplink or downlink for the reference cell, respectively.

[0328] According to a one-hundred-forty-first aspect when referring back to the one-hundred-fortieth aspect, the device is adapted to operate on a symbol that is indicated as a) FD; or b) downlink + SBFD or c) flexible + SBFD and is configured semi-statically or dynamically as downlink and / or uplink on the reference cell and as uplink or downlink on another cell respectively.

[0329] According to a one-hundred-forty-second aspect when referring back to the one-hundred-forty-first aspect, the uplink and / or downlink configuration on the another cell and / or the reference cell is a semi-static configuration, a dynamic configuration or both.

[0330] According to a one-hundred-forty-third aspect when referring back to the one-hundred-forty-first or one-hundred-forty-second aspect, for semi-static downlink configuration of the reference cell or another cell, the device is to operate based on an indication that uses any RRC or MAC CE, or a downlink signal / channel semi-statically configured, e.g., semi-static scheduling of PDCCH, CSI-RS, PDSCH, etc. or a link direction signal indicating downlink reception.2025F68137 - 25014 40

[0331] According to a one-hundred-forty-fourth aspect when referring back to any of the one-hundred-forty-first to one-hundred-forty-third aspects, for semi-static uplink configuration of the reference cell or another cell, the device is to operate based on an indication that uses RRC or MAC CE, or an uplink signal / channel semi-statically configured, e.g., semi-static scheduling of PLICCH, SRS, PLISCH, PRACH etc or a link direction signal indicating uplink transmission.

[0332] According to a one-hundred-forty-fifth aspect when referring back to any of the one-hundred-forty-first to one-hundred-forty-fourth aspects, for dynamic configuration of the reference cell or another cell, the device is to operate based on an indication that uses one or more of SFI, DCI, or a dynamic link direction signal.

[0333] According to a one-hundred-forty-sixth aspect when referring back to any of the one-hundred-forty-first to one-hundred-forty-fifth aspects, the device is adapted to operate on the FD symbol having a downlink configured on both its downlink subbands or only one subband.

[0334] According to a one-hundred-forty-seventh aspect when referring back to any of the one-hundred-forty-first to one-hundred-forty-sixth aspects, the device is adapted to operate on the FD symbol having an uplink subband with a certain configuration, e.g., the configuration is DU or UD.

[0335] According to a one-hundred-forty-eighth aspect when referring back to any of the one-hundred-fortieth to one-hundred-forty-seventh aspects, the symbol is a non-FD symbol only.

[0336] According to a one-hundred-forty-ninth aspect when referring back to any of the one-hundred-fortieth to one-hundred-forty-eighth aspects, the device is adapted to operate accordingly when the symbol in the another cell is SBFD and the reference cell is not configured with FD.

[0337] According to a one-hundred-fiftieth aspect when referring back to any of the seventy-seventh to one-hundred-forty-ninth aspects, the device is adapted to not transmit one or more of a PUCCH, PUSCH, SRS or PRACH that is configured by higher layers on a set of symbols on another cell if at least one symbol from the set of symbols is indicated as downlink by tdd-UL-DLConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and non-SBFD or is a symbol corresponding to one or more of a PDCCH, PDSCH, or CSI-RS reception that is configured by higher layers or an SBFD symbol on the reference cell.2025F68137 - 25014 41

[0338] According to a one-hundred-fifty-first aspect when referring back to the one-hundred-fiftieth aspect, the device is adapted to operate according to the FD symbol being further configured with a link direction signal indicating downlink reception or dynamically configured using one or more of SFI, DCI, dynamic link direction signal etc. for downlink.

[0339] According to a one-hundred-fifty-second aspect when referring back to the one-hundred-fiftieth or one-hundred-fifty-first aspect, the device is adapted to operate according to the FD symbol comprising downlink configured on both its downlink subbands.

[0340] According to a one-hundred-fifty-third aspect when referring back to any of the seventyseventh to one-hundred-fifty-second aspects, the device is adapted to not transmit one or more of a PLICCH, PLISCH, SRS or PRACH that is configured by higher layers on a set of symbols on another cell if at least one symbol from the set of symbols is indicated as downlink by tdd-UL-DLConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or is a symbol corresponding to one or more of a PDCCH, PDSCH, or CSI-RS reception that is configured by higher layers on the reference cell based on at least one of:

[0341] o at least one symbol on another cell is a non-FD symbol;

[0342] o at least one symbol on another cell is an FD symbol; and

[0343] o at least one symbol on another cell is an FD symbol with uplink subband with a certain configuration, e.g., the configuration is DU or UD.

[0344] According to a one-hundred-fifty-fourth aspect when referring back to any of the seventyseventh to one-hundred-fifty-third aspects, the device is adapted to not receive and process one or more of a PDCCH, PDSCH or CSI-RS that is configured by higher layers on a set of symbols on another cell if at least one symbol from the set of symbols is indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or is a symbol corresponding to a SRS, or an FD symbol, or PUCCH, PUSCH, or PRACH transmission that is configured by higher layers on the reference cell.

[0345] According to a one-hundred-fifty-fifth aspect when referring back to the one-hundred-fifty-fourth aspect, the FD symbol is further configured with a link direction signal indicating uplink transmission or dynamically configured using one or more of SFI, DCI, dynamic link direction signal etc. for uplink.

[0346] According to a one-hundred-fifty-sixth aspect when referring back to any of the one-hundred-fifty-fourth to one-hundred-fifty-fifth aspects, the FD symbol comprises an uplink subband with a certain configuration, e.g., the configuration is DU or UD.2025F68137 - 25014 42

[0347] According to a one-hundred-fifty-seventh aspect when referring back to any of the seventyseventh to one-hundred-fifty-sixth aspects, the device is adapted to not receive and process one or more of a PDCCH, PDSCH or CSI-RS that is configured by higher layers on a set of symbols on another cell if at least one symbol from the set of symbols is indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or is a symbol corresponding to one or more of a SRS, or PLICCH, PLISCH, or PRACH transmission that is configured by higher layers on the reference cell based on at least one of:

[0348] o if at least one symbol on another cell is a non-FD symbol;

[0349] o if at least one symbol on another cell is an FD symbol;

[0350] o if at least one symbol on another cell is a FD symbol with downlink subband with a certain configuration. E.g., the configuration is DU or UD or reception is allowed on both the downlink subbands as in DUD configuration.

[0351] According to a one-hundred-fifty-eighth aspect when referring back to any of the seventyseventh to one-hundred-fifty-seventh aspects, the device is adapted to assumes a symbol indicated as downlink or uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DLConfigurationDedicated on another cell to be flexible, if the UE is respectively configured by higher layers to transmit one or more of a SRS, PUCCH, PUSCH and PRACH or to receive one or more of a PDCCH, PDSCH and CSI-RS on the reference cell.

[0352] According to a one-hundred-fifty-ninth aspect when referring back to the one-hundred-fifty-eighth aspect, the device is adapted to operate based on a configuration according to which the transmission or reception is configured on an SBFD symbol of the reference cell.

[0353] According to a one-hundred-sixtieth aspect when referring back to the one-hundred-fifty-ninth aspect, the device is adapted to operate according to

[0354] ■ the reception being configured in only one downlink subband;

[0355] ■ the reception being configured in both the downlink subbands;

[0356] ■ the transmission being within an uplink subband, e.g., it further depends on the type of configuration like DU or UD or DUD, etc.

[0357] According to a one-hundred-sixty-first aspect when referring back to the one-hundred-fifty-ninth or one-hundred-sixtieth aspects, the device is adapted to operate according to the transmission or reception is configured on a non-SBFD symbol of the reference cell.2025F68137 - 25014 43

[0358] According to a one-hundred-sixty-second aspect when referring back to any of the seventyseventh to one-hundred-sixty-first aspects, the device is adapted to assume a symbol indicated as downlink or uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DLConfigurationDedicated on another cell to be flexible or FD, based on FD being configured on the another cell and / or based on a configuration by higher layers to transmit one or more of SRS, PLICCH, PLISCH, or PRACH or to receive one or more of PDCCH, PDSCH, or CSI-RS on the reference cell.

[0359] According to a one-hundred-sixty-third aspect when referring back to the one-hundred-sixty-second aspect, the device is adapted to consider FD only if the symbol is indicated as downlink.

[0360] According to a one-hundred-sixty-fourth aspect when referring back to any of the seventyseventh to one-hundred-sixty-third aspects, the device is adapted to not expect to detect a first DCI format scheduling a transmission or reception on a symbol on a first cell and a second DCI format scheduling a reception or transmission on the symbol on a second cell, respectively.

[0361] According to a one-hundred-sixty-fifth aspect when referring back to any of the first to one-hundred-sixty-fifth aspects, the device is adapted to perform collision handling based on using the FD symbol.

[0362] According to a one-hundred-sixty-sixth aspect when referring back to the one-hundred-sixty-fifth aspect, the device is adapted to perform the collision handling based on an uplink part of the carrier aggregation being in a different carrier as a downlink part of the carrier aggregation, e.g., there is dynamically scheduled DL reception on one carrier and semi-statically configured UL on another carrier.

[0363] According to a one-hundred-sixty-seventh aspect when referring back to the one-hundred-sixty-fifth or one-hundred-sixty-sixth aspects, the device is adapted to operate based on a dynamically scheduled DL reception and semi-statically configured UL transmission are to be not expected by the device, e.g., when the first carrier and the second carrier are within the same band.

[0364] According to a one-hundred-sixty-eighth aspect when referring back to any of the one-hundred-sixty-fifth to one-hundred-sixty-seventh aspects, the device is adapted to operate based on a dynamically scheduled DL reception; wherein semi-statically configured UL transmissions are allowed, wherein the device is adapted for at least one of:2025F68137 - 25014 44

[0365] o reusing an existing collision handling principle and timeline in NR for operation on flexible symbols on a single carrier in unpaired spectrum, i.e., UL transmission is cancelled if cancellation timeline is met, e.g., the carriers are in different bands and optionally applying the same rule for a repetition of the uplink;

[0366] o DL receptions are allowed only in certain cases such as within DL subbands, within non-SBFD symbols, within only DL subbands within SBFD symbols etc.; o UL transmissions are allowed only in certain cases such as only with non-SBFD symbols, within UL subbands within SBFD symbols, e.g., in DU or UD or DUD configurations etc.

[0367] According to a one-hundred-sixty-ninth aspect when referring back to any of the one-hundred-sixty-fifth to one-hundred-sixty-eighth aspects, the device is adapted to operate based on a semi-statically configured DL reception and dynamically scheduled UL transmission are to be not expected by the device, e.g., when the carriers are within the same band.

[0368] According to a one-hundred-seventieth aspect when referring back to any of the one-hundred-sixty-fifth to one-hundred-sixty-ninth aspects, the device is adapted to operate based on a semi-statically configured DL reception and dynamically scheduled UL transmission being allowed, wherein the device is adapted for at least one of:

[0369] o reusing the existing collision handling principles in NR for operation on flexible symbols on a single carrier in unpaired spectrum, i.e., the device does not receive and process DL channel or signal, e.g., the carriers are in different bands and optionally applying the same rule for a repetition of the downlink; o DL receptions are allowed only in certain cases such as within DL subbands, within non-SBFD symbols, within only DL subbands within SBFD symbols etc. o UL transmissions are allowed only in certain cases such as only with non-SBFD symbols, within UL subbands within SBFD symbols, e.g., in DU or UD or DUD configurations etc.

[0370] According to a one-hundred-seventy-first aspect when referring back to any of the one-hundred-sixty-fifth to one-hundred-seventieth aspects, the device is adapted to operate according to a semi-statically configured DL reception vs. semi-statically configured UL transmission being an error case, wherein the first carrier and the second carriers are in same or different bands.2025F68137 - 25014 45

[0371] According to a one-hundred-seventy-second aspect when referring back to any of the one-hundred-sixty-fifth to one-hundred-seventy-first aspects, the device is adapted to operate according to not receiving and processing both dedicated higher layer parameters configuring transmission from the device and dedicated higher layer parameters configuring reception.

[0372] According to a one-hundred-seventy-third aspect when referring back to any of the one-hundred-sixty-fifth to one-hundred-seventy-second aspects, the device is adapted not receive and process both dedicated higher layer parameters configuring transmission from the device and cell specific higher layer parameters configuring reception.

[0373] According to a one-hundred-seventy-fourth aspect when referring back to the one-hundred-seventy-third aspect, the cell specific higher layer parameter relates to a cell-specifically configured DL reception that refers to PDCCH, e.g., in Type-0 / 0A / 1 / 2 CSS set.

[0374] According to a one-hundred-seventy-fifth aspect when referring back to any of the one-hundred-seventy-first to one-hundred-seventy-fourth aspects, the device is adapted to operate according to DL receptions being allowed only in certain cases such as within DL subbands, within non-FD symbols, within only DL subbands of FD symbols and / or carriers being in different bands.

[0375] According to a one-hundred-seventy-sixth aspect when referring back to any of the one-hundred-seventy-first to one-hundred-seventy-fifth aspects, the device is adapted to operate according to UL transmissions being allowed only in certain cases such as only with non-SBFD symbols, within UL subbands of SBFD symbols in DU or UD or DUD configurations and / or carriers being in different bands.

[0376] According to a one-hundred-seventy-seventh aspect when referring back to any of the one-hundred-sixty-fifth to one-hundred-seventy-sixth aspects, the device is adapted to consider a dynamically scheduled DL reception with and / or without repetitions and a dynamically scheduled UL transmission with and / or without repetitions being in the same time domain symbol as an error case, e.g., when the carriers are within the same band.

[0377] According to a one-hundred-seventy-eighth aspect when referring back to the one-hundred-seventy-seventh aspect, the device is adapted to operate according to DL receptions being allowed only in certain cases such as within DL subbands, within non-SBFD symbols, within only SBFD symbols and / or carriers being in different bands.2025F68137 - 25014 46

[0378] According to a one-hundred-seventy-ninth aspect when referring back to the seventy-seventh or one-hundred-seventy-eighth aspects, the device is adapted to operate according to UL transmissions being allowed only in certain cases such as only with non-SBFD symbols, within UL subbands of SBFD symbols in DU or UD or DUD configurations and / or carriers being in different bands.

[0379] According to a one-hundred-eightieth aspect when referring back to any of the one-hundred-sixty-fifth to one-hundred-seventy-ninth aspects, the device is adapted to re-use an existing collision handling principles for TDD that SSB is prioritized over configured UL transmission and dynamically scheduled UL transmission, e.g., when the carriers are within the same band.

[0380] According to a one-hundred-eighty-first aspect when referring back to the one-hundred-eightieth aspect, the device is adapted to operate according to DL receptions being allowed only in certain cases such as within DL subbands, within non-SBFD symbols, within only SBFD symbols and / or carriers being in different bands etc.

[0381] According to a one-hundred-eighty-second aspect when referring back to the one-hundred-eightieth or one-hundred-eighty-first aspect, the device is adapted to operate according to UL transmissions being allowed only in certain cases such as only with non-SBFD symbols, within UL subbands in SBFD symbols in DU or UD or DUD configurations and / or carriers being in different bands etc.

[0382] According to a one-hundred-eighty-third aspect when referring back to any of the one-hundred- sixty-fifth to one-hundred-eighty-second aspects, for a case where dynamic or semistatic DL vs. valid RACH occasion, RO, applies, the device is adapted to at least one of:

[0383] • reusing an existing collision handling rules for HD-FDD RedCap UEs, e.g., when the carriers are within the same band;

[0384] • not expecting collision between PRACH triggered by PDCCH order and dynamically scheduled DL reception;

[0385] • not receiving or processing a DL signal or channel in case of a collision between PRACH triggered by PDCCH order and semi-statically configured DL reception;

[0386] • operate according to a device implementation whether to receive the DL or transmit PRACH in case of a collision between PRACH triggered by higher layer and DL channel or signal;

[0387] • operate according to DL receptions being allowed only in certain cases such as within DL subbands, within non-SBFD symbols, within only SBFD symbols and / or carriers being in different bands etc.;2025F68137 - 25014 47

[0388] • operate according to UL transmissions being allowed only in certain cases such as only with non-SBFD symbols, within SBFD symbols in UL subbands in DU or UD or DUD configurations and / or carriers being in different bands etc.

[0389] A one-hundred-eighty-fourth aspect relates to a radio device for communicating with one or more user devices, UEs, of a wireless communication system, the UEs when referring back to any one of the first to one-hundred-eighty-third aspects; wherein the radio device is to communicate with the one or more UEs using a radio signal comprising a plurality of time blocks in a time domain, and frequency block in a frequency domain.

[0390] According to a one-hundred-eighty-fifth aspect when referring back the one-hundred-eighty-fourth aspects, the radio device is one or more of the following: a base station, BS, a macro cell base station, or a small cell base station, or a central unit, CU, of a base station, or a distributed unit, DU, of a base station, or an Integrated Access and Backhaul, IAB, node, or a road side unit, RSU, or a WiFi access point, AP, or a UE, or a sidelink, SL, UE, or a group leader UE, GL-UE, ora relay ora remote radio head, or an AMF, or an SMF, ora core network, CN, entity, or mobile edge computing, MEC, entity, or a network slice as in the NR or 5G core context, or any transmission and reception point, TRP, one of a TRP as in multi-TRP, mTRP, enabling an item or a device to communicate using the wireless communication network, the item or device being provided with network connectivity to communicate using the wireless communication network, or a non-terrestrial device, e.g., a moving or stationary air-borne device, like a drone, an unmanned aerial vehicle, UAV, or an airplane, or a moving or stationary space-borne device, like a low earth orbit, LEO, satellite, like a LEO-600 satellite or a LEO-1200 satellite, a medium earth orbit, MEO, satellite, or a geosynchronous earth orbit, GEO, satellite.

[0391] A one-hundred-eighty-sixth aspect relates to a method for communicating in a wireless communications network comprising a plurality of cells, the method comprising: aggregating at least a first part of a first symbol of a first carrier of the wireless communication network and at least a second part of a second symbol of a second carrier of the wireless communication network for a carrier aggregation, such that at least one of the first symbol and the second symbol is a full duplex, FD, symbol.

[0392] A one-hundred-eighty-seventh aspect relates to 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 when referring back to the one-hundred-eighty-sixth aspect.2025F68137 - 25014 48

[0393] The solutions given above are described hereinafter whilst making reference to specific realisations that may be combined with one another without limitations.

[0394] 3.1 Methods of Carrier Aggregation

[0395] NR carriers can be aggregated and transmitted and / or received in parallel on the same device. This allows a higher peak data rate and / or higher flexibility in resource allocation schemes. Different scenarios may implement intra- or inter-band aggregation, with freguency contiguous or with non-contiguous component carriers. Furthermore, this may also depend on a particular freguency band, e.g., aggregation with the same freguency range, e.g., FR1, or carrier aggregation within different freguency ranges, e.g., FR1 and / or FR2 and / or FR3.

[0396] In case of symbols using subband full duplex transmission schemes, the combination of SBFD and CA allows a higher flexibility in resource usage in time / freguency / spatial domains.

[0397] Embodiments of the present invention relate to carrier aggregation, i.e., an aggregation of a first carrier and at least one aggregated carrier, wherein at least one of the base carrier and one or more of the aggregated carriers is operated to comprise a full duplex symbol, possibly but not necessary a subband full-duplex symbol, SBFD symbol. Such a full duplex, FD, symbol may comprise freguency resources in uplink direction and downlink direction in the same time resource(s), that are one of:

[0398] full-overlapping,

[0399] partial overlapping,

[0400] non-overlapping, e.g., an SBFD symbol having uplink and downlink subbands.

[0401] According to embodiments, an FD symbol may comprise at least one uplink part and at least one downlink part and optionally a flexible part, that may be used for uplink and / or downlink and / or sidelink, e.g., in a varied manner. Note, that a FD symbol can also consist of more than one uplink part and / or more than one downlink part and / or more than one sidelink part.

[0402] Such configuration may be operated by a base station, wherein the aggregated carriers may be operated by same or different base stations, where in a case of different base stations, a same or different types of base stations may be used, e.g., a macro base station, a micro base station, a small-cell base station, a non terrestrial network, NTN, base station and / or an integrated access and backhaul, lAB-node, a distributed unit, DU, or central unit, CU.2025F68137 - 25014 49

[0403] By use of carrier aggregation a base carrier may be formed, i.e., using a first carrier and one or more second carriers form a base carrier, e.g., the base carrier being formed as a combination comprising at least one of a) TDD / TDD, b) TDD / FDD, c) FDD / TDD and d) FDD / FDD.

[0404] 3.1.1 FDD / TDD (Option c) above)

[0405] In this scenario, carriers configured with different duplex schemes are aggregated. An example of such a configuration is shown in Fig. 6. For example, such an embodiment, may involve a first carrier 432i, which is, by way of non-limiting example, configured using frequency division duplex, FDD, where one band 434i is configured as uplink, UL, and one band 4342 is configured as downlink, DL, carrier. The UL and / or DL carrier aggregate by a system operating on a time division duplex, TDD, carrier 4322.

[0406] A system operating on a TDD carrier may suffer under the constraint that a UE can either transmit or receive at a given point in time. This may lead to additional delays for transmissions and / or receptions, since a UE may have to wait for the particular link direction. In case of a failed transmission, control and / or feedback messages may be delayed, which may result in further delay or even in packet loss, since packets are dropped by higher layer due to failed transmissions or failed signalling of resource maps. Thus, it may be beneficial to allow a more flexible transmission in either link direction, e.g., uplink and / or downlink, on an aggregated carrier.

[0407] For example, SBFD may also be utilized on the base carrier as well as on the aggregated carrier, in order to allow a more flexible transmission and / or reception. In one example, also in Fig. 6, the base carrier 434i, is a TDD carrier, and the aggregated carrier 4342 is the UL and / or DL carrier, operating in a neighbouring band. Note, that also just the UL or the DL carrier may be aggregated, as in a supplemental UL or DL carrier for boosting the capacity.

[0408] In case the DL carrier 4342 is aggregated, a number of symbols / slots within the DL carrier may be configured as SBFD symbols / slots 436i, 4362, which may allow configuring a different link direction, e.g., support of an UL transmission. Furthermore, this may enable a UE to transmit in the uplink direction within the FDD carrier or supplemental DL part of the FDD carrier, even though the said UE is currently within its DL period of the TDD carrier. The benefit may be that the said UE may not have to wait for an uplink transmission for the UL period of the TDD cycle. In addition, this may be beneficial for specific traffic types, e.g., control and / or feedback messages, e.g., transmission of HARQ-ACK / NACKs or channel state information, CSI, or for2025F68137 - 25014 50

[0409] beam management related information. Furthermore, this may include transmission of a preemption indication, such that certain future UL and / or DL transmissions, which may allow a more efficient resource usage,

[0410] ■ Certain transmissions, e.g., in the primary carrier, may not be required and can be dropped,

[0411] ■ HARQ ACK / NACK can be transmitted faster to avoid retransmissions or to allow retransmissions.

[0412] As may be seen in Fig. 6, along the time domain, TDD carrier 4322 may be aggregated with FDD UL carrier 434i so that time slots 436s, 2 of TDD carrier 4322 dedicated for DL such as time slots 4363,2 and / or 4363,4 are bridged by parts 436I,2 and / or 436i, 4 of UL band 432i or resources 4361 and / or 4362 of DL carrier 4342 to continue UL operation of TDD carrier 4322 and / or vice versa. The respective resources 436i and / or 4362 used or punctured for uplink may be aligned, e.g., in the time domain, with regard to a synchronized start and / or a synchronized end as shown for resource 436i having a synchronized end with slot 4363,2. Alternatively, as shown for resources 4362, an offset 438i may be used with regard to a delayed start of the resources 4362 when compared to DL slot 4363,4, e.g., to provide time for switching at the UE. Alternatively or in addition an offset 4382 may provide for an earlier end of resources 4362 when compared to the UL resources 4363,5 to be subsequently used, e.g., to allow switching at the UE. That is, an offset may optionally be used an a length thereof may be selected based on the requirements of at least on or all of the UEs, e.g., in terms of a temporal or static worst case consideration, possibly in order to address the switching time of devices.

[0413] 3.1.2 TDD / TDD (Option a) above)

[0414] Carrier aggregation may be configured among carriers implementing the same duplexing scheme, such as TDD - TDD carriers or FDD - FDD carriers. Note, that this is not limited to two carriers, and may also involve more than two component carriers.

[0415] By way of non-limiting example, a possible scenario with two TDD carriers 432i and 4322 is shown in Fig. 7. These carriers 432i and 4322 may in general be synchronized, especially if operating in the same frequency range, e.g., FR1. This may be done to avoid interference, especially trying to avoid that a neighbouring downlink carrier with high transmit power from a base station saturates the uplink receiver of a UE. Uplink receiver saturation may result in the UE not being able to receive anything in the uplink band. Carrier aggregation can then be used to increase the capacity by jointly allocating resources across carriers in UL and / or DL direction.2025F68137 - 25014 51

[0416] When configuring SBFD symbols 314I,2 and / or 314i, 4 within the base carrier 4321 or within the aggregated carrier 4322, this may allow to transmit into the other link direction. Thus, especially in TDD systems, the UE may be in the DL cycle in its base carrier and may transmit in the UL within a slot or symbol supporting SBFD, in an aggregated carrier.

[0417] This may mimic a FDD carrier, and may allow a continuous transmission of control and / or data during a continuous transmission time 442 even though the UE may normally not be able to do such a transmission, and may have to wait for the UL cycle within its base carrier.

[0418] Furthermore, in TDD system, it may be possible that a UE may have to wait a bit longer in its base carrier for a transmission grant for the UL, since other UEs might have allocated resources, and resource within a particular uplink cycle are already “booked out” by the resource allocation algorithms. Thus, urgent transmissions might not be possible by the said UE. This may be overcome by implementing the described SBFD structure, where urgent transmission may be deferred to a neighbouring SBFD UL symbol, without having to modify the scheduling in the base TDD carrier or band.

[0419] In another embodiment that may be combined or may be implemented independently, still the DL partofan SBFD slot, e.g., in an aggregated carrier, may be utilized to boost the DL capacity, depicted as DL boost 444 in Fig. 7.

[0420] According to an embodiment, that may be combined with other embodiments without significant modification, usage of DL and / or UL part of a SBFD symbol may be signalled in the base carrier, e.g., using cross-carrier scheduling techniques. Such a scenario is described in connection with Fig. 8a and Fig. 8b, referring to skipping some of the resources that may be used in the scenario of Fig. 7. Fig. 8a-b relate to TDD SBFD CA with optimized resource allocation, RA.

[0421] Such a skipping may be configured and / or pre-configured via PHY, MAC-CE, RRC or higher-layer configurations. Furthermore, to reduce further signalling, the skipping may be configured in a semi-persistent manner, e.g., based on a configured grant, CG, or semi-persistent scheduling, SPS, pattern. This may allow a UE to always use the DL and / or UL part of an aggregated carrier on a regular basis, without having to configure this for every transmission.

[0422] If configured on a global basis, e.g., via RRC, there may be a second level of configuration, which may allow to skip certain transmissions within the SBFD slot, e.g., in case there is no2025F68137 - 25014 52

[0423] data for a transmission. The term global basis may refer to the idea to have a basic configuration, which can be modified on a shorter time scale, e.g., adapted, in case we have a short-term requirement. Thus, the UE may perform power saving for the given time instance, see Fig. 8a, where the UL part 4482 of SBFD symbol 314I,4 may remain unused by the UE whilst the UL resources 448i of SBFD symbol 314i ,2 are used for UL of the device.

[0424] In addition or as an alternative, the signalling may also be based on the last received control signalling, e.g., in case it is received in an SBFD or non-SBFD symbol, the UE may expect a future control also in a successive SBFD or non-SBFD symbol. In a further embodiment, it may be more beneficial for a said UE to perform its UL transmissions in the aggregated carrier, e.g., in case this is at a lower frequency, as shown in Fig. 8b the UE may reduce its transmit power and more easily reach the base station. In such a scenario, the UE may use UL SBFD resources with a certain pattern or for a certain time duration or period and automatically switch back after a certain time instance. In addition or as an alternative, the control signalling giving the resource assignment may be handled solely in the aggregated carrier. Nevertheless, there may be implicit and / or explicit signalling, which may indicate to the UE, where to blind decode resource maps. For example, the UE may automatically switch back to its base carrier, e.g., in case there is an explicit signalling, after a timeout, or after reception and / or transmission of a certain number of data symbols within the SBFD part of the aggregated carrier. This fallback to a base carrier can be done immediately, or it may be done after a certain number of transmissions on the aggregated band or after a timeout. By doing this, certain transmissions or receptions on the base carrier may be skipped, and thus, the power consumption of the UE, e.g., by not performing blind decodes, may be reduced.

[0425] In Fig. 8b there is shown that from UL slot 436i ,1 of the base carrier the device may continue with the UL part 448i of SBFD slot 3142,2 of the aggregated carrier and subsequently the UL resources of the aggregated carrier may be used, e.g., within the aggregated carrier such as 4362,3 and thereafter the UL part 4482 of SBFD slot 3142,4. Alternatively or in addition, after the UL part 448i the device may switch to UL slot 436i,s, in both cases UL slot 436I,3 may be skipped.

[0426] Further, the symbols, e.g., SBFD symbols 3142,2 and / or 3142,4, in the aggregated band can be used for boosting the UL and / or DL capacity as described in connection with Fig. 7. Nevertheless, these additional symbols can also be utilized for redundancy transmissions, e.g., data duplication or different redundancy versions, or for transmission of certain control and / or data traffic having special transmission requirements, e.g., control data, feedback data, small data.2025F68137 - 25014 53

[0427] In a further embodiment, that may be combined with the other embodiments without significant modifications, TDD carriers 312i and 3122 used within the aggregation may be shifted in time domain by a time offset 452 as shown in Fig. 9b. This may be configured in such a way, that a UE could basically perform a full duplex communication, e.g., the link direction in the aggregated carrier 3122 is in some or every time instance configured with the opposite link direction as shown in Fig. 9a. In these cases, a UE may perform a continuous UL and / or DL transmission when using the aggregated bands. Nevertheless, in case one of the carriers supports SBFD, it may still either boost its capacity, e.g., by allocating an UL band with a UL SBFD subband, or, it may still utilize the DL part of an SBFD slot 314i ,2 and / or 314i ,4 together with a UL band in its base carrier to perform a full duplex transmission. In a preferred embodiment, both carriers are separated such that the interference of a DL carrier does no saturated the UL receiver. This may be realized in case of sufficient separation in frequency or spatial domains, e.g., by using advanced beamforming techniques. For example, in 6G systems, in case one of the carriers is operated in a totally different frequency band, e.g., FR3, this may still be realized without any special filtering techniques. A possible configuration is part of Fig. 9a.

[0428] In a variant thereof shown in Fig. 9b, forming an embodiment of the present invention, the carriers are shifted in time domain, e.g., by the offset value 452, e.g., the synchronization is not perfect. Still in this case, it may be beneficial to utilize different link directions using SBFD symbols 314I,2 and / or 314I,4. The DL part which may cause unwanted interference to the base carrier could be blanked or punctured out, by the transmitter, such that the aggregation still gives a benefit to the overall system performance, e.g., high data rate at a said UE or a higher reliability at the said UE. The blanking or puncturing may only degrade the DL performance in a certain way, that it can be negligible if only done for a small portion of the DL band and / or subbands. The offset may lead to puncture DL resources, e.g., of SBFD symbol 314I,2 by uplink resources, e.g., of the other carrier 3122. Such puncturing may refer to a technique used in channel coding where certain coded bits are intentionally removed or not transmitted to adjust the effective code rate. Some bits from the encoded sequence may be deleted, e.g., according to a pattern. The receiver may know the pattern and may treat missing bits as erased / unknown.

[0429] 3.1.3 TDD / SUL / TDD / SDL

[0430] Embodiments further relate to a use of supplementary uplink, SUL, and / or a use of supplementary downlink, SDL.2025F68137 - 25014 54

[0431] An idea underlying SUL is that usually cell coverage in UL direction is lower than DL direction because UE transmit power (UL power) is not as strong as gNB transmit power (DL power). As an alternative or in addition, the performance degradation on UL direction due to this difference gets significant as the UE approaches the cell edge. As a possible solution, an idea to use a lower frequency as compared to the original UL frequency is proposed, as cell coverage may increase as the frequency gets lower. To use a secondary UL at much lower frequency is an idea behind SUL. When the channel condition is good, the network or a base station may instruct the device, e.g., a UE, to use the original UL frequency and when the channel condition degrades based on a certain criteria, the network or base station may direct the device to use the secondary (supplementary) UL frequency. Another motivation of SUL may be to improve the coverage by easing the UL power restriction in high frequency bands as described for SUL, but in view of improving the utilization of spectrum resources which has been under-utilized.

[0432] On the other hand, forming an alternative or an addition to SUL, supplementary downlink, SDL, may be based on a different motivation when compared to SUL. SDL can be used to increase coverage and / or capacity in the downlink, which may be required if data traffic is unsymmetric, e.g., which may result in case user devices are downloading a large amount of data.

[0433] A device according to an embodiment may be adapted for using the first carrier as a time division duplex, TDD, carrier and for using the second carrier as a supplemental uplink carrier, SUL, carrier.

[0434] A device according to an embodiment may be adapted for using the first carrier as a time division duplex, TDD, carrier and for using the second carrier as a supplemental downlink carrier, SDL, carrier.

[0435] A device according to an embodiment may be adapted for using the first carrier as a frequency division duplex, FDD, carrier and for using the second carrier as supplemental uplink carrier, SUL, carrier.

[0436] A device according to an embodiment may be adapted for using the second part as an uplink part paired with a downlink band of the first carrier.

[0437] A device according to an embodiment may be adapted to use the first carrier (FDD) to form a base carrier and to use the second carrier to perform a boost in the UL direction.2025F68137 - 25014 55

[0438] A device according to an embodiment may be adapted for using the first carrier as a frequency division duplex, FDD, carrier and for using the second carrier as a supplementary downlink, SDL, carrier.

[0439] A device according to an embodiment may be adapted for using the second part as a downlink part paired with an uplink band of the first carrier.

[0440] A device according to an embodiment may be adapted to use the first carrier (FDD) to form a base carrier and to use the second carrier to perform a boost in the DL direction.

[0441] 3.2 Switching Delays

[0442] In CA scenarios including SBFD symbols, there may be a requirement to introduce additional gaps or guards between UL and DL direction. When referring to Fig. 10a and Fig. 10b, these gaps 462i and 4622 in time domain and / or frequency domain may be used or even required for switching between UL and DL transmission, e.g., reconfiguration of analog components of a UE, e.g., power amplifiers, PAs, or filters. Gaps 462i and / or 4622 or guards may be defined in terms of symbols or slots or half slots etc. Furthermore, the gaps 462i and / or 4622 and / or guards may be defined within the global configuration, or may be assumed according to a particular SBFD slot configuration. For example, a setting that can be configured / pre-configured can be signalled as in the embodiments described herein.

[0443] In addition or as an alternative, gaps 462i and / or 4622 may be configured over the whole frequency range of a carrier 312i or 3122, or may only be defined for certain subbands, within the frequency range of a carrier. Gaps 462i and / or 4622 may be configured on one of the carriers 312i or 3122, e.g., the carrier containing the SBFD slot, or on the carrier having no SBFD slot, or on both carriers. Finally, these gaps 462i and / or 4622 or guards may be used or required in case of same or different radio characteristics apply to the different carriers used for CA. This may be advantageous if the communication technology used for the different carriers is asymmetric, e.g., one of the carriers operated a terrestrial communication system, while the other one utilized non-terrestrial networks, NTN, e.g., satellite communication.

[0444] Radio characteristics can be based on the configuration of the wireless communication system, e.g., one or more of the propagation delay, the timing advance, TA, the processing delay, e.g., the processing can be done on the base station, e.g., regenerative payload within NTN, or within a base station on the ground, e.g., bent-pipe satellite. As an alternative or in addition, this may also depend on or be based on measurements of the radio characteristics, which may2025F68137 - 25014 56

[0445] be reported by a UE. For this, the UE can measure, channel state information, CSI, e.g., RSRP, RSRQ, RSSI, delays, path strengths, and feed this back to a base station or core network, CN.

[0446] NTN may suffer from long delays, since radio propagation is much larger, when compared to communication with a base station on the ground. This may result from the distance of the NTN from the earth, which may be a NTN device operating in a LEO or GEO or low-orbit constellation, or may be a high altitude platform, HAPS, or a an air plane. Thus, in scenarios described above, it may be required to have different gaps or guards in the different carriers, which also impacts in case SBFD is configured for one of the carriers, e.g., the reference cell or the another cell.

[0447] 3.3 UE Behavior - Collision Handling Rules

[0448] According to some embodiments, a slot format may include ‘downlink’ symbols, ‘uplink’ symbols, and / or ‘flexible’ symbols. For example, in a slot in a downlink frame, the UE may assume that downlink transmissions only occur in ‘downlink’ or ‘flexible’ symbols. That is the UE may be configured accordingly. In a slot in an uplink frame, the UE shall only transmit in ‘uplink’ or ‘flexible’ symbols.

[0449] According to embodiments, any cell can be configured with subband full duplex (SBFD). Hence, the symbol in the reference cell or any other cell can be an SBFD symbol as well. According to embodiments, the definition of the reference symbol can be updated to include:

[0450] Where the symbol is configured as

[0451] • downlink, or uplink, as indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL- ConfigurationDedicated,

[0452] • uplink, if the symbol is flexible / SBFD and the UE is configured to transmit SRS, PUCCH, PUSCH, or PRACH on the symbol,

[0453] • downlink, if the symbol is flexible / SBFD and the UE is configured to receive PDCCH, PDSCH or CSI-RS on the Symbol,

[0454] • SBFD, as indicated.

[0455] This symbol may be a downlink or flexible symbol which is converted to an SBFD symbol. For example, the TDD common configuration configures the symbol to be downlink and then the SBFD configuration indicates that it is an SBFD symbol or the TDD common configuration configures the symbol to be a flexible symbol, and the SBFD configuration indicated that it is an SBFD symbol.2025F68137 - 25014 57

[0456] The UE behavior in general may be based if certain conditions are satisfied. Some examples of this are listed hereinafter:

[0457] • A cell with SBFD configuration cannot be a reference cell. The smallest cell index nearest to the cell index of the cell with SBFD configuration is chosen.

[0458] o This may be based on a capability. For example, if the UE is capable of handling reference cells with SBFD, then having a reference cell with SBFD configuration is allowed otherwise not.

[0459] • A cell with SBFD configuration can only be a reference cell if all uplink / downlink or certain defined uplink / downlink link directions are with Configuration 1. Also, e.g., if valid symbol type is non-SBFD, then this is allowed. Configuration 1 means that all transmissions and / or receptions are confined to only one symbol type: the valid symbol type which can be SBFD or non-SBFD. This feature can also be based on the UE capability.

[0460] • A cell with SBFD configuration can only be a part of CA if all uplink / downlink or certain defined uplink / downlink link directions are with Configuration 1. Also, e.g., if valid symbol type is non-SBFD, then this is allowed. Configuration 1 means that all transmissions and / or receptions are confined to only one symbol type: the valid symbol type which can be SBFD or non-SBFD. This feature can also be based on the UE capability.

[0461] • The existing rules for collision handling in a CA scenario as described above apply, in some embodiments, for all or certain signals / channels in the reference cell or any other cell with SBFD configuration if they are configured with Configuration 1 and valid symbol type as non-SBFD.

[0462] • The existing rules for collision handling in a CA scenario as described above apply, according to some embodiments, for non-SBFD symbols in a reference cell and / or other cells, e.g., the another cell.

[0463] • SBFD symbols on a reference cell and / or other cells are considered, according to some embodiments, equivalent to flexible symbols.

[0464] o Existing UE behavior for flexible symbols from the existing rules for collision handling in a CA scenario as described herein may apply to SBFD symbols. For2025F68137 - 25014 58

[0465] example the UE does not expect to be configured by higher layers to receive PDCCH, PDSCH, or CSI-RS on a flexible symbol / SBFD symbol on the reference cell and to detect a DCI format scheduling a transmission on the symbol on another cell, if another cell among the cells configured with directionalCollisionHandling-r16 operates in the same frequency band as the reference cell.

[0466] • The UE may be configured to receive and process link directions indicating uplink / downlink for SBFD symbols in reference cells or other cells.

[0467] o The link directions provided can be semi-static or dynamic.

[0468] o The existing rules for collision handling in CA scenario apply considering the uplink / downlink and semi-static / dynamic link direction in the SBFD symbols.

[0469] • A cell with SBFD configuration can, according to configurations within some embodiments, only be a part of CA if all uplink / downlink or certain defined uplink / downlink link directions are with Configuration 1. Also, e.g., if valid symbol type is non-SBFD, then this is allowed. Configuration 1 means that all transmissions and / or receptions are confined to only one symbol type: the valid symbol type which can be SBFD or non-SBFD. This feature can also be based on UE capability.

[0470] • If the reference symbol is SBFD, downlink / uplink in the reference symbol and uplink / downlink in another cell respectively are not allowed / expected, according to some embodiments. For example, if another cell among the cells configured with directionalCollisionHandling-r16 operates in the same I different band or frequency resources as the reference cell. Also, this behavior can be based on a UE capability. E.g., if the UE is not capable of handling downlink receptions in the reference symbol and uplink transmissions in another cell for a given set of conditions. Given hereinafter some more examples with details are provided:

[0471] o A symbol to be indicated as SBFD or downlink + SBFD or flexible + SBFD on the reference cell and as at least one of uplink or flexible or downlink on another cell respectively. E.g., if another cell among the cells configured with directionalCollisionHandling-r16 operates in the same band as the reference cell:

[0472] ■ The uplink or downlink or flexible can be indicated by tdd-UL-DL- ConfigurationCommon, by tdd-UL-DL-ConfigurationDedicated, DCI, SFI, MAC CE, scheduling of uplink / downlink signals / channels e.g.,2025F68137 - 25014 59

[0473] semi-static scheduling of PDCCH, CSI-RS, PDSCH, PUCCH, PRACH, SRS, PUSCH etc.

[0474] ■ Downlink + SBFD means that the symbol is indicated as downlink by TDD common configuration and also indicated as SBFD. flexible + SBFD means that the symbol is indicated as flexible by TDD common configuration and also indicated as SBFD.

[0475] o A symbol to be indicated as SBFD or downlink + SBFD or flexible + SBFD and to be configured semi-statically or dynamically as downlink / uplink on the reference cell and as uplink / downlink on another cell respectively. E.g., if another cell among the cells configured with directionalCollisionHandling-r16 operates in the same band as the reference cell.

[0476] ■ The uplink / downlink on the another cell / reference cell can be semi- static / dynamic configuration or both.

[0477] ■ For semi-static downlink configuration of the reference cell / another cell, the indication can be using any RRC or MAC CE, or tdd-UL-DL- ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, or a downlink signal / channel semi-statically configured, e.g., semi-static scheduling of PDCCH, CSI-RS, PDSCH, etc. or a link direction signal indicating downlink reception.

[0478] ■ For semi-static uplink configuration of the reference cell / another cell, the indication can be using RRC or MAC CE, or tdd-UL-DL- ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, or an uplink signal / channel semi-statically configured, e.g., semi-static scheduling of PUCCH, SRS, PUSCH, PRACH etc. or a link direction signal indicating uplink transmission.

[0479] ■ For dynamic configuration of the reference cell / another cell, it can be using SFI, DCI, dynamic link direction signal etc.

[0480] o The same set of rules can be followed if the symbol in the another cell is SBFD and the reference cell is not configured with SBFD.

[0481] • Downlink receptions in the reference symbol (SBFD symbol) are allowed or expected, according to some embodiments, in only one downlink subband when uplink transmissions in another cell are configured semi-statically or dynamically. For example, if another cell among the cells configured with directionalCollisionHandling- r16 operates in the same I different band as the reference cell. Also, this behavior can be based on a UE capability. This may relate to a situation when the cell has more than one downlink subband. Further, the choice of which downlink subband can be based2025F68137 - 25014 60

[0482] on various factors or at least one criterion. E.g., the downlink subband which will be least interfered at the UE side from the other aggregated carriers is used for reception. The criterion can be measured by a UE, according to one or more of: an interference level, e.g., SI NR, SIR, RSRQ, etc.; am interference level is below a configured and / or pre-configured threshold and / or among several subbands, the selected subband has the smallest interference level. The uplink / downlink on the another cell / reference cell can be semi-static / dynamic configuration or both. For semi-static downlink configuration of the reference cell / another cell, the indication can be using any RRC or MAC CE, or tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL- ConfigurationDedicated, or a downlink signal / channel semi-statically configured, e.g., semi-static scheduling of PDCCH, CSI-RS, PDSCH, etc. or a link direction signal indicating downlink reception. For semi-static uplink configuration of the reference cell / another cell, the indication can be using RRC or MAC CE, or tdd-UL-DL- ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, or an uplink signal / channel semi-statically configured, e.g., semi-static scheduling of PUCCH, SRS, PUSCH etc. or a link direction signal indicating uplink transmission. For dynamic configuration of the reference cell / another cell, it can be using SFI, DCI, dynamic link direction signal etc. The same set of rules can be followed if the symbol in the another cell is SBFD and the reference cell is not configured with SBFD.

[0483] • If the reference symbol is SBFD, uplink transmissions in the reference symbol and downlink receptions in another cell are allowed / expected based on special conditions for uplink transmissions, according to some embodiments. Examples of special conditions are:

[0484] o when the uplink transmission is restricted to an uplink subband

[0485] o when the uplink transmission is restricted to an uplink subband in between 2 downlink subbands

[0486] For example, if another cell among the cells configured with directionalCollisionHandling-r16 operates in the same I different band as the reference cell. Also, this behavior can be based on a UE capability. The uplink / downlink on the another cell / reference cell can be semi-static / dynamic configuration or both. For semistatic downlink configuration of the reference cell / another cell, the indication can be using any RRC or MAC CE, or tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL- ConfigurationDedicated, or a downlink signal / channel semi-statically configured, e.g., semi-static scheduling of PDCCH, CSI-RS, PDSCH, etc. or a link direction signal indicating downlink reception. For semi-static uplink configuration of the reference2025F68137 - 25014 61

[0487] cell / another cell, the indication can be using RRC or MAC CE, or tdd-UL-DL- ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, or an uplink signal / channel semi-statically configured, e.g., semi-static scheduling of PLICCH, SRS, PLISCH etc. or a link direction signal indicating uplink transmission. For dynamic configuration of the reference cell / another cell, it can be using SFI, DCI, dynamic link direction signal etc. The same set of rules can be followed if the symbol in the another cell is SBFD and the reference cell is not configured with SBFD.

[0488] • The UE according to some embodiments is adapted to not expect a symbol to be indicated as only downlink (not SBFD) on the reference cell which has SBFD configuration and uplink on another cell, respectively, by tdd-UL-DL- ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated. E.g., If another cell among the cells configured with directionalCollisionHandling-r16 operates in the same band as the reference cell.

[0489] • The UE according to some embodiments is adapted to not expect a symbol to be indicated as uplink on the reference cell and only downlink (not SBFD) on another cell, which has SBFD configuration respectively, by tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated. E.g., If another cell among the cells configured with directionalCollisionHandling-r16 operates in the same band as the reference cell.

[0490] • The UE according to some embodiments is adapted to transmit a signal / channel scheduled by a DCI format on a symbol of another cell where the transmissions are within the uplink subband of an SBFD symbol when the symbol is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for the reference cell. E.g., If the reference cell and another cell among the cells configured with directionalCollisionHandling-r16 operate in different frequency bands.

[0491] • The UE according to some embodiments is adapted to transmit a signal / channel scheduled by a DCI format on a symbol of another cell where the transmissions are in an only uplink symbol when the symbol is indicated as downlink by tdd-UL-DL- ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for the reference cell. E.g., If the reference cell and another cell among the cells configured with directionalCollisionHandling-r16 operate in different frequency bands.

[0492] • The UE according to some embodiments is adapted to transmit a signal / channel scheduled by a DCI format on a symbol of another cell when the symbol is indicated2025F68137 - 25014 62

[0493] as only downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL- ConfigurationDedicated for the reference cell configured with SBFD. E.g., If the reference cell and another cell among the cells configured with directionalCollisionHandling-r16 operate in different frequency bands.

[0494] • The UE according to some embodiments is adapted to transmit a signal / channel scheduled by a DCI format on a symbol of another cell when the symbol is indicated as SBFD for the reference cell configured with SBFD. E.g., If the reference cell and another cell among the cells configured with directionalCollisionHandling-r16 operate in different frequency bands.

[0495] o The symbol indicated as SBFD may have semi-static downlink configuration using any RRC or MAC CE, or tdd-UL-DL-ConfigurationCommon or by tdd-UL- DL-ConfigurationDedicated, or a downlink signal / channel semi-statically configured, e.g., semi-static scheduling of PDCCH, CSI-RS, PDSCH, etc. or a link direction signal indicating downlink reception.

[0496] o The symbol indicated as SBFD may have dynamic downlink configuration using SFI, DCI, dynamic link direction signal etc.

[0497] • The UE according to some embodiments is not required to receive a higher layer configured PDCCH, PDSCH, or CSI-RS on flexible / SBFD symbols on the reference cell in a set of symbols, if the UE detects a DCI format scheduling a transmission on one or more symbols in the set of symbols on another cell. E.g., If the reference cell and another cell among the cells configured with directionalCollisionHandling-r16 operate in different frequency bands.

[0498] • The UE according to some embodiments is not required to receive a higher layer configured PDCCH, PDSCH, or CSI-RS on flexible symbols on the reference cell in a set of symbols, if the UE detects a DCI format scheduling a transmission on one or more symbols in the set of symbols on another cell where the one or more symbols are non-SBFD. E.g., If the reference cell and another cell among the cells configured with directionalCollisionHandling-r16 operate in different frequency bands.

[0499] • The UE according to some embodiments is not required to receive a higher layer configured PDCCH, PDSCH, or CSI-RS on flexible symbols on the reference cell in a set of symbols, if the UE detects a DCI format scheduling a transmission on one or more symbols in the set of symbols on another cell where the one or more symbols are2025F68137 - 25014 63

[0500] SBFD symbols. E.g., If the reference cell and another cell among the cells configured with directionalCollisionHandling-r16 operate in different frequency bands.

[0501] • The UE according to some embodiments is adapted to assume symbol as flexible / SBFD, is not required to receive higher layer configured PDCCH, PDSCH, or CSI-RS and not expected to transmit higher layer configured SRS, PUCCH, PUSCH, or PRACH, when tdd-UL-DLConfigurationCommon or tdd-UL-DL- ConfigurationDedicated indicates symbol as downlink or uplink on another cell and as uplink or downlink for the reference cell, respectively.

[0502] o The symbol is indicated as SBFD; or as downlink + SBFD; or as flexible + SBFD and may be configured semi-statically or dynamically as downlink / uplink on the reference cell and as uplink / downlink on another cell respectively

[0503] ■ The uplink / downlink on the another cell / reference cell can be semi- static / dynamic configuration or both.

[0504] ■ For semi-static downlink configuration of the reference cell / another cell, the indication can be using any RRC or MAC CE, or a downlink signal / channel semi-statically configured, e.g., semi-static scheduling of PDCCH, CSI-RS, PDSCH, etc or a link direction signal indicating downlink reception.

[0505] ■ For semi-static uplink configuration of the reference cell / another cell, the indication can be using RRC or MAC CE, or an uplink signal / channel semi-statically configured, e.g., semi-static scheduling of PUCCH, SRS, PUSCH, PRACH etc or a link direction signal indicating uplink transmission.

[0506] ■ For dynamic configuration of the reference cell / another cell, it can be using SFI, DCI, dynamic link direction signal etc.

[0507] ■ The SBFD symbol has downlink configured on both its downlink subbands or only one subband.

[0508] ■ The SBFD symbol with uplink subband with a certain configuration. E.g., the configuration is DU / UD.

[0509] o The symbol is a non-SBFD symbol only.

[0510] o The same set of rules can be followed if the symbol in the another cell is SBFD and the reference cell is not configured with SBFD.

[0511] The UE according to some embodiments is adapted to not transmit a PLICCH, PLISCH, SRS or PRACH that is configured by higher layers on a set of symbols on another cell2025F68137 - 25014 64

[0512] if at least one symbol from the set of symbols is indicated as downlink by tdd-UL- DLConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and non-SBFD or is a symbol corresponding to a PDCCH, PDSCH, or CSI-RS reception that is configured by higher layers or an SBFD symbol on the reference cell.

[0513] o The SBFD symbol is further configured with a link direction signal indicating downlink reception or dynamically configured using SFI, DCI, dynamic link direction signal etc. fordownlink.

[0514] o The SBFD symbol has downlink configured on both its downlink subbands.

[0515] • The UE according to some embodiments is adapted to not transmit a PLICCH, PLISCH, SRS or PRACH that is configured by higher layers on a set of symbols on another cell if at least one symbol from the set of symbols is indicated as downlink by tdd-UL- DLConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or is a symbol corresponding to a PDCCH, PDSCH, or CSI-RS reception that is configured by higher layers on the reference cell.

[0516] o If at least one symbol on another cell is a non-SBFD symbol,

[0517] o If at least one symbol on another cell is an SBFD symbol,

[0518] o If at least one symbol on another cell is an SBFD symbol with uplink subband with a certain configuration. E.g., the configuration is Dll / UD.

[0519] • The UE according to some embodiments is adapted to not receive or process a PDCCH, PDSCH or CSI-RS that is configured by higher layers on a set of symbols on another cell if at least one symbol from the set of symbols is indicated as uplink by tdd- UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or is a symbol corresponding to a SRS, or an SBFD symbol, or PUCCH, PUSCH, or PRACH transmission that is configured by higher layers on the reference cell.

[0520] o The SBFD symbol is further configured with a link direction signal indicating uplink reception or dynamically configured using SFI, DCI, dynamic link direction signal etc. for uplink.

[0521] o SBFD symbol with uplink subband with a certain configuration. E.g., the configuration is DU / UD.

[0522] • The UE according to some embodiments is adapted to not receive or process a PDCCH, PDSCH or CSI-RS that is configured by higher layers on a set of symbols on another cell if at least one symbol from the set of symbols is indicated as uplink by tdd- UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or is a symbol2025F68137 - 25014 65

[0523] corresponding to a SRS, or PLICCH, PLISCH, or PRACH transmission that is configured by higher layers on the reference cell:

[0524] o If at least one symbol on another cell is a non-SBFD symbol

[0525] o If at least one symbol on another cell is an SBFD symbol

[0526] o If at least one symbol on another cell is an SBFD symbol with downlink subband with a certain configuration. E.g., the configuration is Dll / UD or reception is allowed on both the downlink subbands as in DUD configuration.

[0527] • The UE according to some embodiments is adapted to assume a symbol indicated as downlink or uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL- DLConfigurationDedicated on another cell to be flexible, if the UE is respectively configured by higher layers to transmit SRS, PUCCH, PUSCH, or PRACH or to receive PDCCH, PDSCH, or CSI-RS on the reference cell.

[0528] o The transmission / reception is configured on an SBFD symbol of the reference cell:

[0529] ■ The reception is configured in only one downlink subband,

[0530] ■ The reception is configured in both the downlink subbands,

[0531] ■ The transmission is within an uplink subband,

[0532] • Further depends on the type of configuration like DU / UD / DUD o The transmission / reception is configured on a non-SBFD symbol of the reference cell.

[0533] • The UE according to some embodiments is adapted to assume a symbol indicated as downlink or uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL- DLConfigurationDedicated on another cell to be flexible or SBFD if SBFD is configured on the another cell, if the UE is respectively configured by higher layers to transmit SRS, PUCCH, PUSCH, or PRACH or to receive PDCCH, PDSCH, or CSI-RS on the reference cell.

[0534] o SBFD is considered only if the symbol is indicated as downlink.

[0535] • The UE according to some embodiments is adapted to not expect to detect a first DCI format scheduling a transmission or reception on a symbol on a first cell and a second DCI format scheduling a reception or transmission on the symbol on a second cell, respectively.

[0536] In NR, certain uplink and downlink collision handling rules have been agreed within an SBFD carrier based on a broad category of cases. The cases may relate to:2025F68137 - 25014 66

[0537] Collision handling cases within an SBFD carrier:

[0538] o Case 1: Dynamically scheduled DL reception vs. semi-statically configured UL transmission

[0539] e.g., dynamic PDSCH or CSI-RS collides with configured SRS, PLICCH, or CG PUSCH

[0540] o Case 2: Semi-statically configured DL reception vs. dynamically scheduled UL transmission

[0541] e.g., PDCCH or SPS PDSCH collides with dynamic PUSCH or PUCCH o Case 3: Semi-statically configured DL reception vs. semi-statically configured UL transmission

[0542] o Case 4: Dynamically scheduled DL reception vs. dynamic scheduled UL transmission o Case 5: SSB vs. dynamically scheduled or configured UL transmission

[0543] - e.g., PUSCH, PUCCH, PRACH, SRS

[0544] o Case 6: Dynamic or semi-static DL vs. valid RACH occasion, RO

[0545] The above set of cases are defined for collision handling within an SBFD carrier. These cases can be extended to CA where the uplink and downlink will be across different carriers where at least one carrier can have an SBFD configuration. For example, there is dynamically scheduled DL reception on one carrier and semi-statically configured UL on another carrier. The carrier can be a reference carrier as well.

[0546] The known rules for flexible symbols in NR specification 3GPP TS 38.213 V18.5.0 (2024-12) are the following:

[0547] For a set of symbols of a slot indicated to a UE as flexible by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicatedtf provided, or when tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the UE, and if the UE detects a DCI format 2_0 providing a format for the slot using a slot format value other than 255 - if one or more symbols from the set of symbols are symbols in a CORESET configured to the UE for PDCCH monitoring, the UE receives PDCCH in the CORESET only if an SFI-index field value in DCI format 2_0 indicates that the one or more symbols are downlink symbols

[0548] - if an SFI-index field value in DCI format 2_0 indicates the set of symbols of the slot as flexible and the UE detects a DCI format indicating to the UE to receive PDSCH or CSI-2025F68137 - 25014 67

[0549] RS in the set of symbols of the slot, the UE receives PDSCH or CSI-RS in the set of symbols of the slot

[0550] - if an SFI-index field value in DCI format 2_0 indicates the set of symbols of the slot as flexible and the UE detects a DCI format, a RAR UL grant, fallbackRAR UL grant, or successRAR indicating to the UE to transmit PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot the UE transmits the PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot

[0551] - if an SFI-index field value in DCI format 2_0 indicates the set of symbols of the slot as flexible, and the UE does not detect a DCI format indicating to the UE to receive PDSCH or CSI-RS, or the UE does not detect a DCI format, a RAR UL grant, fallbackRAR UL grant, or successRAR indicating to the UE to transmit PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot, the UE does not transmit or receive in the set of symbols of the slot

[0552] - if the UE is configured by higher layers to receive PDSCH or CSI-RS in the set of symbols of the slot, the UE receives the PDSCH or the CSI-RS in the set of symbols of the slot only if an SFI-index field value in DCI format 2_0 indicates the set of symbols of the slot as downlink and, if applicable, the set of symbols is within remaining channel occupancy duration

[0553] - if the UE is configured by higher layers to receive DL PRS in the set of symbols of the slot, the UE receives the DL PRS in the set of symbols of the slot only if an SFI-index field value in DCI format 2_0 indicates the set of symbols of the slot as downlink or flexible.

[0554] - if the UE is configured by higher layers to transmit PUCCH, or PUSCH, or PRACH in the set of symbols of the slot, the UE transmits the PUCCH, or the PUSCH, or the PRACH in the slot only if an SFI-index field value in DCI format 2_0 indicates the set of symbols of the slot as uplink

[0555] - if the UE is configured by higher layers to transmit SRS in the set of symbols of the slot, the UE transmits the SRS only in a subset of symbols from the set of symbols of the slot indicated as uplink symbols by an SFI-index field value in DCI format 2_0 - a UE does not expect to detect an SFI-index field value in DCI format 2_0 indicating the set of symbols of the slot as downlink and also detect a DCI format, a RAR UL grant, fallbackRAR UL grant, or successRAR indicating to the UE to transmit SRS, PUSCH, PUCCH, or PRACH, in one or more symbols from the set of symbols of the slot2025F68137 - 25014 68

[0556] - a UE does not expect to detect an SFI-index field value in DCI format 2_0 indicating the set of symbols of the slot as downlink or flexible if the set of symbols of the slot includes symbols corresponding to any repetition of a PLISCH transmission activated by an UL Type 2 grant PDCCH as described in clause 10.2

[0557] - a UE does not expect to detect an SFI-index field value in DCI format 2_0 indicating the set of symbols of the slot as uplink and also detect a DCI format indicating to the UE to receive PDSCH or CSI-RS in one or more symbols from the set of symbols of the slot

[0558] With the above extract from TS 38.213 V18.5.0 (2024-12) as a background, a UE according to embodiments, may assume that flexible symbols in a CORESET configured to the UE for PDCCH monitoring are downlink symbols if the UE does not detect an SFI-index field value in DCI format 2_0 indicating the set of symbols of the slot as flexible or uplink and the UE does not detect a DCI format indicating to the UE to transmit SRS, PUSCH, PUCCH, or PRACH in the set of symbols.

[0559] For a set of symbols of a slot that are indicated as flexible by tdd-UL-DL-ConfigurationCommon, and tdd-UL-DL-ConfigurationDedicated if provided, or when tdd-UL-DL-ConfigurationCommon, and tdd-UL-DL-ConfigurationDedicated are not provided to the UE, and if the UE does not detect a DCI format 2_0 providing a slot format for the slot

[0560] - the UE may receive PDSCH or CSI-RS in the set of symbols of the slot if the UE receives a corresponding indication by a DCI format

[0561] - the UE may transmit PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot if the UE receives a corresponding indication by a DCI format, a RAR UL grant, fallbackRAR UL grant, or successRAR

[0562] - the UE may receive PDCCH as described in clause 10.1 of TS38.213 V18.5.0 (2024- 12).

[0563] - if the UE is configured by higher layers to receive PDSCH in the set of symbols of the slot, the UE does not receive the PDSCH in the set of symbols of the slot

[0564] - if the UE is configured by higher layers to receive CSI-RS in the set of symbols of the slot, the UE may be adapted to not receive the CSI-RS in the set of symbols of the slot, except when UE is provided CO-DurationsPerCell and the set of symbols of the slot are within the remaining channel occupancy duration.2025F68137 - 25014 69

[0565] if the UE is configured by higher layers to receive DL PRS in the set of symbols of the slot, the UE may receive the DL PRS

[0566] - if the UE is configured by higher layers to transmit SRS, or PUCCH, or PUSCH, or PRACH in the set of symbols of the slot and the UE is not provided enableConfiguredUL, then

[0567] - if the UE does not indicate the capability of [partialCancellation], the UE does not expect to cancel the transmission of the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS 38.214], as determined in clauses 9, 9.2.5 and 9.2.6 or in clause 6.1 of [6. TS 38.214], or the PRACH in the slot if the first symbol of the PUCCH or the PUSCH or actual repetition of the PUSCH or the PRACH in the slot occurs within TprOc,2 relative to a last symbol of a PDCCH reception where the UE is configured to monitor PDCCH for DCI format 2_0; otherwise, the UE cancels the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS 38.214], as determined in clauses 9, 9.2.5 and 9.2.6 or in clause 6.1 of [6. TS 38.214], or the PRACH in the slot;

[0568] - PUSCH transmission(s) can be dynamically scheduled by an UL grant in a DCI, or configured grant, CG, Type 1 or Type 2, or repetition of dynamic PUSCH, CG, scheduling of multiple PUSCH by single DCI, PUSCH over multiple slots with same transport block. A UE can have resources for PUCCH transmissions or for PUCCH and PUSCH transmissions that overlap in time and each PUCCH transmission is over a single slot without repetitions or PUCCH repetitions over multiple slots.

[0569] - if the UE indicates the capability of [partialCancellation], the UE does not expect to cancel the transmission of the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS 38.214], as determined in clauses 9, 9.2.5 and 9.2.6 or in clause 6.1 of [6. TS 38.214], or the PRACH in symbols from the set of symbols that occur within Tproc 2relative to a last symbol of a PDCCH reception where the UE is configured to monitor PDCCH for DCI format 2_0. The UE cancels the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS 38.214], as determined in clauses 9, 9.2.5 and 9.2.6 or in clause 6.1 of [6. TS 38.214], or the PRACH transmission in remaining symbols from the set of symbols;

[0570] - the UE does not expect to cancel the transmission of SRS in symbols from the set of symbols that occur within Tproc 2relative to a last symbol of a PDCCH reception where the UE is configured to monitor PDCCH for DCI format 2_0. The UE cancels the SRS transmission in remaining symbols from the set of symbols;2025F68137 - 25014 70

[0571] - ^proc,2 is the PUSCH preparation time for the corresponding UE processing capability [6, TS 38.214] assuming d2,i = 1 and A corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH carrying the DCI format 2_0 and the SCS configuration of the

[0572]

[0573] corresponds to the SCS configuration of the PRACH if it is 15kHz or higher; otherwise .r= 0;

[0574] - if the UE is configured by higher layers to transmit SRS, or PUCCH, or PUSCH, or PRACH in the set of symbols of the slot and the UE is provided enableConfiguredUL, the UE can transmit the SRS, or PUCCH, or PUSCH, or PRACH, respectively.

[0575] Note that [6, TS 38.214], may refer to TS 38.214 V18.5.0 (2024-12).

[0576] Based on these cases, the UE behavior according to embodiments can be defined as follows:

[0577] Case 1 :

[0578] • Dynamically scheduled DL reception and semi-statically configured UL transmission are not expected by the UE. E.g., when the carriers are within the same band

[0579] • Dynamically scheduled DL reception and semi-statically configured UL transmission are expected and allowed

[0580] o Reuse the existing collision handling principles and timeline in NR for operation on flexible symbols on a single carrier in unpaired spectrum, i.e. UL transmission is cancelled if cancellation timeline is met. E.g., the carriers are in different bands. The same rules apply if there is any repetition.

[0581] o DL receptions are allowed only in certain cases. E.g., within DL subbands, within non-SBFD symbols, within only SBFD symbols etc.

[0582] o UL transmissions are allowed only in certain cases. E.g., only with non-SBFD symbols, within UL subbands in DU / UD / DUD configurations etc.

[0583] Case 2:

[0584] • Semi-statically configured DL reception and dynamically scheduled UL transmission are not expected by the UE. E.g., when the carriers are within the same band

[0585] • Semi-statically configured DL reception and dynamically scheduled UL transmission are expected and allowed

[0586] o reuse the existing collision handling principles in NR for operation on flexible symbols on a single carrier in unpaired spectrum, i.e. UE does not receive DL2025F68137 - 25014 71

[0587] channel / signal. E.g., the carriers are in different bands. The same rules apply if there is any repetition.

[0588] o DL receptions are allowed only in certain cases. E.g., within DL subbands, within non-SBFD symbols, within only SBFD symbols etc.

[0589] o UL transmissions are allowed only in certain cases. E.g., only with non-SBFD symbols, within UL subbands in DU / UD / DUD configurations etc.

[0590] Case 3:

[0591] • Collision Case 3 (semi-statically configured DL reception vs. semi-statically configured UL transmission) is an error case. E.g., irrespective of whether the carriers are in same or different bands.

[0592] o A UE does not expect to receive both dedicated higher layer parameters configuring transmission from the UE and dedicated higher layer parameters configuring reception.

[0593] o A UE does not expect to receive both dedicated higher layer parameters configuring transmission from the UE and cell specific higher layer parameters configuring reception.

[0594] ■ Cell-specifically configured DL reception refers to PDCCH in Type- 0 / 0A / 1 / 2 CSS set

[0595] • DL receptions are allowed only in certain cases. E.g., within DL subbands, within non- SBFD symbols, within only SBFD symbols, carriers are in different bands etc.

[0596] • UL transmissions are allowed only in certain cases. E.g., only with non-SBFD symbols, within UL subbands in DU / UD / DUD configurations, carriers are in different bands etc.

[0597] Case 4:

[0598] • It is considered as an error case if a dynamically scheduled DL reception with / without repetitions and a dynamically scheduled UL transmission with / without repetitions are in the same time domain symbol. E.g., when the carriers are within the same band. • DL receptions are allowed only in certain cases. E.g., within DL subbands, within non- SBFD symbols, within only SBFD symbols, carriers are in different bands etc.

[0599] • UL transmissions are allowed only in certain cases. E.g., only with non-SBFD symbols, within UL subbands in DU / UD / DUD configurations, carriers are in different bands etc.

[0600] Case 5:

[0601] Re-use the existing collision handling principles for NR TDD that SSB is prioritized over configured UL transmission and dynamically scheduled UL transmission. E.g., when the carriers are within the same band.2025F68137 - 25014 72

[0602] • DL receptions are allowed only in certain cases. E.g., within DL subbands, within non- SBFD symbols, within only SBFD symbols, carriers are in different bands etc.

[0603] • UL transmissions are allowed only in certain cases. E.g., only with non-SBFD symbols, within UL subbands in DU / UD / DUD configurations, carriers are in different bands etc.

[0604] Case 6:

[0605] • Reuse the existing collision handling rules for HD-FDD RedCap UEs. E.g., when the carriers are within the same band.

[0606] • UE does not expect collision between PRACH triggered by PDCCH order and dynamically scheduled DL reception.

[0607] • For collision between PRACH triggered by PDCCH order and semi-statically configured DL reception, UE does not receive DL channel / signal.

[0608] • For collision between PRACH triggered by higher layer and DL channel / signal, leave it to UE implementation whether to receive the DL or transmit PRACH.

[0609] • DL receptions are allowed only in certain cases. E.g., within DL subbands, within non- SBFD symbols, within only SBFD symbols, carriers are in different bands etc.

[0610] • UL transmissions are allowed only in certain cases. E.g., only with non-SBFD symbols, within UL subbands in DU / UD / DUD configurations, carriers are in different bands etc.

[0611] 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.

[0612] Fig. 11 illustrates an example of a computer system 600. The units or modules as well as the steps of the methods performed by these units may execute on one or more computer systems 600. The computer system 600 includes one or more processors 602, like a special purpose or a general-purpose digital signal processor. The processor 602 is connected to a communication infrastructure 604, like a bus or a network. The computer system 600 includes a main memory 606, e.g., a random-access memory (RAM), and a secondary memory 608, e.g., a hard disk drive and / or a removable storage drive. The secondary memory 608 may allow computer programs or other instructions to be loaded into the computer system 600. The computer system 600 may further include a communications interface 610 to allow software and data to be transferred between computer system 600 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 wire2025F68137 - 25014 73

[0613] or a cable, fibre optics, a phone line, a cellular phone link, an RF link and other communications channels 612.

[0614] 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 600. The computer programs, also referred to as computer control logic, are stored in main memory 606 and / or secondary memory 608. Computer programs may also be received via the communications interface 610. The computer program, when executed, enables the computer system 600 to implement the present invention. In particular, the computer program, when executed, enables processor 602 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 600. Where the disclosure is implemented using software, the software may be stored in a computer program product and loaded into computer system 600 using a removable storage drive, an interface, like communications interface 610.

[0615] 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.

[0616] 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.

[0617] 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.

[0618] 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.2025F68137 - 25014 74

[0619] 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.

[0620] 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.

[0621] 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.2025F68137 - 25014 75

[0622]

[0623] 2025F68137 - 25014 76

[0624]

[0625] 2025F68137 - 25014 77

[0626]

[0627] 2025F68137 - 25014 78

[0628]

Claims

2025F68137 - 25014 79Claims1. A device such as a user equipment configured for operating in a wireless communications network comprising a plurality of cells,wherein the device is to operate on a first carrier comprising a first symbol;wherein at the first symbol is a full duplex, FD, symbol.wherein the device is adapted to perform collision handling based on using the FD symbol.

2. The device of claim 1 , wherein the device is configured for carrier aggregation comprising aggregating at least a first part of the first symbol of the first carrier of the wireless communication network and at least a second part of a second symbol of a second carrier of the wireless communication network.

3. The device of claim 2, adapted to perform the collision handling based on an uplink part of the carrier aggregation being in a different carrier as a downlink part of the carrier aggregation, e.g., there is dynamically scheduled DL reception on one carrier and semi- statically configured UL on another carrier.

4. The device of one of previous claims, adapted to operate based on a dynamically scheduled DL reception and semi-statically configured UL transmission are to be not expected by the device, e.g., when the first carrier and the second carrier are within the same band.

5. The device of one of previous claims, adapted to operate based on a dynamically scheduled DL reception; wherein semi-statically configured UL transmissions are allowed, wherein the device is adapted for at least one of:o reusing an existing collision handling principle and timeline in NR for operation on flexible symbols on a single carrier in unpaired spectrum, i.e., UL transmission is cancelled if cancellation timeline is met, e.g., the carriers are in different bands and optionally applying the same rule for a repetition of the uplink;o DL receptions are allowed only in certain cases such as within DL subbands, within non-SBFD symbols, within only DL subbands within SBFD symbols etc.;2025F68137 - 25014 80o UL transmissions are allowed only in certain cases such as only with non-SBFD symbols, within UL subbands within SBFD symbols, e.g., in DU or UD or DUD configurations etc.

6. The device of one of previous claims, adapted to operate based on a semi-statically configured DL reception and dynamically scheduled UL transmission are to be not expected by the device, e.g., when the carriers are within the same band.

7. The device of one of previous claims, adapted to operate based on a semi-statically configured DL reception and dynamically scheduled UL transmission being allowed, wherein the device is adapted for at least one of:o reusing the existing collision handling principles in NR for operation on flexible symbols on a single carrier in unpaired spectrum, i.e., the device does not receive and process DL channel or signal, e.g., the carriers are in different bands and optionally applying the same rule for a repetition of the downlink; o DL receptions are allowed only in certain cases such as within DL subbands, within non-SBFD symbols, within only DL subbands within SBFD symbols etc. o UL transmissions are allowed only in certain cases such as only with non-SBFD symbols, within UL subbands within SBFD symbols, e.g., in DU or UD or DUD configurations etc.

8. The device of one of previous claims, adapted to operate according to a semi-statically configured DL reception vs. semi-statically configured UL transmission being an error case, wherein the first carrier and the second carriers are in same or different bands.

9. The device of one of previous claims, adapted to operate according to not receiving and processing both dedicated higher layer parameters configuring transmission from the device and dedicated higher layer parameters configuring reception.

10. The device of one of previous claims, adapted not receive and process both dedicated higher layer parameters configuring transmission from the device and cell specific higher layer parameters configuring reception.

11. The device of claim 10, wherein the cell specific higher layer parameter relates to a cell- specifically configured DL reception that refers to PDCCH, e.g., in Type-0 / 0A / 1 / 2 CSS set.2025F68137 - 25014 8112. The device of one of claims 8 to 11, adapted to operate according to DL receptions being allowed only in certain cases such as within DL subbands, within non-FD symbols, within only DL subbands of FD symbols and / or carriers being in different bands.

13. The device of one of claims 8 to 12, adapted to operate according to UL transmissions being allowed only in certain cases such as only with non-SBFD symbols, within UL subbands of SBFD symbols in DU or UD or DUD configurations and / or carriers being in different bands.

14. The device of one of previous claims, adapted to consider a dynamically scheduled DL reception with and / or without repetitions and a dynamically scheduled UL transmission with and / or without repetitions being in the same time domain symbol as an error case, e.g., when the carriers are within the same band.

15. The device of claim 14, adapted to operate according to DL receptions being allowed only in certain cases such as within DL subbands, within non-SBFD symbols, within only SBFD symbols and / or carriers being in different bands.

16. The device of claim 14 or 15, adapted to operate according to UL transmissions being allowed only in certain cases such as only with non-SBFD symbols, within UL subbands of SBFD symbols in DU or UD or DUD configurations and / or carriers being in different bands.

17. The device of one of previous claims, adapted to re-use an existing collision handling principles for TDD that SSB is prioritized over configured UL transmission and dynamically scheduled UL transmission, e.g., when the carriers are within the same band.

18. The device of claim 17, adapted to operate according to DL receptions being allowed only in certain cases such as within DL subbands, within non-SBFD symbols, within only SBFD symbols and / or carriers being in different bands etc.

19. The device of claims 17 or 18, adapted to operate according to UL transmissions being allowed only in certain cases such as only with non-SBFD symbols, within UL subbands in SBFD symbols in DU or UD or DUD configurations and / or carriers being in different bands etc.2025F68137 - 25014 8220. The device of one of previous claims, wherein for a case where dynamic or semi-static DL vs. valid RACH occasion, RO, applies, the device is adapted to at least one of: • reusing an existing collision handling rules for HD-FDD RedCap UEs, e.g., when the carriers are within the same band;• not expecting collision between PRACH triggered by PDCCH order and dynamically scheduled DL reception;• not receiving or processing a DL signal or channel in case of a collision between PRACH triggered by PDCCH order and semi-statically configured DL reception;• operate according to a device implementation whether to receive the DL or transmit PRACH in case of a collision between PRACH triggered by higher layer and DL channel or signal;• operate according to DL receptions being allowed only in certain cases such as within DL subbands, within non-SBFD symbols, within only SBFD symbols and / or carriers being in different bands etc.;• operate according to UL transmissions being allowed only in certain cases such as only with non-SBFD symbols, within SBFD symbols in UL subbands in DU or UD or DUD configurations and / or carriers being in different bands etc.

21. The device according to any of previous claims, adapted for the carrier aggregation to comprise exactly one carrier as a full duplex carrier that comprises FD symbols comprising the FD symbol.

22. The device according to any of previous claims, adapted for the carrier aggregation to comprise exactly one carrier to comprise a band or subband associated with full duplex, e.g., a subband full duplex subband.

23. The device of one of previous claims, wherein at least one of the first carrier and the second carrier is operated with a slot format comprising downlink symbols, uplink symbols, and flexible symbols.

24. The device of claim 23, adapted to operate according to FD symbols on a reference cell and / or other cells being equivalent to flexible symbols.

25. The device of claim 24, adapted to apply a behavior for flexible symbols to FD symbols.

26. The device of claim 25, adapted to not expect to be configured, e.g., by higher layers, to receive PDCCH, PDSCH, or CSI-RS on a flexible symbol / SBFD symbol on the reference2025F68137 - 25014 83cell and to detect a DCI format scheduling a transmission on the symbol on another cell, if another cell among the cells configured with direction collision handling, e.g., directionalCollisionHandling-r16, operates in the same frequency band as the reference cell.

27. The device of one of claims 23 to 26, adapted to receive link directions indicating uplink and / or downlink for FD symbols in reference cells or other cells and to operate accordingly.

28. The device of claim 27, adapted to operate according to link directions being semi-static or dynamic.

29. The device of claim 27 or 28, adapted to operate based on rules for collision handling in a carrier aggregation scenario considering the uplink and / or downlink and semi-static and / or dynamic link direction in the FD symbols.

30. The device of one of claims 23 to 29, adapted to not expect downlink and / or uplink in the reference symbol and uplink and / or downlink, respectively, in another cell for a case where the symbol of the reference cell is a reference symbol of type FD.

31. The device of claim 30, adapted to operate based on the another cell among a plurality of available cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, operating in a same or different band as the reference cell.

32. The device of one of claims 30 to 31 , adapted to operate according to a signalling that indicates a symbol as one of a) FD; b) both downlink and FD; and c) both flexible and FD on the reference cell and as at least one of uplink; flexible; or downlink on another cell respectively.

33. The device of claim 32, adapted to operate in a scenario where another cell among the cells is configured with directional collision handling, e.g., directionalCollisionHandling- r16, operates in the same band as the reference cell.

34. The device of claim 32 or 33, adapted to operate according to an uplink or downlink or flexible link direction being indicated by one or more of:2025F68137 - 25014 84tdd-UL-DL-ConfigurationCommon, by tdd-UL-DL-ConfigurationDedicated, DCI, SFI, MAC CE, scheduling of uplink / downlink signals / channels, e.g., semi-static scheduling of PDCCH, CSI-RS, PDSCH, PUCCH, PRACH, SRS, PUSCH etc.

35. The device of one of claims 32 to 34, adapted to operate according to a signalling indicating the symbol as downlink by TDD common configuration and also as FD symbol.

36. The device of one of claims 32 to 35, adapted to operate according to a signalling indicating the symbol as flexible by TDD common configuration and also indicated as FD symbol.

37. The device of one of claims 32 to 36, adapted to operate according to a signalling indicating the symbol as FD or downlink + SBFD or flexible + SBFD and configures the symbol semi-statically or dynamically as downlink and / or uplink on the reference cell and as uplink and / or downlink on another cell respectively.

38. The device of claim 37, wherein when another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, operates in the same band as the reference cell, the uplink and / or downlink on the another cell and / or reference cell is a semi-static configuration, a dynamic configuration or both.

39. The device of claims 38, wherein for semi-static downlink configuration of the reference cell and / or the another cell, the indication can be using any RRC or MAC CE, or tdd-UL- DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, or a downlink signal / channel semi-statically configured, e.g., semi-static scheduling of PDCCH, CSI- RS, PDSCH, etc. or a link direction signal indicating downlink reception.

40. The device of claims 38 or 39, wherein for semi-static uplink configuration of the reference cell / another cell, the indication can be using RRC or MAC CE, or tdd-UL-DL- ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, or an uplink signal / channel semi-statically configured, e.g., semi-static scheduling of PUCCH, SRS, PUSCH, PRACH etc or a link direction signal indicating uplink transmission.

41. The device of one of claims 38 to 40, wherein for dynamic configuration of the reference cell or another cell, it can be using one or more of SFI, DCI, dynamic link direction signal etc.2025F68137 - 25014 8542. The device of one of claims 30 to 41 , wherein the device is to operate accordingly in a case where the symbol in the another cell is FD and the reference cell is not configured with FD.

43. The device of one of claims 23 to 42, adapted to not expect downlink receptions in the reference symbol, e.g., SBFD symbol, in only one downlink subband when uplink transmissions in another cell are configured semi-statically or dynamically.

44. The device of claim 43, adapted to operate based on another cell among a plurality of available cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, operates in the same or different band as the reference cell, e.g., in a case when the cell has more than one downlink subband.

45. The device of one of claims 43 to 44, adapted to select a downlink subband from a plurality of available downlink subbands based on a criterion.

46. The device of claim 45, wherein the criterion is related to a downlink subband which will be least interfered at the device side from the other aggregated carriers is used for reception.

47. The device of claim 45 or 46, adapted to operate on an uplink or downlink on the another cell or reference cell being configured in a semi-static and / or dynamic manner.

48. The device of claim 47, adapted for determining an indication of the semi-static downlink configuration of the reference cell and / or the another cell, by using any RRC or MAC CE, or tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, or a downlink signal / channel semi-statically configured, e.g., semi-static scheduling of PDCCH, CSI-RS, PDSCH, etc or a link direction signal indicating downlink reception.

49. The device of claim 47 or 48, adapted for determining an indication of the semi-static uplink configuration of the reference cell and / or another cell, by using RRC or MAC CE, or tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, or an uplink signal / channel semi-statically configured, e.g., semi-static scheduling of PLICCH, SRS, PLISCH etc or a link direction signal indicating uplink transmission.2025F68137 - 25014 8650. The device of one of claims 47 to 49, adapted for determining an indication of the dynamic configuration of the reference cell and / or another cell by using one or more of SFI, DCI, dynamic link direction signal etc.

51. The device of one of claims 47 to 50, adapted to operate accordingly if the symbol in the another cell is FD and the reference cell is not configured with FD.

52. The device of one of claims 23 to 51, adapted to expect uplink transmissions in the reference symbol and downlink receptions in another cell based on special conditions for uplink transmissions in a case where the reference symbol is FD.

53. The device of claim 52, wherein the special condition relates to at least one of:o when the uplink transmission is restricted to an uplink subband,o when the uplink transmission is restricted to an uplink subband, based on a certain configuration, e.g., an uplink in between 2 downlink subbands, DUD or a DU or UD configuration or any combination thereof.

54. The device of claim 52 or 53, wherein, adapted to operate with another cell among a plurality of cells configured with collision handling, e.g., directionalCollisionHandling-r16, in a same and / or different band as the reference cell.

55. The device of one of claims 52 to 54, adapted to operate on an uplink and / or downlink on the another cell and / or reference cell being configured in a semi-static and / or dynamic manner.

56. The device of claim 55, adapted for determining an indication of the semi-static downlink configuration of the reference cell and / or the another cell, by using any RRC or MAC CE, or tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, or a downlink signal / channel semi-statically configured, e.g., semi-static scheduling of PDCCH, CSI-RS, PDSCH, etc or a link direction signal indicating downlink reception.

57. The device of claim 55 or 56, adapted for determining an indication of the semi-static uplink configuration of the reference cell and / or another cell, by using RRC or MAC CE, or tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, or an uplink signal / channel semi-statically configured, e.g., semi-static scheduling of PUCCH, SRS, PUSCH etc or a link direction signal indicating uplink transmission.2025F68137 - 25014 8758. The device of one of claims 55 to 57, adapted for determining an indication of the dynamic configuration of the reference cell and / or another cell by using one or more of SFI, DCI, dynamic link direction signal etc.

59. The device of one of claims 52 to 58, adapted to operate accordingly if the symbol in the another cell is FD and the reference cell is not configured with FD.

60. The device of one of claims 23 to 59, adapted to not expect a symbol to be indicated as only downlink, e.g., non-FD, on a reference cell which has FD configuration and uplink on another cell, respectively, by tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL- ConfigurationDedicated, e.g., if the another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, it operates in the same band as the reference cell.

61. The device of one of claims 23 to 60, adapted to not expect a symbol to be indicated as uplink on the reference cell and only downlink (not SBFD) on another cell, which has SBFD configuration respectively, by tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL- ConfigurationDedicated, e.g., if the another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, it operates in the same band as the reference cell.

62. The device of one of claims 23 to 61 , adapted to transmit a signal or channel scheduled by a DCI format on a symbol of another cell where the transmissions are within the uplink subband of an SBFD symbol when the symbol is indicated as downlink by tdd-UL-DL- ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for the reference cell, e.g., if the reference cell and another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, they operate in different frequency bands.

63. The device of one of claims 23 to 62, adapted to transmit a signal or channel scheduled by a DCI format on a symbol of another cell where the transmissions are in an only uplink symbol when the symbol is indicated as downlink by tdd-UL-DL-ConfigurationCommon ortdd-UL-DL-ConfigurationDedicated for the reference cell, e.g., if the reference cell and another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, they operate in different frequency bands.2025F68137 - 25014 8864. The device of one of claims 23 to 63, adapted to transmit a signal or channel scheduled by a DCI format on a symbol of another cell when the symbol is indicated as only downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for the reference cell configured with SBFD, e.g., if the reference cell and another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling- r16, they operate in different frequency bands.

65. The device of one of claims 23 to 64, adapted to transmit a signal or channel scheduled by a DCI format on a symbol of another cell when the symbol is indicated as SBFD for the reference cell configured with SBFD, e.g., if the reference cell and another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling- r16, they operate in different frequency bands.

66. The device of one of claims 23 to 65, adapted for deriving a DCI format scheduling a transmission on one or more symbols in a set of symbols on another cell and to operate the carrier aggregation without receiving a higher layer configured PDCCH, PDSCH, or CSI-RS on flexible or SBFD symbols on the reference cell, if the UE, e.g., if the reference cell and another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, operate in different frequency bands.

67. The device of one of claims 23 to 66, adapted for deriving a DCI format scheduling a transmission on one or more symbols in the set of symbols on another cell where the one or more symbols are non-SBFD; and to the carrier aggregation without receiving a higher layer configured PDCCH, PDSCH, or CSI-RS on flexible symbols on the reference cell in a set of symbols, e.g., if the reference cell and another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling-r16, operate in different frequency bands.

68. The device of one of claims 23 to 67, adapted for deriving a DCI format scheduling a transmission on one or more symbols in the set of symbols on another cell where the one or more symbols are SBFD symbols, and to operate the carrier aggregation without receiving a higher layer configured PDCCH, PDSCH, or CSI-RS on flexible symbols on the reference cell in a set of symbols, e.g., if the reference cell and another cell among the cells configured with directional collision handling, e.g., directionalCollisionHandling- r16, operate in different frequency bands.

69. The device according to one of previous claims, wherein a full duplex, FD, symbol has2025F68137 - 25014 89frequency resources in uplink direction, II, and downlink direction, D, in the same time resource(s), that are one of:full-overlapping,partial overlapping,non-overlapping, e.g., an SBFD symbol having uplink and downlink subbands.

70. The device according to one of previous claims, wherein the FD symbol comprises frequency resources in uplink direction and frequency resources in downlink direction and optionally flexible frequency resources.

71. The device according to one of previous claims, adapted to operate according to a full- duplex configuration received from a base station.

72. The device according to one of previous claims, adapted to use the first part and the second part simultaneously or subsequently.

73. The device according to one of previous claims, wherein the first carrier and the second carrier implement the same duplexing scheme.

74. The device according to one of previous claims, wherein the device is to aggregate at least the first part, the second part and at least a third part of a third symbol of a third carrier of the wireless communication network, e.g., a third symbol, e.g., to aggregate more than two carriers.

75. The device according to one of previous claims, adapted to operate on the first carrier and the second carrier as synchronized carriers.

76. The device according to one of previous claims, adapted to use uplink resources of the first part for an uplink and for using downlink resources of the second part for downlink.

77. The device according to one of previous claims, adapted to use uplink resources of the first part for an uplink and for using uplink resources of the second part for uplink.

78. The device of claim 77, wherein the device is adapted to implement a continuous uplink transmission in time domain by subsequently using the first part and the second part.2025F68137 - 25014 9079. The device according to one of previous claims, adapted to use downlink resources of the first part for a downlink and for using downlink resources of the second part for downlink.

80. The device of claim 79, wherein the device is adapted to implement a downlink boost in terms of downlink resources by simultaneously using the first part and the second part.

81. The device of one of previous claims, adapted to operate on the first carrier and the second carrier comprising a frequency separation therebetween to mitigate cross-carrier interference.

82. The device of claim 81, adapted to operate in accordance with an adjacent channel interference ratio, ACIR.

83. The device of claim 81 or 82, adapted to adopt at least one of a transmit power and / or at least one filter to maintain interfering emissions below a defined interference ratio.

84. The device of one of the previous claims, adapted to operate on the first carrier and the second carrier as being operated by the same or different operators.

85. The device of one of the previous claims, adapted to operate on the first carrier and the second carrier as being operated by the same or different base station types.

86. The device of claim 85, wherein a base station type isa radio device for communicating with one or more user devices, UEs, of a wireless communication system, the UEs being in accordance with one or more of the previous claims; wherein the radio device is to communicate with the one or more UEs using a radio signal comprising a plurality of time blocks in a time domain, and frequency block in a frequency domain; optionally being one or more of the following: a base station, BS, a macro cell base station, or a small cell base station, or a central unit, CU, of a base station, ora distributed unit, DU, of a base station, or an Integrated Access and Backhaul, IAB, node, or a road side unit, RSU, or a WiFi access point, AP, or a UE, or a sidelink, SL, UE, or a group leader UE, GL-UE, or a relay or a remote radio head, or an AMF, or an SMF, or a core network, CN, entity, or mobile edge computing, MEC, entity, or a network slice as in the NR or 5G core context, or any transmission and reception point, TRP, one of a TRP as in multi-TRP, mTRP, enabling an item or a device to communicate using the wireless communication network, the item or device being provided with2025F68137 - 25014 91network connectivity to communicate using the wireless communication network, or a non-terrestrial device, e.g., a moving or stationary air-borne device, like a drone, an unmanned aerial vehicle, UAV, or an airplane, or a moving or stationary space-borne device, like a low earth orbit, LEO, satellite, like a LEO-600 satellite or a LEO-1200 satellite, a medium earth orbit, MEO, satellite, or a geosynchronous earth orbit, GEO, satellite;or one or more of- a macro base station,- a micro base station,- a small-cell base station,- a non terrestrial network, NTN, base station,- an integrated access and backhaul, lAB-node, a distributed unit, DU, or central unit, CU.

87. The device of one of previous claims, adapted for using the first carrier as a time division duplex, TDD, carrier and for using the second carrier as a TDD carrier.

88. The device of one of previous claims, adapted for using the first carrier as a time division duplex, TDD, carrier and for using the second carrier as a frequency division duplex FDD carrier.

89. The device of one of previous claims, adapted for using the first carrier as a time division duplex, TDD, carrier and for using the second carrier as a supplemental uplink carrier, SUL, carrier.

90. The device of one of previous claims, adapted for using the first carrier as a time division duplex, TDD, carrier and for using the second carrier as a supplemental downlink carrier, SDL, carrier.

91. The device of one of previous claims, adapted for using the first carrier as a frequency division duplex, FDD, carrier and for using the second carrier as an FDD carrier.

92. The device of one of previous claims, adapted for using the second part as an uplink part during a downlink cycle of the first carrier.2025F68137 - 25014 9293. The device of one of the previous claims, wherein using a first carrier and one or more second carriers form a base carrier, e.g., the base carrier being formed as a combination comprising at least one of a) TDD / TDD, b) TDD / FDD, c) FDD / TDD and d) FDD / FDD.

94. The device of one of previous claims, adapted for using the first carrier as a frequency division duplex, FDD, carrier and for using the second carrier as supplemental uplink carrier, SUL, carrier.

95. The device of one of previous claims, adapted for using the second part as an uplink part paired with a downlink band of the first carrier.

96. The device of one of the previous claims, adapted to use the first carrier (FDD) to form a base carrier and to use the second carrier to perform a boost in the UL direction.

97. The device of one of previous claims, adapted for using the first carrier as a frequency division duplex, FDD, carrier and for using the second carrier as an supplementary downlink, SDL, carrier.

98. The device of one of previous claims, adapted for using the second part as a downlink part paired with an uplink band of the first carrier.

99. The device of one of the previous claims, adapted to use the first carrier (FDD) to form a base carrier and to use the second carrier to perform a boost in the DL direction.

100. The device of one of previous claims, adapted to access the first carrier as being operated in a first cell of the wireless communication network and to access the second carrier as being operated in a second cell of the wireless communication network.

101. The device of claim 100, wherein the device is adapted to simultaneously connect to the first cell and the second cell.

102. The device of one of previous claims, wherein the device is adapted to receive and process signalling received with the first carrier, the signalling indicating a use of the second part.

103. The device of claim 102, adapted to receive the signalling as a configuration or preconfiguration.2025F68137 - 25014 93104. The device of claim 102 or 103, adapted to receive the signalling via a physical layer, PHY, a medium access control control element, MAC-CE, a radio resource control, RRC, or a higher-layer configuration.

105. The device of one of claims 102 to 104, adapted to implement the carrier aggregation based on the signalling as a semi-persistent configuration or a semi-persistent scheduling, SPS ora configured grant, CG, configuration.

106. The device of one of claims 102 to 105, adapted to process the signalling based on a basic configuration or global basis, e.g., RRC, as a first level of signalling and for processing a second level of signalling, e.g., via RRC or PHY, wherein the device is adapted to- skip or drop at least one transmission and / or reception within an FD slot of an aggregated carrier, e.g., the secondary carrier(s),- skip all transmissions and / or receptions within the aggregated carrier, e.g., the secondary carrier(s), and / or base carrier and / or primary carrier, - change the link direction within the aggregated carrier and / or base carrier and / or primary carrier, e.g., in case the link direction within the SBFD-slot of a aggregated carrier is supposed to be used for uplink, II, the device uses the downlink, D, link direction within the same carrier, or vice versa, - transmit and / or receive only on the primary carrier and / or the secondary carrier(s),- transmit and / or receive only on the aggregated carrier, e.g., the secondary carrier(s), e.g., without transmitting in the primary carrier,- switch carriers.

107. The device of claim 106, wherein, wherein a carrier switch is configured by one or more of the following- a secondary carrier is configured as the primary carrier,- the primary carrier is configured as a secondary carrier,- carrier aggregation is stopped, e.g., fallback to the primary carrier, - the primary carrier can be removed from the aggregated carriers, e.g., device is reconfigured with one of the secondary carriers as primary carrier.

108. The device of claim 106 or 107, wherein the device is adapted for a power saving mode during a time there the skipped transmission is scheduled.2025F68137 - 25014 94109. The device of one of claims 102 to 108, adapted to process the signalling based on a previous, e.g., last received control signalling, e.g., based on a type of a symbol used for transmitting the control signal.

110. The device of one of claims 102 to 109, wherein the device is adapted to use UL or DL FD resources of the first part or of the second part with a defined pattern and / or for a defined time duration or period and to then switch back to a fallback configuration, according to the signalling.

111. The device of one of claims 102 to 110, wherein the device is adapted to use UL or DL FD resources dependent on at least one of- a carrier frequency of the UL or DL FD resources, e.g., based on a lower frequency causing less path loss to allow less transmit power being required, - an amount of transmit power reduction achieved by using a lower carrier frequency,- a QoS criterion, e.g.,o number of resources to be transmitted by the device, e.g., in case this exceeds a certain threshold, the UL or DL FD resources are used, otherwise they are not used,o a packet delay budget, PDB, in case this is below a configured or preconfigured threshold, the additional UL or DL FD resources are used in order to fulfil the PDBo reliability, e.g., using redundancy transmission or data duplication, in order to increase successful packet delivery.

112. The device of one of previous claims, wherein the device is adapted to receive and process signalling received with the second carrier as an aggregated carrier, the signalling indicating a use of the first part related to the first carrier as a base carrier.

113. The device of one of previous claims, wherein the device is configured or pre-configured or adapted to process implicit and / or explicit signalling indicating where to blind decode resource maps for the carrier aggregation and to operate accordingly.

114. The device of one of previous claims, wherein the device is adapted to return from the carrier aggregation to an operation on the first carrier or the second carrier as a base carrier based on at least one of an explicit signalling, after a timeout and after reception2025F68137 - 25014 95and / or transmission of a certain number of data symbols within the FD part of the aggregated carrier.

115. The device of claim 114, wherein the device is adapted to return to the operation on the base carrier as a fallback immediately; or after a certain number of transmissions on the aggregated band; or after a timeout; or after a number of failed transmissions, e.g., for which the UE received no NACKs or a number of NACKs.

116. The device of claim 115, adapted to return to the operation on the base carrier as a fallback based on one or more of- an indication from the base station, e.g., a signalling received from the base station,- as a result of a request of the device,- by its own decision:o sending a request to the base station,o informing the base station about its action, e.g., return to the operation on the base carrier as a fallback.- by a timeout, e.g., the fallback will be automatically triggered in case a timeout is reached,- by an event-triggered timeout, e.g., battery limit reached.

117. The device of one of claims 115 to 116, wherein based on returning from the carrier aggregation a transmissions or receptions on the base carrier could be skipped, e.g., thus, the power consumption of the UE, e.g., by not performing blind decodes or by not having to transmit on the base carrier in a subsequent time domain resources, could be reduced.

118. The device of one of claims 115 to 117, wherein based on a transmission using the carrier aggregation using the FD symbol, the device is to skip at least one of a transmission and a reception on a base carrier of the carrier aggregation.

119. The device of claim 118, adapted to perform power saving based on a symbol being skipped on the base carrier or on an aggregated carrier, e.g., DRX, e.g., the UE does not have to perform blind decoding on either base carrier or aggregated carrier.

120. The device of one of previous claims, wherein the device is adapted for using the carrier aggregation for boosting at least one of an uplink, UL, and a downlink, DL, capacity;2025F68137 - 25014 96and / or for redundancy transmissions, e.g., to increase at least one of a data rate, a spectral efficiency and a reliability.

121. The device of one of previous claims, wherein the device is to aggregate based on the first carrier and the second carrier being operated as TDD carriers that are shifted in the time domain by a time offset.

122. The device of claim 121 , wherein the device is to use the second part in an opposite link direction when compared to the first part.

123. The device of claim 122, adapted for a continuous UL transmission and / or DL reception in time domain using the aggregated parts.

124. The device of claim 122 or 123, for using an SBFD symbol for using the FD symbol for boosting an uplink of the other symbol or for increasing a downlink capacity of the other symbol, e.g., to increase at least one of a data rate, a spectral efficiency and a reliability.

125. The device of one of claims 122 to 124, wherein the device is to operate on the first carrier and the second carrier as separated in the frequency domain and / or in a spatial domain.

126. The device of one of claims 122 to 125, wherein the time offset is within a time resource, which is one or more of- a number of samples,- a number of OFDM symbols,- a mini-slot or a half slot or a slot or a subslot,- a frame, a half-frame or a radioframe or a hyperframe,- is within a guard period or cyclic prefix,- limited by a threshold, e.g., shorter than a guard period,- depending on the used numerology, e.g., 7 OFDM symbols for 15kHz SOS, 14 OFDM symbols for 30kHz SOS.

127. The device of one of claims 122 to 126, wherein the position of the time offset is at the beginning of a time resource, or at the end of a time resource, e.g., in TDD before or after a DL symbol or UL symbol or flexible symbol.2025F68137 - 25014 97128. The device of one of claims 122 to 127, wherein the resources used within the aggregated SBFD symbol are randomized, or wherein the resources are used according to a configured and / or pre-configured pattern.

129. The device of one of claims 122 to 128, adapted to blank or puncture out a part of a base carrier or aggregated carrier.

130. The device of one of claims 122 to 129, wherein the adapting is with respect to an aggregated part where an overlap of opposite link directions of the FD symbol with respect to the other part occurs.

131. The device of one of previous claims, adapted to operate on the first part and the second part based on a gap or guard between an UL and a DL direction or a UL and a flexible direction, F, or a DL and a flexible direction, F, within a carrier.

132. The device of claim 131 , wherein the gap is adapted for allowing switching between UL and DL transmission, e.g., reconfiguration of analogue components of a UE, e.g., power amplifiers, PAs, or filters, or wherein the device is adapted to use the gap for power saving, e.g., DRX.

133. The device of claim 131 or 132, wherein the gap is defined as a time resource.

134. The device of claim 133, wherein the time resource is one or more of- a number of samples,- a number of OFDM symbols,- a mini-slot or a half slot or a slot or a subslot,- a frame, a half-frame or a radioframe or a hyperframe,- is within a guard period or cyclic prefix,- limited by a threshold, e.g., shorter than a guard period,- depending on the used numerology, e.g., 7 OFDM symbols for 15kHz SCS, 14 OFDM symbols for 30kHz SCS.

135. The device of one of claims 131 to 134, wherein the gap is configured or pre-configured, e.g., via RRC and / or MAC-CE and / or PHY-signalling or higher layer signalling, or wherein the device is to determine the gap based on a FD slot configuration.2025F68137 - 25014 98136. The device of one of claims 131 to 135, wherein the gap is configured over a whole frequency range of a carrier, or is defined for at least one certain subband within the frequency range of a carrier.

137. The device of one of claims 131 to 136, adapted to operate according to a configuration where the gap is configured on one of the carriers, e.g., the carrier containing the FD slot or symbol, or on a carrier having no FD slot, or on both carriers.

138. The device of one of claims 131 to 137, adapted to operate according to a configuration where the gap is related to a same or different radio characteristics applying to the first carrier and the second carrier.

139. The device of claim 138, wherein the different radio characteristics relate to an asymmetric use of a first communication technology used for the first carrier and a second communication technology used for the second carrier.

140. The device of claim 139, wherein one of the first communication technology and the second communication technology is a terrestrial communication and the other is a nonterrestrial communication.

141. The device of one of claims 131 to 140, wherein different gaps of different bandwidth and / or time duration are implemented in the first carrier and in the second carrier.

142. The device of one of previous claims, wherein at least one of the first carrier and the second carrier is operated with a slot format comprising downlink symbols, uplink symbols, and flexible symbols.

143. The device of claim 142, wherein the first part is associated with a reference cell to which the second part is aggregated, wherein the symbol of the reference cell is a reference symbol, wherein the reference symbol and / or of the aggregated part is a FD symbol.

144. The device of claim 143, wherein the reference symbol is one of:downlink, or uplink, e.g., as indicated by tdd-UL-DL-ConfigurationCommon ortdd-UL- DL-ConfigurationDedicated,2025F68137 - 25014 99• uplink, if the reference symbol is a flexible symbol or a FD symbol, wherein the device is adapted to transmit an uplink signal or channel, e.g., at least one of SRS, PLICCH, PLISCH, or PRACH on the reference symbol,• downlink, if the reference symbol is a flexible symbol or a FD symbol, wherein the device is configured to receive at least a downlink signal or channel, e.g., one of PDCCH, PDSCH or CSI-RS on the reference symbol,• FD symbol, as indicated.

145. The device of claim 143 or 144, wherein the reference symbol is a downlink symbol or a flexible symbol which is converted to a FD symbol.

146. The device of claim 145, wherein the device is to operate according to a TDD common configuration that configures the reference symbol to be downlink and to operate according to a FD configuration that indicates that it is a FD symbol; orwherein the device is to operate according to the TDD common configuration that configures the reference symbol to be a flexible symbol, and wherein the device is to operate according to a FD configuration indicating the reference symbol to be a FD symbol.

147. The device of one of claims 143 to 146, wherein the device is to select the reference cell as a cell without FD configuration.

148. The device of one of claims 143 to 147, adapted to select a cell as reference cell that comprises a cell index nearest to a cell index of a cell with FD configuration.

149. The device of claim 143 to 148, adapted to select the cell based on a capability.

150. The device of claim 143 to 149, wherein the device is to select a reference cell with FD configuration as reference cell.

151. The device of claim 143 to 150, wherein whether the device is to select a reference cell with FD configuration as reference cell is based on a device capability.

152. The device of claim 150 or 151 , wherein the device is to select the reference cell with FD configuration as reference cell based on all uplink and / or downlink or certain defined uplink and / or downlink signals / channels are with Configuration 1.2025F68137 - 25014 100153. The device of claim 152, wherein whether the device is to select the reference cell with FD configuration as reference cell based on all uplink and / or downlink or certain defined uplink and / or downlink are with Configuration 1 is based on a device capability.

154. The device of claim 152 or 153, wherein Configuration 1 relates to all transmissions and / or receptions are confined to only one symbol type being a FD or non-FD symbol, e.g., based on a device capability.

155. The device of one of claims 143 to 154, adapted to use a cell with FD configuration for the carrier aggregation based on satisfying a condition that all uplink and / or downlink signals or channels, or certain defined uplink and / or downlink signals or channels are with Configuration 1.

156. The device of claim 155, wherein in case a valid symbol type of Configuration 1 is non- FD, the device is to operate accordingly for carrier aggregation.

157. The device of claim 155 or 156, wherein Configuration 1 relates to all transmissions and / or receptions are confined to only one symbol type being a FD or non-FD symbol, e.g., based on a device capability.

158. The device of any of previous claims 142 to 157, adapted to operate on a symbol indicated as FD symbol that has semi-static downlink configuration using any RRC or MAC CE, ortdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, or a downlink signal / channel semi-statically configured, e.g., semi-static scheduling of PDCCH, CSI-RS, PDSCH, etc. or a link direction signal indicating downlink reception.

159. The device of any of claims 142 to 158, adapted to operate on a symbol indicated as FD that has dynamic downlink configuration using one or more of an SFI, a DCI, a dynamic link direction signal etc.

160. The device of one of claims 142 to 159, adapted to assume a symbol as flexible symbol or FD symbol and to operate the carrier aggregation without receiving a higher layer configured PDCCH, PDSCH, or CSI-RS; and wherein the device is to avoid transmission of a higher layer configured SRS, PLICCH, PLISCH, or PRACH, when tdd-UL- DLConfigurationCommon or tdd-UL-DL-ConfigurationDedicated indicates a symbol as2025F68137 - 25014 101downlink or uplink on another cell and as uplink or downlink for the reference cell, respectively.

161. The device of claim 160, adapted to operate on a symbol that is indicated as a) FD; or b) downlink + SBFD or c) flexible + SBFD and is configured semi-statically or dynamically as downlink and / or uplink on the reference cell and as uplink or downlink on another cell respectively.

162. The device of claim 161 , wherein the uplink and / or downlink configuration on the another cell and / or the reference cell is a semi-static configuration, a dynamic configuration or both.

163. The device of claim 161 or 162, wherein for semi-static downlink configuration of the reference cell or another cell, the device is to operate based on an indication that uses any RRC or MAC CE, or a downlink signal / channel semi-statically configured, e.g., semistatic scheduling of PDCCH, CSI-RS, PDSCH, etc. or a link direction signal indicating downlink reception.

164. The device of one of claims 161 to 163, wherein for semi-static uplink configuration of the reference cell or another cell, the device is to operate based on an indication that uses RRC or MAC CE, or an uplink signal / channel semi-statically configured, e.g., semistatic scheduling of PLICCH, SRS, PLISCH, PRACH etc or a link direction signal indicating uplink transmission.

165. The device of claim 161 to 164, wherein for dynamic configuration of the reference cell or another cell, the device is to operate based on an indication that uses one or more of SFI, DCI, or a dynamic link direction signal.

166. The device of claim 161 to 165, adapted to operate on the FD symbol having a downlink configured on both its downlink subbands or only one subband.

167. The device of claim 161 to 166, adapted to operate on the FD symbol having an uplink subband with a certain configuration, e.g., the configuration is DU or UD.

168. The device of one of claims 160 to 167, wherein the symbol is a non-FD symbol only.2025F68137 - 25014 102169. The device of one of claims 160 to 168, adapted to operate accordingly when the symbol in the another cell is SBFD and the reference cell is not configured with FD.

170. The device of one of claims 142 to 169, adapted to not transmit one ormore of a PLICCH, PLISCH, SRS or PRACH that is configured by higher layers on a set of symbols on another cell if at least one symbol from the set of symbols is indicated as downlink by tdd-UL-DLConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and non-SBFD or is a symbol corresponding to one or more of a PDCCH, PDSCH, or CSI-RS reception that is configured by higher layers or an SBFD symbol on the reference cell.

171. The device of claim 170, adapted to operate according to the FD symbol being further configured with a link direction signal indicating downlink reception or dynamically configured using one or more of SFI, DCI, dynamic link direction signal etc. for downlink.

172. The device of claim 170 or 171, adapted to operate according to the FD symbol comprising downlink configured on both its downlink subbands.

173. The device of one of claims 142 to 172, adapted to not transmit one ormore of a PLICCH, PLISCH, SRS or PRACH that is configured by higher layers on a set of symbols on another cell if at least one symbol from the set of symbols is indicated as downlink by tdd-UL-DLConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or is a symbol corresponding to one or more of a PDCCH, PDSCH, or CSI-RS reception that is configured by higher layers on the reference cell based on at least one of:o at least one symbol on another cell is a non-FD symbol;o at least one symbol on another cell is an FD symbol; ando at least one symbol on another cell is an FD symbol with uplink subband with a certain configuration, e.g., the configuration is DU or UD.

174. The device of one of claims 142 to 173, adapted to not receive and process one or more of a PDCCH, PDSCH or CSI-RS that is configured by higher layers on a set of symbols on another cell if at least one symbol from the set of symbols is indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or is a symbol corresponding to a SRS, or an FD symbol, or PUCCH, PUSCH, or PRACH transmission that is configured by higher layers on the reference cell.2025F68137 - 25014 103175. The device of claim 174, wherein the FD symbol is further configured with a link direction signal indicating uplink transmission or dynamically configured using one or more of SFI, DCI, dynamic link direction signal etc. for uplink.

176. The device of claim 174 or 175, wherein the FD symbol comprises an uplink subband with a certain configuration, e.g., the configuration is DU or UD.

177. The device of one of claims 142 to 176, adapted to not receive and process one or more of a PDCCH, PDSCH or CSI-RS that is configured by higher layers on a set of symbols on another cell if at least one symbol from the set of symbols is indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or is a symbol corresponding to one or more of a SRS, or PUCCH, PUSCH, or PRACH transmission that is configured by higher layers on the reference cell based on at least one of:o if at least one symbol on another cell is a non-FD symbol;o if at least one symbol on another cell is an FD symbol;o if at least one symbol on another cell is a FD symbol with downlink subband with a certain configuration. E.g., the configuration is DU or UD or reception is allowed on both the downlink subbands as in DUD configuration.

178. The device of one of claims 142 to 177, adapted to assumes a symbol indicated as downlink or uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL- DLConfigurationDedicated on another cell to be flexible, if the UE is respectively configured by higher layers to transmit one or more of a SRS, PUCCH, PUSCH and PRACH or to receive one or more of a PDCCH, PDSCH and CSI-RS on the reference cell.

179. The device of claim 178, adapted to operate based on a configuration according to which the transmission or reception is configured on an SBFD symbol of the reference cell.

180. The device of claim 179, adapted to operate according to■ the reception being configured in only one downlink subband;■ the reception being configured in both the downlink subbands;■ the transmission being within an uplink subband, e.g., it further depends on the type of configuration like DU or UD or DUD, etc.

181. The device of claim 179 or 180, adapted to operate according to the transmission or reception is configured on a non-SBFD symbol of the reference cell.2025F68137 - 25014 104182. The device of one of claims 142 to 181, adapted to assume a symbol indicated as downlink or uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL- DLConfigurationDedicated on another cell to be flexible or FD, based on FD being configured on the another cell and / or based on a configuration by higher layers to transmit one or more of SRS, PLICCH, PLISCH, or PRACH or to receive one or more of PDCCH, PDSCH, or CSI-RS on the reference cell.

183. The device of claim 182, adapted to consider FD only if the symbol is indicated as downlink.

184. The device of one of claims 142 to 183, adapted to not expect to detect a first DCI format scheduling a transmission or reception on a symbol on a first cell and a second DCI format scheduling a reception or transmission on the symbol on a second cell, respectively.

185. A radio device for communicating with one or more user devices, UEs, of a wireless communication system, the UEs being in accordance with one or more of the previous claims;wherein the radio device is to communicate with the one or more UEs using a radio signal comprising a plurality of time blocks in a time domain, and frequency block in a frequency domain.

186. The radio device of claim 185, wherein the radio device is one or more of the following:a base station, BS, a macro cell base station, or a small cell base station, or a central unit, CU, of a base station, or a distributed unit, DU, of a base station, or an Integrated Access and Backhaul, IAB, node, or a road side unit, RSU, or a WiFi access point, AP, or a UE, or a sidelink, SL, UE, or a group leader UE, GL-UE, or a relay or a remote radio head, or an AMF, or an SMF, or a core network, CN, entity, or mobile edge computing, MEC, entity, or a network slice as in the NR or 5G core context, or any transmission and reception point, TRP, one of a TRP as in multi-TRP, mTRP, enabling an item or a device to communicate using the wireless communication network, the item or device being provided with network connectivity to communicate using the wireless communication network, or a non-terrestrial device, e.g., a moving or stationary air-borne device, like a drone, an unmanned aerial vehicle, UAV, or an airplane, or a moving or stationary space- borne device, like a low earth orbit, LEO, satellite, like a LEO-600 satellite or a LEO-12002025F68137 - 25014 105satellite, a medium earth orbit, MEO, satellite, or a geosynchronous earth orbit, GEO, satellite.