WO2021217678A1 - Opportunités de planification semi-persistante pour trafic périodique instable - Google Patents

Opportunités de planification semi-persistante pour trafic périodique instable Download PDF

Info

Publication number
WO2021217678A1
WO2021217678A1 PCT/CN2020/088538 CN2020088538W WO2021217678A1 WO 2021217678 A1 WO2021217678 A1 WO 2021217678A1 CN 2020088538 W CN2020088538 W CN 2020088538W WO 2021217678 A1 WO2021217678 A1 WO 2021217678A1
Authority
WO
WIPO (PCT)
Prior art keywords
sps
sps occasion
base station
occasion
pucch resource
Prior art date
Application number
PCT/CN2020/088538
Other languages
English (en)
Inventor
Yisheng Xue
Jing Sun
Xiaoxia Zhang
Chih-Hao Liu
Ozcan Ozturk
Tao Luo
Juan Montojo
Peter Gaal
Mostafa KHOSHNEVISAN
Piyush Gupta
Changlong Xu
Original Assignee
Qualcomm Incorporated
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 Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2020/088538 priority Critical patent/WO2021217678A1/fr
Priority to US17/904,784 priority patent/US20220416955A1/en
Priority to EP21797402.1A priority patent/EP4144165A1/fr
Priority to PCT/CN2021/091455 priority patent/WO2021219129A1/fr
Priority to CN202180030536.6A priority patent/CN115443722A/zh
Publication of WO2021217678A1 publication Critical patent/WO2021217678A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • 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/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/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows

