Block ACK for multiple SPS configurations

Abstract

Aspects of the present disclosure relate to wireless communications, and more particularly, to mechanisms for confirming SPS opportunities from multiple SPS configurations using block ACKs.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Application No. 17 / 201,567, filed on March 15, 2021, which claims the benefit of and priority to pending U.S. Provisional Patent Application No. 63 / 023,395, filed on May 12, 2020, the contents of both applications being incorporated herein in their entirety. Technical Field

[0003] Aspects of the present disclosure relate to wireless communications, and more particularly, to mechanisms for confirming SPS opportunities from multiple SPS configurations using block ACKs. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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.

[0005] In some examples, a wireless multiple access communication system may include multiple base stations, each of which supports communication of multiple communication devices (also referred to as user equipment (UE)) simultaneously. In a long term evolution (LTE) or advanced LTE (LTE-A) network, a set of one or more base stations may define an eNodeB (eNB). In other examples (e.g., in a next generation or 5G network), a wireless multiple access communication system may include multiple distributed units (DU) (e.g., edge units (EU), edge nodes (EN), radio heads (RH), smart radio heads (SRH), transmit receive points (TRP), etc.) communicating with multiple central units (CU) (e.g., central nodes (CN), access node controllers (ANC), etc.), wherein a set of one or more distributed units communicating with a central unit may define an access node (e.g., new radio base station (NR BS), new radio node B (NR NB), network node, 5GNB, gNB, gNodeB, etc.). A base station or DU may communicate with a set of UEs on a downlink channel (e.g., for transmission from a base station or to a UE) and an uplink channel (e.g., for transmission from a UE to a base station or distributed unit).

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, or even global level. An example of an emerging telecommunication standard is New Radio (NR), such as 5G radio access. NR is a collection of enhancements to the LTE mobile standard released by the Third Generation Partnership Project (3GPP). It is designed to better support mobile broadband Internet access by improving spectral efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards, using OFDMA with cyclic prefix (CP) on downlink (DL) and uplink (UL), and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0007] However, as the demand for mobile broadband access continues to grow, there is a need to further improve NR technology. Preferably, these improvements should be applicable to other multi-access technologies and the telecommunication standards that adopt these technologies. Summary of the invention

[0008] Aspects of the present disclosure relate to wireless communications, and more particularly, to mechanisms for semi-static or periodic opportunities for activating uplink or downlink communications.

[0009] Certain aspects of the present disclosure provide a method for wireless communication by a UE. The method generally includes receiving multiple semi-persistent scheduling (SPS) configurations, each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmissions to the UE, monitoring the SPS opportunities of the SPS configurations, and sending one or more block acknowledgments (BAs), each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0010] Certain aspects of the present disclosure provide a method for wireless communication by a network entity. The method generally includes: sending multiple semi-persistent scheduling (SPS) configurations to a user equipment (UE), each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE; sending a physical downlink shared channel (PDSCH) in at least some SPS opportunities of the SPS configuration; and monitoring one or more block acknowledgments (BAs) from the UE, each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0011] Certain aspects of the present disclosure provide a user equipment (UE). The UE generally includes a component for receiving multiple semi-persistent scheduling (SPS) configurations, each SPS configuration assigning a set of periodic opportunities for physical downlink shared channel (PDSCH) transmissions to the UE; a component for monitoring SPS opportunities of the SPS configurations; and a component for sending one or more block acknowledgements (BAs), each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgement window.

[0012] Certain aspects of the present disclosure provide a network entity. The network entity generally includes a component for sending a plurality of semi-persistent scheduling (SPS) configurations to a user equipment (UE), each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE; a component for sending a physical downlink shared channel (PDSCH) in at least some of the SPS opportunities of the SPS configuration; and a component for monitoring one or more block acknowledgements (BAs) from the UE, each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgement window

[0013] Certain aspects of the present disclosure provide a user equipment (UE). The UE generally includes: a receiver configured to receive multiple semi-persistent scheduling (SPS) configurations, each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE; a processing system configured to monitor the SPS opportunities of the SPS configurations; and a transmitter configured to send one or more block acknowledgments (BAs), each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0014] Certain aspects of the present disclosure provide a network entity. The network entity generally includes: a transmitter configured to send multiple semi-persistent scheduling (SPS) configurations to a user equipment (UE), each SPS configuration assigning a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE, and transmitting the physical downlink shared channel (PDSCH) in at least some SPS opportunities of the SPS configuration; and a processing system configured to monitor one or more block acknowledgments (BAs) from the UE, each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0015] Certain aspects of the present disclosure provide an apparatus for wireless communication by a user equipment (UE). The apparatus generally includes: an interface configured to receive multiple semi-persistent scheduling (SPS) configurations, each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE; and a processing system configured to monitor the SPS opportunities of the SPS configurations and generate one or more block acknowledgments (BAs), each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window, wherein the interface is also configured to output one or more BAs for transmission.

[0016] Certain aspects of the present disclosure provide an apparatus for wireless communication by a network entity. The apparatus generally includes: an interface configured to output multiple semi-persistent scheduling (SPS) configurations for transmission to a user equipment (UE), each SPS configuration assigning a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE, and outputting the physical downlink shared channel (PDSCH) for transmission in at least some SPS opportunities of the SPS configuration; and a processing system configured to monitor one or more block acknowledgments (BAs) from the UE, each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0017] Certain aspects of the present disclosure provide a computer-readable medium for wireless communication by a user equipment (UE). The computer-readable medium generally includes executable instructions to receive multiple semi-persistent scheduling (SPS) configurations, each SPS configuration assigning a set of periodic opportunities for physical downlink shared channel (PDSCH) transmissions to the UE, monitor the SPS opportunities of the SPS configurations, and send one or more block acknowledgments (BAs), each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0018] Certain aspects of the present disclosure provide a computer-readable medium for wireless communication by a network entity. The computer-readable medium generally includes instructions operable to send multiple semi-persistent scheduling (SPS) configurations to a user equipment (UE), each SPS configuration assigning a set of periodic opportunities for physical downlink shared channel (PDSCH) transmissions to the UE, sending the physical downlink shared channel (PDSCH) in at least some of the SPS opportunities of the SPS configuration, and monitoring one or more block acknowledgments (BAs) from the UE, each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0019] Aspects generally include methods, apparatus, systems, computer-readable media, and processing systems as substantially described herein with reference to and as illustrated by the accompanying drawings.

[0020] By reading the following description of the specific, exemplary embodiments of the present invention in conjunction with the accompanying drawings, other aspects, features and embodiments of the present invention will become apparent to those of ordinary skill in the art. Although features of the present invention may be discussed with respect to certain embodiments and accompanying drawings below, all embodiments of the present invention may include one or more advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, one or more such features may also be used according to the various embodiments of the present invention discussed herein. In a similar manner, although exemplary embodiments may be discussed below as device, system or method embodiments, it should be understood that such exemplary embodiments may be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 is a block diagram conceptually illustrating an example telecommunications system in accordance with certain aspects of the present disclosure.

[0022] Figure 2 is a block diagram illustrating an example logical architecture of a distributed RAN according to certain aspects of the present disclosure.

[0023] Figure 3 is a diagram illustrating an example physical architecture of a distributed RAN in accordance with certain aspects of the present disclosure.

[0024] Figure 4 is a block diagram conceptually illustrating designs of an example BS and UE in accordance with certain aspects of the present disclosure.

[0025] Figure 5 is a diagram illustrating an example for implementing a communication protocol stack in accordance with certain aspects of the present disclosure.

[0026] Figure 6 An example of a frame format of a New Radio (NR) system is shown.

[0027] Fig. 7A An example of a semi-persistent scheduling (SPS) PDSCH opportunity is shown, which may be used to activate a configured grant (CG) opportunity.

[0028] Figure 7B Example resources for providing SPS confirmation feedback are shown.

[0029] Figure 8 Example operations that may be performed by a user equipment (UE) in accordance with aspects of the present disclosure are illustrated.

[0030] Fig. 9 Example operations that may be performed by a network entity in accordance with aspects of the present disclosure are shown.

[0031] Fig.10 is an overview of different types of block acknowledgements (BAs) for multiple SPS configurations in accordance with certain aspects of the present disclosure.

[0032] Fig.11A An example of a separate BA per SPS configuration according to aspects of the present disclosure is shown.

[0033] Fig. 11B An example of a shared BA for multiple SPS configurations according to aspects of the present disclosure is shown.

[0034] Fig. 12A An example of a shared BA for multiple SPS configurations according to aspects of the present disclosure is shown.

[0035] Fig. 12B and Fig. 12C Example HARQ feedback payloads are shown in accordance with aspects of the present disclosure.

[0036] Fig.13A An example of a shared BA for multiple SPS configurations according to aspects of the present disclosure is shown.

[0037] Fig. 13B and Fig. 13C An exemplary HARQ feedback payload is shown in accordance with aspects of the present disclosure.

[0038] Fig.14A and Fig. 14B An exemplary HARQ feedback payload is shown in accordance with aspects of the present disclosure.

[0039] Fig.15 A communications device is shown that may include various components configured to perform operations of the techniques disclosed herein in accordance with aspects of the present disclosure.

[0040] Fig.16 A communications device is shown that may include various components configured to perform operations of the techniques disclosed herein in accordance with aspects of the present disclosure.

[0041] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized on other aspects without specific recitation. DETAILED DESCRIPTION

[0042] Aspects of the present disclosure relate to wireless communications, and more particularly, to mechanisms for confirming SPS opportunities from multiple SPS configurations using block ACKs.

[0043] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for New Radio (NR) (new radio access technology or 5G technology).

[0044] NR can support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., over 80MHz), millimeter wave (mmW) targeting high carrier frequency (e.g., 60GHz), massive MTC (mMTC) targeting non-backward compatible MTC technology, and / or mission critical services targeting ultra-reliable low latency communication (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTIs) to meet their respective quality of service (QoS) requirements. In addition, these services can coexist in the same subframe.

[0045] Due to the availability of large amounts of bandwidth, certain multi-beam wireless systems, such as mmW systems, have brought gigabit speeds to cellular networks. However, mmWave systems face unique challenges with severe path loss, requiring new technologies such as hybrid beamforming (analog and digital) that did not exist in 3G and 4G systems. Hybrid beamforming can enhance the link budget / signal-to-noise ratio (SNR) that can be utilized during the RACH.

[0046] In such a system, a Node B (NB) and a user equipment (UE) may communicate using beamformed transmissions. In order for the beamforming to work correctly, the NB may need to monitor the beam using beam measurements performed (e.g., based on a reference signal sent by the NB) and feedback generated at the UE. However, since the UE does not know the direction of the reference signal, the UE may need to evaluate several beams to obtain the best Rx beam for a given NB Tx beam. Therefore, if the UE must "scan" all of its Rx beams to perform measurements (e.g., determine the best Rx beam for a given NB Tx beam), the UE may incur significant delays in the measurements and battery life impact. In addition, having to scan all Rx beams is very resource inefficient. Therefore, aspects of the present disclosure provide techniques to assist UEs when using Rx beamforming to perform measurements of serving cells and neighboring cells.

