CROSS-RELERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to United States Patent Application Serial Number 63/044,240 entitled “APPARATUSES, METHODS, AND SYSTEMS FOR SEMI-PERSISTENT SCHEDULING FOR AN ULTRA-RELIABLE LOW-LATENCY COMMUNICATION OPERATION IN AN UNLICENSED ENVIRONMENT” and filed on June 25, 2020 for Hossein Bagheri, which is incorporated herein by reference in its entirety.

FIELD

[0002] The subject matter disclosed herein relates generally to wireless communications and more particularly relates to overlapping physical downlink shared channel transmissions.

BACKGROUND

[0003] In certain wireless communications networks, multiple physical downlink shared channel transmission may be made. The physical downlink shared channels may overlap with one another.

BRIEF SUMMARY

[0004] Methods for overlapping physical downlink shared channel transmissions are disclosed. Apparatuses and systems also perform the functions of the methods. One embodiment of a method includes determining whether a first physical downlink shared channel transmission associated with a first semi-persistent scheduling configuration overlaps with a second physical downlink shared channel transmission associated with a second semi-persistent scheduling configuration. The first semi-persistent scheduling configuration has a lower semi-persistent scheduling configuration index than the second semi-persistent scheduling configuration. In some embodiments, the method includes, in response to determining that the first physical downlink shared channel transmission overlaps with the second physical downlink shared channel transmission: determining whether a first acknowledgment corresponding to the first physical downlink shared channel transmission can be transmitted; and determining whether a second acknowledgment corresponding to the second physical downlink shared channel transmission can be transmitted. In certain embodiments, the method includes, in response to determining that the first acknowledgement cannot be transmitted and that the second acknowledgement can be transmitted, decoding the second physical downlink shared channel and not decoding the first physical downlink shared channel. [0005] One apparatus for overlapping physical downlink shared channel transmissions includes a processor that: determines whether a first physical downlink shared channel transmission associated with a first semi-persistent scheduling configuration overlaps with a second physical downlink shared channel transmission associated with a second semi-persistent scheduling configuration, wherein the first semi-persistent scheduling configuration has a lower semi-persistent scheduling configuration index than the second semi-persistent scheduling configuration; in response to determining that the first physical downlink shared channel transmission overlaps with the second physical downlink shared channel transmission: determines whether a first acknowledgment corresponding to the first physical downlink shared channel transmission can be transmitted; and determines whether a second acknowledgment corresponding to the second physical downlink shared channel transmission can be transmitted; and, in response to determining that the first acknowledgement cannot be transmitted and that the second acknowledgement can be transmitted, decodes the second physical downlink shared channel and not decoding the first physical downlink shared channel.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0007] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for overlapping physical downlink shared channel transmissions;

[0008] Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for overlapping physical downlink shared channel transmissions;

[0009] Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for overlapping physical downlink shared channel transmissions;

[0010] Figure 4 is a schematic block diagram illustrating one embodiment of a fixed frame period structure;

[0011] Figure 5 is a schematic block diagram illustrating one embodiment of a system having overlapping transmissions;

[0012] Figure 6 is a schematic block diagram illustrating another embodiment of a system having overlapping transmissions;

[0013] Figure 7 is a schematic block diagram illustrating a further embodiment of a system having overlapping transmissions; [0014] Figure 8 is a schematic block diagram illustrating yet another embodiment of a system having overlapping transmissions;

[0015] Figure 9 is a schematic block diagram illustrating yet a further embodiment of a system having overlapping transmissions;

[0016] Figure 10 is a schematic block diagram illustrating another embodiment of a system having overlapping transmissions;

[0017] Figure 11 is a schematic block diagram illustrating a further embodiment of a system having overlapping transmissions;

[0018] Figure 12 is a schematic block diagram illustrating yet another embodiment of a system having overlapping transmissions;

[0019] Figure 13 is a schematic block diagram illustrating yet a further embodiment of a system having overlapping transmissions;

[0020] Figure 14 is a schematic block diagram illustrating another embodiment of a system having overlapping transmissions; and

[0021] Figure 15 is a flow chart diagram illustrating one embodiment of a method for overlapping physical downlink shared channel transmissions.

DETAILED DESCRIPTION

[0022] As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

[0023] Certain of the functional units described in this specification may be labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like. [0024] Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

[0025] Indeed, a module of code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.

[0026] Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0027] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0028] Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”) or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0029] Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.

[0030] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.

[0031] Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. The code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the fimctions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks. [0032] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

[0033] The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0034] The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).

[0035] It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.

[0036] Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code. [0037] The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

[0038] Figure 1 depicts an embodiment of a wireless communication system 100 for overlapping physical downlink shared channel transmissions. In one embodiment, the wireless communication system 100 includes remote units 102 and network units 104. Even though a specific number of remote units 102 and network units 104 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0039] In one embodiment, the remote units 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), aerial vehicles, drones, or the like. In some embodiments, the remote units 102 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device, or by other terminology used in the art. The remote units 102 may communicate directly with one or more of the network units 104 via UL communication signals. In certain embodiments, the remote units 102 may communicate directly with other remote units 102 via sidelink communication.

[0040] The network units 104 may be distributed over a geographic region. In certain embodiments, a network unit 104 may also be referred to and/or may include one or more of an access point, an access terminal, a base, a base station, a location server, a core network (“CN”), a radio network entity, a Node-B, an evolved node-B (“eNB”), a 5G node-B (“gNB”), a Home Node-B, a relay node, a device, a core network, an aerial server, a radio access node, an access point (“AP”), new radio (“NR”), a network entity, an access and mobility management function (“AMF”), a unified data management (“UDM”), a unified data repository (“UDR”), a UDM/UDR, a policy control function (“PCF”), a radio access network (“RAN”), a network slice selection function (“NSSF”), an operations, administration, and management (“OAM”), a session management function (“SMF”), a user plane function (“UPF”), an application function, an authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non- 3GPP gateway function (“TNGF”), or by any other terminology used in the art. The network units 104 are generally part of a radio access network that includes one or more controllers communicably coupled to one or more corresponding network units 104. The radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.

