Delayed harq-ack design under dynamic sfi

Abstract

Aspects of the disclosure relate to wireless communications, and more particularly, to mechanisms for acknowledging semi-persistently scheduled (SPS) occasions from multiple SPS configurations using block acknowledgments. An example method generally includes identifying a slot or sub-slot scheduled for reporting acknowledgment feedback for SPS physical downlink shared channel (PDSCH). The method identifies that one or more symbols of the identified slot or sub-slot scheduled to transmit a physical uplink control channel (PUCCH) containing the acknowledgment feedback are semi-static flexible symbols. The method further monitors for a dynamic slot format indicator (SFI) dynamically configuring the one or more semi-static flexible symbols of the slot or sub-slot as downlink, uplink, or flexible. The method then decides, based on the monitoring, whether to report the acknowledgment feedback in the scheduled slot or sub-slot, in a subsequent slot or sub-slot, or both.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims priority to U.S. Application No. 17 / 486,884, filed September 27, 2021, which claims benefit of and priority to U.S. Provisional Patent Application No. 63 / 084,532, filed September 28, 2020, both of which are assigned to the assignee hereof and hereby expressly incorporated by reference herein in their entireties as if fully set forth below and for all applicable purposes.

[0003] INTRODUCTION

[0004] TECHNICAL FIELD

[0005] Aspects of the present disclosure relate to wireless communications, and more particularly, to mechanisms and techniques for delaying hybrid automatic repeat request (HARQ) acknowledgements (ACKs) based on dynamic slot format indicator (SFI) monitoring.

[0006] BACKGROUND

[0007] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems can employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). 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.

[0008] In some examples, a wireless multiple-access communication system can include a number of base stations, each simultaneously supporting communication for multiple communication devices, otherwise known as user equipment (UEs). In a Long Term Evolution (LTE) or LTE-Advanced (LTE-A) network, a set of one or more base stations can define an eNodeB (eNB). In other examples (e.g., in a next generation or 5G network), a wireless multiple access

[0009] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on the same communication network. An example of which is a new radio (NR) such as a 5G radio access. NR is a set of enhancements implemented to the LTE mobile standard promulgated by Third Generation Partnership Project (3GPP). It is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDMA with cyclic prefix (CP) on the downlink (DL) and on the uplink (UL) as well as support beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0010] However, as the demand for mobile broadband access continues to increase, there exists a need for further improvements in NR technologies. Preferably, these improvements should be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

[0011] SUMMARY

[0012] Aspects of the present disclosure relate to wireless communications, and more particularly, to mechanisms and techniques for setting conditions to delay or cancel reporting of acknowledgment feedback to a network entity based on various conditions.

[0013] Certain aspects of the present disclosure provide a method for wireless communications by a user equipment (UE). The method generally includes identifying a slot or sub-slot scheduled for reporting acknowledgement feedback for a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH), identifying that one or more symbols of the identified slot or sub-slot scheduled to transmit a physical uplink control channel (PUCCH) containing the acknowledgement feedback are semi-static flexible symbols, monitoring for a dynamic slot format indicator (SFI) that dynamically configures the one or more semi-static flexible symbols of the slot or sub-slot as downlink, uplink, or flexible, and deciding, based on the monitoring, whether to report the acknowledgement feedback in the scheduled slot or sub-slot, in a subsequent slot or sub-slot, or both.

[0014] Certain aspects of the present disclosure provide a method for wireless communications by a network entity. The method generally includes transmitting, to a UE, an SPS PDSCH, identifying a slot or sub-slot scheduled for the UE to report acknowledgement feedback for the SPS PDSCH, identifying that one or more symbols of the identified slot or sub-slot scheduled to transmit a PUCCH containing the acknowledgement feedback are semi-static flexible symbols, sending, to the UE, a dynamic SFI that dynamically configures the one or more semi-static flexible symbols of the slot or sub-slot as downlink, uplink, or flexible, and deciding, based on the SFI, whether to monitor for the acknowledgement feedback in the scheduled slot or sub-slot, in a subsequent slot or sub-slot, or both.

[0015] Certain aspects of the present disclosure provide a UE for wireless communication. The UE includes at least one processor and a memory coupled to the at least one processor. The at least one processor and the memory are configured to identify a slot or sub-slot scheduled for reporting acknowledgement feedback for an SPS PDSCH. The at least one processor and the memory are configured to identify that one or more symbols of the identified slot or sub-slot scheduled to transmit a PUCCH containing the acknowledgement feedback are semi-static flexible symbols. The at least one processor and the memory are further configured to monitor for a dynamic SFI that dynamically configures the one or more semi-static flexible symbols of the slot or sub-slot as downlink, uplink, or flexible. The at least one processor and the memory are configured to decide, based on the monitoring, whether to report the acknowledgement feedback in the scheduled slot or sub-slot, in a subsequent slot or sub-slot, or both.

[0016] Certain aspects of the present disclosure provide a network entity for wireless communication. The network entity includes at least one processor and a memory coupled to the at least one processor. The at least one processor and the memory are configured to transmit, to a UE, an SPS PDSCH. The at least one processor and the memory are configured to identify a slot or sub-slot scheduled for the UE to report acknowledgment feedback for the SPS PDSCH. The at least one processor and the memory are configured to identify that one or more symbols of the identified slot or sub-slot scheduled to transmit a PUCCH containing the acknowledgment feedback are semi-static flexible symbols. The at least one processor and the memory are configured to send, to the UE, a dynamic SFI dynamically configuring the one or more semi-static flexible symbols of the slot or sub-slot as downlink, uplink, or flexible. The at least one processor and the memory are configured to decide, based on the SFI, whether to monitor for the acknowledgment feedback in the scheduled slot or sub-slot, in a subsequent slot or sub-slot, or both.

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

[0018] Other aspects, features, and embodiments of the application will become apparent to those of ordinary skill in the art, upon reviewing the description of specific example embodiments of the application in conjunction with the accompanying figures. While features may be discussed relative to certain example embodiments and figures below, all embodiments of the application can include one or more of the advantageous features discussed herein. In other words, while one or more BRIEF DESCRIPTION OF THE DRAWINGS

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

[0021] FIG. 2 is a block diagram illustrating an example logical architecture of a distributed RAN, in accordance with aspects of the present disclosure.

[0022] FIG. 3 is a diagram illustrating an example physical architecture of a distributed RAN, in accordance with aspects of the present disclosure.

[0023] FIG. 4 is a block diagram conceptually illustrating a design of an example BS and UE, in accordance with certain aspects of the present disclosure.

[0024] FIG. 5 FIG. 1 is a diagram illustrating an example of a frame structure for a wireless communication system.

[0025] FIG. 6 An example of a frame format for a new radio (NR) system is illustrated.

[0026] FIG. 7 An example of a semi-persistent scheduling (SPS) PDSCH occasion that can be used to activate a configured grant (CG) occasion is illustrated.

[0027] FIG. 8A An example timeline for delayed hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback is illustrated in accordance with aspects of the present disclosure.

[0028] FIG. 8B is a table illustrating example cases of a UE detecting (or missing) a slot format indicator (SFI) in accordance with aspects of the present disclosure.

[0029] FIG. 9 is a flow diagram of example operations that can be performed by a user equipment (UE) in accordance with aspects of the present disclosure.

[0030] FIG. 10 is a flow diagram of example operations that can be performed by a network entity in accordance with aspects of the present disclosure.

[0031] FIG. 11 illustrates a communications device that can include various components configured to perform operations for the techniques described herein in accordance with aspects of the present disclosure.

[0032] FIG. 12 FIG. 12 illustrates a communications device that can include various components configured to perform operations for the techniques described herein in accordance with aspects of the present disclosure.

[0033] To facilitate understanding, like reference numerals have been used, where possible, to designate like elements across the figures. It is contemplated that elements disclosed in one aspect can be beneficially utilized on other aspects without specific recitation.

[0034] DETAILED DESCRIPTION

[0035] Aspects of the present disclosure relate to wireless communication, and more particularly, to mechanisms and techniques for delaying and / or repeating hybrid automatic repeat request (HARQ) acknowledgements (ACKs) based on dynamic slot format indicator (SFI) monitoring.

[0036] 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).

[0037] NR can support various wireless communication services such as Enhanced Mobile Broadband (eMBB) targeting wide bandwidth (e.g. 80 MHz), millimeter wave (mmW) targeting high carrier frequency (e.g. 60 GHz), massive MTC (mMTC) targeting non-backward compatible MTC techniques, and / or mission critical targeting ultra reliable low latency communications (URLLC). These services can include latency and reliability requirements. These services can also have different transmission time intervals (TTI) to meet respective quality of service (QoS) requirements. In addition, these services can co-exist in the same subframe.

[0038] Due to the availability of large bandwidth, certain multi-beam wireless systems, such as mmW systems, bring gigabit speeds to cellular networks. However, the unique challenge of severe path loss faced by mmW systems requires new techniques such as hybrid beamforming (analog and digital) that do not exist in 3G and 4G systems. Hybrid beamforming can enhance the link budget / signal-to-noise ratio (SNR) that can be utilized during RACH.

