WO2025171980A1

WO2025171980A1 - Semi-static dl reception priorization

Info

Publication number: WO2025171980A1
Application number: PCT/EP2025/050814
Authority: WO
Inventors: Guillermo POCOVI; Nhat-Quang NHAN
Original assignee: Nokia Technologies Oy
Current assignee: Nokia Technologies Oy
Priority date: 2024-02-14
Filing date: 2025-01-14
Publication date: 2025-08-21
Anticipated expiration: 2026-08-14

Abstract

According to an aspect, there is provided an apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform the following Receive, from an access node, a first configuration indicating that semi-static downlink, DL, reception should be prioritized over configured grant physical uplink shared channel, CG PUSCH, transmission; receive, from the access node, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions, wherein at least one CG PUSCH transmission occasion in the second configuration overlaps with a semi-static DL reception; and based at least on the first configuration, drop the CG PUSCH transmission at the at least one CG PUSCH transmission occasion and perform the semi-static DL reception.

Description

SEMI-STATIC DL RECEPTION PRIORIZATION

TECHNICAL FIELD

[0001] Various example embodiments relate to wireless communications.

BACKGROUND

[0002] 3rd Generation Partnership Project (3GPP) fifth generation (5G) New Radio (NR) supports two duplexing modes: frequency division duplexing (FDD) for paired bands and time division duplexing (TDD) for unpaired bands. In TDD, the time domain resource is split between downlink and uplink. Allocation of a limited time duration for the uplink in TDD would result in reduced coverage, increased latency, and reduced capacity. Use of a further duplexing mode for allowing simultaneous downlink (DL) and uplink (UL) transmission on different physical resource blocks (RBs)/subbands within an unpaired wideband NR cell has been suggested recently. This duplexing mode, referred to as subband non-overlapping full duplex (SBFD) provides improved UL coverage and latency compared to TDD/FDD. However, the default assumption in 3GPP is that the access node (i.e., gNodeB) will support full-duplex operation, i.e., can transmit (in DL) and receive (in UL) simultaneously in separate resource blocks (RBs) of the NR carrier while the terminal device supports only half-duplex, i.e., it can either transmit or receive at a given time. This presents certain challenges in implementation of the SBFD in practice.

SUMMARY

[0003] According to a first aspect, there is provided the subject matter of the independent claims. Embodiments are defined in the dependent claims.

[0004] According to a second aspect, there is provided an apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from an access node, a first configuration indicating that configured grant physical uplink shared channel, CG PUSCH, transmission should be prioritized over semi-static downlink, DL, reception; receive, from the access node, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions, wherein at least one CG PUSCH transmission occasion in the second configuration overlaps with a semi-static DL reception; and determine, based at least on the first configuration, whether to ignore the semistatic DL reception that overlaps with the at least one CG PUSCH transmission occasion.

[0005] According to a first embodiment of the second aspect, the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to: in accordance with determining to ignore the semi-static DL reception that overlaps with the at least one CG PUSCH transmission occasion, ignore the semi-static DL reception.

[0006] According to a second embodiment of the second aspect, optionally further defining the first embodiment, the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to ignore the semi-static DL reception if the semi-static DL reception overlaps with one or more CG PUSCH transmission occasions that are usable by the apparatus.

[0007] According to a third embodiment of the second aspect, the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to: transmit, to the access node, a report indicating at least one or more first CG PUSCH transmission occasions as usable for upcoming CG PUSCH transmission by the apparatus; and determine to ignore the semi-static DL reception based on the first configuration and on that the semi-static DL reception overlaps with at least one of the one or more first CG PUSCH transmission occasions indicated by the report as usable.

[0008] According to a fourth embodiment of the second aspect, the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to: transmit at least one signal using at least one CG PUSCH transmission occasion that overlaps with the ignored semi-static DL reception.

[0009] According to a fifth embodiment of the second aspect, the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to perform the semi-static DL reception if the semi-static DL reception does not overlap with one or more CG PUSCH transmission occasions that are usable by the apparatus.

[0010] According to a sixth embodiment of the second aspect, at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to: transmit, to the access node, a report indicating at least zero or more first CG PUSCH transmission occasions as usable for upcoming CG PUSCH transmission by the apparatus and one or more second CG PUSCH transmission occasions not to be used by the apparatus, wherein the determining whether to ignore the semi-static DL reception that overlaps with the at least one CG PUSCH transmission occasion is further based on the report; and based at least on the report, determine to perform the semi-static DL reception if the semi-static DL transmission overlaps with at least one of the one or more second CG PUSCH transmission occasions not to be used by the apparatus but not with any of the zero or more first CG PUSCH transmission occasions that are usable by the apparatus.

[0011] According to a seventh embodiment of the second aspect, optionally further defining any of the first, second, third, fourth, fifth or sixth embodiment, the first configuration comprises a binary radio resource control, RRC, parameter indicating that the CG PUSCH transmission should be prioritized over the semi-static DL reception.

[0012] According to a third aspect, there is provides an apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: transmit, to a terminal device, a first configuration indicating that configured grant physical uplink shared channel, CG PUSCH, transmission should be prioritized over semi-static downlink, DL, reception at the terminal device; and transmit, to the terminal device, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions, wherein at least one CG PUSCH transmission occasion in the second configuration overlaps with a semi-static DL transmission; and determine, based at least on the first configuration, whether to perform the semi-static DL transmission that overlaps with the at least one CG PUSCH transmission occasion.

[0013] According to a first embodiment of the third aspect, the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to if the semi-static DL transmission is determined to overlap with one or more first CG PUSCH transmission occasions that are usable by the terminal device, drop the semi-static DL transmission and receive, from the terminal device, at least one signal using at least one of the one or more first CG PUSCH transmission occasions; and/or if the semi-static DL transmission is determined not to overlap with any of the one or more first CG PUSCH transmission occasions that are usable by the terminal device, perform the semi-static DL transmission.

[0014] According to a second embodiment of the third aspect, the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to: receive, from the terminal device, a report indicating one or more first CG PUSCH transmission occasions as usable for upcoming CG PUSCH transmission by the terminal device; and determine to drop the semi-static DL transmission based on the first configuration and on that the semi-static DL transmission overlaps with at least one of the one or more first CG PUSCH transmission occasions indicated by the report as usable by the terminal device.

[0015] According to a third embodiment of the third aspect, the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to: receive, from the terminal device, a report indicating at least zero or more first CG PUSCH transmission occasions as usable for upcoming CG PUSCH transmission by the terminal device and one or more second CG PUSCH transmission occasions not to be used for CG PUSCH transmission by the terminal device; and based at least on the report, determine to perform the semi-static DL transmission if the semi-static DL transmission overlaps with at least one of the one or more second CG PUSCH transmission occasions not to be used by the terminal device but not with any of the zero or more first CG PUSCH transmission occasions that are usable by the terminal device.

[0016] According to a fourth embodiment of the third aspect, optionally further defining any of the first, second or third embodiment, the first configuration comprises a binary radio resource control, RRC, parameter indicating that the CG PUSCH transmission should be prioritized over the semi-static DL reception.

[0017] According to a fourth aspect, there is provided a non-transitory computer readable medium having stored thereon instructions that, when executed by a computing device, cause the computing device to: receive, from an access node, a first configuration indicating that configured grant physical uplink shared channel, CG PUSCH, transmission should be prioritized over semi-static downlink, DL, reception; receive, from the access node, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions, wherein at least one CG PUSCH transmission occasion in the second configuration overlaps with a semi-static DL reception; and determine, based at least on the first configuration, whether to ignore the semistatic DL reception that overlaps with the at least one CG PUSCH transmission occasion.

[0018] According to a fifth aspect, there is provided a non-transitory computer readable medium having stored thereon instructions that, when executed by a computing device, cause the computing device to perform: transmit, to a terminal device, a first configuration indicating that CG PUSCH transmission should be prioritized over semi-static DL reception at the terminal device; transmit, to the terminal device, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions, wherein at least one CG PUSCH transmission occasion in the second configuration overlaps with a semi-static DL transmission; and determine, based at least on the first configuration, whether to perform the semi-static DL transmission that overlaps with the at least one CG PUSCH transmission occasion.

[0019] According to a sixth aspect, there is provided a method comprising: receiving, from an access node, a first configuration indicating that configured grant physical uplink shared channel, CG PUSCH, transmission should be prioritized over semi-static downlink, DL, reception; receiving, from the access node, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions, wherein at least one CG PUSCH transmission occasion in the second configuration overlaps with a semi-static DL reception; and determining, based at least on the first configuration, whether to ignore the semi-static DL reception that overlaps with the at least one CG PUSCH transmission occasion.

[0020] According to a seventh aspect, there is provided a method comprising: transmitting, to a terminal device, a first configuration indicating that CG

PUSCH transmission should be prioritized over semi-static DL reception at the terminal device; transmitting, to the terminal device, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions, wherein at least one CG PUSCH transmission occasion in the second configuration overlaps with a semi-static DL transmission; and determining, based at least on the first configuration, whether to perform the semi-static DL transmission that overlaps with the at least one CG PUSCH transmission occasion.

[0021] One or more examples of implementations are set forth in more detail in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 illustrates a system to which some embodiments may be applied; [0023] Figures 2 to 9 illustrate processes according to some embodiments;

[0024] Figure 10 illustrates an apparatus according to some embodiments; and

[0025] Figures 11 and 12 illustrate processed according to some embodiments.

DETAILED DESCRIPTION OF SOME EMBODIMENTS

[0026] The following embodiments are only presented as examples. Although the specification may refer to “an”, “one”, or “some” embodiment(s) and/or example(s) in several locations of the text, this does not necessarily mean that each reference is made to the same embodiment s) or example(s), or that a particular feature only applies to a single embodiment and/or example. Single features of different embodiments and/or examples may also be combined to provide other embodiments and/or examples.

[0027] As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0028] As used here, the term “semi-static” (e.g.., a semi-static downlink reception) may be defined as referring to behavior which is static or substantially static for extended periods of time but which can change, e.g., periodically or in response to a specific trigger.

