SPS reactivation DCI

Abstract

Methods, computer program products, and apparatuses for SPS reactivation are provided. An example method at a UE includes receiving, from a base station, a first semi-persistent scheduling (SPS) reactivation downlink control information (DCI). The example method further includes receiving, from the base station, a second SPS reactivation DCI. The example method further includes transmitting, to the base station, hybrid automatic repeat request (HARQ) feedback indicating detection of the received first SPS reactivation DCI and the received second SPS reactivation DCI, respectively.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims the benefit of and priority to Greek Patent Application S / N. 20200100465, filed August 7, 2020, entitled “SPS REACTIVATION DCI,” and Greek Patent Application S / N. 20200100466, filed August 7, 2020, entitled “UPLINK CHANNEL RECONFIGURATION FOR SEMI-PERSISTENT SCHEDULING,” and each of which is expressly incorporated herein by reference in its entirety. BACKGROUND TECHNICAL FIELD

[0004] The present disclosure relates generally to communication systems, and more specifically to wireless communication systems with semi-persistent scheduling (SPS).

[0005] INTRODUCTION

[0006] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems can 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.

[0007] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is a continuing

[0008] SUMMARY

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

[0010] Methods, computer program products, and apparatuses for SPS reactivation are provided. In one aspect of the disclosure, a method, computer-readable medium, and apparatus for wireless communication at a user equipment (UE) are provided. The UE receives, from a base station, a first semi-persistent scheduling (SPS) reactivation downlink control information (DCI). The UE further receives, from the base station, a second SPS reactivation DCI. The UE transmits, to the base station, hybrid automatic repeat request (HARQ) feedback indicating detection of the received first SPS reactivation DCI and the received second SPS reactivation DCI, respectively.

[0011] In another aspect of the disclosure, a method, computer-readable medium, and apparatus for wireless communication at a base station are provided. The base station transmits, to a UE, a first SPS reactivation DCI. The base station further transmits, to the UE, a second SPS reactivation DCI. The base station receives, from the UE, HARQ feedback indicating detection of the received first SPS reactivation DCI and the received second SPS reactivation DCI, respectively.

[0012] SPS scheduling is a valuable tool for optimizing network usage, especially for systems that rely on periodic data transmissions, such as in internet voice calls, or in industrial IOT, for example, where sensors and robots exchange periodic data to provide status updates of instructions or rules in an automated factory environment.

[0013] When an SPS event is initiated, the network can use the RRC connection with the UE to establish channel configurations and allocate resources. In conventional SPS implementations, the network has the potential to change the resources allocated to a channel used for downlink data flow using downlink control information (DCI) in the context of SPS activation / re-activation. Such changes can be performed as a result of increased interference on the existing downlink channel, or for scheduling or other reasons.

[0014] However, current wireless systems do not provide a mechanism for dynamically updating physical uplink control channel configuration for any duration other than the single SPS period in which the SPS reactivation signal from the base station is sent. As such, when noise or inter-cell interference phenomena become more prevalent on the uplink, the network can incur high latency and overhead for various reasons, including failed acknowledgements, unnecessary retransmissions, and in more severe cases, potentially significant data loss.

[0015] Accordingly, in an aspect of the disclosure, a method, an apparatus, and a computer readable medium are provided. A method includes a method of a UE. The UE receives a physical uplink control channel (PUCCH) configuration from a base station during a semi-persistent scheduling (SPS) reactivation period. The PUCCH configuration remains valid for all subsequent SPS periods unless conditioned by data accompanying the PUCCH configuration or later changed. The UE further transmits a response to a data message from the base station using the configured PUCCH for each of the subsequent SPS periods.

[0016] The method further includes a method of a base station. The base station identifies a configuration for a physical uplink control channel (PUCCH) during a semi-persistent scheduling (SPS) reactivation period, the configuration being valid for all subsequent SPS periods unless the configuration includes a condition or the configuration is later changed. The base station transmits the PUCCH configuration to the UE on a downlink control channel (PDCCH) during the SPS reactivation period.

[0017] The apparatus includes a UE. The UE includes at least one processor and a memory coupled to the at least one processor. The memory stores code executable by the at least one processor to cause the UE to receive a physical uplink control channel (PUCCH) configuration from a base station during a semi-persistent scheduling (SPS) reactivation period, the PUCCH configuration remaining valid for all subsequent SPS periods unless conditioned by data accompanying the PUCCH configuration or later changed, and transmit a response to a data message from the base station using the configured PUCCH for each of the subsequent SPS periods.

[0018] The apparatus includes another aspect of a UE. The UE includes means for receiving a physical uplink control channel (PUCCH) configuration from a base station during a semi-persistent scheduling (SPS) reactivation period, the PUCCH configuration remaining valid for all subsequent SPS periods unless conditioned by data accompanying the PUCCH configuration or later changed. The UE further includes means for transmitting a response to a data message from the base station using the configured PUCCH for each of the subsequent SPS periods.

[0019] The apparatus further includes a base station. The base station includes at least one processor and a memory coupled to the at least one processor. The memory stores code executable by the at least one processor to cause the base station to identify, during a semi-persistent scheduling (SPS) reactivation period, a configuration for a physical uplink control channel (PUCCH) that is valid for all successive SPS periods unless the configuration includes a condition or the configuration is later changed, and transmit the PUCCH configuration to the UE on a downlink control channel (PDCCH) during the SPS reactivation period.

[0020] The computer-readable medium includes code that, when executed by at least one processor of a UE, causes the at least one processor to receive, from a base station during a semi-persistent scheduling (SPS) reactivation period, a physical uplink control channel (PUCCH) configuration that remains valid for all successive SPS periods unless a condition is set by data accompanying the PUCCH configuration or is later changed. The code causes the at least one processor to transmit, for each of the successive SPS periods, a response to a data message from the base station using the configured PUCCH.

[0021] The computer-readable medium further includes code that, when executed by at least one processor of a base station, causes the at least one processor to identify, during a semi-persistent scheduling (SPS) reactivation period, a configuration for a physical uplink control channel (PUCCH) that is valid for all successive SPS periods unless the configuration includes a condition or the configuration is later changed. The code further causes the at least one processor to transmit the PUCCH configuration to the UE on a downlink control channel (PDCCH) during the SPS reactivation period.

[0022] To the accomplishment of the foregoing and related aspects, this one or more aspects include the features recited in the following claims, the following description and the annexed drawings. The following description and drawings merely exemplify the various aspects. It is understood that numerous specific details can be set forth in this description and that these specific details can be implemented in a variety of systems. As such, various aspects can be implemented in a manner depending on particular needs with or without these specific details. In other instances, well known methods have not been described in detail in order to avoid unnecessarily obscuring the present description. BRIEF DESCRIPTION OF DRAWINGS

[0024] Figure 1 is a diagram illustrating an example of a wireless communications system and an access network.

[0025] Figure 2A is a diagram illustrating an example of a first frame in accordance with aspects of the present disclosure. is a diagram illustrating an example of a first frame in accordance with aspects of the present disclosure.

[0026] Figure 2B This is a diagram illustrating an example of a DL channel within a subframe according to various aspects of this disclosure.

[0027] Figure 2C This is an example illustration of the second frame explaining various aspects of this disclosure.

[0028] Figure 2D This is a diagram illustrating an example of a UL channel within a subframe according to various aspects of this disclosure.

[0029] Figure 3 This is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

[0030] Figure 4 The example communication between the base station and the UE is explained.

[0031] Figure 5 An example communication between the base station and the UE was explained.

[0032] Figure 6 The example communication between the base station and the UE is explained.

[0033] Figure 7 The example communication between the base station and the UE is explained.

[0034] Figure 8 The example communication between the base station and the UE is explained.

[0035] Figure 9 This is a timing diagram of an example SPS reactivation between the base station and the UE.

[0036] Figure 10 This is a timing diagram of an example SPS reactivation between the base station and the UE.

[0037] Figure 11 It is a time series diagram of continuous SPS periods.

[0038] Figure 12 This is a flowchart of a method for wireless communication at the UE.

[0039] Figure 13 This is a flowchart of a method for conducting wireless communication at a base station.

[0040] Figure 14 This is a flowchart of a method for wireless communication at the UE.

[0041] Figure 15 This is a flowchart of a method for conducting wireless communication at a base station.

[0042] Figure 16 This is a flowchart of a method for wireless communication at the UE.

[0043] Figure 17 is a flowchart of a method of wireless communication at a base station.

[0044] Figure 18 is a flowchart of a method of wireless communication at a UE.

[0045] Figure 19 is a flowchart of a method of wireless communication at a base station.

[0046] Figure 20 is an example hardware implementation for an UE apparatus to perform various functions described herein.

[0047] Figure 21 is an example hardware implementation for a base station apparatus to perform various functions described herein.

[0048] DETAILED DESCRIPTION

[0049] The detailed description set forth below, in connection with the appended drawings and embodiments described herinin, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without

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

[0051] By way of example, an element, or any portion of an element, or any combination of elements can be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system can 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.

[0052] Accordingly, in one or more example embodiments, the functions described can be implemented in hardware, software, or any combination thereof. If implemented in software, the functions can 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 can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0053] While aspects are described in the context of some examples, those skilled in the art will appreciate that those examples are illustrative and that the aspects described herein can be carried out in a number of different arrangements and scenarios. The inventive embodiments described herein can be implemented in any of a variety of different platforms, devices, systems, shapes, sizes, and packaging arrangements. For example, the implementations and / or uses can occur via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Some examples can or can not be exclusively intended for, or appropriate to, a particular use or application, but the described innovations can find applicability across a broad array of uses and implementations. The implementations can range from chip-level or module-component implementations to non-module, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical environments, devices incorporating the described aspects and features can also include additional components and features that can be relevant to the implementation and practice of the claimed and described aspects. For example, transmission and reception of wireless signals necessarily includes a number of components (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors(s), interleavers, adders / summers, etc.) for analog and digital purposes. The innovations described herein are intended to be workable in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitutions.

[0054] Timing Figure 1 The drawings are not to scale and timing pulses are generally shown in an exaggerated, simplified manner to avoid obscuring the concepts underlying the present disclosure.

[0055] Figure 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system (also referred to as a wireless wide area network (WWAN)) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and a 5G Core (5GC) network 190. The base stations 102 can include macro cells (high power cellular base stations) and / or small cells (low power cellular base stations). The macro cells can include base stations. The small cells can include femtocells, picocells, and microcells.

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

[0057] The base stations 102 can wirelessly communicate with the UEs 104. Each of the base stations 102 can provide communication coverage for a respective geographic coverage area 110. There can be overlapping geographic coverage areas 110. For example, a small cell 102' can have a coverage area 110' that overlaps with one or more macrocells 102. A network that includes both small cell and macrocells can be known as a heterogeneous network. A heterogeneous network can also include Home Evolved Node Bs (eNBs) (HeNBs), which can provide service to a restricted group known as a closed subscriber group (CSG). The communication links 120 between the base stations 102 and the UEs 104 can 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 can use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. These communication links can be through one or more carriers, where a carrier can be a set of

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

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

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

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