[0039] In such systems, a NodeB (NB) and a user equipment (UE) can communicate using beamformed transmissions. In order for beamforming to work properly, the NB can need to monitor the beams using beam measurements performed at the UE (e.g., based on reference signals transmitted by the NB) and feedback generated. However, since the direction of the reference signals is unknown to the UE, the UE can need to evaluate several beams to obtain the best Rx beam for a given NB Tx beam. Accordingly, if the UE has to "sweep" through all of its Rx beams to perform the measurements (e.g., to determine the best Rx beam for a given NB Tx beam), the UE can incur significant measurement delay and battery life impact. Moreover, the resource efficiency of having to sweep through all Rx beams is extremely low. Accordingly, aspects of the present disclosure provide techniques to assist the UE when performing measurements of serving and neighboring cells when using Rx beamforming.

[0040] The following description provides examples, and is not limiting of the scope, applicability, or examples set forth in the claims. Changes can be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples can omit, substitute, or add various procedures or components as appropriate. For instance, the methods described can be performed in an order different than described, and various steps can be added, omitted, or combined. Also, features described with respect to some examples can be combined in some other examples. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover devices, methods, and programs made and performed using other equivalent structures, functionalities, and / or structures and functionalities. It is understood that any aspect of the disclosure disclosed herein can be implemented by one or more elements of a claim. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.

[0041] The techniques described herein can be used for 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 a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband-CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network can implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network can implement a radio technology such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). NR is an emerging wireless communications technology under development in conjunction with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named“3rd Generation Partnership Project” (3GPP). cdma2000 and UMB are described in documents from an organization named“3rd Generation Partnership Project 2” (3GPP2). The techniques described herein can be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, while aspects can be described herein using terminology commonly associated with 3G and / or 4G wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as 5G and later, including NR technologies.

[0042] Example Wireless System

[0043] FIG. 1 An example wireless network 100 in which aspects of the present disclosure can be performed is illustrated. For example, one or more UEs 120 of the wireless network 100 can be configured to perform operations 900 of FIG. 9 to decide how to report acknowledgment (ACK) feedback based on a monitored slot format indicator (SFI). Similarly, a base station 110 of the wireless network 100 can be configured to perform operations 1000 of FIG. 10 to transmit a dynamic SFI to a UE 120 (performing operations 900 of FIG. 9

[0044] As FIG. 1 ​As illustrated, the wireless network 100 can include a number of BSs 110 and other network entities. According to an example, network entities (including BSs and UEs) can communicate using beams at high frequencies (e.g., > 6 GHz).

[0045] A BS can be a station that communicates with UEs. Each BS 110 can provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can 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 term "cell" and gNB, Node B, 5G NB, AP, NR BS, NR BS, or TRP can be interchangeable. In some examples, a cell can not necessarily be stationary, and the geographic area of the cell can move according to the location of a mobile base station. In some examples, the base stations can be interconnected to one another and / or to one or more other base stations or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (such as a direct physical connection, a virtual network, or the like) using any suitable transport network.

[0046] Generally, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a particular radio access technology (RAT) and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, an air interface, etc. A frequency can also be referred to as a carrier, a frequency channel, etc. Each frequency channel can support one RAT so that the wireless networks using these RATs can operate without interfering with one another. In some cases, NR or 5G RAT networks can be deployed.

[0047] A BS can be a station that communicates with UEs. Each BS 110 can provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can 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 term "cell" and gNB, Node B, 5G NB, AP, NR BS, NR BS, or TRP can be interchangeable. In some examples, a cell can not necessarily be stationary, and the geographic area of the cell can move according to the location of a mobile base station. In some examples, the base stations can be interconnected to one another and / or to one or more other base stations or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (such as a direct physical connection, a virtual network, or the like) using any suitable transport network. FIG. 1In the example shown in FIG. 1, the BSs 110a, 110b and 110c can be macro BSs for the macro cells 102a, 102b and 102c, respectively. The BS 1 lOx can be a pico BS for a pico cell 102x. The BSs 1 lOy and 1 lOz can be femto BSs for the femto cells 102y and 102z, respectively. A BS can support one or multiple (e.g., three) cells.

[0048] Wireless network 100 can also include relay stations. A relay station is an entity that can receive a transmission of data and / or other information from an upstream station (e.g., a BS or a UE) and send a transmission of the data and / or other information to a downstream station (e.g., a UE or a BS). A relay station can be a UE that can also FIG. 1 In the example shown in FIG. 1, a relay station 1 lOr can communicate with the BS 1 lOa and a UE 120r in order to facilitate communications between the BS 1 lOa and the UE 120r. A relay station can also be referred to as a relay BS, a relay, etc.

[0049] Wireless network 100 can be a heterogeneous network that includes BSs of different types, e.g., macro BSs, pico BSs, femto BSs, relays, etc. These different types of BSs can have different transmit power levels, different coverage areas, and different impacts on interference in wireless network 100. For example, macro BSs can have a high transmit power level (e.g., 20 Watts) whereas pico BSs, femto BSs and relays can have a lower transmit power level (e.g., 1 Watt).

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

[0051] A network controller 130 can couple to a set of BSs and provide coordination and control for these BSs. Network controller 130 can be in communication with the BSs 110 via a backhaul. The BSs 110 can also communicate with one another, e.g., directly or indirectly via wireless or wireline backhaul.

[0052] The UEs 120 (e.g., 120x, 120y, etc.) can be dispersed throughout the wireless network 100, and each UE can be stationary or mobile. A UE can also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a Customer Premises Equipment (CPE), a cellular phone, a smart phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device such as a smart watch, smart clothing, smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet, etc.), an entertainment device (e.g., a music device, a video device, a satellite radio, etc.), a vehicular component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium. Some UEs can be considered 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., remote device), or some other entity. A wireless node can provide, for example, connectivity for 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.

[0053] In FIG. 1 solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS selected by the UE to serve the UE on the downlink and / or uplink. A dashed line with double arrows indicates transmissions between a UE and a BS, which can be interfered with.

[0054] Certain 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 partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing of adjacent subcarriers can be fixed, and the total number of subcarriers (K) can be dependent on the system bandwidth. For example, the spacing of the subcarriers can be 15 kHz and the minimum resource allocation (called a'resource block') can be 12 subcarriers (or 180 kHz). Consequently, the nominal FFT size can be equal to 128, 256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth can also be partitioned into subbands. For example, a subband can cover 1.08 MHz (i.e., 6 resource blocks), and there can be 1, 2, 4, 8, or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0055] While aspects of the examples described herein can be associated with LTE technologies, aspects of the present disclosure can be applicable with other wireless communications systems, such as NR.

[0056] NR can utilize OFDM with a CP on the uplink and downlink and include support for half-duplex operation using TDD. A single component carrier bandwidth of 100 MHz can be supported. An NR resource block can span 12 subcarriers with a subcarrier bandwidth of 75 kHz over a 0.1 ms duration. In one aspect, each radio frame can consist of 50 subframes with a length of 10 ms. Consequently, each subframe can have a length of 0.2 ms. In another aspect, each radio frame can consist of 10 subframes with a length of 10 ms, where each subframe can have a length of 1 ms. The link direction (i.e., DL or UL) for each subframe can be indicated by a scheduling grant. Each subframe can include DL / UL data as well as DL / UL control data. Beamforming can be supported and beam direction can be dynamically configured. MIMO transmissions with precoding can also be supported. MIMO configurations in the DL can support up to 8 transmit antennas (multi-layer downlink transmission with up to 8 streams) and up to 2 streams per UE. Multi-layer transmissions with up to 2 streams per UE can be supported. Aggregation of multiple cells can be supported with up to 8 serving cells. Alternatively, NR can support a different air interface other than OFDM.

[0057] In some examples, access to an air interface can be scheduled, where a scheduling entity (e.g., a base station) allocates resources for communication among some or all of the devices and equipment within its service area or cell. Within the present disclosure, as will be discussed further below, a scheduling entity can be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize resources allocated by the scheduling entity. Base stations are not the only entities that can function as a scheduling entity. That is, in some examples, a UE can function as a scheduling entity, scheduling resources for one or more subordinate entities (e.g., one or more other UEs). In this example, the UE is functioning as a scheduling entity, and other UEs utilize resources scheduled by the UE for wireless communication. A UE can function as a scheduling entity in a peer-to-peer (P2P) network and / or in a mesh network. In a mesh networking example, UEs can optionally communicate directly with one another in addition to communicating with a scheduling entity.

[0058] Thus, in a wireless communication network with 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 can utilize the scheduled resources for communication.

[0059] As mentioned above, a RAN can include a CU and a DU. An NR BS (e.g., gNB, 5G Node B, Node B, transmission reception point (TRP), access point (AP)) can correspond to one or more BSs. An NR cell can be configured as an access cell (Acell) or a data only cell (Dcell). For example, a RAN (e.g., central unit or distributed unit) can configure these cells. A Dcell can be a cell used for carrier aggregation or dual connectivity but not for initial access, cell selection / reselection, or handover. In some cases, a Dcell can not transmit a synchronization signal - in some cases, a Dcell can transmit an SS. An NR BS can transmit a downlink signal to a UE to indicate a cell type. Based on the cell type indication, the UE can communicate with the NR BS. For example, the UE can determine to consider the NR BS for cell selection, access, handover, and / or measurement based on the indicated cell type.