[0029] In the following, different exemplifying embodiments will be described using, as an example of an access architecture to which the embodiments may be applied, a radio access architecture based on long term evolution advanced (LTE Advanced, LTE-A) or new radio (NR, 5G), without restricting the embodiments to such an architecture, however. It is obvious for a person skilled in the art that the embodiments may also be applied to other kinds of communications networks having suitable means by adjusting parameters and procedures appropriately. Some examples of other options for suitable systems are the universal mobile telecommunications system (UMTS) radio access network (UTRAN or E- UTRAN), long term evolution (LTE, the same as E-UTRA), wireless local area network (WLAN or WiFi), worldwide interoperability for microwave access (WiMAX), Bluetooth®, personal communications services (PCS), ZigBee®, wideband code division multiple access (WCDMA), systems using ultra-wideband (UWB) technology, sensor networks, mobile ad- hoc networks (MANETs) and Internet Protocol multimedia subsystems (IMS) or any combination thereof.

[0030] Figure 1 depicts examples of simplified system architectures only showing some elements and functional entities, all being logical units, whose implementation may differ from what is shown. The connections shown in Figure 1 are logical connections; the actual physical connections may be different. It is apparent to a person skilled in the art that the system typically comprises also other functions and structures than those shown in Figure 1.

[0031] The embodiments are not, however, restricted to the system given as an example but a person skilled in the art may apply the solution to other communication systems provided with necessary properties.

[0032] The example of Figure 1 shows a part of an exemplifying radio access network.

[0033] A communications system typically comprises more than one (e/g)NodeB 104 in which case the (e/g)NodeBs may also be configured to communicate with one another over links, wired or wireless, designed for the purpose. These links may be used for signaling purposes. The (e/g)NodeB is a computing device configured to control the radio resources of communication system it is coupled to. The NodeB may also be referred to as a base station, an access point or any other type of interfacing device including a relay station capable of operating in a wireless environment. The (e/g)NodeB includes or is coupled to transceivers. From the transceivers of the (e/g)NodeB, a connection is provided to an antenna unit that establishes bi-directional radio links to user devices. The antenna unit may comprise a plurality of antennas or antenna elements. The (e/g)NodeB is further connected to core network 110 (CN or next generation core NGC). Depending on the system, the counterpart on the CN side can be a serving gateway (S-GW, routing and forwarding user data packets), packet data network gateway (P-GW), for providing connectivity of user devices (UEs) to external packet data networks, or mobile management entity (MME), etc.

[0034] The user device 100, 102 (also called UE, user equipment, user terminal, terminal device, etc.) illustrates one type of an apparatus to which resources on the air interface are allocated and assigned, and thus any feature described herein with a user device may be implemented with a corresponding apparatus, such as a relay node. An example of such a relay node is a layer 3 relay (self-backhauling relay) towards the base station. The user equipment may comprise a mobile equipment and at least one universal integrated circuit card (UICC).

[0035] The user device 100, 102 typically refers to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM) or UICC, including, but not limited to, the following types of devices: a mobile station (mobile phone), smartphone, personal digital assistant (PDA), handset, device using a wireless modem (alarm or measurement device, etc.), laptop and/or touch screen computer, tablet, game console, notebook, and multimedia device. It should be appreciated that a user device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network. A user device may also be a device having capability to operate in Internet of Things (loT) network which is a scenario in which objects are provided with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction. Thus, the user devices may not enable direct user interaction or may enable only limited user interaction (e.g., during setup). The user device (or in some embodiments a layer 3 relay node) is configured to perform one or more of user equipment functionalities. The user device may also be called a terminal device, a subscriber unit, mobile station, remote terminal, access terminal, user terminal or user equipment (UE) just to mention but a few names or apparatuses. The user device may comprise one or more antennas.

[0036] Various techniques described herein may also be applied to a cyber-physical system (CPS) (a system of collaborating computational elements con-trolling physical entities). CPS may enable the implementation and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors microcontrollers, etc.) embedded in physical objects at different locations. Mobile cyber physical systems, in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals.

[0037] Additionally, although the apparatuses have been depicted as single entities, different units, processors and/or memory units (not all shown in Figure 1) may be implemented.

[0038] 5G enables using multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and employing a variety of radio technologies depending on service needs, use cases and/or spectrum available. 5G mobile communications supports a wide range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications, including vehicular safety, different sensors and real-time control. 5G is expected to have multiple radio interfaces, namely below 6GHz, cmWave and mmWave, and also being integradable with existing legacy radio access technologies, such as the LTE. Integration with the LTE may be implemented, at least in the early phase, as a system, where macro coverage is provided by the LTE and 5G radio interface access comes from small cells by aggregation to the LTE. In other words, 5G is planned to support both inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6GHz - cmWave, below 6GHz - cmWave - mmWave). One of the concepts considered to be used in 5G networks is network slicing in which multiple independent and dedicated virtual sub-networks (network instances) may be created within the same infrastructure to run services that have different requirements on latency, reliability, throughput and mobility.

[0039] The current architecture in LTE networks is fully distributed in the radio and fully centralized in the core network. The low latency applications and services in 5G require to bring the content close to the radio which leads to local break out and multi-access edge computing (MEC). 5G enables analytics and knowledge generation to occur at the source of the data. This approach requires leveraging resources that may not be continuously connected to a network such as laptops, smartphones, tablets and sensors. MEC provides a distributed computing environment for application and service hosting. It also has the ability to store and process content in close proximity to cellular subscribers for faster response time. Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer-to-peer ad hoc networking and processing also classifiable as local cloud/fog computing and grid/mesh computing, dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and/or latency critical), critical communications (autonomous vehicles, traffic safety, real-time analytics, time- critical control, healthcare applications). [0040] The communication system is also able to communicate with other networks, such as a public switched telephone network or the Internet 112, or utilize services provided by them. The communication network may also be able to support the usage of cloud services, for example at least part of core network operations may be carried out as a cloud service (this is depicted in Figure 1 by “cloud” 114). The communication system may also comprise a central control entity, or a like, providing facilities for networks of different operators to cooperate for example in spectrum sharing.

[0041] Edge cloud may be brought into the RAN by utilizing network function virtualization (NVF) and software defined networking (SDN). Using edge cloud may mean access node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head or unit (RU) or base station comprising radio parts. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. Application of cloudRAN architecture enables RAN real time functions being carried out at the RAN side (in a distributed unit, DU 104) and non-real time functions being carried out in a centralized manner (in a central or centralized unit, CU 108). Thus, in summary, the RAN may comprise at least one distributed access node comprising a central unit, one or more distributed units communicatively connected to the central unit and one or more (remote) radio heads or units, each of which is communicatively connected to at least one of the one or more distributed units.

[0042] It should also be understood that the distribution of labor between core network operations and base station operations may differ from that of the LTE or even be nonexistent. Some other technology advancements probably to be used are Big Data and all-IP, which may change the way networks are being constructed and managed. 5G (or new radio, NR) networks are being designed to support multiple hierarchies, where MEC servers can be placed between the core and the base station or nodeB (gNB). It should be appreciated that MEC can be applied in 4G networks as well.

[0043] 5G may also utilize satellite communication to enhance or complement the coverage of 5G service, for example by providing backhauling. Possible use cases are providing service continuity for machine-to-machine (M2M) or Internet of Things (loT) devices or for passengers on board of vehicles, or ensuring service availability for critical communications, and future rail-way/maritime/aeronautical communications. Satellite communication may utilize geostationary earth orbit (GEO) satellite systems, but also low earth orbit (LEO) satellite systems, in particular mega-constellations (systems in which hundreds of (nano)satellites are deployed). Each satellite 106 in the mega-constellation may cover several satellite-enabled network entities that create on-ground cells. The on-ground cells may be created through an on-ground relay node 104 or by a gNB located on-ground or in a satellite.

[0044] It is obvious for a person skilled in the art that the depicted system is only an example of a part of a radio access system and in practice, the system may comprise a plurality of (e/g)NodeBs, the user device may have an access to a plurality of radio cells and the system may comprise also other apparatuses, such as physical layer relay nodes or other network elements, etc. At least one of the (e/g)NodeBs or may be a Home(e/g)nodeB. Additionally, in a geographical area of a radio communication system a plurality of different kinds of radio cells as well as a plurality of radio cells may be provided. Radio cells may be macro cells (or umbrella cells) which are large cells, usually having a diameter of up to tens of kilometers, or smaller cells such as micro-, femto- or picocells. The (e/g)NodeBs of Figure 1 may provide any kind of these cells. A cellular radio system may be implemented as a multilayer network including several kinds of cells. Typically, in multilayer networks, one access node provides one kind of a cell or cells, and thus a plurality of (e/g)NodeBs are required to provide such a network structure.

[0045] For fulfilling the need for improving the deployment and performance of communication systems, the concept of “plug-and-play” (e/g)NodeBs has been introduced. Typically, a network which is able to use “plug-and-play” (e/g)Node Bs, includes, in addition to Home (e/g)NodeBs (H(e/g)nodeBs), a home node B gateway, or HNB-GW (not shown in Figure 1). A HNB Gateway (HNB-GW), which is typically installed within an operator’s network may aggregate traffic from a large number of HNBs back to a core network.

[0046] 6G architecture is targeted to enable easy integration of everything, such as a network of networks, joint communication and sensing, non-terrestrial networks and terrestrial communication. 6G systems are envisioned to encompass machine learning algorithms as well as local and distributed computing capabilities, where virtualized network functions can be distributed over core and edge computing resources. Far edge computing, where computing resources are pushed to the very edge of the network, will be part of the distributed computing environment, for example in “zero-delay” scenarios. 5G systems may also employ such capabilities. More generally, the actual (radio) communication system is envisaged to be comprised of one or more computer programs executed within a programmable infrastructure, such as general -purpose computing entities (servers, processors, and like).

[0047] The embodiments may be directed to a 5G NR (Advanced) or 6G system supporting, in addition FDD for paired band and TDD for unpaired bands, a further duplexing mode for allowing simultaneous downlink (DL) and uplink (UL) transmission on different physical resource blocks (RBs)/subbands within an unpaired wideband NR cell. This duplexing mode, referred to as subband non-overlapping full duplex (SBFD) provides improved UL coverage and latency compared to TDD/FDD. The coverage improvement comes from cell-edge terminal devices being able to transmit much more frequently over time as compared to traditional TDD where typically around 1 out of 5 slots are used for UL transmission. However, the default assumption in 3GPP is that the access node (i.e., gNodeB) will support full-duplex operation, i.e., can transmit (in DL) and receive (in UL) simultaneously in separate resource blocks (RBs) of the NR carrier while the terminal device supports only half-duplex, i.e., it can either transmit or receive at a given time. This presents certain challenges in implementation of the SBFD which the embodiments aim to address.