[0062] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands in these mid-band frequencies as frequency range designation FR3 (7. 125 GHz - 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, and as such can effectively extend the features of FR1 and / or FR2 into the mid-band frequencies. Additionally, higher operating bands are currently being explored to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher operating bands falls within the EHF band of wavelengths.

[0063] With the above considerations in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, if used herein, can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, can broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or can be within the EHF frequency band.

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

[0065] The base station 180 can transmit a beamformed signal to the UE 104 in one or more transmit directions 182'. The UE 104 can receive the beamformed signal from the base station 180 in one or more receive directions 182". The UE 104 can also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 can receive the beamformed signal from the UE 104 in one or more receive directions. The base station 180 / UE 104 can 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 of the base station 180 can or can not be the same. The transmit and receive directions of the UE 104 can or can not be the same.

[0066] The EPC 160 can include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 can be in communication with a home subscriber server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation as well as other functions. The PDN gateway 172 and the BM-SC 170 are connected to the IP services 176. The IP services 176 can include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 can provide functions for MBMS user service provisioning and

[0067] The core network 190 can include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 can be in communication with a unified data management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred

[0068] A base station can include and / or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a Transmit Receive Point (TRP), or some other suitable terminology. A 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 functional device. Some of the UEs 104 can be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicle, heart monitor, etc.). The UE 104 can 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 communication 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. In some scenarios, the term UE can also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices can collectively or individually access a network and / or individual networks.

[0069] Referring again to Figure 1 In certain aspects, the base station 102 / 180 includes an SPS reactivation DCI component 198 configured to transmit first and second SPS reactivation DCIs and receive, from the UE 104, HARQ feedback indicating detection of the received first SPS reactivation DCI and the received second SPS reactivation DCI, respectively. In certain aspects, the UE 104 includes a HARQ component 199 configured to receive first and second SPS reactivation DCIs and transmit HARQ feedback indicating detection of the received first SPS reactivation DCI and the received second SPS reactivation DCI, respectively.

[0070] Although the following description can focus on 5G NR, the concepts described herein can be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0071] Figure 2A FIG. 200 is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. Figure 2BFigure 230 is an example illustrating the DL channel within a 5G NR subframe. Figure 2C This is a diagram 250 illustrating an example of the second subframe within the 5G NR frame structure. Figure 2D Figure 280 illustrates an example of the UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD), where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL; or it can be Time Division Duplex (TDD), where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL. Figure 2A , 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL) and subframe 3 is configured with slot format 1 (both UL), where D is DL, U is UL, and F is provided for flexible use between DL and UL. Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured to have a slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to 5G NR frame structures for TDD.

[0072] Figures 2A-2D The frame structure has been explained, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include mini-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal CP or extended CP. For normal CP, each time slot may include 14 symbols, while for extended CP, each time slot may include 12 symbols. Symbols on the DL can be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter design. The parameter design defines the subcarrier spacing (SCS) and, in effect, the symbol length / duration, which is equal to 1 / SCS.

[0073]

[0074] For normal CP (14 symbols / slot), different numerologies μ0to 4allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, numerology 2allows 4 slots per subframe. Accordingly, for normal CP and numerology μ, there are 14 symbols / slot and 2 μ slots / subframe. Subcarrier spacing can equal 2 μ * 15 kHz, where μ is numerology 0 to 4. As such, numerology μ = 0 has a subcarrier spacing of 15 kHz, while numerology μ = 4 has a subcarrier spacing of 240 kHz. Symbol length / duration is inversely related to subcarrier spacing. Figures 2A to 2D An example is provided of normal CP with 14 symbols per slot and numerology μ = 2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μβ. Within a frame set, there can be one or more different bandwidth parts (BWPs) that are frequency division multiplexed (see Figure 2B ). Each BWP can have a particular numerology and CP (normal or extended).

[0075] A resource grid can be used to represent the frame structure. Each time slot includes resource blocks (RBs) (also referred to as physical RBs (PRBs)) that extend for the full duration, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

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

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

[0079] Figure 2DExamples of various UL channels within a subframe of a TTI are shown. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data, and can additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0080] Figure 3 is a block diagram of the components of base station 310 and UE 350, which are in communication over access network 320. In the DL, IP packets from the core network 160 can be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter radio access technology (RAT) mobility, and measurement configuration and reporting of UE measurements; 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 detection through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0081] 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, can include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 can be used to determine the coding and modulation schemes, as well as for spatial processing. The channel estimate can be derived from a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can modulate a respective spatial stream onto a radio frequency (RF) carrier

[0082] At the UE 350, 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 can 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 can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions can 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.

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

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

[0085] Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 can 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 can be provided to different antenna 352 via separate transmitters 354TX. Each transmitter 354TX can modulate an RF carrier with a respective spatial stream for transmission.

[0086] 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.

[0087] The controller / processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 can be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 350. IP packets from the controller / processor 375 can 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.

[0088] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 can be configured to perform aspects in connection with 198. Figure 1

[0089] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 can be configured to perform aspects in connection with 198. Figure 1

[0090] In a wireless communication system, a base station can schedule a UE using semi-persistent scheduling. For example, the base station can use SPS to schedule periodic resources for PDSCH transmissions from the base station to the UE. In some examples, SPS reactivation can be used to adjust one or more parameters of previously SPS resources or configurations. SPS reactivation can be useful for applications such as ultra-reliable low-latency (URLLC) applications, among other applications.

[0091] As Figure 4 ​​As illustrated in Example Communication 400, Base Station 402 can communicate with UE 404 by transmitting PDSCH using one or more SPS resources. The UE provides HARQ feedback (e.g., ACK / NACK) for each periodic resource to notify the base station whether the UE received PDSCH during that periodic resource. Base Station 402 may initiate SPS reactivation for various reasons. For example, due to interference, changes in channel conditions, etc., the base station may be unable to successfully transmit data in the PDSCH within the defined number of symbols. SPS reactivation can facilitate beam changes to improve communication performance between Base Station 402 and UE 404. Base Station 402 may transmit an SPS reactivation DCI 406 to UE 404, for example, indicating a new beam for SPS transmission to the UE. Base Station 402 may also transmit an SPS transmission 408 associated with the new beam to UE 404. UE 404 may transmit an acknowledgment 410 in response to receiving SPS transmission 408. However, in some wireless communication systems, because UE 404 can transmit an ACK 410 in response to receiving an SPS transmission 408 regardless of whether SPS reactivation DCI 406 has been received, base station 402 will not have information about whether SPS reactivation DCI 406 has been received. Additionally, due to PDCCH errors or SPS PDSCH errors with new SPSPDSCH configurations, UE 404 may transmit a non-acknowledgment or negative ACK to base station 402, further introducing ambiguity to base station 402's information. Figure 4 In the example described, the reactivation of SPS DCI for PDSCH does not modify the PUCCH parameters.

[0092] Similar to communication 400, such as Figure 5 As illustrated in example communication 500 between base station 402 and UE 504, base station 402 can transmit SPS reactivation DCI 506 and SPS transmission 508 to UE 504. Figure 5In the illustrated example, reactivating the SPS DCI can modify PUCCH parameters (such as the PUCCH Resource Indicator (PRI)). This joint DL SPS PDSCH and UL PUCCH configuration modification can indicate a DL beam change and an equivalent UL beam change. UE 504 can transmit ACK 510 in response to receiving SPS transmission 408. Because UE 504 can transmit ACK 510 in response to receiving SPS transmission 508, and the reactivation of the SPS DCI for PDSCH does indeed modify PUCCH parameters (such as PRI), the transmission of ACK 510 is associated with either the newly received PUCCH parameters or the previous PUCCH parameters. As a result, base station 502 can know whether UE 504 has received the reactivation of the SPS DCI.

[0093] like Figure 6 As illustrated in Example Communication 600, in some wireless communication systems (such as IIoT or URLLC environments), multiple SPSs can be configured or scheduled for the UE (e.g., as illustrated at 606). Figure 6 The explanations cover SPS 1 and SPS2. Figure 6 It also explains how the base station sends an SPS reactivation for an SPS, for example, the first reactivation DCI transmitted for SPS 2. Figure 6 The text also explains that the base station sends a first SPS reactivation DCI associated only with SPS 2 and a second SPS reactivation DCI 608 associated with both SPS 1 and SPS 2. Even though SPS reactivation DCIs 606 and 608 modify the PUCCH parameters, because UE 604 can transmit ACK 610 based on the modified PUCCH parameters upon receiving either the first SPS reactivation DCI 606 or the second SPS reactivation DCI 608, the base station 602 may not know whether UE 604 has successfully received either or both of the first and second SPS reactivation DCIs 606 and 608, leading to ambiguity.

[0094] To resolve this ambiguity, such as Figure 7 As illustrated in example communication 700, a HARQ mechanism is provided for SPS reactivation DCI. UE 704 is configured to provide HARQ feedback 710, wherein it indicates to base station 702 the detection of the first reactivation SPS DCI 706 and the second reactivation SPS DCI 708, respectively. As a result, base station 702 will have information about whether the first reactivation SPS DCI 706 or the second reactivation SPS DCI 708 was successfully transmitted.

[0095] Table 1 illustrates example HARQ feedback for SPS PDSCH for SPS 1 and SPS 2. Table 2 illustrates example HARQ feedback for SPS PDSCH for SPS 1 and SPS 2 that also includes individual HARQ feedback indicating whether the UE received an activation DCI for SPS 1 and whether the UE received an activation DCI for SPS 2.

[0096] Table 1

[0097]

[0098] Table 2

[0099]

[0100]

[0101] In the example for Table 2, at each SPS occasion, the UE will send feedback that provides an ACK / NACK for each PDSCH that is configured for the corresponding SPS, as well as an ACK / NACK feedback about whether an activation / reactivation DCI for that corresponding SPS configuration was received.

[0102] In some aspects, the SPS associated with the first reactivation SPS DCI 706 or the second reactivation SPS DCI 708 can be associated with a single carrier. In some aspects, the SPS associated with the first reactivation SPS DCI 706 or the second reactivation SPS DCI 708 can be a SPS in an IIoT environment. In some aspects, the SPS associated with the first reactivation SPS DCI 706 or the second reactivation SPS DCI 708 can have a period of 2 milliseconds (ms) and a packet size of 40 bytes. A minimum UE processing time (N1) time N1 can be a time of 20 symbols. In some aspects, the HARQ feedback 710 can include two indications (e.g., represented by two bits), each for one of the first reactivation SPS DCI 706 and the second reactivation SPS DCI 708. In some aspects, the HARQ feedback 710 can further include an additional indication that indicates reception of SPS 1 and SPS 2 associated with the first reactivation SPS DCI 706 and the second reactivation SPS DCI 708, respectively. In some aspects, the base station can provide a SPS release and subsequently provide a SPS activation in order to indicate a SPS reconfiguration. The release and activation signaling can increase overhead and increase latency of communications between the base station and the UE. If the UE misses the SPS PDSCH release, additional latency can be caused because the UE can rely on both the release and the activation to apply the new configuration.

