Methods, communications devices, and network infrastructure equipment

Abstract

Methods, communications device, infrastructure equipment, and circuitry for resolving collisions between uplink and downlink transmissions located in different frequency sub-bands (e.g. in an SBFD slot). Based on whether the uplink and downlink transmissions are dynamically scheduled transmissions or configured transmissions, a particular transmission is prioritised. Generally, dynamically scheduled transmissions are prioritised over configured transmissions, however other factors such as associated L1 priority can provide alternative prioritisations.

Description

[0001] METHODS, COMMUNICATIONS DEVICES, AND NETWORK INFRASTRUCTURE EQUIPMENT

[0002] The present application claims the Paris Convention priority of European patent application EP22198464.4, filed 28 September 2022, the contents of which are hereby incorporated by reference

[0003] BACKGROUND

[0004] Field of Disclosure

[0005] The present disclosure relates to a communications device, network infrastructure equipment and methods of operating a communications device to receive data from a wireless communications network.

[0006] Description of Related Art

[0007] The “background” description provided herein is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description which may not otherwise qualify as prior art at the time of filing, are neither expressly or impliedly admitted as prior art against the present invention.

[0008] Modern mobile telecommunication systems, such as those based on the 3GPP defined UMTS and Long Term Evolution (LTE) architecture, are able to support a wider range of services than simple voice and messaging services offered by previous generations of mobile telecommunication systems. For example, with the improved radio interface and enhanced data rates provided by LTE systems, a user is able to enjoy high data rate applications such as mobile video streaming and mobile video conferencing that would previously only have been available via a fixed line data connection. The demand to deploy such networks is therefore strong and the coverage area of these networks, i.e. geographic locations where access to the networks is possible, is expected to continue to increase rapidly.

[0009] Wireless communications networks are expected to routinely and efficiently support communications with an ever-increasing range of devices associated with a wide range of data traffic profiles and types. For example, it is expected that wireless communications networks efficiently support communications with devices including reduced complexity devices, machine type communication (MTC) devices, high resolution video displays, virtual reality headsets and so on. Some of these different types of devices may be deployed in very large numbers, for example low complexity devices for supporting the “The Internet of Things”, and may typically be associated with the transmissions of relatively small amounts of data with relatively high latency tolerance. Other types of device, for example supporting high-definition video streaming, may be associated with transmissions of relatively large amounts of data with relatively low latency tolerance. Other types of device, for example used for autonomous vehicle communications and for other critical applications, may be characterised by data that should be transmitted through the network with low latency and high reliability. A single device type might also be associated with different traffic profiles I characteristics depending on the application(s) it is running. For example, different consideration may apply for efficiently supporting data exchange with a smartphone when it is running a video streaming application (high downlink data) as compared to when it is running an Internet browsing application (sporadic uplink and downlink data) or being used for voice communications by an emergency responder in an emergency scenario (data subject to stringent reliability and latency requirements). In view of this there is a desire for current generation wireless communications networks, for example those referred to as 5G or new radio (NR) systems I new radio access technology (RAT) systems, as well as future iterations I releases of existing systems, to efficiently support connectivity for a wide range of devices associated with different applications and different characteristic data traffic profiles and requirements.

[0010] One example of a new service is referred to as Ultra Reliable Low Latency Communications (URLLC) services which, as its name suggests, requires that a data unit or packet be communicated with a high reliability and with a low communications delay. Another example of a new service is enhanced Mobile Broadband (eMBB) services, which are characterised by a high capacity with a requirement to support up to 20 Gb / s. URLLC and eMBB type services therefore represent challenging examples for both LTE type communications systems and 5G / NR communications systems.

[0011] 5G NR has continuously evolved and the current work plan includes 5G-NR-advanced in which some further enhancements are expected, especially to support new use- cases / scenarios with higher requirements. The desire to support these new use-cases and scenarios gives rise to new challenges for efficiently handling communications in wireless communications systems that need to be addressed.

[0012] SUMMARY OF THE DISCLOSURE

[0013] The present disclosure can help address or mitigate at least some of the issues discussed above.

[0014] According to a first aspect of the invention, there is provided a method for a communications device configured to transmit signals to and / or to receive signals from an infrastructure equipment of a wireless communications network via a wireless radio interface provided by the wireless communications network, the method comprising: identifying a collision between a first uplink transmission and a second downlink transmission, the first uplink transmission and first downlink transmission being located in different frequency sub-bands; determining whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions; based on the determination of whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions, prioritising the first uplink transmission or the first downlink transmission as a prioritised transmission.

[0015] According to a second aspect of the invention, there is provided a method of operating an infrastructure equipment configured to transmit signals to and / or receive signals from a plurality of communications devices via a wireless access interface provided by a wireless communications network, the method comprising: identifying a collision between a first uplink transmission and a second downlink transmission, the first uplink transmission and first downlink transmission being located in different frequency sub-bands; determining whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions; based on the determination of whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions, prioritising the first uplink transmission or the first downlink transmission as a prioritised transmission.

[0016] Respective aspects and features of the present disclosure are defined in the appended claims.

[0017] It is to be understood that both the foregoing general description and the following detailed description are exemplary, but are not restrictive, of the present technology. The described embodiments, together with further advantages, will be best understood by reference to the following detailed description taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] A more complete appreciation of the disclosure and many of the attendant advantages thereof will be readily obtained as the same becomes better understood by reference to the following detailed description when considered in connection with the accompanying drawings wherein like reference numerals designate identical or corresponding parts throughout the several views, and wherein:

[0019] Figure 1 schematically represents some aspects of an LTE-type wireless telecommunication system which may be configured to operate in accordance with certain embodiments of the present disclosure;

[0020] Figure 2 schematically represents some aspects of a new radio access technology (RAT) wireless telecommunications system which may be configured to operate in accordance with certain embodiments of the present disclosure;

[0021] Figure 3 is a schematic block diagram of an example infrastructure equipment and communications device which may be configured to operate in accordance with certain embodiments of the present disclosure;

[0022] Figure 4 schematically illustrates an example of inter-cell cross link interference.

[0023] Figure 5 schematically illustrates an example of intra-cell cross link interference

[0024] Figure 6 illustrates an example division of system bandwidth into dedicated uplink and downlink sub-bands.

[0025] Figure 7 illustrates an example of transmission power leakage.

[0026] Figure 8 illustrates an example of receiver power selectivity.

[0027] Figure 9 illustrates an example of inter sub-band interference.

[0028] Figure 10 illustrates an example of intra sub-band interference.

[0029] Figure 11 illustrates an example of collision between an uplink transmission and a downlink transmission.

[0030] Figure 12 illustrates an approach according to an example of the present disclosure for resolving collision between an uplink transmission and a downlink transmission, where both transmissions are dynamically scheduled transmissions.

[0031] Figure 13 illustrates an approach according to an example of the present disclosure for resolving collision between an uplink transmission and a downlink transmission, where both transmissions are dynamically scheduled transmissions.

[0032] Figure 14 illustrates an approach according to an example of the present disclosure for resolving collision between an uplink transmission and a downlink transmission, where one transmission is a dynamically scheduled transmission, and the other transmission is a configured transmission.

[0033] Figure 15 illustrates an approach according to an example of the present disclosure for resolving collision between an uplink transmission and a downlink transmission, where both transmissions are configured transmissions.

[0034] Figure 16 illustrates a method for resolving collision between an uplink transmission and a downlink transmission according to an example of the present disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0035] Long Term Evolution Advanced Radio Access Technology (4G)

[0036] Figure 1 provides a schematic diagram illustrating some basic functionality of a mobile telecommunications network / system 6 operating generally in accordance with LTE principles, but which may also support other radio access technologies, and which may be adapted to implement embodiments of the disclosure as described herein. Various elements of Figure 1 and certain aspects of their respective modes of operation are well-known and defined in the relevant standards administered by the 3GPP (RTM) body, and also described in many books on the subject, for example, Holma H. and Toskala A [1], It will be appreciated that operational aspects of the telecommunications networks discussed herein which are not specifically described (for example in relation to specific communication protocols and physical channels for communicating between different elements) may be implemented in accordance with any known techniques, for example according to the relevant standards and known proposed modifications and additions to the relevant standards.

[0037] The network 6 includes a plurality of base stations 1 connected to a core network 2. Each base station provides a coverage area 3 (i.e. a cell) within which data can be communicated to and from communications devices 4. Although each base station 1 is shown in Figure 1 as a single entity, the skilled person will appreciate that some of the functions of the base station may be carried out by disparate, inter-connected elements, such as antennas (or antennae), remote radio heads, amplifiers, etc. Collectively, one or more base stations may form a radio access network.