[0060] FIG. 2 An example logical architecture of a distributed radio access network (RAN) 200 is illustrated, which can be implemented in FIG. 1The wireless communications system illustrated in FIG. 3 can be implemented. The 5G access node 206 can include an access node controller (ANC) 202. The ANC can be a central unit (CU) of the distributed RAN 200. The backhaul interface to the next generation core network (NG-CN) 204 can terminate at the ANC. The backhaul interface to neighboring next generation access nodes (NG-ANs) can terminate at the ANC. The ANC can include one or more TRPs 208 (which can also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, or some other term). As described above, a TRP can be used interchangeably with "cell."

[0061] The TRPs 208 can be a DU. The TRPs can be connected to one ANC (ANC 202) or more than one ANC (not illustrated). For example, for RAN sharing, radio as a service (RaaS), and service specific AND deployments, TRPs can be connected to more than one ANC. A TRP can include one or more antenna ports. A TRP can be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.

[0062] The local architecture 200 can be used to illustrate a fronthaul definition. The architecture can be defined to support fronthauling solutions across different deployment

[0063] The architecture can share features and / or components with LTE. According to aspects, the next generation AN (NG-AN) 210 can support dual connectivity with NR. The NG-AN can share a common fronthaul for LTE and NR. According to aspects, the NG-AN can include the TRPs 208 connected to the ANC 202.

[0064] The architecture can enable cooperation between and among TRPs 208. For example, cooperation can be preset within a TRP and / or across TRPs via the ANC 202. According to aspects, no inter-TRP interface can be needed / present.

[0065] According to aspects, a dynamic configuration of split logical functions can be present within the architecture 200. As will be described in more detail FIG. 5 As will be described in more detail, the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and a Physical (PHY) layer can be adaptably placed at the DU or CU (e.g., TRP or ANC, respectively). According to certain aspects, a BS can include a central unit (CU) (e.g., ANC 202) and / or one or more distributed units (e.g., one or more TRPs 208).

[0066] FIG. 3An example physical architecture of a distributed RAN 300 is illustrated in accordance with aspects of the present disclosure. A centralized core network unit (C-CU) 302 can host core network functions. The C-CU can be centrally deployed. C-CU functionality can be offloaded (e.g., to advanced wireless services (AWS)), to handle peak capacity.

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

[0068] A DU 306 can host one or more TRPs (edge node (EN), edge unit (EU), radio head (RH), smart radio head (SRH), etc.). The DU can be located at edges of the network with radio frequency (RF) functionality.

[0069] FIG. 4 Example components of the BS 110 and UE 120, illustrated in FIG. 13B, can be used to implement the aspects of the present disclosure. The BS can include a TRP or gNB. FIG. 1 By way of example, one or more of the antennas 452, DEMOD / MOD 454, processors 466, 458, 464, and / or controller / processor 480 of the UE 120 can be configured to perform operations for the methods described herein (e.g., operations 900 of FIG. 9). Similarly, one or more of the antennas 434, DEMOD / MOD 432, processors 430, 420, 438, and / or controller / processor 440 of the BS 110 can be configured to perform operations for the methods described herein (e.g., operations 1000 of FIG. 10).

[0070] FIG. 9 By way of example, one or more of the antennas 452, DEMOD / MOD 454, processors 466, 458, 464, and / or controller / processor 480 of the UE 120 can be configured to perform operations for the methods described herein (e.g., operations 900 of FIG. 9). Similarly, one or more of the antennas 434, DEMOD / MOD 432, processors 430, 420, 438, and / or controller / processor 440 of the BS 110 can be configured to perform operations for the methods described herein (e.g., operations 1000 of FIG. 10). FIG. 10

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

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

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