[0047] The following description provides examples and does not limit the scope, applicability or examples set forth in the claims. Without departing from the scope of the present disclosure, the functions and arrangements of the elements discussed may be changed. Various examples may appropriately omit, replace or add various processes or components. For example, the described method may be performed in a different order than described, and various steps may be added, omitted or combined. In addition, the features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method that is practiced using other structures, functions or structures and functions in addition to or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims. The term "exemplary" used herein means "used as an example, instance or illustration". Any aspect described herein as "exemplary" is not necessarily to be interpreted as being more preferred or more advantageous than other aspects.

[0048] The technology described herein can be used in various wireless communication networks, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network can implement wireless technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes wideband code division multiple access (WCDMA) and other variants of code division multiple access. cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS). NR is an emerging wireless communication technology developed in conjunction with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and Advanced LTE (LTE-A) are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the "3rd Generation Partnership Project" (3GPP). cdma2000 and UMB are described in documents from an organization called the "3rd Generation Partnership Project 2" (3GPP 2). The techniques described herein can be used for the above-mentioned wireless networks and radio technologies as well as other wireless networks and radio technologies. For clarity, although terms commonly associated with 3G and / or 4G wireless technologies may be used herein to describe various aspects, various aspects of the present disclosure may be applied to other communication systems (such as 5G and higher) based on generations including NR technology.

[0049] Example Wireless System

[0050] Figure 1 An example wireless network 100 is shown in which aspects of the present disclosure may be implemented. For example, one or more UEs 120 of the wireless network 100 may be configured to perform block acknowledgement (BA) Figure 8 Operation 800 of , to provide HARQ feedback for SPS opportunities of multiple SPS configurations. Similarly, the base station 110 of the wireless network 100 may be configured to perform Fig. 9 Operation 900 of receiving and processing such BA sent by UE 120 (performing Figure 8 Operation 800).

[0051] like Figure 1As shown, wireless network 100 may include multiple base stations 110 and other network entities. According to one example, network entities including BSs and UEs may communicate at high frequencies (eg, >6 GHz) using beamforming.

[0052] A BS may be a station that communicates with a UE. Each BS 110 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a Node B and / or a Node B subsystem serving the coverage area, depending on the context in which the term is used. In NR systems, the terms "cell" and gNB, Node B, 5G NB, AP, NR BS, NR BS, or TRP may be interchangeable. In some examples, a cell is not necessarily stationary, and the geographic area of ​​a cell may move depending on the location of a mobile base station. In some examples, base stations may be interconnected to each other and / or to one or more other base stations or network nodes (not shown) in a wireless network 100 using any suitable transport network, through various types of backhaul interfaces, such as direct physical connections, virtual networks, and the like.

[0053] Typically, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific radio access technology (RAT) and can operate on one or more frequencies. RAT may also be referred to as radio technology, air interface, etc. Frequency may also be referred to as carrier, channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0054] A BS may provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access to UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). The BS of a macro cell may be referred to as a macro BS. The BS of a pico cell may be referred to as a pico BS. The BS of a femto cell may be referred to as a femto BS or a home BS. In Figure 1In the example shown, base stations 110a, 110b, and 110c may be macro base stations for macro cells 102a, 102b, and 102c, respectively. BS 110x may be a pico BS for pico cell 102x. BSs 110y and 110z may be femto BSs for femto cells 102y and 102z, respectively. A BS may support one or more (e.g., three) cells.

[0055] The wireless network 100 may also include a relay station. A relay station is a station that receives transmissions of data and / or other information from an upstream station (e.g., a BS or a UE) and sends transmissions of data and / or other information to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that relays transmissions for other UEs. Figure 1 In the example shown, a relay station 110r may communicate with a BS 110a and a UE 120r to facilitate communication between the BS 110a and the UE 120r. A relay station may also be referred to as a relay BS, a relay station, or the like.

[0056] The wireless network 100 may be a heterogeneous network including different types of BSs, such as macro BSs, pico BSs, femto BSs, relay stations, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 20 watts), while a pico BS, a femto BS, and a relay station may have a lower transmit power level (e.g., 1 watt).

[0057] Wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the base stations may have different frame timing, and transmissions from different BSs may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operation.

[0058] A network controller 130 may be coupled to a set of BSs and provide coordination and control for these BSs. The network controller 130 may communicate with the BSs 110 via a backhaul. The BSs 110 may also communicate with each other, directly or indirectly, for example, via a wireless or wired backhaul.