[0041] In one implementation, the wireless communication system 100 is compliant with NR protocols standardized in third generation partnership project (“3GPP”), wherein the network unit 104 transmits using an OFDM modulation scheme on the downlink (“DL”) and the remote units 102 transmit on the uplink (“UL”) using a single-carrier frequency division multiple access (“SC-FDMA”) scheme or an orthogonal frequency division multiplexing (“OFDM”) scheme. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocol, for example, WiMAX, institute of electrical and electronics engineers (“IEEE”) 802.11 variants, global system for mobile communications (“GSM”), general packet radio service (“GPRS”), universal mobile telecommunications system (“UMTS”), long term evolution (“LTE”) variants, code division multiple access 2000 (“CDMA2000”), Bluetooth®, ZigBee, Sigfoxx, among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0042] The network units 104 may serve a number of remote units 102 within a serving area, for example, a cell or a cell sector via a wireless communication link. The network units 104 transmit DL communication signals to serve the remote units 102 in the time, frequency, and/or spatial domain.

[0043] In various embodiments, a remote unit 102 may determine whether a first physical downlink shared channel transmission associated with a first semi-persistent scheduling configuration overlaps with a second physical downlink shared channel transmission associated with a second semi-persistent scheduling configuration. The first semi-persistent scheduling configuration has a lower semi-persistent scheduling configuration index than the second semi- persistent scheduling configuration. In some embodiments, the remote unit 102 may, in response to determining that the first physical downlink shared channel transmission overlaps with the second physical downlink shared channel transmission: determine whether a first acknowledgment corresponding to the first physical downlink shared channel transmission can be transmitted; and determine whether a second acknowledgment corresponding to the second physical downlink shared channel transmission can be transmitted. In certain embodiments, the remote unit 102 may, in response to determining that the first acknowledgement cannot be transmitted and that the second acknowledgement can be transmitted, decode the second physical downlink shared channel and not decoding the first physical downlink shared channel. Accordingly, the remote unit 102 may be used for overlapping physical downlink shared channel transmissions.

[0044] Figure 2 depicts one embodiment of an apparatus 200 that may be used for overlapping physical downlink shared channel transmissions. The apparatus 200 includes one embodiment of the remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit 102 may not include any input device 206 and/or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and/or the display 208.

[0045] The processor 202, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 202 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

[0046] The memory 204, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 204 includes volatile computer storage media. For example, the memory 204 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 204 includes non-volatile computer storage media. For example, the memory 204 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, the memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit 102.

[0047] The input device 206, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 206 may be integrated with the display 208, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 206 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 206 includes two or more different devices, such as a keyboard and a touch panel.

[0048] The display 208, in one embodiment, may include any known electronically controllable display or display device. The display 208 may be designed to output visual, audible, and/or haptic signals. In some embodiments, the display 208 includes an electronic display capable of outputting visual data to a user. For example, the display 208 may include, but is not limited to, a liquid crystal display (“LCD”), a light emitting diode (“LED”) display, an organic light emitting diode (“OLED”) display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the display 208 may include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like. Further, the display 208 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0049] In certain embodiments, the display 208 includes one or more speakers for producing sound. For example, the display 208 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the display 208 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the display 208 may be integrated with the input device 206. For example, the input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, the display 208 may be located near the input device 206.

[0050] In certain embodiments, the processor 202: determines whether a first physical downlink shared channel transmission associated with a first semi-persistent scheduling configuration overlaps with a second physical downlink shared channel transmission associated with a second semi-persistent scheduling configuration, wherein the first semi-persistent scheduling configuration has a lower semi-persistent scheduling configuration index than the second semi-persistent scheduling configuration; in response to determining that the first physical downlink shared channel transmission overlaps with the second physical downlink shared channel transmission: determines whether a first acknowledgment corresponding to the first physical downlink shared channel transmission can be transmitted; and determines whether a second acknowledgment corresponding to the second physical downlink shared channel transmission can be transmitted; and, in response to determining that the first acknowledgement cannot be transmitted and that the second acknowledgement can be transmitted, decodes the second physical downlink shared channel and not decoding the first physical downlink shared channel. [0051] Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and the receiver 212 may be any suitable type of transmitters and receivers. In one embodiment, the transmitter 210 and the receiver 212 may be part of a transceiver.

[0052] Figure 3 depicts one embodiment of an apparatus 300 that may be used for overlapping physical downlink shared channel transmissions. The apparatus 300 includes one embodiment of the network unit 104. Furthermore, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As may be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

[0053] In certain embodiments, a user equipment (“UE”) capable of decoding “x” unicast physical downlink shared channel (“PDSCH”) transmissions in a slot (e.g., ‘x’ may take values from {1,2, 4, 7}), may receive up to “x” unicast PDSCH transmissions without corresponding physical downlink control channel (“PDCCH”) transmissions within the slot. In some embodiments, a UE may have up to 8 active downlink (“DL”) semi-persistent scheduling (“SPS”) configurations in a bandwidth part (“BWP”) of a serving cell. In various embodiments, if there are more than one PDSCH transmissions on a serving cell each without a corresponding PDCCH transmission in a slot, the UE may determine which PDSCHs to receive and/or decode. In such embodiments, the UE starts decoding SPS PDSCHs starting from the lowest SPS configuration index in order of increasing SPS configuration index, skipping SPS PDSCHs that overlap with the PDSCH being decoded (e.g., PDSCHs overlapping with the lowest configured PDSCH are skipped).

[0054] In some embodiments, for operation in an unlicensed spectrum, if semi-static channel access is used (e.g., operation according to frame-based equipment (“FBE”)), downlink and uplink transmissions may be allowed within a frame period (“FP”) that the gNB has acquired (e.g., via channel sensing techniques).

