Patent Description:
<CIT> discloses a method for receiving a physical downlink shared channel (PDSCH) in a wireless communication system. The method performed by a user equipment (UE) comprises receiving, from a base station, a higher layer signal including first information about a configuration of an operation related to a PDSCH repetition, receiving, from the base station, second information related to a number of symbols of a control region, receiving, from the base station, downlink control information (DCI) including information related to a PDSCH repetition number based on the second information, and repeatedly receiving, from the base station, the PDSCH based on the DCI, wherein when the control region is configured with a specific number of symbols, a transmission time unit related to the control region is not included in transmission time units for a PDSCH repetition reception.

<CIT> discloses technology for a user equipment (UE) operable for dynamic downlink (DL) control and data repetition for new radio (NR) ultra-reliable low-latency communication (URLLC). The apparatus can comprise one or more processors configured to: decode a value of a repetition number indicator from downlink control information (DCI); decode information on a physical downlink shared channel (PDSCH) transmission; and decode information on a number of repeated PDSCH transmissions, wherein the number of repeated PDSCH transmissions is equal to the value of the repetition number indicator.

<NPL>) discusses the enhancements on multi-TRP/panel transmission in Rel-<NUM>, including the multi-TRP/panel enhancement for non-coherent joint transmission and multi-TRP enhancement for URLLC.

<CIT> discloses a method for downlink assignments for downlink control channels, including: determining a third set of downlink control channel monitoring occasions that comprises first downlink control channel monitoring occasions and second downlink control channel monitoring occasions, and associated search spaces correspond to two different control resource sets comprising a first control resource set and a second control resource set, wherein: demodulation reference signal ports of the first control resource set are quasi-collocated with a first set of reference signals; demodulation reference signal ports of the second control resource set are quasi-collocated with a second set of reference signals.

<CIT> discloses a method for an uplink data transmission that includes: determining a transmission occasion for an uplink transmission and a Hybrid Automatic Repeat Request, HARQ, process ID corresponding to the transmission occasion; determining an antenna port according to a correspondence between antenna ports and HARQ process IDs and/or a correspondence between antenna ports and transmission occasions; and transmitting, by the antenna port, uplink data corresponding to the HARQ process ID and a pilot signal corresponding to the uplink data.

<CIT> discloses embodiments for time-domain symbol determination and/or indication using a combination of higher layer and downlink control information signaling for physical downlink shared channel and physical uplink shared channel; time domain resource allocations for mini-slot operations; rules for postponing and dropping for multiple mini-slot transmission; and collision handling of sounding reference signals with semi-statically or semi-persistently configured uplink transmissions.

Advantageous, optional features of the invention are then set out in the appended dependent claims. In the following description, any embodiment referred to and not falling within the scope of the claims is merely an example useful to the understanding of the invention.

In one aspect of the disclosure, a method is defined as in claim <NUM>.

In an additional aspect of the disclosure, an apparatus is defined as in claim <NUM>.

In an additional aspect of the disclosure, a non-transitory computer-readable medium is defined as in claim <NUM>.

In an additional aspect of the disclosure, a method is defined as in claim <NUM>.

Other aspects, features, and embodiments will become apparent to those of ordinary skill in the art, upon reviewing the following description of specific, exemplary aspects in conjunction with the accompanying figures. While features may be discussed relative to certain aspects and figures below, all aspects can include one or more of the advantageous features discussed herein. In other words, while one or more aspects may be discussed as having certain advantageous features, one or more of such features may also be used in accordance with the various aspects. In similar fashion, while exemplary aspects may be discussed below as device, system, or method aspects, the exemplary aspects can be implemented in various devices, systems, and methods.

This disclosure relates generally to providing or participating in communication as between two or more wireless devices in one or more wireless communications systems, also referred to as wireless communications networks. In various embodiments, the techniques and apparatus may be used for wireless communication networks such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single-carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, <NUM>th Generation (<NUM>) or new radio (NR) networks (sometimes referred to as "<NUM> NR" networks/systems/devices), as well as other communications networks. As described herein, the terms "networks" and "systems" may be used interchangeably.

A TDMA network may, for example implement a radio technology such as GSM. 3GPP defines standards for the GSM EDGE (enhanced data rates for GSM evolution) radio access network (RAN), also denoted as GERAN. GERAN is the radio component of GSM/EDGE, together with the network that joins the base stations (for example, the Ater and Abis interfaces) and the base station controllers (A interfaces, etc.). The radio access network represents a component of a GSM network, through which phone calls and packet data are routed from and to the public switched telephone network (PSTN) and Internet to and from subscriber handsets, also known as user terminals or user equipments (UEs). A mobile phone operator's network may comprise one or more GERANs, which may be coupled with Universal Terrestrial Radio Access Networks (UTRANs) in the case of a UMTS/GSM network. An operator network may also include one or more LTE networks, and/or one or more other networks. The various different network types may use different radio access technologies (RATs) and radio access networks (RANs).

<NUM> networks contemplate diverse deployments, diverse spectrum, and diverse services and devices that may be implemented using an OFDM-based unified, air interface. To achieve these goals, further enhancements to LTE and LTE-A are considered in addition to development of the new radio technology for <NUM> NR networks. The <NUM> NR will be capable of scaling to provide coverage (<NUM>) to a massive Internet of things (IoTs) with an ultra-high density (e.g., ~<NUM> nodes/km<NUM>), ultra-low complexity (e.g., ~<NUM> of bits/sec), ultra-low energy (e.g., ~<NUM>+ years of battery life), and deep coverage with the capability to reach challenging locations; (<NUM>) including mission-critical control with strong security to safeguard sensitive personal, financial, or classified information, ultra-high reliability (e.g., ~<NUM>% reliability), ultra-low latency (e.g., ~ <NUM>), and users with wide ranges of mobility or lack thereof; and (<NUM>) with enhanced mobile broadband including extreme high capacity (e.g., ~ <NUM> Tbps/km<NUM>), extreme data rates (e.g., multi-Gbps rate, <NUM>+ Mbps user experienced rates), and deep awareness with advanced discovery and optimizations.

<NUM> NR devices, networks, and systems may be implemented to use optimized OFDM-based waveform features. These features may include scalable numerology and transmission time intervals (TTIs); a common, flexible framework to efficiently multiplex services and features with a dynamic, low-latency time division duplex (TDD)/frequency division duplex (FDD) design; and advanced wireless technologies, such as massive multiple input, multiple output (MIMO), robust millimeter wave (mmWave) transmissions, advanced channel coding, and device-centric mobility. Scalability of the numerology in <NUM> NR, with scaling of subcarrier spacing, may efficiently address operating diverse services across diverse spectrum and diverse deployments. For example, in various outdoor and macro coverage deployments of less than <NUM> FDD/TDD implementations, subcarrier spacing may occur with <NUM>, for example over <NUM>, <NUM>, <NUM>, <NUM>, and the like bandwidth. For other various outdoor and small cell coverage deployments of TDD greater than <NUM>, subcarrier spacing may occur with <NUM> over <NUM>/<NUM> bandwidth. For other various indoor wideband implementations, using a TDD over the unlicensed portion of the <NUM> band, the subcarrier spacing may occur with <NUM> over a <NUM> bandwidth. Finally, for various deployments transmitting with mmWave components at a TDD of <NUM>, subcarrier spacing may occur with <NUM> over a <NUM> bandwidth.

The scalable numerology of <NUM> NR facilitates scalable TTI for diverse latency and quality of service (QoS) requirements.

For clarity, certain aspects of the apparatus and techniques may be described below with reference to exemplary LTE implementations or in an LTE-centric way, and LTE terminology may be used as illustrative examples in portions of the description below; however, the description is not intended to be limited to LTE applications. Indeed, the present disclosure is concerned with shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces, such as those of <NUM> NR.

