WO2022032511A1

WO2022032511A1 - Harq-process specific user equipment configuration for reduced capability complexity reduction

Info

Publication number: WO2022032511A1
Application number: PCT/CN2020/108607
Authority: WO
Inventors: Qiaoyu Li; Chao Wei; Hao Xu; Jing Dai; Chenxi HAO; Min Huang; Wei XI; Jing LEI; Huilin Xu; Changlong Xu; Wanshi Chen; Hwan Joon Kwon
Original assignee: Qualcomm Incorporated
Priority date: 2020-08-12
Filing date: 2020-08-12
Publication date: 2022-02-17

Abstract

Aspects presented herein may enable reduced capability UEs to support certain type of services with strict delay but limited throughput, while less parallel hardware or computational resources may be used by the reduced capability UEs. In one aspect, a UE reports, to a base station, a UE capability based on a HARQ process unit (e.g., the UE may indicate to the base station the number of available or maximum HARQ process unit (s) at the UE, etc. ). Then the UE receives downlink communication from the base station. Then the UE processes the downlink communication from the base station and providing HARQ feedback based on the reported UE capability (e.g., based on the number of available HARQ process unit (s) at the UE).

Description

HARQ-PROCESS SPECIFIC USER EQUIPMENT CONFIGURATION FOR REDUCED CAPABILITY COMPLEXITY REDUCTION

Technical Field

The present disclosure relates generally to communication systems, and more particularly, to wireless communication techniques involving hybrid automatic repeat request processing configurations (e.g., for a user equipment) .

Introduction

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR) . 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT) ) , and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB) , massive machine type communications (mMTC) , and ultra-reliable low latency communications (URLLC) . Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

SUMMARY

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication. In some aspects, the wireless communication may be performed at a UE. The apparatus reports (e.g., via a transceiver) , to a base station, a UE capability based on a HARQ process unit. For example, the UE may indicate to the base station the number of available or maximum HARQ process unit (s) . Then the apparatus processes the downlink communication from the base station and provides HARQ feedback based on the reported UE capability (e.g., based on the number of available HARQ process unit (s) ) .

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication. In some aspects, the wireless communication may be performed at a UE. The apparatus reports, to a base station, a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant. Then the apparatus receives the one or more grants from the base station. Then the apparatus receives an additional grant from the base station following the one or more grants by at least the duration of time.

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication. In some aspects, the wireless communication may be performed at a base station. The apparatus receives, from a UE, a UE capability based on a HPU. Then the apparatus transmits downlink communication to the UE. Then the apparatus receives HARQ feedback based on the UE capability.

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication. In some aspects, the wireless communication may be performed at a base station. The apparatus receives, from a UE, a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant. Then the apparatus transmits the one or more grants to the UE. Then the apparatus transmits an additional grant to the UE following the one or more grants by at least the duration of time.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network in accordance with aspects presented herein.

FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.

FIG. 2B is a diagram illustrating an example of DL channels within a subframe, in accordance with various aspects of the present disclosure.

FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.

FIG. 2D is a diagram illustrating an example of UL channels within a subframe, in accordance with various aspects of the present disclosure.

FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

FIG. 4 is a diagram illustrating an example of scheduling offsets in accordance with aspects presented herein.

FIG. 5 is a diagram illustrating an example of UE processing time in accordance with aspects presented herein.

FIG. 6 is a diagram illustrating an example of scheduling offsets based on UE processing time in accordance with aspects presented herein.

FIGs. 7A and 7B are diagrams illustrating examples of parallel computation in accordance with aspects presented herein.

FIG. 8 is a diagram illustrating an example of determining UE processing time capability in accordance with aspects presented herein.

FIG. 9 is a diagram illustrating an example of determining UE processing time capability in accordance with aspects presented herein.

FIG. 10 is a diagram illustrating an example of determining UE processing time capability in accordance with aspects presented herein.

FIG. 11 is a diagram illustrating an example of determining UE processing time capability in accordance with aspects presented herein.

FIG. 12 is a diagram illustrating an example of determining scheduling offsets in accordance with aspects presented herein.

FIG. 13 is a diagram illustrating an example of determining the processing time capability in accordance with aspects presented herein.

FIG. 14 is a diagram illustrating an example of determining the processing time capability in accordance with aspects presented herein.

FIG. 15 is a diagram illustrating an example of HARQ-process unit in accordance with aspects presented herein.

FIG. 16 is a diagram illustrating an example of DCI forbidden time in accordance with aspects presented herein.

FIG. 17 is a diagram illustrating an example of associating a BWP or a CC with HARQ-processes in accordance with aspects presented herein.

FIG. 18 is a flowchart of a method of wireless communication in accordance with aspects presented herein.

FIG. 19 is a diagram illustrating an example of a hardware implementation for an example apparatus in accordance with aspects presented herein.

FIG. 20 is a flowchart of a method of wireless communication in accordance with aspects presented herein.

FIG. 21 is a diagram illustrating an example of a hardware implementation for an example apparatus in accordance with aspects presented herein.

FIG. 22 is a flowchart of a method of wireless communication in accordance with aspects presented herein.

FIG. 23 is a diagram illustrating an example of a hardware implementation for an example apparatus in accordance with aspects presented herein.

FIG. 24 is a flowchart of a method of wireless communication in accordance with aspects presented herein.

FIG. 25 is a diagram illustrating an example of a hardware implementation for an example apparatus in accordance with aspects presented herein.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system (also referred to as a wireless wide area network (WWAN) ) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G Core (5GC) ) . The base stations 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station) . The macrocells include base stations. The small cells include femtocells, picocells, and microcells.

In certain aspects, the UE 104 may include a UE Capability Reporting Component 198. The component 198 can be configured to generate and/or transmit reports of a varying nature to other communication devices. In some arrangements, the component 198 may be configured to report one or more UE capabilities to a base station (e.g., 102/180) . According to some deployment options, each capability may include a set of one or more processing time parameters for a group of HARQ processes. Additionally and/or alternatively, the UE Capability Reporting component 198 may be configured to process the downlink communication from the base station based on a UE capability corresponding to the number of HARQ processes.

In certain aspects, the UE Capability Reporting Component 198 may be configured with a variety of capability information. As one example, the UE Capability Reporting Component 198 can be configured to report, to a base station, a UE capability based on a HARQ process unit (e.g., the UE may indicate to the base station the number of available or maximum HARQ process unit (s) or available computational resource for processing the HARQ at the UE, etc. ) . Additionally and/or alternatively, the UE Capability Reporting Component 198 may be configured to receive downlink communication from the base station and process the downlink communication from the base station and providing HARQ feedback based on the reported UE capability (e.g., based on the number of available HARQ process unit (s) or computational resources for processing the HARQ at the UE) .

The UE Capability Reporting Component 198 may alternatively or additional report additional types of capability information. As one example, in certain aspects, the UE Capability Reporting Component 198 may be configured to report, to a base station, a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant. Additionally and/or alternatively, the UE Capability Reporting 198 is configured to receive the one or more grants from the base station and an additional grant from the base station following the one or more grants by at least the duration of time.

Communication devices may also include scheduling features. In certain aspects, the base station 102/180 may include a Scheduling Component 199 configured to scheduling one or more delays for the UE 104 to process at least one of the PDSCH, the PUSCH, the HARQ process, or the retransmission of PDSCH, etc. The Scheduling Component 199 may schedule the one or more delays based on one or more UE capability, number of HARQ processes associated with or configured for the UE, whether the data transmission is associated with a BWP or CC, etc.

The base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) ) may interface with the EPC 160 through first backhaul links 132 (e.g., S1 interface) . The base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN) ) may interface with core network 190 through second backhaul links 184. In addition to other functions, the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity) , inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS) , subscriber and equipment trace, RAN information management (RIM) , paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 (e.g., X2 interface) . The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless.

The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102' may have a coverage area 110' that overlaps the coverage area 110 of one or more macro base stations 102. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) . The communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations 102 /UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) . The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .

Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) . D2D communication may be through a variety of wireless D2D communications systems, such as for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

The wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the STAs 152 /AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

The small cell 102' may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102' may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, or the like) as used by the Wi-Fi AP 150. The small cell 102', employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.

The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz –7.125 GHz) and FR2 (24.25 GHz –52.6 GHz) . The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz –300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.

A base station 102, whether a small cell 102' or a large cell (e.g., macro base station) , may include and/or be referred to as an eNB, gNodeB (gNB) , or another type of base station. Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies in communication with the UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for the path loss and short range. The base station 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate the beamforming.

The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182'. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 182” . The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 180 /UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180 /UE 104. The transmit and receive directions for the base station 180 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, and/or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services.

The base station may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a transmit reception point (TRP) , or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104. Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) . The UE 104 may also be referred to as a station, a mobile station, 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, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGs. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL) , where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 being configured with slot format 1 (with all UL) . While

subframes

3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI) , or semi-statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI) . Note that the description infra applies also to a 5G NR frame structure that is TDD.

Other wireless communication technologies may have a different frame structure and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms) . Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot may include 14 symbols, and for slot configuration 1, each slot may include 7 symbols. The symbols on DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to a single stream transmission) . The number of slots within a subframe is based on the slot configuration and the numerology. For slot configuration 0, different numerologies μ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For slot configuration 1, different numerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology μ, there are 14 symbols/slot and 2 ^μ slots/subframe. The subcarrier spacing and symbol length/duration are a function of the numerology. The subcarrier spacing may be equal to 2 ^μ*15 kHz, where μ is the numerology 0 to 4. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing. FIGs. 2A-2D provide an example of slot configuration 0 with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a particular numerology.

A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.

As illustrated in FIG. 2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and phase tracking RS (PT-RS) .

FIG. 2B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs) , each CCE including six RE groups (REGs) , each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET) . A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the aforementioned DM-RS. The physical broadcast channel (PBCH) , which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) /PBCH block (also referred to as SS block (SSB) ) . The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) . The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and paging messages.

As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH) . The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS) . The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and hybrid automatic repeat request (HARQ) ACK/NACK feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and/or UCI.

FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller/processor 375. The controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs) , RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression /decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) . The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318 TX. Each transmitter 318 TX may modulate an RF carrier with a respective spatial stream for transmission.

At the UE 350, each receiver 354 RX receives a signal through its respective antenna 352. Each receiver 354 RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) . The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.