[0074] On the uplink, at UE 120, a transmit processor 464 can receive and process data (e.g., for the physical uplink shared channel (PUSCH)) from a data source 462 and control information (e.g., for the physical uplink control channel (PUCCH) from the controller / processor 480. The transmit processor 464 can also generate reference symbols for a reference signal. The symbols from the transmit processor 464 can be precoded by a TX MIMO processor 466 if applicable, further processed by the 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 can be received by the antennas 434, processed by the modulators 432, detected by a MIMO detector 436 if applicable, and further processed by a receive processor 438 to obtain decoded data and control information sent by the UE 120. The receive processor 438 can provide the decoded data to a data sink 439 and to the controller / processor 440.

[0075] The controllers / processors 440 and 480 can direct the operation at the base station 110 and the UE 120, respectively. The scheduler 444 can schedule UEs for data transmission on the downlink and / or uplink. The processor 480 and / or other processors and modules at the UE 120 can perform or direct, e.g., the execution of the functions blocks, and / or processes for the techniques described herein and those illustrated in FIG. 8, and / or other processes for the techniques described herein and those illustrated in the figures. The processors 440 and / or other processors and modules at the BS 110 can perform or direct the execution of processes for the techniques described herein with reference to FIG. 9 The described techniques' processes and / or other processes for the techniques described herein and those illustrated in the figures. The memories 442 and 482 can store data and program codes for the BS 110 and the UE 120, respectively.

[0076] FIG. 5 A diagram 500 is illustrated showing examples for implementing a communication protocol stack in accordance with aspects of the present disclosure is illustrated. The illustrated communication protocol stack can be implemented by devices operating in a 5G system. The diagram 500 illustrates 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 medium access control (MAC) layer 525, and a physical (PHY) layer 530. In various examples, these layers of the protocol stack can be implemented as separate software modules, portions of a processor or ASIC, portions of non-co-located devices connected by a communication link, or various combinations thereof. Co-located and non-co-located implementations can be used, for example, in a protocol stack for a network access device (e.g., an AN, a CU, and / or a DU) or a UE.

[0077] A first option 505-a illustrates a split implementation of the protocol stack, where the implementation of the protocol stack is split between a centralized network access device (e.g., the ANC 202 in FIG. 2 , and a distributed network access device (e.g., the DU 208 in FIG. 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 can be useful in macrocell, microcell, or pico cell deployments.

[0078] A second option 505-b illustrates a unified implementation of the protocol stack, where the protocol stack is implemented in a single network access device (e.g., an access node (AN), a new radio base station (NR BS), a new radio NodeB (NR NB), a 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 can be useful in femtocell deployments.

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

[0080] FIG. 6 is a diagram illustrating an example of a frame format 600 for NR. The transmission timeline for each of the downlink and uplink can be partitioned into units of radio frames. Each radio frame can have a predetermined duration (e.g., 10 milliseconds) and can be partitioned into 10 subframes with indices of 0 through 9, each subframe being 1 millisecond. Each subframe can include a variable number of time slots, depending on the subcarrier spacing. Each time slot can include a variable number of symbol periods (e.g., 7 or 14 symbol periods), depending on the subcarrier spacing. Symbol periods in each time slot can be assigned indices. A mini-slot (which can be referred to as a sub-slot structure) refers to a transmission time interval having a duration that is less than a time slot (e.g., 2, 3, or 4 symbol periods).

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

[0082] In NR, a synchronization signal (SS) block is transmitted. The SS block consists of the PSS, SSS, and two symbols, PBCH. The SS block can be transmitted at fixed time slot positions (such as...). FIG. 6 The symbols 0-3 shown are transmitted. The PSS and SSS can be used by the UE for cell search and acquisition. The PSS provides half-frame timing, and the SS provides CP length and frame timing. The PSS and SSS provide cell identity. The PBCH carries basic system information such as downlink system bandwidth, timing information within the radio frame, SS burst set periodicity, system frame number, etc. SS blocks can be organized into SS bursts to support beam sweeping. Further system information (such as Residual Minimal System Information (RMSI), System Information Block (SIB), and Other System Information (OSI)) can be transmitted in certain subframes on the Physical Downlink Shared Channel (PDSCH).

[0083] The UE can operate in various radio resource configurations, including configurations associated with transmitting pilot signals using a dedicated resource set (e.g., Radio Resource Control (RRC) dedicated state) or configurations associated with transmitting pilot signals using a shared resource set (e.g., RRC shared state). When operating in RRC dedicated state, the UE can select a dedicated resource set for transmitting pilot signals to the network. When operating in RRC shared state, the UE can select a shared resource set for transmitting pilot signals to the network. In either case, the pilot signals transmitted by the UE can be received by one or more network access devices (such as AN, or DU, or portions thereof). Each receiving network access device can be configured to receive and measure pilot signals transmitted on the shared resource set, and also to receive and measure pilot signals transmitted on the dedicated resource set allocated to the UE, wherein the network access device is a member of a set of monitoring network access devices for that UE. One or more receiving network access devices, or a CU to which the receiving network access device transmits pilot signal measurements, can use these measurements to identify the UE's serving cell or initiate changes to the serving cell for one or more UEs.

[0084] Example SPS PDSCH configuration

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

[0086] like FIG. 7As illustrated in the middle, once preconfigured, if the UE is to receive an allocation of downlink resources, the allocation of SPS occasions will repeat according to the preconfigured periodicity, resulting in periodic SPS occasions. For SPS, the base station can use radio resource control (RRC) signaling to define the periodicity of the configured downlink assignments. Similarly, once configured with CG occasions, the allocation of CG occasions can repeat according to the preconfigured periodicity.

[0087] As used herein, the term occasion generally refers to a time in which resources are allocated for a transmission that can or can not ultimately occur. For example, a downlink transmission can or can not occur in an SPS occasion. Similarly, an uplink transmission can or can not occur in a CG occasion. If the transmission can occur, the occasion can be considered activated, and thus those occasions should be monitored.

[0088] Example conditions for delaying HARQ-ACK under dynamic SFI

[0089] Aspects of the present disclosure relate to wireless communications, and more particularly, to mechanisms and techniques for delaying hybrid automatic repeat request (HARQ) acknowledgements (ACKs) based on dynamic slot format indicator (SFI) monitoring. For example, a semi-persistently scheduled (SPS) HARQ-ACK report can be delayed according to the present disclosure due to a conflict with a dynamic SFI.

[0090] Currently, new radio (NR) can provide support for downlink (DL) SPS for periodic traffic. For time division duplex (TDD) systems (e.g., in Release 15 and / or Release 16), if a slot scheduled for reporting HARQ-ACK for SPS is a DL slot, or overlaps with at least one DL symbol, the UE will not transmit the HARQ-ACK. This can result in a waste of system resources, as the gNB can need to retransmit the SPS PDSCH due to having missed the HARQ-ACK report.

[0091] The overlap (e.g., overlap between a slot scheduled for reporting HARQ-ACK and a DL symbol or DL slot) can be due to various reasons. For example, a DL slot / symbol can be semi-statically configured as DL, or a slot / symbol can be converted from semi-static “flexible” to DL (or “dynamic flexible”) by a dynamic SFI or dynamic DL control information (DCI) (e.g., a DL grant scheduling a PDSCH or a grant scheduling an aperiodic channel state information reference signal (CSI-RS) transmission).

[0092] In other cases (e.g., in NR Rel-17), HARQ-ACK feedback for SPS PDSCH can be enhanced by delaying the HARQ-ACK feedback that collides (e.g., overlaps) with a DL symbol / slot (or “dynamic flexible” symbol) to a later uplink symbol / slot. For example, as shown in FIG. 8A FIG. 8A is an example timeline of delayed HARQ-ACK feedback, if SPS HARQ-ACK cannot be transmitted in the first slot or sub-slot (e.g., slots 802 and / or 804) due to collision (e.g., overlap) with a DL symbol / slot, the SPS HARQ-ACK can be delayed to the next (or later) slot / sub-slot (e.g., slot 806).

[0093] In NR, the cancellation of HARQ-ACK for SPS PDSCH can be due to several collision (e.g., resource overlap) cases (also referred to as conditions). For example, in a first case, the HARQ-ACK can collide with a semi-static DL symbol as determined according to at least one of the following configurations:

[0094] 1) a symbol indicated as downlink by TDD-ConfigurationCommon or TDD-UL-DL-ConfigDedicated;

[0095] 2) a symbol indicated to the UE by ssb-PositionInBurst in a system information block (SIB) (e.g., SIB1) or ServingCellConfigCommon for reception of SSB and / or physical broadcast control channel (PBCH) block; and / or

[0096] 3) a symbol indicated to the UE to receive control resource set (CORESET) 0 or a CORESET for Type 0 PDCCH common search space (CSS) set.

[0097] In a second case, the HARQ-ACK feedback can collide with a semi-static “flexible” symbol, but switched to a DL symbol by a dynamic scheduling DCI for the UE to receive a dynamic PDSCH (e.g., in a downlink grant) and / or a CSI-RS (e.g., in an uplink or downlink grant).

[0098] ​In a third scenario, the HARQ-ACK feedback can collide with semi-static flexible symbols, which can be switched to DL or “flexible” by a dynamic SFI indicator (e.g., DCI format 2 0) later. In this scenario (or the second scenario), a problem can arise if the UE misses (e.g., fails to receive) the SFI (in the third scenario) or the DCI (in the second scenario), and there can be a misunderstanding between the UE and the BS about the symbol direction (e.g., UL or DL) subsequently. In this scenario, the UE can cancel the HARQ-ACK feedback for the SPS PDSCH if the UE does not detect any SFI.

[0099] In a fourth scenario, the UE can be configured to monitor the SFI for a set of semi-static flexible symbol(s). The UE can be further configured such that if the UE does not detect the SFI during any of these symbols, the UE can cancel the HARQ-ACK feedback.

[0100] However, the dynamic SFI is typically a group-common DCI, and it can be difficult for the gNB to guarantee that every entity in the group correctly receives the SFI (e.g., more difficult than guaranteeing that one UE correctly receives the SFI). Thus, the reliability of the SFI can not be as high as that of the dynamic scheduling DCI. This is particularly true for massive multiple-input multiple-output (MIMO) millimeter wave (mmW) systems, where the dynamic scheduling DCI can be transmitted on UE-specific beams, while the SFI can only be transmitted using wider (e.g., non-UE-specific) beams.

[0101] In particular, for the third scenario described above, if the UE misses (e.g., fails to receive) the SFI, there can be a misunderstanding between the UE and the network entity about the symbol direction (e.g., UL or DL), which can cause error propagation not only in the current slot but also in subsequent slots due to the delayed HARQ-ACK feedback.

[0102] In some scenarios, the UE can be configured to monitor the dynamic SFI, and at least one symbol of a physical uplink control channel (PUCCH) for HARQ-ACK reporting (e.g., feedback) of the SPS PDSCH is semi-statically configured as a “flexible” symbol. As FIG. 8B As shown, depending on whether the network transmits the SFI with a DL or flexible symbol, a UL symbol, or not at all, and whether the UE successfully receives the SFI, there are six different scenarios (e.g., A, B, C, D, E, “will not happen”), and five of them are actually possible (e.g., it will not be possible for the UE to detect the SFI when the gNB does not transmit it). In some scenarios, the UE can only cancel the HARQ-ACK feedback if the UE does not detect the SFI. FIG. 8BHARQ-ACK feedback for SPS PDSCH in Case B. That is, the gNB transmits and the UE detects a dynamic SFI indicating that all semi-statically configured “flexible” symbols are “uplink” symbols, as shown.

[0103] However, in some approaches, the HARQ-ACK feedback can be delayed whenever the UE detects an SFI indicating “DL” (or “flexible”) (i.e., in Case A of FIG. 8B ), or if the UE misses the SFI (i.e., in Cases C, D, E of FIG. 8A ). For Case D, the gNB cannot be certain whether the UE has received the SFI. Thus, the current HARQ-ACK feedback delay design can result in inconsistent behavior between the gNB and the UE. In other words, the gNB can not expect the delay, but the UE can still delay. This can be problematic because the UE will drop the HARQ-ACK feedback transmission in the current slot, resulting in an error in receiving the HARQ-ACK feedback at the gNB. Moreover, when the UE delays the HARQ-ACK to the next slot, the delay will also impact the HARQ-ACK reporting (and other uplink communications) in the next slot. Thus, delaying the HARQ-ACK (e.g., in Cases A, C, D, E of FIG. 8B ) can cause error propagation, and delaying the HARQ-ACK should be avoided to ensure the reliability of the HARQ-ACK feedback reporting for SPS PDSCH.

[0104] Accordingly, aspects of the disclosure provide mechanisms and techniques to delay and / or repeat HARQ-ACK based on dynamic SFI monitoring. For example, monitoring the dynamic SFI and deciding whether to report the HARQ-ACK feedback based on the monitoring can help ensure consistent behavior between the gNB and the UE, and avoid the above-mentioned errors or error propagation.

[0105] FIG. 9 An example operation 900 for wireless communication by a UE is illustrated. The operation 900 can be performed, for example, by a UE (e.g., the UE 120 of FIG. 1 and 4 to delay HARQ-ACK based on dynamic SFI monitoring.

[0106] The operation 900 begins, at 902, by identifying a slot or sub-slot scheduled for reporting acknowledgement feedback for SPS PDSCH. At 904, the UE identifies that one or more symbols of the identified slot or sub-slot scheduled to transmit a PUCCH containing the acknowledgement feedback are semi-statically flexible symbols.

[0107] At 906, the UE monitors for a dynamic SFI that dynamically configures one or more of the semi-static flexible symbols of the slot or sub-slot as downlink, uplink, or flexible. At 908, the UE decides, based on the monitoring, whether to report the acknowledgment feedback in the scheduled slot or sub-slot, in a subsequent slot or sub-slot, or both.

[0108] FIG. 10 Example operations 1000 that can be performed by a network entity and can be considered complementary to the operations 900 of FIG. 9 . For example, the operations 1000 can be performed by a gNB (e.g., the gNB 110 of FIG. 1 and FIG. 4 ) to transmit a dynamic SFI to a UE (e.g., the UE performing the operations 900). FIG. 9

[0109] The operations 1000 begin, at 1002, by transmitting, to a UE, an SPS PDSCH. At 1004, the network entity identifies a slot or sub-slot scheduled for the UE to report acknowledgment feedback for the SPS PDSCH. At 1006, the network entity identifies that one or more symbols of the identified slot or sub-slot scheduled to transmit a PUCCH containing the acknowledgment feedback are semi-static flexible symbols.

[0110] At 1008, the network entity transmits, to the UE, a dynamic SFI that dynamically configures one or more of the semi-static flexible symbols of the slot or sub-slot as downlink, uplink, or flexible. At 1010, the network entity decides, based on the SFI, whether to monitor for the acknowledgment feedback in the scheduled slot or sub-slot, in a subsequent slot or sub-slot, or both.

[0111] In some cases, it can be assumed that the UE is configured to monitor for a dynamic SFI (e.g., DCI Format 2 0) and transmit a PUCCH with HARQ-ACK for the SPS PDSCH in the slot / sub-slot without a corresponding PDCCH. Further, it can be assumed that at least one symbol of the PUCCH is semi-statically configured as a “flexible” symbol.

[0112] In a first general aspect of the disclosure, a UE can transmit a PUCCH in a slot or sub-slot (e.g., a slot / sub-slot 1102 as shown in FIG. 8B ) and repeat transmission of HARQ-ACK for the SPS PDSCH in a second / later slot (e.g., a next slot / sub-slot 1104) if the UE receives a dynamic SFI (e.g., Case B of FIG. 11A ) indicating all semi-static “flexible” symbols as “uplink.” That is, in the case of a dynamic SFI indicating all semi-static “flexible” symbols as “uplink,” the UE transmits a PUCCH in the slot / sub-slot (e.g., a slot / sub-slot 1102 as shown in FIG. 8B ​In scenario B, the UE may transmit HARQ-ACK feedback for SPSPDSCH twice: once in the current time slot and once in the second time slot (e.g., time slot / sub-time slot 1102, 1104) (with delayed transmission).

[0113] In some cases, if the UE loses SFI (e.g., FIG. 8B Cases C, D, or E), or if the UE receives an indication that at least one symbol in the semi-static flexible symbol is a "downlink" or "flexible" dynamic SFI (e.g., FIG. 8B In scenario A), the UE can cancel the HARQ-ACK feedback in the current time slot (e.g., time slot 1108) and delay the HARQ-ACK transmission to the next time slot (e.g., time slot 1110). As shown, the UE can choose not to transmit the HARQ-ACK feedback in time slot 1112, since time slot 1112 is a downlink time slot. Therefore, in some examples, regardless of whether the UE receives a dynamic SFI, and / or regardless of the content of the dynamic SFI itself, the UE can always transmit the delayed HARQ-ACK in the next (or future) time slot. For example, the UE can cancel reporting the HARQ-ACK in the time slot used for SPS PDSCH and delay the HARQ-ACK to a subsequent time slot or sub-time slot. Doing so helps ensure the reliability of the delayed HARQ-ACK feedback and other HARQ-ACK transmissions in the next time slot.

[0114] In some scenarios, if the corresponding PUCCH resource used to send HARQ-ACK feedback (e.g., for delayed HARQ-ACK and / or regular HARQ-ACK in the second time slot) conflicts with semi-static "flexible" symbols in the second time slot, the UE can use the techniques described above to cancel or delay the HARQ-NACK feedback. That is, if the UE receives an SFI indicating that a semi-static "flexible" symbol is converted to "uplink" (e.g., the same SFI), the UE can transmit delayed HARQ-ACK feedback in the second time slot and repeat the transmission in the third time slot. Additionally or alternatively, the gNB can configure the UE to have a maximum number of times HARQ-ACK can be repeated and / or a maximum number of time slots in which HARQ-ACK transmission can be delayed. In this way, the repetition (of HARQ-ACK feedback) will end in a single time slot where all symbols used for PUCCH transmission are semi-static uplink symbols.

[0115] In a second general aspect of this disclosure, the UE can cancel the current time slot regardless of whether it receives a dynamic SFI (e.g., FIG. 11BThe PUCCH transmission in time slot 1114 or time slot 1116. In other words, as long as at least one symbol of the PUCCH transmission containing HARQ-ACK feedback is a semi-static flexible symbol, the UE will cancel the transmission in the current time slot / sub-time slot and delay it to the next available time slot / sub-time slot.

[0116] Based on this aspect, the UE can then delay the HARQ-ACK feedback for SPS PDSCH transmission to a later time slot / sub-slot (e.g., FIG. 11B In time slots 1118 or 1120, all symbols corresponding to the PUCCH resource are semi-statically configured as "uplink" symbols. As shown, similar to... FIG. 11A In time slot 1112, the UE may not transmit HARQ-ACK feedback in time slot 1122, because time slot 1122 is a downlink time slot. In some cases according to this general aspect, each HARQ-ACK feedback will be transmitted only once (i.e., no duplication).

[0117] FIG. 12 The description includes operations that may be configured to perform the techniques disclosed herein (such as...). FIG. 9 The communication device 1200 comprises various components (e.g., corresponding to device plus functional components) of the operation described herein. The communication device 1200 includes a processing system 1202 coupled to a transceiver 1208. The transceiver 1208 is configured to transmit and receive signals (such as the various signals described herein) for the communication device 1200 via an antenna 1210. The processing system 1202 may be configured to perform processing functions for the communication device 1200, including processing signals received and / or to be transmitted by the communication device 1200.

[0118] Processing system 1202 includes processor 1204 coupled to computer-readable medium / memory 1212 via bus 1206. In some aspects, computer-readable medium / memory 1212 is configured to store instructions (e.g., computer-executable code) that, when executed by processor 1204, cause processor 1204 to perform. FIG. 9The computer-readable medium / memory 1212 includes instructions 1214 for identifying a slot or sub-slot scheduled for reporting acknowledgement feedback for a SPS PDSCH; instructions 1216 for identifying that one or more symbols of the identified slot or sub-slot scheduled to transmit a PUCCH containing the acknowledgement feedback are semi-static flexible symbols; instructions 1218 for monitoring for a dynamic SFI that dynamically configures one or more of the semi-static flexible symbols of the slot or sub-slot as downlink, uplink, or flexible; and instructions 1220 for deciding, based on the monitoring, whether to report the acknowledgement feedback in the scheduled slot or sub-slot, in a subsequent slot or sub-slot, or both. In certain aspects, the processor 1204 has circuitry configured to implement the instructions stored in the computer-readable medium / memory 1212. The processor 1204 includes circuitry 1222 for identifying a slot or sub-slot scheduled for reporting acknowledgement feedback for a SPS PDSCH; circuitry 1224 for identifying that one or more symbols of the identified slot or sub-slot scheduled to transmit a PUCCH containing the acknowledgement feedback are semi-static flexible symbols; circuitry 1226 for monitoring for a dynamic SFI that dynamically configures one or more of the semi-static flexible symbols of the slot or sub-slot as downlink, uplink, or flexible; and circuitry 1228 for deciding, based on the monitoring, whether to report the acknowledgement feedback in the scheduled slot or sub-slot, in a subsequent slot or sub-slot, or both.

[0119] FIG. 13 The communications device 1300 illustrates various components (e.g., corresponding to means-plus-function components) configured to perform the operations for the techniques disclosed herein, such as FIG. 10 The communications device 1300 includes a processing system 1302 coupled to a transceiver 1308. The transceiver 1308 is configured to transmit and receive signals for the communications device 1300 via an antenna 1310, such as the various signals as described herein. The processing system 1302 can be configured to perform processing functions for the communications device 1300, including processing signals received and / or to be transmitted by the communications device 1300.

[0120] The processing system 1302 includes a processor 1304 coupled to a computer- readable medium / memory 1312 via a bus 1306. In certain aspects, the computer-readable medium / memory 1312 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 1304, cause the processor 1304 to perform FIG. 10The operations described or illustrated herein or other operations for implementing the various techniques discussed herein. In certain aspects, the computer-readable medium / memory 1312 stores code 1314 for transmitting, to a UE, an SPS PDSCH; code 1316 for identifying a slot or sub-slot scheduled for the UE to report acknowledgement feedback for the SPS PDSCH; code 1318 for identifying that one or more symbols of the identified slot or sub-slot scheduled to transmit a PUCCH containing the acknowledgement feedback are semi-static flexible symbols; code 1320 for sending, to the UE, a dynamic slot format indicator (SFI) that dynamically configures the one or more semi-static flexible symbols of the slot or sub-slot as downlink, uplink, or flexible; and code 1322 for deciding, based on the SFI, whether to monitor for the acknowledgement feedback in the scheduled slot or sub-slot, in a subsequent slot or sub-slot, or both. In certain aspects, the processor 1304 has circuitry configured to implement code stored in the computer-readable medium / memory 1312. The processor 1304 includes circuitry 1324 for transmitting, to a UE, an SPS PDSCH; circuitry 1326 for identifying a slot or sub-slot scheduled for the UE to report acknowledgement feedback for the SPS PDSCH; circuitry 1328 for identifying that one or more symbols of the identified slot or sub-slot scheduled to transmit a PUCCH containing the acknowledgement feedback are semi-static flexible symbols; circuitry 1330 for sending, to the UE, a dynamic slot format indicator (SFI) that dynamically configures the one or more semi-static flexible symbols of the slot or sub-slot as downlink, uplink, or flexible; and circuitry 1332 for deciding, based on the SFI, whether to monitor for the acknowledgement feedback in the scheduled slot or sub-slot, in a subsequent slot or sub-slot, or both.

[0121] Example Aspects

[0122] Aspect 1 : A method for wireless communications by a user equipment, comprising: identifying a slot or sub-slot scheduled for reporting acknowledgement feedback for a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH); identifying that one or more symbols of the identified slot or sub-slot scheduled to transmit a physical uplink control channel (PUCCH) containing the acknowledgement feedback are semi-static flexible symbols; monitoring for a dynamic slot format indicator (SFI) that dynamically configures the one or more semi-static flexible symbols of the slot or sub-slot as downlink, uplink, or flexible; and deciding, based on the monitoring, whether to report the acknowledgement feedback in the scheduled slot or sub-slot, in a subsequent slot or sub-slot, or both.

[0123] Aspect 2: The method of aspect 1, wherein if the UE receives a dynamic SFI indicating all of the semi-static flexible symbols of a slot or sub-slot as uplink, the UE decides to report the acknowledgment feedback in the scheduled slot and to repeat reporting the acknowledgment feedback in a subsequent slot or sub-slot.

[0124] Aspect 3: The method of any of aspects 1-2, wherein if the UE does not detect a dynamic SFI, the UE decides to cancel the acknowledgment feedback in the scheduled slot or sub-slot and to report the acknowledgment feedback in a subsequent slot or sub-slot.

[0125] Aspect 4: The method of any of aspects 1-3, wherein if the UE receives a dynamic SFI indicating at least one of the semi-static flexible symbols is downlink or flexible, the UE decides to cancel the acknowledgment feedback in the scheduled slot or sub-slot and to report the acknowledgment feedback in a subsequent slot or sub-slot.

[0126] Aspect 5: The method of any of aspects 1-4, further comprising receiving a configuration indicating at least one of: a maximum number of reports of the acknowledgment feedback that can be repeated by the UE; or a maximum number of slots for which reporting of the acknowledgment feedback can be delayed.

[0127] Aspect 6: The method of any of aspects 1-5, wherein the UE is configured to cancel reporting the acknowledgment feedback in the identified slot or sub-slot and to delay the acknowledgment feedback to a subsequent slot or sub-slot regardless of what the UE receives in the SFI or whether the UE receives or fails to receive the SFI.

[0128] Aspect 7: The method of aspect 6, wherein the UE delays the acknowledgment feedback to a slot or sub-slot in which all symbols of a resource of a PUCCH for reporting the acknowledgment feedback are semi-statically configured as uplink symbols.

[0129] Aspect 8: A method for wireless communications by a network entity, comprising: transmitting, to a user equipment (UE), a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH); identifying a slot or sub-slot scheduled for the UE to report acknowledgment feedback for the SPS PDSCH; identifying that one or more symbols of the identified slot or sub-slot scheduled to transmit a physical uplink control channel (PUCCH) containing the acknowledgment feedback are semi-static flexible symbols; sending, to the UE, a dynamic slot format indicator (SFI) dynamically configuring the one or more semi-static flexible symbols of the slot or sub-slot as downlink, uplink, or flexible; and deciding, based on the SFI, whether to monitor for the acknowledgment feedback in the scheduled slot or sub-slot, in a subsequent slot or sub-slot, or both.

[0130] Aspect 9: The method of aspect 8, wherein the network entity decides to monitor for acknowledgment feedback in the scheduled slot if all of the semi-statically flexible symbols of the dynamic SFI indicated slot or sub-slot are decided to be uplink, and also monitors for acknowledgment feedback in a subsequent slot or sub-slot.

[0131] Aspect 10: The method of any of aspects 8-9, wherein the network entity decides to monitor for acknowledgment feedback in a subsequent slot or sub-slot regardless of what the SFI indicates, if the network entity decides to monitor for acknowledgment feedback in the subsequent slot or sub-slot.

[0132] Aspect 11: The method of any of aspects 8-10, wherein if the dynamic SFI indicates that at least one semi-statically flexible symbol is downlink or flexible: the network entity does not monitor for acknowledgment feedback in the scheduled slot or sub-slot; and the network entity monitors for acknowledgment feedback in a subsequent slot or sub-slot.

[0133] Aspect 12: The method of any of aspects 8-11, further comprising signaling, to the UE, a configuration indicating at least one of: a maximum number of reports of acknowledgment feedback that can be repeated by the UE; or a maximum number of slots for which a report of acknowledgment feedback can be delayed.

[0134] Aspect 13: The method of any of aspects 8-12, wherein: the UE is configured to cancel reporting acknowledgment feedback in the identified slot or sub-slot and delay to a subsequent slot or sub-slot regardless of what the UE receives in the SFI or whether the UE receives or fails to receive the SFI; and the network entity is configured to monitor for acknowledgment feedback in the subsequent slot or sub-slot.

[0135] Aspect 14: The method of aspect 13, wherein the network entity is configured to monitor for acknowledgment feedback in a slot or sub-slot in which all symbols of a resource of a PUCCH for reporting the acknowledgment feedback are semi-statically configured to be uplink symbols.

[0136] Aspect 15: An apparatus for wireless communication by a user equipment, comprising: means for identifying a slot or sub-slot scheduled for reporting acknowledgment feedback for a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH); means for identifying that one or more symbols of the identified slot or sub-slot scheduled to transmit a physical uplink control channel (PUCCH) containing acknowledgment feedback are semi-statically flexible symbols; means for monitoring a dynamic slot format indicator (SFI) that dynamically configures one or more semi-statically flexible symbols of the slot or sub-slot to be downlink, uplink, or flexible; and means for deciding, based on the monitoring, whether to report the acknowledgment feedback in the scheduled slot or sub-slot, in a subsequent slot or sub-slot, or both.

[0137] Aspect 16: A user equipment (UE) for wireless communication, comprising: at least one processor and a memory configured to: identify a slot or sub-slot scheduled for reporting acknowledgment feedback for a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH); identify that one or more symbols of the identified slot or sub-slot scheduled to transmit a physical uplink control channel (PUCCH) containing the acknowledgment feedback are semi-statically flexible symbols; monitor for a dynamic slot format indicator (SFI) that dynamically configures the one or more semi-statically flexible symbols of the slot or sub-slot as downlink, uplink, or flexible; and decide, based on the monitoring, whether to report the acknowledgment feedback in the scheduled slot or sub-slot, in a subsequent slot or sub-slot, or both.

[0138] Aspect 17: The UE of aspect 16, wherein the at least one processor and the memory are further configured to: if the UE receives a dynamic SFI indicating all of the semi-statically flexible symbols of the slot or sub-slot as uplink, decide to report the acknowledgment feedback in the scheduled slot and repeat reporting the acknowledgment feedback in a subsequent slot or sub-slot.

[0139] Aspect 18: The UE of aspect 16, wherein if the UE does not detect a dynamic SFI, the UE decides to cancel the acknowledgment feedback in the scheduled slot or sub-slot and report the acknowledgment feedback in a subsequent slot or sub-slot.

[0140] Aspect 19: The UE of aspect 16, wherein if the UE receives a dynamic SFI indicating at least one of the semi-statically flexible symbols is downlink or flexible, the UE decides to cancel the acknowledgment feedback in the scheduled slot or sub-slot and report the acknowledgment feedback in a subsequent slot or sub-slot.

[0141] Aspect 20: The UE of aspect 16, wherein the at least one processor and the memory are further configured to receive a configuration indicating at least one of: a maximum number of reports of the acknowledgment feedback that can be repeated by the UE; or a maximum number of slots that a report of the acknowledgment feedback can be delayed.

[0142] Aspect 21: The UE of aspect 16, wherein the at least one processor and the memory are further configured to cancel reporting the acknowledgment feedback in the identified slot or sub-slot and delay the acknowledgment feedback to a subsequent slot or sub-slot regardless of what the UE receives in the SFI or whether the UE receives or fails to receive the SFI.

[0143] Aspect 22: The UE of aspect 21, wherein the UE delays reporting the acknowledgment feedback to a slot or sub-slot in which all symbols of a resource of a PUCCH for reporting the acknowledgment feedback are semi-statically configured as uplink symbols.

[0144] Aspect 23: The UE of aspect 21, wherein the at least one processor and the memory are further configured to cancel reporting the acknowledgement feedback in the scheduled slot or sub-slot, in a subsequent slot or sub-slot, or both, based on deciding whether to report the acknowledgement feedback regardless of the SFI.

[0145] Aspect 24: A network entity for wireless communication, comprising: at least one processor and a memory configured to: transmit, to a user equipment (UE), a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH); identify a slot or sub-slot scheduled for the UE to report acknowledgement feedback for the SPS PDSCH; identify that one or more symbols of the identified slot or sub-slot scheduled to transmit a physical uplink control channel (PUCCH) containing the acknowledgement feedback are semi-static flexible symbols; send, to the UE, a dynamic slot format indicator (SFI) that dynamically configures one or more semi-static flexible symbols of the slot or sub-slot as downlink, uplink, or flexible; and decide, based on the SFI, whether to monitor for the acknowledgement feedback in the scheduled slot or sub-slot, in a subsequent slot or sub-slot, or both.