[0059] UE 120 (e.g., 120x, 120y, etc.) may be dispersed throughout the wireless network 100, and each UE may be fixed or mobile. UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premises equipment (CPE), cellular phone, smart phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, medical device or medical equipment, biosensor / device, such as smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.) wearable device), entertainment device (e.g., music device, video device, satellite radio, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, global positioning system device, or any other suitable device configured to communicate via wireless or wired medium. Some UEs may be considered as evolved or machine type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc. that can communicate with a BS, another device (e.g., a remote device), or some other entity. For example, a wireless node can provide connectivity to a network (e.g., a wide area network such as the Internet or a cellular network) or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs can be considered Internet of Things (IoT) devices.

[0060] exist Figure 1 In FIG. 1 , a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and / or uplink. A dashed line with double arrows represents interfering transmissions between a UE and a BS.

[0061] Some wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as frequency tones, frequency bins, etc. Each subcarrier can be modulated with data. Typically, modulation symbols are sent in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15kHz, and the minimum resource allocation (called a "resource block") can be 12 subcarriers (or 180kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal FFT size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband may cover 1.08 MHz (ie, 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0062] Although aspects of the examples described herein may be associated with LTE technology, aspects of the present disclosure may be applicable to other wireless communication systems, such as NR.

[0063] NR can utilize OFDM with CP on both the uplink and downlink, and includes support for half-duplex operation using TDD. A single component carrier bandwidth of 100MHz can be supported. NR resource blocks can span 12 subcarriers, with a subcarrier bandwidth of 75kHz and a duration of 0.1ms. In one aspect, each radio frame can consist of 50 subframes with a length of 10ms. Therefore, each subframe can have a length of 0.2ms. In another aspect, each radio frame can consist of 10 subframes with a length of 10ms, where each subframe can have a length of 1ms. Each subframe can indicate the link direction (i.e., DL or UL) used for data transmission, and the link direction of each subframe can be switched dynamically. Each subframe can include DL / UL data and DL / UL control data. Beamforming can be supported, and the beam direction can be dynamically configured. MIMO transmission with precoding can also be supported. The MIMO configuration in DL can support up to 8 transmit antennas, up to 8 streams per UE, and multi-layer DL transmission with up to 2 streams. Multi-layer transmission of up to 2 streams per UE can be supported. Up to 8 serving cells can support multi-cell aggregation. Optionally, NR can support different air interfaces instead of OFDM-based. NR networks can include entities such as CU and / or DU.

[0064] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., a base station) allocates resources for communications between some or all devices and equipment within its service area or cell. In the present disclosure, as further discussed below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, subordinate entities utilize resources allocated by the scheduling entity. The base station is not the only entity that can serve as a scheduling entity. That is, in some examples, a UE may act as a scheduling entity to schedule resources for one or more subordinate entities (subordinate) (e.g., one or more other UEs). In this example, a UE is used as a scheduling entity, and other UEs utilize the resources scheduled by the UE for wireless communications. A UE may act as a scheduling entity in a peer-to-peer (P2P) network and / or a mesh network. In a mesh network example, in addition to communicating with a scheduling entity, UEs may also optionally communicate directly with each other.

[0065] Therefore, in a wireless communication network having scheduled access to time-frequency resources and having a cellular configuration, a P2P configuration, and a mesh configuration, a scheduling entity and one or more subordinate entities may communicate using the scheduled resources.

[0066] As described above, the RAN may include a CU and a DU. A NR BS (e.g., a gNB, a 5G Node B, a Node B, a Transmit Receiving Point (TRP), an Access Point (AP)) may correspond to one or more BSs. An NR cell may be configured as an access cell (ACell) or a data-only cell (DCell). For example, a RAN (e.g., a central unit or a distributed unit) may configure a cell. A DCell may be a cell for carrier aggregation or dual connectivity, but not for initial access, cell selection / reselection, or switching. In some cases, a DCell may not send a synchronization signal – in some cases, a DCell may send an SS. The NR BS may send a downlink signal indicating the cell type to the UE. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine the NR BS based on the indicated cell type to consider cell selection, access, switching, and / or measurement.

[0067] Figure 2 An example logical architecture of a distributed radio access network (RAN) 200 is shown, which may be Figure 1The wireless communication system shown is implemented. The 5G access node 206 may include an access node controller (ANC) 202. The ANC may be a central unit (CU) of the distributed RAN 200. The backhaul interface to the next generation core network (NG-CN) 204 may terminate at the ANC. The backhaul interface to the adjacent next generation access node (NG AN) may terminate at the ANC. The ANC may include one or more TRPs 208 (also referred to as BS, NR BS, Node B, 5G NB, AP, or some other terminology). As described above, TRP may be used interchangeably with "cell".

[0068] The TRP 208 may be a DU. The TRP may be connected to one ANC (ANC 202) or more than one ANC (not shown). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific AND deployments, the TRP may be connected to more than one ANC. The TRP may include one or more antenna ports. The TRP may be configured to provide services to the UE individually (e.g., dynamically selected) or jointly (e.g., joint transmission).

[0069] The local architecture 200 can be used to illustrate a fronthaul definition. The architecture can be defined to support fronthaul technology solutions across different deployment types. For example, the architecture can be based on the sending network capabilities (e.g., bandwidth, latency, and / or jitter).

[0070] The architecture may share features and / or components with LTE. According to various aspects, the next generation AN (NG-AN) 210 may support dual connectivity with NR. The NG-AN may share common fronthaul for LTE and NR.

[0071] The architecture may enable cooperation between and among TRPs 208. For example, cooperation may be provisioned within and / or across TRPs via ANC 202. According to various aspects, an inter-TRP interface may not be required / present.

[0072] According to various aspects, dynamic configuration of separate logic functions may exist in architecture 200. As will be seen in reference Figure 5 In more detail, the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, the medium access control (MAC) layer, and the physical (PHY) layer can be adaptively placed at the DU or CU (e.g., TRP or ANC, respectively). According to certain aspects, the BS may include a central unit (CU) (e.g., ANC 202) and / or one or more distributed units (e.g., one or more TRPs 208).

[0073] Figure 3An example physical architecture of a distributed RAN 300 according to aspects of the present disclosure is shown. A centralized core network unit (C-CU) 302 may host core network functions. The C-CU may be centrally deployed. C-CU functions may be offloaded (e.g., to Advanced Wireless Services (AWS)) to handle peak capacity.

[0074] A centralized RAN unit (C-RU) 304 may host one or more ANC functions. Optionally, the C-RU may host core network functions locally. The C-RU may have a distributed deployment. The C-RU may be closer to the network edge.

[0075] DU 306 may host one or more TRPs (edge ​​node (EN), edge unit (EU), radio head (RH), smart radio head (SRH), etc.) DU may be located at the edge of the network with radio frequency (RF) capabilities.

[0076] Figure 4 Shows Figure 1 Example components of a BS 110 and a UE 120 are shown, which may be used to implement aspects of the present disclosure. The base station may include a TRP or a gNB.

[0077] For example, one or more of the antenna 452, DEMOD / MOD 454, processors 466, 458, 464, and / or controller / processor 480 of the UE 120 may be configured to perform the operations described herein (e.g., Figure 8 Similarly, one or more of 434, DEMOD / MOD 432, processors 430, 420, 438, and / or controller / processor 440 of BS 110 may be configured to perform the operations described herein (e.g., Fig. 9 Operation 900).

[0078] For a restricted association scenario, the base station 110 may be Figure 1 1. The macro BS 110c in FIG. 1 may be the macro BS 110c, and the UE 120 may be the UE 120y. The base station 110 may also be some other type of base station. The base station 110 may be equipped with antennas 434a to 434t, and the UE 120 may be equipped with antennas 452a to 452r.

[0079] At the base station 110, the transmit processor 420 may receive data from the data source 412 and control information from the controller / processor 440. The control information may be used for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), etc. The data may be used for a physical downlink shared channel (PDSCH), etc. The processor 420 may process (e.g., encode and symbol map) the data and the control information to obtain data symbols and control symbols, respectively. The processor 420 may also generate reference symbols, such as for PSS, SSS, and a cell-specific reference signal (CRS). The transmit (TX) multiple-input multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols (if applicable), and may provide output symbol streams to modulators (MOD) 432a to 432t. Each modulator 432 may process a respective output symbol stream (e.g., OFDM, etc.) to obtain an output sample stream. Each modulator 432 may further process (eg, convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 432a through 432t may be transmitted via antennas 434a through 434t, respectively.

[0080] At the UE 120, antennas 452a to 452r may receive downlink signals from the base station 110 and may provide received signals to demodulators (DEMODs) 454a to 454r, respectively. Each demodulator 454 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 454 may further process the input samples (e.g., OFDM, etc.) to obtain received symbols. A MIMO detector 456 may obtain received symbols from all demodulators 454a to 454r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 458 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 460, and provide decoded control information to a controller / processor 480.

[0081] On the uplink, at the UE 120, a transmit processor 464 may receive and process data from a data source 462 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 480 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 464 may also generate reference symbols for a reference signal. The symbols from the transmit processor 464 may be precoded by a TX MIMO processor 466 (if applicable), further processed by demodulators 454a through 454r (e.g., for SC-FDM, etc.), and transmitted to the base station 110. At the BS 110, the uplink signals from the UE 120 may be received by the antenna 434, processed by the modulator 432, detected by the MIMO detector 436 (if applicable), and further processed by the receive processor 438 to obtain decoded data and control information transmitted by the UE 120. The receive processor 438 may provide decoded data to a data sink 439 and may provide decoded control information to a controller / processor 440 .

[0082] Controllers / processors 440 and 480 may direct the operation at base station 110 and UE 120, respectively. Scheduler 444 may schedule UEs for data transmission on the downlink and / or uplink. Processor 480 and / or other processors and modules at UE 120 may perform or direct, for example, Figure 8 The execution of the functional blocks shown in the figure and / or other processes for the techniques described herein and the techniques shown in the figures. The processor 440 and / or other processors and modules at the BS 110 may execute or direct the reference Fig. 9 The processes of the described techniques and / or other processes of the techniques described herein and those processes shown in the figures. Memories 442 and 482 may store data and program codes for BS 110 and UE 120, respectively.

[0083] Figure 5 A diagram 500 is shown showing an example of implementing a communication protocol stack according to various aspects of the present disclosure. The communication protocol stack shown can be implemented by a device running in a 5G system. Diagram 500 shows a communication protocol stack, including a radio resource control (RRC) layer 510, a packet data convergence protocol (PDCP) layer 515, a radio link control (RLC) layer 520, a media access control (MAC) layer 525, and a physical (PHY) layer 530. In various examples, the layers of the protocol stack can be implemented as independent modules of software, parts of a processor or ASIC, parts of non-co-located devices connected by a communication link, or various combinations thereof. For example, co-location and non-co-location implementations can be used in the protocol stack of a network access device (e.g., AN, CU, and / or DU) or a UE.

[0084] The first option 505-a illustrates a separate implementation of the protocol stack, where the implementation of the protocol stack is performed on a centralized network access device (e.g., Figure 2 ANC 202 in ) and distributed network access equipment (e.g., Figure 2 In the first option 505-a, the RRC layer 510 and the PDCP layer 515 can be implemented by the central unit, while the RLC layer 520, the MAC layer 525 and the PHY layer 530 can be implemented by the DU. In various examples, the CU and the DU can be co-located or non-co-located. The first option 505-a may be useful in macro cell, micro cell or pico cell deployment.

[0085] The second option 505-b shows a unified implementation of the protocol stack, where the protocol stack is implemented in a single network access device (e.g., access node (AN), new radio base station (NR BS), new radio node B (NR NB), network node (NN), etc.). In the second option, the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530 can each be implemented by the AN. The second option 505-b may be useful in a femtocell deployment.

[0086] Regardless of whether the network access device implements part or all of the protocol stack, the UE may implement the entire protocol stack (eg, the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530).

[0087] Figure 6 600 is a diagram showing an example of a frame format 600 for NR. The transmission timeline of each of the downlink and uplink may be divided into radio frame units. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be divided into 10 subframes, each 1 ms, indexed from 0 to 9. Depending on the subcarrier spacing, each subframe may include a variable number of slots. Depending on the subcarrier spacing, each slot may include a variable number of symbol periods (e.g., 7 or 14 symbols). The symbol periods in each slot may be assigned an index. A microslot, which may be referred to as a subslot structure, refers to a transmission time interval having a duration less than one slot (e.g., 2, 3, or 4 symbols).

[0088] Each symbol in a slot may indicate the link direction (e.g., DL, UL, or flexible) of data transmission, and the link direction of each subframe may be switched dynamically. The link direction may be based on the slot format. Each slot may include DL / UL data and DL / UL control information.

[0089] In NR, a synchronization signal (SS) block is transmitted. The SS block includes PSS, SSS, and dual-symbol PBCH. The SS block can be transmitted at a fixed time slot position, such as Figure 6 Symbols 0-3 shown. The UE can use PSS and SSS for cell search and acquisition. PSS can provide half-frame timing, and SS can provide CP length and frame timing. PSS and SSS can provide cell identity. PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frames, SS burst set periodicity, system frame number, etc. SS blocks can be organized into SS bursts to support beam scanning. Further system information such as remaining minimum system information (RMSI), system information block (SIB), other system information (OSI) can be sent on the physical downlink shared channel (PDSCH) in certain subframes.

[0090] The UE may operate in various radio resource configurations, including a configuration associated with sending a pilot using a dedicated resource set (e.g., a radio resource control (RRC) dedicated state, etc.) or a configuration associated with sending a pilot using a common resource set (e.g., an RRC common state, etc.). When operating in the RRC dedicated state, the UE may select a dedicated resource set for sending a pilot signal to the network. When operating in the RRC common state, the UE may select a common resource set for sending a pilot signal to the network. In either case, the pilot signal sent by the UE may be received by one or more network access devices (such as an AN or DU or a portion thereof). Each receiving network access device may be configured to receive and measure a pilot signal sent on a common resource set, and also receive and measure a pilot signal sent on a dedicated resource set allocated to the UE, for which the network access device is a member of the monitoring set of the network access device of the UE. One or more receiving network access devices or a CU to which a pilot signal measurement value is sent by a receiving (multiple) network access device may use the measurement to identify a serving cell of the UE, or initiate a change in a serving cell of one or more UEs.

[0091] Block ACK example for multiple SPS configurations

[0092] Aspects of the present disclosure relate to wireless communications, and more particularly, to mechanisms for confirming SPS opportunities from multiple SPS configurations using block ACKs.

[0093] SPS resource allocation is sometimes referred to as configured downlink allocation, which refers to a scheduling technique in which the user equipment (UE) is pre-configured with periodicity and offset by the network / base station (e.g., eNB, gNB, etc.).

[0094] like Fig. 7AAs shown, once preconfigured, if the UE is to receive an allocation of downlink resources, the allocation of SPS opportunities will be repeated according to the preconfigured periodicity, resulting in periodic SPS opportunities. For SPS, the base station can use radio resource control (RRC) signaling to define the periodicity of the configured downlink allocation. Similarly, once the CG opportunity is configured, the allocation of the CG opportunity can be repeated according to the preconfigured periodicity.

[0095] As used herein, the term opportunity generally refers to a time at which resources are allocated for a transmission that may or may not ultimately occur. For example, a downlink transmission may or may not occur during an SPS opportunity. Similarly, an uplink transmission may or may not occur during a CG opportunity. If a transmission may occur, the opportunity may be considered activated, and therefore, these opportunities should be monitored.

[0096] In the current system, CG is semi-statically activated through radio resource control (RRC) or downlink control information (DCI) signaling. In some cases, the UL data packet in the CG opportunity can be triggered by the decoded DL data packet in the SPS opportunity (for example, reporting the action status in response to new input / command from DL). However, this type of activation mechanism may lead to resource waste.

[0097] In some cases, the UE may provide an acknowledgment (e.g., hybrid automatic repeat request or HARQ) feedback indicating whether it received a PDSCH transmission in one or more configured SPS opportunities. In some systems (e.g., in Release 15) N1-PUCCH-AN may be used to specify pre-configured PUCCH resources for SPS HARQ feedback. For example, Figure 7B As shown, PUCCH resources using PUCCH format 0 or 1 can support up to 2 bits of feedback.

[0098] In some systems (e.g., in Release 16 systems), multiple SPS configurations are allowed. The gNB may perform separate configuration (e.g., monitoring of SPS transmission and feedback) for each SPS configuration.

[0099] However, in this case, a potential challenge is how or whether to share the HARQ process pool among multiple SPS configurations. If the HARQ process pool is shared, the HARQ process ID offset can be used to avoid overlapping HARQ processes among SPS configurations, as shown below:

[0100] HARQ process ID=[floor(CURRENT_slot / periodicity)]modulo nrofHARQ-Processes+harq-procID-offset;

[0101] Wherein, CURRENT_slot = [(SFN × numberOfSlotsPerFrame) + number of slots in a frame], and numberOfSlotsPerFrame refers to the number of consecutive slots per frame (e.g., TS 38.211[8]

[0102] regulated in ).

[0103] As described above, when the UE receives the SPS PDSCH, ACK / NACK feedback is sent back to the gNB using the assigned PUCCH resources. If each SPS transmission is ACKed / NACKed individually, unnecessary overhead is incurred in terms of resources. When the UE is configured with multiple SPS configurations, the overhead is even more significant since the PUCCH resources are configured individually.

[0104] Providing HARQ feedback for multiple SPS configurations may also have an impact on UE power consumption. For example, periodic transmission of PUCCH (for SPS HARQ) comes with a power consumption cost at the UE. When the gNB does not send PDSCH at SPS occasions (e.g., when no data is available), the HARQ ACK mechanism per SPS occasion may cause unnecessary interference or unnecessary waste of radio resources.

[0105] However, aspects of the present disclosure propose existing mechanisms that may help reduce overhead due to ACK / NACK feedback when multiple SPS configurations are activated for a UE.

[0106] Figure 8 Example operations 800 are shown for wireless communications by a UE. Operations 800 may be performed, for example, by a UE 120 (eg, UE 120) engaging in communications with a base station that configures the UE with multiple SPS configurations.

[0107] Operations 800 begin, at 802, by receiving a plurality of semi-persistent scheduling (SPS) configurations, each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmissions to a UE.

[0108] At 804, the UE monitors SPS opportunities of the SPS configuration. At 806, the UE sends one or more block acknowledgements (BAs), each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of the one or more SPS configurations occurring within an acknowledgement window.

[0109] Fig. 9 Example operations 900 are shown that may be performed by a network entity and may be considered to be Figure 8For example, operation 900 may be performed by the gNB to configure the UE with multiple SPS configurations (e.g., perform Figure 8 UE of operation 800), and monitors HARQ feedback sent via a separate or shared BA.

[0110] Operations 900 begin, at 902, by sending a plurality of semi-persistent scheduling (SPS) configurations to a user equipment (UE), each SPS configuration allocating to the UE a set of periodic opportunities for physical downlink shared channel (PDSCH) transmissions.

[0111] At 904, the network entity transmits a physical downlink shared channel (PDSCH) in at least some SPS opportunities of the SPS configuration. At 906, the network entity monitors one or more block acknowledgements (BAs) from the UE, each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgement window.

[0112] Fig.10 is an overview of different types of block acknowledgements (BAs) for multiple SPS configurations according to certain aspects of the present disclosure. As shown, proposals include using separate BAs for multiple SPS configurations, or sharing BAs among multiple SPS configurations.

[0113] As will be described in more detail below, the shared BA can be used to provide positive feedback (ACK, indicating that PDSCH is received in an SPS opportunity) and negative feedback (NAK, indicating that PDSCH is not received in an SPS opportunity), or only NAK is used (meaning that if PDSCH is received in an SPS opportunity, no feedback is sent). If ACK and NAK are sent as feedback, the feedback payload can be variable or fixed. If only NAK feedback is sent, the feedback payload can also be variable.

[0114] Fig.11A Examples of separate BAs per SPS configuration according to various aspects of the present disclosure are shown. Fig.11A The top timeline in shows the traditional scenario of providing ACK feedback for each SPS opportunity, which results in considerable overhead. In contrast, the bottom timeline shows how the UE can efficiently acknowledge the aggregate opportunities of the SPS within the ACK window using a single BA for each SPS configuration.

[0115] Fig. 11B An example of a (single) BA shared across multiple SPS configurations according to aspects of the present disclosure is shown. Fig.11A Same, Fig.11AThe top timeline in FIG shows a conventional scenario of providing ACK feedback for each SPS opportunity, which results in considerable overhead. In contrast, the bottom timeline shows how the UE can efficiently acknowledge a set of SPS opportunities within the ACK window using a single BA for both SPS configurations. As shown, using a shared BA for multiple SPS configurations may be more resource and power efficient than the conventional or separate BA cases.

[0116] Fig. 12A Another example of a shared BA for multiple SPS configurations according to aspects of the present disclosure is shown. This example again assumes two SPS configurations (#1 and #2).

[0117] As shown, when multiple SPS configurations share the same block ACK, the number of opportunities for each SPS configuration can vary based on the SPS periodicity. In the example shown, due to different SPS periods, SPS configuration #1 has 4 SPS opportunities in the first and second ACK windows, while SPS configuration #2 has only 2 SPS opportunities in the first ACK window and 1 opportunity in the second ACK window.

[0118] like Fig. 12B and Fig. 12C As shown, in some cases, the HARQ feedback payload may be variable (different in the first and second ACK windows). In this case, variable feedback may be effective because only the opportunities received within the window are acknowledged.

[0119] In some cases, ACK resources may be assigned for a maximum number of opportunities per window. Fig. 12B and 12C The example shown in , assumes a maximum of 6 opportunities per window, such as Fig. 12A As shown in (Configuration #1 in ACK window 1 is 4 and Configuration #2 is 2). Fig. 12B As shown, all resources are available for the first ACK window (which has the largest number of SPS occurrences).

[0120] However, if Fig. 12C As shown, since the second ACK window has only 5 SPS opportunities, not all ACK resources are used. In some cases, unused resources can be left idle. However, in other cases, unused resources can be used to improve the link efficiency of HARQ feedback (e.g., by adjusting MCS).

[0121] In some cases, the ordering of ACK / NAK feedback in a shared BA may be based on the SPS configuration number. Fig. 12B and Fig. 12CIn the example shown, HARQ for SPS configuration #1 occurs first, followed by HARQ for SPS configuration #2. Alternatively, the ordering of ACK / NACK feedback may be based on how the SPS opportunities occur in time.

[0122] Fig.13A Another example of a shared BA for multiple SPS configurations according to aspects of the present disclosure is shown. This example again assumes two SPS configurations (#1 and #2). Again, due to different SPS periods, SPS configuration #1 has 4 SPS opportunities in the first and second ACK windows, while SPS configuration #2 has only 2 SPS opportunities in the first ACK window and 1 opportunity in the second ACK window.

[0123] However, in this example, the HARQ feedback (ACK / NAK feedback) may have a fixed payload. In this case, the gNB may assign resources for the maximum number of opportunities for all SPS configurations that may fall within the ACK window. For this example, Fig. 13B and Fig. 13C As shown in , this results in resources for 6 ACK / NAKs. Fig. 13C As shown, if the SPS opportunity does not appear in the window, the UE may send a NAK. It can be noted that in this case, the UE may only need to send an ACK / NAK in the payload, without sending an SPS configuration ID and / or a HARQ process ID.

[0124] Fig.14A and Fig. 14B shows an example of a variable size payload with only NAKs, assuming the same Fig.13A The example SPS configurations shown are the same. In this case, only NAK is utilized and since the gNB network may not know which SPS configuration and HARQ process ID is NAKed, the UE may need to include some identification information in the UCI with NAK feedback.

[0125] The specific information may depend on whether the HARQ process pool is shared. If overlapping HARQ process IDs are allowed in the SPS configuration, the HARQ process pool is considered shared. If the HARQ process pool is not shared, the UE may include the HARQ process ID and the SPS configuration # in the payload carrying the NAK feedback for that HARQ process ID. If the HARQ process pool is shared (overlapping HARQ process IDs are not allowed in the SPS configuration), it may be sufficient for the UE to include only the HARQ process ID in the payload.

[0126] This addition of identification information may result in increased gNB complexity due to blind decoding of variable payload sizes on PUCCH. In some cases, the payload size can be quantized (e.g., to 1, 4, 8 feedbacks) to reduce gNB decoding complexity. In some cases, a unique ID within the ACK window can also be used when only NAKs are sent in the block ACK.

[0127] There are various options for configuring the BA mechanism described here. For example, the gNB may configure the UE, or the UE may request one or more of the following features:

[0128] Shared pair of individual block ACKs;

[0129] Shared HARQ process ID pool;

[0130] A Block ACK carrying only NAK or both ACK / NAK; or

[0131] Variable versus fixed payload HARQ feedback.

[0132] In some cases, the gNB may send these configurations along with the SPS configuration via RRC signaling. In this case, the activation / deactivation of the feature may be via RRC signaling, MAC or PHY signaling.

[0133] In some cases, for fixed PUCCH allocation, SPS configuration may be utilized to assign and configure PUCCH resource reservation for block ACK. This may be suitable, for example, for scenarios with fixed payload HARQ feedback.

[0134] In some cases, to allow more efficient resource reservation, the network may dynamically assign PUCCH resources (e.g., before each ACK window). This may be useful, for example, for scenarios with variable payload HARQ feedback (e.g., for Fig.14A and Fig. 14B The case shown) is more appropriate because the number of NAKs may vary due to conditions such as interference, channel conditions, etc.

[0135] Fig.15 1500, which may include various components (eg, corresponding to means-plus-function components) configured to perform operations of the techniques disclosed herein, such as Figure 8 The communication device 1500 includes a processing system 1502 coupled to a transceiver 1508. The transceiver 1108 is configured to transmit and receive signals, such as the various signals described herein, for the communication device 1500 via an antenna 1510. The processing system 1502 may be configured to perform processing functions for the communication device 1500, including processing signals received and / or transmitted by the communication device 1500.

[0136] The processing system 1502 includes a processor 1504 coupled to a computer readable medium / memory 1512 via a bus 1506. In some aspects, the computer readable medium / memory 1512 is configured to store instructions (e.g., computer executable code) that, when executed by the processor 1504, cause the processor 1504 to perform Figure 8 , or other operations for performing various techniques discussed herein. In some aspects, the computer-readable medium / memory 1512 stores code 1514 for receiving multiple semi-persistent scheduling (SPS) configurations, each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE; code 1516 for monitoring the SPS opportunities of the SPS configurations; and code 1518 for sending one or more block acknowledgments (BAs), each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window. In some aspects, the processor 1504 has circuits configured to implement the code stored in the computer-readable medium / memory 1512. Processor 1504 includes circuit 1520 for receiving multiple semi-persistent scheduling (SPS) configurations, each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to a UE; circuit 1522 for monitoring the SPS opportunities of the SPS configurations; and circuit 1524 for sending one or more block acknowledgments (BAs), each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0137] Fig.16 1600, which may include various components (eg, corresponding to means-plus-function components) configured to perform operations of the techniques disclosed herein, such as Fig. 9 The communication device 1600 includes a processing system 1602 coupled to a transceiver 1608. The transceiver 1608 is configured to transmit and receive signals, such as the various signals described herein, for the communication device 1600 via an antenna 1610. The processing system 1602 may be configured to perform processing functions for the communication device 1600, including processing signals received and / or transmitted by the communication device 1600.

[0138] The processing system 1602 includes a processor 1604 coupled to a computer readable medium / memory 1612 via a bus 1606. In some aspects, the computer readable medium / memory 1612 is configured to store instructions (e.g., computer executable code) that, when executed by the processor 1604, cause the processor 1604 to perform Fig. 9 , or other operations for performing various techniques discussed herein. In some aspects, the computer-readable medium / memory 1612 stores code 1614 for sending multiple semi-persistent scheduling (SPS) configurations to a user equipment (UE), each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE; code 1616 for sending a physical downlink shared channel (PDSCH) in at least some of the SPS opportunities of the SPS configuration; and code 1618 for monitoring one or more block acknowledgments (BAs) from the UE, each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window. In some aspects, the processor 1204 has circuits configured to implement the code stored in the computer-readable medium / memory 1612. Processor 1604 includes circuit 1620 for sending multiple semi-persistent scheduling (SPS) configurations to a user equipment (UE), each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE; circuit 1622 for sending the physical downlink shared channel (PDSCH) in at least some of the SPS opportunities of the SPS configuration; and circuit 1624 for monitoring one or more block acknowledgments (BAs) from the UE, each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0139] In addition to the above aspects, specific combinations of aspects are also within the scope of the present disclosure, some of which are detailed below:

[0140] Aspect 1: A method for wireless communication by a user equipment (UE), comprising: receiving multiple semi-persistent scheduling (SPS) configurations, each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE; monitoring the SPS opportunities of the SPS configurations; and sending one or more block acknowledgments (BAs), each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0141] Aspect 2: The method according to aspect 1, wherein sending one or more BAs comprises: sending a separate BA for each SPS configuration, each BA providing HARQ feedback for multiple SPS opportunities of the corresponding SPS configuration.

[0142] Aspect 3: The method according to any one of aspects 1-2, wherein sending one or more BAs includes: sending at least one shared BA, the at least one shared BA providing HARQ feedback for SPS opportunities of multiple SPS configurations.

[0143] Aspect 4: The method according to aspect 3, wherein the number of SPS opportunities confirmed by the shared BA for each of the SPS configurations varies based at least on the number of SPS opportunities for each of the SPS configurations with the confirmation window.

[0144] Aspect 5: A method according to aspect 4, wherein the order of confirmation feedback within a BA is based on at least one of: an SPS configuration number of an SPS configuration sharing the shared BA; or an order in which the confirmed SPS opportunities in the shared BA appear within a confirmation window.

[0145] Aspect 6: A method according to Aspect 4, wherein: resources for a shared BA are allocated based on a maximum number of SPS opportunities occurring in a confirmation window; and unused resources allocated to the shared BA are used to improve the link efficiency of HARQ feedback provided in the shared BA.

[0146] Aspect 7: A method according to any one of aspects 3-4, wherein: the shared BA is used only to provide negative acknowledgement (NAK); and the UE uses the shared BA to provide information identifying which SPS opportunities are being negatively acknowledged.

[0147] Aspect 8: The method according to Aspect 7, wherein the identification information includes at least one of a HARQ process ID or an SPS configuration number.

[0148] Aspect 9: The method according to aspect 7, wherein, if overlapping HARQ process IDs are allowed in the SPS configuration, the identification information further includes an SPS configuration number.

[0149] Aspect 10: The method according to aspect 7, wherein the payload size of the shared BA is quantized to provide a fixed number of NAKs.

[0150] Aspect 11: The method according to aspect 7, wherein the identification information further includes a unique identifier corresponding to the SPS opportunity within the confirmation window.

[0151] Aspect 12: The method according to aspect 3, wherein the number of SPS opportunities confirmed by the shared BA for each of the SPS configurations is fixed.

[0152] Aspect 13: A method according to Aspect 12, wherein: resources for shared BA are allocated based on a maximum number of SPS opportunities occurring in a confirmation window; and if no PDSCH transmission is detected in an SPS opportunity within the confirmation window, the UE indicates a negative acknowledgment (NAK).

[0153] Aspect 14: The method according to any one of aspects 1-13, further comprising receiving signaling indicating one or more features for sending one or more BAs.

[0154] Aspect 15: A method according to Aspect 14, wherein one or more features include at least one of the following: whether the UE sends a separate BA for each SPS configuration, each BA providing HARQ feedback for multiple SPS opportunities of the corresponding SPS configuration, or sends a shared BA, which provides HARQ feedback for SPS opportunities of multiple SPS configurations within a confirmation window; whether overlapping HARQ process IDs are allowed in the SPS configuration; whether the BA carries a positive acknowledgment (ACK) and a negative acknowledgment (NAK) or only carries NAK; or whether the number of SPS opportunities for each confirmation in the SPS configuration is fixed or variable.

[0155] Aspect 16: The method according to any one of aspects 14-15, wherein the signaling indicating the one or more characteristics is received in response to a request from the UE.

[0156] Aspect 17: The method according to Aspect 15, wherein the signaling is received together with the SPS configuration.

[0157] Aspect 18: A method according to any one of aspects 14-15, wherein one or more features are activated or deactivated via at least one of radio resource control (RRC), medium access control (MAC), or physical layer (PHY) signaling.

[0158] Aspect 19: The method according to any one of aspects 1-18, wherein a physical uplink control channel (PUCCH) resource for sending one or more BAs is assigned and configured using an SPS configuration.

[0159] Aspect 20: The method according to any one of aspects 1-19, wherein a physical uplink control channel (PUCCH) resource for sending one or more BAs is dynamically assigned.

[0160] Aspect 21: A method for wireless communication by a network entity, comprising: sending multiple semi-permanent scheduling (SPS) configurations to a user equipment (UE), each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE; sending the physical downlink shared channel (PDSCH) in at least some of the SPS opportunities of the SPS configuration; and monitoring one or more block acknowledgments (BAs) from the UE, each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0161] Aspect 22: The method according to aspect 21, wherein monitoring one or more BAs comprises: monitoring a separate BA for each SPS configuration, each BA providing HARQ feedback for multiple SPS opportunities of the corresponding SPS configuration.

[0162] Aspect 23: The method according to any one of aspects 21-22, wherein monitoring one or more BAs comprises: monitoring at least one shared BA that provides HARQ feedback for SPS opportunities of multiple SPS configurations.

[0163] Aspect 24: The method according to Aspect 23, wherein the number of SPS opportunities confirmed by the shared BA for each of the SPS configurations varies based at least on the number of SPS opportunities for each of the SPS configurations with the confirmation window.

[0164] Aspect 25: A method according to Aspect 24, wherein the order of confirmation feedback within a BA is based on at least one of: an SPS configuration number of an SPS configuration sharing the shared BA; or an order in which the confirmed SPS opportunities in the shared BA appear within a confirmation window.

[0165] Aspect 26: A method according to Aspect 24, wherein: resources for a shared BA are allocated based on a maximum number of SPS opportunities occurring in an acknowledgment window; and unused resources allocated to the shared BA are used to improve the link efficiency of the HARQ feedback provided in the shared BA.

[0166] Aspect 27: A method according to any of aspects 23-24, wherein: the shared BA is used only to provide negative acknowledgement (NAK); and the UE uses the shared BA to provide information identifying which SPS opportunities are being negatively acknowledged.

[0167] Aspect 28: The method according to Aspect 27, wherein the identification information includes at least one of a HARQ process ID or an SPS configuration number.

[0168] Aspect 29: The method according to Aspect 27, wherein, if overlapping HARQ process IDs are allowed in the SPS configuration, the identification information includes the SPS configuration number.

[0169] Aspect 30: The method according to aspect 27, wherein the payload size of the shared BA is quantized to provide a fixed number of NAKs.

[0170] Aspect 31: The method according to Aspect 27, wherein the identification information further includes a unique identifier corresponding to the SPS opportunity within the confirmation window.

[0171] Aspect 32: The method according to aspect 23, wherein the number of SPS opportunities confirmed by the shared BA for each of the SPS configurations is fixed.

[0172] Aspect 33: A method according to Aspect 32, wherein: resources for shared BA are allocated based on the maximum number of SPS opportunities occurring in the confirmation window; and if no PDSCH transmission is detected in the SPS opportunity within the confirmation window, the UE indicates a negative acknowledgement (NAK).

[0173] Aspect 34: The method according to any one of aspects 21-33 further comprises signaling an indication of one or more characteristics for sending one or more BAs to the UE.

[0174] Aspect 35: A method according to Aspect 34, wherein one or more features include at least one of the following: whether the UE sends a separate BA for each SPS configuration, each BA providing HARQ feedback for multiple SPS opportunities of the corresponding SPS configuration, or sends a shared BA, which provides HARQ feedback for SPS opportunities of multiple SPS configurations within a confirmation window; whether overlapping HARQ process IDs are allowed in the SPS configuration; whether the BA carries a positive acknowledgment (ACK) and a negative acknowledgment (NAK) or only carries NAK; or whether the number of SPS opportunities for each confirmation in the SPS configuration is fixed or variable.

[0175] Aspect 36: A method according to any one of aspects 34-35, wherein the indication of the one or more characteristics is signaled in response to a request from the UE.

[0176] Aspect 37: The method according to Aspect 35, wherein the signaling notification indication is related to the SPS configuration.

[0177] Aspect 38: The method according to any one of aspects 34-35 also includes activating or deactivating one or more features via at least one of radio resource control (RRC), medium access control (MAC) or physical layer (PHY) signaling.

[0178] Aspect 39: A method according to any one of aspects 21-38, wherein a physical uplink control channel (PUCCH) resource for sending one or more BAs is assigned and configured using an SPS configuration.

[0179] Aspect 40: A method according to any one of aspects 21-39, wherein a physical uplink control channel (PUCCH) resource for transmitting one or more BAs is dynamically assigned.

[0180] Aspect 41: A user equipment (UE), comprising: a component for receiving multiple semi-persistent scheduling (SPS) configurations, each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE; a component for monitoring the SPS opportunities of the SPS configurations; and a component for sending one or more block acknowledgments (BAs), each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0181] Aspect 42: The UE according to aspect 41, wherein the component for sending one or more BAs includes: a component for sending a separate BA for each SPS configuration, each BA providing HARQ feedback for multiple SPS opportunities of the corresponding SPS configuration.

[0182] Aspect 43: The UE according to any one of Aspects 41-42, wherein the component for sending one or more BAs includes: a component for sending at least one shared BA, which provides HARQ feedback for SPS opportunities of multiple SPS configurations.

[0183] Aspect 44: The UE according to aspect 43, wherein the number of SPS opportunities confirmed by the shared BA for each of the SPS configurations varies based on at least the number of SPS opportunities for each of the SPS configurations with the confirmation window.

[0184] Aspect 45: A UE according to Aspect 44, wherein the order of confirmation feedback within a BA is based on at least one of the following: an SPS configuration number of an SPS configuration sharing the shared BA; or an order in which the SPS opportunities confirmed in the shared BA appear within a confirmation window.

[0185] Aspect 46: A UE according to Aspect 44, wherein: resources for a shared BA are allocated based on a maximum number of SPS opportunities occurring in an acknowledgment window; and unused resources allocated to the shared BA are used to improve link efficiency of HARQ feedback provided in the shared BA.

[0186] Aspect 47: A UE according to any one of aspects 43-44, wherein: the shared BA is used only to provide negative acknowledgement (NAK); and the means for sending also uses the shared BA to send information identifying which SPS opportunities are being negatively acknowledged.

[0187] Aspect 48: The UE according to Aspect 47, wherein the identification information includes at least one of a HARQ process ID or an SPS configuration number.

[0188] Aspect 49: The UE according to Aspect 47, wherein, if overlapping HARQ process IDs are allowed in the SPS configuration, the identification information further includes an SPS configuration number.

[0189] Aspect 50: The UE according to aspect 47, wherein the payload size of the shared BA is quantized to provide a fixed number of NAKs.

[0190] Aspect 51: The UE according to aspect 47, wherein the identification information further includes a unique identifier corresponding to the SPS opportunity within the confirmation window.

[0191] Aspect 52: The UE according to aspect 43, wherein the number of SPS opportunities confirmed by the shared BA for each of the SPS configurations is fixed.

[0192] Aspect 53: A UE according to Aspect 52, wherein: resources for shared BA are allocated based on a maximum number of SPS opportunities occurring in a confirmation window; and the UE also includes a component for indicating a negative acknowledgment (NAK) if no PDSCH transmission is detected in an SPS opportunity within the confirmation window.

[0193] Aspect 54: The UE according to aspect 41, further comprising a means for receiving signaling indicating one or more characteristics for sending one or more BAs.

[0194] Aspect 55: A UE according to Aspect 54, wherein one or more features include at least one of the following: whether the UE sends a separate BA for each SPS configuration, each BA providing HARQ feedback for multiple SPS opportunities of the corresponding SPS configuration, or sends a shared BA, which provides HARQ feedback for SPS opportunities of multiple SPS configurations within a confirmation window; whether overlapping HARQ process IDs are allowed in the SPS configuration; whether the BA carries a positive acknowledgment (ACK) and a negative acknowledgment (NAK) or only carries NAK; or whether the number of SPS opportunities for each confirmation in the SPS configuration is fixed or variable.

[0195] Aspect 56: A UE according to any one of aspects 54-55, wherein the signaling indicating the one or more characteristics is received in response to a request from the UE.

[0196] Aspect 57: The UE according to Aspect 55, wherein the signaling is received together with the SPS configuration.

[0197] Aspect 58: A UE according to any one of aspects 54-55, wherein one or more features are activated or deactivated via at least one of radio resource control (RRC), medium access control (MAC), or physical layer (PHY) signaling.

[0198] Aspect 59: The UE according to any one of aspects 41-58, wherein a physical uplink control channel (PUCCH) resource for sending one or more BAs is assigned and configured using an SPS configuration.

[0199] Aspect 60: The UE according to any one of aspects 41-59, wherein a physical uplink control channel (PUCCH) resource for sending one or more BAs is dynamically assigned.

[0200] Aspect 61: A network entity comprising: a component for sending multiple semi-persistent scheduling (SPS) configurations to a user equipment (UE), each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE; a component for sending the physical downlink shared channel (PDSCH) in at least some of the SPS opportunities of the SPS configuration; and a component for monitoring one or more block acknowledgments (BAs) from the UE, each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0201] Aspect 62: The network entity of aspect 61, wherein the means for monitoring one or more BAs comprises means for monitoring a separate BA for each SPS configuration, each BA providing HARQ feedback for a plurality of SPS opportunities of the corresponding SPS configuration.