[0038] Data is transmitted from base stations 1 to communications devices or mobile terminals (MT) 4 within their respective coverage areas 3 via a radio downlink. Data is transmitted from communications devices 4 to the base stations 1 via a radio uplink. The core network 2 routes data to and from the communications devices 4 via the respective base stations 1 and provides functions such as authentication, mobility management, charging and so on. The communications or terminal devices 4 may also be referred to as mobile stations, user equipment (UE), user terminal, mobile radio, communications device, and so forth. Services provided by the core network 2 may include connectivity to the internet or to external telephony services. The core network 2 may further track the location of the communications devices 4 so that it can efficiently contact (i.e. page) the communications devices 4 for transmitting downlink data towards the communications devices 4.

[0039] Base stations, which are an example of network infrastructure equipment, may also be referred to as transceiver stations, nodeBs, e-nodeBs, eNB, g-nodeBs, gNB and so forth. In this regard different terminology is often associated with different generations of wireless telecommunications systems for elements providing broadly comparable functionality. However, certain embodiments of the disclosure may be equally implemented in different generations of wireless telecommunications systems, and for simplicity certain terminology may be used regardless of the underlying network architecture. That is to say, the use of a specific term in relation to certain example implementations is not intended to indicate these implementations are limited to a certain generation of network that may be most associated with that particular terminology.

[0040] New Radio Access Technology (5G (NR))

[0041] An example configuration of a wireless communications network which uses some of the terminology proposed for and used in NR and 5G is shown in Figure 2. In Figure 2 a plurality of transmission and reception points (TRPs) 10 are connected to distributed control units (DUs) 41 , 42 by a connection interface represented as a line 16. Each of the TRPs 10 is arranged to transmit and receive signals via a wireless access interface within a radio frequency bandwidth available to the wireless communications network. Thus, within a range for performing radio communications via the wireless access interface, each of the TRPs 10, forms a cell of the wireless communications network as represented by a circle 12. As such, wireless communications devices 14 which are within a radio communications range provided by the cells 12 can transmit and receive signals to and from the TRPs 10 via the wireless access interface. Each of the distributed units 41 , 42 are connected to a central unit (CU) 40 (which may be referred to as a controlling node) via an interface 46. The central unit 40 is then connected to the core network 20 which may contain all other functions required to transmit data for communicating to and from the wireless communications devices and the core network 20 may be connected to other networks 30.

[0042] The elements of the wireless access network shown in Figure 2 may operate in a similar way to corresponding elements of an LTE network as described with regard to the example of Figure 1. It will be appreciated that operational aspects of the telecommunications network represented in Figure 2, and of other networks discussed herein in accordance with embodiments of the disclosure, which are not specifically described (for example in relation to specific communication protocols and physical channels for communicating between different elements) may be implemented in accordance with any known techniques, for example according to currently used approaches for implementing such operational aspects of wireless telecommunications systems, e.g. in accordance with the relevant standards.

[0043] The TRPs 10 of Figure 2 may in part have a corresponding functionality to a base station or eNodeB of an LTE network. Similarly, the communications devices 14 may have a functionality corresponding to the UE devices 4 known for operation with an LTE network. It will be appreciated therefore that operational aspects of a new RAT network (for example in relation to specific communication protocols and physical channels for communicating between different elements) may be different to those known from LTE or other known mobile telecommunications standards. However, it will also be appreciated that each of the core network component, base stations and communications devices of a new RAT network will be functionally similar to, respectively, the core network component, base stations and communications devices of an LTE wireless communications network.

[0044] In terms of broad top-level functionality, the core network 20 connected to the new RAT telecommunications system represented in Figure 2 may be broadly considered to correspond with the core network 2 represented in Figure 1 , and the respective central units 40 and their associated distributed units I TRPs 10 may be broadly considered to provide functionality corresponding to the base stations 1 of Figure 1. The term network infrastructure equipment I access node may be used to encompass these elements and more conventional base station type elements of wireless telecommunications systems. Depending on the application at hand the responsibility for scheduling transmissions which are scheduled on the radio interface between the respective distributed units and the communications devices may lie with the controlling node I central unit and I or the distributed units I TRPs. A communications device 14 is represented in Figure 2 within the coverage area of the first communication cell 12. This communications device 14 may thus exchange signalling with the first central unit 40 in the first communication cell 12 via one of the distributed units I TRPs 10 associated with the first communication cell 12.

[0045] It will further be appreciated that Figure 2 represents merely one example of a proposed architecture for a new RAT based telecommunications system in which approaches in accordance with the principles described herein may be adopted, and the functionality disclosed herein may also be applied in respect of wireless telecommunications systems having different architectures.

[0046] Thus, certain embodiments of the disclosure as discussed herein may be implemented in wireless telecommunication systems I networks according to various different architectures, such as the example architectures shown in Figures 1 and 2. It will thus be appreciated the specific wireless telecommunications architecture in any given implementation is not of primary significance to the principles described herein. In this regard, certain embodiments of the disclosure may be described generally in the context of communications between network infrastructure equipment I access nodes and a communications device, wherein the specific nature of the network infrastructure equipment I access node and the communications device will depend on the network infrastructure for the implementation at hand. For example, in some scenarios the network infrastructure equipment I access node may comprise a base station, such as an LTE-type base station 1 as shown in Figure 1 which is adapted to provide functionality in accordance with the principles described herein, and in other examples the network infrastructure equipment may comprise a control unit I controlling node 40 and / or a TRP 10 of the kind shown in Figure 2 which is adapted to provide functionality in accordance with the principles described herein.

[0047] A more detailed diagram of some of the components of the network shown in Figure 2 is provided by Figure 3. In Figure 3, a TRP 10 as shown in Figure 2 comprises, as a simplified representation, a wireless transmitter 30, a wireless receiver 32 and a controller or controlling processor 34 which may operate to control the transmitter 30 and the wireless receiver 32 to transmit and receive radio signals to one or more UEs 14 within a cell 12 formed by the TRP 10. As shown in Figure 3, an example UE 14 is shown to include a corresponding transmitter circuit 49, a receiver circuit 48 and a controller circuit 44 which is configured to control the transmitter circuit 49 and the receiver circuit 48 to transmit signals representing uplink data to the wireless communications network via the wireless access interface formed by the TRP 10 and to receive downlink data as signals transmitted by the transmitter circuit 30 and received by the receiver circuit 48 in accordance with the conventional operation.

[0048] The transmitter circuits 30, 49 and the receiver circuits 32, 48 (as well as other transmitters, receivers and transceivers described in relation to examples and embodiments of the present disclosure) may include radio frequency filters and amplifiers as well as signal processing components and devices in order to transmit and receive radio signals in accordance for example with the 5G / NR standard. The controller circuits 34, 44 (as well as other controllers described in relation to examples and embodiments of the present disclosure) may be, for example, a microprocessor, a CPU, or a dedicated chipset, etc., configured to carry out instructions which are stored on a computer readable medium, such as a non-volatile memory. The processing steps described herein may be carried out by, for example, a microprocessor in conjunction with a random access memory, operating according to instructions stored on a computer readable medium. The transmitters, the receivers and the controllers are schematically shown in Figure 3 as separate elements for ease of representation. However, it will be appreciated that the functionality of these elements can be provided in various different ways, for example using one or more suitably programmed programmable computer(s), or one or more suitably configured application-specific integrated circuit(s) I circuitry I chip(s) I chipset(s). As will be appreciated the infrastructure equipment I TRP I base station as well as the UE I communications device will in general comprise various other elements associated with its operating functionality.

[0049] As shown in Figure 3, the TRP 10 also includes a network interface 50 which connects to the DU 42 via a physical interface 16. The network interface 50 therefore provides a communication link for data and signalling traffic from the TRP 10 via the DU 42 and the CU 40 to the core network 20.

[0050] The interface 46 between the DU 42 and the CU 40 is known as the F1 interface which can be a physical or a logical interface. The F1 interface 46 between CU and DU may operate in accordance with specifications 3GPP TS 38.470 and 3GPP TS 38.473, and may be formed from a fibre optic or other wired or wireless high bandwidth connection. In one example the connection 16 from the TRP 10 to the DU 42 is via fibre optic. The connection between a TRP 10 and the core network 20 can be generally referred to as a backhaul, which comprises the interface 16 from the network interface 50 of the TRP10 to the DU 42 and the F1 interface 46 from the DU 42 to the CU 40.

[0051] Full Duplex Time Division Duplex (FD-TDD)