[0103] In some aspects, a downlink assignment index (DAI) for one or more SPS physical data shared channels (PDSCHs) is also used for the first SPS reactivation DCI 706 and the second SPS reactivation DCI 708. The DAI can be included in the first SPS reactivation DCI or the second SPS reactivation DCI. The DAI can include two bits for PDCCHs associated with SPS. In some aspects, the DAI can be of format DAI: (3, 4), where the former is a counter DAI and the latter is a total DAI, as illustrated in 800 of Figure 8 In some aspects, if more than one serving cell is configured in the DL and a higher layer parameter network function instance (e.g., which can be referred to as (NFI)-TotalDAI-Included) is enabled, the DAI can include 8 bits. The four most significant bits (MSBs) can be a counter DAI and a total DAI for a group of scheduled PDSCHs. The two middle bits can be a total DAI for a group of non-scheduled PDSCHs. The two least significant bits (LSBs) can be for PDCCHs associated with the group of non-scheduled PDSCHs.

[0104] SPS can be configured to optimize the use of radio resources by minimizing the overhead for applications involving periodic communication, including relatively short bursts of periodic data. Among other applications, SPS can be used for VoIP, where voice data can be exchanged periodically over a period of time. SPS can also be used for managing industrial IoT traffic, where periodic transmission of control signals or data bursts can be commonly scheduled by sensors, robots, controllers, and other advanced network mechanisms to be used in more complex factories where network automation is common. SPS can be advantageous for periodic signaling of these types of devices to ensure that network latency is minimized for such applications that generally use persistent allocations of periodic data.

[0105] SPS can be established initially and periodically at layer 3 using RRC commands. These RRC sessions can be enabled to initialize SPS commands, which in turn can allocate network resources to be used during subsequent SPS periods. In addition to the occurrence of RRC commands, a base station can use SPS activation and / or reactivation procedures at layer 1, for example, to allow the base station to control and allocate certain specific resources in a much faster manner (e.g., in real-time or near real-time) than when dedicated RRC signaling is used for this purpose.

[0106] In some wireless communication systems, a network can be enabled to perform SPS activation and reactivation events in which DCI can be provided to a UE during an SPS period to change the configuration of a downlink data channel (e.g., PDSCH) in the presence of downlink interference. An SPS reactivation cycle can allow a base station to transmit DCI for reconfiguring a subsequent PDSCH (e.g., using a different set of PRBs, or changing a receive beam or modulation and coding scheme) so that the UE will be notified from the DCI to monitor for data from the newly configured PDSCH. During successive SPS periods, including the initial SPS reactivation period, the newly configured PDSCH can be maintained on the downlink until changed by another SPS reactivation period or by a subsequent RRC SPS session. Similarly, during SPS activation / reactivation, a base station can transmit an indication to a UE on a PDCCH that the base station has changed the configuration of a PUCCH channel used by the UE to transmit responses, such as acknowledgements (ACKs) and negative acknowledgements (NACKs).

[0107] Under such mechanisms, the new PUCCH resource allocation sent by the base station on the PDCCH can not apply to subsequent SPS periods. As a result, in subsequent SPS periods, after the PUCCH is changed during the SPS activation cycle, the UE can fall back to its default PUCCH configuration and can continue to transmit information on the uplink that is experiencing interference. Under such mechanisms, RRC (Layer 3) configuration can provide SPS configuration information for both downlink PDSCH and uplink PUCCH. However, at Layer 1, such as shown in Figure 9 Figure 9 Under such mechanisms, the new PUCCH resource allocation sent by the base station on the PDCCH can not apply to subsequent SPS periods. As a result, in subsequent SPS periods, after the PUCCH is changed during the SPS activation cycle, the UE can fall back to its default PUCCH configuration and can continue to transmit information on the uplink that is experiencing interference. Under such mechanisms, RRC (Layer 3) configuration can provide SPS configuration information for both downlink PDSCH and uplink PUCCH. However, at Layer 1, such as shown in Figure 9 More particularly described, these two approaches can significantly increase the latency of the SPS procedure, which can result in unrecoverable data errors and can incur overhead as the base station consumes additional bandwidth on each cycle to reconfigure the PUCCH resource allocation for the UE.

[0108] Figure 9 is a timing diagram 900 of an example SPS reactivation followed by additional SPS periods between a base station and a UE. While a single base station and UE are shown, the concepts described can apply equally to a base station that schedules SPS sessions for multiple different UEs, e.g., using time division multiplexing.

[0109] Reference is now made to Figure 9 Timing diagram 900 shows multiple recurring SPS periods at the base station - a first 1 ms period, followed by a second period 908, a third period 914, and so on. While the values herein are purely for example purposes, the SPS periods in this illustration can have a length of 1 ms or 112 symbols. The ellipses under different transmissions indicate transmit or receive beamforming, although in other configurations spatial division multiplexing can not be used, and instead omnidirectional or other antenna types can be used. The SRS sent by the UE is transmitted using the same beam(s) as used for the uplink transmission of the SPS PUCCH message, and can be transmitted using the same PRB as the PUCCH. The reactivation DCI transmitted in the PDCCH to configure the SPS PDSCH channel can be accompanied by a new PUCCH resource indicator to modify the PUCCH parameters for ACK / NACK only during that period. The previous RRC session can define the current channel configuration previously, so that the PDSCH uses the previously assigned PRBs and other network properties.

[0110] At the start of the SPS 1 ms period, the base station can transmit data 902 on the PDSCH, which corresponds to periodic data sent to the UE consistent with any ongoing activity that requires the SPS session. The UE 924 can respond with an ACK within twenty symbols on the PUCCH default configuration. The UE can also be able to transmit its own uplink data at the scheduled intervals during the SPS session.

[0111] At the end of the initial SPS period, the UE also transmits an SRS 926 using the same beam and configuration as for the PUCCH. The SRS is a UE uplink transmission that includes an uplink pilot signal to enable the base station to perform channel estimation at different frequencies and use the received signal for uplink scheduling. The SRS can be transmitted by the UE at the request of the network. Based on the received signal strength and quality and the difference from what the base station expects to receive based on its own channel condition assessment and previous communications with the UE, the base station can estimate the channel quality. The base station can also configure these channel estimates for the UE to transmit on the uplink. For example, the base station can specify what power the UE can transmit data on a particular channel.

[0112] At the beginning of the second SPS period 908, the base station can transmit a data signal 906 on the PDSCH. The base station can have detected the presence of downlink interference, which in turn can have caused a degradation of the data signal 906 transmitted on the PDSCH. As a result of the downlink interference, the UE can not be able to decode the data packet transmitted at 906 on the PDSCH. The UE can send a NACK 928 back to the base station.

[0113] In anticipation of a response (NACK 928) from the UE by the base station, the base station can further detect uplink interference occurring at the frequency of the PUCCH allocated to the UE, which in turn can cause the base station to fail to receive the NACK. In some aspects, the network's failure to receive a response (NACK or otherwise) to its transmission is interpreted as a NACK. During the period 908, the base station initiates an SPS reactivation DCI transmission 910 at the downlink control channel (PDCCH). Because the last transmission failed, the base station can attempt to adapt the link to enable successful retransmission of the downlink data packet. The network can provide DCI to the UE in the PDCCH portion of the transmission 910 that indicates that the configuration of the subsequent PDSCH (the signal in transmission 910 immediately following the PDCCH transmission) channel can be changed to attempt to correct for the downlink interference. For example, the DCI in the PDCCH signal can indicate to the UE that the base station is using different PRBs for the PDSCH in transmission 910 than were used in the previous transmission at 906 to attempt to avoid the downlink interference.

[0114] Additionally, based on the base station's perception of uplink interference on the currently configured PUCCH, in addition to the DCI specifying different PRBs for the PDSCH, the base station can include in its PDCCH message in transmission 910 a newly configured PUCCH resource (instead of the currently RRC allocated PUCCH resource) that the UE can use to acknowledge that the UE received data on the newly configured PDSCH. The PUCCH resource is limited to the period 908.

[0115] In one example configuration, the UE can successfully receive both the PDCCH transmission 910 and the data transmission on the newly configured PDSCH, and the UE can use the new PUCCH configuration to send an ACK 930. Here, it is assumed that there is no uplink interference due to the UE using the new PUCCH resource.

[0116] Another SRS signal 932 can be transmitted by the UE near the end of the cycle (e.g., period 908). The SRS signal 932 can be used to detect a constant level of uplink interference at the original PUCCH configuration. For example, if the base station does not receive the NACK 928, the base station can know that there is interference.

[0117] The base station can then send data in transmission 912 on the newly configured PDSCH at the start of period 914. During the previous period, it is noted that the base station has changed the PUCCH resource configuration. However, after the initial SPS cycle, the UE returns to using the same default PUCCH configuration from its previous RRC session for sending NACK 928. Because this configuration has been associated with constant interference, the problem with the current SPS specification is apparent.

[0118] As one possible outcome, the base station can conclude that the UE did not receive the data in transmission 910, and the base station can send a retransmission of the same data. This transmission can contribute to system overhead.

[0119] If the SPS transmission is not received, the UE can be using its original RRC configuration for PUCCH to attempt to decode one or both of transmissions 910 and 912 in the corresponding second and third SPS periods 908 and 914. As another possible outcome, if the base station made a relatively small change to the PDSCH configuration during its transmission on the PDCCH (e.g., it did not involve a large frequency shift), the UE can still be able to decode the data received on the PDSCH at 910 or 912. The UE can use the PUCCH of the previous RRC configuration to send ACK 934. While the UE was able to successfully decode the data in this example, ACK 934 can be perceived as an error by the base station. For example, the base station can use the SRS signal to conclude that constant uplink interference near the UE caused the transmission error, even though the data at 912 was properly decoded and sent to upper layers.

[0120] As such, the transmission at 912 can be considered a skippable transmission, as the base station can conclude that ACK 934 was in error. Continuing in SPS period 914, the base station can attempt to remedy the problem by transmitting another SPS reactivation DCI and a new PUCCH resource indicator in message 916, followed by a retransmission of the same data in a PDSCH message. First, if the transmission has already been received and decoded, the retransmission of the same data results in additional overhead. Thus, the combined DCI / PUCCH resource indicator and data in message 916 can be another latency-adding transmission, to the extent that the base station attempts to resend data that has already been received.

[0121] Referring back to message 916, the UE can reconfigure its PUCCH in response to the PUCCH resource indicator in message 916, and can adjust its reception parameters in response to the DCI to receive the data in the PDSCH at the designated frequency in message 916. The UE can properly decode the data using the downlink and uplink resources specified in the PDCCH message and transmit an interference-free ACK 936. The UE can then send another SRS 938.