[0202] Aspect 63: The network entity according to any of aspects 61-62, wherein the means for monitoring one or more BAs comprises: means for monitoring at least one shared BA providing HARQ feedback for SPS opportunities configured for multiple SPSs.

[0203] Aspect 64: The network entity according to Aspect 63, wherein the number of SPS opportunities confirmed by the shared BA for each of the SPS configurations varies based at least on the number of SPS opportunities for each of the SPS configurations with the confirmation window.

[0204] Aspect 65: A network entity according to Aspect 64, wherein the order of confirmation feedback within a BA is based on at least one of the following: an SPS configuration number of an SPS configuration sharing the shared BA; or an order in which the confirmed SPS opportunities in the shared BA appear within a confirmation window.

[0205] Aspect 66: A network entity according to Aspect 64, wherein: resources for a shared BA are allocated based on a maximum number of SPS opportunities occurring in an acknowledgement window; and unused resources allocated to the shared BA are used to improve link efficiency of HARQ feedback provided in the shared BA.

[0206] Aspect 67: A network entity according to any of Aspects 63-64, wherein: the shared BA is used only to provide negative acknowledgement (NAK); and the network entity further comprises a component for receiving information identifying which SPS opportunities are being negatively acknowledged using the shared BA.

[0207] Aspect 68: The network entity according to Aspect 67, wherein the identification information includes at least one of a HARQ process ID or an SPS configuration number.

