[go: up one dir, main page]

WO2022032509A1 - Configuration d'équipement utilisateur spécifique de processus harq pour une réduction de complexité de capacité réduite - Google Patents

Configuration d'équipement utilisateur spécifique de processus harq pour une réduction de complexité de capacité réduite Download PDF

Info

Publication number
WO2022032509A1
WO2022032509A1 PCT/CN2020/108590 CN2020108590W WO2022032509A1 WO 2022032509 A1 WO2022032509 A1 WO 2022032509A1 CN 2020108590 W CN2020108590 W CN 2020108590W WO 2022032509 A1 WO2022032509 A1 WO 2022032509A1
Authority
WO
WIPO (PCT)
Prior art keywords
capability
base station
tbs
harq processes
pusch
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2020/108590
Other languages
English (en)
Inventor
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
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2020/108590 priority Critical patent/WO2022032509A1/fr
Priority to PCT/CN2021/112050 priority patent/WO2022033515A1/fr
Publication of WO2022032509A1 publication Critical patent/WO2022032509A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0009—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1864—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements

Definitions

  • the present disclosure relates generally to communication systems, and more particularly, to wireless communication techniques involving hybrid automatic repeat request processing configuration (e.g., for a user equipment) .
  • 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.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single-carrier frequency division multiple access
  • TD-SCDMA time division synchronous code division multiple access
  • 5G New Radio 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.
  • 3GPP Third Generation Partnership Project
  • 5G NR includes services associated with enhanced mobile broadband (eMBB) , massive machine type communications (mMTC) , and ultra-reliable low latency communications (URLLC) .
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communications
  • URLLC ultra-reliable low latency communications
  • Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard.
  • LTE Long Term Evolution
  • a method, a computer-readable medium, and an apparatus are provided for wireless communication.
  • the wireless communication may be performed at a UE.
  • the apparatus reports, to a base station, N UE capabilities for N groups of TBS, N being an integer number greater than 1, wherein a first UE capability is reported for a first TBS group and a second UE capability is reported for a second TBS group.
  • the apparatus receives downlink communication having a TBS from the base station.
  • the apparatus processes the downlink communication from the base station based on a UE capability from the N UE capabilities corresponding to the TBS.
  • a method, a computer-readable medium, and an apparatus are provided for wireless communication.
  • the wireless communication may be performed at a UE.
  • the apparatus reports, to a base station, a first processing time capability for a first type of PUSCH. Then the apparatus reports, to the base station, a second processing time capability for a second type of PUSCH. Then the apparatus receives an uplink grant for a PUSCH transmission. Then the apparatus transmits the PUSCH based on a processing time corresponding to the type of the PUSCH transmission.
  • a method, a computer-readable medium, and an apparatus are provided for wireless communication.
  • the wireless communication may be performed at a base station.
  • the apparatus receives, from a UE, N UE capabilities for N groups of TBS, N being an integer number greater than 1, where a first UE capability is received for a first TBS group and a second UE capability is received for a second TBS group. Then the apparatus schedules the UE for downlink communication having a TBS based on a capability reported by the UE for a group including the TBS.
  • a method, a computer-readable medium, and an apparatus are provided for wireless communication.
  • the wireless communication may be performed at a base station.
  • the apparatus receives, from a UE, a first processing time capability for a first type of PUSCH.
  • the apparatus receives, from the UE, a second processing time capability for a second type of PUSCH.
  • the apparatus transmits an uplink grant for a PUSCH transmission.
  • the apparatus receives the PUSCH based on a processing time corresponding to the type of the PUSCH transmission.
  • 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.
  • 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.
  • UE user equipment
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • RAM random-access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable ROM
  • optical disk storage magnetic 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.
  • the UE 104 may include a UE Capability Reporting Component 198 configured to report one or more UE capabilities to a base station (e.g., 102/180) , where each capability may include a set of one or more processing time parameters for a group of HARQ processes. Then the UE Capability Reporting 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.
  • a base station e.g. 102/180
  • each capability may include a set of one or more processing time parameters for a group of HARQ processes.
  • the UE Capability Reporting 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.
  • the UE Capability Reporting Component 198 may be configured with a variety of capability information.
  • the UE Capability Reporting Component 198 can be configured to report, to a base station, N UE capabilities for N groups of TBS (e.g., where N is an integer number greater than 1) .
  • UEs may communicate multiple capability reports. For example, this can include a first UE capability reported for a first TBS group and a second UE capability reported for a second TBS group.
  • the UE Capability Reporting Component 198 may be configured to receive downlink communication having a TBS from the base station and process the downlink communication from the base station based on a UE capability from the N UE capabilities corresponding to the TBS.
  • the UE Capability Reporting Component 198 may alternatively or additional report additional types of capability information.
  • the UE Capability Reporting Component 198 may be configured to report, to a base station, a first processing time capability for a first type of PUSCH and a second processing time capability for a second type of PUSCH.
  • a UE Capability Reporting Component 198 may additionally and/or alternatively be configured to receive an uplink grant for a PUSCH transmission and transmit the PUSCH based on a processing time corresponding to the type of the PUSCH transmission.
  • 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 TBS, UCI, BWP or CC, etc.
  • the base stations 102 configured for 4G LTE may interface with the EPC 160 through first backhaul links 132 (e.g., S1 interface) .
  • the base stations 102 configured for 5G NR may interface with core network 190 through second backhaul links 184.
  • 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.
  • NAS non-access stratum
  • RAN radio access network
  • MBMS multimedia broadcast multicast service
  • RIM RAN information management
  • 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) .
  • eNBs Home Evolved Node Bs
  • HeNBs Home Evolved Node Bs
  • CSG closed subscriber group
  • 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.
  • 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) .
  • 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) .
  • 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) .
  • 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, ZigBe
  • 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.
  • AP Wi-Fi access point
  • STAs Wi-Fi stations
  • communication links 154 e.g., in a 5 GHz unlicensed frequency spectrum or the like.
  • the STAs 152/AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
  • CCA clear channel assessment
  • 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 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.
  • 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.
  • FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles.
  • 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.
  • EHF extremely high frequency
  • ITU International Telecommunications Union
  • 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.
  • 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 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.
  • 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.
  • MME Mobility Management Entity
  • MBMS Multimedia Broadcast Multicast Service
  • BM-SC Broadcast Multicast Service Center
  • PDN Packet Data Network
  • the MME 162 may be in communication with a Home Subscriber Server (HSS) 174.
  • HSS Home Subscriber Server
  • the MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160.
  • 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.
  • IP Internet protocol
  • 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.
  • PLMN public land mobile network
  • 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.
  • MMSFN Multicast Broadcast Single Frequency Network
  • 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.
  • 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.
  • IMS IP Multimedia Subsystem
  • PS Packet Switch
  • PSS Packet
  • 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.
  • SIP session initiation protocol
  • PDA personal digital assistant
  • 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.
  • FDD frequency division duplexed
  • TDD time division duplexed
  • 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) .
  • DCI DL control information
  • RRC radio resource control
  • SFI received slot format indicator
  • 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.
  • the symbol length/duration is inversely related to the subcarrier spacing.
  • the slot duration is 0.25 ms
  • the subcarrier spacing is 60 kHz
  • the symbol duration is approximately 16.67 ⁇ s.
  • 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.
  • RB resource block
  • PRBs physical RBs
  • the resource grid is divided into multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.
  • 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.
  • DM-RS demodulation RS
  • CSI-RS channel state information reference signals
  • the RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and phase tracking RS (PT-RS) .
  • BRS beam measurement RS
  • BRRS beam refinement RS
  • PT-RS phase tracking 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.
  • CCEs control channel elements
  • REGs RE groups
  • a PDCCH within one BWP may be referred to as a control resource set (CORESET) .
  • CORESET control resource set
  • 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.
  • 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.
  • SIBs system information blocks
  • 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.
  • UCI uplink control information
  • the PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and/or UCI.
  • BSR buffer status report
  • PHR power headroom report
  • FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network.
  • 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
  • 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.
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC medium access control
  • 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
  • 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) ) .
  • BPSK binary phase-shift keying
  • QPSK quadrature phase-shift keying
  • M-PSK M-phase-shift keying
  • M-QAM M-quadrature amplitude modulation
  • 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.
  • IFFT Inverse Fast Fourier Transform
  • 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.
  • 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) .
  • FFT Fast Fourier Transform
  • 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.
  • 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.
  • 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.
  • RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting
  • PDCP layer functionality associated with header
  • 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.
  • 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.
  • wireless communication may support reduced capability devices.
  • higher capability devices may include premium smartphones, V2X devices, URLLC devices, eMBB devices, etc.
  • reduced capability devices may include wearables, industrial wireless sensor networks (IWSN) , surveillance cameras, low-end smartphones, etc.
  • IWSN industrial wireless sensor networks
  • NR communication systems may support both higher capability devices and reduced capability devices.
  • a reduced capability device e.g., reduced capability UE
  • 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. ) .
  • 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.
  • the term “reduced capability” may be used to describe a UE with the reduced capability (e.g., reduced capability UE) .
  • 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.
  • 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.
  • a reduced capability UE may have an uplink transmission power of at least 10 dB less than that a higher capability UE.
  • 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.
  • a reduced capability UE may have a reduced number of reception antennas in comparison to other UEs.
  • 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.
  • SNR receive signal to noise ratio
  • 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.
  • 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 0 may indicate the delay (e.g., in slots) between the DL grant 402 reception and corresponding PDSCH 404 reception, and an offset K 2 may indicate the delay between the UL grant 410 reception and the corresponding PUSCH 412 transmission.
  • DL downlink
  • UL uplink
  • the base station may further schedule an additional offset K 1 and/or offset K 3 for the UE, where the offset K 1 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 3 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 0 , K 1 and K 2 in the DCI, and the minimum value for offsets K 0 , K 1 and K 2 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.
  • the base station may take the UE processing time into account. For example, in determining the offset K 1 , 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 2 , 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 for the PUSCH e.g., 412
  • the PUSCH e.g., 412
  • 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 1 , K 2 ) .
  • a UE processing time N 1 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 2 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 1 , N 2 ) 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.
  • CA carrier aggregation
  • the base station may determine the minimum value for the offset K 1 and/or the offset K 2 based on assumptions of a respective UE’s turn-around times (e.g., processing time N 1 , N 2 ) .
  • a UE may indicate one or more capabilities for N 1 and N 2 to the base station, such as based on corresponding entry for N 1 and N 2 from either Table 1 or Table 2.
  • a UE 602 may select a processing time N 1 , N 2 based on a UE capability or from a pre-defined table, such as from Table 1 or Table 2.
  • the UE 602 may indicate the selected processing time to a base station 604.
  • the base station 610 may determine the offsets K 1 and K 2 based on the received N 1 , N 2 .
  • the base station 610 may indicate the offsets K 1 and K 2 to the UE 602, such as via a DCI in a PDCCH.
  • the UE may apply the offset K 1 in association with the HARQ feedback reporting and the offset K 2 in association with the PUSCH transmission. For example, if the UE indicates to the base station a processing time N 1 to be 24 symbols under 120 kHz SCS, the base station may assign at least one slot for the offset K 1 .
  • 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.
  • a parallel implementation e.g., computation
  • the UE may prepare parallel hardware or compurgation resources to meet the (N 1 , N 2 ) capability reported. In other words, the UE may process multiple PDSCHs and their corresponding HARQ feedback at the same time.
  • the UE may prepare multiple hardware or computation resources to meet the (N 1 , N 2 ) 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.
  • a more relaxed capability reporting of the processing time (N 1 , N 2 ) may be configured for the UE, where the UE may report or indicate a greater (e.g., longer) value for the (N 1 , N 2 ) so that the UE may have more time to process the data or the HARQ feedback.
  • 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 1 , N 2 ) ) , 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.
  • services may have a strict delay with varying throughput, and in some instances limited throughput.
  • reduced capability UEs may contain less parallel hardware or computational resources relative to non-reduced capability UEs (e.g., full capability UEs) .
  • a UE may report the processing time (e.g., N 1 , N 2 ) for a group of HARQ-processes (e.g., HARQ-Process Group Specific Processing Time Report) .
  • the UE may report the capability regarding the processing time as shown by flowchart 800 of FIG. 8.
  • the UE may divide the total number of HARQ-processes to be supported into N groups (e.g., G 1 , G 2 , G 3 ...G 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 0 ) ; 2) a minimum delay between the PDSCH reception and the corresponding HARQ feedback (e.g., ACK/NACK) transmission on the UL (e.g., K 1 ) ; 3) a minimum delay between the UL grant reception and the PUSCH transmission (e.g., K 2 ) ; 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 3 ) .
  • a minimum delay e.g., in slots and/or symbols
  • the reported capabilities may descend through a group-index.
  • 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 1 , the UE may expect the scheduled timeline to meet its reported capability for the group G 1 .
  • the UE may expect G 1 HARQ-processes to comprise a timeline to meet its reported capability for the group G 1 , and the others meeting its reported capability for group G 2 .
  • the total number of HARQ-processes to be supported by the UE may be divided into three groups (e.g., G 1 , G 2 , G 3 ) , 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.
  • the reported capability for processing time for Group G 1 is shorter (e.g., tighter) than Group G 2
  • the report capability for processing time for Group G 2 is shorter than Group G 3 , etc.
  • Group 1 may include or support up to 3 HARQ-processes
  • Group 2 may include or support up to 5 HARQ-processes
  • Group 3 may include or support up to 8 HARQ-processes, etc.
  • 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.
  • 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.
  • the reported capability e.g., processing time
  • 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.
  • 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.
  • 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.
  • PUSCHs physical uplink shared channels
  • a UE may report the processing time (e.g., N 1 , N 2 ) 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.
  • 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 0 ) ; 2) a minimum delay between the PDSCH reception and the corresponding HARQ feedback (e.g., ACK/NACK) transmission on the UL (e.g., K 1 ) ; 3) a minimum delay between the UL grant reception and the PUSCH transmission (e.g., K 2 ) ; 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 3 ) .
  • a minimum delay e.g., in slots and/or symbols
  • 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) .
  • 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.
  • PUSCHs physical uplink shared channels
  • 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.
  • 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.
  • 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.
  • the UE may expect the scheduled timeline for all HARQ-processes to meet its reported capability for Level 2.
  • the UE may expect the scheduled timeline for all HARQ-processes to meet its reported capability for Level 3, etc.
  • 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) .
  • some signaling e.g., DCI signal
  • a Semi-Persistent Scheduling 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.
  • 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.
  • HARQ-processes e.g., Level 3 -between 7 and 13 HARQ-processes
  • an additional slot offset (e.g., scheduling) or an adjusted offset may be applied for reduced capability UEs.
  • the offset may be dedicated for reduced capability UEs.
  • the UE may expect the values of K 0 /K 1 /K 2 /K 3 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.
  • the offset values of K 0 /K 1 /K 2 /K 3 for normal UE may be 2/2/3/4 slots respectively.
  • 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.
  • 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 ) .
  • a threshold e.g., N HARQ
  • 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.
  • 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.
  • the base station 1204 may configure a regular offset K 0 /K 1 /K 2 /K 3 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 1 and N 2 for regular UEs (e.g., the processing time identified in Table 1 and Table 2 may remain the same) .
  • 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.
  • PUSCHs physical uplink shared channels
  • the processing time reported by the UE may be based on the transport block size (TBS) (e.g., TBS Dependent Processing Time) .
  • TBS transport block size
  • a UE may report the capability regarding the processing time as shown by flowchart 1300 of FIG. 13.
  • the UE may divide the supported TBS into N groups, such as in an ascending TBS order (e.g., G 1 , G 2 , G 3 ...G 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 0 ) ; 2) a minimum delay between the PDSCH reception and the corresponding HARQ feedback (e.g., ACK/NACK) transmission on the UL (e.g., K 1 ) ; 3) a minimum delay between the UL grant reception and the PUSCH transmission (e.g., K 2 ) ; 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 3 ) .
  • a minimum delay e.g., in slots and/or symbols
  • a larger (e.g., longer) processing time may be configured for these HARQ-processes
  • a looser (e.g., shorter) processing time may be configured for the these HARQ-processes, etc.
  • the PUSCH processing time for the UE may be dependent on a PUSCH type.
  • the PUSCH processing time may be based on whether a UCI is multiplexed with the PUSCH.
  • a UE may report the capability regarding the processing time as shown by flowchart 1400 of FIG. 14.
  • the UE may divide multiple PUSCHs into different types of PUSCHs and may indicate different processing capabilities for the different types of PUSCHs.
  • the UE may divide multiple PUSCHs into a first type of PUSCH with UCI-multiplexing and a second type of PUSCH without UCI-multiplexing.
  • 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) .
  • minimum delay e.g., in slots and/or symbols
  • 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.
  • N CPU CSI Processing Unit
  • 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.
  • HPU HARQ Processing Unit
  • 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.
  • a capability e.g., indicate
  • 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.
  • 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) .
  • 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.
  • HARQ feedback e.g., ACK/NACK
  • 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.
  • 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.
  • 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.
  • a UE 1602 may indicate a DCI Forbidden Time Duration T or T combination (e.g., for multiple DCIs) to a base station 1604.
  • 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.
  • 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.
  • the timing management e.g., processing time
  • 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) .
  • a maximum number of active HARQ-processes e.g., 16
  • a longer processing time e.g., N 1_increase or N 2_increase , etc.
  • the first BWP or CC 1702 may be provided for the first BWP or CC 1702 as it is associated with a higher maximum number of active HARQ-processes.
  • another maximum number of active HARQ-processes e.g., 4
  • N 1 or N 2 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 1 or N 2 is used) .
  • 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) .
  • a dashed line may enable the UE to receive downlink communication having a TBS from the base station and process the downlink communication from the base station based on a UE capability from the one or more UE capabilities corresponding to the TBS.
  • the UE may report, to a base station, N UE capabilities for N groups of TBS, N being an integer number greater than 1, where a first UE capability is reported for a first TBS group and a second UE capability is reported for a second TBS group; and, such as described in connection with FIG. 13.
  • the UE may divide the supported TBS into N groups, such as with an ascending TBS order.
  • the UE may report capabilities for the processing time including at least one or any combination of: minimum delay between DL grant and corresponding PDSCH reception; minimum delay between PDSCH reception and corresponding ACK transmission on UL; minimum delay between UL grant reception and PUSCH transmission; and minimum delay between A/N reception in UL and corresponding retransmission of PDSCH on DL.
  • the minimum delay may be calculated in slots and/or symbols.
  • the UE may report a first UE capability for a first TBS group and the UE may report a second UE capability for a second TBS group.
  • the UE may receive scheduling based on the first UE capability if the TBS is within the first TBS group, and the UE may receive scheduling based on the first UE capability for a first TBS within the first TBS group and based on the second UE capability for a second TBS within the second TBS group.
  • the UE may report a longer processing time for a first TBS group associated with a larger TBS and reports a shorter processing time for a second TBS group with smaller TBS, such as described in connection with FIG. 13.
  • the UE may report a maximum number of HARQ processes based on a BWP or a CC, such as described in connection with FIG. 17.
  • the UE may report 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.
  • 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 or CC, and the UE may process 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 maximum number of HARQ processes in the first BWP and in the second BWP may be RRC configured by the base station.
  • the UE may receive downlink communication having a TBS from the base station, such as described in connection with FIG. 13.
  • the UE may process the downlink communication from the base station based on a UE capability from the N UE capabilities corresponding to the TBS, such as described in connection with FIG. 13.
  • 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.
  • 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, N UE capabilities for N groups of TBS, N being an integer number greater than 1, where a first UE capability is reported for a first TBS group and a second UE capability is reported for a second TBS group, 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 having a TBS 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 based on a UE capability from the N UE capabilities corresponding to the TBS, 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.
  • the apparatus 1902 includes means for reporting, to a base station, N UE capabilities for N groups of TBS, N being an integer number greater than 1, where a first UE capability is reported for a first TBS group and a second UE capability is reported for a second TBS group.
  • the apparatus 1902 includes means for receiving downlink communication having a TBS from the base station.
  • the apparatus 1902 includes means for processing the downlink communication from the base station based on a UE capability from the N UE capabilities corresponding to the TBS.
  • 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.
  • the apparatus 1902 may include the TX Processor 368, the RX Processor 356, and the controller/processor 359.
  • 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) .
  • a dashed line may enable the UE to report or be configured with a longer processing time for transmitting a PUSCH when a PUSCH is multiplexed with a UCI.
  • the UE may report, to a base station, a first processing time capability for a first type of PUSCH, such as described in connection with FIG. 14.
  • the UE may determine the processing time based on whether the PUSCH transmission is multiplexed with multiplexed UCI.
  • the UE may report, to the base station, a second processing time capability for a second type of PUSCH. Similarly, the UE may determine the processing time based on whether the PUSCH transmission is multiplexed with multiplexed UCI, such as described in connection with FIG. 14. For example, at 1402, the UE may divide PUSCHs into ones with UCI-multiplexing and ones without UCI-multiplexing. Then at 1404, the UE may separately report minimum delay between a UL grant reception and a PUSCH transmission, for these two types of PUSCHs.
  • the first processing time capability and the second processing time capability may indicate a delay between reception of an uplink grant from the base station and transmission of a corresponding PUSCH transmission by the UE.
  • the delay may be reported as a number of slots and/or as a number of symbols.
  • the UE may report a maximum number of HARQ processes based on a BWP or a CC, such as described in connection with FIG. 17.
  • the UE may report 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.
  • 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 or CC, and the UE may process 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 maximum number of HARQ processes in the first BWP and in the second BWP may be RRC configured by the base station.
  • the UE may receive an uplink grant for a PUSCH transmission, such as described in connection with FIG. 14.
  • the UE may transmit the PUSCH based on a processing time corresponding to the type of the PUSCH transmission, such as described in connection with FIG. 14.
  • the processing time may be longer for the PUSCH with the multiplexed UCI than for the PUSCH without the multiplexed UCI.
  • 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.
  • 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 first processing time capability for a first type of PUSCH, e.g., as described in connection with 2002 of FIG. 20.
  • the communication manager 2132 further includes a reporting component 2142 that is configured to report, to the base station, a second processing time capability for a second type of PUSCH, 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 uplink grant for a PUSCH transmission, e.g., as described in connection with 2006 of FIG. 20.
  • the communication manager 2132 further includes a transmitting component 2146 that is configured to transmit the PUSCH based on a processing time corresponding to the type of the PUSCH transmission, e.g., as described in connection with 2008 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.
  • the apparatus 2102, and in particular the cellular baseband processor 2104 includes means for reporting, to a base station, a first processing time capability for a first type of PUSCH.
  • the apparatus 2102 includes means for report, to the base station, a second processing time capability for a second type of PUSCH.
  • the apparatus 2102 includes means for receive an uplink grant for a PUSCH transmission.
  • the apparatus 2102 includes means for transmit the PUSCH based on a processing time corresponding to the type of the PUSCH transmission.
  • 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.
  • the apparatus 2102 may include the TX Processor 368, the RX Processor 356, and the controller/processor 359.
  • 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 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 downlink communication having a TBS for the UE based on a UE capability corresponding to the TBS.
  • the base station may receive, from a UE, N UE capabilities for N groups of TBS, N being an integer number greater than 1, where a first UE capability is received for a first TBS group and a second UE capability is received for a second TBS group, such as described in connection with FIG. 13.
  • the UE may report a first UE capability for a first TBS group and reports a second UE capability for a second TBS group.
  • each of the N UE capabilities may include one or more of: a minimum delay in slots or symbols between a DL grant and a corresponding PDSCH reception, a minimum delay in slots or symbols between the PDSCH reception and a corresponding UL HARQ feedback transmission, a minimum delay in slots or symbols between an UL grant reception and a corresponding PUSCH transmission, or a minimum delay in slots or symbols between the UL HARQ transmission and a corresponding retransmission of the PDSCH.
  • the base station may schedule the UE for downlink communication having a TBS based on a capability reported by the UE for a group including the TBS, such as described in connection with FIG. 13.
  • the base station may transmit scheduling based on the first UE capability if the TBS is within the first TBS group.
  • the base station may transmit scheduling based on the first UE capability for a first TBS within the first TBS group and based on the second UE capability for a second TBS within the second TBS group.
  • the UE may report a longer processing time for a first TBS group associated with a larger TBS and reports a shorter processing time for a second TBS group with smaller TBS.
  • 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.
  • 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.
  • 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, N UE capabilities for N groups of TBS, N being an integer number greater than 1, wherein a first UE capability is received for a first TBS group and a second UE capability is received for a second TBS group, e.g., as described in connection with 2202 of FIG. 22.
  • the communication manager 2332 further includes a scheduling component 2342 that is configured to transmit downlink communication having a TBS to the UE, e.g., as described in connection with 2204 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.
  • the apparatus 2302 includes means for receiving, from a UE, N UE capabilities for N groups of TBS, N being an integer number greater than 1, wherein a first UE capability is received for a first TBS group and a second UE capability is received for a second TBS group.
  • the apparatus 2302 includes means for transmitting downlink communication having a TBS to the UE.
  • 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.
  • the apparatus 2302 may include the TX Processor 316, the RX Processor 370, and the controller/processor 375.
  • 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 schedule offset (s) for a PUSCH based at least in part on whether the PUSCH is multiplexed with a UCI.
  • the base station may receive, from a UE, a first processing time capability for a first type of PUSCH, such as described in connection with FIG. 14.
  • the base station may receive, from the UE, a second processing time capability for a second type of PUSCH, such as described in connection with FIG. 14.
  • the first type of the PUSCH may include multiplexed UCI and the second type of the PUSCH may not include the multiplexed UCI.
  • the processing time may be longer for the PUSCH with the multiplexed UCI than for the PUSCH without the multiplexed UCI.
  • the base station may transmit an UL grant for a PUSCH transmission, such as described in connection with FIG. 14.
  • the UL grant may include a scheduling offset for the PUSCH, where the base station may determine the scheduling offset (e.g., processing time) for the UE based on whether the PUSCH transmission will include multiplexed UCI.
  • the base station may receive the PUSCH based on a processing time corresponding to the type of the PUSCH transmission, such as described in connection with FIG. 14.
  • the base station may determine the processing time based on whether the PUSCH transmission will include multiplexed UCI.
  • the first processing time capability and the second processing time capability may indicate a delay between reception of an uplink grant at the UE and transmission of a corresponding PUSCH by the UE, where the delay may be reported as a number of slots and/or symbols.
  • 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.
  • 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.
  • 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 first processing time capability for a first type of PUSCH, e.g., as described in connection with 2402 of FIG. 24.
  • the communication manager 2532 further includes a receiving component 2542 that is configured to receive, from the UE, a second processing time capability for a second type of PUSCH, 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 uplink grant for a PUSCH transmission, e.g., as described in connection with 2406 of FIG. 24.
  • the communication manager 2532 further includes a receiving component 2546 that is configured to receive the PUSCH based on a processing time corresponding to the type of the PUSCH transmission, e.g., as described in connection with 2408 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.
  • the apparatus 2502, and in particular the baseband unit 2504 includes means for receiving, from a UE, a first processing time capability for a first type of PUSCH.
  • the apparatus 2502 includes means for receiving, from the UE, a second processing time capability for a second type of PUSCH.
  • the apparatus 2502 includes means for transmitting an uplink grant for a PUSCH transmission.
  • the apparatus 2502 includes means for receiving the PUSCH based on a processing time corresponding to the type of the PUSCH transmission.
  • 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.
  • the apparatus 2502 may include the TX Processor 316, the RX Processor 370, and the controller/processor 375.
  • 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.
  • Example 1 is a method of wireless communication at a UE, comprising: reporting, to a base station, N UE capabilities for N groups of TBS, N being an integer number greater than 1, wherein a first UE capability is reported for a first TBS group and a second UE capability is reported for a second TBS group; receiving downlink communication having a TBS from the base station; and processing the downlink communication from the base station based on a UE capability from the N UE capabilities corresponding to the TBS.
  • Example 2 the method of Example 1 further includes that the UE reports a first UE capability for a first TBS group and reports a second UE capability for a second TBS group.
  • Example 3 the method of Example 1 or Example 2 further comprises: receiving scheduling based on the first UE capability if the TBS is within the first TBS group; and receiving scheduling based on the first UE capability for a first TBS within the first TBS group and based on the second UE capability for a second TBS within the second TBS group.
  • Example 4 the method of any of Examples 1-3 further includes that the UE reports a longer processing time for a first TBS group associated with a larger TBS and reports a shorter processing time for a second TBS group with smaller TBS.
  • each of the N UE capabilities includes one or more of: a minimum delay in slots or symbols between a DL grant and a corresponding PDSCH reception, a minimum delay in slots or symbols between the PDSCH reception and a corresponding UL HARQ feedback transmission, a minimum delay in slots or symbols between an UL grant reception and a corresponding PUSCH transmission, or a minimum delay in slots or symbols between the UL HARQ transmission and a corresponding retransmission of the PDSCH.
  • Example 6 the method of any of Examples 1-5 further comprises: reporting a maximum number of HARQ processes based on a BWP.
  • Example 7 the method of any of Examples 1-6 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.
  • Example 8 the method of any of Examples 1-7 further includes that the UE 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 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.
  • Example 9 the method of any of Examples 1-8 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.
  • Example 10 the method of any of Examples 1-9 further comprises: reporting a maximum number of HARQ processes based on a CC.
  • Example 11 the method of any of Examples 1-10 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.
  • Example 12 the method of any of Examples 1-11 further includes that the UE 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.
  • Example 13 is an apparatus for wireless communication at a UE, comprising: means for reporting, to a base station, N UE capabilities for N groups of TBS, N being an integer number greater than 1, wherein a first UE capability is reported for a first TBS group and a second UE capability is reported for a second TBS group; means for receiving downlink communication having a TBS from the base station; and means for processing the downlink communication from the base station based on a UE capability from the N UE capabilities corresponding to the TBS.
  • 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 first processing time capability for a first type of PUSCH; reporting, to the base station, a second processing time capability for a second type of PUSCH; receiving an uplink grant for a PUSCH transmission; and transmitting the PUSCH based on a processing time corresponding to the type of the PUSCH transmission.
  • Example 18 the method of Example 17 further includes that the first type of the PUSCH includes multiplexed UCI and the second type of the PUSCH does not include the multiplexed UCI.
  • Example 19 the method of Example 17 or Example 18 further includes that the processing time is longer for the PUSCH with the multiplexed UCI than for the PUSCH without the multiplexed UCI.
  • Example 20 the method of any of Examples 17-19 further comprises: determining the processing time based on whether the PUSCH transmission will include multiplexed UCI.
  • Example 21 the method of any of Examples 17-20 further includes that the first processing time capability and the second processing time capability indicate a delay between reception of an uplink grant from the base station and transmission of a corresponding PUSCH transmission by the UE.
  • Example 22 the method of any of Examples 17-21 further includes that the delay is reported as a number of slots.
  • Example 23 the method of any of Examples 17-22 further includes that the delay is reported as a number of symbols.
  • Example 24 the method of any of Examples 17-23 further comprises: reporting a maximum number of HARQ processes based on a BWP.
  • 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.
  • 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.
  • 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.
  • Example 28 the method of any of Examples 17-27 further comprises: reporting a maximum number of HARQ processes based on a CC.
  • 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.
  • 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.
  • 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 first processing time capability for a first type of PUSCH; means for reporting, to the base station, a second processing time capability for a second type of PUSCH; means for receiving an uplink grant for a PUSCH transmission; and means for transmitting the PUSCH based on a processing time corresponding to the type of the PUSCH transmission.
  • Example 33 the apparatus of Example 32 further comprises means to perform the method of any of Examples 18-31.
  • 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, N UE capabilities for N groups of TBS, N being an integer number greater than 1, wherein a first UE capability is received for a first TBS group and a second UE capability is received for a second TBS group; and scheduling the UE for downlink communication having a TBS based on a capability reported by the UE for a group including the TBS.
  • Example 37 the method of Example 36 further includes that the UE reports a first UE capability for a first TBS group and reports a second UE capability for a second TBS group.
  • Example 38 the method of Example 36 or Example 37 further comprises: transmitting scheduling based on the first UE capability if the TBS is within the first TBS group; and transmitting scheduling based on the first UE capability for a first TBS within the first TBS group and based on the second UE capability for a second TBS within the second TBS group.
  • Example 39 the method of any of Examples 36-38 further includes that the UE reports a longer processing time for a first TBS group associated with a larger TBS and reports a shorter processing time for a second TBS group with smaller TBS.
  • Example 40 the method of any of Examples 36-39 further includes that each of the N UE capabilities includes one or more of: a minimum delay in slots or symbols between a DL grant and a corresponding PDSCH reception, a minimum delay in slots or symbols between the PDSCH reception and a corresponding UL HARQ feedback transmission, a minimum delay in slots or symbols between an UL grant reception and a corresponding PUSCH transmission, or a minimum delay in slots or symbols between the UL HARQ transmission and a corresponding retransmission of the PDSCH.
  • each of the N UE capabilities includes one or more of: a minimum delay in slots or symbols between a DL grant and a corresponding PDSCH reception, a minimum delay in slots or symbols between the PDSCH reception and a corresponding UL HARQ feedback transmission, a minimum delay in slots or symbols between an UL grant reception and a corresponding PUSCH transmission, or a minimum delay in slots or symbols between the UL HARQ transmission and a corresponding retransmission of the PD
  • Example 41 the method of any of Examples 36-40 further comprises: receiving an indication of a maximum number of HARQ processes based on a BWP.
  • Example 42 the method of any of Examples 36-41 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.
  • Example 43 the method of any of Examples 36-42 further includes that the base station schedules 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 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.
  • Example 44 the method of any of Examples 36-43 further comprises: configuring the maximum number of HARQ processes in the first BWP and in the second BWP via a RRC for the UE.
  • Example 45 the method of any of Examples 36-44 further comprises: receiving a maximum number of HARQ processes based on a CC.
  • Example 46 the method of any of Examples 36-45 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.
  • Example 47 the method of any of Examples 36-46 further includes that the base station schedules 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 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 CC.
  • Example 48 the method of any of Examples 36-47 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 49 is an apparatus for wireless communication at a base station, comprising: means for receiving, from a UE, N UE capabilities for N groups of TBS, N being an integer number greater than 1, wherein a first UE capability is received for a first TBS group and a second UE capability is received for a second TBS group; and means for transmitting downlink communication having a TBS to the UE.
  • Example 50 the apparatus of Example 49 further comprises means to perform the method of any of Examples 37-48.
  • Example 51 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-48.
  • Example 52 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-48.
  • Example 53 is a method of wireless communication at a base station, comprising: receiving, from a UE, a first processing time capability for a first type of PUSCH; receiving, from the UE, a second processing time capability for a second type of PUSCH; transmitting an uplink grant for a PUSCH transmission; and receiving the PUSCH based on a processing time corresponding to the type of the PUSCH transmission.
  • Example 54 the method of Example 53 further includes that the first type of the PUSCH includes multiplexed UCI and the second type of the PUSCH does not include the multiplexed UCI.
  • Example 55 the method of Example 53 or Example 54 further includes that the processing time is longer for the PUSCH with the multiplexed UCI than for the PUSCH without the multiplexed UCI.
  • Example 56 the method of any of Examples 53-55 further comprises: determining the processing time based on whether the PUSCH transmission will include multiplexed UCI.
  • Example 57 the method of any of Examples 53-56 further includes that the first processing time capability and the second processing time capability indicate a delay between reception of an uplink grant at the UE and transmission of a corresponding PUSCH by the UE.
  • Example 58 the method of any of Examples 53-57 further includes that the delay is reported as a number of slots.
  • Example 59 the method of any of Examples 53-58 further includes that the delay is reported as a number of symbols.
  • Example 60 the method of any of Examples 53-59 further comprises: receiving an indication of a maximum number of HARQ processes based on a BWP.
  • Example 61 the method of any of Examples 53-60 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.
  • Example 62 the method of any of Examples 53-61 further includes that the base station schedules 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 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.
  • Example 63 the method of any of Examples 53-62 further comprises: configuring the maximum number of HARQ processes in the first BWP and in the second BWP via a RRC for the UE.
  • Example 64 the method of any of Examples 53-63 further comprises: receiving an indication of a maximum number of HARQ processes based on a CC.
  • Example 65 the method of any of Examples 53-64 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.
  • Example 66 the method of any of Examples 53-65 further includes that the base station schedules 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 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 CC.
  • Example 67 the method of any of Examples 53-66 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 68 is an apparatus for wireless communication at a base station, comprising: means for receiving, from a UE, a first processing time capability for a first type of PUSCH; means for receiving, from the UE, a second processing time capability for a second type of PUSCH; means for transmitting an uplink grant for a PUSCH transmission; and means for receiving the PUSCH based on a processing time corresponding to the type of the PUSCH transmission.
  • Example 69 the apparatus of Example 68 further comprises means to perform the method of any of Examples 54-67.
  • Example 70 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 53-67.
  • Example 71 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 53-67.
  • Example 72 is yet another method of wireless communication at a user equipment.
  • the method may include one or more optional actions and/or steps (such as those that follow) .
  • the method may include reporting, to a base station, N UE capabilities for N groups of TBS, N being an integer number greater than 1, wherein a first UE capability is reported for a first TBS group and a second UE capability is reported for a second TBS group.
  • the method may also include receiving downlink communication having a TBS from the base station. Further, the method may optionally include processing the downlink communication from the base station based on a UE capability from the N UE capabilities corresponding to the TBS.
  • Example 73 is yet another method of wireless communication at a user equipment.
  • the method may include one or more optional actions and/or steps (such as those that follow) .
  • the method may include reporting, to a base station, a first processing time capability for a first type of PUSCH.
  • the method may also include reporting, to the base station, a second processing time capability for a second type of PUSCH.
  • the method may optionally include receiving an uplink grant for a PUSCH transmission.
  • the method may optionally include transmitting the PUSCH based on a processing time corresponding to the type of the PUSCH transmission.
  • Example 74 is yet another method of wireless communication at a base station.
  • the method may include one or more optional actions and/or steps (such as those that follow) .
  • the method may include receiving, from a UE, N UE capabilities for N groups of TBS, N being an integer number greater than 1, wherein a first UE capability is received for a first TBS group and a second UE capability is received for a second TBS group.
  • the method may also include scheduling the UE for downlink communication having a TBS based on a capability reported by the UE for a group including the TBS.
  • Example 75 is yet another method of wireless communication at a base station.
  • the method may include one or more optional actions and/or steps (such as those that follow) .
  • the method may include receiving, from a UE, a first processing time capability for a first type of PUSCH.
  • the method may also include receiving, from the UE, a second processing time capability for a second type of PUSCH.
  • the method may optionally include transmitting an uplink grant for a PUSCH transmission.
  • the method may optionally include receiving the PUSCH based on a processing time corresponding to the type of the PUSCH transmission.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des aspects de la présente invention peuvent permettre à des UE à capacité réduite de prendre en charge un certain type de services avec un retard strict mais un débit limité, tandis que des ressources matérielles ou informatiques moins parallèles peuvent être utilisées par les UE à capacité réduite. Selon un aspect de l'invention, un UE rapporte, à une station de base, N capacités d'UE pour N groupes de TBS, N étant un nombre entier supérieur à 1, et une première capacité d'UE étant rapportée pour un premier groupe TBS et une seconde capacité d'UE étant rapportée pour un second groupe TBS. Ensuite, l'UE reçoit une communication de liaison descendante ayant une TBS provenant de la station de base. Ensuite, l'UE traite la communication de liaison descendante à partir de la station de base sur la base d'une capacité d'UE à partir des N capacités d'UE correspondant à la TBS.