Moreover, it should be understood that, in operation, wireless communication networks adapted according to the concepts herein may operate with any combination of licensed or unlicensed spectrum depending on loading and availability. Accordingly, it will be apparent to one of skill in the art that the systems, apparatus and methods described herein may be applied to other communications systems and applications than the particular examples provided.

While aspects and embodiments are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovations described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, packaging arrangements. For example, embodiments and/or uses may come about via integrated chip embodiments and/or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregated, distributed, or OEM devices or systems incorporating one or more described aspects. In some practical settings, devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described embodiments. It is intended that innovations described herein may be practiced in a wide variety of implementations, including both large/small devices, chip-level components, multicomponent systems (e.g. RF-chain, communication interface, processor), distributed arrangements, end-user devices, etc. of varying sizes, shapes, and constitution.

<FIG> shows wireless network <NUM> for communication according to some embodiments. Wireless network <NUM> may, for example, comprise a <NUM> wireless network. As appreciated by those skilled in the art, components appearing in <FIG> are likely to have related counterparts in other network arrangements including, for example, cellular-style network arrangements and non-cellular-style-network arrangements (e.g., device to device or peer to peer or ad hoc network arrangements, etc.).

Wireless network <NUM> illustrated in <FIG> includes a number of base stations <NUM> and other network entities. A base station may be a station that communicates with the UEs and may also be referred to as an evolved node B (eNB), a next generation eNB (gNB), an access point, and the like. Each base station <NUM> may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to this particular geographic coverage area of a base station and/or a base station subsystem serving the coverage area, depending on the context in which the term is used. In implementations of wireless network <NUM> herein, base stations <NUM> may be associated with a same operator or different operators (e.g., wireless network <NUM> may comprise a plurality of operator wireless networks), and may provide wireless communications using one or more of the same frequencies (e.g., one or more frequency bands in licensed spectrum, unlicensed spectrum, or a combination thereof) as a neighboring cell. In some examples, an individual base station <NUM> or UE <NUM> may be operated by more than one network operating entity. In other examples, each base station <NUM> and UE <NUM> may be operated by a single network operating entity.

A base station may provide communication coverage for a macro cell or a small cell, such as a pico cell or a femto cell, and/or other types of cell. A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station or a home base station. In the example shown in <FIG>, base stations 105d and 105e are regular macro base stations, while base stations 105a-105c are macro base stations enabled with one of <NUM> dimension (3D), full dimension (FD), or massive MIMO. Base stations 105a-105c take advantage of their higher dimension MIMO capabilities to exploit 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station which may be a home node or portable access point. A base station may support one or multiple (e.g., two, three, four, and the like) cells.

Wireless network <NUM> may support synchronous or asynchronous operation. In some scenarios, networks may be enabled or configured to handle dynamic switching between synchronous or asynchronous operations.

UEs <NUM> are dispersed throughout the wireless network <NUM>, and each UE may be stationary or mobile. It should be appreciated that, although a mobile apparatus is commonly referred to as user equipment (UE) in standards and specifications promulgated by the 3rd Generation Partnership Project (3GPP), such apparatus may also be referred to by those skilled in the art as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. Within the present document, a "mobile" apparatus or UE need not necessarily have a capability to move, and may be stationary. Some non-limiting examples of a mobile apparatus, such as may comprise embodiments of one or more of UEs <NUM>, include a mobile, a cellular (cell) phone, a smart phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a laptop, a personal computer (PC), a notebook, a netbook, a smart book, a tablet, gaming devices, reality modification devices (e.g., extended reality (XR), augmented reality (AR), virtual reality (VR)), entertainment devices, and a personal digital assistant (PDA). A mobile apparatus may additionally be an "Internet of things" (IoT) or "Internet of everything" (IoE) device such as an automotive or other transportation vehicle, a satellite radio, a global positioning system (GPS) device, a logistics controller, a drone, a multi-copter, a quad-copter, a smart energy or security device, a solar panel or solar array, municipal lighting, water, or other infrastructure; industrial automation and enterprise devices; consumer and wearable devices, such as eyewear, a wearable camera, a smart watch, a health or fitness tracker, a mammal implantable device, gesture tracking device, medical device, a digital audio player (e.g., MP3 player), a camera, a game console, etc.; and digital home or smart home devices such as a home audio, video, and multimedia device, an appliance, a sensor, a vending machine, intelligent lighting, a home security system, a smart meter, etc. In one aspect, a UE may be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, a UE may be a device that does not include a UICC. In some aspects, UEs that do not include UICCs may also be referred to as IoE devices. UEs 115a-115d of the embodiment illustrated in <FIG> are examples of mobile smart phone-type devices accessing wireless network <NUM> A UE may also be a machine specifically configured for connected communication, including machine type communication (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT) and the like. UEs 115e-<NUM> illustrated in <FIG> are examples of various machines configured for communication that access wireless network <NUM>.

A mobile apparatus, such as UEs <NUM>, may be able to communicate with any type of the base stations, whether macro base stations, pico base stations, femto base stations, relays, and the like. In <FIG>, a lightning bolt (e.g., communication link) indicates wireless transmissions between a UE and a serving base station, which is a base station designated to serve the UE on the downlink and/or uplink, or desired transmission between base stations, and backhaul transmissions between base stations. Backhaul communication between base stations of wireless network <NUM> may occur using wired and/or wireless communication links.

In operation at wireless network <NUM>, base stations 105a-105c serve UEs 115a and 115b using 3D beamforming and coordinated spatial techniques, such as coordinated multipoint (CoMP) or multi-connectivity. Macro base station 105d performs backhaul communications with base stations 105a-105c, as well as small cell, base station 105f. Macro base station 105d also transmits multicast services which are subscribed to and received by UEs 115c and 115d.

Wireless network <NUM> can support mission critical communications with ultra-reliable and redundant links for mission critical devices, such UE 115e, which is a drone. Redundant communication links with UE 115e include from macro base stations 105d and 105e, as well as small cell base station 105f. Other machine type devices, such as UE 115f (thermometer), UE <NUM> (smart meter), and UE <NUM> (wearable device) may communicate through wireless network <NUM> either directly with base stations, such as small cell base station 105f, and macro base station 105e, or in multi-hop configurations by communicating with another user device which relays its information to the network, such as UE 115f communicating temperature measurement information to the smart meter, UE <NUM>, which is then reported to the network through small cell base station 105f. Wireless network <NUM> may also provide additional network efficiency through dynamic, low-latency TDD/FDD communications, such as in a vehicle-to-vehicle (V2V) mesh network between UEs 115i-<NUM> communicating with macro base station 105e.

<FIG> shows a block diagram of a design of a base station <NUM> and a UE <NUM>, which may be any of the base stations and one of the UEs in <FIG>. For a restricted association scenario (as mentioned above), base station <NUM> may be small cell base station 105f in <FIG>, and UE <NUM> may be UE 115c or 115D operating in a service area of base station 105f, which in order to access small cell base station 105f, would be included in a list of accessible UEs for small cell base station 105f. Base station <NUM> may also be a base station of some other type. As shown in <FIG>, base station <NUM> may be equipped with antennas 234a through 234t, and UE <NUM> may be equipped with antennas 252a through 252r for facilitating wireless communications.

At the base station <NUM>, a transmit processor <NUM> may receive data from a data source <NUM> and control information from a controller/processor <NUM>. The control information may be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid-ARQ (automatic repeat request) indicator channel (PHICH), physical downlink control channel (PDCCH), enhanced physical downlink control channel (EPDCCH), MTC physical downlink control channel (MPDCCH), etc. The data may be for the PDSCH, etc. The transmit processor <NUM> may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor <NUM> may also generate reference symbols, e.g., for the primary synchronization signal (PSS) and secondary synchronization signal (SSS), and cell-specific reference signal. Transmit (TX) multiple-input multiple-output (MIMO) processor <NUM> may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to modulators (MODs) 232a through 232t. Each modulator <NUM> may additionally or alternatively process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators 232a through 232t may be transmitted via the antennas 234a through 234t, respectively.