[0052] NR / 5G networks can operate using Time Division Duplex (TDD), where an entire frequency band or carrier is switched to either downlink or uplink transmissions for a time period and can be switched to the other of downlink or uplink transmissions at a later time period. Currently, TDD operates in Half Duplex mode (HD-TDD) where the gNB or UE can, at a given time, either transmit or receive packets, but not both at the same time. As wireless networks transition from NR to 5G-Advanced networks, a proposed new feature of such networks is to enhance duplexing operation for Time Division Multiplexing (TDD) by enabling Full Duplex operation in TDD (FD-TDD) [2], In FD-TDD, a gNB can transmit and receive data to and from the UEs at the same time on the same frequency band or carrier. In addition, a UE can operate either in HD-TDD or FD-TDD mode, depending on its capability. For example, when UEs are only capable of supporting HD-TDD, FD-TDD is achieved at the gNB by scheduling a downlink (DL) transmission to a first UE and scheduling an uplink (UL) transmission from a second UE within the same orthogonal frequency division multiplexing (OFDM) symbol (i.e. at the same time). Conversely, when UEs are capable of supporting FD-TDD, FD-TDD is achieved both at the gNB and the UE, where the gNB can simultaneously schedule this UE with DL and UL transmissions within the same OFDM symbol by scheduling the DL and UL transmissions at different frequencies (e.g. physical resource blocks (PRBs)) of the system bandwidth. A UE supporting FD-TDD requires more complex hardware than a UE that only supports HD-TDD. Development of current 5G networks is focused primarily on enabling FD-TDD at the gNB with UEs operating in HD-TDD mode.

[0053] Motivations for enhancing duplexing operation for TDD include an improvement in system capacity, reduced latency, and improved uplink coverage. For example, in current HD-TDD systems, OFDM symbols are allocated only for either a DL or UL direction in a semi-static manner. Hence, if one direction experiences less or no data, the spare resources cannot be used in the other direction, or are, at best, under-utilized. However, if resources can be used for DL data and UL data (as in FD-TDD) at the same time, the resource utilization in the system can be improved. Furthermore, in current HD-TDD systems, a UE can receive DL data, but cannot transmit UL data at the same time, which causes delays. If a gNB or UE is allowed to transmit and receive data at the same time (as with FD-TDD), the traffic latency will be improved. In addition, UEs are usually limited in the UL transmissions when located close to the edge of a cell. While the UE coverage at the cell-edge can be improved if more time domain resources are assigned to UL transmissions (e.g. repetitions), if the UL direction is assigned more time resources, fewer time resources can be assigned to the DL direction, which can lead to system imbalance. Enabling FD-TDD would help allow a UE to be assigned more UL time resources when required, without sacrificing DL time resources.

[0054] Inter-Cell Cross Link Interference (CLI) In NR systems, a slot format (i.e. the allocation of DL and UL OFDM symbols in a slot) can be semi-statical ly or dynamically configured, where each OFDM symbol (OS) in a slot can be configured as Downlink (DL), Uplink (UL) or Flexible (F). An OFDM symbol that is semi- statically configured to be Flexible can be indicated dynamically as DL, UL or remain as Flexible by a Dynamic Slot Format Indicator (SFI), which is transmitted in a Group Common (GO) DCI using DCI Format 2_0, where the CRC of the GC-DCI is masked with SFI-RNTI. Flexible OFDM Symbols that remain Flexible after instruction from the SFI can be changed to a DL symbol or an UL symbol by a DL Grant or an UL Grant respectively. That is, a DL Grant scheduling a PDSCH that overlaps Flexible OFDM Symbols would convert these Flexible OFDM Symbols to DL and similarly an UL Grant scheduling a PUSCH that overlaps Flexible OFDM Symbols would convert these Flexible OFDM Symbols to UL.

[0055] Since each gNB in a network can independently change the configuration of each OFDM symbol, either semi-statical ly or dynamically, it is possible that in a particular OFDM symbol, one gNB is configured for UL and a neighbour gNB is configured for DL. This causes inter-cell Cross Link Interference (CLI) among the conflicting gNBs. Inter-cell CLI occurs when a UE’s UL transmission interferes with a DL reception by another UE in another cell, or when a gNB’s DL transmission interferes with an UL reception by another gNB. That is, inter-cell CLI is caused by non-aligned (conflicting) slot formats among neighbouring cells. An example is shown in Figure 4, where gNB1 411 and gNB2 412 have synchronised slots. At a given slot, gNBTs 411 slot format = {D, D, D, D, D, D, D, D, D, D, U, U, U, U} whilst gNB2’s 412 slot format = {D, D, D, D, D, D, D, D, D, D, D, U, U, U}, where ‘D’ indicates DL and ‘U’ indicates UL. Inter-cell CLI occurs during the 11thOFDM symbol of the slot, where gNB1 411 is performing UL whilst gNB2 412 is performing DL. Specifically, inter-cell CLI 441 occurs between gNB1 411 & gNB2 412, where gNB2’s 412 DL transmission 431 interferes with gNBTs 411 UL reception 432. CLI 442 also occurs between UE1 421 & UE2422, where UETs 421 UL transmission 432 interferes with UE2’s 422 DL reception 431.

[0056] Some legacy implementations attempt to reduce inter-cell CLI in TDD networks caused by flexible and dynamic slot format configurations. Two CLI measurement reports to manage and coordinate the scheduling among neighbouring gNBs include: sounding reference signal (SRS) reference signal received power (RSRP) and CLI received signal strength indicator (RSSI). In SRS-RSRP, a linear average of the power contribution of an SRS transmitted by a UE is measured by a UE in a neighbour cell. This is measured over the configured resource elements within the considered measurement frequency bandwidth, in the time resources in the configured measurement occasions. In CLI-RSSI, a linear average of the total received power observed is measured only at certain OFDM symbols of the measurement time resource(s), in the measurement bandwidth, over the configured resource elements for measurement by a UE.

[0057] Intra-Cell Cross Link Interference (CLI)

[0058] In addition to inter-cell CLI and remote interference, FD-TDD also suffers from intra-cell CLI at the gNB and at the UE. An example is shown in Figure 5, where a gNB 510 is capable of FD-TDD and is simultaneously receiving UL transmission 531 from UE1 521 and transmitting a DL transmission 542 to UE2 522. At the gNB 510, intra-cell CLI is caused by the DL transmission 542 at the gNB’s transmitter self-interfering 541 with its own receiver that is trying to decode UL signals 531 . At UE2 522, intra-cell CLI 532 is caused by an aggressor UE, e.g. UE1 521 , transmitting in the UL 531 , whilst a victim UE, e.g. UE2 522, is receiving a DL signal 542.

[0059] The intra-cell CLI at the gNB due to self-interference can be significant, as the DL transmission can in some cases be over 100dB more powerful than the UL reception. Accordingly, complex RF hardware and interference cancellation are required to isolate this self-interference. In order to reduce self-interference at the gNB, one possibility is to divide the system (i.e. UE / gNB) bandwidth into non-overlapping sub-bands 601-604 allocated to UL or DL, as shown in Figure 6, where simultaneous DL and UL transmissions may occur in different sub-bands 601-604, i.e. in different sets of frequency Resource Blocks (RB). This may be referred to as Subband Full Duplex (SBFD). While Figure 6 shows the system bandwidth as being divided into four sub-bands, substantially any number of sub-bands could be used. For example, the system bandwidth may be divided into three sub-bands, which may include two downlink subbands 601 , 603 and one uplink sub-band 602, however other sub-band arrangements are envisioned.

[0060] To reduce leakage from one sub-band 601-604 to another, a guard sub-band 610 may be configured between UL and DL sub-bands 601-604. An example is shown in Figure 6, where a TDD system bandwidth is divided into 4 sub-bands 601 , 602, 603, 604: Sub-band#1 601 , Sub-band#2 602, Sub-band#3 603 and Sub-band#4604 such that Sub-band#1 601 and Sub- band#3 603 are used for DL transmissions whilst Sub-band#2 602 and Sub-band#4 604 are used for UL transmissions. Guard sub-bands 610 are configured between UL Sub-band#4 604 and DL Sub-band#3 603, between DL Sub-band#3 603 and UL Sub-band#2 602 and between UL Sub-band#2 602 and DL Sub-band#1 601. The arrangement of sub-bands 601- 604 shown in Figure 6 is just one possible arrangement of the sub-bands and other arrangements are possible, and guard bands may be used in substantially any sub-band arrangement.

[0061] Inter Sub-band interference

[0062] Although a transmission is typically scheduled within a specific frequency channel (or subband), i.e. a specific set of RBs, transmission power can leak out to other channels. This occurs because channel filters are not perfect, and as such the roll-off of the filter will cause power to leak into channels adjacent to the intended specific frequency channel. While the following discussion uses the term “channel”, the term “sub-band”, such as the sub-bands shown in Figure 6, may be used instead.