PCT/CN2020/108590 2020-08-12 2020-08-12 Configuration d'équipement utilisateur spécifique de processus harq pour une réduction de complexité de capacité réduite Ceased WO2022032509A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2020/108590 WO2022032509A1 (fr) 2020-08-12 2020-08-12 Configuration d'équipement utilisateur spécifique de processus harq pour une réduction de complexité de capacité réduite
PCT/CN2021/112050 WO2022033515A1 (fr) 2020-08-12 2021-08-11 Configuration d'équipement utilisateur spécifique à un processus de demande harq pour une réduction de complexité de capacité réduite

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/108590 WO2022032509A1 (fr) 2020-08-12 2020-08-12 Configuration d'équipement utilisateur spécifique de processus harq pour une réduction de complexité de capacité réduite

Publications (1)

Publication Number Publication Date
WO2022032509A1 true WO2022032509A1 (fr) 2022-02-17

Family

ID=80247501

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/108590 Ceased WO2022032509A1 (fr) 2020-08-12 2020-08-12 Configuration d'équipement utilisateur spécifique de processus harq pour une réduction de complexité de capacité réduite

Country Status (1)

Country Link
WO (1) WO2022032509A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4651413A1 (fr) * 2024-05-14 2025-11-19 Samsung Electronics Co., Ltd. Équipement utilisateur configuré pour effectuer une communication sans fil avec une station de base et procédé de fonctionnement d'un équipement utilisateur

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190222356A1 (en) * 2018-01-12 2019-07-18 Qualcomm Incorporated Timing considerations for aul-dfi
CN110830184A (zh) * 2018-08-09 2020-02-21 北京三星通信技术研究有限公司 块传输方法、下行传输方法、nrs接收方法、ue、基站和介质

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190222356A1 (en) * 2018-01-12 2019-07-18 Qualcomm Incorporated Timing considerations for aul-dfi
CN110830184A (zh) * 2018-08-09 2020-02-21 北京三星通信技术研究有限公司 块传输方法、下行传输方法、nrs接收方法、ue、基站和介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "3GPP TSG RAN WG1 Meeting AH_NR#3 R1-1715408", HARQ TIMING， MULTIPLEXING， AND BUNDLING, 21 September 2017 (2017-09-21), XP051338876 *
INTEL CORPORATION: "3GPP TSG RAN WG1 Meeting #90 R1-1712598", PROCESSING TIMES AND HARQ PROCESSES IN NR, 25 August 2017 (2017-08-25), XP051315413 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4651413A1 (fr) * 2024-05-14 2025-11-19 Samsung Electronics Co., Ltd. Équipement utilisateur configuré pour effectuer une communication sans fil avec une station de base et procédé de fonctionnement d'un équipement utilisateur