At the UE <NUM>, the antennas 252a through 252r may receive the downlink signals from the base station <NUM> and may provide received signals to the demodulators (DEMODs) 254a through 254r, respectively. MIMO detector <NUM> may obtain received symbols from demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. Receive processor <NUM> may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE <NUM> to a data sink <NUM>, and provide decoded control information to a controller/processor <NUM>.

On the uplink, at the UE <NUM>, a transmit processor <NUM> may receive and process data (e.g., for the physical uplink shared channel (PUSCH)) from a data source <NUM> and control information (e.g., for the physical uplink control channel (PUCCH)) from the controller/processor <NUM>. Transmit processor <NUM> may also generate reference symbols for a reference signal. The symbols from the transmit processor <NUM> may be precoded by TX MIMO processor <NUM> if applicable, further processed by the modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the base station <NUM>. At base station <NUM>, the uplink signals from UE <NUM> may be received by antennas <NUM>, processed by demodulators <NUM>, detected by MIMO detector <NUM> if applicable, and further processed by receive processor <NUM> to obtain decoded data and control information sent by UE <NUM>. Receive processor <NUM> may provide the decoded data to data sink <NUM> and the decoded control information to controller/processor <NUM>.

Controllers/processors <NUM> and <NUM> may direct the operation at base station <NUM> and UE <NUM>, respectively. Controller/processor <NUM> and/or other processors and modules at base station <NUM> and/or controller/processor <NUM> and/or other processors and modules at UE <NUM> may perform or direct the execution of various processes for the techniques described herein, such as to perform or direct the execution illustrated in <FIG>, and/or other processes for the techniques described herein. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively. Scheduler <NUM> may schedule UEs for data transmission on the downlink and/or uplink.

In some cases, UE <NUM> and base station <NUM> may operate in a shared radio frequency spectrum band, which may include licensed or unlicensed (e.g., contention-based) frequency spectrum. In an unlicensed frequency portion of the shared radio frequency spectrum band, UEs <NUM> or base stations <NUM> may traditionally perform a medium-sensing procedure to contend for access to the frequency spectrum. For example, UE <NUM> or base station <NUM> may perform a listen before talk (LBT) procedure such as a clear channel assessment (CCA) prior to communicating in order to determine whether the shared channel is available. A CCA may include an energy detection procedure to determine whether there are any other active transmissions. For example, a device may infer that a change in a received signal strength indicator (RSSI) of a power meter indicates that a channel is occupied. Specifically, signal power that is concentrated in a certain bandwidth and exceeds a predetermined noise floor may indicate another wireless transmitter. A CCA also may include detection of specific sequences that indicate use of the channel. For example, another device may transmit a specific preamble prior to transmitting a data sequence. In some cases, an LBT procedure may include a wireless node adjusting its own backoff window based on the amount of energy detected on a channel and/or the acknowledge/negative-acknowledge (ACK/NACK) feedback for its own transmitted packets as a proxy for collisions.

In <NUM> NR communications systems, a UE may receive a transmission from a base station via a physical downlink shared channel (PDSCH). The PDSCH may be scheduled, by the base station, for transmission during a time slot (e.g., a plurality of symbols). For example, a time slot may include fourteen symbols, and the PDSCH may be scheduled for four of the fourteen symbols, as a non-limiting example. After the UE receives the PDSCH, there is an overall processing time (e.g., a number of symbols) for the UE to decode a downlink control information (DCI) that schedules the PDSCH, receive the PDSCH and decode the transport block (TB) included within, and to prepare a hybrid automatic repeat request acknowledgement (HARQ-ACK) corresponding to the PDSCH. Thus, the overall processing time represents the minimum time (e.g., the minimum number of symbols) between a final symbol of the PDSCH and a first symbol of the HARQ-ACK that is transmitted via a physical uplink control channel (PUCCH).

The overall processing time is defined as in the claims. It includes a first portion of processing time and a second portion of processing time. In at least some wireless communication standards, such as 3GPP wireless communication standards, the first portion of processing time is designated N<NUM> and the second portion of processing time is designated d<NUM>,<NUM>. N<NUM> (e.g., the first portion of processing time) is determined based on a UE processing capability (e.g., a UE may be programmed with one of two UE processing capabilities), subcarrier spacing, and, if the UE has a first UE capability, whether one or more additional positions for demodulation reference signal (DMRS) symbols are configured. N<NUM> (in symbols) for UEs having the first UE processing capability may be given by Table <NUM> below, where µ is the subcarrier spacing (e.g., <NUM> corresponds to <NUM> kilohertz (kHz), <NUM> corresponds to <NUM>, <NUM> corresponds to <NUM>, and <NUM> corresponds to <NUM>):.

N<NUM> (in symbols) for UEs having a second UE processing capability may be given by Table <NUM> below, where µ is the subcarrier spacing:.

The second portion of processing time (e.g., d<NUM>,<NUM>) may be determined based on a PDSCH mapping type (e.g., a PDSCH may have one of two mapping types, mapping type A or mapping type B), the UE processing capability, a length L of the PDSCH, and a number of overlapping symbols between a DCI that schedules the PDSCH and the PDSCH itself. Descriptions of how d<NUM>,<NUM> is determined are further described herein. Once N<NUM> and d<NUM>,<NUM> are determined, the overall processing time is the sum of N<NUM> and d<NUM>,<NUM>.

The overall processing time corresponds to the total time for the UE to decode the DCI that schedules the PDSCH, to receive the PDSCH and decode the TB included within the PDSCH, and to prepare a hybrid automatic repeat request acknowledgement, HARQ-ACK, corresponding to the PDSCH. However, it is noted that in some of the more recent wireless communication standards (e.g., 3GPP wireless communication standards, as a non-limiting example), repetition of PDSCH within a single slot is allowed (e.g., referred to as "TDMSchemeA" in at least one wireless communication standard). In such a scheme, a single DCI scheduling a PDSCH may indicate two transmission configuration indicator (TCI) states within a single slot, with non-overlapped time resource allocation. In such implementations, the PDSCH includes two transmission occasions for the same TB, where each instance of the TB has its own TCI state and redundancy version (RV) with the time granularity of mini-slots. For example, a TCI codepoint included in the DCI may be a multi-bit value that indicates one or two TCI states. The mapping between the codepoint values and the various TCI states may be done through radio resource control (RRC) signaling or through medium access control (MAC) control elements (MAC CEs). The number of transmission occasions scheduled in the PDSCH is determined by the number of TCI states indicated by the DCI (e.g., if one TCI state is indicated, one transmission occasion is scheduled, and if two TCI states are indicated, two transmission occasions are scheduled). The starting symbol and length of the first transmission occasion may be specified by the DCI (e.g., in a start and length indicator value (SLIV) in a time domain resource allocation field (TDRA) of the DCI). The length of the second transmission occasion is the same as the length of the first transmission occasion. There may be a one or more symbol offset between the last symbol of the first transmission occasion and the first symbol of the second transmission occasion. This offset value (referred to as K) may be configured in RRC signaling, or if not configured, is defaulted to zero (e.g., no offset between the transmission occasions).

A UE may receive the PDSCH having two transmission occasions and may perform decoding on the first transmission occasion, the perform soft combining for both PDSCH transmission occasions. Soft combining may be performed because both transmission occasions correspond to the same TB. However, the UE may not be able to determine the overall processing time for a PDSCH with two transmission occasions within the same slot. To illustrate, the two transmission occasions may correspond to different PDSCH mapping types or may have different overlaps between symbols of the DCI and symbols of the PDSCH.