[0122] This cycle of otherwise skippable signals can continue into another cycle in a similar fashion to the transmission of data in the next SPS cycle on PDSCH 918. Here again, the UE can use the PUCCH resource from the original RRC setup and can transmit an ACK 940 that can again be interpreted as an ACK error. That is, the UE can correctly decode the data at 920 and transmit an ACK at 942, but the ACK can be acknowledged as an error because the base station can use the SRS transmission to determine that the ACK was transmitted using a PUCCH that was subject to significant uplink interference.

[0123] This can again trigger another skippable SPS reactivation (DCI transmission and another uplink allocation) and subsequent data transmission 920, similar to the event at 916. ACK 942 can be transmitted using the new PUCCH configured at the PDCCH SPS reactivation, but the transmission is skippable if the data was decoded earlier. The UE can subsequently transmit another SRS signal 944 that can indicate to the base station whether network conditions are sufficient.

[0124] At 922, after a series of unstable transmissions that can delay SPS data exchange and can result in data loss, an SPS reconfiguration is initiated at the RRC level. The RRC reconfiguration period can reconfigure the channel according to conditions, at the cost of further increasing latency by approximately 3-4 milliseconds.

[0125] Figure 9 One configuration is demonstrated in which constant uplink interference requires the base station to issue multiple reactivations so that the UE can transmit uplink acknowledgements without interference using an updated PUCCH configuration. The base station can not be able to dynamically change the uplink allocation on a more regular basis despite the constant interference at the UE’s originally allocated uplink configuration, or it can avoid the overhead incurred. Constant uplink interference detected by the base station using SRS signals (and other signals) can cause inefficiencies in the system in Figure 9 The UE can subsequently return to its original noisy PUCCH conditions after the end of each SPS reactivation cycle. This pattern can result in a waste of resources on the downlink due to received NACKs or ACKs that are falsely believed to be in error based on SRS feedback, both of which result in multiple retransmissions and SPS reactivation cycles.

[0126] Some aspects presented herein improve the efficiency of a wireless communication system by increasing the dynamic uplink resource capabilities for a UE. In some cases, a data field including a list of SPS PUCCH resources (e.g., which can be referred to as “SPS-PUCCH-AN-List”) can be transmitted as data to a UE during a downlink to provide multiple PUCCH configurations for the UE to use during an SPS session. Alternatively, a PUCCH access network message (e.g., which can be referred to as an “n1PUCCH-AN” message) can be provided to the UE as part of control information to inform the UE which PUCCH to use, which in turn can be changed every few milliseconds using another RRC session. Either of these possibilities can be used to provide initial PUCCH configuration information. However, neither of these possibilities addresses the underlying problem of identifying Figure 9 the PUCCH configuration to use for a given SPS session. In the example below Figure 10 , these RRC transmissions can not provide the UE with a list of PUCCH configurations, and the UE can receive information of its SPS configuration during an initial RRC session, including an initial PUCCH.

[0127] Accordingly, in some aspects, an additional information field can be added to the Layer 1 PDCCH. The additional information field can include DCI that adjusts the PDSCH configuration, and can also include additional fields to enable the base station to modify PUCCH configuration parameters for any duration deemed appropriate after an SPS activation / re-activation period. In one configuration, an SPS re-activation signal can indicate that the UE is to change its PUCCH configuration for all subsequent SPS periods, unless and until that PUCCH configuration is subsequently changed by an RRC session or another SPS re-activation. A corresponding additional field can provide data indicating the number of cycles or periods for which the change to the uplink PUCCH applies. This data can include, for example, a base station-specified PUCCH configuration (e.g., different PRBs, transmit beams, and other channel parameters) and the number of SPS periods or cycles in which the PUCCH is to remain at that specified configuration. This data can alternatively or additionally indicate a period of time in which the PUCCH is to remain active in SPS periods, which can inferentially indicate the number of periods or cycles. In some aspects, the UE can continue to use the specified uplink channel configuration for the specified length of time / number of cycles until some specified expiration time or period, or until the base station provides another re-activation cycle that changes the PUCCH configuration prior to the specified expiration.

[0128] If the PUCCH configuration remains unchanged for a specified number of cycles, the UE can revert to the initial PUCCH configuration from the RRC session at the start of the SPS session. Alternatively, at the expiration of the period, the UE can be instructed by the UE or can otherwise default to one of the PUCCH configurations in the possible configuration list. The base station can continue to use SRS to evaluate channel conditions to optimize both uplink and downlink configurations, changing the uplink configuration when appropriate.

[0129] Figure 10 is a timing diagram 1000 of an example SPS reactivation between a base station and a UE.

[0130] Beginning at the first SPS period / cycle of 1 ms, the base station can transmit SPS data on the PDSCH channel at 1004. After a period of twenty symbols, N1, the UE can transmit an acknowledgement 1020 of the properly decoded data. The UE can also transmit an SRS to the base station (1022).

[0131] During the next cycle 1002, the base station can transmit data on the PDSCH channel using the same channel configuration at 1008. Channel conditions can have changed, and the UE can be unable to decode the data from 1008. The UE can accordingly transmit a NACK 1024 on the PUCCH as configured by the initial RRC session (and transmit another SRS 1026).

[0132] At 1002, the UE can transmit on the PDCCH channel (i) an SPS reactivation DCI (e.g., specifying an SPS PDSCH downlink configuration change via newly specified PRBs, beams, and other channel parameters), and (ii) a new PUCCH configuration change along with a condition (e.g., specifying an appropriate SPS PUCCH uplink configuration change via newly specified PRBs, beams, etc.). The optional condition can be an indication of whether the newly configured PUCCH resource can apply to one, two, or another specified number or time duration, or all subsequent (SPS A / N) PUCCHs until a defined scenario occurs, such as until another SPS reactivation is performed or until an RRC signaling period occurs. Without a condition, the UE can be configured to use the new PUCCH configuration unless the PUCCH configuration is later changed. In some aspects, the UE can be configured to use the newly allocated PUCCH configuration once, and then return to the previous configuration unless otherwise indicated by the condition.

[0133] Referring back to Figure 10For example, assume that the SRS 1026 indicates to the base station that the current PUCCH resource is experiencing inter-cell interference. The base station will transmit the SPS reactivation DCI and the uplink PUCCH information depending on these channel conditions. Upon identifying the PUCCH as a new configuration along with data indicating the period / cycle number for which this new PUCCH remains active, the base station sends this information on the current PDCCH. Upon receiving this transmission, the UE can adjust its new reception parameters accordingly for receiving the SPS data on the allocated PDSCH 1011. The UE can then identify the new PUCCH configuration and optional data indicating the range of applicability of this new configuration. The UE can then transmit the ACK 1028 using the specified PUCCH configuration.

[0134] If the channel estimates of the base station are consistent throughout the duration of the SPS period shown, the base station can continue to transmit shared data on the PDSCH as configured by the RRC resources or by the DCI, as shown by the transmissions of 1012, 1014, and 1016. In response, the UE receives the data and sends ACKs at 1032, 1038, and 1044. Meanwhile, the SRS transmissions at 1034, 1040, and 1046 continue to indicate channel conditions, and the SPS proceeds smoothly. A single reactivation 1010 can be used, and at most one data retransmission for PDSCH 1011 can be used. Thus, the overhead can be significantly reduced.

[0135] For example, if the UE is not provided with SPS-PUCCH-AN-List and transmits HARQ-ACK information corresponding to PDSCH reception without a corresponding PDCCH, the PUCCH resource for the corresponding PUCCH transmission with HARQ-ACK information can be provided by the parameter n1PUCCH-AN or by the latest PUCCH configuration in the latest PDCCH.

[0136] For example, as mentioned with reference to Figure 10 As mentioned above, the uplink information described above can be modified and can remain at the same level for any number of SPS periods (cycles) until the SPS reactivation changes the uplink information.

[0137] Figure 11is a timing diagram of an example SPS period 1100 involving a signal exchange between a UE 1104 and a base station 1102. During the Nth SPS period, the base station 1102 can transmit SPS data 1105 to the UE 1104 on a PDSCH channel. The UE 1104 can send an ACK back to the base station 1102 at 1108. The UE can also send a SRS signal 1110, such as by using the same channel resources used by the UE 1104 to send the ACK, although the network can use different configurations.

[0138] As mentioned in 1106, the UE can begin to experience increased inter-cell interference on the uplink. In 1111, the base station can identify the increased uplink interference and be only able to decode the ACK on the existing PUCCH channel. Based on channel measurements made by the base station and other criteria, the channel resource allocation is determined by the network, and the base station proactively performs another SPS reactivation before the uplink interference causes data loss.

[0139] The base station 1102 can transmit an SPS reactivation signal 1114 on a downlink control channel. The signal can specify a new PUCCH configuration, which can include a frequency that is not affected by the current interference. The protocol can be that the new PUCCH is adopted by the UE 1104 and can be used for all successive SPS periods, including the current N+1 period, until the value is changed by another SPS reactivation signal from the base station 1102, or a new RRC signaling session changes the value.

[0140] Accordingly, in the N+1 SPS period, the base station 1102 (e.g., the base station) can transmit an SPS reactivation signal 1114 on a PDCCH including a newly configured PUCCH data. The UE 1104 can receive the downlink control channel transmission. The base station 1102 can also transmit data on a PDSCH 1115. The UE 1104 can receive the data and accordingly transmit an ACK 1116 to the base station 1102 using the new PUCCH configuration. In 1118, the UE 1104 can continue to use the new PUCCH configuration until otherwise instructed by the base station 1102.

[0141] Figure 12 is a flowchart 1200 of a method of wireless communication. The method can be performed by a UE (e.g., the UE 104, the UE 404, 504, 604, 704, 1104, etc.). The method can be used to improve the efficiency of the SPS reactivation procedure.

[0142] At 1202, the UE can receive a first SPS reactivation DCI from a base station. The reception at 1202 can include receiving a DCI that reactivates a SPS configuration, as described in connection with Figure 7Aspects described herein can be used in a wireless communication system. FIG. 7 illustrates an example of a wireless communication system 700 that supports multiple SPS reactivation DCIs, in accordance with aspects of the present disclosure. For example, UE 704 can receive a first reactivation DCI 706 from base station 702. In some aspects, the first SPS reactivation DCI and the second SPS reactivation DCI are for PDSCH. In some aspects, the first SPS reactivation DCI or the second SPS reactivation DCI modifies one or more PUCCH parameters including a PRI. For example, 1202 can be performed by a SPS component 2044 at a UE 704 as described with reference to FIG. 2. Figure 20 Aspects described herein can be used in a wireless communication system. FIG. 7 illustrates an example of a wireless communication system 700 that supports multiple SPS reactivation DCIs, in accordance with aspects of the present disclosure. For example, UE 704 can receive a first reactivation DCI 706 from base station 702. In some aspects, the first SPS reactivation DCI and the second SPS reactivation DCI are for PDSCH. In some aspects, the first SPS reactivation DCI or the second SPS reactivation DCI modifies one or more PUCCH parameters including a PRI. For example, 1202 can be performed by a SPS component 2044 at a UE 704 as described with reference to FIG. 2.