[0208] Aspect 69: The network entity according to Aspect 67, wherein, if overlapping HARQ process IDs are allowed in the SPS configuration, the identification information includes the SPS configuration number.

[0209] Aspect 70: The network entity according to aspect 67, wherein the payload size of the shared BA is quantized to provide a fixed number of NAKs.

[0210] Aspect 71: The network entity according to aspect 67, wherein the identification information further comprises a unique identifier corresponding to the SPS opportunity within the confirmation window.

[0211] Aspect 72: The network entity according to aspect 63, wherein the number of SPS opportunities confirmed by the shared BA for each of the SPS configurations is fixed.

[0212] Aspect 73: A network entity according to Aspect 72, wherein: resources for shared BA are allocated based on a maximum number of SPS opportunities occurring in a confirmation window; and the network entity further comprises a component for receiving an indication of a negative acknowledgment (NAK) if no PDSCH transmission is detected in an SPS opportunity within the confirmation window.

[0213] Aspect 74: The network entity according to any one of aspects 61-73, further comprising means for signaling an indication of one or more characteristics for sending one or more BAs to the UE.

[0214] Aspect 75: A network entity according to Aspect 74, wherein the one or more characteristics include at least one of the following: whether the UE sends a separate BA for each SPS configuration, each BA providing HARQ feedback for multiple SPS opportunities of the corresponding SPS configuration, or sends a shared BA, which provides HARQ feedback for SPS opportunities of multiple SPS configurations within a confirmation window; whether overlapping HARQ process IDs are allowed in the SPS configuration; whether the BA carries a positive acknowledgment (ACK) and a negative acknowledgment (NAK) or only carries NAK; or whether the number of SPS opportunities for each confirmation in the SPS configuration is fixed or variable.