[0055] In various embodiments, if there are several SPS PDSCH transmissions, if a PUCCH resource is not available for some of the overlapped SPS PDSCHs (e.g., if the SPS PDSCHs transmissions overlap close to the boundary of a fixed frame period (“FFP”)), SPS PDSCH transmissions to decode may be determined. In such embodiments, for handling overlapping SPS PDSCH transmissions, a user equipment may decode the SPS PDSCH transmissions with the lowest SPS configuration index among the overlapping SPS PDSCHs. In one example, a UE receives and/or decodes a PDSCH transmission with a lowest configuration index for which the UE can send the acknowledgment in the same FFP among a set of overlapping PDSCH transmissions associated with different SPS configuration indices. In certain embodiments, (e.g., in licensed band operation - forwhich channel sensing is not performed and/or required) some PUCCH resources of a subset of overlapped SPS PDSCH transmissions may not be available.

[0056] In some embodiments, if more than one PDSCH transmission on a serving cell, each without a corresponding PDCCH transmission, are in a slot, after resolving that there is overlapping with symbols in a slot indicated as uplink by tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated, a UE receives one or more PDSCHs without corresponding PDCCH transmissions in the slot according to the following steps.

[0057] In a first step (e.g., step 0): set j=0, where j is the number of selected PDSCH transmissions for decoding. Q is a set of activated PDSCH transmissions without corresponding PDCCH transmissions within the slot.

[0058] In a second step (e.g., step 1): a UE receives one PDSCH transmission with a lowest configured sps-Configlndex within Q, set j=j+l . Designate the received PDSCH transmission as a survivor PDSCH transmission.

[0059] In a third step (e.g., step 2): the survivor PDSCH in step 1 and any other PDSCH transmissions overlapping (even partially) with the survivor PDSCH in step 1, are excluded from

Q

[0060] In a fourth step (e.g., step 3): repeat step 1 and 2 until Q is empty or j is equal to the number of unicast PDSCH transmissions in a slot supported by the UE.

[0061] In various embodiments, a UE is not expected to decode a PDSCH transmission in a serving cell scheduled by a PDCCH with cell (“C”) radio network temporary identifier (“RNTI”) (“C-RNTI”), configured scheduling (“CS”) RNTI (“CS-RNTI”), or modulation and coding scheme (“MCS”) C RNTI (“MCS-C-RNTI”), and one or more PDSCH transmissions required to be received in the same serving cell without a corresponding PDCCH transmission if the PDSCH transmissions partially or fully overlap in time except if the PDCCH transmission scheduling the PDSCH transmission ends at least 14 symbols before the earliest starting symbol of the PDSCH transmissions without the corresponding PDCCH transmission, in which case the UE shall decode the PDSCH transmission scheduled by the PDCCH transmission.

[0062] In certain embodiments, a UE multiplexes uplink control information (“UCI”) with the same priority index in a PUCCH transmission or a physical uplink shared channel (“PUSCH”) transmission. In such embodiments, a PUCCH transmission or a PUSCH transmission may be assumed to have a same priority index as a priority index of UCI a UE multiplexes in the PUCCH transmission or the PUSCH transmission.

[0063] In some embodiments, devices and/or network nodes, such as gNBs, operating in an unlicensed spectrum may be required to perform listen before talk (“LBT”) (e.g., channel sensing) prior to being able to transmit in the unlicensed spectrum. In such embodiments, if the device and/or network node performing LBT does not detect the presence of other signals in the channel, the medium and/or channel may not be considered for transmission. In a FBE mode of operation, a device and/or network node performs LBT in an idle period and, once the channel and/or medium is acquired, the device and/or network node may communicate within the non-idle time of a fixed frame period duration (e.g., channel occupancy time (“COT”)). In various embodiments, an idle time may not be shorter than a maximum of 5% of a FFP and 100 micro seconds.

[0064] Figure 4 is a schematic block diagram illustrating one embodiment of a fixed frame period structure 400. The fixed frame period structure includes a COT 402, an idle time 404, a COT 406, and an idle time 408. A fixed frame period 410 includes the COT 402 and the idle time 404.

[0065] In certain embodiments, which SPS PDSCH transmission to be decoded among overlapping SPS PDSCH transmissions may be determined.

[0066] In some embodiments, if two or more SPS PDSCH transmissions (e.g., 1st SPS PDSCH transmission with a first SPS configuration index and a 2nd SPS PDSCH transmission with a second SPS configuration index, wherein the first SPS configuration index is smaller than the second SPS configuration index) overlap (e.g., in time domain, in frequency domain, in combination of time and frequency domains, or in another domain such as code domain or spatial domain), the SPS PDSCH transmission among the overlapped SPS PDSCH transmissions may be decoded which has one or more of the following conditions, and the UE may skip the other SPS

PDSCH transmissions.

[0067] In such embodiments, a corresponding hybrid automatic repeat request (“HARQ”) acknowledgement (“ACK”) (“HARQ-ACK”) may be sent in its associated PUCCH resource, and the HARQ-ACK corresponding to the other SPS PDSCH transmission cannot be sent (e.g., the PUCCH resource for the HARQ-ACK is not available).

[0068] In one condition, a UE may decode (or receive) a 2nd SPS PDSCH transmission if its associated PUCCH transmission (e.g., 2nd PUCCH transmission) is available for transmission and may not decode or skips (e.g., exclude from receiving) a 1st SPS PDSCH transmission overlapping (even partially) with the 2nd SPS PDSCH transmission if the PUCCH transmission associated with the 1st SPS PDSCH transmission (e.g., 1st PUCCH transmission) is not available (e.g., cannot be transmitted).

[0069] In one embodiment, a 1st PUCCH transmission is not available due to a 1st PUCCH transmission being cancelled (e.g., if a UE determines to cancel the 1st PUCCH transmission at an earlier time with respect to a 1st SPS PDSCH transmission and/or a 2nd SPS PDSCH transmission, with respect to a first symbol and/or last symbol of the 1 st SPS PDSCH transmission and/or the 2nd SPS PDSCH transmission, at least Ύ’ symbols before the last symbol of the 1st SPS PDSCH transmission that ends earlier than the other overlapped 2nd SPS PDSCH transmission ).