[0143] At 1204, the UE can receive, from the base station, a second SPS reactivation DCI. The reception at 1204 can include the reception of a DCI described with reference to FIG. 7. Figure 7 Aspects described herein can be used in a wireless communication system. FIG. 7 illustrates an example of a wireless communication system 700 that supports multiple SPS reactivation DCIs, in accordance with aspects of the present disclosure. For example, UE 704 can receive a first reactivation DCI 706 from base station 702. In some aspects, the first SPS reactivation DCI and the second SPS reactivation DCI are for PDSCH. In some aspects, the first SPS reactivation DCI or the second SPS reactivation DCI modifies one or more PUCCH parameters including a PRI. For example, 1202 can be performed by a SPS component 2044 at a UE 704 as described with reference to FIG. 2. Figure 20 Aspects described herein can be used in a wireless communication system. FIG. 7 illustrates an example of a wireless communication system 700 that supports multiple SPS reactivation DCIs, in accordance with aspects of the present disclosure. For example, UE 704 can receive a first reactivation DCI 706 from base station 702. In some aspects, the first SPS reactivation DCI and the second SPS reactivation DCI are for PDSCH. In some aspects, the first SPS reactivation DCI or the second SPS reactivation DCI modifies one or more PUCCH parameters including a PRI. For example, 1202 can be performed by a SPS component 2044 at a UE 704 as described with reference to FIG. 2.

[0144] At 1206, the UE can transmit, to the base station, HARQ feedback indicating detection of the received first SPS reactivation DCI and the received second SPS reactivation DCI, respectively. For example, UE 704 can transmit ACK 710 to base station 702. The transmission at 1206 can include the transmission of a HARQ feedback described with reference to FIG. 7. Figure 7 Aspects described herein can be used in a wireless communication system. FIG. 7 illustrates an example of a wireless communication system 700 that supports multiple SPS reactivation DCIs, in accordance with aspects of the present disclosure. For example, UE 704 can receive a first reactivation DCI 706 from base station 702. In some aspects, the first SPS reactivation DCI and the second SPS reactivation DCI are for PDSCH. In some aspects, the first SPS reactivation DCI or the second SPS reactivation DCI modifies one or more PUCCH parameters including a PRI. For example, 1202 can be performed by a SPS component 2044 at a UE 704 as described with reference to FIG. 2. Figure 20 Aspects described herein can be used in a wireless communication system. FIG. 7 illustrates an example of a wireless communication system 700 that supports multiple SPS reactivation DCIs, in accordance with aspects of the present disclosure. For example, UE 704 can receive a first reactivation DCI 706 from base station 702. In some aspects, the first SPS reactivation DCI and the second SPS reactivation DCI are for PDSCH. In some aspects, the first SPS reactivation DCI or the second SPS reactivation DCI modifies one or more PUCCH parameters including a PRI. For example, 1202 can be performed by a SPS component 2044 at a UE 704 as described with reference to FIG. 2.

[0145] Figure 13is a flowchart 1300 of a method of wireless communication. The method can be performed by a UE (e.g., the UE 104, the UE 404, 504, 604, 704, 1104, etc.). The method can be used to improve the efficiency of the SPS reactivation procedure.

[0146] At 1302, the UE can receive, from a base station, a first SPS reactivation DCI. The reception at 1302 can include the aspects described in connection with the reception by the SPS component 2044 of the UE 704 from the base station 702 of the first reactivation DCI 706 in FIG. 7. For example, the UE 704 can receive, from the base station 702, the first reactivation DCI 706. In some aspects, the first SPS reactivation DCI and the second SPS reactivation DCI are for PDSCH. In some aspects, the first SPS reactivation DCI or the second SPS reactivation DCI modifies one or more PUCCH parameters including a PRI. For example, 1302 can be performed by the SPS component 2044 of the UE 704 in FIG. 2. Figure 7 Figure 20 At 1304, the UE can receive, from the base station, a second SPS reactivation DCI. The reception at 1304 can include the aspects described in connection with the reception by the SPS component 2044 of the UE 704 from the base station 702 of the second reactivation DCI 708 in FIG. 7. For example, the UE 704 can receive, from the base station 702, the second reactivation DCI 708. In some aspects, the DAI for the one or more SPS PDSCHs is also for the first SPS reactivation DCI and the second SPS reactivation DCI. The DAI can be included in the first SPS reactivation DCI or the second SPS reactivation DCI. The DAI can include two bits for PDCCHs associated with SPS. In some aspects, the first SPS reactivation DCI or the second SPS reactivation DCI includes a field of a SPS configuration index type. In some aspects, a first set of PUCCH resources is associated with a first SPS and a second set of PUCCH resources is associated with a second SPS. For example, 1304 can be performed by the SPS component 2044 of the UE 704 in FIG. 2.

[0147] At 1306, the UE can transmit, to the base station, HARQ feedback indicating detection of the received first SPS reactivation DCI and the received second SPS reactivation DCI, respectively. For example, the UE 704 can transmit the ACK 710 to the base station 702. The transmission at 1306 can include the aspects described in connection with the transmission by the SPS component 2044 of the UE 704 of the ACK 710 to the base station 702 in FIG. 7. For example, the UE 704 can transmit, to the base station 702, the ACK 710. In some aspects, the first SPS reactivation DCI or the second SPS reactivation DCI modifies one or more PUCCH parameters including a PRI. For example, 1306 can be performed by the SPS component 2044 of the UE 704 in FIG. 2. Figure 7 Figure 20

[0148] At 1306, the UE can transmit, to the base station, HARQ feedback indicating detection of the received first SPS reactivation DCI and the received second SPS reactivation DCI, respectively. For example, the UE 704 can transmit the ACK 710 to the base station 702. The transmission at 1306 can include the aspects described in connection with the transmission by the SPS component 2044 of the UE 704 of the ACK 710 to the base station 702 in FIG. 7. For example, the UE 704 can transmit, to the base station 702, the ACK 710. In some aspects, the first SPS reactivation DCI or the second SPS reactivation DCI modifies one or more PUCCH parameters including a PRI. For example, 1306 can be performed by the SPS component 2044 of the UE 704 in FIG. 2. Figure 7 ​​​described at 710. In some aspects, the HARQ feedback includes a first indication indicating receipt of the received first SPS reactivation DCI and a second indication indicating receipt of the received second SPS reactivation DCI. In some aspects, the HARQ feedback further includes a third indication indicating whether a first SPS PDSCH associated with the first SPS reactivation DCI was received and a second set of symbols indicating whether a second SPS PDSCH associated with the second SPS reactivation DCI was received. For example, 1306 can be performed by ACK / NACK component 2042 in FIG. Figure 20

[0149] In some aspects, the UE can receive, at 1308, a first SPS release for the first SPS prior to receiving the first SPS reactivation DCI. In some aspects, the UE can receive, at 1310, a second SPS release for the second SPS prior to receiving the second SPS reactivation DCI.

[0150] Figure 14 is a flow diagram 1400 of a method of wireless communication. The method can be performed by a base station (e.g., the base station 102 / 180; the base station 402, 502, 602, 702, 1102, etc.). The method can be used to improve the efficiency of an SPS reactivation procedure.

[0151] At 1402, the base station transmits, to a UE, a first SPS reactivation DCI. The transmission at 1402 can include aspects described in connection with Figure 7 described at 706. For example, the base station 702 can transmit, to the UE 704, the first SPS reactivation DCI 706. In some aspects, the first SPS reactivation DCI and the second SPS reactivation DCI are for PDSCHs. In some aspects, the first SPS reactivation DCI or the second SPS reactivation DCI modifies one or more PUCCH parameters including a PRI. In some aspects, 1402 can be performed by an SPS component 2142.

[0152] At 1404, the base station can transmit, to the UE, a second SPS reactivation DCI. The transmission at 1404 can include aspects described in connection with Figure 7 ​Aspects described with respect to 708. For example, the base station 702 can transmit a second SPS reactivation DCI 708 to the UE 704. In some aspects, the DAI for the one or more SPS PDSCHs is also for the first SPS reactivation DCI and the second SPS reactivation DCI. The DAI can be included in the first SPS reactivation DCI or the second SPS reactivation DCI. The DAI can include two bits for PDCCHs associated with SPSs. In some aspects, the first SPS reactivation DCI or the second SPS reactivation DCI includes a field of SPS configuration index type. In some aspects, a first set of PUCCH resources is associated with a first SPS and a second set of PUCCH resources is associated with a second SPS. In some aspects, 1404 can be performed by the SPS component 2142.

[0153] At 1406, the base station can receive, from the UE, HARQ feedback indicating detection of the received first SPS reactivation DCI and the received second SPS reactivation DCI, respectively. The reception at 1406 can include aspects described with reference to Figure 7 Aspects described with respect to 710. For example, the base station 702 can receive, from the UE 704, HARQ feedback 710. In some aspects, the HARQ feedback includes a first indication indicating reception of the received first SPS reactivation DCI and a second indication indicating reception of the received second SPS reactivation DCI. In some aspects, the HARQ feedback further includes a third indication indicating whether a first SPS physical data shared channel (PDSCH) associated with the first SPS reactivation DCI was received and a second indication indicating whether a second set of symbols of a second SPS PDSCH associated with the second SPS reactivation DCI was received. In some aspects, 1404 can be performed by the HARQ component 2144.

[0154] Figure 15 is a flowchart 1500 of a method of wireless communication. The method can be performed by a base station (e.g., the base station 102 / 180; the base station 402, 502, 602, 702, 1102, etc.). The method can be used to improve the efficiency of the SPS reactivation procedure.

[0155] At 1502, the base station transmits, to a UE, a first SPS reactivation DCI. The transmission at 1502 can include aspects described with reference to Figure 7Aspects described with reference to 706. For example, the base station 702 can transmit a first SPS reactivation DCI 706 to the UE 704. In some aspects, the first SPS reactivation DCI and the second SPS reactivation DCI are for PDSCH. In some aspects, the first SPS reactivation DCI or the second SPS reactivation DCI modifies one or more PUCCH parameters including a PRI. In some aspects, 1502 can be performed by the SPS component 2142.