The present disclosure provides systems, apparatus, methods, and computer-readable media for enabling determination (at a UE and/or at a base station) of an overall processing time of a UE for a PDSCH that includes multiple transmission occasions, such as based on a DCI that indicates multiple TCI states. For example, a second portion of the overall processing time (e.g., d<NUM>,<NUM>) may be determined based on a mapping type of a first transmission occasion of a PDSCH, a mapping type of a second transmission occasion of the PDSCH, a processing capability of the UE, a length of the first transmission occasion, a number of symbols of the DCI that overlap the first transmission occasion, or a combination thereof. In some implementations, the second portion of the overall processing time may be determined based further on a length of the second transmission occasion, a number of symbols of the DCI that overlap the second transmission occasion, a symbol offset between the first transmission occasion and the second transmission occasion, or a combination thereof. The present disclosure provides multiple alternatives for determining d<NUM>,<NUM> based on this information. Thus, a HARQ-ACK is scheduled based on the overall processing time, which enables a wireless communication system to support repetition of PDSCH within a single slot.

<FIG> is a block diagram of an example wireless communications system <NUM> configured to enable PDSCH repetition (e.g., two or more transmission occasions) in the same slot (or in consecutive slots). In some examples, wireless communications system <NUM> may implement aspects of wireless network <NUM>. Wireless communications system <NUM> includes UE <NUM> and base station <NUM>. Although one UE and one base station are illustrated, in other implementations, wireless communications system <NUM> may include more than one UE, more than one base station, or both.

UE <NUM> can include a variety of components (e.g., structural, hardware components) used for carrying out one or more functions described herein. For example, these components can include a processor <NUM>, a memory <NUM>, a transmitter <NUM>, and a receiver <NUM>. Processor <NUM> may be configured to execute instructions stored at memory <NUM> to perform the operations described herein. In some implementations, processor <NUM> includes or corresponds to controller/processor <NUM>, and memory <NUM> includes or corresponds to memory <NUM>.

Transmitter <NUM> is configured to transmit data to one or more other devices, and receiver <NUM> is configured to receive data from one or more other devices. For example, transmitter <NUM> may transmit data, and receiver <NUM> may receive data, via a network, such as a wired network, a wireless network, or a combination thereof. For example, UE <NUM> may be configured to transmit or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, intranet, extranet, cable transmission system, cellular communication network, any combination of the above, or any other communications network now known or later developed within which permits two or more electronic devices to communicate. In some implementations, transmitter <NUM> and receiver <NUM> may be replaced with a transceiver. Additionally, or alternatively, transmitter <NUM>, receiver <NUM>, or both may include or correspond to one or more components of UE <NUM> described with reference to <FIG>.

Base station <NUM> can include a variety of components (e.g., structural, hardware components) used for carrying out one or more functions described herein. For example, these components can include processor <NUM>, memory <NUM>, transmitter <NUM>, and receiver <NUM>. Processor <NUM> may be configured to execute instructions stored at memory <NUM> to perform the operations described herein. In some implementations, processor <NUM> includes or corresponds to controller/processor <NUM>, and memory <NUM> includes or corresponds to memory <NUM>.

Transmitter <NUM> is configured to transmit data to one or more other devices, and receiver <NUM> is configured to receive data from one or more other devices. For example, transmitter <NUM> may transmit data, and receiver <NUM> may receive data, via a network, such as a wired network, a wireless network, or a combination thereof. For example, base station <NUM> may be configured to transmit or receive data via a direct device-to-device connection, a LAN, a WAN, a modem-to-modem connection, the Internet, intranet, extranet, cable transmission system, cellular communication network, any combination of the above, or any other communications network now known or later developed within which permits two or more electronic devices to communicate. In some implementations, transmitter <NUM> and receiver <NUM> may be replaced with a transceiver. Additionally, or alternatively, transmitter <NUM>, receiver, <NUM>, or both may include or correspond to one or more components of base station <NUM> described with reference to <FIG>.

In a particular implementation, wireless communications system <NUM> includes a <NUM> network. For example, UE <NUM> may include a <NUM> UE (e.g., a UE configured to operate in accordance with a <NUM> network). Base station <NUM> may include a <NUM> base station (e.g., a base station configured to operate in accordance with a <NUM> network).

During operation of wireless communications system <NUM>, UE <NUM> receives DCI <NUM> from base station <NUM>. DCI <NUM> schedules PDSCH <NUM>. DCI <NUM> indicates that PDSCH <NUM> has multiple (e.g., two or more) transmission occasions. For example, DCI <NUM> includes TCI states <NUM> (e.g., a TCI codepoint or a TCI field). Based on the value of TCI states <NUM>, TCI states <NUM> may indicate a single TCI state or two TCI states. If TCI states <NUM> indicates two TCI states, UE <NUM> determines that PDSCH <NUM> includes two transmission occasions (e.g., a first transmission occasion <NUM> and a second transmission occasion <NUM>) within the same slot using non-overlapped time resources. Although described herein as having two transmission occasions, in other implementations, PDSCH <NUM> may have more than two transmission occasions, which may be indicated by the value of TCI states <NUM> and/or by another value or field of DCI <NUM>.

DCI <NUM> may include additional information corresponding to one or more of the transmission occasions. For example, DCI <NUM> may include mapping type <NUM>. In some implementations, mapping type <NUM> indicates whether a mapping type corresponding to first transmission occasion <NUM> corresponds to a first mapping type or a second mapping type (e.g., one of at least two mapping types). The first mapping type may be referred to as "mapping type A" and the second mapping type may be referred to as "mapping type B" in at least one wireless communication standard. For a slot that includes fourteen symbols (e.g., symbol <NUM> - symbol <NUM>), if a transmission occasion corresponds to the first mapping type (e.g., mapping type A), a first DMRS symbol of the PDSCH is either on the third symbol (e.g., symbol <NUM>) or the fourth symbol (e.g., symbol <NUM>) of the slot. Which slot the first DMRS symbol is on (e.g., assigned) is indicated by one bit in a master information block (MIB), and the assignment is not dynamic. Additionally, the starting symbol of the PDSCH can be on the first through the fourth symbols (e.g., symbol <NUM> - symbol <NUM>) and is indicated as part of the TDRA field of DCI <NUM>. The starting symbol can be changed dynamically (e.g., different DCIs can schedule PDSCHs that start on different symbols). If a transmission occasion corresponds to the second mapping type (e.g., mapping type B), the first DMRS symbol is the starting symbol of the PDSCH, and the starting symbol of the PDSCH can be any symbol of the slot except for the last symbol (e.g., symbol <NUM>). The starting symbol is indicated as part of the TDRA field of DCI <NUM>. Although mapping type <NUM> is described as corresponding to first transmission occasion <NUM>, in other implementations, mapping type <NUM> may correspond to second transmission occasion <NUM>, or two mapping type indicators may be included in DCI <NUM> (e.g., one for each of the transmission occasions <NUM>-<NUM>).

DCI <NUM> may also include transmission occasion information <NUM>. Transmission occasion information <NUM> includes information corresponding to first transmission occasion <NUM>. In some implementations, transmission occasion information <NUM> includes a starting symbol of first transmission occasion <NUM> and a length of first transmission occasion <NUM> (in symbols). For example, transmission occasion information <NUM> may include or correspond to a SLIV included in a TDRA field of DCI <NUM>. In some implementations, the length indicated for first transmission occasion <NUM> is the same as the length of second transmission occasion <NUM>. In some other implementations, the length of second transmission occasion <NUM> is not the same as the length of first transmission occasion <NUM> (and both lengths may be indicated by transmission occasion <NUM>). Although transmission occasion information <NUM> has been described as corresponding to first transmission occasion <NUM>, in other implementations, transmission occasion information <NUM> may correspond to second transmission occasion <NUM> or transmission occasion information <NUM> may include information that corresponds to first transmission occasion <NUM> and information that corresponds to second transmission occasion <NUM>.