[0070] In various embodiments, a 1st PUCCH transmission has a smaller priority index than another uplink (“UL”) transmission that overlaps with the 1st PUCCH transmission and, therefore, the first PUCCH transmission is cancelled.

[0071] Figure 5 is a schematic block diagram illustrating one embodiment of a system 500 having overlapping transmissions. The system 500 includes a 1st SPS PDSCH 502 with a corresponding 1st PUCCH 504, a 2nd SPS PDSCH 506 with a corresponding 2nd PUCCH 508, and a high priority (“HP”) PUSCH 510. The 1st PUCCH 504 is cancelled due to an overlap with the HP PUSCH 510. A UE would decode the 2nd SPS PDSCH 506 instead of the 1st SPS PDSCH 502, and skip decoding the 1st SPS PDSCH 502.

[0072] In a related example to the example shown in Figure 5, a UE decodes a 2nd SPS PDSCH and skips decoding a 1st SPS PDSCH if downlink control information (“DCI”) scheduling a HP UL transmission (e.g., HP PUSCH shown in Figure 6 and Figure 7) is received some time before the SPS PDSCH decoding (e.g., the DCI scheduling the HP PUSCH is received at least “Y” symbols before the end of the 1st SPS PDSCH as shown in Figure 6, the DCI scheduling the HP PUSCH is received at least “Y” symbols before the start of the 1st SPS PDSCH as shown in Figure 7, or the DCI scheduling the HP PUSCH is received at least ‘Ύ” symbols before the start and/or end of the earliest SPS PDSCH (e.g., among the 1st SPS PDSCH and the 2nd SPS PDSCH). In one example: 1) ‘Ύ” may be a value reported by the UE as capability signaling; 2) ‘Ύ” may be a configured value; 3) “Y” may be signaled in DCI such as an activation DCI corresponding to the 1st SPS configuration or the 2nd SPS configuration; or 4) ‘Ύ” may be related to a UE processing time (e.g., such as UE PDSCH processing procedure time with some parameters of Tproc, 1 defined to take same or different values, for instance, d 1 , 1 for Tproc, 1 calculation may be set according to UE capability signaling).

[0073] Figure 6 is a schematic block diagram illustrating another embodiment of a system 600 having overlapping transmissions. The system 600 is illustrated over a time 602 and includes DCI 604 with a corresponding HP PUSCH 606, a 1st SPS PDSCH 608 with a corresponding 1st PUCCH 610, and a 2nd SPS PDSCH 612 with a corresponding 2nd PUCCH 614. The end of the 1st SPS PDSCH 608 occurs Y symbols 616 after the DCI 604. The 1st PUCCH 610 is cancelled due to its overlap with the HP PUSCH 606. The UE may decode the 2nd SPS PDSCH 612 instead of the 1st SPS PDSCH 608 if the UE is aware of cancellation of the 1st PUCCH 610 at least Y symbols 616 before the end of the 1st SPS PDSCH 608.

[0074] Figure 7 is a schematic block diagram illustrating a further embodiment of a system 700 having overlapping transmissions. The system 700 includes DCI 702 with a corresponding HP PUSCH 704, a 1st SPS PDSCH 706 with a corresponding 1st PUCCH 708, and a 2nd SPS PDSCH 712 with a corresponding 2nd PUCCH 714. The start of the 1st SPS PDSCH 706 occurs

Y symbols 716 after the DCI 702. The 1st PUCCH 708 is cancelled due to overlap with the HP PUSCH 704. The UE may decode the 2nd SPS PDSCH 712 instead of the 1st SPS PDSCH 706 if the UE is aware of cancelation of the 1st PUCCH 708 at least Y symbols 716 before the start of the 1st SPS PDSCH 712. [0075] In various embodiments, a 1st PUCCH transmission overlaps with a DL symbol and/or DL transmission, and hence the 1st PUCCH transmission is canceled.

[0076] Figure 8 is a schematic block diagram illustrating yet another embodiment of a system 800 having overlapping transmissions. The system 800 includes DCI 802 with a corresponding DL transmission 804, a 1st SPS PDSCH 806 with a corresponding 1st PUCCH 808, and a 2nd SPS PDSCH 812 with a corresponding 2nd PUCCH 814. The endofthe IstSPS PDSCH

806 occurs Y symbols 816 after the DCI 802. The 1st PUCCH 808 is cancelled due to overlap with a DL symbol and/or DL transmission 804. The UE may decode the 2nd SPS PDSCH 812 instead ofthe 1st SPS PDSCH 806 if the UE is aware of cancelation ofthe 1st PUCCH 808 at least

Y symbols 816 before the end of the 1st SPS PDSCH 806. [0077] Figure 9 is a schematic block diagram illustrating yet a further embodiment of a system 900 having overlapping transmissions. The system 900 includes DCI 902 with a corresponding DL transmission 904, a 1st SPS PDSCH 906 with a corresponding 1st PUCCH 908, and a 2nd SPS PDSCH 912 with a corresponding 2nd PUCCH 914. The beginning of the 1st SPS PDSCH 906 occurs Y symbols 916 after the DCI 902. The 1st PUCCH 908 is cancelled due to overlap with a DL symbol and/or DL transmission 904. The UE may decode the 2nd SPS PDSCH

912 instead of the 1st SPS PDSCH 906 if the UE is aware of cancelation of the 1st PUCCH 908 at least Y symbols 916 before the start of the 1st SPS PDSCH 906.

[0078] In certain embodiments, a 1st PUCCH transmission is outside of a channel occupancy (or lies within the idle part of an FFP wherein no transmission is allowed, or is in a different FFP period than the FFP of the associated PDSCH) in an unlicensed spectrum. In one example, the 1st PUCCH transmission is outside of (e.g., in a non-idle part) gNB acquired COT (e.g., the activation DCI corresponding to the first SPS PDSCH indicates a ‘KG value, wherein a PUCCH for an associated SPS PDSCH occasion is sent after ‘KG slots and/or sub-slots after the end of the associated SPS PDSCH occasion).