[0048] In SBFD, two slot types may be defined for both DL and UL transmissions: 1) SBFD slots, during which the non-overlapping DL subband(s) and UL subband(s) both exist (with DL and UL subbands being optionally separated by a guard band), and 2) non-SBFD slots, during which the entire band is used for either DL or UL (i.e., legacy/full DL/UL slots). A subband may be defined here as a contiguous set of frequency resources, e.g., resource blocks (RBs) which are used for transmission/reception in the same link direction. The fact that the access node has full-duplex capabilities (i.e., it can transmit and receive at the same time), while the terminal device is only capable of half-duplex operation, as mentioned above, presents a new issue regarding UE-side UL-DL collision handling when operating using the slot type 1 (an issue not present with UE operation in legacy TDD bands). The embodiments to be discussed below may be directed especially to addressing said issue of UE-side UL-DL collision handling when operating using the slot type 1.

[0049] The UE-side UL-DL collision to be handled in embodiments is specifically a collision between semi-statically configured DL reception (e.g., PDCCH reception) and semi-statically configured UL transmission. In current 3GPP specifications, this is defined as an error case, in the sense that the access node should try to prevent such situation from happening at the UE side. It should be noted that even though this restriction is currently specified for flexible symbols, it is expected that similar restriction may exist for SBFD symbols as well. For example, in current 5G systems, it is not possible to allocate a set of physical downlink control channel (PDCCH) resources that the UE is expected to monitor and an overlapping set of configured UL resources for transmission such as configured grant physical uplink shared channel (CG-PUSCH) resources.

[0050] Configured Grant PUSCH (CG PUSCH) is a mechanism in which an access node can schedule periodic UL PUSCH resources to a UE without using downlink control information (DCI) for every transmission (DCIs in the PDCCH are still used in case of retransmissions.). For radio resource control (RRC) connected UEs of type-1 or type-2, the following properties may apply for configured grant:

- Type-1 : the resource configuration and activation are provided via RRC, i.e., RRC configuration provides information on the periodicity of the assigned PUSCH resources, time- and frequency-domain of the resource allocation, modulation and coding scheme to use and so on.

- Type-2: basic configuration parameters (e.g., periodicity) are provided via RRC, whereas activation (and remaining details on the allocation, e.g., resource allocation) are provided via the PDCCH.

[0051] In general, the CG PUSCH configuration may be defined as specified in RRC specifications.

[0052] When a CG PUSCH is configured (and activated, in case of type-2 CG), the UE may transmit via the PUSCH in each configured grant. In case the UE does not have any UL buffered data to transmit, the UE may skip the transmission if the skipping of the transmission is configured by the access node (otherwise, the UE transmits zero-padded data).

[0053] Some of the embodiments to be discussed below are based on use of unused transmission occasions (UTO) - uplink control information (UCI) reports. Basic UTO-UCI operation is discussed in the following for providing context for these embodiments. A UTO- UCI report is a report transmitted from the UE to the access node. The UTO-UCI report comprises a dynamic indication on UTO(s) of a certain CG PUSCH configuration. A UTO- UCI report may comprise a bitmap (with configured length between 3 and 8 bits) where each bit corresponds to a transmit occasion (TO) within a pre-defined (time) range (i.e., within a pre-defined sliding time window). UTO-UCI reporting has the general purpose of increasing the efficiency of use of the PUSCH resources.

[0054] For a given CG PUSCH configuration, a UTO-UCI report is included in every CG PUSCH transmission. The UTO-UCI report comprises a sequence of bits where each bit is associated with a different upcoming CG PUSCH TO. In other words, there exists a one- to-one mapping between the sequence of bits and a sequence of upcoming CG PUSCH TOs (provided, e.g., in ascending order of start time). In the set of bits, a bit value of ‘0’ indicates that the UE may (i.e., is enabled to but does not have to, these may be referred to as ‘usable’) transmit via the CG PUSCH in a corresponding CG-PUSCH TO, and a bit value of ‘ 1’ indicates that the UE will not transmit CG-PUSCH (these may be referred to as ‘unused’), in a corresponding CG-PUSCH TO. In addition, a CG PUSCH TO indicated as “unused” earlier is not allowed to be indicated as “NOT unused later”. In contrast, a CG PUSCH occasion indicated as “NOT unused” earlier can be indicated as “unused” later on.

[0055] The operation discussed in the previous paragraph is specified further in the specifications. If the UE is provided nrof UTO UCI with value equal to O^UTO~^UCI in configuredGrantConfig of a CG-PUSCH configuration, the UE multiplexes UTO-UCI represented by a bitmap of O^UTO~^UCI bits in each CG-PUSCH transmission for the CG- PUSCH configuration. The QUTO-UCI bits _of UTO-UCI, have a one-to-one mapping to O^UTO~^UCI subsequent CG-PUSCH TOs in ascending order of start time. For unpaired spectrum operation, the QUTO -UCI _sub_seq_uen CG-PUSCH TOs exclude invalid ones where a UE does not transmit a PUSCH due to collision of the PUSCH with DL symbol(s) indicated by tdd-UL-DL- ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated if provided, or with symbol(s) of an SS/PBCH block with index provided by ssb-PositionsInBurst, \)?LSQ< on the procedures defined in the specficiations. A bit value of ‘0’ indicates that the UE may transmit CG-PUSCH, and a bit value of ‘ 1’ indicates that the UE will not transmit CG-PUSCH, in a corresponding CG-PUSCH TO. When the UE indicates by UTO-UCI a value of ‘ 1’ for a CG-PUSCH TO, the UE continues to indicate the value of ‘ 1’ for the CG-PUSCH TO by UTO-UCI multiplexed in subsequent CG-PUSCH transmissions, and the UE does not transmit CG-PUSCH in the CG-PUSCH TO. The Clause 11.1 referred above states the following. For a set of symbols of a slot that are indicated to a UE as flexible by tdd-UL- DL-ConfigurationCommon, and tdd-UL-DL-ConfigurationDedicated if provided, the UE does not expect to receive both dedicated higher layer parameters configuring transmission from the UE in the set of symbols of the slot and dedicated higher layer parameters configuring reception by the UE in the set of symbols of the slot.

[0056] Figure 2 illustrates process for handling collision(s) between semi-statically configured DL reception and semi-statically configured UL transmission (namely, CG PUSCH transmission) according to embodiments. Specifically, Figure 2 illustrates a case where the collision is handled by prioritizing CG PUSCH transmission over semi-static DL reception. The process of Figure 2 may be carried out by an apparatus which may be, for example, a terminal device (i.e., a UE) or a part thereof. The terminal device carrying out the process of Figure 2 may be, for example, one of the terminal devices 100, 102 of Figure 1. The apparatus may be assumed to support half-duplex communication but not full-duplex communication. In the following, the entity carrying out the process of Figure 2 is called an apparatus for simplicity.

[0057] Referring to Figure 2, the apparatus receives, in block 201, from an access node, a first configuration indicating that CG PUSCH transmission should be prioritized over semi-static DL reception (i.e., reception of a semi-static signal or over a semi-static channel). The semi-static DL reception may be, for example, PDCCH reception. The semistatic DL reception may be higher-layer configured DL reception. The CG PUSCH transmission may also be considered semi-static in nature.

[0058] In some embodiments, the first configuration comprises a radio resource control (RRC) parameter indicating that the CG PUSCH transmission should be prioritized over the semi-static DL reception (i.e., the received RRC parameter may have a value which is indicative of CG PUSCH prioritization over the semi-static DL reception). The RRC parameter may be a binary parameter (i.e., a binary flag). One value of the binary RRC parameter may be used to indicate prioritization of the CG PUSCH transmission over the semi-static DL reception (the case of the embodiment shown in Figure 2) while the other value of the binary RRC parameter may be used to indicate prioritization of the semi-static DL reception over the CG PUSCH transmission. For example, a bit value ‘ 1’ may be used for indicating that the CG PUSCH should be prioritized while a bit value ‘0’ may be used for indicating that the semi-static DL reception should be prioritized. [0059] The apparatus receives, in block 202, from the access node, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions. At least one CG PUSCH transmission occasion defined in the second configuration overlaps with a semi-static DL reception. Such overlap may be possible due to the access node supporting SBFD communication, as was described above. In general, the overlap may be over one or more SBFD symbols. In general, the one or more resources may comprise one or more frequency resources and/or one or more time resources.

[0060] In some embodiments, the first and second configurations may be received in an opposite order compared to what is shown in Figure 2.

[0061] In some embodiments, the first and second configurations may be parts of a single configuration message received at the apparatus.

[0062] The apparatus determines, in block 203, based at least on the first configuration, whether to ignore the semi-static DL reception that overlaps with the at least one CG PUSCH transmission occasion (as defined in the second configuration).

[0063] According to (or based on) the determination in block 203, the apparatus may subsequently either ignore or perform the semi-static DL reception which overlaps with the at least one CG PUSCH transmission occasion. Ignoring the semi-static DL reception may be understood as not receiving or not attempting to receive or decode a (semi-static) DL signal or a (semi-static) DL channel. In the former case, the apparatus may transmit at least one signal at at least one of the at least one CG PUSCH transmission occasion overlapping with the (ignored) semi-static DL reception. Whether a signal is transmitted at given CG PUSCH transmission occasion may depend at least on whether said GC PUSCH transmission occasion is defined as usable by the apparatus or as not to be used by the apparatus.

[0064] As mentioned above, the determination in block 203 may be further based on whether any of the at least one CG PUSCH transmission occasion overlapping with the semistatic DL reception are usable by the apparatus. If the at least one overlapping CG PUSCH transmission occasion is known not to be used by the apparatus, there is no reason to ignore the semi-static DL reception even if the CG PUSCH transmission should be prioritized. Thus, in some embodiments, the determination in block 203 may be further based on knowledge of one or more (first) CG PUSCH transmission occasions usable for upcoming CG PUSCH transmissions at the apparatus and/or one or more (second) CG PUSCH transmission occasions not to be used by the apparatus. It should be emphasized that the one or more CG PUSCH transmission occasions usable for upcoming CG PUSCH transmissions at the apparatus are CG PUSCH transmission occasions which the apparatus is able to use but does not have to use. The one or more first and/or second CG PUSCH transmission occasions may be transmission occasions defined in the second configuration (though the second configuration itself may not provide information on whether they are usable by the terminal device).