[0146] Aspect 25: The network entity of aspect 24, wherein the network entity decides to monitor for the acknowledgement feedback in the scheduled slot if the dynamic SFI indicates all semi-static flexible symbols of the slot or sub-slot as uplink, and also monitors for the acknowledgement feedback in a subsequent slot or sub-slot.

[0147] Aspect 26: The network entity of aspect 24, wherein the network entity decides to monitor for the acknowledgement feedback in a subsequent slot or sub-slot regardless of what the SFI indicates if the network entity decides to monitor for the acknowledgement feedback in the subsequent slot or sub-slot.

[0148] Aspect 27: The network entity of aspect 24, wherein if the dynamic SFI indicates that at least one semi-static flexible symbol is downlink or flexible: the network entity does not monitor for the acknowledgement feedback in the scheduled slot or sub-slot; and the network entity monitors for the acknowledgement feedback in a subsequent slot or sub-slot.

[0149] Aspect 28: The network entity of aspect 24, wherein the at least one processor and the memory are configured to signal, to the UE, a configuration indicating at least one of: a maximum number of reports of the acknowledgement feedback that can be repeated by the UE; or a maximum number of slots for which reporting of the acknowledgement feedback can be delayed.

[0150] Aspect 29: The network entity of aspect 24, wherein: the UE is configured to cancel reporting the acknowledgement feedback in the identified slot or sub-slot and delay to a subsequent slot or sub-slot regardless of what the UE receives in the SFI or whether or not the UE receives the SFI, the network entity is configured to monitor for the acknowledgement feedback in the subsequent slot or sub-slot.