The controller/processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer- readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with the DL transmission by the base station 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression /decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.

The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

The controller/processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 350. IP packets from the controller/processor 375 may be provided to the EPC 160. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with the UE Capability Reporting Component 198 of FIG. 1.

At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to perform aspects in connection with the Scheduling Component 199 of FIG. 1.

In addition to regular or higher capability devices, wireless communication may support reduced capability devices. Among others, examples of higher capability devices may include premium smartphones, V2X devices, URLLC devices, eMBB devices, etc. Among other examples, reduced capability devices may include wearables, industrial wireless sensor networks (IWSN) , surveillance cameras, low-end smartphones, etc. For example, NR communication systems may support both higher capability devices and reduced capability devices. A reduced capability device (e.g., reduced capability UE) may be referred to as an NR light device, a reduced capability NR device, a low-tier device, a lower tier device, etc. Reduced capability UEs may communicate based on various types of wireless communication (e.g., device type, machine type, dynamic operations type, reduced capability on/off indications, etc. ) . For example, smart wearables may transmit or receive communication based on low power wide area (LPWA) /mMTC, relaxed IoT devices may transmit or receive communication based on URLLC, sensors/cameras may transmit or receive communication based on eMBB, etc. For purpose of the present disclosure, the term “reduced capability” may be used to describe a UE with the reduced capability (e.g., reduced capability UE) . In some examples, the term “reduced capability” may be an indication transmitted from a UE to indicate that the UE may be operating as a reduced capability UE. For example, a UE may report a reduced capability to a base station, where the UE is indicating to the base station that it is a reduced capability UE, such as a reduced capability NR device, etc.

Reduced capability devices may include fewer, limited, and/or targeted communication abilities relative to other communication device types. By providing reduced capability devices with targeted communication abilities, such devices are provisioned to operate in a range of operational settings. In some examples, a reduced capability UE may have an uplink transmission power of at least 10 dB less than that a higher capability UE. As another example, a reduced capability UE may have reduced transmission bandwidth or reception bandwidth than other UEs. For instance, a reduced capability UE may have an operating bandwidth between 5 MHz and 20MHz for both transmission and reception, in contrast to other UEs which may have a bandwidth of up to 100 MHz bandwidth. As a further example, a reduced capability UE may have a reduced number of reception antennas in comparison to other UEs. For instance, a reduced capability UE may have only a single receive antenna and may experience a lower equivalent receive signal to noise ratio (SNR) in comparison to higher capability UEs that may have multiple antennas. Thus, a reduced capability UE may require PDCCH and/or PDSCH repetitions to compensate for the coverage loss in downlink. A reduced capability UEs may also have reduced computational complexity than other UEs. In addition, a reduced capability UE may be more delay tolerant, such that it may have a more enhanced power saving and battery life configuration.

A base station may configure a UE with one or more time-domain resources for receiving a data from the base station (e.g., via PDSCH) or for transmitting a data to the base station (e.g., via PUSCH) , where the base station may send the configuration to the UE using a PDCCH. The base station may further schedule various types of scheduling offsets or processing timelines for the UE such that the UE may have sufficient time to process the data, tune its beam (s) , provide feedback (e.g., HARQ ACK/NACK) , receive retransmissions, etc. FIG. 4 is a diagram 400 illustrating examples of scheduling offsets for a UE. A base station may schedule an offset for a UE between the time a downlink (DL) grant 402 or an uplink (UL) grant 410 is transmitted to the UE and the time the UE receives the corresponding PDSCH 404 (e.g., the DL data) or transmits the corresponding PUSCH 412 (e.g., the UL data) , where an offset K ₀ may indicate the delay (e.g., in slots) between the DL grant 402 reception and corresponding PDSCH 404 reception, and an offset K ₂ may indicate the delay between the UL grant 410 reception and the corresponding PUSCH 412 transmission. The base station may further schedule an additional offset K ₁ and/or offset K ₃ for the UE, where the offset K ₁ may indicate the delay between the PDSCH 404 reception and the corresponding HARQ feedback 406 (e.g., ACK/NACK) transmission on the UL, and the offset K ₃ may indicate the delay between the HARQ feedback 406 reception in the UL and the corresponding retransmission of the PDSCH 408 on the DL. A wireless communication may support up to sixteen HARQ-processes (e.g., HARQ feedback) per carrier component (CC) . The base station may indicate the values for offsets K ₀, K ₁ and K ₂ in the DCI, and the minimum value for offsets K ₀, K ₁ and K ₂ may be zero. UEs with lower capabilities may use longer offset as they may use a longer RF settling time for their beam weights to be set up, whereas UEs with higher capabilities may use shorter offsets.

In scheduling the aforementioned offsets (e.g., K ₀, K ₁, K ₂ and K ₃) , the base station may take the UE processing time into account. For example, in determining the offset K ₁, the base station may consider the UE processing time for the HARQ feedback (e.g., 406) after the UE receives the DL data over the PDSCH (e.g., 404) . Similarly, in determining the offset K ₂, the base station may consider the UE processing time for the PUSCH (e.g., 412) transmission after the reception of the corresponding UL grant (e.g., 410) . The UE processing time may be considered in terms of symbols together with an absolute time (e.g., in μs) , in addition to slots (e.g., K ₁, K ₂) . For example, as shown by diagram 500 in FIG. 5, a UE processing time N ₁ may indicate the number of OFDM symbols for the UE to process from the end of the PDSCH 504 reception to the earliest possible start of the corresponding HARQ feedback 506 (e.g., ACK/NACK) transmission from a UE 502’s perspective. A UE processing time N ₂ may indicate the number of OFDM symbols for the UE to process from the end of the PDCCH containing the UL grant 510 reception to the earliest possible start of the corresponding PUSCH 512 transmission from the UE 512’s perspective.

The baseline UE processing time capability (e.g., N ₁, N ₂) for slot-based scheduling may be determined based at least in part on the type of DM-RS and the subcarrier spacing (SCS) , such as illustrated by examples in Table 1 and Table 2 below. This may include or apply to carrier aggregation (CA) without cross-carrier scheduling and with single numerology for the PDCCH, the PDSCH, and the PUSCH and no UCI multiplexing.

Table 1 –Example of UE Processing Time and HARQ Timing (Capability #1)

Table 2 –Example of UE Processing Time and HARQ Timing (Capability #2)

The base station may determine the minimum value for the offset K ₁ and/or the offset K ₂ based on assumptions of a respective UE’s turn-around times (e.g., processing time N ₁, N ₂) . For a given configuration and numerology, a UE may indicate one or more capabilities for N ₁ and N ₂ to the base station, such as based on corresponding entry for N ₁ and N ₂ from either Table 1 or Table 2. For example, as shown by diagram 600 of FIG. 6, at 606, a UE 602 may select a processing time N ₁, N ₂ based on a UE capability or from a pre-defined table, such as from Table 1 or Table 2. At 608, the UE 602 may indicate the selected processing time to a base station 604. At 610, the base station 610 may determine the offsets K ₁ and K ₂ based on the received N ₁, N ₂. At 612, the base station 610 may indicate the offsets K ₁ and K ₂ to the UE 602, such as via a DCI in a PDCCH. At 614, the UE may apply the offset K ₁ in association with the HARQ feedback reporting and the offset K ₂ in association with the PUSCH transmission. For example, if the UE indicates to the base station a processing time N ₁ to be 24 symbols under 120 kHz SCS, the base station may assign at least one slot for the offset K ₁.

The aforementioned UE processing time capability reporting (e.g., at 608 of FIG. 6) requirement may force a parallel implementation (e.g., computation) for multiple HARQ-processes for the UE, where there may be up to sixteen HARQ-processes per CC. For example, as shown by diagram 700A of FIG. 7A, when multiple HARQ-processes (e.g., 702, 704) are simultaneously scheduled for the UE, the UE may prepare parallel hardware or compurgation resources to meet the (N ₁, N ₂) capability reported. In other words, the UE may process multiple PDSCHs and their corresponding HARQ feedback at the same time. Similarly, as shown by diagram 700B of FIG. 7B, when multiple PUSCHs (e.g., 706, 708, 710) are simultaneously scheduled for the UE for transmission, the UE may prepare multiple hardware or computation resources to meet the (N ₁, N ₂) capability reported, where the UE may process multiple PUSCH for transmission at the same time. This may increase the complexity or the computational requirement for the UE. To reduce the complexity or the computational requirement for the UE, such as for reduced capability UEs, a more relaxed capability reporting of the processing time (N ₁, N ₂) may be configured for the UE, where the UE may report or indicate a greater (e.g., longer) value for the (N ₁, N ₂) so that the UE may have more time to process the data or the HARQ feedback. However, this may restrict the service types (e.g., with respect to delay) that may be supported by the UE. At times, a UE may support some service types requiring strict delay, but may not necessarily require high throughput (e.g., industrial IoT) . For example, it may not be necessary for the UE to support all sixteen HARQ-processes for the strict delay. However, if the UE employs a more relaxed capability reporting (e.g., longer (N ₁, N ₂) ) , the reporting of the low capability may likely limit the delay. The service type for the UE may include eMBB, mMTC, and URLLC, etc.

Techniques discussed herein generally relate to communication scenarios involving scheduling offsets and delays. Aspects enable and provide flexible solutions that take into account a number of factors, such operational conditions, dynamic channel conditions, mobility aspects, etc. Aspects presented herein can improve efficiency and performance of device operations (e.g., scheduling data transmission and/or HARQ feedback for the UE) . In scenarios where a UE and/or a base station may determine a duration of offsets and/or delays, these determinations can base on various factors. These may include, but are not limited to, numbers of HARQ processes configured for a UE, whether UCI is multiplexed with a PUSCH, whether a UE is a reduced capability UE, and/or whether a TBS carrying the HARQ process (es) and the number of HARQ-process unit available, etc.

Aspects presented herein may provide approaches and techniques configured to balance between delay and complexity for reduced capability UEs. Aspects presented herein may enable reduced capability UEs to support certain types of services. In some scenarios, services may have a strict delay with varying throughput, and in some instances limited throughput. Additionally and/or alternatively, reduced capability UEs may contain less parallel hardware or computational resources relative to non-reduced capability UEs (e.g., full capability UEs) .

In one aspect, a UE may report the processing time (e.g., N ₁, N ₂) for a group of HARQ-processes (e.g., HARQ-Process Group Specific Processing Time Report) . In one example, the UE may report the capability regarding the processing time as shown by flowchart 800 of FIG. 8. At 802, the UE may divide the total number of HARQ-processes to be supported into N groups (e.g., G ₁, G ₂, G ₃ …G _N) . At 804, for the n ^th group (e.g., n is among 1 to N) , the UE may report capabilities for the processing time including at least one or any combination of the followings: 1) a minimum delay (e.g., in slots and/or symbols) between the DL grant and the corresponding PDSCH reception (e.g., K ₀) ; 2) a minimum delay between the PDSCH reception and the corresponding HARQ feedback (e.g., ACK/NACK) transmission on the UL (e.g., K ₁) ; 3) a minimum delay between the UL grant reception and the PUSCH transmission (e.g., K ₂) ; and 4) a minimum delay between the HARQ feedback reception in the UL and the corresponding retransmission of the PDSCH on the DL (e.g., K ₃) . In one configuration, the reported capabilities (e.g., processing time) may descend through a group-index. In addition, the number of HARQ-processes may be separately counted for the DL (e.g., DL grant) , the UL (e.g., UL grant) , and the HARQ feedback, and their respectively capabilities may also be separately reported for the DL, the UL and the HARQ feedback. For example, when the total number of active HARQ-processes is less than G ₁, the UE may expect the scheduled timeline to meet its reported capability for the group G ₁. When the total number of active HARQ-processes is greater than G ₁ but less than G ₂, the UE may expect G ₁ HARQ-processes to comprise a timeline to meet its reported capability for the group G ₁, and the others meeting its reported capability for group G ₂.