[0063] An example of transmission generating adjacent channel leakage is shown in Figure 7. Here, the wanted transmission (Tx) power is the transmission power in the selected frequency band (i.e. the assigned channel 710). Due to roll-off of the transmission filter and nonlinearities in components of the transmitter, some transmission power is leaked into adjacent channels (including an adjacent channel 720), as shown in Figure 7. The ratio of the power within the assigned frequency channel 710 to the power in the adjacent channel 720 is the Adjacent Channel Leakage Ratio (ACLR). The leakage power 750 will cause interference at a receiver that is receiving the signal in the adjacent channels 720.

[0064] Similarly, a receiver’s filter is also not perfect and will receive unwanted power from adjacent channels due to its own filter roll-off. An example of filter roll-off at a receiver is shown in Figure 8. Here, a receiver is configured to receive transmissions in an assigned channel 810, however the imperfect nature of the receiver filter means that some transmission power 850 can be received in adjacent channels 820. Therefore, if a signal 830 is transmitted on an adjacent channel 820, the receiver will inadvertently receive the adjacent signal 830 in the adjacent channel 820, to an extent. The ratio of the received power in the assigned frequency channel 810 to the received power 850 in the adjacent channel 820 is the Adjacent Channel Selectivity (ACS).

[0065] The combination of the ACL from the transmitter and the ACS of a receiver will lead to adjacent channel interference (ACI), otherwise known as inter-sub-band interference, at the receiver. An example is shown in Figure 9, where an aggressor transmits a signal 910 in an adjacent channel at a lower frequency than the victim’s receiving 920 channel. The interference 950 caused by the aggressor’s transmission includes the ACL of the aggressor’s transmitting filter and the ACS of the victim’s receiving filter. In other words, the receiver will experience interference 950 in the ACI frequency range shown in Figure 9.

[0066] As such, due to adjacent channel interference (ACI), cross link interference (CLI) will still occur despite the use of different sub-bands 601-604 for DL and UL transmissions in a FD-TDD cell.

[0067] Intra Sub-band Interference

[0068] Intra sub-band interference can occur when the sub-band configurations among gNBs are not aligned in the frequency domain. Here, CLI may occur in the overlapping frequencies of intercell sub-bands. An example is shown in Figure 10, where gNBTs 1011 system bandwidth is divided into UL sub-band UL-SB#1 1052 occupying f to fa and DL sub-band DL-SB#1 1051 occupying fa to fa, whilst gNB2’s 1012 system bandwidth is divided into UL sub-band UL-SB#2 1054 occupying fa to fa and DL sub-band DL-SB#2 1053 occupying fa to fa. The non-aligned sub-band configurations 1050 cause UL-SB#1 1052 to overlap with DL-SB#2 1053, thereby causing intra sub-band CLI within the overlapping frequencies fa to fa. In this example, intra sub-band CLI 1041 occurs at gNB1 1011 due to gNB2’s 1012 DL transmission 1032 within fa to fa in DL-SB#2 1053 interfering with gNBTs 1011 UL reception 1031 from UE1 1021 within fa to fa in UL-SB#1 1052. In addition, intra sub-band CLI 1042 occurs at UE2 1022 due to UETs 1021 UL transmission 1031 within fa to fa in UL-SB#1 1052 interfering with UE2’s 1022 DL reception 1032 within fa to fa in DL-SB#2 1053.

[0069] Uplink L1 Priority

[0070] In legacy wireless communications networks (e.g. 3GPP Release-15), there are no priority levels in the physical layer. That is, priority levels exist for the Medium Access Control (MAC) layer, where 16 priority levels exist, but not the physical layer. Therefore, when two uplink transmissions collide, their information is multiplexed and transmitted using a single channel. The possible collisions are Physical Uplink Control Channel (PUCCH) with another PUCCH, and PUCCH with Physical Uplink Shared Channel (PUSCH).

[0071] As discussed above, a UE can be configured to provide eMBB and URLLC services. Since eMBB and URLLC have different latency requirements, their uplink transmissions may collide. For example, after an eMBB uplink transmission has been scheduled, an urgent URLLC packet may arrive which would need to be scheduled immediately and therefore its transmission may collide with the eMBB transmission. In order to handle such intra-UE collisions with different latency & reliability requirements, two priority levels at the Physical Layer, known as L1 priority, have recently been introduced (e.g. 3GPP Release-16) for uplink transmissions, i.e. PUCCH or PUSCH transmissions. In such arrangements, intra-UE prioritisation is used. That is, when two UL transmissions with different Physical Layer priority levels (L1 priority) collide, the UE will drop the lower priority transmission. If both uplink transmissions have the same L1 priorities, then the UE may reuse legacy procedures.

[0072] L1 priority levels may in some cases be indicated to the UE by the gNB in the 1-bit priority indicator field of a Downlink Control Information (DCI) message. In such an example, “0” indicates low L1 priority and “1” indicates high L1 priority. The L1 priority for a PUSCH is indicated in the UL Grant carried by DCI Format 0_1 and 0_2. The L1 priority for a PUCCH carrying Hybrid Automatic Repeat Request acknowledgment (HARQ-ACK) feedback for a PDSCH is indicated in the DL Grant scheduling a PDSCH, and is carried by DCI Format 1_1 and 1 2. Uplink and Downlink Collisions in SBFD Slots

[0073] In legacy TDD systems, a UE does not expect to receive DL or transmit UL messages at the same time. However, with SBFD slots, such as those described above and shown in Figure 6, where the bandwidth of a given slot is divided into multiple sub-bands allocated to uplink or downlink, it is possible for a UE to have downlink and uplink messages at the same time. As an example, a Physical Downlink Control Channel (PDCCH) search space (PDSCH SS) may be configured for all slots (or a large number of slots), thereby increasing the likelihood of a collision between the PDCCH SS and an uplink transmission. A PDCCH SS is a set of physical resources, such as a control resource set (CORESET) that a UE periodically monitors in order to blind decode for a potential PDCCH. Such a PDCCH may carry a DCI for scheduling and / or other information, such as a slot format indicator (SFI), a UL cancellation indicator, transmit power control (TPC), and / or a downlink pre-emption indicator.

[0074] Figure 11 shows an example of such a collision between an uplink and downlink transmission. In the example of Figure 11 , Slot n and Slot n+4 are DL and UL slots respectively whilst Slot n+1 , n+2 and n+3 are SBFD slots configured such that it has one DL subband and one UL subband. In Figure 11 , the arrows between transmissions identify a scheduling or HARQ-ACK relationship between the transmissions. For example, the arrow between DCI#1 and PUSCH#1 identifies that PUSCH#1 is scheduled by DCI#1. A similar relationship is identified by the arrow between DCI#2 and PDSCH#1. In addition, the arrow between PDSCH#1 and PUCCH#1 identified that PUCCH#1 carries a HARQ-ACK for PDSCH#1. Similar relationships are shown by arrows in Figures 12-15.

[0075] In this example of Figure 11 , the gNB configures a CORESET containing a PDCCH SS in the first two OFDM symbols of every slot with DL resources, i.e. in Slot n, n+1 , n+2 and n+3. In Slot n, the UE detects a PDCCH carrying DCI#1 in the PDCCH SS which schedules PUSCH#1 to transmit in Slot n+1. In Slot n+1 , the UE has to monitor for PDCCH in the PDCCH SS and also transmit PUSCH#1 between time t2and t3, thereby causing a DL & UL collision. Another collision is shown in Slot n+3 where PUCCH#1 carries the HARQ-ACK for PDSCH#1 , which overlaps with another PDCCH SS CORESET between time and h. Hence there is a need to resolve such collisions between DL & UL in SBFD slots.

[0076] According to example teachings of the present disclosure, conflicts between DL and UL in SBFD slots can be resolved by prioritising the DL or the UL, based at least in part on whether the UL and DL are dynamically scheduled transmissions, or non-dynamically scheduled transmissions. Dynamically scheduled transmissions are transmissions that are scheduled by a DL Grant or UL Grant, such as such as PDSCH, PUSCH and PUCCH. Non-dynamically scheduled transmissions may be configured transmissions, which may occur periodically, such as Configured Grant PUSCH (CG-PUSCH), Semi-Persistent Scheduling (SPS) PDSCH, and PDCCH SS.

[0077] According to example teachings of the present disclosure, it is possible to resolve collisions between two or more dynamically scheduled transmissions (i.e. a scheduled DL transmission and a scheduled UL transmission in an SBFD slot). In one example, if a UE is scheduled with a DL transmission and an UL transmission that collide in an SBFD slot, the UE may ignore the earlier scheduled transmission and receive / transmit the later scheduled transmission. This example enables a gNB to overwrite a previous scheduling decision with a later scheduled transmission. As such, the decision of whether a previous scheduling decision should be overridden may be made by the gNB, which would be aware of the conflict. As such, the UE may effectively assume that the gNB has determined that the later scheduled transmissions should be prioritised. Accordingly, conflicts between transmissions can be resolved while allowing a gNB to change its scheduling decisions on the fly, therefore providing flexibility in scheduling.