[0079] In some embodiments, if a 1st PUCCH transmission is outside of a same channel occupancy (“CO”) as the CO of its associated SPS PDSCH transmission, and if the UE is not configured to transmit the HARQ-ACK corresponding to the 1 st SPS PDSCH transmission outside the same CO as that of the 1st SPS PDSCH (e.g., the UE may be configured to provide the HARQ- ACK in a later acquired COT, in such a case, the UE would decode the 1st SPS PDSCH).

[0080] Figure 10 is a schematic block diagram illustrating another embodiment of a system 1000 having overlapping transmissions. The system 1000 includes a non-idle time of channel occupancy 1002 (e.g., CO 1004), a 1st SPS PDSCH 1006 with a corresponding 1st PUCCH 1008, and a 2nd SPS PDSCH 1010 with a corresponding 2nd PUCCH 1012. The UE may decode the 2nd SPS PDSCH 1010 instead of the 1st SPS PDSCH 1006 if the 1st PUCCH 1008 is outside of the CO 1004.

[0081] In various embodiments, a gNB may set an SPS configuration of a lowest SPS configuration index (e.g., among overlapping SPS PDSCHs) with a HARQ-ACK codebook index (e.g., harq-CodebookID) associated with a higher priority PUCCH (e.g., priority index 1), to avoid potentially dropping of HARQ-ACK transmission. In one example, the 1st PUCCH is configured as a high priority PUCCH and, accordingly, HARQ-ACK information of the 1st SPS PDSCH is multiplexed into the high priority PUSCH. In such an example, the UE may decode (or receive) the 1st SPS PDSCH associated with high priority PUCCH (e.g., 1st PUCCH) and not decode or skips (e.g., exclude from receiving) the 2nd SPS PDSCH overlapping (e.g., even partially) with the 1st SPS PDSCH.

[0082] In some embodiments, a gNB may not always guarantee an SPS configuration of a lowest SPS configuration index among overlapping SPS PDSCHs to have the HARQ-ACK codebook index (e.g., harq-CodebookID) associated with a higher priority PUCCH. In one embodiment, if overlapping SPS PDSCHs have different HARQ-ACK codebook indices associated with different PUCCH priorities, a UE decodes a SPS PDSCH of a HARQ-ACK codebook index associated with a higher PUCCH priority. In another embodiment, if overlapping SPS PDSCHs have different HARQ-ACK codebook indices associated with different PUCCH priorities, a UE decodes a SPS PDSCH with a lowest SPS configuration index among a subset of overlapping SPS PDSCHs with a HARQ-ACK codebook index associated with a higher PUCCH priority. In various embodiments, a UE decodes an SPS PDSCH with a lowest SPS configuration index among a subset of overlapping SPS PDSCHs, where HARQ-ACK information of each SPS PDSCH of the subset of overlapping SPS PDSCHs may be transmitted in an indicated PUCCH resource or may be multiplexed in another PUCCH or a PUSCH that satisfies multiplexing timeline conditions.

[0083] In certain embodiments, if a first SPS PDSCH is indicated (e.g., via RRC or via activation DCI) to have multiple repetitions associated with an SPS occasion (e.g., bundle of repetitions in each SPS period) and if the last repetition overlaps with the second SPS PDSCH, a UE may provide the HARQ-ACK for the first SPS PDSCH in a PUCCH associated with and/or determined from the one before the last SPS PDSCH repetition.

[0084] In some embodiments, the 1st SPS PDSCH has several repetitions in an SPS occasion, and already has received and/or expects to receive at least ‘nf SPS PDSCH receptions (e.g., repetitions), a UE would decode the 2nd SPS PDSCH if there is an overlap with one or more repetitions of the 1st SPS PDSCH.

[0085] In various embodiments, if more than one PDSCH on a serving cell (e.g., each without a corresponding PDCCH transmission) are in a slot, after resolving an overlap with symbols in the slot indicated as uplink by tdd-UL-DL-ConfigurationCommon, or by tdd-UL-DL- ConfigurationDedicated, a UE receives one or more PDSCHs without corresponding PDCCH transmissions in the slot.

[0086] One embodiment includes the following steps. In a first step (e.g., step 0), set j=0, where j is the number of selected PDSCH transmissions for decoding. Q is a set of activated PDSCH transmissions without corresponding PDCCH transmissions within the slot.

[0087] In a second step (e.g., step 1): a UE receives one PDSCH transmission with a lowest configured sps-Configlndex within Q, for which its corresponding HARQ-ACK can be sent in the same channel occupancy as the channel occupancy of the PDSCH transmission, set j=j+l. The received PDSCH transmission is designated as a survivor PDSCH transmission.

[0088] In a third step (e.g., step 2): the survivor PDSCH transmission in step 1 and any other PDSCH transmissions overlapping (e.g., even partially) with the survivor PDSCH transmission in step 1 are excluded from Q.

[0089] In a fourth step (e.g., step 3): repeat step 1 and 2 until Q is empty or j is equal to the number of unicast PDSCH transmissions in a slot supported by the UE.

[0090] Another embodiment includes the following first step (e.g., step 1): a UE receives one PDSCH transmission with the lowest configured sps-Configlndex within Q, if not indicated by radio resource control (“RRC”) and/or activation DCI, otherwise the UE receives one PDSCH transmission with the lowest configured sps-Configlndex within Q for which its corresponding HARQ-ACK can be sent in the same channel occupancy as the channel occupancy of the received PDSCH transmission if indicated by the RRC and/or activation DCI; set j=j+l. The received PDSCH transmission is designated as a survivor PDSCH transmission.