[0156] At 1504, the base station can transmit a second SPS reactivation DCI to the UE. The transmission at 1504 can include aspects described with reference to 708. For example, the base station 702 can transmit a second SPS reactivation DCI 708 to the UE 704. In some aspects, the DAI for the one or more SPS PDSCHs is also for the first SPS reactivation DCI and the second SPS reactivation DCI. The DAI can be included in the first SPS reactivation DCI or the second SPS reactivation DCI. The DAI can include two bits for PDCCHs associated with SPS. In some aspects, the first SPS reactivation DCI or the second SPS reactivation DCI includes a field of a SPS configuration index type. In some aspects, a first set of PUCCH resources is associated with a first SPS and a second set of PUCCH resources is associated with a second SPS. In some aspects, 1504 can be performed by the SPS component 2142. Figure 7 At 1506, the base station can receive, from the UE, HARQ feedback indicating detection of the received first SPS reactivation DCI and the received second SPS reactivation DCI, respectively. The reception at 1506 can include aspects described with reference to 710. For example, the base station 702 can receive, from the UE 704, HARQ feedback 710. In some aspects, the HARQ feedback includes a first indication indicating reception of the received first SPS reactivation DCI and a second indication indicating reception of the received second SPS reactivation DCI. In some aspects, the HARQ feedback further includes a third indication indicating whether a first SPS PDSCH associated with the first SPS reactivation DCI was received and a second indication indicating whether a second set of symbols of a second SPS PDSCH associated with the second SPS reactivation DCI was received. In some aspects, 1504 can be performed by the HARQ component 2144.

[0157] Figure 7 At 1506, the base station can receive, from the UE, HARQ feedback indicating detection of the received first SPS reactivation DCI and the received second SPS reactivation DCI, respectively. The reception at 1506 can include aspects described with reference to 710. For example, the base station 702 can receive, from the UE 704, HARQ feedback 710. In some aspects, the HARQ feedback includes a first indication indicating reception of the received first SPS reactivation DCI and a second indication indicating reception of the received second SPS reactivation DCI. In some aspects, the HARQ feedback further includes a third indication indicating whether a first SPS PDSCH associated with the first SPS reactivation DCI was received and a second indication indicating whether a second set of symbols of a second SPS PDSCH associated with the second SPS reactivation DCI was received. In some aspects, 1504 can be performed by the HARQ component 2144.

[0158] ​In some aspects, the base station can transmit, at 1508, a first SPS release for the first SPS prior to transmitting the first SPS reactivation DCI. In some aspects, the base station can transmit, at 1510, a second SPS release for the second SPS prior to transmitting the second SPS reactivation DCI.

[0159] Figure 16 FIG. 16 is a flow diagram 1600 of a method of wireless communication. The method can be performed by a UE (e.g., the UE 104, the UE 1104, etc.). At 1602, the UE can receive, from a base station, a PUCCH configuration that remains valid for all successive SPS periods unless conditions set by data accompanying the PUCCH configuration or later changed. The conditions that can be transmitted on a PDCCH can include those mentioned in connection with Figure 10 FIG. 16, such as allocating uplink control channel information for a specified number of SPS periods, or indefinitely for an SPS session unless the UE receives different instructions. For example, the UE 1104 can receive a PUCCH configuration from the base station 1102. In some aspects, 1602 can be performed by the SPS component 2044 of Figure 20 FIG. 16.

[0160] At 1612, the UE transmits, for each of the successive SPS periods, a response to a data message from the base station using the configured PUCCH. In some aspects, 1612 can be performed by the ACK / NACK component 2042 of Figure 20 FIG. 16. For example, the UE 1104 can transmit a response to the base station 1102.

[0161] Figure 17 FIG. 17 is a flow diagram 1700 of a method of wireless communication. The method can be performed by a UE (e.g., the UE 104, the UE 1104, etc.). At 1702, the UE can receive, from a base station, a PUCCH configuration that remains valid for all successive SPS periods unless conditions set by data accompanying the PUCCH configuration or later changed. For example, the UE 1104 can receive a PUCCH configuration from the base station 1102. In some aspects, 1702 can be performed by the SPS component 2044 of Figure 20 FIG. 17.

[0162] At 1712, the UE transmits, for each of the successive SPS periods, a response to a data message from the base station using the configured PUCCH. In some aspects, 1712 can be performed by the ACK / NACK component 2042 of Figure 20 FIG. 17. For example, the UE 1104 can transmit a response to the base station 1102.

[0163] At 1706, the UE can receive, on the PDCCH channel, data indicating a number of consecutive SPS periods for which the configured PUCCH is valid. In some aspects, 1706 can be performed by reception component 2030 of FIG. 13. Figure 20 At 1714, the UE can transmit, to the base station, a response to a message from the base station using the allocated PUCCH to indicate an ACK or a NACK. For example, the UE 1104 can transmit, to the base station 1102, a response. In some aspects, 1714 can be performed by ACK / NACK component 2042 of FIG. 13.

[0164] At 1708, the UE can receive, during the SPS reactivation period, DCI from the base station specifying downlink information for a PDSCH. In some aspects, 1708 can be performed by SPS component 2044. For example, the UE 1104 can receive, during the SPS reactivation period, DCI from the base station 1102 specifying downlink information for a PDSCH.

[0165] At 1710, the UE can receive a new PUCCH configuration included in the RRC signaling interval or another SPS reactivation period. In some aspects, 1710 can be performed by SPS component 2044. For example, the UE 1104 can receive, from the base station 1102, a new PUCCH configuration included in the RRC signaling interval or another SPS reactivation period. 1710 can be performed by reception component 2030 of FIG. 13. Figure 20

[0166] At 1714, the UE can transmit, to the base station, a response to a message from the base station using the allocated PUCCH to indicate an ACK or a NACK. For example, the UE 1104 can transmit, to the base station 1102, a response. In some aspects, 1714 can be performed by ACK / NACK component 2042 of FIG. 13. Figure 20

[0167] At 1716, the UE can also transmit, to the base station, a response to a subsequent SPS -based message using a default PUCCH obtained from a previous RRC session after the number of consecutive SPS periods is complete. For example, the UE 1104 can transmit, to the base station 1102, a response to a subsequent SPS -based message using a default PUCCH obtained from a previous RRC session after the number of consecutive SPS periods is complete. In some aspects, 1716 can be performed by ACK / NACK component 2042 of FIG. 13. Figure 20

[0168] Figure 18 FIG. 18 shows a flowchart of a method of wireless communication performed by a base station (e.g., base station 102 / 180; base station 1102; etc.).

[0169] ​​​At 1802, the base station identifies a configuration for PUCCH during the SPS reactivation period that is valid for all subsequent SPS periods unless the configuration includes a condition or the configuration is later changed. For example, the base station 1102 can identify a configuration for PUCCH during the SPS reactivation period that is valid for all subsequent SPS periods unless the configuration includes a condition or the configuration is later changed. In some aspects, 1802 can be performed by a SPS component 2142 of a base station 1102 as shown in FIG. 21. Figure 21

[0170] At 1812, the base station can transmit the identified data to the UE on the PDCCH during the SPS reactivation period. For example, the base station 1102 can transmit the identified data to the UE 1104 on the PDCCH during the SPS reactivation period. In some aspects, 1812 can be performed by a SPS component 2142 of a base station 1102 as shown in FIG. 21. Figure 21

[0171] Figure 19 A flow diagram illustrating wireless communication by a base station (e.g., base station 102 / 190; base station 1102; etc.) is shown.

[0172] At 1902, the base station identifies a configuration for PUCCH during the SPS reactivation period that is valid for all subsequent SPS periods unless the configuration includes a condition or the configuration is later changed. For example, the base station 1102 can identify a configuration for PUCCH during the SPS reactivation period that is valid for all subsequent SPS periods unless the configuration includes a condition or the configuration is later changed. In some aspects, 1902 can be performed by a SPS component 2142 of a base station 1102 as shown in FIG. 21. Figure 21

[0173] At 1912, the base station can transmit the identified data to the UE on the PDCCH during the SPS reactivation period. For example, the base station 1102 can transmit the identified data to the UE 1104 on the PDCCH during the SPS reactivation period. In some aspects, 1912 can be performed by a SPS component 2142 of a base station 1102 as shown in FIG. 21. Figure 21

[0174] At 1906, the base station can receive a response to the data transmission from the UE during each of the subsequent SPS periods. For example, the base station 1102 can receive a response to the data transmission from the UE 1104 during each of the subsequent SPS periods. In some aspects, 1906 can be performed by a SPS component 2142 of a base station 1102 as shown in FIG. 21. Figure 21

[0175] ​​​​​At 1908, the base station can transmit, with the SPS PDCCH, a condition indicating a time duration for the SPS session to expire unless another SPS reactivation changes the configuration of the uplink control channel. For example, the base station 1102 can transmit, with the SPS PDCCH, a condition indicating a time duration for the SPS session to expire. In some aspects, 1908 can be performed by an SPS component 2142 of FIG. 21. Figure 21 The UE can use the new PUCCH configuration until the specified expiration, unless the UE receives another SPS reactivation that changes the configuration.

[0176] At 1910, the base station receives a response, such as an ACK or NACK, on the configured PUCCH during each of the successive SPS periods. For example, the base station 1102 can receive a response, such as an ACK or NACK, on the configured PUCCH during each of the successive SPS periods. In some aspects, 1910 can be performed by a HARQ component 2144 of FIG. 21. Figure 21

[0177] At 1914, the base station can transmit, to the UE, data (e.g., voice data, sensor data, etc.) related to the SPS configuration on a downlink shared channel. For example, the base station 1102 can transmit, to the UE, data related to the SPS configuration on a downlink shared channel. In some aspects, 1914 can be performed by an SPS component 2142 of FIG. 21. Figure 21

[0178] At 1916, the base station can initiate another SPS reactivation period for continuing use of the SPS session with the appropriate uplink (and downlink) channel configuration when the specified number of successive SPS periods is complete. For example, the base station 1102 can initiate another SPS reactivation period for continuing use of the SPS session with the appropriate uplink (and downlink) channel configuration when the specified number of successive SPS periods is complete. In some aspects, 1916 can be performed by an SPS component 2142 of FIG. 21. Figure 21

[0179] At 1918, the base station can resume SPS transmissions using RRC configuration after the expiration period specified by the condition. For example, the base station 1102 can resume SPS transmissions using RRC configuration after the expiration period specified by the condition. In some aspects, 1918 can be performed by an SPS component 2142 of FIG. 21. Figure 21

[0180] Figure 20 ​​​​FIG. 2 is a diagram of an example of a hardware implementation for the apparatus 2002. The apparatus 2002 can be a UE, a component of a UE, or can implement UE functionality. In some aspects, the apparatus 2002 can include a cellular baseband processor 2004 (also referred to as a modem) coupled with a cellular RF transceiver 2022. In some aspects, the apparatus 2002 can further include one or more Subscriber Identity Modules (SIM) cards 2020, an application processor 2006 coupled with a secure digital (SD) card 2008 and a screen 2010, a Bluetooth module 2012, a wireless local area network (WLAN) module 2014, a Global Positioning System (GPS) module 2016, or a power supply 2018. The cellular baseband processor 2004 communicates with the UE 104 and / or BS 102 / 180 by way of the cellular RF transceiver 2022. The cellular baseband processor 2004 can include a computer-readable medium / memory. The computer-readable medium / memory can be non-transitory. The cellular baseband processor 2004 is Figure 3 responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 2004, causes the cellular baseband processor 2004 to perform the various functions described supra. The computer-readable medium / memory can also be used for storing data that is manipulated by the cellular baseband processor 2004 when executing software. The cellular baseband processor 2004 further includes a reception component 2030, a communication manager 2032, and a transmission component 2034. The communication manager 2032 includes the one or more illustrated components. The components of the communication manager 2032 can be stored in the computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 2004. The cellular baseband processor 2004 can be a component of the UE 350 and can include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the apparatus 2002 can be a modem chip and include only the baseband processor 2004, and in another configuration, the apparatus 2002 can be an entire UE (e.g., see 350) and include the additional modules of the apparatus 2002.