[0065] Here and in the following embodiments, the terms “first CG PUSCH transmission occasion” and “second CG PUSCH transmission occasion” are used for referring to the CG PUSCH transmission occasions which are, respectively, usable for CG PUSCH transmission by the apparatus (e.g., the terminal device) and not to be used for CG PUSCH transmission by the apparatus. This convention is adapted merely for clarity of description, that is, no order between the transmission occasions is implied by these terms.

[0066] In some embodiments, the one or more first CG PUSCH transmission occasions usable for upcoming CG PUSCH transmissions at the apparatus and/or the one or more second CG PUSCH transmission occasions not to be used by the apparatus may be transmitted, by the apparatus, to the access node as a part of a report (e.g., a UTO-UCI report), as will be discussed below in detail in connection with Figure 6. The determination in block 203 may be based on said report.

[0067] Figure 3 illustrates process for enabling handling of collision(s) between semi- statically configured DL reception and semi-statically configured UL transmission (namely, CG PUSCH transmission) at a terminal device according to embodiments. The process of Figure 3 may be carried out by an apparatus which may be, for example, an access node (e.g., a gNB) or a part thereof. The access node carrying out the process of Figure 3 may be, for example, the access node 104 of Figure 1. The execution of Figure 3 (e.g., at an access node) may be occur in parallel with the execution of the process of Figure 2 (e.g., at a terminal device). The apparatus may be assumed to support full-duplex communication. In the following, the entity carrying out the process of Figure 3 is called an apparatus for simplicity.

[0068] Referring to Figure 3, the apparatus transmits, in block 301, to a terminal device, a first configuration indicating that CG PUSCH transmission should be prioritized over semi-static DL reception at the terminal device. The first configuration may be defined as described above in connection with Figure 2.

[0069] The apparatus transmits, in block 302, to the terminal device, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions. At least one CG PUSCH transmission occasion defined in the second configuration overlaps with a semi-static DL transmission. The second configuration may be defined as described above in connection with Figure 2.

[0070] The apparatus determines, in block 303, whether to drop the semi-static DL transmission which overlaps with the at least one CG PUSCH transmission occasion.

[0071] According to (or based on) the determination in block 303, the apparatus may subsequently drop or perform the semi-static DL transmission which overlaps with the at least one CG PUSCH transmission occasion. In the former case, the apparatus may receive at least one signal at at least one of the at least one CG PUSCH transmission occasion overlapping with the (dropped) semi-static DL transmission.

[0072] The determination in block 303 may be further based on whether any of the at least one CG PUSCH transmission occasion overlapping with the semi-static DL reception are usable by the terminal device. If the at least one overlapping CG PUSCH transmission occasion are known not to be used by the terminal device, there is no reason to drop the semi-static DL transmission even if the CG PUSCH transmission should be prioritized. Thus, in some embodiments, the determination in block 303 may be further based on knowledge of one or more first CG PUSCH transmission occasions usable for upcoming CG PUSCH transmissions at the terminal device and/or one or more second CG PUSCH transmission occasions not to be used by the terminal device. It should be emphasized that the one or more first CG PUSCH transmission occasions usable for upcoming CG PUSCH transmissions at the terminal device are CG PUSCH transmission occasions which the terminal device is able to use but does not have to use. The one or more first and/or second CG PUSCH transmission occasions may be transmission occasions defined in the second configuration (though the second configuration itself may not provide information on whether they are usable by the terminal device).

[0073] In some embodiments, the one or more first CG PUSCH transmission occasions usable for upcoming CG PUSCH transmissions at the terminal device and/or the one or more second CG PUSCH transmission occasions not to be used by the terminal device may be received, in the apparatus, as part(s) of a report (e.g., a UTO-UCI report), as will be discussed below in detail in connection with Figure 7.

[0074] Figure 4 illustrates process for handling collision(s) between semi-statically configured DL reception and semi-statically configured UL transmission (namely, CG PUSCH transmission) according to embodiments. Specifically, Figure 4 illustrates a case where the collision is handled by prioritizing semi-static DL reception over CG PUSCH transmission (i.e., the opposite case compared to Figures 2 & 3). The process of Figure 4 may be carried out by an apparatus which may be, for example, a terminal device (i.e., a UE) or a part thereof. The terminal device carrying out the process of Figure 4 may be, for example, one of the terminal devices 100, 102 of Figure 1. The apparatus may be assumed to support half-duplex communication but not full-duplex communication. In the following, the entity carrying out the process of Figure 4 is called an apparatus for simplicity.

[0075] Referring to Figure 4, the apparatus receives, in block 401, from an access node, a first configuration indicating that semi-static DL reception (i.e., reception of a semistatic signal or over a semi-static channel) should be prioritized over CG PUSCH transmission (or equally that CG PUSCH transmission should not be prioritized over semistatic DL reception). The semi-static DL reception may be, for example, PDCCH reception. The semi-static DL reception may correspond to higher-layer configured reception. The CG PUSCH transmission may also be considered semi-static in nature.

[0076] In some embodiments, the first configuration comprises a radio resource control (RRC) parameter indicating that the CG PUSCH transmission should be prioritized over the semi-static DL reception (i.e., the received RRC parameter may have a value which is indicative of CG PUSCH prioritization over the semi-static DL reception). The RRC parameter may be a binary parameter (i.e., a binary flag). One value of the binary RRC parameter may be used to indicate prioritization of the CG PUSCH transmission over the semi-static DL reception (the case of the embodiment shown in Figure 2) while the other value of the binary RRC parameter may be used to indicate prioritization of the semi-static DL reception over the CG PUSCH transmission (the case of the embodiment shown in Figure 4). For instance, prioritizeCG PUSCH overSemiStaticDL may be one example of such RRC parameter which may have two values: enabled or disabled (e.g., 1 and 0, respectively). [0077] For example, for a set of symbols of a slot that are indicated to a UE as flexible by tdd-UL-DL-ConfigurationCommon, and tdd-UL-DL-ConfigurationDedicated if provided, or for sub-band full duplex symbols with simultaneous UL and DL transmissions, the UE does not expect to receive both dedicated higher layer parameters configuring transmission from the UE in the set of symbols of the slot and dedicated higher layer parameters configuring reception by the UE in the set of symbols of the slot, except if the UE is provided with priotizeCG PUSCH overSemiStaticDL set to ‘enabled’ in configuredGrantConfig of a CG-PUSCH configuration in which the UE may transmit the CG-PUSCH and not receive the higher-layer configured reception (i.e., semi-static DL reception) or except if the UE is provided with priotizeCG PUSCH overSemiStaticDL set to ‘disabled’ in configuredGrantConfig of a CG-PUSCH configuration in which the UE receives the higher-layer configured reception (i.e., semi-static DL reception) and does not transmit the CG-PUSCH. However, if the UE is provided nrof UTO UCI in configuredGrantConfig of a CG-PUSCH configuration and prioritizeCG PUSCH overSemiStaticDL is set to ‘enabled’, and the UE reports a bit value of ‘ 1’ indicating that the UE will not transmit (i.e., UE is configured to not transmit) a CG- PUSCH in a set of symbols, the UE is expected to receive (i.e., the UE is configured to perform reception of) the higher-layer configured reception in the set of symbols.

[0078] The apparatus receives, in block 402, from the access node, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions. At least one CG PUSCH transmission occasion defined in the second configuration overlaps with a semi-static DL reception. Such overlap may be possible due to the wireless communication system comprising the apparatus and the access node supporting SBFD communication, as was described above.

[0079] Based at least on the first configuration, the apparatus drops, in block 403, the CG PUSCH transmission at least at the at least one CG PUSCH transmission occasion overlapping with the semi-static DL reception and performs, in block 403, the semi-static DL reception which overlaps with at least one CG PUSCH transmission occasion. The decision regarding dropping of the CG PUSCH transmission and the performing of the semistatic DL reception may be further based on the second configuration. Thus, in contrast to the embodiment discussed in connection with Figure 2, here the indication to prioritize the semi-static DL reception may always lead to prioritizing of the semi-static DL reception over any overlapping (potential) CG PUSCH transmissions, irrespective of whether the associated CG PUSCH transmission occasion(s) are usable or not to be used by the apparatus.

[0080] In some embodiments, an apparatus (e.g., a terminal device) may be configured to carry out both of the processes of Figures 2 & 4. In other words, the apparatus may be configured to carry out the process of blocks 202, 203 of Figure 2 in response to receiving a first configuration indicating that CG PUSCH transmission should be prioritized over semistatic DL reception (according to block 201 of Figure 2) and to carry out the process of block 402, 403 of Figure 4 in response to receiving a first configuration indicating that semi-static DL reception should be prioritized over CG PUSCH transmission (according to block 401 of Figure 4).

[0081] Figure 5 illustrates process for enabling handling of collision(s) between semi- statically configured DL reception and semi-statically configured UL transmission (namely, CG PUSCH transmission) at a terminal device according to embodiments. Specifically, Figure 5 illustrates a case where the collision is handled by prioritizing semi-static DL reception over CG PUSCH transmission (i.e., the opposite case compared to Figures 2 & 3). The process of Figure 5 may be carried out by an apparatus which may be, for example, an access node (e.g., a gNB) or a part thereof. The access node carrying out the process of Figure 5 may be, for example, the access node 104 of Figure 1. The execution of Figure 5 (e.g., at an access node) may be occur in parallel with the execution of the process of Figure 4 (e.g., at a terminal device). The apparatus may be assumed to support full-duplex communication. In the following, the entity carrying out the process of Figure 5 is called an apparatus for simplicity

[0082] Referring to Figure 5, the apparatus transmits, in block 501, to a terminal device, a first configuration indicating that semi-static DL reception should be prioritized over CG PUSCH transmission at the terminal device. The first configuration may be defined as described above in connection with Figure 4.