[0151] Aspect 30: The method of aspect 29, wherein the at least one processor and the memory are configured to monitor for acknowledgment feedback in slots or sub-slots in which all symbols of a resource of a PUCCH for reporting the acknowledgment feedback are semi-statically configured as uplink symbols.

[0152] Aspect 31: An apparatus for wireless communication comprising means for performing one or more methods of claims 1-14.

[0153] Aspect 32: A computer-readable medium, comprising instructions to cause a processing system to perform one or more methods of claims 1-14.

[0154] The methods disclosed herein comprise one or more steps or actions for achieving the described method. The method steps and / or actions can be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order is specified, the order and / or use of terms can be modified without departing from the scope of the claims.

[0155] As used herein, the term “at least one of’ a set of items refers to any combination of one or more items from the set. As an example, “at least one of a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination of items from among a, b, and c (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

[0156] As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” can include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, “determining” can include resolving, selecting, choosing, establishing and the like.

[0157] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will readily be understood by those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be granted the full scope consistent with the language of the claims, wherein references to the singular form of an element are not intended to mean “one and only one” (unless specifically stated otherwise) but “one or more.” Unless specifically stated otherwise, the term “some / a” refers to one or more. All structural and functional equivalents of the aspects described throughout this disclosure that are now or hereafter known to a person skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be donated to the public, whether or not such disclosure is expressly stated in the claims. No element of a claim should be interpreted under the provisions of 35 U.S.SC §112, paragraph 6, unless the element is expressly stated using the phrase “means for…” or, in the case of a method claim, the element is stated using the phrase “steps for…”.

[0158] The various operations of the methods described above can be performed by any suitable means capable of performing the corresponding functions. These means may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors. Generally, where the operations illustrated in the figures are present, these operations may have corresponding paired means with similar numbering plus functional components. For example, FIG. 4 The processors 458, 464, and 466 of the UE 120 and / or the controller / processor 480, and / or the processors 420, 430, and 438 of the BS 110 and / or the controller / processor 440, shown herein, may be configured to perform FIG. 9 Operation 900 and / or FIG. 10 Operation 1000.

[0159] The receiving device may include FIG. 4 The receiver described herein (such as one or more antennas and / or a receiver processor). Similarly, the means for transmission may include... FIG. 4 The transmitters described herein (such as one or more antennas and / or a transmission processor). Devices for monitoring, indication, signaling, activation, and deactivation may include processing systems, which may include one or more processors, such as... FIG. 4The processors 458, 464, 466 of the UE 120, the controller / processor 480 of the UE 120, and / or the processors 420, 430, 438 of the BS 110, the controller / processor 440 of the BS 110, and / or the processors 458, 464, 466 and / or controller / processor 480 of the UE 120 and / or the processors 420, 430, 438 and / or controller / processor 440 of the BS 110 described herein can be used to perform one or more aspects of the disclosure.

[0160] In some cases, a device can not actually transmit frames, but can have an interface for outputting frames for transmission (a means for outputting). For example, a processor can output frames to a radio frequency (RF) front end via a bus interface for transmission. Similarly, a device can not actually receive frames, but can have an interface for obtaining frames received from another device (a means for obtaining). For example, a processor can obtain (or receive) frames from an RF front end via a bus interface for reception.

[0161] The various illustrative logical blocks, modules, and circuits described in connection with the disclosure can be implemented or performed 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 can be a microprocessor, but in the alternative, the processor can be any commercially available processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0162] If implemented in hardware, an example hardware configuration can comprise a processing system in a wireless node. The processing system can be implemented with a bus architecture. The bus can include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints. The bus can link together various circuits including processors, machine-readable media, and buses themselves. A bus interface can be used to connect a network adapter to the processing system via the bus. The network adapter can be used to implement signal processing functionality for the PHY layer. In the case of user terminal 120 (see FIG. 1), a user interface (e.g., keypad, display, mouse, joystick, etc.) can also be connected to the bus. The bus can also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore will not be described any further. The processor can be implemented with one or more general-purpose and / or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Depending on the specific application of the processing system and the overall design constraints, those of skill in the art will recognize the best way to implement the functions described with respect to the processing system. FIG. 1 ) can also be connected to the bus. The bus can also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore will not be described any further. The processor can be implemented with one or more general-purpose and / or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Depending on the specific application of the processing system and the overall design constraints, those of skill in the art will recognize the best way to implement the functions described with respect to the processing system.