Definitions

  • the present disclosure relates generally to communication systems, and more particularly, to wireless communication including semi-persistent scheduling (SPS) .
  • SPS semi-persistent scheduling
  • 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
  • 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 at a user equipment (UE) .
  • the apparatus receives a configuration for a plurality of semi-persistent scheduling (SPS) occasions each SPS occasion including multiple opportunities for a downlink transmission by a base station.
  • SPS semi-persistent scheduling
  • the apparatus monitors for the downlink transmission during one or more opportunities of an SPS occasion.
  • a method, a computer-readable medium, and an apparatus are provided for wireless communication at a base station.
  • the apparatus configures a UE for a plurality of SPS occasions, each SPS occasion including multiple opportunities for downlink transmission by the base station.
  • the apparatus transmits a packet to the UE in an opportunity of an SPS occasion based on an arrival time of the packet.
  • 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.
  • FIGs. 2A, 2B, 2C, and 2D are diagrams illustrating examples of a first 5G/NR frame, DL channels within a 5G/NR subframe, a second 5G/NR frame, and UL channels within a 5G/NR subframe, respectively.
  • 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 illustrates example aspects of jittered period traffic.
  • FIG. 5 illustrates an example of SPS occasions for jittered periodic traffic.
  • FIG. 6 illustrates SPS occasions for multiple hybrid automatic repeat request (HARQ) processes for jittered periodic traffic.
  • HARQ hybrid automatic repeat request
  • FIG. 7 illustrates an example of SPS occasions for a single HARQ process including multiple opportunities in accordance with aspects presented herein.
  • FIG. 8 illustrates an example of SPS occasions for a single HARQ process including multiple opportunities and example resources for feedback in accordance with aspects presented herein.
  • FIG. 9 illustrates an example of SPS occasions for a single HARQ process including multiple opportunities and example resources for feedback in accordance with aspects presented herein.
  • FIG. 10 illustrates an example of SPS occasions for a single HARQ process including multiple opportunities and example resources for feedback in accordance with aspects presented herein.
  • FIG. 11 illustrates an example of SPS occasions for a single HARQ process including multiple opportunities and example resources for feedback in accordance with aspects presented herein.
  • FIG. 12 illustrates an example of SPS occasions for a single HARQ process including multiple opportunities and example resources for feedback in accordance with aspects presented herein.
  • FIG. 13 illustrates an example of SPS occasions for a single HARQ process including multiple opportunities and example resources for feedback in accordance with aspects presented herein.
  • FIG. 14 illustrates an example of SPS occasions for a single HARQ process including multiple opportunities and example resources for feedback in accordance with aspects presented herein.
  • FIG. 15 illustrates an example of SPS occasions for a single HARQ process including multiple opportunities and example aspects for scheduling a retransmission in accordance with aspects presented herein.
  • FIG. 16 is a flowchart of a method of wireless communication at a UE in accordance with aspects presented herein.
  • FIG. 17 is a flowchart of a method of wireless communication at a base station 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.
  • Downlink packets may arrive at a base station 102 or 180 in a periodic manner, and SPS resources may be provided for the transmission of the downlink packets to a UE 104.
  • the downlink traffic may have a jittered arrival.
  • Aspects presented herein provide SPS resources that enable the periodic transmission of downlink packets that may experience a jittered arrival at a base station 102 or 180 for transmission to the UE 104.
  • the aspects presented herein may enable low latency downlink traffic to be communicated to the UE 104 in a manner that balances the latency of the communication with efficient scheduling of resources and reducing processing complexity for the UE.
  • the base station 102 or 180 may include an SPS schedule component 199 that configures a UE 104 for monitoring a plurality of SPS occasions, each SPS occasion including multiple opportunities for downlink transmission by the base station 102 or 180. Then, the base station 102 or 180 may transmit a packet to the UE 104 in an opportunity of an SPS occasion based on an arrival time of the packet.
  • the UE 104 may include an SPS component 198 that receives the configuration for the plurality of SPS occasions from the base station 102 or 180, each SPS occasion including multiple opportunities for a downlink transmission by the base station 102 or 180.
  • the UE 104 may monitor for the downlink transmission during one or more opportunity of the SPS occasion, e.g., until an opportunity in which the UE receives the downlink packet (s) .
  • the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.
  • 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 base stations 102 configured for 4G LTE may interface with the EPC 160 through backhaul links 132 (e.g., S1 interface) .
  • the base stations 102 configured for 5G NR may interface with core network 190 through backhaul links 184.
  • NG-RAN Next Generation RAN
  • 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 backhaul links 134 (e.g., X2 interface) .
  • the 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, FlashLinQ, WiMedia,
  • 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 in a 5 GHz unlicensed frequency spectrum.
  • AP Wi-Fi access point
  • STAs Wi-Fi stations
  • communication links 154 in a 5 GHz unlicensed frequency spectrum.
  • the STAs 152 /AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
  • 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 5 GHz unlicensed frequency spectrum 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.
  • a base station 102 may include 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 (mmW) frequencies, and/or near mmW frequencies in communication with the UE 104.
  • mmW millimeter wave
  • mmW millimeter wave
  • mmW base station Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters.
  • Radio waves in the band may be referred to as a millimeter wave.
  • Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters.
  • the super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave.
  • Communications using the mmW /near mmW radio frequency band (e.g., 3 GHz –300 GHz) has extremely high path loss and a short range.
  • the mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.
  • 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 a 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 PS Streaming Service, and/or other IP services.
  • IMS IP Multimedia Subsystem
  • the base station may also be referred to as a gNB, Node B, evolved 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 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 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.
  • 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 X is flexible for use between DL/UL, and subframe 3 being configured with slot format 34 (with mostly UL) .
  • 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 5 allow for 1, 2, 4, 8, 16, and 32 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 5.
  • ⁇ is the numerology 0 to 5.
  • the symbol length/duration is inversely related to the subcarrier spacing.
  • the subcarrier spacing is 15 kHz and symbol duration is approximately 66.7 ⁇ s.
  • 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 x for one particular configuration, where 100x is the port number, 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) , each CCE including nine RE groups (REGs) , each REG including four consecutive REs in an OFDM symbol.
  • 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.
  • 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 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 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 SDU
  • 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 318TX.
  • Each transmitter 318TX may modulate an RF carrier with a respective spatial stream for transmission.
  • each receiver 354RX receives a signal through its respective antenna 352.
  • Each receiver 354RX 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
  • 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 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 199 of FIG. 1.
  • Downlink packets may arrive at a base station (e.g., the base station 102 or 180) in a periodic manner.
  • the base station may allocate SPS resources for the transmission of the downlink packets to a UE (e.g., the UE 104) .
  • the downlink traffic may have a jittered arrival.
  • FIG. 4 illustrates an example timeline 400 showing the scheduled arrival times 402, 404, and 406 of periodic downlink packets.
  • the arrival time may correspond to a time at which a base station expects to receive the downlink packets for transmission to the UE.
  • the pattern in FIG. 4 illustrates packets having a nominal arrival time of every T seconds.
  • the actual arrival time of the downlink packet may vary, e.g., may arrive at a non-deterministic instant.
  • the packets may have a jittered arrival with respect to the scheduled arrival pattern.
  • the packet may comprise a small size packet, e.g., of less than 50 bytes, e.g., a 40 byte or smaller packet.
  • FIG. 4 illustrates the actual arrival of the first packet at the first scheduled arrival time 402 being ⁇ 1 prior to the scheduled arrival time 402.
  • the second packet arrives ⁇ 2 following the scheduled arrival time 404.
  • the third packet arrives ⁇ 3 following the scheduled arrival time 406.
  • the actual arrival time may be within a random amount of time ⁇ i around (e.g., before or after) the ith epoch.
  • the packet may have a small packet size.
  • the packets may be associated with a low latency, e.g., for correct delivery within an interval T v that may be smaller than the period T, e.g., T v ⁇ T.
  • the communication may include industrial IoT (IIoT) that includes periodic, low-latency downlink traffic.
  • IIoT industrial IoT
  • the characteristics and periodicity of the downlink packets may be scheduled in an efficient manner based on SPS resources.
  • the efficient scheduling of the transmissions may be helpful, e.g., to a base station that supports a massive number of UEs and may provide periodic downlink packets to the UEs.
  • the jittered arrival of the downlink packets presents a challenge to the base station in scheduling the downlink transmission using SPS resources.
  • the base station may schedule the downlink transmissions using dynamic grants
  • the dynamic grants involve a significant amount of added signaling between the base station and the UEs. The added overhead may become especially difficult for a base station supporting a number of such UEs.
  • FIG. 5 illustrates an example timeline 500 showing the scheduled arrival times 502, 504, and 506 of periodic downlink packets and the jittered actual arrival times 512, 514, and 516 that is similar to the jittered arrival of packets in FIG. 4.
  • the base station configures the SPS downlink occasion to be later than the possible ⁇ i so that the traffic arrival is before the SPS occasions 522, 524, 526.
  • the base station will be able to use the SPS downlink resource allocated for transmission of the periodic packets, e.g., without wasting an SPS resources that occurs before the packet arrives or without resorting to a dynamic grant.
  • the SPS occasions add delay to the packet by waiting until after the latest time at which the packet may arrive even if the downlink packet arrives earlier.
  • FIG. 6 illustrates an example timeline 600 showing the scheduled arrival times 602, 604, and 606 of periodic downlink packets and the jittered actual arrival times 612, 614, and 616 that is similar to the jittered arrival of packets in FIGs. 4 and 5.
  • the base station may configure multiple SPS processes around the nominal arrival instant (e.g., providing times based on the potential for arrival before or after the nominal arrival time) .
  • the base station configures a first SPS process 620, a second SPS process 630, and a third SPS process 640, each having an SPS occasion for each scheduled packet arrival.
  • the 6 involves orthogonal sets of HARQ processes to be assigned together with multiple PUCCH transmissions from the UE providing feedback for the different SPS processes.
  • the number of PUCCH transmissions may be reduced through the selection of the number of SPS processes.
  • the use of multiple SPS processes may lead to multiple HARQ NACKs.
  • Additional, the example involves added complexity at the UE in order to support multiple downlink SPS configurations.
  • Some UEs, such as reduced capability UEs, may not support multiple downlink SPS configurations.
  • aspects presented herein provide SPS resources that enable the periodic transmission of downlink packets that may experience a jittered arrival at a base station.
  • the aspects presented herein may enable low latency downlink traffic to be communicated to the UE in a manner that balances the low latency of the communication with efficient scheduling of resources and reduced processing complexity for the UE.
  • Aspects presented herein may improve the periodic communication of small, low-latency packets, e.g., to reduced capability UEs.
  • FIG. 7 illustrates an example timeline 700 showing the scheduled arrival times 702, 704, and 706 of periodic downlink packets and the jittered actual arrival times 712, 714, and 716 that is similar to the jittered arrival of packets in FIGs. 4, 5, and 6.
  • the base station provides multiple opportunities for each SPS occasion. For example, at a first SPS occasion, the base station provides opportunities 722a, 722b, and 722c. The opportunities correspond to potential resources allocated for the downlink transmission. At a second SPS occasion, the base station provides opportunities 724a, 724b, and 724c, and at a third SPS occasion, the base station provides opportunities 726a, 726b, and 726c.
  • the base station may configure a multiple slot configured-grant (CG) for the downlink transmission from the base station.
  • the base station may transmit the packet, according to its arrival, over the next slot, e.g., in any of the opportunities of the corresponding SPS occasion.
  • the packet with the actual arrival time of 712 may be transmitted in opportunity 722a
  • the packet with the actual arrival time of 714 may be transmitted in opportunity 724c
  • the packet with the actual arrival time of 716 may be transmitted in opportunity 726b.
  • the multiple opportunities of the SPS configuration in FIG. 7 enables the downlink packet to be transmitted to the UE with reduced latency, e.g. in comparison to the example in FIG. 5.
  • the SPS occasions may correspond to a single HARQ process and may involve a reduced HARQ response, e.g., in comparison to the example in FIG. 6.
  • the UE may send an ACK if CRC is passed over any slot of the SPS occasion. If not, the UE may send a NACK.
  • the aspects of FIG. 7 may enable the UE to turn off its receiver, e.g., after a passing CRC, which may enable power savings at the UE.
  • aspects may enable efficient communication with reduced capability devices that may not support the multiple SPS configurations described in connection with FIG. 6.
  • the aspects presented herein support massive reduced capability UEs (which may be referred to in some examples as NR-light UEs) with jittered periodic traffic.
  • the massive UE numbers may benefit from the SPS resources rather than a dynamic grant (DG) -based solution in which the PDCCH may be a bottleneck that limits communication.
  • Massive UE numbers may also challenge the configuration and activation/re-activation of multi-SPS configurations, such as the described in connection with FIG. 6.
  • the aspects presented herein operate with reduced HARQ processes and reduced HARQ responses in comparison with the multi-SPS configuration described in connection with FIG. 6.
  • the base station may configure the UE to support the multiple opportunity SPS downlink communication described in connection with FIG. 7.
  • the base station may configure the UE via RRC to monitor for downlink communication based on a multiple opportunity SPS configuration.
  • the UE may be configured for any number of s > 1 number of opportunities per SPS occasion.
  • the number opportunities may correspond to a number of slots of SPS resources starting from an offset time from the scheduled arrival time. The offset may provide at least one opportunity prior to the scheduled arrival time, as illustrated in FIG. 7.
  • the base station may transmit the packet to the UE in an opportunity of the corresponding SPS occasion. For example, the base station may transmit the packet to the UE in a single opportunity of the SPS occasion, e.g., without transmitting the packet in multiple opportunities of the SPS occasion.
  • the UE may perform blind decoding of the SPS PDSCH at each opportunity (e.g., at 722a, 722b, and 722c for the first SPS occasion) .
  • Each SPS occasion may correspond to one HARQ process that is shared by the multiple opportunities of the SPS occasion, e.g., in contrast to the example in FIG. 6.
  • the same HARQ ID determination mechanism may be used as for an SPS occasion having a single opportunity, such as described in connection with FIG. 5.
  • FIG. 8 illustrates an example in which the base station may allocate a single, shared resource for ACK/NACK feedback from the UE.
  • the UE successfully receives the downlink packet in a first opportunity of the SPS occasion corresponding to HARQ 0.
  • the UE may transmit ACK/NACK feedback in the single PUCCH resource 802.
  • each of the opportunities of the SPS occasion map to the same PUCCH reporting instance.
  • the UE may reporting a multiple bit ACK/NACK that provides individual feedback for each of the opportunities. For example, for s opportunities, the UE may report an s bit ACK/NACK with 1 bit for each opportunity.
  • the UE may indicate an ACK in a bit corresponding to the first opportunity, and may indicate a NACK in the bits of the other two opportunities.
  • the downlink packet was transmitted in the second opportunity, but was not successfully received by the UE, e.g., due to low SINR. Therefore, the UE may indicate a NACK for each of the bits of the PUCCH.
  • the timing of the PUCCH may be configured through DCI activation. In some examples, at most one ACK bit may be included in the ACK codebook.
  • the sequence of ACK positions in the PUCCH may be used by the base station for proactive SPS reactivation if arrival drifting occurs.
  • the base station may provide a dynamic grant, e.g. DCI 804, to schedule a retransmission of a downlink packet that was not successfully received for a particular SPS occasion.
  • the base station may send a dynamic grant in the DCI 804 that indicates the HARQ ID of the corresponding SPS occasion (e.g., HARQ 0) as an index that indicates to the UE the downlink packet that will be retransmitted.
  • the DCI might not identify the particular opportunity in which the initial packet was transmitted.
  • the UE may perform a HARQ combination of the retransmission with the SPS opportunity of the initial transmission.
  • the UE may use the HARQ ID to identify the SPS occasion of the initial transmission.
  • the UE may determine the opportunity of the identified SPS occasion that has a maximum likelihood of the downlink packet. The maximum likelihood may be based on the blind PDSCH decoding performed by the UE, e.g., based on a metric for the DMRS sequence detection, etc.
  • the UE may perform HARQ combining of the retransmission with the determined opportunity of the SPS occasion.
  • the base station may provide an indication to the UE that enables the UE to determine the opportunity of the SPS occasion to use for HARQ combining with the retransmission.
  • FIG. 15 illustrates an example time diagram 1500 showing an example indication by the base station.
  • the base station may use a coincidence between a time domain resource allocation (TDRA) in a retransmission dynamic grant, e.g., in DCI 1504, and that of the SPS opportunity for the initial transmission of the downlink packet to indicate to the UE the opportunity for performing HARQ combination with the retransmission.
  • TDRA time domain resource allocation
  • the initial transmission for the SPS occasion associate with HARQ 0 may include multiple opportunities, such as described in connection with FIG. 7. Each opportunity in FIG.
  • the base station may send a dynamic grant that indicates a corresponding starting time offset with respect to a slot boundary as the opportunity in which the packet was initially transmitted. For example, in FIG. 15, the packet was transmitted in the third opportunity of the SPS occasion, having a time offset of 2 ⁇ relative to the slot boundary.
  • the DCI 1504 indicates the HARQ process, e.g., HARQ0 and schedules the retransmission with the same time offset as the third opportunity, e.g., 2 ⁇ relative to a slot boundary.
  • the UE may use the time offset to identify the corresponding opportunity of the SPS occasion. After determining the opportunity that was indicated as including the initial downlink packet, the UE may perform HARQ combining of the retransmission with the determined opportunity of the SPS occasion.
  • FIG. 9 illustrate examples 900 and 950 of a single PUCCH instance 902 having combined ACK/NACK feedback for each of the opportunities of the SPS occasion.
  • the UE may have a single configured PUCCH reporting instance 902.
  • the base station may report a single ACK or a single NACK for the SPS occasion.
  • the UE may report a single bit ACK/NACK with respect to each of the opportunities of the SPS occasion.
  • the UE did not successfully receive the downlink packet that was transmitted in the third opportunity of the SPS occasion corresponding to HARQ0. Therefore, the UE sends a NACK in the PUCCH 902.
  • the UE successfully receives the downlink packet in the first opportunity of the SPS occasion and transmits an ACK in the PUCCH 902.
  • the UE may transmit an ACK when the UE receives PDSCH that passes CRC in any opportunity of the SPS occasion. Otherwise, the UE may send a NACK.
  • the UE may enter a sleep state, e.g., a micro-sleep, a reduced power mode, turning of the receiver, etc., between the successful receipt of the downlink packet and the PUCCH 902.
  • the UE may conduct a micro-sleep after detecting a CRC pass, such as staying in a discontinuation reception (DRX) off mode.
  • DRX discontinuation reception
  • each opportunity may correspond to a discontinuous transmission (DTX) by the base station.
  • the base station may schedule the retransmission in a dynamic grant, as described in connection with FIG. 8.
  • the UE may perform HARQ combination for the retransmission as described in connection with either FIG. 8 or FIG. 15.
  • FIG. 10 illustrates an example 1000 having multiple PUCCH opportunities 1002a, 1002b, 1002c, and 1004.
  • the UE may transmit at most two PUCCH transmissions.
  • the base station may provide an ACK only PUCCH opportunity for each of s-1 SPS opportunities that enables an early ACK for a successfully received downlink packet.
  • the PUCCH opportunities enable the UE to provide an ACK to the base station more quickly than the examples in FIGs. 8 and 9. Additionally, by limiting the feedback in the PUCCH resources 1002a, 1002b, and 1002c to an ACK helps to reduce the amount of signaling from the UE.
  • the last PUCCH resources 1004 after the last opportunity of the SPS occasion may be configured in any of various ways.
  • the PUCCH resource 1004 may have a different time, frequency, and/or format than the other PUCCH resources 1002a, 1002b, and 1002c.
  • the PUCCH resource 1004 may be configured for ACK/NACK feedback, whereas the PUCCH resources 1002a, 1002b, and 1002c may be configured for ACK feedback but not for NACK feedback.
  • the UE may send an ACK in the PUCCH resource corresponding to the opportunity in which the downlink packet was received and may send an ACK in the PUCCH resource 1004, e.g., two ACKs.
  • the UE may send an ACK in the PUCCH resource corresponding to the opportunity in which the downlink packet was received without sending an ACK in the PUCCH resource 1004. If the packet is not successfully received in any of the opportunities, the base station may send a NACK in the PUCCH resource 1004. The base station may schedule the retransmission in a dynamic grant, as described in connection with FIG. 8. The UE may perform HARQ combination for the retransmission as described in connection with either FIG. 8 or FIG. 15.
  • FIG. 11 illustrates a set of examples having multiple PUCCH opportunities 1102a, 1102b, 1102c, e.g., one for each opportunity of the SPS occasion.
  • the UE may transmit at most one PUCCH transmission.
  • the base station may provide s PUCCH opportunities, e.g., one for each of the s SPS opportunities.
  • the PUCCH opportunities enables an early ACK for a successfully received downlink packet.
  • Each of the PUCCH opportunities may be configured for ACK but not for NACK.
  • the UE transmits an ACK in the PUCCH 1102a after successfully receiving the downlink packet in the first opportunity.
  • the UE does not transmit any feedback, e.g., does not transmit in the PUCCH 1102a, 1102b, or 1102c because the UE did not successfully receive the downlink packet in any of the opportunities of the SPS occasion.
  • the PUCCH opportunities enable the UE to provide an ACK to the base station more quickly than the examples in FIGs. 8 and 9.
  • the last PUCCH 1102c is for ACK and not for NACK.
  • the UE may transition to a micro-sleep after transmitting the ACK, e.g., operating during the remaining opportunities of the SPS occasion in a DRX off mode.
  • the base station may schedule the retransmission in a dynamic grant, as described in connection with FIG. 8.
  • the UE may perform HARQ combination for the retransmission as described in connection with either FIG. 8 or FIG. 15.
  • FIG. 12 illustrates a set of examples showing a single PUCCH resource 1202 that is configured for ACK/NACK feedback.
  • the PUCCH resource 1202 may correspond to a PUCCH resource for the last SPS opportunity of the SPS occasion.
  • the UE may perform DTX in the PUCCH resource 1202 by not transmitting any feedback in the PUCCH resource 1202, e.g., if the UE has previously sent an ACK in another PUCCH resource 1204.
  • the UE may transmit an ACK in the PUCCH resource 1202.
  • the UE may transmit the ACK if a successfully received downlink packet has not previously been acknowledged.
  • the UE may transmit a NACK in the PUCCH resource 1202 if the downlink packet was not successfully received in any of the opportunities of the SPS occasion.
  • the UE may be configured with other PUCCH resources that are for ACK but not NACK.
  • the base station may schedule the retransmission in a dynamic grant, as described in connection with FIG. 8 if the base station detects a NACK in the PUCCH resource 1202 or if the base station detects DTX in PUCCH resources for each of the SPS opportunities.
  • the UE may perform HARQ combination for the retransmission as described in connection with either FIG. 8 or FIG. 15.
  • FIG. 13 illustrates a set of examples showing a single PUCCH resource 1302 that is configured for ACK/NACK feedback.
  • the PUCCH resource 1302 may correspond to a PUCCH resource for the last SPS opportunity of the SPS occasion.
  • the UE may transmit an ACK in the PUCCH resource 1302 even though the UE sent an ACK in another PUCCH resource 1304, in contrast to the example 1200 in FIG. 12.
  • the UE may transmit a single ACK in the PUCCH resource 1302 if the UE successfully receives the downlink packet in the last SPS opportunity of the SPS occasion.
  • the UE may transmit a NACK in the PUCCH resource 1302 if the downlink packet was not successfully received in any of the opportunities of the SPS occasion.
  • the UE may be configured with other PUCCH resources that are for ACK but not NACK.
  • the UE may send up to two ACKs, e.g., as in the example 1300, but may send a single NACK.
  • the base station may schedule the retransmission in a dynamic grant, as described in connection with FIG. 8 if the base station detects a NACK in the PUCCH resource 1302 or if the base station detects DTX in PUCCH resources for each of the SPS opportunities.
  • the UE may perform HARQ combination for the retransmission as described in connection with either FIG. 8 or FIG. 15.
  • FIG. 14 illustrates a set of examples showing an additional PUCCH resource 1402 that is provided in addition to the individual PUCCH resources for each SPS opportunity of the SPS occasion.
  • the additional PUCCH resource 1402 may be provided after the last SPS opportunity of the SPS occasion.
  • the PUCCH resource 1302 corresponded to the PUCCH resource for the last SPS occasion.
  • the additional PUCCH resource 1402 is provided in addition to a PUCCH resource for the last SPS opportunity.
  • the other PUCCH resources may be configured for ACK but not NACK.
  • the additional PUCCH resource 1402 may be configured to ACK and NACK.
  • the additional PUCCH resource may be delayed in time compared to the other PUCH resources.
  • the additional PUCCH resource may be separated, e.g., separated in time and/or frequency from the other PUCCH resources corresponding to individual SPS opportunities.
  • the UE may transmit an ACK in the PUCCH resource 1402 even though the UE sent an ACK in another PUCCH resource 1404.
  • the UE may transmit an ACK in the PUCCH resource 1402 1402 even though the UE sent an ACK in another PUCCH resource 1404.
  • the UE may transmit a NACK in the PUCCH resource 1402 if the downlink packet was not successfully received in any of the opportunities of the SPS occasion.
  • the UE may send up to two ACKs, e.g., as in the examples 1400 and 1450, but may send a single NACK.
  • the base station may schedule the retransmission in a dynamic grant, as described in connection with FIG. 8 if the base station detects a NACK in the PUCCH resource 1402 or if the base station detects DTX in PUCCH resources for each of the SPS opportunities.
  • the UE may perform HARQ combination for the retransmission as described in connection with either FIG. 8 or FIG. 15.
  • FIGs. illustrate the concepts using an example of three SPS opportunities per SPS occasion, the concepts may be applied to any number of SPS opportunities in an SPS occasion.
  • the UE may transmit feedback differently when the UE transmits the ACK/NACK feedback in a PUSCH transmission, e.g., piggybacked with a PUSCH transmission or multiplexed with a PUSCH transmission.
  • the UE may determine to report either ACK or NACK for a PDSCH in the SPS occasion or the SPS opportunity if the UE multiplexes the HARQ feedback with PUSCH.
  • the UE may transmit a NACK when the HARQ feedback is multiplexed with PUSCH, e.g., piggybacked with the PUSCH.
  • ACK only limitations may be applicable when the HARQ feedback is not multiplexed with PUSCH and may not be applicable when the HARQ feedback is multiplexed with the PUSCH.
  • FIG. 16 is a flowchart 1600 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; 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 The method improves the efficient use of resources for jittered periodic traffic.
  • the 1602 the UE receives a configuration for a plurality of SPS occasions each SPS occasion including multiple opportunities for a downlink transmission by a base station.
  • the plurality of SPS occasions may be for a single SPS configuration.
  • the multiple opportunities of the SPS occasion may be associated with a same HARQ process.
  • each of the multiple opportunities may correspond to a slot starting from an offset for the SPS occasion.
  • each SPS occasion may include multiple opportunities, such as described in connection with FIG. 7.
  • the UE monitors for the downlink transmission during one or more opportunity of an SPS occasion. Monitoring for the downlink transmission may include performing blind decoding for a PDSCH at each opportunity of the SPS occasion until the downlink transmission is successfully received. In some examples, the UE may monitor for the downlink transmission during each of the opportunities of the SPS occasion. In some examples, the UE may monitor for the downlink transmission during the opportunities of the SPS occasion until the UE successfully receives a downlink transmission. If the UE successfully receives the downlink transmission prior to the last opportunity, the UE may stop monitoring for the opportunities of the SPS occasion.
  • each of the multiple opportunities for the SPS occasion may map to a single PUCCH resource for feedback, such as described in connection with FIG. 8 or FIG. 9.
  • the UE may transmit feedback for each of the multiple opportunities for the SPS occasion in the single PUCCH resource, such as described in connection with FIG. 8 or FIG. 9.
  • the feedback may comprise HARQ feedback including at least one bit for each of the multiple opportunities for the SPS occasion.
  • the HARQ feedback may provide individual feedback for each of the opportunities of the SPS occasion, such as described in connection with FIG. 8.
  • the HARQ feedback may include a single bit that provides overall HARQ feedback for the opportunities of the SPS occasion, such as described in connection with FIG. 9.
  • the UE may receive scheduling information for a retransmission in DCI indicating a HARQ process for the SPS occasion as an index for the retransmission.
  • the DCI may identify the HARQ process to inform the UE which downlink transmission is being retransmitted.
  • the UE may perform HARQ combination of the retransmission.
  • the UE may perform the HARQ combination of the retransmission with an opportunity of the SPS occasion having a highest detection metric.
  • the UE may determine the opportunity of the SPS that was most likely to have included the downlink transmission and may perform the HARQ combination based on the UE’s determination.
  • the base station may provide information to the UE to assist the UE in determining which opportunity to use to perform HARQ combination.
  • the DCI scheduling the retransmission may further include a time domain resource allocation for the retransmission.
  • the DCI may indicate a timing offset, such as described in connection with FIG. 15, that helps the UE to identify the opportunity of the SPS occasion that included the initial transmission. Then, at 1624, the UE may determine the opportunity of the SPS occasion for HARQ combination with the retransmission based on the time domain resource allocation for the retransmission.
  • the UE may transmit HARQ feedback having a shared bit for the multiple opportunities of the SPS occasion.
  • the HARQ feedback may include aspects described in connection with any of FIGs. 9, 10, 12, 13, or 14.
  • the UE may enter a sleep state between successfully receiving the downlink transmission in an opportunity of the SPS occasion and transmitting the HARQ feedback or following transmitting the HARQ feedback, e.g., following transmission of an early ACK.
  • FIGs. 9, 11, and 12 illustrate examples in which the UE may transition to a sleep state, a reduced power state, or a state in which the UE does not monitor for the PDSCH following successful receipt of the PDSCH and/or transmission of the HARQ.
  • the UE may receive scheduling for PUCCH resources for providing HARQ feedback for the SPS occasion.
  • the UE may receive scheduling for individual PUCCH resources for one or more of the multiple opportunities of the SPS occasion.
  • FIGs. 10-14 illustrate various examples of PUCCH resources that include individual PUCCH resources for one or more of multiple opportunities of the SPS occasion.
  • the UE may receive scheduling for individual PUCCH resources for each of the multiple opportunities of the SPS occasions.
  • the scheduling may provide the individual PUCCH resources for a subset (e.g., s-1) of the multiple opportunities (e.g., for s opportunities) of the SPS occasion, such as in any of the examples in FIGs. 10, 12, or 13.
  • the scheduling may provide one less individual PUCCH resource (e.g., s-1) than a number (e.g., s with s being an integer number) of the multiple opportunities.
  • the individual PUCCH resources may be limited to use for positive acknowledgments, e.g., such as described in connection with any of FIGs. 10-14.
  • the scheduling may schedule an additional PUCCH resource following the SPS occasion.
  • the additional PUCCH resource may comprise a different time, a different frequency, or a different format than the individual PUCCH resources, e.g., as described in connection with any of FIGs. 10, 12, 13, or 14.
  • the scheduling may provide the individual PUCCH resources for each of the multiple opportunities of the SPS occasion, such as described in connection with FIG. 11 or FIG. 14.
  • the individual PUCCH resources may be limited to use for positive ACKs, e.g., and may be limited from use for NACKs.
  • the UE may transmit an ACK in an individual PUCCH resource and enter a sleep mode following successful receipt of the downlink transmission, if the downlink transmission is successfully received. Then, at 1616, the UE may refrain from sending feedback if the downlink transmission is not successfully received in any of the multiple opportunities of the SPS occasion, e.g., as described in connection with FIG. 11.
  • the scheduling at 1604 may schedule the individual PUCCH resources that are limited to ACKs for a subset (e.g., s-1) of the multiple opportunities of the SPS occasion and schedule a last PUCCH resource following a last opportunity of the SPS occasion for ACK/NACK, e.g., such as described in connection with any of FIGs. 12-14.
  • a subset e.g., s-1
  • a last PUCCH resource following a last opportunity of the SPS occasion for ACK/NACK e.g., such as described in connection with any of FIGs. 12-14.
  • the UE may transmit a single ACK to the base station in an individual PUCCH resource or last PUCCH resource. If the UE does not successfully receive the downlink packet in any of the opportunities of the SPS occasion, the UE may transmit a NACK in the last PUCCH resource.
  • FIG. 12 illustrates an example in which the UE may transmit a single ACK, e.g., in an individual PUCCH resource or the last PUCCH resource.
  • the UE may transmit the ACK to the base station in an individual PUCCH resource and the last PUCCH resource. If the UE does not successfully receive the downlink packet in any of the opportunities of the SPS occasion, the UE may transmit a NACK in the last PUCCH resource.
  • FIG. 13 illustrates an example in which the UE may transmit the ACK multiple times, e.g., in an individual PUCCH resource and a final PUCCH resource.
  • the scheduling may schedule the individual PUCCH resources that are limited to ACKs for each of the multiple opportunities of the SPS occasion and may schedule an additional PUCCH resource following a last opportunity of the SPS occasion for an ACK/NACK, e.g., as described in connection with FIG. 14.
  • the UE may transmit the ACK to the base station in an individual PUCCH resource and the additional PUCCH resource, at 1618, if the downlink is successfully received and may transmit the NACK in the additional resource if the packet is not successfully received in any of the opportunities of the SPS occasion.
  • the UE may adjust feedback based on whether the feedback is piggybacked in PUSCH. For example, the UE may receive the scheduling, at 1604, for a PUCCH resource that is limited to positive ACKs for an opportunity of the SPS occasion. Then, at 1620, the UE may transmit a NACK multiplexed with a PUSCH and corresponding to the opportunity of the SPS occasion.
  • Each block in the aforementioned flowchart of FIG. 16 and/or the aspects that are performed by the UE in any of FIGs. 7-15 may be performed by a component of a UE apparatus that 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 UE includes means for performing the method described in connection with FIG. 16 and/or the aspects performed by the UE in any of FIGs. 7-15.
  • the aforementioned means may be one or more of the aforementioned components of an apparatus and/or a processing system of such an apparatus configured to perform the functions recited by the aforementioned means.
  • the processing system may include a transmission processor, a reception processor, and a controller/processor.
  • the aforementioned means may be memory 360, such as the TX processor 368, the RX processor 356, and/or the controller/processor 359 configured to perform the functions recited by the aforementioned means.
  • FIG. 17 is a flowchart 1700 of a method of wireless communication.
  • the method may be performed by a base station or a component of a base station (e.g., the base station 102, 180, 310; a processing system, 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) .
  • a base station or a component of a base station e.g., the base station 102, 180, 310; a processing system, 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 improves the efficient use of resources for jittered periodic traffic.
  • the base station configures a UE for a plurality of SPS occasions each SPS occasion including multiple opportunities for downlink transmission by the base station.
  • the plurality of SPS occasions may be for a single SPS configuration.
  • the multiple opportunities of the SPS occasion may be associated with a same HARQ process.
  • each of the multiple opportunities may correspond to a slot starting from an offset for the SPS occasion.
  • each SPS occasion may include multiple opportunities, such as described in connection with FIG. 7.
  • the base station transmits a packet to the UE in an opportunity of an SPS occasion based on an arrival time of the packet. For example, the base station may transmit the packet to the UE in a single opportunity from the multiple opportunities of the SPS occasion.
  • each of the multiple opportunities for the SPS occasion map to a single PUCCH resource for feedback, e.g., as described in connection with FIG. 8 or FIG. 9.
  • the base station receives HARQ feedback having at least one bit for each of the multiple opportunities for the SPS occasion, at 1708, such as described in connection with FIG. 8 or FIG. 9.
  • the feedback may comprise HARQ feedback including at least one bit for each of the multiple opportunities for the SPS occasion.
  • the HARQ feedback may provide individual feedback for each of the opportunities of the SPS occasion, such as described in connection with FIG. 8.
  • the HARQ feedback may include a single bit that provides overall HARQ feedback for the opportunities of the SPS occasion, such as described in connection with FIG. 9.
  • the base station may schedule a retransmission in DCI indicating a HARQ process for the SPS occasion as an index for the retransmission, e.g., as described in connection with FIG. 9 and/or FIG. 15.
  • the DCI scheduling the retransmission may further include a time domain resource allocation for the retransmission that indicates the opportunity of the SPS occasion for the UE to use for a HARQ combination with the retransmission, e.g., as described in connection with FIG. 15.
  • the base station may receive HARQ feedback having a shared bit for the multiple opportunities of the SPS occasion.
  • the HARQ feedback may include aspects described in connection with any of FIGs. 9, 10, 12, 13, or 14.
  • the base station may schedule individual PUCCH resources for one or more of the multiple opportunities of the SPS occasion.
  • FIGs. 10-14 illustrate various examples of PUCCH resources that include individual PUCCH resources for one or more of multiple opportunities of the SPS occasion.
  • the scheduling may provide the individual PUCCH resources for a subset of the multiple opportunities of the SPS occasion, such as in any of the examples in FIGs. 10, 12, or 13. For example, the scheduling may provide one less individual PUCCH resource than a number of the multiple opportunities.
  • the individual PUCCH resources may be limited to use for positive acknowledgments, e.g., such as described in connection with any of FIGs. 10-14.
  • the base station may schedule an additional PUCCH resource following the SPS occasion.
  • the additional PUCCH resource may comprise a different time, a different frequency, or a different format than the individual PUCCH resources, e.g., as described in connection with any of FIGs. 10, 12, 13, or 14.
  • the base station may schedule individual PUCCH resources for each of the multiple opportunities of the SPS occasion, such as described in connection with FIG. 11 or FIG. 14.
  • the individual PUCCH resources may be limited to use for positive ACKs, e.g., and may be limited from use for NACKs.
  • the base station may schedule a retransmission of the packet, e.g., at 1716, if a positive acknowledgment is not received in any of the individual PUCCH resources.
  • the base station may schedule the individual PUCCH resources that are limited to ACKs for a subset of the multiple opportunities of the SPS occasion and schedule a final PUCCH resource following a last opportunity of the SPS occasion for ACK/NACK, e.g., such as described in connection with any of FIGs. 12-14.
  • the base station may receive an ACK in an individual PUCCH resource, if the downlink transmission is successfully received by the UE or may determine that the downlink transmission was not successfully received by the UE if the base station does not receive feedback, e.g., such as described in connection with FIG. 11.
  • the base station may schedule s-1 individual PUCCH resources for individual opportunities of the SPS occasion, which are limited to positive ACKs and may schedule a single PUCCH resource following the SPS occasion for an ACK/NACK.
  • the base station may receive a single ACK in an individual PUCCH resource or the last PUCCH resource if the downlink packet is successfully received or may receive a NACK in the last PUCCH resource if the downlink packet is not successfully received.
  • FIG. 12 illustrates examples aspects of a single ACK or a single NACK.
  • the base station may receive the ACK from the UE in an individual PUCCH resource and the final PUCCH resource.
  • FIG. 13 illustrates an example in which the base station may receive the ACK multiple times, e.g., in an individual PUCCH resource and a final PUCCH resource.
  • the base station may schedule, at 1704, the individual PUCCH resources that are limited to ACKs for each of the multiple opportunities of the SPS occasion and may schedule an additional PUCCH resource following a last opportunity of the SPS occasion for an ACK/NACK, e.g., as described in connection with FIG. 14.
  • the base station may receive an ACK in an individual PUCCH resource and the additional PUCCH resource, at 1714.
  • the UE may adjust feedback based on whether the feedback is piggybacked in PUSCH. For example, the base station may schedule a PUCCH resource that is limited to positive ACKs for an opportunity of the SPS occasion. However, the base station receive a NACK from the UE multiplexed with a PUSCH and corresponding to the opportunity of the SPS occasion.
  • Each block in the aforementioned flowchart of FIG. 17 and/or the aspects that are performed by the base station in any of FIGs. 7-15 may be performed by a component of a base station apparatus that 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 base station apparatus includes means for performing the method described in connection with FIG. 17 and/or the aspects performed by the base station in any of FIGs. 7-15.
  • the aforementioned means may be one or more of the aforementioned components of an apparatus and/or a processing system of such an apparatus configured to perform the functions recited by the aforementioned means.
  • the processing system may include a transmission processor, a reception processor, and a controller/processor.
  • the aforementioned means may be memory 360, such as the TX processor 368, the RX processor 356, and/or the controller/processor 359 configured to perform the functions recited by the aforementioned means.
  • Example 1 is a method of wireless communication at a UE, comprising: receiving a configuration for a plurality of SPS occasions each SPS occasion including multiple opportunities for a downlink transmission by a base station; and monitoring for the downlink transmission during one or more opportunity of an SPS occasion.
  • Example 2 the method of Example 1 further includes that the plurality of SPS occasions are for a single SPS configuration.
  • Example 3 the method of Example 1 or Example 2 further includes that the multiple opportunities of the SPS occasion are associated with a same HARQ process.
  • Example 4 the method of any of Examples 1-3 further includes that each of the multiple opportunities corresponds to a slot starting from an offset for the SPS occasion.
  • Example 5 the method of any of Examples 1-4 further includes that monitoring for the downlink transmission includes performing blind decoding for a PDSCH at each opportunity of the SPS occasion until the downlink transmission is successfully received.
  • Example 6 the method of any of Examples 1-5 further includes that each of the multiple opportunities for the SPS occasion map to a single PUCCH resource for feedback, the method comprising: transmitting the feedback for each of the multiple opportunities for the SPS occasion in the single PUCCH resource.
  • Example 7 the method of any of Examples 1-6 further includes that the feedback comprises HARQ feedback including at least one bit for each of the multiple opportunities for the SPS occasion.
  • Example 8 the method of any of Examples 1-7 further includes receiving scheduling information for a retransmission in DCI indicating a HARQ process for the SPS occasion as an index for the retransmission.
  • Example 9 the method of any of Examples 1-8 further includes performing HARQ combination of the retransmission with an opportunity of the SPS occasion having a highest detection metric.
  • Example 10 the method of any of Examples 1-9 further includes that the DCI scheduling the retransmission further includes a time domain resource allocation for the retransmission, the method further comprising: determining an opportunity of the SPS occasion for HARQ combination with the retransmission based on the time domain resource allocation for the retransmission.
  • Example 11 the method of any of Examples 1-10 further includes transmitting HARQ feedback having a shared bit for the multiple opportunities of the SPS occasion.
  • Example 12 the method of any of Examples 1-11 further includes entering a sleep state between successfully receiving the downlink transmission in an opportunity of the SPS occasion and transmitting HARQ feedback or following transmitting the HARQ feedback.
  • Example 13 the method of any of Examples 1-12 further includes receiving scheduling for individual PUCCH resources for each of the multiple opportunities of the SPS occasion.
  • Example 14 the method of any of Examples 1-13 further includes that the individual PUCCH resources are limited to use for positive acknowledgments.
  • Example 15 the method of any of Examples 1-14 further includes transmitting an ACK in an individual PUCCH resource, if the downlink transmission is successfully received; and refraining from sending feedback if the downlink transmission is not successfully received in any of the multiple opportunities of the SPS occasion.
  • Example 16 the method of any of Examples 1-15 further includes that the individual PUCCH resources are limited to positive ACKs for an opportunity of the SPS occasion; and transmitting a NACK multiplexed with a PUSCH and corresponding to the opportunity of the SPS occasion.
  • Example 17 the method of any of Examples 1-16 further includes that the SPS occasion comprises s opportunities, s being an integer number, the method further comprising: receiving scheduling for s-1 individual PUCCH resources for individual opportunities of the SPS occasion, wherein the individual PUCCH resources are limited to use for positive acknowledgments; and receiving scheduling for a last PUCCH resource following the SPS occasion for an ACK or a NACK.
  • Example 18 the method of any of Examples 1-17 further includes that the last PUCCH resource comprises a different time, a different frequency, or a different format than the individual PUCCH resources.
  • Example 19 the method of any of Examples 1-18 further includes transmitting a single ACK to the base station in an individual PUCCH resource or the last PUCCH resource if the downlink transmission is successfully received; and transmitting the NACK to the base station in the last PUCCH resource is the downlink transmission is not successfully received.
  • Example 20 the method of any of Examples 1-19 further includes transmitting the ACK to the base station in an individual PUCCH resource and the last PUCCH resource if the downlink transmission is successfully received; and transmitting the NACK in the last PUCCH resource if the downlink transmission is not successfully received in the SPS occasion.
  • Example 21 the method of any of Examples 1-20 further includes receiving scheduling for individual PUCCH resources that are limited to ACKs for each of the multiple opportunities of the SPS occasion and for an additional PUCCH resource following a last opportunity of the SPS occasion for an ACK or a NACK.
  • Example 22 the method of any of Examples 1-21 further includes transmitting the ACK to the base station in an individual PUCCH resource and the additional PUCCH resource if the downlink transmission is successfully received; and transmitting the NACK in the additional PUCCH resource if the downlink transmission is not successfully received in the SPS occasion.
  • Example 23 is a device including one or more processors and one or more memories in electronic communication with the one or more processors storing instructions executable by the one or more processors to cause the device to implement a method as in any of Examples 1-22.
  • Example 24 is a system or apparatus including means for implementing a method or realizing an apparatus as in any of Examples 1-22.
  • Example 25 is a non-transitory computer readable medium storing instructions executable by one or more processors to cause the one or more processors to implement a method as in any of Examples 1-22.
  • Example 26 is a method of wireless communication at a base station, comprising: configuring a UE for a plurality of SPS occasions, each SPS occasion including multiple opportunities for downlink transmission by the base station; and transmitting a packet to the UE in an opportunity of an SPS occasion based on an arrival time of the packet.
  • Example 27 the method of Example 26 further includes that the plurality of SPS occasions are for a single SPS configuration.
  • Example 28 the method of Example 26 or Example 27 further includes that the multiple opportunities of the SPS occasion are associated with a same HARQ process.
  • Example 29 the method of any of Examples 26-28 further includes that the base station transmits the packet to the UE in a single opportunity from the multiple opportunities of the SPS occasion.
  • Example 30 the method of any of Examples 26-29 further includes that each of the multiple opportunities corresponds to a slot starting from an offset for the SPS occasion.
  • Example 31 the method of any of Examples 26-30 further includes that each of the multiple opportunities for the SPS occasion map to a single PUCCH resource for feedback.
  • Example 32 the method of any of Examples 26-31 further includes receiving HARQ feedback having at least one bit for each of the multiple opportunities for the SPS occasion.
  • Example 33 the method of any of Examples 26-32 further includes scheduling a retransmission in DCI indicating a HARQ process for the SPS occasion as an index for the retransmission.
  • Example 34 the method of any of Examples 26-33 further includes that the DCI scheduling the retransmission further includes a time domain resource allocation for the retransmission that indicates the opportunity of the SPS occasion for the UE to use for a HARQ combination with the retransmission.
  • Example 35 the method of any of Examples 26-34 further includes receiving HARQ feedback having a shared bit for the multiple opportunities of the SPS occasion.
  • Example 36 the method of any of Examples 26-35 further includes scheduling individual PUCCH resources for each of the multiple opportunities of the SPS occasion.
  • Example 37 the method of any of Examples 26-36 further includes that the individual PUCCH resources are limited to use for positive acknowledgments.
  • Example 38 the method of any of Examples 26-37 further includes receiving an ACK in an individual PUCCH resource, if the downlink transmission is successfully received; and scheduling a retransmission of the packet if a positive acknowledgment is not received in any of the individual PUCCH resources.
  • Example 39 the method of any of Examples 26-38 further includes that the SPS occasion comprises s opportunities, s being an integer number, the method further comprising: scheduling s-1 individual PUCCH resources for individual opportunities of the SPS occasion, wherein the individual PUCCH resources are limited to use for positive acknowledgments; and scheduling a last PUCCH resource following the SPS occasion for an ACK or a NACK
  • Example 40 is a device including one or more processors and one or more memories in electronic communication with the one or more processors storing instructions executable by the one or more processors to cause the device to implement a method as in any of Examples 26-39.
  • Example 41 is a system or apparatus including means for implementing a method or realizing an apparatus as in any of Examples 26-39.
  • Example 42 is a non-transitory computer readable medium storing instructions executable by one or more processors to cause the one or more processors to implement a method as in any of Examples 26-39.
  • 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)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé, un support lisible par ordinateur et un appareil destinés à une communication sans fil au niveau d'un équipement utilisateur (UE). L'UE reçoit une configuration pour une pluralité d'occasions de planification semi-persistante (SPS), chaque SPS comprenant de multiples opportunités pour une transmission en liaison descendante par une station de base. L'UE surveille la transmission de liaison descendante pendant une ou plusieurs opportunités d'une occasion SPS. La station de base transmet un paquet à l'UE dans une opportunité d'une occasion SPS d'après une heure d'arrivée du paquet.