[0083] The apparatus transmits, in block 502, to the terminal device, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions. At least one CG PUSCH transmission occasion defined in the second configuration overlaps with a semi-static DL transmission. The second configuration may be defined as described above in connection with Figure 4. [0084] Based at least on the first configuration, the apparatus ignores, in block 503, CG PUSCH reception at least at the at least one CG PUSCH transmission occasion overlapping with the semi-static DL transmission and performs, in block 503, the semi-static DL transmission which overlaps with the at least one (dropped) CG PUSCH transmission occasion.

[0085] Figure 6 illustrates process for handling collision(s) between semi-statically configured DL reception and semi-statically configured UL transmission (namely, CG PUSCH transmission) according to embodiments. Specifically, Figure 6 illustrates a case where the collision is handled by prioritizing CG PUSCH transmission over semi-static DL reception. The process of Figure 6 may be carried out by an apparatus which may be, for example, a terminal device (i.e., a UE) or a part thereof. The terminal device carrying out the process of Figure 6 may be, for example, one of the terminal devices 100, 102 of Figure 1. The apparatus may be assumed to support half-duplex communication but not full-duplex communication. In the following, the entity carrying out the process of Figure 6 is called an apparatus for simplicity.

[0086] The process of Figure 6 may be considered one more detailed implementation of the process of Figure 2. Thus, any of the features and definitions discussed in connection with Figure 2 (and/or 3) may apply, mutatis mutandis, also here.

[0087] Similar to blocks 201, 202 of Figure 2, the apparatus initially receives, in block 601, from an access node, a first configuration indicating that CG PUSCH transmission should be prioritized over semi-static DL reception (i.e., reception of a semi-static signal or over a semi-static channel), and receives, in block 602, from the access node, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions. At least one CG PUSCH transmission occasion defined in the second configuration overlaps with a semi-static DL reception.

[0088] The apparatus transmits, in block 603, to the access node, a report indicating one or more first CG PUSCH transmission occasions as usable for upcoming CG PUSCH transmission by the apparatus and/or one or more second CG PUSCH TO(s) not to be used by apparatus. The one or more first and/or second CG PUSCH transmission occasions may be transmission occasions defined in the second configuration (though the second configuration itself may not provide information on whether they are usable by the terminal device). The generation of the report by the apparatus may be dependent on the first configuration (i.e., on whether the CG PUSCH transmission or the semi-static DL reception is prioritized) and/or the second configuration, as will be discussed further in connection with Figure 8. The report may be used subsequently by the access node (along with the first and second configurations) for determining whether it should expect to receive GC PUSCH transmission or to transmit a semi-static DL signal, as will be described in connection with Figure 7.

[0089] The report transmitted in block 603 may be an UTO-UCI report.

[0090] In some embodiments, the one or more first CG PUSCH transmission occasions may be indicated as respective one or more ‘0’ bits of the report (e.g., one or more ‘0’ bits in o^UTO~^ucl of an UTO-UCI report), and/or the one or more second CG PUSCH transmission occasions may be indicated as respective one or more ‘ 1 ’ bits of the report (e.g., one or more ‘ 1’ bits in o^UTO~^UCI of an UTO-UCI report).

[0091] The apparatus determines, in block 604, whether the one or more first CG PUSCH transmission occasions usable by the apparatus overlap with the semi-static DL reception. This determination may be at least based on the second configuration and the report.

[0092] If none of the one or more first CG PUSCH transmission occasions usable by the apparatus overlap with the semi-static DL reception in block 604 (i.e., the semi-static DL reception overlaps with zero or at least one of the one or more unused CG PUSCH transmission occasions not to be used by the apparatus but not with any CG PUSCH transmission occasion that is usable by the apparatus), the apparatus performs, in block 605, the semi-static DL reception (i.e., receives at least one signal in downlink at least during the overlapping one or more first CG PUSCH transmission occasions). In this case, the semistatic DL reception may still overlap with at least one of the one or more second CG PUSCH transmission occasions not to be used by the apparatus. Also in this case, the apparatus is assumed not to transmit any signals during the one or more overlapping CG PUSCH transmission occasions.

[0093] If at least one of the one or more first CG PUSCH transmission occasions usable by the apparatus overlaps with the semi-static DL reception in block 604, the apparatus ignores, in block 606, the semi-static DL reception and transmits, in block 606, at least one signal using at least the at least one of the one or more first CG PUSCH transmission occasions usable by the apparatus. The at least one signal may, in some cases, be transmitted also during at least one of the one or more second CG PUSCH transmission occasions not used by the apparatus.

[0094] Figure 7 illustrates process for enabling handling of collision(s) between semi- statically configured DL reception and semi-statically configured UL transmission (namely, CG PUSCH transmission) at a terminal device according to embodiments. The process of Figure 7 may be carried out by an apparatus which may be, for example, an access node (e.g., a gNB) or a part thereof. The access node carrying out the process of Figure 7 may be, for example, the access node 104 of Figure 1. The execution of Figure 7 (e.g., at an access node) may be occur in parallel with the execution of the process of Figure 6 (e.g., at a terminal device). The apparatus may be assumed to support full-duplex communication. In the following, the entity carrying out the process of Figure 7 is called an apparatus for simplicity.

[0095] The process of Figure 7 may be considered one more detailed implementation of the process of Figure 3. Thus, any of the features and definitions discussed in connection with Figure 3 (and/or 2) may apply, mutatis mutandis, also here.

[0096] Similar to blocks 301, 302 of Figure 3, the apparatus initially transmits, in block 701, to a terminal device, a first configuration indicating that CG PUSCH transmission should be prioritized over semi-static DL reception (i.e., reception of a semi-static signal or over a semi-static channel), and transmits, in block 702, to the terminal device, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions. At least one CG PUSCH transmission occasion defined in the second configuration overlaps with a semi-static DL reception.

[0097] The apparatus receives, in block 703, from the terminal device, a report indicating one or more first CG PUSCH transmission occasions as usable for upcoming CG PUSCH transmission by the terminal device and optionally one or more second CG PUSCH TO(s) not to be used by terminal device. The report may be defined as described in connection with Figure 6.

[0098] The apparatus determines, in block 704, whether the one or more first CG PUSCH transmission occasions usable by the terminal device overlap with the semi-static DL reception. This determination may be at least based on the second configuration and the report.

[0099] If none of the one or more first CG PUSCH transmission occasions usable by the apparatus overlap with the semi-static DL reception in block 704 (i.e., the semi-static DL reception overlaps with zero or at least one of the one or more unused CG PUSCH transmission occasions not to be used by the terminal device but not with any CG PUSCH transmission occasion that is usable by the terminal device), the apparatus performs, in block 705, the semi-static DL transmission (i.e., transmits at least one signal in uplink at least during the overlapping one or more first CG PUSCH transmission occasions). It may be assumed in this case that no CG PUSCH transmission is to be carried out by the terminal device (which may support only half-duplex) during the one or more overlapping CG PUSCH transmission occasions.

[00100] If at least one of the one or more first CG PUSCH transmission occasions usable by the terminal device overlaps with the semi-static DL reception in block 704, the apparatus drops, in block 706, the semi-static DL transmission and receives, in block 706, at least one signal using at least the at least one of the one or more first CG PUSCH transmission occasions usable by the terminal device.

[00101] Figure 8 illustrates process for handling collision(s) between semi-statically configured DL reception and semi-statically configured UL transmission (namely, CG PUSCH transmission) according to embodiments. Specifically, Figure 8 illustrates a case where the collision is handled by prioritizing semi-static DL reception over CG PUSCH transmission (i.e., the opposite case compared to Figures 6 & 7). The process of Figure 8 may be carried out by an apparatus which may be, for example, a terminal device (i.e., a UE) or a part thereof. The terminal device carrying out the process of Figure 8 may be, for example, one of the terminal devices 100, 102 of Figure 1. The apparatus may be assumed to support half-duplex communication but not full-duplex communication. In the following, the entity carrying out the process of Figure 8 is called an apparatus for simplicity

[00102] The process of Figure 8 may be considered one more detailed implementation of the process of Figure 4. Thus, any of the features and definitions discussed in connection with Figure 4 (and/or 5) may apply, mutatis mutandis, also here. [00103] Similar to blocks 401, 402 of Figure 4, the apparatus receives, in block 801, from an access node, a first configuration indicating that semi-static DL reception (i.e., reception of a semi-static signal or over a semi-static channel) should be prioritized over CG PUSCH transmission, and receives, in block 802, from the access node, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions. At least one CG PUSCH transmission occasion defined in the second configuration overlaps with a semi-static DL reception.

[00104] The apparatus generates, in block 803, a report indicating one or more first CG PUSCH transmission occasions as usable for upcoming CG PUSCH transmission by the apparatus and/or one or more second CG PUSCH TO(s) not to be used by the apparatus. The one or more first and/or second CG PUSCH transmission occasions may be transmission occasions defined in the second configuration (though the second configuration itself may not provide information on whether they are usable by the terminal device). The generation of the report in block 803 may be dependent on the first configuration (i.e., on whether the CG PUSCH transmission or the semi-static DL reception is prioritized) and/or the second configuration.

[00105] The report generated in block 803 may be an UTO-UCI report.