For example, as shown by diagram 900 of FIG. 9, the total number of HARQ-processes to be supported by the UE may be divided into three groups (e.g., G ₁, G ₂, G ₃) , where each group may correspond to a reported capability for processing time that is based on one or more criteria selected from options 1) to 4) above. The reported capability for processing time for each group may be in a descending order (e.g., through a group-index) , where each consecutive or succeeding group may have a longer processing time. For example, the reported capability for processing time for Group G ₁ is shorter (e.g., tighter) than Group G ₂, the report capability for processing time for Group G ₂ is shorter than Group G ₃, etc. (e.g., G ₁ < G ₂ < G ₃) . Group 1 may include or support up to 3 HARQ-processes, Group 2 may include or support up to 5 HARQ-processes, and Group 3 may include or support up to 8 HARQ-processes, etc. When there is a total of two active HARQ-processes (e.g., 2 < G ₁) , the UE may expect the scheduled timeline (e.g., by the base station) for all HARQ-processes (e.g., 2 HARQ-processes in total –HARQ #1 and #2) to meet its reported capability for Group 1. When there is a total of four active HARQ-processes (e.g., G1 < 5 < G2) , the UE may expect the scheduled timeline for the HARQ-processes in Group 1 (3 HARQ-processes in total –HARQ #1 to #3) to meet its reported capability (e.g., processing time) for Group 1, and the UE may expect the scheduled timeline for the HARQ-processes in Group 2 (1 HARQ-process in total –HARQ #4) to meet its reported capability for Group 2. When there is a total of nine active HARQ-processes (e.g., G ₁ + G ₂ < 9 < G ₃) , the UE may expect the scheduled timeline for HARQ-processes in Group 1 (3 HARQ-processes in total –HARQ #1 to #3) and for the HARQ-processes in Group 2 (5 HARQ-processes in total –HARQ #4 to #8) to meet its reported capability for Group 1 and Group 2 respectively, and the UE may expect the scheduled timeline for HARQ-processes in Group 3 (1 HARQ-process in total –HARQ #9) to meet its reported capability for Group 3, etc. In addition, a HARQ-process may be defined as an active HARQ-process based on whether the associated HARQ Round Trip Time (RTT) timer is running. The RTT timer may specify the minimum amount of transmission time intervals (TTIs) before a DL HARQ retransmission is expected by the UE. For example, the UE may not monitor for the PDCCH while the HARQ RTT timer is running, and the UE may resume PDCCH reception after the HARQ RTT timer expires.

In addition, the total number of active HARQ processes may be calculated separately for an uplink grant, a downlink grant, and a HARQ feedback, and the number of active HARQ processes may be determined based on one or more of: the number of HARQ processes that have a running HARQ RTT timer, the number of HARQ processes that have DL grant DCI decoded but their corresponding PDSCHs have not been received by the UE, the number of HARQ processes that have UL grant DCI decoded but their corresponding physical uplink shared channels (PUSCHs) have not been transmitted, and the number of HARQ processes in which the UE has received a PDSCH but a corresponding scheduled HARQ feedback has not been reported, etc.

In another aspect, a UE may report the processing time (e.g., N ₁, N ₂) based on one or more levels associating with active HARQ-processes. For example, the UE may report capability regarding the processing time as shown by flowchart 1000 of FIG. 10. At 1002, the UE may divide the number of active HARQ-processes into N levels, where the n ^th level may comprises H _n active HARQ-processes. At 1004, for the n ^th level, the UE may report capabilities for processing time, including at least one or any combination of the followings options: 1) a minimum delay (e.g., in slots and/or symbols) between the DL grant and the corresponding PDSCH reception (e.g., K ₀) ; 2) a minimum delay between the PDSCH reception and the corresponding HARQ feedback (e.g., ACK/NACK) transmission on the UL (e.g., K ₁) ; 3) a minimum delay between the UL grant reception and the PUSCH transmission (e.g., K ₂) ; and 4) a minimum delay between the HARQ feedback reception in the UL and the corresponding retransmission of the PDSCH on the DL (e.g., K ₃) . The number of HARQ-processes may be separately counted for the DL (e.g., DL grant) , the UL (e.g., UL grant) , and the HARQ feedback, and their respectively capabilities may also be separately reported for the DL, the UL and the HARQ feedback. Higher capabilities (e.g., shorter processing time) may be reported for levels with lower H _n (e.g., less HARQ-processing) . For examples, if there are more HARQ-processes for the UE, the processing time may be looser (e.g., longer) . Similarly, a HARQ-process may be defined as an active HARQ-process based on whether the associated HARQ RTT timer is running, where the total number of active HARQ processes may be calculated separately for an uplink grant, a downlink grant, and a HARQ feedback. The number of active HARQ processes may also be determined based on one or more of: the number of HARQ processes that have a running HARQ RTT timer, the number of HARQ processes that have DL grant DCI decoded but their corresponding PDSCHs have not been received by the UE, the number of HARQ processes that have UL grant DCI decoded but their corresponding physical uplink shared channels (PUSCHs) have not been transmitted, and the number of HARQ processes in which the UE has received a PDSCH but a corresponding scheduled HARQ feedback has not been reported, etc.

For example, as shown by diagram 1100 of FIG. 11, the total number of HARQ-processes to be supported by the UE may be divided into three levels, where each level may correspond to a reported capability for processing time that is based on one or more criteria selected from options 1) to 4) above. The reported capability for processing time may be longer for more active HARQ-processes, and the reported capability for processing time may be shorter for fewer active HARQ-processes. For example, Level 1 may comprise up to 3 HARQ-processes and the report capability for the processing time for Level 1 is shorter (e.g., tighter) than Level 2; Level 2 may comprise up to 6 HARQ-processes and the report capability for the processing time for Level 2 is shorter than Level 3 but longer than Level 1; and Level 3 may comprise up to 13 HARQ-processes and may have the longest processing time such that Level 1 < Level 2 < Level 3 in terms of the processing time. When there is a total of two active HARQ-processes (e.g., 2 < Level 1) , the UE may expect the scheduled timeline (e.g., by the base station) for all HARQ-processes to meet its reported capability for Level 1. When there is a total of five active HARQ-processes (e.g., Level 1 < 5 < Level 2) , the UE may expect the scheduled timeline for all HARQ-processes to meet its reported capability for Level 2. When there is a total of nine active HARQ-processes (e.g., Level 2 < 9 < Level 3) , the UE may expect the scheduled timeline for all HARQ-processes to meet its reported capability for Level 3, etc.

In this configuration, the UE may determine the HARQ-processing timeline dynamically based on the number of active HARQ-processes (e.g., by selecting appropriate level and indicating corresponding processing time) . However, in some instances, there might be a misalignment between the base station and the UE when some signaling (e.g., DCI signal) fails to be received by the UE and/or the base station. Thus, as an alternative, a Semi-Persistent Scheduling (SPS) may be configured for the UE through the RRC configuration, such that the UE may be SPS configured to be expected with a scheduled timeline to meet its reported capability for the n ^th level. For example, the base station may configure the UE to expect eight HARQ-processes for a certain duration, then the UE may expect the scheduled timeline within this duration is based on its reported capability for eight HARQ-processes (e.g., Level 3 -between 7 and 13 HARQ-processes) . This may reduce and avoid misalignment in data transmission between the UE and the base station when certain signaling is not received by the UE or the base station.

In another aspect, an additional slot offset (e.g., scheduling) or an adjusted offset may be applied for reduced capability UEs. In some examples, the offset may be dedicated for reduced capability UEs. For example, the UE may expect the values of K ₀/K ₁/K ₂/K ₃ to be increased with K _{0_increase}/K _{1_increase}/K _{2_increase}/K _{3_increase} slot (s) , depending on at least one or any combination of the followings: 1) the UE reports itself as a reduced capability UE; and 2) the number of active HARQ-processes exceeds a threshold value N _HARQ, where the threshold value N _HARQ could be determined based on one or more of the followings: further UE capability reporting, base station configuration, and/or predefined, etc.

FIG. 12 is a diagram 1200 illustrating an example of scheduling offset for the reduced capability UE. For example, the offset values of K ₀/K ₁/K ₂/K ₃ for normal UE may be 2/2/3/4 slots respectively. At 1206, a UE 1202 may indicate a reduced capability to a base station 1204, e.g., indicating that the UE 1202 is a reduced capability UE. At 1208, the base station 1204 may determine whether to apply a longer offset based on whether the UE 1202 is a reduced capability UE and/or based on whether the number of active HARQ-processes exceeds a threshold (e.g., N _HARQ) . For example, the base station may determine to schedule communication for the UE 1202 using one or more longer offset values based on the UE being a reduced capability UE. In another example, the base station may determine to schedule communication for the UE 1202 using longer offset value (s) based on the number of active HARQ processes exceeding the threshold. In another example, the base station may determine to schedule communication for the UE 1202 using longer offset value (s) based on the UE being a reduced capability UE and the number of active HARQ processes exceeding the threshold.