[0163] If implemented in software, the functions can be stored or transmitted over as one or more instructions or code on a computer-readable medium. Software shall be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media include both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. The processor can be responsible for managing the bus and general processing, including the execution of software modules stored on the machine-readable storage media. A computer-readable storage medium can be coupled with the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral with the processor. By way of example, the machine-readable media can include a transmission line, a carrier wave modulated by data, and / or a computer readable storage medium with instructions stored thereon separate from the wireless node, all of which can be accessed via the bus. Alternatively, or in addition, the machine-readable media, or any portion thereof, can be integrated with the processor, such as the case can be with cache and / or general register files. Examples of machine-readable storage media can include, by way of example, 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 medium, or any combination thereof. The machine-readable media can be embodied in a computer-program product.

[0164] A software module can comprise a single instruction, or many instructions, and can be distributed over several different code segments, among different programs, and across multiple storage media. The computer-readable media can comprise a number of software modules. The software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions. The software modules can include a transmission module and a receiving module. Each software module can reside in a single storage device or be distributed across multiple storage devices. By way of example, a software module can be loaded into RAM from a hard drive when a triggering event occurs. During execution of the software module, the processor can load some of the instructions into cache to increase access speed. One or more cache lines can then be loaded into a general register file for execution by the processor. When referring to the functionality of a software module below, it will be understood that such functionality is implemented by the processor when executing instructions from that software module.

[0165] Also, 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, 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 Blu-ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Thus, in some aspects computer-readable media can comprise non-transitory computer-readable media (e.g., tangible media). In addition, for other aspects computer-readable media can comprise transitory computer- readable media (e.g., a signal). Combinations of the above should also be included within the scope of computer-readable media.

[0166] Thus, certain aspects can comprise a computer program product for performing the operations presented herein. For example, such a computer program product can comprise a computer-readable medium having instructions stored thereon, the instructions being executable by one or more processors to perform the operations described herein. For example, instructions for performing the operations described herein and illustrated in the figures.

[0167] Further, it should be appreciated that modules and / or other appropriate means for performing the methods and techniques described herein can be downloaded and / or otherwise obtained by a user terminal and / or base station as applicable. For example, such a device can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, various methods described herein can be provided via a storage means (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.), such that a user terminal and / or base station can obtain the various methods upon coupling or providing the storage means to the device.

[0168] It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes, and variations can be made in the method 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: The identifier is used to report the time slot or sub-time slot for receiving feedback for the Semi-Persistent Scheduling (SPS) Physical Downlink Shared Channel (PDSCH); One or more symbols that are scheduled to transmit the Physical Uplink Control Channel (PUCCH) containing the received feedback in the identified time slot or sub-time slot are semi-static flexible symbols. The monitoring dynamically configures one or more of the semi-static flexible symbols in the time slot or sub-time slot as downlink, uplink, or flexible dynamic time slot format indicator (SFI); and The monitoring determines whether the confirmation feedback should be reported in the scheduled time slot or sub-time slot, in a subsequent time slot or sub-time slot, or both.