[0078] An example of this is shown in Figure 12, where in Slot n+3, a collision occurs between PUCCH#1 , which is scheduled by DCI#1 (to carry HARQ-ACK for PDSCH#1), and PDSCH#2, which is scheduled by DCI#2. Since DCI#2 occurs after DCI#1 , PDSCH#2 is the later scheduled transmission (i.e. the scheduling of PDSCH#2 occurred at a later time (t4) than the scheduling of PUCCH#1 (to)), and therefore PUCCH#1 is the earlier scheduled transmission. Therefore, according to this example the UE drops / ignores PUCCH#1 , i.e., the earlier scheduled transmission, and decodes PDSCH#2, i.e., the later scheduled transmission.

[0079] A UE may resolve the conflicts by dropping or ignoring the non-prioritised transmission. This may include dropping or ignoring an entirety of the non-prioritised transmission or only a portion of the non-prioritised transmission. For example, the UE may drop or ignore only the portions (i.e. OFDM symbols) of the non-prioritised transmission that conflict with the prioritised transmission. For example, in the example of Figure 12, the UE may only drop the OFDM symbols of PUCCH#1 between times t8and t9, where the collision occurs.

[0080] In some examples, the UE may resolve such a collision based on an associated L1 priority. As L1 priority is only defined for UL transmissions, such as PUSCH and PUCCH, for DL transmissions such as PDSCH, the associated L1 priority is the priority of the corresponding PUCCH carrying its HARQ-ACK. For UL transmissions, the associated L1 priority in this example is the L1 priority indicated in the UL Grant for PUSCH or DL Grant for PUCCH. The UE may examine the associated priority of the UL and DL transmissions and use this to determine which transmission to prioritise. For example, the UE may determine that the DL has a higher associated priority than the UL and therefore that the DL should be prioritised (e.g. by ignoring the UL).

[0081] An example is shown in Figure 13, where in Slot n+3, PUSCH#1 scheduled by UL Grant DCI#1 collides with PDSCH#2 scheduled by DL Grant DCI#2. PUSCH#1 is indicated in DCI#1 as Low L1 Priority (LP) whilst DCI#2 indicates PUCCH#2 as High L1 Priority (HP), and since PUCCH#2 is the corresponding PUCCH carrying HARQ-ACK for PDSCH#2, PDSCH#2 has an associated High L1 Priority. As per this example, the UE may drop PUSCH#1 , i.e., with lower L1 priority or drop the OFDM symbols colliding with PDSCH#2, and decodes PDSCH#2, i.e., with higher associated L1 priority.

[0082] In some examples, the UE may take into account both the priority of the UL and DL transmissions, as well as the scheduling time for the DL and UL. For example, the UE can first consider the L1 priority of the UL transmission and the associated L1 priority of the DL transmission, and if both have the same L1 priority (or e.g. one or both transmissions have no associated priority) the UE then considers the scheduled time of the transmission, so that it can ignore the earlier scheduled transmission. Furthermore, in some examples, the UE may consider a collision between two scheduled transmissions to be an error. Accordingly, the UE may decide on its own (e.g. based on additional criteria or randomly) to drop or ignore one of the transmissions, or to drop or ignore both transmissions.

[0083] According to example teachings of the present disclosure, it is possible to resolve collisions between a scheduled transmission and a non-scheduled transmission (i.e. a configured transmission or a control channel). In a configured transmission, the UE may be configured with periodically occurring resources, where in each occasion there may or may not be a transmission in the configured resources. Configured transmissions may include a CG- PUSCH, an SPS PDSCH, or a PUCCH carrying a HARQ-ACK for an SPS PDSCH. In collisions between a scheduled transmission and a configured transmission, the UE may generally prioritise the scheduled transmission over the non-scheduled transmission. This recognizes that the gNB is aware of the collision and if the gNB deliberately schedules a transmission to collide with a control channel, then the gNB would likely have no intention to use the control channel or configured transmissions. As such, deliberate scheduling decisions by the gNB can be prioritised.

[0084] An example of this arrangement is shown in Figure 14. In this example, an SPS (PDSCH) with a periodicity of 2 slots has been activated for the UE, and it occurs in Slot n+1 and Slot n+3 and the associated PLICCH for the SPS is transmitted in the next slot after the SPS. In Slot n+2, the PUCCH#1 associated with the SPS in Slot n+1 collides with PDSCH#1 which is scheduled by DL Grant DCI#1. As per this example, since PDSCH#1 is a dynamically scheduled transmission, the UE drops PUCCH#1 and decodes PDSCH#1. Similarly, in Slot n+3, the SPS collides with PUSCH#1 which is dynamically scheduled by UL Grant DCI#2 and in this example, the UE drops the SPS (i.e. does not attempt to decode the SPS) and transmits PUSCH#1.

[0085] In some examples, the decision regarding which transmission to prioritise may be additionally be based on an associated L1 priority for the UL and DL transmissions. For example, when a scheduled transmission collides with a configured transmission in an SBFD slot, if the configured transmission has higher associated L1 priority than the scheduled transmission, then the UE drops the scheduled transmission. Otherwise, if the configured transmission has equal or lower L1 priority than the scheduled transmission, the UE drops the configured transmission and decodes / transmits the scheduled transmission.

[0086] According to example teachings of the present disclosure, it is possible to resolve collisions between multiple non-scheduled transmissions. For example, the UE may prioritise the transmission with the higher priority level. As such, if a CG-PUSCH and an SPS PDSCH collide in an SBFD slot, the UE may drop the configured transmission with the lower associated L1 priority and transmit / decode the configured transmission with the higher associated L1 priority.

[0087] Furthermore, in some examples the UE may prioritise a transmission based on the traffic within the configured transmissions. For example, if a CG-PUSCH and an SPS PDSCH collide in an SBFD slot then the UE may firstly determine if there is any traffic for the CG-PUSCH and if not, it may monitor the SPS PDSCH. If there is traffic in the CG-PUSCH, the UE may drop the SPS and transmit the CG-PUSCH. It should be noted that resources for a configured transmission may not necessarily be utilised, even though the resources are reserved for that transmission. This prevents unused resources being prioritised over non-empty transmissions. This example may be utilized in combination with various other examples described herein. For example, the UE may first determine that both transmissions have a same priority, and then determine which transmission to prioritise based on the traffic within the configured transmissions.

[0088] In some examples, the UE may prioritise a transmission based on whether a transmissions carry a HARQ-ACK, and based on whether the HARQ-ACK is an ACK or a NACK. For example, if a PUCCH associated with a first SPS collides with a second SPS then the UE may determine if the HARQ-ACK carried by the PUCCH is NACK or ACK. This may, for example, be performed after determining that both transmissions have the same L1 priority and / or both contain traffic (i.e. are not empty / the configured resources would be utilised). If the PUCCH carries an ACK, the UE may transmit the PUCCH and ignore the SPS, otherwise if the PUCCH carries a NACK, the UE may drops the PUCCH and monitor the second SPS. This recognizes that a NACK can be caused by failed decoding of the PDSCH in the SPS or that the SPS is empty. As such, if there is a failed decoding, the gNB would retransmit the PDSCH, meaning the UE will have a second opportunity to decode the SPS PDSCH. In addition, if the SPS is empty the gNB does not expect to receive a NACK, and thus the UE can afford to drop the PUCCH carrying a NACK.

[0089] An example of this arrangement is shown in Figure 15, where the UE is configured with two SPS occasions, i.e., SPS#1 and SPS#2. The UE can be configured with up to 8 different SPS, where each of these SPS can have different periodicity, resources and TBS. SPS#1 has a periodicity of 5 slots whilst SPS#2 has a shorter periodicity of 2 slots. In Slot n+1 , PUCCH#1 which is the associated PUCCH for SPS#1 at time h in Slot n collides with SPS#2 at time t2. In this example, the UE successfully decoded a PDSCH in SPS#1 , and therefore it needs to send an ACK in PUCCH#1. The UE may therefore drop SPS#2 and transmit PUCCH#1.

[0090] In some examples, the UE may prioritise a transmission based on the type of transmission. For example, where a CG-PUSCH collides with a PDCCH search space in an SBFD slot, the UE may ignore the CG-PUSCH and monitor the PDCCH search space for a potential PDCCH. This recognizes that the gNB may have an urgent transmission and therefore needs to send a PDCCH to schedule that urgent transmission and therefore it is better that the UE monitors the PDCCH search space than to transmit the CG-PUSCH. Alternatively, the UE may transmit the CG-PUSCH and ignore the PDCCH search space, for example if the CG-PUSCH has a High L1 Priority. These examples effectively discourage a gNB from configuring a CG-PUSCH that overlaps with a PDCCH Search Space in SBFD slots since the UE will always ignore the CG-PUSCH or ignore the PDCCH Search Space if the CG-PUSCH has High L1 Priority. However, there may be cases where the gNB cannot avoid such configurations that collide, especially if the CG-PUSCH and PDCCH Search Space have different periodicities and only overlap once in a while (i.e. does not overlap consistently).