If the base station 1204 determines to apply longer offset, at 1210, the base station 1204 may configure a dedicated offset (e.g., longer offset) K _{0_increase}/K _{1_increase}/K _{2_increase}/K _{3_increase} for the UE 1202, which may be 3/3/5/7 slots respectively. On the other hand, if the base station 1204 determines not to apply longer offset, at 1210, the base station 1204 may configure a regular offset K ₀/K ₁/K ₂/K ₃ for the UE 1202, which may be 2/2/3/4 slots respectively.

The base station 1204 may configure a regular offset for a reduced capability UE when the number of active HARQ-processes does not exceed the threshold, and the base station 1204 may also configure a dedicated offset for a non-reduced capability UE when the number of active HARQ-processes exceeds the threshold. The values for K _{0_increase}, K _{1_increase}, K _{2_increase}, K _{3_increase} may be determined based on one or more of the followings: further UE capability reporting, a base station configuration, and/or a predefined value, etc. Aspects presented here may avoid or minimize the impact on the processing time N ₁ and N ₂ for regular UEs (e.g., the processing time identified in Table 1 and Table 2 may remain the same) .

Similarly, a HARQ-process may be defined as an active HARQ-process based on whether the associated HARQ RTT timer is running, where the total number of active HARQ processes may be calculated separately for an uplink grant, a downlink grant, and a HARQ feedback. The number of active HARQ processes may also be determined based on one or more of: the number of HARQ processes that have a running HARQ RTT timer, the number of HARQ processes that have DL grant DCI decoded but their corresponding PDSCHs have not been received by the UE, the number of HARQ processes that have UL grant DCI decoded but their corresponding physical uplink shared channels (PUSCHs) have not been transmitted, and the number of HARQ processes in which the UE has received a PDSCH but a corresponding scheduled HARQ feedback has not been reported, etc.

In another aspect, the processing time reported by the UE may be based on the transport block size (TBS) (e.g., TBS Dependent Processing Time) . In one example, a UE may report the capability regarding the processing time as shown by flowchart 1300 of FIG. 13. At 1302, the UE may divide the supported TBS into N groups, such as in an ascending TBS order (e.g., G ₁, G ₂, G ₃ …G _N) . At, 1304, for the n ^th group (e.g., n is among 1 to N) , the UE may report capabilities for the processing time including at least one or any combination of the following options: 1) a minimum delay (e.g., in slots and/or symbols) between the DL grant and the corresponding PDSCH reception (e.g., K ₀) ; 2) a minimum delay between the PDSCH reception and the corresponding HARQ feedback (e.g., ACK/NACK) transmission on the UL (e.g., K ₁) ; 3) a minimum delay between the UL grant reception and the PUSCH transmission (e.g., K ₂) ; and 4) a minimum delay between the HARQ feedback reception in the UL and the corresponding retransmission of the PDSCH on the DL (e.g., K ₃) . For example, if one or more HARQ-processes are associated with a larger TBS, a larger (e.g., longer) processing time may be configured for these HARQ-processes, whereas if one or more HARQ-processes are associated with a smaller TBS, a looser (e.g., shorter) processing time may be configured for the these HARQ-processes, etc.

In another aspect, the PUSCH processing time for the UE may be dependent on a PUSCH type. As one example, the PUSCH processing time may be based on whether a UCI is multiplexed with the PUSCH. For example, a UE may report the capability regarding the processing time as shown by flowchart 1400 of FIG. 14. At 1402, the UE may divide multiple PUSCHs into different types of PUSCHs and may indicate different processing capabilities for the different types of PUSCHs. As an example, the UE may divide multiple PUSCHs into a first type of PUSCH with UCI-multiplexing and a second type of PUSCH without UCI-multiplexing. At 1404, the UE may separately report minimum delay (e.g., in slots and/or symbols) between the UL grant reception and the PUSCH transmission for the two types of PUSCHs (e.g., PUSCH with or without UCI-multiplexing) . As the PUSCHs with UCI-multiplexing may take longer time to process by the UE than PUSCHs without UCI-multiplexing, the base station may schedule the UE for PUSCHs with UCI-multiplexing based on a longer (e.g., a more relaxed) processing time.

The UE may perform various measurements for a channel and report the measurements to a base station in channel state information (CSI) report. The UE may process or calculate the CSI report using one or more CSI Processing Unit (CPU) . If the UE supports simultaneous CSI calculations (e.g., processing) , the UE may indicate to the base station the number of simultaneous CSI calculations N _CPU it supports. If a number of L CPUs are occupied for calculation of the CSI reports in a given OFDM symbol, the UE may have a number of (N _CPU –L) unoccupied CPUs.

In another aspect, the UE may calculate or indicate a HARQ-processing capability based on HARQ Processing Unit (HPU) , where the HPU may be used to implicitly indicate the computational resources per HARQ-process. As shown by diagram 1500 of FIG. 15, at 1506, a UE 1502 may report a capability (e.g., indicate) to a base station 1504 the number of supported simultaneous HARQ-processes N _HPU for the UE.If a number of L HPUs are occupied for calculation of the UL-grant, the DL-grant, and/or the PDSCH-decoding in a given duration (e.g., one or more OFDM symbol (s) or slot (s) , etc. ) , the UE may have a number of (N _HPU-L) unoccupied HPUs. The UE may separately report capabilities for the UL-grant, the DL-grant, and the PDSCH-decoding, respectively. After the UE 1502 reports the capabilities (e.g., maximum number of supported simultaneous HARQ-processes N _HPU or number of unoccupied HPUs (N _HPU-L) ) to the base station 1504, at 1508, the base station 1504 may determine the number of unoccupied HPU for the UE 1502 (e.g., if the UE 1502 indicates the maximum number of HPU to the base station 1504) or the base station 1504 may determine whether the UE 1502 has any unoccupied HPU(s) (e.g., if the UE 1502 indicates the number of unoccupied HPU (s) to the base station 1504) .

Then, at 1510, the base station 1504 may schedule the offset, DL/UL grant, and/or HARQ feedback for the UE 1502 based on the number of unoccupied HPU. For example, for the UL, the UE may not be expected to receive more UL-grant DCIs when the UE has zero unoccupied HPUs or the unoccupied HPU is below a threshold for the UL. Similarly, for the DL, the UE may not be expected to compute HARQ feedback (e.g., ACK/NACK) for the PDSCH (or receive more DL-grant DCIs) when the UE has zero unoccupied HPUs or the unoccupied HPU is below a threshold for the DL.

At 1512, the UE 1502 may receive downlink communication from the base station 1504, and then at 1514, the UE 1502 may process the downlink communication from the base station 1504 and/or providing HARQ feedback based on the reported UE capability.

In another aspect, the UE processing time may be determined based at least in part on a DCI forbidden time. The “DCI forbidden time” may refer to a time period during which the UE does not expect to receive a DCI with an UL or DL grant. The DCI forbidden time may correspond to a period of time during which the base station is limited from sending, or does not send, DCI scheduling UL or DL communication for the UE.

In one example, after the UE receives a DL or UL grant DCI, the UE may not expect to receive another DL or UL grant within a duration of time T (i.e., the DCI forbidden time following the prior DL or UL grant DCI) . The duration T may be determined and/or reported by the UE as a UE capability. For example, as shown by diagram 1600 of FIG. 16, at 1606, a UE 1602 may indicate a DCI Forbidden Time Duration T or T _combination (e.g., for multiple DCIs) to a base station 1604.

At 1608, after the UE receives a DL or UL grant DCI or N DL/UL grant DCIs, the UE may not expect to receive another DL or UL grant DCI (s) (e.g., at 1610) within the duration T or the duration T _combination. The base station may refrain from sending DCI with another UL or DL grant to the UE during the duration T or the duration T _combination. Both the duration T _combination (e.g., for group DCI) and the duration T (e.g., for single DCI) may be reported by the UE to the base station as UE capabilities. In other words, the base station 1604 may wait to transmit one or more DCI during the duration T or the duration T _combination. The UE may report the UE’s capability for the DCI forbidden time separately for an UL grant and a DL grant.

In another aspect, the timing management (e.g., processing time) and the maximum number of HARQ-processes to be configured for the UE may be based on the BWP for the communication and/or the CC for the communication (e.g., BWP/CC Specific timing management) . For example, as shown by diagram 1700 of FIG. 17, for a first BWP or CC 1702, a maximum number of active HARQ-processes (e.g., 16) may be defined for or associated with the first BWP or CC 1702, where a longer processing time (e.g., N _{1_increase} or N _{2_increase}, etc. ) may be provided for the first BWP or CC 1702 as it is associated with a higher maximum number of active HARQ-processes. For a second BWP or CC 1704, another maximum number of active HARQ-processes (e.g., 4) may be defined for or associated with the second BWP or CC 1704, where there may be no change to the existing timing management (e.g., standard or original processing time N ₁ or N ₂ is used) . Thus, the UE may report to the base station one or more processing timing capabilities dependent on one or more HARQ processes for the first BWP or CC 1702 and the processing timing capability independent of the number of HARQ processes for the second BWP or CC 1704 (e.g., a standard or a default value) . The UE may then process a downlink communication based on the UE capability corresponding to the number of HARQ processes if the downlink communication is received in the first BWP/CC, and the UE may process the downlink communication using processing times that are not dependent on the number of HARQ processes if the downlink communication is received in the second BWP/CC, etc. The maximum number of HARQ processes in the first BWP/CC and in the second BWP/CC may be configured by the base station via RRC configuration.

FIG. 18 is a flowchart 1800 of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., the

UE

104, 350, 502, 602, 1202, 1502, 1602; a processing system, which may include the memory 360 and which may be the entire UE 350 or a component of the UE 350, such as the TX processor 368, the RX processor 356, and/or the controller/processor 359) . Optional aspects are illustrated with a dashed line. The method may enable the UE to report maximum or available computational resources for processing one or more HARQ-processes, and then the UE may expect scheduling based on the reported computational resources.

At 1802, the UE may report, to a base station, a UE capability based on a HARQ process unit (e.g., the UE may indicate to the base station the number of available or maximum HARQ process unit (s) or available computational resource for processing the HARQ at the UE, etc. ) , such as described in connection with FIG. 15. For example, at 1506, the UE 1502 may report number of supported simultaneous HARQ-processes to the base station 1504. The UE capability may be based on processing an UL grant, processing an uplink grant, processing a physical downlink shared channel. After reporting to the base station about the number of unoccupied HARQ-process units, the UE may receive a scheduling offset from the base station based on a number of unoccupied HARQ-process units.