[0215] Aspect 76: The network entity according to any one of aspects 74-75, wherein the indication of the one or more characteristics is signaled in response to a request from the UE.

[0216] Aspect 77: The network entity according to Aspect 75, wherein the signaling notification indication is related to the SPS configuration.

[0217] Aspect 78: The network entity according to any one of Aspects 74-75 further comprises a component for activating or deactivating one or more features via at least one of radio resource control (RRC), medium access control (MAC) or physical layer (PHY) signaling.

[0218] Aspect 79: The network entity according to any one of aspects 61-78, wherein a physical uplink control channel (PUCCH) resource for sending one or more BAs is assigned and configured using an SPS configuration.

[0219] Aspect 80: The network entity according to any one of aspects 61-79, wherein a physical uplink control channel (PUCCH) resource for sending one or more BAs is dynamically assigned.

[0220] Aspect 81: A user equipment (UE) comprising: a receiver configured to receive multiple semi-persistent scheduling (SPS) configurations, each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE; a processing system configured to monitor the SPS opportunities of the SPS configurations; and a transmitter configured to send one or more block acknowledgments (BAs), each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0221] Aspect 82: The UE according to aspect 81, wherein the sending of one or more BAs comprises sending a separate BA for each SPS configuration, each BA providing HARQ feedback for multiple SPS opportunities of the corresponding SPS configuration.

[0222] Aspect 83: The UE according to any one of Aspects 81-82, wherein the sending of one or more BAs comprises: sending at least one shared BA, the at least one shared BA providing HARQ feedback for SPS opportunities of multiple SPS configurations.

[0223] Aspect 84: The UE according to Aspect 83, wherein the number of SPS opportunities confirmed by the shared BA for each of the SPS configurations varies based on at least the number of SPS opportunities for each of the SPS configurations with the confirmation window.

[0224] Aspect 85: A UE according to Aspect 84, wherein the order of confirmation feedback within a BA is based on at least one of the following: an SPS configuration number of an SPS configuration sharing the shared BA; or an order in which the SPS opportunities confirmed in the shared BA appear within a confirmation window.

[0225] Aspect 86: A UE according to Aspect 84, wherein: resources for the shared BA are allocated based on a maximum number of SPS opportunities occurring in an acknowledgment window; and unused resources allocated to the shared BA are used to improve link efficiency of HARQ feedback provided in the shared BA.

[0226] Aspect 87: A UE according to any one of aspects 83-84, wherein: the shared BA is used only to provide negative acknowledgement (NAK); and the processing system is further configured to use the shared BA to provide information identifying which SPS opportunities are being negatively acknowledged.

[0227] Aspect 88: The UE according to Aspect 87, wherein the identification information includes at least one of a HARQ process ID or an SPS configuration number.

[0228] Aspect 89: The UE according to Aspect 87, wherein, if overlapping HARQ process IDs are allowed in the SPS configuration, the identification information further includes an SPS configuration number.

[0229] Aspect 90: The UE according to aspect 87, wherein the payload size of the shared BA is quantized to provide a fixed number of NAKs.

[0230] Aspect 91: The UE according to aspect 87, wherein the identification information further includes a unique identifier corresponding to the SPS opportunity within the confirmation window.

[0231] Aspect 92: The UE according to aspect 83, wherein the number of SPS opportunities confirmed by the shared BA for each of the SPS configurations is fixed.

[0232] Aspect 93: A UE according to Aspect 92, wherein: resources for shared BA are allocated based on a maximum number of SPS opportunities occurring in a confirmation window; and the processing system is also configured to indicate a negative acknowledgment (NAK) if no PDSCH transmission is detected in an SPS opportunity within the confirmation window.

[0233] Aspect 94: The UE according to any one of aspects 81-93, wherein the receiver is further configured to receive signaling indicating one or more characteristics for sending one or more BAs.

[0234] Aspect 95: A UE according to Aspect 94, wherein the one or more characteristics include at least one of the following: whether the UE sends a separate BA for each SPS configuration, each BA providing HARQ feedback for multiple SPS opportunities of the corresponding SPS configuration, or sends a shared BA, which provides HARQ feedback for SPS opportunities of multiple SPS configurations within a confirmation window; whether overlapping HARQ process IDs are allowed in the SPS configuration; whether the BA carries a positive acknowledgment (ACK) and a negative acknowledgment (NAK) or only carries NAK; or whether the number of SPS opportunities for each confirmation in the SPS configuration is fixed or variable.