In some implementations, there is a symbol offset (e.g., K) between the last symbol of first transmission occasion <NUM> and the first symbol of the second transmission occasion <NUM>. The symbol offset may be RRC configurable. For example, base station <NUM> may transmit RRC message <NUM> to UE <NUM>. RRC message <NUM> may include symbol offset <NUM> (e.g., K). If symbol offset <NUM> is equal to zero or is not configured (e.g., RRC message <NUM> is not transmitted), the starting symbol of second transmission occasion <NUM> is the next symbol after the last symbol of first transmission occasion <NUM>. If symbol offset <NUM> is configured, first transmission occasion <NUM> and second transmission occasion <NUM> are offset by a number of symbols indicated by symbol offset <NUM>.

After transmitting DCI <NUM> (and RRC message <NUM> in some implementations), base station <NUM> transmits a TB to UE <NUM> via PDSCH <NUM>. The TB may be transmitted during first transmission occasion <NUM> and during second transmission occasion <NUM>. The transmission occasions may correspond to different TCI states, and thus correspond to different transmit receive points (TRPs). Transmitting the same TB via different TRPs may improve diversity in the transmission of the TB.

Examples of PDSCHs with multiple transmission occasions are shown in <FIG>. In a first example <NUM>, a starting symbol of a first transmission occasion (e.g., first transmission occasion <NUM>) is symbol <NUM> and a length of the first transmission occasion is <NUM> symbols. This information may be indicated by a SLIV of a TDRA field of a DCI, such as transmission occasion information <NUM> of DCI <NUM> of <FIG>. Thus, the first transmission occasion occupies symbols <NUM>-<NUM> of the slot. Additionally, a symbol offset is set equal to <NUM> (or is not configured). This may be indicated by symbol offset <NUM> of RRC message <NUM> of <FIG>. Because the symbol offset is <NUM>, a starting symbol of a second transmission occasion (e.g., second transmission occasion <NUM>) immediately follows the last symbol of the first transmission occasion. As explained above, the length of the second transmission occasion is the same as the length of the first transmission occasion. Thus, the second transmission occasion occupies symbols <NUM>-<NUM> of the slot.

In a second example <NUM>, the starting symbol of a first transmission occasion and the length of the first transmission occasion are the same as in the first example <NUM>. However, in the second example, the symbol offset is <NUM>. Because the symbol offset is <NUM>, there are <NUM> symbols between the last symbol of the first transmission occasion and the first symbol of the second transmission occasion. Thus, the second transmission occasion occupies symbols <NUM>-<NUM> of the slot. These examples are for illustration only, and in other examples, the start value of the first transmission occasion, the length of the transmission occasions, and the symbol offset may be different.

Although two transmission occasions have been illustrated in a single slot, in other implementations, more than two transmission occasions may be included within a single slot, thereby increasing PDSCH repetition. Alternatively, the two (or more) transmission occasions may be included in different slots. For example, two transmission occasions may be included in consecutive slots. As another example, two (or more) transmission occasions may be included in non-consecutive slots. As described above, although the lengths of the transmission occasions are described as being the same, in other implementations, each transmission occasion may have its own length which is different from the length of other transmission occasions. Additionally, or alternatively, although the transmission occasions are described as non-overlapping (e.g., using different resources), in some other implementations, the transmission occasions may at least partially overlap (e.g., multiple transmission occasions may occur during the same symbol). Additionally, or alternatively, although the transmission occasions are described as having separate TCI states, in some other implementations, at least two transmission occasions may share the same TCI state. In some such implementations, an additional value or field may be included in the DCI to indicate the number of transmission occasions if the number of transmission occasions does not correspond to the number of TCI states.

Returning to <FIG>, after receiving PDSCH <NUM>, UE <NUM> performs decoding on the TB corresponding to first transmission occasion <NUM> and then performs soft combining for the TB received during both first transmission occasion <NUM> and second transmission occasion <NUM>. This enables UE <NUM> to process the TB in an efficient manner.

UE <NUM> also determines an overall processing time <NUM> needed by UE <NUM> to decode DCI <NUM>, receive PDSCH <NUM> and decode the TB, and generate a HARQ-ACK <NUM> responsive to the TB of PDSCH <NUM>. Overall processing time <NUM> refers to a number of symbols that follow a last symbol of PDSCH <NUM> (e.g., a last symbol of second transmission occasion <NUM>). Overall processing time <NUM> may include a first portion <NUM> and a second portion <NUM>.

Determining first portion <NUM> (e.g., N<NUM>) is the same regardless of whether there is a single transmission occasion or multiple transmission occasions within PDSCH <NUM> (e.g., within the same slot). First portion <NUM> may be determined based on processing capability <NUM> (e.g., which indicates whether UE <NUM> has one of at least two capability types: a first processing capability ("capability <NUM>") or a second processing capability ("capability <NUM>")), subcarrier spacing associated with PDSCH <NUM>, and whether one or more additional positions for DMRS symbols are configured. For example, UE <NUM> may determine first portion <NUM> based on a mapping of processing capability <NUM>, the subcarrier spacing associated with PDSCH <NUM>, and whether the one or more additional positions for DMRS symbols are configured that is specified in a wireless communication standard (e.g., a 3GPP wireless communication standard). The mappings are described above in Table <NUM> and Table <NUM>.

Determining second portion <NUM> (e.g., d<NUM>,<NUM>) is not the same when there are multiple transmission occasions within PDSCH <NUM>. However, in order to explain the determination of second portion <NUM> for multiple transmission occasions, it is helpful to first describe determining a portion (e.g., d<NUM>,<NUM>) of an overall processing time for a PDSCH that includes a single transmission occasion. When a mapping type of a transmission occasion is the first mapping type (e.g., mapping type A), a processing time (e.g., d<NUM>,<NUM>) corresponding to the transmission occasion is determined based on a last symbol of the transmission occasion. For example, the last symbol of the transmission occasion may be designated the i-th symbol. If i is less than <NUM>, the processing time is equal to <NUM> - i symbols. If i is greater than or equal to <NUM>, the processing time is equal to <NUM> symbols.

When the mapping type of the transmission occasion is the second mapping type (e.g., mapping type B), the processing time (e.g., d<NUM>,<NUM>) is determined based on the UE processing capability of the UE. When the processing capability is a first capability type (e.g., processing capability <NUM>), the processing time is determined based on a length of the transmission occasion or a number of symbols of the DCI that overlap the transmission occasion. To illustrate, when the length of the transmission occasion is greater than or equal to <NUM>, the processing time is equal to <NUM> symbols. When the length (e.g., L) of the transmission occasion is between <NUM> and <NUM> symbols, the processing time is equal to <NUM> - L. When the length of the transmission occasion is equal to <NUM> symbols, the processing time is equal to <NUM> + min(d, <NUM>), where d is the number of symbols of the DCI that overlap the transmission occasion. When the length of the transmission occasion is equal to <NUM> symbols, the processing time is equal to <NUM> + d.

Alternatively, when the mapping type of the transmission occasion is the second mapping type (e.g., mapping type B) and the processing capability is the second capability type (e.g., processing capability <NUM>), the processing time is determined based on a length of the transmission occasion, a number of symbols of the DCI that overlap the transmission occasion, or a number of symbols of a control resource set (CORESET) corresponding to the DCI. To illustrate, when the length of the transmission occasion is greater than or equal to <NUM> symbols, the processing time is equal to <NUM> symbols. When the length of the transmission occasion is between <NUM> and <NUM> symbols, the processing time is equal to d, where d is the number of symbols of the DCI that overlap the transmission occasion. When the length of the transmission occasion is equal to <NUM> symbols, if the number of symbols of the CORESET is equal to <NUM> (e.g., a <NUM>-symbol CORESET) and the DCI and the transmission occasion have the same starting symbol, the processing time is equal to <NUM> symbols. Otherwise, when the length of the transmission occasion is equal to <NUM> symbols (e.g., if the CORESET is not a <NUM>-symbol CORESET or the DCI and the transmission occasion do not share the same starting symbol), the processing time is equal to d.