In one configuration, the UE may determine a number of unoccupied HPUs in a duration of time based on the number of supported simultaneous HARQ processes and a current number of occupied HPUs for processing one or more of an uplink grant, a downlink grant, or a physical downlink shared channel. In such configuration, the duration may be based on one or more symbols and/or slots. In such configuration, the UE may not receive additional uplink grants if the UE has no unoccupied HPUs for uplink. In such configuration, the UE may not determine HARQ feedback for a PDSCH if the UE has no unoccupied HPUs for downlink. In such configuration, the UE may not receive additional downlink grants for a PDSCH if the UE has no unoccupied HPUs for downlink.

At 1804, the UE may receive downlink communication from the base station, such as described in connection with FIG. 15. For example, at 1512, the UE 1502 may receive a downlink communication from the base station 1504.

At 1806, the UE may process the downlink communication from the base station and provide HARQ feedback based on the reported UE capability (e.g., based on the number of available HARQ process unit (s) or computational resources for processing the HARQ at the UE) , such as described in connection with FIG. 15. For example, at 1514, the UE 1502 may process the downlink communication from the base station 1504 and provide HARQ feedback based on the reported UE capability.

FIG. 19 is a diagram 1900 illustrating an example of a hardware implementation for an apparatus 1902. The apparatus 1902 is a UE and includes a cellular baseband processor 1904 (also referred to as a modem) coupled to a cellular RF transceiver 1922 and one or more subscriber identity modules (SIM) cards 1920, an application processor 1906 coupled to a secure digital (SD) card 1908 and a screen 1910, a Bluetooth module 1912, a wireless local area network (WLAN) module 1914, a Global Positioning System (GPS) module 1916, and a power supply 1918. The cellular baseband processor 1904 communicates through the cellular RF transceiver 1922 with the UE 104 and/or BS 102/180. The cellular baseband processor 1904 may include a computer-readable medium /memory. The computer-readable medium /memory may be non-transitory. The cellular baseband processor 1904 is responsible for general processing, including the execution of software stored on the computer-readable medium /memory. The software, when executed by the cellular baseband processor 1904, causes the cellular baseband processor 1904 to perform the various functions described supra. The computer-readable medium /memory may also be used for storing data that is manipulated by the cellular baseband processor 1904 when executing software. The cellular baseband processor 1904 further includes a reception component 1930, a communication manager 1932, and a transmission component 1934. The communication manager 1932 includes the one or more illustrated components. The components within the communication manager 1932 may be stored in the computer-readable medium /memory and/or configured as hardware within the cellular baseband processor 1904. The cellular baseband processor 1904 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359. In one configuration, the apparatus 1902 may be a modem chip and include just the baseband processor 1904, and in another configuration, the apparatus 1902 may be the entire UE (e.g., see 350 of FIG. 3) and include the aforediscussed additional modules of the apparatus 1902.

The communication manager 1932 includes a reporting component 1940 that is configured to report, to a base station, a UE capability based on a HARQ process unit, e.g., as described in connection with 1802 of FIG. 18. The communication manager 1932 further includes a receiving component 1942 that is configured to receive downlink communication from the base station, e.g., as described in connection with 1804 of FIG. 18. The communication manager 1932 further includes a processing component 1944 that is configured to process the downlink communication from the base station and providing HARQ feedback based on the reported UE capability, e.g., as described in connection with 1806 of FIG. 18.

The apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowchart of FIG. 18. As such, each block in the aforementioned flowchart of FIG. 18 may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof. In one configuration, the apparatus 1902, and in particular the cellular baseband processor 1904, includes means for reporting, to a base station, a UE capability based on a HARQ process unit. The apparatus 1902 includes means for processing the downlink communication from the base station and providing HARQ feedback based on the reported UE capability. The aforementioned means may be one or more of the aforementioned components of the apparatus 1902 configured to perform the functions recited by the aforementioned means. As described supra, the apparatus 1902 may include the TX Processor 368, the RX Processor 356, and the controller/processor 359. As such, in one configuration, the aforementioned means may be the TX Processor 368, the RX Processor 356, and the controller/processor 359 configured to perform the functions recited by the aforementioned means.

FIG. 20 is a flowchart 2000 of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., the

UE

104, 350, 502, 602, 1202, 1502, 1602; a processing system, which may include the memory 360 and which may be the entire UE 350 or a component of the UE 350, such as the TX processor 368, the RX processor 356, and/or the controller/processor 359) . Optional aspects are illustrated with a dashed line. The method may enable the UE to indicate a duration to a base station in which the base station may be refrained from transmitting a DL or a UL grant DCI to the UE during the indicated duration.

At 2002, the UE may report, to a base station, a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant, such as described in connection with FIG. 16. For example, at 1606, the UE 1602 may transmit a DCI forbidden time duration T or T _combination (for multiple DCIs) to the base station 1604. The UE may report the duration of time for one or more uplink grants, for one or more downlink grants, or both, where the duration of time may be reported to the base station as a UE capability. In addition, the duration of time may apply to reception of a single grant or to reception of multiple grants.

At 2004, the UE may receive the one or more grants from the base station, such as described in connection with FIG. 16. For example, at 1608, the UE 1602 may receive first one or more grants from the base station 1604.

At 2006, the UE may receive an additional grant from the base station following the one or more grants by at least the duration of time, such as described in connection with FIG. 16. For example, at 1608, the UE 1602 may receive second one or more grants from the base station 1604 after the DCI forbidden time duration expires.

In one configuration, as shown in connection with FIG. 17, the UE may report a maximum number of HARQ processes based on a BWP. In such configuration, the UE may report one or more processing timing capabilities dependent on one or more HARQ processes for a first BWP and a processing timing capability independent of the number of HARQ processes for a second BWP. Then the UE may process the downlink communication based on the one or more processing timing capabilities corresponding to the number of HARQ processes if the downlink communication is received in the first BWP and processes the downlink communication using the processing timing capability independent of the number of HARQ processes if the downlink communication is received in the second BWP. The maximum number of HARQ processes in the first BWP and in the second BWP is RRC configured by the base station. Additionally, or optionally, the UE may also report a maximum number of HARQ processes based on a CC. Similarly, the UE may report one or more processing timing capabilities dependent on one or more HARQ processes for a first CC and a processing timing capability independent of the number of HARQ processes for a second CC. Then the UE may processes the downlink communication based on the one or more processing timing capabilities corresponding to the number of HARQ processes if the downlink communication is received in the first CC and processes the downlink communication using the processing timing capability independent of the number of HARQ processes if the downlink communication is received in the second CC. The maximum number of HARQ processes in the first CC and in the second CC may also be RRC configured by the base station.

FIG. 21 is a diagram 2100 illustrating an example of a hardware implementation for an apparatus 2102. The apparatus 2102 is a UE and includes a cellular baseband processor 2104 (also referred to as a modem) coupled to a cellular RF transceiver 2122 and one or more subscriber identity modules (SIM) cards 2120, an application processor 2106 coupled to a secure digital (SD) card 2108 and a screen 2110, a Bluetooth module 2112, a wireless local area network (WLAN) module 2114, a Global Positioning System (GPS) module 2116, and a power supply 2118. The cellular baseband processor 2104 communicates through the cellular RF transceiver 2122 with the UE 104 and/or BS 102/180. The cellular baseband processor 2104 may include a computer-readable medium /memory. The computer-readable medium /memory may be non-transitory. The cellular baseband processor 2104 is responsible for general processing, including the execution of software stored on the computer-readable medium /memory. The software, when executed by the cellular baseband processor 2104, causes the cellular baseband processor 2104 to perform the various functions described supra. The computer-readable medium /memory may also be used for storing data that is manipulated by the cellular baseband processor 2104 when executing software. The cellular baseband processor 2104 further includes a reception component 2130, a communication manager 2132, and a transmission component 2134. The communication manager 2132 includes the one or more illustrated components. The components within the communication manager 2132 may be stored in the computer-readable medium /memory and/or configured as hardware within the cellular baseband processor 2104. The cellular baseband processor 2104 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359. In one configuration, the apparatus 2102 may be a modem chip and include just the baseband processor 2104, and in another configuration, the apparatus 2102 may be the entire UE (e.g., see 350 of FIG. 3) and include the aforediscussed additional modules of the apparatus 2102.

The communication manager 2132 includes a reporting component 2140 that is configured to report, to a base station, a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant, e.g., as described in connection with 2002 of FIG. 20. The communication manager 2132 further includes a receiving component 2142 that is configured to receive the one or more grants from the base station, e.g., as described in connection with 2004 of FIG. 20. The communication manager 2132 further includes a receiving component 2144 that is configured to receive an additional grant from the base station following the one or more grants by at least the duration of time, e.g., as described in connection with 2006 of FIG. 20.

The apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowchart of FIG. 20. As such, each block in the aforementioned flowchart of FIG. 20 may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof. In one configuration, the apparatus 2102, and in particular the cellular baseband processor 2104, includes means for reporting, to a base station, a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant. The apparatus 2102 includes means for receiving the one or more grants from the base station. The apparatus 2102 includes means for receiving an additional grant from the base station following the one or more grants by at least the duration of time. The aforementioned means may be one or more of the aforementioned components of the apparatus 2102 configured to perform the functions recited by the aforementioned means. As described supra, the apparatus 2102 may include the TX Processor 368, the RX Processor 356, and the controller/processor 359. As such, in one configuration, the aforementioned means may be the TX Processor 368, the RX Processor 356, and the controller/processor 359 configured to perform the functions recited by the aforementioned means.

Figure 22 is a flowchart 2200 of a method of wireless communication. The method may be performed by a base station or a component of a base station (e.g.,

base station

102, 180, 310, 604, 1204, 1504, 1604; which may include the memory 376 and which may be the entire base station 310 or a component of the base station 310, such as the TX processor 316, the RX processor 370, and/or the controller/processor 375) . Optional aspects are illustrated with a dashed line. The method may enable the base station to schedule one or more offsets for a UE based at least in part on the UE’s available computational resources for processing one or more HARQ-processes.