Similar Documents

Publication Publication Date Title
US12016019B2 (en) Multiple TRP PDSCH scheduling using DCI without TCI field
US12127242B2 (en) Transmission time implicitly triggering UCI multiplexing on PUSCH with different priorities
US11812431B2 (en) Methods and apparatus for monitoring DL communication with timing offsets
US12052745B2 (en) UL transmission control
US11791944B2 (en) UE triggered one-shot HARQ-ACK feedback
US12114340B2 (en) Apparatus and method for monitoring for a control signal in a resource block
US12150122B2 (en) Collision handling for parallel uplink transmission
US11984983B2 (en) Carrier selection for PUCCH repetition with PUCCH carrier switching
US11825499B2 (en) CSI report and DL grant
US11728873B2 (en) Early beam failure detection
US11509350B2 (en) Methods and apparatus to facilitate hopping of measurement occasions for transmissions
US11811699B2 (en) Full-duplex turbo HARQ-ACK
US12160876B2 (en) Simultaneous Rx/Tx for multiple carriers
WO2022033515A1 (fr) Configuration d'équipement utilisateur spécifique à un processus de demande harq pour une réduction de complexité de capacité réduite
US12052750B2 (en) Different modulation orders and number of MIMO layers for HP and LP UCI multiplexing on PUSCH
US12177018B2 (en) PUCCH/PUSCH DMRS bundling duration
US20220361214A1 (en) Harq-ack multiplexing on pusch in ul ca
US12047944B2 (en) Partial PUSCH repetition configuration
US12149321B2 (en) Partial beam failure report
US12452902B2 (en) Building transport blocks in wireless networks
US11979884B2 (en) HARQ timing for multi-PDSCH grant
WO2022032509A1 (fr) Configuration d'équipement utilisateur spécifique de processus harq pour une réduction de complexité de capacité réduite
US20220240242A1 (en) Methods and apparatus for utilizing ul symbols for deferred sps harq-ack transmissions
US11690075B2 (en) Multi-slot blind detection limits
US12376167B2 (en) Techniques to facilitate prioritizing packet data convergence protocol (PDCP) protocol data units in dual connectivity

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20949008

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20949008

Country of ref document: EP

Kind code of ref document: A1