[0091] In general, the above techniques have been described primarily in terms of conflict resolution being performed by a UE. However, a base station (e.g. a gNB) may perform conflict resolution in substantially the same way. As such, all techniques described herein in relation to a UE should be understood as being equally applicable to a base station.

[0092] Figure 16 illustrates a flowchart for an example method 1600 for a UE for resolving a conflict between an uplink transmission and a downlink transmission located in different frequency sub-bands of an SBFD slot. This example method is described in the context of two colliding transmissions for ease of explanation, however the method may be performed for larger numbers of colliding transmissions. The method may be also or alternatively be performed by a base station in an analogous manner.

[0093] The method begins at Step 1602, where the UE identifies whether a collision exists between an uplink transmission and a downlink transmission located in different frequency sub-bands of an SBFD slot. If there is no collision (exit “N” from Step 1602), the method ends. If there is a collision (exit “Y” from Step 1602), the method proceeds to Step 1604, where the UE determines whether the colliding transmissions are dynamically scheduled transmissions or configured transmissions. It should be noted that Steps 1602 and 1604 may take a different form and ordering. For example, the UE may determine that a new transmission has been scheduled and may then determine whether any collision exists. Similarly, the UE may identify an upcoming configured transmission and may then determine if a collision exists.

[0094] At Step 1604, if both of the transmissions are dynamically scheduled transmissions (exit “2” from Step 1604), the method may proceed to Step 1618, where the UE determines whether the transmissions have the same associated priority level. This step may in some cases include determining whether one or both of the transmissions has an associated priority level. The associated priority level for an UL transmission may be an L1 priority level, and the associated priority level for an UL transmission may be an L1 priority level for a PLICCH carrying a HARQ-ACK for the DL transmission, as described above. If the transmissions have different priority levels (exit “Y” from Step 1618), the method proceeds to Step 1620 where the UE prioritises the transmission with the higher priority level. For example, if the UL has a ‘High’ L1 priority level and the DL has a ‘Low’ associated L1 priority level, the UE prioritises the UL. Alternatively, if the UL and DL have the same priority level (exit “N” from Step 1618), the UE proceeds to Step 1622 and prioritises the transmission that was scheduled later (e.g. in a similar manner as described above in relation to Figure 12). Prioritising a particular transmission may include dropping or ignoring the non-prioritised transmission. This may include dropping or ignoring an entirety of the non-prioritised transmission or only a portion of the non-prioritised transmission. In some cases, the UE may not examine the priority of the UL and DL, or may determine that all or some of the UL and DL do not have associated priority levels, and thus may move directly from exit “2” of Step 1604 to Step 1622. If only one of the transmissions has an associated priority level, the UE may prioritise a particular transmission based on this (e.g. by prioritising the transmission with an associated priority level, or vice versa).

[0095] Returning to Step 1604, if only one of the two transmissions is a dynamically scheduled transmission (exit “1” from Step 1604), such that there is a collision between a dynamically scheduled transmission and a configured transmission, the UE may proceed to step 1614, where the UE determines whether the transmissions have the same associated priority level. This step is substantially similar to Step 1618 described above. If the transmissions have different priority levels (exit “Y” from Step 1614), the method proceeds to Step 1620 where the UE priorities the transmission with the higher priority level. Alternatively, if the UL and DL have the same priority level (exit “N” from Step 1614), the UE proceeds to Step 1616 and prioritises the transmission that was dynamically scheduled over the configured transmission (e.g. in a similar manner as described above in relation to Figure 14). In some cases, the UE may not examine the priority of the UL and DL, or may determine that all or some of the UL and DL do not have associated priority levels, and thus may move directly from exit “1” of Step 1604 to Step 1616.

[0096] Returning to Step 1604, if none of the two transmissions is a dynamically scheduled transmission (exit “0” from Step 1604), the method may proceed to Step 1606, where the UE determines whether the transmissions have the same associated priority level. This step is substantially similar to Steps 1618 and 1614 described above. If the transmissions have different priority levels (exit “Y” from Step 1606), the method proceeds to Step 1620 where the UE priorities the transmission with the higher priority level. Alternatively, if the UL and DL have the same priority level (exit “N” from Step 1606), the method may proceed to Step 1608 where the UE determines whether there is any traffic scheduled for the UL transmission. For example, if the UL is a CG-PUSCH, the UE may determine whether there is any traffic intended to be transmitted on the CG-PUSCH. If the UL transmission does not have any intended traffic (exit “N” from Step 1608), the method proceeds to Step 1610 where the UE priorities the DL transmission. Alternatively, if the UE does not identify any of the transmissions as having no intended traffic (exit “N” from Step 1608), the method may proceed to Step 1612. Furthermore, in some examples, after determining that there is intended traffic for the UL transmission, the UE may prioritise the UL transmission and skip step 1612.

[0097] At Step 1612, the UE determines whether the UL transmission carries an HARQ-ACK. Step 1612 may, in some cases have already been carried out (e.g. at Step 1604), and as such the UE may already know whether the UL transmission carries a HARQ-ACK and therefore may skip immediately to Step 1628 or 1624. If the UL does not carry a HARQ-ACK (exit “N” from Step 1612), the UE may identify the collision as a scheduling error (Step 1628). There are a number of possible actions the UE may take in this case. For example, the UE may drop both transmissions, or may select one of the transmissions to prioritise either randomly or using other criteria. Alternatively, at Step 1612, if the UE determines that the UL does carry a HARQ- ACK (exit “Y” from Step 1612), the UE proceeds to Step 1624, where the UE determines whether the UL carries an ACK or a NACK. If the UL transmission carries a NACK (exit “N” from Step 1624), the method may proceed to step 1628, where the UE may prioritise the DL transmission. Alternatively, if the UL transmission carries an ACK (exit “Y” from Step 1624), the UE proceeds to step 1626 and prioritises the UL transmission.

[0098] In some examples, after determining that none of the two transmissions is a dynamically scheduled transmission (exit “0” from Step 1604), the UE may skip any of steps 1606, 1608, and 1612. For example, the UE may skip from Step 1604 to Step 1608, or Step 1612, or may skip from Step 1606 to Step 1612. Furthermore, any section of the method of Figure 16 may include additional considerations or determinations which the UE may use to determine which transmission to prioritise. For example, the UE may also determine which transmission to prioritise based on the type of transmission (e.g. the UE may prioritise a PDCCH SS over a CG-PUSCH, or vice versa), or may only (de)prioritise an UL carrying an ACK if certain other criteria are met. As a further example, the UE may determine which transmission to prioritise based at least in part on whether the UL carries an ACK (i.e. steps 1612, 1624, 1626 and 1630) for cases where both of the colliding transmissions are dynamically scheduled (exit “2” from Step 1604). As such, the specific steps and processes shown in Figure 16 are not intended to be limiting and Figure 16 should be interpreted as merely an example implementation of the teachings disclosed herein.

[0099] Accordingly, there has been described methods, communications device, infrastructure equipment, and circuitry for resolving collisions between uplink and downlink transmissions located in different frequency sub-bands (e.g. in an SBFD slot). Based on whether the uplink and downlink transmissions are dynamically scheduled transmissions or configured transmissions, a particular transmission is prioritised. Generally, dynamically scheduled transmissions are prioritised over configured transmissions, however other factors such as associated L1 priority can provide alternative prioritisations.

[0100] The following numbered clauses provide further example aspects and features of the present technique:

[0101] 1. A method of operating a communications device configured to transmit signals to and / or to receive signals from an infrastructure equipment of a wireless communications network via a wireless radio interface provided by the wireless communications network, the method comprising: identifying a collision between a first uplink transmission and a second downlink transmission, the first uplink transmission and first downlink transmission being located in different frequency sub-bands; determining whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions; based on the determination of whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions, prioritising the first uplink transmission or the first downlink transmission as a prioritised transmission.

[0102] 2. The method of clause 1 , wherein prioritising the prioritised transmission comprises dropping at least a portion of the non-prioritised transmission of the first uplink transmission and the first downlink transmission. 3. The method of clause 2, wherein dropping at least a portion of the non-prioritised transmission comprises dropping only Orthogonal Frequency-Division Multiplexing (OFDM) symbols of the non-prioritised transmission that collide with the prioritised transmission.

[0103] 4. The method of clause 2, wherein dropping at least a portion of the non-prioritised transmission comprises dropping all of the non-prioritised transmission.