At 2202, the base station may receive, from a UE, a UE capability based on a HPU, where the UE capability may include a number of supported simultaneous HARQ processes based on the HPU, such as described in connection with FIG. 15. In one configuration, the UE capability may be based on processing an uplink grant, processing an uplink grant, and/or processing a physical downlink shared channel.

At 2204, the base station may transmit downlink communication to the UE, such as described in connection with FIG. 15. In one configuration, prior to transmit the downlink communication, the base station may determine a number of unoccupied HPUs for the UE in a duration of time based on the number of supported simultaneous HARQ processes and a current number of occupied HPUs for processing one or more of an uplink grant, a downlink grant, or a physical downlink shared channel. In such configuration, the duration may be based on one or more symbols and/or slots. In such configuration, the base station may not transmit additional uplink grants if the UE has no unoccupied HPUs for uplink. Similarly, the base station may not transmit additional downlink grants for a PDSCH if the UE has no unoccupied HPUs for downlink. Thus, the base station may transmit a scheduling offset to the UE based on a number of unoccupied HARQ-process units.

At 2206, the base station may receive HARQ feedback based on the UE capability, such as described in connection with FIG. 15. However, the base station may not receive HARQ feedback for a PDSCH if the UE has no unoccupied HPUs for downlink.

In another configuration, as described in connection with FIG. 17, the base station may receive an indication of a maximum number of HARQ processes based on a BWP or a CC, such as described in connection with FIG. 17. In such configuration, the base station may receive a report of one or more processing timing capabilities dependent on one or more HARQ processes for a first BWP or CC and a processing timing capability independent of the number of HARQ processes for a second BWP or CC. Then the base station may schedule the downlink communication based on the one or more processing timing capabilities corresponding to the number of HARQ processes if the downlink communication is received in the first BWP or CC and schedules the downlink communication using the processing timing capability independent of the number of HARQ processes if the downlink communication is received in the second BWP or CC. The base station may configure the maximum number of HARQ processes in the first BWP or CC and in the second BWP or CC via an RRC for the UE.

FIG. 23 is a diagram 2300 illustrating an example of a hardware implementation for an apparatus 2302. The apparatus 2302 is a base station and includes a baseband unit 2304. The baseband unit 2304 may communicate through a cellular RF transceiver with the UE 104. The baseband unit 2304 may include a computer-readable medium /memory. The baseband unit 2304 is responsible for general processing, including the execution of software stored on the computer-readable medium /memory. The software, when executed by the baseband unit 2304, causes the baseband unit 2304 to perform the various functions described supra. The computer-readable medium /memory may also be used for storing data that is manipulated by the baseband unit 2304 when executing software. The baseband unit 2304 further includes a reception component 2330, a communication manager 2332, and a transmission component 2334. The communication manager 2332 includes the one or more illustrated components. The components within the communication manager 2332 may be stored in the computer-readable medium /memory and/or configured as hardware within the baseband unit 2304. The baseband unit 2304 may be a component of the BS 310 and may include the memory 376 and/or at least one of the TX processor 316, the RX processor 370, and the controller/processor 375.

The communication manager 2332 includes a receiving component 2340 that is configured to receive, from a UE, a UE capability based on a HPU, e.g., as described in connection with 2202 of FIG. 22. The communication manager 2332 further includes a transmitting component 2342 that is configured to transmit downlink communication to the UE, e.g., as described in connection with 2204 of FIG. 22. The communication manager 2332 includes a receiving component 2344 that is configured to receive HARQ feedback based on the UE capability, e.g., as described in connection with 2206 of FIG. 22.

The apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowchart of FIG. 22. As such, each block in the aforementioned flowcharts of FIG. 22 may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof. In one configuration, the apparatus 2302, and in particular the baseband unit 2304, includes means for receiving, from a UE, a UE capability based on a HPU. The apparatus 2302 includes means for transmitting downlink communication to the UE. The apparatus 2302 includes means for receiving HARQ feedback based on the UE capability. The aforementioned means may be one or more of the aforementioned components of the apparatus 2302 configured to perform the functions recited by the aforementioned means. As described supra, the apparatus 2302 may include the TX Processor 316, the RX Processor 370, and the controller/processor 375. As such, in one configuration, the aforementioned means may be the TX Processor 316, the RX Processor 370, and the controller/processor 375 configured to perform the functions recited by the aforementioned means.

Figure 24 is a flowchart 2400 of a method of wireless communication. The method may be performed by a base station or a component of a base station (e.g.,

base station

102, 180, 310, 604, 1204, 1504, 1604; which may include the memory 376 and which may be the entire base station 310 or a component of the base station 310, such as the TX processor 316, the RX processor 370, and/or the controller/processor 375) . Optional aspects are illustrated with a dashed line. The method may enable the base station to refrain from transmitting a DL or a UL grant DCI to a UE in a duration of time indicated by the UE.

At 2402, the base station may receive, from a UE, a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant, such as described in connection with FIG. 16. In one configuration, the base station may receive the duration of time for one or more uplink grants and/or one or more downlink grants. In such configuration, the duration of time may be indicated to the base station as a UE capability by the UE, where the base station may refrain from sending the additional grant to the UE during the duration of time following the one or more grants. The duration of time in which the base station is refrained from sending the additional grant may apply to transmission of a single grant or multiple grants.

At 2404, the base station may transmit the one or more grants to the UE, such as described in connection with FIG. 16. However, the base station may not transmit additional grant with the duration of time after transmitting the one or more grants to the UE.

At 2406, after the duration of time expires, the base station may transmit an additional grant (s) to the UE (e.g., following the one or more grants by at least the duration of time) , such as described in connection with FIG. 16. In another configuration, as described in connection with FIG. 17, the base station may receive an indication of a maximum number of HARQ processes based on a BWP or a CC, such as described in connection with FIG. 17. In such configuration, the base station may receive a report of one or more processing timing capabilities dependent on one or more HARQ processes for a first BWP or CC and a processing timing capability independent of the number of HARQ processes for a second BWP or CC. Then the base station may schedule the downlink communication based on the one or more processing timing capabilities corresponding to the number of HARQ processes if the downlink communication is received in the first BWP or CC and schedules the downlink communication using the processing timing capability independent of the number of HARQ processes if the downlink communication is received in the second BWP or CC. The base station may configure the maximum number of HARQ processes in the first BWP or CC and in the second BWP or CC via an RRC for the UE.

FIG. 25 is a diagram 2500 illustrating an example of a hardware implementation for an apparatus 2502. The apparatus 2502 is a base station and includes a baseband unit 2504. The baseband unit 2504 may communicate through a cellular RF transceiver with the UE 104. The baseband unit 2504 may include a computer-readable medium /memory. The baseband unit 2504 is responsible for general processing, including the execution of software stored on the computer-readable medium /memory. The software, when executed by the baseband unit 2504, causes the baseband unit 2504 to perform the various functions described supra. The computer-readable medium / memory may also be used for storing data that is manipulated by the baseband unit 2504 when executing software. The baseband unit 2504 further includes a reception component 2530, a communication manager 2532, and a transmission component 2534. The communication manager 2532 includes the one or more illustrated components. The components within the communication manager 2532 may be stored in the computer-readable medium /memory and/or configured as hardware within the baseband unit 2504. The baseband unit 2504 may be a component of the BS 310 and may include the memory 376 and/or at least one of the TX processor 316, the RX processor 370, and the controller/processor 375.

The communication manager 2532 includes a receiving component 2540 that is configured to receive, from a UE, a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant, e.g., as described in connection with 2402 of FIG. 24. The communication manager 2532 further includes a transmitting component 2542 that is configured to transmit the one or more grants to the UE, e.g., as described in connection with 2404 of FIG. 24. The communication manager 2532 includes a transmitting component 2544 that is configured to transmit an additional grant to the UE following the one or more grants by at least the duration of time, e.g., as described in connection with 2406 of FIG. 24.

The apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowchart of FIG. 24. As such, each block in the aforementioned flowcharts of FIG. 24 may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof. In one configuration, the apparatus 2502, and in particular the baseband unit 2504, includes means for receiving, from a UE, a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant. The apparatus 2502 includes means for transmitting the one or more grants to the UE. The apparatus 2502 includes means for transmitting an additional grant to the UE following the one or more grants by at least the duration of time. The aforementioned means may be one or more of the aforementioned components of the apparatus 2502 configured to perform the functions recited by the aforementioned means. As described supra, the apparatus 2502 may include the TX Processor 316, the RX Processor 370, and the controller/processor 375. As such, in one configuration, the aforementioned means may be the TX Processor 316, the RX Processor 370, and the controller/processor 375 configured to perform the functions recited by the aforementioned means.

The following examples set forth additional aspects and are illustrative only and aspects thereof may be combined with aspects of other embodiments or teaching described herein, without limitation.

Example 1 is a method of wireless communication at a UE, comprising: reporting, to a base station, a UE capability based on a HPU; receiving downlink communication from the base station; and processing the downlink communication from the base station and providing HARQ feedback based on the reported UE capability.

In Example 2, the method of Example 1 further includes that the UE capability includes a number of supported simultaneous HARQ processes based on the HPU.

In Example 3, the method of Example 1 or Example 2 further comprises: determining a number of unoccupied HPUs in a duration of time based on the number of supported simultaneous HARQ processes and a current number of occupied HPUs for processing one or more of an uplink grant, a downlink grant, or a physical downlink shared channel.

In Example 4, the method of any of Examples 1-3 further includes that the duration is based on one or more symbols.

In Example 5, the method of any of Examples 1-4 further includes that the duration is based on one or more slots.

In Example 6, the method of any of Examples 1-5 further includes that the UE does not receive additional uplink grants if the UE has no unoccupied HPUs for uplink.

In Example 7, the method of any of Examples 1-6 further includes that the UE does not determine HARQ feedback for a PDSCH if the UE has no unoccupied HPUs for downlink.

In Example 8, the method of any of Examples 1-7 further includes that the UE does not receive additional downlink grants for a PDSCH if the UE has no unoccupied HPUs for downlink.

In Example 9, the method of any of Examples 1-8 further includes that the UE capability is based on processing an uplink grant.

In Example 10, the method of any of Examples 1-9 further includes that the UE capability is based on processing a downlink grant.

In Example 11, the method of any of Examples 1-10 further includes that the UE capability is based on processing a physical downlink shared channel.

In Example 12, the method of any of Examples 1-11 further comprises: receiving a scheduling offset from the base station based on a number of unoccupied HARQ-process units.