[00106] In some embodiments, the one or more first CG PUSCH transmission occasions may be indicated as respective one or more ‘0’ bits of the report (e.g., one or more ‘0’ bits in o^UTO~^ucl of an UTO-UCI report), and/or the one or more second CG PUSCH transmission occasions may be indicated as respective one or more ‘ 1 ’ bits of the report (e.g., one or more ‘ 1’ bits in o^UTO~^UCI of an UTO-UCI report.

[00107] The generation of the report in block 803 may comprise omitting, from the report (i.e., from at least one CG PUSCH transmission occasion to be reported), any CG PUSCH transmission occasions overlapping (in at least one SBFD symbol) with the semistatic DL reception based on the second configuration. In other words, only CG PUSCH transmission occasions which do not overlap with the semi-static DL reception based on the second configuration are included in the report. Such omitted CG PUSCH transmission occasions may comprise first CG PUSCH transmission occasion(s) usable by the apparatus and/or second CG PUSCH transmission occasion(s) not to be used by the apparatus. The omitted CG PUSCH transmission occasion(s) may not be indicated at all in the report (i.e., not even as unused by the apparatus). As a result of said omission, the generated report may comprise zero or more first CG PUSCH transmission occasions indicated as usable for upcoming CG PUSCH transmission by the apparatus though none of said zero or more first CG PUSCH transmission occasions overlap with the semi-static DL reception. This operation may be carried out only when the first configuration indicates that the semi-static DL reception is to be prioritized at the apparatus over the CG PUSCH transmission (i.e., not in the case discussed in connection with Figure 6) as, in this particular case, the information regarding CG PUSCH transmission occasions overlapping with the semi-static DL reception is of little use to the access node as the semi-static DL reception will, in any case, be prioritized over the CG PUSCH transmission at those overlapping CG PUSCH transmission occasions. If the report is an UTO-UCI report, this omitting may mean, in practice, that the CG PUSCH transmission occasions to be omitted are not counted in the O^UTO~^UCI bits of the UTO-UCI report (i.e., they are indicated neither as usable by the apparatus nor as not used by the apparatus). The omitting feature described in this paragraph provides the technical benefit of reduction of signaling/processing overhead.

[00108] The apparatus transmits, in block 804, the generated report to the access node.

[00109] Similar to block 403 of Figure 4, based at least on the first configuration, the apparatus drops, in block 805, the CG PUSCH transmission (at least at the least one CG PUSCH transmission occasion) and performs, in block 805, the semi-static DL reception which overlaps with the at least one CG PUSCH transmission occasion. The decision regarding dropping of the CG PUSCH transmission and the performing of the semi-static DL reception may be further based on the second configuration.

[00110] In some embodiments, an apparatus (e.g., a terminal device) may be configured to carry out both of the processes of Figures 6 & 8. In other words, the apparatus may be configured to carry out the process of blocks 202 to 606 of Figure 6 in response to receiving a first configuration indicating that CG PUSCH transmission should be prioritized over semi-static DL reception (according to block 201 of Figure 2) and to carry out the process of block 802 to 805 of Figure 8 in response to receiving a first configuration indicating that semi-static DL reception should be prioritized over CG PUSCH transmission (according to block 401 of Figure 4).

[00111] Figure 9 illustrates process for enabling handling of collision(s) between semi- statically configured DL reception and semi-statically configured UL transmission (namely, CG PUSCH transmission) at a terminal device according to embodiments. The process of Figure 9 may be carried out by an apparatus which may be, for example, an access node (e.g., a gNB) or a part thereof. The access node carrying out the process of Figure 9 may be, for example, the access node 104 of Figure 1. The execution of Figure 9 (e.g., at an access node) may be occur in parallel with the execution of the process of Figure 8 (e.g., at a terminal device). The apparatus may be assumed to support full-duplex communication. In the following, the entity carrying out the process of Figure 9 is called an apparatus for simplicity.

[00112] The process of Figure 9 may be considered one more detailed implementation of the process of Figure 5. Thus, any of the features and definitions discussed in connection with Figure 5 (and/or 4) may apply, mutatis mutandis, also here.

[00113] Similar to blocks 501, 502 of Figure 5, the apparatus transmits, in block 901, to a terminal device, a first configuration indicating that semi-static DL reception should be prioritized over CG PUSCH transmission at the terminal device, and transmits, in block 902, to the terminal device, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions. At least one CG PUSCH transmission occasion defined in the second configuration overlaps with a semi-static DL transmission. The second configuration may be defined as described above in connection with Figure 7.

[00114] The apparatus receives, in block 903, from the terminal device, a report (being, e.g., an UTO-UCI report) indicating one or more first CG PUSCH transmission occasions as usable for upcoming CG PUSCH transmission by the terminal device and/or one or more second CG PUSCH TO(s) not to be used by the terminal device. The report may have been generated by the terminal device as discussed in connection with Figure 8. Thus, in some embodiments, the report may comprise no CG PUSCH transmission occasions overlapping with the semi-static DL transmission (i.e., zero first CG PUSCH transmission occasions overlapping with the semi-static DL transmission and zero second CG PUSCH transmission occasions overlapping with the semi-static DL transmission) as such CG PUSCH transmission occasions may have been omitted or removed already when generating the report.

[00115] Based at least on the first configuration, the apparatus ignores, in block 904, CG PUSCH reception and performs, in block 904, the semi-static DL transmission that overlaps with the at least one (dropped) CG PUSCH transmission occasion. [00116] Figure 11 illustrates a flow diagram according to an embodiment. The steps of Figure 11 may be performed (i.e., is configured to perform) by an apparatus that is a UE or a part of a UE (e.g. comprised in the UE). Referring to Figure 11, in step 1101, the apparatus obtains, from an access node, a configuration indicating whether configured grant physical uplink shared channel, CG PUSCH, transmission is to be prioritized over semi-static downlink, DL, reception that overlaps with at least one CG PUSCH transmission occasion of the CG PUSCH transmission. The configuration obtained (e.g. received from the access node) may also be referred to as first configuration (e.g., as received in step 401 of Figure 4 embodiment or in step 501 of Figure 5 embodiment). The word ‘either’ should be interpreted here so that the apparatus performs one of the operations (i.e., one of CG PUSCH transmission or semi-static DL reception), but not the other.

[00117] In step 1102, based at least on the configuration obtained in step 1101, the apparatus either transmits the CG PUSCH transmission or performs the semi-static DL reception. That is, for instance, the apparatus may transmit CG PUSCH transmission if the configuration indicates that CG PUSCH transmission is to be prioritized over semi-static DL reception. Or, for instance, the apparatus may perform semi-static DL reception if the configuration indicates that semi-static DL reception is to be prioritized over CG PUSCH transmission.

[00118] Figure 12 illustrates an embodiment in which the apparatus determines which one to prioritize: CG PUSCH transmission or semi-static DL reception.

[00119] In step 1201, the apparatus obtains the configurations similarly as in step 1101.

[00120] In step 1202, the apparatus determines that the semi-static DL reception, configured for the apparatus, overlaps with at least one CG PUSCH transmission occasion of the CG PUSCH transmission configured for the apparatus. For example, this determination may be based on configuration of one or more CG PUSCH transmission occasions received from the access node. Such configuration of the one or more CG PUSCH transmission occasions may be referred to as second configuration herein (see e.g., steps 202 and 402).

[00121] Based on the determining in step 1202, the apparatus applies, at least, the configuration obtained in step 1201 to determine (step 1203) which one of the following to prioritize: the CG PUSCH transmission, or the semi-static DL reception. [00122] In an embodiment, the configuration indicates that the CG PUSCH transmission is to be prioritized over the semi-static DL reception that overlaps with the at least one CG PUSCH transmission occasion of the CG PUSCH transmission. Thus, the apparatus is caused to transmit the CG PUSCH transmission based on the configuration as in step 1205.

[00123] In an embodiment, step 1205 further includes the apparatus to ignore the semistatic DL reception.

[00124] In an embodiment, the configuration indicates that the semi-static DL reception, which overlaps with the at least one CG PUSCH transmission occasion of the CG PUSCH transmission, is to be prioritized over the CG PUSCH transmission. Thus, the apparatus is caused to perform the semi-static DL reception as in step 1204.

[00125] In an embodiment, step 1204 further includes the apparatus to, based on the configuration, prevent transmitting the CG PUSCH transmission using the at least one CG PUSCH transmission occasion which overlaps with the semi-static DL reception. Thus, the transmission occasion(s) that overlap with the semi-static DL reception that should be prioritized are not used by the apparatus.

[00126] The determination of which action (e.g. of step 1102 or 1204/1205) to perform may thus base at least on the configuration (obtained e.g., in step 1101, 1201). Additionally, the determination may be further based on a message, transmitted from the apparatus to the access node, indicating one or more transmission occasions as usable by the apparatus and/or one or more transmission occasions as not to be used by the apparatus. This message may be an unused transmit occasion-uplink control information, UTO-UCI, reporting message or comprises UTO-UCI. Thus, the message may be referred to as report herein. Below are listed some examples of how the apparatus may be configured to act depending on the configuration and the message.

[00127] For example, if the configuration indicates that the CG PUSCH transmission is to be prioritized over the semi-static DL reception that overlaps with the at least one CG PUSCH transmission occasion of the CG PUSCH transmission and if the semi-static DL reception overlaps with one or more CG PUSCH transmission occasions that are indicated as usable by the apparatus (i.e., using the message), the first apparatus is caused to transmit the CG PUSCH transmission. Additionally, the apparatus may further be caused to ignore the semi-static DL reception.

[00128] For example, if the configuration indicates that the CG PUSCH transmission is to be prioritized over the semi-static DL reception that overlaps with the at least one CG PUSCH transmission occasion of the CG PUSCH transmission and if the semi-static DL reception does not overlap with any CG PUSCH transmission occasions that are indicated as usable by the apparatus (i.e., using the message), the first apparatus is caused to perform the semi-static DL reception. Additionally, the apparatus may further be caused to prevent transmitting CG PUSCH transmission as the overlapping transmission occasions are indicated as unused and therefore cannot be used by the apparatus.

[00129] In an embodiment, if the configuration indicates that the semi-static DL reception, which overlaps with the at least one CG PUSCH transmission occasion of the CG PUSCH transmission, is to be prioritized over the CG PUSCH transmission, the apparatus is caused to generate the message such that the message does not indicate any transmission occasions that overlap with the semi-static DL reception. Thus, the message may not indicate any transmission occasions that would overlap with the semi-static DL reception. For example, this may mean that transmission occasion or transmission occasions that overlap with the semi-static DL reception are not counted in a bitmap of O^UTO~^UCI bits of the UTO- UCI.

[00130] The blocks, related functions, and information exchanges described above by means of Figures 2 to 9 and 11 to 12 are in no absolute chronological order, and some of them may be performed simultaneously or in an order differing from the given one. Other functions can also be executed between them or within them, and other information may be sent, and/or other rules applied. Some of the blocks or part of the blocks or one or more pieces of information can also be left out or replaced by a corresponding block or part of the block or one or more pieces of information.

[00131] The embodiments provide at least the following technical advantages. The embodiments allow semi-static DL and (semi-static) UL CG-PUSCH to overlap in time with specific rules on which channel to prioritize in case of such overlaps. This results in more flexible resource allocation and reduces the burden on the access node on having to meticulously configure UL and DL signals in a way that unexpected UL-DL collision cases are avoided at the UE side. The proposed interplay with existing UTO-UCI furthermore allows the access node to know when the terminal device is expected to transmit or receive, improving the radio resource efficiency in both UL and DL directions. Finally, by omitting CG PUSCH transmission occasions overlapping with the semi-static DL transmission which is to be prioritized from the (UTO-UCI) report, processing/signaling overhead can be reduced.

[00132] Figure 10 provides an apparatus 1001 according to some embodiments. The apparatus 1001 of Figure 10 may be, for example, a terminal device or a part thereof or an access node (e.g., a gNB) or a part thereof. The apparatus 1001 may be any of the terminal devices 100, 102 or the access node 104 of Figure 1.

[00133] The apparatus 1001 may comprise one or more communication control circuitry 1020, such as at least one processor, and at least one memory 1030, including one or more algorithms 1031 (instructions), such as a computer program code (software) wherein the at least one memory and the computer program code (software) are configured, with the at least one processor, to cause the apparatus 1001 to carry out any one of the exemplified functionalities of the apparatus (e.g., the terminal device or the access node) described above. Said at least one memory 1030 may also comprise at least one database 1032.

[00134] When the one or more communication control circuitry 1020 comprises more than one processor, the apparatus 1001 may be a distributed device wherein processing of tasks takes place in more than one physical unit. Each of the at least one processor may comprise one or more processor cores. A processing core may comprise, for example, a Cortex-A8 processing core manufactured by ARM Holdings or a Zen processing core designed by Advanced Micro Devices Corporation. The one or more communication control circuitry 1020 may comprise at least one Qualcomm Snapdragon and/or Intel Atom processor. The one or more communication control circuitry 1020 may comprise at least one application-specific integrated circuit (ASIC). The one or more control circuitry 1020 may comprise at least one field-programmable gate array (FPGA).

[00135] Referring to Figure 10, the one or more communication control circuitry 1020 of the apparatus 1001 are configured to carry out functionalities of the A-IoT device, the reader or the activator described above by means of any of Figures 2 to 9 or 11 to 12 using one or more individual circuitries. It is also feasible to use specific integrated circuits, such as ASIC (Application Specific Integrated Circuit) or other components and devices for implementing the functionalities in accordance with different embodiments. [00136] Referring to Figure 10, the apparatus 1001 may further comprise different interfaces (I/F) 1010 such as one or more communication interfaces comprising hardware and/or software for realizing communication connectivity according to one or more communication protocols. If the apparatus 1001 is a terminal device, the one or more communication interfaces 1010 may comprise, for example, at least one communication interface between the apparatus 1001 and at least one access node. If the apparatus 1001 is an access node, the one or more communication interfaces 1010 may comprise, for example, at least one communication interface between the apparatus 1001 and at least one terminal device.

[00137] The one or more communication interfaces 1010 may comprise standard well- known components such as an amplifier, filter, frequency-converter, (de)modulator, and encoder/decoder circuitries, controlled by the corresponding controlling units, and one or more antennas. The apparatus 1001 may also comprise one or more user interfaces.

[00138] Referring to Figure 10, the memory 1030 may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.

[00139] As used in this application, the term ‘circuitry’ may refer to one or more or all of the following: (a) hardware-only circuit implementations, such as implementations in only analog and/or digital circuitry, and (b) combinations of hardware circuits and software (and/or firmware), such as (as applicable): (i) a combination of analog and/or digital hardware circuit(s) with software/firmware and (ii) any portions of hardware processor(s) with software, including digital signal processor(s), software, and memory(ies) that work together to cause an apparatus, such as a terminal device or an access node, to perform various functions, and (c) hardware circuit(s) and processor(s), such as a microprocessor s) or a portion of a microprocessor(s), that requires software (e.g. firmware) for operation, but the software may not be present when it is not needed for operation. This definition of ‘circuitry’ applies to all uses of this term in this application, including any claims. As a further example, as used in this application, the term ‘circuitry’ also covers an implementation of merely a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. [00140] In an embodiment, at least some of the processes described in connection with Figures 2 to 9 or 11 to 12 may be carried out by an apparatus comprising corresponding means for carrying out at least some of the described processes. Some example means for carrying out the processes may include at least one of the following: detector, processor (including dual-core and multiple-core processors), digital signal processor, controller, receiver, transmitter, encoder, decoder, memory, RAM, ROM, software, firmware, display, user interface, display circuitry, user interface circuitry, user interface software, display software, circuit, filter (low-pass, high-pass, bandpass and/or bandstop), sensor, circuitry, inverter, capacitor, inductor, resistor, operational amplifier, diode and transistor. In an embodiment, the at least one processor, the memory, and the computer program code form processing means or comprises one or more computer program code portions for carrying out one or more operations according to any one of the embodiments of Figures 2 to 9 or 11 to 12 or operations thereof. In some embodiments, at least some of the processes may be implemented using discrete components.