[0104] 5. The method of any preceding clause, wherein a dynamically scheduled transmission is a Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), or a Physical Uplink Control Channel (PUCCH).

[0105] 6. The method of any preceding clause, wherein a transmission that is not a dynamically scheduled transmission is a configured transmission or a control channel, wherein the configured transmission or control channel is a Physical Downlink Control Channel (PDCCH) search space, a Semi-Persistent Scheduling (SPS) PDSCH, a Configured Grant PUSCH (CG- PUSCH), or a PUCCH carrying a HARQ-ACK in response to an SPS PDSCH.

[0106] 7. The method according to clause 6, wherein the first downlink transmission is a PDCCH search space, wherein for the first downlink transmission the communications device is configured to monitor a set of physical resources for a PDCCH.

[0107] 8. The method of any preceding clause, wherein only one of the uplink transmission and the first downlink transmission is a dynamically scheduled transmission.

[0108] 9. The method according to clause 8, wherein prioritising the first uplink transmission or the first downlink transmission comprises prioritising the dynamically scheduled transmission as the prioritised transmission.

[0109] 10. The method of any of clauses 1-6, wherein both of the one of the uplink transmission and the first downlink transmission are dynamically scheduled transmissions.

[0110] 11 . The method according to clause 10, wherein prioritising the first uplink transmission or the first downlink transmission is additionally based on determining that a scheduling error exists.

[0111] 12. The method according to clause 11 , wherein based on determining that a scheduling error exists, the communications device discards both the first uplink transmission or the first downlink transmission.

[0112] 13. The method according to any of clauses 1-6, wherein neither of the uplink transmission and the first downlink transmission is a dynamically scheduled transmission.

[0113] 14. The method according to clause 13, wherein prioritising the first uplink transmission or the first downlink transmission is additionally based on determining whether the communications device has any traffic to be included in the first uplink transmission.

[0114] 15. The method according to clause 14, further comprising: if the communications device has traffic for the first uplink transmission, prioritising the first uplink transmission as the prioritised transmission; and if the communications device does not have any traffic for the first uplink transmission, prioritising the first downlink transmission as the prioritised transmission.

[0115] 16. The method according to any of clauses 13 or 14, wherein the first uplink transmission is a CG-PUSCH and the first downlink transmission is a PDCCH search space, and wherein the communications device priorities the PDCCH search space as the prioritised transmission. 17. The method according to clause 13 or 14, wherein the first uplink transmission is a CG-PUSCH and the first downlink transmission is a PDCCH search space, and wherein the communications device priorities the CG-PUSCH as the prioritised transmission.

[0116] 18. The method of any preceding clause, wherein prioritising the first uplink transmission or the first downlink transmission is additionally based on a determined priority for the first uplink transmission and the first downlink transmission.

[0117] 19. The method according to clause 18, wherein the determined priority level for the first uplink transmission is an L1 priority for the first uplink transmission, and wherein the priority level for the first downlink transmission is an L1 priority for a second uplink transmission, the second transmission being configured to carry a HARQ-ACK for the first downlink transmission.

[0118] 20. The method according to any preceding clause, wherein prioritising the first uplink transmission or the first downlink transmission is additionally based on the prioritised transmission being scheduled after the non-prioritised transmission.

[0119] 21. The method according to any preceding clause, wherein prioritising the first uplink transmission or the first downlink transmission is additionally based on whether the first uplink transmission includes a HARQ-ACK, and whether the HARQ-ACK is an ACK or a NACK.

[0120] 22. The method according to clause 16, further comprising: if the first uplink transmission includes an ACK, prioritising the first uplink transmission as the prioritised transmission; and if the first uplink transmission includes a NACK, prioritising the first downlink transmission as the prioritised transmission.

[0121] 23. A communications device, the communications device comprising: a transceiver configured to transmit signals to and / or to receive signals from an infrastructure equipment of a wireless communications network and / or one or more other communications devices, and a controller configured in combination with the transceiver to: identify a collision between a first uplink transmission and a second downlink transmission, the first uplink transmission and first downlink transmission being located in different frequency sub-bands; determine whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions; based on the determination of whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions, prioritise the first uplink transmission or the first downlink transmission as a prioritised transmission.

[0122] 24. Circuitry for a communications device comprising: transceiver circuitry configured to transmit signals to and / or to receive signals from an infrastructure equipment of a wireless communications network and / or one or more other communications devices, and controller circuitry configured in combination with the transceiver to: identify a collision between a first uplink transmission and a second downlink transmission, the first uplink transmission and first downlink transmission being located in different frequency sub-bands; determine whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions; based on the determination of whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions, prioritise the first uplink transmission or the first downlink transmission as a prioritised transmission.

[0123] 25. A method of operating an infrastructure equipment configured to transmit signals to and / or receive signals from a plurality of communications devices via a wireless access interface provided by a wireless communications network, the method comprising: identifying a collision between a first uplink transmission and a second downlink transmission, the first uplink transmission and first downlink transmission being located in different frequency sub-bands; determining whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions; based on the determination of whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions, prioritising the first uplink transmission or the first downlink transmission as a prioritised transmission.

[0124] 26. The method of clause 25, wherein prioritising the prioritised transmission comprises dropping at least a portion of the non-prioritised transmission of the first uplink transmission and the first downlink transmission.

[0125] 27. The method of clause 26, wherein dropping at least a portion of the non-prioritised transmission comprises dropping only Orthogonal Frequency-Division Multiplexing (OFDM) symbols of the non-prioritised transmission that collide with the prioritised transmission.

[0126] 28. The method of clause 26, wherein dropping at least a portion of the non-prioritised transmission comprises dropping all of the non-prioritised transmission.

[0127] 29. The method of any of clauses 25-28, wherein a dynamically scheduled transmission is a Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), or a Physical Uplink Control Channel (PUCCH).

[0128] 30. The method of any of clauses 25-29, wherein a transmission that is not a dynamically scheduled transmission is a configured transmission or a control channel, wherein the configured transmission or control channel is a Physical Downlink Control Channel (PDCCH) search space, a Semi-Persistent Scheduling (SPS) PDSCH, a Configured Grant PUSCH (CG- PUSCH), or a PUCCH carrying a HARQ-ACK in response to an SPS PDSCH.

[0129] 31 . The method of any of clauses 25-30, wherein only one of the uplink transmission and the first downlink transmission is a dynamically scheduled transmission.

[0130] 32. The method according to clause 31 , wherein prioritising the first uplink transmission or the first downlink transmission comprises prioritising the dynamically scheduled transmission as the prioritised transmission.

[0131] 33. The method of any of clauses 25-30, wherein both of the one of the uplink transmission and the first downlink transmission are dynamically scheduled transmissions. 34. The method according to clause 33, wherein prioritising the first uplink transmission or the first downlink transmission is additionally based on determining that a scheduling error exists.

[0132] 35. The method according to clause 34, wherein based on determining that a scheduling error exists, the communications device discards both the first uplink transmission or the first downlink transmission.

[0133] 36. The method according to any of clauses 25-30, wherein neither of the uplink transmission and the first downlink transmission is a dynamically scheduled transmission.

[0134] 37. The method according to clause 36, wherein prioritising the first uplink transmission or the first downlink transmission is additionally based on determining whether the infrastructure equipment has any traffic to be included in the first downlink transmission.

[0135] 38. The method according to clause 37, further comprising: if the infrastructure equipment has traffic for the first downlink transmission, prioritising the first downlink transmission as the prioritised transmission; and if the infrastructure equipment does not have any traffic for the first downlink transmission, prioritising the first uplink transmission as the prioritised transmission.

[0136] 39. The method according to any of clauses 36 or 37, wherein the first uplink transmission is a CG-PUSCH and the first downlink transmission is a PDCCH, and wherein the infrastructure equipment priorities the PDCCH as the prioritised transmission.

[0137] 40. The method according to clause 36 or 37, wherein the first uplink transmission is a CG-PUSCH and the first downlink transmission is a PDCCH, and wherein the infrastructure equipment priorities the CG-PUSCH as the prioritised transmission.

[0138] 41. The method of any of clauses 25-40, wherein prioritising the first uplink transmission or the first downlink transmission is additionally based on a determined priority for the first uplink transmission and the first downlink transmission.

[0139] 42. The method according to clause 41 , wherein the determined priority level for the first uplink transmission is an L1 priority for the first uplink transmission, and wherein the priority level for the first downlink transmission is an L1 priority for a second uplink transmission, the second transmission being configured to carry a HARQ-ACK for the first downlink transmission.

[0140] 43. The method according to any of clauses 25-42, wherein prioritising the first uplink transmission or the first downlink transmission is additionally based on the prioritised transmission being scheduled after the non-prioritised transmission.