[0235] Aspect 96: A UE according to any one of aspects 94-95, wherein the signaling indicating the one or more characteristics is received in response to a request from the UE.

[0236] Aspect 97: The UE according to Aspect 95, wherein the signaling is received together with the SPS configuration.

[0237] Aspect 98: A UE according to any one of Aspects 94-95, wherein one or more features are activated or deactivated via at least one of radio resource control (RRC), medium access control (MAC), or physical layer (PHY) signaling.

[0238] Aspect 99: A UE according to any one of aspects 81-98, wherein a physical uplink control channel (PUCCH) resource for sending one or more BAs is assigned and configured using an SPS configuration.

[0239] Aspect 100: The UE according to any one of aspects 81-99, wherein a physical uplink control channel (PUCCH) resource for sending one or more BAs is dynamically assigned.

[0240] Aspect 101: A network entity comprising: a transmitter configured to send multiple semi-persistent scheduling (SPS) configurations to a user equipment (UE), each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE, and sending the physical downlink shared channel (PDSCH) in at least some of the SPS opportunities of the SPS configuration; and a processing system configured to monitor one or more block acknowledgments (BAs) from the UE, each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0241] Aspect 102: The network entity of aspect 101, wherein the processing system monitors the one or more BAs by monitoring a separate BA for each SPS configuration, each BA providing HARQ feedback for a plurality of SPS opportunities of the corresponding SPS configuration.

[0242] Aspect 103: The network entity according to any of aspects 101-102, wherein the processing system monitors the one or more BAs by monitoring at least one shared BA providing HARQ feedback for SPS opportunities of a plurality of SPS configurations.

[0243] Aspect 104: The network entity according to aspect 103, wherein the number of SPS opportunities confirmed by the shared BA for each of the SPS configurations varies based at least on the number of SPS opportunities for each of the SPS configurations with the confirmation window.

[0244] Aspect 105: A network entity according to aspect 104, wherein the order of confirmation feedback within a BA is based on at least one of: an SPS configuration number of an SPS configuration sharing the shared BA; or an order in which the confirmed SPS opportunities in the shared BA appear within a confirmation window.

[0245] Aspect 106: A network entity according to aspect 104, wherein: resources for the shared BA are allocated based on a maximum number of SPS opportunities occurring in an acknowledgement window; and unused resources allocated to the shared BA are used to improve link efficiency of HARQ feedback provided in the shared BA.

[0246] Aspect 107: A network entity according to any one of Aspects 103-104, wherein: the shared BA is used only to provide negative acknowledgement (NAK); and the network entity also includes a receiver configured to receive information identifying which SPS opportunities are being negatively acknowledged using the shared BA.

[0247] Aspect 108: The network entity according to aspect 107, wherein the identification information comprises at least one of a HARQ process ID or an SPS configuration number.

[0248] Aspect 109: The network entity according to aspect 107, wherein, if overlapping HARQ process IDs are allowed in the SPS configuration, the identification information comprises the SPS configuration number.

[0249] Aspect 110: The network entity of aspect 107, wherein a payload size of the shared BA is quantized to provide a fixed number of NAKs.

[0250] Aspect 111: The network entity according to aspect 107, wherein the identification information further comprises a unique identifier corresponding to the SPS opportunity within the confirmation window.

[0251] Aspect 112: The network entity according to Aspect 103, wherein the number of SPS opportunities confirmed by the shared BA for each of the SPS configurations is fixed.

[0252] Aspect 113: A network entity according to Aspect 112, wherein: resources for shared BA are allocated based on a maximum number of SPS opportunities occurring in a confirmation window; and the network entity also includes a receiver configured to receive a negative acknowledgement (NAK) if no PDSCH transmission is detected in an SPS opportunity within the confirmation window.

[0253] Aspect 114: The network entity according to any of aspects 101-113, wherein the processing system is further configured to provide signaling transmitted to the UE for sending an indication of one or more characteristics of the BA.

[0254] Aspect 115: A network entity according to Aspect 114, wherein the one or more characteristics include at least one of the following: whether the UE sends a separate BA for each SPS configuration, each BA providing HARQ feedback for multiple SPS opportunities of the corresponding SPS configuration, or sends a shared BA, which provides HARQ feedback for SPS opportunities of multiple SPS configurations within a confirmation window; whether overlapping HARQ process IDs are allowed in the SPS configuration; whether the BA carries a positive acknowledgement (ACK) and a negative acknowledgement (NAK) or only carries a NAK; or whether the number of SPS opportunities for each confirmation in the SPS configuration is fixed or variable.

[0255] Aspect 116: The network entity according to any of aspects 114-115, wherein the indication of the one or more characteristics is signaled in response to a request from the UE.

[0256] Aspect 117: The network entity according to aspect 115, wherein the signaling notification indication is related to the SPS configuration.

[0257] Aspect 118: A network entity according to any one of Aspects 114-115, wherein the processing system is further configured to activate or deactivate one or more features via at least one of radio resource control (RRC), medium access control (MAC) or physical layer (PHY) signaling.

[0258] Aspect 119: The network entity according to any one of aspects 101-118, wherein a physical uplink control channel (PUCCH) resource for sending the BA is assigned and configured using an SPS configuration.

[0259] Aspect 120: The network entity according to any one of aspects 101-119, wherein a physical uplink control channel (PUCCH) resource for sending the BA is dynamically assigned.

[0260] Aspect 121: An apparatus for wireless communication by a user equipment (UE), comprising: an interface configured to receive multiple semi-permanent scheduling (SPS) configurations, each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE; and a processing system configured to monitor the SPS opportunities of the SPS configurations and generate one or more block acknowledgments (BAs), each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window, wherein the interface is further configured to output one or more BAs for transmission.

[0261] Aspect 122: An apparatus for wireless communication by a network entity, comprising: an interface configured to output multiple semi-persistent scheduling (SPS) configurations for transmission to a user equipment (UE), each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE, and outputting a physical downlink shared channel (PDSCH) for transmission in at least some of the SPS opportunities of the SPS configurations; and a processing system configured to monitor one or more block acknowledgments (BAs) from the UE, each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0262] Aspect 123: A computer-readable medium for wireless communications by a user equipment (UE), comprising executable instructions to: receive multiple semi-persistent scheduling (SPS) configurations, each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmissions to the UE; monitor the SPS opportunities of the SPS configurations; and send one or more block acknowledgments (BAs), each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0263] Aspect 124: A computer-readable medium for wireless communications by a network entity, comprising executable instructions to: send multiple semi-persistent scheduling (SPS) configurations to a user equipment (UE), each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmissions to the UE; send the physical downlink shared channel (PDSCH) in at least some of the SPS opportunities of the SPS configurations; and monitor one or more block acknowledgments (BAs) from the UE, each BA providing hybrid automatic repeat request (HARQ) feedback for multiple SPS opportunities of one or more SPS configurations occurring within an acknowledgment window.

[0264] The method disclosed herein includes one or more steps or actions for implementing the method. Without departing from the scope of the claims, the method steps and / or actions can be interchangeable with each other. In other words, unless a specific order of steps or actions is specified, the order and / or use of specific steps and / or actions can be modified without departing from the scope of the claims.

[0265] As used herein, phrases referring to "at least one of" a list of items refer to any combination of those items, including single members. For example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination of multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc or any other order of a, b, and c).

[0266] As used herein, the term "determining" encompasses a variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, a database, or another data structure), ascertaining, etc. In addition, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. In addition, "determining" may include parsing, selecting, choosing, establishing, etc.

[0267] The foregoing description is provided to enable those skilled in the art to practice the various aspects described herein. It will be readily apparent to those skilled in the art that various modifications to these aspects are to be made, and the general principles defined herein may be applicable to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to conform to the full scope consistent with the language of the claims, wherein, unless otherwise stated, the elements in the singular form are not intended to represent "one and only one", but to represent "one or more". Unless otherwise specified, the term "some" refers to one or more. All structural and functional equivalents of the elements of the various aspects described in this disclosure known or to be known by those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be included by the claims. In addition, nothing disclosed herein is intended to be donated to the public, regardless of whether such disclosure is explicitly stated in the claims. Unless the element is explicitly described using the phrase "parts for", or in the case of a method claim, the element is described using the phrase "steps for", no claim element should be interpreted according to the provisions of the sixth paragraph of 35 U.S.C. 112.

[0268] The various operations of the above methods may be performed by any suitable components capable of performing the corresponding functions. The components may include various (multiple) hardware and / or software components and / or (multiple) modules, including but not limited to circuits, application specific integrated circuits (ASICs), or processors. Generally, where operations are illustrated in a figure, those operations may have corresponding corresponding parts-plus-function components with similar numbers. For example, Figure 4 The processors 458, 464, 466 of the UE 120 and / or the controller / processor 480 and / or the processors 420, 430, 438 and / or the controller / processor 440 of the BS 110 may be configured to perform Figure 8 Operation 800 and Fig. 9 Operation 900.

[0269] The means for receiving may include a receiver, such as Figure 4 One or more antennas and / or receiving processors as shown in . Similarly, the components for transmitting may include a transmitter, such as Figure 4 One or more antennas and / or transmit processors as shown in . The means for monitoring, the means for indicating, the means for signaling notification, the means for activating and the means for deactivating may include a processing system, which may include one or more processors, such as Figure 4 Processors 458 , 464 , 466 and / or controller / processor 480 of UE 120 and / or processors 420 , 430 , 438 and / or controller / processor 440 of BS 110 are shown.

[0270] In some cases, a device may have an interface to output frames for transmission (components for outputting) rather than actually transmitting frames. For example, a processor may output frames to a radio frequency (RF) front end via a bus interface for transmission. Similarly, a device may have an interface to obtain frames received from another device (components for obtaining) rather than actually receiving frames. For example, a processor may obtain (or receive) frames from an RF front end via a bus interface for reception.

[0271] The various exemplary logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.