[0181] The communication manager 2032 can include an SPS component 2044, which can be configured to perform one or more of 1202, 1204, 1302, 1304, 1602, 1702, 1706, 1708, or 1710. The communication manager 2032 can further include an ACK / NACK component 2042, which can be configured to perform one or more of 1206, 1306, 1612, 1712, 1714, or 1716.

[0182] The apparatus can include means for performing Figures 12-13additional components to each of the blocks of the algorithms in the flow charts of 16-17. As such, Figures 12-13 Each block of the flow charts of 16-17 can be performed by a component and the apparatus can include one or more of those components. The components can 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.

[0183] As illustrated, the device 2002 can include various components configured to perform various functions. In one configuration, the device 2002, and in particular the cellular baseband processor 2004, can include means for receiving, from a base station, a PUCCH configuration during an SPS reactivation period, the PUCCH configuration remaining valid for all successive SPS periods unless conditioned by data accompanying the PUCCH configuration or later changed. The cellular baseband processor 2004 can further include means for transmitting, for each of the successive SPS periods, a response to a data message from the base station using the configured PUCCH. The cellular baseband processor 2004 can further include means for receiving, on a PDCCH, data indicating a number of successive SPS periods for which the configured PUCCH is valid. The cellular baseband processor 2004 can further include means for transmitting, after the number of successive SPS periods is complete, a response to a subsequent SPS-based message from the base station using a default PUCCH obtained from a previous RRC session. The cellular baseband processor 2004 can further include means for receiving, from the base station during the SPS reactivation period, a DCI specifying a configuration for a physical downlink PDSCH. The cellular baseband processor 2004 can further include means for transmitting a response to a message from the base station further including sending one of an ACK or a NACK in response to whether the message was successfully decoded. The cellular baseband processor 2004 can further include means for transmitting, during each of the SPS periods, an SRS after transmitting a response to the base station. The cellular baseband processor 2004 can further include means for receiving a first SPS reactivation DCI from the base station. The cellular baseband processor 2004 can further include means for receiving a second SPS reactivation DCI from the base station. The cellular baseband processor 2004 can further include means for transmitting HARQ feedback to the base station indicating detection of the received first SPS reactivation DCI and the received second SPS reactivation DCI, respectively. The cellular baseband processor 2004 can further include means for receiving a first SPS release. The cellular baseband processor 2004 can further include means for receiving a second SPS release. The means can be one or more of the components of the device 2002 configured to perform the functions recited by the means. As described above, the device 2002 can include the TX processor 368, the RX processor 356, and the controller / processor 359. As such, in one configuration, the means can be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the means.

[0184] Figure 21is an example of a diagram 2100 that illustrates hardware implementation for the apparatus 2102. The apparatus 2102 can be a base station, a component of a base station, or can implement base station functionality. In some aspects, the apparatus 2002 can include a baseband unit 2104. The baseband unit 2104 can communicate with the UE 104 through a cellular RF transceiver 2122. The baseband unit 2104 can include a computer-readable medium / memory. The baseband unit 2104 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the baseband unit 2104, causes the baseband unit 2104 to perform the various functions described supra. The computer-readable medium / memory can also be used for storing data that is manipulated by the baseband unit 2104 when executing software. The baseband unit 2104 further includes a reception component 2130, a communication manager 2132, and a transmission component 2134. The communication manager 2132 includes the one or more illustrated components. The components of the communication manager 2132 can be stored in the computer-readable medium / memory and / or configured as hardware within the baseband unit 2104. The baseband unit 2104 can be a component of the base station 310 and can include the memory 376 and / or at least one of the TX processor 316, the RX processor 370, and the controller / processor 375.

[0185] The communication manager 2132 can include an SPS component 2142, which can perform one or more of 1402, 1404, 1502, 1504, 1802, 1812, 1902, 1912, 1908, 1914, 1916, or 1918. The communication manager 2132 further can include a HARQ component 2144, which can perform one or more of 1406, 1506, 1906, or 1910.

[0186] The apparatus can include additional components that perform each of the blocks of the algorithm in the flowcharts of FIGs. 14-19. As such, Figures 14-15 Each block in the flowcharts of FIGs. 14-19 can be performed by a component and the apparatus can include one or more of those components. The components can 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. Figures 14-15 Each block in the flowcharts of FIGs. 14-19 can be performed by a component and the apparatus can include one or more of those components. The components can 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.

[0187] As illustrated, the device 2102 can include various components configured to perform various functions. In one configuration, the device 2102, and in particular the baseband unit 2104, can include means for identifying a configuration for a PUCCH during an SPS reactivation period, the configuration being valid for all successive SPS periods unless the configuration includes a condition or the configuration is later changed. The baseband unit 2104 can further include means for transmitting the identified PUCCH configuration to a UE on a PDCCH during the SPS reactivation period. The baseband unit 2104 can further include means for transmitting other data to the UE on a PDSCH during each of the successive SPS periods. The baseband unit 2104 can further include means for initiating another SPS reactivation period for determining another PUCCH configuration allocated to the UE after transmitting the other data during each of the number of successive SPS periods. The baseband unit 2104 can further include means for receiving a response from the UE on the configured PUCCH to the transmission on the PDSCH during each of the successive SPS periods. The baseband unit 2104 can further include means for resuming SPS transmissions using a default RRC configuration after an expiration period of successive SPS transmissions specified by a condition. The baseband unit 2104 can further include means for identifying a DCI including a configuration of a downlink shared channel. The baseband unit 2104 can further include means for transmitting a first SPS reactivation DCI to the UE. The baseband unit 2104 can further include means for transmitting a second SPS reactivation DCI to the UE. The baseband unit 2104 can further include means for receiving HARQ feedback from the UE indicating detection of the received first SPS reactivation DCI and the received second SPS reactivation DCI, respectively. The baseband unit 2104 can further include means for transmitting a first SPS release. The baseband unit 2104 can further include means for transmitting a second SPS release. The means can be one or more of the components of the device 2102 configured to perform the functions recited by the means. As described above, the device 2102 can include the TX processor 316, the RX processor 370, and the controller / processor 375. As such, in one configuration, the means can be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recited by the means.

[0188] It should be understood that the specific order or hierarchy of various blocks disclosed in the exemplary processes / flow diagrams is an illustration. It should be appreciated that based upon design choices, the specific order or hierarchy of various blocks can be re-arranged. Further, some blocks can be processed in parallel or in an order different than that described. The various blocks can be found to be stored in a computer-readable medium which can be a single memory or spread across multiple memories. The methods presented and / or flow diagrams presented are examples terms of the various blocks presented and can be implemented by various means, such as different computer-readable mediums or hardware. Further, a number of the blocks can be deleted or combined into fewer blocks. The resulting sequences may

[0189] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will readily be understood by those skilled in the art, and the universal principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be granted the full scope consistent with the language of the claims, wherein references to the singular form of an element, unless specifically stated otherwise, are not intended to mean “one and only one,” but rather “one or more.” Terms such as “if,” “when,” and “at the time of,” should be interpreted as meaning “under this condition,” rather than implying a direct temporal relationship or reaction. That is, these phrases (e.g., “when”) do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but only imply that an action will occur when a condition is met, without requiring a specific or immediate temporal constraint for the action to occur. The term “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as superior to or overriding other aspects. Unless specifically stated otherwise, the term “some / a” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. Elements of all aspects described throughout this disclosure that are presently or hereafter known to those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended as a donation to the public, whether or not such disclosure is explicitly stated in the claims. Terms such as “module,” “mechanism,” “element,” and “device” are not necessarily substitutes for the term “apparatus.” Thus, no claim element should be interpreted as an apparatus plus a function unless the element is explicitly stated using the phrase “apparatus for…”.

[0190] The following aspects are illustrative only and may be combined with other aspects or teachings described herein without limitation.

[0191] Aspect 1 is an apparatus for wireless communication at a UE, comprising a memory; and at least one processor coupled with the memory and configured to: receive, from a base station, a first SPS reactivation DCI; receive, from the base station, a second SPS reactivation DCI; and transmit, to the base station, HARQ feedback indicating detection of the first SPS reactivation DCI and the second SPS reactivation DCI, respectively.

[0192] Aspect 2 is the apparatus of Aspect 1, wherein the first SPS reactivation DCI or the second SPS reactivation DCI modifies one or more PUCCH parameters including a PRI.

[0193] Aspect 3 is the apparatus of any of Aspects 1-2, wherein the HARQ feedback comprises a first indication indicating reception of the first SPS reactivation DCI and a second indication indicating reception of the second SPS reactivation DCI.

[0194] Aspect 4 is the apparatus of any of Aspects 1-3, wherein the HARQ feedback further comprises a third indication indicating whether a first SPS PDSCH associated with the first SPS reactivation DCI is received and a second set of indications indicating whether a second SPS PDSCH associated with the second SPS reactivation DCI is received, wherein a DAI for one or more SPS PDSCHs is also for the first SPS reactivation DCI and the second SPS reactivation DCI, and wherein the DAI is included in the first SPS reactivation DCI or the second SPS reactivation DCI.

[0195] Aspect 5 is the apparatus of any of Aspects 1-4, wherein the DAI comprises a number of bits corresponding to a number of SPS configurations.

[0196] Aspect 6 is the apparatus of any of Aspects 1-5, wherein the first SPS reactivation DCI or the second SPS reactivation DCI comprises a field of a SPS configuration index type.

[0197] Aspect 7 is the apparatus of any of Aspects 1-6, wherein a first set of PUCCH resources is associated with a first SPS and a second set of PUCCH resources is associated with a second SPS.

[0198] Aspect 8 is the apparatus of any of Aspects 1-7, wherein the at least one processor is further configured to: receive, prior to receiving the first SPS reactivation DCI, a first SPS release for a first SPS; and receive, prior to receiving the second SPS reactivation DCI, a second SPS release for a second SPS.

[0199] Aspect 9 is an apparatus for wireless communication at a base station, comprising a memory; and at least one processor coupled with the memory and configured to: transmit, to a UE, a first SPS reactivation DCI; transmit, to the UE, a second SPS reactivation DCI; and receive, from the UE, HARQ feedback indicating detection of the first SPS reactivation DCI and the second SPS reactivation DCI, respectively.