<FIG> illustrates examples of determining a processing time of a PDSCH that includes a single transmission occasion. In a first example <NUM>, the PDSCH starts at the second symbol, has a length of <NUM> symbols, and ends at the fifth symbol. In first example <NUM>, the PDSCH corresponds to the first mapping type (e.g., because the DMRS symbol is not the first symbol of the PDSCH). In the first example, i (e.g., the last symbol of the PDSCH) is equal to <NUM>. Because <NUM> < <NUM>, the processing time (e.g., d<NUM>,<NUM>) is equal to <NUM> - <NUM> = <NUM> symbols.

In a second example <NUM>, the PDSCH corresponds to the second mapping type (e.g., because the DMRS symbol is the first symbol of the PDSCH) and the UE capability corresponds to the first capability type. In second example <NUM>, the PDSCH starts at the second symbol, has a length (L) of <NUM> symbols, and ends at the fifth symbol. Because L is between <NUM> and <NUM>, the processing time (e.g., d<NUM>,<NUM>) is equal to <NUM> - L = <NUM> - <NUM> = <NUM> symbols.

In a third example <NUM>, the PDSCH corresponds to the second mapping type and the UE capability corresponds to the first capability type. In third example <NUM>, the PDSCH starts at the second symbol, has a length (L) of <NUM> symbols, and ends at the third symbol. Additionally, <NUM> symbols of the DCI overlap the PDSCH (e.g., the DCI is also located at the second and third symbols). Because L = <NUM>, the processing time (e.g., d<NUM>,<NUM>) is equal to <NUM> + d = <NUM> + <NUM> = <NUM> symbols.

In a fourth example <NUM>, the PDSCH corresponds to the second mapping type and the UE capability corresponds to the second capability type. In fourth example <NUM>, the PDSCH starts at the second symbols, has a length (L) of <NUM> symbols, and ends at the fifth symbol. Additionally, <NUM> symbols of the DCI overlap the PDSCH. Because L is between <NUM> and <NUM>, the processing time (e.g., d<NUM>,<NUM>) is equal to d = <NUM> symbols.

In a fifth example <NUM>, the PDSCH corresponds to the second mapping type and the UE capability corresponds to the second capability type. In fifth example <NUM>, the PDSCH starts at the second symbol, has a length (L) of <NUM> symbols, and ends at the third symbol. Additionally, the DCI is a <NUM>-symbol CORESET (e.g., includes <NUM> symbols) and the DCI and the PDSCH start at the same symbol (e.g., the second symbol). Because the DCI is the <NUM>-symbol CORESET and the DCI and the PDSCH start at the same symbol, the processing time (e.g., d<NUM>,<NUM>) is equal to <NUM> symbols.

Returning to <FIG>, UE <NUM> determines overall processing time <NUM> as defined in the claims. The determination may be based on a sum of first portion <NUM> and second portion <NUM>. First portion <NUM> is determined as described above. Second portion <NUM> (e.g., d<NUM>,<NUM>) is determined based on a mapping type of first transmission occasion <NUM>, a mapping type of second transmission occasion <NUM>, processing capability <NUM>, a length of first transmission occasion <NUM>, a length of second transmission occasion <NUM>, a number of symbols of DCI <NUM> that overlap first transmission occasion <NUM>, a number of symbols of DCI <NUM> that overlap second transmission occasion <NUM>, symbol offset <NUM>, or a combination thereof. In some implementations, the mapping type of first transmission occasion <NUM> is indicated by mapping type <NUM>, and the mapping type of second transmission occasion <NUM> is always the second mapping type (e.g., mapping type B). In some other implementations, both mapping types are always the second mapping type. In other implementations, the mapping types may have other values. Determining second portion <NUM> in such a manner corresponds to determining second portion <NUM> based on a processing time corresponding to first transmission occasion <NUM>, a processing time corresponding to second transmission occasion <NUM>, other information, or a combination thereof.

Second portion <NUM> (e.g., d<NUM>,<NUM>) may be determined according to a variety of alternatives or rules. In some implementations (e.g., a first alternative/rule), UE <NUM> determines a first processing time corresponding to first transmission occasion <NUM> and a second processing time corresponding to second transmission occasion <NUM>. For example, the first processing time may be determined as described above as if first transmission occasion <NUM> was the only transmission occasion, and the second processing time may be determined as described above as if second transmission occasion <NUM> was the only transmission occasion. In these implementations, second portion <NUM> is equal to a maximum of the first processing time and the second processing time.

In some other implementations (e.g., a second alternative/rule), UE <NUM> determines a difference between the first processing time corresponding to first transmission occasion <NUM> and symbol offset <NUM>. UE <NUM> also determines the second processing time corresponding to second transmission occasion <NUM>. In these implementations, second portion <NUM> is equal to a maximum of the difference (e.g., between the first processing time and symbol offset <NUM>) and the second processing time.

In some other implementations (e.g., a third alternative/rule), UE <NUM> determines a processing time corresponding to second transmission occasion <NUM>, and second portion <NUM> is equal to the processing time corresponding to second transmission occasion <NUM>. In some other implementations (e.g., a fourth alternative/rule), UE <NUM> determines a processing time corresponding to first transmission occasion <NUM>, and second portion <NUM> is equal to the processing time corresponding to first transmission occasion <NUM>. Alternatively, second portion <NUM> may be equal to a difference between the processing time corresponding to first transmission occasion <NUM> and symbol offset <NUM>.

In some other implementations (e.g., a fifth alternative/rule), UE <NUM> determines a combined processing time corresponding to a combination of first transmission occasion <NUM> and second transmission occasion <NUM>. The combined processing time is determined based on a combined length of first transmission occasion <NUM> and second transmission occasion <NUM>. Second portion <NUM> is equal to the combined processing time. In some implementations, symbol offset <NUM> is included in the combined length (e.g., the combined length is the sum of the length of first transmission occasion <NUM>, symbol offset <NUM>, and second transmission occasion <NUM>). In some other implementations, symbol offset <NUM> is excluded from the combined length (e.g., the combined length is the sum of the length of first transmission occasion <NUM> and the length of second transmission occasion <NUM>, and symbol offset <NUM> is ignored). The mapping type for the combination may be based on the mapping type of first transmission occasion <NUM>, the mapping type of second transmission occasion <NUM>, or both. For example, if the mapping types of both transmission occasions are the same, the mapping type for the combination is the mapping type of either transmission occasion. In some implementations, if the mapping types of the transmission occasions are different, the combined transmit time is determined based on the mapping type of first transmission occasion <NUM>. Alternatively, if the mapping types of the transmission occasions are different, the combined transmit time may be determined based on the mapping type of second transmission occasion <NUM>.

In some other implementations (e.g., a sixth alternative/rule), UE <NUM> determines a processing time corresponding to second transmission occasion <NUM>. However, in this determination, UE <NUM> uses the number of symbols of DCI <NUM> that overlap either first transmission occasion <NUM> or second transmission occasion <NUM> (e.g., that overlap any part of PDSCH <NUM>). Second portion <NUM> is equal to the processing time corresponding to second transmission occasion <NUM> (determined with all overlapping DCI symbols).