[00141] Embodiments as described may also be carried out, fully or at least in part, in the form of a computer process defined by a computer program or portions thereof. Embodiments of the methods described in connection with any of Figures 2 to 9 or 11 to 12 may be carried out by executing at least one portion of a computer program comprising corresponding instructions. The computer program may be provided as a computer readable medium comprising program instructions stored thereon or as a non-transitory computer readable medium comprising program instructions stored thereon. The computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, which may be any entity or device capable of carrying the program. For example, the computer program may be stored on a computer program distribution medium readable by a computer or a processor. The computer program medium may be, for example but not limited to, a record medium, computer memory, read-only memory, electrical carrier signal, telecommunications signal, and software distribution package, for example. The computer program medium may be a non-transitory medium. Coding of software for carrying out the embodiments as shown and described is well within the scope of a person of ordinary skill in the art.

[00142] In the following, some examples are provided. [00143] Example 1. An apparatus (e.g. an UE) comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from an access node, a first configuration indicating that semi-static downlink, DL, reception should be prioritized over configured grant physical uplink shared channel, CG PUSCH, transmission; receive, from the access node, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions, wherein at least one CG PUSCH transmission occasion in the second configuration overlaps with a semi-static DL reception; and based at least on the first configuration, drop the CG PUSCH transmission at the at least one CG PUSCH transmission occasion and perform the semi-static DL reception.

[00144] Example 2. The apparatus of Example 1, wherein the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to: transmit, to the access node, a report indicating one or more first CG PUSCH transmission occasions usable for upcoming CG PUSCH transmission by the apparatus and/or one or more second CG PUSCH transmission occasions not to be used for upcoming CG PUSCH transmission by the apparatus.

[00145] Example 3. The apparatus of Example 2, wherein the one or more first CG PUSCH transmission occasions usable for upcoming CG PUSCH transmission by the apparatus are indicated, in the report, as respective zero or more ‘0’ bits and/or the one or more second CG PUSCH transmission occasions not to be used for upcoming CG PUSCH transmission by the apparatus are indicated, in the report, as respective one or more ‘ 1’ bits.

[00146] Example 4. The apparatus of Example 2 or 3, wherein the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to: generate the report based at least on the first and second configurations.

[00147] Example 5. The apparatus of Example 4, wherein the generating of the report comprises: omitting, from the report, any CG PUSCH transmission occasions overlapping with the semi-static DL reception based on the second configuration.

[00148] Example 6. The apparatus according to any of Examples 2 to 5, wherein the report is an unused transmission occasions-uplink control information, UTO-UCI, report. [00149] Example 7. The apparatus according to any of Examples 1 to 6, wherein the first configuration comprises a binary radio resource control, RRC, parameter indicating that the semi-static DL reception should be prioritized over the CG PUSCH transmission.

[00150] Example 8. A method comprising: receiving, from an access node, a first configuration indicating that semi-static downlink, DL, reception should be prioritized over configured grant physical uplink shared channel, CG PUSCH, transmission; receiving, from the access node, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions, wherein at least one CG PUSCH transmission occasion in the second configuration overlaps with a semi-static DL reception; and based at least on the first configuration, dropping the CG PUSCH transmission at the at least one CG PUSCH transmission occasion and performing the semi-static DL reception

[00151] Example 9. An apparatus (e.g. a UE) comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: obtain, from an access node, a configuration indicating whether configured grant physical uplink shared channel, CG PUSCH, transmission is to be prioritized over semi-static downlink, DL, reception that overlaps with at least one CG PUSCH transmission occasion of the CG PUSCH transmission; and based at least on the configuration, either transmit the CG PUSCH transmission or perform the semi-static DL reception.

[00152] Example 10. The apparatus of Example 9, wherein the apparatus is further caused to: determine that the semi-static DL reception, configured for the apparatus, overlaps with at least one CG PUSCH transmission occasion of the CG PUSCH transmission configured for the apparatus; based on the determining, apply at least the configuration to determine which one of the following to prioritize: the CG PUSCH transmission, or the semistatic DL reception.

[00153] Example 11. The apparatus of Example 9 or 10, wherein the configuration indicates that the CG PUSCH transmission is to be prioritized over the semi-static DL reception that overlaps with the at least one CG PUSCH transmission occasion of the CG PUSCH transmission, and wherein the apparatus is caused to transmit the CG PUSCH transmission based on the configuration. [00154] Example 12. The apparatus of Example 11, wherein the apparatus is further caused to, based on the configuration, ignore the semi-static DL reception.

[00155] Example 13. The apparatus of Example 9 or 10, wherein the configuration indicates that the semi-static DL reception, which overlaps with the at least one CG PUSCH transmission occasion of the CG PUSCH transmission, is to be prioritized over the CG PUSCH transmission, and wherein the apparatus is caused to perform the semi-static DL reception.

[00156] Example 14. The apparatus of Example 13, wherein the apparatus is further caused to, based on the configuration, prevent transmitting the CG PUSCH transmission using the at least one CG PUSCH transmission occasion which overlaps with the semi-static DL reception.

[00157] Example 15. The apparatus of Example 9 or 10, wherein the apparatus is further caused to: transmit, to an access node, a message indicating one or more transmission occasions as usable by the apparatus and/or one or more transmission occasions as not to be used by the apparatus, wherein the apparatus is caused, based on the configuration and the message, either to transmit the CG PUSCH transmission or to perform the semi-static DL reception.

[00158] Example 16. The apparatus of Example 15, wherein if the configuration indicates that the CG PUSCH transmission is to be prioritized over the semi-static DL reception that overlaps with the at least one CG PUSCH transmission occasion of the CG PUSCH transmission and if the semi-static DL reception overlaps with one or more CG PUSCH transmission occasions that are indicated as usable by the apparatus, the apparatus is caused to transmit the CG PUSCH transmission.