[0200] Aspect 10 is the apparatus of Aspect 9, wherein the first SPS reactivation DCI and the second SPS reactivation DCI are for PDSCH.

[0201] Aspect 11 is the apparatus of any of Aspects 9-10, wherein the first SPS reactivation DCI or the second SPS reactivation DCI modifies one or more PUCCH parameters including a PRI.

[0202] Aspect 12 is the apparatus of any of Aspects 9-11, wherein the HARQ feedback comprises a first indication indicating reception of the first SPS reactivation DCI and a second indication indicating reception of the second SPS reactivation DCI.

[0203] Aspect 13 is the apparatus of any of Aspects 9-12, wherein the HARQ feedback further comprises a third indication indicating whether a first SPS PDSCH associated with the first SPS reactivation DCI was received and a second set of indications indicating whether a second SPS PDSCH associated with the second SPS reactivation DCI was received.

[0204] Aspect 14 is the apparatus of any of Aspects 9-13, wherein a DAI for one or more SPS PDSCHs is also for the first SPS reactivation DCI and the second SPS reactivation DCI.

[0205] Aspect 15 is the apparatus of any of Aspects 9-14, wherein the DAI is included in the first SPS reactivation DCI or the second SPS reactivation DCI.

[0206] Aspect 16 is the apparatus of any of Aspects 9-15, wherein the first SPS reactivation DCI or the second SPS reactivation DCI comprises a field of a SPS configuration index type.

[0207] Aspect 17 is an apparatus for wireless communication at a UE, comprising a memory; and at least one processor coupled with the memory and configured to receive, from a base station during an SPS reactivation period, a PUCCH configuration that remains valid for all successive SPS periods unless conditioned by data accompanying the PUCCH configuration or later changed; and transmit, using the PUCCH configuration, a response to a data message from the base station for each of the successive SPS periods.

[0208] Aspect 18 is the apparatus of Aspect 17, wherein the at least one processor is further configured to receive, on a PDCCH, data indicating a number of successive SPS periods for which the PUCCH configuration is valid, and wherein the data indicating the number of successive SPS periods comprises a time duration.

[0209] Aspect 19 is the apparatus of any of Aspects 17-18, wherein the at least one processor is further configured to use a default PUCCH obtained from a previous RRC session to transmit a response to a subsequent SPS-based message from the base station after the number of successive SPS periods is complete.

[0210] Aspect 20 is the apparatus of any of Aspects 17-19, wherein the PUCCH configuration is changed by a new PUCCH configuration included in an RRC signaling interval or another SPS reactivation period.

[0211] Aspect 21 is the apparatus of any of Aspects 17-20, wherein the at least one processor is further configured to receive, from the base station during the SPS reactivation period, a DCI specifying a configuration for a physical downlink PDSCH.

[0212] Aspect 22 is the apparatus of any of Aspects 17-21, wherein the at least one processor is further configured to transmit the response to the data message from the base station by sending one of an ACK or a NACK in response to whether the data message is successfully decoded.

[0213] Aspect 23 is the apparatus of any of Aspects 17-22, wherein the at least one processor is further configured to transmit, during each SPS period, an SRS after transmitting the response to the base station.

[0214] Aspect 24 is the apparatus of any of Aspects 17-23, wherein the PUCCH configuration comprises one or more of a specified beam width, a number of beams, a PRB, or a transmit power.

[0215] Aspect 25 is an apparatus for wireless communication at a base station, comprising a memory; and at least one processor coupled with the memory and configured to: identify a PUCCH configuration during an SPS reactivation period, the PUCCH configuration being valid for all successive SPS periods unless the PUCCH configuration includes a condition or the configuration is later changed; and transmit the PUCCH configuration to a UE on a PDCCH during the SPS reactivation period.

[0216] Aspect 26 is the apparatus of Aspect 25, wherein the condition includes a specified number of successive SPS periods for which the PUCCH configuration is allocated for use by the UE, and wherein the at least one processor coupled to the memory is further configured to transmit other data to the UE on a PDSCH during each of the successive SPS periods.

[0217] Aspect 27 is the apparatus of any of Aspects 25-26, wherein the at least one processor coupled to the memory is further configured to initiate another SPS reactivation period for determining another PUCCH configuration allocated to the UE after transmitting the other data during each of the specified number of successive SPS periods.

[0218] Aspect 28 is the apparatus of any of Aspects 25-27, wherein the at least one processor coupled to the memory is further configured to receive a response to a transmission on the PDSCH from the UE on a PUCCH during each of the successive SPS periods, and wherein the response includes an ACK or a NACK.

[0219] Aspect 29 is the apparatus of any of Aspects 25-28, wherein the at least one processor coupled to the memory is further configured to resume SPS transmissions using a default RRC configuration after an expiration period of successive SPS transmissions specified by the condition.

[0220] Aspect 30 is the apparatus of any of Aspects 25-29, wherein the at least one processor coupled to the memory is further configured to identify DCI, the DCI including a PDSCH configuration, and wherein the DCI configuration includes a specified identity of PRBs.

[0221] Aspect 31 is a method of wireless communication for implementing any of Aspects 1 to 8.

[0222] Aspect 32 is an apparatus for wireless communication, comprising means for implementing any of Aspects 1 to 8.

[0223] Aspect 33 is a computer-readable medium storing computer executable instructions, that when executed by a processor, cause the processor to implement any of Aspects 1 to 8.

[0224] Aspect 34 is a method of wireless communication for implementing any of aspects 9 through 16.

[0225] Aspect 35 is an apparatus for wireless communication including means for implementing any of aspects 9 through 16.

[0226] Aspect 36 is a computer readable medium storing computer executable code, where the code, when executed by a processor, causes the processor to implement any of aspects 9 through 16.

[0227] Aspect 37 is a method of wireless communication for implementing any of aspects 17 through 24.

[0228] Aspect 38 is an apparatus for wireless communication including means for implementing any of aspects 17 through 24.

[0229] Aspect 39 is a computer readable medium storing computer executable code, where the code, when executed by a processor, causes the processor to implement any of aspects 17 through 24.

[0230] Aspect 40 is a method of wireless communication for implementing any of aspects 24 through 30.

[0231] Aspect 41 is an apparatus for wireless communication including means for implementing any of aspects 25 through 30.

[0232] Aspect 42 is a computer readable medium storing computer executable code, where the code, when executed by a processor, causes the processor to implement any of aspects 25 through 30.

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: a memory; and at least one processor coupled to the memory and configured to: receive a first semi-persistent scheduling (SPS) reactivation downlink control information (DCI); receive a second SPS reactivation DCI; and transmit a hybrid automatic repeat request (HARQ) feedback indicating detection of the first SPS reactivation DCI and the second SPS reactivation DCI, respectively, wherein the HARQ feedback comprises a first indication indicating reception of the first SPS reactivation DCI and a second indication indicating reception of the second SPS reactivation DCI.

2. The apparatus of claim 1, wherein the first SPS reactivation DCI or the second SPS reactivation DCI modifies one or more physical uplink control channel (PUCCH) parameters including a PUCCH resource indicator (PRI).

3. The apparatus of claim 1, wherein the HARQ feedback further comprises a third indication indicating whether a first SPS physical data shared channel (PDSCH) associated with the first SPS reactivation DCI is received and a second indication indicating whether a second SPS PDSCH associated with the second SPS reactivation DCI is received for a second set of symbols, wherein a downlink assignment index (DAI) for one or more SPS physical data shared channel (PDSCHs) is further for the first SPS reactivation DCI and the second SPS reactivation DCI, and wherein the DAI is included in the first SPS reactivation DCI or the second SPS reactivation DCI.

4. The apparatus of claim 3, wherein the DAI comprises a number of bits corresponding to a number of SPS configurations.

5. The apparatus of claim 1, wherein the first SPS reactivation DCI or the second SPS reactivation DCI comprises a field of a SPS configuration index type.

6. The apparatus of claim 1, wherein a first set of physical uplink control channel (PUCCH) resources are associated with a first SPS and a second set of PUCCH resources are associated with a second SPS.

7. The apparatus of claim 1, wherein the at least one processor is further configured to: receive a first SPS release for a first SPS prior to receiving the first SPS reactivation DCI; and receive a second SPS release for a second SPS prior to receiving the first SPS reactivation DCI.

8. An apparatus for wireless communication at a network node, comprising: a memory; and at least one processor coupled to the memory and configured to: transmit a first semi-persistent scheduling (SPS) reactivation downlink control information (DCI); transmit a second SPS reactivation DCI; and receiving hybrid automatic repeat request, HARQ, feedback indicating detection of the first SPS reactivation DCI and the second SPS reactivation DCI, respectively, wherein the HARQ feedback includes a first indication indicating reception of the first SPS reactivation DCI and a second indication indicating reception of the second SPS reactivation DCI.

9. The apparatus of claim 8, wherein the first SPS reactivation DCI and the second SPS reactivation DCI are for a physical data shared channel, PDSCH.

10. The apparatus of claim 8, wherein the first SPS reactivation DCI or the second SPS reactivation DCI modifies one or more PUCCH parameters including a physical uplink control channel, PUCCH, resource indicator, PRI.

11. The apparatus of claim 8, wherein the HARQ feedback further includes a third indication indicating whether a first SPS physical data shared channel, PDSCH, associated with the first SPS reactivation DCI was received and a second set of symbols indicating whether a second SPS PDSCH associated with the second SPS reactivation DCI was received.

12. The apparatus of claim 8, wherein a downlink assignment index, DAI, for one or more SPS physical data shared channel, PDSCHs, is also for the first SPS reactivation DCI and the second SPS reactivation DCI.

13. The apparatus of claim 12, wherein the DAI is included in the first SPS reactivation DCI or the second SPS reactivation DCI.

14. The apparatus of claim 8, wherein the first SPS reactivation DCI or the second SPS reactivation DCI includes a field of a SPS configuration index type.

15. A method of wireless communication at a user equipment, UE, comprising: receiving a first semi-persistent scheduling, SPS, reactivation downlink control information, DCI; receiving a second SPS reactivation DCI; and transmitting hybrid automatic repeat request, HARQ, feedback indicating detection of the first SPS reactivation DCI and the second SPS reactivation DCI, respectively, wherein the HARQ feedback includes a first indication indicating reception of the first SPS reactivation DCI and a second indication indicating reception of the second SPS reactivation DCI.

16. A method of wireless communication at a network node, comprising: transmitting a first semi-persistent scheduling, SPS, reactivation downlink control information, DCI; transmitting a second SPS reactivation DCI; and receive hybrid automatic repeat request (HARQ) feedback indicating detection of the first SPS reactivation DCI and the second SPS reactivation DCI, respectively, wherein the HARQ feedback includes a first indication indicating reception of the first SPS reactivation DCI and a second indication indicating reception of the second SPS reactivation DCI.

Images