<FIG> illustrates examples of determining a portion of an overall processing time (e.g., d<NUM>,<NUM>) for PDSCHs that include two transmission occasions. In a first example <NUM>, a first transmission occasion corresponds to the first mapping type (e.g., mapping type A). The UE corresponds to the first processing capability type (e.g., processing capability <NUM>). The first transmission occasion starts at the second symbol, has a length of <NUM> symbols, and ends at the fifth symbol. In first example <NUM>, a second transmission occasion corresponds to the second mapping type (e.g., mapping type B). The second transmission occasion starts at the sixth symbol, has a length of <NUM> symbols, and ends at the ninth symbol. In first example <NUM>, the symbol offset is <NUM> (or is not configured).

Based on the description above, the processing time of the first transmission occasion is equal to <NUM> - i = <NUM> - <NUM> = <NUM> symbols. Based on the description above, the processing time of the second transmission occasion is equal to <NUM> - L = <NUM> - <NUM> = <NUM> symbols. For the first alternative, second portion <NUM> (e.g. d<NUM>,<NUM>) is equal to max(<NUM>, <NUM>) = <NUM> symbols. For the second alternative, second portion <NUM> is equal to max (<NUM>-<NUM>, <NUM>) = max(<NUM>,<NUM>) = <NUM> symbols. For the third alternative, second portion <NUM> is equal to <NUM> symbols (e.g., the processing time of the second transmission occasion). For the fourth alternative, second portion <NUM> is equal to <NUM> symbols (e.g., the processing time of the first transmission occasion). For the fifth alternative, the combined length is equal to <NUM> symbols and, if the mapping type of the combination is the mapping type of the first transmission occasion (e.g., the first mapping type), L is greater than or equal to <NUM> symbols, resulting in second portion <NUM> being equal to <NUM> symbols. In the sixth implementation, second portion <NUM> is equal to <NUM> symbols (e.g., the processing time of the second transmission occasion with no modifications because there is no overlap of a DCI with either transmission occasion).

In a second example <NUM>, a first transmission occasion corresponds to the second mapping type (e.g., mapping type B). The UE corresponds to the first processing capability type (e.g., processing capability <NUM>). The first transmission occasion starts at the second symbol, has a length of <NUM> symbols, and ends at the third symbol. In second example <NUM>, a second transmission occasion corresponds to the second mapping type. The second transmission occasion starts at the fifth symbol, has a length of <NUM> symbols, and ends at the sixth symbol. In second example <NUM>, the symbol offset is <NUM> symbol. A DCI overlaps both symbols of the first transmission occasion.

Based on the description above, the processing time of the first transmission occasion is equal to <NUM> + d = <NUM> + <NUM> = <NUM> symbols. The processing time of the second transmission occasion is <NUM> + d = <NUM> + <NUM> = <NUM> symbols. For the first alternative, second portion <NUM> (e.g., d<NUM>,<NUM>) is equal to max(<NUM>,<NUM>) = <NUM> symbols. For the second alternative, second portion <NUM> is equal to max(<NUM>-<NUM>,<NUM>) = max(<NUM>,<NUM>) = <NUM> symbols. For the third alternative, second portion <NUM> is equal to <NUM> symbols. For the fourth alternative, second portion <NUM> is equal to <NUM> symbols. For the fifth alternative, the combined length is equal to <NUM> symbols (excluding the symbol offset) and the mapping type is the second mapping type. Thus, because L is between <NUM> and <NUM> symbols, second portion <NUM> is equal to <NUM> - L = <NUM> - <NUM> = <NUM> symbols. For the sixth alternative, the number of overlapping symbols of the DCI and the entirety of the PDSCH is <NUM> symbols, the length is <NUM>, and second portion <NUM> is equal to <NUM> + d = <NUM> + <NUM> = <NUM> symbols.

In a third example <NUM>, a first transmission occasion corresponds to the first mapping type (e.g., mapping type A). The UE corresponds to the second processing capability type (e.g., processing capability <NUM>). The first transmission occasion starts at the first symbol, has a length of <NUM> symbols, and ends at the third symbol. In third example <NUM>, a second transmission occasion corresponds to the second mapping type (e.g., mapping type B). The second transmission occasion starts at the fourth symbol, has a length of <NUM> symbols, and ends at the sixth symbol. In third example <NUM>, the symbol offset is <NUM> symbols (or is not configured). A DCI overlaps <NUM> symbols of the first transmission occasion.