Example 13 is an apparatus for wireless communication at a UE, comprising: means for reporting, to a base station, a UE capability based on a HPU; means for receiving downlink communication from the base station; and means for processing the downlink communication from the base station and providing HARQ feedback based on the reported UE capability.

In Example 14, the apparatus of Example 13 further comprises means to perform the method of any of Examples 2-12.

Example 15 is an apparatus for wireless communication at a UE, comprising: a memory; and at least one processor coupled to the memory, the memory and the at least one processor configured to perform the method of Examples 1-12.

Example 16 is a computer-readable medium storing computer executable code for wireless communication at a UE, the code when executed by a processor cause the processor to perform the method of any of Examples 1-12.

Example 17 is a method of wireless communication at a UE, comprising: reporting, to a base station, a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant; receiving the one or more grants from the base station; and receiving an additional grant from the base station following the one or more grants by at least the duration of time.

In Example 18, the method of Example 17 further includes that the UE reports the duration of time for one or more uplink grants.

In Example 19, the method of Example 17 or Example 18 further includes that the UE reports the duration of time for one or more downlink grants.

In Example 20, the method of any of Examples 17-19 further includes that the duration of time is reported to the base station as a UE capability.

In Example 21, the method of any of Examples 17-20 further includes that the duration of time applies to reception of a single grant.

In Example 22, the method of any of Examples 17-21 further includes that the duration of time applies to reception of multiple grants.

In Example 23, the method of any of Examples 17-22 further includes that the duration of time applies following reception of the multiple grants within a period of time.

In Example 24, the method of any of Examples 17-23 further comprises: reporting a maximum number of HARQ processes based on a BWP.

In Example 25, the method of any of Examples 17-24 further includes that the UE reports one or more processing timing capabilities dependent on one or more HARQ processes for a first BWP and a processing timing capability independent of the number of HARQ processes for a second BWP.

In Example 26, the method of any of Examples 17-25 further includes that the UE processes a downlink communication based on the one or more processing timing capabilities corresponding to the number of HARQ processes if the downlink communication is received in the first BWP and processes the downlink communication using the processing timing capability independent of the number of HARQ processes if the downlink communication is received in the second BWP.

In Example 27, the method of any of Examples 17-26 further includes that the maximum number of HARQ processes in the first BWP and in the second BWP is RRC configured by the base station.

In Example 28, the method of any of Examples 17-27 further comprises: reporting a maximum number of HARQ processes based on a CC.

In Example 29, the method of any of Examples 17-28 further includes that the UE reports one or more processing timing capabilities dependent on one or more HARQ processes for a first CC and a processing timing capability independent of the number of HARQ processes for a second CC.

In Example 30, the method of any of Examples 17-29 further includes that the UE processes a downlink communication based on the one or more processing timing capabilities corresponding to the number of HARQ processes if the downlink communication is received in the first CC and processes the downlink communication using the processing timing capability independent of the number of HARQ processes if the downlink communication is received in the second CC.

In Example 31, the method of any of Examples 17-30 further includes that the maximum number of HARQ processes in the first CC and in the second CC is RRC configured by the base station.

Example 32 is an apparatus for wireless communication at a UE, comprising: means for reporting, to a base station, a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant; means for receiving the one or more grants from the base station; and means for receiving an additional grant from the base station following the one or more grants by at least the duration of time.

In Example 33, the apparatus of Example 32 further comprises means to perform the method of any of Examples 18-30.

Example 34 is an apparatus for wireless communication at a UE, comprising: a memory; and at least one processor coupled to the memory, the memory and the at least one processor configured to perform the method of Examples 17-31.

Example 35 is a computer-readable medium storing computer executable code for wireless communication at a UE, the code when executed by a processor cause the processor to perform the method of any of Examples 17-31.

Example 36 is a method of wireless communication at a base station, comprising: receiving, from a UE, a UE capability based on a HPU; transmitting downlink communication to the UE; and receiving HARQ feedback based on the UE capability.

In Example 37, the method of Example 36 further includes that the UE capability includes a number of supported simultaneous HARQ processes based on the HPU.

In Example 38, the method of Example 36 or Example 37 further comprises: determining a number of unoccupied HPUs for the UE in a duration of time based on the number of supported simultaneous HARQ processes and a current number of occupied HPUs for processing one or more of an uplink grant, a downlink grant, or a physical downlink shared channel.

In Example 39, the method of any of Examples 36-38 further includes that the duration is based on one or more symbols.

In Example 40, the method of any of Examples 36-39 further includes that the duration is based on one or more slots.

In Example 41, the method of any of Examples 36-40 further includes that the base station does not transmit additional uplink grants if the UE has no unoccupied HPUs for uplink.

In Example 42, the method of any of Examples 36-41 further includes that the base station does not receive HARQ feedback for a PDSCH if the UE has no unoccupied HPUs for downlink.

In Example 43, the method of any of Examples 36-42 further includes that the base station does not transmit additional downlink grants for a PDSCH if the UE has no unoccupied HPUs for downlink.

In Example 44, the method of any of Examples 36-43 further includes that the UE capability is based on processing an uplink grant.

In Example 45, the method of any of Examples 36-44 further includes that the UE capability is processing an uplink grant.

In Example 46, the method of any of Examples 36-45 further includes that the UE capability is based on processing a physical downlink shared channel.

In Example 47, the method of any of Examples 36-46 further comprises: transmitting a scheduling offset to the UE based on a number of unoccupied HARQ-process units.

Example 48 is an apparatus for wireless communication at a base station, comprising: means for receiving, from a UE, a UE capability based on a HPU; means for transmitting downlink communication to the UE; and means for receiving HARQ feedback based on the UE capability.

In Example 49, the apparatus of Example 48 further comprises means to perform the method of any of Examples 37-47.

Example 50 is an apparatus for wireless communication at a base station, comprising: a memory; and at least one processor coupled to the memory, the memory and the at least one processor configured to perform the method of Examples 36-47.

Example 51 is a computer-readable medium storing computer executable code for wireless communication at a base station, the code when executed by a processor cause the processor to perform the method of any of Examples 36-47.

Example 52 is a method of wireless communication at a base station, comprising: receiving, from a UE, a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant; transmitting the one or more grants to the UE; and transmitting an additional grant to the UE following the one or more grants by at least the duration of time.

In Example 53, the method of Example 52 further includes that the base station receives the duration of time for one or more uplink grants.

In Example 54, the method of Example 52 or Example 53 further includes that the base station receives the duration of time for one or more downlink grants.

In Example 55, the method of any of Examples 52-54 further includes that the duration of time is received by the base station as a UE capability, and wherein the base station refrains from sending the additional grant to the UE during the duration of time following the one or more grants.

In Example 56, the method of any of Examples 52-55 further includes that the duration of time applies to transmission of a single grant.

In Example 57, the method of any of Examples 52-56 further includes that the duration of time applies to transmission of multiple grants.

In Example 58, the method of any of Examples 52-57 further includes that the duration of time applies following transmission of the multiple grants within a period of time.

In Example 59, the method of any of Examples 52-58 further comprises: receiving an indication of a maximum number of HARQ processes based on a BWP.

In Example 60, the method of any of Examples 52-59 further includes that the base station receives a report of one or more processing timing capabilities dependent on one or more HARQ processes for a first BWP and a processing timing capability independent of the number of HARQ processes for a second BWP.

In Example 61, the method of any of Examples 52-60 further includes that the base station schedules communication for the UE based on the one or more processing timing capabilities corresponding to the number of HARQ processes if the downlink communication is received in the first BWP and schedules the communication for the UE using the processing timing capability independent of the number of HARQ processes if the downlink communication is received in the second BWP.

In Example 62, the method of any of Examples 52-61 further comprises: configuring the maximum number of HARQ processes in the first BWP and in the second BWP via a RRC for the UE.

In Example 63, the method of any of Examples 52-62 further comprises: receiving an indication of a maximum number of HARQ processes based on a CC.

In Example 64, the method of any of Examples 52-63 further includes that the base station receives a report of one or more processing timing capabilities dependent on one or more HARQ processes for a first CC and a processing timing capability independent of the number of HARQ processes for a second CC.

In Example 65, the method of any of Examples 52-64 further includes that the base station schedules communication for the UE based on the one or more processing timing capabilities corresponding to the number of HARQ processes if the downlink communication is received in the first CC and schedules the communication for the UE using the processing timing capability independent of the number of HARQ processes if the downlink communication is received in the second CC.

In Example 66, the method of any of Examples 52-65 further comprises: configuring the maximum number of HARQ processes in the first CC and in the second CC via a RRC for the UE.

Example 67 is an apparatus for wireless communication at a base station, comprising: means for receiving, from a UE, a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant; means for transmitting the one or more grants to the UE; and means for transmitting an additional grant to the UE following the one or more grants by at least the duration of time.

In Example 68, the apparatus of Example 67 further comprises means to perform the method of any of Examples 53-66.

Example 69 is an apparatus for wireless communication at a base station, comprising: a memory; and at least one processor coupled to the memory, the memory and the at least one processor configured to perform the method of Examples 52-66.

Example 70 is a computer-readable medium storing computer executable code for wireless communication at a base station, the code when executed by a processor cause the processor to perform the method of any of Examples 52-66.

Example 71 is yet another method of wireless communication at a user equipment. The method (like other techniques discussed herein) may include one or more optional actions and/or steps (such as those that follow) . For example, the method may include reporting, to a base station, a UE capability based on a HPU. The method may also include receiving downlink communication from the base station. Further, the method may optionally include processing the downlink communication from the base station and providing HARQ feedback based on the reported UE capability.

Example 72 is yet another method of wireless communication at a user equipment. The method (like other techniques discussed herein) may include one or more optional actions and/or steps (such as those that follow) . For example, the method may include reporting, to a base station, a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant. The method may also include receiving the one or more grants from the base station. Further, the method may optionally include receiving an additional grant from the base station following the one or more grants by at least the duration of time.

Example 73 is yet another method of wireless communication at a base station. The method (like other techniques discussed herein) may include one or more optional actions and/or steps (such as those that follow) . For example, the method may include receiving, from a UE, a UE capability based on a HPU. The method may also include transmitting downlink communication to the UE. Further, the method may optionally include receiving HARQ feedback based on the UE capability.