[0141] 44. An infrastructure equipment comprising: a transceiver configured to transmit signals to and / or receive signals from a plurality of communications devices, and a controller configured in combination with the transceiver to: identify a collision between a first uplink transmission and a second downlink transmission, the first uplink transmission and first downlink transmission being located in different frequency sub-bands; determine whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions; based on the determination of whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions, prioritise the first uplink transmission or the first downlink transmission as a prioritised transmission.

[0142] 45. Circuitry for an infrastructure equipment comprising: transceiver circuitry configured to transmit signals to and / or receive signals from a plurality of communications devices, and controller circuitry configured in combination with the transceiver to: identify a collision between a first uplink transmission and a second downlink transmission, the first uplink transmission and first downlink transmission being located in different frequency sub-bands; determine whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions; based on the determination of whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions, prioritise the first uplink transmission or the first downlink transmission as a prioritised transmission.

[0143] It will be appreciated that the above description for clarity has described embodiments with reference to different functional units, circuitry and / or processors. However, it will be apparent that any suitable distribution of functionality between different functional units, circuitry and / or processors may be used without detracting from the embodiments.

[0144] Described embodiments may be implemented in any suitable form including hardware, software, firmware or any combination of these. Described embodiments may optionally be implemented at least partly as computer software running on one or more data processors and / or digital signal processors. The elements and components of any embodiment may be physically, functionally and logically implemented in any suitable way. Indeed, the functionality may be implemented in a single unit, in a plurality of units or as part of other functional units. As such, the disclosed embodiments may be implemented in a single unit or may be physically and functionally distributed between different units, circuitry and / or processors.

[0145] Although the present disclosure has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Additionally, although a feature may appear to be described in connection with particular embodiments, one skilled in the art would recognise that various features of the described embodiments may be combined in any manner suitable to implement the technique.

[0146] REFERENCES

[0147] [1] Holma H. and Toskala A, “LTE for UMTS OFDMA and SC-FDMA based radio access”, John Wiley and Sons, 2009.

[0148] [2] RP-213591 , “New SI: Study on evolution of NR duplex operation,” CMCC, RAN#94e

Claims

CLAIMS1. A method of operating a communications device configured to transmit signals to and / or to receive signals from an infrastructure equipment of a wireless communications network via a wireless radio interface provided by the wireless communications network, the method comprising: identifying a collision between a first uplink transmission and a second downlink transmission, the first uplink transmission and first downlink transmission being located in different frequency sub-bands; determining whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions; based on the determination of whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions, prioritising the first uplink transmission or the first downlink transmission as a prioritised transmission.

2. The method according to claim 1 , wherein prioritising the prioritised transmission comprises dropping at least a portion of the non-prioritised transmission of the first uplink transmission and the first downlink transmission.

3. The method according to claim 2, wherein dropping at least a portion of the nonprioritised transmission comprises dropping only Orthogonal Frequency-Division Multiplexing (OFDM) symbols of the non-prioritised transmission that collide with the prioritised transmission.

4. The method according to claim 2, wherein dropping at least a portion of the nonprioritised transmission comprises dropping all of the non-prioritised transmission.

5. The method according to claim 1 , wherein a dynamically scheduled transmission is a Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), or a Physical Uplink Control Channel (PUCCH).

6. The method according to claim 1 , wherein a transmission that is not a dynamically scheduled transmission is a configured transmission or a control channel, wherein the configured transmission or control channel is a Physical Downlink Control Channel (PDCCH) search space, a Semi-Persistent Scheduling (SPS) PDSCH, a Configured Grant PUSCH (CG- PUSCH), or a PUCCH carrying a HARQ-ACK in response to an SPS PDSCH.

7. The method according to claim 6, wherein the first downlink transmission is a PDCCH search space, wherein for the first downlink transmission the communications device is configured to monitor a set of physical resources for a PDCCH.

8. The method according to claim 1 , wherein only one of the uplink transmission and the first downlink transmission is a dynamically scheduled transmission.

9. The method according to claim 8, wherein prioritising the first uplink transmission or the first downlink transmission comprises prioritising the dynamically scheduled transmission as the prioritised transmission.

10. The method according to claim 1 , wherein both of the one of the uplink transmission and the first downlink transmission are dynamically scheduled transmissions.

11. The method according to claim 10, wherein prioritising the first uplink transmission or the first downlink transmission is additionally based on determining that a scheduling error exists.

12. The method according to claim 11 , wherein based on determining that a scheduling error exists, the communications device discards both the first uplink transmission or the first downlink transmission.

13. The method according to any of claims 1-6, wherein neither of the uplink transmission and the first downlink transmission is a dynamically scheduled transmission.

14. The method according to claim 13, wherein prioritising the first uplink transmission or the first downlink transmission is additionally based on determining whether the communications device has any traffic to be included in the first uplink transmission.

15. The method according to claim 14, further comprising: if the communications device has traffic for the first uplink transmission, prioritising the first uplink transmission as the prioritised transmission; and if the communications device does not have any traffic for the first uplink transmission, prioritising the first downlink transmission as the prioritised transmission.

16. The method according to claim 13, wherein the first uplink transmission is a CG- PLISCH and the first downlink transmission is a PDCCH search space, and wherein the communications device priorities the PDCCH search space as the prioritised transmission.

17. The method according to claim 13, wherein the first uplink transmission is a CG- PLISCH and the first downlink transmission is a PDCCH search space, and wherein the communications device priorities the CG-PUSCH as the prioritised transmission.

18. The method according to claim 1 , wherein prioritising the first uplink transmission or the first downlink transmission is additionally based on a determined priority for the first uplink transmission and the first downlink transmission.

19. The method according to claim 18, wherein the determined priority level for the first uplink transmission is an L1 priority for the first uplink transmission, and wherein the priority level for the first downlink transmission is an L1 priority for a second uplink transmission, the second transmission being configured to carry a HARQ-ACK for the first downlink transmission.

20. The method according to claim 1 , wherein prioritising the first uplink transmission or the first downlink transmission is additionally based on the prioritised transmission being scheduled after the non-prioritised transmission.

21. The method according to claim 1 , wherein prioritising the first uplink transmission or the first downlink transmission is additionally based on whether the first uplink transmission includes a HARQ-ACK, and whether the HARQ-ACK is an ACK or a NACK.

22. The method according to claim 16, further comprising: if the first uplink transmission includes an ACK, prioritising the first uplink transmission as the prioritised transmission; and if the first uplink transmission includes a NACK, prioritising the first downlink transmission as the prioritised transmission.

23. A communications device, the communications device comprising: a transceiver configured to transmit signals to and / or to receive signals from an infrastructure equipment of a wireless communications network and / or one or more other communications devices, and a controller configured in combination with the transceiver to: identify a collision between a first uplink transmission and a second downlink transmission, the first uplink transmission and first downlink transmission being located in different frequency sub-bands; determine whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions;based on the determination of whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions, prioritise the first uplink transmission or the first downlink transmission as a prioritised transmission.

24. Circuitry for a communications device comprising: transceiver circuitry configured to transmit signals to and / or to receive signals from an infrastructure equipment of a wireless communications network and / or one or more other communications devices, and controller circuitry configured in combination with the transceiver to: identify a collision between a first uplink transmission and a second downlink transmission, the first uplink transmission and first downlink transmission being located in different frequency sub-bands; determine whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions; based on the determination of whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions, prioritise the first uplink transmission or the first downlink transmission as a prioritised transmission.

25. A method of operating an infrastructure equipment configured to transmit signals to and / or receive signals from a plurality of communications devices via a wireless access interface provided by a wireless communications network, the method comprising: identifying a collision between a first uplink transmission and a second downlink transmission, the first uplink transmission and first downlink transmission being located in different frequency sub-bands; determining whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions; based on the determination of whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions, prioritising the first uplink transmission or the first downlink transmission as a prioritised transmission.

26. An infrastructure equipment comprising: a transceiver configured to transmit signals to and / or receive signals from a plurality of communications devices, and a controller configured in combination with the transceiver to: identify a collision between a first uplink transmission and a second downlink transmission, the first uplink transmission and first downlink transmission being located in different frequency sub-bands; determine whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions;based on the determination of whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions, prioritise the first uplink transmission or the first downlink transmission as a prioritised transmission.

27. Circuitry for an infrastructure equipment comprising: transceiver circuitry configured to transmit signals to and / or receive signals from a plurality of communications devices, and controller circuitry configured in combination with the transceiver to: identify a collision between a first uplink transmission and a second downlink transmission, the first uplink transmission and first downlink transmission being located in different frequency sub-bands; determine whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions; based on the determination of whether the first uplink transmission and first downlink transmission are a dynamically scheduled transmissions, prioritise the first uplink transmission or the first downlink transmission as a prioritised transmission.

Images