PCT/CN2020/088538 2020-05-01 2020-05-01 Opportunités de planification semi-persistante pour trafic périodique instable WO2021217678A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
PCT/CN2020/088538 WO2021217678A1 (fr) 2020-05-01 2020-05-01 Opportunités de planification semi-persistante pour trafic périodique instable
US17/904,784 US20220416955A1 (en) 2020-05-01 2021-04-30 Semi-persistent scheduling opportunities for jittered periodic traffic
EP21797402.1A EP4144165A1 (fr) 2020-05-01 2021-04-30 Opportunités de planification semi-persistante pour trafic périodique instable
PCT/CN2021/091455 WO2021219129A1 (fr) 2020-05-01 2021-04-30 Opportunités de planification semi-persistante pour trafic périodique instable
CN202180030536.6A CN115443722A (zh) 2020-05-01 2021-04-30 用于抖动周期性业务的半持久调度机会

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/088538 WO2021217678A1 (fr) 2020-05-01 2020-05-01 Opportunités de planification semi-persistante pour trafic périodique instable

Publications (1)

Publication Number Publication Date
WO2021217678A1 true WO2021217678A1 (fr) 2021-11-04

Family

ID=78373275

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/088538 WO2021217678A1 (fr) 2020-05-01 2020-05-01 Opportunités de planification semi-persistante pour trafic périodique instable