Example 74 is yet another method of wireless communication at a base station. The method (like other techniques discussed herein) may include one or more optional actions and/or steps (such as those that follow) . For example, the method may include receiving, from a UE, a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant. The method may also include transmitting the one or more grants to the UE. Further, the method may optionally include transmitting an additional grant to the UE following the one or more grants by at least the duration of time.

It is understood that the specific order or hierarchy of blocks in the processes /flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes /flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more. ” Terms such as “if, ” “when, ” and “while” should be interpreted to mean “under the condition that” rather than imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when, ” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration. ” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ”

Claims

A method of wireless communication at a user equipment (UE) , comprising:

reporting, to a base station, a UE capability based on a hybrid automatic repeat request (HARQ) process unit (HPU) ; and

processing the downlink communication from the base station and providing HARQ feedback based on the reported UE capability.
The method of claim 1, wherein the UE capability includes a number of supported simultaneous HARQ processes based on the HPU.
The method of claim 2, further comprising:

determining a number of unoccupied HPUs in a duration of time based on the number of supported simultaneous HARQ processes and a current number of occupied HPUs for processing one or more of an uplink grant, a downlink grant, or a physical downlink shared channel.
The method of claim 3, wherein the duration is based on one or more symbols.
The method of claim 3, wherein the duration is based on one or more slots.
The method of claim 3, wherein the UE does not receive additional uplink grants if the UE has no unoccupied HPUs for uplink.
The method of claim 3, wherein the UE does not determine HARQ feedback for a physical downlink shared channel (PDSCH) if the UE has no unoccupied HPUs for downlink.
The method of claim 3, wherein the UE does not receive additional downlink grants for a physical downlink shared channel (PDSCH) if the UE has no unoccupied HPUs for downlink.
The method of claim 1, wherein the UE capability is based on processing an uplink grant.
The method of claim 1, wherein the UE capability is based on processing a downlink grant.
The method of claim 1, wherein the UE capability is based on processing a physical downlink shared channel.
The method of claim 3, further comprising:

receiving a scheduling offset from the base station based on a number of unoccupied HARQ-process units.
An apparatus for wireless communication at a user equipment (UE) , comprising:

means for reporting, to a base station, a UE capability based on a hybrid automatic repeat request (HARQ) process unit (HPU) ;

means for receiving downlink communication from the base station; and

means for processing the downlink communication from the base station and providing HARQ feedback based on the reported UE capability.
The apparatus of claim 13, further comprises means to perform the method of any of claims 2-12.
An apparatus for wireless communication at a user equipment (UE) , comprising:

a memory; and

at least one processor coupled to the memory, the memory and the at least one processor configured to perform the method of claims 1-12.
A computer-readable medium storing computer executable code for wireless communication at a user equipment (UE) , the code when executed by a processor cause the processor to perform the method of any of claims 1-12.
A method of wireless communication at a user equipment (UE) , comprising:

reporting, to a base station, a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant;

receiving the one or more grants from the base station; and

receiving an additional grant from the base station following the one or more grants by at least the duration of time.
The method of claim 17, wherein the UE reports the duration of time for one or more uplink grants.
The method of claim 17, wherein the UE reports the duration of time for one or more downlink grants.
The method of claim 17, wherein the duration of time is reported to the base station as a UE capability.
The method of claim 17, wherein the duration of time applies to reception of a single grant.
The method of claim 17, wherein the duration of time applies to reception of multiple grants.
The method of claim 22, wherein the duration of time applies following reception of the multiple grants within a period of time.
The method of claim 17, further comprising:

reporting a maximum number of HARQ processes based on a BWP.
The method of claim 24, wherein the UE reports one or more processing timing capabilities dependent on one or more HARQ processes for a first BWP and a processing timing capability independent of the number of HARQ processes for a second BWP.
The method of claim 25, wherein the UE processes a downlink communication based on the one or more processing timing capabilities corresponding to the number of HARQ processes if the downlink communication is received in the first BWP and processes the downlink communication using the processing timing capability independent of the number of HARQ processes if the downlink communication is received in the second BWP.
The method of claim 26, wherein the maximum number of HARQ processes in the first BWP and in the second BWP is radio resource control (RRC) configured by the base station.
The method of claim 17, further comprising:

reporting a maximum number of HARQ processes based on a component carrier (CC) .
The method of claim 28, wherein the UE reports one or more processing timing capabilities dependent on one or more HARQ processes for a first CC and a processing timing capability independent of the number of HARQ processes for a second CC.
The method of claim 29, wherein the UE processes a downlink communication based on the one or more processing timing capabilities corresponding to the number of HARQ processes if the downlink communication is received in the first CC and processes the downlink communication using the processing timing capability independent of the number of HARQ processes if the downlink communication is received in the second CC.
The method of claim 30, wherein the maximum number of HARQ processes in the first CC and in the second CC is radio resource control (RRC) configured by the base station.
An apparatus for wireless communication at a user equipment (UE) , comprising:

means for reporting, to a base station, a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant;

means for receiving the one or more grants from the base station; and

means for receiving an additional grant from the base station following the one or more grants by at least the duration of time.
The apparatus of claim 32, further comprises means to perform the method of any of claims 18-30.
An apparatus for wireless communication at a user equipment (UE) , comprising:

a memory; and

at least one processor coupled to the memory, the memory and the at least one processor configured to perform the method of claims 17-31.
A computer-readable medium storing computer executable code for wireless communication at a user equipment (UE) , the code when executed by a processor cause the processor to perform the method of any of claims 17-31.
A method of wireless communication at a base station, comprising:

receiving, from a user equipment (UE) , a UE capability based on a hybrid automatic repeat request (HARQ) process unit (HPU) ;

transmitting downlink communication to the UE; and

receiving HARQ feedback based on the UE capability.
The method of claim 36, wherein the UE capability includes a number of supported simultaneous HARQ processes based on the HPU.
The method of claim 37, further comprising:

determining a number of unoccupied HPUs for the UE in a duration of time based on the number of supported simultaneous HARQ processes and a current number of occupied HPUs for processing one or more of an uplink grant, a downlink grant, or a physical downlink shared channel.
The method of claim 38, wherein the duration is based on one or more symbols.
The method of claim 38, wherein the duration is based on one or more slots.
The method of claim 38, wherein the base station does not transmit additional uplink grants if the UE has no unoccupied HPUs for uplink.
The method of claim 38, wherein the base station does not receive HARQ feedback for a physical downlink shared channel (PDSCH) if the UE has no unoccupied HPUs for downlink.
The method of claim 38, wherein the base station does not transmit additional downlink grants for a physical downlink shared channel (PDSCH) if the UE has no unoccupied HPUs for downlink.
The method of claim 36, wherein the UE capability is based on processing an uplink grant.
The method of claim 36, wherein the UE capability is processing an uplink grant.
The method of claim 36, wherein the UE capability is based on processing a physical downlink shared channel.
The method of claim 38, further comprising:

transmitting a scheduling offset to the UE based on a number of unoccupied HARQ-process units.
An apparatus for wireless communication at a base station, comprising:

means for receiving, from a user equipment (UE) , a UE capability based on a hybrid automatic repeat request (HARQ) process unit (HPU) ;

means for transmitting downlink communication to the UE; and

means for receiving HARQ feedback based on the UE capability.
The apparatus of claim 48, further comprises means to perform the method of any of claims 37-47.
An apparatus for wireless communication at a base station, comprising:

a memory; and

at least one processor coupled to the memory, the memory and the at least one processor configured to perform the method of claims 36-47.
A computer-readable medium storing computer executable code for wireless communication at a base station, the code when executed by a processor cause the processor to perform the method of any of claims 36-47.
A method of wireless communication at a base station, comprising:

receiving, from a user equipment (UE) , a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant;

transmitting the one or more grants to the UE; and

transmitting an additional grant to the UE following the one or more grants by at least the duration of time.
The method of claim 52, wherein the base station receives the duration of time for one or more uplink grants.
The method of claim 52, wherein the base station receives the duration of time for one or more downlink grants.
The method of claim 52, wherein the duration of time is received by the base station as a UE capability, and wherein the base station refrains from sending the additional grant to the UE during the duration of time following the one or more grants.
The method of claim 52, wherein the duration of time applies to transmission of a single grant.
The method of claim 52, wherein the duration of time applies to transmission of multiple grants.
The method of claim 57, wherein the duration of time applies following transmission of the multiple grants within a period of time.
The method of claim 52, further comprising:

receiving an indication of a maximum number of HARQ processes based on a BWP.
The method of claim 59, wherein the base station receives a report of one or more processing timing capabilities dependent on one or more HARQ processes for a first BWP and a processing timing capability independent of the number of HARQ processes for a second BWP.
The method of claim 60, wherein the base station schedules communication for the UE based on the one or more processing timing capabilities corresponding to the number of HARQ processes if a downlink communication is received in the first BWP and schedules the communication for the UE using the processing timing capability independent of the number of HARQ processes if the downlink communication is received in the second BWP.
The method of claim 61, further comprising:

configuring the maximum number of HARQ processes in the first BWP and in the second BWP via a radio resource control (RRC) for the UE.
The method of claim 52, further comprising:

receiving an indication of a maximum number of HARQ processes based on a component carrier (CC) .
The method of claim 63, wherein the base station receives a report of one or more processing timing capabilities dependent on one or more HARQ processes for a first CC and a processing timing capability independent of the number of HARQ processes for a second CC.
The method of claim 64, wherein the base station schedules communication for the UE based on the one or more processing timing capabilities corresponding to the number of HARQ processes if a downlink communication is received in the first CC and schedules the communication for the UE using the processing timing capability independent of the number of HARQ processes if the downlink communication is received in the second CC.
The method of claim 65, further comprising:

configuring the maximum number of HARQ processes in the first CC and in the second CC via a radio resource control (RRC) for the UE.
An apparatus for wireless communication at a base station, comprising:

means for receiving, from a user equipment (UE) , a duration of time following reception of one or more grants when the UE does not expect to receive an additional grant;

means for transmitting the one or more grants to the UE; and

means for transmitting an additional grant to the UE following the one or more grants by at least the duration of time.
The apparatus of claim 67, further comprises means to perform the method of any of claims 53-66.
An apparatus for wireless communication at a base station, comprising:

a memory; and

at least one processor coupled to the memory, the memory and the at least one processor configured to perform the method of claims 52-66.
A computer-readable medium storing computer executable code for wireless communication at a base station, the code when executed by a processor cause the processor to perform the method of any of claims 52-66.