[0091] Certain embodiments include the following second step (e.g., step 1): a UE receives one PDSCH transmission with the lowest configured sps-Configlndex within Q for which its corresponding HARQ-ACK can be sent in the same channel occupancy as the channel occupancy of the PDSCH and its corresponding HARQ-ACK can be sent in a PUCCH resource that contains the most number of HARQ-ACK bits in a time duration (or a PUCCH resource having more than ‘y’ HARQ-ACK bits if available, or associated with a PUCCH resource of SPS-PUCCH-AN- ResourcelD with the highest ID, or the lowest SPS configuration index with the HARQ-ACK codebook of the high priority or HARQ-ACK codebook associated a higher priority PUCCH), set j=j+l. The received PDSCH transmission is designated as a survivor PDSCH transmission.

[0092] In some embodiments, a UE is not expected to receive an SPS PDSCH transmission for which the corresponding PUCCH transmission is not available (e.g., for operation in licensed spectrum, due to overlap with semi-static DL symbols) or lies outside of the FFP of the associated SPS PDSCH transmission. In such embodiments, the UE does not perform SPS PDSCH transmission overlap handling between the two overlapped SPS PDSCH transmissions.

[0093] In various embodiments, a 2nd SPS PDSCH transmission is decoded if the 2nd PUCCH transmission is the last PUCCH transmission, within a non-idle part of the FFP of the SPS PDSCH, associated with the 2nd SPS configuration. In one example, a 2nd SPS PDSCH is decoded if the HARQ-ACK associated with the 2nd SPS PDSCH transmission has only one chance and/or possibility to be conveyed within the non-idle part of the FFP of the SPS PDSCH, associated with the 2nd SPS configuration. In one example, there are still PUCCH resources corresponding to the SPS PDSCH transmissions associated with the 1st SPS configuration within the non-idle part of the FFP as shown in Figure 11.

[0094] Figure 11 is a schematic block diagram illustrating a further embodiment of a system 1100 having overlapping transmissions. The system 1100 includes a non-idle time of channel occupancy 1102 (e.g., CO 1104), a 1st SPS PDSCH occasion ‘n’ 1106 with a corresponding 1st SPS PUCCH occasion ‘n’ 1108, a 1st SPS PDSCH occasion ‘n+U 1110 with a corresponding 1st SPS PUCCH occasion ‘n+U 1112, a 2nd SPS PDSCH occasion ‘k’ 1114 with a corresponding 2nd SPS PUCCH occasion ‘k’ 1116, and a 2nd SPS PDSCH occasion ‘k+U 1118 with a corresponding 2nd SPS PUCCH occasion ‘k+U 1120. Upon overlap between 1st SPS PDSCH occasion ‘n’ 1106 and 2nd SPS PDSCH occasion ‘k’ 1114, the UE decodes 2nd SPS PDSCH at occasion ‘k’ 1114 and skips decoding and/or does not receive 1st SPS PDSCH occasion ‘n’ 1106.

[0095] In certain embodiments, a 2nd SPS PDSCH transmission is decoded if the 2nd SPS PDSCH transmission is transmitted and/or received in a last SPS occasion of the 2nd SPS configuration within the non-idle duration of the current FFP, and the 1st SPS PDSCH transmission is not decoded if the 1st SPS PDSCH transmission is not transmitted and/or received in the last SPS occasion of the 1st SPS configuration within the non-idle duration of the current FFP.

[0096] Figure 12 is a schematic block diagram illustrating yet another embodiment of a system 1200 having overlapping transmissions. The system 1200 includes a non-idle time of channel occupancy 1202 (e.g., CO 1204), a 1st SPS PDSCH occasion ‘n’ 1206 with a corresponding 1st SPS PUCCH occasion ‘n’ 1208, a 1st SPS PDSCH occasion ‘h+G 1210 with a corresponding 1st SPS PUCCH occasion ‘h+G 1212, a 2nd SPS PDSCH occasion ‘k’ 1214 with a corresponding 2nd SPS PUCCH occasion ‘k’ 1216, and a 2nd SPS PDSCH occasion ‘k+U 1218. Upon overlap between 1st SPS PDSCH occasion ‘n’ 1206 and 2nd SPS PDSCH occasion ‘k’ 1214, the UE decodes 2nd SPS PDSCH occasion ‘k’ 1214 and skips decoding and/or does not receive 1st SPS PDSCH occasion ‘n’ 1206.

[0097] In various embodiments, a UE is not expected to decode a PDSCH transmission in a serving cell scheduled by a PDCCH transmission with C-RNTI, CS-RNTI or MCS-C-RNTI and one or more PDSCH transmissions required to be received in the same serving cell without a corresponding PDCCH transmission if the PDSCH transmissions partially or fully overlap in time except if the PDCCH transmission scheduling the PDSCH transmission ends at least 14 symbols before the earliest starting symbol of the PDSCH transmissions without the corresponding PDCCH transmission, in which case the UE may decode the PDSCH transmission scheduled by the PDCCH transmission.

[0098] Figure 13 is a schematic block diagram illustrating yet a further embodiment of a system 1300 having overlapping transmissions. The system 1300 includes DCI 1302 with a corresponding dynamic PDSCH transmission 1304, a 1st SPS PDSCH 1306, and a 2nd SPS PDSCH 1310. The start of the 1st SPS PDSCH 1306 occurs Y symbols 1308 (e.g., at least 14 symbols) after the DCI 1302. As used throughout, Y symbols may refer to 14 symbols. The dynamic PDSCH transmission 1304 is decoded if the DCI 1302 scheduling the dynamic PDSCH transmission 1304 is received at least 14 symbols prior to the first symbol of the earliest SPS PDSCH overlapping with the scheduled dynamic PDSCH transmission 1304. [0099] In certain embodiments, if a 1st SPS PDSCH transmission overlaps with a 2nd SPS PDSCH transmission, and the UE determines to decode only the 2nd SPS PDSCH transmission, the 14-symbol requirement (e.g., DCI needs to be received 14 symbols prior to the earliest SPS PDSCH symbol) is applied to the 2nd SPS PDSCH transmission. [0100] Figure 14 is a schematic block diagram illustrating another embodiment of a system