[0272] If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. Depending on the specific application and overall design constraints of the processing system, the bus may include any number of interconnecting buses and bridges. The bus may link various circuits together, including a processor, a machine-readable medium, and a bus interface. The bus interface may be used to connect a network adapter, etc., to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In the user terminal 120 (see Figure 1 ), a user interface (e.g., keyboard, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, etc., which are well known in the art and are not described further. The processor may be implemented using one or more general and / or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits that can run software. Those skilled in the art will recognize how to best implement the functionality of the processing system depending on the specific application and the overall design constraints imposed on the entire system.

[0273] If implemented in software, these functions may be stored or transmitted as one or more instructions or codes on a computer-readable medium. Software should be broadly interpreted as instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or other. Computer-readable media include computer storage media and communication media, including any media that facilitates the transfer of computer programs from one place to another. The processor may be responsible for managing the bus and general processing, including running software modules stored on a machine-readable storage medium. A computer-readable storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Alternatively, the storage medium may be integrated into the processor. For example, a machine-readable medium may include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium on which instructions separated from a wireless node are stored, all of which may be accessed by a processor through a bus interface. Alternatively or additionally, a machine-readable medium or any portion thereof may be integrated into a processor, such as in the case of a cache and / or a general register file. For example, examples of machine-readable storage media may include RAM (random access memory), flash memory, ROM (read-only memory), PROM (programmable read-only memory), EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage media, or any combination thereof. Machine-readable media may be included in a computer program product.

[0274] A software module may include a single instruction or multiple instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media. A computer-readable medium may include multiple software modules. A software module includes instructions that, when executed by a device such as a processor, cause a processing system to perform various functions. A software module may include a sending module and a receiving module. Each software module may reside in a single storage device, or may be distributed across multiple storage devices. For example, when a triggering event occurs, a software module may be loaded from a hard disk into a RAM. During the operation of a software module, a processor may load some instructions into a cache to increase access speed. Then, one or more cache lines may be loaded into a general register file for the processor to run. When the functions of a software module are mentioned below, it will be understood that such functions are implemented by the processor when executing instructions from the software module.

[0275] Likewise, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio and microwave are included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Optical disks, where magnetic disks typically reproduce data magnetically, and optical disks reproduce data optically with lasers. Thus, in some aspects, computer readable media may include non-transitory computer readable media (e.g., tangible media). Additionally, for other aspects, computer readable media may include transient computer readable media (e.g., signals). Combinations of the above should also be included within the scope of computer readable media.

[0276] Thus, certain aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having stored (and / or encoded) thereon instructions that can be executed by one or more processors to perform the operations described herein. For example, instructions for performing the operations described herein and in the accompanying drawings.

[0277] In addition, it should be understood that the modules and / or other appropriate components for performing the methods and techniques described herein can be downloaded and / or otherwise obtained by a user terminal and / or a base station. For example, such a device can be coupled to a server to facilitate the transfer of components for performing the methods described herein. Alternatively, the various methods described herein can be provided by a storage component (e.g., RAM, ROM, physical storage media such as a compact disc (CD) or a floppy disk), so that the user terminal and / or the base station can obtain the various methods when the storage component is coupled or provided to the device. In addition, any other suitable technology for providing the methods and techniques described herein to the device can be utilized.

[0278] It is to be understood that the claims are not limited to the precise configuration and components described above. Various modifications, changes and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. A method for wireless communication by a user equipment UE, comprising: receiving a plurality of semi-persistent scheduling (SPS) configurations, each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE; monitoring SPS opportunities of the plurality of SPS configurations; as well as sending one or more block acknowledgments (BAs), each BA providing hybrid automatic repeat request (HARQ) feedback for a plurality of SPS opportunities of one or more of the plurality of SPS configurations occurring within an acknowledgment window, The one or more BAs include at least one shared BA, the shared BA provides HARQ feedback for the SPS opportunities of the multiple SPS configurations, and The number of SPS opportunities confirmed by the shared BA for the multiple SPS configurations varies based on at least the number of SPS opportunities within the confirmation window for each SPS configuration in the multiple SPS configurations.

2. The method according to claim 1, wherein: The ordering of confirmation feedback within the BA is based on at least one of the following: the SPS configuration numbers of the multiple SPS configurations that share the shared BA; or The order in which the SPS opportunities confirmed in the shared BA appear within the confirmation window.

3. The method according to claim 1, wherein: allocating resources for the shared BA based on a maximum number of SPS opportunities occurring within a confirmation window; and Unused resources allocated to the shared BA are used to improve link efficiency of HARQ feedback provided in the shared BA.

4. The method according to claim 1, wherein: The shared BA is only used to provide negative acknowledgement NAK; and The UE uses the shared BA to provide information identifying which SPS opportunities are being negatively acknowledged.

5. The method according to claim 4, wherein: The information includes at least one of a HARQ process ID or an SPS configuration number.

6. The method according to claim 4, wherein: If overlapping HARQ process IDs are allowed in the SPS configuration, the information also includes the SPS configuration number.

7. The method according to claim 4, wherein: The payload size of the shared BA is quantized to provide a fixed number of NAKs.

8. The method according to claim 4, wherein: The information also includes a unique identifier corresponding to the SPS opportunity within the confirmation window.

9. The method according to claim 1, wherein: The payload size of the shared BA is fixed.

10. The method according to claim 9, wherein: allocating resources for the shared BA based on a maximum number of SPS opportunities occurring within a confirmation window; and If no PDSCH transmission is detected in an SPS opportunity within the acknowledgment window, the UE indicates a negative acknowledgment NAK.

11. The method of claim 1, further comprising receiving signaling indicating one or more characteristics for transmitting the one or more BAs.

12. The method according to claim 11, wherein: The one or more features include at least one of the following: Whether the UE sends a separate BA for each SPS configuration, each BA providing HARQ feedback for multiple SPS opportunities of the corresponding SPS configuration, or sends a shared BA, the shared BA providing HARQ feedback for SPS opportunities of multiple SPS configurations within the acknowledgment window; Whether overlapping HARQ process IDs are allowed in SPS configuration; Whether the BA carries both a positive acknowledgment ACK and a negative acknowledgment NAK or only a NAK; or Whether the number of SPS opportunities confirmed by the BA for each of the plurality of SPS configurations is fixed or variable.

13. A method for wireless communication by a network entity, comprising: Sending a plurality of semi-persistent scheduling (SPS) configurations to a user equipment (UE), each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE; transmitting a physical downlink shared channel (PDSCH) in at least some SPS opportunities of the plurality of SPS configurations; as well as monitoring one or more block acknowledgements (BAs) from the UE, each BA providing hybrid automatic repeat request (HARQ) feedback for a plurality of SPS opportunities of one or more of the plurality of SPS configurations occurring within an acknowledgement window, The one or more BAs include at least one shared BA, the shared BA provides HARQ feedback for the SPS opportunities of the multiple SPS configurations, and The number of SPS opportunities confirmed by the shared BA for the multiple SPS configurations varies based on at least the number of SPS opportunities within the confirmation window for each SPS configuration in the multiple SPS configurations.

14. The method according to claim 13, wherein: The ordering of confirmation feedback within the BA is based on at least one of the following: the SPS configuration numbers of the multiple SPS configurations that share the shared BA; or The order in which the SPS opportunities confirmed in the shared BA appear within the confirmation window.

15. The method of claim 13, wherein: allocating resources for the shared BA based on a maximum number of SPS opportunities occurring within a confirmation window; and Unused resources allocated to the shared BA are used to improve link efficiency of HARQ feedback provided in the shared BA.

16. The method of claim 13, wherein: The shared BA is only used to provide negative acknowledgement NAK; and The shared BA also includes information identifying which SPS opportunities are being negatively acknowledged.

17. The method according to claim 16, wherein: The information includes at least one of a HARQ process ID or an SPS configuration number.

18. The method according to claim 16, wherein: If overlapping HARQ process IDs are allowed in the SPS configuration, the information includes the SPS configuration number.

19. The method according to claim 16, wherein: The payload size of the shared BA is quantized to provide a fixed number of NAKs.

20. The method according to claim 16, wherein: The information also includes a unique identifier corresponding to the SPS opportunity within the confirmation window.

21. The method according to claim 13, wherein: The payload size of the shared BA is fixed.

22. The method of claim 21, wherein: allocating resources for the shared BA based on a maximum number of SPS opportunities occurring within a confirmation window; and If no PDSCH transmission is detected in an SPS opportunity within the acknowledgment window, the UE indicates a negative acknowledgment NAK.

23. The method of claim 13, further comprising signaling an indication to a UE of one or more characteristics for sending the one or more BAs.

24. The method according to claim 23, wherein: The one or more features include at least one of the following: Whether the UE sends a separate BA for each SPS configuration, each BA providing HARQ feedback for multiple SPS opportunities of the corresponding SPS configuration, or sends a shared BA, the shared BA providing HARQ feedback for SPS opportunities of multiple SPS configurations within the acknowledgment window; Whether overlapping HARQ process IDs are allowed in SPS configuration; Whether the BA carries both a positive acknowledgment ACK and a negative acknowledgment NAK or only a NAK; or Whether the number of SPS opportunities confirmed by the BA for each of the plurality of SPS configurations is fixed or variable.

25. A user equipment UE, comprising: Memory; as well as One or more processors coupled to the memory, configured to cause the UE to: receiving a plurality of semi-persistent scheduling (SPS) configurations, each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE; monitoring SPS opportunities of the plurality of SPS configurations; as well as sending one or more block acknowledgments (BAs), each BA providing hybrid automatic repeat request (HARQ) feedback for a plurality of SPS opportunities of one or more of the plurality of SPS configurations occurring within an acknowledgment window, The one or more BAs include at least one shared BA, the shared BA provides HARQ feedback for the SPS opportunities of the multiple SPS configurations, and The number of SPS opportunities confirmed by the shared BA for the multiple SPS configurations varies based on at least the number of SPS opportunities within the confirmation window for each SPS configuration in the multiple SPS configurations.

26. The UE according to claim 25, wherein: allocating resources for the shared BA based on a maximum number of SPS opportunities occurring within a confirmation window; and Unused resources allocated to the shared BA are used to improve link efficiency of HARQ feedback provided in the shared BA.

27. The UE according to claim 25, wherein: The shared BA is only used to provide negative acknowledgement NAK; as well as The one or more processors are configured to cause the UE to provide information identifying which SPS opportunities are being negatively acknowledged using the shared BA.

28. The UE according to claim 25, wherein: The payload size of the shared BA is fixed.

29. The UE according to claim 28, wherein: allocating resources for the shared BA based on a maximum number of SPS opportunities occurring in a confirmation window; as well as If no PDSCH transmission is detected in an SPS opportunity within an acknowledgment window, the one or more processors are configured to cause the UE to indicate a negative acknowledgment (NAK).

30. A network entity, comprising: Memory; as well as One or more processors coupled to the memory, configured to cause the network entity to: Sending a plurality of semi-persistent scheduling (SPS) configurations to a user equipment (UE), each SPS configuration allocating a set of periodic opportunities for physical downlink shared channel (PDSCH) transmission to the UE; transmitting a physical downlink shared channel (PDSCH) in at least some SPS opportunities of the plurality of SPS configurations; as well as monitoring one or more block acknowledgements (BAs) from the UE, each BA providing hybrid automatic repeat request (HARQ) feedback for a plurality of SPS opportunities of one or more of the plurality of SPS configurations occurring within an acknowledgement window, The one or more BAs include at least one shared BA, the shared BA provides HARQ feedback for the SPS opportunities of the multiple SPS configurations, and The number of SPS opportunities confirmed by the shared BA for the multiple SPS configurations varies based on at least the number of SPS opportunities within the confirmation window for each SPS configuration in the multiple SPS configurations.

Images