Country Status (1)

Country Link
WO (1) WO2021217678A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109565676A (zh) * 2017-05-05 2019-04-02 瑞典爱立信有限公司 用于配置半持久调度的方法和设备
US20190191416A1 (en) * 2016-08-25 2019-06-20 Zte Corporation Method for receiving information, base station, and terminal
WO2019193700A1 (fr) * 2018-04-04 2019-10-10 株式会社Ｎｔｔドコモ Terminal utilisateur et station de base sans fil

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190191416A1 (en) * 2016-08-25 2019-06-20 Zte Corporation Method for receiving information, base station, and terminal
CN109565676A (zh) * 2017-05-05 2019-04-02 瑞典爱立信有限公司 用于配置半持久调度的方法和设备
WO2019193700A1 (fr) * 2018-04-04 2019-10-10 株式会社Ｎｔｔドコモ Terminal utilisateur et station de base sans fil

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "On configuration aspects for multiple SPS and CG.", 3GPP DRAFT; R2-1906838 ON CONFIGURATION ASPECTS FOR MULTIPLE SPS AND CG, vol. RAN WG2, 2 May 2019 (2019-05-02), Reno, US, pages 1 - 4, XP051711137 *
OPPO: "Remaining issues on NR-U configured grant", 3GPP DRAFT; R2-1914403, vol. RAN WG2, 8 November 2019 (2019-11-08), Reno, USA, pages 1 - 7, XP051816486 *