1400 having overlapping transmissions. The system 1400 includes DCI 1402 with a corresponding dynamic PDSCH transmission 1404, a 1st SPS PDSCH 1406, and a 2nd SPS PDSCH 1408. The start of the 1st SPS PDSCH 1406 occurs X symbols 1410 (e.g., less than 14 symbols) after the DCI 1402. Moreover, the start of the 2nd SPS PDSCH 1408 occurs Y symbols 1412 (e.g., at least 14 symbols) after the DCI 1402. The dynamic PDSCH transmission 1404 is decoded if the DCI

1402 scheduling the dynamic PDSCH transmission 1404 is received at least 14 symbols prior to the first symbol of the SPS PDSCH overlapping with the scheduled dynamic PDSCH, wherein the SPS PDSCH is determined after resolving overlap amongst the overlapped SPS PDSCHs (i.e., 2nd SPS PDSCH 1408). [0101] In some embodiments, a UE is not expected to decode a PDSCH transmission in a serving cell scheduled by a PDCCH transmission with C-RNTT, CS-RNTI or MCS-C-RNTI and one or more PDSCH transmissions required to be received in the same serving cell without a corresponding PDCCH transmission if the PDSCH transmissions partially or fully overlap in time except if the PDCCH scheduling the PDSCH transmission ends at least 14 symbols before the earliest starting symbol of the PDSCH transmissions without the corresponding PDCCH transmission after resolving overlapping SPS PDSCH transmissions, in which case the UE may decode the PDSCH scheduled by the PDCCH transmission.

[0102] It should be noted that embodiments herein may be applicable to DL, UL, or sidelink transmissions according to a configured grant. [0103] Figure 15 is a flow chart diagram illustrating one embodiment of a method 1500 for overlapping physical downlink shared channel transmissions. In some embodiments, the method 1500 is performed by an apparatus, such as the remote unit 102. In certain embodiments, the method 1500 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0104] In various embodiments, the method 1500 includes determining 1502 whether a first physical downlink shared channel transmission associated with a first semi-persistent scheduling configuration overlaps with a second physical downlink shared channel transmission associated with a second semi-persistent scheduling configuration. The first semi-persistent scheduling configuration has a lower semi-persistent scheduling configuration index than the second semi -persistent scheduling configuration. In some embodiments, the method 1500 includes, in response to determining that the first physical downlink shared channel transmission overlaps with the second physical downlink shared channel transmission: determining 1504 whether a first acknowledgment corresponding to the first physical downlink shared channel transmission can be transmitted; and determining whether a second acknowledgment corresponding to the second physical downlink shared channel transmission can be transmitted. In certain embodiments, the method 1500 includes, in response to determining that the first acknowledgement cannot be transmitted and that the second acknowledgement can be transmitted, decoding 1506 the second physical downlink shared channel and not decoding the first physical downlink shared channel.

[0105] In certain embodiments, the second acknowledgment is sent in an uplink transmission and the first acknowledgment is not generated. In one embodiment, the second semi- persistent scheduling configuration has a hybrid automatic repeat request codebook index associated with a higher physical uplink control channel priority than the first semi-persistent scheduling configuration. In some embodiments, determining that the first acknowledgement cannot be transmitted further comprises determining, based on downlink control information scheduling a transmission, that the transmission overlaps with a physical uplink control channel resource associated with the first physical downlink shared channel, and the downlink control information is received at least a predetermined time prior to a start of the first physical downlink shared channel transmission. In various embodiments, the predetermined time comprises a predetermined number of symbols.

[0106] In one embodiment, the transmission comprises a downlink transmission, an uplink transmission, or a sidelink communication. In certain embodiments, the transmission comprises a downlink transmission, and the method further comprises decoding the downlink transmission in response to the downlink control information being received at least fourteen symbols prior to a start of the second physical downlink shared channel transmission, and wherein the downlink control information is received less than fourteen symbols prior to the start of the first physical downlink shared channel transmission. In some embodiments, determining that the first acknowledgement cannot be transmitted further comprises determining, based on downlink control information scheduling a transmission, that the transmission overlaps with a physical uplink control channel resource associated with the first physical downlink shared channel, and the downlink control information is received at least a predetermined time prior to an end of the first physical downlink shared channel transmission. [0107] In various embodiments, determining that the first acknowledgement cannot be transmitted further comprises determining that the first acknowledgement cannot be transmitted based on a boundary of a channel occupancy time. In one embodiment, determining that the first acknowledgement cannot be transmitted further comprises determining that the first acknowledgement cannot be transmitted based on a semi-persistent scheduling occasion index, a number of semi-persistent scheduling occasions of a semi-persistent scheduling configuration left before an end of a channel occupancy time, a number of physical uplink control channel resources associated with the semi-persistent scheduling configuration left before the end of the channel occupancy time, or some combination thereof. [0108] In certain embodiments, the first physical downlink shared channel transmission and the second physical downlink shared channel transmission are on a serving cell and each of the first physical downlink shared channel transmission and the second physical downlink shared channel transmission have a corresponding physical downlink control channel transmission in a slot. In some embodiments, prior to determining whether the first physical downlink shared channel transmission overlaps with the second physical downlink shared channel transmission, the method further comprises resolving overlapping with symbols in a slot indicated as uplink.

[0109] In one embodiment, a method comprises: determining whether a first physical downlink shared channel transmission associated with a first semi-persistent scheduling configuration overlaps with a second physical downlink shared channel transmission associated with a second semi-persistent scheduling configuration, wherein the first semi-persistent scheduling configuration has a lower semi-persistent scheduling configuration index than the second semi-persistent scheduling configuration; in response to determining that the first physical downlink shared channel transmission overlaps with the second physical downlink shared channel transmission: determining whether a first acknowledgment corresponding to the first physical downlink shared channel transmission can be transmitted; and determining whether a second acknowledgment corresponding to the second physical downlink shared channel transmission can be transmitted; and, in response to determining that the first acknowledgement cannot be transmitted and that the second acknowledgement can be transmitted, decoding the second physical downlink shared channel and not decoding the first physical downlink shared channel. [0110] In certain embodiments, the second acknowledgment is sent in an uplink transmission and the first acknowledgment is not generated.