2. The method of claim 1, wherein if the UE receives the dynamic SFI indicating all semi-static flexible symbols of the time slot or sub-time slot as uplink, the UE decides to report the confirmation feedback in the scheduled time slot.

3. The method of claim 2, wherein the UE decides to repeat the receipt feedback in a subsequent time slot or sub-time slot.

4. The method of claim 1, wherein if the UE does not detect the dynamic SFI, the UE decides to cancel the confirmation feedback in the scheduled time slot or sub-time slot and reports the confirmation feedback in the subsequent time slot or sub-time slot.

5. The method of claim 1, wherein if the UE receives an indication that at least one of the semi-static flexible symbols is a downlink or a flexible dynamic SFI, the UE decides to cancel the confirmation feedback in the scheduled time slot or sub-time slot and reports the confirmation feedback in the subsequent time slot or sub-time slot.

6. The method of claim 1, further comprising receiving a configuration indicating at least one of the following: The maximum number of times the confirmed feedback report can be repeated by the UE; or The maximum number of time slots that the confirmed feedback report can be delayed.

7. The method of claim 1, wherein the UE is configured to cancel reporting the reception feedback in the identified time slot or sub-time slot and delay it to a subsequent time slot or sub-time slot, regardless of what the UE receives in the SFI or whether the UE receives or fails to receive the SFI.

8. The method of claim 7, wherein the UE reports the receipt feedback delayed until all symbols of the resource for which the PUCCH is used to report the receipt feedback are semi-statically configured as uplink symbol slots or sub-slots.

9. The method of claim 7, further comprising: Cancel reporting the received feedback in the identified time slot or sub-time slot; as well as The confirmation feedback is delayed to a subsequent time slot or sub-time slot.

10. A method for wireless communication by a network entity, comprising: Transmit Semi-Persistent Scheduling (SPS) Physical Downlink Shared Channel (PDSCH); The time slot or sub-slot that is scheduled for User Equipment (UE) to report confirmation feedback for the SPS PDSCH; One or more symbols that are scheduled to transmit the Physical Uplink Control Channel (PUCCH) containing the received feedback in the identified time slot or sub-time slot are semi-static flexible symbols. Sending one or more of the semi-static flexible symbols of the time slot or sub-time slot dynamically configured as downlink, uplink, or flexible dynamic time slot format indicator (SFI); and The SFI is used to determine whether to monitor the receipt feedback in the scheduled time slot or sub-time slot, in a subsequent time slot or sub-time slot, or both.

11. The method of claim 10, wherein the network entity decides to monitor the confirmation feedback in the scheduled time slot when the dynamic SFI indicates that all semi-static flexible symbols of the time slot or sub-time slot are uplinks, and also monitors the confirmation feedback in subsequent time slots or sub-time slots.

12. The method of claim 10, wherein the network entity decides whether to monitor the receipt feedback in the subsequent time slot or sub-time slot, regardless of what the SFI indicates.

13. The method of claim 10, wherein if the dynamic SFI indicates that at least one of the semi-static flexible symbols is downlink or flexible: The network entity does not monitor the confirmed feedback in the scheduled time slot or sub-time slot; and The network entity monitors the receipt feedback in the subsequent time slot or sub-time slot.

14. The method of claim 10, further comprising sending a signaling notification to the UE instructing at least one of the following configurations: The maximum number of times the confirmed feedback report can be repeated by the UE; or The maximum number of time slots that the confirmed feedback report can be delayed.

15. The method of claim 10, wherein: The UE is configured to cancel reporting the reception confirmation feedback in the identified time slot or sub-time slot and delay it to a subsequent time slot or sub-time slot, regardless of what the UE receives in the SFI or whether the UE receives or fails to receive the SFI; and The network entity is configured to monitor the receipt feedback in the subsequent time slot or sub-time slot.

16. The method of claim 15, wherein the network entity is configured to monitor the acknowledgment feedback in a time slot or sub-time slot of uplink symbols where all symbols of the resource for reporting the acknowledgment feedback are semi-statically configured.

17. A user equipment (UE) for wireless communication, comprising: At least one processor coupled to the memory, said at least one processor being configured to: The identifier is used to report the time slot or sub-time slot for receiving feedback for the Semi-Persistent Scheduling (SPS) Physical Downlink Shared Channel (PDSCH); One or more symbols that are scheduled to transmit the Physical Uplink Control Channel (PUCCH) containing the received feedback in the identified time slot or sub-time slot are semi-static flexible symbols. The monitoring dynamically configures one or more of the semi-static flexible symbols in the time slot or sub-time slot as downlink, uplink, or flexible dynamic time slot format indicator (SFI); and The monitoring determines whether the confirmation feedback should be reported in the scheduled time slot or sub-time slot, in a subsequent time slot or sub-time slot, or both.

18. The UE of claim 17, wherein the at least one processor is further configured to: if the UE receives the dynamic SFI indicating all semi-static flexible symbols of the time slot or sub-time slot as uplink, decide to report the reception feedback in the scheduled time slot.

19. The UE of claim 18, wherein the at least one processor is further configured to: determine whether to repeat the receipt feedback in a subsequent time slot or sub-time slot.

20. The UE of claim 17, wherein if the UE does not detect the dynamic SFI, the UE decides to cancel the confirmation feedback in the scheduled time slot or sub-time slot and reports the confirmation feedback in the subsequent time slot or sub-time slot.

21. The UE of claim 17, wherein if the UE receives an indication that at least one of the semi-static flexible symbols is a downlink or a flexible dynamic SFI, the UE decides to cancel the confirmation feedback in the scheduled time slot or sub-time slot and reports the confirmation feedback in the subsequent time slot or sub-time slot.

22. The UE of claim 17, wherein the at least one processor is further configured to receive a configuration indicating at least one of the following: The maximum number of times the confirmed feedback report can be repeated by the UE; or The maximum number of time slots that the confirmed feedback report can be delayed.

23. The UE of claim 17, wherein the at least one processor is further configured to cancel reporting the reception feedback in the identified time slot or sub-time slot and delay it to a subsequent time slot or sub-time slot, regardless of what the UE receives in the SFI or whether the UE receives or fails to receive the SFI.

24. The UE of claim 23, wherein the UE reports the receipt feedback delayed until all symbols of the resource for which the PUCCH is used to report the receipt feedback are semi-statically configured as uplink symbol slots or sub-slots.

25. The UE of claim 23, wherein the at least one processor is further configured to: Cancel reporting the received feedback in the identified time slot or sub-time slot; and The confirmation feedback is delayed to a subsequent time slot or sub-time slot.

26. A network entity for wireless communication, comprising: At least one processor coupled to a memory, wherein the at least one memory is configured to: Transmit Semi-Persistent Scheduling (SPS) Physical Downlink Shared Channel (PDSCH); The time slot or sub-slot that is scheduled for User Equipment (UE) to report confirmation feedback for the SPS PDSCH; One or more symbols that are scheduled to transmit the Physical Uplink Control Channel (PUCCH) containing the received feedback in the identified time slot or sub-time slot are semi-static flexible symbols. Sending one or more of the semi-static flexible symbols of the time slot or sub-time slot dynamically configured as downlink, uplink, or flexible dynamic time slot format indicator (SFI); and The SFI is used to determine whether to monitor the receipt feedback in the scheduled time slot or sub-time slot, in a subsequent time slot or sub-time slot, or both.

27. The network entity of claim 26, wherein the at least one processor is further configured to: determine, in the case that the dynamic SFI indicates all semi-static flexible symbols of the time slot or sub-time slot as uplinks, to monitor the confirmation feedback in the scheduled time slot, and also to monitor the confirmation feedback in subsequent time slots or sub-time slots.

28. The network entity of claim 26, wherein the at least one processor is further configured to determine whether to monitor the receipt feedback in a subsequent time slot or sub-time slot, regardless of what the SFI indicates.

29. The network entity of claim 26, wherein if the dynamic SFI indicates that at least one of the semi-static flexible symbols is downlink or flexible: The network entity does not monitor the confirmed feedback in the scheduled time slot or sub-time slot; and The network entity monitors the receipt feedback in the subsequent time slot or sub-time slot.

30. The network entity of claim 26, wherein the at least one processor is configured to send a signaling notification to the UE indicating at least one of the following configurations: The maximum number of times the confirmed feedback report can be repeated by the UE; or The maximum number of time slots that the confirmed feedback report can be delayed.

31. The network entity as claimed in claim 26, wherein: When the UE is configured to cancel reporting the confirmation feedback in the identified time slot or sub-time slot and delay it to a subsequent time slot or sub-time slot, regardless of what the UE receives in the SFI or whether the UE receives or fails to receive the SFI, the network entity is configured to monitor the confirmation feedback in the subsequent time slot or sub-time slot.

32. The network entity of claim 31, wherein the at least one processor is configured to monitor the acknowledgment feedback in a time slot or sub-time slot of uplink symbols where all symbols of the PUCCH resource for reporting the acknowledgment feedback are semi-statically configured.

Images