Similar Documents

Publication Publication Date Title
US11464001B2 (en) Joint activation of multiple semi-persistent scheduling configurations in a single message
EP3857755B1 (fr) Terminaison précoce d'un pusch avec une nouvelle autorisation de liaison montante
US11172503B2 (en) SPS for signaling with non-integer periodicities
US11576228B2 (en) Uplink preemption indication on multiplexed uplink channels
US11044589B2 (en) V2X network based relaying
US11171765B2 (en) System and method for indicating preemption of transmissions
WO2021142760A1 (fr) Élément unique de dci mettant à jour des paramètres de commande pour de multiples porteuses composantes
US20220095324A1 (en) Transmission time implicitly triggering uci multiplexing on pusch with different priorities
WO2020205130A1 (fr) Procédés et appareil de rapport d'informations de nouveau faisceau
US11678223B2 (en) Transmission power control command accumulation for NR-dual connectivity
US20210105100A1 (en) Prioritization between a scheduling request and harq feedback
US20230269719A1 (en) Techniques to facilitate ue indication of sps pucch harq feedback location
WO2021217678A1 (fr) Opportunités de planification semi-persistante pour trafic périodique instable
US11805548B2 (en) Supporting UL LBT status report in NR-U
US20230045191A1 (en) Semi-persistent scheduling physical uplink control channel (pucch) hybrid automatic repeat request deferral for pucch groups
US20230145848A1 (en) Ue requested smtc window configuration adaptation
US20240154730A1 (en) Sps pucch harq ack/nack configuration
US20220232427A1 (en) Collision indicators for sci forwarding information and sci forwarding triggering
US20230337024A1 (en) Wake-up signal based semi-persistent scheduling configuration for extended reality traffic
US20230261791A1 (en) Delayed semi-persistent scheduling harq-ack with physical uplink channel repetition
US20230135803A1 (en) Management of uplink signal transmission repetitions in a user equipment (ue) configured with one or more portions of a frequency band
US20230269803A1 (en) Techniques to facilitate prioritizing packet data convergence protocol (pdcp) protocol data units in dual connectivity
US20230327821A1 (en) Harmonization of multiple configured grant uplink with or without retransmission timer
US20240073889A1 (en) Extending uplink communications by user equipment cooperation
US20230269720A1 (en) Soft a/n report triggering for sps pdsch

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: 20934059

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: 20934059

Country of ref document: EP

Kind code of ref document: A1