[0111] In one embodiment, the second semi-persistent scheduling configuration has a hybrid automatic repeat request codebook index associated with a higher physical uplink control channel priority than the first semi-persistent scheduling configuration. [0112] In some embodiments, determining that the first acknowledgement cannot be transmitted further comprises determining, based on downlink control information scheduling a transmission, that the transmission overlaps with a physical uplink control channel resource associated with the first physical downlink shared channel, and the downlink control information is received at least a predetermined time prior to a start of the first physical downlink shared channel transmission.

[0113] In various embodiments, the predetermined time comprises a predetermined number of symbols.

[0114] In one embodiment, the transmission comprises a downlink transmission, an uplink transmission, or a sidelink communication.

[0115] In certain embodiments, the transmission comprises a downlink transmission, and the method further comprises decoding the downlink transmission in response to the downlink control information being received at least fourteen symbols prior to a start of the second physical downlink shared channel transmission, and wherein the downlink control information is received less than fourteen symbols prior to the start of the first physical downlink shared channel transmission.

[0116] In some embodiments, determining that the first acknowledgement cannot be transmitted further comprises determining, based on downlink control information scheduling a transmission, that the transmission overlaps with a physical uplink control channel resource associated with the first physical downlink shared channel, and the downlink control information is received at least a predetermined time prior to an end of the first physical downlink shared channel transmission.

[0117] In various embodiments, determining that the first acknowledgement cannot be transmitted further comprises determining that the first acknowledgement cannot be transmitted based on a boundary of a channel occupancy time.

[0118] In one embodiment, determining that the first acknowledgement cannot be transmitted further comprises determining that the first acknowledgement cannot be transmitted based on a semi-persistent scheduling occasion index, a number of semi-persistent scheduling occasions of a semi-persistent scheduling configuration left before an end of a channel occupancy time, a number of physical uplink control channel resources associated with the semi-persistent scheduling configuration left before the end of the channel occupancy time, or some combination thereof.

[0119] In certain embodiments, the first physical downlink shared channel transmission and the second physical downlink shared channel transmission are on a serving cell and each of the first physical downlink shared channel transmission and the second physical downlink shared channel transmission have a corresponding physical downlink control channel transmission in a slot.

[0120] In some embodiments, prior to determining whether the first physical downlink shared channel transmission overlaps with the second physical downlink shared channel transmission, the method further comprises resolving overlapping with symbols in a slot indicated as uplink.

[0121] In one embodiment, an apparatus comprises: a processor that: determines whether a first physical downlink shared channel transmission associated with a first semi-persistent scheduling configuration overlaps with a second physical downlink shared channel transmission associated with a second semi-persistent scheduling configuration, wherein the first semi- persistent scheduling configuration has a lower semi-persistent scheduling configuration index than the second semi-persistent scheduling configuration; in response to determining that the first physical downlink shared channel transmission overlaps with the second physical downlink shared channel transmission: determines whether a first acknowledgment corresponding to the first physical downlink shared channel transmission can be transmitted; and determines whether a second acknowledgment corresponding to the second physical downlink shared channel transmission can be transmitted; and, in response to determining that the first acknowledgement cannot be transmitted and that the second acknowledgement can be transmitted, decodes the second physical downlink shared channel and not decoding the first physical downlink shared channel.

[0122] In certain embodiments, the second acknowledgment is sent in an uplink transmission and the first acknowledgment is not generated.

[0123] In some embodiments, the processor determining that the first acknowledgement cannot be transmitted further comprises the processor determining, based on downlink control information scheduling a transmission, that the transmission overlaps with a physical uplink control channel resource associated with the first physical downlink shared channel, and the downlink control information is received at least a predetermined time prior to a start of the first physical downlink shared channel transmission. [0124] In various embodiments, the predetermined time comprises a predetermined number of symbols.

[0125] In one embodiment, the transmission comprises a downlink transmission, an uplink transmission, or a sidelink communication. [0126] In certain embodiments, the transmission comprises a downlink transmission, the processor decodes the downlink transmission in response to the downlink control information being received at least fourteen symbols prior to a start of the second physical downlink shared channel transmission, and the downlink control information is received less than fourteen symbols prior to the start of the first physical downlink shared channel transmission.

[0127] In some embodiments, the processor determining that the first acknowledgement cannot be transmitted further comprises the processor determining, based on downlink control information scheduling a transmission, that the transmission overlaps with a physical uplink control channel resource associated with the first physical downlink shared channel, and the downlink control information is received at least a predetermined time prior to an end of the first physical downlink shared channel transmission.

[0128] In various embodiments, the processor determining that the first acknowledgement cannot be transmitted further comprises the processor determining that the first acknowledgement cannot be transmitted based on a boundary of a channel occupancy time.

[0129] In one embodiment, the processor determining that the first acknowledgement cannot be transmitted further comprises the processor determining that the first acknowledgement cannot be transmitted based on a semi-persistent scheduling occasion index, a number of semi- persistent scheduling occasions of a semi-persistent scheduling configuration left before an end of a channel occupancy time, a number of physical uplink control channel resources associated with the semi-persistent scheduling configuration left before the end of the channel occupancy time, or some combination thereof.

[0130] In certain embodiments, the first physical downlink shared channel transmission and the second physical downlink shared channel transmission are on a serving cell and each of the first physical downlink shared channel transmission and the second physical downlink shared channel transmission have a corresponding physical downlink control channel transmission in a slot.

[0131] In some embodiments, prior to determining whether the first physical downlink shared channel transmission overlaps with the second physical downlink shared channel transmission, the processor resolves overlapping with symbols in a slot indicated as uplink.

[0132] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.