Based on the description above, the processing time of the first transmission occasion, because i is < <NUM>, is equal to <NUM> - i = <NUM> - <NUM> = <NUM> symbols. The processing time of the second transmission occasion, because L is between <NUM> and <NUM> symbols, is equal to d = <NUM> symbols (because the DCI does not overlap any symbols of the second transmission occasion. For the first alternative, second portion <NUM> (e.g., d<NUM>,<NUM>) is equal to max(<NUM>,<NUM>) = <NUM> symbols. For the second alternative, second portion <NUM> is equal to max(<NUM>-<NUM>,<NUM>) = max(<NUM>,<NUM>) = <NUM> symbols. For the third alternative, second portion <NUM> is equal to <NUM> symbols. For the fourth alternative, second portion <NUM> is equal to <NUM> symbols. For the fifth alternative, the combined length is <NUM> symbols, the mapping type is the first mapping type, and the combination ends on the sixth symbol. Thus, second portion <NUM> = <NUM> - i = <NUM> -<NUM> = <NUM> symbol. For the sixth alternative, the number of overlapping symbols of the DCI and the entirety of the PDSCH is <NUM>, L is equal to <NUM> symbols (e.g., between <NUM> and <NUM>), and second portion <NUM> = d = <NUM> symbols.

Returning to <FIG>, after determining second portion <NUM>, UE <NUM> may determine overall processing time <NUM> by summing first portion <NUM> and second portion <NUM>. After decoding PDSCH <NUM>, UE <NUM> may generate HARQ-ACK <NUM> responsive to the TBs received via PDSCH <NUM>. UE <NUM> may transmit, to base station <NUM>, HARQ-ACK <NUM> at a time after PDSCH <NUM> that is greater than or equal to overall processing time <NUM>. HARQ-ACK <NUM> may be transmitted via a physical uplink control channel (PUCCH). Thus, overall processing time <NUM> indicates the minimum number of symbols between the final symbol of PDSCH <NUM> (e.g., of second transmission occasion <NUM>) and the first symbol of HARQ-ACK <NUM>.

UE <NUM> may determine second portion <NUM> based on one or more of the rules (e.g., alternatives) described above. In some implementations, UE <NUM> determines second portion <NUM> based on a particular rule (e.g., alternative) that is preprogrammed at UE <NUM> prior to deployment or release of UE <NUM>. In some such implementations, the rule may be specified by a wireless communication standard (e.g., a 3GPP wireless communication standard). In some other implementations, a rule for determining second portion <NUM> may be specified by the network. For example, the rule may be specified in a master information block (MIB) and may be static within wireless communications system <NUM>. Alternatively, the rule may be dynamically specified via RRC signaling or MAC CEs. In still other implementations, UE <NUM> may be preprogrammed with a plurality of rules, and a particular rule (of the six above-described alternatives/rules) for determining second portion <NUM> may be selected at UE <NUM>, such as based on characteristics of DCI <NUM> or PDSCH <NUM>.

Although the determination of overall processing time <NUM> has been described as being performed by UE <NUM>, base station <NUM> may also determine overall processing time <NUM>. To illustrate, much of the information used to determine overall processing time <NUM>, such as mapping type <NUM>, transmission occasion information <NUM>, and symbol offset <NUM> either originates at or is known to base station <NUM>. Additionally, UE <NUM> may share processing capability <NUM> with base station <NUM> during an association process. Thus, base station <NUM>, after transmitting DCI <NUM>, may determine overall processing time <NUM> in the same manner as UE <NUM>. Base station <NUM> may schedule UE <NUM> to transmit HARQ-ACK <NUM> at a time after PDSCH <NUM> (e.g., second transmission occasion <NUM>) that is greater than or equal to overall processing time <NUM>.

Thus, <FIG> describes wireless communications system <NUM> that enables PDSCH repetition in a single slot without causing problems to scheduling of HARQ-ACK <NUM>. For example, even though DCI <NUM> indicates two TCI states and PDSCH therefore includes two transmission occasions, UE <NUM> and/or base station <NUM> is able to determine overall processing time <NUM> according to one or more rules (e.g., alternatives) described herein. Thus, scheduling of transmission of HARQ-ACK <NUM> may be sufficiently delayed to give UE <NUM> time to decode first transmission occasion <NUM> and perform soft combining on both transmission occasions as part of processing PDSCH <NUM>.

<FIG> is a flow diagram illustrating example blocks executed to implement one aspect of the present disclosure. The example blocks will also be described with respect to UE <NUM> as illustrated in <FIG> is a block diagram illustrating UE <NUM> configured according to one aspect of the present disclosure. UE <NUM> includes the structure, hardware, and components as illustrated for UE <NUM> of <FIG>. For example, UE <NUM> includes controller/processor <NUM>, which operates to execute logic or computer instructions stored in memory <NUM>, as well as controlling the components of UE <NUM> that provide the features and functionality of UE <NUM>. UE <NUM>, under control of controller/processor <NUM>, transmits and receives signals via wireless radios 901a-r and antennas 252a-r. Wireless radios 901a-r includes various components and hardware, as illustrated in <FIG> for UE <NUM>, including modulator/demodulators 254a-r, MIMO detector <NUM>, receive processor <NUM>, transmit processor <NUM>, and TX MIMO processor <NUM>.

At block <NUM>, the UE receives, from a base station, a DCI scheduling a PDSCH. The PDSCH includes a first transmission occasion and a second transmission occasion following the first transmission occasion during a single slot. The UE <NUM> may execute, under control of controller/processor <NUM>, DCI reception logic <NUM> stored in memory <NUM>. The execution environment of DCI reception logic <NUM> provides the functionality to receive, from a base station, a DCI scheduling a PDSCH. The PDSCH includes a first transmission occasion and a second transmission occasion following the first transmission occasion during a single slot. In some implementations, the DCI indicates two TCI states within a single slot.

At block <NUM>, the UE determines an overall processing time following a last symbol of the PDSCH. The UE <NUM> may execute, under control of controller/processor <NUM>, processing time determiner <NUM> stored in memory <NUM>. The execution environment of processing time determiner <NUM> provides the functionality to determine an overall processing time following a last symbol of the PDSCH. A portion of the overall processing time may be determined based on a mapping type of a first transmission occasion of the PDSCH, a mapping type of a second transmission occasion of the PDSCH, a processing capability of UE <NUM>, a length of the first transmission occasion, a length of the second transmission occasion, a number of symbols of the DCI that overlap the first transmission occasion, a number of symbols of the DCI that overlap the second transmission occasion, a symbol offset between the first transmission occasion and the second transmission occasion, or a combination thereof. For example, UE <NUM> may determine the portion of the overall processing time according to one or more of the six rules (e.g., alternatives) described above.

<FIG> is a flow diagram illustrating example blocks executed to implement one aspect of the present disclosure. The example blocks will also be described with respect to base station <NUM> as illustrated in <FIG> is a block diagram illustrating base station <NUM> configured according to one aspect of the present disclosure. Base station <NUM> includes the structure, hardware, and components as illustrated for base station <NUM> of <FIG>. For example, base station <NUM> includes controller/processor <NUM>, which operates to execute logic or computer instructions stored in memory <NUM>, as well as controlling the components of base station <NUM> that provide the features and functionality of base station <NUM>. Base station <NUM>, under control of controller/processor <NUM>, transmits and receives signals via wireless radios 1001a-t and antennas 234a-t. Wireless radios 1001a-t includes various components and hardware, as illustrated in <FIG> for base station <NUM>, including modulator/demodulators 232a-t, MIMO detector <NUM>, receive processor <NUM>, transmit processor <NUM>, and TX MIMO processor <NUM>.

At block <NUM>, the base station transmits, to a UE, a DCI scheduling a PDSCH. The PDSCH including a first transmission occasion and a second transmission occasion following the first transmission occasion during a single slot. The base station <NUM> may execute, under control of controller/processor <NUM>, DCI transmission logic <NUM> stored in memory <NUM>. The execution environment of DCI transmission logic <NUM> provides the functionality to transmits, to a UE, a DCI scheduling a PDSCH. The PDSCH including a first transmission occasion and a second transmission occasion following the first transmission occasion during a single slot. In some implementations, the DCI indicates two TCI states within a single slot.

At block <NUM>, the base station determines an overall processing time of the UE following a last symbol of the PDSCH. The base station <NUM> may execute, under control of controller/processor <NUM>, processing time determiner <NUM> stored in memory <NUM>. The execution environment of processing time determiner <NUM> provides the functionality to determine an overall processing time of the UE following a last symbol of the PDSCH. A portion of the overall processing time may be determined based on a mapping type of a first transmission occasion of the PDSCH, a mapping type of a second transmission occasion of the PDSCH, a processing capability of the UE, a length of the first transmission occasion, a length of the second transmission occasion, a number of symbols of the DCI that overlap the first transmission occasion, a number of symbols of the DCI that overlap the second transmission occasion, a symbol offset between the first transmission occasion and the second transmission occasion, or a combination thereof. For example, base station <NUM> may determine the portion of the overall processing time according to one or more of the six rules (e.g., alternatives) described above.

At block <NUM>, the base station schedules a HARQ-ACK from the UE at a time after the PDSCH that is greater than or equal to the overall processing time. The base station <NUM> may execute, under control of controller/processor <NUM>, HARQ-ACK scheduling logic <NUM> stored in memory <NUM>. The execution environment of HARQ-ACK scheduling logic <NUM> provides the functionality to schedule a HARQ-ACK from the UE at a time after the PDSCH that is greater than or equal to the overall processing time.

The functional blocks and modules described herein (e.g., the functional blocks and modules in <FIG>) may comprise processors, electronics devices, hardware devices, electronics components, logical circuits, memories, software codes, etc., or any combination thereof. In addition, features discussed herein relating to <FIG> may be implemented via specialized processor circuitry, via executable instructions, and/or combinations thereof.

Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps (e.g., the logical blocks in <FIG>) described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both.

The steps of a method or algorithm described in connection with the disclosure herein may be embodied directly in hardware, in a software module executed by a processor (e.g., directly, after compilation/conversion/interpretation, etc.), or in a combination of the two. An exemplary storage medium is coupled (e.g., communicatively, operatively, electronically, or otherwise) to the processor such that the processor can read information from, and write information to, the storage medium.

In one or more exemplary designs, the functions described may be implemented in hardware, software, or any combination thereof. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), hard disk, solid state disk, and bluray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.

Claim 1:
A method of wireless communication at a user equipment, UE (<NUM>), the method comprising:
receiving (<NUM>), from a network entity (<NUM>), a downlink control information, DCI, scheduling a physical downlink shared channel, PDSCH, the PDSCH including a first transmission occasion and a second transmission occasion following the first transmission occasion during a single slot, wherein the DCI is configured for scheduling transmission of a same transport block, TB, in the first transmission occasion and the second transmission occasion;
determining a processing time corresponding to the first transmission occasion; and
determining (<NUM>) an overall processing time following a last symbol of the PDSCH, wherein the overall processing time corresponds to the total time for the UE to decode the DCI that schedules the PDSCH, to receive the PDSCH and decode the TB included within the PDSCH, and to prepare a hybrid automatic repeat request acknowledgement, HARQ-ACK, corresponding to the PDSCH,
wherein the overall processing time comprises a first portion of processing time and a second portion of processing time, and wherein the second portion of processing time is the processing time corresponding to the first transmission occasion.