[00159] Example 17. The apparatus of Example 16, wherein the apparatus is further caused to ignore the semi-static DL reception.

[00160] Example 18. The apparatus of Example 15, wherein if the configuration indicates that the CG PUSCH transmission is to be prioritized over the semi-static DL reception that overlaps with the at least one CG PUSCH transmission occasion of the CG PUSCH transmission and if the semi-static DL reception does not overlap with any CG PUSCH transmission occasions that are indicated as usable by the apparatus, the apparatus is caused to perform the semi-static DL reception. [00161] Example 19. The apparatus of Example 18, wherein the apparatus is further caused to prevent transmitting the CG PUSCH transmission.

[00162] Example 20. The apparatus of Example 15, wherein if the configuration indicates that the semi-static DL reception, which overlaps with the at least one CG PUSCH transmission occasion of the CG PUSCH transmission, is to be prioritized over the CG PUSCH transmission, the apparatus is caused to generate the message such that the message does not indicate any transmission occasions that overlap with the semi-static DL reception.

[00163] Example 21. The apparatus of any of Examples 15 to 20, wherein the message is an unused transmit occasion-uplink control information, UTO-UCI, reporting message or comprises UTO-UCI.

[00164] Example 22. The apparatus of Example 21 when dependent on Example 20, wherein the message not indicating any transmission occasions that overlap with the semistatic DL reception denotes that transmission occasion or transmission occasions that overlap with the semi-static DL reception are not counted in a bitmap of O^A(UTO-UCI) bits.

[00165] Example 23. A method for user equipment, the method comprising: obtaining, from an access node, a configuration indicating whether configured grant physical uplink shared channel, CG PUSCH, transmission is to be prioritized over semi-static downlink, DL, reception that overlaps with at least one CG PUSCH transmission occasion of the CG PUSCH transmission; and based at least on the configuration, either transmitting the CG PUSCH transmission or performing the semi-static DL reception.

[00166] Example 24. An apparatus (e.g. a UE) comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from an access node, a first configuration indicating that configured grant physical uplink shared channel, CG PUSCH, transmission should be prioritized over semi-static downlink, DL, reception; receive, from the access node, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions, wherein at least one CG PUSCH transmission occasion in the second configuration overlaps with a semi-static DL reception; and determine, based at least on the first configuration, whether to ignore the semi-static DL reception that overlaps with the at least one CG PUSCH transmission occasion. [00167] Example 25. The apparatus of Example 24, wherein the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to: in accordance with determining to ignore the semi-static DL reception that overlaps with the at least one CG PUSCH transmission occasion, ignore the semi-static DL reception.

[00168] Example 26. The apparatus of Example 24 or 25, wherein the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to ignore the semi-static DL reception if the semi-static DL reception overlaps with one or more CG PUSCH transmission occasions that are usable by the apparatus.

[00169] Example 27. The apparatus of Example 24, wherein the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to: transmit, to the access node, a report indicating at least one or more first CG PUSCH transmission occasions as usable for upcoming CG PUSCH transmission by the apparatus; and determine to ignore the semi-static DL reception based on the first configuration and on that the semi-static DL reception overlaps with at least one of the one or more first CG PUSCH transmission occasions indicated by the report as usable.

[00170] Example 28. The apparatus of any of Examples 25 to 27, wherein the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to: transmit at least one signal using at least one CG PUSCH transmission occasion that overlaps with the ignored semi-static DL reception.

[00171] Example 29. The apparatus of Example 24, wherein the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to perform the semi-static DL reception if the semi-static DL reception does not overlap with one or more CG PUSCH transmission occasions that are usable by the apparatus.

[00172] Example 30. The apparatus of Example 24, wherein the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to: transmit, to the access node, a report indicating at least zero or more first CG PUSCH transmission occasions as usable for upcoming CG PUSCH transmission by the apparatus and one or more second CG PUSCH transmission occasions not to be used by the apparatus, wherein the determining whether to ignore the semi-static DL reception that overlaps with the at least one CG PUSCH transmission occasion is further based on the report; and based at least on the report, determine to perform the semi-static DL reception if the semi-static DL transmission overlaps with at least one of the one or more second CG PUSCH transmission occasions not to be used by the apparatus but not with any of the zero or more first CG PUSCH transmission occasions that are usable by the apparatus.

[00173] Example 31. The apparatus according to any of Examples 24 to 30, wherein the first configuration comprises a binary radio resource control, RRC, parameter indicating that the CG PUSCH transmission should be prioritized over the semi-static DL reception.

[00174] The term “non-transitory”, as used herein, is a limitation of the medium itself (that is, tangible, not a signal) as opposed to a limitation on data storage persistency (for example, RAM vs. ROM).

[00175] Reference throughout this specification to one embodiment or an embodiment means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present solution. Thus, appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment.

[00176] As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. In addition, various embodiments and example of the present solution may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as de facto equivalents of one another, but are to be considered as separate and autonomous representations of the present solution.

[00177] Even though embodiments have been described above with reference to examples according to the accompanying drawings, it is clear that the embodiments are not restricted thereto but can be modified in several ways within the scope of the appended claims. Therefore, all words and expressions should be interpreted broadly and they are intended to illustrate, not to restrict, the embodiment. It will be obvious to a person skilled in the art that, as technology advances, the inventive concept can be implemented in various ways. Further, it is clear to a person skilled in the art that the described embodiments may, but are not required to, be combined with other embodiments in various ways.

INDUSTRIAL APPLICABILITY [00178] At least some embodiments find industrial application in wireless communications.

Claims

1. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from an access node, a first configuration indicating that semi-static downlink, DL, reception should be prioritized over configured grant physical uplink shared channel, CG PUSCH, transmission; receive, from the access node, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions, wherein at least one CG PUSCH transmission occasion in the second configuration overlaps with a semi-static DL reception; and based at least on the first configuration, drop the CG PUSCH transmission at the at least one CG PUSCH transmission occasion and perform the semi-static DL reception.

2. The apparatus of claim 1, wherein the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to: transmit, to the access node, a report indicating one or more first CG PUSCH transmission occasions usable for upcoming CG PUSCH transmission by the apparatus and/or one or more second CG PUSCH transmission occasions not to be used for upcoming CG PUSCH transmission by the apparatus.

3. The apparatus of claim 2, wherein the one or more first CG PUSCH transmission occasions usable for upcoming CG PUSCH transmission by the apparatus are indicated, in the report, as respective zero or more ‘0’ bits and/or the one or more second CG PUSCH transmission occasions not to be used for upcoming CG PUSCH transmission by the apparatus are indicated, in the report, as respective one or more ‘ 1’ bits.

4. The apparatus of claim 2 or 3, wherein the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to: generate the report based at least on the first and second configurations.

5. The apparatus of claim 4, wherein the generating of the report comprises: omitting, from the report, any CG PUSCH transmission occasions overlapping with the semi-static DL reception based on the second configuration.

6. The apparatus according to any of claims 2 to 5, wherein the report is an unused transmission occasions-uplink control information, UTO-UCI, report.

7. The apparatus according to any preceding claim, wherein the first configuration comprises a binary radio resource control, RRC, parameter indicating that the semi-static DL reception should be prioritized over the CG PUSCH transmission.

8. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: transmit, to a terminal device, a first configuration indicating that semi-static DL reception should be prioritized over CG PUSCH transmission at the terminal device; transmit, to the terminal device, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions, wherein at least one CG PUSCH transmission occasion in the second configuration overlaps with a semi-static DL transmission; and based at least on the first configuration, ignore CG PUSCH reception at least at the at least one CG PUSCH transmission occasion and perform the semi-static DL transmission.

9. The apparatus of claim 8 wherein the at least one memory and the instructions are configured, with the at least one processor, to cause the apparatus to: receive, from the terminal device, a report indicating one or more first CG PUSCH transmission occasions usable for upcoming CG PUSCH transmission by the terminal device and/or one or more second CG PUSCH transmission occasions not to be used for upcoming CG PUSCH transmission by the apparatus, wherein the report comprises no CG PUSCH transmission occasions overlapping with the semi-static DL transmission.

10. The apparatus of claim 9, wherein the report is a UTO-UCI report.

11. The apparatus according to any of claims 8 to 10, wherein the first configuration comprises a binary radio resource control, RRC, parameter indicating that the semi-static DL reception should be prioritized over the CG PUSCH transmission.

12. A method comprising: receiving, from an access node, a first configuration indicating that semi-static downlink, DL, reception should be prioritized over configured grant physical uplink shared channel, CG PUSCH, transmission; receiving, from the access node, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions, wherein at least one CG PUSCH transmission occasion in the second configuration overlaps with a semi-static DL reception; and based at least on the first configuration, dropping the CG PUSCH transmission at the at least one CG PUSCH transmission occasion and performing the semi-static DL reception

13. A method comprising: transmitting, to a terminal device, a first configuration indicating that semi-static DL reception should be prioritized over CG PUSCH transmission at the terminal device; transmitting, to the terminal device, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions, wherein at least one CG PUSCH transmission occasion in the second configuration overlaps with a semi-static DL transmission; and based at least on the first configuration, ignoring CG PUSCH reception at least at the at least one CG PUSCH transmission occasion and performing the semi-static DL transmission

14. A non-transitory computer readable medium having stored thereon instructions that, when executed by a computing device, cause the computing device to: receive, from an access node, a first configuration indicating that semi-static downlink, DL, reception should be prioritized over configured grant physical uplink shared channel, CG PUSCH, transmission; receive, from the access node, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions, wherein at least one CG PUSCH transmission occasion in the second configuration overlaps with a semi-static DL reception; and based at least on the first configuration, drop the CG PUSCH transmission at the at least one CG PUSCH transmission occasion and perform the semi-static DL reception.

15. A non-transitory computer readable medium having stored thereon instructions that, when executed by a computing device, cause the computing device to: transmit, to a terminal device, a first configuration indicating that semi-static DL reception should be prioritized over CG PUSCH transmission at the terminal device; transmit, to the terminal device, a second configuration that configures one or more resources for one or more CG PUSCH transmission occasions, wherein at least one CG PUSCH transmission occasion in the second configuration overlaps with a semi-static DL transmission; and based at least on the first configuration, ignoring CG PUSCH reception at least at the at least one CG PUSCH transmission occasion and performing the semi-static DL transmission.